Database Info

[ROM] Stock RUU 1.32.651.1 | Update.zip Format

This is a download for the stock evo rom, rooted and in update.zip format. Please note that you will NOT be able to just flash this on your phone and have root. This is here for you to be able to have a totally stock rom (with root, superuser, and debugging turned on) once you do root your Evo. Those instructions will be coming soon. So again remember... for right now this doesn't technically serve you any purpose. However once you root your Evo, you can use this to flash a totally stock rom that is rooted.
Not much else to say here.
Base: Supersonic_1.32.651.1
Download: http://geekfor.me/evo/21/stock-evo-update-zip

flipzmode said:
This is a download for the stock evo rom, rooted and in update.zip format. Please note that you will NOT be able to just flash this on your phone and have root. This is here for you to be able to have a totally stock rom (with root, superuser, and debugging turned on) once you do root your Evo. Those instructions will be coming soon. So again remember... for right now this doesn't technically serve you any purpose. However once you root your Evo, you can use this to flash a totally stock rom that is rooted.
Not much else to say here.
Base: Supersonic_1.32.651.1
Download: http://geekfor.me/evo/21/stock-evo-update-zip
Click to expand...
Click to collapse
Thumbs up!

killer! thanks!

is it possible to get more details on what the exact changes are between this and stock?
the su binary was added to /system/bin and set chmod 4755 in the system image?
usb debugging was turned on so the settings file in /data for adb is set to 1 instead of 0?
superuser.apk was added to /data/data or /system/app ?
also, why does this need to flash boot.img? it seems the boot.img in this .zip is slightly larger than the matching boot.img from the original stock RUU and the userdebug RUU PC36IMG.zip? has/what is modified in this boot.img?
from the update-script:
show_progress 0.1 0
format BOOT:
write_raw_image PACKAGE:boot.img BOOT:
show_progress 0.1 0
thanks flipzmode!!!

thanks for this

Sorry, what is the difference between this and the RUU(PC36IMG.zip) in Toast's tutorial thread?

splicitysplat said:
Sorry, what is the difference between this and the RUU(PC36IMG.zip) in Toast's tutorial thread?
Click to expand...
Click to collapse
the PC36IMG.zip is a full RUU. it contains radio, wipes /data, loads /system, loads bootloader and recovery, etc.
this Supersonic.zip is ONLY the STOCK /system with su (root), superuser and adb turned on.
if you want root in normal android mode, you'll want to install this.

so whats the easiest way to upgrade to this Rom? Can you simply use rOM Manager? or do you have to do it through command prompt while the phone is in recovery mode?\\\\
Never mind I think I answered my own question. - Thanks

joeykrim said:
the PC36IMG.zip is a full RUU. it contains radio, wipes /data, loads /system, loads bootloader and recovery, etc.
this Supersonic.zip is ONLY the STOCK /system with su (root), superuser and adb turned on.
if you want root in normal android mode, you'll want to install this.
Click to expand...
Click to collapse
Thank you. So, my check list should go:
-Get EVO
-Root using Toast's tutorial
-Flash Flipz ROM
Is this correct?

splicitysplat said:
Thank you. So, my check list should go:
-Get EVO
-Root using Toast's tutorial
-Flash Flipz ROM
Is this correct?
Click to expand...
Click to collapse
-Get EVO
-Root using Toast's tutorial
-Apply Custom Recovery using Toast's tutorial
-Flash Flipz ROM
yup, sounds good.

Does this rom disable OTA update from Sprint? What I'm thinking is, since Sprint has temporarily enable the WiFi hotspot to work without us paying the $29.99 fee, if we disable the OTA update, then maybe they can't modify the WiFI hotspot it in the future, that requires us to pay the fee?

apexi350z said:
Does this rom disable OTA update from Sprint? What I'm thinking is, since Sprint has temporarily enable the WiFi hotspot to work without us paying the $29.99 fee, if we disable the OTA update, then maybe they can't modify the WiFI hotspot it in the future, that requires us to pay the fee?
Click to expand...
Click to collapse
never heard of them temporarily enabling it. do you currently have a working wifi hotspot? did you have to take it into the store to enable it?

