Related
My transformer was rooted using the old method and I've installed Prime.
I have problems with the camera so want to flash blob v5
Can i just flash the blob file with cwm?
The instructions are quite involved but it looks like i dont need to do most of what it says.
I believe you can skip some steps 1-4 i believe since you are already rooted. Dont quote me though.
reading the FAQ would have answered this, just follow the blob flashing steps.
I don't see in the FAQ where it says if you can flash the blob using CWM.
I already knew about the ADB push method. My question was specifically about using CWM. It just uppacks and copies files (as root), like ADB doesn't it?
as it isn't stated there, and there isn't a zip file no.
seshmaru said:
as it isn't stated there, and there isn't a zip file no.
Click to expand...
Click to collapse
Ah, the blob is not a zip file, gotcha! Thanks for the helpful response, I've learned something today
OK, I'll do it the ADB way, thanks!
RedMist said:
Ah, the blob is not a zip file, gotcha! Thanks for the helpful response, I've learned something today
OK, I'll do it the ADB way, thanks!
Click to expand...
Click to collapse
Added to the FAQ now.
RedMist said:
Ah, the blob is not a zip file, gotcha! Thanks for the helpful response, I've learned something today
OK, I'll do it the ADB way, thanks!
Click to expand...
Click to collapse
if you really don't want to take the ADB route, MoDaCo's Hr4 custom ROM does include the blob and is flashable via CWM.
Regards,
Dave
foxmeister said:
if you really don't want to take the ADB route, MoDaCo's Hr4 custom ROM does include the blob and is flashable via CWM.
Regards,
Dave
Click to expand...
Click to collapse
Thank you. I didnt realise Hr4 did that
foxmeister said:
if you really don't want to take the ADB route, MoDaCo's Hr4 custom ROM does include the blob and is flashable via CWM.
Regards,
Dave
Click to expand...
Click to collapse
^^ This
Now can we please close + move this thread, as it isn't really dev related.
Hello, I am confused. I have heard some people have issues after installing nvflash and then installing a custom recovery. I notice that they are both flashed to the address "0x0b05". Will this cause a problem? For instance, recovery overwrites NVflash or vice versa.
Thanks. Any guidance appreciated
ostar2 said:
Hello, I am confused. I have heard some people have issues after installing nvflash and then installing a custom recovery. I notice that they are both flashed to the address "0x0b05". Will this cause a problem? For instance, recovery overwrites NVflash or vice versa.
Click to expand...
Click to collapse
You do not "install" nvflash. nvflash is a tool that runs on a PC. For using it with the TF700, you first need to flash a hacked bootloader and run a tool to extract a blob file from your tablet. Then you save this blob on your PC and keep it safe. This blob is used with the "wheelie" tool, which prepares the communication with the tablet, so that you finally can use nvflash.
And 0x0b05 is not an address, it is the vendor part of the Transformer's USB ID.
You should read the nvflash-related threads thoroughly, this should clean up some of your confusion. Do not try the procedure before you know what you are doing!
thankyou for clarifying that for me. In this case I have one other question, what are the chances that flashing the bootloader would fail and brick the device?
ostar2 said:
what are the chances that flashing the bootloader would fail and brick the device?
Click to expand...
Click to collapse
It worked fine for me, but for a well-founded answer, we would need some statistical data.
I'd say the chances are greater than 0, but not much, if you know what you are doing. At least I do not know any reports of bricking by flashing the bootloader - all recent bricks I read about in this forum were a result of using some inappropriate way to flash a custom recovery and then trying to wipe data.
_that said:
It worked fine for me, but for a well-founded answer, we would need some statistical data.
I'd say the chances are greater than 0, but not much, if you know what you are doing. At least I do not know any reports of bricking by flashing the bootloader - all recent bricks I read about in this forum were a result of using some inappropriate way to flash a custom recovery and then trying to wipe data.
Click to expand...
Click to collapse
Well, if thats the case poll or survey should be done. Also, I have been back and forth about nvflash and what happens if I flash the Asus jb update after installing the custom bootloader? Will it overwrite the custom bootloader? Thanks.
ostar2 said:
Well, if thats the case poll or survey should be done. Also, I have been back and forth about nvflash and what happens if I flash the Asus jb update after installing the custom bootloader? Will it overwrite the custom bootloader? Thanks.
Click to expand...
Click to collapse
Yes, it will overwrite the custom bootloader. But at that time you should already have pulled your blob and stored it safely on your PC and backed it up multiple times, so you don't need the custom bootloader anymore - it is only required for extracting the blob, not for running nvflash.
Ok, thanks. I just needed to be sure of what would happen. I will install the custom bootloader and recovery, generate blobs and preform nvflash backup. I am still unsure if I want to use the stock ROM with a custom recovery or if I want to use cm10 with a custom recovery.
I am definitly going to use cm10 or cm10.1, custom bootloader with twrp recovery after here that Asus spies on what you do with your tablet.
ostar2 said:
I am definitly going to use cm10 or cm10.1, custom bootloader with twrp recovery after here that Asus spies on what you do with your tablet.
Click to expand...
Click to collapse
Just FYI: CleanROM does not include CMClient and DMClient.
Thanks, I still think I am going to go with cyanogenmod 10.1 when it comes out.
At this point I don't want create $499.99 paper weight.
I have read that nvflash can cause a bootloop. Is this true?
ostar2 said:
I have read that nvflash can cause a bootloop. Is this true?
Click to expand...
Click to collapse
Where did you read that?
Improper use of nvflash can cause all kinds of malfunction, however proper use of nvflash should always be able to repair that (if you have backups).
I read this
d14b0ll0s said:
-----------------------------------------------------------------------------------+
Apps to avoid (causing bootloops etc.)
Beats Audio - see why
Wallpaper Wizardrii - see why
Transformer reboot to recovery - see why
NVFlash = softbrick
CMClient (stock) - see why you should probably
disable it (unless you desire constant surveillance)
LCD Density - see why
Click to expand...
Click to collapse
Here: http://forum.xda-developers.com/showthread.php?t=1764480
_that said:
Where did you read that?
Improper use of nvflash can cause all kinds of malfunction, however proper use of nvflash should always be able to repair that (if you have backups).
Click to expand...
Click to collapse
Also, are there any detailed guides on how install nvflash?
ostar2 said:
Also, are there any detailed guides on how install nvflash?
Click to expand...
Click to collapse
This is the guide: http://androidroot.mobi/t3_nvflash/
Make sure you understand exactly what you are doing before you begin. It's easier to do on a Linux PC because of fewer driver issues.
_that said:
This is the guide: http://androidroot.mobi/t3_nvflash/
Make sure you understand exactly what you are doing before you begin. It's easier to do on a Linux PC because of fewer driver issues.
Click to expand...
Click to collapse
Mainly what I am confused about is this: Do I need any extra blob files to install nvflash other than the ones listed?
I understand that you need to backup the "generated" blob files. If so, where would I get them?
Read the guide again. You do not "install" nvflash, the guide describes the procedure of using a hacked bootloader to extract data (the blob) needed to run nvflash.
_that said:
Read the guide again. You do not "install" nvflash, the guide describes the procedure of using a hacked bootloader to extract data (the blob) needed to run nvflash.
Click to expand...
Click to collapse
I know. When I said install nvflash I was referring to the "AndroidRoot" bootloader.
ostar2 said:
I know. When I said install nvflash I was referring to the "AndroidRoot" bootloader.
Click to expand...
Click to collapse
To install that, you need only the files available on the AndroidRoot site and a working fastboot setup.
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....
I have an Asus TF300T that I have unlocked, and flashed TWRP 10.6.3.1 onto it. I have then flashed the latest 4.4 Cyanogen nightly, and it bootloops. I think this is because of my bootloader.
Normally once I am at the custom recovery point on a device, I have no further issues and flash rom's like crazy. This specific bootloader requirement is new to me. I've farted around on a few devices before (Moto Milestone, HTC Desire Z, HP Touchpad, Sam GS3), but I'm not very technical.
I think my current bootloader is 10.4.2.18. (It reads Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.4.2.18-20121122" A03).
How do I upgrade my bootloader to allow for 4.4 rom's, and must I downgrade my bootloader if I want to install something like Ubuntu?
The instructions mentioned here http://forum.xda-developers.com/showpost.php?p=48508679&postcount=7 took me to http://forum.xda-developers.com/showthread.php?p=49258989 but neither of these post's seem to be talking about the bootloader. Is there a way to simply upgrade just the bootloader? Or must I flash a special stock Asus rom that upgrades it for me, then reflash TWRP and proceed from there?
I think I may understand. I've downloaded the latest firmware update from the Asus website. Is this zip flashable within TWRP? Or can I simply fastboot the blob within the firmware zip? If so, what would the command be?
jiddahidda said:
I think I may understand. I've downloaded the latest firmware update from the Asus website. Is this zip flashable within TWRP? Or can I simply fastboot the blob within the firmware zip? If so, what would the command be?
Click to expand...
Click to collapse
Use fastboot to install the latest stock blob. Remember to extract the blob file:
Code:
fastboot -i 0x0B05 flash system blob.blob
Then you can flash TWRP 2.6.3.2 and then a KitKat ROM.
I seem to have lost the ability to get it into fastboot mode to apply your instructions. Is it bricked if it bootloops, and I cannot get into that bootloader screen by holding down the volume down button? Your instructions are straight forward but I haven't had a chance to try them yet because of this new issue. So does this sound like it's bricked?
cmendonc2 said:
Code:
fastboot -i 0x0B05 flash system blob.blob
Click to expand...
Click to collapse
Is there another way to get it into fastboot mode? See my post above this one.
I can get into APX mode. Can I fix this using APX mode? I'm googling around but I'll wait for word from you before doing anything, I don't want to make this worse.
jiddahidda said:
I can get into APX mode. Can I fix this using APX mode? I'm googling around but I'll wait for word from you before doing anything, I don't want to make this worse.
Click to expand...
Click to collapse
You cannot use APX mode unless you have already made NvFlash Backups. IF you made then, you can recover using that method.
I seem to have lost the ability to get it into fastboot mode to apply your instructions. Is it bricked if it bootloops, and I cannot get into that bootloader screen by holding down the volume down button? Your instructions are straight forward but I haven't had a chance to try them yet because of this new issue. So does this sound like it's bricked?
Click to expand...
Click to collapse
Yes, that does sound bricked. What you can do is look up Buster's recovery script and try using that to recover. It should be in the General Section.
cmendonc2 said:
You cannot use APX mode unless you have already made NvFlash Backups. IF you made then, you can recover using that method.
Click to expand...
Click to collapse
I think I know the answer, but I'll ask anyway. Is it possible to use someone elses NvFlash backups? I looked into making these backups but never did it .
cmendonc2 said:
Yes, that does sound bricked. What you can do is look up Buster's recovery script and try using that to recover. It should be in the General Section.
Click to expand...
Click to collapse
I've seen you suggest this script several times in several threads, but could never find it. I've been searching for threads with the word Buster or Recovery or Script and I can't find anything that seem's to be what you're talking about? Sorry to be a pain, what's his XDA username?
I think I've found it, but it relies on getting into fastboot, which I can't do. I stumbled on this post earlier while panicing when it first bricked. I think I'm screwed .
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
jiddahidda said:
I think I've found it, but it relies on getting into fastboot, which I can't do. I stumbled on this post earlier while panicing when it first bricked. I think I'm screwed .
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Click to expand...
Click to collapse
Yes, but did you try using the paper clip to reset it? try a few combinations of using it.
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