[Q] [HELP] TF101 Loop while starting - Eee Pad Transformer Q&A, Help & Troubleshooting

Hi all !
First my apology for the reason of those words. I'm an Android-noob
Well I've Rooted my TF101 with EasyFlasher, it's a good thing, installing RogueXM Touch v1.5.0-R1 Recovery.
I launched an AOKP JB milestone 1 and it was well installed.
But I did a mistake, I didn't done a NAND backup.
Now when I try running my TF101, it starts, and run the AOKP JB Milestone 1, but no keyboard, no configuration, well I'm stuck there. Anyway I reboot in recovery trying install another rom pushing file into it by ADB.
Nothing works
I can't reflash Stock rom, EasyFlasher tall me that's ok but when I boot the TF101 I'm always return under AOKP
I don't know who could I flash the Stock rom to be able to repair this $*%£ tablet
If someone has a clue ?
Thank you

[Q] means you should post it in Q&A.
This is the development forum.

sorry I just realize I'm not in the good forum

Since you cannot boot, there are really only 2 options:
Use ADB when in recovery to unbrick (Push new ROM to flash, use the dd command to install a different recovery) - also, be sure to update to the Naked Drivers for ADB for it to work best.
Use APX mode and EasyFlasher or NVFlash to push the stock ROM or a different recovery.
I HIGHLY recommend using TWRP for recovery, it can see the internal and external microSD (FAT32 only).

Moved to correct board.

frederuco said:
Since you cannot boot, there are really only 2 options:
Use ADB when in recovery to unbrick (Push new ROM to flash, use the dd command to install a different recovery) - also, be sure to update to the Naked Drivers for ADB for it to work best.
Use APX mode and EasyFlasher or NVFlash to push the stock ROM or a different recovery.
I HIGHLY recommend using TWRP for recovery, it can see the internal and external microSD (FAT32 only).
Click to expand...
Click to collapse
Well I did that.
But I had big troubles to win
I flashed ics_92117_WW_stock_EBT_SOS.zip and then the AOKP JB Milestone who's working perfectly

Related

[Q] How do I install stock recovery on my SBKv2 TF101?

