Database Users

[Guide] Safely unlock bootloader on official MM

UPDATE: This is now unneeded because threr is a faster way ro unlock bootloader on official MM here, he updated for official MM
Hi, I discovered an unlock method for official MM!! This maybe long but's it totally safe
You need:
Adb and fastboot environment ready PC
LP RAW File
Android 6.0 Beta Unlock tool
Android 5.0 One-Click Unlock tool
First version of beta MM (Z00A) (Z008)
Official MM zip (find it on Asus site)
Thanks to all people upload these links
Just do the following:
Flash the lastest LP via AFT (using raw file given above), wipe all data. If you already on MM, you have to downgrade
Unlock your bootloader using 1 click tool given above
Boot to stock recovery and sideload the first version of beta MM
Unlock the bootloader using MM beta unlock tool above
Boot to stock recovery
Two case here:
Case 1: You can't boot stock recovery
Normally boot your phone (to Android)
Setup it as a new phone
If it shows there is a new firmware, don't update!!!
Enable Developer options, then enable usb debugging
Copy the official MM zip to external sd card
Open command prompt, run adb reboot recovery, accept the adb permission if prompted
After it boots to recovery, select Apply update from SD, then choose the zip file you've copied before
Wait for it to update, it may stuck at flashing splashcreen, don't worry, it's trolling you, may be Asus forgot to update the script
Goto step 7
Case 2: You can boot stock recovery
Sideload the official MM zip (adb sideload <filename>.zip)
Goto step 7
7. Flash this TWRP (fastboot flash recovery <twrp>.img)
8. Root your phone using this method
9. Reboot, if it shows "Your phone has failed verification bla bla..", then you've success. It may reset loop like note 7 in the first time start, don't worry.
9. Enjoy :highfive:
Note: If you're facing with battery problems on MM, factory reset it in Settings > Backup and Reset > Factory Reset > Erase everything
Successfully on my ZE550ML
The warning screen is normal so don't worry and there is no way to fix it for now

Reverse

Reverse #2

Please answer this I have a unlocked Bootloader + twrp Intalled + root, now I am really confused that after upgrading to MM will my Bootloader get automatically lock or what
Sent from my ASUS_Z00A using XDA-Developers mobile app

NiTesh said:
Please answer this I have a unlocked Bootloader + twrp Intalled + root, now I am really confused that after upgrading to MM will my Bootloader get automatically lock or what
Sent from my ASUS_Z00A using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes, BL will be relocked once you upgrade to MM.
If you want to unlock MM BL(6.0), refer to this thread.
Or you can downgrade to Lollipop referring to this thread. Then your BL(5.0) is unlocked.

