Incremental Updates? - Asus Transformer TF700

Hey all,
I just replaced my TF700 through Best Buy's super replacement program, and thank God I got one at .26. I am going through the process of rooting, unlocking, NVFlashing, recovery, etc. and have a question. To get back up to current ROMs, should I install ASUS firmware updates incrementally? Or can I just flash say CM 10.1 or CleanROM right over .26?
Thanks!

I_EAT_BABIES said:
Hey all,
I just replaced my TF700 through Best Buy's super replacement program, and thank God I got one at .26. I am going through the process of rooting, unlocking, NVFlashing, recovery, etc. and have a question. To get back up to current ROMs, should I install ASUS firmware updates incrementally? Or can I just flash say CM 10.1 or CleanROM right over .26?
Thanks!
Click to expand...
Click to collapse
Don't know about CM10.1, but as for CleanRom, I think it's fair to say that as long as you have the lastest or second latest bootloader, you can flash CRomI on it.
Like I said, don't know about CM, because I never tried it, no matter how much I wanted to be on 4.2, because I am super happy with CRomI, which as an Asus based Rom works flawlessly with the dock

I_EAT_BABIES said:
Hey all,
I just replaced my TF700 through Best Buy's super replacement program, and thank God I got one at .26. I am going through the process of rooting, unlocking, NVFlashing, recovery, etc. and have a question. To get back up to current ROMs, should I install ASUS firmware updates incrementally? Or can I just flash say CM 10.1 or CleanROM right over .26?
Thanks!
Click to expand...
Click to collapse
No you can't, you need JB bootloader, you need to flash a full JB firmware from Asus. Others, may just flash the JB bootloader independently. After you have JB bootloader then you can flash cm10 or Cleanrom since they build on JB base. (cm10 and cleanrom don't included bootloader, just rom and kernel)

Thanks guys.
I'm assuming even just flashing the bootloader will wipe my recovery?

I_EAT_BABIES said:
I'm assuming even just flashing the bootloader will wipe my recovery?
Click to expand...
Click to collapse
If you extract the bootloader from the full blob and flash only that (or use a stand-alone bootloader blob extracted by someone else), then it won't wipe your recovery.
But if you don't know 100% what you are doing, it is safer and easier to flash the complete firmware and re-flash the recovery via fastboot.
Remember that a recovery incompatible with the bootloader in combination with "wipe data" leads to a brick (which can be solved with nvflash or otherwise by Asus only).

Related

Can't load recovery

