Database Users

Update for root users with stock rom

Any body having problems updating maunauly after flashing cyanogens multitouch. Nexus cnat verify package. Can anyone help?

If the package can't be verified it's probably bad...or a corrupted download. Try downloading it again.

I tried downloading file three time and still get the same thing. Does it have to do anything with flashing cyanogens multitouch? should I wait for OTA update?

I too am having this issue. I am more than willing to donate to his hacking cause if I can just find a way to get this update. I am no opposed to flashing EVERYTHING back to factory. Please would someone look into this.

It's working now
artvandelay300 said:
I too am having this issue. I am more than willing to donate to his hacking cause if I can just find a way to get this update. I am no opposed to flashing EVERYTHING back to factory. Please would someone look into this.
Click to expand...
Click to collapse
I was able to process the update using a guide i found androidcentral . com
I am too new of a member to post links I guess. If you need this link feel free to let me know. Loving the new update

I'm having the same exact problem. Rooted my n1 to install cyanogen's multitouch and now when i try to manually install the OTA update it fails. I'm desperate for help >__< anyone have any tips?

Ok, so here's what I've learned over the last 18 hours.
If your phone is rooted, custom rom OR stock, you can't install the official update package, either over the air, or manually.
You CAN, however, install the patched version of it that modaco released here:
http://forum.xda-developers.com/showthread.php?t=627411
You'll need, at minimum, his 'main update,' and his 'radio update.
You'll also need his NEW VERSION of superboot, if you want to re-root your phone. Installing the updates breaks root, so you'll need this.
DO NOT use the old superboot that you previously used. It broke my Wi-Fi. Get the new one.
Additionally, you'll have to switch from the stock recovery program to Amon-Ra's recovery, available here:
http://forum.xda-developers.com/showthread.php?t=611829
The stock recovery program can only install official updates, and on a rooted phone, that doesn't seem to work. So use Amon-Ra.
So, to review here's the steps in the order you'll need to do them:
1. Install Amon-Ra Recovery 1.5.3
2. Install modaco's main update
3. Install modaco's radio update
4. Use fastboot to flash modaco's new superboot.img to re-root your phone.
Done!

Ok so assuming i follow that tutorial and break my root access, i'd be able install future OTA updates without having to go through all this again correct?
The only reason we can't install it manually now is because we're rooted so it would make sense to say that removing root access would let us perform future updates legit without having to find patches right?
I'm new to android and i honestly don't even need root privileges, i only wanted multitouch.

Well, to my understanding, no, you won't be able to install stock OTA updates, because your rom (your OS), is no longer stock, so stock updates will fail verification, like they did with this one.
I think you can probably restore OTA ability by reflashing your phone with the stock rom, thereby restoring it to the stock state. There's a very detailed tutorial here, with links to a stock image:
http://forum.xda-developers.com/showthread.php?t=614850
Also, here's a link that's stickied in the developer's forum for stock recovery options from modaco. Slightly less detailed, but it looks simpler to me:
http://forum.xda-developers.com/showthread.php?t=619801
I'm pretty sure that being rooted at all breaks OTA support, and having anything in the OS non-stock also breaks OTA support (ie the early MT browser). I could be wrong on that, but I think that's the case.

Crap. I wan't to try installing the stock rom but i'm looking at the directions and i can't follow them. I'm guessing all the things in bold are commands i have to run somewhere but i don't know where.

Yeah, it's a bit confusing, and a lot to get your head around.
You mean the fastboot commands?
You used fastboot when you rooted, right? To flash the superboot.img.
You have to plug your phone into your computer and reboot while holding down the trackball to get the fastboot screen (the white screen).
Then you put the stock images in the same directory as fastboot (which you should still have from when you rooted your phone with superboot) and flash them, using the commands from the tutorial page. (You run them from the command prompt or terminal, depending on what OS your computer has)

tonyx3 said:
So, to review here's the steps in the order you'll need to do them:
1. Install Amon-Ra Recovery 1.5.3
2. Install modaco's main update
3. Install modaco's radio update
4. Use fastboot to flash modaco's new superboot.img to re-root your phone.
Done!
Click to expand...
Click to collapse
Thanks Tony I was also a nub and trying to find the proper way to de-root my phone this worked 100%!

Deetz said:
Thanks Tony I was also a nub and trying to find the proper way to de-root my phone this worked 100%!
Click to expand...
Click to collapse
De-root? So you didn't re-root with the new superboot?
Also, you do know that your phone isn't stock now, right? And that future OTA updates will probably not work without similar steps?
If you followed those instructions, you now have the update, but it's a modded version of it, designed for non-stock roms.
Glad it worked, though!

tonyx3 said:
Yeah, it's a bit confusing, and a lot to get your head around.
You mean the fastboot commands?
You used fastboot when you rooted, right? To flash the superboot.img.
You have to plug your phone into your computer and reboot while holding down the trackball to get the fastboot screen (the white screen).
Then you put the stock images in the same directory as fastboot (which you should still have from when you rooted your phone with superboot) and flash them, using the commands from the tutorial page. (You run them from the command prompt or terminal, depending on what OS your computer has)
Click to expand...
Click to collapse
The tutorial i used to root my phone required me to download superboot and put the folder in my C: drive. The folder is called superboot but when i was running commands on the command prompt some of them said fastboot, so is superboot the same thing as fastboot? This is what that folder looks like:
{
"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"
}
Here's what i THINK i have to do.
Download the stock image, extract all the files and put it into the superboot folder i have on my C: drive. Then open up a command prompt and type in:
Code:
cd\
cd\superboot
adb reboot bootloader
fastboot devices
fastboot erase userdata
fastboot erase cache
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash system system.img
All while my n1 is plugged in while booted normally but with debugging enabled.
Is this correct or am i missing something?