Upgrade to MM
Hello folks!
2 week before MM was released i'ved opted to unlock my ZE551ML BL and therefore install twrp and a MM custom ROM..
so here´s the thing i stayed with the ROM for about 3 weeks and honestly..it works very well..but when i knew that 6.0 official was coming out i decided to go back to stock..i did it following manny tuturials avaliable for me to get my BL Re-Locked..but unsuccessfully..so i followed mr_gourav2000 tuturial (http://forum.xda-developers.com/zenfone2/development/stock-rom-ul-z00a-ww-2-20-40-168-t3354526) and reverted to the WW_Z00A-2.20.40.183-to-2.20.40.184 (hopefully i can get the sshot in this post) version...since my BL is unlocked i can´t get no updates..my question is:
Is there anyway to go to MM 6.0 by ASUS with the current status of my phone?
is there anything i can do to revert this??
Cheers to everyone
https://www.dropbox.com/sc/xue7iuqfyvgdvo3/AAATR4mYtcHzM1IhfKbx2a1oa

R3D SoX F4N said:
Hello folks!
2 week before MM was released i'ved opted to unlock my ZE551ML BL and therefore install twrp and a MM custom ROM..
so here´s the thing i stayed with the ROM for about 3 weeks and honestly..it works very well..but when i knew that 6.0 official was coming out i decided to go back to stock..i did it following manny tuturials avaliable for me to get my BL Re-Locked..but unsuccessfully..so i followed mr_gourav2000 tuturial (http://forum.xda-developers.com/zenfone2/development/stock-rom-ul-z00a-ww-2-20-40-168-t3354526) and reverted to the WW_Z00A-2.20.40.183-to-2.20.40.184 (hopefully i can get the sshot in this post) version...since my BL is unlocked i can´t get no updates..my question is:
Is there anyway to go to MM 6.0 by ASUS with the current status of my phone?
is there anything i can do to revert this??
Cheers to everyone
https://www.dropbox.com/sc/xue7iuqfyvgdvo3/AAATR4mYtcHzM1IhfKbx2a1oa
Click to expand...
Click to collapse
Just download the update package and rename it to mofd_sdupdate.zip, copy it to internal storage. Then reboot to stock recovery, the update will automatically start. This should work if you have lastest stock recovery

can anyone please upload official recovery for Zenfone 2 ZE551ML, currenty i have twrp installed on Android version 5.0 LP Stock

HungNgocPhat said:
Just download the update package and rename it to mofd_sdupdate.zip, copy it to internal storage. Then reboot to stock recovery, the update will automatically start. This should work if you have lastest stock recovery
Click to expand...
Click to collapse
i have twrp recovery at the moment cause i followed mr_gouvad2000 tuturial..
what do you sugest?
flash WW_ZE551ML_2.20.40.196_20160815.raw?
WW_ZE551ML_2.20.40.194_20160713.raw?
and then go and do what you told?
cheers

hello, i cant find first mm beta for ml551...can you help me? thank you and sorry for my english

tridet18 said:
hello, i cant find first mm beta for ml551...can you help me? thank you and sorry for my english
Click to expand...
Click to collapse
someone correct me if i am worng but....
https://www.asus.com/Phone/ZenFone_2_ZE551ML/HelpDesk_Download/
Look for this version WW-4.21.40.134

Hello, thank you but this version is official, i need de first beta 6.0
R3D SoX F4N said:
someone correct me if i am worng but....
Look for this version WW-4.21.40.134
Click to expand...
Click to collapse

that version...i can´t find it anywere..maybe someone here knows were to find it?

Updated the first MM beta link in OP

hello , thanks to your tutorial I managed to unlock the bootloader , I have TWRP version 3.0.0.2 with stock installed but when I wanted to install CM13 and gapps I restarted the phone and automatically returns to recovery again. some help?

tridet18 said:
hello , thanks to your tutorial I managed to unlock the bootloader , I have TWRP version 3.0.0.2 with stock installed but when I wanted to install CM13 and gapps I restarted the phone and automatically returns to recovery again. some help?
Click to expand...
Click to collapse
Have you downloaded the correct build? There are build for MM bootloader, if you flash the normal builds, it will fail and reboot to recovery again. Gapps is the same for all builds
After you install that special build, do not update to newer nightlies, it will fail. For updates, check the link i give you and see if there is a new MMBL build.
About that, here is the post: http://forum.xda-developers.com/showpost.php?p=68542370&postcount=8551

hello friend, I tried to install the CM13 ROM that indicated me and I get Error 7 in TWRP 3.0.2.0, I have Android 6.0 (.134) official and if I can change kernel and flash rom SuperSU but change with a new MM Blows I can not (CM13, AICP, beanstalk ....) thanks for your help!

tridet18 said:
hello friend, I tried to install the CM13 ROM that indicated me and I get Error 7 in TWRP 3.0.2.0, I have Android 6.0 (.134) official and if I can change kernel and flash rom SuperSU but change with a new MM Blows I can not (CM13, AICP, beanstalk ....) thanks for your help!
Click to expand...
Click to collapse
Run the script again (i gave you in above post). Download the CM13 in that link, not in the OP of CM13 thread. Flash that CM13 and Gapps (Gapps is universal for MMBL and LPBL).
May be you have corrupt download, I'm currently running CM13 on MMBL

Hello, I have finally found the solution, the problem is the recovery, the TWRP 3.0.0.2 da failure with new builds, I Flashed next on the link you put me through adb and now it works, thank you very much for everything .

hlp
tridet18 said:
Hello, I have finally found the solution, the problem is the recovery, the TWRP 3.0.0.2 da failure with new builds, I Flashed next on the link you put me through adb and now it works, thank you very much for everything .
Click to expand...
Click to collapse
how u unlocked bootloader

[GUIDE] Error 7 Solution While flashing 7.1.2 ROMs

A brief Intro.
Starting from the 7.1.2 ROMs most of the developers decided to follow the process of checking modem version at the time of flashing the rom. Many peoples ended up in
"Error 7- assert(xiaomi.verify_modem("MSM8976.LA.1.0.c3-30041-STD.PROD-1.77504.1.83742.1") == "1")"
The main reason for this is the outdated firmware or it is happened to those who had unofficially unlocked the bootloader.
Some more info..
1. You must be on MM build bootloader. If you are unofficially unlocked bootloader it will give you ERROR7.
@TheStrix have alreday given a short information about it in his Official LineageOS thread. If you are unaware of it read it here
2.Outdated Firmware.
Your firmware must be from from MIUI Global DEV v7.5.4 or above.
Get MIUI Global DEV v7.5.4 from here
or the latest firmware from here
NB:-
- Iam using the MIUI Global DEV v7.5.4 firmware. All working fine including Volte. I dont know about the second one,you can give it a try.
-If you are unofficially unlocked ,MIUI Global DEV v7.5.4 will re lock your bootloader you will end up in bootloop.
- I will not be reponsible for any damages.
Solution 1 [Permanent Solution] ..
1. So if you are unofficially unlocked, i will suggest to clean flash the latest MIUI Fatboot Rom. Kenzo users get it from here.
2.Flash it using MIFlashTool ,and officially unlock it.
HOW TO UNLOCK THE BOOTLOADER OF REDMI NOTE 3?
PART 1 : REQUESTING FOR UNLOCK PERMISSION
Step 1 – Open up your favorite web browser in your computer (Chrome is recommended) then go to this link
Step 2 – You’ll see the official page of “Unlock Your Mi Device”. Now simply click on the blue “Unlock Now” Button in the middle of the page.
Step 3 – You’ll see a login page in the next page which is in Chinese. If you use Google Chrome to open the page, then you can simply use its built-in Google Translate feature.
Step 4 – Once logged in, you’ll see the Unlock Application Permissions page.Now simply fill in all required fields then click on that green Apply Immediately button.
Step 5 – In the next page, you’ll need to enter a verification code sent to you via SMS. Check your phone for any SMS verification sent by Xiaomi server. The code is usually valid for only 5 minutes so you need to enter it immediately.
Step 6– Once you have submitted the 6 digits code, you’ll then be redirected to another page saying that from the point toward all you need to do is just waiting for Xiaomi Developers to review and approve your application. Once approved, you’ll get another SMS which normally arrives in 15 min(Atleast for me. For some it may take time). The approval process is manual so just be patient on this.
PART 2 : BOOTLOADER UNLOCKING PROCESS
Requirements for Bootloader Unlocking :
-An active Mi account linked to your device, your phone number and it has permission to proceed with bootloader unlock (follow previous steps above)
-Please backup your data for just in case scenario.
-Again, if you are not fully aware of flashing custom ROM, then you better stay away of unlocking your phone’s bootloader.
Download Mi Flash Unlock tool for Windows here, and install it on your computer / PC.
Step 1 – On your device, please login to your Mi account.
Step 2 – Put / reboot your device into bootloader mode. To do that, simply turn off your device, press the Power button and Volume down ( – ) button at the same time.
Step 3 – On your computer, open MiFlash Unlock tool you’ve just installed. Click on the Agree button when asked.
Step 4 – Login to MiFlash Unlock tool with the same Mi Account.
Step 5 – Now connect your phone to computer using its USB cable.
Step 6 – Once your phone is connected, the Unlock button will become active. Next, simply click on the Unlock button to start the process. The unlock process will take about 10 – 15 seconds to complete. That’s all.
After unlocking your phone’s bootloader, you’ll be able to flash TWRP and other custom ROM. Enjoy..
Please take these as your concern upon unlocking bootloader :
One Mi account could only unlock one device within 30 days.
If you see a notice saying that “current user is not logged in connected device” then please reboot your device normally then login with your account in the device (see Step 1).
Unlocking bootloader will wipe all user data especially if your device is encrypted. That’s why you’ll need to create backup before going to proceed.
Neither Xiaomi or I will guaranteed if anything goes wrong during and as the result of unlocking. Proceed with your own risks.
Also, unlocked Xiaomi devices will be marked in the official service end.
PART 3 : Installing TWRP and Custom Rom.
Step 1 –. Get latest TWRP from here. Flash it via fastboot { I will not be explaining that in details}
Step 2 –. Take back up of EFS using Twrp. Wipe Everything including internal storage.
Step 3 –. Install Firmware-Rom-Gapps in order. Error 7 will be solved
Solution 2[Temporary Solution] ..
Only try this method if you are not able to officially unlock your device . Dont use the Firmware by Strix.It will relock your bootloader.
Step1 - Downalod the rom to your pc.
Step2 - Use any notepad. Suggestd one Notepad++. Get it from here
Step3 - Open the Rom.zip{dont extarct}. Navigate to META-INF/com/google/android/updater-script.
Double click on updater-script and open it with notepad++. Edit and remove this line from the file
Code:
assert(xiaomi.verify_modem("MSM8976.LA.1.0.c3-30041-STD.PROD-1.77504.1.83742.1") == "1")
Allow the file to save and close the zip.{Rom will recompress by itself}.
Step4 - Flash in order. Firmware -Rom-Gapps.
Some FAQ's ..
1. Iam not getting volte
Ans:- Restore the EFS. Try rebooting your phone 2 or 3 times. After Clean flash ,I had to reboot 3 times to get volte working. :fingers-crossed:
2.Iam not able to see FingerPrint Option?
Ans:- Your are defenitely on an old Firmware.Update to Latest Firmware It will work.
3.Iam getting Some other Errors. :crying:
Ans:- Post your Screen Shot Below.Will Check.
4.Iam getting some other problems in ROM.
Ans:- Report it with proper logs to the developer.Iam helpless.
5.I bricked my device
Ans:- I will Laugh at you. Always do everything at your own risk. :silly:
Some Advices ..
* At least use search once in your life time. From my observation its clear that no one ever uses search in the Rom Section. Even is there is a solution in every page you keep on asking same questions.
*Dont flood the thread.
*Dont qoute the whole op.
*Respect other members
If this was of help to anyone hit the like :fingers-crossed:

First

There's a problem with not updating the bootloader (aboot) and staying with a LP bootloader, you will most likely encounter bootloops. Say you edit that code line for the modem check, it will flash but it won't boot/work properly. You must update the bootloader in order to boot newer ROMs. And you need to update the modem and other stuff so you won't face issues. You need to offcially unlock no matter what you do, it's very easy.

Asphyxiate666 said:
There's a problem with not updating the bootloader (aboot) and stay with a LP bootloader, you will most likely encounter bootloops. Say you edit that code line for the modem check, it will flash but it won't boot. You must update the bootloader in order to boot newer ROMs. And you need to update the modem and other stuff so you won't face issues. You need to offcially unlock no matter what you do, it's very easy.
Click to expand...
Click to collapse
that's why I wrote temporary method..only for those who are lazy and not willing to start from root by flashing fastboot rom

adithyan25 said:
that's why I wrote temporary method..only for those who are lazy and not willing to start from root by flashing fastboot rom
Click to expand...
Click to collapse
I understand but with their laziness they will ruin their devices then come here and say "omg sir it doesn't boot wtf is this useless rom crap developers".

Asphyxiate666 said:
I understand but with their laziness they will ruin their devices then come here and say "omg sir it doesn't boot wtf is this useless rom crap developers".
Click to expand...
Click to collapse
I know that...most people don't even bother to use search..even if there is a solution just above their question they won't give a damn to look it..

guys help..i had officially unlocked the bootloader..and i don't remember the firmware i had installed...n i am still getting the error code 7..do i need to flash the kenzo global or dev firmware from the link..??

PrathaM X said:
guys help..i had officially unlocked the bootloader..and i don't remember the firmware i had installed...n i am still getting the error code 7..do i need to flash the kenzo global or dev firmware from the link..??
Click to expand...
Click to collapse
you must format your phone (not wipe) using twrp then install fw-rom-gapps...use fw by strix from above method(permanent)

I flashed v8.5.1.0 using MiFlash and it said flash completed successfully. However now it is stuck on the Mi splash screen with "powered by android" logo at the bottom. The dots are moving so I assume it is loading but it's been on that same screen for the past 10 minutes now.
Previously, the bootloader was officially unlocked but some stuff broke as I tried to upgrade to a new ROM and that's why I decided to flash v8.5.1.0 in order to go back to stock and start from scratch.
Edit: It works!

adithyan25 said:
you must format your phone (not wipe) using twrp then install fw-rom-gapps...use fw by strix from above method(permanent)
Click to expand...
Click to collapse
I'm on Marshmallow boot loader (flashed faatboot ROM) and officially unlocked & formated data.
Yesterday I did a update RR ROM (9th july) then I got error 7.
at the time of flashing I was on latest firmware 7.7.6.
So reflashed 7.5.4 firmware and it's worked.
So we should always stick to 7.5.4 firmware ? For avoiding error 7?

baku2313 said:
I'm on Marshmallow boot loader (flashed faatboot ROM) and officially unlocked & formated data.
Yesterday I did a update RR ROM (10th july) then I got error 7.
at the time of flashing I was on latest firmware 7.7.6.
So reflashed 7.5.4 firmware and it's worked.
So we should always stick to 7.5.4 firmware ? For avoiding error 7?
Click to expand...
Click to collapse
yep..in my knowledge the latest firmware has a change in modem version(updated version) so it wont match with one in updater script... so i will say to stick with some older firmware unless the developers chabge it in the roms update-script file...
iam using strix fw 7.6.15

adithyan25 said:
yep..in my knowledge the latest firmware has a change in modem version(updated version) so it wont match with one in updater script... so i will say to stick with some older firmware unless the developers chabge it in the roms update-script file...
iam using strix fw 7.6.15
Click to expand...
Click to collapse
Can you provide me the link please.

baku2313 said:
Can you provide me the link please.
Click to expand...
Click to collapse
its in the aosp extended 4.4 update op...
im quite busy now...i will share it later if you havent found it .... you will find the link in aosp extended thread

adithyan25 said:
its in the aosp extended 4.4 update op...
im quite busy now...i will share it later if you havent found it .... you will find the link in aosp extended thread
Click to expand...
Click to collapse
Strix updated his thread with 7.7.6 firmware (Kenzo).

I am on MM on Redmi note 3 Snapdragon version! I tried firmware (7.7.0 I guess) and then ROM Zip but still got the Problem ! Any thing else I can do?

What if i have locked bootloader and flashed twrp through miflash?

coolguy22 said:
What if i have locked bootloader and flashed twrp through miflash?
Click to expand...
Click to collapse
In theory it should work I guess? Assuming you used the guide from @khajiit here you should have a MarshMellow bootloader, as the MIUI version linked there is based on MM (kate_global_images_6.11.3_20161103.0000.00_6.0_global_16db0fc5fa), so it shouldn't relock. Can't try myself since I unlocked mine recently.

Amon_Re said:
In theory it should work I guess? Assuming you used the guide from @khajiithere you should have a MarshMellow bootloader, as the MIUI version linked there is based on MM (kate_global_images_6.11.3_20161103.0000.00_6.0_global_16db0fc5fa), so it shouldn't relock. Can't try myself since I unlocked mine recently.
Click to expand...
Click to collapse
Ok so if i get the latest firmware and install some 7.1.2 rom it shouldn't bootloop?

coolguy22 said:
Ok so if i get the latest firmware and install some 7.1.2 rom it shouldn't bootloop?
Click to expand...
Click to collapse
In theory, it should work.

..

Welp, I searched, didn't find a relevant answer. XT1625 help wanted.

Bought my phone in Fry's, had stock nougat. Order of events that led to my current predicament:
1. Wanted to root.
2. Installed TWRP, tried pushing supersu without a new kernel, didnt do so systemless.
3. Tried again systemless.
4. ended up in bootloader loop.
5. realized i didnt back up, so i installed this: https://forum.xda-developers.com/general/rooting-roms/real-official-stock-rom-xt1625-xt1642-t3575895
6. Driver on pc no longer recognizes phone to the point of being able to see system storage, and also cannot open TWRP anymore.
7. The link above is MM. I wanted at least Nougat, since, i got used to some features.... like being able to freaking use hands free calling via bluetooth in my cars.
8. I just want to be able to see internal storage again, and access TWRP, so i can install Lineage and get past this horrible nightmare.
You guys are awesome, I am years behind most of you when it comes to these processes, I have to read line by line what to do in these tutorials, I dont even understand half of the acronyms, or understand half of the terms.
Thanks in advance.
P.S. Just to clarify, marshmellow is working.

Wolamute said:
P.S. Just to clarify, marshmellow is working.
Click to expand...
Click to collapse
Yours really doesn't ask you to upgrade to Nougat like 10 times a day? Mine just must be pushy.
First try: Settings > About phone > system updates
If that doesn't work post what build version of MM you are now on. (also on the about phone page)

Wolamute said:
Bought my phone in Fry's, had stock nougat. Order of events that led to my current predicament:
1. Wanted to root.
2. Installed TWRP, tried pushing supersu without a new kernel, didnt do so systemless.
3. Tried again systemless.
4. ended up in bootloader loop.
5. realized i didnt back up, so i installed this: https://forum.xda-developers.com/general/rooting-roms/real-official-stock-rom-xt1625-xt1642-t3575895
6. Driver on pc no longer recognizes phone to the point of being able to see system storage, and also cannot open TWRP anymore.
7. The link above is MM. I wanted at least Nougat, since, i got used to some features.... like being able to freaking use hands free calling via bluetooth in my cars.
8. I just want to be able to see internal storage again, and access TWRP, so i can install Lineage and get past this horrible nightmare.
You guys are awesome, I am years behind most of you when it comes to these processes, I have to read line by line what to do in these tutorials, I dont even understand half of the acronyms, or understand half of the terms.
Thanks in advance.
P.S. Just to clarify, marshmellow is working.
Click to expand...
Click to collapse
Off-topic, kind of, but I'm trying to flash ANY recent version of TWRP on my XT1625. I unlocked the bootloader, but try to flashing twrp in fastboot mode always returns an error: "(bootloader) Image not signed or corrupt"
What twrp version did you use and where can I get it, please.

What twrp version did you use and where can I get it, please.
Click to expand...
Click to collapse
twrp-3.2.1-0-athene.img
from https://twrp.me/motorola/motorolamotogplus2016.html
Did you unlock your bootloader?
fastboot flashing unlock
---------- Post added at 08:16 PM ---------- Previous post was at 07:57 PM ----------
Wolamute said:
P.S. Just to clarify, marshmellow is working.
Click to expand...
Click to collapse
So I went through and fastboot flashed all those files from your link to Motorola support.
It wouldn't let me relock the bootloader with fastboot oem lock
it did lock with fastboot flashing lock
I was able to reboot, now of course with a verification error boot msg
Connected to wifi and it auto-prompted the Nougat ota update.
Just completed the Nougat install currently on build NPJ25.93-14
Maybe you just need to reflash those files from the Motorola site, and connect to wifi for the 700+MB download?
there's another security update to NPJ25.93-14-4 available after you get back to nougat. Good luck

superceege said:
twrp-3.2.1-0-athene.img
from https://twrp.me/motorola/motorolamotogplus2016.html
Did you unlock your bootloader?
---------- Post added at 08:16 PM ---------- Previous post was at 07:57 PM ----------
Click to expand...
Click to collapse
My xt1625 was boot-unlocked, and I was try the same twrp version you mentioned. I continued researching, and found that, despite the error msg, twrp was flashed correctly. I just needed to go to recovery directly from the bootloader screen. Thanks for your help.

superceege said:
Yours really doesn't ask you to upgrade to Nougat like 10 times a day? Mine just must be pushy.
First try: Settings > About phone > system updates
If that doesn't work post what build version of MM you are now on. (also on the about phone page)
Click to expand...
Click to collapse
EDIT : Ok guys i figured out what to do, the phone wasnt being detected with MTP unless i switched it to charge only, then back to MTP, now i have TWRP back on, and will be trying out lineage. Thanks for the input, it helped!
It's like i said, the one in the link, its 6.0.1. , the kernel is 3.10.84-g061c37c
No, it never pushes notifications about updates with this stock rom posted on xdad, and no, i cannot use the menus to prompt a manual update.
Like i said, i can no longer even access TWRP, my recovery screen says no command, which i can bypass by holding power and clicking volume up, then releasing power, but its not TWRP, and i cannot access internal storage to put anything on it anymore.

Wolamute said:
EDIT : Ok guys i figured out what to do, the phone wasnt being detected with MTP unless i switched it to charge only, then back to MTP, now i have TWRP back on, and will be trying out lineage. Thanks for the input, it helped!
It's like i said, the one in the link, its 6.0.1. , the kernel is 3.10.84-g061c37c
No, it never pushes notifications about updates with this stock rom posted on xdad, and no, i cannot use the menus to prompt a manual update.
Like i said, i can no longer even access TWRP, my recovery screen says no command, which i can bypass by holding power and clicking volume up, then releasing power, but its not TWRP, and i cannot access internal storage to put anything on it anymore.
Click to expand...
Click to collapse
Hmm, what 6.0.1. build do you have (if you scroll down to the bottom of Settings>About Phone, there should be an entry for Build Number)? I recall that for US devices you need to be on MPJ24.139-48/49 or MPJ24.139-64 to be eligible for the OTA update to Nougat. Any other different firmware build may not give you an update as the build's not recognised by the update server for your region/software channel.
However, as you flashed the MM firmware onto your device when you previously had Nougat, I would advise against taking the OTA update route. Depending on what version of Nougat you had before you tried to root, you may hard brick your device if you try to flash the OTA, since flashing MM firmware may not downgrade your bootloader, as such you'd be flashing an old OTA onto a newer Nougat bootloader, which is a really bad idea. If you can remember what stock firmware you had (or at least what security patch it was), we can try to locate the correct firmware for you to flash and safely get you back onto the update path.
As for the recovery, that sounds like the stock recovery you have on your device, which if you re-flashed the stock ROM, will replace TWRP. You may have to re-flash TWRP.
On a related note, on Marshmallow, you do not need to flash a custom kernel - you could flash TWRP and your choice of root manager. On stock Nougat (on the G4/Plus devices), you must flash a custom kernel, else you will likely bootloop as you experienced. Here's a rooting guide for G4/Plus Nougat devices: https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
---------- Post added at 04:28 AM ---------- Previous post was at 04:23 AM ----------
Baboon_Red said:
Off-topic, kind of, but I'm trying to flash ANY recent version of TWRP on my XT1625. I unlocked the bootloader, but try to flashing twrp in fastboot mode always returns an error: "(bootloader) Image not signed or corrupt"
What twrp version did you use and where can I get it, please.
Click to expand...
Click to collapse
That error is normal, as far as I know - the TWRP image is not cryptographically signed by Motorola, so that message seems to be mainly informational and alerting you that you are flashing unsigned images in fastboot (which you are), since fastboot is mainly used to flash signed images. Once you've flashed TWRP, reboot straight to recovery to ensure the TWRP is not overwritten by the stock recovery. Afterwards, you can boot as normal.
Be careful to flash the TWRP version/architecture for what you want to do - e.g. if you wish to flash 64 bit custom ROMs, you must use a 64 bit TWRP version. Attempting to flash 64 bit custom ROMs via 32 bit TWRP may give you an error 255 otherwise.

deleted

deleted

i have J730F and will going to flash twrp soon on it and what i experienced that we need Odin , custom recovery file, turning on development tool by tapping 7 times the build number then turning on OEM unlock then flashing recovery, but better to uncheck auto reboot on odin to get the recovery flash properly.
now u said u have J730GM and no idea this devices belong to which country and sim lock ?
will be sharing my result after getting succeed on my device of flashing recovery

deleted

nomadicdev said:
if you have oreo, your rom will lock you out after flashing twrp, and you'll have to wipe it all and wait a week to unlock owm unlock again. gm is singapore/thailand/ india I think. of course no sim lock, I think that's just a US thing
There's a specific method to flash twrp, and I assume one has to format and reflash the rom from within twrp after decryption
Click to expand...
Click to collapse
OH ic
well yes i have oreo and i was going to start the procedure of flashing custom recovery, my model is J7 Pro not (2017) but they both are same, now not sure what will happen after flashing custom recovery but hopping the things will go smoothly,
any thanks dear for the information

i have successfully flashed twrp the latest one on my J7 Pro with also flashing RMM-State_Bypass_Mesa_v2 and no-verity-opt-encrypt-6.0 then booted up into stock oreo rom and found my oem lock in developer options is there and my device is working absolutely fine so far
now going to flash the S9 One ui rom on it
Thank U

P8Lite stuck on huawei logo - had access to TWRP

Hello, it is my first post on this forum and it of course has to be problem. I am not expert in mobile phone hacking/flashing and this issue is too big for me to handle.
So like 6 hours ago i had working p8lite L21 with official android 6.0 and locked bootloader. I really wanted install costum rom due to performance issue, so i downgrade it back to 5.0 lolipop, than I root it with kingroot and successful extract key and unlock it using this tutorial: https://forum.xda-developers.com/newthread.php?do=newthread&f=4627
Than I flash recovery and install TWRP 3.0.2-0 and it all just worked. I was so happy that i manage to pull this off and I forgot that now i have EMUI 3.1 (ALE-L21C432B170) and i flashed phone with this:
https://forum.xda-developers.com/p8lite/development/rom-lineageos-14-1-p8-lite-t3824247
Of course it bricked because I missed that part with special version of TWRP. After that i tried to install something older just to get phone to work again:
https://forum.xda-developers.com/p8lite/development/rom-cyanogenmod-13-0-ale-l21-t3708835
And surprise, surprise, it did not work either and now I am stuck with huawei boot logo.
I did some research how to fix this issue, but i found so many different problems and solutions, I thought that at this point I really should ask for help because I just have no idea what i am doing now At this stage, can i just flash some costum rom (idc what exactly, just wanna to be lightweight) or i have to somehow restore original firmware? And if so how to do it? As i mentioned, i had access to TWRP.
Thanks a lot for your help in advance.

can someone help me with unbricking this phone? ?
@edit ok nevermind, i thought that this phone is cheap anyways so why not risk and just flashed boot/recovery/system from stock rom with fastboot. I did it and it works again, i needed just this simple hint to do it but i guess p8lite forum is dead.

ChuZZZta said:
Hello, it is my first post on this forum and it of course has to be problem. I am not expert in mobile phone hacking/flashing and this issue is too big for me to handle.
So like 6 hours ago i had working p8lite L21 with official android 6.0 and locked bootloader. I really wanted install costum rom due to performance issue, so i downgrade it back to 5.0 lolipop, than I root it with kingroot and successful extract key and unlock it using this tutorial: https://forum.xda-developers.com/newthread.php?do=newthread&f=4627
Than I flash recovery and install TWRP 3.0.2-0 and it all just worked. I was so happy that i manage to pull this off and I forgot that now i have EMUI 3.1 (ALE-L21C432B170) and i flashed phone with this:
https://forum.xda-developers.com/p8lite/development/rom-lineageos-14-1-p8-lite-t3824247
Of course it bricked because I missed that part with special version of TWRP. After that i tried to install something older just to get phone to work again:
https://forum.xda-developers.com/p8lite/development/rom-cyanogenmod-13-0-ale-l21-t3708835
And surprise, surprise, it did not work either and now I am stuck with huawei boot logo.
I did some research how to fix this issue, but i found so many different problems and solutions, I thought that at this point I really should ask for help because I just have no idea what i am doing now At this stage, can i just flash some costum rom (idc what exactly, just wanna to be lightweight) or i have to somehow restore original firmware? And if so how to do it? As i mentioned, i had access to TWRP.
Thanks a lot for your help in advance.
Click to expand...
Click to collapse
Can you access TWRP or fastboot mode?? Yes, the thread has been quite inactive... it used to be totally different few years back...

amageek said:
Can you access TWRP or fastboot mode?? Yes, the thread has been quite inactive... it used to be totally different few years back...
Click to expand...
Click to collapse
Yea, i had access to twrp and fastboot. I already fixed it by flashing stock rom with fastboot. But maybe you can help me with other issue, currently i have android 5.0.1 emui 3.1 build c432b170 and i wanna install this rom:
https://forum.xda-developers.com/p8lite/development/rom-lineageos-14-1-p8-lite-t3824247
as i understand i need to have android 7.0 with emui 4.1, install costum twrp and than flash this rom. But how to update this phone to android 7.0? When i check for updates it says that there is nothing to update

ChuZZZta said:
Yea, i had access to twrp and fastboot. I already fixed it by flashing stock rom with fastboot. But maybe you can help me with other issue, currently i have android 5.0.1 emui 3.1 build c432b170 and i wanna install this rom:
https://forum.xda-developers.com/p8lite/development/rom-lineageos-14-1-p8-lite-t3824247
as i understand i need to have android 7.0 with emui 4.1, install costum twrp and than flash this rom. But how to update this phone to android 7.0? When i check for updates it says that there is nothing to update
Click to expand...
Click to collapse
I believe I can help you... Check the First Comment of that post... you'll see two additional firmwares... Only those firmwares have EMUI 4.1... b896 is for dual sim and b895 is for single sim... use any of those as per your requirements... after that download the LineageOS firmware and then proceed as per the Thread's recommended way... Also, before installing LineageOS, make sure you don't have any lockscreen lock...
feel free to ask if you have any more questions...
PS: i may reply bit late... maybe an hour, 5 hours or even days... but will try to check frequently..

amageek said:
PS: i may reply bit late... maybe an hour, 5 hours or even days... but will try to check frequently..
Click to expand...
Click to collapse
No worries, im happy that someone reply to me
So yea, i noticed those two softwares, i have two imei number so i picked b896 version for dual sim, but when i extract it and place in dload folder and try to update it via holding power button + -, i get software installation failed message. So I am not rly sure how to install this firmware, do i have to extract update.app and flash recovery/boot/system with fastboot, or i need to install it using some twrp? I look for guide but everyone are using this powerbutt + - methode to do this

ChuZZZta said:
No worries, im happy that someone reply to me
So yea, i noticed those two softwares, i have two imei number so i picked b896 version for dual sim, but when i extract it and place in dload folder and try to update it via holding power button + -, i get software installation failed message. So I am not rly sure how to install this firmware, do i have to extract update.app and flash recovery/boot/system with fastboot, or i need to install it using some twrp? I look for guide but everyone are using this powerbutt + - methode to do this
Click to expand...
Click to collapse
Do you mean Vol +, Vol - and Power Button by powerbutton +- ? That's one way of flashing it, if you get error by that method, try it once again. If it doesn't work at all, then yes extract the update.app and go for the hard way...

amageek said:
Do you mean Vol +, Vol - and Power Button by powerbutton +- ? That's one way of flashing it, if you get error by that method, try it once again. If it doesn't work at all, then yes extract the update.app and go for the hard way...
Click to expand...
Click to collapse
Yea, i mean that i holding all three buttons (power vol+ vol-) and than it just says that installation failed. To flash it with fastboot i need to just flash recovery/boot/system or more files? I am asking because currently i have android 5 and this firmware is android 7 and I am just not sure if i can just simply flash those files and it will works.
Thanks for helping me

ChuZZZta said:
Yea, i mean that i holding all three buttons (power vol+ vol-) and than it just says that installation failed. To flash it with fastboot i need to just flash recovery/boot/system or more files? I am asking because currently i have android 5 and this firmware is android 7 and I am just not sure if i can just simply flash those files and it will works.
Thanks for helping me
Click to expand...
Click to collapse
Which one are you trying to flash??? b896?? or simply LineageOS??
If it's b896, then I did read that it can only be flashed on ALE-L21C02xxx, but i am unsure about it... I did installed LineageOS and Resurrection Remix back in the days but I don't think I ever used C02 ROM for B896...
Also if you have the latest TWRP, you can simply flash with it... Try it...
Here's the link for tutorial