Related
Ok, so clockwork recovery has worked without fail for 8 months...
then today i tried to reboot into recovery (using power menu, adb etc) and it just sits on the google screen.
I have reflashed a few different recovery images and locked/unlocked the loader.
I can get into recovery only after straight after flashing the recovery, by going to the bootloader and selecting reboot (not recovery)
something is balked here, any ideas?
(i would just lock the bootloader again and take it back as faulty, but when that is done, it boots straight into recovery, i assume because there is no ROM there)
Lock the bootloader then unlock it again then reflash Clockwork.
Have you tried using the modded one on the dev forums at 4.0.0.2?
yep, im afraid ive done that... any way to reinstall the bootloader itself?
slimjimwoods said:
yep, im afraid ive done that... any way to reinstall the bootloader itself?
Click to expand...
Click to collapse
Yeah you can find the images (there was a update to the bootloader in 2.3.2 or something) and go into bootloader mode and type.
fastboot flash bootloader whatever-the-bootloader-name-is.img
My bootloader is: I9020XXKA3
any chance you could point me in the right direction of the images, google is seeming fruitless...
slimjimwoods said:
any chance you could point me in the right direction of the images, google is seeming fruitless...
Click to expand...
Click to collapse
Yup, no problem. I was just looking for it. Is the KA3 bootloader the version you currently have? Because I know it was optional to update the bootloader, especially for non-stock ROM'ers.
http://www.mediafire.com/download.php?sn9fu022r88w2n7
MD5: BBA9E3926224CA5C9B4DF891F50F1A90
currently I have I9020XXJK1...
slimjimwoods said:
currently I have I9020XXJK1...
Click to expand...
Click to collapse
Yeah thats the older bootloader that came with the stock phone. The KA3 bootloader is the newest bootloader that was included with the 2.3.3 OTA. Just make sure you're using a I9020 model. Which you probably are since you're in the UK so you shouldn't have anything to worry about.
excellent thankyou, and im right in saying
fastboot flash boot *above file*...
slimjimwoods said:
excellent thankyou, and im right in saying
fastboot flash boot *above file*...
Click to expand...
Click to collapse
1. put bootloader.img into \android-sdk-windows\tools\
2. command prompt, cd C:\android-sdk-windows\tools\ (or where ever your SDK folder is)
3. put phone into bootloader mode if it isnt already
4. fastboot flash bootloader bootloader.img
5. reboot bootloader
6. check bootloader version
p.s. verify its MD5 hash before you fastboot it
aha! thankyou, it was flash bootloader... ok thats done, I shall try clockwork and get back to you
slimjimwoods said:
aha! thankyou, it was flash bootloader... ok thats done, I shall try clockwork and get back to you
Click to expand...
Click to collapse
good luck
clockwork is fine now, flashed CM7 nightly but it just sat on the black Google screen again... going to try something a bit more stable... thankyou for your help on this
its booted
[ROM-AOSP GRJ22][NS+NS4G] Oxygen-2.1.6,
slimjimwoods said:
its booted
[ROM-AOSP GRJ22][NS+NS4G] Oxygen-2.1.6,
Click to expand...
Click to collapse
congrats CM7 nightly should of flashed too. just have to wipe dalvik,cache,factory and it should be fine afterwards.
Oxygen is pretty nice though. I manipulated the ROM to be like Cyanogen by copying over Cyanbread. More lightweight and less bloat compared to CM7.
would that add in DSP manager?
slimjimwoods said:
would that add in DSP manager?
Click to expand...
Click to collapse
Nope. have to separately add it in, Voodoo Sound is better anyways.
That's true, but I tend to run them alongside each other, dsp doing the equalizer... (like to give the treble a boost)
slimjimwoods said:
That's true, but I tend to run them alongside each other, dsp doing the equalizer... (like to give the treble a boost)
Click to expand...
Click to collapse
Just add the app in, see what happens.
After my thread for the TF101, here are my first repackaged OTA updates for the TF700:
First of all let me make this clear:
If you have root and want to keep it, use OTA Rootkeeper.
The original recovery is removed from the blob, so you won't lose your current recovery.
If after flashing one of these zips you still have the OTA update notification, do this:
Go to Settings -> Apps -> All and clear data from DMClient.
Current OTA 9.4.5.26:
US version:
us-9.4.5.22-to-9.4.5.26-TF700-CWM-v1.0.zip MD5: 2C6C763D0A7618E4AB4CB530D714F833
WW version:
ww-9.4.5.22-to-9.4.5.26-TF700-CWM-v1.0.zip MD5: E9597AD7C18483445A1F006D91A44C1B
IMPORTANT! If you deleted/changed some files, these updates will NOT work. These updates are meant for people on a stock rooted rom.
Sweet I know a few people were looking for a flashable OTA update.
...for CWM that hasn't been ported yet
tweeklulz said:
...for CWM that hasn't been ported yet
Click to expand...
Click to collapse
AFAIK cwm zips are compatible with TWRP.
It's a generic name which is supported by most recoveries.
(TWRP or CWM) As far as we are able to unlock our TF700... That not my case...
But it's a good news for those who can
Lizard, a better title would be "[ROM][FLASHABLE]" or something. People tend to get very confused when you say "CWM" because they think no other recovery can flash it .
eyeballer said:
Lizard, a better title would be "[ROM][FLASHABLE]" or something. People tend to get very confused when you say "CWM" because they think no other recovery can flash it .
Click to expand...
Click to collapse
I've changed the title to flashable, since I don't consider the update zips to be roms. I hope this will take away some of the confusion.
Lizard said:
I've changed the title to flashable, since I don't consider the update zips to be roms. I hope this will take away some of the confusion.
Click to expand...
Click to collapse
Thanks! Will reduce our support requests for TWRP
Bad Link To zip File
Oops! This page appears broken. DNS Error - Server cannot be found.
This is the message I get when I click the link to download your OTA update, need that update, can you help. Please.
TECHNOLLIC said:
Oops! This page appears broken. DNS Error - Server cannot be found.
This is the message I get when I click the link to download your OTA update, need that update, can you help. Please.
Click to expand...
Click to collapse
Look at the date of the OP - 9.4.5.26 is very old. Why do you need this old update?
_that said:
Look at the date of the OP - 9.4.5.26 is very old. Why do you need this old update?
Click to expand...
Click to collapse
To install NvFlash. I have 9.4.5.30, NvFlash will not install with this Rom version, it has to be before that.
TECHNOLLIC said:
To install NvFlash. I have 9.4.5.30, NvFlash will not install with this Rom version, it has to be before that.
Click to expand...
Click to collapse
You cannot downgrade from 9.4.5.30 to 9.4.5.26; the 9.4.5.30 bootloader and above accepts only signed bootloaders and the older ones are not signed.
_that said:
You cannot downgrade from 9.4.5.30 to 9.4.5.26; the 9.4.5.30 bootloader and above accepts only signed bootloaders and the older ones are not signed.
Click to expand...
Click to collapse
So how will I be able to install the NvFlash Tool? I want to flash custom roms but I want to protect my tablet from getting bricked.
TECHNOLLIC said:
So how will I be able to install the NvFlash Tool? I want to flash custom roms but I want to protect my tablet from getting bricked.
Click to expand...
Click to collapse
You can no longer able to install nvflash once you already flashed above .26 version, like .30 and up. You're out of luck.
buhohitr said:
You can no longer able to install nvflash once you already flashed above .26 version, like .30 and up. You're out of luck.
Click to expand...
Click to collapse
That sucks, I didn't flash .30, it came with it already installed. I'm used to flashing my phones, so it should be no problem flashing my tablet. Thank you very much for your help.
If you've flashed roms on other phones or tablets in the past then you should be fine. Just don't do anything crazy and you shouldn't brick it. I don't have NV Flash capabilities on mine, though I had the chance to but updated my bootloader anyway. Doesn't bother me as I'm not a dev and won't be doing anything crazy on mine. I've done plenty of flashing on many phones and the Asus Prime in the past, so I'm not worried about it
Sent from my Evo LTE using XDA Premium
TECHNOLLIC said:
That sucks, I didn't flash .30, it came with it already installed. I'm used to flashing my phones, so it should be no problem flashing my tablet.
Click to expand...
Click to collapse
Just be careful to never choose "wipe data" in the bootloader menu without a working (compatible to bootloader) recovery, that is the #1 reason for hard bricks:
http://forum.xda-developers.com/showthread.php?t=1917304
_that said:
Just be careful to never choose "wipe data" in the bootloader menu without a working (compatible to bootloader) recovery, that is the #1 reason for hard bricks:
http://forum.xda-developers.com/showthread.php?t=1917304
Click to expand...
Click to collapse
Thanks again for your help and support.
I just received my TF700T for Christmas and it has JB. Can I flash this to go back and get root without unlocking?
rocketjr said:
I just received my TF700T for Christmas and it has JB. Can I flash this to go back and get root without unlocking?
Click to expand...
Click to collapse
Yes. see http://forum.xda-developers.com/showthread.php?t=1925230
Sent from my ASUS Transformer Infinity TF700 running Android JB (rooted) via Tapatalk HD
Move to dev if better suited there.
Thanks goes to saltxyz for this find.
For those of us on the TF300 JB bootloader you can revert back to ICS using my instructions in my other post here only be sure to grab the new .30 firmware: http://forum.xda-developers.com/showthread.php?t=1873635
Not only is ICS running smoothly again thanks to the bootloader but THE .30 BOOTLOADER ALLOWED THE JB KERNEL TO RUN!!
That's right I was able to flash my own TF300 ROM which has everything but the kernel removed from the blob and it ran JB while leaving the bootloader intact.
nice! good to hear asus has things figured out.
I'm guessing this is part of the prep for JB with the bootloader supporting both.
Mike02z said:
I'm guessing this is part of the prep for JB with the bootloader supporting both.
Click to expand...
Click to collapse
I can only assume so.
Can we just flash the .30 zip file in TWRP?
rooted/unlocked
amaury48 said:
Can we just flash the .30 zip file in TWRP?
rooted/unlocked
Click to expand...
Click to collapse
Yes, but you have to extract US_epad_user_9_4_5_30_20120907_UpdateLauncher.zip to US_epad-user-9.4.5.30.zip and flash it.
amaury48 said:
Can we just flash the .30 zip file in TWRP?
rooted/unlocked
Click to expand...
Click to collapse
I've flashed it several times today. You will have to re-install TWRP via fastboot, and then flash SuperUser, if you care about root.
LMMT said:
I've flashed it several times today. You will have to re-install TWRP via fastboot, and then flash SuperUser, if you care about root.
Click to expand...
Click to collapse
I know it's stated that you have already done this, but I really don't want to screw something up and I don't have NVFlash to recover from a hard brick.Can you, or others, confirm that you can indeed move from the .13 JB bootloader to the .30 ICS bootloader successfully and then be able to use the NVFlash?
Edit: Oops, I guess this is for the TF700 only, or will this work on the actual TF300 as well? Anyone know?
-Nate
herschwolf said:
I know it's stated that you have already done this, but I really don't want to screw something up and I don't have NVFlash to recover from a hard brick.Can you, or others, confirm that you can indeed move from the .13 JB bootloader to the .30 ICS bootloader successfully and then be able to use the NVFlash?
Edit: Oops, I guess this is for the TF700 only, or will this work on the actual TF300 as well? Anyone know?
-Nate
Click to expand...
Click to collapse
Actually a user in the nvflash thread said he tried it for the TF300 and it worked.
Sent from my EVO using xda premium
Tried to boot in to recovery to flash a root zip..
When i volume up to enter recovery, screen goes black. I hit power button and TWRP opens but its unusable and dual screen..top and bottom. Slide to unlock is on the screen but nothing works. Only way out is to hold down power and reset.
Help!
Motochopper not working. I run SuperUS app and get "There is no SU binary installed, and SuperSU cannot install it. This is a problem!"
I agree!
DatacomGuy said:
Motochopper not working. I run SuperUS app and get "There is no SU binary installed, and SuperSU cannot install it. This is a problem!"
I agree!
Click to expand...
Click to collapse
What bootloader are you on (its in settings app)
cmendonc2 said:
what bootloader are you on (its in settings app)
Click to expand...
Click to collapse
10.6.1.8-20130225
DatacomGuy said:
10.6.1.8-20130225
Click to expand...
Click to collapse
10.6.1.8 is compatible with very few recoveries. Upgrade it to 10.6.1.27 to flash recoveries for KitKat ROMs.
cmendonc2 said:
10.6.1.8 is compatible with very few recoveries. Upgrade it to 10.6.1.27 to flash recoveries for KitKat ROMs.
Click to expand...
Click to collapse
Asus has 10.6.1.27.5 posted. This one safe?
How do i manually update this?
DatacomGuy said:
Asus has 10.6.1.27.5 posted. This one safe?
How do i manually update this?
Click to expand...
Click to collapse
I know you can use that firmware to install KitKat ROMs as shown here (http://forum.xda-developers.com/showthread.php?p=49028315).
Use the 10.6.1.27.5 firmware with this:
Tylorw1 said:
1. Download the latest version of Android for your tablet. Make sure you download the correct SKU version.
A. To find the SKU, go into settings, About tablet, and look for your Build Number, There are two letters (such as US,WW, TW, etc.) that is your SKU. When downloading the zip from ASUS', you must download the correct SKU zip.
2. Decompress downloaded .zip file (it will be another .zip)
3. Rename it to:
A. For the TF700 and TF300: EP201_768_SDUPDATE.zip
4. Make sure your MicroSD card is formatted Fat32. It must be Fat32 Format or it will not work.
5. Copy the file to (the root directory of) your MicroSD
6. Insert the MicroSD into the tablet
7. Shutdown (power off) the tablet
8. Power it on by pressing and holding VOLUME DOWN and POWER buttons simultaneously
9. When you see white text in the top left corner of the screen, release the buttons ^^ and press VOLUME UP button (on RCK, this is your recovery which should already be selected) until you see Android logo and process bar
10. Give the update process 5-10 minutes. It should not take longer than that. If it happens to run for more than 45 minutes to an hour, force shut down the tablet and see if it boots. If it does not, try rerunning steps 7-9.
Click to expand...
Click to collapse
Only issue is that it's flashed in recovery, which isn't functioning for me.. Or usable.
Can I flash cwm again, flash this firmware, then try twrp again?
DatacomGuy said:
Only issue is that it's flashed in recovery, which isn't functioning for me.. Or usable.
Can I flash cwm again, flash this firmware, then try twrp again?
Click to expand...
Click to collapse
You can also use fastboot to flash the ROM from your computer
Sent from my TF300T using xda app-developers app
cmendonc2 said:
You can also use fastboot to flash the ROM from your computer
Sent from my TF300T using xda app-developers app
Click to expand...
Click to collapse
Alright..
fastboot -i 0x0B05 flash recovery firmwarefile.zip
Click to expand...
Click to collapse
Is that the right syntax?
DatacomGuy said:
Alright..
Is that the right syntax?
Click to expand...
Click to collapse
Remove the "recovery", that means you are flashing to the recovery partition. So
Code:
fastboot -i 0x0B05 flash firmwarefile.zip
for the stock Rom.
cmendonc2 said:
Remove the "recovery", that means you are flashing to the recovery partition. So
Code:
fastboot -i 0x0B05 flash firmwarefile.zip
for the stock Rom.
Click to expand...
Click to collapse
I'm trying to flash "US_epad-user-10.6.1.27.5.zip" by doing:
fastboot -i 0x0b05 flash US_epad-user-10.6.1.27.5.zip"
Click to expand...
Click to collapse
and i get:
Unknown partition 'US_epad-user-10.6.1.27.5.zip'
error: cannot determine image filename for 'US_epad-user-10.6.1.27.5.zip'
Click to expand...
Click to collapse
What might i be doing wrong? I tried with the zip and without.
I checked the contents of the zip, and i have folder named "META-INF" with a bunch of content, and also a blob file, about 820mb.
Grr.
DatacomGuy said:
I'm trying to flash "US_epad-user-10.6.1.27.5.zip" by doing:
and i get:
What might i be doing wrong? I tried with the zip and without.
I checked the contents of the zip, and i have folder named "META-INF" with a bunch of content, and also a blob file, about 820mb.
Grr.
Click to expand...
Click to collapse
Extract the blob from the stock zip file. It should be a large file. Put that blob in your fastboot folder.
Code:
fastboot -i 0x0B05 flash system blob
cmendonc2 said:
Extract the blob from the stock zip file. It should be a large file. Put that blob in your fastboot folder.
Code:
fastboot -i 0x0B05 flash system blob
Click to expand...
Click to collapse
There we go.. Thank you very much for all your help.
Got it all flashed, all running well.
I tried to boot in to recovery, and got a "system error". I'm assuming i need to reflash the correct TWRP, and then try motochopper again? Or is there a better way to root..
EDIT: Currently running stock 4.2.1...
EDIT2: Is this the right one?
openrecovery-twrp-2.6.3.0-tf300t-JB.blob
DatacomGuy said:
There we go.. Thank you very much for all your help.
Got it all flashed, all running well.
I tried to boot in to recovery, and got a "system error". I'm assuming i need to reflash the correct TWRP, and then try motochopper again? Or is there a better way to root..
EDIT: Currently running stock 4.2.1...
Click to expand...
Click to collapse
Flashing the stock wipes the recovery, so you will need to flash the correct version of TWRP this time . I dont think you need TWRP for motochopper. Since you are unlocked, you can just flash the SU binaries directly from TWRP.
cmendonc2 said:
Flashing the stock wipes the recovery, so you will need to flash the correct version of TWRP this time . I dont think you need TWRP for motochopper. Since you are unlocked, you can just flash the SU binaries directly from TWRP.
Click to expand...
Click to collapse
Makes sense.. openrecovery-twrp-2.6.3.0-tf300t-JB.blob the right version?
You lost me on your last part.. where do i find the SU binaries?
DatacomGuy said:
Makes sense.. openrecovery-twrp-2.6.3.0-tf300t-JB.blob the right version?
You lost me on your last part.. where do i find the SU binaries?
Click to expand...
Click to collapse
Wait! Flashing that will brick it again!!! Dont flash that, use the -42 TWRP since you are on Android 4.2 now.
cmendonc2 said:
Wait! Flashing that will brick it again!!! Dont flash that, use the -42 TWRP since you are on Android 4.2 now.
Click to expand...
Click to collapse
LOL!
openrecovery-twrp-2.6.3.0-tf300t-4.2.blob
Got it.
What about root? After i flash, where do i find the SU binaries?
DatacomGuy said:
LOL!
openrecovery-twrp-2.6.3.0-tf300t-4.2.blob
Got it.
What about root? After i flash, where do i find the SU binaries?
Click to expand...
Click to collapse
TWRP should have the SU binaries built into it. If TWRP doesn't detect root when it is run from the bootloader, it asks you if you want to flash them. Are you trying to flash a KitKat ROM or a Jelly Bean ROM. KitKat needs TWRP -2.6.3.1
cmendonc2 said:
TWRP should have the SU binaries built into it. If TWRP doesn't detect root when it is run from the bootloader, it asks you if you want to flash them. Are you trying to flash a KitKat ROM or a Jelly Bean ROM. KitKat needs TWRP -2.6.3.1
Click to expand...
Click to collapse
i dont want to flash any rom right now, i just want to stick with stock 4.2.1...
Last time i flashed TWRP.. albeit incorrectly.. it didnt ask anything when i rebooted into recovery. I'm assuming thats when it asks....
So I'm on a VP and am BL unlocked, twrp'd and rooted on 7.1 and want to update to 7.1.1. I want to flash the stock boot.img so I can take the OTA and update. Problem is I keep trying to extra the boot.img but can't get it to flash.
Not sure if I'm doing it wrong or have the wrong img but it's driving me nuts.
I've read through the forums and I know I'll get flamed for asking but I just need a bit of help with this.
Thx
mpetruzz said:
So I'm on a VP and am BL unlocked, twrp'd and rooted on 7.1 and want to update to 7.1.1. I want to flash the stock boot.img so I can take the OTA and update. Problem is I keep trying to extra the boot.img but can't get it to flash.
Not sure if I'm doing it wrong or have the wrong img but it's driving me nuts.
I've read through the forums and I know I'll get flamed for asking but I just need a bit of help with this.
Thx
Click to expand...
Click to collapse
fastboot flash boot_a /path/to/boot.img
fastboot flash boot_b /path/to/boot.img
Or, just flash the whole image with flash-all command. 7.1.1 (NMF26O, Dec 2016) is the one you want and its found here https://developers.google.com/android/images. You can edit the script and remove the -w and it'll keep the user data in tact. For me, it was better to start from scratch.
Droid1019 said:
fastboot flash boot_a /path/to/boot.img
fastboot flash boot_b /path/to/boot.img
Click to expand...
Click to collapse
Ok thanks! I had a few people give me the wrong command line that's prolly why it wasn't working. I'll give this a shot later!!
Droid1019 said:
fastboot flash boot_a /path/to/boot.img
fastboot flash boot_b /path/to/boot.img
Or, just flash the whole image with flash-all command. 7.1.1 (NMF26O, Dec 2016) is the one you want and its found here https://developers.google.com/android/images. You can edit the script and remove the -w and it'll keep the user data in tact. For me, it was better to start from scratch.
Click to expand...
Click to collapse
OK, so now I'm using those commands and still am getting the error message cannot load path/to/boot.img.
I can give the flash all a try, how to I edit the script to remove the -w??
mpetruzz said:
OK, so now I'm using those commands and still am getting the error message cannot load path/to/boot.img.
I can give the flash all a try, how to I edit the script to remove the -w??
Click to expand...
Click to collapse
If you get that error message it sounds like you don't have the right path for it to find that file. With the phone in bootloader mode I type in the command then drag the bit image into the terminal window and execute. I use a Mac so I don't know if you can drag the file in on a Windows machine. You'll have the same issue with the flash all if you don't have the right path.
mpetruzz said:
So I'm on a VP and am BL unlocked, twrp'd and rooted on 7.1 and want to update to 7.1.1. I want to flash the stock boot.img so I can take the OTA and update. Problem is I keep trying to extra the boot.img but can't get it to flash.
Not sure if I'm doing it wrong or have the wrong img but it's driving me nuts.
I've read through the forums and I know I'll get flamed for asking but I just need a bit of help with this.
Thx
Click to expand...
Click to collapse
Can't you just flash stock recovery and sideload the OTA? Seems a lot easier and safer.
bobby janow said:
Can't you just flash stock recovery and sideload the OTA? Seems a lot easier and safer.[/QUOTE
Yeah that does sound better!!. Honestly I might just leave it on 7.1 til some Roms come out.
Click to expand...
Click to collapse
mpetruzz said:
bobby janow said:
Can't you just flash stock recovery and sideload the OTA? Seems a lot easier and safer.[/QUOTE
Yeah that does sound better!!. Honestly I might just leave it on 7.1 til some Roms come out.
Click to expand...
Click to collapse
7.1.1 is worth it. Not sure when roms are coming out but with the OTA it's about a 10 minute install and reboot. You'll need to just fastboot flash recovery recovery.img for the stock, go directly into recovery with the vol keys / power key and then adb sideload the ota file after entering the recovery menu.
Did you flash another kernel? Is that why you want to replace the boot.img? If so you can probably just flash the OTA without changing anything other than recovery since it will overwrite the boot.img anyway.
Click to expand...
Click to collapse
bobby janow said:
mpetruzz said:
7.1.1 is worth it. Not sure when roms are coming out but with the OTA it's about a 10 minute install and reboot. You'll need to just fastboot flash recovery recovery.img for the stock, go directly into recovery with the vol keys / power key and then adb sideload the ota file after entering the recovery menu.
Did you flash another kernel? Is that why you want to replace the boot.img? If so you can probably just flash the OTA without changing anything other than recovery since it will overwrite the boot.img anyway.
Click to expand...
Click to collapse
Right now I'm only BL unlocked, twrp'd and rooted. No kernel modifications.
Where do I get the recovery.img from?
I was told by others here I need to flash the stock boot image in order to take the OTA. Jeez I'm getting so confused cause I keep getting different info
Click to expand...
Click to collapse
mpetruzz said:
bobby janow said:
Right now I'm only BL unlocked, twrp'd and rooted. No kernel modifications.
Where do I get the recovery.img from?
I was told by others here I need to flash the stock boot image in order to take the OTA. Jeez I'm getting so confused cause I keep getting different info
Click to expand...
Click to collapse
Stock recovery is in the image file from Google. Download it and extract it and flash it in bl. You might need things to "take" the OTA but I don't believe you need anything to flash the OTA (adb sideload) That will overwrite any kernel (boot.img) changes you made. But you said you made no kernel changes so why would you need to flash a boot.img?
Click to expand...
Click to collapse
bobby janow said:
mpetruzz said:
Stock recovery is in the image file from Google. Download it and extract it and flash it in bl. You might need things to "take" the OTA but I don't believe you need anything to flash the OTA (adb sideload) That will overwrite any kernel (boot.img) changes you made. But you said you made no kernel changes so why would you need to flash a boot.img?
Click to expand...
Click to collapse
OK so i'm in the system image file for 7.1 and am not seeing the recovery.img. Must be doing something wrong, but it's def not there. Anywhere else I can grab it from?
Also once I get it what would the adb command line be to flash it?
Click to expand...
Click to collapse
bobby janow said:
mpetruzz said:
Stock recovery is in the image file from Google. Download it and extract it and flash it in bl. You might need things to "take" the OTA but I don't believe you need anything to flash the OTA (adb sideload) That will overwrite any kernel (boot.img) changes you made. But you said you made no kernel changes so why would you need to flash a boot.img?
Click to expand...
Click to collapse
I got it and am all set!! Used the skipsoft tool to flash the stock recovery, then sideloaded the OTA!!
Thanks brother for all the help!!!!
Click to expand...
Click to collapse
Hey I'm pretty new to this but is there a way I can update without a computer, I dont mind losing root as long as I'm still unlocked... I'm using a Verizon phone on at&t if that matters... If not I can always to it tomorrow when I can get to a computer..
bobby janow said:
mpetruzz said:
7.1.1 is worth it. Not sure when roms are coming out but with the OTA it's about a 10 minute install and reboot. You'll need to just fastboot flash recovery recovery.img for the stock, go directly into recovery with the vol keys / power key and then adb sideload the ota file after entering the recovery menu.
Did you flash another kernel? Is that why you want to replace the boot.img? If so you can probably just flash the OTA without changing anything other than recovery since it will overwrite the boot.img anyway.
Click to expand...
Click to collapse
OK maybe i spoke too soon. I sideloaded the OTA and was able to install TWRP, but now when I flash the su zip I don't have the SuperSu app and can't get root. I've tried it twice and it looks like it's flashed but then when I reboot it's not there.
What am I not doing to get this too work??
Click to expand...
Click to collapse
mpetruzz said:
bobby janow said:
OK maybe i spoke too soon. I sideloaded the OTA and was able to install TWRP, but now when I flash the su zip I don't have the SuperSu app and can't get root. I've tried it twice and it looks like it's flashed but then when I reboot it's not there.
What am I not doing to get this too work??
Click to expand...
Click to collapse
http://forum.xda-developers.com/pixel-xl/development/root-supersu-t3490156
This is where you'll need to go at this point. Lots to read but you have to do it in order to get it working correctly. Good luck, you'll get it.
Click to expand...
Click to collapse
bobby janow said:
mpetruzz said:
http://forum.xda-developers.com/pixel-xl/development/root-supersu-t3490156
This is where you'll need to go at this point. Lots to read but you have to do it in order to get it working correctly. Good luck, you'll get it.
Click to expand...
Click to collapse
Got it, man this pixel is crazy different than what I'm used too. Thanks all for the help!
Click to expand...
Click to collapse