Hello everyone,
My problem is this: I wanted to install a CM10 nightly on the device, so I root using the DebugfsRoot method, install rom manager, flash a recovery, try to install a ROM and it did not work. Rebooting into recovery got me the red triangle, but using the volume buttons allowed me to get in (only it did not have the option to install updates or anything. I think it was just he mounting and partition options)
Since I did not unlock the device before doing this, I chose to do so using ASUS's unlock utility. Once done, I tried booting into recovery, but the device would be stuck at "booting recovery kernel image" and won't budge. I tried flashing different version of CW but it did not seem to work.
Finally, for some reason, I chose the "wipe data" option from the bootloader and the device was stuck, again, at "booting recovery kernel image", only this time I can't boot into a ROM nor can I boot back into bootloader.
What happens when I boot using power and volume down is this:-
The device is Unlocked
Android cardhu-user bootloader <2.10 e> released by "US_epad-9.4.5.26-20120720" A03
Checking for android ota recovery
Booting recovery kernel image
and then everything's stuck.
Booting normally makes the device stop at "the device is unlocked" message because, I assume, there is no ROM flashed into the device.
Thanks for helping in advance.
It's not just that I can't get the unit to go into recovery, It's that I can't even get to fastboot (it tries to go into recovery every time I try to get into fastboot)
ShiroiKage said:
It's not just that I can't get the unit to go into recovery, It's that I can't even get to fastboot (it tries to go into recovery every time I try to get into fastboot)
Click to expand...
Click to collapse
I believe your device is bricked. Using a wrong version of custom recovery may caused this. I haven't seen anyone able to fix the issue that you having right now, the only thing is to send out to Asus for repair.
buhohitr said:
I believe your device is bricked. Using a wrong version of custom recovery may caused this. I haven't seen anyone able to fix the issue that you having right now, the only thing is to send out to Asus for repair.
Click to expand...
Click to collapse
So, if I get it repaired/replaced, what version of CW recovery should I get? It seems that there is not, yet, a version for the Infinity tab. I really want to get a custom ROM because the stuff ASUS has slapped on their version of Android gets under my skin.
ShiroiKage said:
So, if I get it repaired/replaced, what version of CW recovery should I get? It seems that there is not, yet, a version for the Infinity tab. I really want to get a custom ROM because the stuff ASUS has slapped on their version of Android gets under my skin.
Click to expand...
Click to collapse
The Team Win TWRP version 2.3.1.0 works really well. It's a touch recovery and very easy to use and full featured.
okantomi said:
The Team Win TWRP version 2.3.1.0 works really well. It's a touch recovery and very easy to use and full featured.
Click to expand...
Click to collapse
One very last question:-
Would it work if I get the CM10 nightly for the TF300T installed on a TF700T (since it's practically the same device with a different screen)? If not, is there a ROM that's pure JB without ASUS's stuff installed one it?
Your replies are very much appreciated.
ShiroiKage said:
One very last question:-
Would it work if I get the CM10 nightly for the TF300T installed on a TF700T (since it's practically the same device with a different screen)? If not, is there a ROM that's pure JB without ASUS's stuff installed one it?
Your replies are very much appreciated.
Click to expand...
Click to collapse
I would NOT recommend you do so with tf300 on tf700. There is no pure stock debloated version for JB, however, if you want to stay as close as stock and stable I would recommend "Cleanrom for JB". This rom doesn't have Asus bloatware and a few performance tweaks make it very good.
buhohitr said:
I would NOT recommend you do so with tf300 on tf700. There is no pure stock debloated version for JB, however, if you want to stay as close as stock and stable I would recommend "Cleanrom for JB". This rom doesn't have Asus bloatware and a few performance tweaks make it very good.
Click to expand...
Click to collapse
So I got it replaced (Best Buy swapped it for a new one) and everything's fine. I even installed Clean ROM and it's good. Problem is that the left speaker is not working and I need to flash the stock ROM to make sure it's nothing caused by software, before I go back and re-return the unit. However, ASUS's firmware is not longer wanting to flash. It gives me the "failed" message in TWR's recovery (no backup because my internal memory was wiped when installing ASUS's JB update :/)
EDIT: Never mind. I thought the holes at the bottom, on either side of the USP port, were the speakers. Turns out I was not thinking straight. Still, I'd like to know if anyone has an idea as to why the ASUS firmware is not wanting to install.
ShiroiKage said:
So I got it replaced (Best Buy swapped it for a new one) and everything's fine. I even installed Clean ROM and it's good. Problem is that the left speaker is not working and I need to flash the stock ROM to make sure it's nothing caused by software, before I go back and re-return the unit. However, ASUS's firmware is not longer wanting to flash. It gives me the "failed" message in TWR's recovery (no backup because my internal memory was wiped when installing ASUS's JB update :/)
EDIT: Never mind. I thought the holes at the bottom, on either side of the USP port, were the speakers. Turns out I was not thinking straight. Still, I'd like to know if anyone has an idea as to why the ASUS firmware is not wanting to install.
Click to expand...
Click to collapse
You can't install the ASUS firmware through custom recovery. It has to be stock. I believe there are signature checks that prevent it from installing otherwise.
Sent from my ASUS Transformer Pad TF700T
did you unzip the file? should be a zip within a zip. you flash the zip inside
lafester said:
did you unzip the file? should be a zip within a zip. you flash the zip inside
Click to expand...
Click to collapse
You know, I unzipped the file the first time I installed it to get Clean ROM to flash, I had the unzipped folder there yet I managed to forget to use the unzipped file. /InfiniteFacePalm

