Currently my TF300T is unlocked, rooted, ICS TWRP 2.3.1, nvflash blob files created (copies made and moved elsewhere) with AndroidRoot.mobi custom bootloader. I'm running stock ICS v9.4.3.17 and never ran any OTA's (one is downloaded/pending for install, but doesn't seem to do anything - likely because I'm unlocked?).
It's been recommended to just flash the JB bootloader & use a custom JB ROM rather than updating fully to JB (was said there are or had been, issues flashing the full JB from ASUS' website). With the nvflash blobs, I should be able to go back to ICS so I'd rather do a full update if possible. An earlier post [Q] Upgrade to JB bootloader from Unlocked ICS BL? asked the same but I need clarification on the answer (plus making sure - they were running ICS stock bootloader, not the custom from AndroidRoot like me):
mikaole said:
just fastboot TWRP for ICS and then flash the 1st JB StockRom(dl from Asus and unzip once) in TWRP.
Then fastboot TWRP for JB, then flash the latest JB StockRom(dl from Asus and unzip once) .
Then fastboot TWRP for JB and then the Rom you like
Click to expand...
Click to collapse
If reading right, in fastboot mode first flash ICS TWRP (I ignore as I already have it), then from TWRP install the 1st JB Stock ROM zip, reboot into fastboot mode, flash TWRP for JB (or should I use nvflash?), and lastly, reboot into TWRP and install the latest ASUS stock ROM zip (v10.4.2.18).
Figuring my steps are correct, what version from ASUS is considered the 1st ROM? Currently only v10.4.2.17 and v10.4.2.18 are available. Also wondering why the need to flash an earlier version of JB and then the most current? And lastly, have others in same situation done this successfully or encountered any issues I should be aware of?
I did this a short time ago to go from BB6 on ICS bootloaded to BB6 on JB. All I did was dropped back to stock ICS, upgraded TWRP, then drop the unzipped zip of the latest ASUS release. This got me stock JB on JB bootloaded. I then flashed the next BB6 version and went on my way.
The only painful part was that the post called for moving the blob to a specific folder and creating a command file. None of that worked for me. But leaving the unzipped zip file in the root of the SD card and rebooting worked flawlessly.
Good luck.
Sent from my Transformer Pad TF300T using Tapatalk HD
bsaman said:
I did this a short time ago to go from BB6 on ICS bootloaded to BB6 on JB. All I did was dropped back to stock ICS, upgraded TWRP, then drop the unzipped zip of the latest ASUS release. This got me stock JB on JB bootloaded. I then flashed the next BB6 version and went on my way.
The only painful part was that the post called for moving the blob to a specific folder and creating a command file. None of that worked for me. But leaving the unzipped zip file in the root of the SD card and rebooting worked flawlessly.
Good luck.
Sent from my Transformer Pad TF300T using Tapatalk HD
Click to expand...
Click to collapse
Thanks! So you were going from another set of instructions but ended up just flashed twrp-jb and installed the unzipped zip of Asus JB release via TWRP (I left out the revert to ICS part since I'm already there)? And do you have nvflash installed? No issue running the JB version of TWRP prior to upgrading to JB (had thought bootloader or ... would have an issue with it)? Would seem like order should be reversed, I may not be understanding it all fully!
Had come across various instructions but none seemed to fit being unlocked/rooted/nvflash/... and wasn't sure if would require different steps. Again thanks.
wha2do said:
Would seem like order should be reversed, I may not be understanding it all fully!
Had come across various instructions but none seemed to fit being unlocked/rooted/nvflash/... and wasn't sure if would require different steps. Again thanks.
Click to expand...
Click to collapse
I think you're right... I was on BB6 w/ICS bootloader (NVflashed, though I don't think it matters) and had to roll back to ASUS ICS ROM first, then rooted, then upgraded to ASUS JB ROM, and then it goes blurry. Not sure if I upgraded TWRP or rooted stock JB at this point.
In any case, I followed the "update to JB" thread to a tee, and all went well except for the step regarding the actual JB update.
Sent from my Transformer Pad TF300T using Tapatalk HD
wha2do said:
Currently my TF300T is unlocked, rooted, ICS TWRP 2.3.1, nvflash blob files created (copies made and moved elsewhere) with AndroidRoot.mobi custom bootloader. I'm running stock ICS v9.4.3.17 and never ran any OTA's (one is downloaded/pending for install, but doesn't seem to do anything - likely because I'm unlocked?).
It's been recommended to just flash the JB bootloader & use a custom JB ROM rather than updating fully to JB (was said there are or had been, issues flashing the full JB from ASUS' website). With the nvflash blobs, I should be able to go back to ICS so I'd rather do a full update if possible. An earlier post [Q] Upgrade to JB bootloader from Unlocked ICS BL? asked the same but I need clarification on the answer (plus making sure - they were running ICS stock bootloader, not the custom from AndroidRoot like me):
If reading right, in fastboot mode first flash ICS TWRP (I ignore as I already have it), then from TWRP install the 1st JB Stock ROM zip, reboot into fastboot mode, flash TWRP for JB (or should I use nvflash?), and lastly, reboot into TWRP and install the latest ASUS stock ROM zip (v10.4.2.18).
Figuring my steps are correct, what version from ASUS is considered the 1st ROM? Currently only v10.4.2.17 and v10.4.2.18 are available. Also wondering why the need to flash an earlier version of JB and then the most current? And lastly, have others in same situation done this successfully or encountered any issues I should be aware of?
Click to expand...
Click to collapse
First I want to address your possible OTA. Processing requires stock recovery on your tablet. Having Twrp or CWM means the update will not process.
When you flash a complete stock rom from fastboot, Twrp, or CWM you are flashing stock recovery as it is included in the blob.
Most versions of Asus firmware can be found here! Don't forget to look at the second post as It includes the ICS stuff and older JB.
The first version of JB was to my knowledge JB 10.4.2.9.
Sorry, I forgot why flash first version of JB.
It has been said that is when your internal sdcard was repartitioned for JB.
tobdaryl said:
First I want to address your possible OTA. Processing requires stock recovery on your tablet. Having Twrp or CWM means the update will not process.
When you flash a complete stock rom from fastboot, Twrp, or CWM you are flashing stock recovery as it is included in the blob.
Most versions of Asus firmware can be found here! Don't forget to look at the second post as It includes the ICS stuff and older JB.
The first version of JB was to my knowledge JB 10.4.2.9.
Sorry, I forgot why flash first version of JB.
It has been said that is when your internal sdcard was repartitioned for JB.
Click to expand...
Click to collapse
Thanks for the info. To add to your one comment (for others that may come across this looking for add'l info), flashing a full stock rom will overwrite any custom recovery previously in place. TWRP (using the appropriate version for your firmware) or CWM will need to be reflashed again...
Checking, it does appear v10.4.2.9 is the first version of JB on the TF300T.
I've come across at least one or more posts/guides that mention ICS v9.4.3.30 should be installed before updating to JB - one being: [GUIDE]Upgrade your TF300t to Jellybean, recovery, root & remove bloatware[Noobproof]. I'm wondering if it's because that method updates to JB using the dlpkgfile (not sure what format it is)?
My take is doing the additional flash to v9.4.3.30 first can't hurt anything, but quite possibly unnecessary here? Any other thoughts or words of warnings from anyone? Thanks!
Related
Hi there!
I'm a owner of a TF101 (B50) for month now, and recently I had the need to switch between multiple version of Android (as I'm an Android dev) : back and forth to/from Honeycomb from/to ICS for example, multiple time a day!
So, as I'm used to do with all my "Google's Experience" devices (Nexus S, Galaxy Nexus), I installed CWM on my TF101 to be able to generate nandroid. So far, so good.
I then downgraded my tablet to stock 3.2 using nvflash, installed CWM, and did a nandroid. Great, I now have an Honeycomb backup. Of course, at this point, I'm no more able to upgrade using OTA, so here's my first question :
1- Once CWM installed, how do you upgrade to the latest build ? Asus blobs are not compatible with CWM!
Then, since I needed an ICS nandroid, I reverted to stock 3.2 (using NVFLASH), and I let the OTA did the job for me - before installing CWM. Ok, now, I have both Honeycomb and ICS as backup : let's test that.
I rebooted in recovery, and then restored my 3.2 nandroid (from ICS, remember?). All I had once the job was done, was the android logo with an exclamation mark
After some Googling, I understood why : unlike my Google's devices, on the TF101, it seems CWM can't restore the boot partition. So, the bootloader used was the one for ICS, and the tablet failed to boot.... Here's my 2nd question :
2- Am I right? What guys are you suggesting to be able to switch easily between different nandroid versions ? Should I nvflash the boot partition by hand? If so, where to find a documentation on NVFLASH ? (I'm regretting fastboot )
Thanks for reading.
You can repackage the blobs so that they can be flashed from cwm. I think one roach's 3201 recovery is packaged this way, so you can take it apart to see how it all works. Essentially blobs are flashed through the staging partition. There is a blob tools thread in the dev section that has all the details.
If you want to go back and forth between roms, I think that nvflash will be your best bet. Rayman and bubble bee have the most info. Check out therenwebsite. It's something like androidroot.mobi? There is also a full backup and restore thread in the dev section that explains a lot of the details of nvflash.
sent from my transformer
I read, somewhere, that we can flash stock Asus firmwares using CWM ('update zip') by first extracting the initial zip (which contains another zip containing the blob). Is it true?
nono240 said:
I read, somewhere, that we can flash stock Asus firmwares using CWM ('update zip') by first extracting the initial zip (which contains another zip containing the blob). Is it true?
Click to expand...
Click to collapse
yes but you will loose root and cwm recovery. It's the easy unroot method.
Not a big concern. I can easily recover both root and CWM using the universal root method since I have a B50!
Thanks
Will you lose root/cwm even if you have OTA Rootkeeper installed?
You Shouldn't but no guarentees x)
Dear all
My tf700t stops at the first Asus monitor with nVidia logo down and unlocked at the top left. Have rooted it with unlocked it with Asus tool, rooted with "RootDebugfs," added TWRP via GooManager and tested several roms, but Asus will not boot. Having thus access to Fastboot and TWRP. The following roms is tried: "Mysticial ROM v1", "Team EOS ROM for the TF700" and "Maniacs ROM" for 4.0, but the same thing happens every time. Have tried all possible ways to delete cache but no result. I need help now.
alldog said:
Dear all
My tf700t stops at the first Asus monitor with nVidia logo down and unlocked at the top left. Have rooted it with unlocked it with Asus tool, rooted with "RootDebugfs," added TWRP via GooManager and tested several roms, but Asus will not boot. Having thus access to Fastboot and TWRP. The following roms is tried: "Mysticial ROM v1", "Team EOS ROM for the TF700" and "Maniacs ROM" for 4.0, but the same thing happens every time. Have tried all possible ways to delete cache but no result. I need help now.
Click to expand...
Click to collapse
It seems you picked three ROMS with problems to try for your 1st flash. I can't say anything about the Mystical ROM v1 (although it is based on a TF300 JB OTA) but the other 2 just may not boot at all (maniac is old old, and the EOS JB Rom v3 couldn't boot).
If you can try ZEUS v4 (ICS) or unofficial CM10 alphs latest 9/25 build (JB) you would be OK.
IF you are truly stuck, and you have a microsd card, follow the restore from a soft brick guide from here: http://forum.xda-developers.com/showthread.php?t=1803343
Please note that this guide references the .26 update...if you updated to the .30 update, use that stock rom (I think you can get it from the same place). Just follow the instructions and you should be back at square one-stock. Re-root and reinstall TWRP, then choose a ROM more wisely, by reading the threads to see what is working well.
okantomi said:
It seems you picked three ROMS with problems to try for your 1st flash. I can't say anything about the Mystical ROM v1 (although it is based on a TF300 JB OTA) but the other 2 just may not boot at all (maniac is old old, and the EOS JB Rom v3 couldn't boot).
If you can try ZEUS v4 (ICS) or unofficial CM10 alphs latest 9/25 build (JB) you would be OK.
IF you are truly stuck, and you have a microsd card, follow the restore from a soft brick guide from here: http://forum.xda-developers.com/showthread.php?t=1803343
Please note that this guide references the .26 update...if you updated to the .30 update, use that stock rom (I think you can get it from the same place). Just follow the instructions and you should be back at square one-stock. Re-root and reinstall TWRP, then choose a ROM more wisely, by reading the threads to see what is working well.
Click to expand...
Click to collapse
Sorry, no luck with the ZEUS v4. Same happen again. When booting, the first screen hangs....no weel either. Have been reading for 3 days now here on xda and tryed a lot of possible solutions. I cant get TWRP to mount a microsd card, have to rely on the pad itself. So, any other ideas?
okantomi said:
It seems you picked three ROMS with problems to try for your 1st flash. I can't say anything about the Mystical ROM v1 (although it is based on a TF300 JB OTA) but the other 2 just may not boot at all (maniac is old old, and the EOS JB Rom v3 couldn't boot).
If you can try ZEUS v4 (ICS) or unofficial CM10 alphs latest 9/25 build (JB) you would be OK.
IF you are truly stuck, and you have a microsd card, follow the restore from a soft brick guide from here: http://forum.xda-developers.com/showthread.php?t=1803343
Please note that this guide references the .26 update...if you updated to the .30 update, use that stock rom (I think you can get it from the same place). Just follow the instructions and you should be back at square one-stock. Re-root and reinstall TWRP, then choose a ROM more wisely, by reading the threads to see what is working well.
Click to expand...
Click to collapse
Thanks for tips mister, since I dont can find the right version from ASUS I have to ask...in Europe is it the WW version i suppose to use, and its the Firmware not the Source code?
alldog said:
Sorry, no luck with the ZEUS v4. Same happen again. When booting, the first screen hangs....no weel either. Have been reading for 3 days now here on xda and tryed a lot of possible solutions. I cant get TWRP to mount a microsd card, have to rely on the pad itself. So, any other ideas?
Click to expand...
Click to collapse
Why not installing a stock rom (the same version you had before the issues started) with TWRP, that should get you back on track.
Edit: Yes european version should be WW_SKU and please use the firmware not the source.
Got one step further ..or did I? Tryed to put in stock .30 used "fastboot -i 0x0B05 flash system blob" in fastboot usb-mode. Seemd ok until this message arrived: Failed to prosess flash system error (0x17003)
So, close but not there. There are some problem with flashing since other images also refuse to install. What now?
I've got the ICS bootloader and wanted to flash the new bootloader and get cm10 back on my device.
Couldn't I just flash the blob for 4.1 to do this? I see the 'how to' that talks about moving files here and there, but shouldn't I be able to use the tool to install the latest stock/ota blob to do the same thing?
beepea206 said:
I've got the ICS bootloader and wanted to flash the new bootloader and get cm10 back on my device.
Couldn't I just flash the blob for 4.1 to do this? I see the 'how to' that talks about moving files here and there, but shouldn't I be able to use the tool to install the latest stock/ota blob to do the same thing?
Click to expand...
Click to collapse
If you're still on ICS, I would recommend you first to back up your bootloader using nvflash (search the development forum). Updating to JB will also re-write the bootloader and there isn't a known way to revert that change, meaning that once you flash JB you can't go back to ICS. Although I never had to go back to ICS cause JB is pretty stable, I did it anyway just to be on the safe side.
Once you do that (or if you already did) you are better off running asus update to JB. As far as I know, in order to flash JB roms you need a JB recovery image, which you can't install if you're on ICS.
Yea, that was kinda what I was looking to find out... Can't we just use the Asus update and blobs to go to jb and, if we wanted, back to ics?
Since it wipes the device, can't we just use the Asus updater and tool rather than the overly complicated method described in another post?
It's been a while since I've had to flash a blob, but I think it was the Viper tool I used... Seems like we could just get the ICS and jb blobs and use that tool to flash which ever we wanted. But someone please correct me if I'm wrong.
I just got my TF700 the other day. I was able to downgrade to .30, root, and unlock the bootloader without incident. I just pushed CWM per this thread: http://forum.xda-developers.com/showpost.php?p=31556045&postcount=1. I tried booting into CWM, got the standard quick vibration but the tablet was dead after that. I messed around for a while and finally after holding the power button several times in a row, it booted as normal. Battery is at 80%
Before I go any further, what just happened? Can I push CWM again the same way to re-install it? How should I proceed?
FWIW, the checksum for download 1 on the page mentioned only matched the checksum for #2. I used #2 because it matched its MD5 as it was listed on the page.
lowriderdog37 said:
I just got my TF700 the other day. I was able to downgrade to .30, root, and unlock the bootloader without incident. I just pushed CWM per this thread: http://forum.xda-developers.com/showpost.php?p=31556045&postcount=1. I tried booting into CWM, got the standard quick vibration but the tablet was dead after that. I messed around for a while and finally after holding the power button several times in a row, it booted as normal. Battery is at 80%
Before I go any further, what just happened? Can I push CWM again the same way to re-install it? How should I proceed?
FWIW, the checksum for download 1 on the page mentioned only matched the checksum for #2. I used #2 because it matched its MD5 as it was listed on the page.
Click to expand...
Click to collapse
The proper way to do this is to upgrade to the latest stock JB (10.4.4.25), unlock, and you can either fastboot the recovery or unlock it be flashing Superuser. It is not advised to downgrade,even if it seems easier, because if you do it the way I stated, everything will be latest and should not have any problems whatsoever. since you downgraded to ICS, you now have a ICS bootloader. an ICS bootloader will not boot JB, nor vice versa. so now you will need to flash a JB bootloader, which will not boot the stock ICS, so you will now need Cromi, Cyanogen,or another custom rom to get it update with JB. Make sure you have them preinstalled on a SDcard before doing any more flashing.
If I am wrong, hopefully someone will correct me.
Tylor
Sent from my ASUS Transformer TF700T Infinity Pad Using Tapatalk HD
Rom: Cyanogen Nightlies 10.1 or CleanRom 3.4.4 - Depends on the mood .
Tylorw1 said:
The proper way to do this is to upgrade to the latest stock JB (10.4.4.25), unlock, and you can either fastboot the recovery or unlock it be flashing Superuser. It is not advised to downgrade,even if it seems easier, because if you do it the way I stated, everything will be latest and should not have any problems whatsoever. since you downgraded to ICS, you now have a ICS bootloader. an ICS bootloader will not boot JB, nor vice versa. so now you will need to flash a JB bootloader, which will not boot the stock ICS, so you will now need Cromi, Cyanogen,or another custom rom to get it update with JB. Make sure you have them preinstalled on a SDcard before doing any more flashing.
If I am wrong, hopefully someone will correct me.
Tylor
Sent from my ASUS Transformer TF700T Infinity Pad Using Tapatalk HD
Rom: Cyanogen Nightlies 10.1 or CleanRom 3.4.4 - Depends on the mood .
Click to expand...
Click to collapse
The writeups I had seen prior unlocking said to downgrade to .30...so I did. I am still sitting on .30 and am planning on installing CM 10.1 which I have on both the TF700 internal and an external SD card. The only problem is what I mentioned above where my device wouldn't boot into CWM and subsequently locked up for about 15 min. Should I upgrade to JB .25 prior to booting into CWM and installing CM 10.1?
lowriderdog37 said:
The writeups I had seen prior unlocking said to downgrade to .30...so I did. I am still sitting on .30 and am planning on installing CM 10.1 which I have on both the TF700 internal and an external SD card. The only problem is what I mentioned above where my device wouldn't boot into CWM and subsequently locked up for about 15 min. Should I upgrade to JB .25 prior to booting into CWM and installing CM 10.1?
Click to expand...
Click to collapse
I CM10.1 requires the JB bootloader, If you install CM on the ICS it wont boot. I dont see why the recovery is the problem. I would try updating to JB bootloader, use the zips in Cromi's second post, and then try installing Cromi. Downgrading is only recommended if you want to stay on a locked bootloader. Otherwise, you should flash the root.then install recovery, or simply fastboot it.
In order to install CM you will need to update the bootloader, then once it is updated you will not be able to boot into the ICS rom, so you will have to already have CM10.1, also dont forget google apps, so it can be flash afterwards.
IF CM is installed with the ICS boot loader it will just not boot, it will go into recovery but that is it. I dont see any probability in bricking your device. But I am only a newb, so you may wanna wait for another's input.
Tylor
Sent from my ASUS Transformer TF700T Infinity Pad Using Tapatalk HD
Rom: Cyanogen Nightlies 10.1 or CleanRom 3.4.4 - Depends on the mood .
---------- Post added at 01:26 PM ---------- Previous post was at 01:20 PM ----------
lowriderdog37 said:
The writeups I had seen prior unlocking said to downgrade to .30...so I did. I am still sitting on .30 and am planning on installing CM 10.1 which I have on both the TF700 internal and an external SD card. The only problem is what I mentioned above where my device wouldn't boot into CWM and subsequently locked up for about 15 min. Should I upgrade to JB .25 prior to booting into CWM and installing CM 10.1?
Click to expand...
Click to collapse
Or you could install the 10.4.4.25 stock, then just fastboot a recovery. I mistakenly said root with zip, you cant without custom recovery so scratch that, the only way to install custom recovery via the method I gave is fastboot. Or the way you did so, but that requires more steps and upgrades. Also greater chance of bricking. This is because of the incompatibility of the rom, boot loader, and recovery. If you have latest recovery,I would install the bootloader, then flash CM10.1 + Gapps and should be good to go.
Tylor
Sent from my ASUS Transformer TF700T Infinity Pad Using Tapatalk HD
Rom: Cyanogen Nightlies 10.1 or CleanRom 3.4.4 - Depends on the mood .
Got it working. Yes, it appears CWM is bootloader specific. I flashed the JB bootloader and was able to get into cwm and install CM10.1 I am not up and running. Thanks!
lowriderdog37 said:
Got it working. Yes, it appears CWM is bootloader specific. I flashed the JB bootloader and was able to get into cwm and install CM10.1 I am not up and running. Thanks!
Click to expand...
Click to collapse
Just remember for future reference, keep things up to date,or at least compatible with one another or you will run into trouble later.The #1 reason for tf700's bricking software wise is people do not update their bootloader as they update their recovery. Just keep things recent and you should have not a problem.
Tylor
Sent from my ASUS Transformer TF700T Infinity Pad Using Tapatalk HD
Rom: Cyanogen Nightlies 10.1 or CleanRom 3.4.4 - Depends on the mood .
Hi, I unlocked my TF300T sotck ICS 4.0.3 with the Asus app, I flashed CWM and the root_signed thingy without a problem. I then did a data wipe, cache and dalvik wipe and flashed CM10 stable build for TF300T and the Gapps zip. I reboot and it's stuck on ASUS screen. I'm currently doing a restore of the "nandroid". Will this restore my tablet to ICS? What did I do wrong? How do I get either Cm10 to work or return to the ICS? Also, if I need to flash something else, how do I do it? Does the CWM recognize msd cards? Because all I have on the internal memory is the CM10 which currently did not work for me. I'm a little desperate right now. Thanks.
EDIT: DAMN IT, I just got an error restoring data. What the hell do I do? Please!
i tried restoring again and reflashing cm10 and the gapps and still nothing changes. I did wipe again the caches and still nothing. Also I can't download other roms to the tablet because my computer doesn't recognize the tablet because it hasn't booted and the cwm won't recognize micro sd cards. So I think flashing something else isn't an option. Did I break my tablet completely? I'm almost in tears
I tried several things due to some searches on different forums but nohitng works. I tried wiping caches and reflashing Cm10, didn't work. I tried pluggin my tablet to my computer and sending the asus stock rom via ADB and flashing that, but CWM gives me an "installacion aborted" error. I just don't know what to do nor I understand what went wrong. I did everything according to multiple tutorials. Unlocking, flashing CWM and rooting went just fine. But installing CM10 ended up pretty much destroying my tablet. I wanna kill myself.
I think you have a brick??!! :'( cm10 is jellybean and you where on ics and you probably didn't flash the jellybean bootloader did you?
Sent from my ASUS Transformer Pad TF300T
Not a single tutorial said that I had to do that. Every tutorial says "unlock bootloader, flash cwm, flash root_signed, flash cmrom". I did just that. Are you telling me that my tablet is lost forever?
in most cm threads (except cm9) their is stated that you atleast need android 4.1.1 with it's bootloader or 4.2 with it's bootloader, what i suggest you try is to flash a bootloader and upgrade staight to 4.1.1 you can download the firmware from asus the links are on this guide: http://forum.xda-developers.com/showthread.php?p=39272826 FOLLOW THIS GUIDE CORRECTLLY OR YOU MIGHT PERMANENTLY BRICK YOUR TABLET!!!!
EDIT: if you get an error during flash it's probably the drivers or a fastboot flash brick wich is only fixable by replacing the motherboard!!
Sent from my ASUS Transformer Pad TF300T
If what you say is true, then you can't flash CM10 on a stock ICS tablet, and that goes against every freaking tutorial I've read before messing with my tablet.
What exactly is your bootloader version?
Sent from my ASUS Transformer Pad TF300T
I'm not sure what my answer is. The "bootloader" was unlocked by the Asus app from their website. I did that by downloading (I believe it was V7) the apk from their website and installing that and unlocking the tablet. From there on, I just followed did fastboot flashing CWM and rooting. I never read a tutorial that said "you should flash JB bootloader before installing cm10". In fact I thought that just by unlocking the tablet, rooting and flashing the custom recovery one could just install a custom rom regardless of wether it's JB or not. It's funny because I didn't want to upgrade to stock JB because it seemed buggy from a lot of reviewers, and CM10 was the classic option to have JB and a lot of great features and speed. So I google time and time again how to flash CM10 on a ICS stock ASUS. I just followed the tutorials for that.
is my tablet unrecoverably bricked? I also tried fastbooting and "flash system blob" with the blob for the ICS 4.0.3 firmware, after a while of "sending" the file in the command prompt, I got a blue progress bar in the fastboot screen on the tablet and then "FAILED". So I guess that doesn't work either.
Nothing will work?
Try entering fastboot reboot: does your tablet reboot or does it hang?
cm10 is android 4.1 it seems logical that it only runs on a 4.1 bootloader and not on an ics one! most posts must have said that you atleast need jelllybean 4.1.1
I was confused in the beginning aswell because my phone accepts any rom no matter what bootloader version!
Sent from my ASUS Transformer Pad TF300T
If it makes so much sense that CM10 with JB 4.1 only boots with the JB bootloader, then how the hell one can go from ICS to CM10?! Google tutorial flash cm10 on asus tf300t stock ics and you'll find a thousand tutorials not one of which says you need JB bootloader. I mean, I assume one could upgrade to the official JB rom and then unlock bootloader, etc, but I'm telling you, every tutorial that said "stock ics to cm10" did no mention the bootloader version issue. I'm not trying toblame anyone other than myself for "bricking" my tablet, but I read so many tutorials to ensure I wouldn't mess it up that I'm very upset about this.
I can use fastboot and adb commands. But I haven't been able to flash the ICS stock rom so far. First of all, it's not on the Asus website anymore, and the one I got from the web gave me this error on CWM "instaling update.. installation aborted". I also tried flashing the .blob via fastboot and it also failed. It seems nothing works. Any thoughts, anyone?
philos64 posted links to some old ICS ASUS firmwares in this post:
http://forum.xda-developers.com/showpost.php?p=33883254&postcount=3
Maybe worth a try ? Never been on ICS myself - just thought I'd mention this source...sorry for wasting your time if this is what you already tried.
Yeah, I tried flashing the ICS 9.4.3.30 (my stock rom) and it didn't fly (said installation aborted) and also tried to flash it as a blob and it failed. I guess I deserve this, but I just can't bellieve this isn't fixable.
samus88 said:
Yeah, I tried flashing the ICS 9.4.3.30 (my stock rom) and it didn't fly (said installation aborted) and also tried to flash it as a blob and it failed. I guess I deserve this, but I just can't bellieve this isn't fixable.
Click to expand...
Click to collapse
We would like to know what bootloader you now have. You use the bootloader menu to get to cwm. Tell us how many ICONS you have and what they are. This way we will have more info to consider options if any.
It's ICS. I have the Wipe Data and the Coldboot option. If I'm connecte with the usb cable, there's also the usb icon.
Currently I don't have the tablet, because I send it to a tech support place and they should give me a repair budget (if they deem it repairable, I guess) by tomorrow, but I'm not confident that they'll be able to fix it. So I'm still open to suggestions. Thanks!
samus88 said:
It's ICS. I have the Wipe Data and the Coldboot option. If I'm connecte with the usb cable, there's also the usb icon.
Currently I don't have the tablet, because I send it to a tech support place and they should give me a repair budget (if they deem it repairable, I guess) by tomorrow, but I'm not confident that they'll be able to fix it. So I'm still open to suggestions. Thanks!
Click to expand...
Click to collapse
I reread the thread and I believe I would make a blob with just stock recovery (4.03) to match your bootloader. I know fastboot is failing on a complete blob but may process something as small as recovery. The blob could also be pushed to your tablet with adb and flash with that.
I made these choices as a place to begin since we need to match your bootloader.
Once stock recovery was in place we could use adb to push a once unzipped stock firmware (4.03) and get stock recovery to install it for us.
Thanks a lot man. When I get the tablet back and you make me that blob I'll definitely give it a try. Although I have a question, I already have the once unzipped stock ICS on my tablet (pushed it with ADB), how do I install it with stock recovery should flashing that blob work?
samus88 said:
Thanks a lot man. When I get the tablet back and you make me that blob I'll definitely give it a try. Although I have a question, I already have the once unzipped stock ICS on my tablet (pushed it with ADB), how do I install it with stock recovery should flashing that blob work?
Click to expand...
Click to collapse
With stock recovery in place go into bootloader and pretend you are going into cwm that activates stock recovery now. If android lays down we'll rename the zip to EP201_768_SDUPDATE.zip and try again.
I'll download 4.03 and make the recovery blob tomorrow so we'll be ready.
Sorry about that. I read "I would make" as "I will make", lol. Is there a stock recovery 4.0.3 blob on the internet for download? I'll get some sleep now, but I'll try to prepare everythng for when I get the tablet back, assuming I don't have fixed for me by tech support (although I'd love not to have to pay forit, right)
samus88 said:
Sorry about that. I read "I would make" as "I will make", lol. Is there a stock recovery 4.0.3 blob on the internet for download? I'll get some sleep now, but I'll try to prepare everythng for when I get the tablet back, assuming I don't have fixed for me by tech support (although I'd love not to have to pay forit, right)
Click to expand...
Click to collapse
No, there is the full blob in the factory firmware and that is what I'll use. It only takes a couple of minutes to extract the recovery image file which might flash and then re-blob just the recovery partition.
Downloading takes longer than everything else.
Update:
This zip contains stock 4.03 recovery as a blob and as an image file.
Unzip and try flashing the blob - if it fails try flashing twice more or until success. If it still fails try flashing the image file - three times if it fails.
Note:
These are to be flashed with fastboot or adb, not cwm.
Great, thanks man. Unfortunately, I won't have my tablet until at least wednesday because of the holiday on my country (independence day and such). But I'll give it a try and get back to you.