Hi i have H3G_UK_1.29.771.11 with hboot_0.96.0000 with own rom, rooted, now i will Only update the Hboot and the other new stuff, like Radio... but i will have my rom like it is, the rom is 2.17 base
the hboot i will use is H3G_UK_2.17.771.3 with hboot_1.12.0000
is this possible
Update:
i have made a firmware.zip with
android-info.txt
hboot_1.12.0000.img
rcdata.img
skiped
boot.img and recovery.img whos i have the one i what on my phone alredy
is this gona work?
fastboot oem rebootRUU
fastboot flash zip firmware.zip
Just flash the RUU and be done with it!
Hmm no if i need to do it i wait for JB RUU...
EddyOS said:
Just flash the RUU and be done with it!
Click to expand...
Click to collapse
Always better to be up-to-date IMO, at least if you use the new RUU now you only have to run the OTA once JB is released so you only have to set things up again now
But to answer your question, it's not advisable to try and flash just the HBOOT as you need other FW parts to go with it and the RUU is designed to run together
Ok...
so i flash the recovery from H3G_UK_1.29.771.11 relock bootloder
run H3G_UK_2.17.771.3 RUU DONE?
and after i can unlock bootloader and root like before?
Absolutely! Although you won't be able to get the JB OTA if you're rooted (well, you can be it's more hassle then it's worth IMO)
EddyOS said:
Absolutely! Although you won't be able to get the JB OTA if you're rooted (well, you can be it's more hassle then it's worth IMO)
Click to expand...
Click to collapse
Why wouldn't you just want to relock the bootloader and then run RUU??? can't you unlock bootloader like before and then flash CWM and the whole rooting process again after updating to 2.17 and hboot 1.12... anyway whats the point of updating to hboot1.12??? its still has ICS
I have an international stock HTC One M9. CID is: HTC__621 and firmware version: 210.709.1 - I've already found the stock recovery for 210.709.1 - I'm looking to install a custom ROM, but I may want to go back to stock later on. I found a TWRP stock backup for 210.709.1, but because I am S-ON, will I not have to manually flash the boot.img? I used winrar to look into the TWRP backup, and I could not find a boot.img. So, my question is: if I flash the TWRP backup using TWRP, will the boot.img automatically get flashed?
You will have to flash the boot.img manually. The boot image is there it should be called boot.emmc.win .
mrbtree98 said:
You will have to flash the boot.img manually. The boot image is there it should be called boot.emmc.win .
Click to expand...
Click to collapse
Should I rename this to: "boot.img"? And then, use command: " fastboot flash boot boot.img"?
mrbtree98 said:
You will have to flash the boot.img manually. The boot image is there it should be called boot.emmc.win .
Click to expand...
Click to collapse
There's no "boot.emmc.win" within the archive? I can't find it...
arif9m9 said:
Should I rename this to: "boot.img"? And then, use command: " fastboot flash boot boot.img"?
Click to expand...
Click to collapse
Some weeks ago I was told that all newer phones than the HTC One M7 are able to flash boot images with TWRP even if they are S-ON. (I wasn't able to verify that since my phone is S-OFF.) So there should be no need to rename and manually flash the boot image if it's already inside the backup.
arif9m9 said:
There's no "boot.emmc.win" within the archive? I can't find it...
Click to expand...
Click to collapse
You can find the needed boot image in my signature.
Flippy498 said:
You can find the needed boot image in my signature.
Click to expand...
Click to collapse
Thanks. I downloaded: "boot_2.10.709.1.img" from your signature. Do I just flash it in fastboot like this: fastboot flash boot boot_2.10.709.1.img"? Is it okay if I rename it to just: boot.img?
My M9 is completely stock, right now. I'm intending to: unlock the bootloader, flash TWRP recovery, and finally, install an ASOP ROM.
When attempting to go back to stock, I'm going to: boot into TWRP, wipe everything except for SD card, flash the 2.10.709.1 TWRP stock backup, boot into fastboot and flash the command: "fastboot flash boot boot_2.10.709.1.img", flash the stock 2.10.709.1 recovery, and finally, relock the bootloader. Will all these steps be correct for an attempt to go back to stock?
arif9m9 said:
Thanks. I downloaded: "boot_2.10.709.1.img" from your signature. Do I just flash it in fastboot like this: fastboot flash boot boot_2.10.709.1.img"? Is it okay if I rename it to just: boot.img?
My M9 is completely stock, right now. I'm intending to: unlock the bootloader, flash TWRP recovery, and finally, install an ASOP ROM.
When attempting to go back to stock, I'm going to: boot into TWRP, wipe everything except for SD card, flash the 2.10.709.1 TWRP stock backup, boot into fastboot and flash the command: "fastboot flash boot boot_2.10.709.1.img", flash the stock 2.10.709.1 recovery, and finally, relock the bootloader. Will all these steps be correct for an attempt to go back to stock?
Click to expand...
Click to collapse
If you use the backup from my signature you only need to follow the instructions on the first page of my google sheet to get back to stock.
Be warned: Since Android 5.1 you should only relock the bootloader if you are completely sure that your phone is able to boot to system and that you ticked the new option that allows a bootloader unlock (can be found in the developers options). Many users already got stuck with a non-booting phone that cannot be re-unlocked because they didn't fulfill these requirements. (Sidenote: If you only want to get back to stock to install new OTAs you don't need to relock your bootloader.)
Besides I read that some people stated that the AOSP roms of the M9 messed up their LTE reception (so that LTE was even unusable on other custom roms or stock rom). I don't know whether this problem is already fixed. Some weeks passed since I read about that problem so I suggest you to read the corresponding threads before you start flashing.
arif9m9 said:
Thanks. I downloaded: "boot_2.10.709.1.img" from your signature. Do I just flash it in fastboot like this: fastboot flash boot boot_2.10.709.1.img"? Is it okay if I rename it to just: boot.img?
My M9 is completely stock, right now. I'm intending to: unlock the bootloader, flash TWRP recovery, and finally, install an ASOP ROM.
When attempting to go back to stock, I'm going to: boot into TWRP, wipe everything except for SD card, flash the 2.10.709.1 TWRP stock backup, boot into fastboot and flash the command: "fastboot flash boot boot_2.10.709.1.img", flash the stock 2.10.709.1 recovery, and finally, relock the bootloader. Will all these steps be correct for an attempt to go back to stock?
Click to expand...
Click to collapse
There is no need to flash the boot.img separately on this phone.
As noted DO NOT RELOCK unless you have ticked that "allow oem unlocking" option first. I cannot stress this enough.
Also, no AOSP rom currently has a working camera.
iElvis said:
There is no need to flash the boot.img separately on this phone.
As noted DO NOT RELOCK unless you have ticked that "allow oem unlocking" option first. I cannot stress this enough.
Also, no AOSP rom currently has a working camera.
Click to expand...
Click to collapse
My phone is S-ON, won't I have to flash the boot.img via fastboot?
arif9m9 said:
My phone is S-ON, won't I have to flash the boot.img via fastboot?
Click to expand...
Click to collapse
Flippy498 said:
Some weeks ago I was told that all newer phones than the HTC One M7 are able to flash boot images with TWRP even if they are S-ON.
Click to expand...
Click to collapse
iElvis said:
There is no need to flash the boot.img separately on this phone.
Click to expand...
Click to collapse
No, it's not needed. The only exceptions are backups that don't contain a boot image (like mine for example). That's why I created the google sheet with the instructions.
Flippy498 said:
No, it's not needed.
Click to expand...
Click to collapse
But, when installing custom ROMS, I'll definitely have to use the fastboot command to flash the boot image, right?
arif9m9 said:
But, when installing custom ROMS, I'll definitely have to use the fastboot command to flash the boot image, right?
Click to expand...
Click to collapse
No.
Flippy498 said:
No.
Click to expand...
Click to collapse
But, I'm S-ON....
arif9m9 said:
But, I'm S-ON....
Click to expand...
Click to collapse
It hasn't been an S-on restriction since the M7.
iElvis said:
It hasn't been an S-on restriction since the M7.
Click to expand...
Click to collapse
Does that mean I can flash RUUs even if I'm S-ON?
arif9m9 said:
Does that mean I can flash RUUs even if I'm S-ON?
Click to expand...
Click to collapse
For your CID/MID, yes.
iElvis said:
For your CID/MID, yes.
Click to expand...
Click to collapse
But, all the 'Returning to stock' guides
for the M9 state S-OFF is obligatory?
arif9m9 said:
But, all the 'Returning to stock' guides
for the M9 state S-OFF is obligatory?
Click to expand...
Click to collapse
It depends. If you have a current RUU for your phone (i.e., you don't need to downgrade), you can run it S-on, as that's what it's for.
But if you need to downgrade because the only RUU is an earlier version, yes you do need s-off.
S-off also allows you to go back to LOCKED instead of RELOCKED.
iElvis said:
It depends. If you have a current RUU for your phone (i.e., you don't need to downgrade), you can run it S-on, as that's what it's for.
But if you need to downgrade because the only RUU is an earlier version, yes you do need s-off.
S-off also allows you to go back to LOCKED instead of RELOCKED.
Click to expand...
Click to collapse
When going back to stock, at which stage should I relock my bootloader?
arif9m9 said:
But, all the 'Returning to stock' guides
for the M9 state S-OFF is obligatory?
Click to expand...
Click to collapse
Because if you follow these guides your phone will state "locked" instead of "relocked" at the end. And that is only possible with S-OFF. Besides with S-ON you can only use RUUs with the same firmware version as your phone (or newer RUUs)*.
*Actually downgrades seem to be possible, too, but as far as I know only if the two first numbers of the firmware versions before and after the downgrade are the same. Like from 1.32.xxx.15 to 1.32.xxx.8 but not from 1.40 versions to 1.32 versions or from 2.xx versions to lower versions.
Edit: Looks like I didn't type fast enough.
Can someone help me with relocking my Moto G5? i have looked everywhere and nothing works! please help
Locking my Bootloader. Sorry i forgot to add that
aaronboy205 said:
Locking my Bootloader. Sorry i forgot to add that
Click to expand...
Click to collapse
Try doing the following
Code:
fastboot oem lock begin
Now enter all the commands to flash stock firmware then
Code:
fastboot oem lock
So you should end up with something like this
Code:
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem lock
Be aware that you can still tell the bootloader has been previously unlocked as normally when you unlock the bootloader it blows a fuse which can never be replaced (I presume unless you replace the entire motherboard)
Okay I'll try that. Cheers
Doesn't work! Just says "still require signed boot.img"
aaronboy205 said:
Doesn't work! Just says "still require signed boot.img"
Click to expand...
Click to collapse
And I presume you have flashed boot.img from an official firmware during the process
If so find another firmware or I don't know the answer
So does that mean i can't relock my bootloader!?
RIGHT! I've locked the bootloader but now everytime i boot it. It says "Your device has loaded a different operating system" it would be great if it didn't
aaronboy205 said:
So does that mean i can't relock my bootloader!?
Click to expand...
Click to collapse
it means you need a signed boot.img so if the one you are flashing during the process isnt signed find another
try this one
https://forum.xda-developers.com/attachment.php?attachmentid=4191493&d=1498252560
There probably is a way but without doing it all myself I cant tell you
It's okay now. I think thanks anyway
TheFixItMan said:
Try doing the following
Now enter all the commands to flash stock firmware then
So you should end up with something like this
Be aware that you can still tell the bootloader has been previously unlocked as normally when you unlock the bootloader it blows a fuse which can never be replaced (I presume unless you replace the entire motherboard)
Click to expand...
Click to collapse
There's no fuse that goes they can't tell if its been unlocked its not Knox , its when u get the unlock code they no the devices serial number . If you hard brick they can't necessaly tell!
infixremix said:
There's no fuse that goes they can't tell if its been unlocked its not Knox , its when u get the unlock code they no the devices serial number . If you hard brick they can't necessaly tell!
Click to expand...
Click to collapse
Oh! Thanks for the information dude!
aaronboy205 said:
It's okay now. I think thanks anyway
Click to expand...
Click to collapse
So... you get it done?
renanfamous said:
So... you get it done?
Click to expand...
Click to collapse
Yes but then I unlocked it again coz u think ROMS are going to be better than stock!
Cant be done i dont think
aaronboy205 said:
Can someone help me with relocking my Moto G5? i have looked everywhere and nothing works! please help
Click to expand...
Click to collapse
The issue is in the signed boot image. you see, you need the official motorola firmware to be able to lock the bootloader again as they only have the signed boot images. :/
Why are you trying to relock the bootloader btw?
hello to everyone , I would like to know how to re lock the bootloader and unroot and flash to stock global rom. If anyone can help it would be much appreciated. I am currently using RR on china dev base (chiron)
thanks
I believe if you wipe and flash stock, it relocks the bootloader.
alose said:
I believe if you wipe and flash stock, it relocks the bootloader.
Click to expand...
Click to collapse
thanks will try that!
or fastboot oem lock
animaleyes76 said:
or fastboot oem lock
Click to expand...
Click to collapse
alose said:
I believe if you wipe and flash stock, it relocks the bootloader.
Click to expand...
Click to collapse
i flashed the stock rom but still unlocked bootloader
if i do the fastboot method will it work? have you tried it? do i have a chance of bricking the device?
Terole said:
i flashed the stock rom but still unlocked bootloader
if i do the fastboot method will it work? have you tried it? do i have a chance of bricking the device?
Click to expand...
Click to collapse
It was fine for me. If you are still a bit nervous use the Xiaomi flash tool to flash a fastboot stock Rom and pick the flash and relock option in the bottom right http://en.miui.com/a-234.html
Terole said:
i flashed the stock rom but still unlocked bootloader
if i do the fastboot method will it work? have you tried it? do i have a chance of bricking the device?
Click to expand...
Click to collapse
Did you ever get your bootloader relocked? I'm getting the Mi Mix 2s (China Version) on friday and wondering how to flash stock global and then relock bootloader.\