Related
I have a brand new Pixel XL from Verizon that I received today and was successful in unlocking. However, I tried to root and now I am stuck on bootloop. I cannot post in DEVELOPMENT because I haven't posted here in years (haven't had ANDROID in a while). Can anyone help? I am able to access via fastboot (I believe) but I must be flashing the wrong images. I don't want to brick this nice new day-old device. I have been at it for 5 hours via research on my own, but now I am looking for someone that can help me via P.M. or what it may take. I really want to get back to enjoying this device! Thanks in advance!
bdsuser said:
I have a brand new Pixel XL from Verizon that I received today and was successful in unlocking. However, I tried to root and now I am stuck on bootloop. I cannot post in DEVELOPMENT because I haven't posted here in years (haven't had ANDROID in a while). Can anyone help? I am able to access via fastboot (I believe) but I must be flashing the wrong images. I don't want to brick this nice new day-old device. I have been at it for 5 hours via research on my own, but now I am looking for someone that can help me via P.M. or what it may take. I really want to get back to enjoying this device! Thanks in advance!
Click to expand...
Click to collapse
Read the third post in the thread below to get set up and back to stock. Then we will work on root. If you tried to root and you bootlooped it then you used the wrong SU.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242
1. Download a ROM. A stock version is probably in the forums somewhere if that's what you want.
2. Download TWRP image and zip from the TWRP thread.
3. Download SuperSU from the SuperSU thread.
4. Download a vendor image. There's no "official" vendor image thread AFAIK, but you can grab one from the Pure Nexus rom thread. NMF26V is compatible with all 7.1.1 ROMs & stock.
Now you have two options:
Fast: Put the ROM, TWRP(zip only), SuperSU and vendor image on USB flash drive, then connect the USB 3 to USB C adapter to your flash drive. Don't connect it to the phone yet. An external HDD/SSD should also work if that's all you've got.
Slow: While in TWRP(Instructions below) push the ROM, TWRP(zip only), SuperSU and vendor image files to your phone through ADB with "adb push C:\file_path\ /sdcard/" sans quotes. You will need to do this for each file, or alternatively push a folder containing the four files. adb file transfer is very slow.
5. Boot your phone to the bootloader, and connect it to your computer. This can be achieved by holding volume down and power from an off state.
Note: If your device is still bootlooping you won't be able to get to the bootloader. Hold volume up and power until the device shuts off to get out of the bootloop temporarily, then boot to bootloader.
6. In a command window, "fastboot boot twrp.img"
7. Connect your flash drive to your phone if you chose that option, or push the files through adb if you chose that option
8. Flash TWRP zip, ROM and vendor image. STAY IN TWRP
9. Return to TWRP's home screen > advanced > file manager. Scroll down until you see 'fstab.marlin'(in the root '/' directory). Tap on 'fstab.marlin' and delete it. Skipping this step means SuperSU won't install.
10. Flash SuperSU zip, reboot to system and you're done.
SDK
TonikJDK said:
Read the third post in the thread below to get set up and back to stock. Then we will work on root. If you tried to root and you bootlooped it then you used the wrong SU.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242
Click to expand...
Click to collapse
Just thought I'd update you...And I know I sound like I have no idea what I'm doing but traditionally I've never had issues like this But I am trying to get ADB to show the flash-all command. The one I have installed doesn't show that feature so I can't follow the tutorial. If you have a direct link to what I may be missing I would appreciate it otherwise I will update you once I figure it out.
bdsuser said:
Just thought I'd update you...And I know I sound like I have no idea what I'm doing but traditionally I've never had issues like this But I am trying to get ADB to show the flash-all command. The one I have installed doesn't show that feature so I can't follow the tutorial. If you have a direct link to what I may be missing I would appreciate it otherwise I will update you once I figure it out.
Click to expand...
Click to collapse
The link to the proper adb and fastboot are in the post i pointed you to.
Help with root and TWRP
TonikJDK said:
The link to the proper adb and fastboot are in the post i pointed you to.
Click to expand...
Click to collapse
Thanks for your assistance. I now have root installed and I think I'm good except for one thing. I keep thinking TWRP is installed but for some reason when I reboot to bootloader, then select reboot recovery mode, it takes me to android recovery. I am used to recovery taking me to TWRP. I know TWRP works but I feel like I'm temporarily flashing it each time or something. I even installed the twrp app and I see I can flash zips that way, etc, but I wanted to know if you knew how to make the phone boot to TWRP in recovery? Or is that necessary?
bdsuser said:
Thanks for your assistance. I now have root installed and I think I'm good except for one thing. I keep thinking TWRP is installed but for some reason when I reboot to bootloader, then select reboot recovery mode, it takes me to android recovery. I am used to recovery taking me to TWRP. I know TWRP works but I feel like I'm temporarily flashing it each time or something. I even installed the twrp app and I see I can flash zips that way, etc, but I wanted to know if you knew how to make the phone boot to TWRP in recovery? Or is that necessary?
Click to expand...
Click to collapse
I dont do it that way on this phone. TWRP and SU are modifying the same parts of the phone, and there are cases where it could conflict. Rare, not a big deal, but since i don't need TWRP installed i don't.
To install it ypu first boot to it.
Fastboot boot twrpFilename.
Then from within TWRP you install the TWRP zip.
Make sure it is TWRP RC1
All set
Thanks again for your help. I am running pure ROM as I mentioned and I seem to like it. Do you K or if Franco works with Pure or do you have a suggestion on a good rom/kernel? Is there anything else that you can suggest I should be using with the new phone? I remember there used to be tools that you could install that allowed you to customize the system even further but the name escapes me. . Is there anything like that or even a theme tool which is a must have when you are rooted and running custom roms? No big deal if not. Very happy with where I stand now. Really appreciate you getting me back up and running!
You are most welcome. I don't ROM so I don't know what kernels work with what roms for sure. But my understanding is that they are all pretty universal. I run stock with Franco.
Other than that i dont mod much. Ad blocker, black themes and a few adjustments to Franco.
TonikJDK said:
You are most welcome. I don't ROM so I don't know what kernels work with what roms for sure. But my understanding is that they are all pretty universal. I run stock with Franco.
Other than that i dont mod much. Ad blocker, black themes and a few adjustments to Franco.
Click to expand...
Click to collapse
Perfect! Thanks yet again. Have a great remainder of the day!
bdsuser said:
Thanks again for your help. I am running pure ROM as I mentioned and I seem to like it. Do you K or if Franco works with Pure or do you have a suggestion on a good rom/kernel? Is there anything else that you can suggest I should be using with the new phone? I remember there used to be tools that you could install that allowed you to customize the system even further but the name escapes me. . Is there anything like that or even a theme tool which is a must have when you are rooted and running custom roms? No big deal if not. Very happy with where I stand now. Really appreciate you getting me back up and running!
Click to expand...
Click to collapse
Im running pure and elementalx with excellent results.
?Tapped from my pure pixelXl?
have you ever seen an issue where the phone boots to twrp even though everything was working fine? It starts happening if I do a restart. Then no matter what it boots into TWRP unless I wipe again? I believe it's happening after I flash root but I'm going out of my mind with trial and error. Any help would be appreciated.
bdsuser said:
have you ever seen an issue where the phone boots to twrp even though everything was working fine? It starts happening if I do a restart. Then no matter what it boots into TWRP unless I wipe again? I believe it's happening after I flash root but I'm going out of my mind with trial and error. Any help would be appreciated.
Click to expand...
Click to collapse
HELLO!!! I understand any frustrations you may be having, as the pixel devices have changed a good bit for us as far as development. Anyways. I'm just going to throw some knowledge out there, then proceed to help get you up and running!
You couldn't post in the development section because of your post count, but even if you could, it would have been in the wrong section and it would have been removed, or moved to the questions section.
Also, I see someone has pointed it out earlier, but I'll say it again just to make sure everything is clear. The command you were running "fastboot boot TWRP.img" only boots TWRP temporarily. You are suppose to have two files, one IMG file and one zip file. You boot the IMG file, then once you're in TWRP, you flash the zip file, then reboot to recovery and you will have installed TWRP properly.
With root, flashing wrong files or using the outdated root method will cause boot loops. The correct way to root (again already been said) is the get TWRP up and running, delete the fstab file (see earlier post) then flash SuperSU and reboot. Just throwing this out there Incase someone comes across it, if you manage to boot loop your device due to to rooting, you can fastboot flash franco's kernel and it will fix the bootloop (,but you won't have root) this isn't the correct way to fix it, but it will get you back up and running without downloading the large factory image.
***About to edit this post to continue giving more info***
Here is a correct guide and good template to get you running.
start by flashing a clean factory image, then let it boot and get it set up.
Reboot to fastboot, fastboot boot TWRP IMG then flash TWRP zip using the latest versions (RC1 is latest, pm me for more info).
Reboot the phone to recovery to ensure TWRP stuck.
Go-to advanced, file manager in TWRP and find the fstab.marlin file and delete.
Then you can go ahead and flash the latest SuperSU (I use 2.79 sr3) and when it's done reboot to system and verify root.
After rooting you can go ahead and flash a kernel if you want, I use elemental which you can flash in TWRP, but see the kernel instructions prior to flashing.
Reboot and you have a nice stock ROM with root and kernel.
For flashing Roms, kind of follow the same template, most Roms require you to flash part of or the whole latest factory image.
If your on a clean install, go ahead and install TWRP as mentioned above.
Then use TWRP to install whatever ROM you want per ROM developer instructions.
Side note, some Roms replace the TWRP with cwm or stock recovery, so it's always nice to flash the TWRP zip after flashing a ROM.
After flashing ROM, boot to system to make sure all is well, then boot back to recovery and follow instructions above for root/kernel.
As far as the problem you're having now, it usually comes from flashing outdated SuperSU images. Do a search for 2.79 sr3 and use it to root (pm me if you need help)
You might have to start clean one more time, And flash factory image.
noidea24 said:
HELLO!!! I understand any frustrations you may be having, as the pixel devices have changed a good bit for us as far as development. Anyways. I'm just going to throw some knowledge out there, then proceed to help get you up and running!
You couldn't post in the development section because of your post count, but even if you could, it would have been in the wrong section and it would have been removed, or moved to the questions section.
Also, I see someone has pointed it out earlier, but I'll say it again just to make sure everything is clear. The command you were running "fastboot boot TWRP.img" only boots TWRP temporarily. You are suppose to have two files, one IMG file and one zip file. You boot the IMG file, then once you're in TWRP, you flash the zip file, then reboot to recovery and you will have installed TWRP properly.
With root, flashing wrong files or using the outdated root method will cause boot loops. The correct way to root (again already been said) is the get TWRP up and running, delete the fstab file (see earlier post) then flash SuperSU and reboot. Just throwing this out there Incase someone comes across it, if you manage to boot loop your device due to to rooting, you can fastboot flash franco's kernel and it will fix the bootloop (,but you won't have root) this isn't the correct way to fix it, but it will get you back up and running without downloading the large factory image.
***About to edit this post to continue giving more info***
Here is a correct guide and good template to get you running.
start by flashing a clean factory image, then let it boot and get it set up.
Reboot to fastboot, fastboot boot TWRP IMG then flash TWRP zip using the latest versions (RC1 is latest, pm me for more info).
Reboot the phone to recovery to ensure TWRP stuck.
Go-to advanced, file manager in TWRP and find the fstab.marlin file and delete.
Then you can go ahead and flash the latest SuperSU (I use 2.79 sr3) and when it's done reboot to system and verify root.
After rooting you can go ahead and flash a kernel if you want, I use elemental which you can flash in TWRP, but see the kernel instructions prior to flashing.
Reboot and you have a nice stock ROM with root and kernel.
For flashing Roms, kind of follow the same template, most Roms require you to flash part of or the whole latest factory image.
If your on a clean install, go ahead and install TWRP as mentioned above.
Then use TWRP to install whatever ROM you want per ROM developer instructions.
Side note, some Roms replace the TWRP with cwm or stock recovery, so it's always nice to flash the TWRP zip after flashing a ROM.
After flashing ROM, boot to system to make sure all is well, then boot back to recovery and follow instructions above for root/kernel.
As far as the problem you're having now, it usually comes from flashing outdated SuperSU images. Do a search for 2.79 sr3 and use it to root (pm me if you need help)
You might have to start clean one more time, And flash factory image.
Click to expand...
Click to collapse
There is absolutely no need to delete the fstab file anymore. That only needed to be done when TWRP was still alpha 2, and almost three versions of su earlier.
ALL roms replace TWRP with stock recovery unless you are using lineage then you will get Cyanogenmod recovery, so reflashing TWRP before booting into system is a must.
If you are flashing root and or custome kernel and end up in a bootloop, flashing the stock boot.img to both slots via:
'fastboot flash --slot _a boot boot.img'
'fastboot flash --slot _b boot boot.Img'
will fix the issue and you will be able to boot up just fine. Again you will have to reboot into TWRP from the bootloader and reflash the zip. When you are done flashing the boot.img's you might as well just
'Fastboot boot TWRP-file.img'
Then install the zip!
I'm using stock oos and root with magisk
Everytime I get an ota it removes root.
Does anyone have any ideas
It happens because if you choose to update over System Settings it somehow knows that your phone is rooted / has an unlocked BL.
Therefore, Oneplus only offers the full Image. There is a way to inspect this full Image.
The way I'm doing it whenever I'm updating is:
download the newest FW over PC, inspect zip... delete something that says "recovery" on it.
Because that is the one, that will return you to stock recovery, instead of keeping TWRP installed.
After flashing that zip; TWRP should still be available for you, from there you can re-flash the magisk zip and you should all be rooted then.
moeq123 said:
It happens because if you choose to update over System Settings it somehow knows that your phone is rooted / has an unlocked BL.
Therefore, Oneplus only offers the full Image. There is a way to inspect this full Image.
The way I'm doing it whenever I'm updating is:
download the newest FW over PC, inspect zip... delete something that says "recovery" on it.
Because that is the one, that will return you to stock recovery, instead of keeping TWRP installed.
After flashing that zip; TWRP should still be available for you, from there you can re-flash the magisk zip and you should all be rooted then.
Click to expand...
Click to collapse
After that do you only loose root? Is your data, apps, customizations still there? Other than magisk root what else got deleted? Please answer i wanna do it your way.
Also where do you download FW file?
nadiration said:
After that do you only loose root? Is your data, apps, customizations still there? Other than magisk root what else got deleted? Please answer i wanna do it your way.
Also where do you download FW file?
Click to expand...
Click to collapse
Firmwares should be available on manufactures site.
For Oneplus 5T it should be that link: https://downloads.oneplus.com/devices/oneplus-5t/
Honestly, I can't tell what's inside These files; as I don't have one of them at Hand; and I'm not allowed to download and open such files here at work.
If you want I can expect them later after work (4 hours or something) or you download one and post me the Folder tree as a text here.
I know, that if you remove this one recovery file/Folder/entry that it passes the flashing of the recovery Partition.
If I recall correctly (from my Knowledge of devices and roms other than op5t) inside of These downloaded firmwares there should be a file called "Image.zip"
inside that Image.zip there should be Folders or files like "boot", "recovery" "system Images", and "userdata".
Delete recovery and userdata, repack it to "Image.zip" and repack that zip to the previously downloaded zip...
flashing that pack should prevent you from your data being wiped.
I don't know if magisk will work without flashing magisk.zip over.
Before you do all that stuff, back up your data, try it, and please - let us know if that has worked.
[Edit]: TL;DR - In the end, it just wipes your data and installs another recovery because it has been told to do so inside of these Firmware Images.
Download that Firmware, inspect everything, and delete stuff that tells him to do stuff that you don't like.
Hello Friends!
Basically, I rooted my Samsung A50 using the Odin with magisk_patched.tar. I did not install TWRP or CWM on the phone.
It worked amazingly!
...at first.
Then it got all messed up -- you can read about the issues I was having at the end of this post.
Fortunately, the phone works again with the stock ROM after reflashing the BL/AP/CP/CSC files using Odin!
Now I am trying to figure out the best method for rooting with Magisk and installing TWRP or CWM. (if that is needed)
Any suggestions? Any recommendations for posts I can read, videos, or other tutorials?
I don't want to screw this up again!
I *really* appreciate any tips, directions or help of any kind!
And I apologize for being pretty inept at this stuff
BACKGROUND ====================================================
Straight up: I am somewhat tech-savvy but my skill level is quite low with android stuff -- I have spent a lot of time reading and trying to figure it all out. I realize I just need help to find the best path forward.
I deleted some modules in Magisk that I tried to check out.....
===> then Magisk Manager displayed "Magisk in not installed" and it seemed like root access was no longer available.
===> Clicked install
===> Would you like to Install Magisk 19.3?
===> Clicked Install ===> Given choice to 'Download Zip Only' or 'Select and Patch a File' -- I tried selecting and patching 'magisk_patched.tar' which seemed to work but now I believe the phone is in a bootloop (Samsung logo is displaying without getting anywhere)
I have everything on the phone backed up. I have 'magisk_patched.tar' on my PC.
I decided to wipe the phone and re-do the whole process.
I then ===> reflashed 'magisk_patched.tar' file using odin in download mode.
It seemed to work at first -- the stock ROM was asking for language, privacy agreements, etc.
But it would reboot within 30 seconds of android starting - I could not get past the privacy agreements.
It was stuck in a loop.
Then I tried to ===> flash TWRP using Odin (instructions here: https://www.******.com/root-samsung-...0-with-magisk/)
Now I cannot access recovery.
The phone is just stuck on the Samsung Galaxy A50 screen.
I am able to get into download mode using volume +/- & USB-C. But reflashing the patched ROM or trying to install TWRP using the methods that I know are not working.
I am really not sure what to do now.
===> I am currently reflashing the BL/AP/CP/CSC files using Odin.
The place that I am at is at the top of this post.
Thanks for your help!!
doctadocta said:
Hello Friends!
Basically, I rooted my Samsung A50 using the Odin with magisk_patched.tar. I did not install TWRP or CWM on the phone.
It worked amazingly!
...at first.
Then it got all messed up -- you can read about the issues I was having at the end of this post.
Fortunately, the phone works again with the stock ROM after reflashing the BL/AP/CP/CSC files using Odin!
Now I am trying to figure out the best method for rooting with Magisk and installing TWRP or CWM. (if that is needed)
Any suggestions? Any recommendations for posts I can read, videos, or other tutorials?
I don't want to screw this up again!
I *really* appreciate any tips, directions or help of any kind!
And I apologize for being pretty inept at this stuff
BACKGROUND ====================================================
Straight up: I am somewhat tech-savvy but my skill level is quite low with android stuff -- I have spent a lot of time reading and trying to figure it all out. I realize I just need help to find the best path forward.
I deleted some modules in Magisk that I tried to check out.....
===> then Magisk Manager displayed "Magisk in not installed" and it seemed like root access was no longer available.
===> Clicked install
===> Would you like to Install Magisk 19.3?
===> Clicked Install ===> Given choice to 'Download Zip Only' or 'Select and Patch a File' -- I tried selecting and patching 'magisk_patched.tar' which seemed to work but now I believe the phone is in a bootloop (Samsung logo is displaying without getting anywhere)
I have everything on the phone backed up. I have 'magisk_patched.tar' on my PC.
I decided to wipe the phone and re-do the whole process.
I then ===> reflashed 'magisk_patched.tar' file using odin in download mode.
It seemed to work at first -- the stock ROM was asking for language, privacy agreements, etc.
But it would reboot within 30 seconds of android starting - I could not get past the privacy agreements.
It was stuck in a loop.
Then I tried to ===> flash TWRP using Odin (instructions here: https://www.******.com/root-samsung-...0-with-magisk/)
Now I cannot access recovery.
The phone is just stuck on the Samsung Galaxy A50 screen.
I am able to get into download mode using volume +/- & USB-C. But reflashing the patched ROM or trying to install TWRP using the methods that I know are not working.
I am really not sure what to do now.
===> I am currently reflashing the BL/AP/CP/CSC files using Odin.
The place that I am at is at the top of this post.
Thanks for your help!!
Click to expand...
Click to collapse
Uncheck auto reboot in Odin. Flash twrp, then hold your hard key combo to boot straight into recovery. You have to go from fastboot (odin mode) straight to recovery after you first flash it, or the stock recovery will replace twrp with itself. Once you get it to stick you won't have to worry about how you boot up.
Spaceminer said:
Uncheck auto reboot in Odin. Flash twrp, then hold your hard key combo to boot straight into recovery. You have to go from fastboot (odin mode) straight to recovery after you first flash it, or the stock recovery will replace twrp with itself. Once you get it to stick you won't have to worry about how you boot up.
Click to expand...
Click to collapse
Thanks for the response, Spaceminer!
When I try to flash TWRP_A50_Magisk_Prepatched.tar
from here: https://drive.google.com/drive/folders/1brK12SaoQ4gRbhuqLm7k0ZaW_iiaqfde
I get stuck on the Samsung Galaxy A50 screen.
I am basically trying to follow the directions here:
https://forum.xda-developers.com/galaxy-a50/development/recovery-twrp-galaxy-a50-t3916199
after trying to flash TWRP, I am now stuck on the Samsung screen.
I am now going back to the download screen (volume up, vol down + usc-c) and reloading the stock ROM stuff.
I can't seem to get TWRP to work - I think I may be using the wrong file.
Any suggestions on what TWRP file I should flash for a Samsung A50?
Like I mentioned above, I get stuck on the Samsung Galaxy A50 screen when I try to flash TWRP_A50_Magisk_Prepatched.tar
from here: https://drive.google.com/drive/folde...7k0ZaW_iiaqfde
any help is deeply appreciated!
doctadocta said:
after trying to flash TWRP, I am now stuck on the Samsung screen.
I am now going back to the download screen (volume up, vol down + usc-c) and reloading the stock ROM stuff.
I can't seem to get TWRP to work - I think I may be using the wrong file.
Any suggestions on what TWRP file I should flash for a Samsung A50?
Like I mentioned above, I get stuck on the Samsung Galaxy A50 screen when I try to flash TWRP_A50_Magisk_Prepatched.tar
from here: https://drive.google.com/drive/folde...7k0ZaW_iiaqfde
any help is deeply appreciated!
Click to expand...
Click to collapse
Do you have a copy of your stock boot.img and stock recovery? I'll take a look at that tar file in the mean time. You might need an updated package.
Spaceminer said:
Do you have a copy of your stock boot.img and stock recovery? I'll take a look at that tar file in the mean time. You might need an updated package.
Click to expand...
Click to collapse
Hello Spaceminer! Thanks for the support.
I ended up going back to the stock ROM using Odin ===> installing magisk patched ROM
so now I have everything up and running with root access.
Do you recommend that I do anything from here?
Should I install TWRP or CWM on the Samsung A50 even though I have root access using the patched magisk ROM method using Odin?
Thank you for the support!!
be well.
doctadocta said:
Hello Spaceminer! Thanks for the support.
I ended up going back to the stock ROM using Odin ===> installing magisk patched ROM
so now I have everything up and running with root access.
Do you recommend that I do anything from here?
Should I install TWRP or CWM on the Samsung A50 even though I have root access using the patched magisk ROM method using Odin?
Thank you for the support!!
be well.
Click to expand...
Click to collapse
Me personally, I would just for sake of making a backup. If you don't plan on modifying system files, then skipping it isn't going to hurt anything.
As I just spent like 8~hours getting my device out of bootloop.. (after trying to root + twrp...) I might as well take the time to post how I got it working.
DISCLAIMER: Only do this if you are desperate - I have no idea why this worked for me to be honest..
Here is how I managed to get my phone(A505FN btw) to boot again it:
download currently used firmware
extract boot.img + place it on external sd
Flash TWRP.tar (see roms&kernels forum section)
hold up + power while flashing until you are in TWRP
now flash boot.img for bootloader
reboot to system
IT BOOTS (I never got it passed samsung logo + text complaining about non offical firmware)
//edit
RIP it installed on SD card, anyone got any tips on how I move it onto internal?
It doesn't show internal storage anymore..
Shout outs to all the non english youtube videos about flashing android phones lmao
Im having kind of same issue but i only tried to install twrp via odin but then it got stuck on samsung logo boot loop. Later i tried creating recovery tar file and tried flashing it in odin but it wont go to the recovery mode although it came as Pass in odin and now im stuck on downloding screen fml any help is appreciated. can some please suggest my next course of action? is my phone gone>?
As far as I understand no one could manage to root sm-a505f.
Still no solution?
Sent from my [device_name] using XDA-Developers Legacy app
Spaceminer said:
Me personally, I would just for sake of making a backup. If you don't plan on modifying system files, then skipping it isn't going to hurt anything.
Click to expand...
Click to collapse
The twrp gives problems but since I rooted with just the patched bootloader in magisk and flash it with Odin. It works stable and I don't have issue's.
ebayusuff said:
As far as I understand no one could manage to root sm-a505f.
Still no solution?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
i tried but stucked at modem_debug.log. can't proceed further. go back to SC to restore the default rom.
Thinking on having magisk but not TWRP. as TWRP may cause many malfunctioning.
Does anyone know where i can find the newest security December 1, 2019 update for the g7 play? i've searched online and cannot find it anywhere. My phone keeps reminding me of a failed update so i went looking for the new one. Do i re-flash the phone to stock and update it that way before re-rooting it or wait until someone post the newest update in the mirrors repository? What do you guys suggest?
dominoeflux said:
Does anyone know where i can find the newest security December 1, 2019 update for the g7 play? i've searched online and cannot find it anywhere. My phone keeps reminding me of a failed update so i went looking for the new one. Do i re-flash the phone to stock and update it that way before re-rooting it or wait until someone post the newest update in the mirrors repository? What do you guys suggest?
Click to expand...
Click to collapse
https://support.motorola.com/us/en/Solution/MS147329
Oct 2019 seems to be the latest:
https://www.theandroidsoul.com/spri...lay-moto-g6-play-with-october-security-patch/
Normally you go back to stock, patch and then re-root.
What model do you have?
I cannot get root on my XT1952-4.
mtmtumbo said:
https://support.motorola.com/us/en/Solution/MS147329
Normally you go back to stock, patch and then re-root.
What model do you have?
I cannot get root on my XT1952-4.
Click to expand...
Click to collapse
I have the same model with boost mobile...do you need help rooting it? I just followed the instructions for the boot.img magisk patch but when you patch it make sure you select beta in magisk and in advanced settings make sure all are checked especially recovery mode before you patch and lastly when you reboot, reboot to recovery every time or the root will not stick...that's something no one mentioned when i was trying to root mine. I had to research the problem of why the root wasn't sticking. When you reboot to recovery it will stay on a blank screen and then vibrate, that's normal. It does that before it boots up. Once it's booted, check to make sure you have root by opening the magisk app, you should see both green check marks and thanks for you help with how to update.
dominoeflux said:
I have the same model with boost mobile...do you need help rooting it? I just followed the instructions for the boot.img magisk patch but when you patch it make sure you select beta in magisk and in advanced settings make sure all are checked especially recovery mode before you patch and lastly when you reboot, reboot to recovery every time or the root will not stick...that's something no one mentioned when i was trying to root mine. I had to research the problem of why the root wasn't sticking. When you reboot to recovery it will stay on a blank screen and then vibrate, that's normal. It does that before it boots up. Once it's booted, check to make sure you have root by opening the magisk app, you should see both green check marks and thanks for you help with how to update.
Click to expand...
Click to collapse
thanks, I followed the instructions as well to patch boot.img and use fastboot with magisk_patched.img, but when I rebooted, I only got the xxxxxx-xxxxxx-xxxxxxx-xxxxxxx-xxxxxx code and then no vibration and nothing else - seems stuck and just looping at this point
what do you mean select beta in magisk?
what version of apk did you create the patched img from? 7.4.0?
and yes, i made sure i checked all the advanced options (including recovery) before creating the patched img file
mtmtumbo said:
thanks, I followed the instructions as well to patch boot.img and use fastboot with magisk_patched.img, but when I rebooted, I only got the xxxxxx-xxxxxx-xxxxxxx-xxxxxxx-xxxxxx code and then no vibration and nothing else - seems stuck and just looping at this point
what do you mean select beta in magisk?
what version of apk did you create the patched img from? 7.4.0?
and yes, i made sure i checked all the advanced options (including recovery) before creating the patched img file
Click to expand...
Click to collapse
when you go in the magisk manager, select the three lines at the top left and go to settings/update channel and select beta....if you don't you will loop. i used the latest magisk version which is 7.4.0 so yes you're using the correct one. your suppose to see those codes it's normal, if the phone does not vibrate, then that means that it didn't work.
dominoeflux said:
when you go in the magisk manager, select the three lines at the top left and go to settings/update channel and select beta....if you don't you will loop. i used the latest magisk version which is 7.4.0 so yes you're using the correct one. your suppose to see those codes it's normal, if the phone does not vibrate, then that means that it didn't work.
Click to expand...
Click to collapse
Thanks, I enabled beta in magisk and tried it again and it still did not vibrate after showing the codes - just rebooting in a loop as before.
What size is your magisk_patched.img and boot.img files?
Here are mine:
33,554,432 boot.img
18,103,592 magisk_patched.img
You can see after the patching that the size of the boot image drops almost in half - is that normal?
I transfer these files using adb push and pull as I heard MTP transfers could corrupt the files.
Anyhow, since we're on the same build, can you post up your boot and patched img somewhere so I can try them?
mtmtumbo said:
Thanks, I enabled beta in magisk and tried it again and it still did not vibrate after showing the codes - just rebooting in a loop as before.
What size is your magisk_patched.img and boot.img files?
Here are mine:
33,554,432 boot.img
18,103,592 magisk_patched.img
You can see after the patching that the size of the boot image drops almost in half - is that normal?
I transfer these files using adb push and pull as I heard MTP transfers could corrupt the files.
Anyhow, since we're on the same build, can you post up your boot and patched img somewhere so I can try them?
Click to expand...
Click to collapse
Did you repatch the stock boot.img before flashing again? The magisk patch is different if not on beta and the magisk recovery is not selected, that's why it's probably still not working.
also make sure that you're patching the correct boot.img from your stock firmware that you're on, it creates problems if you're not. I can't upload my .imgs for some reason and you're correct it didn't vibrate the first time i was successful, but after i have to reboot the phone i would reboot to recovery so when the phone boots the root sticks, that's when it will vibrate.
@mtmtumbo I apologize I haven't been on here in a couple of days, any update on rooting your g7 play?
dominoeflux said:
Did you repatch the stock boot.img before flashing again? The magisk patch is different if not on beta and the magisk recovery is not selected, that's why it's probably still not working.
also make sure that you're patching the correct boot.img from your stock firmware that you're on, it creates problems if you're not. I can't upload my .imgs for some reason and you're correct it didn't vibrate the first time i was successful, but after i have to reboot the phone i would reboot to recovery so when the phone boots the root sticks, that's when it will vibrate.
Click to expand...
Click to collapse
happy new year all
yes i re-patched the stock boot.img before flashing, magisk was on beta and yes the third option in advanced for recovery was selected before i patched the boot.img
after i saw the codes and it was looping, i rebooted the phone to recovery but no difference
i'm also having a problem flashing twrp without just using fastboot boot twrp.img - flashing it with fastboot flash doesn't work (using dtbo.img first to avoid the black screen)
btw you can use mega.nz to upload your img's - give it a shot and post the URL here
if it matters, this is the ROM I'm using:
XT1952-4_CHANNEL_RETCA_9.0_PPY29.105-134_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC
mtmtumbo said:
happy new year all
yes i re-patched the stock boot.img before flashing, magisk was on beta and yes the third option in advanced for recovery was selected before i patched the boot.img
after i saw the codes and it was looping, i rebooted the phone to recovery but no difference
i'm also having a problem flashing twrp without just using fastboot boot twrp.img - flashing it with fastboot flash doesn't work (using dtbo.img first to avoid the black screen)
btw you can use mega.nz to upload your img's - give it a shot and post the URL here
if it matters, this is the ROM I'm using:
XT1952-4_CHANNEL_RETCA_9.0_PPY29.105-134_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC
Click to expand...
Click to collapse
Happy New Year man.....i believe i figured out why you're still boot looping, did you reboot back into the bootloader after you flashed the patched.img?
edit: when your doing twrp, you have to boot into it before installing it to the ramdisk. there's a how to in this forum here: https://forum.xda-developers.com/g7-play/how-to/how-to-successfully-install-twrp-g7-play-t3979701
the GSI's don't work for me so i'm waiting for a legit custom build before installing twrp again
Update 134-7
XT1952-2
ATTMX
https://mirrors.lolinet.com/firmwar...USMXLA_regulatory-XT1952-2-MEXICO_CFC.xml.zip
OpenMX
https://mirrors.lolinet.com/firmwar...EFAULT_regulatory-XT1952-2-MEXICO_CFC.xml.zip
RETAR
https://mirrors.lolinet.com/firmwar...ULT_regulatory-XT1952-2-ARGENTINA_CFC.xml.zip
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.