[ROM] Stock RUU 1.32.651.1 | Update.zip Format - EVO 4G Android Development

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

Related

[Win32 Tool]GUI Root with Check and Recovery!

{
"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"
}
ShiftRRv1.0
Shift Root and Recovery will be able to root you're phone in a pretty safe manner. The program is designed to only flash the eng boot if the MD5 checksums are correct.
This does it by simply pushing / pulling the hboot from the phone and checking the MD5 as if you were to manually do it. Only this just does it automatically.
Check Root:
This will just run a quick and simple SU test to make sure you are or are not rooted.
Root:
You will click on this to install the ENG Hboot and load the correct files after the Hboot has been flashed.
Install Recovery:
You simply select the recovery image you want to use with your HTC Evo Shift. Leave the phone at the home screen and click install. It will auto reboot you to bootloader, flash the zip then auto reboot you to recovery to make sure it flashed successfully.
Backup / Restore WIMAX:
This option lets you quickly and easily backup your wimax keys to your home pc. It will also let you restore your wimax keys to your phones partitions.
[WHAT THIS PROGRAM DOES]
When you click on root, and click "NO" for this phone does not have a ENG Hboot. The program push's the ENGHboot from the Hboot folder to the phone and push's busybox. From there it gets a temp root shell. It then cross checks the MD5sum on the phone itself using busybox md5sum /data/local/eng_hboot if the MD5Sum math's it then proceed's with the dd if cmd. Once the dd if cmd is done. The program then sends the dd if cmd to /data/local/eng_hboot_check, it runs the cmd busybox md5sum again and verifies that the MD5Sum matches if so everything went well, the program cleans up its mess off the phone and alerts you its safe to reboot. IF IT FAIILS it will try 1 more time. The program is designed to check the HBOOT md5sum and verify if its the ORIG hboot if it is not and the MD5Sum doesn't check between the ENG and ORIGINAl it will attempt to flash the original and notify you if it succeeds. IF IT FAILS AGAIN. IT WILL NOTIFY YOU NOT TO TURN OFF YOUR PHONE AND COME HERE FOR FURTHER INSTRUCTIONS. I ADVISE YOU TO LISTEN.
After this YOU MUST REBOOT THE PHONE.
When phone is powered up again Click Root again this time select "YES" that the phone has a ENGHboot, this will get temp root again and push all the needed files, "SQLITE3", "BusyBOX", "SU", "Superuser.apk" to there proper location.
If YOU CLICK "YES" and didnt have the ENG Hboot thats fine it simply will temp root you and push files to your phone, but when you reboot they will be gone. Just start from the begining again and do it again.
Download V1 Here
DOWNLOAD NOW HERE
User's having trouble opening the application please download the latest dotNET framework from:
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=0a391abd-25c1-4fc0-919f-b21f31ab88b7
THIS IS FOR XDA MEMBERS ONLY. PLEASE DO NOT POST IN OTHER FORUMS AND PLEASE DO NOT MIRROR THE PROGRAM.
download link added
Image of program added.
Reserved...
Thanks for sharing. No need for me to try it now but if I ever replace or need to re-root. Really like the option to backup wimax keys too.
Looks great but too bad I don't need it! Like the option to back up wimax, but what about restoring them!?
Im giving this a try now
It "did its thing" after rebooting the program is still "waiting" and the phone is booted. Hmmm help?
xstingstreetx,
Can you give me more information?
Were you trying to root, or where you trying to do recovery?
Version of windows as well?
ahhhh!! I'm back 2 download it and.. well I'll wait again lol Thanks a lot for this..
I RUUed my phone and Wanted an easy way to re-root..
working?
other than the OP has anybody got this to work properly?
amoamare said:
xstingstreetx,
Can you give me more information?
Were you trying to root, or where you trying to do recovery?
Version of windows as well?
Click to expand...
Click to collapse
I was trying to root, and I have windows 7 64 bit
Where is the link ! someone please give me the file , pretty please please please been waiting for this !!!
I don't know if this is what it's trying to achieve or not. I don't know how to do it either. Judging by all my previous phones, an all in one script could be written to do everything the s-off, root, and recovery post is telling how to do. Just a "simple" batch file and some support files and presto, it's all done!
Zip everything needed together and just unzip and run. I could probably teach myself by ripping apart other all in one packages and adjusting my port to follow loosely what they are doing but I just don't have the free time to spend on that project. By the time I would get around to doing it, someone else would have finished it. I just don't know things like telling the phone to reboot into different modes so it could continue it's job. I can visualize it in my head but making it a reality is completely different. Doh!
Anyone know where the download link went? I've been having trouble with rooting my phone and wanted to try this, but theres no download link in the first post (unless my computer decided to stop showing links).
Link was removed temporarily. Learn to read guys, sheesh
On a side note, I'm pretty psyched about this OP, since I haven't had the ambition to sit down and root my phone yet. Just curious, are there any files that would need to be downloaded prior to using this (such as the ****-root.zip used in the other root method)?
Oops, saw everything except "removed temp..." in the first post.
It looks like there isn't anything extra that needs to be downloaded. Looks like the OP figured out a way around it.
SirRipo said:
Link was removed temporarily. Learn to read guys, sheesh
On a side note, I'm pretty psyched about this OP, since I haven't had the ambition to sit down and root my phone yet. Just curious, are there any files that would need to be downloaded prior to using this (such as the ****-root.zip used in the other root method)?
Click to expand...
Click to collapse
Possibly the recovery files ( clockworkmod 2.x or 3.x ) and have HTC sync set up to even connect the phone I would guess.
Sent from my PG06100 using XDA App
Sorry guys will work on this again in a few days girl is supposed to be going in to labor today...
On the side note the issue that I ran into is that running rageagainstthecage from the windows side does not give you root. It actually disables usb connection between the phone and the computer. I was trying to make this so you didnt need anything other then the program. But now with that being a problem z4root would be needed to obtain at least temp root but if i doesnt drop you to # then it still will not work from doing it automatically using arguments. That is what i'm trying to resolve first..
Ill get back to you guys on it, and ill even add the option to restore wimax keys.
That's what I was thinking You have to Temp root with Z4root first.
Since The manual root requires super user to work.
Dude!!!! thank you so much for this. Been wanting t root badly but was afraid to try the other method. Good luck with baby!!
Perhaps someone brave could test it out by temp rooting with visionary/z4root and then running the program? If you posted the download link back up.

