Related
So, I want to say that my Nokia 8 TA-1004 is having Bootloop. This happens very occasionally and randomly. It just attacks unexpected. I can't see what is the problem or what's the source of it. Thankfully, I have the logcat file. However, I do not understand what was the main cause. So please, I am asking the experts in here to help me identify the source of this error.
The Bootloop just boot like 4-5 times and then stopped Bootloop or sometimes just go straight to DOWNLOAD MODE and I had to restart manually. After that, i was able to gointo system like exploring like usual, and then it happens again. Sometimes not opening the app also happens. Repeat until you gets the nerve.
The phones status is rooted with magisk and unlocked bootloader but no twrp yet. Also, I am at 4.88B SP01 June,01 patch. If you are telling me that the root is the cause, then it is unlikely since it has been weeks since I had it rooted but the problem just came these recently.
Once again, I ask for the help of forumers here. I want to at least enjoy my phone that I love. I dont really want to sell the phone anymore.
Here's the link of logcat:
https://www16.zippyshare.com/v/2W0SVK8t/file.html
I promise. No viruses. Thank you
Hey, I suspect that this problem could be fixed by flashing original bootloader image.
I assume you have flashed an unsuitable image and I think you are using an unlocked bootloader, that's why you are facing this problem.
error748 said:
Hey, I suspect that this problem could be fixed by flashing original bootloader image.
I assume you have flashed an unsuitable image and I think you are using an unlocked bootloader, that's why you are facing this problem.
Click to expand...
Click to collapse
Do you mean flashing original Boot.img? As we know, to gain root, we need to flash patched boot.img with magisk. Do you mean this kind of issue? I notice the problem is in Android System. It says failed to load as data may corrupt. Google is also not responding and Google play services.
Unlocked Bootloader isnt the issue. But, I do think image is unsuitable. However, I have patched boot.img as the same as the version of Nokia. Is such thing still happen?
godofknife said:
Do you mean flashing original Boot.img? As we know, to gain root, we need to flash patched boot.img with magisk. Do you mean this kind of issue? I notice the problem is in Android System. It says failed to load as data may corrupt. Google is also not responding and Google play services.
Unlocked Bootloader isnt the issue. But, I do think image is unsuitable. However, I have patched boot.img as the same as the version of Nokia. Is such thing still happen?
Click to expand...
Click to collapse
now do one thing. flash stock boot img (will break wifi), after that download official twrp and boot into it. then from twrp flash twrp zip file provided with official boot img. reboot to twrp and flash latest magisk beta. (you will have wifi working after this)
This way you will get root and stable system.. no need to flash patched boot img anymore..
Make sure to revert back to stock boot first before flashing twrp..
sumitinhome said:
now do one thing. flash stock boot img (will break wifi), after that download official twrp and boot into it. then from twrp flash twrp zip file provided with official boot img. reboot to twrp and flash latest magisk beta. (you will have wifi working after this)
This way you will get root and stable system.. no need to flash patched boot img anymore..
Make sure to revert back to stock boot first before flashing twrp..
Click to expand...
Click to collapse
sumitinhome, I just did factory reset. The problem STILL HAPPENS. It means it wasn't any of the app but from the system or the boot.img itself perhaps.
With no way to enter the system, how do i get into the fastboot now? By pressing volume down + Power (That shows DOWNLOAD MODE)? Is that the fastboot? Then yet again, the only issue that I have is the exactly driver for Nokia 8. I found lots of drivers in the internet but I am quite confused which one is the real driver of Nokia 8 to be able to detect in fastboot and ADB. Do you have a driver installer?
Assuming if you will have given Nokia driver and I managed to get into fastboot mode by using hard key, do I type this command?
fastboot flash boot.img? Or is it wrong command?
Thank you and sorry if i ask too many questions.
godofknife said:
sumitinhome, I just did factory reset. The problem STILL HAPPENS. It means it wasn't any of the app but from the system or the boot.img itself perhaps.
With no way to enter the system, how do i get into the fastboot now? By pressing volume down + Power (That shows DOWNLOAD MODE)? Is that the fastboot? Then yet again, the only issue that I have is the exactly driver for Nokia 8. I found lots of drivers in the internet but I am quite confused which one is the real driver of Nokia 8 to be able to detect in fastboot and ADB. Do you have a driver installer?
Assuming if you will have given Nokia driver and I managed to get into fastboot mode by using hard key, do I type this command?
fastboot flash boot.img? Or is it wrong command?
Thank you and sorry if i ask too many questions.
Click to expand...
Click to collapse
1. download mode is fastboot mode.. no difference there.
2. unfortunately i dont have installer for drivers but you can find it if you browse nokia section in this forum.
3. you will need command 'fastboot flash boot_a boot.img' and 'fastboot flash boot_b boot.img' to flash stock boot img to your phone..
4. if you wish to install twrp then you will need to follow instructions from following thread
https://forum.xda-developers.com/nokia-8/development/official-twrp-nb1-t3832232
Make sure to read the thread and comments carefully before doing anything.
Hope it helped.
sumitinhome said:
1. download mode is fastboot mode.. no difference there.
2. unfortunately i dont have installer for drivers but you can find it if you browse nokia section in this forum.
3. you will need command 'fastboot flash boot_a boot.img' and 'fastboot flash boot_b boot.img' to flash stock boot img to your phone..
4. if you wish to install twrp then you will need to follow instructions from following thread
https://forum.xda-developers.com/nokia-8/development/official-twrp-nb1-t3832232
Make sure to read the thread and comments carefully before doing anything.
Hope it helped.
Click to expand...
Click to collapse
Hey there, thanks for the fast respond. It greatly helps.
Alright, I am waiting for the driver. Also, I checked anywhere in the forum section of Nokia 8 but none of them have 00WW_4.88bSP01 version of stock boot.img which is 1st June 2018 patch.
Do you happen to have had it? Is it okay if i ask for it? Thank you.
godofknife said:
Hey there, thanks for the fast respond. It greatly helps.
Alright, I am waiting for the driver. Also, I checked anywhere in the forum section of Nokia 8 but none of them have 00WW_4.88bSP01 version of stock boot.img which is 1st June 2018 patch.
Do you happen to have had it? Is it okay if i ask for it? Thank you.
Click to expand...
Click to collapse
I have it. Wait sometime.. i will upload it on gdrive and share you link
sumitinhome said:
I have it. Wait sometime.. i will upload it on gdrive and share you link
Click to expand...
Click to collapse
Yes sumitinhome, thank you so much. Try make it one upload with the driver. All that and I will do the fastboot command asap..
Oh yeah, one verify question. When the bootloader is unlocked, updating the newest ROM after august will lock the bootloader again or not? Some say yes, some say no. A member name hikari stated no, we are unaffected. But, some say relock again. Which is true?
godofknife said:
Yes sumitinhome, thank you so much. Try make it one upload with the driver. All that and I will do the fastboot command asap..
Oh yeah, one verify question. When the bootloader is unlocked, updating the newest ROM after august will lock the bootloader again or not? Some say yes, some say no. A member name hikari stated no, we are unaffected. But, some say relock again. Which is true?
Click to expand...
Click to collapse
we are unaffected.. and i have only boot img unfortunately.. i dont have drivers..
and dont update to august yet.. let pie come and update to pie directly then..
---------- Post added at 02:10 PM ---------- Previous post was at 02:04 PM ----------
godofknife said:
Hey there, thanks for the fast respond. It greatly helps.
Alright, I am waiting for the driver. Also, I checked anywhere in the forum section of Nokia 8 but none of them have 00WW_4.88bSP01 version of stock boot.img which is 1st June 2018 patch.
Do you happen to have had it? Is it okay if i ask for it? Thank you.
Click to expand...
Click to collapse
here is boot img
https://drive.google.com/file/d/1XtxIWQdn9dbtt1tJydM_6fFhslRZfozr/view?usp=drivesdk
sumitinhome said:
we are unaffected.. and i have only boot img unfortunately.. i dont have drivers..
and dont update to august yet.. let pie come and update to pie directly then..
---------- Post added at 02:10 PM ---------- Previous post was at 02:04 PM ----------
here is boot img
https://drive.google.com/file/d/1XtxIWQdn9dbtt1tJydM_6fFhslRZfozr/view?usp=drivesdk
Click to expand...
Click to collapse
Ah ha, thank you very much. I just need one more requirement. The driver. Honestly, there are so many drivers for Nokia 8 and none of them seems to work with my device detection. There's also type F, M driver..... Seriously confusing.
@sumitinhome, you are awesome. I must say thank you for helping me. Phone is no longer in bootloop state. However, I may require just little more help. I have also installed TWRP and succeeded. The problem is that the WIFI breaks. I went ahead and installed Magisk using zip one like you mentioned the steps in installing TWRP. It still doesn't solve the WIFI problem. How could this be? (Do note that I did not use fastboot flash twrp.img. I use fastboot boot twrp.img instead)
I also have other questions. During MTP in TWRP, I saw the partition drive; The internal storage and USB-OTG as given in picture below. What is the second drive meaning?
Second question is why is Magisk manager only showing Installed version v17.1? And the button is just uninstalled. I recall there are other buttons and feature like Safety Net and advance settings.
Finally, I want to know how do we get into recovery mode without using ADB command everytime? I tried pressing Volume UP + Power. But, it didn't go into TWRP. It just goes normal reboot.
Thank you so much once again.
Pic: https://ibb.co/jFtHPp
godofknife said:
@sumitinhome, you are awesome. I must say thank you for helping me. Phone is no longer in bootloop state. However, I may require just little more help. I have also installed TWRP and succeeded. The problem is that the WIFI breaks. I went ahead and installed Magisk using zip one like you mentioned the steps in installing TWRP. It still doesn't solve the WIFI problem. How could this be? (Do note that I did not use fastboot flash twrp.img. I use fastboot boot twrp.img instead)
I also have other questions. During MTP in TWRP, I saw the partition drive; The internal storage and USB-OTG as given in picture below. What is the second drive meaning?
Second question is why is Magisk manager only showing Installed version v17.1? And the button is just uninstalled. I recall there are other buttons and feature like Safety Net and advance settings.
Finally, I want to know how do we get into recovery mode without using ADB command everytime? I tried pressing Volume UP + Power. But, it didn't go into TWRP. It just goes normal reboot.
Thank you so much once again.
Pic: https://ibb.co/jFtHPp
Click to expand...
Click to collapse
Do one thing.
Flash stock boot img again. and after that do the following
1) Full charge your phone.
2) Get a MicroSD card ( 8 or 16 GB )
3) Download this - https://mega.nz/#!mRZHDaJI!3KrT2F0ZE...KQux5EvPWVGI_4
4) Copy it to SDCARD from your PC.
5) Put the SD card in ur mobile.
6) Go to recovery
7) Select update, from SDCARD - start flashing by pressing power button.
This will get back wifi. after that you can update to latest august patch too if you want and then flash twrp.
And about that OTG thing, don't worry twrp is being updated it will be fixed very soon. People are working on it.
sumitinhome said:
Do one thing.
Flash stock boot img again. and after that do the following
1) Full charge your phone.
2) Get a MicroSD card ( 8 or 16 GB )
3) Download this - https://mega.nz/#!mRZHDaJI!3KrT2F0ZE...KQux5EvPWVGI_4
4) Copy it to SDCARD from your PC.
5) Put the SD card in ur mobile.
6) Go to recovery
7) Select update, from SDCARD - start flashing by pressing power button.
This will get back wifi. after that you can update to latest august patch too if you want and then flash twrp.
And about that OTG thing, don't worry twrp is being updated it will be fixed very soon. People are working on it.
Click to expand...
Click to collapse
I see. Number 3 has Encryption. Also, before i can do this, i have a new problem. I was so stupid. I accidentally format everything including the system which leaves me NO OS. I should have just wipe data (factory reset). Not advanced wipe. Can I still install Stock rom (any version) with twrp? What do i do?
@sumitinhome, also I forgot to mention. SD Card and Internal storage is not detected in TWRP Mode. I checked in my PC. ADB Sideload is also fail. Is this the end of my phone fate?
EDITED: Never mind. I was using the obsolete TWRP Version. I updated to the latest one and SD Card and internal is detected in TWRP once again.
godofknife said:
@sumitinhome, also I forgot to mention. SD Card and Internal storage is not detected in TWRP Mode. I checked in my PC. ADB Sideload is also fail. Is this the end of my phone fate?
EDITED: Never mind. I was using the obsolete TWRP Version. I updated to the latest one and SD Card and internal is detected in TWRP once again.
Click to expand...
Click to collapse
well done
sumitinhome said:
well done
Click to expand...
Click to collapse
Thank you.
godofknife said:
I see. Number 3 has Encryption. Also, before i can do this, i have a new problem. I was so stupid. I accidentally format everything including the system which leaves me NO OS. I should have just wipe data (factory reset). Not advanced wipe. Can I still install Stock rom (any version) with twrp? What do i do?
Click to expand...
Click to collapse
@sumitinhome, how about this? I still have the issue. NO OS is running.
godofknife said:
Thank you.
@sumitinhome, how about this? I still have the issue. NO OS is running.
Click to expand...
Click to collapse
told you flash stock boot img again.. and use the above method i mention to flash firmware..
Do one thing.
Flash stock boot img again. and after that do the following
1) Full charge your phone.
2) Get a MicroSD card ( 8 or 16 GB )
3) Download this - https://mega.nz/#!mRZHDaJI!3KrT2F0ZE...KQux5EvPWVGI_4
4) Copy it to SDCARD from your PC.
5) Put the SD card in ur mobile.
6) Go to recovery
7) Select update, from SDCARD - start flashing by pressing power button
sumitinhome said:
told you flash stock boot img again.. and use the above method i mention to flash firmware..
Do one thing.
Flash stock boot img again. and after that do the following
1) Full charge your phone.
2) Get a MicroSD card ( 8 or 16 GB )
3) Download this - https://mega.nz/#!mRZHDaJI!3KrT2F0ZE...KQux5EvPWVGI_4
4) Copy it to SDCARD from your PC.
5) Put the SD card in ur mobile.
6) Go to recovery
7) Select update, from SDCARD - start flashing by pressing power button
Click to expand...
Click to collapse
That was also the solution for NO OS? Wow. Thanks. Um, the download link need Decryption key. Do you happen to have it?
godofknife said:
That was also the solution for NO OS? Wow. Thanks. Um, the download link need Decryption key. Do you happen to have it?
Click to expand...
Click to collapse
no it doesn't need any key
First of all the guide i took it from @Vedrick by searching here in XDA. I just opened this post because i found his guide with a little bit hardness and its easier now for ya.
Well lets start. FIRST Back up all your data.
I was on the latest version of CLT-L29 Huawei p20 pro 6/128 9.0.0.195(C432E5R1P9) if you try it on another version let me know
As always, if you do this it's at your own risk.
PREREQUIREMENTS:
Watch my video on youtube that made to help you guys
1) ADB, Fastboot and Drivers
2)Patched boot image
3) A pc of course.
4) Make sure your phone is not bootloop and working
5)Enable Debugging and OEM unlocking from dev options
This is how i got root on EMUI 9 without TWRP recovery
1 - I Flashed Get your phone on fastboot mode FIRST MAKE SURE YOUR PHONE HAS UNLOCKED BOOTLOADER (download it, and move it on your adb folder-default is on C: drive) (press SHIFT button and right click on the adb folder->select open here PowerShell) type the command fastboot flash recovery_ramdisk patched_boot.img
2-Reboot phone, install Magisk manager last apk from google , go into settings, and change the update channel to custom: )COPY AND PASTE THIS LINKhttps://raw.githubusercontent.com/topjohnwu/magisk_files/master/canary_builds/release.json, go back to the Magisk home screen and hit install, download the odd Magisk file.zip file.
3-Reboot phone, press and hold the volume up key if it goes to ERecovery then reboot again and keep pressing like the video.
4-Open Magisk app, install the zip, then patch, and install the downloaded Magisk.zip file if it says direct install(recommender choose this should say this)
5-Reboot phone, press and hold the volume up key and your phone should boot just fine.(like i said above and like i show the video)
6-Open Magisk, install, select direct install option. and reboot.
Note:
1 - Now your phone will reboot into the recovery every time on its own, which is a good thing, you no longer need to hold the volume up key every time you reboot, it does it for you. This means no TWRP.
2 - In order to apps root access for the first time you need to have Magisk open, or you wont get prompted for approval. Then the app will have permanent root access.
3- You can enter fastboot mode from connecting your phone to pc and open adb as i say above and type adb reboot bootloader OR by turn off your phone, press the down button volume and after 3 secs connect the cable on your pc DONT LEAVE THE DOWN BUTTON
Usefull Commands: If you cannot enter bootloader mode ( IS NEEDED ) type this command on the adb , but first connect your phone with your PC/LAPTOP adb reboot bootloader
IF you have any questions fell free to comment bellow. Also i am gonna try some things to flash twrp and have it for ever because @Vedrick i think couldnt flash twrp recovery
Hi,
thanks a lot taking time for this guide but there are 2 things that I think are confusing :
FIRST - Once you have flashed recovery_ramdisk partition with the patched_boot.img file through fastboot , and you reboot holding up volume button, the phone boots. But after installing latest magisk manager, even without changing the update channel adress, phone is already rooted and you can add modules, etc...
SECOND - when following the guide step by step, part 4 is a problem because it finds new version and asks tout update. And when you do, the guide says install then to patch the tout install the downloaded file.
That part ils not clear as you do not tell what file to patch at this state....
If you could clear that part it would be perfect.
deltaman83 said:
Hi,
thanks a lot taking time for this guide but there are 2 things that I think are confusing :
FIRST - Once you have flashed recovery_ramdisk partition with the patched_boot.img file through fastboot , and you reboot holding up volume button, the phone boots. But after installing latest magisk manager, even without changing the update channel adress, phone is already rooted and you can add modules, etc...
SECOND - when following the guide step by step, part 4 is a problem because it finds new version and asks tout update. And when you do, the guide says install then to patch the tout install the downloaded file.
That part ils not clear as you do not tell what file to patch at this state....
If you could clear that part it would be perfect.
Click to expand...
Click to collapse
i am gonna check it now because my phone was bricked and i cant root now
deltaman83 said:
Hi,
thanks a lot taking time for this guide but there are 2 things that I think are confusing :
FIRST - Once you have flashed recovery_ramdisk partition with the patched_boot.img file through fastboot , and you reboot holding up volume button, the phone boots. But after installing latest magisk manager, even without changing the update channel adress, phone is already rooted and you can add modules, etc...
SECOND - when following the guide step by step, part 4 is a problem because it finds new version and asks tout update. And when you do, the guide says install then to patch the tout install the downloaded file.
That part ils not clear as you do not tell what file to patch at this state....
If you could clear that part it would be perfect.
Click to expand...
Click to collapse
ok i did manage to root it again. you need to unlock your bl and press the volume up button. i edited the post
I did first time as just flashing fastboot recovery_ramdisk with patched_boot.img was enough when opening magisk manager.
Updating was the issue. SO i downloaded the original recovery_ramdisk 195 , and used that file to patch with the latest version downloaded. Then I flashed in fastboot the new patched_boot.img and all was good to latest version.
deltaman83 said:
I did first time as just flashing fastboot recovery_ramdisk with patched_boot.img was enough when opening magisk manager.
Updating was the issue. SO i downloaded the original recovery_ramdisk 195 , and used that file to patch with the latest version downloaded. Then I flashed in fastboot the new patched_boot.img and all was good to latest version.
Click to expand...
Click to collapse
why to download another patch i dont get it.
plus see my signature
Because with yours i was not on latest magisk. Now i can update each time there's a new version by patching the original recovery_ramdisk and flashing the patched_boot.img on fastboot.
I'm curently on 18.2-e05cdc83 (18104)
deltaman83 said:
Because with yours i was not on latest magisk. Now i can update each time there's a new version by patching the original recovery_ramdisk and flashing the patched_boot.img on fastboot.
I'm curently on 18.2-e05cdc83 (18104)
Click to expand...
Click to collapse
i have the same version as you. the problem is 1) you cant have twrp recovery 2) when you open a app that needs root you have to open magisk app first otherwise the permissions will fail
unfortunately no twrp recovery ...
You're right I noticed that
deltaman83 said:
unfortunately no twrp recovery ...
You're right I noticed that
Click to expand...
Click to collapse
do no try to flash twrp it bricked my device.,
Join my telegram group dude
Thanks a lot but i don't have enough time....see m'y number of posts by there lol...same on Facebook etc (f..k I'm already late for work....?).
Regards
Hi all, this method will work on my device? thanks!
P20 PRO
model: CLT-L09
Build: 9.0.0.163 (C432E5R1P9patch01) GPU Turbo
EMUI: 9.0.0
Android 9
Evasi0n3r said:
Hi all, this method will work on my device? thanks!
P20 PRO
model: CLT-L09
Build: 9.0.0.163 (C432E5R1P9patch01) GPU Turbo
EMUI: 9.0.0
Android 9
Click to expand...
Click to collapse
Hello yes sir.
Please check my signature and join my telegram
Watch my video on youtube that made to help you guys https://youtu.be/AB6wwBTfKEc
Hi. Thank you.
I did it in firmware 9.0.0.191 and worked fine.
gvflavio said:
Hi. Thank you.
I did it in firmware 9.0.0.191 and worked fine.
Click to expand...
Click to collapse
np if u want press the thanks button. also join my telegram group see the link in my signature bellow this post.
John
You are genius. Thanks working great p20 pro 9.0.0.191c605
Every time I flash the patched_boot.img and restart with volume up into recovery I have a bootloop. I have CLT-L09 pie 9.0.0.1.9.5 with the custom link for magisk. The only way to get out of the loop is to reflash the stock recovery_ramdis.img. But after flashing stock recovery, magisk has no root any more...
Any suggestions why I only get the bootloop after reflashing the patched_boot.img?
Thanks a lot!
mauritz1972 said:
You are genius. Thanks working great p20 pro 9.0.0.191c605
Click to expand...
Click to collapse
Do you have a problem when you try to pull down the quick setting touching the right or left corner of the screen?
That happens to me when I rooted it.
I need to unlock bootloader with some key, or can i just follow the guide?
Anyone know how to root mate 9 on emui 9? Just updated and twrp doesn't work
quate from @irony_delerium
1) Make sure you've got the stock firmware zip files. (I'm assuming you do.)
2) Extract UPDATE.APP from the main update.zip file (the big one).
3) Using Huawei Firmware Extractor on your desktop (search on XDA for it), load UPDATE.APP and extract the recovery ramdisk image. It's going to be "RECOVERY_RAMDIS" in that app as I recall.
4) Put the image into your phone's internal storage (MTP works, though I've never used it, I usually use adb: adb push RECOVERY_RAMDIS.img /sdcard)
5) Install Magisk Manager on your phone. You want the current release (18.1) at the very minimum. Canary builds also work
6) Select the Install button in the Magisk interface. Select "Patch boot image". In the file browser that comes up, select the image you just transferred in #4.
7) When Magisk finishes, pull the image back to your PC (adb: adb pull /sdcard/Download/patched_boot.img)
8) Reboot to the bootloader and flash (fastboot flash recovery_ramdisk patched_boot.img)
9) Reboot to recovery (fastboot reboot, pull the USB cable and hold volume up).
mavera said:
quate from @irony_delerium
1) Make sure you've got the stock firmware zip files. (I'm assuming you do.)
Thanks man got it working today, has anyone tried viper4android on emui 9 yet does it work?
Click to expand...
Click to collapse
mavera said:
quate from @irony_delerium
1) Make sure you've got the stock firmware zip files. (I'm assuming you do.)
2) Extract UPDATE.APP from the main update.zip file (the big one).
3) Using Huawei Firmware Extractor on your desktop (search on XDA for it), load UPDATE.APP and extract the recovery ramdisk image. It's going to be "RECOVERY_RAMDIS" in that app as I recall.
4) Put the image into your phone's internal storage (MTP works, though I've never used it, I usually use adb: adb push RECOVERY_RAMDIS.img /sdcard)
5) Install Magisk Manager on your phone. You want the current release (18.1) at the very minimum. Canary builds also work
6) Select the Install button in the Magisk interface. Select "Patch boot image". In the file browser that comes up, select the image you just transferred in #4.
7) When Magisk finishes, pull the image back to your PC (adb: adb pull /sdcard/Download/patched_boot.img)
8) Reboot to the bootloader and flash (fastboot flash recovery_ramdisk patched_boot.img)
9) Reboot to recovery (fastboot reboot, pull the USB cable and hold volume up).
Click to expand...
Click to collapse
Thank you. worked for me.
Do you have working TWRP for EMUI 9?
weyrulez said:
Thank you. worked for me.
Do you have working TWRP for EMUI 9?
Click to expand...
Click to collapse
Thank you very much, it worked, but it does not go into recovery
Cant boot to recovery and fastboot. any help?
weyrulez said:
Cant boot to recovery and fastboot. any help?
Click to expand...
Click to collapse
For fastboot you can connect to pc wit cable and try.
But yuo don't boot recovery, because you patched boot image. If you flash original recovery_ramdisk, you can boot recovery.
MHA-L29 cihazımdan Tapatalk kullanılarak gönderildi
weyrulez said:
Thank you. worked for me.
Do you have working TWRP for EMUI 9?
Click to expand...
Click to collapse
TWRP for the Mate 20 X Pie works on the Mate 9. Make sure you thank Feeeza.
ajsmsg78 said:
TWRP for the Mate 20 X Pie works on the Mate 9. Make sure you thank Feeeza.
Click to expand...
Click to collapse
Thank you. And i will thank him too. But after a lot of reading. I think. Mate 9 users can only choose between magisk and TWRP. I hope i am wrong. ?
weyrulez said:
Thank you. And i will thank him too. But after a lot of reading. I think. Mate 9 users can only choose between magisk and TWRP. I hope i am wrong.
Click to expand...
Click to collapse
If you install root (patched magic boot img) on recovery_ramdisk and twrp on the erecovery partition you can have both. You'll just have to hold in volume up at boot to enable root or volume up + volume down to enter twrp or don't hold in anything to boot up uprooted. Follow the instructions on the Mate 20 X twrp thread and it should work. Personally I can't flash anything to erecovery after manually updating to Pie.
ajsmsg78 said:
TWRP for the Mate 20 X Pie works on the Mate 9. Make sure you thank Feeeza.
Click to expand...
Click to collapse
you try?
works fine?
Hurupdater for update pie x pie works?
aureliomilitao said:
you try?
works fine?
Hurupdater for update pie x pie works?
Click to expand...
Click to collapse
I flashed to pie with EMUI Flasher but hurupdater should work. You'd have to try it.
Hi, I had to recover my tablet and it updated to 9.1.0.332. My Magisk patched recovery_ramdisk from a previous version (9.0.x) is no longer working so I'm trying to find a download for a 9.1.0 EMUI ROM. The Firmware Finder doesn't find it and I can't find it through their website either. 9.0.x seem to be the latest I can find.
Not sure how else I can get root back, can I pull an image from the partition itself to patch it with Magisk and flash it with fastboot? I'm reluctant to flash anything (like TWRP for example) as long as I don't have the original firmware to extract and restore the original partitions.
Thanks for the help!
Which tablet version do you have? I have SHT-W09 and I can you provide with a download link for the firmware.
Unfortunately I do have 9.1.0.331 as latest version received on my tablet otherwise I could also provide a patched recovery_ramdisk.img if you have the same model.
My model is 10" wifi only CMR-W09 C432.
I found the full firmware and I have a Magisk patched recovery_ramdisk if anyone wants it.
Link to shared folder with all 3 files.
Direct link to full firmware CMR-W09 EMUI 9.1.0.332 (C432E5R1P3T8).
Direct link to patched recovery_ramdisk.
Direct link to original recovery_ramdisk.
I just have a weird issue getting to boot with Magisk activated. I used to just hold volume up during reboot up until the Huawei boot logo and release. I'd see the three options in yellow and it would continue to boot. Magisk would be active.
Now, I seem to only get Magisk activated with a USB cable hooked up and I am never sure how exactly I did it. When I think I got it, next time it will fail and Im struggling again with pushing volume buttons and powering off/on rebooting. I seem to have the most luck with both volume up and down when the tablet is powered off but that fails most of the time too.
Most of the time I just end up in EMUI recovery (which fails) and need to reboot again.
What exactly is the procedure? Did it change with EMUI 9.1 updates?
Thanks for the help.
Edit: recording this for my own sanity: just now got Magisk activated by powering off with USB disconnected, hold volume up & down simultaneously and connect USB. Release both volume buttons at the Huawei boot logo.
droidvark said:
I just have a weird issue getting to boot with Magisk activated. I used to just hold volume up during reboot up until the Huawei boot logo and release. I'd see the three options in yellow and it would continue to boot. Magisk would be active.
Now, I seem to only get Magisk activated with a USB cable hooked up and I am never sure how exactly I did it. When I think I got it, next time it will fail and Im struggling again with pushing volume buttons and powering off/on rebooting. I seem to have the most luck with both volume up and down when the tablet is powered off but that fails most of the time too.
Most of the time I just end up in EMUI recovery (which fails) and need to reboot again.
What exactly is the procedure? Did it change with EMUI 9.1 updates?
Thanks for the help.
Edit: recording this for my own sanity: just now got Magisk activated by powering off with USB disconnected, hold volume up & down simultaneously and connect USB. Release both volume buttons at the Huawei boot logo.
Click to expand...
Click to collapse
Hello Droidvark, thanks for the file links above, which have been very helpful. However, like you, I struggle to get my M5 pad to boot into (magisk) recovery, not erecovery, and I just don't seem to manage to do it anymore. Either I end up in unrooted mode or erecovery or some huawei usb update screen.
Can anybody help and let me know how I can boot my M5 mediapad into magisk/root/recovery mode? It used to work in the past by pressing the power and volume up buttons until the huawei/android logo appears, but over the last few days it hasn't worked anymore. I did upgrade to magisk 20.4 during that time, and emui 9.1 from 9.0, with the latter being the more likely culprit.
Anyway, I'm very grateful for any advice and help. Cheers, David
---------- Post added at 04:04 AM ---------- Previous post was at 03:11 AM ----------
spoo333 said:
Hello Droidvark, thanks for the file links above, which have been very helpful. However, like you, I struggle to get my M5 pad to boot into (magisk) recovery, not erecovery, and I just don't seem to manage to do it anymore. Either I end up in unrooted mode or erecovery or some huawei usb update screen.
Can anybody help and let me know how I can boot my M5 mediapad into magisk/root/recovery mode? It used to work in the past by pressing the power and volume up buttons until the huawei/android logo appears, but over the last few days it hasn't worked anymore. I did upgrade to magisk 20.4 during that time, and emui 9.1 from 9.0, with the latter being the more likely culprit.
Anyway, I'm very grateful for any advice and help. Cheers, David
Click to expand...
Click to collapse
'adb reboot recovery' did the trick and all is well now. It's possible the first magisk ramdisk patching wasn't successful on top of that.
spoo333 said:
Hello Droidvark, thanks for the file links above, which have been very helpful. However, like you, I struggle to get my M5 pad to boot into (magisk) recovery, not erecovery, and I just don't seem to manage to do it anymore. Either I end up in unrooted mode or erecovery or some huawei usb update screen.
Can anybody help and let me know how I can boot my M5 mediapad into magisk/root/recovery mode? It used to work in the past by pressing the power and volume up buttons until the huawei/android logo appears, but over the last few days it hasn't worked anymore. I did upgrade to magisk 20.4 during that time, and emui 9.1 from 9.0, with the latter being the more likely culprit.
Anyway, I'm very grateful for any advice and help. Cheers, David
---------- Post added at 04:04 AM ---------- Previous post was at 03:11 AM ----------
'adb reboot recovery' did the trick and all is well now. It's possible the first magisk ramdisk patching wasn't successful on top of that.
Click to expand...
Click to collapse
'adb reboot recovery' doesn't always work either. Once again stuck ... anybody have an idea how to enter magisk patched recovery? thx
spoo333 said:
'adb reboot recovery' doesn't always work either. Once again stuck ... anybody have an idea how to enter magisk patched recovery? thx
Click to expand...
Click to collapse
Hey,
You can install apk name Rashr and then there is option to go to recovery try that once and let me know what does it do.
Sent from my P5 mini using premium XDA app
PrashannaGP said:
Hey,
You can install apk name Rashr and then there is option to go to recovery try that once and let me know what does it do.
Sent from my P5 mini using premium XDA app
Click to expand...
Click to collapse
llello PrashannaGP,
thanks for trying to help. As expected, the app doesn't start up as it it needs root access. If I could boot into the magisk enabled recovery, then Magisk itself would also provide the option to boot into recovery. Without root access, neither of those two apps can offer that function
The problem is getting the pad to boot the magisk patched recovery partition once, then I'd be in business.
spoo333 said:
llello PrashannaGP,
thanks for trying to help. As expected, the app doesn't start up as it it needs root access. If I could boot into the magisk enabled recovery, then Magisk itself would also provide the option to boot into recovery. Without root access, neither of those two apps can offer that function
The problem is getting the pad to boot the magisk patched recovery partition once, then I'd be in business.
Click to expand...
Click to collapse
Please refer to this page.
https://huaweiflash.com/how-to-install-twrp-recovery-on-huawei-mediapad-m5/
Unfortunately I forgot that you have no root access.
Does your USB cable work well and
Works this code??
adb kill-server
adb devices
adb reboot
adb reboot bootloader
fastboot devices
fastboot flash recovery [downloaded twrp file]
fastboot reboot
adb reboot recovery
Try that post and if something went wrong I am responsible and will be happy to help you.
Sent from my P5 mini using XDA-Developers Legacy app
PrashannaGP said:
Please refer to this page.
https://huaweiflash.com/how-to-install-twrp-recovery-on-huawei-mediapad-m5/
Unfortunately I forgot that you have no root access.
Does your USB cable work well and
Works this code??
adb kill-server
adb devices
adb reboot
adb reboot bootloader
fastboot devices
fastboot flash recovery [downloaded twrp file]
fastboot reboot
adb reboot recovery
Try that post and if something went wrong I am responsible and will be happy to help you.
Sent from my P5 mini using XDA-Developers Legacy app
Click to expand...
Click to collapse
thank you for your help and offer to help me out (further) in case things went belly up. Don't know if it was your detailed description or downgrading Magisk to 20.3 (apparently there is some issue with bootloops or similar on my device and a few others), but it's working again )) I got my rooted pad back and I'm happy and grateful!!
For other users with a Mediapad M5 running Emui 9: remember to use fastboot flash recovery_ramdisk [magisk_patched.img] as per Magisk installation guide for Emui 9+ instead.
spoo333 said:
thank you for your help and offer to help me out (further) in case things went belly up. Don't know if it was your detailed description or downgrading Magisk to 20.3 (apparently there is some issue with bootloops or similar on my device and a few others), but it's working again )) I got my rooted pad back and I'm happy and grateful!!
For other users with a Mediapad M5 running Emui 9: remember to use fastboot flash recovery_ramdisk [magisk_patched.img] as per Magisk installation guide for Emui 9+ instead.
Click to expand...
Click to collapse
its my pleasure mate no worries now!
For those who want to try LineageOS 17.1/18.1-UNOFFICIAL-GSI . IMO stable enough to be used as your daily driver.
LOSQ/LiR is not developed nor maintained by me!
Credits: @eremitein
Requirements: basically full stock EMUI 9.1, with stock recovery_ramdisk.
Note: I prefer to install in fastboot mode, it's quick, easy and most importantly, safe.
IMPORTANT! Before booting up the ROM, you will need to perform a factory reset in stock recovery!
Install arm64-b.. only!
1. LOSQ - LineageOS 17.1-[10]-unofficial-GSI
with the GAPPS
GAPPS
without GAPPS
Vanilla
-----------------------
LiR- LineageOS 18.1-unofficial-[11]-GSI
Download
2. Extract the ROM .img file from the compressed file.
3. Flash extracted losq/lir... .img from fastboot , use command
fastboot flash system (file_name).img
4. Run command fastboot reboot, unplug your phone, when appears on screen yellow warning, press and hold for 3 sec Volume Up . In eRecovery select 'Wipe data/factory reset'.Reboot .
NFC patch:
https://forum.xda-developers.com/t/losq-lineageos-17-1-unofficial-gsi.4219291/post-84394147
Magisk root (23.0):
(Note: If you don't plan to use TWRP, simply install patched Recovery_ramdisk in fastboot mode. Run command
fastboot flash recovery_ramdisk magisk_patched-23.img ),
- download and install Magisk manager-23.apk:
https://mega.nz/file/go0m2RiR#M5UTv6FPjWPtDaGPr-u2tpJMCwdf8uwnniZg69LiGfw
- Install TWRP-9.1
https://mega.nz/#!tkcTlATI!A8UJGPBGtxJbLcUOJoxCGJj5PFZXzCnjbb3OkwqKTP8
over eRecovery (it's necessary on EMUI 9.1):
- copy TWRP file to the SD card, and also copy to the SD card patched Recovery_ramdisk:
https://mega.nz/file/lp1kHLxJ#htCMaPjSsg_dy0w_jNOft-t_DZRAPwhOvwy_Wr2cjX8
- flash TWRP - run command
fastboot flash recovery_ramdisk (TWRP's_name).img
- boot into TWRP, select storage - SD Card, select "Install image", find TWRP-9.1.img file and mark eRecovery, swipe. Go back, find magisk_patched-23.img file, mark Recovery, swipe. Go back to the TWRP's main menu, select Reboot > Recovery. Done.
Note: you then need to boot your phone every time via Recovery. It'll boot into android as normal but with root.
( Note: for those who want keep the erecovery as a fail-safe:
https://forum.xda-developers.com/t/...-erecovery-with-twrp-installed-on-it.4357127/ )
To remove Magisk reinstall stock recovery_ramdisk via TWRP or fastboot , download Here
How to boot into TWRP:
- Turn off your phone, connect to the PC (or charger), then press and hold Power + Volume Up, device will reboot into eRecovery (= TWRP).
How to boot into patched Recovery :
- Restart your phone, when appears the yellow warning on the screen, press and hold Volume Up for ~ 2 sec,
release the button and immediately press and hold again for ~ 2 sec. Repeat it 6-7 times, the device will reboot into Stock Recovery (you can perform Wipe cache or Factory reset).
Tips:
https://forum.xda-developers.com/t/treble-gsi-favorite-gallery-camera-and-file-manager.4246019/
I have tried this rom - but without the magisk as I don't really care for root.. However.. This rom still has one big missing feature.. Fingerprint unlock. I can go to register fingerprint. Add the finger multible times to complete the circle.. however.. every time it misses just the last part - it will fail. If anyone has a fix for this I would be happy to use this as my daily driver as it works just fine.
whitetigerdk said:
This rom still has one big missing feature.. Fingerprint unlock
Click to expand...
Click to collapse
I'm afraid you're wrong... It works perfectly for me.
Can confirm that so far everything works flawless. Fingerprint sensor is working on the phone too.
Thank you Alf.
Just two additional questions:
How will updates be perform in future?
How to switch from LOS 16 to this rom - the other P20 lite we have is still on v.16?
Cheers
Horqai
horqai said:
How will updates be perform in future?
Click to expand...
Click to collapse
Hi, I don't know bro, I'm not a developer . But you can check the update here:
https://sourceforge.net/projects/treblerom/files/LOSQ/
horqai said:
How to switch from LOS 16 to this rom
Click to expand...
Click to collapse
Install Service ROM using dload method (9.1.0.132 recomm.) , then you can safely flash 17.1 GSI. Dload method will erase all your data and will lock the BL again!
-Alf- said:
Hi, I don't know bro, I'm not a developer . But you can check the update here:
https://sourceforge.net/projects/treblerom/files/LOSQ/
Install Service ROM using dload method (9.1.0.132 recomm.) , then you can safely flash 17.1 GSI. Dload method will erase all your data and will lock the BL again!
Click to expand...
Click to collapse
Ugh, is there a way to install emui 9 without it locking my bootloader? I unlocked my bootloader via the @huaweihax method.
[/QUOTE]
XRealX said:
Ugh, is there a way to install emui 9 without it locking my bootloader?
Click to expand...
Click to collapse
OTA update, via HiSuite, you can try also through eRecovery ...
make sure to have the stock recovery flash.
XRealX said:
I unlock my bootloader via the @huaweihax method.
Click to expand...
Click to collapse
Idk how huaweihax method works, but the BL unlock
code is permanent, it wont expire, you use the same bootloader code to unlock if your device is relocked.
Btw, with EMUI 8 installed with May 2018 security patch you should be able to use DC-Unlocker or hcu-client to get BL unlock code for 4euros.
Or, you can also unlock BL for free using
PotatoNV method
OTA update, via HiSuite, you can try also through eRecovery ...
make sure to have the stock recovery flash.
Idk how huaweihax method works, but the BL unlock
code is permanent, it wont expire, you use the same bootloader code to unlock if your device is relocked.
Btw, with EMUI 8 installed with May 2018 security patch you should be able to use DC-Unlocker or hcu-client to get BL unlock code for 4euros.
Or, you can also unlock BL for free using
PotatoNV method
Click to expand...
Click to collapse
There's no way I'm paying for unlocking!
The huaweihax method works this way: you give some information about your device and you flash a slock file to the ramdisk. It unlocks your phone.
To prevent EMUI 9 from re-locking your device, you can flash a zip file to have a custom bootloader unlock code.
Btw, I have hyperlinked the thread that describes this in the "thingy" word.
I guess that custom code should work even if my device is re-locked.
I do not start the phone only in loop TWRP mode, what solution do I have to revive the phone
I do not start the phone only in loop TWRP mode, what solution do I have to revive the phone
How can I repair the factory erecovery I am using the phenix program but it gives me recovery error
itrisev said:
How can I repair the factory erecovery I am using the phenix program but it gives me recovery error
Click to expand...
Click to collapse
Sorry, this is not the DC-Phoenix support chat, let's please remember to keep conversations and comments in this thread about LOSQ - LineageOS 17.1, thanks...
Thanks @-Alf-
I followed all your advice in the LOS 16 thread to get 16 installed, but couldn't get gapps to work. So I thought lemme give LOS 17 a shot since it includes gapps, and it works great! However I get the same issue with fingerprint as @whitetigerdk. During fingerprint enrolment it works up until the last time you have to finger it, after which I get popup "Enrolment was not completed: Fingerprint enrolment didn't work. Try again or use a different finger". I can provide a screenshot but it's literally just that text.
Apart from that everything seems to work fine. Haven't installed magisk yet, will do that next.
An3skmbi said:
During fingerprint enrolment it works up until the last time you have to finger it, after which I get popup "Enrolment was not completed: Fingerprint enrolment didn't work.
Click to expand...
Click to collapse
-Alf- said:
Tested on 9.1.0.132.
Click to expand...
Click to collapse
-Alf- said:
Clean OS
Click to expand...
Click to collapse
-Alf- said:
Install Service ROM using dload method (9.1.0.132 recomm.)
Click to expand...
Click to collapse
Most of custom ROMs require lower build number, on latest build number may or may not work correctly.
If you have followed this guide to the letter and it didn't work, i'm afraid I cant help you .
I've not had any major issue with this LineageOS.
P.S.:
If all this has worked on my device, it does not mean that it goes with everyone else, and vice versa (we are talking about Huawei devices ).
@-Alf- Thanks, that might be it. I'm on firmware 9.1.0.200(C185E4R1P8T8) as that was the recommended one for LOS 16. Let me give it a shot with 132, will update with results.
Edit: With "Clean OS" I assume you mean a clean install of the stock ROM? My approach is to install 132 via dload, unlock bootloader, then follow your installation steps.
An3skmbi said:
With "Clean OS" I assume you mean a clean install of the stock ROM? My approach is to install 132 via dload, unlock bootloader, then follow your installation steps.
Click to expand...
Click to collapse
Yes, but I'm afraid there's no .132 build number for region C185 on androidhost.ru
IMO you can get it via paid service only, for 17euros , hm...look here
.132
The difference between .132 and .200 is google patch - may 2019 vs. july 2019.
-Alf- said:
Yes, but I'm afraid there's no .132 build number for region C185 on androidhost.ru
Click to expand...
Click to collapse
What about this one? http://huawei-firmware.com/rom/huawei-p20-lite/ane-lx1/42056
It doesn't have a dload folder, it's just the update.zip basically, so I'm not sure how to flash it only unlocked my phone yesterday, not used to huawei roms yet.
Edit: they explain how here, you create the dload folder manually.
An3skmbi said:
they explain how here, you create the dload folder manually.
Click to expand...
Click to collapse
This guide is valid for Android 6 . Huawei-firmware is a really reliable website .
-Alf- said:
This guide is valid for Android 6 . Huawei-firmware is a really reliable website .
Click to expand...
Click to collapse
What do you mean really reliable when the guide is for Android 6? Is there a way to flash the 132 ROM from huawei-firmware?
Also, magisk installation worked perfectly by following your instructions. I can pass safety net with the universal safetynet fix module and got google play certification with the props module.
Is there a way to now boot into TWRP (erecovery)? Currently when booting it doesn't show the option to hold volume up to enter erecovery, it immediately says your phone is booting now. The only way to get into TWRP is to fastboot flash recovery twrp, do stuff there, then flash magisk_patched-ane-v21 over recovery and reboot.
Edit: I captured a logcat while getting the fingerprint enrollment error, there are some exceptions about the enrollment, not sure if that could mean something to the devs to help fix it?
An3skmbi said:
Is there a way to flash the 132 ROM from huawei-firmware?
Click to expand...
Click to collapse
Nope.
An3skmbi said:
Is there a way to now boot into TWRP (erecovery)?
Click to expand...
Click to collapse
Oops I thought I mentioned it in my post, mea culpa.
You have two options:
1. Turn off phone, connect to PC (or charger), then pres and hold Power + Volume Up, device will reboot into eRecovery (= TWRP).
2. Restart phone, when appears the yellow warning on screen, press Volume up, hold for ~ 2 sec,
release the button and immediately press and hold again for 2 sec, repeat it 6-7 times, the device will reboot into Stock Recovery , then you can do normal restart - Reboot system now.