[Q] Question on ICS to JB update - Bootloader or Full?

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!

[Q] Can the bootloader be downgraded

Hi all,
After having successfully rooted my TF700 lately (while keeping the bootloader locked), I've been looking into unlocking the bootloader so I can flash a custom ROM (thinking about CROMI). Before flashing a custom ROM, people seem to recommend getting nvflash in order.
My problem is, however, I'm already on JB, and my understanding is that you need an ICS .26 bootloader (or earlier) in order to setup nvflash. I know that it's possible to downgrade the firmware from JB to ICS (in fact, this is what I did in order to be able to root my device - going from the latest JB to ICS .30); however, after searching around a fair bit, I'm still not clear on whether it's possible to revert the bootloader to an earlier version.
Can someone please clarify this for me. If I've already updated my device to JB, is there absolutely no way for me to set up nvflash?
Thanks!
joshnl said:
Hi all,
After having successfully rooted my TF700 lately (while keeping the bootloader locked), I've been looking into unlocking the bootloader so I can flash a custom ROM (thinking about CROMI). Before flashing a custom ROM, people seem to recommend getting nvflash in order.
My problem is, however, I'm already on JB, and my understanding is that you need an ICS .26 bootloader (or earlier) in order to setup nvflash. I know that it's possible to downgrade the firmware from JB to ICS (in fact, this is what I did in order to be able to root my device - going from the latest JB to ICS .30); however, after searching around a fair bit, I'm still not clear on whether it's possible to revert the bootloader to an earlier version.
Can someone please clarify this for me. If I've already updated my device to JB, is there absolutely no way for me to set up nvflash?
Thanks!
Click to expand...
Click to collapse
Once you're on JB, the lowest you can downgrade is ICS .30. You're too late for Nvflash. No way around it.
Okay... sucks, but thanks for the info. That's what I was afraid of.
Since that is the case, how critical is it to set up nvflash before getting into the whole custom ROM thing? Am I crazy to get into it without nvflash as a backup plan?
joshnl said:
Since that is the case, how critical is it to set up nvflash before getting into the whole custom ROM thing? Am I crazy to get into it without nvflash as a backup plan?
Click to expand...
Click to collapse
There is a bug in the bootloader that you should be aware of: If your recovery is broken because it is
* too old, designed for the ICS bootloader, or
* you erased it via fastboot
then you should NEVER EVER choose "wipe data" from the bootloader menu. Except you want an expensive paperweight. Because then you can't even enter fastboot to fix it. This is the only situation where nvflash would really help you out.
If you always test any newly flashed recovery first by using the power+volume buttons, you are safe.
Thanks, _that!
_that said:
There is a bug in the bootloader that you should be aware of: If your recovery is broken because it is
* too old, designed for the ICS bootloader, or
* you erased it via fastboot
then you should NEVER EVER choose "wipe data" from the bootloader menu. Except you want an expensive paperweight. Because then you can't even enter fastboot to fix it. This is the only situation where nvflash would really help you out.
If you always test any newly flashed recovery first by using the power+volume buttons, you are safe.
Click to expand...
Click to collapse
I know man who did wipe data from bootloader, it didn't brick him He has done this today on unlocked, TWRP and CROMI on TF300T. The newest bootloader fix it.
Hazard17 said:
I know man who did wipe data from bootloader, it didn't brick him He has done this today on unlocked, TWRP and CROMI on TF300T. The newest bootloader fix it.
Click to expand...
Click to collapse
It would not brick him if he installed the latest version the either recovery -- that's exactly what _that said.
Simply put, just keep your recovery up-to-date when major versions release and update the bootloader. When things such as this happen, they will be posted in the rom threat, just make sure you read thoroughly. Also, read the change log before upgrading the recovery, and if you use TWRP use GooManager and it will upgrade it for you at a tap of a button.

[Q] Temporarily bricked after trying to boot into CWM

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 .

Stuck on ASUS screen while installing CM10

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.

Categories

Resources