Fastboot and superboot aren't the same thing.
Fastboot is the bootmode on your phone when you hold the trackball down while powering on. The one with the white screen and androids on skateboards. Fastboot allows you to connect via usb and the command prompt to run some commands on the phone, via your computer, such as flashing the img's on.
Superboot is the name of the img file you flashed (using fastboot), which alters the boot up settings on the phone, giving you root priveleges.
As for your list of commands, I think it looks right. Just do all the steps from the tutorial for restoring stock.
Yes, you start with the phone booted normally, but with debugging enabled. But when you use the adb reboot bootloader command, it will reboot into fastboot mode. You could skip that step and just turn your phone on while holding the trackball down.
Good luck!
And let us know how it goes, eh?

Oh ok cool, i think i get it now.
One last thing before i give it a try though, i was looking at step 11 but a file they want me to flash isn't in my superboot folder, even when i dump the stock firmware files in there. Do i have to get the file "system.img" from somewhere first and put it in the superboot folder or is it auto-generated some how?
Code:
Step 11. fastboot flash system system.img
-edit-
also, this is what my superboot folder looks like WITH the stock firmware files dumped into it:
The boxed files are from the unzipped firmware. Did i place them correctly?

Oh, I see.
The tutorial page has two links to stock roms.
But they seem to be in slightly different formats. The first one is hosted on rapidshare, and the second on modaco, right? So you downloaded
"22607-ERD79-update-nexusone-stock-signed.zip"???
That one has it in a different format from the instructions. Either download the one on rapidshare, or go here and get the "Image Format Download" :
http://android.modaco.com/content/google-nexus-one-nexusone-modaco-com/300414/18-jan-22607-erd79-stock-rom-for-nexus-one-images-update-zip-online-kitchen-optional-root-insecure/
(note: i've downloaded the one on rapidshare, but not the one on the modaco page I just linked, so I can't verify that they're identical, although they appear to be. I'm downloading the modaco one now, to check the md5sum)
Edit: I downloaded the modaco image in the link, and it is indeed exactly the same as the one hosted on rapidshare in the tutorial (the md5sums match)

Oh ok, ill try grabbing it now then.
I did a checksum for MoDoCos and got a mismatch. Zipped i get:
Code:
5e17b0351024c8fb1a2020f1fd55210e
and non-zipped is:
Code:
e4cf141242e1a362f136a8afd841e0f3
Either way, the rapidfire one is downloading so ill see if that has what i need
-edit-
Cool, the rapidfire md5sum matches up and has my missing file

PhantomRampage said:
Oh ok, ill try grabbing it now then.
I did a checksum for MoDoCos and got a mismatch. Zipped i get:
Code:
5e17b0351024c8fb1a2020f1fd55210e
and non-zipped is:
Code:
e4cf141242e1a362f136a8afd841e0f3
Either way, the rapidfire one is downloading so ill see if that has what i need
Click to expand...
Click to collapse
Right, the checksums won't match, cause the data is different zipped and unzipped. The math that it does on the data wont yield the same result. But the zipped one you posted matches mine. And the other download should match the md5sum posted in the tutorial.

