Install canary then update https://github.com/topjohnwu/Magisk
Then install this patch https://drive.google.com/file/d/11KaE0arOuqL6PUfV__CL4ajmqwxv1Skk/view?usp=drivesdk
Put this in fastboot folder
Then fastboot flash boot magisk_patched.img
google pay not working
jaythenut said:
Install canary then update https://github.com/topjohnwu/Magisk
Then install this patch https://drive.google.com/file/d/11KaE0arOuqL6PUfV__CL4ajmqwxv1Skk/view?usp=drivesdk
Put this in fastboot folder
Then fastboot flash boot magisk_patched.img
google pay not working
Click to expand...
Click to collapse
I do not have the P5 yet to test root.
To get Google Pay working, you need to hide play and pay services.
Also use system less for adware. (AdAway).
Sent from my Pixel 3a XL using Tapatalk
vandyman said:
I do not have the P5 yet to test root.
To get Google Pay working, you need to hide play and pay services.
Also use system less for adware. (AdAway).
Sent from my Pixel 3a XL using Tapatalk
Click to expand...
Click to collapse
Thanks
Adaway working a treat ?
It works thanks a lot
jaythenut said:
this patch
Click to expand...
Click to collapse
Can you tell us who made that patch. It might help some decide whether to trust it on their brand spanking new $1000 toy.
jaythenut said:
google pay not working
Click to expand...
Click to collapse
If you are lucky enough that Google hasn't yet turned on hardware attestation for you yet then you can use Magiskhide to get GP working (somebody else has already mentioned what you need to hide).
When, not if, they switch you over to hardware attestation you'll have 2 choices... Live without any app that requires your device to pass SafetyNet, or get rid of Magisk and relock your bootloader. (also hope that unlocking the bootloader on the pixel 5 doesn't trip some sort of fuse which makes it impossible to take things back to a pre-unlocked state)
I'm not going to root mine and I sincerely hope that you don't regret rooting yours.
Cheers.
Sent from my Pixel 5 using XDA Labs
SteveYoungs said:
Can you tell us who made that patch. It might help some decide whether to trust it on their brand spanking new $1000 toy.
If you are lucky enough that Google hasn't yet turned on hardware attestation for you yet then you can use Magiskhide to get GP working (somebody else has already mentioned what you need to hide).
When, not if, they switch you over to hardware attestation you'll have 2 choices... Live without any app that requires your device to pass SafetyNet, or get rid of Magisk and relock your bootloader. (also hope that unlocking the bootloader on the pixel 5 doesn't trip some sort of fuse which makes it impossible to take things back to a pre-unlocked state)
I'm not going to root mine and I sincerely hope that you don't regret rooting yours.
Cheers.
Sent from my Pixel 5 using XDA Labs
Click to expand...
Click to collapse
Hi mate I made the patch easy to do ?
And thanks for the info
Pixel 5, unlocked bootloader, rooted. Banking apps (tested: Germany BW Bank app & pushTAN app, Bosnia Unicredit Bank - all in one banking + token app) WORK with root and magisk hide (SafetyNet fails due to hardware attestation). Other apps that work while rooted with magiskhide regardles of attestation: PayPal, GooglePay (*due to a current issue with PayPal im not able to enable contactless payments with GPay at the moment, awaiting PayPal support reply, however the GPay app does launch and says that "Phone meets security requirements" despite SafetyNet failure.
With Magisk HideProps Module (Force Basic Attestation -> Pixel 3a) SafetyNet passes without issues.
GooglePay enabling contactless payments requires SafetyNet to pass. I added PayPal as contactless GPay option after passing SafetyNet. After enabling it I went on and restored the original Pixel 5 Fingerprint, didn't try paying anything this way yet tho. (If it passes like this, the HideProps would be a onetime thing, provided you dont add/remove cards often).
jaythenut said:
Install canary then update https://github.com/topjohnwu/Magisk
Then install this patch https://drive.google.com/file/d/11KaE0arOuqL6PUfV__CL4ajmqwxv1Skk/view?usp=drivesdk
Put this in fastboot folder
Then fastboot flash boot magisk_patched.img
google pay not working
Click to expand...
Click to collapse
What is the patch that needs to be installed? Just rooted without it and I don't see anything in particular not working (I flashed the whole image again and used that boot image with magisk).
matssa said:
What is the patch that needs to be installed? Just rooted without it and I don't see anything in particular not working (I flashed the whole image again and used that boot image with magisk).
Click to expand...
Click to collapse
Patch is there if you don't know how to patch the boot ?
didnt work here
Hi
It didnt work on my side.
Downloaded the Factory Image (not KKDI only) and patched with Canary Magisk MAnager
If I flash the patched img with the latest platform tools it says : FAILED (remote: Failed to write to partition Not Found)
If I use the Minimal ADB package it goes through, but does not install Magisk and root ^^
What am I doing wrong?
Thanks for your help
Frost Storm said:
Hi
It didnt work on my side.
Downloaded the Factory Image (not KKDI only) and patched with Canary Magisk MAnager
If I flash the patched img with the ADB driver it says : FAILED (remote: Failed to write to partition Not Found)
If I use the Minimal ADB package it goes through, but does not install Magisk and root ^^
What am I doing wrong?
Thanks for your help
Click to expand...
Click to collapse
Use my patch in first post ?
jaythenut said:
Use my patch in first post
Click to expand...
Click to collapse
I tried.
but didnt work either
from which factory image is this patched img?
Which platform tools are u using?
Frost Storm said:
I tried.
but didnt work either
from which factory image is this patched img?
Click to expand...
Click to collapse
The latest global
jaythenut said:
The latest global
Click to expand...
Click to collapse
Nope It still says
Code:
< waiting for device >
...
OKAY [ 0.058s]
finished. total time: 0.059s
PS M:\Pixel_5\platform-tools_r30.0.4-windows\platform-tools> fastboot flash boot magisk_patched.img
target reported max download size of 268435456 bytes
sending 'boot' (98304 KB)...
OKAY [ 2.740s]
writing 'boot'...
FAILED (remote: Failed to write to partition Not Found)
finished. total time: 2.821s
Frost Storm said:
Nope It still says
Code:
< waiting for device >
...
OKAY [ 0.058s]
finished. total time: 0.059s
PS M:\Pixel_5\platform-tools_r30.0.4-windows\platform-tools> fastboot flash boot magisk_patched.img
target reported max download size of 268435456 bytes
sending 'boot' (98304 KB)...
OKAY [ 2.740s]
writing 'boot'...
FAILED (remote: Failed to write to partition Not Found)
finished. total time: 2.821s
Click to expand...
Click to collapse
Ok have you put the patch in the fastboot folder and done
Fastboot flash boot magisk_patched.img
jaythenut said:
Ok have you put the patch in the fastboot folder and done
Fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse
Correct
Before I inlocked the bootloader successfully
Frost Storm said:
Correct
Before I inlocked the bootloader successfully
Click to expand...
Click to collapse
Did you turn on usb debugging and put the phone into bootloader mode
jaythenut said:
Did you turn on usb debugging and put the phone into bootloader mode
Click to expand...
Click to collapse
Thats funny
yes, I did, although this is not mentioned in most guides
Frost Storm said:
Thats funny
yes, I did
Click to expand...
Click to collapse
Well I'm out of ideas sorry couldn't help
jaythenut said:
Well I'm out of ideas sorry couldn't help
Click to expand...
Click to collapse
Same for me
This not my first time (had Nexus 4, 5, 6P and Pixel 2 XL all with root from day one)
Related
Having been on Sprint's LG G4 (damn bootloops of death) and G5s for the past two years, I've been out of the rooting game for a while... I'm no stranger to HTC; I started with the OG EVO and went up through the M8 before jumping ship to LG.
I reeeeeaallly don't mean to sound like a noob, but I don't see any "Root" thread... I see all of the rom development, but no plain old "Do this, get root."
I searched the Q&A and News subs, and I found something that seems a little too easy... Do I seriously just unlock via HTCdev, fastboot install TWRP, and install SuperSU from recovery to have full root status?
Again, I really apologize for sounding like I just fell off a turnip truck, but the most rooting experience I've had in the past two years has been a couple of Kindle Fires, and those have admittedly been done with supertools.
I thank you in advance for any words of wisdom, and again, sorry for sounding like a boob (I swear, I searched the forum first).
scooter1979 said:
Do I seriously just unlock via HTCdev, fastboot install TWRP, and install SuperSU from recovery to have full root status?
Click to expand...
Click to collapse
Yes.
Kisakuku said:
Yes.
Click to expand...
Click to collapse
+1
But even better would be to use Magisk, without flashing TWRP but booting it after unlocking the bootloader to flash Magisk.
Sent from my HTC U11 using XDA Labs
5m4r7ph0n36uru said:
+1
But even better would be to use Magisk, without flashing TWRP but booting it after unlocking the bootloader to flash Magisk.
Click to expand...
Click to collapse
I saw this after I decided to go with Magisk instead of flashing SuperSU, but still flashed TWRP... Would going without TWRP be better just to preserve stock recovery for OTA purposes, or is there another reason why bypassing custom recovery would have been better?
scooter1979 said:
Would going without TWRP be better just to preserve stock recovery for OTA purposes, or is there another reason why bypassing custom recovery would have been better?
Click to expand...
Click to collapse
Ease of taking OTAs is the only reason. Then again, you can re-flash stock recovery (readily available for all firmware versions) in TWRP in a matter of seconds.
Kisakuku said:
you can re-flash stock recovery (readily available for all firmware versions) in TWRP in a matter of seconds.
Click to expand...
Click to collapse
I saw all of those in the collections spreadsheet, pretty awesome... It all seems a bit easier than I remember from the M8 days.
Thanks for your help.
5m4r7ph0n36uru said:
+1
But even better would be to use Magisk, without flashing TWRP but booting it after unlocking the bootloader to flash Magisk.
Sent from my HTC U11 using XDA Labs
Click to expand...
Click to collapse
you can even install Magisk now via adb w/ no root or twrp....hmmm, I wonder if unlocked bootloader is even needed...must look into
OMJ said:
you can even install Magisk now via adb w/ no root or twrp....hmmm, I wonder if unlocked bootloader is even needed...must look into
Click to expand...
Click to collapse
Read it as well in the meantime. As far as I see it is a boot.img flash. Anf as it is boot and as long as boot is signed correctly... may be worth a try without unlocking the bootloader in first place.
Sent from my HTC U11 using XDA Labs
5m4r7ph0n36uru said:
Read it as well in the meantime. As far as I see it is a boot.img flash. Anf as it is boot and as long as boot is signed correctly... may be worth a try without unlocking the bootloader in first place.
Sent from my HTC U11 using XDA Labs
Click to expand...
Click to collapse
nope, boot.img wont flash when locked
Code:
C:\sdktools\magisk>fastboot flash boot new-boot.img
target reported max download size of 1562400000 bytes
sending 'boot' (29864 KB)...
OKAY [ 2.279s]
writing 'boot'...
(bootloader) HOSD CL#-----
FAILED (remote: 9 RU_SECURITY_FAIL boot and bootloader isn't BL_UNLOCKED)
finished. total time: 3.349s
OMJ said:
nope, boot.img wont flash when locked
Click to expand...
Click to collapse
Thanks for your feedback. Tried it myself fife minutes ago. Well could have known it, as boot, recovery and system are the partitions that are unlocked for flashes when bootloader gets unlocked.
Sent from my HTC U11 using XDA Labs
complete unrooting procedure for Mi A1 [Android Oreo]
1) remove all magisk modules
I mean untick all magisk modules and click on delete icon beside them
After this reboot your device
2) then open magisk manager and uninstall using completely uninstall option
3) then power off your device
4) go to fastboot mode
( by pressing vol- + power buttons simultaneously)
5) then unlock OEM using command
fastboot oem unlock
6) then check for current slot by using below command
fastboot getvar current-slot
7) then we should flash stock boot image
Using this command
fastboot flash boot_a boot.img
( If a is current slot )
Or
fastboot flash boot_b boot.img
( if current slot is b )
Boot image file : https://drive.google.com/file/d/1EsuVTv5zIrfhDH7VG6uSyTXUWPS7Dvfl/view?usp=drivesdk
8) then lock your OEM using command
fastboot oem lock
9) then reboot using command
fastboot reboot
Congratulations your device is unrooted successfully !!
Suggested vedios for mi A1 users
Iam maintaing my channel for mi A1 related vedios and other technical stuff
Do subscribe for latest updates
Rooting using magisk :
Complete gcam setup :
#reserved
Or..
1. download fastboot ROM from Xiaomi, run flash_all_except_storage.bat (or flash it in MiFlash)
Congrats, you have stock device!
This way you are sure that you have correct boot.img corresponding to your ROM (otherwise OTA update will fail) and not some "random file from the Internet".
Thank you very much!!!! Was looking for this in a pretty long time!!!
Nope. This boot.img doesn't work for me. After completing the instructions I'm just getting the Mi logo and then restart and it goes on forever. Maybe my system.img is bad??? Can anybody give me a link to a perfect Oreo fastboot ROM, becuase I found two: the one is my current ROM and the other one's system.img "cannot be extracted".
nicolasmart said:
Nope. This boot.img doesn't work for me. After completing the instructions I'm just getting the Mi logo and then restart and it goes on forever. Maybe my system.img is bad??? Can anybody give me a link to a perfect Oreo fastboot ROM, becuase I found two: the one is my current ROM and the other one's system.img "cannot be extracted".
Click to expand...
Click to collapse
This one works for me https://forum.xda-developers.com/showpost.php?p=75027522&postcount=63
Currently I'm rooted, but I fully booted right after flashing it without any mods and ROM started fine.
It will show some sparse warning during flashing, but it will complete the process OK.
Really? Is that what you're using? That's the exact one with the system.img errors. Nah, maybe a bad download.
nicolasmart said:
Really? Is that what you're using? That's the exact one with the system.img errors. Nah, maybe a bad download.
Click to expand...
Click to collapse
Yep, working fine (well, except the video recording bug, but that is most probably Xiaomi's fault). I downloaded this file as well (https://forum.xda-developers.com/mi-a1/development/tool-aosp-8-0-ql1515-dec-8-2017-t3722184) and extracted and compared both system.img files and they are exactly the same except the very small difference - second one allows encryption as optional (modified) vs. forced (stock) in fstab. It might cause bootloop if you try to lock the bootloader with that system. Try to redownload files from Mega..
_mysiak_ said:
Yep, working fine (well, except the video recording bug, but that is most probably Xiaomi's fault). I downloaded this file as well (https://forum.xda-developers.com/mi-a1/development/tool-aosp-8-0-ql1515-dec-8-2017-t3722184) and extracted and compared both system.img files and they are exactly the same except the very small difference - second one allows encryption as optional (modified) vs. forced (stock) in fstab. It might cause bootloop if you try to lock the bootloader with that system. Try to redownload files from Mega..
Click to expand...
Click to collapse
Hmm... redownloaded from Mega, says
Code:
error: cannot load '.\system.img'
Yes, I'm sure the file is in the current folder.
I tried a different fastboot.exe and the error is more specific this time :
Code:
target reported max download size of 534773760 bytes
Invalid sparse file format at header magi
Edit: The weird thing is that all other images from this Fastboot ROM install and work just fine. I've even used the boot.img from it. It works without any problems. The system is problematic.
nicolasmart said:
Hmm... redownloaded from Mega, says
Code:
error: cannot load '.\system.img'
Yes, I'm sure the file is in the current folder.
I tried a different fastboot.exe and the error is more specific this time :
Code:
target reported max download size of 534773760 bytes
Invalid sparse file format at header magi
Edit: The weird thing is that all other images from this Fastboot ROM install and work just fine. I've even used the boot.img from it. It works without any problems. The system is problematic.
Click to expand...
Click to collapse
First fastboot.exe is probably old, second one seems to be fine. Just wait until it starts flashing system.img, it will take a minute or two and will look like frozen (fastboot has to split file into 6 smaller ones, probably has something to do with missing sparse format), be patient and don't interrupt the process.
_mysiak_ said:
First fastboot.exe is probably old, second one seems to be fine. Just wait until it starts flashing system.img, it will take a minute or two and will look like frozen (fastboot has to split file into 6 smaller ones, probably has something to do with missing sparse format), be patient and don't interrupt the process.
Click to expand...
Click to collapse
THANK YOU!!!! IT WORKED!!! I AM NOW WITH LOCKED BOOTLOADER AGAIN! :victory: :victory: :victory:
nicolasmart said:
THANK YOU!!!! IT WORKED!!! I AM NOW WITH LOCKED BOOTLOADER AGAIN! :victory: :victory: :victory:
Click to expand...
Click to collapse
You saved me too.
presented error in the "no command" and did not accept the January update
Thank it worked for me!
After this unroot method i could install the january ota.
Then I used this https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654 method to root again
_mysiak_ said:
Or..
1. download fastboot ROM from Xiaomi, run flash_all_except_storage.bat (or flash it in MiFlash)
Congrats, you have stock device!
This way you are sure that you have correct boot.img corresponding to your ROM (otherwise OTA update will fail) and not some "random file from the Internet".
Click to expand...
Click to collapse
No need to uninstall modules and magisk
Just download & flash stock rom is enough to return to stock unrooted rom.
Is this you saying?
rkview37 said:
No need to uninstall modules and magisk
Just download & flash stock rom is enough to return to stock unrooted rom.
Is this you saying?
Click to expand...
Click to collapse
If you want to return to stock ROM and never use Magisk again, then you might want to uninstall Magisk first. But if you are only unrooting to apply OTA for example, it is enough to flash stock ROM and then reinstall Magisk - all your modules and settings will be kept.
_mysiak_ said:
If you want to return to stock ROM and never use Magisk again, then you might want to uninstall Magisk first. But if you are only unrooting to apply OTA for example, it is enough to flash stock ROM and then reinstall Magisk - all your modules and settings will be kept.
Click to expand...
Click to collapse
Actually sir
I have flashed patched boot image not just just boot
is your method work then
&Of course I just unroot to apply ota
rkview37 said:
Actually sir
I have flashed patched boot image not just just boot
is your method work then
&Of course I just unroot to apply ota
Click to expand...
Click to collapse
For OTA update, just reflash the latest stock ROM (keep data), apply OTA and root with Magisk again.
camerlengo said:
Thank it worked for me!
After this unroot method i could install the january ota.
Then I used this https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654 method to root again
Click to expand...
Click to collapse
Ok bro
_mysiak_ said:
Or..
1. download fastboot ROM from Xiaomi, run flash_all_except_storage.bat (or flash it in MiFlash)
Congrats, you have stock device!
This way you are sure that you have correct boot.img corresponding to your ROM (otherwise OTA update will fail) and not some "random file from the Internet".
Click to expand...
Click to collapse
Can u link me to the latest fastboot rom? , The link in the thread on the mi forums is too old I guess
AlwaysWin said:
Can u link me to the latest fastboot rom? , The link in the thread on the mi forums is too old I guess
Click to expand...
Click to collapse
http://ru.miui.com/thread-1308-1-1.html
This website is in Russian but download from this site
Rom is Oreo Jan official rom flash it using mi flash tool
Experimental twrp for moto one vision (need tester)
Requirements: Bootloader Unlocked
Before installing, test using "fastboot boot TWRP_Kane.img"
link: https://drive.google.com/file/d/1vhNiSuvB99j69wjNXoJn4dycpjUtKkTI/view?usp=drivesdk
I can test it this weekend
I wish I could try it right away, but I'm away from home over the weekend and I left my one vision at home.
can do, sir
---------- Post added at 01:02 PM ---------- Previous post was at 12:52 PM ----------
"Validation image failed"
Booting via fastboot failed.
I'm new to this, contact me any time if you need more info.
Alisson1397 said:
Experimental twrp for moto one vision (need tester)
Requirements: Bootloader Unlocked
Before installing, test using "fastboot boot TWRP_Kane.img"
link: https://drive.google.com/file/d/1vhNiSuvB99j69wjNXoJn4dycpjUtKkTI/view?usp=drivesdk
Click to expand...
Click to collapse
I tried it but I'm getting this error:
Sending 'boot.img' (36236 KB) OKAY [ 1.170s]
Booting FAILED (remote: '')
fastboot: error: Command failed
On bootloader screen it says "Validation image failed"
On adb screen says :
C:\Users\dml02\Downloads>fastboot boot TWRP_Kane.img
downloading 'boot.img'...
OKAY [ 0.825s]
booting...
FAILED (remote failure)
finished. total time: 0.991s
"Validation image failed" on my device.
If anyone knows how to fix the error, please help!
Alisson1397 said:
If anyone knows how to fix the error, please help!
Click to expand...
Click to collapse
sorry to ask mate. Are you the dev of this twrp image?
AndresOrue said:
sorry to ask mate. Are you the dev of this twrp image?
Click to expand...
Click to collapse
Yes, I compiled it, but found a device tree ready for twrp
I made a device tree for this device, successful kernel and twrp compilation, but still the same error as above.
Guys, is it worth the wait for working twrp for motorola one vision?
Tuldon said:
Guys, is it worth the wait for working twrp for motorola one vision?
Click to expand...
Click to collapse
I was near to buy one for developments, I didn't due to his price now is 274 euro was 240 but I arrived too late, it's too high for android one phone :/ .
Tuldon said:
Guys, is it worth the wait for working twrp for motorola one vision?
Click to expand...
Click to collapse
haky 86 said:
I was near to buy one for developments, I didn't due to his price now is 274 euro was 240 but I arrived too late, it's too high for android one phone :/ .
Click to expand...
Click to collapse
Yep, this phone is too expensive and a waste of time. I regret I bought it
I'm in the same situation with my Motorola One Action. I'm looking in both forums because they're almost the same phone (same SoC, different camera config and codename; Vision is Kane and Action is Troika).
I managed to get the stock firmware for my One Action XT2013-1, grabbed the boot.img, patched on Magisk, unlocked the Bootloader and tried to boot the patched image with the same error described in this post "Validation image failed" on device and "Failed" on fastboot.exe.
We need to bypass that validation so we can boot unsigned images on our phones. Sadly, I'm not a developer but will happily test any advance on my device.
Greetings.
From what I know "Validation image failed" error comes up if you haven't unlocked the bootloader or if the firmware you're trying to flash is older than your current firmware.
Did you enabled the "OEM unlocking" toggle from the developer settings? This might block the twrp installation.
@Alisson1397 also are you sure that the source code you're using for this twrp is for our particular device?
SnoopDoggyStyleDogg said:
From what I know "Validation image failed" error comes up if you haven't unlocked the bootloader or if the firmware you're trying to flash is older than your current firmware.
Did you enabled the "OEM unlocking" toggle from the developer settings? This might block the twrp installation.
@Alisson1397 also are you sure that the source code you're using for this twrp is for our particular device?
Click to expand...
Click to collapse
Use this device tree to compile TWRP
https://github.com/AlissonGrizotti/TWRP-device_motorola_kane
Maybe I'm using an outdated boot.img, but I find it unlikely
Hello, today i've successfully rooted my Pixel 3 with magisk and everything seems to be working fine except, i cant install TWRP.
i get the following upon doing fastboot boot twrp.img
Sending 'boot.img' (65536 KB) OKAY [ 2.169s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
i've tried mulitple USB A to USB C cables, and even usb-c to usb-c because my laptop has that port. Someone Please help
AmberKat said:
Hello, today i've successfully rooted my Pixel 3 with magisk and everything seems to be working fine except, i cant install TWRP.
i get the following upon doing fastboot boot twrp.img
Sending 'boot.img' (65536 KB) OKAY [ 2.169s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
i've tried mulitple USB A to USB C cables, and even usb-c to usb-c because my laptop has that port. Someone Please help
Click to expand...
Click to collapse
If you're on Android 10, twrp doesn't work. You really don't need it now anyway.
jd1639 said:
If you're on Android 10, twrp doesn't work. You really don't need it now anyway.
Click to expand...
Click to collapse
So downgrading back to Pie will solve the issue?
AmberKat said:
So downgrading back to Pie will solve the issue?
Click to expand...
Click to collapse
If you're adamant about having twrp, yes.
Xdevillived666 said:
If you're adamant about having twrp, yes.
Click to expand...
Click to collapse
I have the same issue, how can i flash a custom kernel and magisk without twrp in Android 10 please?
luizffgarcia said:
I have the same issue, how can i flash a custom kernel and magisk without twrp in Android 10 please?
Click to expand...
Click to collapse
For a custom kernel, you will need to use a kernel manager (EX kernel manager or FK kernel manager). Both are a small amount of money that is of course well worth it to support the devs. As for Magisk, you need to install the Magisk Manager canary APK and then patch boot to root.
sliding_billy said:
For a custom kernel, you will need to use a kernel manager (EX kernel manager or FK kernel manager). Both are a small amount of money that is of course well worth it to support the devs. As for Magisk, you need to install the Magisk Manager canary APK and then patch boot to root.
Click to expand...
Click to collapse
Thanks, i already have EX manager, and i have just rooted with canary. Cheer
luizffgarcia said:
Thanks, i already have EX manager, and i have just rooted with canary. Cheer
Click to expand...
Click to collapse
Easy peasy!
jd1639 said:
If you're on Android 10, twrp doesn't work. You really don't need it now anyway.
Click to expand...
Click to collapse
Why is TWRP not needed in Android 10? I have the same issue as the OP with fastboot boot hanging at sending boot.img, but a different reason for wanting TWRP to boot, namely to make a nandroid backup. I do not want to flash twrp, just boot as I have done for years pre OS10. I have no interest in backing up on Google servers, just wish to do a nandroid. Is there some other way to do this in OS10 without root?
Thanks, John
John Markley said:
Why is TWRP not needed in Android 10? I have the same issue as the OP with fastboot boot hanging at sending boot.img, but a different reason for wanting TWRP to boot, namely to make a nandroid backup. I do not want to flash twrp, just boot as I have done for years pre OS10. I have no interest in backing up on Google servers, just wish to do a nandroid. Is there some other way to do this in OS10 without root?
Thanks, John
Click to expand...
Click to collapse
Android 10's file structure is different so you won't be able to boot or flash twrp. Teamwin may figure out how to get twrp to work on it someday but for now it doesn't. So no nandriod, you'll need to find another way to backup if that's what you're looking to do.
jd1639 said:
Android 10's file structure is different so you won't be able to boot or flash twrp. Teamwin may figure out how to get twrp to work on it someday but for now it doesn't. So no nandriod, you'll need to find another way to backup if that's what you're looking to do.
Click to expand...
Click to collapse
Thank you. I'll just do adb backups then, unless Teamwin solves it. Until now I've always done both adb and nandroid.
I am currently on Android 9 and going to upgrade to the latest 10.
Is there anything chance for me to do a full image backup of the phone in advance before upgrading.
In case that the Android 10 doesn't fit me very well, I can roll back to Android 9 without losing any files.
Appreciate your comments and thank you in advance for the assistance.
jd1639 said:
Android 10's file structure is different so you won't be able to boot or flash twrp. Teamwin may figure out how to get twrp to work on it someday but for now it doesn't. So no nandriod, you'll need to find another way to backup if that's what you're looking to do.
Click to expand...
Click to collapse
Hey,
I screwed up when patching the boot image for magisk on the latest stock rom update. I've attempted to reinstall the factory image but experience two different errors depending on which version of platform tools im using:
When I use 33.0.3 i get this error: fastboot: error: device requires partition vendor kernel boot which is not known to this version of fastboot
When i use 34.0.1 i get this error: Sending sparse 'super' 1/1 (4194303 KB) FAILED (Sparse file is too large or invalid)
I'm at a loss on how to correct the problem at this point. I've tried Pixelflasher but that fails also (I'm assuming from the same errors).
Any help is greatly appreciated as I'm without a phone until I fix this
Thanks in advance!!!!!
stslimited84 said:
Hey,
I screwed up when patching the boot image for magisk on the latest stock rom update. I've attempted to reinstall the factory image but experience two different errors depending on which version of platform tools im using:
When I use 33.0.3 i get this error: fastboot: error: device requires partition vendor kernel boot which is not known to this version of fastboot
When i use 34.0.1 i get this error: Sending sparse 'super' 1/1 (4194303 KB) FAILED (Sparse file is too large or invalid)
I'm at a loss on how to correct the problem at this point. I've tried Pixelflash but that fails also (I'm assuming from the same errors).
Any help is greatly appreciated as I'm without a phone until I fix this
Thanks in advance!!!!!
Click to expand...
Click to collapse
I would suggest using PixelFlasher (from this sub-forum) with 33.0.3, you should be able to revive your phone.
stslimited84 said:
Hey,
I screwed up when patching the boot image for magisk on the latest stock rom update. I've attempted to reinstall the factory image but experience two different errors depending on which version of platform tools im using:
When I use 33.0.3 i get this error: fastboot: error: device requires partition vendor kernel boot which is not known to this version of fastboot
When i use 34.0.1 i get this error: Sending sparse 'super' 1/1 (4194303 KB) FAILED (Sparse file is too large or invalid)
I'm at a loss on how to correct the problem at this point. I've tried Pixelflash but that fails also (I'm assuming from the same errors).
Any help is greatly appreciated as I'm without a phone until I fix this
Thanks in advance!!!!!
Click to expand...
Click to collapse
I would go with Pixel Flasher. pretty simple program with a lot of options. Patching Magisk and a few clicks to install firmware.
Fishawy said:
I would suggest using PixelFlasher (from this sub-forum) with 33.0.3, you should be able to revive your phone.
Click to expand...
Click to collapse
Thanks for the response.
As i mentioned in the OP, I tried pixelflasher and it does not work. I believe its experiencing the same issues since its just UI executing the commands essentially.
schmeggy929 said:
I would go with Pixel Flasher. pretty simple program with a lot of options. Patching Magisk and a few clicks to install firmware.
Click to expand...
Click to collapse
I tried pixel flasher with no success
stslimited84 said:
I tried pixel flasher with no success
Click to expand...
Click to collapse
Where are you getting your platform tools? Please tell me it's not a minimal adb thing and/or not from the android developers site...?
simplepinoi177 said:
Where are you getting your platform tools? Please tell me it's not a minimal adb thing and/or not from the android developers site...?
Click to expand...
Click to collapse
using the standard kit from https://developer.android.com/tools/releases/platform-tools
stslimited84 said:
using the standard kit from https://developer.android.com/tools/releases/platform-tools
Click to expand...
Click to collapse
weirdly enough, I've seen "sparse" or "partition" errors happen to members who ended up getting it working by changing the USB cord!
I might re-download platform tools (r33.0.3 of course), place it in a different location, and try there again. And/or re-download the factory firmware image but make sure to compare the checksums and make sure you're not trying to flash corrupted images...
*don't forget to remove the "-w" or your device will be wiped...
stslimited84 said:
Hey,
I screwed up when patching the boot image for magisk on the latest stock rom update. I've attempted to reinstall the factory image but experience two different errors depending on which version of platform tools im using:
When I use 33.0.3 i get this error: fastboot: error: device requires partition vendor kernel boot which is not known to this version of fastboot
When i use 34.0.1 i get this error: Sending sparse 'super' 1/1 (4194303 KB) FAILED (Sparse file is too large or invalid)
I'm at a loss on how to correct the problem at this point. I've tried Pixelflasher but that fails also (I'm assuming from the same errors).
Any help is greatly appreciated as I'm without a phone until I fix this
Thanks in advance!!!!!
Click to expand...
Click to collapse
Go over to the Pixel Flasher thread and submit a support.zip. Maybe badabing can help diagnose.
simplepinoi177 said:
weirdly enough, I've seen "sparse" or "partition" errors happen to members who ended up getting it working by changing the USB cord!
I might re-download platform tools (r33.0.3 of course), place it in a different location, and try there again. And/or re-download the factory firmware image but make sure to compare the checksums and make sure you're not trying to flash corrupted images...
*don't forget to remove the "-w" or your device will be wiped...
Click to expand...
Click to collapse
I've downloaded both several times but ill try a new location. At this point, I dont care if the device is wiped, I just need it working. i can restore the apps from backups.
I was able to fix it by using the android flash tool in chrome. It was the only thing that would overcome the errors. Phone is up and running again.
stslimited84 said:
I was able to fix it by using the android flash tool in chrome. It was the only thing that would overcome the errors. Phone is up and running again.
Click to expand...
Click to collapse
Glad you got it sorted.
stslimited84 said:
I was able to fix it by using the android flash tool in chrome. It was the only thing that would overcome the errors. Phone is up and running again.
Click to expand...
Click to collapse
that's always a good option to think on...I was gonna suggest it after checking on USB cord issues...glad you got it fixed...
Glad for your!
Is it the tool at https://flash.android.com/ ?
Did you patch boot.img and flash that?
As init_boot.img needs to be patched in Magisk and installed, for Pixel 7 series.
krakout said:
Glad for your!
Is it the tool at https://flash.android.com/ ?
Click to expand...
Click to collapse
Yep. I tried using the beta build first without success. Then I used the latest public build and it worked
I had something similar happen when flashing the latest QPR beta last week. I fixed it by sideloading the ota.zip instead, then booting to bootloader to flash the patched image after.