Lock bootloader and restore recovery - Honor 7X Questions & Answers

Hey all,
Is it possible to relock bootloader and restore stock recovery? I have stock room with root and twrp but want to revert back to full stock. Anyone know if that is possible currently?

I'm pretty sure the only stock firmware that has been released for this device is the Chinese variant. If you're on the L24 variant like I am there is no way to get back to stock of you rooted and installed twrp unless you made your own backups.

I made my own backup from stock but would like to make sure I get any OTAs. I assume I need to get back to a locked bootloader?

Nope. I have an unlocked bootloader and I just got an OTA yesterday. Installed with no problem. The twrp is a definite reason why one wouldn't be able to install ota and I'm not 100% sure but I think that being rooted is another although I've read conflicting stories about the root part.

Related

[Q] Bell Desire Z stok Rom

Hi
I'm desperately looking for any Bell mobility stock 1.34.666.5 or Over.
The camera button is not working so I sent my phone to repair but they send it back because I do not have the right rom that was provided with my phone. I was able to unroot and put back 1.34.666.1 (the only one that is available it seems) but the technical support told me that my phone shipped with 1.34.666.5 and that they can't do anything unless I'm putting back this rom.
I tried getting OTA updates for 1.34.666.1 but it's not available. Minimum rom # to get OTA updates have to be 1.34.666.5
I'm screwed.
Regards
I have a nandroid backup of the stock ROM...it's rooted though.
Will I be able to flash using Clockwork Recovery? I can manage to remove root after flashing, I think.
Yes, flashable via Clockwork.
I'll let you know when I have it uploaded.
...and it's up.
https://xda:[email protected]/_xda/Bell.DZ.Stock.ROOTED.7z
Some notes:
- I only included the system and boot portions of the nandroid backup due to privacy concerns
- As such, you should do a system and boot restore (after a full wipe, of course) under "Advanced Restore"
- As mentioned earlier, this is rooted (so you'll need to unroot)
Hope this helps. Let us know how it goes.
Good news, I have been able to return to stock 1.34.666.5. Thank you very much for your backup.
I was thinking going unrooted was to be easy but i'm a little bit stuck.
How can I unroot and put back stock bootloader without flashing a new rom.
If I have to flash a new rom, is there a way to build one based on the backup you provided?
I've look at software update and there's an OTA update available for my phone. I tried to install but because I do not have the right bootloader (I think that's the problem) I'm unable to do the OTA update.
Thanks.
Tonkadan said:
Good news, I have been able to return to stock 1.34.666.5. Thank you very much for your backup.
I was thinking going unrooted was to be easy but i'm a little bit stuck.
How can I unroot and put back stock bootloader without flashing a new rom.
If I have to flash a new rom, is there a way to build one based on the backup you provided?
I've look at software update and there's an OTA update available for my phone. I tried to install but because I do not have the right bootloader (I think that's the problem) I'm unable to do the OTA update.
Thanks.
Click to expand...
Click to collapse
That's good to hear. I'd recommend making your own nandroid backup immediately.
As for the bootloader, you're sure you flashed the ENG HBOOT during the rooting process? If that's the case, I'm not sure where you can find the stock HBOOT...
Yes, I installed the Eng HBoot.
I'm trying now renaming the OTA update.zip, put on the root of sdcard and make recovery to install that update but I got an error about getprop CID?? and the update failed...
Still looking for a solution.
How did you make out Tonkadan? I'm in the same boat. I heard that if you did apply this update that you would not be able to root your phone anymore.
I' still rooted. I'm unable to go back to stock. I'm using cyanogenmod 7 for now but would really want to go back to stock if somone have the official Bell rom over 1.34.666.5.
... Or any way to get OTA updates for RUU 1.34.666.1 that is available on shippedroms.com

Help installing a "generic" ROM

Long story short, I purchased a One X from Amazon that was supposed to be an unlocked international version. Turns out it's a T-Mobile Germany version.
Everything works fine, but it has bloat on it and it's on a slightly older software version (1.28.111.10) and I'd like to make it a generic version that I can install updates on when they come out.
Can someone point me in the right direction? Where can I get a stock Generic rom for the Tegra 3 version?
I'm assuming my first steps are:
Unlock at HTC Dev
Install Clockwork Mod Recovery
I'm kind of a noob at this, or at least a novice, so any help would be appreciated. I was going to send the phone back, but it seems a shame if I can basically get it to be the way I want anyway.
For what i understand you want to be able to recieve OTAs, right?
You need stock recovery to update the phone, and i dont know if changing your CID will make the device recieve the different updates.
Why not try some stock roms?
http://forum.xda-developers.com/showthread.php?t=1546970
http://forum.xda-developers.com/showthread.php?t=1648527
that wont be able to receive OTAs but hey its updated.
I never used any of those 2 but mike is doing a good work with ARHD which might be an option.
fredfb said:
For what i understand you want to be able to recieve OTAs, right?
You need stock recovery to update the phone, and i dont know if changing your CID will make the device recieve the different updates.
Why not try some stock roms?
http://forum.xda-developers.com/showthread.php?t=1546970
http://forum.xda-developers.com/showthread.php?t=1648527
that wont be able to receive OTAs but hey its updated.
I never used any of those 2 but mike is doing a good work with ARHD which might be an option.
Click to expand...
Click to collapse
Okay, so to flash one of those stock ROMs, I have to flash Clockwork first, flash the rom, then flash stock recovery again to be able to get updates, correct? I suppose I could just leave it Clockwork and then flash the updates manually.
Once you flash a custom ROM, even based off of stock, you do not want to receive OTA's as that could mess up with the Dev did and cause you issues. The Devs will keep their ROMs up to date so you just flash their updates manually with Clockworkmod.
greyhulk said:
Okay, so to flash one of those stock ROMs, I have to flash Clockwork first, flash the rom, then flash stock recovery again to be able to get updates, correct? I suppose I could just leave it Clockwork and then flash the updates manually.
Click to expand...
Click to collapse
You see, i never tried that. I dont know if those stock roms are able to recieve the update, but you could flash them using CWR.
And the devs will most likely update the stock roms. its not really be a big issue. You can always use something like titanium backup to save everything you want, even tho flashing an updated version of stock rom shouldnt mess anything up.
greyhulk said:
Long story short, I purchased a One X from Amazon that was supposed to be an unlocked international version. Turns out it's a T-Mobile Germany version.
Everything works fine, but it has bloat on it and it's on a slightly older software version (1.28.111.10) and I'd like to make it a generic version that I can install updates on when they come out.
Can someone point me in the right direction? Where can I get a stock Generic rom for the Tegra 3 version?
I'm assuming my first steps are:
Unlock at HTC Dev
Install Clockwork Mod Recovery
I'm kind of a noob at this, or at least a novice, so any help would be appreciated. I was going to send the phone back, but it seems a shame if I can basically get it to be the way I want anyway.
Click to expand...
Click to collapse
If I were you I would send the phone back and demand the version you ordered.
You wont be able to flash a WWE RUU because we don't have S-Off yet however as everyone has mentioned above you can Unlock via HTCDev, flash Clockwork and then flash away with your desired custom rom.

[Q] Downgrading CM11 to stock 4.3 on i747M

I know there are a few threads regarding this issue but I can't seem to find a definitive answer.
I am currently running stock 4.3 jellybean (rooted). My phone hasn't received the 4.4 KitKat update yet, so I wanted to install CM11 in order to get KitKat on my s3. However, I heard CM11 can be buggy on the s3, so in case things go south, I want to be able to revert back to the stock 4.3 rom. Some people have said that you can easily flash the stock ROM via ODIN. However, others said that downgrading from 4.4.2 to 4.3 will hard brick the device since installing CM11 updates the boot loader. So downgrading to 4.3 stock with a 4.4.2 boot loader will cause a hard brick according to other threads I've seen. My question is, how can I downgrade from CM11 to stock 4.3 safely without bricking? Thanks in advance.
If you are sure you are using a Canadian version of the i747m, you can flash back to stock in Odin using a stock 4.3 ROM for the phone's original carrier (Bell, Rogers, Telus).
audit13 said:
If you are sure you are using a Canadian version of the i747m, you can flash back to stock in Odin using a stock 4.3 ROM for the phone's original carrier (Bell, Rogers, Telus).
Click to expand...
Click to collapse
Yes I got the phone from Rogers, it's most definitely i747M. But do I have to worry about any issues with the bootloader? I'm assuming installing CM11 will install the 4.4.2 bootloader, so if I choose to downgrade to the stock 4.3 rom, will it cause any issues seeing as I'm running a 4.3 rom with a 4.4.2 bootloader? I just want to make sure because I heard it can cause some serious problems if the bootloader is newer than the rom.
Mzrz said:
Yes I got the phone from Rogers, it's most definitely i747M. But do I have to worry about any issues with the bootloader? I'm assuming installing CM11 will install the 4.4.2 bootloader, so if I choose to downgrade to the stock 4.3 rom, will it cause any issues seeing as I'm running a 4.3 rom with a 4.4.2 bootloader? I just want to make sure because I heard it can cause some serious problems if the bootloader is newer than the rom.
Click to expand...
Click to collapse
I have never come across a custom ROM that touches the bootloader. A compatible bootloader has to be loaded on the phone before you attempt to install the custom ROM. Supported bootloaders can be found in the ROM's updater script.
I assume your phone has no warranty since you rooted it on stock 4.3. Did you root it by installing a pre-rooted ROM?
You could copy a ROM to your external SD card, install Philz Touch via Odin, reboot directly to recovery, create a nandroid backup, wipe cache, Dalvik, data, and install your KK ROM.
audit13 said:
I have never come across a custom ROM that touches the bootloader. A compatible bootloader has to be loaded on the phone before you attempt to install the custom ROM. Supported bootloaders can be found in the ROM's updater script.
I assume your phone has no warranty since you rooted it on stock 4.3. Did you root it by installing a pre-rooted ROM?
You could copy a ROM to your external SD card, install Philz Touch via Odin, reboot directly to recovery, create a nandroid backup, wipe cache, Dalvik, data, and install your KK ROM.
Click to expand...
Click to collapse
Okay, I was just making sure because I know OTA updates can change the bootloader, so I just wanted to make sure the custom roms don't do that. As for the custom recovery, are you recommending Philz Touch over CWM and TWRP? Do you know which custom recovery is installed from the CM installer?
audit13 said:
I have never come across a custom ROM that touches the bootloader. A compatible bootloader has to be loaded on the phone before you attempt to install the custom ROM. Supported bootloaders can be found in the ROM's updater script.
I assume your phone has no warranty since you rooted it on stock 4.3. Did you root it by installing a pre-rooted ROM?
You could copy a ROM to your external SD card, install Philz Touch via Odin, reboot directly to recovery, create a nandroid backup, wipe cache, Dalvik, data, and install your KK ROM.
Click to expand...
Click to collapse
Oh and one more question, my phone was originally carrier locked to Rogers and unrooted on 4.3 jelly bean. I brought it in to a cell store for them to carrier unlock it for me, but they used a rooting method to unlock it (because SuperSU was installed on it when I brought it back). They didn't unlock it with a code, so I'm guessing they used something like Samsung Tool or z3x shell. If I install CM11, will I lose the unlock, considering it's more of a "soft unlock", or is the unlock permanent regardless of how many roms I flash? Thanks for your help!
Mzrz said:
Okay, I was just making sure because I know OTA updates can change the bootloader, so I just wanted to make sure the custom roms don't do that. As for the custom recovery, are you recommending Philz Touch over CWM and TWRP? Do you know which custom recovery is installed from the CM installer?
Click to expand...
Click to collapse
Philz is based on the latest release of CWM and I prefer CWM over TWRP because I had problems flashing ROMs. Once I switched to Philz/CWM, no more problems.
Mzrz said:
Oh and one more question, my phone was originally carrier locked to Rogers and unrooted on 4.3 jelly bean. I brought it in to a cell store for them to carrier unlock it for me, but they used a rooting method to unlock it (because SuperSU was installed on it when I brought it back). They didn't unlock it with a code, so I'm guessing they used something like Samsung Tool or z3x shell. If I install CM11, will I lose the unlock, considering it's more of a "soft unlock", or is the unlock permanent regardless of how many roms I flash? Thanks for your help!
Click to expand...
Click to collapse
The unlock should be permanent. I unlocked it using the free method when on 4.1.1 and no ROM has ever caused it to re-lock. Reflashing a completely stock ROM, including the bootloader, did not relock the phone.
Please remember that flashing and changing ROMs will always carry a risk of soft bricking or hard bricking your phone. Make sure you read all of the guides and be prepared for disaster.
Good read here: http://forum.xda-developers.com/showthread.php?t=2201860

How do you unlock an i747M locked to Fido? [OctOS L 5.1.1]

So I'm planning to switch carriers and I'm wondering how I can unlock my i747M locked to Fido that's running OctOS L 5.1.1. If I have to downgrade, how do I transfer all my current app data and pic's. Also, is it possible to keep the unlock if you were to update you phone to a higher version or install a custom ROM or install the nandroid backup you made before unlocking? Please leave me with some important things to know about while unlocking your phone if possible!
If the phone is running a 4.3 or newer bootloader, you'll have to buy an unlock code.
In order to enter the unlock code, the phone should be running a stock samsung ROM from sammobile.
I suggest creating a nandroid backup with TWRP, copy the backup to your computer, flash the stock ROM, perform a factory reset after flashing stock, unlock, flash TWRP, restore nandroid.
audit13 said:
If the phone is running a 4.3 or newer bootloader, you'll have to buy an unlock code.
In order to enter the unlock code, the phone should be running a stock samsung ROM from sammobile.
I suggest creating a nandroid backup with TWRP, copy the backup to your computer, flash the stock ROM, perform a factory reset after flashing stock, unlock, flash TWRP, restore nandroid.
Click to expand...
Click to collapse
so, in a nutshell, i just need to downgrade my phone to a stock rom of 4.3 or below and just search up a video of how to unlock it using the keypad method?
than if i wanted to, i could use the nandroid backup i did before and flash it and still have an unlocked phone?
You cannot use the free method once the phone is running a 4.3 or newer bootloader because you cannot properly run the 4.1.1 modem on a 4.3 or 4.4.2 bootloader and the 4.3 or 4.4.2 bootloader cannot be downgraded to a 4.1.1 bootloader.
Before flashing anything, which bootloader is on the phone?
audit13 said:
You cannot use the free method once the phone is running a 4.3 or newer bootloader because you cannot properly run the 4.1.1 modem on a 4.3 or 4.4.2 bootloader and the 4.3 or 4.4.2 bootloader cannot be downgraded to a 4.1.1 bootloader.
Before flashing anything, which bootloader is on the phone?
Click to expand...
Click to collapse
Sorry for the noob question, but how do i found out my bootloader?
If this helps, my baseband is I747MVLUFOB3
I actually just logged on to get similar clarification. I have an unlock code, but it does not work when I enter it using OctOS-M. Do I need to be on a stock rom to unlock? Can I easily jump back to a stock rom, then back again to a marshmallow rom?
JoshMcMadMac said:
I actually just logged on to get similar clarification. I have an unlock code, but it does not work when I enter it using OctOS-M. Do I need to be on a stock rom to unlock? Can I easily jump back to a stock rom, then back again to a marshmallow rom?
Click to expand...
Click to collapse
From what ive heard, you have to be on a stock rom. As of google, even then, some users have problems or cant, which from what ive heard, can be fixed by downgrading to 4.3 (make sure ur bootloader is the same or your phone WILL be bricked).
Please note that this is from what ive heard and may not be accurate.
Install the Samsung phone info app from the play store as it will tell you a lot.
audit13 said:
Install the Samsung phone info app from the play store as it will tell you a lot.
Click to expand...
Click to collapse
My boot loader seems to be the same as my baseband.
What is the bootloader version?
GamingDevilsCC said:
From what ive heard, you have to be on a stock rom. As of google, even then, some users have problems or cant, which from what ive heard, can be fixed by downgrading to 4.3 (make sure ur bootloader is the same or your phone WILL be bricked).
Click to expand...
Click to collapse
That sounds problematic...I am on NJ2. I am not having any luck finding anything about getting back to stock on the newest bootloader.
audit13 said:
If the phone is running a 4.3 or newer bootloader, you'll have to buy an unlock code.
In order to enter the unlock code, the phone should be running a stock samsung ROM from sammobile.
I suggest creating a nandroid backup with TWRP, copy the backup to your computer, flash the stock ROM, perform a factory reset after flashing stock, unlock, flash TWRP, restore nandroid.
Click to expand...
Click to collapse
Do you think this one would work?
https://z3x-team.com/forum/topic.php?id=9505
Whats a CWM anyways?
CWM is Clockworkmod with is a custom recovery. CWM is outdated as it has not been updated for quite some time. Many recent custom ROMs now require TWRP.
You may be able to software unlock the phone but you'll probaby need a UART cable and Samsung Pro tools. I don't believe Pro Tools is free.
The linked thread is from 2014 and, in 2014, many phones were running 4.1.2 which meant the phone could be downgraded to 4.1.1 using and sim unlocked using the dialler's menu options.

Android 6 update w/ TWRP?

Hello,
I have rooted my HTC One m8(No S-OFF). It also has TWRP and it's on Android 5.0.1/HTC Sense 6
I googled and read about reverting to stock recovery and then doing an OTA upgrade of the OS. But I'd rather not go back to stock and then TWRP back again.
Is there any way or instructional to follow that can enable me to update to Android 6 whilst keeping TWRP and my root settings on.
Any help is appreciated
My experience, is that Marshmallow ROMs work fine on Lollipop firmware. I've been doing so since December, for no better reason than I've been too lazy to update my firmware.
So that means you should be able to just restore the proper Marshmallow TWRP backup for your version, and just run that without updating anything else. Although, be sure to leave yourself an escape plan, just in case it doesn't work (either your own LP backup, or be prepared to use one from the collection).
However, for best compatibility, you should really update your firmware. And doing so, either by flashing stock firmware, OTA, or RUU by "official" means (and official/signed means are what you need to use, since you are s-on) will by definition wipe out TWRP.
But honestly, flashing TWRP back to the phone is easy. You just download the .img file to your computer, than flash with a single fastboot command, with the phone connected. This is actually a fast and simple process, when compared to the other stuff you are talking about doing (restoring stock backup and recovery, OTA update).
Plus, since you are updating to Marshmallow, you'll also want to update to TWRP 3.0.2 anyway.
redpoint73 said:
My experience, is that Marshmallow ROMs work fine on Lollipop firmware. I've been doing so since December, for no better reason than I've been too lazy to update my firmware.
So that means you should be able to just restore the proper Marshmallow TWRP backup for your version, and just run that without updating anything else. Although, be sure to leave yourself an escape plan, just in case it doesn't work (either your own LP backup, or be prepared to use one from the collection).
However, for best compatibility, you should really update your firmware. And doing so, either by flashing stock firmware, OTA, or RUU by "official" means (and official/signed means are what you need to use, since you are s-on) will by definition wipe out TWRP.
But honestly, flashing TWRP back to the phone is easy. You just download the .img file to your computer, than flash with a single fastboot command, with the phone connected. This is actually a fast and simple process, when compared to the other stuff you are talking about doing (restoring stock backup and recovery, OTA update).
Plus, since you are updating to Marshmallow, you'll also want to update to TWRP 3.0.2 anyway.
Click to expand...
Click to collapse
Thanks redpoint73.
My chief motivation behind moving to Android 6 is a sound problem I've been having lately. I installed the AcousticX sound mod but when I listen to audiobooks, I hear a clipping sound sometimes.
The developer over @ AcousticX suggested a few things and one of which was making the switch to marshmallow.
thread: http://forum.xda-developers.com/showthread.php?p=68881108#post68881108
From some reading and your suggestions, I gathered the right way to go about this is, is to flash stock recovery(overriding twrp). Do an OTA upgrade(1.6 gb download/install) and afterwards reinstall TWRP and whatever else was previously done.
Am I correct in surmising this?
Thanks
AadilK said:
From some reading and your suggestions, I gathered the right way to go about this is, is to flash stock recovery(overriding twrp). Do an OTA upgrade(1.6 gb download/install) and afterwards reinstall TWRP and whatever else was previously done.
Am I correct in surmising this?
Click to expand...
Click to collapse
Not only the stock recovery, but you also need to restore the unrooted TWRP backup (never rooted ROM, "unrooting" doesn't work). Since having root will prevent OTA.
The full process is described here: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
The other option, depending on what M8 version you have, may be to RUU to Marshmallow. That allows you skip a lot of the steps needed in the previous method (restoring a never rooted TWRP backup, restoring stock recovery, OTA updated) but adds a couple other steps (relock bootloader to RUU, unlock it again after RUU to flash TWRP); plus the RUU will wipe all user data on the device.
So its a judgment call for you (if your version has RUU) what path is preferred.

Categories

Resources