Hello,
I flashed CWM on my tablet but it is encrypted. I need to decrypt it to be able to flash new ROMs. The problem is that I cant wipe it with CWM because of the encryption .
Where can I find the stock recovery for my WW B80 TF101 with stock ICS ?
I did find a US recovery for Honeycomb on the Unlockr, but I'm not sure if that would work.
I can't use NVFlash since it's SBKv2 either .
I'd appreciate any help I can get on this. Thanks for a great forum, I've had a lot of help here before with my old Windows Phones .
/rodstrom
rodstrom said:
Hello,
I flashed CWM on my tablet but it is encrypted. I need to decrypt it to be able to flash new ROMs. The problem is that I cant wipe it with CWM because of the encryption .
Where can I find the stock recovery for my WW B80 TF101 with stock ICS ?
I did find a US recovery for Honeycomb on the Unlockr, but I'm not sure if that would work.
I can't use NVFlash since it's SBKv2 either .
I'd appreciate any help I can get on this. Thanks for a great forum, I've had a lot of help here before with my old Windows Phones .
/rodstrom
Click to expand...
Click to collapse
What version of CWM recovery do you have and how did you flash it?
The stock recovery from the unlocker.com need to be flash via CWM, since you say you can't use your CWM that's useless.
Have you tried installing a different CWM recovery?
Here you can find Roach's 3.2.0.1 and Team Rouge CWM recovery.
(both are install via RecoveryInstaller)
http://forum.xda-developers.com/showpost.php?p=22359727&postcount=218
What do you mean by "encrypted"?
What are the errors you see when you try to wipe data on this device?
What is the CWM version you are using?
Perhaps someone will correct me, but a properly installed recovery does not care about data encryption to be able to format the partition (i.e. wipe). Stock recovery will not help in this. It will simply remove all the useful commands and interfaces and show a nice picture of a dead droid.
I can flash things trough CWM but CWM cant see the sdcard since its encrypted trough honeycomb/ics builtin encryption setting. If I find the right recovery I would be able to flash it . If I try to factory reset from settings it does absolutely nothing since it tries to boot into stock recovery . Factory reset from cwm does nothing since cwm cant touch the encrypted sdcard .
I've read that no CWM can touch the encrypted partition since it doesnt have the password. Only stock recovery can wipe an encrypted tablet. Other than my cwm cant wipe encrypted tablets it works fine for me. I can flash other roms but they are completely useless since they cant read my encrypted drive.
Does someone know if it matters if I use the US recovery for honeycomb? Or where I can find the recovery for tf101 ics ww.
Ps . Im sorry if this post seems like a mess, I'm really tired and my soft keyboard sucks.
your only choice in your case is if it's CWM 3.2.0.1 is to take your SD card out of your tablet use a card reader and FORMAT your Card FAT32 then save the roms you want to it then boot back in to CWM and it will see them after that
if you have the newer CWM with the Blue controls is Will not use the MicroSD CARD
is uses Onboard Memory and your going to need to some how get ADB to see it.
install android dev kit and send a few commands so CWM can see the microSD card. it's very much like fixing recovery bootloop.
i know your pain i own B50 (SBkv1) B70 & B80 (both SBKv2) and a prime
Did you try the team eos superwipe?
Also I think he is talking about the internal sd and not the micro.
Sent from my Transformer TF101 using Tapatalk
ok here is what i did for my boot loop i did to figure this one out with encryption on
only Do this IF you have ADB working
Get in to Recovery and Format your Partations Then reboot to recovery a 2nd time
and do a adb push i pushed (Team Rouge CWM Recovery) But in your Case
pushing TF101 Rooted Stock 9.2.1.17 + bootloader + modded recovery
http://forum.xda-developers.com/showthread.php?t=1552303
Might be best as it will fix and problems your having with recovery and switch it back to the MicroSD Card Slot for ROMS
after trying it i think i will Stick with TeamRouge Recovery
lots of guides around on how to setup ADB
rodstrom said:
I can flash things trough CWM but CWM cant see the sdcard since its encrypted trough honeycomb/ics builtin encryption setting.
Click to expand...
Click to collapse
What version of CWM do you have? If it's the 5.5.0.4 than it only read from the internal SD.
baseballfanz said:
What version of CWM do you have? If it's the 5.5.0.4 than it only read from the internal SD.
Click to expand...
Click to collapse
He means the internal mmc (the location of /data).
@rodstrom, if I understand you correctly, you are saying that once you encrypted your tablet (through an option in the security settings), you cannot wipe /data (or factory reset) through normal options in CWM or another recovery. You think that the only way to wipe data on an encrypted /data partition is through a stock recovery. Correct?
That sounds weird to me, but I have read similar comments in other places. If this is true, then the "encrypt tablet" option is a danger.
Have you tried to format /data using the CWM's "mounts and storage" menu? What was the result?
Have you tried what @Dreamboxuser suggested: the superwipe?
Can you try to format using adb commandline while in CWM?
feisty_noodle exactly!
I can't wipe from settings since it tries to reboot into stock recovery . And I can't wipe from CWM since the eMMC is inaccessible because of the encryption .
From CWMs "Mounts and storage" I am unable to format /data since it is inaccessible . It says something like that it cant read it...
I have not heard of the superwipe, but I'll have to google it. I haven't tried formatting through adb yet, but I'm not sure if that would help.
I'm pretty convinced that I need the stock recovery to wipe the eMMC .
feisty_noodle said:
He means the internal mmc (the location of /data).
Click to expand...
Click to collapse
OK, I misunderstood.
@rodstrom
The SuperWipe can be found in Revolution ROM thread.
Becareful using it, if you have a CWM version that read internal only such as 5.5.0.4, it will wipe all you files. I suggest using Roach's 3.2.0.1 or Team Rouge recovery if you're going to use SuperWipe script.
I had the Team Rouge recovery earlier. Although now I have 5.5 something and I can't do anything at all with it . How do I install Team Rouge again ? I tried the modded RecoveryInstaller but nothing happened , just a reboot .
Also I have to cold boot everytime it has turned off . I really need to change my recovery now , if not to stock then at least to something else than 5.5...
Bump,
I'm in trouble here, I have CWM 5.5.0.8 which can't read my external MicroSD, nor read my encrypted internal SD.
I can't flash anything now... What can I do? Is adb an option?
If I can't find my stock recovery I would at least like to have a useful recovery which can read my external MicroSD so I can do something at all.
Sent from my Transformer TF101 using XDA
rodstrom said:
Bump,
I'm in trouble here, I have CWM 5.5.0.8 which can't read my external MicroSD, nor read my encrypted internal SD.
I can't flash anything now... What can I do? Is adb an option?
If I can't find my stock recovery I would at least like to have a useful recovery which can read my external MicroSD so I can do something at all.
Sent from my Transformer TF101 using XDA
Click to expand...
Click to collapse
This member was successful in mounting his external sd with adb shell
http://forum.xda-developers.com/showthread.php?p=24007127
Hi again!
I'm back and I have tried to follow the post you linked. The problem now is that I can't seem to connect with adb when the device is in recovery mode. Adb works perfectly when booted normally though.
To mount trough adb in recovery mode seems to be exactly what I need, so if I can get adb running in CWM I believe this would be solved.
Maybe another possibility could be to change the mounts in CWM's init.rc before I reboot to CWM, but I don't know if it is possible, or where that file would be. What do you think?
restore stock recovery
I have a rooted TF101 with stock ROM and cwm recovery. I would like to restore stock recovery and keep the other things as is so that I can do OTA when its available. After did may search, I finally found a way and restored stock recovery
successfylly. I would like to sharte my experience with you:
1. The stock recovery is "8239USrecovery.zip". The file name is kind of misleading, but it actaully is a universal
stock recovery for TF101. See "Asus Transformer EPIC NOOB GUIDE."(http://forum.xda-developers.com/showthread.php?t=1494230)
2. The cwm 5504 as from market app "ROM MANAGER" has a "boot into recovery loop" bug. I changed to roach's cwm version
by
2.1 boot into cwm recovery and flash cwm_recovery-5504_roach-tf101-r2.zip.
2.2 cold boot, use terminal emulator to issue
su
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
2.3 reboot
3. boot into cwm recovery (roach's version), flash 8239USrecovery.zip and then reboot.
After reboot, cwm is gone.
I can't flash anything at all though, because of 5.5.0.4 only reading the internal sdcard which is encrypted.
If I could get adb working in CWM I could mount the external microsd and flash things again.
Is there any possibility to change CWM's mountpoints from within Android OS?
Sent from my Transformer TF101 using XDA

[Q] [q] ???help bricked maybe????

Hello, I believed I have an issue. Hope it not to serious. My problem is that i can't get passed the ASUS logo Splash screen.
1st: I was one stock jelly bean rooted cwm recovery v6.0.1.2 and decide I wanted to get on to Hydro 3.6 Jellybean (9/17)
2nd I downloaded the ROM wiped cache,delvic and factory reset then installed, didn't install at first so I tried a mirror and then it installed correctly restarted the tablet and here I am.
3rd: Tried clean rom 2.0 still no luck.
Please help I'm 15 and don't wanna break the bad news to my parents.
Ps: I am able to still boot into CWM recovery 6.0.1.2 tried everything nothing working and able to fastboot but cold boot and wipe data don't work and haven't shut off tablet since accident will remain on and charged.
jekovenatinsley said:
Hello, I believed I have an issue. Hope it not to serious. My problem is that i can't get passed the ASUS logo Splash screen.
1st: I was one stock jelly bean rooted cwm recovery v6.0.1.2 and decide I wanted to get on to Hydro 3.6 Jellybean (9/17)
2nd I downloaded the ROM wiped cache,delvic and factory reset then installed, didn't install at first so I tried a mirror and then it installed correctly restarted the tablet and here I am.
3rd: Tried clean rom 2.0 still no luck.
Please help I'm 15 and don't wanna break the bad news to my parents.
Ps: I am able to still boot into CWM recovery 6.0.1.2 tried everything nothing working and able to fastboot but cold boot and wipe data don't work and haven't shut off tablet since accident will remain on and charged.
Click to expand...
Click to collapse
It's just a softbrick. As long as you can get into fastboot you are ok.
I suggest reflashing the stock jellybean rom. You can download it from the asus website.
As for getting it into your device (i dont know if cwm supprots sd cards yet). You can use the adb push commands or you can flash twrp which supprots flashing from the sd card.
Also next time read the rom thread carefully. It specifically says you should use twrp.
Hey man try this, it works for me (Same situation but i'm 17 xD)
1) Download this http://www.mediafire.com/?5diezc69u1b16f8
2)Extract the "recovery1" folder in C:\ drive
3)Plug the tablet to PC and turn it on while pressing VOL- and POWER, then go to the fastboot mode (is the USB symbol)
4)Download from here ( http://support.asus.com/Download.asp...300T&p=20&s=16 ) the WW of US instead of the version of the tablet you have got, the extract the blob file in the "recovery1" folder
5)Open CMD, type cd c:\recovery1 then press enter
6)Type dir to see if all the files are in the folder
7)type this command fastboot -i 0x0B05 flash system blob
8)After is done, type fastboot -i 0x0B05 reboot
9)Enjoy!
If you can't do any of this steps, post here and I will help you
Fixed It!
ZerOMKD said:
It's just a softbrick. As long as you can get into fastboot you are ok.
I suggest reflashing the stock jellybean rom. You can download it from the asus website.
As for getting it into your device (i dont know if cwm supprots sd cards yet). You can use the adb push commands or you can flash twrp which supprots flashing from the sd card.
Also next time read the rom thread carefully. It specifically says you should use twrp.
Click to expand...
Click to collapse
Hey actually like 10 mins after I posted I was able to install Clean Rom.
I formated every partition except sd card in v6.0.1.2 cwm recovery as well as factory reset and wipe dalvik.
Actually I like cwm recovery better and it does support microsd cards now. This is the jb/touch bootloader.
Thanks for the Help anyways.
.
Same problem, when i try to flash JB Hydro 3.6... i stuck into bootloop... i flash the official asus update and it works... But when i try to flash the hydro rom it doesn't work.... Why?
I guess you have the new JellyBean Bootloader... because of that you can only flash ROM's which are made for it...
.
I know... i update from jb ota to hydro... but when i flash the 3.6 i got bootloop... and now i can flash this rom...

