I was on February stock image with twrp and magisk and elemental X kernal installed prior and had everything functioning properly since the febuary update but just installed flux theme within substratum and when i applied overlay my screen went black with only status bar icons showing ...so i rebooted phone and for some reason it boots and hangs on the google loading page then boots to twrp ...unfortunatly i had password/fingerprint lock on so twrp wont decrypt , i tried using adb/fastboot to try and do a flash all bat but fastboot message says fastboot is not recongnized as an internal or external command , operable program or batch file ... i have the -w removed from the flash all bat , i'm wondering if it wont flash because adb setting isn't on in developer settings..... dont know what to do or how to fix :crying:
If anyone could help or offer advice it would be greatly appreciated
Mr. Blanco said:
I was on February stock image with twrp and magisk and elemental X kernal installed prior and had everything functioning properly since the febuary update but just installed flux theme within substratum and when i applied overlay my screen went black with only status bar icons showing ...so i rebooted phone and for some reason it boots and hangs on the google loading page then boots to twrp ...unfortunatly i had password/fingerprint lock on so twrp wont decrypt , i tried using adb/fastboot to try and do a flash all bat but fastboot message says fastboot is not recongnized as an internal or external command , operable program or batch file ... i have the -w removed from the flash all bat , i'm wondering if it wont flash because adb setting isn't on in developer settings..... dont know what to do or how to fix :crying:
If anyone could help or offer advice it would be greatly appreciated
Click to expand...
Click to collapse
Your likely going to have to do a clean flash of the factory image, and wipe it clean since you can't get into twrp to restore your backup. However, it also sounds like your device is not being recognized by adb/fastboot. When your in fastboot mode, and type fastboot devices, do you get your phone ID displayed?? Also, are your SDK/platform-tools up to date??
Badger50 said:
Your likely going to have to do a clean flash of the factory image, and wipe it clean since you can't get into twrp to restore your backup. However, it also sounds like your device is not being recognized by adb/fastboot. When your in fastboot mode, and type fastboot devices, do you get your phone ID displayed?? Also, are your SDK/platform-tools up to date??
Click to expand...
Click to collapse
I'm using sdk platform tools dec, 27.0.1 so i believe it is the most up to date version and when i fastboot devices i do get a serial number - fastboot showing , which is what kind of confused me , did the flash all bat and got that message as i posted before and the only thing i have changed in it was removing the -w ... so kind of scratching my head here why it's not working ... do you have any ideas what i might be able to do to fix
Mr. Blanco said:
I'm using sdk platform tools dec, 27.0.1 so i believe it is the most up to date version and when i fastboot devices i do get a serial number - fastboot showing , which is what kind of confused me , did the flash all bat and got that message as i posted before and the only thing i have changed in it was removing the -w ... so kind of scratching my head here why it's not working ... do you have any ideas what i might be able to do to fix
Click to expand...
Click to collapse
Are you typing the command, or double clicking the script??
Your definitely up to date on SDK BTW ?
Badger50 said:
Your likely going to have to do a clean flash of the factory image, and wipe it clean since you can't get into twrp to restore your backup. However, it also sounds like your device is not being recognized by adb/fastboot. When your in fastboot mode, and type fastboot devices, do you get your phone ID displayed?? Also, are your SDK/platform-tools up to date??
Click to expand...
Click to collapse
i'm really embarrassed ... i was using the flash all bat from with in the factory image and not the platform tools file .. i sincerely apologize for posting this thread , this was definitely a user error ....is there a way to delete this embarrassing thread ...lol
Mr. Blanco said:
i'm really embarrassed ... i was using the flash all bat from with in the factory image and not the platform tools file .. i sincerely apologize for posting this thread , this was definitely a user error ....is there a way to delete this embarrassing thread ...lol
Click to expand...
Click to collapse
Dude, there's nothing to be embarrassed about, most of us have been there, no big deal. However, I still don't think dirty flashing the factory image is going to fix it, hopefully it does, but essentially your not removing the files that's causing the ui to fail. But we shall see.
Badger50 said:
Dude, there's nothing to be embarrassed about, most of us have been there, no big deal. However, I still don't think dirty flashing the factory image is going to fix it, hopefully it does, but essentially your not removing the files that's causing the ui to fail. But we shall see.
Click to expand...
Click to collapse
well phone is back up and running completely stock now just about to flash twrp, and the flash kernal and magisk ...still not sure what caused this whole thing as i only installed flux substratum theme , phone was fine and fully functioning since last update ... and by the way thank you for reaching out to help me , i really appreciate it ....one thing that was strange though was when process what finished flashing , i got the corrupt device message warning before booting in to the os but everything seems fine so far
Mr. Blanco said:
well phone is back up and running completely stock now just about to flash twrp, and the flash kernal and magisk ...still not sure what caused this whole thing as i only installed flux substratum theme , phone was fine and fully functioning since last update ... and by the way thank you for reaching out to help me , i really appreciate it ....one thing that was strange though was when process what finished flashing , i got the corrupt device message warning before booting in to the os but everything seems fine so far
Click to expand...
Click to collapse
Glad your back up and running. Little FYI for you. Theme overlays can shut you down very quickly, as you now know. When twrp is working correctly, it's not as big deal, since you just go into twrp and flash the substratum rescue zip and all is well. So, going forward, if you want to theme, keep your lock screen security set to swipe or none until you are finished themeing. There is an adb way to push twrp to temporary cache so that you can use it. Here is the link if you want to learn how to do it ??
https://forum.xda-developers.com/pi...aimen-flash-kernel-1-00-t3702057/post75495348
Badger50 said:
Glad your back up and running. Little FYI for you. Theme overlays can shut you down very quickly, as you now know. When twrp is working correctly, it's not as big deal, since you just go into twrp and flash the substratum rescue zip and all is well. So, going forward, if you want to theme, keep your lock screen security set to swipe or none until you are finished themeing. There is an adb way to push twrp to temporary cache so that you can use it. Here is the link if you want to learn how to do it
https://forum.xda-developers.com/pi...aimen-flash-kernel-1-00-t3702057/post75495348
Click to expand...
Click to collapse
Yes i will using your advice when attempting to theme or make any other adjustments from now on ...just found out i removed the -w from the factory image and not the one in the platforms tools so once again i have lost all saved data and starting from scratch..... grrrrrrr .... lol and thank you for the link ! i'm figuring since i'm starting from scratch that maybe i could check out the DU rom that's out right now , just wondering if you have flashed and if so how do you like it so far
Mr. Blanco said:
Yes i will using your advice when attempting to theme or make any other adjustments from now on ...just found out i removed the -w from the factory image and not the one in the platforms tools so once again i have lost all saved data and starting from scratch..... grrrrrrr .... lol and thank you for the link ! i'm figuring since i'm starting from scratch that maybe i could check out the DU rom that's out right now , just wondering if you have flashed and if so how do you like it so far
Click to expand...
Click to collapse
Oh yeah! I'm running it, and it's really solid! Bout the only thing not working is the squeeze thingy, which I never use anyway, and some issues with wifi calling. Other than that, it's great! ??
Badger50 said:
Oh yeah! I'm running it, and it's really solid! Bout the only thing not working is the squeeze thingy, which I never use anyway, and some issues with wifi calling. Other than that, it's great!
Click to expand...
Click to collapse
That's awesome, glad to hear to that , and i can live with out squeeze and wifi calling i'm just about to give it a shot right now , wish me luck ..lol read your post on your/bajasur install instructions if it worked for you guys i'm hoping it will work for me ...... just to double check with you since you were able to get it up and running , is this the process ......
1. Be on February Security
2. Disable Security Pin in settings
3. Reboot to TWRP (Make backup if needed)
4. Factory Data Reset
5. Flash DU
6. Flash TWRP
7. Reboot ROM and set up without security
8. Reboot back to TWRP and flash latest Magisk
9. Reboot back to ROM and set up security
10. Done!
Mr. Blanco said:
That's awesome, glad to hear to that , and i can live with out squeeze and wifi calling i'm just about to give it a shot right now , wish me luck ..lol read your post on your/bajasur install instructions if it worked for you guys i'm hoping it will work for me ...... just to double check with you since you were able to get it up and running , is this the process ......
1. Be on February Security
2. Disable Security Pin in settings
3. Reboot to TWRP (Make backup if needed)
4. Factory Data Reset
5. Flash DU
6. Flash TWRP
7. Reboot ROM and set up without security
8. Reboot back to TWRP and flash latest Magisk
9. Reboot back to ROM and set up security
10. Done!
Click to expand...
Click to collapse
Yep, you got it. Justd don't wipe system in twrp! ?
Badger50 said:
Yep, you got it. Justd don't wipe system in twrp!
Click to expand...
Click to collapse
just booted into twrp and don't have touch functions , as i'm completly stock now , should i flash the flash kernal to get touch functions in twrp and then follow that process
Mr. Blanco said:
just booted into twrp and don't have touch functions , as i'm completly stock now , should i flash the flash kernal to get touch functions in twrp and then follow that process
Click to expand...
Click to collapse
Did you disable lock screen security first? Kinda hard to flash a kernel if you don't have touch functions. Unless you adb push it.
Badger50 said:
Did you disable lock screen security first? Kinda hard to flash a kernel if you don't have touch functions. Unless you adb push it.
Click to expand...
Click to collapse
Yes i disabled all security features ... lock screen / finger print but thinking i should have fastbooted twrp img and from with in the twrp img i should have flashed the Du rom zip and then the twrp zip ... is there a way to do the install with out touch functions like adb push ? never pushed anything to my device before and now wondering do i need to flash stock feb image again and then do the fastboot twrp img and from there flash the DU zip and then the permanent twrp zip ?
Mr. Blanco said:
Yes i disabled all security features ... lock screen / finger print but thinking i should have fastbooted twrp img and from with in the twrp img i should have flashed the Du rom zip and then the twrp zip ... is there a way to do the install with out touch functions like adb push ? never pushed anything to my device before and now wondering do i need to flash stock feb image again and then do the fastboot twrp img and from there flash the DU zip and then the permanent twrp zip ?
Click to expand...
Click to collapse
Try fastbooting the twrp.img first and see if you get it working fist :good:
Badger50 said:
Try fastbooting the twrp.img first and see if you get it working fist :good:
Click to expand...
Click to collapse
Boom shaka laka ...... i got it up and running i fastbooted the stock boot.img and the did the twrp.img thing and flashed the rom and twrp and everything is up and running now, so glad it all worked out and , going to attemp to flash magisk now ... do you know if the latest magisk works 15.4 or should i stick with 15.3 ? and by the way thank you for helping with this whole process , i'm really grateful , big time props to you for all your help !!!!
Mr. Blanco said:
Boom shaka laka ...... i got it up and running i fastbooted the stock boot.img and the did the twrp.img thing and flashed the rom and twrp and everything is up and running now, so glad it all worked out and , going to attemp to flash magisk now ... do you know if the latest magisk works 15.4 or should i stick with 15.3 ? and by the way thank you for helping with this whole process , i'm really grateful , big time props to you for all your help !!!!
Click to expand...
Click to collapse
Saaweeeeeeeeeeet! Good job man :good: Magisk 15.4 is working fine for me. And, your very welcome ??
Badger50 said:
Saaweeeeeeeeeeet! Good job man :good: Magisk 15.4 is working fine for me. And, your very welcome [/Q
i have a question , i got a message about a vendor image on my fist boot up , was just wondering if you did too and if thats just part of the package deal when using this rom
Click to expand...
Click to collapse
Mr. Blanco said:
Badger50 said:
Saaweeeeeeeeeeet! Good job man :good: Magisk 15.4 is working fine for me. And, your very welcome [/Q
i have a question , i got a message about a vendor image on my fist boot up , was just wondering if you did too and if thats just part of the package deal when using this rom
Click to expand...
Click to collapse
Some have reported the same on other AOSP roms. A possible fix, though not always successful, is to fastboot the vendor.img to both slots. The message is harmless, and won't cause any damage to your OS. It's just annoying at boot up is all ?
Click to expand...
Click to collapse
Related
Hi all,
*I've unlocked bootloader
* Have tried fastboot boot TWRP.img, as well as tried flashing TWRP RC1 via the Skipsoft toolkit.
Every way I've tried the phone just sits at the TWRP boot screen and doesn't allow me to go any further..
Any help here would be truly appreciated!
Cheers,
I've been having the same issue tonight. Re-flash the stock image, go through the whole setup process and make sure you add a lockscreen pin, then flash TWRP. That is what worked for me. I still can't flash a Rom though for some reason. It's driving me insane.
dutchy716 said:
I've been having the same issue tonight. Re-flash the stock image, go through the whole setup process and make sure you add a lockscreen pin, then flash TWRP. That is what worked for me. I still can't flash a Rom though for some reason. It's driving me insane.
Click to expand...
Click to collapse
You're braver than me. I haven't had my Pixel XL long but this is the first phone I've ever owned where I am afraid to try and install a custom recovery and ROM. With the dual partitions and what I hear about TWRP still being buggy it just seems like Google didn't want people to run anything but pure Android on the Pixels.
dutchy716 said:
I've been having the same issue tonight. Re-flash the stock image, go through the whole setup process and make sure you add a lockscreen pin, then flash TWRP. That is what worked for me. I still can't flash a Rom though for some reason. It's driving me insane.
Click to expand...
Click to collapse
Same issue here, but no solution. Adding a lockscreen pin didn't change anything for me. I just get a teamwin image but it just sits there & doesn't actually open TWRP. My bootlocker is unlocked but thats as far as I can get 7.1.2 with May security. I have tried reloading everything and followed commonly recommended steps.
Any suggestions greatly appreciated. I would love to get this thing rooted and get some ROM flexibility - even to just get rid of the Nav Bar ....
mikefnz said:
Same issue here, but no solution. Adding a lockscreen pin didn't change anything for me. I just get a teamwin image but it just sits there & doesn't actually open TWRP. My bootlocker is unlocked but thats as far as I can get 7.1.2 with May security. I have tried reloading everything and followed commonly recommended steps.
Any suggestions greatly appreciated. I would love to get this thing rooted and get some ROM flexibility - even to just get rid of the Nav Bar ....
Click to expand...
Click to collapse
I have never had a problem. Make sure your using the rc1 fast boot TWRP. Should be fastboot boot twrp.img. I change file name to this or copy and paste. Then you install rc1 or rc2 zip.
I know you will have problems if you try to install the wrong file.
mac796 said:
I have never had a problem. Make sure your using the rc1 fast boot TWRP. Should be fastboot boot twrp.img. I change file name to this or copy and paste. Then you install rc1 or rc2 zip.
I know you will have problems if you try to install the wrong file.
Click to expand...
Click to collapse
I am doing exactly as you mentioned.. flash rc1.img, however the phone does not go beyond the boot screen, it just sits there.... Can I ask what steps you are taking prior to flashing twrp? Thanks!
mazubo said:
I am doing exactly as you mentioned.. flash rc1.img, however the phone does not go beyond the boot screen, it just sits there.... Can I ask what steps you are taking prior to flashing twrp? Thanks!
Click to expand...
Click to collapse
Hmm are you on may bootloader because i think modifying the boot partition causes bootloop without the boot signature?
XtraArrow said:
Hmm are you on may bootloader because i think modifying the boot partition causes bootloop without the boot signature?
Click to expand...
Click to collapse
Yes I am.. should I downgrade to 7.1.1? Tjere was no mention of that issue in the skipsoft toolkit thread... Weird!
mazubo said:
Yes I am.. should I downgrade to 7.1.1? Tjere was no mention of that issue in the skipsoft toolkit thread... Weird!
Click to expand...
Click to collapse
Sure, i guess.. or you could just manually flash the April bootloader. a lot easier.
XtraArrow said:
Sure, i guess.. or you could just manually flash the April bootloader. a lot easier.
Click to expand...
Click to collapse
Ok, would flashing just the bootloader wipe the phone? Also how would I find just the bootloader? Thanks for the suggestion, I haven't flashed just a bootloader before..
mazubo said:
I am doing exactly as you mentioned.. flash rc1.img, however the phone does not go beyond the boot screen, it just sits there.... Can I ask what steps you are taking prior to flashing twrp? Thanks!
Click to expand...
Click to collapse
That strange. I just flash a factory image from Google
Set up a security pattern
Enable adb debugging
Fastboot boot twrp 3.0.2-0 rc1 IMG
Make sure it asks for your security pattern if it doesn't reboot to bootloader and fastboot twrp again, and keep repeating until it does
Install twrp 3.1.0.0 rc2 or rc1 zip
If your using may bootloader's fish VBS 6 zip
And it should stick, if you flash. Anything else that messes with boot flash that VBS zip at the end again
mazubo said:
Ok, would flashing just the bootloader wipe the phone? Also how would I find just the bootloader? Thanks for the suggestion, I haven't flashed just a bootloader before..
Click to expand...
Click to collapse
If you download the offiial april firmware, you can manually extract it from the .zip then you would do this command in fastboot :--------- fastboot flash bootloader PUTFILEHERE.img
EDIT: Are you able to get into TWRP by any chance??
mac796 said:
That strange. I just flash a factory image from Google
Set up a security pattern
Enable adb debugging
Fastboot boot twrp 3.0.2-0 rc1 IMG
Make sure it asks for your security pattern if it doesn't reboot to bootloader and fastboot twrp again, and keep repeating until it does
Install twrp 3.1.0.0 rc2 or rc1
If your using may bootloader's fish VBS 6 zip
And it should stick, if you flash. Anything else that messes with boot flash that VBS zip at the end again
Click to expand...
Click to collapse
Hmm, maybe this is where I've gone wrong.. I thought the need to create a security pin/pattern was only if coming from a previously rooted state, or from a custom ROM. I will try this as well and report back.. thanks!
XtraArrow said:
If you download the offiial april firmware, you can manually extract it from the .zip then you would do this command in fastboot :--------- fastboot flash bootloader PUTFILEHERE.img
EDIT: Are you able to get into TWRP by any chance??
Click to expand...
Click to collapse
Unable to get into twrp as previously mentioned. I flash the IMG file, then it just hangs on the TWRP boot screen..
mazubo said:
Unable to get into twrp as previously mentioned. I flash the IMG file, then it just hangs on the TWRP boot screen..
Click to expand...
Click to collapse
Alright, try doing what I mentioned. Download April firmware, extract the bootloader.img from it and flash using command above.
XtraArrow said:
Alright, try doing what I mentioned. Download April firmware, extract the bootloader.img from it and flash using command above.
Click to expand...
Click to collapse
This seems likely to work. Thanks for the suggestions, and I'll report back! Cheers!
mazubo said:
This seems likely to work. Thanks for the suggestions, and I'll report back! Cheers!
Click to expand...
Click to collapse
I'm no expert but it's seems like a decent suggestion. Let us know how it goes.
@mazubo
You keep stating that you just flash the image. Are you flashing it from the bootloader then trying to boot to recovery?
You have to boot TWRP from your PC first. Then from TWRP you can then "flash" TWRP.
Just wanted to make sure that was a step you were taking!
Just wait. It will take little longer
Sent from my Pixel XL using Tapatalk
freddy0872 said:
@mazubo
You keep stating that you just flash the image. Are you flashing it from the bootloader then trying to boot to recovery?
You have to boot TWRP from your PC first. Then from TWRP you can then "flash" TWRP.
Just wanted to make sure that was a step you were taking!
Click to expand...
Click to collapse
Yes, I have tried fastboot to flash the TWRP img, as well as skipsofts toolkit. I guess I've been using the term "flash" for fastboot, as I haven't been able to use twrp yet.. I understand that you need to flash the TWRP img via pc and then flash the TWRP zip, then SuperSU or magisk, whatever your poison may be !
Hello
Can some send me a TWRP backup of their Mate SE? I only need the boot image. Please just the boot partition. I don't have a good internet where I am at right now and I bricked. Thanks!
Sandman-007 said:
Hello
Can some send me a TWRP backup of their Mate SE? I only need the boot image. Please just the boot partition. I don't have a good internet where I am at right now and I bricked. Thanks!
Click to expand...
Click to collapse
Unlocked for a whole , what, 3 hours , and you brick already.
Sorry had to do that.
I don't have mate , but 7x the roms are supposedly basically the same. At least the 7x custom roms work on se.
I have boot image uploaded , along with the the rest of the partitions , as separate files. On Android file host. You can. Try to use that.
As far as mate back up I have found one, but it is whole backup.
https://androidfilehost.com/?w=files&flid=261152
mrmazak said:
Unlocked for a whole , what, 3 hours , and you brick already.
Sorry had to do that.
I don't have mate , but 7x the roms are supposedly basically the same. At least the 7x custom roms work on se.
I have boot image uploaded , along with the the rest of the partitions , as separate files. On Android file host. You can. Try to use that.
As far as mate back up I have found one, but it is whole backup.
https://androidfilehost.com/?w=files&flid=261152
Click to expand...
Click to collapse
LOL what can I say, I took one for the team!
Thanks, I actually found a boot.img for a 7x that I fastboot flashed but it didn't help. I am downloading a Full TWRP backup for the Mate SE that I found but my internet at my GFs is real slow so gonna take a couple hours. I'll update.
What Roms for 7x work on SE? Maybe I will just flash one of those? My phone wasn't on Oreo so I don't imagine an Oreo ROM working,
Oh and I bricked by flashing Magisk and no-verify 4.1. I knew I shouldve stayed away from Magisk and just flashed SuperSU
Sandman-007 said:
LOL what can I say, I took one for the team!
Thanks, I actually found a boot.img for a 7x that I fastboot flashed but it didn't help. I am downloading a Full TWRP backup for the Mate SE that I found but my internet at my GFs is real slow so gonna take a couple hours. I'll update.
What Roms for 7x work on SE? Maybe I will just flash one of those? My phone wasn't on Oreo so I don't imagine an Oreo ROM working,
Oh and I bricked by flashing Magisk and no-verify 4.1. I knew I shouldve stayed away from Magisk and just flashed SuperSU
Click to expand...
Click to collapse
I have it downloaded already and have put the images up as files.
***updating this in 5 minutes with link***
mrmazak said:
I have it downloaded already and have put the images up as files.
***updating this in 5 minutes with link***
Click to expand...
Click to collapse
Ok Thanks. So which Rom were u referring too because I only see one and it's Oreo based.
Sandman-007 said:
Ok Thanks. So which Rom were u referring too because I only see one and it's Oreo based.
Click to expand...
Click to collapse
I'm reading through the Mate thread again to see which ones. I think it was the manual Oreo update that worked, but have not found that claim yet.
here is link to folder, still uploading files , but boot is ready
https://www.androidfilehost.com/?w=files&flid=266003
mrmazak said:
I'm reading through the Mate thread again to see which ones. I think it was the manual Oreo update that worked, but have not found that claim yet.
here is link to folder, still uploading files , but boot is ready
https://www.androidfilehost.com/?w=files&flid=266003
Click to expand...
Click to collapse
Thanks downloading now. I do believe it was the manual Oreo. It works for the L31
Sandman-007 said:
Thanks downloading now. I do believe it was the manual Oreo. It works for the L31
Click to expand...
Click to collapse
found the post i remeber reading.
https://forum.xda-developers.com/showpost.php?p=76286950&postcount=159
mrmazak said:
I'm reading through the Mate thread again to see which ones. I think it was the manual Oreo update that worked, but have not found that claim yet.
here is link to folder, still uploading files , but boot is ready
https://www.androidfilehost.com/?w=files&flid=266003
Click to expand...
Click to collapse
Thank You! That worked! My phone boots. That funny because I tried 2 other boot.img for the 7x but they didn't work. Thanks!
Edit: Welp Spoke too soon. I boot but get a black screen once I hit home screen. Trying a Factory reset. I did one earlier but ehhh...
Sandman-007 said:
Thank You! That worked! My phone boots. That funny because I tried 2 other boot.img for the 7x but they didn't work. Thanks!
Edit: Welp Spoke too soon. I boot but get a black screen once I hit home screen.
Click to expand...
Click to collapse
that last boot is from mate backup.
try to go inside , to dark room to see if screen is really blank or just turned down real low.
the brightness on these seem to be able to go way too low.
mrmazak said:
that last boot is from mate backup.
try to go inside , to dark room to see if screen is really blank or just turned down real low.
the brightness on these seem to be able to go way too low.
Click to expand...
Click to collapse
I can see the nav bar and the power menu options. Launcher just wont start. I think I need to flash system image
Sandman-007 said:
I can see the nav bar and the power menu options. Launcher just wont start. I think I need to flash system image
Click to expand...
Click to collapse
well, lets review what you did , and maybe figure out what is "broke" maybe less drastic than system flash is needed.
mrmazak said:
well, lets review what you did , and maybe figure out what is "broke" maybe less drastic than system flash is needed.
Click to expand...
Click to collapse
Ok. SO after I unlocked my bootloader I flashes TWRP 3.1.1-0. I can't find 3.1.1-1 for the 7x even tho that is the one ppl say to use since it supports decrypt.
Then I flashed the latest Magisk and no-verity 4.1. When my system didn't boot I tried n-verity 6.0 then 5.1 as I thought I was using the wrong version but it didn't help.
I did try flashing the uninstaller for Magisk but it fails to flash. Can't find /Vender it says. Honestly I should've just flashed SuperSU.
Sandman-007 said:
Ok. SO after I unlocked my bootloader I flashes TWRP 3.1.1-0. I can't find 3.1.1-1 for the 7x even tho that is the one ppl say to use since it supports decrypt.
Then I flashed the latest Magisk and no-verity 4.1. When my system didn't boot I tried n-verity 6.0 then 5.1 as I thought I was using the wrong version but it didn't help.
I did try flashing the uninstaller for Magisk but it fails to flash. Can't find /Vender it says. Honestly I should've just flashed SuperSU.
Click to expand...
Click to collapse
Maybe need to flash vendor partition.
Still uploading that file. Is at 33%Done
It is 822 mb
Version I am putting up is from the b130 backup
Check back in file host folder in about 15-20 minutes. Or continue with the original full backup download. Done
mrmazak said:
Maybe need to flash vendor partition.
Still uploading that file. Is at 33%Done
It is 822 mb
Version I am putting up is from the b130 backup
Check back in file host folder in about 15-20 minutes. Or continue with the original full backup download. Done
Click to expand...
Click to collapse
Thank you. It'll be a few hours but I will get back to you!
mrmazak said:
Maybe need to flash vendor partition.
Still uploading that file. Is at 33%Done
It is 822 mb
Version I am putting up is from the b130 backup
Check back in file host folder in about 15-20 minutes. Or continue with the original full backup download. Done
Click to expand...
Click to collapse
Well I tried flashing Boot, System and Vender and I still have the blank screen. I even wiped system and Data then reflashed. I suspect the system.img is different for Mate SE and I am flashing 7x System.img
Sandman-007 said:
Well I tried flashing Boot, System and Vender and I still have the blank screen. I even wiped system and Data then reflashed. I suspect the system.img is different for Mate SE and I am flashing 7x System.img
Click to expand...
Click to collapse
The folder I shared is the mate se backup.
mrmazak said:
The folder I shared is the mate se backup.
Click to expand...
Click to collapse
Any suggestions then because I flashed all the files after a full wipe and I still get a Black Screen with nav bar showing and power options showing but no launcher
Sandman-007 said:
I can see the nav bar and the power menu options. Launcher just wont start. I think I need to flash system image
Click to expand...
Click to collapse
i bricked mine within a day, same reason: magisk + no-verify. Can't say for sure why, I installed magisk ok, no-verify had zip error, but installed anyway, then I wiped caches. result = no boot. Maybe I shouldn't have wiped?
I was able to recover using someone else's backup imgs and part of the process here:
https://forum.xda-developers.com/honor-6x/how-to/how-to-to-stock-emui-5-0-flashing-twrp-t3679985
I used fastboot to flash the system and boot imgs and used twrp to flash the vendor img. I think that was the trick, just using fastboot to flash the vendor resulted in the black screen with nav controls only.
drunkle said:
i bricked mine within a day, same reason: magisk + no-verify. Can't say for sure why, I installed magisk ok, no-verify had zip error, but installed anyway, then I wiped caches. result = no boot. Maybe I shouldn't have wiped?
I was able to recover using someone else's backup imgs and part of the process here:
https://forum.xda-developers.com/honor-6x/how-to/how-to-to-stock-emui-5-0-flashing-twrp-t3679985
I used fastboot to flash the system and boot imgs and used twrp to flash the vendor img. I think that was the trick, just using fastboot to flash the vendor resulted in the black screen with nav controls only.
Click to expand...
Click to collapse
OK I tried that. Selected the vender partition in TWRP and flashed vender img on top. Still black screen.
I went to the dark side in April 2016, and haven't flashed anything in about 2 years. Wife's tablet (flo) needs an update, MM is getting laggy though the tablet has always been good to us.
Titanium was getting to be crap around the last time I used it, with problems mostly restoring, does that still hold true? Might just use it to back up a couple apps she uses a lot and just use Play Store to restore the rest. It's not really important, just curious.
Downloading the TWRP app, I know TWRP is installed but willing to bet it needs to be updated and the app can do that.
Tablet is near its EOL, not planning on rooting it if the ROM doesn't come pre-rooted. I have no idea what Magisk is.
So I'm gonna go into TWRP, wipe system, wipe data, wipe cache, wipe dalvik. Flash ROM (going with Lineage 15.1). Now at one point 2-3 years ago the common wisdom was starting to become "flash ROM, boot ROM, reboot to recovery and then flash Gapps." Y'all still doing that? Or can I just flash Gapps right after flashing ROM and reboot then?
Bit nervous as I haven't flashed in a while, but also kind of exciting.
We've got Android 8.1 Oreo now... Working perfectly on our Nexus 7... You should check it out...
Any suggestions for which are the most stable roms to try? I'm in the same boat. I'm on android 6.0.1, stopped flashing things a while ago and it might even be official! But mine's running like a dog so think I wanna try something to jazz it up!
You should try pure Nexus rom based on 7.1.2 for ultimate good battery life. Oreo is Good but battery isn't the greatest.
Well i have been rooting for a bit.
My N7 2013 Flo is not rooted. It is unlocked.
I thought i have via adb fastboot put latest twrp on it...but i turn it off (go into bootloader) toggle into recovery...tarp is not there (triangle with red 'i').....
I dont want to go ballistic but I never would have thought I am having such a hard time putting recovery image onto it.
It is stock 6.1
CF root doesn't exist anymore...some say use majisk....that's not working....
Without a recovery tool....(twrp) nothing can be flashed..
AM I MISSING SOMETHING
ganggreen777 said:
Well i have been rooting for a bit.
My N7 2013 Flo is not rooted. It is unlocked.
I thought i have via adb fastboot put latest twrp on it...but i turn it off (go into bootloader) toggle into recovery...tarp is not there (triangle with red 'i').....
I dont want to go ballistic but I never would have thought I am having such a hard time putting recovery image onto it.
It is stock 6.1
CF root doesn't exist anymore...some say use majisk....that's not working....
Without a recovery tool....(twrp) nothing can be flashed..
AM I MISSING SOMETHING
Click to expand...
Click to collapse
Firstly, your stock 6.1 is ancient and obsolete. Here are detailed instructions to install a modern Android, TWRP and root....
https://wiki.lineageos.org/devices/flo/install
ROM - https://download.lineageos.org/flo
native root solution, no need for CF, Magisk, etc. - https://download.lineageos.org/extras (install addonsu-14.1-arm-signed.zip and activate it in the developer options)
:good:
k23m said:
Firstly, your stock 6.1 is ancient and obsolete. Here are detailed instructions to install a modern Android, TWRP and root....
https://wiki.lineageos.org/devices/flo/install
ROM - https://download.lineageos.org/flo
native root solution, no need for CF, Magisk, etc. - https://download.lineageos.org/extras (install addonsu-14.1-arm-signed.zip and activate it in the developer options)
:good:
Click to expand...
Click to collapse
Thanks so much for responding back!!!!
Tonight I will follow the steps. I trust it will go fine.
Excited to do this. ......yep I waited this long to root this device
k23m said:
Firstly, your stock 6.1 is ancient and obsolete. Here are detailed instructions to install a modern Android, TWRP and root....
https://wiki.lineageos.org/devices/flo/install
ROM - https://download.lineageos.org/flo
native root solution, no need for CF, Magisk, etc. - https://download.lineageos.org/extras (install addonsu-14.1-arm-signed.zip and activate it in the developer options)
:good:
Click to expand...
Click to collapse
I did the 'install lineageOS on flo and installed TWRP latest. Seem like fastboot went into a slew of commands
and finished. I followed the steps to reboot into recovery and twrp is not there. Android dude opened with red triangle.
I have no clue whats up. I leave it sit, and it reboots into android splash screen and bootsup so i can use the tablet. I guess this is why I am soo perplexed. "Am i missing something?"
ganggreen777 said:
....twrp is not there. Android dude opened with red triangle.
...."Am i missing something?"
Click to expand...
Click to collapse
I think you have missed this step.... "Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install." - https://twrp.me/asus/asusnexus72013wifi.html
k23m said:
I think you have missed this step.... "Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install." - https://twrp.me/asus/asusnexus72013wifi.html
Click to expand...
Click to collapse
Thank you for 'helping me'......I have googled this combo everywhere and tried it all. Nothing is allowing the tablet to populate into twrp.....
Perhaps its really not fastbooting twrp into the device
Kevin_McLaughlin said:
Thank you for 'helping me'......I have googled this combo everywhere and tried it all. Nothing is allowing the tablet to populate into twrp.....
Perhaps its really not fastbooting twrp into the device
Click to expand...
Click to collapse
Wait, is Kevin_McLaughlin=ganggreen777 ?
Anyway, here is an alternative way:
- fastboot flash recovery twrp-3.2.3-0-flo.img (please copy the output and post it here)
- fastboot reboot-bootloader
- select recovery in the bootloader
That's it, but you must do it in this order or else TWRP will be gone again.
k23m said:
Wait, is Kevin_McLaughlin=ganggreen777 ?
Anyway, here is an alternative way:
- fastboot flash recovery twrp-3.2.3-0-flo.img (please copy the output and post it here)
- fastboot reboot-bootloader
- select recovery in the bootloader
That's it, but you must do it in this ordecr or else TWRP will be gone again.
Click to expand...
Click to collapse
Why u asking???? Have we chatted b4?¿?
I will do as stated above (I swear I am (thinking) I am doing it as above all the other times. (when you say copy output...is that from the fastboot dialogue? ) ...is it as easy as copy paste ...I dont remember how to copy via adb fastboot...
(Makes me wonder if twrp is really being fastbooted into the n7 2013
Thanks for helping.
k23m said:
Wait, is Kevin_McLaughlin=ganggreen777 ?
Anyway, here is an alternative way:
- fastboot flash recovery twrp-3.2.3-0-flo.img (please copy the output and post it here)
- fastboot reboot-bootloader
- select recovery in the bootloader
That's it, but you must do it in this order or else TWRP will be gone again.
Click to expand...
Click to collapse
So I did the steps and it appeared. THANKS!!!
I downloaded the latest nightly of the link you told me to go to. I tried to flash it......it didnt flash.
ganggreen777 said:
So I did the steps and it appeared. THANKS!!!
I downloaded the latest nightly of the link you told me to go to. I tried to flash it......it didnt flash.
Click to expand...
Click to collapse
Did you try a factory reset immediately prior to installing it?
Sent from my Asus P027 using XDA Labs
ganggreen777 said:
So I did the steps and it appeared. THANKS!!!
I downloaded the latest nightly of the link you told me to go to. I tried to flash it......it didnt flash.
Click to expand...
Click to collapse
You need to do the following in TWRP:
(Optional, but recommended): Select the Backup button to create a backup.
Select Wipe and then Advanced Wipe.
Select Cache, System and Data partitions to be wiped and then Swipe to Wipe.
Go back to return to main menu, then select Install.
Navigate to /sdcard , and select the LineageOS .zip package.
next install the addonsu-14.1-arm-signed.zip (root addon)
and finally GApps (Google Apps) from https://opengapps.org/ - select ARM 7.1 pico
"Note: If you want any Google Apps on your device, you must follow this step before the first boot into Android!"
:highfive:
beachfl said:
Did you try a factory reset immediately prior to installing it?
Sent from my Asus P027 using XDA Labs
Click to expand...
Click to collapse
Lol
Hell no....totally forgot.
I will do the next thing you posted....and check back.
THANKS
ganggreen777 said:
Lol
Hell no....totally forgot.
I will do the next thing you posted....and check back.
THANKS
Click to expand...
Click to collapse
BTW
I am great to go.....thanks very much for helping me thru
---------- Post added at 01:06 AM ---------- Previous post was at 01:04 AM ----------
k23m said:
You need to do the following in TWRP:
(Optional, but recommended): Select the Backup button to create a backup.
Select Wipe and then Advanced Wipe.
Select Cache, System and Data partitions to be wiped and then Swipe to Wipe.
Go back to return to main menu, then select Install.
Navigate to /sdcard , and select the LineageOS .zip package.
next install the addonsu-14.1-arm-signed.zip (root addon)
and finally GApps (Google Apps) from https://opengapps.org/ - select ARM 7.1 pico
"Note: If you want any Google Apps on your device, you must follow this step before the first boot into Android!"
:highfive:
Click to expand...
Click to collapse
BTW I am great to go... Thanks for sticking thru with me
I'm running the stock rom on the November patch. I have TWRP installed with Magisk and the Kirisakura kernel. I've read and Googled for a solution and still can't get it to work. I have the latest ADB told installed but I am unable to push the update through. Can someone tell me what I'm missing? This used to be so much simpler lol. Thanks in advance.
DarkPhoenix said:
I'm running the stock rom on the November patch. I have TWRP installed with Magisk and the Kirisakura kernel. I've read and Googled for a solution and still can't get it to work. I have the latest ADB told installed but I am unable to push the update through. Can someone tell me what I'm missing? This used to be so much simpler lol. Thanks in advance.
Click to expand...
Click to collapse
From what I understand you can not do ADB in TWRP to install an update. What I did was download the factory images, remove -w from the flash all.bat. flashed the images and let the phone boot normally. Once I knew it was running I went to the bootloader and booted TWRP temporarily. Once that was up I flashed Magisk and then my kernel
I don't install TWRP anymore.
DarkPhoenix said:
I'm running the stock rom on the November patch. I have TWRP installed with Magisk and the Kirisakura kernel. I've read and Googled for a solution and still can't get it to work. I have the latest ADB told installed but I am unable to push the update through. Can someone tell me what I'm missing? This used to be so much simpler lol. Thanks in advance.
Click to expand...
Click to collapse
Adding to what hatdrc said, you want the full image, not OTA, and install from your PC in fastboot mode. If you are concerned about saving your data, remove the -w switch from flash-all.bat first using a file editor like notepad. Have the twrp.zip, kernel.zip and magisk.zip files already staged. I personally don't boot to system first (but you can), I "catch" the reboot after flashing completes with the volume down button to reboot to fastboot mode. Then fastboot boot twrp.img, and then install twrp, kernel and magisk zips all in one go using the "add more zips" button in twrp. Every month when you update, you'll lose twrp, kernel and magisk, so those have to be reflashed each time. You'll soon get used to it and can do the whole thing in about 5 minutes consistently. Just make sure to pre-stage the 3 zip files on the phone before you start. Best of luck.
I tried that but couldn't get it to work. I downloaded the ADB tools again just in case there was an issue with that. I'm going to run the flash-all script again to see if I can get it to work.
DarkPhoenix said:
I tried that but couldn't get it to work. I downloaded the ADB tools again just in case there was an issue with that. I'm going to run the flash-all script again to see if I can get it to work.
Click to expand...
Click to collapse
if whats suggested above doesnt work, you can make the OTA work....download the ota to your PC, boot to Android Recovery (not TWRP), apply the ota via ADB from the menu. Whenever I have "odd" issues applying the Full image, this always works for me. Obviously you need to re-root after.
GL!
cmh714 said:
if whats suggested above doesnt work, you can make the OTA work....download the ota to your PC, boot to Android Recovery (not TWRP), apply the ota via ADB from the menu. Whenever I have "odd" issues applying the Full image, this always works for me. Obviously you need to re-root after.
GL!
Click to expand...
Click to collapse
Doesn't installing TWRP remove Android Recovery?
DarkPhoenix said:
Doesn't installing TWRP remove Android Recovery?
Click to expand...
Click to collapse
hmm, since I dont install TWRP anymore, you may be correct....still cant hurt to try
DarkPhoenix said:
Doesn't installing TWRP remove Android Recovery?
Click to expand...
Click to collapse
Yes it does. TWRP replaces the stock recovery.
Sent from my [device_name] using XDA-Developers Legacy app
v12xke said:
Adding to what hatdrc said, you want the full image, not OTA, and install from your PC in fastboot mode. If you are concerned about saving your data, remove the -w switch from flash-all.bat first using a file editor like notepad. Have the twrp.zip, kernel.zip and magisk.zip files already staged. I personally don't boot to system first (but you can), I "catch" the reboot after flashing completes with the volume down button to reboot to fastboot mode. Then fastboot boot twrp.img, and then install twrp, kernel and magisk zips all in one go using the "add more zips" button in twrp. Every month when you update, you'll lose twrp, kernel and magisk, so those have to be reflashed each time. You'll soon get used to it and can do the whole thing in about 5 minutes consistently. Just make sure to pre-stage the 3 zip files on the phone before you start. Best of luck.
Click to expand...
Click to collapse
Ok, I got the flash-all script to run. My brain shut down and I was running the wrong command.
DarkPhoenix said:
Ok, I got the flash-all script to run. My brain shut down and I was running the wrong command.
Click to expand...
Click to collapse
Well done. Now you can do it all over again in a week on Monday the 7th when the January build comes out.
v12xke said:
Well done. Now you can do it all over again in a week on Monday the 7th when the January build comes out.
Click to expand...
Click to collapse
I was updating so I could install Bootleggers rom so updating should be a lot easier lol.
I get into a bootloop after flashing magisk.
The only way out of the bootloop is to flash the original unpatched boot.img (after which everything works perfectly).
I am on 10.0.8. Anybody else have any idea how to troubleshoot this?
I don't think you have to flash Magisk patched boot image, you just have to boot from it. Don't know if its the same thing.
What I do is "fastboot boot magisk_patched.img", then when it boots on the Magisk Manager app, select install -> direct install. After installation is done reboot like normal and Magisk should be installed normally by then.
hectorviov said:
I don't think you have to flash Magisk patched boot image, you just have to boot from it. Don't know if its the same thing.
What I do is "fastboot boot magisk_patched.img", then when it boots on the Magisk Manager app, select install -> direct install. After installation is done reboot like normal and Magisk should be installed normally by then.
Click to expand...
Click to collapse
Hmm, I try your method and I think it's roughly the same.
When I do fastboot boot magisk_patched.img, my device goes into a bootloop. I waited 8 minutes (exactly) and figured it was never gonna boot, and so I killed it. When it booted again, it booted fine with no problems (except not rooted, obviously).
Then maybe you're using a wrong boot image, what's the Build number on Settings -> About phone? (It should be something like "Oxygen OS 10.0.8.HD65AA", that's what I'm currently on). Also, is your bootloader unlocked?
hectorviov said:
Then maybe you're using a wrong boot image, what's the Build number on Settings -> About phone? (It should be something like "Oxygen OS 10.0.8.HD65AA", that's what I'm currently on). Also, is your bootloader unlocked?
Click to expand...
Click to collapse
It's "Oxygen OS 10.0.8.HD65AA" under about phone. I'm also sure my phone is already unlocked because under developer options it says "bootloader is already unlocked" (and fastboot oem unlock gives me an error saying "device already unlocked")
I'm pretty sure it's the right boot image, since I used payload dumper and made the magisk image myself from the dumped boot.img. (both preserve force encryption and perserve AVB are checked)
I have the same, maybe the payload dumper did something wrong with the boot image, or magisk patcher. Try and use this one. Is the one I created and it worked perfectly.
hectorviov said:
I have the same, maybe the payload dumper did something wrong with the boot image, or magisk patcher. Try and use this one. Is the one I created and it worked perfectly.
Click to expand...
Click to collapse
I tried your file and it still gave me a bootloop =/
that said your fastboot boot boot.img trick is really handy since now I don't have to flash my old boot.img to fix the bootloop, haha
Edit: I solved it, all I needed to do was to do a system wipe (ugh) and everything worked...
ixrs said:
I tried your file and it still gave me a bootloop =/
that said your fastboot boot boot.img trick is really handy since now I don't have to flash my old boot.img to fix the bootloop, haha
Edit: I solved it, all I needed to do was to do a system wipe (ugh) and everything worked...
Click to expand...
Click to collapse
I'm having a similar issue, but when I flash the patched boot image I created, I'm only able to reboot into bootloader and it won't boot back into Oxygen OS for me to do the next steps with the Magisk Manager.
When did you do the system wipe, before you rebooted into Android, and did you do the system wipe using TWRP or stock recovery?
I flashed the original boot.img then booted up normally. I then wiped everything. Then I set up my phone again (ugh) and flashed the patched image and it worked.
ixrs said:
I flashed the original boot.img then booted up normally. I then wiped everything. Then I set up my phone again (ugh) and flashed the patched image and it worked.
Click to expand...
Click to collapse
Thanks, just to be clear (I've done this 30 times with no success, and I'm not new to xda or rom/kernel/gapps installation, so this has me scratching my head).
When you say wiped everything, was it:
1) With TWRP from this thread (https://forum.xda-developers.com/oneplus-7t/development/recovery-unofficial-twrp-recovery-t3976961)?
1.1) If with this TWRP, was it a factory reset, dalivik/cache wipe or another wipe OR
2) With original recovery
2.1) If with original recovery, was it Reset system setting, Wipe cache or Erase everything (Music, pics, etc)
You are the only one I've seen with similar issues (you were in bootloop, I'm always rebooting into bootloader) with something I haven't tried yet, so this might get me over the hump (fingers crossed)
I actually did it from within the phone (settings, system, reset, erase all data). I believe it would be equivalent to reset system setting?
ixrs said:
I actually did it from within the phone (settings, system, reset, erase all data). I believe it would be equivalent to reset system setting?
Click to expand...
Click to collapse
Thanks, was going crazy. Tried so many times, will post this to the main root guide on xda in case it helps someone else. Yay. Vanced Youtube here I come
lockekey said:
Thanks, just to be clear (I've done this 30 times with no success, and I'm not new to xda or rom/kernel/gapps installation, so this has me scratching my head).
When you say wiped everything, was it:
1) With TWRP from this thread (https://forum.xda-developers.com/oneplus-7t/development/recovery-unofficial-twrp-recovery-t3976961)?
1.1) If with this TWRP, was it a factory reset, dalivik/cache wipe or another wipe OR
2) With original recovery
2.1) If with original recovery, was it Reset system setting, Wipe cache or Erase everything (Music, pics, etc)
You are the only one I've seen with similar issues (you were in bootloop, I'm always rebooting into bootloader) with something I haven't tried yet, so this might get me over the hump (fingers crossed)
Click to expand...
Click to collapse
First the OP was in a bootloop cuz he flashed but not booted the magisk_pated.img so when he tried to boot from magisk_patched it didn't work.
So you can either simply go and download the OnePlus last 1.0.8.0 fastboot ROM and extract the boot.img then flash that using the command and so you will be out of the bootloop.
Don't use the twrp!... it's been stated plenty of times that there's no working android 10 twrp for our device yet.
*start from here...*
Instead all you need to do is to download magisk 20.3
-Extract last APK from the zip
-Install apk (magisk manager)
-Inside magisk manager choose install and then choose patch IMG
-Choose the image that you got from the fastboot official rom.
-You will get the magisk_patched.img in your downloads folder
-Take that file to the pc
-Put your phone In fastboot mode
-Then cmand fastboot boot magisk_patched.img
-Phone will boot
-Open magisk manager again.
-Choose install again and you will have a new option called direct install.
-Choose that and just reboot once and done...
Now you are rooted.
It's simple.
PriPhaze said:
First the OP was in a bootloop cuz he flashed but not booted the magisk_pated.img so when he tried to boot from magisk_patched it didn't work.
So you can either simply go and download the OnePlus last 1.0.8.0 fastboot ROM and extract the boot.img then flash that using the command and so you will be out of the bootloop.
Don't use the twrp!... it's been stated plenty of times that there's no working android 10 twrp for our device yet.
*start from here...*
Instead all you need to do is to download magisk 20.3
-Extract last APK from the zip
-Install apk (magisk manager)
-Inside magisk manager choose install and then choose patch IMG
-Choose the image that you got from the fastboot official rom.
-You will get the magisk_patched.img in your downloads folder
-Take that file to the pc
-Put your phone In fastboot mode
-Then cmand fastboot boot magisk_patched.img
-Phone will boot
-Open magisk manager again.
-Choose install again and you will have a new option called direct install.
-Choose that and just reboot once and done...
Now you are rooted.
It's simple.
Click to expand...
Click to collapse
Never used TWRP. Knew it wasn't working.
Tried all three methods from the main Root thread on xda and none worked (including payload dumper to extract my boot image,etc etc).
Please see my reply above yours. I've added those details to the main Root thread in case it helps someone else.
No idea why I could only reboot into bootloader as I only updated to 10.0.8 using oxygen updater and could never Root with all the methods I found on xda.
Erasing all data fixed my issue and I am Groot.
Sent from my HD1905 using Tapatalk
lockekey said:
Never used TWRP. Knew it wasn't working.
Tried all three methods from the main Root thread on xda and none worked (including payload dumper to extract my boot image,etc etc).
Please see my reply above yours. I've added those details to the main Root thread in case it helps someone else.
No idea why I could only reboot into bootloader as I only updated to 10.0.8 using oxygen updater and could never Root with all the methods I found on xda.
Erasing all data fixed my issue and I am Groot.
Click to expand...
Click to collapse
There's no need for payload dumper..
Also you must been using a wrong version of magisk cuz there's no way to fail if you do follow the steps correctly .
All you had to do it was too restore boot.img from fastboot ROM in case you made the mistake to flash the magisk_patched.img instead of booting on it.
And that's it then you just follow the steps.
Yea obviously doing factory reset helped because it restored the boot.img but is like you decided to take the long way instead of the quick and easy way.
PriPhaze said:
There's no need for payload dumper..
Also you must been using a wrong version of magisk cuz there's no way to fail if you do follow the steps correctly .
All you had to do it was too restore boot.img from fastboot ROM in case you made the mistake to flash the magisk_patched.img instead of booting on it.
And that's it then you just follow the steps.
Yea obviously doing factory reset helped because it restored the boot.img but is like you decided to take the long way instead of the quick and easy way.
Click to expand...
Click to collapse
I had no trouble flashing the boot.img without issue to restore my access to OOS. That wasn't the issue. I used the right magisk_patched boot. That wasn't the issue (confirmed this evening when I used the same image to root successfully after I erased my data). The payload dumper method was from this guide (https://forum.xda-developers.com/oneplus-7t/how-to/guide-how-to-root-oneplus-7t-twrp-t3979307) and if the easier 1st 2 methods worked, I wouldn't have tried the 3rd payload dumper method (which got me another version of the same original boot image that I couldn't patch and get to work).
I could never reboot to OOS to install magisk manager and complete a direct install (either after a boot or flashing of the patched image), until I erased data.
Flashing the patched image works as well, it's just another method. I highly recommend reading the above thread.
A tip, you kind of need to know what a person has tried before making suggestions, let alone telling people what they must have done wrong or that they wasted time by using the wrong method.
I highly recommend reading the above thread to learn how to respond to people without coming off as condescending and overbearing. I lot of people tried to help me there and I was very appreciative of how they tried to assist.
lockekey said:
I had no trouble flashing the boot.img without issue to restore my access to OOS. That wasn't the issue. I used the right magisk_patched boot. That wasn't the issue (confirmed this evening when I used the same image to root successfully after I erased my data). The payload dumper method was from this guide (https://forum.xda-developers.com/oneplus-7t/how-to/guide-how-to-root-oneplus-7t-twrp-t3979307) and if the easier 1st 2 methods worked, I wouldn't have tried the 3rd payload dumper method (which got me another version of the same original boot image that I couldn't patch and get to work).
I could never reboot to OOS to install magisk manager and complete a direct install (either after a boot or flashing of the patched image), until I erased data.
Flashing the patched image works as well, it's just another method. I highly recommend reading the above thread.
A tip, you kind of need to know what a person has tried before making suggestions, let alone telling people what they must have done wrong or that they wasted time by using the wrong method.
I highly recommend reading the above thread to learn how to respond to people without coming off as condescending and overbearing. I lot of people tried to help me there and I was very appreciative of how they tried to assist.
Click to expand...
Click to collapse
No one is trying to be condescending... just pointing out facts ..
Thanks for the advice I guess?
But it doesn't really matter; these days people get offended so easily that I'm starting to consider to don't post anymore..
I mean obviously as you can see I have been here for long and lately things have changed that I can't even say anything without being called rude.
And we'll I'm glad you managed to fix your problem although the solution was a bit weird.
Seeya
PriPhaze said:
No one is trying to be condescending... just pointing out facts ..
Thanks for the advice I guess?
But it doesn't really matter; these days people get offended so easily that I'm starting to consider to don't post anymore..
I mean obviously as you can see I have been here for long and lately things have changed that I can't even say anything without being called rude.
And we'll I'm glad you managed to fix your orientation although the solution was a bit weird.
Seeya
Click to expand...
Click to collapse
You may not be trying to be condescending but you are. And you continue by calling what you say facts and ignoring anything I say.
I've been on xda a long time (since nexus 4, 2012), installing kernels, Roms, etc. I'm not a noob and try and help when I can. I've never been called rude and noone ever seemed offended by any of my posts.
I don't think I have run into anyone as rude and condescending as you on xda.
But it's not you, it's everyone else.
I didn't need your help. It was clear I had the info I was looking for and a potential solution to my issue, if you bothered reading. Not sure what point you were trying to make.
Seeya.
lockekey said:
You may not be trying to be condescending but you are. And you continue by calling what you say facts and ignoring anything I say.
I've been on xda a long time (since nexus 4, 2012), installing kernels, Roms, etc. I'm not a noob and try and help when I can. I've never been called rude and noone ever seemed offended by any of my posts.
I don't think I have run into anyone as rude and condescending as you on xda.
But it's not you, it's everyone else.
I didn't need your help. It was clear I had the info I was looking for and a potential solution to my issue, if you bothered reading. Not sure what point you were trying to make.
Seeya.
Click to expand...
Click to collapse
And there we go.. you got triggered.
Sorry but this is a forum and well is open so everyone can come and comment.
Even if you dont need anyone's help anyone can come and quote you if they want.
PriPhaze said:
And there we go.. you got triggered.
Sorry but this is a forum and well is open so everyone can come and comment.
Even if you dont need anyone's help anyone can come and quote you if they want.
Click to expand...
Click to collapse
I thought you were considering not posting anymore because everyone is so triggered.
It was never a free speech issue. It was always you being a condescending know it all issue.
Just don't cry about people being triggered when people call you what you are.
You're amazing and you know it. Don't change a thing.