i believe that the tethering app from sprint is free to use for the first month. they wont start charging for it until july

So does this rom disable OTA update?
joeykrim said:
never heard of them temporarily enabling it. do you currently have a working wifi hotspot? did you have to take it into the store to enable it?
Click to expand...
Click to collapse
http://www.engadget.com/2010/05/28/evo-4g-on-sale-at-8am-on-june-4th-with-one-month-free-4g-mobile/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

from the sounds of that article, it is a sprint dedicated app installed on the phone. my guess is it will check thru the internet, whether or not you are allowed to wifi tether, and then either activate the application or forward you to an activation page in the browser.
i could be completely wrong but im guessing this will have absolutely nothing to do with OTA.
If this rom is completely stock as Flipz indicated in his first post, OTA will not be disabled.

OTA on Sprint
In my experience, OTA has not been the same on Sprint that it was on T-mobile. Each time an update came out, I had to use the Device Self Service app to get the update. I've been running a rooted ROM based on stock for the Hero and have never just had an OTA update start up.

I just flashed this after rooting because this supposedly fixed a market problem and now I'm stuck in an endless boot cycle on the Sprint 4g logo...any idea how to fix?
Edit: I'm currently restoring based on the backup I made. But people should beware that this can cause problems!

when sprint makes u pay for the hotspot it wont be a ota update. all that will happen is a change in the system on ur account on the back end just like if u loose ur phone and u have them restrict it

I wonder how sprint is going to determine who to charge. If it is active now it is going to take a OTA to turn it off. that is if they are tracking by the application. They could be just monitoring data amounts being transferred and going to charge if you are over a certain amount. Anyone from sprint on that knows for sure.

damnit. i had no problem with toasts root instructions.. despite this being my first android, but i'm having a helluva time finding instructions to install your custom rom.. bah humbug

[UTIL] Android Splash Image Changer

Simply change the splash screen of your phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Requirements:
- At this time only phone's with a resolution of 480x800 will do.
- Remember, in order to flash custom splash screens, you must have s-off which can be obtained using alpharev.
- Before you click the "Push to Phone" button, make sure your device has the USB Debugging feature enabled.
(Settings -> Applications -> Development -> USB debugging)
How the magic works:
- This tool will first convert your selected image to the appropriate file format (splash1.img).
- It will then try to reboot your phone using ADB (Command used: adb.exe reboot bootloader).
- While rebooting your phone this tool will start a fastboot session (fastboot.exe flash splash1 splash1.img)
- If the phone is rebooted into the bootloader, it will execute the actual flashing process
- After flashing this tool will reboot your phone once again to finish the whole process (fastboot.exe reboot)
Version history:
1.0 - Initial release
***I take no responsibility for any damage you cause by using this tool. It is for educational purposes only.

Placeholder for the future, you never know...

where is this image located? i wanna do it for my custom rom

Hi,
How does it work ?
When I click "Push to Phone", it say "Please wait while your phone is rebooting" during about 1 second and nothing.

Gjole86 said:
where is this image located? i wanna do it for my custom rom
Click to expand...
Click to collapse
Cool question!
Behind the scenes of this tool I'm doing some fancy conversions to the image.
This results in a flash-able file called splash1.img.
This image is then flashed to splash1 with the command: fastboot flash splash1 splash1.img.
Thing you have to do is create the file splash1.img and incorporate the flashing procedure into your update script.
I don't have any experience in that procedure, but going to try it out.
It should work, others have done this before.
Will be back for this one
For now, take a look at this thread.
It should make some things clear for you I think.

tsukasa21 said:
Hi,
How does it work ?
When I click "Push to Phone", it say "Please wait while your phone is rebooting" during about 1 second and nothing.
Click to expand...
Click to collapse
Do you have S-OFF?

Yes I have S-OFF. I'm trying to restore my splash screen to the original one (I'm currently having the alpharev joker)

It works!! finally i can get rid of the joker!!

Amazing.
Just suggest reduce a little bit the Window. The button isn't showed in 1280x800 correctly
And please, add the information about, WHEN click on PUSH TO PHONE (HBOOT,FASTBOOT,Charge Only with debug...)
Regards and thank you