Bricked? Cant boot past Asus Screen

Hi guys, Im having a little Problem with my tf300. I've been running Baked 6 rom for a couple months and saw that version 7 was released which is full 4.2.1. Backed up, wiped, flashed, and rebooted.
Got stuck at Asus splash screen. unable to turn device off, it just turns right back on to the splash screen. I am able to hold volume down + power to get into TWRP recovery.
Restored back up, rebooted and still stuck on ASUS screen. Tried another backup with same result
Tried re-downloading rom copying it to external memory card and flashing again, still stuck at asus screen.
I am so lost here, not sure if i should throw this thing out the window, or get on my knees and pray.
any help is greatly appreciated.
I have googled the problem and have seen similar issues, but not anybody that can access recovery and still has the problem.
cavz903 said:
Hi guys, Im having a little Problem with my tf300. I've been running Baked 6 rom for a couple months and saw that version 7 was released which is full 4.2.1. Backed up, wiped, flashed, and rebooted.
Got stuck at Asus splash screen. unable to turn device off, it just turns right back on to the splash screen. I am able to hold volume down + power to get into TWRP recovery.
Restored back up, rebooted and still stuck on ASUS screen. Tried another backup with same result
Tried re-downloading rom copying it to external memory card and flashing again, still stuck at asus screen.
I am so lost here, not sure if i should throw this thing out the window, or get on my knees and pray.
any help is greatly appreciated.
I have googled the problem and have seen similar issues, but not anybody that can access recovery and still has the problem.
Click to expand...
Click to collapse
Are you sure to be still rooted ?
Simply question
If you aren't still root, just root again before to try some rom install
philos64 said:
Are you sure to be still rooted ?
Simply question
If you aren't still root, just root again before to try some rom install
Click to expand...
Click to collapse
sorry for the delay - thanks for the reply.
I dont know how to tell if im rooted from recovery.
So just went ahead and flashed the root file i found here:
http://www.androidgadgematic.com/2012/10/root-asus-transformer-pad-tf300-install-cwm.html
flashed Baked 7 and gapps again with same result.
(however i noticed at first reboot the asus screen shows a quick blue loading bar under center logo. then nothing.)
rebooted into TWRP - wiped - flashed root.zip again - restored backup.......asus screen.
another thing i noticed was when i try to install (flash) anything, it says no md5 found or if i select "force md5 check" it fails.
im a seasoned novice. I've gotten myself out of some sticky jams. but im totally lost here....
cavz903 said:
Hi guys, Im having a little Problem with my tf300. I've been running Baked 6 rom for a couple months and saw that version 7 was released which is full 4.2.1. Backed up, wiped, flashed, and rebooted.
Got stuck at Asus splash screen. unable to turn device off, it just turns right back on to the splash screen. I am able to hold volume down + power to get into TWRP recovery.
Restored back up, rebooted and still stuck on ASUS screen. Tried another backup with same result
Tried re-downloading rom copying it to external memory card and flashing again, still stuck at asus screen.
I am so lost here, not sure if i should throw this thing out the window, or get on my knees and pray.
any help is greatly appreciated.
I have googled the problem and have seen similar issues, but not anybody that can access recovery and still has the problem.
Click to expand...
Click to collapse
I suggest flash latest stock with twrp. You will loose twrp but with a working unit you can fastboot twrp again.
tobdaryl said:
I suggest flash latest stock with twrp. You will loose twrp but with a working unit you can fastboot twrp again.
Click to expand...
Click to collapse
thanks
ive looked around. but cant find a flashable stock download.
i did find a method to flash a blob via fastboot. but i dont know how to tell if i have a WW or a TW sku.(to DL firmware from asus site)
is TW for users in Taiwan? and WW for everybody else world wide?
cavz903 said:
thanks
ive looked around. but cant find a flashable stock download.
i did find a method to flash a blob via fastboot. but i dont know how to tell if i have a WW or a TW sku.(to DL firmware from asus site)
is TW for users in Taiwan? and WW for everybody else world wide?
Click to expand...
Click to collapse
The SKU versions on the asus firmware page, are as follows:
- US = USA
- CN = China
- TW = Taiwan
- WW = Worldwide
- DE = Germany
- JP = Japan
- TB = Belgium, Turkey, Luxembourg
But you can flash US or WW, they are compatible
philos64 said:
The SKU versions on the asus firmware page, are as follows:
- US = USA
- CN = China
- TW = Taiwan
- WW = Worldwide
- DE = Germany
- JP = Japan
- TB = Belgium, Turkey, Luxembourg
But you can flash US or WW, they are compatible
Click to expand...
Click to collapse
ok so, downloaded WW stock firmware from Asus site. flashed blob file via fastboot.
it said it finished "okay"
rebooted and, back at the Asus Screen.
and now i dont have recovery either. any suggestions?
thank you
any other ideas? im lost here... thanks
cavz903 said:
any other ideas? im lost here... thanks
Click to expand...
Click to collapse
This is normal. The stock blob contains stock recovery and is flashed over the recovery you have in place.
Time to reflash your twrp.
tobdaryl said:
This is normal. The stock blob contains stock recovery and is flashed over the recovery you have in place.
Time to reflash your twrp.
Click to expand...
Click to collapse
Ok so i will re-flash twrp via fastboot. but then what!? re-root via an update.zip? and flash a few custom rom? beacuse i am still stuck at the Asus boot screen.
cavz903 said:
Ok so i will re-flash twrp via fastboot. but then what!? re-root via an update.zip? and flash a few custom rom? beacuse i am still stuck at the Asus boot screen.
Click to expand...
Click to collapse
Flash the latest twrp (2.4.1.0). There were issues of using 4.2 and custom recoveries. That was the reason for the last two versions of twrp.
All custom roms here I have checked are pre rooted so the only time I flash root is with a stock rom.
If you were not already using twrp 2.4.1.0 then reflash your stock rom. Earlier versions might not flash the roms properly for 4.2. We need to get working first then you can flash your rom choice.
I hope your version of twrp is less than 2.4.1.0 because if not I'm lost at the moment. I'll be thinking and searching while you play.
Good Luck!
Note: Sorry I should have said twrp 2.4.1.0 JellyBean!
cavz903 said:
Ok so i will re-flash twrp via fastboot. but then what!? re-root via an update.zip? and flash a few custom rom? beacuse i am still stuck at the Asus boot screen.
Click to expand...
Click to collapse
How are you getting the roms onto your device to flash them, the TF300 doesn't have any external memory. Unless there is a way to push the file to the internal sdcard via fastboot, that I'm looking into right now, I dont understand how you are able to flash anything besides .img files or an update.zip.
flukeSG2 said:
How are you getting the roms onto your device to flash them, the TF300 doesn't have any external memory. Unless there is a way to push the file to the internal sdcard via fastboot, that I'm looking into right now, I dont understand how you are able to flash anything besides .img files or an update.zip.
Click to expand...
Click to collapse
Flash recovery with fastboot
fastboot -i 0x0B05 flash recovery recovery.img
fastboot -i 0x0B05 reboot
Note: recovery is in the directory with fastboot on the pc
Flash recovery with adb
adb shell
su
adb push twrp.blob /sdcard/twrp.blob
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4 Then reboot to complete installation.
adb reboot
Note: twrp.blob is in the directory with adb and fastboot on the pc and is copied to the sdcard
Flash recovery with android terminal
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
exit
Note: twrp.blob is on the sdcard
/sdcard as used here is an example – paths to both (internal or external) sdcards change with rom and you need to look at the proper path for the sdcard you wish to use. A root browser is what I use for this.
These are examples for the tf300 there are others.
Red text are actual commands typed!
Maybe this will help to explain the most commonly used methods.
Your internal and external sdcards are normally mounted when your tablet is plugged into your pc
I'm sorry I had to respond!
tobdaryl said:
Flash recovery with fastboot
fastboot -i 0x0B05 flash recovery recovery.img
fastboot -i 0x0B05 reboot
Note: recovery is in the directory with fastboot on the pc
Flash recovery with adb
adb shell
su
adb push twrp.blob /sdcard/twrp.blob
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4 Then reboot to complete installation.
adb reboot
Note: twrp.blob is in the directory with adb and fastboot on the pc and is copied to the sdcard
Flash recovery with android terminal
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
exit
Note: twrp.blob is on the sdcard
/sdcard as used here is an example – paths to both (internal or external) sdcards change with rom and you need to look at the proper path for the sdcard you wish to use. A root browser is what I use for this.
These are examples for the tf300 there are others.
Red text are actual commands typed!
Maybe this will help to explain the most commonly used methods.
Your internal and external sdcards are normally mounted when your tablet is plugged into your pc
I'm sorry I had to respond!
Click to expand...
Click to collapse
I apparently don't have drivers for adb for my tf300t. I have no problem with fastboot. I am able to successfully flash the recovery, but I am unable to push any data to my sdcard.
Without being able to fully boot my tablet, I'm not sure I can even get adb to work? If I install drivers for adb, won't I lose my fastboot capabilities that I currently have? My tablet shows up as a fastboot device in my device manager, would I just open it's properties and select new drivers for it?
My next idea is to get ahold of the system.img, boot.img and recovery.img from a rom to flash from fastboot. I can't seem to find these inside any roms I've downloaded yet, where would I find them? I am thinking I would prefer the latest stock asus rom if possible. I've downloaded the rom from Asus website, unzipped it and no .img files in it. I've also downloaded the rooted stock rom from xda here and also no .img files inside it. Does this even sound plausible, to flash those .img files from inside fastboot to make the tablet boot up?
Edit: Small side question, what exactly is "-i 0x0B05" that for? I seem to be able to accomplish flashing things without that small bit in my commands for example I can just type \fastboot flash recovery recovery.img and that works just fine. So what is that small code?
flukeSG2 said:
I apparently don't have drivers for adb for my tf300t. I have no problem with fastboot. I am able to successfully flash the recovery, but I am unable to push any data to my sdcard.
Since you did not provide data about your situation I looked at your previous posts. Notice the big red line in my signature about WIPE DATA.
I'll try to help but this is a hard one to fix. You have to be willing to keep chipping away till I give or we have success. It can be very frustrating.
Without being able to fully boot my tablet, I'm not sure I can even get adb to work? If I install drivers for adb, won't I lose my fastboot capabilities that I currently have? My tablet shows up as a fastboot device in my device manager, would I just open it's properties and select new drivers for it?
My next idea is to get ahold of the system.img, boot.img and recovery.img from a rom to flash from fastboot. I can't seem to find these inside any roms I've downloaded yet, where would I find them? I am thinking I would prefer the latest stock asus rom if possible. I've downloaded the rom from Asus website, unzipped it and no .img files in it. I've also downloaded the rooted stock rom from xda here and also no .img files inside it. Does this even sound plausible, to flash those .img files from inside fastboot to make the tablet boot up?
Edit: Small side question, what exactly is "-i 0x0B05" that for? I seem to be able to accomplish flashing things without that small bit in my commands for example I can just type \fastboot flash recovery recovery.img and that works just fine. So what is that small code?
Click to expand...
Click to collapse
-i 0x0B05 is an identification provided by google for Asus android products. Each vendor is provided with a number. My tablet does not require it either but some do so we just suggest it to everyone.
I'm skipping everything else you asked for the moment.
Prior to flashing CWM were you on JB or ICS?
Either way we need to replace your non working CWM with twrp (2.4.1.0). Here is the link if you were on JB then flash JB if you were on ICS flash ICS.
tobdaryl said:
-i 0x0B05 is an identification provided by google for Asus android products. Each vendor is provided with a number. My tablet does not require it either but some do so we just suggest it to everyone.
I'm skipping everything else you asked for the moment.
Prior to flashing CWM were you on JB or ICS?
Either way we need to replace your non working CWM with twrp (2.4.1.0). Here is the link if you were on JB then flash JB if you were on ICS flash ICS.
Click to expand...
Click to collapse
Hey I appreciate your help man. I was on CM10 JB 4.1.1, but that was before they required us to have the JB Bootloader, which is where I started to mess up at. I've had CWM since I was running CM10, so when I wiped data, it wasn't from a stock recovery, but I'm guessing that doesn't make a difference. Anyways right now, I'm waiting for the battery to charge up a bit, let it die out last night. I will post as soon as I get TWRP flashed.
flukeSG2 said:
Hey I appreciate your help man. I was on CM10 JB 4.1.1, but that was before they required us to have the JB Bootloader, which is where I started to mess up at. I've had CWM since I was running CM10, so when I wiped data, it wasn't from a stock recovery, but I'm guessing that doesn't make a difference. Anyways right now, I'm waiting for the battery to charge up a bit, let it die out last night. I will post as soon as I get TWRP flashed.
Click to expand...
Click to collapse
Good. While waiting you can download the latest ICS stock 9.4.3.30. You will find it in post 3 of this thread.
So I've got an interesting snag now. I've flashed TWRP 4 times, it never takes. When I boot into recovery, it's still CWM. When I use fastboot, it says it's sending and writing are both ok, but when I reboot into recovery it's still CWM 5.5.0.4.
Edit: I even went as far as to try using the JB version of TWRP, because I was on JB before, just not the 4.2.1 that requires JB bootloader. Still gives me the same result.
Edit 2: I have the stock boot.blob also I just tried flashing, same thing, still got CWM after flashing the blob.
flukeSG2 said:
So I've got an interesting snag now. I've flashed TWRP 4 times, it never takes. When I boot into recovery, it's still CWM. When I use fastboot, it says it's sending and writing are both ok, but when I reboot into recovery it's still CWM 5.5.0.4.
Edit: I even went as far as to try using the JB version of TWRP, because I was on JB before, just not the 4.2.1 that requires JB bootloader. Still gives me the same result.
Edit 2: I have the stock boot.blob also I just tried flashing, same thing, still got CWM after flashing the blob.
Click to expand...
Click to collapse
Your recovery has to be the same as your bootloader. Don't mistake JB in rom name and JB bootloader. They are two different things and if your bootloader is ICS then we need ICS.
OK. Let's see what we have to work with now. Boot into CWM, plug your tablet into your pc and check for adb access.(adb devices)
tobdaryl said:
Your recovery has to be the same as your bootloader. Don't mistake JB in rom name and JB bootloader. They are two different things and if your bootloader is ICS then we need ICS.
OK. Let's see what we have to work with now. Boot into CWM, plug your tablet into your pc and check for adb access.(adb devices)
Click to expand...
Click to collapse
It's not charging fast enough on my pc, so I had to disconnect it and plug it into the wall for awhile again. I can pm you if you'd like when I get it fully charged.

