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
Related
I brought a transformer tf300 a few days ago that was already rooted and unlocked. I can't get adobe flash to work. I tried side loading a few version of adobe but still no success. Google market says my device is not compatible with adobe. I don't think the rooted device really serves me any purpose so I would like to take it back to factory condition. I need some help doing it since I have never rooted a device before.
It is rooted with
aokp-tf300t-build-38.
Android ver 4.0.4.
Kernel 2.6.39.4 g2bf1397-dirty.
Build IMM761.
Thanks for all your help if you can. I will need step by step instructions, and thanks again for the help
jflynn0 said:
I brought a transformer tf300 a few days ago that was already rooted and unlocked. I can't get adobe flash to work. I tried side loading a few version of adobe but still no success. Google market says my device is not compatible with adobe. I don't think the rooted device really serves me any purpose so I would like to take it back to factory condition. I need some help doing it since I have never rooted a device before.
It is rooted with
aokp-tf300t-build-38.
Android ver 4.0.4.
Kernel 2.6.39.4 g2bf1397-dirty.
Build IMM761.
Thanks for all your help if you can. I will need step by step instructions, and thanks again for the help
Click to expand...
Click to collapse
download the latest firmware from the asus site first. http://www.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_TF300T/#download
Then install the current software version. You can use the instructions from here to reflash stock rom in post 2
http://forum.xda-developers.com/showthread.php?t=1668173
dxwilliams40 said:
download the latest firmware from the asus site first. http://www.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_TF300T/#download
Then install the current software version. You can use the instructions from here to reflash stock rom in post 2
http://forum.xda-developers.com/showthread.php?t=1668173
Click to expand...
Click to collapse
don't know what im doing wrong when i try to flash the stock rom i get stuck as the ASUS splash screen with spinning wheel. Any suggestions?!?
cjohnsonthe2nd said:
don't know what im doing wrong when i try to flash the stock rom i get stuck as the ASUS splash screen with spinning wheel. Any suggestions?!?
Click to expand...
Click to collapse
Did you unzip the firmware and flash the zip named "US_epad-user-9.4.3.29"?
dxwilliams40 said:
Did you unzip the firmware and flash the zip named "US_epad-user-9.4.3.29"?
Click to expand...
Click to collapse
yes and CWM says install from sd card complete, no errors. I get the intial boot screen with the blue progress bar then I get stuck at the spash screen with the spinning wheel.
Luckily I had a nandroid of my AOKP setup and can go back to that. Ive tried a few times today to return to stock with the same results.
cjohnsonthe2nd said:
yes and CWM says install from sd card complete, no errors. I get the intial boot screen with the blue progress bar then I get stuck at the spash screen with the spinning wheel.
Luckily I had a nandroid of my AOKP setup and can go back to that. Ive tried a few times today to return to stock with the same results.
Click to expand...
Click to collapse
Remember to full wipe before installation including /system and after clear dalvik and cache then fix permissions.
By not wiping /system can cause some data to be left and corrupt stock installation had this happen on my g2x and have seen it on some other threads.
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
I wiped the cache before I started the install and now when I boot into the usb fastboot my comp flashed a bootloader notification but then nothing else happens. I tried it a second time and I dont even get the notification. Also if I let it boot regular the Asus screen shows when i first boot but then nothing ever comes up just black screen
Hi guys,
My tablet is rooted (and back to fully stock ROM from Acer's website). I updated OTA just a moment ago, and I was totally shocked to see the message "Booting kernal recovery image - Recovery verified failed..."
I tried rebooting, fastbooting,....they all don't work. How should I move on? What can be done now?
Please do help me. I need the tablet, and never knew such a situation could arise.
Thanks!
Sounds like your device's bootloader is locked again. Just perform a fastboot oem unlock and see whether that fixes your problem. Worked for me.
/edit: Which, of course, assumes you're able to get into fastboot. You should be able to get in using adb... what do you mean by "they all don't work"?
got the same problem. how do you get into fastboot again?
Liquidator said:
Sounds like your device's bootloader is locked again. Just perform a fastboot oem unlock and see whether that fixes your problem. Worked for me.
/edit: Which, of course, assumes you're able to get into fastboot. You should be able to get in using adb... what do you mean by "they all don't work"?
Click to expand...
Click to collapse
I assume yes, it is locked since I went back to a fully Stock ROM (which includes the locked bootloader?). But what has a bootloader got to do with an OTA update?
What I mean by they all don't work is that, even when I try shutting down, rebooting or enter stock recovery using the volume keys + power button, nothing works. Absolutely nothing! The screen just stays there.
I then thought, let the battery run down and maybe I can enter stock recovery and flash the zip for the stock ROM again from my SD card, but this doesn't work. The tablet just boots again to that same screen, with a message saying wiping off update cache and something to do with cdm.
I fear my device is gone. If anyone can lead me to getting back my device up and running, as a small token of appreciation, I will provide you with either $10 via PayPal or a $10 Google Play Gift Card code. This is really important for me, and I can't seem to find any help on this matter on the Internet.
I tried to update to JB, by flashing a stock rom through CWM. But then I try to get into the recovery I get hte same message. For me, if i dont try to get into the recovery it repeats an animation of the Acer logo and it never ends. I believe ill have to give it to the acer support. I also cant get into the stock recovery, so we pretty much have the same problem.
Temporeiches said:
I tried to update to JB, by flashing a stock rom through CWM. But then I try to get into the recovery I get hte same message. For me, if i dont try to get into the recovery it repeats an animation of the Acer logo and it never ends. I believe ill have to give it to the acer support. I also cant get into the stock recovery, so we pretty much have the same problem.
Click to expand...
Click to collapse
No, we don't have a same problem. I don't have CWM on my device, and I am doing an OTA. I can do absolutely NOTHING other than stare at the error message in red ink and the static Acer logo.
Okay sorry. Just want to tell you that I flashed the stock rom and so I lost CWM. If i find a way to fix mine ill tell you and it might help you.
As an update, after letting the tablets battery drain out and then charging it back up, the message I am seeing now is a little longer:
Erasing cache before SD update...
SD Update cmd: recovery
--Update_package=sdcard:update.zip
Booting recovery kernal image
Recovery verified failed...
PS: If anyone can make sense of this message, please tell me.
If I recall correctly, the stock recovery has no user interface whatsoever. All it does is offer to flash a signed update.zip from the external SD card.
I have/had CWM installed, and got the "Recovery verified failed..." message after flashing JB as well. Thing is, it appears Acer is not only flashing the system, but also a new bootloader (which explains the new key-press combos necessary to get into recovery). Why it's not working for you on a stock device I am unable to tell, but something may have gone wrong during your update.
So, suggestion: Place the update.zip from Acer on a microSD and see what happens. With any luck, it'll just flash the system contained within the zip again and it'll work.
Liquidator said:
If I recall correctly, the stock recovery has no user interface whatsoever. All it does is offer to flash a signed update.zip from the external SD card.
I have/had CWM installed, and got the "Recovery verified failed..." message after flashing JB as well. Thing is, it appears Acer is not only flashing the system, but also a new bootloader (which explains the new key-press combos necessary to get into recovery). Why it's not working for you on a stock device I am unable to tell, but something may have gone wrong during your update.
So, suggestion: Place the update.zip from Acer on a microSD and see what happens. With any luck, it'll just flash the system contained within the zip again and it'll work.
Click to expand...
Click to collapse
So how do I get this latest firmware? I can't find on acers website.
himmatsj said:
So how do I get this latest firmware? I can't find on acers website.
Click to expand...
Click to collapse
http://global-download.acer.com/Step5.aspx?Step1=Tablet&Step2=ICONIA%20TAB&Step3=A510&BC=Acer&SC=&LC=en&OS=a09&FS=O02&Category=OS
Change the Language and download the largest file (thats stock ICS) best is the RV28.RC02.WW.GEN1 so later you can retry an update
Temporeiches said:
http://global-download.acer.com/Step5.aspx?Step1=Tablet&Step2=ICONIA%20TAB&Step3=A510&BC=Acer&SC=&LC=en&OS=a09&FS=O02&Category=OS
Change the Language and download the largest file (thats stock ICS) best is the RV28.RC02.WW.GEN1 so later you can retry an update
Click to expand...
Click to collapse
Did the update fail because I already had the previous Acer firmware version as update.zip on my ext sd card? The tab is friggin useless as things stand!!
himmatsj said:
Did the update fail because I already had the previous Acer firmware version as update.zip on my ext sd card? The tab is friggin useless as things stand!!
Click to expand...
Click to collapse
Try this:
Here's how to get into fastboot (bootloader) manually:
Turn off your tablet
Hold the Volume Down (**) button and press the Power button
As soon as the tablet vibrates, let go of only the Power button (keep the Volume Down (**) button pressed) and immediately start switching the Screen Rotation Lock slider back and forth.
If this works continue.Connect your device to PC. Open your device manager look for fastboot under other devices and right click on it and select update driver. Then click browse my computer for driver software and locate the folder i could send by mail, just ask me. Click Next, and it might say it is a threat, but click continue (its safe as I edited it myself) and let it install. Next download http://forum.xda-developers.com/showthread.php?t=1661324 and use it to unlock bootloader. Next follow instructions on http://forum.xda-developers.com/showthread.php?t=1866378 Then place a ROM from NoThrills on an external sdcard, and insert it into the tablet. If the tablet is shut down get into CWM through the key combination for ICS bootloader power and ** sound button and for JB bootloader
* PowerON+Vol-
* At the first vibration release PowerOn, keeping Vol- pressed
* At the second vibration release Vol- and press Vol+
Next flash the rom from external sdcard and reboot. Now things should work.
Guys, can anyone help me understand, why when I do an OTA on a fully stock ROM (no bootloader unlocked, no custom recovery, no custom ROM and no root), do I get the message I mention earlier? (that is: Booting recovery kernel image, Recovery verified failed...)
Mind you, I did go to a custom ROM once, which was No Thrills A700 Fraken ROM for the A510. Could that be an issue here?
Please, just help me understand why I am continuously getting this error when I do an OTA. If you can successfully explain to me, I owe you $10 (PayPal or Google Play Gift Code).
Thanks!
PS: I am not looking for a solution (don't tell me flash this and that, I've done all that). I am merely looking for an explanantion as to why the above happens.
himmatsj said:
Guys, can anyone help me understand, why when I do an OTA on a fully stock ROM (no bootloader unlocked, no custom recovery, no custom ROM and no root), do I get the message I mention earlier? (that is: Booting recovery kernel image, Recovery verified failed...)
Mind you, I did go to a custom ROM once, which was No Thrills A700 Fraken ROM for the A510. Could that be an issue here?
Please, just help me understand why I am continuously getting this error when I do an OTA. If you can successfully explain to me, I owe you $10 (PayPal or Google Play Gift Code).
Thanks!
PS: I am not looking for a solution (don't tell me flash this and that, I've done all that). I am merely looking for an explanantion as to why the above happens.
Click to expand...
Click to collapse
it likely happend due to you rooting and flashing a non stock kernel.
when you apply the update off acers website after having it cwm and a customer rom i don't believe it will replace the recovery properly.
this is becasue the files on acers sites are updates and not full roms.
this is the reason why i did not do it to mine.
don't quote me on it but i had a similar issue with an old phone and ended up stuck on customer roms after that.
malos1984 said:
it likely happend due to you rooting and flashing a non stock kernel.
when you apply the update off acers website after having it cwm and a customer rom i don't believe it will replace the recovery properly.
this is becasue the files on acers sites are updates and not full roms.
this is the reason why i did not do it to mine.
don't quote me on it but i had a similar issue with an old phone and ended up stuck on customer roms after that.
Click to expand...
Click to collapse
You mean when I flashed the A700 Franken ROM by NoThrills, that had a non-stock kernel?
If so, what can I do to get back stock kernel on my tablet? There has to be some way, right?
PS: I flashed the official files from Acer via the update.zip file from their website. From here: http://forum.xda-developers.com/showthread.php?t=1897791
PSS: I checked, and I *think* you are wrong because by flashing the files from Acer's website I am back to the stock kernel. Version number: 2.6.39.4+ (Correct me if I am wrong to assume as such)
himmatsj said:
You mean when I flashed the A700 Franken ROM by NoThrills, that had a non-stock kernel?
If so, what can I do to get back stock kernel on my tablet? There has to be some way, right?
PS: I flashed the official files from Acer via the update.zip file from their website. From here: http://forum.xda-developers.com/showthread.php?t=1897791
PSS: I checked, and I *think* you are wrong because by flashing the files from Acer's website I am back to the stock kernel. Version number: 2.6.39.4+ (Correct me if I am wrong to assume as such)
Click to expand...
Click to collapse
yes but i don't think those update.zip's restore the recovery partitions correctly. They seem to only restore the stock rom and nothing else?
Nothrills may be able to clarify that though. i don't know too much about how these roms work.
malos1984 said:
yes but i don't think those update.zip's restore the recovery partitions correctly. They seem to only restore the stock rom and nothing else?
Nothrills may be able to clarify that though. i don't know too much about how these roms work.
Click to expand...
Click to collapse
Yeah, I hope someone who is directly involved in these things like NoThrills can come and enlighten us.
Thread moved to Q&A
MD
Problem SOLVED!
Hi guys,
For all those having the "recovery verification failed" error while trying to do OTA, I know the fix!
The key is, you need to restore stock recovery manually. There's a zip file of the stock recovery here (at the bottom of the first post). Just restore stock recovery as per usual.
Steps to follow in brief:
1) Install stock recovery manually from HERE
2) If your's isn't the stock Acer ROM, download the correct ICS version for your region from HERE (place it as update.zip and follow steps as per normal to flash)
3) Go to settings>apps>all apps>systemupdater, and then clear data/cache.
4) Reboot tablet and you should get an OTA notification.
5) You're done!
Hi i'm new to all of this but after reading a lot i decided to root my asus Tf300t and instaled a recovery ( CWM).
i instaled a custom rom ( cleanrom 3.4.2) and everything was working good ,but i decided to flash the Unters kernel for Tf 300T.
It reboots and a message appears Android is upgrading Panel Firmware 0%. After that Touch Screen never worked again .
I tried reinstalling cleanrom , stock rom downloaded from Asus Website WW_epad 10_4_2_20 was flashed with fastboot without
results. I do not know what to do next , any help is really appreciated.
nmvp said:
Hi i'm new to all of this but after reading a lot i decided to root my asus Tf300t and instaled a recovery ( CWM).
i instaled a custom rom ( cleanrom 3.4.2) and everything was working good ,but i decided to flash the Unters kernel for Tf 300T.
It reboots and a message appears Android is upgrading Panel Firmware 0%. After that Touch Screen never worked again .
I tried reinstalling cleanrom , stock rom downloaded from Asus Website WW_epad 10_4_2_20 was flashed with fastboot without
results. I do not know what to do next , any help is really appreciated.
Click to expand...
Click to collapse
This happened to me once. You must make sure that the CWM you installed is for JB, not ICS. Even then, CMW might give you problems. I tried to flash the stock rom you mentioned (10_4_2_20) from CWM recovery without success. I extracted the above ROM twice in my laptop. First try gave another zip file*. The second time would create a folder with a blob file inside. I transferred that blob to the platform-tools folder. Went to CMD (run as administrator) in Windows, then to the platform-tools folder, and issued the following commands:
fastboot -i 0x0B05 flash staging blob
took a few minutes to finish (rebooted a few times if my recollection serves me right. You might want to check other threads for accuracy). Once done, type:
fastboot -i 0x0B05 reboot
You're done. Custom recovery has been overwritten. If you want TWRP, you can install it again with ADB. Hope this helps.
* I've been flashing this zip file with TWRP recovery without encountering any glitches.
Thanks for your quick reply. Did what you told me but without success.
I forgot to say that the first time I loaded the stock rom 10_4_2_20, automatically lost the CWM recovery and as I have no dock can not even have
access to anything. Also I can not load the recovery again.
I talked to ASUS support and postage plus diagnosis is 50 € plus the cost of repair. And if I choose to send it to ASUS, the pad is locked again.
I do not know what to do anymore.
:crying:
What do you think I can do more?
nmvp said:
Thanks for your quick reply. Did what you told me but without success.
I forgot to say that the first time I loaded the stock rom 10_4_2_20, automatically lost the CWM recovery and as I have no dock can not even have
access to anything. Also I can not load the recovery again.
I talked to ASUS support and postage plus diagnosis is 50 € plus the cost of repair. And if I choose to send it to ASUS, the pad is locked again.
I do not know what to do anymore.
:crying:
What do you think I can do more?
Click to expand...
Click to collapse
If this thing doesn't boot and you've no access to custom recovery, I can't suggest anything more. Sorry. Does it show in windows as fastboot device? What does ADB say when you type the command?
I do not think you understood well, I can do the boot, the touchscreen does not work after having appeared "Android is updating Firmware Panel 0%."
As I do not have a dock, the pad stays at the initial settings menu when a new rom is flashed because touchscreen do not work.
My problem is only the touchscreen .
And now because i flashed stock rom i lost recovery and from now on i can not enable install from insecure locations in android .
For that reason the pad w'ont let me install another recovery again.
nmvp said:
I do not think you understood well, I can do the boot, the touchscreen does not work after having appeared "Android is updating Firmware Panel 0%."
As I do not have a dock, the pad stays at the initial settings menu when a new rom is flashed because touchscreen do not work.
My problem is only the touchscreen .
And now because i flashed stock rom i lost recovery and from now on i can not enable install from insecure locations in android .
For that reason the pad w'ont let me install another recovery again.
Click to expand...
Click to collapse
Evidently, I have a hard time making out what you're saying. For instance, this: "from now on i can not enable install from insecure locations in android.." What are insecure locations in Android? Beats me.
In short, you're right. The reason I gave directions was that I thought you were asking for a way to flash stock ROM (104220), which apparently you already had ("..because i flashed stock rom i lost recovery..."). If you already have the latest stock ROM on, then I totally misunderstood. Forget I ever said anything.
Thanks for trying to help me.What i mean with unknown sources is an option in Android settings - Security-allow programs install from unsecure locations
I think this is more clearly now.
Sent from my GT-I9000 using xda app-developers app
nmvp said:
Thanks for trying to help me.What i mean with unknown sources is an option in Android settings - Security-allow programs install from unsecure locations
I think this is more clearly now.
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
That setting in android has nothing to do with flashing a recovery from fast boot. Can you get to fastboot? Yes? Then you can flash a recovery from a PC.
there a new update rolling just wait
it may fix your problem first go back to stock
Yes i can use fastboot but if i try to flash a .IMG recovery it gives me always error, but if i flash stock blob files it goês OK .That's why i thougt that was necessary to enable install apps from unsecure locations.
OK i went to stock but touch screen still not working.
try cold booting 2 times
Tryed cold boot 5 times.Didn't work.I think that the problem is with painel driver .I want to know if driver is loaded with ROM or not.
This is solved. I sent the tablet to ASUS and they despite being unlocked, solved the problem without any cost, because it was not a root cause
that this happened, and activated the Asus warranty. I must say they were very honest and professional.
Congratulations ASUS.:good:
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.
Hi,
Sorry for the noob question here, I've managed to get myself very confused as to the state of my tf700t.
Some time ago I unlocked my bootloader and rooted my device (stock ROM with su I believe) and installed TWRP. All was well, but of course I couldn't get Android 4.2 OTA, so given I don't really use root much I decided to try to get back as close to stock as possible. I downloaded the 10.4.4.20 firmware from Asus and flashed it in using TWRP, so far so good.
Still no option to OTA, so I figured I would download and flash 10.6.1.14 instead and do the same thing, but I have problems! If I boot into recovery, instead of TWRP I get the android logo with the open door and spinning blue icosahedron. Poor old android then keels over backwards with an open chest and an alert sign. The tablet then reboots normally.
Question 1: Have I overwritten my recovery when I flashed the stock ROM? - I'm not sure if the ROMs should even overwrite the recovery partition; if this shouldn't happen, are there any clues as to what I have done?
The system actually recognises that I have 10.6.1.14 on my SD card and offers to install it, but that reboots and gives me the same dead android lying on his back. Question 2: Could this be related to the (broken?) recovery image, or could it just be a duff download of the firmware?
I suppose the bug question is how should i proceed? Should I look for a way to re-root the device, reinstall TWRP (maybe using goomanager) and flash again or am I just hopelessly misunderstanding where I am? Many thanks for any steers you chaps can offer.
Anatosuchus said:
Hi,
Sorry for the noob question here, I've managed to get myself very confused as to the state of my tf700t.
Some time ago I unlocked my bootloader and rooted my device (stock ROM with su I believe) and installed TWRP. All was well, but of course I couldn't get Android 4.2 OTA, so given I don't really use root much I decided to try to get back as close to stock as possible. I downloaded the 10.4.4.20 firmware from Asus and flashed it in using TWRP, so far so good.
Still no option to OTA, so I figured I would download and flash 10.6.1.14 instead and do the same thing, but I have problems! If I boot into recovery, instead of TWRP I get the android logo with the open door and spinning blue icosahedron. Poor old android then keels over backwards with an open chest and an alert sign. The tablet then reboots normally.
Question 1: Have I overwritten my recovery when I flashed the stock ROM? - I'm not sure if the ROMs should even overwrite the recovery partition; if this shouldn't happen, are there any clues as to what I have done?
The system actually recognises that I have 10.6.1.14 on my SD card and offers to install it, but that reboots and gives me the same dead android lying on his back. Question 2: Could this be related to the (broken?) recovery image, or could it just be a duff download of the firmware?
I suppose the bug question is how should i proceed? Should I look for a way to re-root the device, reinstall TWRP (maybe using goomanager) and flash again or am I just hopelessly misunderstanding where I am? Many thanks for any steers you chaps can offer.
Click to expand...
Click to collapse
The stock Asus firmware includes bootloader, kernel, recovery and apps. You have flashed the stock recovery. Head over to the twrp thread or my ROM thread in my sig to see how to get twrp 2.5 onto your tab.
Anatosuchus said:
Hi,
Sorry for the noob question here, I've managed to get myself very confused as to the state of my tf700t.
Some time ago I unlocked my bootloader and rooted my device (stock ROM with su I believe) and installed TWRP. All was well, but of course I couldn't get Android 4.2 OTA, so given I don't really use root much I decided to try to get back as close to stock as possible. I downloaded the 10.4.4.20 firmware from Asus and flashed it in using TWRP, so far so good.
Still no option to OTA, so I figured I would download and flash 10.6.1.14 instead and do the same thing, but I have problems! If I boot into recovery, instead of TWRP I get the android logo with the open door and spinning blue icosahedron. Poor old android then keels over backwards with an open chest and an alert sign. The tablet then reboots normally.
Question 1: Have I overwritten my recovery when I flashed the stock ROM? - I'm not sure if the ROMs should even overwrite the recovery partition; if this shouldn't happen, are there any clues as to what I have done?
The system actually recognises that I have 10.6.1.14 on my SD card and offers to install it, but that reboots and gives me the same dead android lying on his back. Question 2: Could this be related to the (broken?) recovery image, or could it just be a duff download of the firmware?
I suppose the bug question is how should i proceed? Should I look for a way to re-root the device, reinstall TWRP (maybe using goomanager) and flash again or am I just hopelessly misunderstanding where I am? Many thanks for any steers you chaps can offer.
Click to expand...
Click to collapse
Yes, you did. Everytime you install stock file of any version, it will update your bootloader, rom, and kernel. Just use Motochopper to root your device and reinstall your custom recovery with goomanager.
No, it is stock recovery. Just reroot with motochopper and install custom recovery with goomanager. Have fun. :good:
Right, thanks! If I want to stay completely stock I just need to figure out why the newer update is failing. Could be the file name now I think about it.
Otherwise I'll re-root and re-TWRP...
Anatosuchus said:
Hi,
Sorry for the noob question here, I've managed to get myself very confused as to the state of my tf700t.
Some time ago I unlocked my bootloader and rooted my device (stock ROM with su I believe) and installed TWRP. All was well, but of course I couldn't get Android 4.2 OTA, so given I don't really use root much I decided to try to get back as close to stock as possible. I downloaded the 10.4.4.20 firmware from Asus and flashed it in using TWRP, so far so good.
Still no option to OTA, so I figured I would download and flash 10.6.1.14 instead and do the same thing, but I have problems! If I boot into recovery, instead of TWRP I get the android logo with the open door and spinning blue icosahedron. Poor old android then keels over backwards with an open chest and an alert sign. The tablet then reboots normally.
Question 1: Have I overwritten my recovery when I flashed the stock ROM? - I'm not sure if the ROMs should even overwrite the recovery partition; if this shouldn't happen, are there any clues as to what I have done?
The system actually recognises that I have 10.6.1.14 on my SD card and offers to install it, but that reboots and gives me the same dead android lying on his back. Question 2: Could this be related to the (broken?) recovery image, or could it just be a duff download of the firmware?
I suppose the bug question is how should i proceed? Should I look for a way to re-root the device, reinstall TWRP (maybe using goomanager) and flash again or am I just hopelessly misunderstanding where I am? Many thanks for any steers you chaps can offer.
Click to expand...
Click to collapse
The Android on his back is your stock recovery and it does not find a valid update file.
Weird is, that your system seems to see the 10.6.1.14 file (I assume you get an automatic notification and click "install" or "update" ) and then the recovery does not seem to install it...?
You could have a bad download, so try that first if you want to get the latest stock rom, or you can try to rename the downloaded file to EP201_768_SDUPDATE.zip, put it on your microSD card and reboot into recovery. The recovery should recognize the update file and start flashing it.
But since you are unlocked anyway - why don't you give CromiX a try? It runs so much better than the stock rom!
And for that, yes you would have to root again using the Motochopper tool and then install TWRP 2.5 with Goo Manager.
If you go that route make sure you flash the latest bootloader from the OP of the CROMiX thread first, boot back into your old rom once before you flash CROMiX.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Alright, I'm convinced - I'll try going totally custom! Presumably CromiX handles the external keyboard and touch pad properly?
Anatosuchus said:
Alright, I'm convinced - I'll try going totally custom! Presumably CromiX handles the external keyboard and touch pad properly?
Click to expand...
Click to collapse
It's based on the stock rom, cleaned up and tweaked and optimized. Everything works - and better than on stock! I recommend selecting the option to disable fsync during installation. It boosts performance considerably, and since the rom is totally stable, the "risk" is neglible.
You will love it!
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
OK, ChromiX installed! Looks interesting already, will tinker with it over the next couple of days.