Can someone please tell me how to go back from .13 to .9 so I can root my TF please? So far I haven't found anything telling me how, just telling me it can be done. I got the old OFW from asus's website and moved it to the root of my SD card and tried a reload but still keeps loading .13 after the wipe.
So can someone tell me how or what I am doing wrong?
Just extract the contents of the .9 OFW into the root of your MicroSD, pop it in the Transformer and it should prompt you to update.
Sent from my Transformer TF101
frosty5689 said:
Just extract the contents of the .9 OFW into the root of your MicroSD, pop it in the Transformer and it should prompt you to update.
Sent from my Transformer TF101
Click to expand...
Click to collapse
Ah cool, just open the zip and let me make the asus/update/... folders on the SD card and it will grab that one. Thanks.
Thank you, I felt so stupid and now it worked just fine.
I also want to downgrade from ICS back to Honeycomp.
Can i do that without root ? - just like an update -
And where can I download the de Version- on the asus webside is only theDE 4.0.3 version.
Kind regads
gandalf
1234556789 said:
I also want to downgrade from ICS back to Honeycomp.
Can i do that without root ? - just like an update -
And where can I download the de Version- on the asus webside is only theDE 4.0.3 version.
Kind regads
gandalf
Click to expand...
Click to collapse
I don't think you can go backward on a non root tf
baseballfanz said:
I don't think you can go backward on a non root tf
Click to expand...
Click to collapse
-Ok and with root-? What programs do i need and where do i find the original honeycomprom?
kind regards
gandalf
1234556789 said:
-Ok and with root-? What programs do i need and where do i find the original honeycomprom?
kind regards
gandalf
Click to expand...
Click to collapse
Would you consider giving the revolver ROM a try? I downgraded from 1.3.1 beta(ICS) to 3.11(HC).
I am fairly certain Asus like most device manufacturers try to keep you from being able to downgrade from official OEM versions of software back to older versions- the reason being, of course, that the newer versions sometimes fix software and security vulnerabilities (like 8.6.5.21 losing the ability to use an APK file to root, like razorclaw, and imagine a rogue application exploiting this vulnerability, achieving root, and broadcasting to the developer any information without notifying you about it..). The interesting thing is that the method of denying firmware 'updates' to downgrade seems to be arithmetically calculated from the version numbers, basically if update package version is < current version update will be denied. However, when they decided to engineer the update denial this way, it left it's own vulnerability, in that firmwares for the TF101G, being the later model of the TF101, automatically have a higher firmware version because of the 3rd digit is a 6 instead of a 5, indicating that the version is for TF101G. This left the old honeycomb ROMs with this vulnerability- if you had updated to 8.6.5.21, you were still able to 'update' to an older firmware the device viewed as 'newer' than the current device firmware, i.e. 8.6.5.21 users could update from a stock device to downgrade their firmware using the TF101G firmware 8.6.6.19, which could still be rooted with the APK vulnerability.
Now that we have moved onto ICS and there is not yet a TF101G version of ICS available, we lack this native downgrade option, and we are yet to see if Asus is going to fix this 'vulnerability' by simply amending the TF101G and TF101 version numbers, or by altering the way in which the OEM recovery mode accepts or rejects Asus update packages, I have the feeling that they already have with the 9.2.1.11 update recovery that was included.
All of the precursor information I just listed brings me to the only current method known to rollback your firmware if you are on ICS, either 9.2.1.17 or 9.2.1.11..you must root your device with ViperMOD, install CWM via RecoveryInstaller, and use CWM to manually install the firmware to a previous version. This will perhaps add a few layers of complexity..you may have to toggle signature verification and script asserts enabled (I am making a wild guess on this one, I've not yet tried to downgrade just yet), and you will be persistently bothered by Asus update notifications (there are plenty of threads describing how to rid yourself of these). My guess is that soon Asus will begin pulling the HC ROMs from their official website so you might want to grab that ASAP. And if you want to keep from getting bothered by update notifications yet stay stock 100%, you can (until they release the ICS for it) flash the TF101G version of the firmware, 8.6.6.21.
IN SUMMARY; to downgrade ICS to HC, you will have to root and flash recovery modes. There doesn't seem to be a way around it. And IMO it's probably best to NVFlash back to HC, no telling what kind of data will be left that will conflict with HC from ICS if you do simply flash a HC ROM via CWM. You will probably want to make sure you have the right kernel just in case you have to flash it as well..I can imagine a nightmare scenario if the Asus update didn't include a kernel that it leaves your ICS kernel intact, which will not load HC, and also flashes over your recovery, leaving you pretty much bricked without NVFlash. Fairly sure Asus update contain the full ROM- kernel included, but I always err on the side of caution..I'd flash the HC kernel first personally..just to be safe. If nightmare scenario does occur, you can't flash it after you reboot.
Rani El-Maalouf said:
Would you consider giving the revolver ROM a try? I downgraded from 1.3.1 beta(ICS) to 3.11(HC).
Click to expand...
Click to collapse
I had the revolver rom before- with my last transformer.- But ICS - if working, -is better.- and best seems to me: revolver rom ics based on a (good working !!) stockrom.
Meanwhile i rooted the transformer and install CWM - tried stockrom flashing with CWM- but because of usb is not working+ random reeboots, i changed to revolver ics- Revolver ics had a working usb connection (also random reboots- - and today a freeze while booting) .
I trie to find out the reason for the reboots.
I only go back to HC if there are too much problems with this rom - by i had to trie out first.
To luna_c666
---sorry.... need time + dictonary forall that. - but seems to me a good answer.
kind regards
gandalf
Related
I've successfully recovered my tablet using this method. I was trying to update my TF using the batch script method and somehow managed to flash an outdated kernel. I know this because Asus tech support told me that was the reason my TF wasn't receiving the ota to 3.2. However, Asus tech support also told me that I could flash a new kernel by downloading the source code onto my tablet, then the TF would automatically recognize the [.rar] file and install my new kernel; which didn't work out as you might imagine.
I am now on official 3.1 8.4.4.11.and my kernel is v 2.6.36.3-00011-g3eb19ex And I can't get the OTA update. At one time I had official 3.2 [after previously flashing stock 3.1] but decided to try to root when I found out Netflix wasn't officially supported like the EEE pad site says it does.
Every time I try the batch script method, I end up stuck on the eee pad logo screen. Adb is working as well as apx drivers. Ultimate goal here is stock 3.2 rooted with netflix, but at this point I'd settle for stock official 3.2.
Any ideas? Tia
You may get help if you post your QUESTIONS in the correct forum.
This is the development forum....not Q&A.
Sent from my Jailbroken iPhone 4 using Tapatalk.
Thanks for the input. I just felt that that based on the content of the question, it would be better suited here.
you could try the zip file from the thread titled [OTA]Stock 3.2 zip file
And +1 on wrong section. This is not related to developing a new ROM or features for the Eee Pad.
I'm trying to avoid flashing CWM, that's where I end up bricking it.
jdmnash said:
I'm trying to avoid flashing CWM, that's where I end up bricking it.
Click to expand...
Click to collapse
I would suggest you to try Nvflash. it is the easiest way to root that tf.
I think the relationship between nvflash and the TF is complicated.
There are a few bootloaders out there, including the one used by custom roms, as well as the 4 stock ones.
My theory is that the kernel images in the boot and recovery images have to match the bootloader that is on the TF.
Throw in the fact that the bootloader is only written using the nvflash --create command or during the OTA update, and we have TFs with all kinds of different bootloaders going around that won't match what people are flashing. I think this is why CWM breaks whenever there is a stock OTA that rewrites the bootloader. I think most people brick trying to go back to stock from a custom rom. Going from stock to custom usually isn't a problem because the compatible bootloader is flashed in the rooting process.
Is this the first time we've seen an completely unlocked bootloader on Android?
sent from my cyanogen(mod) vision
jdmnash said:
Thanks for the input. I just felt that that based on the content of the question, it would be better suited here.
Click to expand...
Click to collapse
No. Android Development is for "DEVELOPMENT" does this thread have any kind of release? No.
That's why there's a sticky thread that says,
[REF] SEARCH BEFORE POSTING!! All Questions Go In The Q&A FORUM!!
Originally Posted By: mskip
Click to expand...
Click to collapse
ok folks i get it. I'm sorry. Is there anything I can do right now about accidently posting this in the wrong forum? Please forgive me. Mods feel free to move the thread or ban me or both. Whatever the normal punishment is.
Use the NVFlash unroot method here:
http://tabletroms.com/forums/showthread.php?1071-Asus-Transformer-NVFlash-Stock-3.1-Recovery-Roms
That will get it back to stock everything with 8.4.4.5. Then, you can manually install 8.4.4.11 with the download on the Asus website. After that it will recognize the OTA update to 8.6.5.6. Once you've done all that, use the Batch Script for a quick root, and you're done. I did this today. As long as you follow all the steps, it's a breeze.
I don't think it will recognize the OTA update to 8656. Roach's update will work, but not the stock update.
sent from my cyanogen(mod) vision
It will recognize it, because if you follow all the steps I listed, you're completely stock until you run the batch script to root 3.2. I did this myself on my transformer today.
My OP is not very clear, but that is exactly the steps I've followed to get to where I am today. I've given it 2 days to detect the new update and i've got nothing. I'm currently sitting on stock 8.4.4.11 waiting for the OTA.
kingwp1 said:
It will recognize it, because if you follow all the steps I listed, you're completely stock until you run the batch script to root 3.2. I did this myself on my transformer today.
Click to expand...
Click to collapse
How did you root before and what were you running before you went back to stock 8445?
sent from my cyanogen(mod) vision
stock 3.2. I was trying to get rooted 3.2 to get netflix
jdmnash said:
stock 3.2. I was trying to get rooted 3.2 to get netflix
Click to expand...
Click to collapse
Did you ever make a backup with CWM when you had 3.2?
no it was stock 3.2 firmware/recovery
I'm making progress. I'm now on rooted 8.4.4.11... still trying to get to 3.2
I own an EEE PAD Transformer TF101 and its got the 8.6.5.21(WW) firmware and I rooted it via Nachoroot and have installed CWM to be able to make full system backups/restores.
Now in the one hand I'm elated a new Android version called ICS is coming soon but have a couple of 'fears' and questions.
-Will the Tegra2 inside the TF101 run ICS just as smooth as Honeycomb ?
-I want to choose the moment ICS gets updated myself and I hate being forced by OTA but am I right that with Nachoroot and CWM installed it won't work anyways so no fears for that ?
-In that case I still keep getting OTA notifications I guess. Is here a tool to switch that off ?
Would it be wise to use OTA Keeper to backup my root or has OTA Keeper got any drawbacks ?
I bet ICS will at first not be rootable anyways right ?
maicod said:
I own an EEE PAD Transformer TF101 and its got the 8.6.5.21(WW) firmware and I rooted it via Nachoroot and have installed CWM to be able to make full system backups/restores.
Now in the one hand I'm elated a new Android version called ICS is coming soon but have a couple of 'fears' and questions.
-Will the Tegra2 inside the TF101 run ICS just as smooth as Honeycomb ?
-I want to choose the moment ICS gets updated myself and I hate being forced by OTA but am I right that with Nachoroot and CWM installed it won't work anyways so no fears for that ?
-In that case I still keep getting OTA notifications I guess. Is here a tool to switch that off ?
Would it be wise to use OTA Keeper to backup my root or has OTA Keeper got any drawbacks ?
I bet ICS will at first not be rootable anyways right ?
Click to expand...
Click to collapse
Correct. A rooted device most likely will have OTA disabled. To confirm, just go into Settings -> About Tablet and if you see a Check for System Update link, then OTA is probably still enabled. You may have to put a rebuilt Rom like Krakd or Prime 2.11 to have OTA disabled.
I think that Root will come fairly quickly for ICS considering the Source has been released for a long while. So the guys who look for those root exploits probably already have a nice stash lined up for when devices receive their updates.
Tegra 2 is plenty powerful enough to run ICS, that combined with the amount of Ram you shouldn't be to worried about that.
If you want...hop over to the Development threads and grab the latest ICS port from Paul Burton. That way you can check it out and see how you feel about ICS. Note: Paul's build are still considered early and some things may not work as you want, but that doesn't mean they won't work at all once Asus pushes out the official build or when Paul finishes up his port.
if you do flash paul's ROM please ask any questions in this thread HERE, and not in the dev thread. Also, be sure to read everything before flashing. It isn't quite complete and you will want to go back to HC after you flash.
gVibeR said:
Correct. A rooted device most likely will have OTA disabled. To confirm, just go into Settings -> About Tablet and if you see a Check for System Update link, then OTA is probably still enabled.
Click to expand...
Click to collapse
I checked and the update link still works and I'm sure I will still get OTA notifications
One good thing is that I noticed that since the RESCUE partition is replaced with CWM that OTA will fail when it reboots into rescue mode to install the update.
I am not keen on installing these ROMS that you mentioned since I don't know what is removed etc. compared to the original roms.
I was thinking this:
since I have root access isn't there a way to remove the OTA update service from starting up by using "terminal emulator" from the Android Market and edit the config file or directory where the OTA update notification service gets started ? Anyone knows if this is possible and how ?
I moved /system/UpdateLauncher.apk and Updatelauncher.odex into another map but that didn't stop the notifications and renaming ota.certs isnt wise since the new firmware update file will keep downloading again and again.
gVibeR said:
I think that Root will come fairly quickly for ICS considering the Source has been released for a long while. So the guys who look for those root exploits probably already have a nice stash lined up for when devices receive their updates.
Tegra 2 is plenty powerful enough to run ICS, that combined with the amount of Ram you shouldn't be to worried about that.
Click to expand...
Click to collapse
okay cool !
Thanks for the Paul Burton tip but I think I just wait until ICS comes available. I bet it won't take long anymore.
maicod said:
I checked and the update link still works and I'm sure I will still get OTA notifications
One good thing is that I noticed that since the RESCUE partition is replaced with CWM that OTA will fail when it reboots into rescue mode to install the update.
I am not keen on installing these ROMS that you mentioned since I don't know what is removed etc. compared to the original roms.
I was thinking this:
since I have root access isn't there a way to remove the OTA update service from starting up by using "terminal emulator" from the Android Market and edit the config file or directory where the OTA update notification service gets started ? Anyone knows if this is possible and how ?
I moved /system/UpdateLauncher.apk and Updatelauncher.odex into another map but that didn't stop the notifications and renaming ota.certs isnt wise since the new firmware update file will keep downloading again and again.
okay cool !
Thanks for the Paul Burton tip but I think I just wait until ICS comes available. I bet it won't take long anymore.
Click to expand...
Click to collapse
Dont screw with the system its just not good news!!!!!!
If you have cwm recovery ota will check and you will know when ics arrives but it wont install because of the custom recovery not because of root as stated above.
Sent from my Transformer TF101 using xda premium
If you don't want to get the update at all, freeze or disable DMClient app.
Can anyone tell me how to downgrade back to Honeycomb or point me to the enigmatically-named forum post?
I'm running stock 4.0.3, kernel 2.6.39.4.
Please don't hang me if this is already on here somewhere. I did search, but all I found was version numbers and frankly, a lot of stuff I didn't understand.
From the Moderator: Doing a proper search will yield the right results. To find in a search you need to take your original query and then rearrange the word order sometimes to find. oka1
I recently did the OTA update to ICS. Since then I have had power drain, random reboot, and problems connecting to Wi-Fi.
Any help would be greatly appreciated.
Being you're on stock ROM, the only way is if your tf is nvflash compatible.
Serial # B60 or previous (some B70)
B50
My serial starts with B50, so I guess I'm at least in a good starting place.
Loremonger said:
My serial starts with B50, so I guess I'm at least in a good starting place.
Click to expand...
Click to collapse
Yes the B50 certainly is NVFlash compatible.
Here are a lot of NVFlash ROM, I don't see the latest HC (.21) ROM but try searching here or Google.
http://www.tabletroms.com/forums/tr...stock-3-2-recovery-roms-unbricking-tools.html
or it might update itself in stage up to .21 (not 100% sure on this)
Thank you, baseballfanz, that at least gives me a starting point.
From the Moderator: Doing a proper search will yield the right results. To find in a search you need to take your original query and then rearrange the word order sometimes to find. oka1
Click to expand...
Click to collapse
Well, at least I didn't post in the developer's forum. Anyway, it doesn't matter how much you manipulate the search, it won't yield results that aren't on this forum.
What abt 101G S\N B90 running ICS 9.2.2.3 ? How to downgrade to HC ?
Note: Don't have root and can't root
hearts king101 said:
What abt 101G S\N B90 running ICS 9.2.2.3 ? How to downgrade to HC ?
Note: Don't have root and can't root
Click to expand...
Click to collapse
Sorry, dude. But from what I found out today, it looks like anything above B70 is "in the works." Something should be out soon, but for now, it looks like you're stuck. I would check this post regularly to see if an update is available for later models.
I did that yesterday hoping that with a clean stock installation would fix problems (and it's working great until now, but as all we know problems come in a random way with ics).
So, I found on the net an nvflash 8.6.5.13 ww rom (full with bootloader, kernel and recovery).
Backup all your stuff first.
I booted into cwm, complete wipe, including /data/media.
Put tf in apx mode, nvflash complete rom, boot it.
After then I configured wifi and a notification about updates appeared. I did that and my tf was upgraded to 8.6.5.21 ww.
Then you can use that, flash cwm with nvflash, flash any honeycomb rom.
Instead I upgraded it with stock 9.2.1.17 ww rom (using official upgrade notification), because I want to see if it works correctly for me (100% stock without root, 9.2.1.17 is not rootable without flashing over a modified rom or with ota rootkeeper)..
Only time will tell if problems are gone for me on ics...
Does anyone know where I might be able to find the latest of the Honeycomb updates? I've got the 8.6.5.13 NVFlash, but I've been searching and haven't been able to find any of the 'Official' updates. It doesn't help that searching XDA for '8.6.5.19' actually searches for '8 6 5 19'. I believe the latest is either 8.6.6.21 or 8.6.5.21? If someone could point me in the direction of the latest (or two latest) oficcial Asus Honeycomb updates, I'd appreciate it.
Hi Subnetmask (255.255.255.0)
Why dont you just use ota from asus? are is your TF rooted and CWM installed?
Otherwise use gnufabio's recovery installer app to install cwm so you can upgrade.
or use nvflash to install ICS????
It looks like he wants to downgrade, or only upgrade to the latest HC and avoid ICS. I'd link you to the download from asus on their site, but of course it's down -_-
When the site is back up it should be on there. If not search for 8.6.6.21 stock rooted tf101 or along those lines.
Thing O Doom said:
It looks like he wants to downgrade, or only upgrade to the latest HC and avoid ICS. I'd link you to the download from asus on their site, but of course it's down -_-
When the site is back up it should be on there. If not search for 8.6.6.21 stock rooted tf101 or along those lines.
Click to expand...
Click to collapse
That's exactly it. I downgraded to 8.6.5.13, but don't want to upgrade it to ICS again just yet... SInce I downgraded it to 8.6.5.13 it hasn't shut down on its own again yet (Big surprise...).
I looked on Asus' web site, and unless there's another section I couldn't find, the only non-ICS download is 8.6.5.13 for the 'CN' SKU. I've searched around Google and unless I"m missing something (always possible) nothing useful has come up yet. Searching here is kinda useless because '8.6.5.13' gets searched as '8 6 5 13' so pretty much any thread with an 8, a 6, a 5 or a 13 gets displayed :/.
I have a copy of Stock 8.6.5.21 (latest HC). I can post it up once I get to my PC.
Probably be a couple of hours.
baseballfanz said:
I have a copy of Stock 8.6.5.21 (latest HC). I can post it up once I get to my PC.
Probably be a couple of hours.
Click to expand...
Click to collapse
That would be awesone. No rush, whenever you have a chance .
Here you go,
http://www.4shared.com/zip/ht-SmZQE/UpdateLauncher_US_epaduser8_6_.html
Awesome. Thanks!
Anyone have 8.6.5.19? I don't know why I'm having so much trouble, but I can't get my TF101 to re-root for the life of me. I've tried on the bare 8.6.5.13 & with 8.6.5.21, with ViperMod, NachoRoot and Razorclaw. .13 is too old and .21 is too new for Razorclaw, Nachroot by it's self didn't seem to work right, and Vipermod, using option 3 didn't seem to work either. The problem with ViperMod was when it came back saying UID should be '0', it was always '2000'. If I cna get .19, I should be able to use Razorclaw, then rootkeeper, and update to .21. Then I just need to make the Asus update prompts go away...
SubnetMask said:
Anyone have 8.6.5.19? I don't know why I'm having so much trouble, but I can't get my TF101 to re-root for the life of me. I've tried on the bare 8.6.5.13 & with 8.6.5.21, with ViperMod, NachoRoot and Razorclaw. .13 is too old and .21 is too new for Razorclaw, Nachroot by it's self didn't seem to work right, and Vipermod, using option 3 didn't seem to work either. The problem with ViperMod was when it came back saying UID should be '0', it was always '2000'. If I cna get .19, I should be able to use Razorclaw, then rootkeeper, and update to .21. Then I just need to make the Asus update prompts go away...
Click to expand...
Click to collapse
I have not seen any 8.6.5.19 (Asus pulled it pretty quick after RazorClaw)
There's a 8.6.6.19 you can use (It's for the TF101G but work on the TF101)
http://forum.xda-developers.com/showthread.php?t=1417006&
baseballfanz said:
I have not seen any 8.6.5.19 (Asus pulled it pretty quick after RazorClaw)
There's a 8.6.6.19 you can use (It's for the TF101G but work on the TF101)
http://forum.xda-developers.com/showthread.php?t=1417006&
Click to expand...
Click to collapse
I saw that thread. The file appears to be for 'WW' SKUs, and MultiUpload appears to not be working. The other problem is if I could DL it, I doube I'd be able to apply 8.6.5.21 once rooted.
Don't know why I'm having so much trouble rooting the thing... I've done it after every release since I got it. I must've just gone stoopid lol. Searching for root give ICS information overload.
SubnetMask said:
I saw that thread. The file appears to be for 'WW' SKUs, and MultiUpload appears to not be working. The other problem is if I could DL it, I doube I'd be able to apply 8.6.5.21 once rooted.
Don't know why I'm having so much trouble rooting the thing... I've done it after every release since I got it. I must've just gone stoopid lol. Searching for root give ICS information overload.
Click to expand...
Click to collapse
This link still work.
http://forum.xda-developers.com/showpost.php?p=21729271&postcount=250
It doesn't matter if it's WW or not. your goal is to get root and after which you can flash the correct version for your region.
If it work and you get root, use OTA Root Keeper to save your root, upgrade to 8.6.5.21 and restore root. Worth a try
Finally got it rooted... After about an hour of searching, I found the method that I had originally used (the 'One Click' root found here). I installed OTA Root keeper, but that didn't work on my upgrade to .21 from .9. I ended up having to re-root, but since the 'One-Click' worked, it wasn't too painful. Using linix to root it is so obscure (to me) I totally forgot about it.
Still, if someone happens to have the 8.6.5.19 update file (Call me wierd, but I'd rather have/use the proper file for my unit rather than the one for the TF101g even though it may work fine), it would be great to get that to add to my 'collection'.
Before anybody says to use the search function, I've been looking through the general topics non-stop for one that applies to my situation, and either it slipped through the cracks (likely) or it doesn't exist (not likely).
Basically, my tablet is rooted and unlocked, and I'm on ICS; the first one that had face unlock in it. I'd really like to update my tab to JB, but I need to be pointed toward directions for updating a rooted and unlocked tab. But on top of that, I also need recent instructions, because I know that earlier attempts at getting this thing updated have resulted in lots of bricked tabs.
If anybody could tell me if it's possible to update my tablet to JB right now, I'd appreciate it, and if someone has figured out how to do it, can you please point me toward that thread? I'd really appreciate it.
-Tim
I'm in the same configuration, custom-ics-rom with twrp recovery on unlocked device.
I believe the first thing to do is enabling NVFLASH, that will make things safer also in the worst cases.
I did that and now hopefully I have an unbrickable device.
I'm a bit confused on how to go forward, I know that there are two versions of twrp, maybe I should install the JB version, booting inside it and then flash the downloaded JB update from ASUS site, or use the twrp for ICS for flashing and after that install the JB version ?
Anyone knows what is the correct option ?
Giuseppe
Tim 13 said:
Before anybody says to use the search function, I've been looking through the general topics non-stop for one that applies to my situation, and either it slipped through the cracks (likely) or it doesn't exist (not likely).
Basically, my tablet is rooted and unlocked, and I'm on ICS; the first one that had face unlock in it. I'd really like to update my tab to JB, but I need to be pointed toward directions for updating a rooted and unlocked tab. But on top of that, I also need recent instructions, because I know that earlier attempts at getting this thing updated have resulted in lots of bricked tabs.
If anybody could tell me if it's possible to update my tablet to JB right now, I'd appreciate it, and if someone has figured out how to do it, can you please point me toward that thread? I'd really appreciate it.
-Tim
Click to expand...
Click to collapse
Keep ICS, as JB will cause much trouble especially if you are rooted, trying to OC and is generally slowein my opinion
I prefer to try it anyway, tomorrow I will try flashing, after all if something will go wrong I should be able to recover with nvflash.
[
QUOTE=grimsonfart;32974661]Keep ICS, as JB will cause much trouble especially if you are rooted, trying to OC and is generally slowein my opinion[/QUOTE]
Thank you, Grim. That's disappointing to hear about JB, but if you think that my current build is better than that (which makes sense considering I've seen at least one thread about downgrading from JB to ICS), then I will keep my tab on ICS for now, and thank you for your input, I appreciate it.
-Tim
If you have twrp recovery, can't you download the jb ROM from the Asus site for your region and flash it in? I'm unlocked and that's how I upgraded one version of jb to another, but my ICS to jb was ota, so in your case I can't speak from experience. There is a full upgrade, and root guide in the general section.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
I just managed to do what you re looking to achieve.
I m pretty noob so it tok me a whole day to figure it out.
So first download jb update on asus website (pick the right one for ur type of tf300)
Flash it through adb
At that point i got jb installation working but bootloop
So i flashed jb version of twrp (adb)
I then went in recovery and flashed clean rom 2.5 which worked flawlessly
Just for the fun i did factory reset afetrwards and stock jb eventually launched right
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
gst0098 said:
I'm in the same configuration, custom-ics-rom with twrp recovery on unlocked device.
I believe the first thing to do is enabling NVFLASH, that will make things safer also in the worst cases.
I did that and now hopefully I have an unbrickable device.
I'm a bit confused on how to go forward, I know that there are two versions of twrp, maybe I should install the JB version, booting inside it and then flash the downloaded JB update from ASUS site, or use the twrp for ICS for flashing and after that install the JB version ?
Anyone knows what is the correct option ?
Giuseppe
Click to expand...
Click to collapse
I successfully installed jb following the guide on this site, the only thing that was not working was the flashing of the stock rom, neither given options worked (fastboot flash recovery or fastboot flash system) , I discovered that our eepad has a partition nmed staging used for firmware installs. I then flashed with
fastboot flash staging blolb
and all went good.
Btw I find the JB better than ics, more responsive and smoother, and also if it is not yet overcooked.