Ok so everything went fine, i now have a non-rooted nexus one with an unlocked bootloader.
Unfortunately, i still cant manually install the OTA update I get:
Code:
E:Can't open /cache/recovery/command
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying current system...
assert failed: apply_patch_check(MTD:boot:20930
56:1d155a5be2f8cc6d7cef733f87f3bce97be2c3bd:2101
248:e7f20e513e5bd5c30e20670e992092296ee731a0")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
So what are my options now? Oh and thanks tony, i really appreciate your help

[GUIDE] Step by Step ROOT Nexus S via ClockworkMod Recovery image (i9020T only)

GRH78
Bootloader v.JK1
Baseband v.JK8
Yes, there are tons of guides out there, and even one click scripts that can ROOT the SNS (Samsung Nexus S) for you, but none of them go into enough detail for any of them to work properly.
Having many android devices working properly via ADB on your computer doesn't automatically guarantees it will see the SNS.
So, before jump to the exiting stuff of ROOTing the SNS, lets cover some basics to actually get you started and make sure you can actually ROOT the SNS, else all is in vain.
MOD EDIT: This guide does not apply to the AT&T/Rogers/Telus variants of the Nexus S (i9020A). For those models, please refer to this guide.
Part 1
Download Android SDK release 13 click the file name android-sdk_r13-windows.zip (34 MB) direct from Google, instead of wasting your time jumping through hoops and dodging pop up/flash ADs from those FileSharing places.
Note: from SDK release 14 onward, Google removed the fastboot command, you'll have to maker the fastboot command yourself if you want to use the latest version of the SDK
Turn Off your SNS
Make sure the SNS is connected to the PC via the USB cable
Boot the SNS into the Bootloader Interface, by holding Volume UP & Power button
{
"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"
}
it reads LOCK STATE - LOCKED
open Device Manager (or run devmgmt.msc) make sure you don't see this problem (windows failed to identify the SNS and install the correct drivers)
Do a right click and select Update Driver Software
Select Brose my computer for driver software
point it to where you downloaded the Android SDK (..\android-sdk-windows\google-usb_driver)
Make sure to CLICK "Let me pick from a list of device drivers on my computer"
Then from the list 3 choices select Android Bootloader Interface
If it's installed properly it should show up like this (reboot is not required)
NOTE: if you encounter problems like question marks, unknown drivers, or exclamation marks eve after you have installed the drivers, download and try the USBDeview 32/64 to remove and uninstall all the junk USB devices from your computer/registry​
Now that the basic preparations are done, we can finally get to have fun with the SNS & hack away via ADB.exe / FASTBOOT.exe
Part 2
open a command prompt go to run & type CMD hit enter
switch to the directory where you downloaded & unzipped the ..\android-sdk-windows\tools
type fastboot oem unlock and hit enter
Then you will get this
Code:
fastboot oem unlock
...
meanwhile on the SNS you'll see this screen
selecting YES will wipe EVERYTHING from the SNS, so make sure you have backed up everything you needed to safe before you continue.
use the Volume up/down keys to select and Power key to apply
you should see something like this after it's done
Code:
... OKAY [435.433s]
finished. total time: 435.433s
now back on this screen you should read
LOCK STATE - UNLOCKED
Download the clockwork recovery recovery-clockwork-5.0.2.0-crespo.img image, and save it to the ..\android-sdk-windows\tools directory
renamed it to recovery.img
then type fastboot flash recovery recovery.img and hit enter
you should get something like this, if not your image is corrupted, download it again
Code:
sending 'recovery' (3980 KB)... OKAY [ 0.621s]
writing 'recovery'... OKAY [ 0.511s]
finished. total time: 1.132s
Then back on the SNS select Power Off (Reboot also works)
Power ON the SNS
...meanwhile the SNS is rebooting Download superuser from http://forum.xda-developers.com/showthread.php?t=682828
choose the Eclair/Froyo version
Mount the USB storage
droidmage said:
So all you guys who are having trouble getting root inside the rom, When your in recovery before you flash the superuser.zip file select -- mounts and storage -- then --mount /system -- then flash the .zip file and reboot
Click to expand...
Click to collapse
drag/drop the su-version#-signed.zip file into the root of the internal SD of the SNS
Power Off the SNS
Boot the SNS into the Bootloader Interface, by holding Volume UP & Power button
select Recovery
then it should boot into this screen, if not then repeat the steps to download the image
select install ZIP from sdcard (power button to apply)
select choose zip from sdcard (power button to apply)
select su-version#-signed.zip file you downloaded earlier, and apply it
select yes - install su-version#-signed.zip
confirm it says "Install from sdcard complete"
select go back
select reboot
done!
Enjoy your unlocked & rooted phone!

NOTES:
It's normal to lose the recovery after the reboot, the steps to flash the CW recovery needs to be repeated every time you want to access the CW recovery.
This is due the build in protection in 2.3
As some one pointed it out on another topic, the good thing about this is that you'll never lose the stock recovery of 2.3, thus minimizing the chance of a bricked phone.
If you want to the CW recovery to remain permanently, you'll need to rename /etc/install-recovery.sh to something thing else
To simplify things with the Command Line, it's best to copy and paste the contents inside ..\android-sdk-windows\platform-tools to ..\android-sdk-windows\tools
that way you'll have all the necessary files in the same location to prevent errors
MIRROR:
since CW website seems to be down, here's a mirror for the Image file.
download the 7zip attachment, unzip and flash recovery.img (recovery-clockwork-5.0.2.0-crespo.img)

Good guide but i have a question,
didn't you miss the step about renaming the install-recovery.sh script
that reflash recovery if crc is wrong?

Thank you sir, I was hoping for a good step-by-step guide for us first-timers.

Nice guide.
The only thing that's making me hesitate to do root on my NS is reversing the whole process...
stock recovery for example. I know someone made a backup of it but some people are stating odd results of using that backed up stock recovery... wifi broke, missing apps, mobiles stuck on EDGE...
I'll wait until google releases a firmware that contains everything

Cubfan185 said:
Thank you sir, I was hoping for a good step-by-step guide for us first-timers.
Click to expand...
Click to collapse
thank you, that was the idea.
many of the GUIDEs we have here are usually aimed at people that already knows what to do, which usually leaves out all the 1st time owners of the phone.

it's fairly simple, the instructions are as simple as this
http://forum.xda-developers.com/showthread.php?t=884097
and you can choose any stock ROM to flash back
sinatosk said:
Nice guide.
The only thing that's making me hesitate to do root on my NS is reversing the whole process...
stock recovery for example. I know someone made a backup of it but some people are stating odd results of using that backed up stock recovery... wifi broke, missing apps, mobiles stuck on EDGE...
I'll wait until google releases a firmware that contains everything
Click to expand...
Click to collapse

Alright, just did it successfully. I had a few problems when installing the SDK and using fastboot. The recovery image must have been corrupt a few times for me. I had to take the battery out because it was stuck at the Google screen. My heart skipped a beat at that point, I didn't want to brick anything. Also had to put a required .dll file in the tools directory and the drivers were giving me problems, but got it all figured out. Thanks again.
Edit: Any reason why root required apps are saying they don't have root access?

Will Google definatly release a full restore firmware of the current ROMS, something simular to an HTC RUU, or is it just something we're hoping they'll do?

silly question... which fastboot binary did you use? the one from the htc developer site?

onicrom said:
silly question... which fastboot binary did you use? the one from the htc developer site?
Click to expand...
Click to collapse
it is included in the Android SDK 2.3 ... read the step by step guide again

Great guide, I'm new to the SDK and adb and fastboot so this helped a lot. My phone crashed last night and I had to completely restore it. Biggest upset is I was racing my girlfriend to beat Angry Birds Seasons and now my save games are gone. Along with other app data and all my settings.
So the Nexus S is stock what I root phones to get to. I love the pure Google experience. Never had one completely crap out crash though.
I followed your guide to the tee and got it what I thought would be rooted. When I get to the end though I boot up and the ClockworkMod ROM Manager v3.0.0.2 says "You must root your phone for ROM Manager to function. Superuser was not found at "/system/bin/su" or "/system/xbin/su". Also Superuser app says there is an update available, then tries to install and says it can't. So it puts the update zip on my root of my storage. I boot into CMR and try to install that and it errors saying it's not there. But it is when I look is mass storage mode from my computer.
I boot into clockwork mod recovery just like your guide says the bootloader says unlocked. I don't get it. What did I miss? Only reason I want to root is to use Titanium backup. I really wish google had a better backup system for app data but they don't... yet. So I don't want what happened last night to happen again.
Thanks in advance,
JB
Nexus S, stock rom just want root access for backup.

AllGamer said:
NOTES:
It's normal to lose the recovery after the reboot, the steps to flash the CW recovery needs to be repeated every time you want to access the CW recovery.
This is due the build in protection in 2.3
As some one pointed it out on another topic, the good thing about this is that you'll never lose the stock recovery of 2.3, thus minimizing the chance of a bricked phone.
Click to expand...
Click to collapse
Hmmm I miss this post. Does this happen with 2.3.1 aswell and root will still be on after reboot?
If so. I'm rooting RIGHT NOW!!!
Thank-you
edit: I did some searching and found the answer ... there is a file at "/etc/install-recovery.sh". that restores your recovery back to stock upon reboot while still retaining root ( 2.3 and 2.3.1 ). As stated previously... you simply re-flash the recovery to get to the recovery again

sinatosk said:
Hmmm I miss this post. Does this happen with 2.3.1 aswell and root will still be on after reboot?
If so. I'm rooting RIGHT NOW!!!
Thank-you
edit: I did some searching and found the answer ... there is a file at "/etc/install-recovery.sh". that restores your recovery back to stock upon reboot while still retaining root ( 2.3 and 2.3.1 ). As stated previously... you simply re-flash the recovery to get to the recovery again
Click to expand...
Click to collapse
yes, i actually like it this way, it keeps your original safe

Titanium Backup and few other apps are why i ROOT the phone as well.
after you fastboot over the CW recovery image and rooted, were you able to install Super User?
there is another trick, you can Install Super User first from Market
then repeat the steps to fastboot the clock work recovery image and get root access
jvblack82 said:
Great guide, I'm new to the SDK and adb and fastboot so this helped a lot. My phone crashed last night and I had to completely restore it. Biggest upset is I was racing my girlfriend to beat Angry Birds Seasons and now my save games are gone. Along with other app data and all my settings.
So the Nexus S is stock what I root phones to get to. I love the pure Google experience. Never had one completely crap out crash though.
I followed your guide to the tee and got it what I thought would be rooted. When I get to the end though I boot up and the ClockworkMod ROM Manager v3.0.0.2 says "You must root your phone for ROM Manager to function. Superuser was not found at "/system/bin/su" or "/system/xbin/su". Also Superuser app says there is an update available, then tries to install and says it can't. So it puts the update zip on my root of my storage. I boot into CMR and try to install that and it errors saying it's not there. But it is when I look is mass storage mode from my computer.
I boot into clockwork mod recovery just like your guide says the bootloader says unlocked. I don't get it. What did I miss? Only reason I want to root is to use Titanium backup. I really wish google had a better backup system for app data but they don't... yet. So I don't want what happened last night to happen again.
Thanks in advance,
JB
Nexus S, stock rom just want root access for backup.
Click to expand...
Click to collapse

Followed the guide to a T as well and did not get root access. But unlocking the bootloader, installing the SDK and learning about fastboot and such was very helpful. Using that, I used the automated batch file posted in this topic http://forum.xda-developers.com/showthread.php?t=882333 and it worked.

What to do if my Device Manager showed Android 1.0?

ykphuah said:
What to do if my Device Manager showed Android 1.0?
Click to expand...
Click to collapse
you select the correct driver to install the ABD support or Bootloader support, depending in which screen you have the phone on
just review the step by step guide, it is mentioned there

sinatosk said:
Nice guide.
The only thing that's making me hesitate to do root on my NS is reversing the whole process...
stock recovery for example. I know someone made a backup of it but some people are stating odd results of using that backed up stock recovery... wifi broke, missing apps, mobiles stuck on EDGE...
I'll wait until google releases a firmware that contains everything
Click to expand...
Click to collapse
If you're running 2.3.1 all you need to do to get back to stock recover is reboot the phone, because /etc/install-recovery.sh runs every boot and checks to see if the recovery is stock or not...if not it flashes it for you. So unless you've renamed the /etc/install-recovery.sh file you can easily get stock recovery.

knytphal said:
If you're running 2.3.1 all you need to do to get back to stock recover is reboot the phone, because /etc/install-recovery.sh runs every boot and checks to see if the recovery is stock or not...if not it flashes it for you. So unless you've renamed the /etc/install-recovery.sh file you can easily get stock recovery.
Click to expand...
Click to collapse
... yeah I know. Made a post earlier today about it in this thread...

[Q] error updating nexus 7 stock rooted to 4.2.2

hello guys, i know there are a lot of threads for this but i dont have time.i have a rooted nexus 7 with stock and i dont have custom recovery. i got an error when I updated it via OTA. Any easy solution to solve this???
P.S. I am a NEW newbie

It helps if you provide the error message you receive in recovery.
You may have removed or nodded a file in /system a while ago and forgot. If that's the case, you need to acquire the stock 4.2.1 files and replace them before trying the OTA again.
Since you're rooted, I'd suggest using OTARootKeeper to temp remove root for the OTA flash.
Sent from my Nexus 7 using Tapatalk 2

nikon120 said:
It helps if you provide the error message you receive in recovery.
You may have removed or nodded a file in /system a while ago and forgot. If that's the case, you need to acquire the stock 4.2.1 files and replace them before trying the OTA again.
Since you're rooted, I'd suggest using OTARootKeeper to temp remove root for the OTA flash.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
First of all there was no error message displayed.only the android with red exclamation was on the screen.
secondly i am already on stock...so i think my files are ok
i am going to temp unroot with OTA rootkeeper and update it again...thx

Flash Custom Recovery
mmystere68 said:
First of all there was no error message displayed.only the android with red exclamation was on the screen.
secondly i am already on stock...so i think my files are ok
i am going to temp unroot with OTA rootkeeper and update it again...thx
Click to expand...
Click to collapse
U are now on Stock Recovery
first flash Custom recovery (CWM or TWRP) :angel:
then flash that zip file through that recovery :laugh:

kerneldev said:
first flash Custom recovery (CWM or TWRP) :angel:
then flash that zip file through that recovery :laugh:
Click to expand...
Click to collapse
Can i flash custom recovery with my tab only(no computer available right now)???
which zip file should i flash through the recovery???
will i still be able to receive OTA updates from google afterwards???
i backed up root with OTArootkeeper...will it restore the root after update?

mmystere68 said:
Can i flash custom recovery with my tab only(no computer available right now)???
which zip file should i flash through the recovery???
will i still be able to receive OTA updates from google afterwards???
i backed up root with OTArootkeeper...will it restore the root after update?
Click to expand...
Click to collapse
U can flash custom recovery through GooMAnager app

kerneldev said:
U can flash custom recovery through GooMAnager app
Click to expand...
Click to collapse
Hi...I installed goomanager and flashed twrp custom recovery while flashing android 4.2.2 zip I got a status 7 error.....help me please...
BTW after the update how do I return to stock recovery???

Saome issue here, identical behavior. Restarted to get back to 4.2.1.
Sent from my Nexus 7 using xda app-developers app

init3 said:
Saome issue here, identical behavior. Restarted to get back to 4.2.1.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Maybe you havent renamed browserproxybrovider odex file to original name? You have to change that file in order to use the AOSP (stock) browser.
Thats the reason i rooted.
Restore browserproxyprovider (if you changed it), restart the device, open ota rootkeeper and temporarly unroot, update.
Worked for me

Not sure, I'm having stock 4.2.1 rooted.
Update has been downloaded, asked for reboot, and then...
Boom. Error. Nothing explicit unfortunately.
Sent from my Nexus 7 using xda app-developers app

kerneldev said:
U are now on Stock Recovery
first flash Custom recovery (CWM or TWRP) :angel:
then flash that zip file through that recovery :laugh:
Click to expand...
Click to collapse
i did exactly as u said...but when flashing the update i got a status 7 error....help me plz
{
"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"
}

mmystere68 said:
i did exactly as u said...but when flashing the update i got a status 7 error....help me plz
Click to expand...
Click to collapse
Hello mmystere68,
I had exactly the same problem, my screen looked identical to yours.
I interpreted the report as a corrupt 4.2.1 system and decided to replace it.
Now I have a working 4.2.2 whit user data intact, so should you by .
1. Downloading Nexus 7 toolkit 4.0 from http://forum.xda-developers.com/showthread.php?t=1809195 this thread.
2 Choosing my present build from the list
3 Installing nexus 7 drivers thru the toolkit (option 1)
4. Downloading and flashing a fresh 4.2.1 thru the toolkit (option 9) (there is an option not to wipe user data)
5: Rooting thru the toolkit (option 4)
6 Flashing CWM (option 6)
7. Enter recovery, flash the 4.2.2 update choose not to flash stock recovery and choose to fix root.
You´re done and should have a working rooted 4.2.2
Best regards
Magnus

You folks ought to look at those error messages closely, rather than simply saying "I got Status 7!"
Status 7 is a generic failure code meaning that any one out of hundreds of different assert() checks failed.
In the OP's case, the specific file involved is the framework file mentioned.
Just because you have "rooted stock" on your phone does not mean you are immune from these problems.
The OTA process performs binary patching on individual files. In order for that to work, the file targeted for patching must be identical to the original. So, the OTA first performs checksum verification of each and every file that will be patched before any patching activity begins. Worse yet, it stops immediately on the first check that fails.
So, for example the OP has a problem with that framework file. It is possible that if he were to dig that file out of a pure stock ROM, and get it copied into his existing ROM ( being careful to pay attention to user/group file ownership and permissions) that the OTA would now run to completion. But it is also possible that there are a few or even many more files that also got altered, so the next time the OTA is attempted, it will again give a "Status 7" message - but now involving a different file. this is a consequence of the stop-on-first-fail behavior of the OTA.
That's why I said: Look at the error message CAREFULLY!
OK, now back to the assertion "but I only rooted stock - I didn't change anything!"
Well, if you gave root privilege to apps, that app might have changed something.
I don't know what causes the OP's framework file problem, but (for instance) I see reports on here where Stickmount and Beats are altering files in /system.
The good thing about these OTA checks is that 100% of them are performed before any patching begins. So you can certainly just iterate the OTA process replacing files one at a time with the original stock version until you are successful. Please make sure you have a full Nandroid backup before you begin, though. I wouldn't do this with anything but a lightly-rooted stock ROM though - too many potential file differences would make this a laborious process.
BTW, there are reports on here that on tilapia/3g N7's that custom recoveries can complete the OTA but fail on the radio firmware install. This puts those folks in a catch-22 situation: since all the other files get patched, the OTA will no longer run, as 100% of the regular files no longer match the anticipated checksum(s) of the prior ROM versions.
OK, one last thing - even when the stock recovery fails the update and does not produce an on-screen error message, I believe the error meassage can still be found: boot to your rooted ROM and have a look for the recovery log file in /cache/recovery.
cheers

magno said:
Hello mmystere68,
I had exactly the same problem, my screen looked identical to yours.
I interpreted the report as a corrupt 4.2.1 system and decided to replace it.
Now I have a working 4.2.2 whit user data intact, so should you by .
1. Downloading Nexus 7 toolkit 4.0 from http://forum.xda-developers.com/showthread.php?t=1809195 this thread.
2 Choosing my present build from the list
3 Installing nexus 7 drivers thru the toolkit (option 1)
4. Downloading and flashing a fresh 4.2.1 thru the toolkit (option 9) (there is an option not to wipe user data)
5: Rooting thru the toolkit (option 4)
6 Flashing CWM (option 6)
7. Enter recovery, flash the 4.2.2 update choose not to flash stock recovery and choose to fix root.
You´re done and should have a working rooted 4.2.2
Best regards
Magnus
Click to expand...
Click to collapse
Seems like a long process to me and I don't have a PC to do all that stuff right now....I think I am going to stick to 4.2.1 for the time being.... BTW will I still have this problem for when 'key lime pie' is out?
Last question : how do I return to stock recovery without losing data and having to use a PC

I am having the same issue. 4.2.1, rooted with the stock recovery. It downloads the OTA update and when it reboots to install it gets about 25% of the way in and then goes to an ERROR! screen. Reboots into 4.2.1 a few seconds later. I am hearing that it may be caused by installing Beats audio. I uninstalled it but no change. I have not messed with the toolkit much, and I don't want to lose my data.

Most sound mods install patched files. You don't say how you removed it. But if any files were left behind then you will not be able to install the update.
I know with KingBeatz the only way to truly restore is to reflash the ROM you are on.
Note 2 - Charge - Player 5.0 - Fascinate
<><><><><><><><><><>
Read more, Post less
Read twice, flash once
Assume good intentions

let me share how to update ota ^^
Remove google patch.
Use super su. Unroot your nexus .
Then use twrp recovery.
Go to cache select the 4.2.2 ota update.
Unmark all verification and flash the 4.2.2 update zip.
Flash cwm-supersu-v0.99.zip to root back your nexus 7.
Reboot and download super su at google play.
Poof!! 4.2.2 rooted nexus 7 without wipe anything

the 4.2.2 zip OTA name
6ece895ecb23.signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip (it is inside root/cache file.)
Or you can use nexus manager in google play to download the OTA update.

konwaikong said:
Remove google patch.
Use super su. Unroot your nexus .
Then use twrp recovery.
Go to cache select the 4.2.2 ota update.
Unmark all verification and flash the 4.2.2 update zip.
Flash cwm-supersu-v0.99.zip to root back your nexus 7.
Reboot and download super su at google play.
Poof!! 4.2.2 rooted nexus 7 without wipe anything
Click to expand...
Click to collapse
i dont quite understand...is there a video tutorial for this???

How to remove Google patch??
Tried it....doesn't work...I get the same error when flashing the update zip

[OTA] How to capture Android 5.0 Lollipop official firmwares

{
"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"
}
Welcome to the Official Motorola Lollipop firmwares thread.
Here you will find the Firmware images of Lollipop for Moto G 1st generation once available.​
It will be useful to have all variants of the awaited OTA here, since all devices have some differences in hardware, so here I will be placing all OTAs once they are released.
How to capture an Over The Air update?
If you want to contribute with your specific carrier OTA, once your OTA is available, do this:
Download the OTA but don't install it yet. With a ROOTED DEVICE, use some root explorer and go to /cache folder inside the root folder of the phone and copy the downloaded ZIP file to your emulated SD card, then copy it to your PC, upload it to any server you like and submit the link here to have all firmwares in one site.
The OTA will be named like Blur_Version.173.44.9.falcon_umts.Latam.en.AR (this is an example of an Argentinian retail Moto G 4.4.4 OTA ZIP package).
As I said, you need a ROOTED DEVICE to do this, so, if you want to contribute to this database, do all this procedure and unroot your device, or restore your firmware with this guide to make a clean install of the new firmware.
Click to expand...
Click to collapse
LINKS​
Comming soon​
All contributors will be named here:
Thanks to:
* @lost101 for the /cache directory info

That's just my opinion but should related to android L threads be created once we at least will know when it comes? Or even better when it will be released?
There is already one thread have been closed http://forum.xda-developers.com/moto-g/general/lollipop-t2929720
I'm just saying that this thread is kinda pointless for now.

Yea I thought placeholder threads weren't allowed on XDA

S0bes said:
That's just my opinion but should related to android L threads be created once we at least will know when it comes? Or even better when it will be released?
There is already one thread have been closed http://forum.xda-developers.com/moto-g/general/lollipop-t2929720
I'm just saying that this thread is kinda pointless for now.
Click to expand...
Click to collapse
The thread you mention is useless.. But this will be useful since it will take no more than some weeks to see the update. So this thread can be opened right now, since I give info and instructions to capture an OTA to share with everybody when it is available... And I'll put my OTA for Arg retail Moto G here..

alexkta said:
Yea I thought placeholder threads weren't allowed on XDA
Click to expand...
Click to collapse
This is not just a placeholder, since I give instructions to capture the OTAs when they come up.. To anyone who wants to help with this database I give that instructions with some time before the OTAs roll out.

There is already a thread for Motorola Firmware Images. Please keep this thread OTA Updates only, and reword the OP to reflect this.

Cool..! This will have good database of Android L OTA's for all variants and easier to grab them once available in a single thread. But please make sure you update the OP as soon as someone shares in posts :good:
I think you can even add Variant names in advance at OP like XT1033 , XT1032 so on.

"Official" ? OP work for Motorola?
If not then its a community effort which is better than Official in my view

MarckozZ said:
The thread you mention is useless.. But this will be useful since it will take no more than some weeks to see the update. So this thread can be opened right now, since I give info and instructions to capture an OTA to share with everybody when it is available... And I'll put my OTA for Arg retail Moto G here..
Click to expand...
Click to collapse
Sent from my XT1033 using XDA Free mobile app

Thanks for this, helped me capture my 5.1 OTA update

actually I have found a way to capture the OTA without root,
step 1. download the OTA but dont install it..
step 2. power off the device and boot into bootloader mode
step 3. flash custom recovery like twrp 2.8.6.0 (fastboot flash recovery twrp-recovery.img)
step 4. boot into the custom recovery, go to the file manager and go the /cache/ folder
step 5. copy the update file from the cache folder, and paste into the main sdcard root area
step 6. connect the phone to the computer via usb cable while in recovery mode
step 7. copy the update file to the computer.
now to install the update, just reboot back into bootloader mode, flash the stock recovery back with fastboot (fastboot flash recovery recovery.img)
step 8. enter stock recovery mode (to show options - hold power and volume up for 3 seconds)
step 9. apply update from sdcard (you will see the update file still there - Blur_Version.XX.zip)
This works, I have tried this 3 times before on 5.0.2 firmware.

AgentChaos said:
actually I have found a way to capture the OTA without root,
step 1. download the OTA but dont install it..
step 2. power off the device and boot into bootloader mode
step 3. flash custom recovery like twrp 2.8.6.0 (fastboot flash recovery twrp-recovery.img)
step 4. boot into the custom recovery, go to the file manager and go the /cache/ folder
step 5. copy the update file from the cache folder, and paste into the main sdcard root area
step 6. connect the phone to the computer via usb cable while in recovery mode
step 7. copy the update file to the computer.
now to install the update, just reboot back into bootloader mode, flash the stock recovery back with fastboot (fastboot flash recovery recovery.img)
step 8. enter stock recovery mode (to show options - hold power and volume up for 3 seconds)
step 9. apply update from sdcard (you will see the update file still there - Blur_Version.XX.zip)
This works, I have tried this 3 times before on 5.0.2 firmware.
Click to expand...
Click to collapse
Thanks for that, for ages I didn't know how to get the recovery options!

Repairing Nexus 6 Marshmallow 6.0 Failed Root

If your stupid like me :silly: and you blindly follow the [HOW-TO] The Nexus 6 All-In-One Beginner's Guide you may be trying to figure out how to fix your phone.
The beginner guide linked above is amazing to say the least but the OP has not updated it yet to reflect the 6.0 update. If your phone has Marshmallow 6.0 and you follow the instructions you will render your Nexus 6 unusable. Not bricked, just not functional. You will get an error that states Your device is corrupt. It can't be trusted and may not work properly. (seen below) Followed by a blank screen. But don't worry, its very easy to fix with just a few extra steps. :fingers-crossed:
{
"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"
}
If you are here, it is assumed that you have already done the following steps:
Step 0.1 Download and install the Android SDK tools (adb and fastboot), as well as the Google USB drivers. This is step 2 in the beginner guide and there is a great write up here on these tools. [noob-read] adb and fastboot. What is it? How can it help you?
Step 0.2 Unlocked the Bootloader.
Step 0.3 Ran the CF-Root tool. The file name is CF-Auto-Root-shamu-shamu-nexus6.zip
If you watched the CMD window closely this is where the problem happened. There will be a couple errors thrown. You will wait to see the big red Android on your phone but instead you will see the above warning message flash briefly followed by a black screen. If this is the case, proceed to step 1​
Please Note: Parts of these steps are copied and pasted from other instructions. Consider this a grouping of other instructions for the purpose of simplification.
Step 1 - Install a Custom Recovery (taken from the original guide)
Go HERE to download the latest TWRP recovery for the Nexus 6. At the time of this write-up, I used 2.8.5.0
Turn the phone off. Then boot it into the bootloader/fastboot mode by holding volume down + power.
Rename the recovery file that you downloaded above to recovery.img. *Make sure that you rename it to recovery.img NOT recovery.img.img
Move the recovery.img file to C:\Program Files (x86)\Android\android-sdk\platform-tools
Open command prompt and run the following commands:
Code:
cd C:\Program Files (x86)\Android\android-sdk\platform-tools
Code:
fastboot flash recovery recovery.img
On the phone, use the volume buttons to scroll onto "Restart Bootloader" and hit power to select it.
After the bootloader reloads, use the volume buttons to scroll onto "Recovery Mode" and power to select it. You should then be greeted with your newly installed custom recovery.
Power off the phone
Step 2 - Install the Modified boot.img (Original steps HERE)
Download the modified boot.img from http://downloadmirror.co/android/sx/shamu-mra58k-boot.zip
Unzip the file and move it to C:\Program Files (x86)\Android\android-sdk\platform-tools
Boot the phone back into bootload mode using Power + volume down.
Open a command prompt and enter the following commands:
Code:
cd C:\Program Files (x86)\Android\android-sdk\platform-tools
Code:
fastboot flash boot boot.img
Power off the phone
Step 3 - Flash the SuperSU zip via TWRP Recovery v2.56 beta (original steps HERE)
Downlaod SuperSU x2.56 from http://downloadmirror.co/android/u1/SuperSU-v2.56-20151030013730.zip
Boot your phone into the bootloader mode with Power + volume down
Enter recovery mode. This will open TWRP Recovery
After TWRP Recovery is open, connect your phone to your computer.
Open My Computer where youc an see the C: drive, and other connected drives. You should see your Nexus 6 listed. Open it.
Move the SuperSU zip onto your phone. I placed mine in the TWRP folder.
On your phone, select Install, then navigate to the folder that contains the SuperSU zip. Click on the zip file.
Swipe to Confirm Flash and begin the flash.
Once SuperSU is flashed, select the Reboot System option.
And that's it, your phone should now boot back up to your fresh rooted copy of Android Marshmallow 6.0. You can download a root verification app to confirm the root. :victory:

all i did was flash a twrp flashable stock marshmallow, then a custom kernel and supersu(in twrp). no odd message, everything booted fine

simms22 said:
all i did was flash a twrp flashable stock marshmallow, then a custom kernel and supersu(in twrp). no odd message, everything booted fine
Click to expand...
Click to collapse
You followed the correct instructions haha. That is basically what those 3 steps above entail, but broken down well enough they could be followed by someone who has not rooted a phone in the past. You also have to consider that if they followed that original beginner guide they can no longer boot into android, which kind of induces panic in most of us newbies and it makes it hard to search for and find the right answers. So basically this guide picks up right at the point where you realized "oh crap my phone didn't boot up like the instructions said it would, and now it won't turn on" :crying:
For those of us who have been down this road a time or two, this guide will not help them at all. Its really just directed to newbie's who are now stuck because of the beginner guide above.

K!ngpen said:
You followed the correct instructions haha. That is basically what those 3 steps above entail, but broken down well enough they could be followed by someone who has not rooted a phone in the past. You also have to consider that if they followed that original beginner guide they can no longer boot into android, which kind of induces panic in most of us newbies and it makes it hard to search for and find the right answers. So basically this guide picks up right at the point where you realized "oh crap my phone didn't boot up like the instructions said it would, and now it won't turn on" :crying:
Click to expand...
Click to collapse
key word, that gets very many in trouble afterwards.. "panic".
yea, i remember those days. but i was very lucky, as i never paniced. when i first rooted my g1(beginning of 2009), there were not very many people that knew about android, nor much info about it. so most of what we did back then was lots of trial and error :angel:

simms22 said:
key word, that gets very many in trouble afterwards.. "panic".
yea, i remember those days. but i was very lucky, as i never paniced. when i first rooted my g1(beginning of 2009), there were not very many people that knew about android, nor much info about it. so most of what we did back then was lots of trial and error :angel:
Click to expand...
Click to collapse
I'm right there with you. My first rooted device was a motorola xt720 sometime in 2010 I think. It was a company phone and like most very young IT folk I was curious lol. New versions of Android started rolling out but the phone wasn't going to get the update. So i was suck on Eclair. I stayed after work and tried the root, and it didn't work to say the least... I stayed at work until 2am trying to get that darn thing to work. 3 days later I got it to flash cyanogen. It was buggy as hell but i didn't care because I didnt have to explain to my boss that I broke my phone by trying to "hack" it lol. That was a win in my book. I later worked up the courage to get it back on a rooted version of Froyo. Pretty bumpy start to my rooting career to say the least. Now I'm a die hard Nexus follower just looking for an excuse to root the next device.

K!ngpen said:
You followed the correct instructions haha...
Click to expand...
Click to collapse
Everyone who is trying to help other users earns respect.

Thanks for this. it got me 98% there but SuperSU says i need to update the binary. Its gives me the option to update normally which fails or to update through twrp. Im not sure how to update through twrp. Any suggestions?

Noopguy said:
Thanks for this. it got me 98% there but SuperSU says i need to update the binary. Its gives me the option to update normally which fails or to update through twrp. Im not sure how to update through twrp. Any suggestions?
Click to expand...
Click to collapse
Just to confirm, your phone now boots back up correctly, but you get the popup stating that the binaries for SuperSU are missing?

K!ngpen said:
Just to confirm, your phone now boots back up correctly, but you get the popup stating that the binaries for SuperSU are missing?
Click to expand...
Click to collapse
Not missing but needs updating. My phone boots up and everything seems to fine otherwise. I tried updating with the normal option but it fails and going into twrp does nothing. I just cant figure out how to update the binaries with twrp. I tried to post a screen shot but XDA wont let me post a link since im a new user. imgur.com/a/Jgwpt

Noopguy said:
Not missing but needs updating. My phone boots up and everything seems to fine otherwise. I tried updating with the normal option but it fails and going into twrp does nothing. I just cant figure out how to update the binaries with twrp. I tried to post a screen shot but XDA wont let me post a link since im a new user. imgur.com/a/Jgwpt
Click to expand...
Click to collapse
And this was an unrooted nexus 6 with android 6.0 when you started? It wasn't already rooted on a lower version of android or anything like that?

K!ngpen said:
And this was an unrooted nexus 6 with android 6.0 when you started? It wasn't already rooted on a lower version of android or anything like that?
Click to expand...
Click to collapse
No i had it rooted on 5.1.1 this morning and updated to 6.0 with a factory image. I ran into problems rerooting after the update and I came here. I used your guide and everything works except i cant figure out how to update the binaries for SuperSU.

Noopguy said:
No i had it rooted on 5.1.1 this morning and updated to 6.0 with a factory image. I ran into problems rerooting after the update and I came here. I used your guide and everything works except i cant figure out how to update the binaries for SuperSU.
Click to expand...
Click to collapse
If you sideload this through TWRP you shouldn't need to update the binaries. It has the latest included.

Noopguy said:
I tried updating with the normal option but it fails and going into twrp does nothing. I just cant figure out how to update the binaries with twrp.
Click to expand...
Click to collapse
Flash SuperSU 2.52 Beta (not 2.56), then boot into Android and select "Update SuperSU Binaries" and select "TWRP/CWM" option rather than "Normal". Worked for me.
alryder said:
If you sideload this through TWRP you shouldn't need to update the binaries. It has the latest included.
Click to expand...
Click to collapse
I still needed to.
I'm on MRA58R, BTW (the third and latest factory image for Nexus 6).

sjgore said:
Flash SuperSU 2.52 Beta (not 2.56), then boot into Android and select "Update SuperSU Binaries" and select "TWRP/CWM" option rather than "Normal". Worked for me.
I still needed to.
I'm on MRA58R, BTW (the third and latest factory image for Nexus 6).
Click to expand...
Click to collapse
That's strange, I sideloaded that for MRA58K, MRA58N and MRA58R and I don't think I was ever prompted to update the binaries. I'm not sure you are being asked to.

alryder said:
If you sideload this through TWRP you shouldn't need to update the binaries. It has the latest included.
Click to expand...
Click to collapse
Thanks guys, this really helped. Flashing 2.52 did the trick and i didnt need to update the binaries after i flashed it. I am also on MRA58R

I was going to say as well, SuperSU v2.52 is what needs to be installed via TWRP, not v2.56. I believe v2.56 is for the new systemless root option but it sounds less stable and buggy.

Does this wipe any data? I have been looking to root and actually followed that guide myself, got the same issue and fixed by reflashing a factory image.
EDIT: I'm assuming I don't have to break my phone again to do this correct? Can I just pick up from step 1 to flash the recovery and go from there?

Something weird happened to me after flashing TWRP and I thought I'd share. So my N6 wasn't corrupted at all, but I decided to root my phone and I started by flashing TWRP. I went into boot loader and then recovery to make sure it worked and it did. When I went to reboot the system, I got the the "your device is corrupt screen." I pressed the power button and the screen turned black for a few seconds and then it rebooted normally. I went back into recovery to try and reproduce this and it happened again, Not sure why this happened but everything is functional.

New to rooting and I want to root my Nexus 6
I have a Verizon Nexus 6 with the build number "MRA58R." I haven't unlocked the bootloader or ran CF-Root tool like Steps 0.2 and 0.3 say. To root my phone, should I try and purposely break it by following the All-In-One Beginner's Guide and then follow the steps you put? Or is there another way I should go about rooting it? Thanks for your help

atvisic said:
I have a Verizon Nexus 6 with the build number "MRA58R." I haven't unlocked the bootloader or ran CF-Root tool like Steps 0.2 and 0.3 say. To root my phone, should I try and purposely break it by following the All-In-One Beginner's Guide and then follow the steps you put? Or is there another way I should go about rooting it? Thanks for your help
Click to expand...
Click to collapse
Lol why break it first. I didn't read through the op here but all you need to do is unlock the bootloader. Flash twrp with fastboot. Reboot to recovery without booting the phone, if you boot the phone before going into twrp it will get overwritten and you will need to reflash it. Flash a custome kernel in twrp, flash SuperSU 2.52 or higher in twrp.
The instructions in the op are more complete naturally. But when it has you flash the boot.img, you can use a custom kernel instead.