Go back from Oreo to Nougat and lock your device - Honor 8 Guides, News, & Discussion

TESTED DEVICES
FRD-L09 (By me)
Code:
/*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this GUIDE
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
WHAT YOU NEED
1. Your device, unlocked, upgraded to Oreo and with TWRP by @Pretoriano80 for the P10
2. The B416 rollback zip (download it on Firmware Finder) and HuRUpdater by @zxz0O0 (tested only with 0.4).
3. MicroSD card (you can use internal memory too, but it's a bit more complicated).
4. Your PC (You'll find out why you need it).
5. Your USB cable.
HOW TO
1. Put HuRUpdater and the 3 files you have downloaded before on MicroSD card (remember to rename it correctly!)
2. Reboot ro TWRP
3. Factory reset on TWRP (that will fix your data encryption, we need it later).
4. Reboot to TWRP
5. Flash HuRUpdater
6. Turn off your device and reboot to eRecovery (device still be bootloader unlocked).
7. Make a factory reset on eRecovery.
8. Boot your device (just to make sure it works as expected).
9. Shutdown your device and boot it on bootloader.
10. Fastboot oem relock your device.
11. Boot your device normally.
12. On developer options re-enable FRP.
13. Turn off device and reboot to eRecovery
14. Download B416 FULL and leave it installing.
15. Voilà! You device is on Nougat and locked again!

"FUN FACTS"
This method will remove the ability to update to Oreo via HiSuite or eRecovery so no official upgrade because Oreo build is older than that build

If someone try that guide for other device and works please tell me here or via PM

Hello there,
There's a simpler way to relock your device. Simply use HiSuite from your computer. From HiSuite version 9, you can rollback to Nougat and then upgrade back to Oreo. When searching for updates in HiSuite, Nougat is displayed as an option, from there you can rollback. It'll relock your phone. If it doesn't, while on Nougat, simply relock with Multi-Tool 8 that you can find here on XDA.

Sideness said:
Hello there,
There's a simpler way to relock your device. Simply use HiSuite from your computer. From HiSuite version 9, you can rollback to Nougat and then upgrade back to Oreo. When searching for updates in HiSuite, Nougat is displayed as an option, from there you can rollback. It'll relock your phone. If it doesn't, while on Nougat, simply relock with Multi-Tool 8 that you can find here on XDA.
Click to expand...
Click to collapse
Not at all HiSuite works. On mine for example doesn't work

Related

[GUIDE][REBRAND] HONOR 8 [ONLY EMUI 4.1] [NOT FOR DUAL SIM USERS]

Disclaimer:
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this TOOL
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
So before giving a huge explanation on useless stuff with a prolonged explanation, as the title itself says this thread is meant only for users who ever willing to rebrand their Honor 8. Currently , i worked a bit with !nsideOut , One of the members of TeamMT and i successfully rebranded my Honor 8 FRD-L04(US variant) to FRD-L02 (INDIAN variant) . I request Dual sim users dont try this as the zip itself includes oem specific files of Indian Variant so u will loose the dual sim functionality.
A BIG NOTE : DO NOT TRY THIS ON EMUI 5 . ALL INFO IS EXTRACTED FROM EMUI4.1 AND SO ONLY MARSHMALLOW (EMUI4.1) USERS SHOULD TRY THIS .​
Procedure for Rebranding to L-02:
unlock bootloader
Install TWRP recovery from here
reboot ur phone to homescreen
goto settings/storage and set sdcard as default storage
Download L-02 stock update.app [Emui 4.1 B160][size 1.49gb]
Copy UPDATE.APP to sdcard/dload/
download and Install zip from the attachments or Download here
Now reboot to recovery through adb by using the command
Code:
adb reboot recovery
Once twrp boots up , search for the downloaded zip and install it from recovery.
Now poweroff from recovery.
use the 3 button trigger to install update.app (click VOL UP+VOL DOWN + POWER simultaneously)
Now u will find the update.app starts flashing.
Procedure for Rebranding to L-04:
unlock bootloader
Install TWRP recovery from here
reboot ur phone to homescreen
goto settings/storage and set sdcard as default storage
Download L-04 stock update.app [Emui 4.1 B122][size 1.57 GB]
Copy UPDATE.APP to sdcard/dload/
download and Install zip from the attachments or Download here
Now reboot to recovery through adb by using the command
Code:
adb reboot recovery
Once twrp boots up , search for the downloaded zip and install it from recovery.
Now poweroff from recovery.
use the 3 button trigger to install update.app (click VOL UP+VOL DOWN + POWER simultaneously)
Now u will find the update.app starts flashing.
Credits:
!nsideOut
TeamMT​
XDA:DevDB Information
Honor 8 Rebrand, Tool/Utility for the Honor 8
Contributors
gopinaidu77
Version Information
Status: Stable
Created 2017-05-27
Last Updated 2017-06-25
Reserved
Reserved
@gopinaidu77
Hi gopinaidu77, do you have FRD-DL00 oeminfo file? I debranded my DL00 but I forgot back up my oeminfo, now I really need help to go back...

Rescue - restore - downgrade - ze500kl

Hi Everyone! ZE500KL is my 2nd Asus device after FE170CG. As usual, would like to share a short tutorial on how to restore stock ROM / downgrade to Lollipop / rescue after being bricked.
Disclaimer
You have been warned!
I am not responsible for bricked devices, dead SD cards or
thermonuclear war. Please do some research before attempting
this procedure. The firmwares provided below are from official
sources and is provided as it is. The procedure has been tested
only on 8 GB variant of Asus Zenfone 2 Laser(Ze500KL) and no
issues has been observed. Make sure the hardware is intact.
You are totally on your own. If you point the finger at me for
messing up your device, I will laugh at you.
Stuffs Needed:
Stock ROMs - Lollipop 12.8.5.222 WW / Marshmallow 13.1010.1612.53 WW
Stock Recovery (Signed) - 12.8.5.222 / 12.8.5.118 (old)
Asus Drivers
ADB tools - For flasing recovery, clearing data, cache & system and starting clean
Device charged atleast 75%
Procedure:
1. Boot up the device into fastboot mode using vol up + power keys
2. Flash the stock recovery using
Code:
fastboot flash recovery recovery.img
3. Now clean the device using the commands one by one
Code:
fastboot erase cache
fastboot erase userdata
fastboot erase system
4. Now power off the device
5. Copy the latest Lollipop / Marshmallow ROM zip to the sd card without errors
NOTE: Marshmallow OTA will look for the lastest Lollipop build - 12.8.5.222 before starting the flash. So flash the recovery V 12.8.5.222(Link above) and it will be automatically upgraded during the flash
6. Insert the SD card into the phone
7. Now boot into the recovery using vol down + power keys
8. You should see the stock recovery we flashed earlier
9. Do a factory reset for consistency
10. Now install the ROM using SD card option and follow the prompts
11. On successful install, select the restart option
First boot will take a bit(Be patient!) and you should see the welcome screen if all went well. Good Luck!
Once the recovery is installed successfully, then It should be a piece of cake to install the ROM. I did above method lots of times without failures. I had to downgrade to Lollipop due to insufficient internal storage(8 GB) since I use lots of apps for my office use which can't be avoided!

[Developer Verified] [TESTED] [WORKING] Meizu m3 Note Bootloader Unlock Tool

RADev Team Presents:
Bootloader Unlock Tool for Meizu m3 Note M91 (TESTED) (WORKING)​
Warning:- This tutorial is only for M3 Note (M91). Do not try it on Meizu m3 note (L91)
If you still want to try it, you're on your own as although the developer claims that it is working on Meizu m3 note (L91) it hasn't been tested
Backup all your personal data, contacts, everything to your PC/laptop as all your personal data will be lost after following this tutorial
I am not responsible for bootlooping, hard bricked, soft bricked devices, however, i will try my best to help you out of it and our team will release a hard brick fixing tool for Meizu m3 note (M91) soon. (Links will be posted here)
After you perform these steps, your phone will not have a firmware installed. You will have to manually install the firmware again.
Requirements:-
1. A mildly functioning brain
2. Ability to follow specific instructions
3. Root
4. A Meizu m3 note
5. Unlocker tool
6. A PC/laptop with ADB installed
Steps:
1. Upgrade to 6.7.9.12 daily WITH CLEAR DATA TICKED, other versions have not been tried or tested by me, I was successful in unlocking the bootloader by testing the apk on this firmware.
Link for 6.7.9.12 daily firmware:- https://download.meizu.com/Firmware.../cn_daily/20170912000320/3d65e1ba/update.zip
2. Install ADB on your system (Follow this link if you don't know the steps):- https://forum.xda-developers.com/showthread.php?t=2588979
3. Login to your Meizu account on your phone then go to Settings>Fingerprint & Security>Root Permission and enter Meizu account password. Phone will reboot and root itself.
4. Download the unlocker.apk from here and install it on the phone:- https://drive.google.com/open?id=0By0YAAxheuSKaDJ1YXJKYUJSVkk
5. Open unlocker app and grant it root permission. Click on unlock and wait till it shows unlock success and #END in the last and 2nd last line
Tip:-You can also follow the original developers on QQ (They are great guys and allowed our team to mirror, modify and post the unlock tool without wanting anything in return)
6. Now turn off the device and boot into Fastboot mode by pressing Volume Up + Power button at the same time. You will see a small dialog in the bottom corner of the phone saying 'Fastboot Mode..."
7. Connect your phone to PC, open command prompt on Windows or terminal in Linux and type
Code:
fastboot devices
. If the device ID is shown then it means that your phone is ready for flashing. If not, try installing ADB Drivers again.
8. After the device is detected in fastboot mode, type
Code:
fastboot oem unlock
Do not panic if it doesn't unlock in the first try. Keep trying. It took me a while to get it unlocked. Follow the steps on the phone when you type fastboot unlock. IT will prompt you to either press the volume up or volume down button to confirm the execution of the command you've given.
9. After the bootloader unlock is successful, power off your device.
10. Restarting the device will show you that there is no firmware installed on the phone, will wait for 5 seconds and then boot into TWRP.
11. This happened because the tool we used earlier to unlock the phone installed TWRP while unlocking the device.
12. The TWRP is quite buggy and cannot mount data and system partitions as it was ported a long time ago. To fix this, go to Wipe>Advanced Wipe in TWRP and format every partition.
13. If that doesn't work then repair file system in twrp of every partition you can. After this you'll be good to go.
If you face any difficulty following any of the steps mentioned here please join our Chatbox and Channel on Telegram so that our 1000+ members can help you out
Channel:- https://t.me/RADevTeam
ChatBox:- https://t.me/FlymeChatBox
Other useful links:-
Hard Brick Fix Tool for Meizu m3 Note:- https://forum.xda-developers.com/android/development/developer-verified-meizu-m3-note-hard-t3682743
We will also be posting a new TWRP, hard brick fixing tool and a new custom ROM for the phone. Please support us
Our work is and always will be 100% free of charge. Being a developer is not easy and requires a lot of time and resources. If you like our job PLEASE CONSIDER DONATING.​Donation Link:- http://radevdonate.blogspot.com​
So, congratulations! Your bootloader has been unlocked. You're free to do anything you want on your Meizu device
Thanks RADev Team
Excellent post thank you =) :fingers-crossed:
Thank you very much :highfive:
Thanks very much.
And wait for your Los ROM :highfive:
#need help
I am stuck at
check ok
###END
phantom rippers said:
I am stuck at
check ok
###END
Click to expand...
Click to collapse
me too
I successfully installed TWRP, but i can't install any firmware. I always have an error 7. Help me please.
daniil_min said:
I successfully installed TWRP, but i can't install any firmware. I always have an error 7. Help me please.
Click to expand...
Click to collapse
Hey use the twrp by sxrhd. That works flawlessly
Unlock boot loader please
Flyme 7 will not be releasing for meizu m3 note( l91) please unlock bootloader
HI there! Is there a way to upgrade current android version 5.1 on meizu m3 note l681h to a newest android version? Why nobody doest try it? Or tried and failed? Can't find any info about it. I don't want flyme 7 etc, i want upgraded android for install Gcam on this meizu.
"We will also be posting a new TWRP, hard brick fixing tool and a new custom ROM for the phone. Please support us."------I want to know how can I get the new TWRP and the new custom ROM.I'd appreciate very much if you could help me.

P9 lite brick? @transition Nougat-MM. PHONE locked, FRP unlock

Hi, second post on the forums, I'm in bigger trouble now.
I unlocked my bootloader and then rooted my VNS-L21 so I could edit my hosts file. I tried going back to official and unrooted firmware afterwards, but something went wrong along the way.
The stages:
-OFW VNS-L21C432B504, obtained bootloader code through DC-unlocker (developer options on, OEM unlock on, debug usb on)
-unlocked bootloader with SRKtool using this method get-instant-huawei-bootloader-unlock-code/
-rooted using Magisk and made a full backup through Revolution Recovery using this method https://ministryofsolutions.com/2018/05/huawei-p9-lite-root-for-nougat-new-method.html
- some tinkering here but don't remember exactly plus I guess it's not that relevant ; I think I got rid of root here
- downgraded from Nougat to MM using dload method according to this thread https://forum.xda-developers.com/hu...torial-rollback-n-to-mm-c432-devices-t3563955 (first flashing rollback package from C432B504 to C900B300, then flashing C432B160 - full)
- everything went fine, bootloader relocked; but I was unable to upgrade to Nougat/B504 - settings-update showed "no updates available", putting update.app in dload folder (obtained from firmware finder, TeamMT, full B504 file) didn't work, pressing three buttons resulted in error (the version not compatible or sth)
-tried dload with previous rollback file
...and now I'm here:
- phone constantly stuck at boot screen (red Huawei logo)
- dload not starting by pressing three buttons
- recovery not starting by pressing volume up
The only thing I can get is white fastboot screen when connected to PC. It says "phone locked" (bootloader) in green, "FRP unlocked" in red. As usb debugging/oem unlock were not enabled this time, platform-tools/adb with command "adb devices" says nothing is connected, similar goes for SRK
Is it hopeless and my phone is thrash or is there anything I can do? Please help!
PS. All I wanted to do with my root was to change hosts file and then unroot/relock phone, seems like it wasn't worth all this work ( https://forum.xda-developers.com/huawei-p9lite/help/retaining-modified-hosts-file-unrooting-t3868641 )
Update: "fastboot devices" in adb directory resulted in detecting my device, next I found and tried command "fastboot oem [PASSWORD]", now there's a change: "This device cannot be trusted" is showing again, in fastboot I see "PHONE Unlocked" in red now. So time to flash some firmware with a command? But which firmware and how exactly to do that?
You have again unlocked your Bootloader? I suggest you flash a Nougat Compatible TWRP and then from within TWRP make wipes. After that use Hurupdater to flash Nougat firmware. First flash TWRP. If it boots into TWRP then format data and then wipe Dalvik/Art Cache, Cache, Data, System and Internal. Next download Hurupdater and stock Nougat Firmware. You need to download three ZIP update.zip, update_data_full_public.zip and regional update file. Next rename them as suggested in Hurupdater thread. Finally place all four files in same folder in SD card and then install and select only Hurupdater.zip to flash. After it complete reboot to stock recovery and factory reset. If all goes well you will be on Nougat.
Thank you so much, HuRU update method was what finally got me from Marshmallow to Nougat
So. I take it your phone is working now? Glad to know and be of help. If you need help with anything then just ask
Yes, it is, I'm currently struggling with systemless hosts on my Magisk rooted Nougat but other than that - everything works fine. Turns out that most of the recoveries I found then were meant for Nougat, only one recovery file worked on Marshmallow (and I've tried quite a few of such files and they were hard to find).
________________
After flashing TWRP recovery, updating Magisk to 17.3 beta and installing newest (4.0.10) version of Adaway - the problem is gone. My guess is that the fault was on Magisk's side as after updating it the "systemless hosts" function in Adaway was no longer grayed out.

[GUIDE] Relocking bootloader on custom ROMs

Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
This guide will teach you how to relock bootloader on custom ROMs to increase the security of your device
Commands:
Relock:
Code:
fastboot flashing lock_bootloader
Or if not available:
Code:
fastboot oem lock
Unlock:
Make sure to have the OEM unlocking option enabled in developers settings and do:
Code:
fastboot oem unlock-go
Or
Code:
fastboot flashing unlock
Requirements and warnings:
- The ROM you're flashing MUST be signed, otherwise it won't boot
- The recovery must be signed as well, so all the TWRP builds since the 3.3.0-1 one you can find here
- Wiping data isn't necessary and will be avoided by TWRP itself, but if you want to switch from locked to unlocked or vice versa without wiping, make sure to delete locksettings.db in /data/system (from recovery)
- With a locked bootloader you'll be able to boot signed ROMs and recovery without issues, and also to install new ones. You'll be able to access the recovery without issues and the 5 seconds warning will still be there (although different).
- To make sure that nothing gives issues, also uninstall magisk before relocking or unlocking bootloader (unless you plan to wipe data anyway)
Downloads:
Official LineageOS signed builds
Official TWRP signed builds (3.3.0-1 and newer)
If you appreciate my work on Z2 and my effort to keep this device active and alive you can donate to me via paypal here​
Hnm
Bootloader relocked fine...
No issues...
A small paypal donation. Transaction # 17403731NK2381648
DD3Boh said:
This guide will teach you how to relock bootloader on custom ROMs to increase the security of your device
Commands:
Relock:
Or if not available:
Unlock:
Make sure to have the OEM unlocking option enabled in developers settings and do:
Or
Requirements and warnings:
- The ROM you're flashing MUST be signed, otherwise it won't boot
- The recovery must be signed as well, so all the TWRP builds since the 3.3.0-1 one you can find here
- Wiping data isn't necessary and will be avoided by TWRP itself, but if you want to switch from locked to unlocked or vice versa without wiping, make sure to delete locksettings.db in /data/system (from recovery)
- With a locked bootloader you'll be able to boot signed ROMs and recovery without issues, and also to install new ones. You'll be able to access to recovery without issues and the 5 seconds warning will still be there (even if different).
- To make sure that nothing gives issues, also uninstall magisk before relocking or unlocking bootloader (unless you plan to wipe data anyway)
Downloads:
Official LineageOS signed builds
Official TWRP signed builds (3.3.0-1 and newer)
If you appreciate my work on Z2 and my effort to keep this device active and alive you can donate to me via paypalhere
Click to expand...
Click to collapse
I am having bootloop (means whenever its connected to charging it is alright but after disconnected it is having bootloop)and I tried everything possible but nothing works...also qfill and changing battery not works... Still it's alright whenever it connected to source.... Now pc isn't detecting adb to try out.. Please guide
Well I tried following this guide with a fresh installation of official LineageOS 16 and the latest TWRP, but I ended up with my phone constantly rebooting back to recovery and having to format data. Maybe my problem was because I was using encrypted data?
I do have one question. How exactly does that improve the security of the device? One of my biggest concerns with using custom ROMs is that if my phone was lost or stolen, someone could easily boot into TWRP and copy files from the storage or delete locksettings.db to gain access to everything like accounts, payment methods, personal photos, etc. To combat this I have always used encrypted data, since TWRP will not be able to show data without the encryption password. But there are a couple of downsides to this; reduced performance, much slower boot-times, and delayed Android updates via custom ROMs. (None of the Android 10 ROMs support encryption which means I am stuck on Android 9 for the time being, which is frustrating when everyone else had the update months ago)
So if there was a way I could somehow secure my data without having the device encrypted, that would be a huge advantage. However, I fail to see how just locking the bootloader 'improves security' when someone could still boot into TWRP and easily retrieve data? Hope you might be able to offer some insight. @DD3Boh
No mention of user-settable root of trust? Will I risk bricking my device if I follow these steps on Galaxy S10e running LineageOS?

Categories

Resources