Firstly, I am complete noob when it comes to rooting and romming, and joined the forum in hopes of someone being able to help me.
I followed 'Frederuco's Guide to Root and ROM' my tf101.
This worked well and I successfully rooted my device.
My problem started when I tried to be a smartass and load on different ROMs.
Using TWRP I pushed all the wipe options possible and then turned off the device.
When I rebooted it there was no OS at all and I couldn't load anything because it didn't see my microSD card (which is where I'd put the recovery stuff).
OK I thought, I'll use Easyflasher and re-install stock android. Obviously I didn't follow those instructions correctly because that made the problem worse, and now there is no TWRP either, and all the computer sees is 'Android phone' 'APX Transformer Interface' in the device manager. There is nothing useful in the USB host controllers section of device manager (i.e. no nvidia boot recovery).
So, I seem to have a device that is completely blank - no OS, no recovery, and possibly no bootloader either.
I am hoping someone can possibly provide me with some easy to follow (idiot-proof) instructions to bring my device back to life, as I have a sinking feeling that I've completely wrecked my tf101.
EasyFlasher will still recover your device as long as you can enter APX. Post any errors/warnings/problems you may be having while flashing and people will be able to help.
Lethe6 said:
EasyFlasher will still recover your device as long as you can enter APX. Post any errors/warnings/problems you may be having while flashing and people will be able to help.
Click to expand...
Click to collapse
Here is what comes up:
On computer:
Easyflasher 0.8.3
>Extracting blob archive..
>Blob extracted!
>Blob size 4054.07421875kb
Running Wheelie..
>Tablet is now ready for Nvflash
>Extracting from blob...
>Cleaning up before flashing...
>Checking file sizes
>SOS size 0kb
>APP size 0kb
>EBT size 0kb
>LNX size 4054kb
Done!
(A separate window opened that said formatting partitions - it got to 16 I think, then said it was extracting some things, then it went away.)
On tablet it says this:
Entering NvFlash recovery mode / Nv3p Server
Chip Uid: 03806245434033d7
!!!!!phone update success!!!!!!
So what do I do next?
It should reboot the device into the stock firmware. Did you grab it from the Asus website?
Lethe6 said:
It should reboot the device into the stock firmware. Did you grab it from the Asus website?
Click to expand...
Click to collapse
I got the firmware from one of the forums on here. It is stock kernel ics 9.2.1.17. When I unplug the tablet and try to reboot it doesn't do anything.
try booting back into recovery and see if its still there.
U did know you can change between internal sd and your external micro sd with TWRP? - just incase
Get the actual firmware from Asus. I wouldn't trust a random firmware from the forums. Make sure you get the right version too (WW or US).
Noob listen, patience is a virtue, so read allvthe instructions and comments below before you jump into something, otherwise this is what happens.
Now coming to easy flasher download asus firmware from asus (no third party link), flash it and again wait till its completely finished. Once its done, restart and you are good... Let it boot up, then if you want then use easy flasher to root and install twrp again.
BTW 1st time when you wiped using twrp all you needed to do was remove micro SD, reload the ROM onto it and flash the ROM... Anyway that's an old story now
Good luck,
REMEMBER: ALWAYS READ THE FORUM AND COMMENTS
Sent from my Transformer TF101 using xda app-developers app
Depending on your tablet serial you might be able to recover in APX mode using an NVFlash ROM
http://www.xdafileserver.nl/Files/A...OMS/ICS .27/NVFLASH_ICS_9.2.1.27_WW_NOROOT.7z
Thank you one and all for your help!
udupa82 said:
Noob listen, patience is a virtue, so read allvthe instructions and comments below before you jump into something, otherwise this is what happens.
Now coming to easy flasher download asus firmware from asus (no third party link), flash it and again wait till its completely finished. Once its done, restart and you are good... Let it boot up, then if you want then use easy flasher to root and install twrp again.
BTW 1st time when you wiped using twrp all you needed to do was remove micro SD, reload the ROM onto it and flash the ROM... Anyway that's an old story now
Good luck,
REMEMBER: ALWAYS READ THE FORUM AND COMMENTS
Sent from my Transformer TF101 using xda app-developers app
Click to expand...
Click to collapse
Thank you all so much for your help. I have managed to get it working again.
Would someone be able to direct me to an easy to follow forum link to upgrade my transformer to Jellybean using Cyanogen please with idiot-proof instructions?
Many thanks again.
To answer why the previous things didn't work, If you look at easyflasher's first log it shows the SOS and APP partitions as 0kb, and it looks like you were just flashing a kernel, not the whole os.
The SOS is recovery and APP is the full os, so in the future make sure that you are nvflashing / flashing the right zip.
Also from the op if I read it right your tablet got wiped because you wiped it in recovery then turned it off without first flashing the rom.zip.
Go ahead and use my PERI 1-click root tool or another 1-click (easyflasher etc...) to get recovery on there again. Then put the ROM.zip file you want on the tf, go into recovery and wipe cache, data/factory reset, and Dalvik-cache. then Install the rom.zip from sdcard/internal (SD preferred, if the rom is on the sd card I recommend formatting data too..)
Then reboot and it should boot into shiny new JB.
Related
I read some posts about how to downgrade the transformer's firmware, but these were all pretty old and when I followed these steps they didn't work. I was wondering if it is still possible to downgrade from 3.2 to 3.1 build 8.4.4.11.
Thanks
one way would be to follow eepad unroot thread to go back to stock 8.4.4.5 and do microSD card update to stock 8.4.4.11
Which recovery do you have?
There is an update for 8.4.4.11 on the ASUS website. This is NOT the OTA udpate. This is a zipped blob that you can flash from the stock recovery. If you are rooted with CWM, I think it might flash through the staging partition.
gee one said:
Which recovery do you have?
There is an update for 8.4.4.11 on the ASUS website. This is NOT the OTA udpate. This is a zipped blob that you can flash from the stock recovery. If you are rooted with CWM, I think it might flash through the staging partition.
Click to expand...
Click to collapse
I have the stock recovery.
I think you can download the 84411 update from the ASUS website and flash it with the stock recovery.
It is not the OTA, but a full system that will over-write your system files. I think you unzip the file and copy the whole ASUS folder to your SD card. Insert your SD card and it will recognize and prompt you for the update. To be clear, you should have something like /ASUS/Update/US_eeepad....8.4.4.11.zip on your sdcard. It will recognize it when it is inserted.
Double check this and flash at your own peril.... it might not let you downgrade, in which case, there are 2 unroot guides in the dev section.
i want to do this, is the SD card 100% needed? i dont have one right now
Sorta- the sdcard would make it easy, but I think you could extract the pieces and flash them via nvflash.
If you are rooted, you can "flash" them via adb by copying the blob onto the staging partition.
why downgrade? it not needed to root or anything, so am i missing someting?
Have you tried nvflash? That seems to be the best way, but be sure to backup data, I got titanium backup and coped the data to my sdcard
Sent from my revolver!
since few weeks ago my TF its been having problem of deep sleeping and will turn on whenever he wants or when battery has 0% but my friend TF which is stock and bought from the same place and time i did still has 3.1 8.4.4.5.2 build is just fine so i wanted to try downgrading
You might also consider reflashing the ROM you are using now. I did notice some odd SOD issues from a bad flash. I had other issues as well- the screen would dim if I tried to follow a link in an email. I forget the actual cause, but it was fixed when I reflashed the right parts back in.
sorry im kinda newb about this.... how do i know what kind of ROM im using and how do i reflash it?
xtonyx06 said:
sorry im kinda newb about this.... how do i know what kind of ROM im using and how do i reflash it?
Click to expand...
Click to collapse
There is no exact method of knowing, but you can looking in settings/about tablet and look at the kernel version and build number. Then cross reference them with this thread. You might have a custom rom, in which case it might have the name in the build number.
You might have a bad flash. You could try charging the batttery completely (overnight) and then reflashing. If you are having issues, it might be easier to flash a custom ROM such as Prime 1.9.
http://forum.xda-developers.com/showthread.php?t=1251044
Be sure to back up any important data since nvflash will erase everything.
I searched this forum a bit and I can't find a nice guide. I am currently running rooted .19 on my TF101, B70KAS. Is it as simple as dropping the ROM on my internal SD and letting it update to the latest Revolver release (based on .21)? Or can I do it with booting into recovery mode? This is my first tablet and I have no clowworkmod on my tablet... do I need to flash that somehow? Where's a guide?
thanks!
ninjai117 said:
I searched this forum a bit and I can't find a nice guide. I am currently running rooted .19 on my TF101, B70KAS. Is it as simple as dropping the ROM on my internal SD and letting it update to the latest Revolver release (based on .21)? Or can I do it with booting into recovery mode? This is my first tablet and I have no clowworkmod on my tablet... do I need to flash that somehow? Where's a guide?
thanks!
Click to expand...
Click to collapse
Since i am firm believer you need to learn what you are doing i will lay down the basics from there you are on your own.
1) read and study SU access
2) read and study SU access
3) read and study SU access
4) root
5) install clockwork recovery
6)download Revolver
7)verify the MD5SUM
8)boot into recovery
9)do a nandroid back up
10) do a factor reset via CWRI
11) flash the OS you want
12) reboot
13) enjoy
neidlinger said:
Since i am firm believer you need to learn what you are doing i will lay down the basics from there you are on your own.
1) read and study SU access
2) read and study SU access
3) read and study SU access
4) root
5) install clockwork recovery
6)download Revolver
7)verify the MD5SUM
8)boot into recovery
9)do a nandroid back up
10) do a factor reset via CWRI
11) flash the OS you want
12) reboot
13) enjoy
Click to expand...
Click to collapse
I am very familiar with CWM, flashing, nandroid backups, etc. I've had a nexus one for a long long time. I just can't find any good stickies on how to install CWM on my tablet, which I assume is my first step, though I find it odd there are no stickies. On the Nexus One forum there are lots! Where can I learn about installing CWM on my tablet with stock (but rooted) .19 FW?
ninjai117 said:
I am very familiar with CWM, flashing, nandroid backups, etc. I've had a nexus one for a long long time. I just can't find any good stickies on how to install CWM on my tablet, which I assume is my first step, though I find it odd there are no stickies. On the Nexus One forum there are lots! Where can I learn about installing CWM on my tablet with stock (but rooted) .19 FW?
Click to expand...
Click to collapse
Search for RecoveryInstaller in the Themes and Apps section.
One click CWM installer, don't get any easier than that.
I had the Same issue coming from the nexus s. the tricky bit is that rom manager does not support the transformer. I've got a galaxy tab 10.1 as well and flashing over a custom recovery was easy as pie.
anyway, what you have to do is this: http://forum.xda-developers.com/showthread.php?t=1213723
(http://forum.xda-developers.com/showthread.php?t=1093818)
then you need to install an app (i use reboot2recovery) from the marketplace to get into the custom recovery. i've tried quickboot or rom manager but all it does it take me to a black screen or reboot the device. reboot2recovery will actually drop you into clockworkmod recovery. from there, do your nandroid backup. you'll need an SD card in your transformer for it to actually go ahead with the backup.
aside: from my reading, the backup should backup to internal storage with that modded clockwork. i've never been able to get it to work though. anyway, just use an SD card for now so you can get through the difficult stuff.
so at this point uve done the following:
installed clockwordmod using the first 2 links and installed the reboot2recovery APK to get into recovery.
now you have an SD card in your transformer and you are doing a nandroid backup.
once completed, put the 200+mb revolver rom on the root of your SD card. you may also want to put another kernel. i use the one recommended by revolver.
now just wipe the cache, data, etc as usual. now flash the rom, reboot the system when completed. plug in your gmail account, wifi password etc. and then reinstall the reboot2recovery apk. now reboot to recovery and then flash the kernel. reboot and ure good to go. install revolver parts to allow for additional tweaking and OTA updating.
i got my transformer from bestbuy this thanksgiving and went to revolver 3.9.5 immediately. last night i actually flashed revolver 3.11 right over it. not a single problem.
edit: reading the above post, i remember that my FIRST recovery installation was using that one-click tool and, as was said, it works flawlessly. you still need the reboot2recovery though. and recoveryinstaller WILL NOT install the modified for internal storage version of clockwork. i'm thinking maybe i just havent tried backing up since updating to the internal storage version, which is why i think i've "never gotten it to work"
baseballfanz said:
Search for RecoveryInstaller in the Themes and Apps section.
One click CWM installer, don't get any easier than that.
Click to expand...
Click to collapse
Awesome, I had tried it earlier and it didn't do anything. Then I realized that my superuser app was FCing, however I could still use adb shell and su just fine! After I realized there was an update for the superuser app, I installed it. Everything is perfect now.
kramer987 said:
I had the Same issue coming from the nexus s. the tricky bit is that rom manager does not support the transformer. I've got a galaxy tab 10.1 as well and flashing over a custom recovery was easy as pie.
anyway, what you have to do is this: http://forum.xda-developers.com/showthread.php?t=1213723
(http://forum.xda-developers.com/showthread.php?t=1093818)
then you need to install an app (i use reboot2recovery) from the marketplace to get into the custom recovery. i've tried quickboot or rom manager but all it does it take me to a black screen or reboot the device. reboot2recovery will actually drop you into clockworkmod recovery. from there, do your nandroid backup. you'll need an SD card in your transformer for it to actually go ahead with the backup.
aside: from my reading, the backup should backup to internal storage with that modded clockwork. i've never been able to get it to work though. anyway, just use an SD card for now so you can get through the difficult stuff.
so at this point uve done the following:
installed clockwordmod using the first 2 links and installed the reboot2recovery APK to get into recovery.
now you have an SD card in your transformer and you are doing a nandroid backup.
once completed, put the 200+mb revolver rom on the root of your SD card. you may also want to put another kernel. i use the one recommended by revolver.
now just wipe the cache, data, etc as usual. now flash the rom, reboot the system when completed. plug in your gmail account, wifi password etc. and then reinstall the reboot2recovery apk. now reboot to recovery and then flash the kernel. reboot and ure good to go. install revolver parts to allow for additional tweaking and OTA updating.
i got my transformer from bestbuy this thanksgiving and went to revolver 3.9.5 immediately. last night i actually flashed revolver 3.11 right over it. not a single problem.
edit: reading the above post, i remember that my FIRST recovery installation was using that one-click tool and, as was said, it works flawlessly. you still need the reboot2recovery though. and recoveryinstaller WILL NOT install the modified for internal storage version of clockwork. i'm thinking maybe i just havent tried backing up since updating to the internal storage version, which is why i think i've "never gotten it to work"
Click to expand...
Click to collapse
none of those gives a step by step (im noob )
i just dont know what "Reboot into recovery using "adb reboot recovery" " means
im already rooted and i cant get to the CWM recovery because i cant see the install from zip, backup current rom or wipe data , nor those options
jesesystem said:
none of those gives a step by step (im noob )
i just dont know what "Reboot into recovery using "adb reboot recovery" " means
im already rooted and i cant get to the CWM recovery because i cant see the install from zip, backup current rom or wipe data , nor those options
Click to expand...
Click to collapse
It mean open your command prompt in your computer fire up the ADB server and type
Code:
adb reboot recovery
Why why not download the reboot recovery app from the market?
https://market.android.com/details?id=com.transformer.recovery
Sent from my Transformer TF101 using Tapatalk
jesesystem said:
none of those gives a step by step (im noob )
i just dont know what "Reboot into recovery using "adb reboot recovery" " means
im already rooted and i cant get to the CWM recovery because i cant see the install from zip, backup current rom or wipe data , nor those options
Click to expand...
Click to collapse
Have you installed CWM recovery?
Rooting alone does not install CWM recovery.
jesesystem said:
none of those gives a step by step (im noob )
i just dont know what "Reboot into recovery using "adb reboot recovery" " means
im already rooted and i cant get to the CWM recovery because i cant see the install from zip, backup current rom or wipe data , nor those options
Click to expand...
Click to collapse
Search for RecoveryInstaller in the Themes and Apps section.
One click CWM installer, don't get any easier than that.
thank you guyz i just needed to install cwm recovery, its just that those steps are not on any step by step , i can access now in to cwm recovery
Once in recovery it cant mount sd
SGS Dutchie said:
Once in recovery it cant mount sd
Click to expand...
Click to collapse
You have a micro sd card insert into the slot?
baseballfanz said:
You have a micro sd card insert into the slot?
Click to expand...
Click to collapse
Nope,thought it was the internal sd just like is shown in file explorer.
SGS Dutchie said:
Nope,thought it was the internal sd just like is shown in file explorer.
Click to expand...
Click to collapse
CWM only work with external card for now
Removable/MicroSD
baseballfanz said:
CWM only work with external card for now
Removable/MicroSD
Click to expand...
Click to collapse
Ah, I must go and search for one then.
baseballfanz said:
CWM only work with external card for now
Removable/MicroSD
Click to expand...
Click to collapse
Thx man, you really helped me out today. First with my root/cwm problem and now with this rom.
You really are a great help. Thx again!
I'll preface this by saying the following:
I know there are a lot of brick guides out there, and most are relatively easy to get out of. I've worked myself into a bit of a pickle, though.
It started when I noticed that there was an update available through the CM updater. I figured, what the hell, I'm running a nightly and this is likely to be a stable release, so I went ahead and downloaded it. I got home and checked the get.cm page, and sure enough, a new, stable build had recently been released. Being the diligent soul that I am, I made sure to do a full backup before I installed the .zip. Everything worked out just fine, the backup went swell, the update finished without problems, and then I rebooted my device.
All I see is the Asus splash screen. It just stays there. So I think, no big deal, it just didn't work out like I wanted, I'll go format my data (which I didn't do the first time around, in hopes that everything would carry over) and install again. The same thing happens. I haven't started panicking yet, since I still have 3 backups (1 older Jellybean, and one much older ICS). None of them work. I wipe everything that I can think might help. Data, system, cache, dalvik, you name it. Nothing was working, and I was starting to freak out. Then I decided to try to get some action through fastboot, hoping that I could push a .zip that wasn't the CM10 update that had started everything. In my search for a push command, I thought it would be a good idea to try a wipe from fastboot. This wiped everything. Not only the system, boot, etc. partitions, but also my personal partition that had all of my data. This in itself isn't a big problem, but it also left the partitions unformatted. Now I have a device that is devoid of data and can't do anything but get into CWM and fastboot.
What the hell can I do? Am I doomed? Is there no way to get out of the hole I've dug myself into?
tl;dr failed update, things got really real, really fast.
Specs before the initial update
ROM: CM10 nightly, Jellybean 4.1.x
CWM: 5.5.0.4
Kernel Version (?): 9.4.3.30-20120604 (I'm not sure with this, it says something about "android carhu-user" before it)
same thing just happened to me. Im going to download another version of CM and try that. It might just be that.
DerangedLoofah said:
same thing just happened to me. Im going to download another version of CM and try that. It might just be that.
Click to expand...
Click to collapse
That's the thing, though, I have no idea how I'm supposed to get it to my device now...
http://forum.xda-developers.com/showthread.php?t=1989076
Have you tried this? I was just thinking about it because I can't reflash my recovery and thought this may be the way to start over.
OK I downloaded the us jb update and extracted to my external SD card and flashed it in recovery after wipes. Everything is good now.
Edit: flash recovery in fast boot.
Sent from my SCH-I535 using Tapatalk 2
Glad you got it!
nitsuj79 said:
Glad you got it!
Click to expand...
Click to collapse
DerangedLoofah managed to get it, but I still haven't had any luck.
DerangedLoofah said:
OK I downloaded the us jb update and extracted to my external SD card and flashed it in recovery after wipes. Everything is good now.
Edit: flash recovery in fast boot.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
How did you flash it in fastboot? I can't figure out how to get to something that's on the external SD card. What were the exact commands you used?
1. Download any software from this topic http://forum.xda-developers.com/show....php?t=1697227
2. Unpack it one so you have a zip without UpdateLauncher
3. Rename the zip to EP201_768_SDUPDATE.zip
4. Put on a sdcard into the root (the sdcard should be clean, no other files)
5. Boot you tablet to RCK (Volume down + power, then volume up)
6. Let the magic begin!!! Take some minutes.
Attention! JB user pleas choose a JB ROM, don't flash ICS ROM on JB bootloader.
You tried this method with no love? I was able to flash stock pretty easily doing this.
nitsuj79 said:
1. Download any software from this topic http://forum.xda-developers.com/show....php?t=1697227
2. Unpack it one so you have a zip without UpdateLauncher
3. Rename the zip to EP201_768_SDUPDATE.zip
4. Put on a sdcard into the root (the sdcard should be clean, no other files)
5. Boot you tablet to RCK (Volume down + power, then volume up)
6. Let the magic begin!!! Take some minutes.
Attention! JB user pleas choose a JB ROM, don't flash ICS ROM on JB bootloader.
You tried this method with no love? I was able to flash stock pretty easily doing this.
Click to expand...
Click to collapse
Does that work with CWM? I don't have the stock bootloader on it.
This works only if you didn't flash custom recovery, it is the best method for locked devices. But you can still flash any stock ROM from CWM (but I suggest to use TWRP, you can install it from external sd). And you can push the ROM to internal memory via adb. I think you can install stock ROM via fastboot too, I am not sure, but the command fastboot update should help.
I managed to get it working again. If you can get to fastboot, push a bootloader that supports an external SD cards (like TWRP) and then from that install one of the official ASUS firmwares. From there, you have to root again, but it's better than having a device that won't boot at all.
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.