Develop Bugs

Cannot root marlin

I have a Pixel XL that was purchased from the google store and WAS running the latest image flawlessly (NDE63V).
i got a little frisky and decided to root, and see if some of my favorite root applications would work.
i checked "oem unlocking" in developer settings, then proceeded to boot into fastboot to unlock.
i ran the unlock command successfully, rebooted, and set my phone back up.
i then downloaded "root-marlin-pixelxl.zip" which had the latest su (SR3).
i booted into fastboot, and ran the command "fastboot boot boot-to-root.img", it completed successfully.
the device then rebooted, rebooted again, then got stuck in a bootloop. i let it sit for an hour hoping patience would fix my issue.
it never did. i held power, and force restarted the device and let it attempt to boot again (never did).
as a last resort, i booted into recovery, wiped data/reset, and attempted to boot one more time. again, it never did.
I downloaded the factory image from google (NDE63V), flashed it, and attempted root one more time.
i went through the whole process as before, even tried using the earlier boot-to-root, and still nothing. i am currently flashing my pixel xl back to stock ONE MORE TIME, and i doubt ill try to root again.
i did a search on the forums, as well as google, and couldnt find answers. i found people with similar problems, but they never received help.
Anyone have any suggestions? similar problems?

Was it with the latest fastboot tool? There are so many versions flying about, I wouldn't give up until you've made sure it's the latest from Google.
Sent from my Pixel XL using Tapatalk

DaveHTC200 said:
Was it with the latest fastboot tool? There are so many versions flying about, I wouldn't give up until you've made sure it's the latest from Google.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
My operating system is Linux Mint 18 "cinnamon" 64 bit.
i obtained the latest fastboot and adb drivers from the Google repository. i ran
>sudo apt-get update
>sudo apt-get install android-tools-fastboot android-tools-adb
when using adb and fastboot commands on my 5x and 6p, all commands are executed and work flawlessly.
i

noidea24 said:
My operating system is Linux Mint 18 "cinnamon" 64 bit.
i obtained the latest fastboot and adb drivers from the Google repository. i ran
>sudo apt-get update
>sudo apt-get install android-tools-fastboot android-tools-adb
when using adb and fastboot commands on my 5x and 6p, all commands are executed and work flawlessly.
i
Click to expand...
Click to collapse
Well if they're from Google then it's odd!!
Just because they work with the 5x and 6p doesn't mean too much because of the new boot slots with the pixel, so it's slightly different.
I'm at loss as much of you, as there isn't any reason you should have this issue
Sent from my Pixel XL using Tapatalk

ive watched a video or two and seen one difference between what i did and what others did.
after "fastboot oem unlock" i had let my phone boot back up.
i seen others run "fastboot oem unlock" and then without booting they run the "fastboot boot boot-to-root.img" before boot. then they let it boot, reboot and run the "fastboot boot boot-to-root.img" one more time.
i guess ill try it once more.

Update.
while waiting for the factory image to download (accidentally deleted it) i figured id keep ****ing with it.
quick explanations of whats happened.
unlocked bootloader
fastboot booted boot-to-root
go stuck in a bootloop
tried reset in recovery
kept bootlooping
while still bootlooping, i (just being curious) booted to bootloader, fastboot flashed elementalx, fastboot reboot'ed, got the device to power up fine.
now im tryin to boot-to-root one more time, if it doesnt work i guess ill be fine with no root with ex kernel.

noidea24 said:
Update.
while waiting for the factory image to download (accidentally deleted it) i figured id keep ****ing with it.
quick explanations of whats happened.
unlocked bootloader
fastboot booted boot-to-root
go stuck in a bootloop
tried reset in recovery
kept bootlooping
while still bootlooping, i (just being curious) booted to bootloader, fastboot flashed elementalx, fastboot reboot'ed, got the device to power up fine.
now im tryin to boot-to-root one more time, if it doesnt work i guess ill be fine with no root with ex kernel.
Click to expand...
Click to collapse
Let us / me know what happens. This is a problem a lot of peeps are having...
Thanks!
-Scott

