Hi,
First, i apologize for my english!
So, i'm on rooted device by vipermod, WW ROM on 8.6.5.21.
When the OTA for ICS was coming, after downloading and reboot a droid with an exclamation mark come!
I've trying the OTA after an hard reset but there was always the same trouble.
For launch the TF101 in recovery mode there is also the same problem!!!
So i read on various forums for another people with the same trouble, they managed the upgrade to ICS manually with NVFlash: forum.xda-developers.com/showthread.php?t=1524302&page=1
My device is recognized in APX mode, but when i launch the bat file ,my device is no more recognized and i can't flashing!!!!
Anyone as the same trouble??
Only B60 series below and some earlier versions of B70 work with NVflash. Which series are you on?
I've a BBO device.
I've search but not found a thread with an history of different series of the TF.
How can i know the date of manufacture of my device?
Related
Eee Pad is bricked. Here's the story. I used http://forum.xda-developers.com/showthread.php?t=1125714 (pure root) to root the device about less than a month ago.
Just today i saw an update for the OS and i updated, but when i turned it back on it was bricked. WHAT DO I DO? PLEASE HELP
try this
turn off your TF
plug it to your computer
turn on your TF while holding the "up" volume key
if your computer detects your TF, then good news, there's hope for you. your TF is not bricked, and you still have access to NVFLASH.
you can use it to restore your TF into a functional state in many ways.
one of those ways is enumerated here: WARNING, this will erase all your data.
http://forum.xda-developers.com/showthread.php?t=1123429
remember that the image files gets extracted to the same folder as the .bat or .sh files, (some people misplace them and think it didn't work)
Sent from my Transformer TF101 using Tapatalk
ilive12 said:
Eee Pad is bricked. Here's the story. I used http://forum.xda-developers.com/showthread.php?t=1125714 (pure root) to root the device about less than a month ago.
Just today i saw an update for the OS and i updated, but when i turned it back on it was bricked. WHAT DO I DO? PLEASE HELP
Click to expand...
Click to collapse
I agree with finalhit about how to fix it, but am curious what you actually did where you say " Just today i saw an update for the OS and i updated ". ?
Did you apply an OTA update, apply some other thing , and if so, which other thing? You might just be a quick partition 5 nvflash from success (restoring CWM to a reasonable version for your system). Which flavor of TF? US, WW, TW? more info.
THANKS IT WORKED!
Well actually it was my father who updated. I rooted his TF for him (to get netflix working) back on 3.1, and today he just decided to update OTA to 3.2 (the US version.). Glad its working again or i would have been screwed
I have spent hours searching and reading, but I can't find an up-to-date answer.
I have a B70 TF101 that is at 8.6.5.21. I rooted using nachoroot. I want to put on cyanogenmod 9 RC. It does work using ROM Manager. Seems that in spite of telling it to install clockworkmod, it doesn't. I can't get it into APX mode. So I guess I'm ready to try to downgrade it to 8.6.5.19. I find loads of references and links to multiupload for that file, but it no longer is available.
How can I downgrade to 8.6.5.19? I just want to put on Cyanogenmod.
Please help.
Hi Thornthree,
try http://forum.xda-developers.com/showthread.php?p=25385687 step 3.
in this post you find places for the blob file and what to do (step 3)
I think you need the 8.6.6.19 (is for tf101/g, but also for the tf101
But is your TF now able to go into apx mode yes or no?
maybe start with this:
http://forum.xda-developers.com/showthread.php?t=1688012
goodluck......
There's not a need to downgrade.
You could also use PERI.
http://forum.xda-developers.com/showthread.php?p=26737790
Yep, several one-click rooting methods out for the latest versions.
My PERI tool as mentioned above is one of these, just plug-in, run and root.
I could never get into APX mode. I followed all of the instructions to get there that I could find but none of them worked. The power and up volume keys did nothing on my TF101. I finally got power and volume down to get me into clockworkmod, but then it couldn't find the zip file. When I finally got the zip file visible, then chose reboot system now, it just kept looping into clockworkmod. Somehow, in the end, after all kinds of crazy attempts of key combinations, it's somehow worked.
I had to end up going back to factory reset, then all kinds of acrobatics to place a zip file in the right place, then do another factory reset and wipe, which somehow ended up in my having cyanogenmod working. I don't know if I could reproduce the process. Also, it's very frustrating that none of the tutorials did anything to work on my tablet. I'm just thankful that it's where I want it right now. I don't know if I need to install OTA root keeper or not, and I don't know what I'll do if I ever need to upgrade to a different ROM or an updated cyanogenmod.
Thanks for all the replies. I'll keep them in mind for the future.
Sent from my DROID2 using xda app-developers app
I need to upgrade my TF101G WW B90 and can't get it out of 3.0.1. I've tried numerous things for several days to no avail
I'm asking for expert advice from anyone that has done this successfully (please don't give advice such as "try this, it should work"), I need a definite solution PLEASE :good:
Solved
I downloaded the latest firmware from Asus and renamed it EP101_SDUPDATE.zip, put it on my MicroSD and booted into Asus Recovery, and now Bob is officially your uncle!
I've searched but every thread dealing with this concerns a tablet whose update failed or rooted or something. I just bought my gf a brand new Champaign tf700, it came with ics obviously, and it says no update found when I go into settings and search for update. Tried a factory reset and cold boot... no luck finding a JB update.
How do I get this thing to update? Any easy solutions?
nonstop14 said:
I've searched but every thread dealing with this concerns a tablet whose update failed or rooted or something. I just bought my gf a brand new Champaign tf700, it came with ics obviously, and it says no update found when I go into settings and search for update. Tried a factory reset and cold boot... no luck finding a JB update.
How do I get this thing to update? Any easy solutions?
Click to expand...
Click to collapse
http://support.asus.com/Download.as...&m=ASUS Transformer Pad Infinity TF700T&os=32
Steps of Update:
1. Check SW version of your Eee Pad Transformer Infinity TF700T*
2. Download Eee Pad Transformer Infinity TF700T Firmware: V10.4.4.16 Only for US SKU and Update version of SOP (From “Manual” Item)
※Firmware update cannot do *SKU conversion* and downgrade version.
Wrong SKU may cause update failure, You can only update your SW version on the Same SKU
*How to check SW version of your Eee Pad Transformer Infinity TF700T?
Path: [Settings]-->[About tablet]-->Build number
Example: You should be able to see the build number WW_epad-10.X.X.X_2012xxxx, where “WW” means SKU.
**Basically download the US update (Guessing since your profile says Detroit you have US version), and store the update onto your micro SD card. Then plug the micro SD into the tab and it should prompt to update. Good luck.**
Are you rooted? Do you plan to unlock? What version are you on? (.26, .30) If you are on .26, check out the thread on NVFlash in development. After you upgrade, you cannot use NVFlash. If you need to upgrade, and don't want to unlock, you should be able to go to asus direct and download the update. Check out this thread on NVFlash : http://forum.xda-developers.com/showthread.php?t=1901479.
Try this one for update: http://forum.xda-developers.com/showthread.php?t=1803090, note, it does require root.
I just returned a prime today that I bought for a friend in exchange for a C8 infinity. Tablet didnt want to update to JB and was stuck on 4.0.3. So I used my laptop and went to the Asus support download site, download 4.1.1 US version, unzipped it and another zipped file came up, Plugged the infinity to the laptop via Asus cable, copied the second zipped file into the main directory I think it was /mnt/sdcard, Rebooted and the exclamation sign came up and installed the new 4.1.1. Then went back and deleted the file that I copied on to the main directory. Dont need an sdcard to manually update.
I just received my tf700 on Tuesday (from NewEgg) . I got two OTAs updates that afternoon - neither was JB. Finally JB came through last night. So you might have to wait a day or two. ...
Sent from my NookColor using xda premium
Try registering your new tablet on the Asus website.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
junrider said:
I just returned a prime today that I bought for a friend in exchange for a C8 infinity. Tablet didnt want to update to JB and was stuck on 4.0.3. So I used my laptop and went to the Asus support download site, download 4.1.1 US version, unzipped it and another zipped file came up, Plugged the infinity to the laptop via Asus cable, copied the second zipped file into the main directory I think it was /mnt/sdcard, Rebooted and the exclamation sign came up and installed the new 4.1.1. Then went back and deleted the file that I copied on to the main directory. Dont need an sdcard to manually update.
Click to expand...
Click to collapse
This works perfectly.
Sent from my SPH-D710 using xda app-developers app
nonstop14 said:
I've searched but every thread dealing with this concerns a tablet whose update failed or rooted or something. I just bought my gf a brand new Champaign tf700, it came with ics obviously, and it says no update found when I go into settings and search for update. Tried a factory reset and cold boot... no luck finding a JB update.
How do I get this thing to update? Any easy solutions?
Click to expand...
Click to collapse
1. When still on .26, install Nvflash. Look it up on the forum for the steps. It's not that hard.
2. You might be one of the people having an Infinity that apprarently is not showing up in ASUS' serial number database. This will preclude you from a) receiving an OTA (Over-The-Air) update like the one you're hunting for, and b) will prevent you from being able to unlock the device, so no custom recoveries (and therefore no backups) and no custom ROM'ing. For a lot of us, that was enough to seek (warranty) replacement.
3. If you decide to keep this 700, the procedures given for manually updating a firmware work. However, I'd sincerely recommend you reading through their main threads to really get a good feel for what to do and, more importantly, what NOT to do. There are quite few ways of updating a 700 by hand, depending on what works and your skill level.
Thanks for posting this question. I was having the same issue and now i found my answer WIN!
So it had been quite some time since I tried messing with my tf300 so....
I was on cm-9, when to update to cm-10.1, tried to update twrp then it wouldn't boot to recovery, tried to flash back to stock JB bootloader using "fastboot flash system.blob" gave me a flash error (invalid size) and for some reason fastboot doesnt recognize my device.
So I have no recovery and no rom.
I tried "fastboot boot boot.blob" from cm-9 and cm-10 and it wont boot. just stuck on "waiting for device"
When I type "fastboot devices" it just starts a new command line, no serial number.
I can include any information needed to help my situation, I just need to be told where to look.
To be honest, I couldn't remember what bootloader I was on. It had been a while. Is there a way to tell?
Can't get the tablet to stay off either while I wait for help. Lol
Sent from my LG-LS970 using xda premium
Any ideas?
Sent from my LG-LS970 using xda premium
Now I think my situation might have gotten worse.
I can't get into fastboot now. It just keeps trying to go into recovery mode but there is no recovery so it just continuously reboots.
No one can help?
Sent from my LG-LS970 using xda premium
Well that sucks...
Sent from my LG-LS970 using xda premium
Depends on what you were trying to do, were you trying to update the recovery first and to what version. I believe cm 9 is based on an older build of bootloader. What exactly did you do. From my knowladge as to reading and seeing so many people just flashing before reading the threads you should first update the bootloader then the recovery depending on what recovery version you were trying to update to. From what it sound like you tried to update the recovery before bootloader just not sure what version of recovery but if wrong one and didnt update bootloader sounds like you maybe un recoverably bricked like what everyone else is doing before reading and as of now. Aslo if you have an nvflash backup there may be a fix i'm just not sure how as i never had it but accorging to some it seems that was the only hope for them to get out. Reaad the threads there maybe help on here some where just so many are flashing and bricking before reading people are getting frustrated because theres no help for it.
I know it doesn't help, but since you wanted to know what happened, I can tell you that much. Since you were on CM9, you had to be on the original ICS bootloader. Stock JB can't be fastboot-flashed over ICS because of changes to the partitioning and other low-level stuff, which is why it wouldn't flash and why it subsequently failed to boot.
I'm also just picking up my TF300 for the first time since August. I just recovered from a soft-brick today (my story, which in hindsight was a complete f-up on my part), which was why I hadn't been using it. I ended up fastboot-flashing the newest ICS firmware (I actually tried it back in August, but fastboot wouldn't work; I didn't do anything differently today, but fastboot had been updated recently and magically worked), then performing the NVFlash backups from the sticky thread (this isn't quite where our paths diverged, but it may have been a good idea to do that before you tried upgrading to JB -- not that it helps now, but for future reference).
Like you, I tried fastboot-flashing the stock JB firmware over the ICS firmware and got the same error you got. So, I tried flashing the ICS firmware again, but got the same Invalid Size error. At this point, my tablet wouldn't boot past the splash screen (not the animation with the spinner; the first one with the NVidea logo in the corner), and fastboot wouldn't flash any firmware.
This next part is the part where our stories more-or-less fork.
Faced with another soft brick just hours after fixing one, I fastboot-flashed TWRP instead (made sure to use an ICS version since the JB firmware didn't flash, and the NVFlash bootloader I had was based on the ICS bootloader), which worked, and I booted into recovery. I used TWRP to flash the ICS firmware (I actually had it on my internal SD card in August, but I could have also pushed it with ADB if I didn't already have it), and I got a functioning tablet again.
Next, to upgrade to Jellybean correctly, I booted into Android and used ADB to push the Jellybean firmware to my tablet. I put it on the root of the internal storage, and the tablet saw it and alerted me to the update. Since TWRP had been replaced by the stock recovery when I flashed the ICS firmware, I just let the tablet do its thing with the update, and I ended up with a perfectly-functioning stock Jellybean ROM. I then performed each subsequent update (I never once skipped any update steps) the same way until I was on the newest 4.1.1 firmware (I'm not updating to 4.2.1 until CM10.1 works with it).
I'm not sure how much research you did before you updated your tablet, but I was trolling the TF300 forums for a good 2 or 3 hours before I even tried upgrading, and I still had trouble (I never saw any posts about people trying to fastboot-flash JB over ICS, so I didn't know it wouldn't work until I tried it at least 3 times). From the limited details you provided, it doesn't sound like you did much searching before you started flashing. In the future, it may be a good idea to research a lot more than you think you have to before flashing things on expensive devices.
Also, in the future, when you're asking for help like this, it's best to go overboard on the details - just like a murder investigation, we want to help you figure out what killed your tablet, but we can't do that if you don't tell us about the strange footprints you saw in your neighbor's lawn the night before. Mention every single icon or word that appears on the tablet, every single button-press you've made, every keystroke you've typed, etc., whether it seems important or not. We can't be there with you, so you have to bring your situation to us.
At this point, the only advice I can give is to let the tablet die, charge it again (so the battery's full but the tablet's powered off), and try again when the battery's full. If you can get ADB to work while the tablet is trying to boot recovery, you may be able to flash a new recovery and then try flashing the ICS firmware (flashing the JB firmware might work, but then you can't use NVFlash). That's about the best you can do if you can't get it into fastboot mode (short of RMAing your tablet). If you can get fastboot to work somehow, then you can easily flash a new recovery and follow the steps I took. But if you do get your tablet booting with the ICS firmware, perform the NVFlash backups ASAP before you update to Jellybean.
I hope you can get your tablet to work. I thought mine was a goner until I got lucky with an updated fastboot. Now, I'm ecstatic that it works, and I'm going to be a lot more careful in the future.