This is in the General section so does it work with OTHER phones, my screen res isnt the one specified, do i still need S OFF or is that for HTC phones?
If it doesnt work for any other phones can we get it moved to the HTC section?

Vivasanti said:
This is in the General section so does it work with OTHER phones, my screen res isnt the one specified, do i still need S OFF or is that for HTC phones?
If it doesnt work for any other phones can we get it moved to the HTC section?
Click to expand...
Click to collapse
It will work for other phones as well, as long as the resolution is 480x800 (for now) and you have S-OFF.
Will be working on compatibility for other resolution soon.

dneto said:
Amazing.
Just suggest reduce a little bit the Window. The button isn't showed in 1280x800 correctly
And please, add the information about, WHEN click on PUSH TO PHONE (HBOOT,FASTBOOT,Charge Only with debug...)
Regards and thank you
Click to expand...
Click to collapse
Totally agree on the big window size, will adjust it to a more appropriate size in the next release.
For the extra prerequisite info... working on it now

Vivasanti said:
This is in the General section so does it work with OTHER phones, my screen res isn't the one specified, do i still need S OFF or is that for HTC phones?
If it doesn't work for any other phones can we get it moved to the HTC section?
Click to expand...
Click to collapse
Looking again into the compatibility it indeed seems to only work on HTC devices.
Seems like S-Off is a htc thing.
Hope someone with a galaxy S phone can test this, don't know if flashing is a problem.
If that's the case I would have to take a different approach.
My aim is to make it device independent.

Where is "Pay me a Beer (aka Donate)" Button? =]
Thank you.

dneto said:
Where is "Pay me a Beer (aka Donate)" Button? =]
Thank you.
Click to expand...
Click to collapse
Haha, Tnx for the nice reply, makes me happy
People around me are calling me stupid, not adding a donate button to my apps.
To me its nothing more than cluttering the UI, distracting you from things that ARE important.
If people really want to donate, they can do so on this forum.
Have added a celebrate link to my signature, think it should be enough

on win xp 64 bit i click push to phone and it just shows the windows hourglass when i scroll over the app - nothing is happening on the phone end or in the app.

sundar2012 said:
on win xp 64 bit i click push to phone and it just shows the windows hourglass when i scroll over the app - nothing is happening on the phone end or in the app.
Click to expand...
Click to collapse
This sometimes happens to me to, temporary workaround to this could be: close the app and try again.
Has something to do with kicking off adb the first time.
It just hangs, but when you try it the second time it should be already running in the background.
I'm currently rebuilding the whole app, upcoming release would fix it, but for now, try it a second time

You should try to make a version that can do an animation splash screen, that'd be awesome. Its still a cool app though.

natehoch96 said:
You should try to make a version that can do an animation splash screen, that'd be awesome. Its still a cool app though.
Click to expand...
Click to collapse
I Agree, working on it now ;-)

Anoniem100 said:
Simply change the splash screen of your phone.
Requirements:
- At this time only phone's with a resolution of 480x800 will do.
- Remember, in order to flash custom splash screens, you must have s-off which can be obtained using alpharev.
- Before you click the "Push to Phone" button, make sure your device has the USB Debugging feature enabled.
(Settings -> Applications -> Development -> USB debugging)
How the magic works:
- This tool will first convert your selected image to the appropriate file format (splash1.img).
- It will then try to reboot your phone using ADB (Command used: adb.exe reboot bootloader).
- While rebooting your phone this tool will start a fastboot session (fastboot.exe flash splash1 splash1.img)
- If the phone is rebooted into the bootloader, it will execute the actual flashing process
- After flashing this tool will reboot your phone once again to finish the whole process (fastboot.exe reboot)
Version history:
1.0 - Initial release
***I take no responsibility for any damage you cause by using this tool. It is for educational purposes only.
Click to expand...
Click to collapse
Working fantastic on my desire, many thanks

[Q] Precautions to take with root? re looming 4.4.2 OTA

There are how-tos from 2012 about using Voodoo to store root access (like squirrels storing their nuts for the winter) but is there a better way now? ... Am I wrong in anticipating a problem here?
9.18.94.XT926.Verizon.en.US with saferoot
Thanks