[ROOT] [KERNEL] [RECOVERY] - Root / Voodoo Lagfix / CWM Recovery

Hi all
Whipped this up for a friend. Thought we'd be nice and share
These packages will work on any current sw version for the Charge.
Please find below kernel and recovery packages hacked for the following:
permanent adb root
installs Superuser and su binary automatically on boot
includes Voodoo ext4 lagfix - CREDIT TO SUPERCURIO! http://project-voodoo.org/lagfix
lowmemorykiller tweaks
sdcard readahead cache speed tweak
If you are using Odin to flash, simply flash the below package. If you are using Heimdall, remove the zImage file from the below package and flash it.
After flashing the first time, you will hear a voice from the phone telling you what is occurring. The conversion to ext4 will take a few minutes. BE PATIENT. Once it boots, Superuser should be installed, and your phone's filesystem will be converted from rfs to ext4. To disable Voodoo lagfix and convert back to rfs, simply create a file on your sdcard inside the Voodoo folder, named "disable-lagfix". Then reboot your phone and listen for the voices again. This will also take a few minutes.
Please familiarize yourself with using Odin or Heimdall and have backup images on-hand if you are going to use this kernel. If you screw up, you will need them
I DO NOT have a Charge, these files have been tested by other users. As always I assume absolutely NO liability for anything that happens if you use this kernel. Phone blows up? It's on you to fix it
If you find this software helpful please click the "Thanks" or the "Donate" button. Either is fine by me. If you would like to investigate the changes that were made, please feel free to find them here, and here.
Enjoy.
EDIT
Uploaded 2nd version
EDIT
Uploaded 3rd version
changed the install scripts around
should copy files more efficiently
fix file ownership and permissions
UNTESTED!
EDIT
Uploaded 4th version
Confirmed root from independent user!
rewrote install process to preserve file path and permissions
will look into the bootanimation graphics issue
http://dl.dropbox.com/u/14764513/VoodooChargeKernel4.tar.md5
EDIT
Uploaded additional recovery file
Flashes custom version of ClockworkMod recovery 3.x
Recovery includes Voodoo specific options for enabling/disabling Voodoo lagfix
Flash with Odin or Heimdall just like the kernel files
HAS BEEN LIGHTLY TESTED! USE CAUTION AND HAVE A BACKUP!
if you do not have root:
* check adb shell and see if you get a '#' prompt. If so, you *have* root on adb, and you may install whatever you want in /system
* check to see if Superuser app is installed
* check to see if /system/xbin/su exists on your phone.
If you have problems, please post the results of those checks. Thanks.
LLGW. Headed to bed now but first thing in the morning, I wondering what I'm doing
Thanks jt!!!! Can't wait to flash this once my charge comes in the mail.
Sent from my SCH-I500 using XDA App
Ok, somebody use this to system dump ED2.
And, uh, is there matching Voodoo clockwork?
s44 said:
Ok, somebody use this to system dump ED2.
Click to expand...
Click to collapse
please
And, uh, is there matching Voodoo clockwork?
Click to expand...
Click to collapse
probably not
What verison of odin should I use? I just flashed this and it failed.
using odin3 v1.3 and failed too..
phone wont boot, had to reflash ed1
The kernel flash was successful, and the filesystem conversion took about 8 minutes to run. However, I was not rooted when the phone booted back up. Here is what I did, let me know if I missed a step:
Start on rooted ED1
Accept ED2 OTA
Lose Root
Flash new kernel using ODIN
After ~10 minutes, phone boots successfully, but I do not have root.
asenduk said:
using odin3 v1.3 and failed too..
phone wont boot, had to reflash ed1
Click to expand...
Click to collapse
Keep trying. I finally got it to flash with 1.30. Seems to be booting. On boot it did not change the file system, it just booted normally.
Edit:I just put in my spare battery and it is now converting the file system. The other battery was probably too low.
Where's my wifi? Anyone else facing an error when attempting to start wifi?
Yeah it looks like it killed wifi. I also am not rooted.
So if I flash back to rooted ED1 will it wipe my data?
azhockey said:
So if I flash back to rooted ED1 will it wipe my data?
Click to expand...
Click to collapse
I just reversed the filesystem changes and then flashed back to ED1. My data appears to be intact.
moondrius said:
Keep trying. I finally got it to flash with 1.30. Seems to be booting. On boot it did not change the file system, it just booted normally.
Edit:I just put in my spare battery and it is now converting the file system. The other battery was probably too low.
Click to expand...
Click to collapse
had to rename the file to .tar.md5 now its working..
asenduk said:
had to rename the file to .tar.md5 now its working..
Click to expand...
Click to collapse
I was able to flash with it just named .tar, using ODIN 1.85. Did you retain your root access after the renamed flash?
Updated OP with a new version. Anyone who has flashed the original version, please check adb shell and see if you get a '#' prompt. If you do, then you're technically rooted
NotATreoFan said:
I was able to flash with it just named .tar, using ODIN 1.85. Did you retain your root access after the renamed flash?
Click to expand...
Click to collapse
Superuser was installed but root was lost... Trying the updated version... On a positive note Quadrant is great! 1400-1550 avg
EDIT: wifi fixed with v2 but still no root.. will try from scratch and report back
{
"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"
}
Everything has worked for me. Thank you.
Sent from my ADR6400L using XDA Premium App
yes im obviously a newb for asking this question but i have odin and have downloaded the kernal tar file. how am i supposed to flash it onto the phone now? Ive found how to put the phone into download mode i just dont know what im supposed to do with odin
devanmc said:
yes im obviously a newb for asking this question but i have odin and have downloaded the kernal tar file. how am i supposed to flash it onto the phone now? Ive found how to put the phone into download mode i just dont know what im supposed to do with odin
Click to expand...
Click to collapse
Click PDA and select the file then just hit start