[Q] I might have bricked my TF101G finally - Please help!

OK. This is an older TF101G, which was running ICS, but needed to go back to stock.
My first mistake was to follow a thread which installed the stock WW HC image, but with an US stock recovery. There, I could not get updates.
I tried to fix this by rooting this monster with nachoroot. I rooted successfully. My second mistake was to use RomManager to install CWM. Though it says it has the right image, this does not work. You can boot into it, but it cannot mount the sdcard, nor can it install any zip. The machine still boots into ICS.
To recover from this, I did my third mistake. I followed an advice to insert a blob from this web page with dd to mmcblk0p4. The blob is the boot blob from CM9.1. However, now this boot blob cannot start the ICS system. It hangs at the boot logo. I can still boot into CWM, however.
To recover from this, I tried booting as far as it goes, and starting adb shell. The screen is showing a boot logo of the Transformer at that time. But the su command now longer works and hangs the shell. This beats me. Otherwise I would have tried the blob from the ICS version I installed.
Is there any way to get out of this mess?
Update:
I tried re-rooting with nachoroot. But trying to push nachoroot.bin to /data/local fails because of "permission denied". Pushing to /mnt/sdcard works. But I am not permitted to chmod to 777 there.
I solved this for the moment
Sorry, I solved it myself. Glad to see that I am still faster than the people here
I followed an advice in a posting to install the universal drivers on Windows. Simply download the drivers and updated the device drives in the hardware manager. Then I boot into CWM. There adb shell magically goes to a root shell. Probably because I rooted the phone before. Then I used dd to push the blob of the original android firmware to mmcblk0p4. The device now reboots into HC!
It remains to find out how to get a working CWM recovery to this device, so I can put an ICS ROM on it.
mga010 said:
Sorry, I solved it myself. Glad to see that I am still faster than the people here
I followed an advice in a posting to install the universal drivers on Windows. Simply download the drivers and updated the device drives in the hardware manager. Then I boot into CWM. There adb shell magically goes to a root shell. Probably because I rooted the phone before. Then I used dd to push the blob of the original android firmware to mmcblk0p4. The device now reboots into ICS!
It remains to find out how to get a working CWM recovery to this device.
Click to expand...
Click to collapse
Use PERI.
It will push a working CWM via ADB.
Works with the TF101g
Be advised the version it uses only seers the internal storage to flash ROMs.
frederuco said:
Use PERI.
It will push a working CWM via ADB.
Works with the TF101g
Be advised the version it uses only seers the internal storage to flash ROMs.
Click to expand...
Click to collapse
Yeah, thanks, I used this tool to flash a working recovery when I was on ICS.
Now I am on rooted HC and a useless CWM. I could use the recoveryblob in the PERI tool and do the same dd trick I did with the boot blob. But I want to make sure this recovery will cooperate with my HC system. At least there should be a way to revert.
I don't see why it wouldn't work with HC.
Experience?
frederuco said:
I don't see why it wouldn't work with HC.
Click to expand...
Click to collapse
There are users which report on the PERI thread about problems with HC.
No Ideas
So nobody knows how to update my Transformer? The remaining problem is that I have HC (stock) running with a disfunctional CWM recovery.
Maybe I will live with it for a while and open a new thread later.
Solved, I hope!
Ok. I solved this too. I found TWPR 2.2 on the net and took the recoveryblob out of it. Then copied this to /dev/block/mmcblk0p4 with
dd if=recoveryblob of=/dev/block/mmcblk0p4
Reboot, and got my new recovery. I hope I can install and decent ROM now.

