Related
I've followed instructions to unlock my bootloader which is done. I'm not sure if - "Device is unlocked. Status Code 3:" is correct or not, but that is what I see.
After unlocking I flashed TWRP 2.6.3.0-xt1032.img and it flashed correctly according to adb (attached). When I reboot the phone into bootloader and select recovery the screen just goes blank. I also tried "recovery-clockwork-touch-6.0.4.7-falcon.img", which seemed to flash OK in adb. The bootloader screen goes blank when I select recovery on the phone for CWM as well.
Both recovery flashes showed a similar result on the phone - this paste is for CWM
In Moto bootmode:
USB Connected
cmd: getvarartition-type:recovery
cmd: getvar:max-download-size
cmd: download:07b2000
cmd: flash:recovery
Mismatched partition zize (recovery)
The phone has stock Android 5.0.2 installed and still works, but I can't get any further than flashing the recovery image in adb. I did flash the logo.bin in adb and it seemed to flash correctly .
I'm running Windows 8.1, USB 3 ports.
Is there something I'm missing, or a different way to do the root? I'm stuck at this point, but luckily can run with the stock ROM for now.
I would appreciate any help I can get, Thanks
both recoveries you have used are seemingly outdated for lollipop bootloader. i would suggest you to try out the newly built TWRP (which is not yet publicly released) cant post URLs here yet but search for '[RECOVERY][falcon]TWRP 2.8.7.0 touch recovery [2015-06-24]' here in XDA
---------- Post added at 11:14 PM ---------- Previous post was at 11:03 PM ----------
here is the URL: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
koshikas said:
both recoveries you have used are seemingly outdated for lollipop bootloader. i would suggest you to try out the newly built TWRP (which is not yet publicly released) cant post URLs here yet but search for '[RECOVERY][falcon]TWRP 2.8.7.0 touch recovery [2015-06-24]' here in XDA
---------- Post added at 11:14 PM ---------- Previous post was at 11:03 PM ----------
here is the URL: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Click to expand...
Click to collapse
I tried and same result. After flashing with adb - disconnect USB , boot into bootloader, down to recovery, push power button and blank screen. Normal power up does the same thing as does factory. Ad I can confirm the version is 41.18.
Thanks
jjcdennis said:
I tried and same result. After flashing with adb - disconnect USB , boot into bootloader, down to recovery, push power button and blank screen. Normal power up does the same thing as does factory. Ad I can confirm the version is 41.18.
Thanks
Click to expand...
Click to collapse
these blank screens are quiet frustrating, can you get hold of the stock firmware for your model and flash back the stock recovery first and then try again with latest custom recoveries
koshikas said:
these blank screens are quiet frustrating, can you get hold of the stock firmware for your model and flash back the stock recovery first and then try again with latest custom recoveries
Click to expand...
Click to collapse
I had problems last weekend after trying to go to CM12.1 after rooting and ending up in a bootloader loop. I ended up using a KitKat stock rom and mfastboot2 and typed in all of the lines - it worked. The phone then updated to 5.0.2 via auto update.
I don't have that stock from the network update, but found this one - XT1034_Retail_Canada_502_Stock_Untouched which contains 3 files, Meta-inf, system and boot.img. I don't see a recovery in the folder. I'm not really sure what to look for and how to do this.
Thanks
jjcdennis said:
I had problems last weekend after trying to go to CM12.1 after rooting and ending up in a bootloader loop. I ended up using a KitKat stock rom and mfastboot2 and typed in all of the lines - it worked. The phone then updated to 5.0.2 via auto update.
I don't have that stock from the network update, but found this one - XT1034_Retail_Canada_502_Stock_Untouched which contains 3 files, Meta-inf, system and boot.img. I don't see a recovery in the folder. I'm not really sure what to look for and how to do this.
Thanks
Click to expand...
Click to collapse
make sure you get exactly a stock ROM that is made for your model. trying firmware made for other models is surefire way of bricking you phone. usually the stock firmware images ending with '*.xml.zip' do have a 'recovery.img' in them.
koshikas said:
make sure you get exactly a stock ROM that is made for your model. trying firmware made for other models is surefire way of bricking you phone. usually the stock firmware images ending with '*.xml.zip' do have a 'recovery.img' in them.
Click to expand...
Click to collapse
Thanks again.
If I find a correct ROM (I do have a KitKat 4.4.4 version), do I flash back with adb, or with mfastbootv2?
The ROM I showed was from here: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
I have also found a firmware link on this thread "http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795" that looks to be in the correct format. There are thorough instructions on how to flash the firmware, but I am not sure if this will fix my issue or not.
Would appreciate any advice on how to proceed.
Thanks
I finally understood your comment "...can you get hold of the stock firmware for your model and flash back the stock recovery first and then try again with latest custom recoveries". I got a copy of the stock firmware, extracted the recovery from it and flashed it via adb to the phone - ok. I then tried to get into phone fastboot recovery, but was faced with the blank screen again. I flashed twrp 2.8.7.0 and the same thing in fastboot recovery - blank screen. I also tried cwm 6.0.5.1 and the same thing, blank screen.
ADB sees the device and accepts the commands, but the Motorola fastboot recovery doesn't open any of the recoveries. Nothing else in the bootloader seems to work ie: Factory - blank screen.
Every one of the recovery files other than the stock recovery shows a pink colored error "Mismatched partition size (recovery).
Anybody have any ideas as to what I can do to get a recovery to work?
Is there a different way to root this phone?
@jjcdennis i think you should post this to one of the active threads, since nobody with experience (this is well beyond mine) has dropped in yet. i would highly recommend; http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Moved to http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
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
I installed the Stable Android 10 on my GM1910 via TWRP, totally forgetting about maintaining root and TWRP.
So how do I bring back TWRP and root?
fastboot boot doesn't seem to work, I managed to pull the boot.img and patch it with Magisk from another device but flashing it through fastboot ends up in an endless bootanimation.
Could anyone help me? here's a link of the boot.img i pulled, it works if you flash it without magisk patching it.
Link: https://drive.google.com/file/d/1O8lF1UDwwu0zT8ro5Q1gKKfdxF-HGPEW/view?usp=sharing
(Almost) exactly the same here. I tired flashing a patched boot.img, it actually boots - but magisk manager gets stuck on the splash screen and some apps, including chrome, won't start. Trying to boot TWRP results in the phone getting stuck on the "fastboot mode" screen.
My only solution would be to downgrade, root, keep the upgrade this time. But because my ISP is doing some maintenance work I don't have wifi - and restoring my phone through mobile data does not seem to work correctly.
EDIT: In fastboot, neither bootloader version nor baseband version are show, product name is "msmnile". Has this always been that way?
EDIT 2, solution:
I extracted the boot.img from the device, and patched it using magisk on the same phone:
https://drive.google.com/file/d/1-Gf-6iXSFuYT5xDR-mnLKANvkXUHal9e/view?usp=sharing
Run this command in fastboot so you know which is the CURRENT active slot :
Code:
fastboot getvar current-slot
Run this command so you can flash the correct slot :
Code:
fastboot flash boot_X magisk_patched.img
replace X with the a or b from the command before.
:good:
dmj0shu4 said:
I installed the Stable Android 10 on my GM1910 via TWRP, totally forgetting about maintaining root and TWRP.
So how do I bring back TWRP and root?
fastboot boot doesn't seem to work, I managed to pull the boot.img and patch it with Magisk from another device but flashing it through fastboot ends up in an endless bootanimation.
Could anyone help me? here's a link of the boot.img i pulled, it works if you flash it without magisk patching it.
Link: https://drive.google.com/file/d/1O8lF1UDwwu0zT8ro5Q1gKKfdxF-HGPEW/view?usp=sharing
Click to expand...
Click to collapse
Hi sorry to hear that you got this problem and hopefully it gets fixed. I have another question: does that mean using TWRP to completely clean the device then installing Android 10 via zip will remove TWRP and fastboot everything? Does that mean after installing, everything will be refreshed like a box opened phone?
dmj0shu4 said:
I installed the Stable Android 10 on my GM1910 via TWRP, totally forgetting about maintaining root and TWRP.
So how do I bring back TWRP and root?
fastboot boot doesn't seem to work, I managed to pull the boot.img and patch it with Magisk from another device but flashing it through fastboot ends up in an endless bootanimation.
Could anyone help me? here's a link of the boot.img i pulled, it works if you flash it without magisk patching it.
Link: https://drive.google.com/file/d/1O8lF1UDwwu0zT8ro5Q1gKKfdxF-HGPEW/view?usp=sharing
Click to expand...
Click to collapse
If you have an endless boot animation you might be trying to boot from the wrong slot, try using the fastboot set_active command to change slot, then restart
h0l said:
Run this command in fastboot so you know which is the CURRENT active slot :
Run this command so you can flash the correct slot : replace X with the a or b from the command before.
:good:
Click to expand...
Click to collapse
I got a bit confused.
If the current slot is boot_a, i flash it in boot_b or am I supposed to flash on the one that isn't the current slot?
djsubterrain said:
If you have an endless boot animation you might be trying to boot from the wrong slot, try using the fastboot set_active command to change slot, then restart
Click to expand...
Click to collapse
Which is the default active slot? Is it okay to use either of the 2?
dmj0shu4 said:
Which is the default active slot? Is it okay to use either of the 2?
Click to expand...
Click to collapse
Either one should work if the rom and the rooted boot image is on it (If you are rooting). That's why you should install using TWRP, if you look in the reboot menu it will show you the active slot.
djsubterrain said:
Either one should work if the rom and the rooted boot image is on it (If you are rooting). That's why you should install using TWRP, if you look in the reboot menu it will show you the active slot.
Click to expand...
Click to collapse
I would've used TWRP but it won't let me boot into it
fastboot boot [recovery.img] does not seem to work for android 10, atleast on my case
dmjoshu4 said:
I got a bit confused.
If the current slot is boot_a, i flash it in boot_b or am I supposed to flash on the one that isn't the current slot?
Click to expand...
Click to collapse
You are supposed to flash it in the one that IS the active one. Because you do want to root the slot that you'll be booting.
does that mean using TWRP to completely clean the device then installing Android 10 via zip will remove TWRP and fastboot everything? I.e. everything will be refreshed like a box opened phone?
gh279760559 said:
does that mean using TWRP to completely clean the device then installing Android 10 via zip will remove TWRP and fastboot everything? I.e. everything will be refreshed like a box opened phone?
Click to expand...
Click to collapse
not everything, just twrp and root will be gone if you restarted without installing magisk to the inactive slot
h0l said:
(Almost) exactly the same here. I tired flashing a patched boot.img, it actually boots - but magisk manager gets stuck on the splash screen and some apps, including chrome, won't start. Trying to boot TWRP results in the phone getting stuck on the "fastboot mode" screen.
My only solution would be to downgrade, root, keep the upgrade this time. But because my ISP is doing some maintenance work I don't have wifi - and restoring my phone through mobile data does not seem to work correctly.
EDIT: In fastboot, neither bootloader version nor baseband version are show, product name is "msmnile". Has this always been that way?
EDIT 2, solution:
I extracted the boot.img from the device, and patched it using magisk on the same phone:
https://drive.google.com/file/d/1-Gf-6iXSFuYT5xDR-mnLKANvkXUHal9e/view?usp=sharing
Run this command in fastboot so you know which is the CURRENT active slot :
Code:
fastboot getvar current-slot
Run this command so you can flash the correct slot :
Code:
fastboot flash boot_X magisk_patched.img
replace X with the a or b from the command before.
:good:
Click to expand...
Click to collapse
dude, thanks for this, i was banging my head against a wall trying to get root to work. I used your patched boot img and i had the version mismatch, but i local updated my android and it has root!
dmj0shu4 said:
I would've used TWRP but it won't let me boot into it
fastboot boot [recovery.img] does not seem to work for android 10, atleast on my case
Click to expand...
Click to collapse
I have not been able to boot TWRP either in fastboot mode - got stuck at "OnePlus Logo FastBoot" black screen.
Hi guys.. can you post the steps in rooting android 10??
I've already had bootloader unlocked.
Do i need to.follow the steps intended for android 9??
Like
1. Install TWRP via fastboot.. (2files)
2. Reboot to twrp.
3. Flash magisk via twrp??
Is that it?? If so. Then after reading this thread.. some of. You mentioned about boot. Img?? Patched?? What's that supposed to mean?? Sir??
Thanks. Any advice is highly appreciated..
---------- Post added at 08:30 AM ---------- Previous post was at 08:28 AM ----------
And by the way..
Im on Gm1910 model. Global rom. Gm21AA build.. if that info would matter.. i dont actually need the root on android 9. Coz parallel app is working.. but now in android 10. It isnt working.. so.i need to root to grant su to game guardian.. thanks..
MigbyPie said:
I have not been able to boot TWRP either in fastboot mode - got stuck at "OnePlus Logo FastBoot" black screen.
Click to expand...
Click to collapse
Same.
I've read that Q/10 is different and you can't install TWRP like that anymore. Supposedly you need to use the MSM tool or the all-in-one tool but I've tried both of those and still can't boot to TWRP.
E30Nova said:
Same.
I've read that Q/10 is different and you can't install TWRP like that anymore. Supposedly you need to use the MSM tool or the all-in-one tool but I've tried both of those and still can't boot to TWRP.
Click to expand...
Click to collapse
Hopefully there will be a solution. I had tried to update from Pie to Q10 while staying rooted and it didn't work. So I had to wipe the whole device and decided to wait for a smoother root method for my device. If you have any other ideas about rooting Q10 let me know. Thank you
h0l said:
(Almost) exactly the same here. I tired flashing a patched boot.img, it actually boots - but magisk manager gets stuck on the splash screen and some apps, including chrome, won't start. Trying to boot TWRP results in the phone getting stuck on the "fastboot mode" screen.
My only solution would be to downgrade, root, keep the upgrade this time. But because my ISP is doing some maintenance work I don't have wifi - and restoring my phone through mobile data does not seem to work correctly.
EDIT: In fastboot, neither bootloader version nor baseband version are show, product name is "msmnile". Has this always been that way?
EDIT 2, solution:
I extracted the boot.img from the device, and patched it using magisk on the same phone:
https://drive.google.com/file/d/1-Gf-6iXSFuYT5xDR-mnLKANvkXUHal9e/view?usp=sharing
Run this command in fastboot so you know which is the CURRENT active slot :
Code:
fastboot getvar current-slot
Run this command so you can flash the correct slot :
Code:
fastboot flash boot_X magisk_patched.img
replace X with the a or b from the command before.
:good:
Click to expand...
Click to collapse
You saved my life! Thank you!
But how do we get twrp now? Is there any way?
Me too. Use tool all in one but it doesnt work. Stuck at "waiting twrp boots".
Any help, thanks.
Same here any Solution?
Sent from my GM1911 using Tapatalk
---------- Post added at 08:14 AM ---------- Previous post was at 08:14 AM ----------
Stuck at Fastboot booting when flashed img and also zip
Sent from my GM1911 using Tapatalk
I updated my phone to 10 last night, followed the same guide as I have for every other update but this time I lost root for some reason.
I still have TWRP recovery on there but it can't read internal storage so I can't flash Magisk.
I tried changing file system to ext 2 then back to 4 and then repairing it as I read elsewhere and this wiped the phone obviously but internal storage seemed to be working until I set the phone up again, downloaded Magisk, rebooted to recovery and I'm back where I started, internal storage showing as 0mb in TWRP.
Any ideas how to fix?
Magisk on G7 Play XT1952-4 Installed Succesfully
(Just a heads up. I have never posted to XDA before but have lurked on here for years. I don't have enough posts to post it in the Dev section. So I apologize if my post format is bad. But I will do my best. Hopefully I am not reporting old news, I've been waiting a few months to finally get Magisk to work on this phone.)
I do not take responsibility if you brick your phone doing this. So do it at your own risk.
Google Drive folder link with all files at the bottom of this post with screenshots as well
Install:
Firmware used during this is PPY29.105_160 (Firmware included in GDrive folder)
BOOTLOADER HAS TO BE UNLOCKED ON YOUR PHONE
I suggest you to backup and factory reset your phone before doing this.
If you're already on this firmware, then I have placed both the stock boot.img and the magisk_patched.img separate as well so you don't have to unzip the full firmware. I haven't tried this with other models of this phone or firmwares. Upgrade to this firmware if on an older version. Multiple ways to do so I'm sure you can figure it out
Copy the boot.img to your phones storage
Install Magisk Manager 7.3.4 aka 239 (APK in GDrive folder). Make sure all 3 options are checked in advanced settings in Magisk. Click install on Magisk and patch the file and locate it on your phone.
Place the patched.img in your ADB folder. Reboot into fastboot. I used CMD in Windows so I ran the following "fastboot flash boot magisk_patched.img"
Toggle up to Boot Recovery
Please Note. When I did the following. For some reason I was unable to get to the stock recovery after doing this. If I remove modules and reboot the phone Magisk is "not installed" however if you reboot the phone and go into Fastboot mode and then select the option of boot to recovery, it boots the phone normal with magisk enabled??? :confused. Eh at this point I'm just glad to have Magisk installed on this phone finally lol. I'm sure you can find the answer in the Magisk in Recovery section here
Magisk should be installed now after booting up. Check Magisk Manager to verify.
Notes:
I tried to install one module just to verify it wasn't a fluke and I was able to do so successfully
Once again I apologize if this post is unorganized or anything. Running on little sleep
I will do my best to answer any questions you might have from my experience when I am able to.
GOOGLE DRIVE FOLDER LINK
Nice work OP. Well written guide. Clear and concise.
i need some help i tried this method and ended up loosing baseband idk what i did wrong i have a retail varient , tried flashing stock rom multiple times do we have a persist.img to get the phone booting again ? twrp wont even boot i get the failed to many links error to see if wiping the phone that way would make it boot i flashed to both banks i have the XT195-4 varian
Use rsd lite to flash full rom it will reset your phone then enable usb debugging so you can reboot to fastboot then follow the instructions
Linuxassassin said:
Use rsd lite to flash full rom it will reset your phone then enable usb debugging so you can reboot to fastboot then follow the instructions
Click to expand...
Click to collapse
Thank you I managed to create a flash.bat with revived the phone I can confirm working on retail varient firmware 138
Ok this is a bit odd. Managed to get magisk installed. Rebooted and magisk is no longer installed. Figured I would have to reboot recovery again. Now whenever I go to boot recovery in the bootloader it just falls back to the bootloader.
The recovery option in magisk will not stick either it seems
Edit: Not sure what happened. I reflashed the stock firmware for my device, went through the steps again, and now magisk seems to have stuck. I do have to boot to recovery, but that was to be expected according to the documentation.
Oh Viper4Android, how I have missed thee
Edit 2: It appears the reboot to recovery option in magisk is what is breaking my install. As long as I do not try to reboot to recovery from anything outside of the bootloader, magisk sticks. Not sure what the cause for this is, but for now it is best to stay away from those options in Magisk
Edit 3: Not sure what the issue is, but after some tinkering, and a reboot, booting recovery to get magisk loaded does not work. Reboot to recovery takes me straight to the bootloader. If I click start the phone boots without magisk, and if I hold the button combo I get the stock recovery, but magisk appears to be gone
Please help
I flash wrong boot so I reflashed the entire firmware then patched the boot.img of the firmware I just flashed, all ok.
I flashed the patched boot image and toggled volume key to recovery but have no options there, so have to start phone by holding power button.
When phone boots up magisk is not installed. This is killing me so close yet...
P.s I omitted erase user data and erase DDR and phone is exactly as I left it ?
moochermick said:
Please help
I flash wrong boot so I reflashed the entire firmware then patched the boot.img of the firmware I just flashed, all ok.
I flashed the patched boot image and toggled volume key to recovery but have no options there, so have to start phone by holding power button.
When phone boots up magisk is not installed. This is killing me so close yet...
P.s I omitted erase user data and erase DDR and phone is exactly as I left it
Click to expand...
Click to collapse
your missing a step , what worked for me , since i updated my phone manually and now im on slot_a flash both banks with the magisk_patched.img and you wont have that problem , if your on slot_b flash slot_a as well , and it should work , fastboot getvar all to see what slot is bootable
@thenatti
Thanks I will give that ago.
thenatti said:
your missing a step , what worked for me , since i updated my phone manually and now im on slot_a flash both banks with the magisk_patched.img and you wont have that problem , if your on slot_b flash slot_a as well , and it should work , fastboot getvar all to see what slot is bootable
Click to expand...
Click to collapse
I have flashed the patched boot to both banks and still magisk not installed, what's all this talk about booting from recovery, I can't do anything from recovery except hold the power button to restart the phone.
Any further suggestions?
Ok here's what worked...
Reflashed all firmware and restarted phone,
Flashed patched boot.img and in fastboot on pc "fastboot continue" phone rebooted.
Back into fastboot on phone and selected "recovery" phone rebooted and Magisk installed.???
Many many thanks to op and everyone involved.
Can anyone make a video with installation of Magisk on this device, PLEASE!! Will be more easy..
I am thinking my original problem is with Magisk itself. For some reason I randomly lose root after a restart, and booting recovery just goes straight back to the bootloader. It hasnt happened to me again, but it happened twice yesterday.
I am usually good a bug tracking, but I have been unable to narrow this down to a specific thing.
Anyway.... today things are working great.
moochermick said:
Ok here's what worked...
Reflashed all firmware and restarted phone,
Flashed patched boot.img and in fastboot on pc "fastboot continue" phone rebooted.
Back into fastboot on phone and selected "recovery" phone rebooted and Magisk installed.
Many many thanks to op and everyone involved.
Click to expand...
Click to collapse
Can you bring me your steps for install Magisk on your device with variant that you have, please?
I would suggest for people having trouble with getting magisk installed
A few things to note
No will need to boot into fastboot then use volume keys to
Select recovery option Everytime you boot or you won't be rooted
Stay on the beta of magisk cause stable is not ready for our device
If you brick use rsd lite with latest firmware
Thats on https://mirrors.lolinet.com/firmware/moto/channel/official/
How to boot in fastboot is volume up and power key
When you flash firmware via rsd lite it will factory reset your phone
Then after that setup your phone but don't connect to WiFi or do
Just enable developer options
USB debugging
Plug phone into PC
If you don't have the us varient of the phone get the firmware for your phone
transfer the boot.img from your firmware to your phone
install magisk manager from the original post
Then follow the instructions to install magisk
ALSO MAKE SURE YOUR BOOTLOADER IS UNLOCKED
Or you will brick your phone
Hope that helps
I have had a successful install pretty stable been running great for I think 3days now
Mods I installed
Viper4android
Energized
Edxposed needs riru core to work
Gravitybox for pie requires edxposed
Anyone have the boot.img for firmware
PPYS29.105-134-2
---------- Post added at 10:50 PM ---------- Previous post was at 10:44 PM ----------
Linuxassassin said:
I have had a successful install pretty stable been running great for I think 3days now
Mods I installed
Viper4android
Energized
Edxposed needs riru core to work
Gravitybox for pie requires edxposed
Click to expand...
Click to collapse
How you could flash the modules?
thx
Linuxassassin said:
I would suggest for people having trouble with getting magisk installed
A few things to note
No will need to boot into fastboot then use volume keys to
Select recovery option Everytime you boot or you won't be rooted
Stay on the beta of magisk cause stable is not ready for our device
If you brick use rsd lite with latest firmware
Thats on
How to boot in fastboot is volume up and power key
When you flash firmware via rsd lite it will factory reset your phone
Bro thank you so much rsd lite unbricked my device!
Then after that setup your phone but don't connect to WiFi or do
Just enable developer options
USB debugging
Plug phone into PC
If you don't have the us varient of the phone get the firmware for your phone
transfer the boot.img from your firmware to your phone
install magisk manager from the original post
Then follow the instructions to install magisk
ALSO MAKE SURE YOUR BOOTLOADER IS UNLOCKED
Or you will brick your phone
Hope that helps
Click to expand...
Click to collapse
Bro thank you so much rsd lite unbricked my device!
Fdraco10 said:
Anyone have the boot.img for firmware
PPYS29.105-134-2
---------- Post added at 10:50 PM ---------- Previous post was at 10:44 PM ----------
How you could flash the modules?
Click to expand...
Click to collapse
You search riru core in modules
Install that reboot to recovery
Flash edxposed
Funfact gsi won't flash on a phone till we get unofficial twrp
So I use gravitybox for pie hence my power menu
Hi everyone,
since yesterday ive got a HTC U12+. Now I want to root the phone. But the latest TWRP (TWRP 3.3.1-0 Released) is not compatible with PIE. (Error 23 RU_READ_PARTITION_FAIL read/open partition fail)
Is there any way to root the phone?
Thank you for your help.
alexmentin said:
Hi everyone,
since yesterday ive got a HTC U12+. Now I want to root the phone. But the latest TWRP (TWRP 3.3.1-0 Released) is not compatible with PIE. (Error 23 RU_READ_PARTITION_FAIL read/open partition fail)
Is there any way to root the phone?
Thank you for your help.
Click to expand...
Click to collapse
Root in PIE and latest twrp are working good
did you unlock the phone?
did you encrypt the phone?
SIRKRA said:
Root in PIE and latest twrp are working good
did you unlock the phone?
did you encrypt the phone?
Click to expand...
Click to collapse
Yes the Phone is unlocked.
How do I encrypt it?
Sorry, my fault I was on download mode.
When you boot the twrp.img in fastboot, than it works.
Thanky you for your help
SIRKRA said:
Root in PIE and latest twrp are working good
did you unlock the phone?
did you encrypt the phone?
Click to expand...
Click to collapse
I want to boot temporary to TWRP so I can flash the magisk.zip to get root. But when I boot temporary to TWRP (with fastboot) - TWRP asks for a decryption pattern. So I entered my phone pattern but TWRP says that it's wrong. Therefore I can't access my partition to flash the zip.
The bootloader is unlocked. As I can see in my settings, my phone is encrypted but I never encrypted it. I think it's per default encrypted.
Is it because TWRP support for the HTC U12+ is dead? How did you root it?
Has anyone rooted 2.50.709.3 (it fixed the stutter on startup & mic is clearer) will tarp 3.3.1 0 work this second update on Pie, (Taiwan model) I intend to temp twrp to put magisk so on phone, bootloader unlocked already
---------- Post added at 04:25 PM ---------- Previous post was at 04:15 PM ----------
byinhh said:
I want to boot temporary to TWRP so I can flash the magisk.zip to get root. But when I boot temporary to TWRP (with fastboot) - TWRP asks for a decryption pattern. So I entered my phone pattern but TWRP says that it's wrong. Therefore I can't access my partition to flash the zip.
The bootloader is unlocked. As I can see in my settings, my phone is encrypted but I never encrypted it. I think it's per default encrypted.
Is it because TWRP support for the HTC U12+ is dead? How did you root it?
Click to expand...
Click to collapse
Unlock bootloader first via htcdev, Make sure you msgisk on your memory card no bigger than 32gb as twrp won't recognise it if it's bigger, In bootloader mode not download mode ,make sure yr adb working, then type fastboot boot twrp.img in cmd and from ur PC adb folder. It will boot into twrp and flash msgisk from there
It's working!
jab5555 said:
Has anyone rooted 2.50.709.3 (it fixed the stutter on startup & mic is clearer) will tarp 3.3.1 0 work this second update on Pie, (Taiwan model) I intend to temp twrp to put magisk so on phone, bootloader unlocked already
---------- Post added at 04:25 PM ---------- Previous post was at 04:15 PM ----------
Unlock bootloader first via htcdev, Make sure you msgisk on your memory card no bigger than 32gb as twrp won't recognise it if it's bigger, In bootloader mode not download mode ,make sure yr adb working, then type fastboot boot twrp.img in cmd and from ur PC adb folder. It will boot into twrp and flash msgisk from there
Click to expand...
Click to collapse
Thank you very much! It worked!
For other people having the same problems:
What I did:
Prerequisites: 1. Bootloader must be unlocked, 2. adb drivers are correctly working, 3. USB-Debugging enabled
1. Downloaded latest magisk.zip file and put it on the microSD card (not bigger than 32GB)
2. Put into smartphone
3. connect and booted to bootloader (via adb reboot bootloader)
4. typed fastboot boot twrp.img (from the path, where twrp.img is located)
5. Now TWRP is asking you for a decryption pattern. Ignore this and click on Cancel. After that you will get the normal main menu of TWRP.
6. Click on Install and choose your microSD.
7. Flash your magisk.zip.
byinhh said:
Thank you very much! It worked!
For other people having the same problems:
What I did:
Prerequisites: 1. Bootloader must be unlocked, 2. adb drivers are correctly working, 3. USB-Debugging enabled
1. Downloaded latest magisk.zip file and put it on the microSD card (not bigger than 32GB)
2. Put into smartphone
3. connect and booted to bootloader (via adb reboot bootloader)
4. typed fastboot boot twrp.img (from the path, where twrp.img is located)
5. Now TWRP is asking you for a decryption pattern. Ignore this and click on Cancel. After that you will get the normal main menu of TWRP.
6. Click on Install and choose your microSD.
7. Flash your magisk.zip.
Click to expand...
Click to collapse
i did the same thing but got the message "This device is corrupt. It can´t be trusted and will not boot"
bronyel said:
i did the same thing but got the message "This device is corrupt. It can´t be trusted and will not boot"
Click to expand...
Click to collapse
I had that error on my Pixel 2 XL when an update broke my root and I tried to reflash magisk which I believe my boot.img was already patched by magisk previously. I was stuck in a boot loop. After days of not finding a solution, I ended up flashing a stock image. I then reflashed magisk. The issue may be that the boot image is on the wrong partition or corrupted. There may be a solution but I never did find one at that time.
---------- Post added at 04:28 PM ---------- Previous post was at 04:17 PM ----------
byinhh said:
Thank you very much! It worked!
For other people having the same problems:
What I did:
Prerequisites: 1. Bootloader must be unlocked, 2. adb drivers are correctly working, 3. USB-Debugging enabled
1. Downloaded latest magisk.zip file and put it on the microSD card (not bigger than 32GB)
2. Put into smartphone
3. connect and booted to bootloader (via adb reboot bootloader)
4. typed fastboot boot twrp.img (from the path, where twrp.img is located)
5. Now TWRP is asking you for a decryption pattern. Ignore this and click on Cancel. After that you will get the normal main menu of TWRP.
6. Click on Install and choose your microSD.
7. Flash your magisk.zip.
Click to expand...
Click to collapse
I also wanted to add that after doing this, download the latest MagiskManager.apk from this site and install.
After installation, start the Magisk manager app and press OK on the popup to reboot the phone.
Next, just download a root checker app from the play store to check for root.
bronyel said:
i did the same thing but got the message "This device is corrupt. It can´t be trusted and will not boot"
Click to expand...
Click to collapse
That's very strange. I didn't had that problem. I found a Q&A at xda-developers where someone had the same problem. Perhaps it might help you.
https://forum.xda-developers.com/u12-plus/help/wont-boot-device-corrupt-t3927896
The other way to get root is to patch the boot.img.
byinhh said:
That's very strange. I didn't had that problem. I found a Q&A at xda-developers where someone had the same problem. Perhaps it might help you.
https://forum.xda-developers.com/u12-plus/help/wont-boot-device-corrupt-t3927896
The other way to get root is to patch the boot.img.
Click to expand...
Click to collapse
Patching the boot.img is the method I did to root last night. All rooted and Magisk Manager + Leedroid Rom installed. Looks good.
*Is there a easy way to install TWRP now? / Is there any point? I am not going to do any more customisation or install any other ROMS or do any OTA updates for the next 2-3 years! It would be nice to have the option of having a recovery and performing a nandroid back-up...only because that's what I have been doing for years. I've only ever needed a backup once, but it was a big help when I did! I have no idea if the phone is encrypted or not (not too sure what this means). My APP data + photos + Contacts / Calendar are backed-up to Google.
no support for this phone anymore...
sonny123 said:
Patching the boot.img is the method I did to root last night. All rooted and Magisk Manager + Leedroid Rom installed. Looks good.
*Is there a easy way to install TWRP now? / Is there any point? I am not going to do any more customisation or install any other ROMS or do any OTA updates for the next 2-3 years! It would be nice to have the option of having a recovery and performing a nandroid back-up...only because that's what I have been doing for years. I've only ever needed a backup once, but it was a big help when I did! I have no idea if the phone is encrypted or not (not too sure what this means). My APP data + photos + Contacts / Calendar are backed-up to Google.
Click to expand...
Click to collapse
If you want to see whether your phone is encrypted or not:
Go to Settings - Security & location - Advanced - Encryption & credentials
I think it is encrypted by default.
I have TWRP installed on my phone but without the decryption of my internal storage most functions will not be available. (No Nandroid Backups, no flashing of Custom ROMs, ...)
TWRP for HTC U12+ has to be updated to decrypt the internal storage...
byinhh said:
If you want to see whether your phone is encrypted or not:
Go to Settings - Security & location - Advanced - Encryption & credentials
I think it is encrypted by default.
I have TWRP installed on my phone but without the decryption of my internal storage most functions will not be available. (No Nandroid Backups, no flashing of Custom ROMs, ...)
TWRP for HTC U12+ has to be updated to decrypt the internal storage...
Click to expand...
Click to collapse
Thanks so much for explaining that. I really appreciate it. Yes, it is encrypted. What a downer! lol. Oh well, not a big deal. I have just spent last night and tonight moving over pictures (I don't use google photos, but I will from now!) wallpaper, ringtones etc... Hopefully, I never have to 'repair' the phone by reverting to stock and losing all of these settings that I insist on having.
sonny123 said:
Thanks so much for explaining that. I really appreciate it. Yes, it is encrypted. What a downer! lol. Oh well, not a big deal. I have just spent last night and tonight moving over pictures (I don't use google photos, but I will from now!) wallpaper, ringtones etc... Hopefully, I never have to 'repair' the phone by reverting to stock and losing all of these settings that I insist on having.
Click to expand...
Click to collapse
Yeah, Nandroid would be better. I personally backup my Apps with Titanium Backup; photos, videos and music on my personal cloud; rest with Google Account.
byinhh said:
Yeah, Nandroid would be better. I personally backup my Apps with Titanium Backup; photos, videos and music on my personal cloud; rest with Google Account.
Click to expand...
Click to collapse
I will try Ti Backup this week and let you know if it worked. Cheers.
byinhh said:
I want to boot temporary to TWRP so I can flash the magisk.zip to get root. But when I boot temporary to TWRP (with fastboot) - TWRP asks for a decryption pattern. So I entered my phone pattern but TWRP says that it's wrong. Therefore I can't access my partition to flash the zip.
The bootloader is unlocked. As I can see in my settings, my phone is encrypted but I never encrypted it. I think it's per default encrypted.
Is it because TWRP support for the HTC U12+ is dead? How did you root it?
Click to expand...
Click to collapse
Do a data wipe inside twrp and reboot to fastboot and it be fine m8, I get the same error but that cures it ?
---------- Post added at 12:03 PM ---------- Previous post was at 11:59 AM ----------
shadokreeper said:
I had that error on my Pixel 2 XL when an update broke my root and I tried to reflash magisk which I believe my boot.img was already patched by magisk previously. I was stuck in a boot loop. After days of not finding a solution, I ended up flashing a stock image. I then reflashed magisk. The issue may be that the boot image is on the wrong partition or corrupted. There may be a solution but I never did find one at that time.
---------- Post added at 04:28 PM ---------- Previous post was at 04:17 PM ----------
I also wanted to add that after doing this, download the latest MagiskManager.apk from this site and install.
After installation, start the Magisk manager app and press OK on the popup to reboot the phone.
Next, just download a root checker app from the play store to check for root.
Click to expand...
Click to collapse
I used a 128gb usb c stick, don't understand why it won't mount anything bigger than 32gb Sdcard but OK with USB stick??
Everything worked fine with 2.55.401.3 on my U12+ with magisk until my phone accidentally auto-updated system to htc original image(same build). Now it works without root and when I only patch boot.img -> whatever slot_a or b - phone hangs after login.
Changing active slots doesn't change anything, and when I flash stock boot.img then system works ok again.
Patched boot.img doesn't start / unpatched boot.img works ok.
Whast's going on? Can You help me? Most stupid is that google pay stopped working saying that my phone is rooted while it isn't. LOL