Scott said:
Let us / me know what happens. This is a problem a lot of peeps are having...
Thanks!
-Scott
Click to expand...
Click to collapse
this has worked, refer to post #710 here
in case your lazy, ill qoute my post here...
------------------------------------------------------------------------------------
noidea24 said:
In the same boot. bootloop after fastboot booting the sr2 and sr3 boot-to-root.
i couldnt get it to stop bootlooping, so i started downloading the factory image.
while downloading i figured id mess around with it.
i took my bootlooping pixel xl, put it in bootloader mode, and fastboot flashed elementalX kernel, then fastboot reboot'ed.
oddly enough, flashing EX kernel fixed the bootloop, and it booted properly.
so now im flashing elemental, then doing the boot-to-root, to see if i cant get my pixel to boot with root.
------------------------------------------------------------------------------------------------------
this has worked!
ill tell you exactly what happened.
flashed stock, tried rooting via boot-to-root sr3, boot looped.
flashed to stock, tried rooting via boot-to-root sr2, bootlooped.
while bootlooping, i flashed the elementalX kernel, this stopped the bootloop.
i then booted back into bootloader and tried the boot-to-root while on EX kernel, and it worked flawlessly, no boot loops.
so just to be sure, i repeated my process. boot to root would always cause a bootloop on a stock device (my device)
but as long as elementalx was flashed first, boot-to-root would not cause a boot loop
tl:dr
Boot to root would not work (caused bootloop) on completley stock pixel xl
Boot to root does work as long as i flash elementalx first.
Click to expand...
Click to collapse

sorry, more information.
everything ive said before is still correct, but......
the boot-to-root is not working.
with elementalx, it does prevent the bootloop after flashing boot-to-root, but it does not root.
no superuser app is installed, and after installing the superuser app it says the su binary is not installed.
ive tried going back and flashing boot-to-root, it reboots twice, boots properly, but no su binary still.

I am in the same boat...
i used the method of flashing the elemental kernel to fix the bootloop, however, i now have the app but no binaries.

Deus_eps_machina said:
I am in the same boat...
i used the method of flashing the elemental kernel to fix the bootloop, however, i now have the app but no binaries.
Click to expand...
Click to collapse
would you do me a favor, and boot into your bootloader, and tell me the manufacturer of your "UFS" and your "DRAM"?

noidea24 said:
would you do me a favor, and boot into your bootloader, and tell me the manufacturer of your "UFS" and your "DRAM"?
Click to expand...
Click to collapse
Samsung

Deus_eps_machina said:
Samsung
Click to expand...
Click to collapse
i think that variance is part of the problem.
from the people ive asked, the only people with problems all have samsung...

noidea24 said:
i think that variance is part of the problem.
from the people ive asked, the only people with problems all have samsung...
Click to expand...
Click to collapse
i do not think thats the problem...
I just downgraded to the October build 63P and i have working root...

I think most or all the people with issues were on V and some, I think went to X and it worked.

jjayzx said:
I think most or all the people with issues were on V and some, I think went to X and it worked.
Click to expand...
Click to collapse
yep, i was on V

noidea24 said:
this has worked, refer to post #710 here
in case your lazy, ill qoute my post here...
------------------------------------------------------------------------------------
Click to expand...
Click to collapse
Good stuff!
I am totally trolling the Xl forums to see what issues peeps have (yep, I got one).
Thanks for the feedback. Made a note in my notebook :good:
-Scott

Can you keep root and move to the latest build?

noidea24 said:
Can you keep root and move to the latest build?
Click to expand...
Click to collapse
You will need to re-root

Scott said:
You will need to re-root
Click to expand...
Click to collapse
But then that's a problem, Since we are having problems rooting on the nde63v build.
I think I can sacrifice root to stay on the latest build for now.

Stuck on team win recovery project please help

I have no idea how to root or anything like that, I bought this oneplus 3 and had a update a week later.. so when I did the software update it took me into teamwin recovery mode and now I don't know how to get back into my phone please help....

Did you buy the phone second hand or did you try to flash TWRP yourself? It shouldn't have TWRP installed by default.
Regardless, you can use TWRP to flash the latest update.
Given that you have TWRP, I'm assuming that you have an unlocked bootloader. Did you notice a warning pop up everytime you reboot your phone before? It should say something along the lines of "your device has been unlocked and can't be trusted". If not, you'll have to unlock it (it wipes your phone in the process).
If the bootloader is unlocked, you can simply download and flash the latest zip for OOS 4.0.3 in TWRP. This will update you phone and replace TWRP with the stock recovery (so you don't run into this problem again in the future when installing an OTA). If you don't intend to modify your phone in any way, then this is all you need to do, your phone should be functional.
There are plenty of threads with detailed guides on how to do all of this.

I'm also stuck on TWRP after stupidly downloading the latest OTA and I don't know what to do!
Phone won't boot normal, just goes off.
Situation:
- Bootloader, Fastboot and TWRP wil load.
- Device seen by windows
- Zip install in TWRP gets stuck at 'patching zip unconditiontally'
- Another zip flashes, but gets stuck at the end, no reboot option (manually but that's not the way)
Can someone please point me in the right direction? I don't care if I lose data, just want my phone back!
not helping:
Saying i'm a dipsh-t I know, I know, I will do better in the future, for now, help a brother out please

sndr1384 said:
I'm also stuck on TWRP after stupidly downloading the latest OTA and I don't know what to do!
Phone won't boot normal, just goes off.
Situation:
- Bootloader, Fastboot and TWRP wil load.
- Device seen by windows
- Zip install in TWRP gets stuck at 'patching zip unconditiontally'
- Another zip flashes, but gets stuck at the end, no reboot option (manually but that's not the way)
Can someone please point me in the right direction? I don't care if I lose data, just want my phone back!
not helping:
Saying i'm a dipsh-t I know, I know, I will do better in the future, for now, help a brother out please
Click to expand...
Click to collapse
Simple, check the OnePlus D/L sites for this one http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img and flash it by TWRP or fastboot to RECOVERY. Boot once with the official Recovery and all ist fine again.

This is issue of using a faulty twrp so for that when ur phone us booting up go to fastboot and flash twrp 3.0.4-1 and everything will work

emuandco said:
Simple, check the OnePlus D/L sites for this one http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img and flash it by TWRP or fastboot to RECOVERY. Boot once with the official Recovery and all ist fine again.
Click to expand...
Click to collapse
Similar Problem here:
just wanted to flash latest OOS 4.0.3, so I flashed back stock recovery with flashify and rebooted into recovery mode to flash the already downloaded OOS 4.0.3. zip. That's when it began to go poop! After rebooting it just went dark with no Chance to power it on again! No dice with power button, Volume up/down + power button, nothing! Not even the LED's are blinking when plugged in. So this one seems to be basically dead!
I got it once booting again after randomly pushing the buttons (after x minutes!?), but everytime I reboot the phone it just shuts off without beeing able to power it on again. At the Moment it's dead!
Any ideas what might happened? If I get it on again, should I immediately reset it to factory Settings?
I am kinda lost here! Any help/ideas would be much appreciated!

Flashify? Never used it and never trusted apps which flash stuff on a running system. Use fastboot and reflash the recovery partition. Link to recovery is in my former post.
fastboot flash recovery PATHTOIMGFILE

Thank you for your advice! Still a lot to learn! Got it up again, will try as you suggested!

It appeared that my stock recovery file was corrupted , but all is fine again! Thank you very much!

Mannycolon85 said:
I have no idea how to root or anything like that, I bought this oneplus 3 and had a update a week later.. so when I did the software update it took me into teamwin recovery mode and now I don't know how to get back into my phone please help....
Click to expand...
Click to collapse
I may have been the person you traded with to get the OnePlus 3, but I took the phone back and after 5 hours I got it up and running.
The phone would boot to TWRP, but even after wiping the entire system and dragging a ROM zip to the internal storage, reinstalling did nothing. It just kept booting back to recovery.
The solution entailed the following.
Download stock recovery IMG. Flashed through TWRP. Rebooted recovery and now was back to stock recovery.
Download the official OxygenOS ROM zip from the OnePlus website and changed the name to update.zip
Next I downloaded Android studio for access to ADB. I had never used ADB before, but I knew this was needed to push a file to the phone.
Needless to say, ADB kept freezing my computer when I would type in the commands to side load.
I deleted Android studio and installed a minimal ADB/Fastboot I found online. I opened my command prompt, typed the command for sideloading, and immediately got my installation starting. It took about 10 minutes to fully install. When it was finished, I rebooted and had a fully functioning OnePlus 3
Sent from my ONEPLUS A3000 using Tapatalk

various issues with google variant

I've had Google phones for years now, including previous Pixel, but I just got an XL 2 yesterday and I'm regretting it.
It's Google unlocked and running June's latest image. I've experienced various app crashing on stock, and random reboots.
Then there's the rooting and flashing. I unlocked the bootloader and installed the most recent, twrp (the one verified to work on xda for roms) but can't flash anything.
My twrp either hangs on the twrp start screen, or when it does load, the touch screen doesn't work. When I can get it going, every rom I flash gives me an error on the second step. I'm flashing on slot B by the way, that's what boots up when I boot to twrp.
Lastly, I am unlocked both for flashing and flashing_critical thru adb, so I'm at a loss and seriously confused.
When I FIRST unlocked everything, I was able to flash Nitrogen rom but I got stuck at the rom splash screen.
Tldr:
-What is the Correct install method/sequence for roms?
-do the slots matter?
-is random reboots and app crashing on stock a sign of a hardware issue?

I haven't installed a custom ROM on my P2XL, so I'm running rooted stock. Anyway, for rooted stock, this is what I did.
Entered bootloader mode.
Booted into recovery using the command "fastboot boot recovery.img", where "recovery.img" is the TWRP recovery iteslf. In my case, I renamed it "taimen.img".
Flashed the TWRP installer zip needed for the P2XL (Required if intending to replace the stock recovery).
Rebooted into recovery.
Flashed a custom kernel (Recommended - resolves touch issues in TWRP).
Flashed Magisk.
6. Rebooted.
If installing a custom ROM, flash it prior to the custom kernel. Slots only matter if running stock. Random reboots and app crashes are not signs of a hardware issue.

stevew84 said:
I've had Google phones for years now, including previous Pixel, but I just got an XL 2 yesterday and I'm regretting it.
It's Google unlocked and running June's latest image. I've experienced various app crashing on stock, and random reboots.
Then there's the rooting and flashing. I unlocked the bootloader and installed the most recent, twrp (the one verified to work on xda for roms) but can't flash anything.
My twrp either hangs on the twrp start screen, or when it does load, the touch screen doesn't work. When I can get it going, every rom I flash gives me an error on the second step. I'm flashing on slot B by the way, that's what boots up when I boot to twrp.
Lastly, I am unlocked both for flashing and flashing_critical thru adb, so I'm at a loss and seriously confused.
When I FIRST unlocked everything, I was able to flash Nitrogen rom but I got stuck at the rom splash screen.
Tldr:
-What is the Correct install method/sequence for roms?
-do the slots matter?
-is random reboots and app crashing on stock a sign of a hardware issue?
Click to expand...
Click to collapse
Ya know my friend, after our conversation yesterday, and your questions in the nitrogen thread, and now random reboots and app crashes, I think it's time to consider a factory reset. You shouldn't be having those problems on a stock setup. If that's not successful, then I would definitely consider an RMA. Just my 2 cents worth :good:

I agree. I got it used tho which is an issue.

Badger50 said:
Ya know my friend, after our conversation yesterday, and your questions in the nitrogen thread, and now random reboots and app crashes, I think it's time to consider a factory reset. You shouldn't be having those problems on a stock setup. If that's not successful, then I would definitely consider an RMA. Just my 2 cents worth :good:
Click to expand...
Click to collapse
Just so you know, I got the rom to flash finally, but it's stuck at the rom splash screen during first boot. I'm going to leave it and hope it eventually boots up.

stevew84 said:
Just so you know, I got the rom to flash finally, but it's stuck at the rom splash screen during first boot. I'm going to leave it and hope it eventually boots up.
Click to expand...
Click to collapse
If it doesn't after 5 minutes, do a hard restart with the power button. If that doesn't work, then reboot to twrp and flash the rom and twrp installer zip again.

Ok cool thanks. I relocked bootloader last night and went back to stock. Unlocked it all this morning from my work computer and different unlock app. So here's hoping.

Badger50 said:
If it doesn't after 5 minutes, do a hard restart with the power button. If that doesn't work, then reboot to twrp and flash the rom and twrp installer zip again.
Click to expand...
Click to collapse
I finally got everything to work. My vendor image is a mismatch but I could just flash junes and be done with it, right?

stevew84 said:
I finally got everything to work. My vendor image is a mismatch but I could just flash junes and be done with it, right?
Click to expand...
Click to collapse
What did you do to get it to work? You could just flash the June vendor.img to both slots. If you keep getting a vendor mismatch, probably nothing to worry about according to the Dev of nitrogen.

Different machine, cable and unlocking tool.
But I went to bone stock with locked bootloader, then flashed the newest twrp with the newest all in one tool. Was on slot A so wiped everything and flashed rom plus twrp again. I rebooted system to slot B, but then it just hung at the rom splash screen.
So I did it all over on slot A, ignored the "no os installed" message and booted anyway. Then it fired up. Rebooting into twrp from there took me to B, which is where I need to be for an image file or root.
So yea, thanks for the help.

I'm having this issue also. I tried flashing nitrogen, it hung. I tried to go back with factory reset Img and nothing happens in adb. Flashed the may img and it wouldn't boot all the way up. Now I'm stuck in bootloader trying to figure this all out. Seems like nothing in doing is working. I can get recovery to boot, but no files inside so idk. Tried to sideloadb nitrogen, but it said adb out of date for device when sdk is fully updated.

MatthewRobinson said:
I'm having this issue also. I tried flashing nitrogen, it hung. I tried to go back with factory reset Img and nothing happens in adb. Flashed the may img and it wouldn't boot all the way up. Now I'm stuck in bootloader trying to figure this all out. Seems like nothing in doing is working. I can get recovery to boot, but no files inside so idk. Tried to sideloadb nitrogen, but it said adb out of date for device when sdk is fully updated.
Click to expand...
Click to collapse
You didn't mention the out of date message in your other post, but uninstall SDK and then download the stand-alone adb/fastboot binaries from May of this year. Dump that in a folder (eg. c:\adb) and put that folder in your path statement. Manually flash the full factory image without modifying flash-all.bat. Post your screeen if you have any errors. :good:

stevew84 said:
I agree. I got it used tho which is an issue.
Click to expand...
Click to collapse
Google knows the date the phone was purchased based on imei number and honors their warranty by date, not owner. Unless it was blacklisted.

smartymcfly said:
Google knows the date the phone was purchased based on imei number and honors their warranty based on that.
Click to expand...
Click to collapse
Thanks. I might try to take advantage.

pixel xl stuck in bootloop after trying to install twrp!

Someone please help me, im really worried i bricked my new phone. I just got this phone about two weeks ago.
So i unlocked my bootloader a few days ago and now since its the weekend i decided i would try to do some more modding with my phone. Well i followed all instructions to the T and now im stuck in a bootloop and not able to access recovery mode. Im worried that when it does run out of battery, which is going to take forever. That as soon as i give it power it will go back into the bootloop. Someone please give me some advice on how to alleviate this issue.

Did you relock the bootloader ?

no i didnt. i was able to get the phone to turn off by holding the power button down for a longtime. so i got it figured out. still would like to install twrp but now im kinda freaked out lol.

Get the SDK tools, download twrp for marlin and the zip, boot to bootloader, fastboot twrp, move the installer zip to the phone, flash it like normal in twrp

Oh yeah good point. Do not flash TWRP in fastboot, you have to fastboot boot into TWRP. And flash TWRP from within itself (TWRP recovery)

okay yeah ive been having a hell of a time trying to get twrp installed i just cant get it going. how do you fastboot twrp?

Go to this thread: [Guide] Pixel XL Android 8.1.0 (OREO) Unlock/Lock Bootloader + Install Stock Images/Custom kernels/TWRP Recovery/Systemless ROOT + June Security Patch
Do #4 then #7.

I've had some boothangs - not loops, but I'm wondering if it might be related to disabling the rapid charge? I keep seeing this repeated in the logcat when it's frozen"
06-27 09:31:54.937 695 695 W /system/bin/thermalserviced: Waited one second for [email protected]::IThermal/default. Waiting another...
06-27 09:31:55.512 1156 1156 W zygote64: Waited one second for [email protected]::IThermal/default. Waiting another...
Click to expand...
Click to collapse
The mentioning of the thermal makes me think of a possible relationship to heat and rapid charging... but I'm no engineer.

I encountered this problem after messing with my hosts file and thought I would post my solution even though this was for the pixel 2 just in case anyone else is searching for the same problem. To get it to boot again I flashed the factory boot image in fastboot. I then patched the factory boot image with magisk manager and manually flashed this in fastboot. The phone then booted up fine. This still happens occasionally on reboot when I make changes, but repeating the process gets it to boot up again.

Help, might have killed my device

Not 100% sure of best place to post this, but I'm getting desperate now...
I'm pretty worried I've killed my device. After following the guide on how to root with Magisk, my phone is stuck on the white "loading" screen with a G logo. I've since tried to restart, but I can either go into fastboot mode or get the white screen when attempting to boot into android.
Tried to flash the latest factory image to fix it, but that couldn't get that to work. Now the phone isn't showing up on adb devices either. panicking a little bit here.
Does anyone know what to do?

ADB won't work unless the phone is booted into Android or in stock recovery for a sideload.
Does your computer recognize the device when you are in Fastboot mode and type "fastboot devices"? Try flashing the factory image again but make sure you have the most up to date platform tools from Google. Old versions are a common cause of issues.
Did you flash TWRP recovery or just boot to it to root? If you still have stock recovery you can try a factory reset from there but any modified images you installed might be the issue.

like Fury said, your platform tools need to be updated, same thing happened to me.

What didn't work when you flashed the factory image? Do you have the latest sdk tools version of fastboot and adb?
Sent from my [device_name] using XDA-Developers Legacy app

fury683 said:
ADB won't work unless the phone is booted into Android or in stock recovery for a sideload.
Does your computer recognize the device when you are in Fastboot mode and type "fastboot devices"? Try flashing the factory image again but make sure you have the most up to date platform tools from Google. Old versions are a common cause of issues.
Did you flash TWRP recovery or just boot to it to root? If you still have stock recovery you can try a factory reset from there but any modified images you installed might be the issue.
Click to expand...
Click to collapse
Thanks so much, this is where I was going wrong. Have gone into recovery and rescued it.
Tried the process again to get Magisk working, but ended up the same although this time the white screen only went on for a while before I got an error saying my data was corrupted. Tbh, after all the stress I'm just going to give up on this and live with the phone in stock. All my drivers and adb were installed and setup today, so everything is up to date.
edit...
Not out of the woods yet. After restarting the phone and going through the setup, it's not detecting the SIM card or any wifi networks. I've installed the OTA and wiped data once more after having this problem, still not resolved.

Nick676 said:
Thanks so much, this is where I was going wrong. Have gone into recovery and rescued it.
Tried the process again to get Magisk working, but ended up the same although this time the white screen only went on for a while before I got an error saying my data was corrupted. Tbh, after all the stress I'm just going to give up on this and live with the phone in stock. All my drivers and adb were installed and setup today, so everything is up to date.
Thanks again for helping.
Click to expand...
Click to collapse
It sounds like you are trying to install Magisk v17.1 like I tried. If so you need to use v17.3 beta. If you follow this thread you should be fine. It even tells you what to do for your original problem, just takes some reading and patience.

Misterxtc said:
It sounds like you are trying to install Magisk v17.1 like I tried. If so you need to use v17.3 beta. If you follow this thread you should be fine. It even tells you what to do for your original problem, just takes some reading and patience.
Click to expand...
Click to collapse
I tried it with both 17.1 and 17.3, so not sure what the issue is. Seem to have finally booted up properly with wifi and signal working, so hopefully it's all good now. Gonna give up on rooting.

Nick676 said:
Not 100% sure of best place to post this, but I'm getting desperate now...
I'm pretty worried I've killed my device. After following the guide on how to root with Magisk, my phone is stuck on the white "loading" screen with a G logo. I've since tried to restart, but I can either go into fastboot mode or get the white screen when attempting to boot into android.
Tried to flash the latest factory image to fix it, but that couldn't get that to work. Now the phone isn't showing up on adb devices either. panicking a little bit here.
Does anyone know what to do?
Click to expand...
Click to collapse
you may want to try to totally uninstalling Magisk frist with the official latest Magisk uninstaller and reboot and then do a complete factory reset. this has helped me in the past.
my new pixel 3XL will be the first Android phone that I owned that will not be rooted.