I wouldn't take the OTA until someone figures out a way to root the OTA, and that doesn't look very promising. Honestly, I don't think Voodoo will help out here, either.

RikRong said:
I wouldn't take the OTA until someone figures out a way to root the OTA, and that doesn't look very promising. Honestly, I don't think Voodoo will help out here, either.
Click to expand...
Click to collapse
Guess I could educate myself about how Saferoot works, but ... I'm still learning Java! Will be a while before I know how things _really_ work.
Thanks

From the play store:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

For the unlocked fellows and fellowettes out there, it's as simple as 1) unrooting, 2) taking OTA, and 3) flashing SuperSU in TWRP / CWM to regain root access, correct?

LifeAsADroid said:
For the unlocked fellows and fellowettes out there, it's as simple as 1) unrooting, 2) taking OTA, and 3) flashing SuperSU in TWRP / CWM to regain root access, correct?
Click to expand...
Click to collapse
As long as you haven't frozen or removed any other system apps, then yes. I usually just do a clean wipe and install with RSD Lite since I remove all kinds of crap when I use stock.
And yeah, you can always flash SuperSU in recovery if your bootloader is unlocked.
/e: On second thought, take that first sentence with a grain of salt. I realized I've never actually taken an OTA the traditional way with a custom recovery installed. It seems like that wouldn't work properly.

killrhythm09 said:
As long as you haven't frozen or removed any other system apps, then yes. I usually just do a clean wipe and install with RSD Lite since I remove all kinds of crap when I use stock.
And yeah, you can always flash SuperSU in recovery if your bootloader is unlocked.
/e: On second thought, take that first sentence with a grain of salt. I realized I've never actually taken an OTA the traditional way with a custom recovery installed. It seems like that wouldn't work properly.
Click to expand...
Click to collapse
Holy cow, I am thanking you all over the place tonight! Such great useful information you have! I was wondering if you wouldn't mind explaining in a little more detail what you mean by "clean wipe and install with RSD Lite". I have a feeling I may or may not have deleted something important along the way. I know I have frozen things in TiBu (which I can defrost, update, and re-freeze or finally delete since this will be our last update from Motorola), and I don't think I have deleted any of the system files as of yet, but I am pretty certain I have modified system files (changing things in SystemUI, etc) for certain mods.
In case the modded files forbid me from taking the OTA, could you explain a little about how you clean wipe and install with RSD Lite?
After final install of KitKat (by whichever method), if I have clean wiped, I'll lose my photos, messages, etc, yes? Is there a way to save that stuff? TiBu backup of the "text messaging" app or the "gallery" app perhaps?
I promise you I am not thread-stalking you around XDA, but thanks again for all your time tonight!

RSD Lite is a software tool you install on your PC to flash Motorola phones in fastboot. If you ever see an fxz package (which I think stands for fastboot xml zip) they can be used by RSD Lite to basically restore your phone to stock. They usually come with a file with different sections that you can comment or uncomment if you only want to flash specific partitions (i.e. only the modem, or just the kernel).
There's probably a better solution for backing up, but I just use TiBu and then copy everything off my internal storage & SD onto my PC temporarily, then copy it back after. I do it so infrequently that I haven't bothered to figure out a better way, sorry.
/e: Meant to include this site, since it has lots of different firmware releases that you can use with RSD Lite:
http://sbf.droid-developers.org/phone.php?device=5
If you have any other questions, let me know.

LifeAsADroid said:
For the unlocked fellows and fellowettes out there, it's as simple as 1) unrooting, 2) taking OTA, and 3) flashing SuperSU in TWRP / CWM to regain root access, correct?
Click to expand...
Click to collapse
1.5) flash stock from custom recovery.
Note m recovery is in my button goodies. I think hd & m share the same img. Check the md5.
---------- Post added at 09:44 AM ---------- Previous post was at 09:42 AM ----------
Voodoo root keeper will work for easy unroot but not for keeping root beyond 4.2.

I personally won't take the update until sometime figures out a way to have root in kit kat.