[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.

[Toolkit] Wug's Nexus Root Toolkit v2.1.4 [Updated 01/16/16]: Nexus 5X Thread

Unlocking, rooting, relocking and unrooting simplified! (and much more!)
VERSION 2.1.4 - This program will automatically bring together all the files you need to unlock and root your device in a few clicks, or flash it back to stock and re-lock it. You can also use this program to backup/restore all your important data, flash zips, set file permissions, push and pull files, install apps, generate logcats/bugreports, and much more! With the included file association options, you can perform tasks like flashing zips, installing apps, restoring android backup files, and flashing/booting img files with just a double click! The program includes a full featured interface for automating tasks in TWRP, enhanced restore features, an in-built auto-updater/notification system, ‘any build’ mode, advanced restore features,’NRT- Live Log’ for viewing the adb/fastboot cmds that are run in the background, quick tools utilities, and tools for taking screenshots/screen-recordings. All the latest official Android builds and Nexus devices are supported. The program intelligently and selectively downloads the files it needs for your device and makes sure you are using the latest files available. The program can even auto-detect your device and build. This release brings full Marshmallow root support plus all automated features by utilizing a new system that no longer requires modified boot.imgs. Check out the updated changelog for a more comprehensive breakdown of the feature set and changes in this release.
~ my goal for this project is make the entire process as smooth and simple as possible ~
{
"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"
}
Please read the FAQs before posting questions: http://www.wugfresh.com/nrt/faqs/
Looking for a walk-through? >> Excellent Instructional/How-To Videos: http://www.wugfresh.com/videos/
More information & Download Links: http://www.wugfresh.com/nrt/
Changelog: http://www.wugfresh.com/nrt/changelog/
Enjoy! ^_^
{{ WugFresh }}
Reserved
*I am big fan of this device. Looking forward to using it as my daily driver, and very happy to extend NRT support*
just added to index
[INDEX] LG NEXUS 5X Resources Compilation Roll-Up
Nice to see you here WugFresh!
Good to see you, glad you've joined us :thumbup:
Hi! Very nice to see you here! You're always been my backup when I screw up something in the past with my nexus devices. I'm know I can always get back to stock with NRT
Verstuurd vanaf mijn Nexus 5X met Tapatalk
@WugFresh
Love your NRT on the Nmmexus 6. Glad you're here. Makes life a lot easier
I couldn't install busybox as mentioned in the instructions provided for "rooting", it's the last step (confirmation for root). It prompted me to change installation directory but system/bin doesn't work as well. And i can't boot recovery as well after the whole rooting process. It just shows me a dead android there
edit: i may have download stock recovery as well, as prompted by your toolkit after rooting.
#2 edit: reflashed twrp to solve my problems, but you may want to mention something to prevent something like that from happening again. Or maybe i'm just dumb
#3 edit: so sorry, it seems that the busybox provided was outdated, update it from playstore and installation will be good to go
imadiu said:
I couldn't install busybox as mentioned in the instructions provided for "rooting", it's the last step (confirmation for root). It prompted me to change installation directory but system/bin doesn't work as well. And i can't boot recovery as well after the whole rooting process. It just shows me a dead android there
edit: i may have download stock recovery as well, as prompted by your toolkit after rooting.
#2 edit: reflashed twrp to solve my problems, but you may want to mention something to prevent something like that from happening again. Or maybe i'm just dumb
#3 edit: so sorry, it seems that the busybox provided was outdated, update it from playstore and installation will be good to go
Click to expand...
Click to collapse
I am having BusyBox issues also.
mmartenn said:
I am having BusyBox issues also.
Click to expand...
Click to collapse
If you tried to install busybox right after you root your phone, as what the Root toolkit tells you to, it will not work like mine. That's because it's outdated. So just go to play store and update that app first before you reinstall any other app. I presume you rooted your device right after you unlock your bootloader which factory resets your device.
I have issue gaining write access to /system, busybox can't install to system/bin or system/xbin, had to install busybox through recovery.
also no /system write access through adb shell, it says system file read only
coolineho said:
I have issue gaining write access to /system, busybox can't install to system/bin or system/xbin, had to install busybox through recovery.
also no /system write access through adb shell, it says system file read only
Click to expand...
Click to collapse
Same problem here. Any solutions?
riceknight said:
Same problem here. Any solutions?
Click to expand...
Click to collapse
Not yet, still waiting ;(
I'm also facing the same issue, can't install busy box. It force closes after it fails to install. I tried updating to 124.1 but that didn't work, I also uninstalled and installed again from the playstore but that didn't work.
I also can't reboot into TWRP, unless I reboot through the NRT updater.
If I try to reboot normally without the updater, then I get the red warning message saying my phone is corrupt, followed by the green android robot with a red warning triangle coining out of it's stomach.
I'm running MDB08L
What I'm doing wrong?
Thanks
Sent from my Nexus 5X using Tapatalk
Install notes:
In options menu disable installing busybox, install busybox from play store after root process.
After root, Flashboot Flash Recovery in Advanced Utilities.
I have had no problems after using these steps.
I followed the steps above and busybox still wouldn't install so I found a 1.24.1 flashable zip flashed it and it worked . just another option to try if all others are not working
Does the "Restore: Flash Stock + Unroot" option completely wipe any trace of unlocking, rooting so that the phone could be sent to Google for repair. (I'm just asking, in case my screen breaks)
Tank87 said:
Does the "Restore: Flash Stock + Unroot" option completely wipe any trace of unlocking, rooting so that the phone could be sent to Google for repair. (I'm just asking, in case my screen breaks)
Click to expand...
Click to collapse
Yup, just did mine to send it back to google for warranty replacement of intermittent power button.
Guys here is a flashable zip. It's busybox 1.24.1 permissive. It's works 100% for me many times. If anyone wants 1.24.1 SElinux just let me know and I'll upload it
https://www.dropbox.com/s/e8tpfd4d8qcsqo5/Busybox-1.24.1.zip?dl=0
Sent from my Nexus 5X using Tapatalk
skulldreamz said:
Guys here is a flashable zip. It's busybox 1.24.1 permissive. It's works 100% for me many times. If anyone wants 1.24.1 SElinux just let me know and I'll upload it
https://www.dropbox.com/s/e8tpfd4d8qcsqo5/Busybox-1.24.1.zip?dl=0
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I just tried flashing this file (through twrp right?). It doesn't look like it worked through TWRP I got an "Updated process ended with error=1, error flashing 1.24.1.zip", and busybox is still not present on the phone when I restarted it. I tried downloading it from the play store directly and it still gives me the "it looks like it was not installed successfully" error message. Should I be flashing this file some other way? Thanks in advance!

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

Categories

Resources