My Google Pixel XL(NJH47B) has been stuck in the Paranoid Android boot animation for nearly two hours now. I followed teamandroid.com's guide to unlocking the bootloader and rooting my phone. It worked. I then installed PA using twrp using this KDCloudy's youtube tutorial uploaded on un 22, 2017 (I can't post links. sorry.). This also worked. My problems began when I attempted to root my phone using the same tutorial I followed before successfully installing PA. After installing SuperSU I rebooted my phone. When I attempted to reboot my phone I was taken to a screen that says "Your device software can't be checked for corruption. Please lock the bootloader.". When I pressed the power button to continue the booting I saw the google logo for 1-2 seconds and then I was taken to a ramdump screen. When I pressed the volume up and volume down button I was taken back to the previous screen. I didn't know what to do and ended up installing PA again. I followed the youtube tutorial's instructions once again and was greeted with the same screen telling me to lock the bootloader. When I wait for the screen to do disappear or if I press the power button I go into the PA boot animation. I've been in the PA boot animation for more than two hours now. I can go to the ramdump screen and from there I could access the bootloader. I'm fairly new to this. Any help would be greatly appreciated.
The message telling you to lock the bootloader is completely normal if you are using the phone with an unlocked bootloader, which you need to do if you are rooted or running a custom ROM. You should have ignored that screen and ignored the power dump message and given the phone enough time to boot up. I would completely power down the phone. Give it a minute and try to boot up again ignoring any messages that might pop up. If your phone isn't booted up after 5 minutes the easiest thing to do is start over. Download the latest Google factory image from Google's website. Flash it using the flash-all.bat command. After you are successfully booted up on stock start over with booting into temp TWRP, flash TWRP zip, flash PA zip, flash SU zip and boot up ignoring any messages you see. After you have successfully booted into PA go back into the bootloader again, go into the temp version of TWRP again, flash the TWRP zip again and boot back into PA again. If you don't boot into your rom once and then flash the TWRP zip again your custom recovery will disappear and you will be back to factory recovery. You should be fine. It's pretty near impossible to hard brick this phone.
Jiantou said:
My Google Pixel XL(NJH47B) has been stuck in the Paranoid Android boot animation for nearly two hours now. I followed teamandroid.com's guide to unlocking the bootloader and rooting my phone. It worked. I then installed PA using twrp using this KDCloudy's youtube tutorial uploaded on un 22, 2017 (I can't post links. sorry.). This also worked. My problems began when I attempted to root my phone using the same tutorial I followed before successfully installing PA. After installing SuperSU I rebooted my phone. When I attempted to reboot my phone I was taken to a screen that says "Your device software can't be checked for corruption. Please lock the bootloader.". When I pressed the power button to continue the booting I saw the google logo for 1-2 seconds and then I was taken to a ramdump screen. When I pressed the volume up and volume down button I was taken back to the previous screen. I didn't know what to do and ended up installing PA again. I followed the youtube tutorial's instructions once again and was greeted with the same screen telling me to lock the bootloader. When I wait for the screen to do disappear or if I press the power button I go into the PA boot animation. I've been in the PA boot animation for more than two hours now. I can go to the ramdump screen and from there I could access the bootloader. I'm fairly new to this. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Go into TWRP and do a factory reset.
Once in a while when flashing a new ROM, I get stuck in the ROM's first boot process.
A factory reset always seems to cure that.
I flashed the stock image, enabled USB debugging, added SU and TWRP, and booted into TWRP. I flashed the TWRP zip, went back, flashed Ressurection Remix(not PA), went back, and flashed the SU zip. I rebooted. I am stuck in the RR boot animation. It's not looping, it's just been loading for two hours. I know how to get out though. I just would like to know what I've been doing wrong.
Jiantou said:
I flashed the stock image, enabled USB debugging, added SU and TWRP, and booted into TWRP. I flashed the TWRP zip, went back, flashed Ressurection Remix(not PA), went back, and flashed the SU zip. I rebooted. I am stuck in the RR boot animation. It's not looping, it's just been loading for two hours. I know how to get out though. I just would like to know what I've been doing wrong.
Click to expand...
Click to collapse
You're flashing the latest stock image and not the one from May, correct? There was a problem with SU and the May bootloader where the phone would bootloop if you didn't also flash an additional boot signature file. If that isn't your problem it still seems to be SU related since both times you bootlooped after flashing that file. Maybe there is a problem with the actual SU file you are flashing.
http://forum.supersu.com/topic/152/supersu-v2-82-release
I would try downloading it again.
jhs39 said:
You're flashing the latest stock image and not the one from May, correct? There was a problem with SU and the May bootloader where the phone would bootloop if you didn't also flash an additional boot signature file. If that isn't your problem it still seems to be SU related since both times you bootlooped after flashing that file. Maybe there is a problem with the actual SU file you are flashing.
http://forum.supersu.com/topic/152/supersu-v2-82-release
I would try downloading it again.
Click to expand...
Click to collapse
That's the one I've been using. I successfully installed Ressurection Remix but I'm still not rooted. I installed that file twice and booted successfully but I'm still not rooted.
Jiantou said:
That's the one I've been using. I successfully installed Ressurection Remix but I'm still not rooted. I installed that file twice and booted successfully but I'm still not rooted.
Click to expand...
Click to collapse
Are you sure you even need to be rooted? Are you still in a bootloop or can you boot into Ressurection Remix?
As an alternative you could try the Pixel modified version of Magiisk to root. The official version doesn't work on the Pixel. But the shortcut for the modified Magisk version is actually in the Resurrection Remix rom thread.
You also mentioned flashing gapps but the Resurrection Remix flashing instructions say gapps are already built into the rom. You don't want to flash a gapps zip if gapps are built into the rom.
Resurrection Remix has pretty detailed flashing instructions. If you follow them you should be ok.
---------- Post added at 08:48 AM ---------- Previous post was at 08:40 AM ----------
Look at the last post in this thread if you decide to try Magisk:
https://forum.xda-developers.com/pixel-xl/help/magisk-adaway-root-help-t3631249
Also uninstall SU if you have it installed. It's not compatible with Magisk. You can uninstall SU using the free SU Manager app from the Play Store. I'm assuming you already have that app if you tried to root with SU because you need the SU manager app and the SU zip in order to manage root.
Related
Hi,
there are several threads on this forum dealing with nexus devices that get stuck at the google logo when booting up, however my case is a little different:
I can not even get into recovery.
Here's the symptoms:
The touchscreen became unresponsive. I read that fixing the cache partition helps and it did.
From time to time my device would get stuck at google logo on boot, but i was still able to get into recovery, wipe cache and it would work again. This happened 2-3 times over the course of the last 3 weeks maybe, so i thought its just some minor hangup
2 days ago the device became unresponsive again and i was unable to get into recovery. I have tried several times and once i was lucky to get into recovery (it showd google logo, but when i pressed the power button to turn it off i got into recovery)
now nothing will work. i can get into the bootloader no problem and fastboot is in a working condition
i have tried flashing the factory image using the files provided by google. So far no success
Does anyone know something else to try?
EDIT: aniket0317 suggested using Wugfresh's Root Toolkit which includes a script to unbrick in case of bootloops. That seems to have worked.
Flashing back to stock is a first step, to ensure it's nothing in the software. What do you mean by "So far no success"?
Use Wugfresh's Nexus Root Toolkit. There is a option named Stock Flash+Unroot (Bootloop). The device should be able to get into fastboot mode, though.
aniket0317 said:
Use Wugfresh's Nexus Root Toolkit.
Click to expand...
Click to collapse
This seems to have done it. I have followed the instructions in the toolkit and rebooted the device several times already successfully. The next days will tell whether the touchscreen freezes still happen. But for now, thank you.:good:
mistermabuse said:
This seems to have done it. I have followed the instructions in the toolkit and rebooted the device several times already successfully. The next days will tell whether the touchscreen freezes still happen. But for now, thank you.:good:
Click to expand...
Click to collapse
Press thanks if I helped you
Sent from my Nexus 7 using Tapatalk
Same problem
Hey,
my Nexus 7 2013 has the same error.
Im stuck in Google screen, only enter in fastboot mode.
Tried Nexus Root Toolkit and other methods but stays the same...
In TWRP, touchscreen doesnt work.
What can i do???
Thanks!
Hey thiago,
I don't really know what to do, but I have the same problem now...
I guess it should be possible to somehow boot clockworkmod recovery from fastboot,
but I'm not sure.
I'll mark this thread not solved again -.-
mistermabuse said:
Hi,
there are several threads on this forum dealing with nexus devices that get stuck at the google logo when booting up, however my case is a little different:
I can not even get into recovery.
Here's the symptoms:
The touchscreen became unresponsive. I read that fixing the cache partition helps and it did.
From time to time my device would get stuck at google logo on boot, but i was still able to get into recovery, wipe cache and it would work again. This happened 2-3 times over the course of the last 3 weeks maybe, so i thought its just some minor hangup
2 days ago the device became unresponsive again and i was unable to get into recovery. I have tried several times and once i was lucky to get into recovery (it showd google logo, but when i pressed the power button to turn it off i got into recovery)
now nothing will work. i can get into the bootloader no problem and fastboot is in a working condition
i have tried flashing the factory image using the files provided by google. So far no success
Does anyone know something else to try?
EDIT: aniket0317 suggested using Wugfresh's Root Toolkit which includes a script to unbrick in case of bootloops. That seems to have worked.
Click to expand...
Click to collapse
EDIT 2: Yes it worked, at first. Now the device is stuck in a bootloop again. I can boot into team win recovery, but touch doesn't work there so I can't do anything. Booting CWM from fastboot is also not suceessful.
What do you mean CWM is not successful, that there's no touch response? If all else fails, you can use the non-touch version of CWM, using the side buttons to navigate. But I'd be concerned if screen touches are not being recognized.
CWM dont start. Only twrp. Is there a TWRP non touch version?
There's no non-touch version of TWRP that I know of, since its design is based on touch.
What do you mean by CWM won't start? It just freezes? Did you flash the correct one?
6.0.4.3 for regular N7 2013: http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.7-flo.img
6.0.4.8 for N7 2013 LTE: http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.8-deb.img
6.0.4.3 for N7 2013 GSM: http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.3-tilapia.img
still frozen
Pandae said:
There's no non-touch version of TWRP that I know of, since its design is based on touch.
What do you mean by CWM won't start? It just freezes? Did you flash the correct one?
[/url]
Click to expand...
Click to collapse
Yes, i used this version for Regular N7 2013, but still frozen in the google screen.
I have the same problem.
Stuck on google logo. It boots Fastboot only. It does not boot system or recovery.
What I have done so far:
Unlocked the bootloader
Flashed preview android L successfully But it did not boot. Then i Installed android 4.4.4. Successfully But still nothing. Then i flashed android 4.3 with the same result. Lastly i flashed TWRP to try and flash a zip, but again it does not go past the google logo. Everything i flash goes successfully or at least there are no errors on the logs. I have used wugs nexus toolkit to flash everything. I can see the bootloader version being changed after flashing different android versions, so i can confirm it is flashing bootloader at least.
My conclusion:
I think there is a hardware problem but I don't know how to troubleshoot what is wrong.
If anyone has any suggestion. It will be much appreciated.
Sent from my SM-G900F using XDA Premium HD app
Send it back to Google
gopin said:
I have the same problem.
Stuck on google logo. It boots Fastboot only. It does not boot system or recovery.
What I have done so far:
Unlocked the bootloader
Flashed preview android L successfully But it did not boot. Then i Installed android 4.4.4. Successfully But still nothing. Then i flashed android 4.3 with the same result. Lastly i flashed TWRP to try and flash a zip, but again it does not go past the google logo. Everything i flash goes successfully or at least there are no errors on the logs. I have used wugs nexus toolkit to flash everything. I can see the bootloader version being changed after flashing different android versions, so i can confirm it is flashing bootloader at least.
My conclusion:
I think there is a hardware problem but I don't know how to troubleshoot what is wrong.
If anyone has any suggestion. It will be much appreciated.
Click to expand...
Click to collapse
What if you flashed the stock factory recovery/ROM, or is that what you mean by 4.4.4 and 4.3? Don't use a recovery to flash the individual .img files, just run flash-all.bat and see what it does.
https://developers.google.com/android/nexus/images
Pandae said:
What if you flashed the stock factory recovery/ROM, or is that what you mean by 4.4.4 and 4.3? Don't use a recovery to flash the individual .img files, just run flash-all.bat and see what it does.
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Yes. I flashed the factory images using wugs nexus toolkit and ticked the option flash stuck + unroot (bricked or bootlooping) to see if it would work as mentioned by OP. All factory images flash successfully all partitions, but it does not boot recovery or system. I tried different android versions hoping it would make a difference and tried booting recovery after flashing each image (4.4.4 and 4.3). I haven't tried typing the command flash all.bat myself to flash the image as you suggested. I've used the toolkit to make it easier. I'll try flashing stock typing command flash all.bat myself and report.
Sent from my SM-G900F using XDA Premium HD app
Use your warranty, send it back to Google.
So after a few months of being on a older fw that i rooted i decided to update. Downgraded fw, re-rooted, unlocked bootloader, installed clockworkmod recovery. Finally the last step - adb latest custom rom and reboot. Did the install via cwm and it failed.
Rebooted and now stuck at the amazon logo. I tried the usb keyboard trick a few times( printscr,alt,i) but mine seems to boot very fast directly to black screen with amazon logo. So at this point not sure if any way to recover....any ideas?
ugabuga said:
So after a few months of being on a older fw that i rooted i decided to update. Downgraded fw, re-rooted, unlocked bootloader, installed clockworkmod recovery. Finally the last step - adb latest custom rom and reboot. Did the install via cwm and it failed.
Rebooted and now stuck at the amazon logo. I tried the usb keyboard trick a few times( printscr,alt,i) but mine seems to boot very fast directly to black screen with amazon logo. So at this point not sure if any way to recover....any ideas?
Click to expand...
Click to collapse
If it failed to flash... you rebooted because... The only way to get back to recovery is the printscreen method, but because you have a corrupt system, it's not going to be easy to trigger it.
ugabuga said:
So after a few months of being on a older fw that i rooted i decided to update. Downgraded fw, re-rooted, unlocked bootloader, installed clockworkmod recovery. Finally the last step - adb latest custom rom and reboot. Did the install via cwm and it failed.
Rebooted and now stuck at the amazon logo. I tried the usb keyboard trick a few times( printscr,alt,i) but mine seems to boot very fast directly to black screen with amazon logo. So at this point not sure if any way to recover....any ideas?
Click to expand...
Click to collapse
I had this same issue, I attempted to install using the sideload command and it kept failing. To get the update to install, I pushed the update to the /sdcard/0 and installed from there, and it installed with no dramas.
No help on recovering your device though, just my experience in case it happens again.
Thanks for replies... I guess I'll try to get back into recovery again tonight. When pressing the 3 kb buttons... is it press and hold immediately after plugging the ftv on or is it repeatedly pressing all 3 buttons? If I do trigger recovery and restore, what actually gets restored? Is the the prior working version? Do I need to worry about it updating an losing root?
Btw I did push the rom to /sdcard/0 so not sure why it failed maybe bad download.
So I rooted my sgh-m919 (m919uvuemk2) running android 4.3. Root went fine, but I couldn't get TWRP (2.8.7.0) installed. Anytime I tried to boot into it, it would just boot normally. Thinking it was knox messing with the firmware boot, I uninstalled it. It seemed to uninstall fine but when I tried to get into recovery/download mode while holding the buttons it flashed the android screen then rebooted normally.
Then I installed andromizer and was finally able to get to TWRP. So I installed cyanogenmod 12.1 fine, but gapps failed (error code 70). So i've lost root. And my phone still can't get into download mode. Flashes and boots normally. Doesn't seem like a hard or soft brick situation, but I don't really know. I wasn't able to find any forums that fit this description.
Any ideas or recommendations on what I should do?
Any help greatly appreciated... thank you!
slungshot said:
So I rooted my sgh-m919 (m919uvuemk2) running android 4.3. Root went fine, but I couldn't get TWRP (2.8.7.0) installed. Anytime I tried to boot into it, it would just boot normally. Thinking it was knox messing with the firmware boot, I uninstalled it. It seemed to uninstall fine but when I tried to get into recovery/download mode while holding the buttons it flashed the android screen then rebooted normally.
Then I installed andromizer and was finally able to get to TWRP. So I installed cyanogenmod 12.1 fine, but gapps failed (error code 70). So i've lost root. And my phone still can't get into download mode. Flashes and boots normally. Doesn't seem like a hard or soft brick situation, but I don't really know. I wasn't able to find any forums that fit this description.
Any ideas or recommendations on what I should do?
Any help greatly appreciated... thank you!
Click to expand...
Click to collapse
I think you may have some terms confused.
To get into Download Mode: Turn off your phone, then turn it on and hold down the Volume Down button. You will get a screen that starts with "Warning!!", and where you can press Volume Up to Continue, or Volume Down to Cance.
To get into Recovery Mode: Turn off your phone, then turn it on and hold down the Volume Up button. You will get some small text at the top left of the screen, and then whichever Recovery you have installed in the Recovery partition will run.
You use Download mode to flash using ODIN.
To get something into the Recovery partition, you can flash using ODIN, or if you are rooted, you can use an app like the TWRP Manager app, and some others.
Also, there isn't an official 2.8.7.0 TWRP. The latest is 2.8.4.0 which may be most/part of your issue.
Getting root is very easy on the SGH-M919, just use the CF-AutoRoot app. But, you don't need root to flash TWRP with ODIN. Also, almost every non-stock ROM will come pre-rooted. So, if you have flashed a CM rom, you are rooted. But, you may need to download SuperSU from the app store.
Rob
Hi Rob, Thanks for the reply. My problem is I hold down the buttons but they no longer boot me into recovery, the android recovery screen flashes for a sec, then boots normally.
I may have found a workaround though, it seems I can now do a recovery option from the power down menu, and that boots me into TWRP. Not sure why the buttons no longer get me into the recovery console, but this may work.
Funny thing is I lost root after installing cm 12.1 while rooted. I think I may downgrade to kit kat because it seems like lollipop drains the battery much faster.
rlichtefeld said:
I think you may have some terms confused.
To get into Download Mode: Turn off your phone, then turn it on and hold down the Volume Down button. You will get a screen that starts with "Warning!!", and where you can press Volume Up to Continue, or Volume Down to Cance.
To get into Recovery Mode: Turn off your phone, then turn it on and hold down the Volume Up button. You will get some small text at the top left of the screen, and then whichever Recovery you have installed in the Recovery partition will run.
You use Download mode to flash using ODIN.
To get something into the Recovery partition, you can flash using ODIN, or if you are rooted, you can use an app like the TWRP Manager app, and some others.
Also, there isn't an official 2.8.7.0 TWRP. The latest is 2.8.4.0 which may be most/part of your issue.
Getting root is very easy on the SGH-M919, just use the CF-AutoRoot app. But, you don't need root to flash TWRP with ODIN. Also, almost every non-stock ROM will come pre-rooted. So, if you have flashed a CM rom, you are rooted. But, you may need to download SuperSU from the app store.
Rob
Click to expand...
Click to collapse
slungshot said:
Hi Rob, Thanks for the reply. My problem is I hold down the buttons but they no longer boot me into recovery, the android recovery screen flashes for a sec, then boots normally.
I may have found a workaround though, it seems I can now do a recovery option from the power down menu, and that boots me into TWRP. Not sure why the buttons no longer get me into the recovery console, but this may work.
Funny thing is I lost root after installing cm 12.1 while rooted. I think I may downgrade to kit kat because it seems like lollipop drains the battery much faster.
Click to expand...
Click to collapse
If TWRP 2.8.70 is not functioning correctly, then please try the last stable version: 2.8.4.0.
See the thread here: http://forum.xda-developers.com/showthread.php?t=2263001&page=61
I run 2.8.4.0, and the buttons work and TWRP Manager works, etc.
CM12 comes pre-rooted - all non-stock ROMs do. You may have lost the SuperSU app when you flashed, but that can be downloaded from the app store.
Rob
Thanks Rob. I figured out that I was still able to reboot into recovery without buttons so I just went that route. Where did you get the 4.4.4 rom? I can't find anything on the cyanogen site other than snapshot 4.4.2, which I installed last night trying to solve my problem of when someone calls they hear a wicked echo.
rlichtefeld said:
If TWRP 2.8.70 is not functioning correctly, then please try the last stable version: 2.8.4.0.
See the thread here: http://forum.xda-developers.com/showthread.php?t=2263001&page=61
I run 2.8.4.0, and the buttons work and TWRP Manager works, etc.
CM12 comes pre-rooted - all non-stock ROMs do. You may have lost the SuperSU app when you flashed, but that can be downloaded from the app store.
Rob
Click to expand...
Click to collapse
slungshot said:
Thanks Rob. I figured out that I was still able to reboot into recovery without buttons so I just went that route. Where did you get the 4.4.4 rom? I can't find anything on the cyanogen site other than snapshot 4.4.2, which I installed last night trying to solve my problem of when someone calls they hear a wicked echo.
Click to expand...
Click to collapse
SamMobile has all the Stock firmwares for all the Samsung phones. However, their downloads can be a little slow.
Luckily, ShinySide on this forum in the General Section has this thread with fast downloads:
http://forum.xda-developers.com/galaxy-s4-tmobile/general/firmwares-official-mdl-mk2-nb4-t2816508
Flashing 4.4.4 will get you the most recent firmware - boot, recovery, modem and ROM. So, you'll need to flash a recovery and CM Rom after that if you want to go back to CM. However, with CM you lose WiFi Calling. You could root the Stock and remove any apps you don't want, or freeze them with TitaniumBackup. That way you get the best of both worlds - stock, but only running the apps you want.
YMMV.
Rob
I am no longer able to boot into my recovery. TWRP nor stock / default. I am on a custom ROM. I am on 7.1.2 root with magisk 12. I have tried all the fastboot commands to live boot into recovery. I have tried TWRP official app. I have tried FlashFire. Everytime I try to boot into my recovery my phone just reboots back into the OS.
Wrong section
Hacker101 said:
I am no longer able to boot into my recovery. TWRP nor stock / default. I am on a custom ROM. I am on 7.1.2 root with magisk 12. I have tried all the fastboot commands to live boot into recovery. I have tried TWRP official app. I have tried FlashFire. Everytime I try to boot into my recovery my phone just reboots back into the OS.
Click to expand...
Click to collapse
So you have tried booting into the bootloader and entered "fastboot boot twrp.img" in adb?
This happens to me all the time. Using the advanced reboot menu on my ROM or "adb reboot recovery" while connected to my PC just results in the phone booting back into the OS. Pretty annoying. It has to have something to do with the Slots.
Anyways, to get around this, disconnect the phone from any power source, turn the phone completely off, wait 5-10 seconds, then press and hold Vol Down + Power to get to the bootloader. Then use the volume keys to select Recovery Mode and press power to boot into recovery. This method works every time for me. If this does not work for you or results in some other screen/error/whatever other than booting into TWRP, then you must live boot (as suggested in the above post) into TWRP and flash TWRP RC2.
Alcolawl said:
This happens to me all the time. Using the advanced reboot menu on my ROM or "adb reboot recovery" while connected to my PC just results in the phone booting back into the OS. Pretty annoying. It has to have something to do with the Slots.
Anyways, to get around this, disconnect the phone from any power source, turn the phone completely off, wait 5-10 seconds, then press and hold Vol Down + Power to get to the bootloader. Then use the volume keys to select Recovery Mode and press power to boot into recovery. This method works every time for me. If this does not work for you or results in some other screen/error/whatever other than booting into TWRP, then you must live boot (as suggested in the above post) into TWRP and flash TWRP RC2.
Click to expand...
Click to collapse
I have done this 100+ times. Booting into recovery using any method does not work. Including live booting.
Hacker101 said:
I have done this 100+ times. Booting into recovery using any method does not work. Including live booting.
Click to expand...
Click to collapse
If you are still able to access the bootloader, I would suggest flashing a factory image (removing -w if you want to keep your data) with the flash-all.bat. It sounds as if your recovery partition has been removed somehow making it unable to be booted into. Perhaps flashing the factory image will fix your partitions and solve the problem. It's worth a shot I guess if you can't access it at all. Good luck to you!
TheBobMiller said:
If you are still able to access the bootloader, I would suggest flashing a factory image (removing -w if you want to keep your data) with the flash-all.bat. It sounds as if your recovery partition has been removed somehow making it unable to be booted into. Perhaps flashing the factory image will fix your partitions and solve the problem. It's worth a shot I guess if you can't access it at all. Good luck to you!
Click to expand...
Click to collapse
How am I supposed to flash a factory image if I can't flash anything? Plus I am on a Linux computer not windows. Isn't .bat windows? Would I need a .sh type of command?
Hacker101 said:
How am I supposed to flash a factory image if I can't flash anything? Plus I am on a Linux computer not windows. Isn't .bat windows? Would I need a .sh type of command?
Click to expand...
Click to collapse
The factory image flashes in bootloader mode and should correct any issue you have. You have to install the Android SDK platform on your Linux machine. Go to this link https://developer.android.com/studio/index.html#tos-header and scroll down to almost the bottom for just the command line tools and follow the instructions to install. Then go to https://developers.google.com/android/images and download the factory image you want to flash and follow the instructions in that link to flash. I don't have a Linux machine myself, but I believe the process is fairly similar and it should work just fine.
TheBobMiller said:
The factory image flashes in bootloader mode and should correct any issue you have. You have to install the Android SDK platform on your Linux machine. Go to this link https://developer.android.com/studio/index.html#tos-header and scroll down to almost the bottom for just the command line tools and follow the instructions to install. Then go to https://developers.google.com/android/images and download the factory image you want to flash and follow the instructions in that link to flash. I don't have a Linux machine myself, but I believe the process is fairly similar and it should work just fine.
Click to expand...
Click to collapse
Sweet I'll give it a try when I get home later. We got a nasty storm blowing in so I may not get to it today. Also I'll remember to Thank that post tomorrow lol limited to eight a day. When you have 100+ people helping you out at once it's hard to thank each one.
Hacker101 said:
Sweet I'll give it a try when I get home later. We got a nasty storm blowing in so I may not get to it today. Also I'll remember to Thank that post tomorrow lol limited to eight a day. When you have 100+ people helping you out at once it's hard to thank each one.
Click to expand...
Click to collapse
Don't worry about the Thanks, cause I'm sure others have contributed more. Sorry I'm not more familiar with the Linux instructions!
Ok having the same issue as OP. A and B slots do not allow me to boot into recovery mode. It just immediately restarts as soon as the white Google splash screen appears. I have just done a factory reset with N2G47O. After complete, the stock default recovery works fine. I booted TWRP from fast boot to install the latest, issue came again. Trying to get into recovery mode just causes it to bootloop until you hold the volume down button to get bootloader up to boot to system instead. I am downloading and will flash NOF27D (last 7.1.1) to see if I can reinstall twrp from that. I can confirm that installing twrp when on that image worked. Will report back...
Hacker101 said:
Sweet I'll give it a try when I get home later. We got a nasty storm blowing in so I may not get to it today. Also I'll remember to Thank that post tomorrow lol limited to eight a day. When you have 100+ people helping you out at once it's hard to thank each one.
Click to expand...
Click to collapse
jkashuba07 said:
Ok having the same issue as OP. A and B slots do not allow me to boot into recovery mode. It just immediately restarts as soon as the white Google splash screen appears. I have just done a factory reset with N2G47O. After complete, the stock default recovery works fine. I booted TWRP from fast boot to install the latest, issue came again. Trying to get into recovery mode just causes it to bootloop until you hold the volume down button to get bootloader up to boot to system instead. I am downloading and will flash NOF27D (last 7.1.1) to see if I can reinstall twrp from that. I can confirm that installing twrp when on that image worked. Will report back...
Click to expand...
Click to collapse
I forgot to ask if you were on the latest May security update. If you were on that version then you need to use the Android Verified Signer.zip from chainfire after you flash twrp. What version are you running?
jkashuba07 said:
Ok having the same issue as OP. A and B slots do not allow me to boot into recovery mode. It just immediately restarts as soon as the white Google splash screen appears. I have just done a factory reset with N2G47O. After complete, the stock default recovery works fine. I booted TWRP from fast boot to install the latest, issue came again. Trying to get into recovery mode just causes it to bootloop until you hold the volume down button to get bootloader up to boot to system instead. I am downloading and will flash NOF27D (last 7.1.1) to see if I can reinstall twrp from that. I can confirm that installing twrp when on that image worked. Will report back...
Click to expand...
Click to collapse
Ok, I can confirm after doing factory reset to NOF27D I was able to reinstall TWRP and boot to it successfully
---------- Post added at 04:57 PM ---------- Previous post was at 04:56 PM ----------
TheBobMiller said:
I forgot to ask if you were on the latest May security update. If you were on that version then you need to use the Android Verified Signer.zip from chainfire after you flash twrp. What version are you running?
Click to expand...
Click to collapse
Yes I was on May.. Do you have link to Verified Signer?
jkashuba07 said:
Ok, I can confirm after doing factory reset to NOF27D I was able to reinstall TWRP and boot to it successfully
---------- Post added at 04:57 PM ---------- Previous post was at 04:56 PM ----------
Yes I was on May.. Do you have link to Verified Signer?
Click to expand...
Click to collapse
Here is the link to the verifiedbootsigner.zip from Chainfire: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Make sure you give him some Thanks and Donate if possible! He has earned plenty of both from all of us Android users!
Instructions: Anytime you flash anything that affects the boot partition (ie. twrp, rom, kernel, etc), make sure to flash the boot signer zip at the end of the flashing before a reboot.
TheBobMiller said:
Here is the link to the verifiedbootsigner.zip from Chainfire: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Make sure you give him some Thanks and Donate if possible! He has earned plenty of both from all of us Android users!
Instructions: Anytime you flash anything that affects the boot partition (ie. twrp, rom, kernel, etc), make sure to flash the boot signer zip at the end of the flashing before a reboot.
Click to expand...
Click to collapse
Thank you, and will do.. yes chainfire has done a lot of good work, definitely have appreciated him over the years
TheBobMiller said:
Here is the link to the verifiedbootsigner.zip from Chainfire: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Make sure you give him some Thanks and Donate if possible! He has earned plenty of both from all of us Android users!
Instructions: Anytime you flash anything that affects the boot partition (ie. twrp, rom, kernel, etc), make sure to flash the boot signer zip at the end of the flashing before a reboot.
Click to expand...
Click to collapse
That's only for May and so on correct? I am on April. Heard nasty things form root uses about root screwing up, bootloader problems, etc. So I stayed away from May and stayed on April.
Hacker101 said:
That's only for May and so on correct? I am on April. Heard nasty things form root uses about root screwing up, bootloader problems, etc. So I stayed away from May and stayed on April.
Click to expand...
Click to collapse
Correct. Only the may bootloader requires the extra zip file to be flashed. I am still on April but I have heard people not having any problems and some having nothing but problems from May. I think I'm going to give it a try tomorrow and see how it goes.
Edit: Tried the May bootloader and couldn't get it to boot a custom rom or TWRP, so I went back to April after flashing the Android O Beta and playing with it for a couple of hours. I feel that the Beta is still too early for a daily driver, but it was nice to mess around with some of the features we will have once this OS is released.
Phone is stuck on this white screen with the G on it and the status bar scrolling over and over. Phone is unlocked and rooted and i was having trouble installing a recovery onto it. I just spent 3 hours setting everything up. Do i have to wipe and start again?
equlizer said:
Phone is stuck on this white screen with the G on it and the status bar scrolling over and over. Phone is unlocked and rooted and i was having trouble installing a recovery onto it. I just spent 3 hours setting everything up. Do i have to wipe and start again?
Click to expand...
Click to collapse
What did you flash to cause this?? Did you try a hard restart by holding the power button down until it starts rebooting?
Tried a hard restart and same thing happens. I was trying to install TWRP using skipsoft toolkit #6 option.
equlizer said:
Tried a hard restart and same thing happens. I was trying to install TWRP using skipsoft toolkit #6 option.
Click to expand...
Click to collapse
Since I'm not familiar with toolkits, or their interface, I'll let someone else take over. Have you considered using adb and fastboot commands to accomplish your task?
I would if i knew what i was doing I just tried the wipe everything option and now it says "cant load android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory reset and erase all user data stored on this device"
Well i did that and i get that same message over and over again. How do i start fresh? I have the image on my computer
equlizer said:
I would if i knew what i was doing I just tried the wipe everything option and now it says "cant load android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory reset and erase all user data stored on this device"
Well i did that and i get that same message over and over again. How do i start fresh? I have the image on my computer
Click to expand...
Click to collapse
If you want to continue using the toolkit, I would post your problems in that thread. The folks that made it will be more qualified to help you than I could.
i went into bootloader mode and did the flash all. The phone reboots and comes back with the same message "cant load android"
I dont care what i use to get things working again. pls help.
equlizer said:
i went into bootloader mode and did the flash all. The phone reboots and comes back with the same message "cant load android"
I dont care what i use to get things working again. pls help.
Click to expand...
Click to collapse
I will try my best.
1. You have definitely unlocked_critical correct. If you haven't, you need to.
2. Have you downloaded SDK on your pc? You need this as well. You can find a link to it on Google's factory image page.
3. You have downloaded the latest factory image and unzipped it with the 7zip program.
4. Inside the SDK program, look for a file called platform tools.
5. You need to take the contents you extracted from the factory image, and place them in the platform tools folder. That includes: Radio, bootloader, the flash-all.bat file, and another large zip file that contains the boot, system, vendor and about 16 other things.
6. Put your phone into bootloader mode and plug it into the pc. Open a command prompt from the platform tools folder and type "fastboot devices" if your phone ID comes up, your good.
7. Double click the flash-all.bat file, and that should start the installation process. It will take a little while to install the OS, so be patient. If all goes well, your phone should automatically boot up.
8. I will try and find a link for all this installation stuff.
9. Good luck!
---------- Post added at 01:23 PM ---------- Previous post was at 01:16 PM ----------
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Here is a link to instructions written by one of the best kernel developers out there. Read it carefully if what I gave you doesn't make sense.
Tried it this morning and when i go to root with magisk (followed every step) i get the white screen with the G and the bar scrolling
equlizer said:
Tried it this morning and when i go to root with magisk (followed every step) i get the white screen with the G and the bar scrolling
Click to expand...
Click to collapse
Did you ever get your phone to boot up on stock system?
Badger50 said:
Did you ever get your phone to boot up on stock system?
Click to expand...
Click to collapse
Not sure how i did it but it seems to have reverted back to complete stock. Everything setup after but when it rebooted it said "this device cannot be trusted, hit the power button to continue" so i do and it seems to boot back into the phone. How do i get rid of that message?
Ive never had so many issues with a phone before.
How do i get rid of that message?
once you had the Bootloader unlocked in this phone it will display that message in every boot, there is no way to get rid of it at this moment.
equlizer said:
Not sure how i did it but it seems to have reverted back to complete stock. Everything setup after but when it rebooted it said "this device cannot be trusted, hit the power button to continue" so i do and it seems to boot back into the phone. How do i get rid of that message?
Ive never had so many issues with a phone before.
Click to expand...
Click to collapse
A lot of trouble people have with these phones has to do with the A/B partitions, glitches in cables, sdk, PC's, ghosts in the machine, and users not taking the time to read and learn what to do. Anyway, glad you got it going. Your welcome.
Everything else worked except for the rooting with magisk. when it patches the image using manager 5.4.3 it says its downloading version 14.0 not 14.5. I go to flash the patched boot img then it just reboots to the white screen with the G and it hangs there till i shut it off.
equlizer said:
Everything else worked except for the rooting with magisk. when it patches the image using manager 5.4.3 it says its downloading version 14.0 not 14.5. I go to flash the patched boot img then it just reboots to the white screen with the G and it hangs there till i shut it off.
Click to expand...
Click to collapse
Manually download 14.5 and flash it in twrp. Or, take the stock boot.img, place it on your phones internal storage, open magisk, hit install, and select patch boot (I think) Then take the patched_boot.img and flash that with fastboot. Either way should give you root.
I already said I patched it using the magisk I installed but when I flash it I get the G on the white screen. I can't even get twrp to stick. This was all using 8.1 but now I'm on 8.0. I guess I'll try again?
equlizer said:
I already said I patched it using the magisk I installed but when I flash it I get the G on the white screen. I can't even get twrp to stick. This was all using 8.1 but now I'm on 8.0. I guess I'll try again?
Click to expand...
Click to collapse
What twrp version are you using? So, you can fastboot the twrp-3.1.1-beta2-taimen-img but then are unable to flash the twrp.zip once you enter temporary twrp?
I just downloaded twrp 3.1.1 beta 2 taimen.img and the zip
how do i fastboot the img?
then from there do i flash magisk 14.5.zip then reboot and install magisk manager 5.4.3 then check for root?
equlizer said:
I just downloaded twrp 3.1.1 beta 2 taimen.img and the zip
how do i fastboot the img?
then from there do i flash magisk 14.5.zip then reboot and install magisk manager 5.4.3 then check for root?
Click to expand...
Click to collapse
Go to fastboot and type: fastboot boot twrp-3.1.1-beta2-taimen.img
That should immediately take you temporary twrp where you then flash the twrp.zip, and then flash your magisk zip. That should also install the magisk app as well.
it takes me to the screen where it says "this devices cannot be trusted" so i hit the power button then it just reboots into android 8.0. I appreciate all the help