LifeAsADroid said:
In case the modded files forbid me from taking the OTA, could you explain a little about how you clean wipe and install with RSD Lite?
Click to expand...
Click to collapse
The best solution is to use SamuriHL's House of Moto tools. You must read, read again, and read one more time before installing and using the tool. Once it's set up correctly, it is very easy to use. You can get it here -> http://www.droidrzr.com/index.php/topic/28162-house-of-moto-20-for-now/
Read the OP in the thread first. Again, read it and then once more, as he states. The instructions are all there, but you have to read through them entirely before you attempt to use the tools.
I use this all the time when I'm ready to flash back to stock after being on a custom ROM when a new OTA comes out.
I use Titanium Backup to backup all my apps and data to my external SD card.
I use Backup to Gmail app to backup my call log, sms and mms messages so I can restore them later.
I backup my contacts and such to Google as well.
I use Listables to generate a list of the apps I had installed. I have so many that I sometimes forget which ones I used.
After that, I use HoM to flash back to stock and then reinistall TiBu to restore my apps.
Then, I use HoM to flash back the custom recovery (TWRP in my case) and flash root back onto my device (I'm unlocked so I don't have to use an exploit).
However, it would be best to hold off on root if you are wanting to obtain the OTA, unless of course you are using a locked device. Then, you might want to hold off until it's determined if there is a root exploit that will work.
Even though I'm unlocked, I'm going to wait and make sure they don't find a way to relock it. I don't believe they can since it was a physical change in the device (blown fuse - can't unblow it - is that a real word?)
That's it.

How to install January 5th patch while using custom recovery and root on Google Pixel

Okay, I am sure a lot of you already know how to do this to your Pixel. Some of us do not, and I was one of them. I am the standard noob that just followed Youtube videos to unlock previous carrier locked phones. I am now enjoying this Google Pixel that is unlocked!
So if you are reading this thread, hopefully there isn't another one just like this (yes I looked).
To start off, if you are in here reading this, you have unlocked your bootloader and installed a custom recovery such as TWRP and rooted. Now you are seeing that you need to update your phone with the latest security patch. You try and you try and you can't do it. Even when you unroot it will still fail to update, or at least it did for me. Here I will explain what I went through and did to obtain the latest update. (Warning, you will loose root and custom recovery). THIS IS INTENDED FOR THE GOOGLE STORE PURCHASED PHONES
Lets get this started finally.....
Go into your developer options and enable usb debugging.
Download the newly released package file from google that has fastboot and ADB without needing android SDK.
DOWNLOAD or read about it HERE
Now you will need to download the Factory Image for you device
Find your correct device HERE
Make sure you choose the correct device and correct update, for me I downloaded the "7.1.1 (NMF26U, Jan 2017)" for my Pixel. Also a USA phone.
So now you have the adb fastboot binary package and your factory image. You will need to extract the platform-tools-latest-windows.zip and open the folder and you will see another folder, open it and now you will see a bunch of files. Now open another window and extract your factory image. Once it is done, open the folder until you see the files. Now copy these into the Platform tools folder in the directory with the fastboot.
Once this is done your folder should look like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now you will want to right click "flash-all" and click edit. It will open notepad and show the contents of the batch file. You can hit Ctrl+F and type in -w in the search and hit okay, or you can look for it without search (it is near the bottom). Once you find it, just delete the "-w" and save the file. Make sure to keep it as the batch file or this won't work.
Once this is done, in the folder that is shown above, click a blank area in the folder so no file is highlighted. Now hold shift and right click, it will come up with a dialog saying open command window here, click that.
Now we are going to reboot the phone into bootloader mode. In the command window, type everything that is underlined below
adb reboot bootloader
Now your phone should have booted into the bootloader screen or it should be asking for USB rights to use adb. If it asks for permission, hit okay and re run the code above and your phone should reboot.
Once you are in the bootloader screen you will need to do is run the flash-all.bat. It will load and go though some text on the CMD window it brings up. It will say some files are missing, which is fine. But if it fails it will tell you that it did. You can also tell by rebooting the phone or click "start" in the bootloader mode and then checking for OTA updates. It should say January 5th patch installed.
Now you can go through and install your custom recovery again and re root. Which takes no time at all and I am sure someone on here has posted before. If not, let me know and I can make a tutorial over it.
Note: I am very sorry for the bad layout and extended write up. First time ever doing this and I am hoping to help people. If there are any errors, let me know!

All of this is already well known and documented. It is device molding 101
No one with 2 licks of common sense uses YouTube videos for something like this.

zelendel said:
All of this is already well known and documented. It is device molding 101
No one with 2 licks of common sense uses YouTube videos for something like this.
Click to expand...
Click to collapse
Haha well my apologies, I did state that I was a complete noob about all of this. I'm sure there are other noobs like myself

exbtlegends said:
Haha well my apologies, I did state that I was a complete noob about all of this. I'm sure there are other noobs like myself
Click to expand...
Click to collapse
I'm not a noob, but i'm a old fart, and we forget things, even simple things like this, I'm glad to have a simple reminder of how to do things. Thanks for the refresher.

jrat69 said:
I'm not a noob, but i'm a old fart, and we forget things, even simple things like this, I'm glad to have a simple reminder of how to do things. Thanks for the refresher.
Click to expand...
Click to collapse
Not a problem ?

I know you say this is for the GPS version, but has anyone tried it on Verizon? I'm not sure if the firmware is the same on both phones, so I don't want to soft-brick by downloading the Google version if they're different. Same boat as you were, OTA fails even after unrooting.

32BitWhore said:
I know you say this is for the GPS version, but has anyone tried it on Verizon? I'm not sure if the firmware is the same on both phones, so I don't want to soft-brick by downloading the Google version if they're different. Same boat as you were, OTA fails even after unrooting.
Click to expand...
Click to collapse
As long as you never re-lock your bootloader, the process is the same. There's no more separate Verizon images, just USA and international.

This is really complicated. ADB side load the OTA file, reinstall TWRP and root, done.

Good work. This is a very minute stuff of removing -w from the batch file. Very handy work.
Sent from my Pixel using Tapatalk

Do you need to reflash stock kernel before removing root/TWRP before flashing?

32BitWhore said:
Do you need to reflash stock kernel before removing root/TWRP before flashing?
Click to expand...
Click to collapse
Flashing the image overwrites anything you customized besides the regular user data and internal storage (with the -w removed). You don't have to remove or reflash anything else before following these instructions.

TCPDump said:
This is really complicated. ADB side load the OTA file, reinstall TWRP and root, done.
Click to expand...
Click to collapse
I couldn't side load the update.. TWRP would not load the side load feature.

I'm having an issue also: https://forum.xda-developers.com/pixel/help/sideload-ota-t3534926... Can we just unroot, take the OTA and then reroot?

km8j said:
I'm having an issue also: https://forum.xda-developers.com/pixel/help/sideload-ota-t3534926... Can we just unroot, take the OTA and then reroot?
Click to expand...
Click to collapse
Even when I un rooted mine. I was still failing to get the update.

If you made any changes the the system partition then it will fail and simply unrooting doesn't make the all the changes needed. So if OTA mean anything to you then I would suggest not messing with your device as there is Jo promise that after an OTA you will be able to root again tonight away

jesssiii said:
As long as you never re-lock your bootloader, the process is the same. There's no more separate Verizon images, just USA and international.
Click to expand...
Click to collapse
I know the past 2 were the same for google pixel and Verizon pixel but I wouldn't assume they are always going to be. I'm sure some of them will be specific at times whenever Verizon decides they wanna mess with them

FYI, I was able to sideload after updating TWRP to RC1, but now SuperSU 2.79 will install from within TWRP but when the phone restarts SuperSU is not installed... not sure if we have to wait until a new version of SuperSU is released.

SpoiledHeeb said:
FYI, I was able to sideload after updating TWRP to RC1, but now SuperSU 2.79 will install from within TWRP but when the phone restarts SuperSU is not installed... not sure if we have to wait until a new version of SuperSU is released.
Click to expand...
Click to collapse
You need SuperSU 2.79 RC3

Edited build.prop and now the phone is bricked.

Alright, so here's what happened.
Finally updated hardware and went from a nexus 6p to a pixel xl.
It's running 8.0.
So I decided it was time to get the phone up to the same customization that I had on my 6p.
One of my first things, after rooting of course, was adding qemu.hw.mainkeys=1 to build.prop in order to get rid of the soft keys. Same exact thing I've done on literally all of my android phones ever.
Rebooted.
I now get this sweet messaging saying "Can't load Android system..." (See Picture) and so on. Suggesting Try again and Factory data reset.
So I'm like whatever, I can just pull build.prop to my computer. So I find some guides on how to do that and boot to the bootloader.
But then adb devices shows:
"List of devices attached"
And then nothing. So adb can't find my phone.
Here's what I tried in trouble shooting.
Disconect Cable
adb kill-server
adb start-server
Plug back in.
Still nothing.
I even tried a different USB port.
So now I'm like "Okay, I'll take the bullet and factory reset."
So I did.
After setup, I get about 30 seconds (without softkeys) of phone time before my the System UI crashes and the phone shuts off.
Upon reboot, I'm faced with the same "Can't load Android system screen..." (See picture again if you want) and we're back to square one.
So...
Can't adb pull on build.prop because adb can't find my phone.
Can't boot into the regular system and edit build.prop from there because the phone isn't rooted (cause the only way to boot into the system is to factory reset).
Can't root the phone because adb can't find my phone.
And lastly, can't flash factory images because adb can't find my phone.
That's all the trouble shooting I've tried. If anyone can help me out here, I would be super grateful, cause right now, I have a really expensive paperweight.
Thanks in advance.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

hello, try flashing through fastboot following this post:
https://forum.xda-developers.com/showpost.php?p=70041042&postcount=3
here if you want to unlock the bootloader:
https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-unlock-root-flash-pixel-xl-t3507886

Yup. That worked. Thank you!

Any idea why adding qemu.hw.mainkeys=1 to build.prop killed my rom?

burt1215 said:
Any idea why adding qemu.hw.mainkeys=1 to build.prop killed my rom?
Click to expand...
Click to collapse
Because the UI has to have nav keys, unless your Pixel has hardware keys, you'll probably have to keep the softkeys.
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Droidriven said:
Because the UI has to have nav keys, unless your Pixel gas hardware keys, you'll probably have to keep the softkeys.
Click to expand...
Click to collapse
I've hidden the softkeys on my Nexus 4, Nexus 5, and Nexus 6P. And on every operating system since ICS.
What's different now? Is it the Pixel XL or Oreo?

burt1215 said:
I've hidden the softkeys on my Nexus 4, Nexus 5, and Nexus 6P. And on every operating system since ICS.
What's different now? Is it the Pixel XL or Oreo?
Click to expand...
Click to collapse
To be honest, I've never heard of it being an issue either, I was just speculating, however unlikely it may be.
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Droidriven said:
To be honest, I've never heard of it being an issue either, I was just speculating, however unlikely it may be.
Click to expand...
Click to collapse
Ha. No worries.
After fixing my phone, I decided to edit build.prop again, cause it's not stupidity unless you try the same thing multiple times while expecting different results right?
Anyway, same exact thing happened.
This time I fixed it without wiping my phone, but it leads me to believe that build.prop can't be edited... but I'm still not sure why.

burt1215 said:
Ha. No worries.
After fixing my phone, I decided to edit build.prop again, cause it's not stupidity unless you try the same thing multiple times while expecting different results right?
Anyway, same exact thing happened.
This time I fixed it without wiping my phone, but it leads me to believe that build.prop can't be edited... but I'm still not sure why.
Click to expand...
Click to collapse
Are you booting to recovery and wiping cache and dalvik/ART cache(obviously not factory reset or wipe data, just the caches)? It's usually required when modifying system files.
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Droidriven said:
Are you booting to recovery and wiping cache and dalvik/ART cache(obviously not factory reset or wipe data, just the caches)? It's usually required when modifying system files.
Click to expand...
Click to collapse
I edited build.prop and rebooted the system.
Got the same error as the picture in the original post.
Booted into TWRP and pulled build.prop onto my computer.
Edited the file, pushed it back in and rebooted into the system without any errors.

burt1215 said:
I edited build.prop and rebooted the system.
Got the same error as the picture in the original post.
Booted into TWRP and pulled build.prop onto my computer.
Edited the file, pushed it back in and rebooted into the system without any errors.
Click to expand...
Click to collapse
Strange, at least it works.
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE