Related
I'm in the middle of trying to install TWRP tried multiple versions and different sites and flashed at least 5 different TWRP images and cannot boot into TWRP. I just end up at the EMIU recovery. Is TWRP not functioning for this model?
EMUI: 5.0
Android: 7.0
Hi there @WillDaBeast69. I actually purchased one of these and want to root it and such. I'm gonna be in your thread a bit trying to help you find a way and also help me and everyone else in the process to find a solution. If a solution is already available then hopefully someone else will post it.
AFAIK - currently I don't see anything regarding the L14 which is the 64GB version.
What I'd like you to do first is get back on the stock firmware. Unless you know where to find one, I'm going to say look for an UPDATE.APP somewhere for the L14. I'm going to do some searching as well. If you find it please post the link. If you find one that works and it's not on an official site (Honor site) then I'll also download it and upload to a central location that everyone can get to it.
Once you're back on the stock firmware, I'm going to ask you to try and get a TWRP image booted on the device. Not installed but booted. Once we have that up we can proceed.
*EDIT*
So after doing a bit of digging I found a link in someone's sig.
All thanks go to @Dominikrod for his sig which lead to this post.
https://forum.xda-developers.com/showpost.php?p=70396400&postcount=547
Full thread: https://forum.xda-developers.com/ho...-to-nougat-t3510275/post70396400#post70396400
But before we can proceed, we will need to get your phone back up and running if it's not already in a working state.
*EDIT*
So after following the instructions I got one of the L14's I have up and running rooted. The other one is giving me some trouble because I can't unlock the bootloader for some reason. Keeps telling me the code is wrong. Once I get it up and running I'll make sure I post pics of the process.
Confirmed working on EMUI5 - Android OS 7.
THANK YOU!!
khat17 said:
Hi there @WillDaBeast69. I actually purchased one of these and want to root it and such. I'm gonna be in your thread a bit trying to help you find a way and also help me and everyone else in the process to find a solution. If a solution is already available then hopefully someone else will post it.
AFAIK - currently I don't see anything regarding the L14 which is the 64GB version.
What I'd like you to do first is get back on the stock firmware. Unless you know where to find one, I'm going to say look for an UPDATE.APP somewhere for the L14. I'm going to do some searching as well. If you find it please post the link. If you find one that works and it's not on an official site (Honor site) then I'll also download it and upload to a central location that everyone can get to it.
Once you're back on the stock firmware, I'm going to ask you to try and get a TWRP image booted on the device. Not installed but booted. Once we have that up we can proceed.
*EDIT*
So after doing a bit of digging I found a link in someone's sig.
All thanks go to @Dominikrod for his sig which lead to this post.
https://forum.xda-developers.com/showpost.php?p=70396400&postcount=547
Full thread: https://forum.xda-developers.com/ho...-to-nougat-t3510275/post70396400#post70396400
But before we can proceed, we will need to get your phone back up and running if it's not already in a working state.
*EDIT*
So after following the instructions I got one of the L14's I have up and running rooted. The other one is giving me some trouble because I can't unlock the bootloader for some reason. Keeps telling me the code is wrong. Once I get it up and running I'll make sure I post pics of the process.
Confirmed working on EMUI5 - Android OS 7.
Click to expand...
Click to collapse
khat17 said:
Hi there @WillDaBeast69. I actually purchased one of these and want to root it and such. I'm gonna be in your thread a bit trying to help you find a way and also help me and everyone else in the process to find a solution. If a solution is already available then hopefully someone else will post it.
AFAIK - currently I don't see anything regarding the L14 which is the 64GB version.
What I'd like you to do first is get back on the stock firmware. Unless you know where to find one, I'm going to say look for an UPDATE.APP somewhere for the L14. I'm going to do some searching as well. If you find it please post the link. If you find one that works and it's not on an official site (Honor site) then I'll also download it and upload to a central location that everyone can get to it.
Once you're back on the stock firmware, I'm going to ask you to try and get a TWRP image booted on the device. Not installed but booted. Once we have that up we can proceed.
*EDIT*
So after doing a bit of digging I found a link in someone's sig.
All thanks go to @Dominikrod for his sig which lead to this post.
https://forum.xda-developers.com/showpost.php?p=70396400&postcount=547
Full thread: https://forum.xda-developers.com/ho...-to-nougat-t3510275/post70396400#post70396400
But before we can proceed, we will need to get your phone back up and running if it's not already in a working state.
*EDIT*
So after following the instructions I got one of the L14's I have up and running rooted. The other one is giving me some trouble because I can't unlock the bootloader for some reason. Keeps telling me the code is wrong. Once I get it up and running I'll make sure I post pics of the process.
Confirmed working on EMUI5 - Android OS 7.
Click to expand...
Click to collapse
Hoping you're still monitoring this thread or get a notification. I also just purchased the L14 and was disappointed to find that it is "special" as all the guides, firmware, etc that are available are for the L04. I was wondering what progress you've made since this post? Have you had any other issues, flashed custom ROMs, and if so, how did they work?
Also, have you had any luck finding current update.app/zip files for the L14? I found posts directing to an app called Firmware Finder which seems to pull up multiple copies but also read that those might somehow be locked and result in a brick/soft brick. Any help would be appreciated!
Thanks!
Sticky92 said:
THANK YOU!!
Click to expand...
Click to collapse
No problem. Anytime.
dsEVOlve said:
Hoping you're still monitoring this thread or get a notification. I also just purchased the L14 and was disappointed to find that it is "special" as all the guides, firmware, etc that are available are for the L04. I was wondering what progress you've made since this post? Have you had any other issues, flashed custom ROMs, and if so, how did they work?
Also, have you had any luck finding current update.app/zip files for the L14? I found posts directing to an app called Firmware Finder which seems to pull up multiple copies but also read that those might somehow be locked and result in a brick/soft brick. Any help would be appreciated!
Thanks!
Click to expand...
Click to collapse
From what's been happening to me, I think Huawei may be clamping down on allowing persons to unlock their bootloader and root the phones. I've not been able to get into the site at all - I've managed to root my wife's phone but mine.............nothing. Nothing works. I got the info directly from their site and it just won't work. I emailed them and they say that they don't assist individuals with bootloader unlock nor do they allow it - which seems to be new policy.
The instructions that are in the link I have works. As long as you got your bootloader unlocked you can install TWRP, SuperSU and root. If you go through the instructions in the link and need step-by-step assistance then just post back.
Error on FRD-L14 and B388
khat17 said:
No problem. Anytime.
From what's been happening to me, I think Huawei may be clamping down on allowing persons to unlock their bootloader and root the phones. I've not been able to get into the site at all - I've managed to root my wife's phone but mine.............nothing. Nothing works. I got the info directly from their site and it just won't work. I emailed them and they say that they don't assist individuals with bootloader unlock nor do they allow it - which seems to be new policy.
The instructions that are in the link I have works. As long as you got your bootloader unlocked you can install TWRP, SuperSU and root. If you go through the instructions in the link and need step-by-step assistance then just post back.
Click to expand...
Click to collapse
I try to install all the TWRP imgs on the links, I´m using the FRD-L14 B388, but after I reboot the phone after flashing the TWRP recovery pressing VOL + and VOL - , I received the message "Your device has been unlocked and cant be trusted.... Your device is booting now..." after some minutes it goes to EMUI recovery instead of TWRP.
Is there something I can do it to solve this issue?
Thanks in advanced!
sammyrano said:
I try to install all the TWRP imgs on the links, I´m using the FRD-L14 B388, but after I reboot the phone after flashing the TWRP recovery pressing VOL + and VOL - , I received the message "Your device has been unlocked and cant be trusted.... Your device is booting now..." after some minutes it goes to EMUI recovery instead of TWRP.
Is there something I can do it to solve this issue?
Thanks in advanced!
Click to expand...
Click to collapse
This is normal after you unlock the bootloader. Unless you re-lock it you won't get rid of that error AFAIK. Small annoyance to pay for full root.
khat17 said:
This is normal after you unlock the bootloader. Unless you re-lock it you won't get rid of that error AFAIK. Small annoyance to pay for full root.
Click to expand...
Click to collapse
Hi, so I can live with this message not a big deal in the mean time is just a normal information alert.
Thank you so much for the information!
sammyrano said:
Hi, so I can live with this message not a big deal in the mean time is just a normal information alert.
Thank you so much for the information!
Click to expand...
Click to collapse
I also got honor 8 FRD-L14 version rooted with Magisk and stock EMUI 5.0.1. You should try Dolby atmos audio mod from this thread https://forum.xda-developers.com/android/apps-games/soundmod-axon-7-dolby-atmos-t3412342 and also Google dose for Magisk to improve battery life.
Best wishes sir.
khat17 said:
No problem. Anytime.
From what's been happening to me, I think Huawei may be clamping down on allowing persons to unlock their bootloader and root the phones. I've not been able to get into the site at all - I've managed to root my wife's phone but mine.............nothing. Nothing works. I got the info directly from their site and it just won't work. I emailed them and they say that they don't assist individuals with bootloader unlock nor do they allow it - which seems to be new policy.
The instructions that are in the link I have works. As long as you got your bootloader unlocked you can install TWRP, SuperSU and root. If you go through the instructions in the link and need step-by-step assistance then just post back.
Click to expand...
Click to collapse
Any chance that step by step assistance is still on the table? I'm revisiting the notion of unlocking and rooting but your previous post and the threads linked to it have me quite a bit lost. Do I have to go all the way back to build B162 to get it to work properly? I know my way around ADB and have unlocked every phone I've had going back to the first HTC Evo but all the different versions of this phone has me all turned around. :/
A walkthrough with direct links to files used would be greatly appreciated if you have the time.
Thanks in advance for any help you can provide!
Not a problem. I'll see what I can do. Will need a little time to compile the info.
dsEVOlve said:
Any chance that step by step assistance is still on the table? I'm revisiting the notion of unlocking and rooting but your previous post and the threads linked to it have me quite a bit lost. Do I have to go all the way back to build B162 to get it to work properly? I know my way around ADB and have unlocked every phone I've had going back to the first HTC Evo but all the different versions of this phone has me all turned around. :/
A walkthrough with direct links to files used would be greatly appreciated if you have the time.
Thanks in advance for any help you can provide!
Click to expand...
Click to collapse
khat17 said:
Not a problem. I'll see what I can do. Will need a little time to compile the info.
Click to expand...
Click to collapse
Any progress?
dsEVOlve said:
Any progress?
Click to expand...
Click to collapse
Apologies. Vehicle issues that I'm sorting out have taken up my time.
So first thing we're gonna do is this. Go to this thread.
https://forum.xda-developers.com/ho...-to-nougat-t3510275/post70396400#post70396400
Download the files there. You have an L14 and this thread I've linked to has files for that phone.
Next you want an SD card. An 8GB card should work. You will also need a hash checker like the one in the link below.
http://getmd5checker.com
Once you have all of those post back and we can proceed.
I used this guide to install TWRP on my FRD-L14 without a hitch:
https://forum.xda-developers.com/honor-8/how-to/guide-unlock-bootloader-tested-root-t3443946
Is there a certain step you get caught up on? I just reverted back to stock after being on a custom ROM for a day so it is fresh in my mind.
This is the TWRP I used:
https://forum.xda-developers.com/honor-8/development/twrp-t3566563
@dsEVOlve - you can try the link that @Deemo13 posted. I'll still be here to go through the step by step process. If you're available tonight I will also give you remote assistance in getting it done if you'd like the help that way.
https://www.teamviewer.com/en/download/previous-versions/
Go there and download version 11 if you'd like the remote assistance in getting this done. If we can agree on a time then I'll ask you to PM me the ID and PW.
Let's go through and see if we can get you setup.
Deemo13 said:
I used this guide to install TWRP on my FRD-L14 without a hitch:
https://forum.xda-developers.com/honor-8/how-to/guide-unlock-bootloader-tested-root-t3443946
Is there a certain step you get caught up on? I just reverted back to stock after being on a custom ROM for a day so it is fresh in my mind.
This is the TWRP I used:
https://forum.xda-developers.com/honor-8/development/twrp-t3566563
Click to expand...
Click to collapse
Did you flash SuperSU or magisk? If SuperSU, did you flash it or simply install from Play Store?
---------- Post added at 04:39 AM ---------- Previous post was at 04:36 AM ----------
khat17 said:
@dsEVOlve - you can try the link that @Deemo13 posted. I'll still be here to go through the step by step process. If you're available tonight I will also give you remote assistance in getting it done if you'd like the help that way.
https://www.teamviewer.com/en/download/previous-versions/
Go there and download version 11 if you'd like the remote assistance in getting this done. If we can agree on a time then I'll ask you to PM me the ID and PW.
Let's go through and see if we can get you setup.
Click to expand...
Click to collapse
Thanks for the offer of assistance. I think I've got the process now and the files needed to root. I was just wary before because nothing I came across specifically said it was for the L14 variant.
Just trying to figure out if I want to go the SuperSU or Magisk route. Any suggestions?
And the first link you provided utilizes build 360. How do I go about getting the latest build to flash? Firmware finder?
dsEVOlve said:
Did you flash SuperSU or magisk? If SuperSU, did you flash it or simply install from Play Store?
---------- Post added at 04:39 AM ---------- Previous post was at 04:36 AM ----------
Thanks for the offer of assistance. I think I've got the process now and the files needed to root. I was just wary before because nothing I came across specifically said it was for the L14 variant.
Just trying to figure out if I want to go the SuperSU or Magisk route. Any suggestions?
And the first link you provided utilizes build 360. How do I go about getting the latest build to flash? Firmware finder?
Click to expand...
Click to collapse
I did not flash or root the phone, so unfortunately I can't give any advice on this front
Wondering if we will still see the 9.1 update here in the US....
Thanks. Upgrading to 9.1 is what I am thinking about. But after many failed tries, I gave up, for now.
Still on 8.x, and no sign of 9.x.
No help from query made to Huawei USA.
Same here, Oreo 8.0 with B377. Nothing in FF either
Had Live Chat with Huawei USA re this, and in summary the answer was ..."if and when the update is released, it will be uploaded to your phone automatically.".
The operative phrase being "...if and when...".
Sadly, I don't see it happening. With each day, the tension between Huawei and the U.S., now the rest of the world, I don't see anything further from them, for the 9, which is why I went with a different phone in November. After the Mate2, 8, 9 I was looking forward to more Huawei phones, but, with dropped support for the U.S. (rightly so), I had to move on.
Great phones, but without DIRECT OEM support for a U.S. model, I'm just not into the whole root, unlock, flash stuff anymore.
If it doesn't come from the OEM, I don't bother with it. Just gettin' too old....now get off my lawn!
I pretty much agree, except Google and Android bowing to the ban pressure, causes me to rethink not only future Huawei products ( “...if, and when they become available in the USA”), but also Android and Google. I have avoided the dark side (Apple) till now, but am rethinking that..
OnePlus has a good reputation. But in older models I read about higher radiation emissions than other peer phones at that time.
I am thinking of having it once my mate 9 dies...
Sent from my MHA-L29 using Tapatalk
Zalophus said:
I pretty much agree, except Google and Android bowing to the ban pressure, causes me to rethink not only future Huawei products ( “...if, and when they become available in the USA”), but also Android and Google. I have avoided the dark side (Apple) till now, but am rethinking that..
Click to expand...
Click to collapse
I won't go *that* dark, as I can't ever imagine owning Apple. It's tricky because I want this phone, just upgraded. I'm all in on Google, just can't find a great phone at a decent (sub $500) price...
EMUI 9 Pie 9 available according to firmware finder
MHA-LGRP2-OVS 9.1.0.252 FullOTA-MF dated 7/17/2019 available according to FF for MHA-L29C567
I just bought a OnePlus 6t and it's has 8gb ram yada yada and really zippy. I like the mate 9 more. The screen on the mate is nice and bright and the sound quality from the headphones blows away the 1+. I even rooted the 1+ and increased the headphones to 90 but still quality is not as good. I like the volume and power on the same side of the mate. I'm desperately trying to figure out how to get pie on it. I'm going to post a question about what files are out there I can flash. I've tried and failed so far.
It's been a while since anyone asked: is there any way to get C567 to 9.0/9.1?
I'm at MHA-L29 8.0.0.360(C567) --never bothered to get to the latest Oreo 377 (doubt that has an effect as I've been going for the FullOTA-MF).
Today I tried firmware finder erecovery and patched hisuite on numerous 9.0 and 9.1 firmwares that were supposedly approved for my IMEI. I haven't tried rebranding, dload method (don't even know if that exists for C567 Pie), or emuiflasher.
Anyone been able to do it?
(I confess I've posted this same question two a couple of other threads here on XDA).
I also keep trying and ran across this article and says to use flashy to manually flash the 2 beta files for 9.0 way back in january. I wonder if I can use the flashy tool to flash the current 9.0 432 files for now and let those update to 9.1 when it happens. Had I seen this article way back in January I would have tried it. You can use the second link to download any version of android for the mate 9. Type "mha-L29" into the search field where it says "enter model" and press enter. Then just left click on the "filelist" and a second later it will pop up. The cut and past the url into a new window and press enter and it will start downloading. If the beta files will work with flashy then why not the actual files. In xda the p20 forum has similar instruction for beta pie back in 2018.
https://www.getdroidtips.com/huawei-mate-9-android-9-0-pie-update/
https://pro-teammt.ru/online-firmware-database-ru/
Edit: Someone did the exact thing I was thinking about with the p10. He used ff to download the actual files and used flashy. Maybe I'll give it a shot earlier tomorrow. I'm not sure how to use flashy yet though. It says unzip the update files into the unzipped flashy folder but not sure where in the folder. I guess I can try and see.
https://forum.xda-developers.com/mate-10/help/pie-upate-t3891577
jeffrimerman said:
I also keep trying and ran across this article and says to use flashy to manually flash the 2 beta files for 9.0 way back in january. I wonder if I can use the flashy tool to flash the current 9.0 432 files for now and let those update to 9.1 when it happens. Had I seen this article way back in January I would have tried it. You can use the second link to download any version of android for the mate 9. Type "mha-L29" into the search field where it says "enter model" and press enter. Then just left click on the "filelist" and a second later it will pop up. The cut and past the url into a new window and press enter and it will start downloading. If the beta files will work with flashy then why not the actual files. In xda the p20 forum has similar instruction for beta pie back in 2018.
https://www.getdroidtips.com/huawei-mate-9-android-9-0-pie-update/
https://pro-teammt.ru/online-firmware-database-ru/
Edit: Someone did the exact thing I was thinking about with the p10. He used ff to download the actual files and used flashy. Maybe I'll give it a shot earlier tomorrow. I'm not sure how to use flashy yet though. It says unzip the update files into the unzipped flashy folder but not sure where in the folder. I guess I can try and see.
https://forum.xda-developers.com/mate-10/help/pie-upate-t3891577
Click to expand...
Click to collapse
Nice find jeffrimerman! Looking around, I found the original developer of the beta flashy tool is @a1Pha, who designed it for the P20 Pro. Here's his OP on the method:
https://forum.xda-developers.com/hu...uide-how-to-install-emui-9-android-9-t3839316
I read thru the 45 pages of comments in that thread and saw a couple of folks that had successfully used the tool to upgrade from Oreo to Pie and rebrand at the same time. Also a couple of folks who used it on other Huawei models. The tool requires two zip files, so I think you're right about needing to upgrade to 9.0 first (as 9.1 has a single zip file).
Quite a bit of discussion in the thread relates to maintaining bootloader and FRP open. It seems we might end up with those locked, making it difficult to change/upgrade ROMs other than by OTA. That would mean that under the worst scenario (other than some unexpected bootloop), we might get stuck on that 9.0 ROM if for some reason Huawei checks IMEI and not region for upgrades. The thread also has a post (linked in the OP) that has a modified FLASH.txt file to use to upgrade from "Beta to Beta" and another for getting back to Oreo, so even this scenario might be avoided.
As for where to put the zip files, the beta-flash_0.2.zip, once unpacked, has a folder conveniently labeled "ZIPS-HERE"!
I'm currently downloading MHA-L29 9.0.1.191(C432E7R1P8) from FF, and will wait to hear from your test to give it a shot! Good luck, and I'll help anyway I can if something goes south. :good:
---------- Post added at 09:52 AM ---------- Previous post was at 09:19 AM ----------
Opening the FLASH.bat in beta-flashy, I noticed it installs a custom "No Check" recovery. It probably has a "secret sauce" in it, so it's probably required to use the one for the P20 Pro that's in the original tool. For a moment I thought of replacing it with the "No Check" recovery for MHA specifically in the HWOTA8 tool (also by @mankindtw but slightly different file size), but best not to tinker too much?
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-oreo-update-package-t3699522
https://www.dropbox.com/s/11ghma7pqkbq32h/MHA_RECOVERY8_NoCheck.img?dl=0
Oh wow, I actually PM'd him last night asking about exactly how to use the tool. I tried downloading from his link on that post but it didn't work. I did see the zips here so I'm sure you're right on that. The article I posted here mentioned unzipping the updates so that's what confused me. I'll have to read that guys post and see if he mentions it. Maybe he'll respond to my pm before I attempt it. He also flashed a beta 9.0 and wasn't sure if updates would come ota after that so maybe he'll know by now since it's been months. If I don't get a response then I'll ask in his thread. Has 9.0 been able to be rooted? I have my unlock code still so I can redo that from adb if I need to.
I didn't have any trouble downloading the beta flashy, but just in case, here's a copy:
https://www.dropbox.com/s/te9fcilkphi7n7i/beta-flashy_0.2.zip?dl=0
I'm not that concerned about further updates once we're on 9.0 C432, for example to 9.1. There seem to be multiple options in case OTA doesn't work: using the beta-flashy with the "beta to beta" modified script, using the EMUIFlasher_1.2.apk (intended for OpenKirin, but apparently useful for rom changes within Oreo or within Pie--but not between them), the FF eRecovery method, modified HiSuite (probably the best option as I believe it doesn't require root, unlocked bootloader or data wipe), or perhaps HWOTA9:
https://forum.xda-developers.com/mate-9/how-to/emui-9-0-beta-t3857239/page18
Let me know if you decide to pull the trigger! I'm tempted to give it a shot too.
---------- Post added at 01:08 PM ---------- Previous post was at 12:27 PM ----------
Regarding root on 9.0/9.1, it seems patching recovery with Magisk is working, although with some hiccups especially in 9.1 (stock phone app crashes):
9.0: https://forum.xda-developers.com/mate-10/how-to/guide-magisk-root-mate-10-pro-t3886967
9.1: https://forum.xda-developers.com/hu...nt/guide-magisk-root-p30-pro-bl-code-t3938285
Note that having bootloader unlock is indispensable for root. Glad I got it back in the day!
I've got the files, same ones you downloaded. The guy that updated with flashy on his mate 10 back in Jan couldn't remember exactly what he did.
"Download the firmware and extract it inside the same flashing tool extracted area" - This is from the article so it sounds like extract them into the "zips here" but then they technically wouldn't be zips so makes me wonder.
"Extract the firmware bundle, you'll get two ZIPs and some XMLs." - Tool creator says something similar but he said you end up with 2 zips but he was talking about 1 beta file which might have bundled the 2 updates together which makes me think I just put "update" and "update full yada yada" into the zips here folder.
I'm noticing if I unzip both files they both have a "META-INF" folder which could cause some confusion so it makes me think do not unzip the updates. I think tonight I'll end up trying it with the updates being zipped.
I think I'm on page 10 of the post of the p20 with the tool and one guy mentioned renaming the zips. I'll have to read and see if we need to rename them. Did you notice anything?
This was some instructions I read in a "flash.txt" file I read for using the tool to downgrade so I imagine we need to do the same to upgrade. Same name for the HuRupdater also. I think I have all the info I need
echo.
echo Put the update.zip into the "ZIPS-HERE" folder.
echo.
pause
echo.
echo Now rename the update_full_XXXXXX_hw_eu.zip to update_all_hw.zip and put it in the ZIPS-HERE folder.
echo.
pause
echo.
I assumed you would rename the zips and put them in the folder "ZIPS-HERE" without extracting the contents.
I was thinking the same thing but since both literally said extract I didn't want a brick =( hehe. I did it!!! I put the whole folder and ran it from the C root of the drive just to be safe. I thought someone mentioned it not seeing files. I followed the instructions that show on the pc in cmd promt since it pops up a cmd window and guides you through. It seem to do it smoothly then the phone boots and you have EMUI with the circle loading the file to 100%. When I hit 100% it said "update failed" and gave me one uption to reboot. I was worried I had a brick. When it rebooted a different Huawei logo came up and said "optimizing apps" and got up to 100% and booted up fine. Phone looked exactly the same which worried me. I never did a factory reset so it literally did a normal update and kept all my settings and icons the same and I never had to input anything. I checked phone info and it's build number is 9.0.1.191(C432E7), with emui verson 9.01. Success!!!!! Security patch says May 5 2019. I imagine we'll get a regular update when 9.1 rolls out to us or you can probably put resurrection remix if you want. I put that on my Xiaomi Mi 8 Lite and it's pretty nice. So far so good. My bootloader must still be unlocked since it gave me that warning. Even developer options is still there. Enable OEM unlock is checked but not greyed out so I can still lock maybe. Let me know if you have any questions.
Edit: This helped get hotspot working again
Connection your phone to the computer (may need to enable developer settings)
adb shell settings get global tether_dun_required
If the result is "null" or "1"
adb shell settings put global tether_dun_required 0
Reboot phone
So, I gave it a shot as well. All went as you described, except I didn't get to the "optimizing apps". Instead it bootlooped about 3 times and then told me there had been a problem and that it suggested a factory reset. Must have been some root app or setting after all these years that tripped the process. Anyway, I was able to then get back to a clean 9.0.1 C432 and luckily I had done a full backup to external storage with the Huawei app. I restored, had to tinker with some apps that didn't get all their settings updated and reenter my Google password, etc. but am back in business in Pie!
I did try to go ahead and update to 9.1 via FF eRecovery and modded HiSuite to no avail. Also, the phone keeps wanting to "update" me to the same firmware by installing a 20kb OTA claiming I have some unauthorized apps (even right after factory reset). So I'm a bit suspicious that I won't be getting OTA to 9.1.
Next step will be to root (I've got several apps that require it), and perhaps try the 9.1 update via EMUIFlasher or some other method in a couple of weeks if I don't get an OTA push.
Thanks for getting my courage up and working on this together. Let's keep this thread active with any updates from either of us. Hopefully this will also help other C567 Mate 9 users get to Pie.
---------- Post added at 08:22 AM ---------- Previous post was at 07:44 AM ----------
Succeeded in rooting with Magisk:
Magisk Manager apk in OP: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Instructions for EMUI 9: https://topjohnwu.github.io/Magisk/install.html
That's great news, we're 2 for 2. I had Viper4Android which I never got working, magisk, root checker but not really that many root apps so maybe that helped. I wonder if we can use this same method to get to 9.1 or is that just 1 file now. I think this tool is written for 2 files, not 3 and not 1. I wonder if the "dload" method would work. I could never get the big update.app file onto my sd card. It would always fail but maybe I need to reformat it from exfat to ntfs or something. Welcome to PIE =)
Hello Guys,
i had bought an Huawei P20 about an year ago. Now you know with all of this "USA-Huawei" Trouble going on, the thought came to my mind that i better start unlocking bootloader and be prepared to flash custom rom if worst come to worst. so far, so good.
now i started looking around if there is an easy method of getting the bootloader unlocked. but oh my, the huawei company is very friendly to us users and say "no, you wont get any unlock code from us anymore". so screw that.
now i want to try some experimental stuff. it looks like this:
my Smartphone has currently the version EML-L29 8.1.0.168(C432). I bought some Credits (i think it is that thing for $4) from DC-Unlocker. Yeah yeah i know, there they say "no support for Huawei P20!!!". But i still want to try. Well i tried, but it doesnt work - what you should expect.
now i read from some other website that there is another way of unlocking it. i only read it diagonal but the one thing i read was the information "unlocking bootloader is only possible till firmware version june 2018". so i jumped to an maaybe interesting conclusion about unlocking the phone with DC-Unlocker or HCU (whatever, i guess maybe both use the same method anyway).
if i do an rollback to the old firmware version *before* June 2018 on the device, wouldnt it be possible to do the unlock? Because the security patches that preventing it unlocked arent on the device then.
So what i have done so far is loading the old firmware version 8.1.0.128(C432). But the source is saying that it is coming from "Asia" but in the next line it reads "Asia, Europe" etc. - do they mean that this version is universal or do i run in trouble if i install one that is having the wrong area?
the next thing that kinda baffles me... all guides are sayin "copy the extracted dload folder to your sd-card". even the p20 guides do that. but.. well you know, the p20 device doesnt even have sd-card support. so how are you intended to use it then? i wonder about that a bit.
i dont think that without unlocked bootloader, flashing an original OTA full update would be impossible. but im not really sure how. there is this shady menu you can reach if you call this strange numbercode. but im very unsure if that will really work out. the phone (it is still a phone without SD-Card-Support) even has the option "apply update from sd-card". so im wondering how this feature they implemented in the original software is intended to use at all. maybe i should push the dload folder on the internal storage? i dunno.
i read about another possibilty of flashing stock roms. they say you can do it per adb command. so no problems would be here, i have adb and the hisuite and all already set. but i have absolutely no idea if that is possible without unlocked bootloader. so the questions arose from my mind are those:
- does an stock rom image from possibly/maybe asia would do any harm to my device like it is getting unbootable or anything like that?
- is it possible to flash an image older android stock rom with methods like this special menu on the device or the adb load?
- do you all think that my plan of downgrading the phone in order to get the bootloader code would work?
i'm looking very forward to your answers )
no_monday said:
Bootloader Unlocking through Downgrade possible?
Click to expand...
Click to collapse
No. Sorry. There's no solution. Reason: It would appear in this forum within minutes and thousands of people would be happy to unlock their bootloaders. Many Huawei-Owners here on XDA invested a lot of brain power to find a way. Noone succeeded. No bootloader code, no unlock.
If you still want to play around with firmwares, please inform us about any progress.
Jan Philipp said:
No. Sorry. There's no solution. Reason: It would appear in this forum within minutes and thousands of people would be happy to unlock their bootloaders. Many Huawei-Owners here on XDA invested a lot of brain power to find a way. Noone succeeded. No bootloader code, no unlock.
If you still want to play around with firmwares, please inform us about any progress.
Click to expand...
Click to collapse
okay so there are basically no real information. look, i dont expect anyone to say like "oh there is an easy method xy" because i know it doesnt exist on this moment in time.
however i made an percent of an progress, it is more a thing for other interested custom rom modders out there.
i downloaded this update.zip and there are all kinds of howtos on the internet about it. the one thing i did is basically create the dload folder. then i put the extracted update.app in there. i rebooted the phone with power, vol down + vol up. i released the power button after the vibrating. the flashing screen indeed appeared! but something very strange has happened and i have no explanation what have happend.
so the emui updater appeared. there was this emui logo in the middle, the circle building up around it. but then it stopped at 5%. i really got panicked that im about to brick my device. so in an mad attempt i wanted to stop the update and power off the phone. glad i didnt do it. the phone always said if i tried to press the power button long enough "the system will crash if it is powered down". i stopped - but i tried it serveral times to stop.
now the strange thing is.. it stuck relatively long on this screen. but after a while (i guess it was 5-6 minutes) it suddenly got dark. and the battery was at 100%, so it wasnt a faulty battery. i just wondered. the phone - other than i would expect - rebooted. after a short while of the logo flashing (for about an half minute) it finally started. first i didnt have any connect to GSM Network. but after a short while that was okay too. all apps are still there. i looked at "about" and the version is still the same as before.
do someone have any imagination what has happened there? so apparently the phone *does* try to install something on this method, but the method seemed to fail. or is there any knowledge out yet for update logs that are getting generated by this process? i try to find any hint in order to tackle this problem atm.
and one thing is still on my mind.. could it be that the update is already through and i just didnt realized it yet because these other custom files werent changed? i mean that could be an possibility to say the least. anyway, i will try to use hcu now if maybe sth has changed. and i give kingoroot as well a shot if this buddy finds everything about rooting the device. maybe with root rights through exploit i can get further.
no_monday said:
okay so there are basically no real information. look, i dont expect anyone to say like "oh there is an easy method xy" because i know it doesnt exist on this moment in time.
however i made an percent of an progress, it is more a thing for other interested custom rom modders out there.
i downloaded this update.zip and there are all kinds of howtos on the internet about it. the one thing i did is basically create the dload folder. then i put the extracted update.app in there. i rebooted the phone with power, vol down + vol up. i released the power button after the vibrating. the flashing screen indeed appeared! but something very strange has happened and i have no explanation what have happend.
so the emui updater appeared. there was this emui logo in the middle, the circle building up around it. but then it stopped at 5%. i really got panicked that im about to brick my device. so in an mad attempt i wanted to stop the update and power off the phone. glad i didnt do it. the phone always said if i tried to press the power button long enough "the system will crash if it is powered down". i stopped - but i tried it serveral times to stop.
now the strange thing is.. it stuck relatively long on this screen. but after a while (i guess it was 5-6 minutes) it suddenly got dark. and the battery was at 100%, so it wasnt a faulty battery. i just wondered. the phone - other than i would expect - rebooted. after a short while of the logo flashing (for about an half minute) it finally started. first i didnt have any connect to GSM Network. but after a short while that was okay too. all apps are still there. i looked at "about" and the version is still the same as before.
do someone have any imagination what has happened there? so apparently the phone *does* try to install something on this method, but the method seemed to fail. or is there any knowledge out yet for update logs that are getting generated by this process? i try to find any hint in order to tackle this problem atm.
and one thing is still on my mind.. could it be that the update is already through and i just didnt realized it yet because these other custom files werent changed? i mean that could be an possibility to say the least. anyway, i will try to use hcu now if maybe sth has changed. and i give kingoroot as well a shot if this buddy finds everything about rooting the device. maybe with root rights through exploit i can get further.
Click to expand...
Click to collapse
It seems you have a couple of questions, pal, I answered to the first one (Bootloader Unlocking through Downgrade possible?). All I said is that it's impossible to unlock the bootloader through a downgrade. If you read all the how-to's you should have noticed that FirmwareFinder doesn'st work anymore since EMUI 9.0. This Information simply means Huawei doesn't allow us to flash updates on our own anymore like we did before. For sure there are some guides how to rollback to Android 8 but even this changes nothing to the bootloader.
Sadly I have no answer to the other questions about the strange behavior, it sounds pretty odd. Never heared something like this. But good luck fixing your phone anyway.
well i found out a couple of things now.
first thing: you know the service menu when you try to apply a zip archive from sd card? well you wont be able to use it UNTIL you use an usb-otg cable and an exFat formatted USB-Stick. Next thing to know is, you have to use the right images. there seem to be an kind of rule how this images are supposed to be and the image i found was from an russian firmware download site it was linked here in the forum in a thread. so i did choose "apply zip from sdcard" and .. IT DOES! the device rebooted, the stick flashed and the flashing process occured! and guys, im back to Version EML-L29 8.1.0.128(C432)! it is clearly stated in the build version view in settings. so.. i guess you *can* roll back even without firmware updater.
so far so good. but lets get back to the problem with the Bootloader. sadly Jan Philipp was totally right.. the bootloader cant be unlocked even in this version with the security patch of 5. may 2018. that is kinda sad. even kingoroot is still no different from before. i guess i have to search now for an way to get the system rooted. however, it must be easier on an earlier security update stage like now instead of the future versions of emui 8.1.
edit: another strange thing i discovered so far is that after this restore.. the play store wasnt able to connect to the google server until i gave permission to a few google processes to calendar and file access (i wonder what that is all about). maybe it has something to do with incompatibilities in the rom versions but now it works just fine as it should).
"unlocking bootloader with exploit is only possible till firmware version june/july 2018" does not apply to 2018's devices with kirin970, kirin980 & kirin710.
You are with kirin970.
So to unlock your kirin970, the only way for now is to wait for 3rd party seller to hypotheticaly start back their dervice:
- In the last 6 months there was only 2 'windows' which lasted 3 or 4 days where you could order your bootloader's unlock code by imei (from 5 to 124 us$).
GuestD0711 said:
another strange thing i discovered so far is that after this restore.. the play store wasnt able to connect to the google server until i gave permission to a few google processes to calendar and file access (i wonder what that is all about). maybe it has something to do with incompatibilities in the rom versions but now it works just fine as it should).
Click to expand...
Click to collapse
Google Play services require all permissions, otherwise won't work.
I also been searching on how to unlock the bootloader and found no solution or hope. I guess we are stuck with EMUI forever.
Reply from Huawei:
You can roll back to earlier versions of EMUI software, but you have to roll back one version at a time. However, our earlier phones operate exclusively on Google Mobile Services so removing it would limit the functionality extremely, however, we do have a range of new devices that no longer rely on Google Mobile Services and use Huawei Mobile Services instead - such as our P40 series.
Here are the instructions for rolling back software:
[Rollback Guideline] EMUI 9.1 (Android 9) Rollback to EMUI 9.0 (Android 9) Operation Instruction
EMUI 9.1 (Android 9) can now be rolled back to the official version of EMUI 9.0 (Android 9) using HiSuite, without downloading any intermediate packages. To ensure that the rollback succeeds, read the instructions carefully and perform the steps as instructed.
1. The following are precautions for roll-back.
a. Rolling back to an earlier version will erase all data on your device. Use an SD card, computer, or Cloud storage to back up all important data before rolling back your phone, and make sure all backed up content is complete and effective.
b. Use a computer running a Windows operating system to visit http://consumer.huawei.com/minisite/HiSuite_en/index.html and download the latest version of HiSuite. If HiSuite is installed on your computer, click the version number in the lower left corner of the page to check if it is the latest version. Make sure HiSuite version is 9.1.0.303 _OVE or above.
c. Before rolling back the phone, make sure your phone has not been upgraded using non-official updates. Otherwise, the roll-back may fail and unknown issues may be introduced. If you have used non-official packages to upgrade your phone, it is recommended that you go to an after-sales service center to roll back your phone.
d. Before rolling back your phone, make sure that your phone system has not been unlocked or rooted. If the system has been unlocked or rooted, it is recommended that you go to an after-sales service center to roll back your phone.
e. Before the roll-back, restore the phone to factory settings to make sure there is enough storage space.
f. Make sure the battery level is more than 50%.
Hi All,
I need assistance to update my EML L29 Huawei P20 phone.
The phone is Locked and FRP Lock
Issue the phone is always booting into recovery mode and not into the main screen.
I tired flashing via CMD using twrp.img file but its not writing.
Need help
I mean its with SuperSU and of course doesn't survive a reboot and still can't figure out anyway to write to /system..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How did you manage this? Was it with just installing SuperSU?
https://github.com/gfunkmonk/N920V_7_TMPROOT
Hey man @gfunkmonk, thank you so much for continuing development on this phone because I lost all hope recently. I saw your link to github.com and downloaded the files. Flashed the first folder using Odin but couldn't figure out what to do with the second folder. I would love if you could assist me in getting it done. I know it's tempting root but at least I could remove bloatware and run certain software. Looking forward to a reply and hopefully full root could actually be a possibility. I'll also volunteer to test anything you come up with if you continue development.
Oh yeah, the second folder is a linux script.. i'll add something for windows. Unfortunately you aren't going to be able to do that anyways. If you try to remount /system read/write the phone will lock up and reboot. I believe this is due to dm-verity which would require patching the kernel. Not possible since the bootloader is locked.
gfunkmonk said:
Oh yeah, the second folder is a linux script.. i'll add something for windows. Unfortunately you aren't going to be able to do that anyways. If you try to remount /system read/write the phone will lock up and reboot. I believe this is due to dm-verity which would require patching the kernel. Not possible since the bootloader is locked.
Click to expand...
Click to collapse
I saw different options on different threads, Would something like this be possible on marshmallow 6.0.1? Or maybe flashing a different firmware such as one for the N920T beacause they use the same processor after flashing a combination file? Full root is possible on 5.1.1 for the N920V but because we cant downgrade if you didn't have an old device without updates it's impossible. So I think the best bet is working with marshmallow for now. I've seen people say they get temp root without crashing using mobilego so maybe applying what you have here would have better luck on MM. Maybe dm-verity could be bypassed and maybe we can use safestrap to flash files that could help.
You most certainly can downgrade to 5.1.1. I did it a couple days ago myself. But yes you do have to flash a combination firmware and use safestrap, Now, I'm not much of a dev but I did make some pretty cool roms for my Moto Droid and later my Droid 3... Now, I remeber we had a safestrap on it, I almost swear it had some nifty was to boot other kernels... but that was just 2012 and I can't remeber.
As far as MM if you had a engboot kernel that gives root in adb, it would work exactly the same. Sorry I don't know much about the N920V, I have a N920T.. I got the Verizon one as a cheap whim on ebay. Plus it was gold lol.
I've got a way to get perm root but its so complicated and still can't touch /system or it reboots so not even worth it,
Either way, I found MM firmware that should flash, I might mess with it later.
Oh, and I certainly wouldn't flash another models anything. Like with Note8s they literally are all the same... I *think* I read something about the N920P being close enough it could boot our kernel or the other way around... something like that. But I think any of that stuff would just end badly.
gfunkmonk said:
You most certainly can downgrade to 5.1.1. I did it a couple days ago myself. But yes you do have to flash a combination firmware and use safestrap, Now, I'm not much of a dev but I did make some pretty cool roms for my Moto Droid and later my Droid 3... Now, I remeber we had a safestrap on it, I almost swear it had some nifty was to boot other kernels... but that was just 2012 and I can't remeber.
As far as MM if you had a engboot kernel that gives root in adb, it would work exactly the same. Sorry I don't know much about the N920V, I have a N920T.. I got the Verizon one as a cheap whim on ebay. Plus it was gold lol.
I've got a way to get perm root but its so complicated and still can't touch /system or it reboots so not even worth it,
Either way, I found MM firmware that should flash, I might mess with it later.
Oh, and I certainly wouldn't flash another models anything. Like with Note8s they literally are all the same... I *think* I read something about the N920P being close enough it could boot our kernel or the other way around... something like that. But I think any of that stuff would just end badly.
Click to expand...
Click to collapse
Hey man could you maybe give me a link to the combination file and safestrap as well as instructions on how to downgrade? There's permanent root on 5.1.1 and I'd rather have a rooted phone on lollipop than a stock one on nougat.
Hopefully you can mess around the MM firmware and figure something out. I think we're about the only two persons still interested in root on the version note 5 so we gotta stick together lol.
I'm definitely no dev or anything but I can contribute with info as I've searched every thread on XDA and other sides and I will help you test etc. Thanks again for everything you're doing man, you've stopped me from giving up on this device XD .
Yeah, so this is the combonation file I used: https://drive.google.com/file/d/1FEU3Msz3MQTCv5DnMe6zc8PlZERa2y6x/edit
So flash it in Odin and let it boot up all the way and whatnot.
use wondershare/mobilego to root from your computer or kingoroot or Kingroot 5.3.7, but you'll want to switch their junk for SuperSU. There's a script for that. Search "replace kingroot with supersu" the file is usually called mrw.zip
Go to the play store and install 'flashfire' If you have trouble with it crashing when you start it manually change the date on the phone to 2012, it'll work then, just believe me.
get safestrap 4.08 here https://forum.xda-developers.com/verizon-galaxy-note5/recovery-locked-safestrap-recovery-v4-t3915714
in flashfire click install zip, select the safestrap and when it asks hit mount system rw. Then hit flash, screen will go dark stuff will scroll by it'll reboot. when it does you'll have an option to enter recovery.
NOBLEROM is pre-rooted 5.1.1 it's here https://forum.xda-developers.com/verizon-galaxy-note5/rom-noble-rom-aoj3-v1-0-t3940543
flash that into recovery and then reflash safestrap before you leave, cause it'll be overwritten by that rom
and uhhh that's it. when you reboot you should be greeted with rooted 5.1.1
gfunkmonk said:
Yeah, so this is the combonation file I used: https://drive.google.com/file/d/1FEU3Msz3MQTCv5DnMe6zc8PlZERa2y6x/edit
So flash it in Odin and let it boot up all the way and whatnot.
use wondershare/mobilego to root from your computer or kingoroot or Kingroot 5.3.7, but you'll want to switch their junk for SuperSU. There's a script for that. Search "replace kingroot with supersu" the file is usually called mrw.zip
Go to the play store and install 'flashfire' If you have trouble with it crashing when you start it manually change the date on the phone to 2012, it'll work then, just believe me.
get safestrap 4.08 here https://forum.xda-developers.com/verizon-galaxy-note5/recovery-locked-safestrap-recovery-v4-t3915714
in flashfire click install zip, select the safestrap and when it asks hit mount system rw. Then hit flash, screen will go dark stuff will scroll by it'll reboot. when it does you'll have an option to enter recovery.
NOBLEROM is pre-rooted 5.1.1 it's here https://forum.xda-developers.com/verizon-galaxy-note5/rom-noble-rom-aoj3-v1-0-t3940543
flash that into recovery and then reflash safestrap before you leave, cause it'll be overwritten by that rom
and uhhh that's it. when you reboot you should be greeted with rooted 5.1.1
Click to expand...
Click to collapse
Hey man I got it to work and i just want to say thank you so much! My error before was that flashify wasn't flashing the zip properly. Flashfire did the trick and the ROM works now and everything. However I'm noticing a few bugs such as the WiFi password is forgotten after a reboot and the fingerprint sensor option no longer works. I know you weren't on development of Noble ROM but any idea on how to fix this?
Also I saw this customn rom - : Samsung OneUI Running Full Android 9.0 For the Exynos7420 Family! . Here's the link if you have time to have a look [ https://forum.xda-developers.com/note5/development/rom-floyd-n7fe-port-v1-0-t3882804 ] Do you think I would be able to flash it now that I have safestrap installed?
Also if there are any updates regarding getting permanent root on Marshmallow or ultimately Nougat think we could be kept in the loop on this thread? I'll probably just check in every few days. Once again thanks for everything you've helped me with.
Jherane said:
Hey man I got it to work and i just want to say thank you so much! My error before was that flashify wasn't flashing the zip properly. Flashfire did the trick and the ROM works now and everything. However I'm noticing a few bugs such as the WiFi password is forgotten after a reboot and the fingerprint sensor option no longer works. I know you weren't on development of Noble ROM but any idea on how to fix this?
Also I saw this customn rom - : Samsung OneUI Running Full Android 9.0 For the Exynos7420 Family! . Here's the link if you have time to have a look [ https://forum.xda-developers.com/note5/development/rom-floyd-n7fe-port-v1-0-t3882804 ] Do you think I would be able to flash it now that I have safestrap installed?
Also if there are any updates regarding getting permanent root on Marshmallow or ultimately Nougat think we could be kept in the loop on this thread? I'll probably just check in every few days. Once again thanks for everything you've helped me with.
Click to expand...
Click to collapse
Again the only kernels we can use are flashed through odin and have to pass secure boot check, So stock or engboot. Now I used to run that rom on my t-mobile version, till it bugged me so much that the camera is broken in the S8/N8 ports past Nougat. As for the wifi pass and biometrics, never checked it. Now, same thing happens when you root a Note8 (which is a similar process) and I believed it's fixed by flashing a Nougat bootloader. Unfortunatley, we don't have one, so basically both will be forever broken.
As for MM, you gotta remember I'm one guy and I'm simply doing this for fun. I don't always know what I'm doing exactly 100%, some of its straight trial and error. I'll probably try flashing stock MM and playing around a bit tomorrow maybe, but I wouldn't have high hopes for anything there either tbh.
I got a little excited because I found an engboot kernel for MM, but unfortunately, it's exactly like nougat. root is temp and trying to modify or remount /system leaves phone unresponsive and eventually reboots. However, I haven't noticed any random reboots like nougat.
gfunkmonk said:
I got a little excited because I found an engboot kernel for MM, but unfortunately, it's exactly like nougat. root is temp and trying to modify or remount /system leaves phone unresponsive and eventually reboots. However, I haven't noticed any random reboots like nougat.
Click to expand...
Click to collapse
Haha the journey continues, I figured it would be a huge task since most people said it was impossible XD. It's a little more stable than Nougat I guess because it's closer to 5.1.1 I think the issue is always gonna lie with getting system to mount r/w without freezing. Whatever code they inserted as soon as the system is altered the kernel panics unfortunately.
Btw Completely get you regarding the development. I didn't mean any disrespect, just meant in the event you had a breakthrough, wasn't so much out of expectation ?
I see you mentioned a S8/N8 port, I'm not the most advanced in the custom rom section so are you saying that the the noble rom you mentioned to me earlier today is an s8 or n8 port or is that another rom? If I can ask you to clarify?
Lastly about the Wi-Fi and Fingerprint, it sucks but I can live with that with everything that root offers. I'm gonna do a complete wipe and repeat the process to see if it goes away or search the noble rom thread to see if anyone had the same error.
Jherane said:
Haha the journey continues, I figured it would be a huge task since most people said it was impossible XD. It's a little more stable than Nougat I guess because it's closer to 5.1.1 I think the issue is always gonna lie with getting system to mount r/w without freezing. Whatever code they inserted as soon as the system is altered the kernel panics unfortunately.
Btw Completely get you regarding the development. I didn't mean any disrespect, just meant in the event you had a breakthrough, wasn't so much out of expectation
I see you mentioned a S8/N8 port, I'm not the most advanced in the custom rom section so are you saying that the the noble rom you mentioned to me earlier today is an s8 or n8 port or is that another rom? If I can ask you to clarify?
Lastly about the Wi-Fi and Fingerprint, it sucks but I can live with that with everything that root offers. I'm gonna do a complete wipe and repeat the process to see if it goes away or search the noble rom thread to see if anyone had the same error.
Click to expand...
Click to collapse
No, the Floyd rom you linked me is an N8 port. The Note8 came up because they way you root it is similar. Flash combination, flashfire, all that.
Now interestingly, 6.0.1 let me make a backup of /system without rebooting, 7.0 would not. So I got one idea here that could work, but it's going to take me a minute to test it.
gfunkmonk said:
No, the Floyd rom you linked me is an N8 port. The Note8 came up because they way you root it is similar. Flash combination, flashfire, all that.
Now interestingly, 6.0.1 let me make a backup of /system without rebooting, 7.0 would not. So I got one idea here that could work, but it's going to take me a minute to test it.
Click to expand...
Click to collapse
Well that actually sounds like progress. There was another thread on here about rooting the N920V, Idk if you've seen it for maybe situations where you get stuck. All the best.
Can you send me/post a link? I have learned a couple things today, its progress but I don't know how much.
gfunkmonk said:
Can you send me/post a link? I have learned a couple things today, its progress but I don't know how much.
Click to expand...
Click to collapse
Long story short: can we flash normal system.img over ENG bootloaders? I got "SYSTEM REV. CHECK FAIL DEVICE:1, BINARY:0" after reboot, so instead we can flash it as flashable zip. yes this work but we end up with bootloop. so what to do to pass this situation.
digging in ENG boot.img ramdisk I can see "export LD_PRELOAD libsigchain.so:liblptcp.so" and system/lib/liblptcp.so nor system/lib64/liblptcp.so is not there in stock 5.1.1, So take them from ENG firmware you will get fully working system over combo bootloader.
Attached Files
File Type: zip LD_PRELOAD-NOBLELTEVZW-SS-FF-flashable.zip
@gfunkmonk I'm trying to post the links here but it won't allow me. I'm gonna private message them to you. Also what do you get from this? I'm seeing on another thread where a DEV said this could fix the Wi-Fi and fingerprint issue because it would be a stock system image but the binary would be bootloader would be unlocked. Any help please. I know this maybe not your area of expertise but I asked on the thread and it seems to be dead. Thanks in advance.
---------- Post added at 03:59 AM ---------- Previous post was at 03:58 AM ----------
gfunkmonk said:
Can you send me/post a link? I have learned a couple things today, its progress but I don't know how much.
Click to expand...
Click to collapse
Long story short: can we flash normal system.img over ENG bootloaders? I got "SYSTEM REV. CHECK FAIL DEVICE:1, BINARY:0" after reboot, so instead we can flash it as flashable zip. yes this work but we end up with bootloop. so what to do to pass this situation.
digging in ENG boot.img ramdisk I can see "export LD_PRELOAD libsigchain.so:liblptcp.so" and system/lib/liblptcp.so nor system/lib64/liblptcp.so is not there in stock 5.1.1, So take them from ENG firmware you will get fully working system over combo bootloader.
Attached Files
File Type: zip LD_PRELOAD-NOBLELTEVZW-SS-FF-flashable.zip
@gfunkmonk I'm trying to post the links here but it won't allow me. I'm gonna private message them to you. Also what do you get from this? I'm seeing on another thread where a DEV said this could fix the Wi-Fi and fingerprint issue because it would be a stock system image but the bootloader would be changed. Any help please. I know this maybe not your area of expertise but I asked on the thread and it seems to be dead. Thanks in advance.
Jherane said:
Long story short: can we flash normal system.img over ENG bootloaders? I got "SYSTEM REV. CHECK FAIL DEVICE:1, BINARY:0" after reboot, so instead we can flash it as flashable zip. yes this work but we end up with bootloop. so what to do to pass this situation.
digging in ENG boot.img ramdisk I can see "export LD_PRELOAD libsigchain.so:liblptcp.so" and system/lib/liblptcp.so nor system/lib64/liblptcp.so is not there in stock 5.1.1, So take them from ENG firmware you will get fully working system over combo bootloader.
Attached Files
File Type: zip LD_PRELOAD-NOBLELTEVZW-SS-FF-flashable.zip
@gfunkmonk I'm trying to post the links here but it won't allow me. I'm gonna private message them to you. Also what do you get from this? I'm seeing on another thread where a DEV said this could fix the Wi-Fi and fingerprint issue because it would be a stock system image but the binary would be bootloader would be unlocked. Any help please. I know this maybe not your area of expertise but I asked on the thread and it seems to be dead. Thanks in advance.
---------- Post added at 03:59 AM ---------- Previous post was at 03:58 AM ----------
Long story short: can we flash normal system.img over ENG bootloaders? I got "SYSTEM REV. CHECK FAIL DEVICE:1, BINARY:0" after reboot, so instead we can flash it as flashable zip. yes this work but we end up with bootloop. so what to do to pass this situation.
digging in ENG boot.img ramdisk I can see "export LD_PRELOAD libsigchain.so:liblptcp.so" and system/lib/liblptcp.so nor system/lib64/liblptcp.so is not there in stock 5.1.1, So take them from ENG firmware you will get fully working system over combo bootloader.
Attached Files
File Type: zip LD_PRELOAD-NOBLELTEVZW-SS-FF-flashable.zip
@gfunkmonk I'm trying to post the links here but it won't allow me. I'm gonna private message them to you. Also what do you get from this? I'm seeing on another thread where a DEV said this could fix the Wi-Fi and fingerprint issue because it would be a stock system image but the bootloader would be changed. Any help please. I know this maybe not your area of expertise but I asked on the thread and it seems to be dead. Thanks in advance.
Click to expand...
Click to collapse
Ahhh, I get it but no. That's what we did. used the ENG bootloader and kernel (combination files) then re-wrote the system image. Which speaking of, I've got to test out the new nougat image I made earlier.
Okay so what I'm asking is, the issue with the Wi-Fi and biometrics seems to be with the Kernel that's included in noble rom. I read somewhere where you can flash a system image from an earlier 5.1.1 firmware. Say AOJ3 and it should still work since it's close enough to stock and that should fix the Wi-Fi issue. My problem is I have the system image extracted but I don't know how to create a flashible Zip from the system.img so I can use flashify or safetrap to flash it. I saw the kitchen stuff but it's a little complicated for me.
The Dev for noble rom also created a script that would remove the parts of the system that wouldn't allow the normal system image to boot over the ENG bootloader so I'm wondering if this would work. I'm really just desperately searching for a fix to the wifi password being forgotten after reboot so if you have any ideas or workaround it would be greatly appreciated. I can live without the fingerprint scanner.
I saw something about maybe using Tasker to move the file containing the saved password to somewhere safe at shutdown and restoring it on reboot but I'm not sure of proof of concept so I thought I'd ask here first if it sounds feasible.
either flashfire or the safestrap twrp lets you flash an 'img' file... But remeber if it doesn't work you have to redo the entire process and flash & root the combo again
I am reading conflicting things trying to figure this out. Can someone who is absolutely sure please let me know? I can't afford to waste another entire day making educated guesses.
It doesn't seem like the TWRP version numbers correspond to the Android builds, but if they do please correct me.
Thank you
You don't need to figure it out, there's only 2 threads about working TWRP, One for Android 9 & 10 and One for 11 and in the OP of each thread are specified what are working and what doesn't and how to install/boot it properly.
RokCruz said:
You don't need to figure it out, there's only 2 threads about working TWRP, One for Android 9 & 10 and One for 11 and in the OP of each thread are specified what are working and what doesn't and how to install/boot it properly.
Click to expand...
Click to collapse
Oh ****, thank you! I totally missed these searching. Believe it or not I really did look, quite a bit. Anyway, thanks again.
Edit: That 9&10 thread I've read, but I didn't know it was for "9 & 10" exactly. I just kinda assumed since it doesnt work with 11 which I had to figure out the hard way. That 11 thread though is super helpful.
didymus said:
Oh ****, thank you! I totally missed these searching. Believe it or not I really did look, quite a bit. Anyway, thanks again.
Edit: That 9&10 thread I've read, but I didn't know it was for "9 & 10" exactly. I just kinda assumed since it doesnt work with 11 which I had to figure out the hard way. That 11 thread though is super helpful.
Click to expand...
Click to collapse
It's specified in the name of the twrp
And another thing, this type of question should go in the section Questions and answers
RokCruz said:
It's specified in the name of the twrp
And another thing, this type of question should go in the section Questions and answers
Click to expand...
Click to collapse
Yeah, I wasn't sure about where to post it since it was directly about recovery. Sorry about that. I won't make the same mistake again.
Also, I'm just now figuring out what is what, but I don't see how any of those files designate they are for 11 in that screenshot you posted. I've seen all those files actually. I've also spent time on the TWRP website and read mostly everything. The only thing I could find was a post that said it (11 support) was coming, but I tried the newest one there and it bricked the phone. I also read in an article that the lad(s) who wrote those is working officially with TWRP, so I thought the TWRP website would be "the horse's mouth".
I know I installed it correctly too because in the past week I've installed TWRP so many times I could practically do it blindfolded now.
I don't mean to take a bunch of your time, but where in that screenshot does it designate "11"? I know `Pie` is an older Android, but I thought `Q` was too. Maybe I'm just wrong and it's 11. I was just getting confused because the OOS version numbers are right there in the boot image file name for Magisk, so when I saw those numbers on the TWRP files I just thought they were all for much older Android years ago.
Anyway, thank you, sorry for the n00b post, but I definitely am reading and searching and not just posting immediately when I encounter a problem. I've actually learned a ****load in the past week struggling with all of this though so I can't really complain. Eventually I will get up to speed and be able to write some things. I just hope yall don't ban me before then, lol.
didymus said:
Yeah, I wasn't sure about where to post it since it was directly about recovery. Sorry about that. I won't make the same mistake again.
Also, I'm just now figuring out what is what, but I don't see how any of those files designate they are for 11 in that screenshot you posted. I've seen all those files actually. I've also spent time on the TWRP website and read mostly everything. The only thing I could find was a post that said it (11 support) was coming, but I tried the newest one there and it bricked the phone. I also read in an article that the lad(s) who wrote those is working officially with TWRP, so I thought the TWRP website would be "the horse's mouth".
I don't mean to take a bunch of your time, but where in that screenshot does it designate "11"? I know `Pie` is an older Android, but I thought `Q` was too. Maybe I'm just wrong and it's 11. I was just getting confused because the OOS version numbers are right there in the boot image file name for Magisk, so when I saw those numbers on the TWRP files I just thought they were all for much older Android years ago.
Anyway, thank you, sorry for the n00b post, but I definitely am reading and searching and not just posting immediately when I encounter a problem. I've actually learned a ****load in the past week struggling with all of this though so I can't really complain. Eventually I will get up to speed and be able to write some things.
Click to expand...
Click to collapse
That screenshot was for this
didymus said:
Edit: That 9&10 thread I've read, but I didn't know it was for "9 & 10" exactly.
Click to expand...
Click to collapse
If you're in android 11 forget the thread about android 9 & 10
RokCruz said:
That screenshot was for this
If you're in android 11 forget the thread about android 9 & 10
Click to expand...
Click to collapse
Yeah, so, this one for 11 I've tried before. Once I install it how the thread says then I can only boot into TWRP. I'm just unsure what to do now because all the threads just say "flash rom, flash magisk". I didn't even know you could flash Magisk via TWRP.
I have the OTA of the new update downloaded. I have the boot.img extracted. I just have no idea how to fix this. I've done this before and I thought I bricked it and that's why I thought this wasn't for 11. :/
Edit: I'm guessing that I `adb push` the OTA to the device and see if I can flash that in TWRP?? Then once I am in the OS use Magisk to patch the boot? I'm unsure because places use the term "Magisk Manager" like its different from Magisk and I've never seen an app called exactly "Magisk Manager". I'm just assuming that was like... the old name of the app, but I don't know that could just be me filling in the blanks incorrectly.
Edit:Edit: I'm attempting to sideload the OTA. I think I've read of people doing this. *crosses fingers*
didymus said:
Yeah, so, this one for 11 I've tried before. Once I install it how the thread says then I can only boot into TWRP. I'm just unsure what to do now because all the threads just say "flash rom, flash magisk". I didn't even know you could flash Magisk via TWRP.
I have the OTA of the new update downloaded. I have the boot.img extracted. I just have no idea how to fix this. I've done this before and I thought I bricked it and that's why I thought this wasn't for 11. :/
Edit: I'm guessing that I `adb push` the OTA to the device and see if I can flash that in TWRP?? Then once I am in the OS use Magisk to patch the boot? I'm unsure because places use the term "Magisk Manager" like its different from Magisk and I've never seen an app called exactly "Magisk Manager". I'm just assuming that was like... the old name of the app, but I don't know that could just be me filling in the blanks incorrectly.
Edit:Edit: I'm attempting to sideload the OTA. I think I've read of people doing this. *crosses fingers*
Click to expand...
Click to collapse
Wait, what? Im not sure what are you trying to do.
I guess you're new in all of this right?
My work here was the twrp thing.
RokCruz said:
Wait, what? Im not sure what are you trying to do.
I guess you're new in all of this right?
My work here was the twrp thing.
Click to expand...
Click to collapse
Im trying to install TWRP. I do it exactly how the thread says and then system never boots into OOS again and I just have fastboot and TWRP. Basically bricked. Then when I try to reboot to recovery which should be TWRP (right?) it just boots me into the regular "recovery".
Thats why I think this is broken and I resigned to just not updating into 11.
I've never had this much trouble doing this. Ever. Not even close.
Edit: Yeah, so I patched the 11 boot.img and now I have root again, but no TWRP. I don't know how to keep both in 11. When I was 9.5.3 I used the Magisk A/B retention script and kept it, but once it became 11 it bricked the phone and the TWRP logo just flashed. I had to reflash the OTA to boot again. Thats another reason why I thought it didn't work for OOS11.
Starting to think I have a learning disability, lmao. Wish I was joking.
I just try.
When I flashed official TWRP and used it to flash any ROM(including OOS), it will lose or replace it by ROM's recovery...
caca12357 said:
I just try.
When I flashed official TWRP and used it to flash any ROM(including OOS), it will lose or replace it by ROM's recovery...
Click to expand...
Click to collapse
Yeah, exactly what is happening with me. The closest I ever had it working was with using the A/B Retention script within Magisk Modules, but the second I hit OOS11 it **** the bed. I think "official TWRP" is different than what he linked up there for 11. I mean, I know they are, as it says "unofficial", but that's kind of why I'm confused because the images on TWRP.me use the similar numbering nomenclature and imply there are newer version for my device, so why would a newer version not work, but an older version work?
And if this particular TWRP does actually support 11 then why hasn't TWRP Official incorporated it into their releases? It's just little things like that which led me to believe it's not working. Also, I read a bunch of articles saying it wasn't working, but they could have been old. However, one of them was on Reddit and a few months old, but maybe they were wrong.
I feel like I went on a wild goose chase today, but I really hope didn't.
@RokCruz Just out of curiousity, do you actually have a OnePlus 7 Pro right now with OOS11 and working TWRP/root? I'm not saying you're just making this up or anything, but maybe something has changed since the last time you tried? If you currently have an OOS 11.0.11 device with TWRP/root atleast I'll know it's possible.
@caca12357 I'm going to try to do a local OTA upgrade then before I reboot run the A/B retention script and then Magisks option for OTA and see if that does anything. If TWRP works for 11 something like that should make it work, but who knows. Have you messed with A/B Retention at all?
If you want to PM me we can figure it out together.
Thread moved to proper section
didymus said:
Yeah, exactly what is happening with me. The closest I ever had it working was with using the A/B Retention script within Magisk Modules, but the second I hit OOS11 it **** the bed. I think "official TWRP" is different than what he linked up there for 11. I mean, I know they are, as it says "unofficial", but that's kind of why I'm confused because the images on TWRP.me use the similar numbering nomenclature and imply there are newer version for my device, so why would a newer version not work, but an older version work?
And if this particular TWRP does actually support 11 then why hasn't TWRP Official incorporated it into their releases? It's just little things like that which led me to believe it's not working. Also, I read a bunch of articles saying it wasn't working, but they could have been old. However, one of them was on Reddit and a few months old, but maybe they were wrong.
I feel like I went on a wild goose chase today, but I really hope didn't.
@RokCruz Just out of curiousity, do you actually have a OnePlus 7 Pro right now with OOS11 and working TWRP/root? I'm not saying you're just making this up or anything, but maybe something has changed since the last time you tried? If you currently have an OOS 11.0.11 device with TWRP/root atleast I'll know it's possible.
Click to expand...
Click to collapse
Yes, and do you know how I flash TWRP to my OP7P? First, I flashed Pixel Experience recovery by fastboot, and I used Pixel Experience recovery to sideload the official TWRP. (In other words, I never can temporarily or permanently flash TWRP directly). If I did not want to convert my /data to the f2fs file system I will not do this meaningless work...