[Q] Soft bricked after CWM installation / SOLVED

Hi all,
I have a TF300T with stock 4.2.1 android.
As i also own a nexus 7 with cyanogenmod, i decided to also give it a try on my TF300T
Unfortunately it ended in a endless loop of CWM recovery :crying:
This is what i did :
- i started with this thread http://forum.xda-developers.com/showthread.php?t=2055430
- it reference to another thread that describes how to install CWM recovery - > http://forum.xda-developers.com/showthread.php?t=1668173
I followed all 9 point in the CWM installation guide.
After that i wanted to flash the root zip and recognized that the CWM is not able to mount the sdcard and internal memory.
So i was not able to root the device and also not able to flash any custom rom.
After reading in the forum i was able with "adb reboot fastboot" to boot again into the stock ROM.
- Reading more in the forum i learned that TWRP should have been used . So i tried with fastboot to overwrite the existing recovery , but with no success.
- Reading even more in the forum i saw that there is a way to remove the CWM by restoring the orginal stock ROM with the folloing command.
"fastboot -i 0x0B05 flash staging blob" with blob coming from TW_epad-user-10.6.2.6.zip from asus web page.
After that i can not even reboot to the stock android ROM.
I still have CWM after booting of the device.
I can still open adb shell. But su is not working as i do not have root.
What is the best way now to get back to a working android on my TF300T?
Many thanks in advance for any good hints.
/BR
Is that the firmware that was already on it? I'd try installing 10.6.1.15.3 which is the newest firmware via fastboot. Should erase the recovery. I wouldn't do the 27.3 firmware, not all ROMs support it
as i do not have fastboot anymore , how to flash the stock ROM?
Can this be done with adb?
Or is there a way to get fastboot again?
I currently have endloess boot loop into CWM.
And as i can not access in CWM the sdcard and internal memory i am not able to flash anything.
I just saw this thread here - > http://forum.xda-developers.com/showthread.php?t=2236885
They had similar problems and also no fastboot
Other point is , do i need root access to fix it?
Even with adb i can not push files as the partitions are not mounted.
What about using sideload feature in CWM? will this allow to send a custom rom zip?
I finally got back my fast boot.
I made an hard reset (with hole below sdcard)
After that I could start the tablet with volume down and got back to fastboot
By that I am now able to start again the stock android that was already installed. So as long as I do not shutdown the tablet I at least can use it.
I see quiet a lot of discussions in the forum about soft brick tf300 after 4.2.1 ubdates.
I will now follow these and see if there will be a proper solution for my issue.
Thx
Sent from my Nexus 7 using xda app-developers app
kreutpet said:
I finally got back my fast boot.
I made an hard reset (with hole below sdcard)
After that I could start the tablet with volume down and got back to fastboot
By that I am now able to start again the stock android that was already installed. So as long as I do not shutdown the tablet I at least can use it.
I see quiet a lot of discussions in the forum about soft brick tf300 after 4.2.1 ubdates.
I will now follow these and see if there will be a proper solution for my issue.
Thx
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Found a recovery that actually works with 10.6.1.8 (4.2 bootloader): http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.4.4.0-tf300t-4.2.blob
Good to get you back to flashing happy. Not sure if it works with the 10.6.1.27. update though.
Finally have reached my goal...
CyanogenMod 10.1 nightly , trap, rooted....
After Ben back to stock I used this guideline staring from 4.2.1 stock
http://www.android-hilfe.de/root-cu...1-10-6-1-15-3-twrp-recovery-2-5-0-0-root.html
Sent from my Nexus 7 using xda app-developers app
Asus TF300T issues with CWM 6.0.2.3
I bought an Asus TF300T for Christmas 2014. It had JellyBean 4.2.1 on it.
I decided to try to update the device to Lollipop CM12 and admittantly I am a noob when it comes to Android tablets.
So, I installed the ClockworkMod (which installed correctly), but it has my tablet stuck in a loop. It won't mount the /sdcard
and when I open a Command Prompt with Administrator Privileges and attach the usb cable to the device, it won't find it.
I've downloaded the stock rom from Asus for the device and placed it on a 2 GB MicroSD Card that the device will not find or see.
After reading through this thread, I am feeling a bit out of my league on how to recover the device.
Any assistance would be greatly appreciated.

Categories

Resources