Got the .30 WW build notif this morning, i tried to install it but it rebooted tablet, then i saw a picture of android with its belly open with a red triangle, then rebooted and it told me the update failes. Now i cant find the files to update manually because they are not on the website
I have downloaded the update, but not installed it yet. I have made a copy of /cache/dlpkgfile but was wondering if I need other files in order to be able to supply the forum with a manual update package.
Anyone knows which files should be backed up before installinf the update in order for other users to be able to get the files and do a manual update?
I was bored about waiting for the WW Update so I installed the US .30 (no root or unlocking required, I'm not unlocked)
download it from here:
http://db.tt/arTCXvI9 (posted in OTA Thread, I got it from here)
or here:
https://dl.dropbox.com/u/16925401/US_epad_user_9_4_5_30_20120907_UpdateLauncher.zip
extract and rename the included ZIP to EP201_768_SDUPDATE.zip
put it to a MicroSD Card and reboot to recovery
Wait 10 min and let all progress finish and congratulations you are now on .30 US
Works pretty nice here ASUS Recovery just checks for the signature of the ZIP but the updater-script don't check the SKU or even the Model ^^ (the reason why we can install the TF300 JB ROM)
Here is the link to my dlpkgfile (9.4.5.30 WW ota), copied before flashing : https://www.dropbox.com/s/0y9vtu1zrymh5df/dlpkgfile
size : 11.73 MB
md5sum : 4b108d1eddacef8e0f8d5ceaeaf1aa25
Was somebody able to copy the /cache/recovery/command file as well?
Edit: It seems command file is a text file which should just read:
--update_package=/cache/dlpkgfile
---------- Post added at 05:55 PM ---------- Previous post was at 05:09 PM ----------
It seems I've deleted too much from /system/app/ to make sense of it (note: always make backups). Could someone post a link to his/her dump from /system/app/ from WW 26?
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
d14b0ll0s said:
It seems I've deleted too much from /system/app/ to make sense of it (note: always make backups). Could someone post a link to his/her dump from /system/app/ from WW 26?
Click to expand...
Click to collapse
i've uploaded the files (whole /system/app directory of WW .26) here: http://www.sendspace.com/file/4d541b hope you are able to download there, never used this hosting provider
Thanks A LOT! Much appreciated. Downloading it now.
BTW, there's an xda-friendly file-hosting site http://d-h.st/
It worked, seems that recovery is checking for both /system/app/ consistency and stock build.prop (it turned out I had a backup after all, but it helped anyway, thanks!)
(still 2.6.x kernel, JB needed..)
Could someone please post an exact, complete, step by step of exactly how to upgrade WW to .30 using the file from post #4 above.
I am about to download my OTA update and if it fails I want to know how to resume, and then run the upgrade via the file.
Thanks for any help
Cheers Q
Copy dlpkgfile to /cache and command to /cache/recovery/
Reboot
Hold vol down & power buttons
When you see white text in top left corner, release both buttons and press vol up
You'll see the droid and progress bar in the recovery mode
If it fails, reboot, see the log in /cache/recovery/, adjust and follow all the steps again
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
MechanteMiette said:
Here is the link to my dlpkgfile (9.4.5.30 WW ota), copied before flashing : https://www.dropbox.com/s/0y9vtu1zrymh5df/dlpkgfile
size : 11.73 MB
md5sum : 4b108d1eddacef8e0f8d5ceaeaf1aa25
Click to expand...
Click to collapse
thanks ill try that and report success or failure
d14b0ll0s said:
Copy dlpkgfile to /cache and command to /cache/recovery/
Reboot
Hold vol down & power buttons
When you see white text in top left corner, release both buttons and press vol up
You'll see the droid and progress bar in the recovery mode
If it fails, reboot, see the log in /cache/recovery/, adjust and follow all the steps again
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
Thanks for the guide it is very much appreciated and gave me the confidence to go ahead with my update. Fortunately mine worked perfectly but I am sure someone else will find it very helpful and I will book mark it for future reference if required.
Thanks again
Cheers Q
How come people are having issues? I just installed the .30 just fine. Then again, I'm running completely stock, not even rooted.
Sent from my ASUS Transformer Pad TF700T
Now I got the OTA .30 update the first morning it was available and have had no issues with the upgrade process nor afterwards with any part of my OS. You gotta wonder though whats going on when some people are getting their units bricked or totally messed up and others (like myself) that flew through the upgrade with out a hiccup. Very strange people very strange.
Sure makes me consider not letting a OTA upgrade just do its thing with out waiting a bit to see whats happening with other users
Vo01985 said:
How come people are having issues? I just installed the .30 just fine. Then again, I'm running completely stock, not even rooted.
Sent from my ASUS Transformer Pad TF700T
Click to expand...
Click to collapse
I think because they have changed some of the files like DMClient or CMClient.apk - odex or build.prop and if they dont replace them with the stock ones it fails.
It worked perfectly on my rooted TF700 with WW SKU I just used Voodoo to restore root after the update.
Cheers Q
Quozl said:
I think because they have changed some of the files like DMClient or CMClient.apk - odex or build.prop and if they dont replace them with the stock ones it fails.
It worked perfectly on my rooted TF700 with WW SKU I just used Voodoo to restore root after the update.
Cheers Q
Click to expand...
Click to collapse
In my case I did have changes to the build.prop but replaced it with stock before doing running the update. Still didn't help and it soft-bricked. I ended up having to do full factory wipe + flash .26 using the stock recovery (I was just rooted, but still locked).
Well now that I'm on complete stock fresh install I'm not getting the OTA no matter how many times I try to reboot/check for update. Maybe I got from Asus a 'Go back to start, do not pass Go, do not collect OTA' card
fail
So I copied dlpkgfile to /cache. After that I go to /cache/recovery and open last_log in that log I modified the command to /cache/recovery/. I reboot to recovery, hold volume up and then the update fails all the time. Maybe i misunderstood something
I think because they have changed some of the files like DMClient or CMClient.apk - odex or build.prop and if they dont replace them with the stock ones it fails.
Click to expand...
Click to collapse
i didnt change anything, im not even rooted and the OTA failed for me. I got this logo and then the tablet rebboted and told me update failed and the tablet was restored to previous state
{
"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"
}
polish_pat said:
i didnt change anything, im not even rooted and the OTA failed for me. I got this logo and then the tablet rebboted and told me update failed and the tablet was restored to previous state
Click to expand...
Click to collapse
I think the best thing to do is to wait, until asus put the update on ther site. And than download it and install it manually from sdcard.
i'll try the method suggested in post 4 and i'll report back later tonight when i get home
Related
Hi
Here are the nvflash versions for the .17 update. For those that wanna go back to stock for warrenty or have a dualboot this can come in handy.
I've tested the WW version on my on transformer and it worked (got a B70 with SBK1) created the US and TW version the sameway with the same config files so it should work! LET ME KNOW IF IT WORKS FOR YOU
But remember i'm not responsible for any bricks flashing my causes and you do this on your own riks.
Quick guide:
1. Connect cable to computer and turn device on while holding down Volume Up. Screen will stay off, but USB will come on.
2. Find “APX” device in Device manager and update driver, then point it at usbpcdriver directory from the zip.
3. Run download.bat.
I'm hosting them on my own server:
http://www.xdafileserver.nl/
*Added US version, and TW version
Thanks
.
Worked great on a B60 and a B70.
Thank you.
Sent from my Transformer TF101 using Tapatalk
not for TF101G - B90 ?
Nopes these are only for versions with SBK1 and the B90 series doesnt have that sorry m8, but there are otherways to get back to stock for B90 just look in the dev section.
Korumera said:
Nopes these are only for versions with SBK1 and the B90 series doesnt have that sorry m8, but there are otherways to get back to stock for B90 just look in the dev section.
Click to expand...
Click to collapse
oow.. thanks for the reply..
mine still in stock, but HC 3.2.1.. i thought ICS for TF101G already available for certain countries..
thanks a lot anyway..
@Korumera
I want to create JP version.
Can you tell me how to create ?
Thanks would this remove any version of clockwork recovery such as the disasterours 5.x that makes you do a cold boot on each restart?
Regards
rdosti said:
Thanks would this remove any version of clockwork recovery such as the disasterours 5.x that makes you do a cold boot on each restart?
Regards
Click to expand...
Click to collapse
Yes
NVFLASH'ing removes every partition and restores the orignal one.
Windows won't allow me to install the driver. It says the third-party INF does not contain digital signature information, and it doesn't give me an ignore and proceed anyway option. Any ideas? I'm doing this from device manager.
Edit: if anyone else has this happen, rebooting to boot options (the screen that lets you boot into safe mode and such) there is a setting to disable signed drivers. That worked for me.
This is so useful. Thanks.
Really good job! Thanks man!
nicely done! I was thinking about creating one for this version but I got tied up with work.
No problem
Hope it comes in handy!
and chadster214 work comes first at least they say so haha
Hi!
ROM: NVFLASH_ICS_9.2.1.21_WW_NOROOT
CWM Recovery ICS - Stock?
Edit: When i press power+volume down for 7 seconds (aprox) show this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks
Hmmm try to flash it again, i've checked the zip file and it contains all the files including the recovery (blob.sos)
Thanks a lot. Fixed a issue for me. No matter what I flashed I couldn't get the wifi to work again. Just stayed in a state of trying to turn on.
Tried and tested the WW version; no problem at all.
Korumera said:
Hmmm try to flash it again, i've checked the zip file and it contains all the files including the recovery (blob.sos)
Click to expand...
Click to collapse
I install the new NVFLASH_ICS_9.2.1.24_WW_NOROOT
My recovery it's the same, how is the recovery stock? you have screens?
I read that is normal in stock (android with admiration sign)
Thanks in advance, sorry for my english
This process works fine. A few things to keep in mind:
1) Unzip the .7z file in a folder in a folder at the root of your hard drive: I typically open my Windows boot drive, create a new folder, name it "nvflash" and dump the archive's contents into it. This avoids getting errors as a result of the Windows folder/file path being too long.
2) Timing is important when connecting the tablet to the computer: on Windows 7, I simply press the power on+volume up buttons for 2-3 seconds (up until the "new hardware found" bubble appears in the tray area), I then let go and make sure the screen remains off (*VERY IMPORTANT*).
3) To install the Windows driver for my TF101, I go to Device Manager, right-click on the APX icon (it should show a yellow exclamation point), update the driver by pointing Windows to the /usbpcdriver folder (e.g. c:\nvflash\usbpcdriver, for example), let Windows finish the install and ONLY then start the flashing process by running download.bat in Administrator mode.
{
"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"
}
Hi there, this is a beta version of a tool that I made.
It's designed to be used by people that are unfamiliar with Wheelie or Nvflash.
This is a tool designed to automate the process of unbricking your device, flashing a new firmware, or flashing recovery.
This tool uses Wheelie and Nvflash.
Credits to Androidroot.mobi for Wheelie and Nvidia for Nvflash!
Thank you AndroidRoot crew for reviving my tablet.
WARNING: ONLY USE THIS ON TF101 DEVICES - IF USED ON OTHER DEVICES YOU WILL BRICK IT
Works for:
ANY TF101:
SBK1 (B10-B70)
SBK2 (B70,B80,B90++)
Some B70 models are SBK1, some newer B70 are SBK2, if you don't know which one you have, try both!
Does NOT work for:
TF101G (TF101 3G)
SL101 (TF101 Slider)
Requirements:
APX Drivers ( I recommend using these )
Flashing recovery:
Start EasyFlasher.
Follow the simple instructions (click the buttons)
???
Profit! If you want Root, download latest Superuser, put on sdcard/internal storage and flash from CWM.
Instructions for unbricking/flashing ASUS stock firmware.
Download the latest ASUS WORLDWIDE Firmware [yarr.fjolstad.no - direct https]
Mirror [MEGA]
Put the .zip inside the "asusupdate" folder (inside EasyFlasher folder)
Do _NOT_ UNZIP it. Else this won't work.
Click the "Flash Asus stock zip" button in EasyFlasher and it'll do the rest of the job.
Screenshot:
Download:
Latest version always available on my site: https://yarr.fjolstad.no/pub/EasyFlasher-0.8.3b-STABLE.zip
NOTES:
Even though I test every release before I release it, please note that some things could be broken.
I am not responsible if your device is bricked, (although that should be impossible unless you can't get into APX mode for some reason)
Changelog:
Code:
[B]Version 0.8.3*[/B]
Fixed progressbar
Rewrote some code to fix XP issues
Fixed some minor issues
[B]Version 0.8.2*[/B]
Removed some unused code
Added official TWRP 2.2.1 & Roach CWM recovery
New GUI again
Removed Ubuntu button (separate app. coming)
[B]Version 0.7.1[/B]
Added TWRP 2.2 recovery
Removed backup/restore - Use recovery instead guys, it's much faster and nvflash is.. buggy when reading large partitions. Might still add a flash function.
Added most of the code for ubuntu dualboot, however the function is not yet implemented, I need to test it some more, PM me if you want to betatest.
Rewrote some code
[B]Version 0.6[/B]
Code for backup/restore added, needs further testing.
Cleaned up the GUI, again. still ugly.
[B]Version 0.5[/B]
Did some work on the GUI, still ugly
Added OneFlash - unbrick/restore to stock in 1 click.
Wrote code for superuser autoflash, needs more testing.
Want to be a beta tester for future features? PM me :)
[B]Version 0.4[/B]
Released first public beta, everything should work.
Recovery Flashing Added.
[B]Version 0.3[/B]
Added SBK Selection
[B]Version 0.2[/B]
Rewrote how I use wheelie/nvflash
new GUI
[B]Version 0.1[/B]
Test GUI
Wheelie added.
nice!......wont try it but i can appreciate how much easier it will make things
Good alternative to my tool Nice work. Works well
Yeeha!
After days of frustration and a marathon 6-hour run today, I finally got a working recovery. You are so my hero!
---------- Post added at 05:31 PM ---------- Previous post was at 05:28 PM ----------
Never donated to anyone before but thought I'd throw you a beer or so. No donate button though.
Emandab1 said:
After days of frustration and a marathon 6-hour run today, I finally got a working recovery. You are so my hero!
---------- Post added at 05:31 PM ---------- Previous post was at 05:28 PM ----------
Never donated to anyone before but thought I'd throw you a beer or so. No donate button though.
Click to expand...
Click to collapse
Thanks But I'd appreciate it if you donated to AndroidRoot instead, they are the reason why all of this is possible, they worked hard on Wheelie.
You can donate to them here if you wish:
http://androidroot.mobi/donations/
Am I understanding this right? This will make NVflash usable on my B8O?
Works on any Tf101, not the Tf101G or slider. Any tf B20-C14912409214012949 though
THANK YOU SOOOOOO MUCH. I am not going to stress about flashing nearly as much now. I was always scared of a bricking chance since NVflash wasn't an option.
Now that I have done this can I use the standard NVflash tool for flashing ROMs also?
Looking forward to trying this. I was wondering, how hard would it be to make an "idiot-proof unbrick" option on this?
Basically I was thinking make it so the user downloads the latest ASUS blob files or whatever it needs, and then have a button that automatically runs the scripts to unpack it and then flash it.
Would it be easily doable? May save a lot of people new to this a lot of headaches
jtc42 said:
Looking forward to trying this. I was wondering, how hard would it be to make an "idiot-proof unbrick" option on this?
Basically I was thinking make it so the user downloads the latest ASUS blob files or whatever it needs, and then have a button that automatically runs the scripts to unpack it and then flash it.
Would it be easily doable? May save a lot of people new to this a lot of headaches
Click to expand...
Click to collapse
This is coming in the next version which will be out later today.
Later today! What's the hold up?
I'm curious. Why do you want the ASUS updates now that we've gotten some good ICS ROMs for the Infuse? To me that sounds like a step backward.
Emandab1 said:
Later today! What's the hold up?
I'm curious. Why do you want the ASUS updates now that we've gotten some good ICS ROMs for the Infuse? To me that sounds like a step backward.
Click to expand...
Click to collapse
Oh it's already out (ver 0.5), I just forgot to tell you guys.
Are there any features that people want added? I love suggestions
whitekidney said:
Are there any features that people want added? I love suggestions
Click to expand...
Click to collapse
I would love to be able to flash ROMs with this tool. Is that possible to add?
Sorry for the noob question but can this be used to downgrade to honeycomb by putting one of the zipped blob files from Wolfs thread in the asusupdate folder?
joefloater said:
Sorry for the noob question but can this be used to downgrade to honeycomb by putting one of the zipped blob files from Wolfs thread in the asusupdate folder?
Click to expand...
Click to collapse
Yep, should work, tell me if you have any error and I'll reprogram it for you.
Putting just the "blob" file in the temp folder should also work.
This works awesome! Thank you so much.
Bah, stupid Android with red exclamation point!
EDIT: Nevermind, I am an idiot. At least now I know my Transformer is SBK2, all is working fine, thanks!
whitekidney said:
Yep, should work, tell me if you have any error and I'll reprogram it for you.
Putting just the "blob" file in the temp folder should also work.
Click to expand...
Click to collapse
I have tried it both ways, with the zip file in the asusupdate folder and with the blob in the temp folder and either way it just hangs and does nothing.
Any help would be greatly appreciated.
joefloater said:
I have tried it both ways, with the zip file in the asusupdate folder and with the blob in the temp folder and either way it just hangs and does nothing.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Try running it as admin.
I have tried both CWM recover and TWRP and I cannot get either one to open a zip to flash. Both say the same thing;
"Finding update package...
Opening update package...
E: Can't open /sdcard/CleanROM 2.7 Inheritance ODEX.zip
(bad)
Installation aborted."
I have tried redownloading the rom, downloading different and stock roms but to no avail. It always says can't open such rom...
I have already deleted stock operating system so I cannot go back to stock... I have recovery, fastboot, and that's about it. Someone please help me. :'(
did you unlock your device prior to rooting? silly question, i know.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
timrock said:
did you unlock your device prior to rooting? silly question, i know.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
Yes, my device is unlocked. I successfully used the bootloader unlocking tool by asus.
Are you downloading to the tablet or a PC or MAC desktop?
If you're downing to the tablets internal try instead to down the file to a desktop and move it to an external microSD in the tab.
Thats OK said:
Are you downloading to the tablet or a PC or MAC desktop?
If you're downing to the tablets internal try instead to down the file to a desktop and move it to an external microSD in the tab.
Click to expand...
Click to collapse
I am downloading from a PC onto a 16gb MicroSD card. It see's the file but cannot open it. "Unable to open zip file." "Error flashing zip 'external_sdcard/CleanRom 2.7 Inheritance ODEX.zip' "
MrUnfeigned said:
I am downloading from a PC onto a 16gb MicroSD card. It see's the file but cannot open it. "Unable to open zip file." "Error flashing zip 'external_sdcard/CleanRom 2.7 Inheritance ODEX.zip' "
Click to expand...
Click to collapse
Copy the zip to your internal memory and flash from internal (/sdcard).
buhohitr said:
Copy the zip to your internal memory and flash from internal (/sdcard).
Click to expand...
Click to collapse
I attempted that as well as other locations and it still will not flash any zip.
MrUnfeigned said:
I attempted that as well as other locations and it still will not flash any zip.
Click to expand...
Click to collapse
Have you try to redownload the rom file?? the file itself may be bad.
Try checking the md5sum of the zip file directly on the device (use adb shell from a PC and the "md5sum" command).
The zip files are fine. I almost want to think that it won't open the zips because it thinks I'm not rooted or something... Is there a way to install a rom from ADB or another way... as if I didn't have recovery?
MrUnfeigned said:
I have tried both CWM recover and TWRP and I cannot get either one to open a zip to flash. Both say the same thing;
"Finding update package...
Opening update package...
E: Can't open /sdcard/CleanROM 2.7 Inheritance ODEX.zip
(bad)
Installation aborted."
Click to expand...
Click to collapse
These messages come from the stock recovery. If you really installed CWM and TWRP, it didn't work - try installing your recovery again.
_that said:
These messages come from the stock recovery. If you really installed CWM and TWRP, it didn't work - try installing your recovery again.
Click to expand...
Click to collapse
I have tried installing it several times and using different recoveries.. Is there a way to install a different recovery with ADB or another way besides using "Scott's TF700T Recovery Install Tool"?
p.s. I really appreciate all the comments and help I'm receiving. Please keep it coming . I really want to get my tablet back in working order.
Did you check the md5 sum of ROMs? Could still be bad downloads
MrUnfeigned said:
I cannot install a .zip file with TWRP version 2.2.2.3 or 2.3.1.0. Both give me the same error.
"Finding update package...
Opening update package...
E: Can't open /sdcard/CleanROM 2.7 Inheritance ODEX.zip
(bad)
Installation aborted."
Click to expand...
Click to collapse
See the other thread - these messages are from the stock recovery, TWRP does not contain these strings.
TWRP looks like this: http://phota.me/7zXg.jpg - did you ever see this screen?
MrUnfeigned said:
I have tried installing it several times and using different recoveries.. Is there a way to install a different recovery with ADB or another way besides using "Scott's TF700T Recovery Install Tool"?
p.s. I really appreciate all the comments and help I'm receiving. Please keep it coming . I really want to get my tablet back in working order.
Click to expand...
Click to collapse
You have USB degugging checked under settings/developer options....correct?
Pretty sure _that is onto your problem with not having the custom recovery installed.
Remember you have to hold volume down for at least 5 seconds on a reboot.
Look to see if the tiny letters upper left say booting recovery.
If TWRP is installed you'll see a blue looking screen that says "TEAMWIN" after releasing the volume button.
*just a note if you're properly rooted and can verify root go to Google Play and download GOO Manager to your tablet.
GOO Manager is the easiest way to install the latest TWRP intead of using fastboot.
mr.wizard said:
Did you check the md5 sum of ROMs? Could still be bad downloads
Click to expand...
Click to collapse
How do I check the md5 sums? Never heard of that before...
_that said:
See the other thread - these messages are from the stock recovery, TWRP does not contain these strings.
TWRP looks like this: http://phota.me/7zXg.jpg - did you ever see this screen?
Click to expand...
Click to collapse
Here are some pictures of what's going on.
{
"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"
}
Thats OK said:
You have USB degugging checked under settings/developer options....correct?
Pretty sure _that is onto your problem with not having the custom recovery installed.
Remember you have to hold volume down for at least 5 seconds on a reboot.
Look to see if the tiny letters upper left say booting recovery.
If TWRP is installed you'll see a blue looking screen that says "TEAMWIN" after releasing the volume button.
*just a note if you're properly rooted and can verify root go to Google Play and download GOO Manager to your tablet.
GOO Manager is the easiest way to install the latest TWRP intead of using fastboot.
Click to expand...
Click to collapse
I have TWRP installed. Here are some picture to help describe a little better about what's going on.
why two threads? and the pics dont show in either thread.
http://s1323.beta.photobucket.com/user/MrUnfeigned/library/TF700%20problems
Here is a link to the place the images are stored. If you could take a look it might better explain things.
MrUnfeigned said:
http://s1323.beta.photobucket.com/user/MrUnfeigned/library/TF700%20problems
Here is a link to the place the images are stored. If you could take a look it might better explain things.
Click to expand...
Click to collapse
do you have the zip on the memory card? because sdcard is also known as the internal memory, not the actual microsd. move the zip to the memory card, if you have not done so already. navigate to the microsd card. You want to keep going up a level until you see a folder called REMOVABLE. open that folder, and you will see your memory card. now navigate to where the zip file is.
Ok so first Hello welcome to my first post thanks for viewing it.
Ive been searching google for days couldnt find anything on it maybe im blind but i did try!
Now to business im looking into getting my blob file on nvflash and it says
The current AndroidRoot.mobi bootloader versions are
Transformer Prime TF201: 10.4.2.15 (INCOMPATIBLE WITH HAIRY BEAN)
Transformer TF300: 10.6.1.15.3
Transformer TF700: 10.6.1.14.4
Nexus 7 (2012): 4.13
just search up "tegra 3 guide nvflash on jelly bean" on Google it should be the first website
I have included a picture of my about section on my tablet as I'm a bit confused on if mine will work or if it cant be a lower version
A video tutorial on this would really make this a lot easier
Anyway thought id post here cause i don't want a very expensive brick.
View attachment 2399950
Bkyourway said:
Ok so first Hello welcome to my first post thanks for viewing it.
Ive been searching google for days couldnt find anything on it maybe im blind but i did try!
Now to business im looking into getting my blob file on nvflash and it says
The current AndroidRoot.mobi bootloader versions are
Transformer Prime TF201: 10.4.2.15 (INCOMPATIBLE WITH HAIRY BEAN)
Transformer TF300: 10.6.1.15.3
Transformer TF700: 10.6.1.14.4
Nexus 7 (2012): 4.13
just search up "tegra 3 guide nvflash on jelly bean" on Google it should be the first website
I have included a picture of my about section on my tablet as I'm a bit confused on if mine will work or if it cant be a lower version
A video tutorial on this would really make this a lot easier
Anyway thought id post here cause i don't want a very expensive brick.
View attachment 2399950
Click to expand...
Click to collapse
I don't know that there's a problem with flashing the flatline.img (bootloader 10.6.1.14.4) with what you're currently having on your tab. However, just so you feel safe, downgrade you rom to 10.6.1.14.4, then flash the flatline image. Once you have the blobs, upgrade again.
graphdarnell said:
I don't know that there's a problem with flashing the flatline.img (bootloader 10.6.1.14.4) with what you're currently having on your tab. However, just so you feel safe, downgrade you rom to 10.6.1.14.4, then flash the flatline image. Once you have the blobs, upgrade again.
Click to expand...
Click to collapse
Can anyone point me to this build as it seems to have been removed on the Asus website and i cant find it on google anywhere though i shall continue searching.
I would greatly appreciate it.
Bkyourway said:
Can anyone point me to this build as it seems to have been removed on the Asus website and i cant find it on google anywhere though i shall continue searching.
I would greatly appreciate it.
Click to expand...
Click to collapse
You are on an ICS bootloader and you HAVE to upgrade to JB before you try to make nvFlash work!
Download any of the 10.6.1.14.x (.4/.8/.10) firmware (just make sure it's your SKU), then push the latest TWRP version in fastboot to the tablet - just to make sure that you really have fastboot working on your PC.
Then proceed with nvFlash.
Alright made some good progress i think.
Ive generated the blobs.
But i cannot figure out how to adb pull i keep getting this message (screenshot)
{
"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"
}
That is where it told me to use the command by the way
I have tried this on the screen where they were generated and with android fully booted
Will i have to regenerate the blobs because i left the recovery?
So I'm at a loss i appreciate all the help so far and hope i can get this resolved!
Edit:I think i need to install the universal drivers still I've been trying to cant figure it out and its way to late to continue if someone else can give me an idea on it or a step by step guide would be amazing.
Far as i can tell I've got the adb driver installed out of the driver pack but I'm not sure what to do now to get my blobs pulled off my device.
Bkyourway said:
Alright made some good progress i think.
Ive generated the blobs.
But i cannot figure out how to adb pull i keep getting this message (screenshot)
View attachment 2401361
That is where it told me to use the command by the way
I have tried this on the screen where they were generated and with android fully booted
Will i have to regenerate the blobs because i left the recovery?
So I'm at a loss i appreciate all the help so far and hope i can get this resolved!
Edit:I think i need to install the universal drivers still I've been trying to cant figure it out and its way to late to continue if someone else can give me an idea on it or a step by step guide would be amazing.
Far as i can tell I've got the adb driver installed out of the driver pack but I'm not sure what to do now to get my blobs pulled off my device.
Click to expand...
Click to collapse
Just use your tablet's file manager to search for them and copy them to a SD card or via USB. You don't HAVE to adb pull those files. They are somewhere on you internal SD.
Do you have adb working? Does it return your tablet's serial number if you cmd: adb devices
berndblb said:
Just use your tablet's file manager to search for them and copy them to a SD card or via USB. You don't HAVE to adb pull those files. They are somewhere on you internal SD.
Do you have adb working? Does it return your tablet's serial number if you cmd: adb devices
Click to expand...
Click to collapse
Got it working i backed up my blob and assorted other files and backed them up three times.
now i need to figure out how to backup the bricksafe file which ive been working on for hours
The wheelie --blob blob.bin command doesnt seem to be working so im probably doing something wrong
i have installed the apx driver for my tablet from the universal naked drivers
EDIT
I boot into nvflash where the screen is blank
type in the command
it then sits at resume mode untill i turn it off then it test below resumed mode
I would like to point out that i am using google and searching forum after forum for answers before i come here asking question that are easily answered by a quick search.
Thanks again for any help
Bkyourway said:
The wheelie --blob blob.bin command doesnt seem to be working so im probably doing something wrong
Click to expand...
Click to collapse
Apparently.
I think im done!
Got all the files backed up thank you for all your help guys!
For those having issues in the future i had to place my blob file in the folder with the wheelie.exe before the --blob blob.bin command would work
Okay, I am sure a lot of you already know how to do this to your Pixel. Some of us do not, and I was one of them. I am the standard noob that just followed Youtube videos to unlock previous carrier locked phones. I am now enjoying this Google Pixel that is unlocked!
So if you are reading this thread, hopefully there isn't another one just like this (yes I looked).
To start off, if you are in here reading this, you have unlocked your bootloader and installed a custom recovery such as TWRP and rooted. Now you are seeing that you need to update your phone with the latest security patch. You try and you try and you can't do it. Even when you unroot it will still fail to update, or at least it did for me. Here I will explain what I went through and did to obtain the latest update. (Warning, you will loose root and custom recovery). THIS IS INTENDED FOR THE GOOGLE STORE PURCHASED PHONES
Lets get this started finally.....
Go into your developer options and enable usb debugging.
Download the newly released package file from google that has fastboot and ADB without needing android SDK.
DOWNLOAD or read about it HERE
Now you will need to download the Factory Image for you device
Find your correct device HERE
Make sure you choose the correct device and correct update, for me I downloaded the "7.1.1 (NMF26U, Jan 2017)" for my Pixel. Also a USA phone.
So now you have the adb fastboot binary package and your factory image. You will need to extract the platform-tools-latest-windows.zip and open the folder and you will see another folder, open it and now you will see a bunch of files. Now open another window and extract your factory image. Once it is done, open the folder until you see the files. Now copy these into the Platform tools folder in the directory with the fastboot.
Once this is done your folder should look like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now you will want to right click "flash-all" and click edit. It will open notepad and show the contents of the batch file. You can hit Ctrl+F and type in -w in the search and hit okay, or you can look for it without search (it is near the bottom). Once you find it, just delete the "-w" and save the file. Make sure to keep it as the batch file or this won't work.
Once this is done, in the folder that is shown above, click a blank area in the folder so no file is highlighted. Now hold shift and right click, it will come up with a dialog saying open command window here, click that.
Now we are going to reboot the phone into bootloader mode. In the command window, type everything that is underlined below
adb reboot bootloader
Now your phone should have booted into the bootloader screen or it should be asking for USB rights to use adb. If it asks for permission, hit okay and re run the code above and your phone should reboot.
Once you are in the bootloader screen you will need to do is run the flash-all.bat. It will load and go though some text on the CMD window it brings up. It will say some files are missing, which is fine. But if it fails it will tell you that it did. You can also tell by rebooting the phone or click "start" in the bootloader mode and then checking for OTA updates. It should say January 5th patch installed.
Now you can go through and install your custom recovery again and re root. Which takes no time at all and I am sure someone on here has posted before. If not, let me know and I can make a tutorial over it.
Note: I am very sorry for the bad layout and extended write up. First time ever doing this and I am hoping to help people. If there are any errors, let me know!
All of this is already well known and documented. It is device molding 101
No one with 2 licks of common sense uses YouTube videos for something like this.
zelendel said:
All of this is already well known and documented. It is device molding 101
No one with 2 licks of common sense uses YouTube videos for something like this.
Click to expand...
Click to collapse
Haha well my apologies, I did state that I was a complete noob about all of this. I'm sure there are other noobs like myself
exbtlegends said:
Haha well my apologies, I did state that I was a complete noob about all of this. I'm sure there are other noobs like myself
Click to expand...
Click to collapse
I'm not a noob, but i'm a old fart, and we forget things, even simple things like this, I'm glad to have a simple reminder of how to do things. Thanks for the refresher.
jrat69 said:
I'm not a noob, but i'm a old fart, and we forget things, even simple things like this, I'm glad to have a simple reminder of how to do things. Thanks for the refresher.
Click to expand...
Click to collapse
Not a problem ?
I know you say this is for the GPS version, but has anyone tried it on Verizon? I'm not sure if the firmware is the same on both phones, so I don't want to soft-brick by downloading the Google version if they're different. Same boat as you were, OTA fails even after unrooting.
32BitWhore said:
I know you say this is for the GPS version, but has anyone tried it on Verizon? I'm not sure if the firmware is the same on both phones, so I don't want to soft-brick by downloading the Google version if they're different. Same boat as you were, OTA fails even after unrooting.
Click to expand...
Click to collapse
As long as you never re-lock your bootloader, the process is the same. There's no more separate Verizon images, just USA and international.
This is really complicated. ADB side load the OTA file, reinstall TWRP and root, done.
Good work. This is a very minute stuff of removing -w from the batch file. Very handy work.
Sent from my Pixel using Tapatalk
Do you need to reflash stock kernel before removing root/TWRP before flashing?
32BitWhore said:
Do you need to reflash stock kernel before removing root/TWRP before flashing?
Click to expand...
Click to collapse
Flashing the image overwrites anything you customized besides the regular user data and internal storage (with the -w removed). You don't have to remove or reflash anything else before following these instructions.
TCPDump said:
This is really complicated. ADB side load the OTA file, reinstall TWRP and root, done.
Click to expand...
Click to collapse
I couldn't side load the update.. TWRP would not load the side load feature.
I'm having an issue also: https://forum.xda-developers.com/pixel/help/sideload-ota-t3534926... Can we just unroot, take the OTA and then reroot?
km8j said:
I'm having an issue also: https://forum.xda-developers.com/pixel/help/sideload-ota-t3534926... Can we just unroot, take the OTA and then reroot?
Click to expand...
Click to collapse
Even when I un rooted mine. I was still failing to get the update.
If you made any changes the the system partition then it will fail and simply unrooting doesn't make the all the changes needed. So if OTA mean anything to you then I would suggest not messing with your device as there is Jo promise that after an OTA you will be able to root again tonight away
jesssiii said:
As long as you never re-lock your bootloader, the process is the same. There's no more separate Verizon images, just USA and international.
Click to expand...
Click to collapse
I know the past 2 were the same for google pixel and Verizon pixel but I wouldn't assume they are always going to be. I'm sure some of them will be specific at times whenever Verizon decides they wanna mess with them
FYI, I was able to sideload after updating TWRP to RC1, but now SuperSU 2.79 will install from within TWRP but when the phone restarts SuperSU is not installed... not sure if we have to wait until a new version of SuperSU is released.
SpoiledHeeb said:
FYI, I was able to sideload after updating TWRP to RC1, but now SuperSU 2.79 will install from within TWRP but when the phone restarts SuperSU is not installed... not sure if we have to wait until a new version of SuperSU is released.
Click to expand...
Click to collapse
You need SuperSU 2.79 RC3