Related
I have a Transformer B70 and I used the Pure root 8.4.4.11 method
Shown here (http://forum.xda-developers.com/showthread.php?t=1185104)
and I can't seem to get into recovery after following all the steps.
it seems to hang at "Booting recovery kernel image"
Warboy said:
I have a Transformer B70 and I used the Pure root 8.4.4.11 method
Shown here (http://forum.xda-developers.com/showthread.php?t=1185104)
and I can't seem to get into recovery after following all the steps.
it seems to hang at "Booting recovery kernel image"
Click to expand...
Click to collapse
I'm having the same issue too.
And what is really weird is that it was working the very first time I did it, but after trying to root the 3.2 update, I can't get it to work anymore. Nor can I get the tablet to see the 3.2 OTA... I wonder if I borked it up somehow with NVFlash. Anyone got any ideas?
Did you read the note about recovery in first post?
brk said:
Did you read the note about recovery in first post?
Click to expand...
Click to collapse
my guess is no.
Yeah, I completely missed that. I need to sleep more instead of hacking tablets...
I still don't understand why it worked the first time I did it manually, but after restoring to stock via NVFlash, I can't get the exact same recovery.img file to boot on the same tablet.
Is there a way to wipe the whole flash and start fresh? I had this kind of issue on the GTablet and the full wipe clean and re-install to stock fixed it. Maybe I can look at the commands to do it in the GTab and adapt it for myself.
I just installed clockworkmod recovery though a nvflash method with a rooted 8.4.4.5
I believe this is my first post on these forums. I just did the nachoroot mod today per
[ROOT] NachoRoot - supporting all firmware jan 3rd 2-118
and
[Update: Works On The OG Transformer, Too!] Exclusive: 'NachoRoot' Brings Root Access To The Transformer Prime, Even With The Newest Firmware:
on my TF101 B80 32 gb.
I did the procedure per the second link above. I've been able to verify root with Root Check Basic from the Android Market.
I've never rooted an Android device before and am quite concerned about unrooting, in case I ever need to return my unit to Asus.
I've heard I need cwm, the clockwork recovery mod, in order to unroot. I hope it is ok to do this after the initial rooting procedure.
Please pardon me if this has been asked before, as it my first time, and I find a lot of the documentation a bit cryptic.
Thanks in advance...
Yes the procedure to unroot with your build number required flashing a repacked stock ROM via CWM recovery. For TF with older SBK they can use NVFlash.
You can flash CWM anytime with RecoveryInstaller
http://forum.xda-developers.com/showthread.php?t=1346180
To unroot
http://theunlockr.com/2011/11/28/how-to-unroot-and-remove-cwm-recovery-on-asus-transformer/
Thanks fire the response!
I've managed to browse parts of the file system previously blocked. Otherwise, I haven't made another changes to my system. Its nice to finally where some of my apps have been storing data.
I am curious about cwm which I've installed. It enables recovery mode to restore the stock ROM. It is one of the two options presented after holding the power and volume down buttons together. One option is cold boot and the other is recovery. The recovery option was there before nachoroot and the cwm installations. What is different about the recovery option now versus before?
skallal said:
Thanks fire the response!
I've managed to browse parts of the file system previously blocked. Otherwise, I haven't made another changes to my system. Its nice to finally where some of my apps have been storing data.
I am curious about cwm which I've installed. It enables recovery mode to restore the stock ROM. It is one of the two options presented after holding the power and volume down buttons together. One option is cold boot and the other is recovery. The recovery option was there before nachoroot and the cwm installations. What is different about the recovery option now versus before?
Click to expand...
Click to collapse
Are you sure you have flashed CWM recovery? You should have a lot more options.
After installing RecoveryInstaller, did you open the app and click on "flash CWM recovery" tab?
I didn't click on the flash tab because I don't intend do recovery at this time. To be clear I understand what recovery is, I think it means to return my TF101 back to an unrooted state with the current ota release, which is .23, and also wipe out all my data. If this is incorrect, please let me know.
You said I should see more options than just the flash tab. What else should I see? And when should I see it?
Now that I've successfully rooted, my main objective is to learn how to return my device back to its unrooted state in order be ready for the ICS ota update when it arrives. If that means I'll also wipe out my data in the process, then I'll need to learn how to backup and restore.
Please do let me know if I understand the process or not. I still have have a reading and learning ahead.
Recovery lets you flash packages, ROM patches, and complete ROMs that require very deep (i.e. low level) system access.
If you don't intend to flash any custom ROMs (e.g. Revolver) or install things that need low level system access (e.g. a USB to Ethernet adapter) you won't need to flash CWM.
One of the admins on Transformer Forums gave me the impression I need cwm to unroot my TF101. That is the only reason I downloaded it.
If I don't need cwm to unroot, then I'll focus my reading on unrooting link listed earlier in this thread.
I don't have any interest in other roms, at least not for now. My concern, for now, is unrooting when it comes time for the ICS update...
baseballfanz said:
Yes the procedure to unroot with your build number required flashing a repacked stock ROM via CWM recovery. For TF with older SBK they can use NVFlash.
You can flash CWM anytime with RecoveryInstaller
http://forum.xda-developers.com/showthread.php?t=1346180
To unroot
http://theunlockr.com/2011/11/28/how-to-unroot-and-remove-cwm-recovery-on-asus-transformer/
Click to expand...
Click to collapse
The second link above (theunlockr.com) refers to old firmware (repacked-8.2.3.13_US_without_SU_app.zip).
Is that file already outdated?
Perhaps a newer version for .21?
Well it all depends on your serial number. Early builds (B60 and earlier plus some B70) you can use NVFlash to get back to totally stock.
If you have B80(and some B70) and above you'll need cwm recovery to get back to stock following the link i posted above.
I finally watched the video from your earlier post and it answered a quite a few questions.
Bottom line: when it comes time to update to ICS, do I need to unroot first?
The ICS update is my main reason for unrooting. I read for some users lost root after the last ota update to .21. I don't have any immediate need to unroot other than to prepare for the ICS update when yet comes.
And there's also a long term need unroot when and if I ever send the unit back to Asus for service.
So, my brand new Transformer came yesterday (From Amazon) and it has an SBK v2 bootloader (sbk detect under mac, serial is BC0KAS), here is what I understood, and ask for questions, after many reading, can you please confirm or correct?
1- SBK v1 can be rooted, put custom roms, return back to stock, unbrick in case something goes wrong with nvflash. [CONFIRMED]
2- SBK v2 can be rooted? (some say B70 can, or is it just B70 with SBK v1?) [CONFIRMED]
3- SBK v2 can have custom roms? (depends on point 2)? [CONFIRMED]
4- SBK v2 cannot have ClockWorkMod? [Wrong, SBKv2 CAN have ClockWorkMod]
5- SBK v2 does NOT support nvflash, so if you softbrick you cannot recover (I am certain of this one, I guess). [CONFIRMED, if you damage ROM & clockworkmod = BRICK]
What can be done then with an SBK v2 device? wait for developers to find the ways to crack it (as sbkv1), or have an nvflash working?
Is there some petition open to tell Asus to unblock the bootloader as they did with the Transformer Prime?
currently (after 1 day), I am already thinking of returning it back.
I know i might be asking a lot of questions, but information is not easily available in 1 thread.
Update:
New question: with SBKv2 is it possible to return back to stock (Stock ROM, unrooted with stock recovery)?
Thanks in advance...
SBK doesn't keep you from rooting from what I understand, the firmware version does (current 8.6.5.21 has been cracked and can be rooted by nachoroot, or if not can be firmware upgraded to 8.6.6.19 and rooted with razorclaw)
SBK2 simply keeps you from using NVFlash to recover, as far as I know, once you are rooted, you can install CWM recovery on any SBK version.
Just alot of SBK2 owners have not rooted or installed CWM if they did root for fear of losing their recovery (if you bungle the recovery, you may be able to flash your recovery through the ROM, if you mess up your ROM, you can flash another ROM through CWM or stock recovery, BUT if your recovery img is corrupted AND your ROM stops working, SBK1 can flash both via NVFlash, SBK2 is effectively bricked)
EDIT: SBK2 USED to keep you from being able to root when NVFlash was the only method available for rooting and installing superuser and busybox, see here
http://forum.xda-developers.com/archive/index.php/t-1347388.html
I was going to say I will try to NVFlash my device and tell you if it is SBK1 or 2, I assumed it would be SBK2 because it is B70, but lo and behold it was SBK1..I would have been lucky a few months ago before the razorclaw app was developed and SBK2 was rooted, but I didn't get my TF until after that..
So, SBK1 here have gone to stock many times, but cannot confirm the procedure for SBK2 tablets, though I assume it is possible. Thought for sure I was going to be able to come back and say my TF was SBK2 and had been to stock, but nope haha
EDIT: considering you can backup your entire setup via CWM, recovery mage and all, and flash it wthin CWM (like restoring the backup) is evidence to me that you can no doubt unroot an SBK2 as long as you have a working recovery image.
From what I understand, the first thing to do on a new device is to have root (with the tools you mentioned), once you have this (stock ROM with root), you can install CWM, and with CWM you can install custom and stock roms.
but how can I bring back the standard Stock recovery? when I have stock unrooted ROM I can't flash Recovery partition from the Android itself, and nvflash doesn't work on SBK2. can CWM be used to flash a stock recovery over itself?
Is there any chance that Asus will unlock the TF101 when it releases the tool to unlock the Transformer Prime (in February, as promissed)? in case they both use same blocking technology?
mcbyte_it said:
From what I understand, the first thing to do on a new device is to have root (with the tools you mentioned), once you have this (stock ROM with root), you can install CWM, and with CWM you can install custom and stock roms.
but how can I bring back the standard Stock recovery? when I have stock unrooted ROM I can't flash Recovery partition from the Android itself, and nvflash doesn't work on SBK2. can CWM be used to flash a stock recovery over itself?
Is there any chance that Asus will unlock the TF101 when it releases the tool to unlock the Transformer Prime (in February, as promissed)? in case they both use same blocking technology?
Click to expand...
Click to collapse
Yes you can flash stock recovery over cwm from within cwm, you have to have the file..i found it and have it on my hard drive, but can't remember where i got it from..the same procedure as going stock on sbk1 tablets
The proof that you can flash recovery while in recovery mode is that you can install higher versions or different developer's versions of recoveries from cwm. Im sure when running cwm it is being read from ram so flashing the recovery partition will only affect your recovery after you reboot (i.e. Can technically go into cwm, flash recovery partition first and then flash stock rom, but i believe packages are available to flash both at once, and there would be no reason to do it in this order, but im pretty sure it could be done)
Somewhere on here is a guide how to return to stock to prepare for the ics update, it should contain the odd bits and links to fill in my sparse knowledge.
Getting back to stock ROM and recovery
http://theunlockr.com/2011/11/28/how-to-unroot-and-remove-cwm-recovery-on-asus-transformer/
That's the one!
8329 recovery.zip.. Btw it should be noted that the recovery image is not region-branded, that should mean it will work with any region, while you will need to make sure to get the region-specific firmware..
And i did the procedure in reverse from that thread, not to confuse, but i:
Placed both files (recovery and firmware) into my sd card root
Booted into cwm and flashed stock recovery, wipe everything before powering down
Rebooted into recovery again and flashed the firmware with stock recovery.
I think it will work either way, i left my rooted rom in place so i could install cwm if the recovery flash failed, i suppose the alternative is leaving your recovery in place in case the stock rom flash fails..i just like knowing on the first reboot whether my first flash was successful and not flashing blind imo.
Bump.
This post suggest new Transformers can be nvflashed too.
http://forum.xda-developers.com/showthread.php?t=1518552
Waiting for answer from OP to see what he has to say.
Anyone else got any news?
josteink said:
Bump.
This post suggest new Transformers can be nvflashed too.
http://forum.xda-developers.com/showthread.php?t=1518552
Waiting for answer from OP to see what he has to say.
Anyone else got any news?
Click to expand...
Click to collapse
SBK v2 is still not nvflash compatible
josteink said:
Bump.
This post suggest new Transformers can be nvflashed too.
http://forum.xda-developers.com/showthread.php?t=1518552
Waiting for answer from OP to see what he has to say.
Anyone else got any news?
Click to expand...
Click to collapse
That thread is full of bad information and garbage. I would forget it exists.
I was under the impression from reading different Asus statements that the sbk for TF-101 was going to be released with ICS the way it was with TF-201, did Asus not keep their word on this?
Cheers!
-M
Xda member since 2007
dragon_76 said:
I was under the impression from reading different Asus statements that the sbk for TF-101 was going to be released with ICS the way it was with TF-201, did Asus not keep their word on this?
Cheers!
-M
Xda member since 2007
Click to expand...
Click to collapse
That would be news to me. If you could find a source for this statement, I would be interested.
From what I understood reading (this forum and other sites), the story is different between TF101 and TF201: the Prime has the bootloader locked/encrypted, and with it locked you can't even install the CWM recovery, while with sbkv2 you can do everything except nvflash, so i doubt that asus will release anything for the sbkv2 transformers.
anyway, i am not following the subject, but does the new Prime unlocker allow something like nvflash to work?
mcbyte_it said:
5- SBK v2 does NOT support nvflash, so if you softbrick you cannot recover (I am certain of this one, I guess). [CONFIRMED, if you damage ROM & clockworkmod = BRICK]
Click to expand...
Click to collapse
What can I do with brick? Only waiting for some solution?
Did Asus could repair it for a fee?
RMA
Thinking about calling ASUS to ***** about this tablet being locked and demanding the opportunity to either downgrade to sbk1 or upgrade to a prime. I'll let y'all know my findings.
Styxiak said:
What can I do with brick? Only waiting for some solution?
Did Asus could repair it for a fee?
Click to expand...
Click to collapse
Until a solution is found, you can use a bricked device as a very nice door stop.
Sent from my Transformer TF101 using Tapatalk 2
A solution has been found
http://forum.xda-developers.com/showthread.php?t=1688447
nvflash for sbk v2,finally ?
android root .mobi has a released a a solution, i am going to try it, will post results when done
The revival of the thread from the dead! -dun dun dun-!
Anyway, yes 'Wheelie!' Nvflash for Sbkv2 devices has been released, and works very well on my b70 Sbkv2
it only works on the tf101 though, not the G or Slider.
I'm about to buy used Eee Pad Transformer TF101, with dock/keyboard. It has serial number starting with B90KAS and latest firmware update (ICS).
What is the current status of bootloader unlocking craft? Would I be able to install Ubuntu/OpenSUSE and/or use custom kernels with latest KatKiss ROMs?
I've heard that there are different versions of the TF and one in particular can't be rooted or something. I plan on rooting this weekend but I want to make sure I have a rootable version. How can I check?
With all the methods out there, It's hard to believe you'll have an unrootable tablet.
This only use to be true before RazorClaw, NachoRoot and ViperMod was avaiable.
Back then you'll have to figure out if you have an SBK v1 or SBK v2 to use NVFlash.
baseballfanz said:
With all the methods out there, It's hard to believe you'll have an unrootable tablet.
This only use to be true before RazorClaw, NachoRoot and ViperMod was avaiable.
Back then you'll have to figure out if you have an SBK v1 or SBK v2 to use NVFlash.
Click to expand...
Click to collapse
Many thanks for the information!
My TF has an SBK v2 because the serial number starts with BB0. My TF was upgraded to stock ICS downloaded from the Asus website (US build version US_epad-9.xx....). My questions:
1) Could you recommend a rooting approach about my situation? How can I check whether the TF is rooted or not?
2) If I flash the full version of ICS using Plan B of ICS - CWM flashable here (http://forum.xda-developers.com/showthread.php?t=1514658), my TF will be rooted, correct?
3) To be able to flash using Plan B, is the following the appropriate CWM I need to install first (note: my TF is not rooted yet)?
http://forum.xda-developers.com/show....php?t=1093818
Sorry for these basic questions. I've never done any tablet flashing before. Really appreciate any guide and pointers.
mj56gt said:
Many thanks for the information!
My TF has an SBK v2 because the serial number starts with BB0. My TF was upgraded to stock ICS downloaded from the Asus website (US build version US_epad-9.xx....). My questions:
1) Could you recommend a rooting approach about my situation? How can I check whether the TF is rooted or not?
2) If I flash the full version of ICS using Plan B of ICS - CWM flashable here (http://forum.xda-developers.com/showthread.php?t=1514658), my TF will be rooted, correct?
3) To be able to flash using Plan B, is the following the appropriate CWM I need to install first (note: my TF is not rooted yet)?
http://forum.xda-developers.com/show....php?t=1093818
Sorry for these basic questions. I've never done any tablet flashing before. Really appreciate any guide and pointers.
Click to expand...
Click to collapse
You have to be rooted first. Being rooted allows you to install CWM. CWM enables you to flash ROMs.
(NvFlash lets you flash roms without rooting and without CWM, but it doesn't work with sbk2 so you can forget about it.)
1) You root with this http://forum.xda-developers.com/showthread.php?t=1516639 Make sure you read the post completely. The option you need to use for TF101 ICS is OPTION 1.
2) Supposedly the root kit also flashes CWM to your TF at the same time but people are reporting it doesn't work. In that case, use http://forum.xda-developers.com/showthread.php?t=1346180 confirmed to work on TF101 ICS rooted with vipermod.
3) Now you have rooted ICS with CWM. Read up on CWM and how to flash ROMs if you want to.
horndroid said:
You have to be rooted first. Being rooted allows you to install CWM. CWM enables you to flash ROMs.
(NvFlash lets you flash roms without rooting and without CWM, but it doesn't work with sbk2 so you can forget about it.)
1) You root with this http://forum.xda-developers.com/showthread.php?t=1516639 Make sure you read the post completely. The option you need to use for TF101 ICS is OPTION 1.
2) Supposedly the root kit also flashes CWM to your TF at the same time but people are reporting it doesn't work. In that case, use http://forum.xda-developers.com/showthread.php?t=1346180 confirmed to work on TF101 ICS rooted with vipermod.
3) Now you have rooted ICS with CWM. Read up on CWM and how to flash ROMs if you want to.
Click to expand...
Click to collapse
I really appreciate your kind help, horndroid! I'll try out your suggestion soon. Thanks again...
I have my tablet still on ICS, locked, all stock ROM, except I used a root exploit for ICS to have root.
What I would like to know; what is the best method for me to be able to happily try out different ROM's without fluffing up and bricking my tablet?
I know I need to unlock, install customer recovery. Is NVFlash backup necessary?
I've also got a HTC Desire HD which I've flashed with many ROM's without ever running into issues.
The Asus TF300 seems different and I've seen too many posts where people have bricked their devices.
Is it true that flashing a ROM designed for one version of the bootloader, on a device with a different version will brick your device?
Also it is true that certain wipes from recovery brick your device?
psjw12 said:
Is it true that flashing a ROM designed for one version of the bootloader, on a device with a different version will brick your device?
Also it is true that certain wipes from recovery brick your device?
Click to expand...
Click to collapse
Yes flashing a rom on a 4.2 bootloader that was made to work on a 4.1 bootloader will most likley cause a bootloop or a softbrick but should be able to be recovered in most cases.
The main cause of bricked devices atm is flashing the incorrect recovery for your bootloader version. This is flashing a non-4.2 recovery on a 4.2 bootloader, causes a fastboot flash brick - more info on this in my how-to in sig below.
I'm not sure about bricking your devices using wipes in recovery but the wipe data option in the bootloader menu will in most cases brick the device.
Not sure what the best method is but I pefer using the fastboot method over the twrp method but it's up to you, however the fastboot method does seem to work even with a locked device (but try at own risk).
It's up to if you want to do the NVFlash backup, it is suposed to be a fail safe in case of brick, although this does seem to depend on how the device was bricked. ie does not seem to work with the fastboot flash brick.
If you need more info or would like a step-by-step on how to unlock and upgrade for your situation just let me know.
pjc21 said:
It's up to if you want to do the NVFlash backup, it is suposed to be a fail safe in case of brick, although this does seem to depend on how the device was bricked. ie does not seem to work with the fastboot flash brick.
Click to expand...
Click to collapse
How is a fastboot flash brick caused?
pjc21 said:
If you need more info or would like a step-by-step on how to unlock and upgrade for your situation just let me know.
Click to expand...
Click to collapse
Thank you. I understand what to do but I don't feel confident. I've been happy flashing my HTC Desire HD for a long time and never had issues but I've seen so many bad stories on these forums it's really making me uncomfortable. I really want to go ahead and flash my device as it's slow and keeps crashing, and I want to be able to flash different ROM's without breaking a sweat. But I'd rather have a slow crashing device than a bricked one.
pjc21 said:
ie does not seem to work with the fastboot flash brick.
Click to expand...
Click to collapse
Sources? I've never seen anyone with NVFlash even say they experienced any bricks. I don't see why it wouldn't be recoverable. As far as I've seen, everyone who succumbed to the "4.1 recovery on 4.2 bootloader" brick had no NVFlash backups. Unless you're talking about a different brick, in which case you lost me. NVFlash should work just fine with any brick. Unless you brick it while restoring your NVFlash backups, in which case, you're boned.
EndlessDissent said:
Sources? I've never seen anyone with NVFlash even say they experienced any bricks. I don't see why it wouldn't be recoverable. As far as I've seen, everyone who succumbed to the "4.1 recovery on 4.2 bootloader" brick had no NVFlash backups. Unless you're talking about a different brick, in which case you lost me. NVFlash should work just fine with any brick. Unless you brick it while restoring your NVFlash backups, in which case, you're boned.
Click to expand...
Click to collapse
No sources, I was just going off a few comments in this thread but they don't state weather they did actually have nvflash backup or not, just that there was no fixing with nvflash.
I agree with you that as long as you can boot to apx and have nvflash backup and don't brick during nvflash restore then you should be able to unbrick from any brick.
Sorry for any confusion here.
pjc21 said:
No sources, I was just going off a few comments in this thread but they don't state weather they did actually have nvflash backup or not, just that there was no fixing with nvflash.
Click to expand...
Click to collapse
Where? I went through the thread backwards from the last page back to page 7 or 8. Only one person even mentioned NVFlash, and he was asking if he could use NVFlash backups from a different tablet because he didn't have any of his own (that's not possible because of the way the bootloaders are signed). I also didn't see anyone actually tell him it wasn't possible. He was the third to last post in the thread.
So nobody in that thread (after page 7, anyway) said anything about NVFlash let alone that it doesn't work. NVFlash should work just fine to fix the fastboot bricks, just like any other brick.
Edit: So one other guy in a random post just kind of said NVFlash wouldn't work, nothing else - no details at all. A couple people asked him for details and proof, but he never replied. I have a feeling he meant NVFlash couldn't help because he didn't have any backups. If you have the NVFlash backups, you can recover from pretty much any brick.
Thank you guys for your help.
So does the following plan sound safe to you?
1. Backup my device (apps, data and sdcard)
2. Unlock with Asus unlock tool (v7 right?)
3. Do NVFlash Backup
4. Do official ASUS upgrade to JB 4.1 (I would do this by extracting the download from their site onto my SD card right? Because once unlocked I won't get offered any updates)
5. Once on JB, flash the correct 4.1 TWRP onto my recovery via Fastboot
6. Get Flash happy with my 4.1 compatible ROM's, do a few data wipes in between.
Sounds good to me. As long as you check version numbers and filenames carefully, there shouldn't be a problem.
What about on an Unlocked device
Back in March when Jelly Bean 4.2 came out I went from a rooted and unlocked machine to the newest stock os (10.6.1.8) I am looking to upgrade to the official 10.6.1.15.3 that is available on the ASUS site. Is it as simple as downloading the ASUS updateLauncher and putting it on my sd card and running it from the tablet? Or am I at risk being on an unlocked device, do I need to add any other steps?
teedoe said:
Back in March when Jelly Bean 4.2 came out I went from a rooted and unlocked machine to the newest stock os (10.6.1.8) I am looking to upgrade to the official 10.6.1.15.3 that is available on the ASUS site. Is it as simple as downloading the ASUS updateLauncher and putting it on my sd card and running it from the tablet? Or am I at risk being on an unlocked device, do I need to add any other steps?
Click to expand...
Click to collapse
From what I know you should be able to upgrade from stock version to a newer stock version without any issues. The only thing I'm not sure about is if that method will wipe all your data. I'd advise a backup first.
psjw12 said:
From what I know you should be able to upgrade from stock version to a newer stock version without any issues. The only thing I'm not sure about is if that method will wipe all your data. I'd advise a backup first.
Click to expand...
Click to collapse
Well now I am stuck, here is what I tried without success.
Backed up my data
Downloaded the newest file from ASUS - 10.6.1.15
Placed file on my internal SD
Renamed it to US_epad-user-10.6.1.15.3.zip
System Update is detected so I tried to run it from the OS - but it fails, gives me a Unknown Error (2) and restores itself to previous. I tried it twice with no luck.
Any idea how I can get this file to update.
Thanks,
teedoe said:
Well now I am stuck, here is what I tried without success.
Backed up my data
Downloaded the newest file from ASUS - 10.6.1.15
Placed file on my internal SD
Renamed it to US_epad-user-10.6.1.15.3.zip
System Update is detected so I tried to run it from the OS - but it fails, gives me a Unknown Error (2) and restores itself to previous. I tried it twice with no luck.
Any idea how I can get this file to update.
Thanks,
Click to expand...
Click to collapse
Did you remove any apps or system files? If your ROM isn't 100% exactly stock before the update, the update will fail.
It was a simple mistake, I just needed to extract the zip file I downloaded from ASUS one time and then transfer it to my SD card. Worked perfectly after that and I did not lose any data or apps.
Thanks to all on the forums for your advice and help!