Database Info

[Utility]EZ Update Android 4.2/CWM/Root/Save Data/1 Click

Lots of people are having problems with the Android 4.2 update. They lose root or they can't get back into recovery. So BEFORE you flash 4.2 or if you already did and are having issues. Download this utility I whipped up. It will flash (or reflash) the 4.2 update (Including system, kernel and bootloader). It'll flash the latest 4.2 compatible ClockworkMod Touch Recovery. And then it'll get you all set up to re-root your N7 within the latest CWM. Instructions are included in the README file. PLEASE READ IT!
You DO NOT need to be on a stock rom to run this and it will NOT erase your data. But it is recommended when you get into CWM recovery for obvious reasons.
If anyone is having any issues and you get caught at the Google splash screen. You can use Power, Vol - to hard shut down the tablet, then Power, Vol +, Vol - to get into the bootloader. From here you can install the factory images from google. Once you're back up and running, you can run this tool to gain root and CWM back.
Updated 11/14/2012: Replaced SuperSu.apk with the latest version designed for 4.2
Updated 11/14/2012 14:41EST: This package will now contain 3 different runme files. One of them will not erase your data, one will erase your cache only and the last one will erase your data and cache. It seems people coming from some roms are having bootloops or hangs because of a lack of data wipe. You can attempt to run the one with no data wipe, but if you run into trouble, try one of the others. Some have made it through with only a cache wipe. See what works for you.
Updated 11/14/2012 16:53EST: Removed full data erase option as I forgot it will erase your SD card and therefor erase the root zip before it gets a chance to flash. There is only 1 runme file now and it will erase your cache, but leave your data alone. If you're having problems, or you want to avoid problems. Erase your data in CWM before you flash the supersu zip included in the package.
For Now - Windows ONLY, Sorry.
Linux version, on the way
Anyway:
Download and PLEASE READ the Read Me!

Saweet
Sent from my Nexus 7 using xda premium

Just trying to make it easy

im on 4.2 already ,can i use this to root?

Thanks for putting this together tucstwo, it was super helpful and easy for a lot of us here

Ok, I tried this and got stuck on the boot screen. Guess Ill try it again. I was on AOKP before.Can I just run this from there? I should I have wiped before?
edit
Ok it worked once I wiped it when it booted in CWR.
Great job. Now just have to test if it is still rooted

Im not getting something. After I press runme.bat my Nexus goes to clockwork recovery, its not touch, I have to choose from options like Start, Recovery Mode, etc. It doesnt match the instructions. Im super confused, any help?
Ugh. now my device is stuck at the google start screen, and not going anywhere. Android is too complicated sometimes for dumb people like me...

Solange82200 said:
Im not getting something. After I press runme.bat my Nexus goes to clockwork recovery, its not touch, I have to choose from options like Start, Recovery Mode, etc. It doesnt match the instructions. Im super confused, any help?
Click to expand...
Click to collapse
Its booting you in fastboot. just follow the instructions in the window that comes up when you run the runme.bat.
When it boots in fastboot just hit the space bar. It will take a couple times of hitting the spacebar before you reach the CWR stage where you flash the PlaceMeOnYourSDCardSuperSu.zip

When I click runme, it opens up the cmd window, starts the daemon, and then just sits there with a blinking cursor. Tried this few times already, nothing is happening.
EDIT: My nexus 7 is connected and has usb debugging turned on.

Hasan10 said:
When I click runme, it opens up the cmd window, starts the daemon, and then just sits there with a blinking cursor. Tried this few times already, nothing is happening.
Click to expand...
Click to collapse
Do you have ADB set up on you computer?
Did you make sure you have USB debugging selected on your nexus 7 in developer options?

trusteelfan said:
Do you have ADB set up on you computer?
Did you make sure you have USB debugging selected on your nexus 7 in developer options?
Click to expand...
Click to collapse
Figured it out. My computer recognizes the Nexus 7 as a portable device, but not recognizing it in the usb debugging mode (shows "Nexus" under Other Devices with a yellow triangle). Tried to update the driver, but it failed.

Thanks, it wasn't clear to me for some reason when I was doing it. It just kept saying after the black screen press continue, but something stopped along the way. I cant do it again because my device wont get past the Google startup screen, so I guess Im just going to flash from stock or something. Thank you for the quick help though, much appreciated!

Solange82200 said:
Thanks, it wasn't clear to me for some reason when I was doing it. It just kept saying after the black screen press continue, but something stopped along the way. I cant do it again because my device wont get past the Google startup screen, so I guess Im just going to flash from stock or something. Thank you for the quick help though, much appreciated!
Click to expand...
Click to collapse
You can run it again if it got stuck. I had to run it twice
---------- Post added at 10:04 PM ---------- Previous post was at 10:03 PM ----------
Hasan10 said:
Figured it out. My computer recognizes the Nexus 7 as a portable device, but not recognizing it in the usb debugging mode (shows "Nexus" under Other Devices with a yellow triangle). Tried to update the driver, but it failed.
Click to expand...
Click to collapse
The Nexus 7 toolkit will put the right drivers in place if you need them.

OK, I will try that.
By the way, I am currently on Android 4.1 with unlocked BL and CWM Recovery running Franco Kernel. Is this utility safe to use with this setup?
---------- Post added at 11:14 PM ---------- Previous post was at 11:07 PM ----------
OK So I have finally got the drivers, and then ran the runme. It booted me into fastboot mode and now it says sending 'bootloader' <2096 KB>... and seems to be stuck on it. I havent touched anything on my nexus 7, didn't press any buttons yet.
Unplugged it and then plugged it back in. It failed to flash the bootloader and went straight to boot and system flashing. It has now booted into Android 4.2, but I am assuming it still got the older bootloader. I think I will have to re-run the whole process to ensure new bootloader gets flashed eh? Or is there a 4.2 bootloader floating around that I can just flash using CWM and save myself the trouble?

Hasan10 said:
OK, I will try that.
By the way, I am currently on Android 4.1 with unlocked BL and CWM Recovery running Franco Kernel. Is this utility safe to use with this setup?
---------- Post added at 11:14 PM ---------- Previous post was at 11:07 PM ----------
OK So I have finally got the drivers, and then ran the runme. It booted me into fastboot mode and now it says sending 'bootloader' <2096 KB>... and seems to be stuck on it. I havent touched anything on my nexus 7, didn't press any buttons yet.
Unplugged it and then plugged it back in. It failed to flash the bootloader and went straight to boot and system flashing. It has now booted into Android 4.2, but I am assuming it still got the older bootloader. I think I will have to re-run the whole process to ensure new bootloader gets flashed eh?
Click to expand...
Click to collapse
It takes it a few minutes to run the process. You should have just waited

trusteelfan said:
It takes it a few minutes to run the process. You should have just waited
Click to expand...
Click to collapse
No I realized it didn't install the fastboot drivers before the process began. So it was actually not able to send the bootloader. Anyways, can you please read my edited post above and advise me with that to do?
EDIT: I went ahead and re-ran the process. Since all drivers were in place, the total process took less than 5 mins, arguably faster than an OTA. Still have all of my data and the goodness of 4.2.
Thanks a lot OP for this great utility.

trusteelfan said:
Ok, I tried this and got stuck on the boot screen. Guess Ill try it again. I was on AOKP before.Can I just run this from there? I should I have wiped before?
edit
Ok it worked once I wiped it when it booted in CWR.
Great job. Now just have to test if it is still rooted
Click to expand...
Click to collapse
What was it that you wiped? Just to make sure I do exactly what you did. I'm stuck on the glowing nexus logo.

essay708 said:
What was it that you wiped? Just to make sure I do exactly what you did. I'm stuck on the glowing nexus logo.
Click to expand...
Click to collapse
I had to wipe my data. It didnt like coming from AOKP

Nevermind, I wiped cache and dalvik cache and it worked for me too.

Everything is good over here. Rooted with twrp instead tho. Anyway something weird is going on with my battery, and yo seem pretty knowledgeable so I thought I'd run it by ya and see if you couldn't shed some light on the issue. Anyway my battery stats are showing that the device isn't awake.. When clearly it is and in the stats it says the screen is even on.. But not awake. Also the screen seems to brighten and dim at odd times idk if that has anything to do with it. But I flashed an ota update.. Bootloader and all. Kept root with supersu. You think something might have been corrupt or something? Here's a screenshot of the issue.. Hmm another issue, whenever I try to take a screenshot.. With more than one app, it takes a pic of an earlier point when I was on twrp getting ready for the 4.2 update. Some really strange things are going on..

Help, Goes straight to TWRP on startup

Hello Everyone,
I am a Noob, Yes. Please help. I was trying to install TWRP onto my TF300T. I installed it Via ADB. Had it installed with my stock ROM. I tried to do a backup so I could flash CM10. It said it wasn't mounted. I tried again and then it reboot and now goes straight to TWRP. I can get my device on ADB via the cmd screen but it says that the device is attached in recovery and my serial number is now 01233456789ABCD. Have I completely bricked my tablet? Is there anything I can do? I have been searching the forums for literally hours and am at wits end. Any suggestions would be appreciated. Sorry if this has been gone over time and time again but I can't figure it out. Please help. Thanks
Marc

To add,
When I try to do anything via fastboot it just hangs waiting for device. I can't get it to go to the fastboot page on my tablet, it just goes straight to the TWRP page.

Let me guess... You were on the Asus 4.2.1 OTA release, and installed TWRP 2.4.4.0-JB...

splashg said:
Let me guess... You were on the Asus 4.2.1 OTA release, and installed TWRP 2.4.4.0-JB...
Click to expand...
Click to collapse
Yes, that would be correct. So I managed to reset the device and cold boot back to a working device. Now i'm still wanting to flash a custom recovery and change ROMS to cyanogenmod (had it on my S1 and loved it) but am a bit nervous. How do I reset my partition and clear the old TWRP and flash a working version of CWR via fastboot or a version of TWRP that will work with my OTA rom. I thought I had done quite a bit of research before hand but am feeling a bit overwhelmed now. I don't want to go through another twelve hours of trying every trick I can find on the internet to unbrick my device.
Thanks

Just a few other things to add. So now when i have my device connected to my computer in normal function i can recognize it when I enter adb devices on my cmd prompt. Then I do the fastboot reboot bootloader which it then sends it into the fastboot screen. type in adb devices and it doesn't recognize the device anymore. I try the commands to install the cwm recovery.img and my cmd screen goes through the normal steps saying it's completed it. Then i try to reboot the device through fastboot and it freezes on the bootload screen with the green box no longer flashing on the rck box. Hold power button for six seconds to reboot and i have a working device again. So now i'm lost. How do I reset everything so I can start over, repartition so I can flash a custom recovery and carry on. any help is appreciated.

I don't know how you got yours back, even the bootloader cold-booting linux won't go into the OS for me.
That said, AFAIK, TWRP 2.4.4.0-4.2 or 2.5.0.0-4.2 are the only ones that will work with the 4.2.1 OTA update. Let me know if you somehow manage to get either on there because I can't seem to flash anything.

splashg said:
I don't know how you got yours back, even the bootloader cold-booting linux won't go into the OS for me.
That said, AFAIK, TWRP 2.4.4.0-4.2 or 2.5.0.0-4.2 are the only ones that will work with the 4.2.1 OTA update. Let me know if you somehow manage to get either on there because I can't seem to flash anything.
Click to expand...
Click to collapse
I tried flashing the new correct version of TWRP. it just freezes on the rck tab of the bootloader. It goes through the process on fastboot on my cmd prmt but does nothing on the tablet end. At least I have a working device on 4.2.1 just frustrating that TW didn't state that there is a 4.2 version not just a JB version. So now I can't get OTA updates and can't flash any custom or stock ROM's. So I'm permanently stuck with 4.2 but it's better than being stuck with a brick I guess. This isn't my first time rooting, flashing or working with ADB and fastboot. Did my research before flashing the custom recovery and thought I followed TW's steps very accurately. I hope that they update their site to stop a large number of people soft or hard bricking their devices. I at least can hold out hope that someone will figure out how to re install the bootloader. There has to be a fix as the rest of my device works so the motherboard isn't shot. Good luck. Let me know if anything or anyone figures it out.

lomoski said:
I tried flashing the new correct version of TWRP. it just freezes on the rck tab of the bootloader. It goes through the process on fastboot on my cmd prmt but does nothing on the tablet end. At least I have a working device on 4.2.1 just frustrating that TW didn't state that there is a 4.2 version not just a JB version. So now I can't get OTA updates and can't flash any custom or stock ROM's. So I'm permanently stuck with 4.2 but it's better than being stuck with a brick I guess. This isn't my first time rooting, flashing or working with ADB and fastboot. Did my research before flashing the custom recovery and thought I followed TW's steps very accurately. I hope that they update their site to stop a large number of people soft or hard bricking their devices. I at least can hold out hope that someone will figure out how to re install the bootloader. There has to be a fix as the rest of my device works so the motherboard isn't shot. Good luck. Let me know if anything or anyone figures it out.
Click to expand...
Click to collapse
I finally gave up, sent mine in today, it will cost but what the hell, i want my tablet in working order. I've tried the remedies myself, to no avail.
So off to ASUS.

Let me know what they end up charging you. I did a service request on-line, but haven't heard back yet.

steveb05 said:
Let me know what they end up charging you. I did a service request on-line, but haven't heard back yet.
Click to expand...
Click to collapse
I won't know how much it will cost until the unit is in their hands. I initiated my RMA online as well, they told me i will be contacted by phone after they examine it, I'm prepared to invest another 100 bucks as i got the unit for $299. I'll be hesitant to go much higher. I will post a number when i hear from them, if they haven't replied back to you.

I've got the same problem on my TF300T.
I'm going to try to get it working.
Not entirely sure what caused it, since I had used encryption in cm10.1 prior to flashing Asus stock 4.2.1.
BTW, I've been able to get back to fastboot by running adb reboot bootloader when TWRP is loaded.
Update: Seems to be that new 10.6.x.x bootloader... gotta love Asus :-/
--- Update II----
I can't flash anything in fastboot anymore :-/

[Q] only booting into recovery after updates/more please help

Hi all I've been an idiot and am hoping I haven't done any permanent damage to my unlocked/rooted tf300 so before I continued doing anymore I wanted to make a post here asking for any help possible.
I hadn't updated to the 4.2.1 build yet and finally decided to bite the bullet an hour or two ago since I wanted to try out the newest version of cromi. I was using the patched 2.4 twrp and initially updated to the 10.6.1.8 update using fastboot, then decided I might as well do the 10.6.1.15.3 using the fastboot again and finally updated to the 2.5 twrp using fastboot. As the jb updates were happening I would get the message that the tablet wasn't rooted and to install SuperSU, and because I'm a dumb creature of habit both times I just instinctively swiped to install, only realizing what I had done after the fact.
After all of this I was still able to at least turn on my tablet and get to the home screen, but unable to do a factory reset in recovery (the log would say "unable to" on every task, but the final message would still say successful?) or have any options to install a rom within it. I had also noticed that I wasn't rooted anymore. I used motochopper and was rooted again for the time being and used a couple apps that required root just to make sure that was the case. At this point I rebooted the tablet and holding down the power button/volume down, I think this is the point where my tablet would just boot straight into recovery, unable to boot into anything except recovery since even if I hold down the power button/volume down.
I've tried to do a factory reset and get the same response as earlier and I get a "failed" message when I try to do a data format. I know there will be at least a couple glaring red flags within this message to anybody who knows much more than I do, but I'm hoping this isn't the end of my tablet and would greatly appreciate any assistance provided. If you need any extra information please let me know I'll do the best I can with providing whatever would be useful, thank you in advance for your time and help.

did you install the 4.2 recovery version?

if you have TF300T (not TG or TL), you need to flash openrecovery-twrp-2.5.0.0-tf300t-4.2.blob which you can download from the TWRP official website.
On 10.6.1.15.3, to enter fastboot mode, you need to reboot your tablet and hold volume down button until you see 3 icons (RCK, Android logo, and Wipe). At this point, release the volume down, but do not select any option and do not press volume up. Without doing anything, you are now in fastboot mode.
Do the usual thing you did... connect your tablet to PC via your USB cable, run cmd.exe and change your path to where you have fastboot and the "openrecovery-twrp-2.5.0.0-tf300t-4.2.blob" file. Type:
fastboot -i 0x0B05 flash recovery openrecovery-twrp-2.5.0.0-tf300t-4.2.blob
wait until you see a blue progress bar on your tablet. When that completes without error, type:
fastboot reboot
Enter TWRP recovery, Wipe dalvik and cache, try flashing the official ASUS 10.6.1.15.3 stock ROM again. Do not swipe to install SuperSU to root at this point. Just tap "Do not install." If installation goes well, reboot, and re-flash "openrecovery-twrp-2.5.0.0-tf300t-4.2.blob", as installing the official stock ROM may have overwritten your TWRP recovery.
To root, use motochopper like you did. Or alternatively, flash a custom 10.6.1.15.3 stock-compatible kernel and let TWRP install SuperSU (Swipe to install) when prompted before you reboot system. You will get a SuperSU installer app on your launcher. Run that app and choose "Play" or "install from recovery" option. I can confirm that both method works without apparent issues. Choosing Play would be easier and faster than having to go to recovery to flash SuperSU binaries.
I hope this works for you.

matt95 said:
did you install the 4.2 recovery version?
Click to expand...
Click to collapse
Thank you here's hopefully where the problem lies, I accidently downloaded the -JB version, not the -4.2.
How would I be able to fix this? In response to both this and ImmovableObject's post, holding down the power/volume down buttons doesn't take me to the screen with the 3 icons anymore where I can run fastboot, it just sends me into recovery mode without those options ever showing up.

peerpressure said:
Thank you here's hopefully where the problem lies, I accidently downloaded the -JB version, not the -4.2.
How would I be able to fix this? In response to both this and ImmovableObject's post, holding down the power/volume down buttons doesn't take me to the screen with the 3 icons anymore where I can run fastboot, it just sends me into recovery mode without those options ever showing up.
Click to expand...
Click to collapse
there is no solution to this unfortunately, your tab is bricked... we have to wait for a fix but it will take some time

matt95 said:
there is no solution to this unfortunately, your tab is bricked... we have to wait for a fix but it will take some time
Click to expand...
Click to collapse
That's too bad I'm leaving for a month and was hoping to be able to use it while I was gone, oh well nobody to blame but myself looks like I'll be without a tablet for a while. Thank you guys for your time and help I really appreciate it, hopefully the fix will come at some point soon in the near future.

I apologize for this last post feel free to ignore it because it's moreso just asking for an opinion but I thought I might as well ask, if you (or anybody else) were in this position would you wait for a solution to hopefully come out or cut your losses and try to sell the tablet on somewhere like ebay as a nonfunctioning unit?
edit: and if I did sell it would I have to worry about this problem being fixed and the buyer would have access to everything currently on the tablet or is that information inaccessible/wiped?

peerpressure said:
I apologize for this last post feel free to ignore it because it's moreso just asking for an opinion but I thought I might as well ask, if you (or anybody else) were in this position would you wait for a solution to hopefully come out or cut your losses and try to sell the tablet on somewhere like ebay as a nonfunctioning unit?
edit: and if I did sell it would I have to worry about this problem being fixed and the buyer would have access to everything currently on the tablet or is that information inaccessible/wiped?
Click to expand...
Click to collapse
probably this will be fixed, i don't know why but we are working onto it... i won't sell it just for few dollars.... it's not worth it

One idea (although I haven't tested it) to install TWRP 4.2 inside of TWRP, then reboot. If this doesn't work, then I suggest buying another motherboard off of eBay and replace it with the one in your tablet.

c0ded said:
One idea (although I haven't tested it) to install TWRP 4.2 inside of TWRP, then reboot. If this doesn't work, then I suggest buying another motherboard off of eBay and replace it with the one in your tablet.
Click to expand...
Click to collapse
Thank you so much for the response, would there be a way to go about getting the 4.2 version onto my tablet though if it only boots into recovery, even when you hold down the power button/volume down? When I plug the tablet into my computer it isn't able to be recognized (I'm assuming just because it only gets to the recovery screen).

Try running "fastboot devices" on your computer while in the bootloader. Does it show anything?
Correct me if I'm wrong, but I remember reading somewhere the when in the bootloader, fastboot automatically launches on 4.2.
---------- Post added at 08:48 PM ---------- Previous post was at 08:31 PM ----------
It IS possible to flash recovery while you're in recovery. Here's how (from tobdaryl; twrp can be gotten from here: techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.4.4.0-tf300t-4.2.blob):
adb push openrecovery-twrp-2.4.4.0-tf300t-4.2.blob /sdcard/openrecovery-twrp-2.4.4.0-tf300t-4.2.blob
adb shell
su
dd if=/sdcard/openrecovery-twrp-2.4.4.0-tf300t-4.2.blob of=/dev/block/mmcblk0p4
adb reboot
An then to flash stock (once again, from tobdaryl; roms can be gotten from here: forum.xda-developers.com/showthread.php?t=1697227):
adb push blob /sdcard/blob
adb shell
su
dd if=/sdcard/blob of=/dev/block/mmcblk0p4
adb reboot

Oh, well it hasn't been letting me go into the bootloader on the tablet, just boots into recovery regardless, but for what it's worth the options/commands still show up as shown in the attachment. I don't know if that's something they do anyways though.

What about "adb devices"?

c0ded said:
What about "adb devices"?
Click to expand...
Click to collapse
The list of devices attached doesn't show any it looks like it can't find it

Have you tried flashing 4.2 within TWRP?

How would I be able to go about doing that? (sorry for the inexperience and delays in response, have to wait five minutes between posts)

Download the 4.2 rom (http://www.androidfilehost.com/?fid=22926241640219416), extract it, and put the extracted zip file on to a MicroSD card. Boot into TWRP and install it from the external MicroSD (I don't know how to go about that since I don't have TWRP).
Also, you shouldn't be waiting 5 minutes between each response. You are over 10 posts.
---------- Post added at 09:12 PM ---------- Previous post was at 09:06 PM ----------
Oops. I just read the statement carefully and realized that you have to be verified by a moderator, not have over 10 posts.

I tried it out but sadly it looks like the external microsd is unable to mount so I can't pull anything off of it
edit: It gives me the option to mount a system when the ext. microsd is in but not when it is out, I don't know if that is of any help? Every other option isn't possible though.

What type of MicroSD card are you using?

A sandisk 32gb class 4 microsdhc, it's the same one I had been using with the tablet previously before this all happened

Unrecoverable Bootloader Error (Soft-Brick) [SOLVED]

Mods, please move this to the General section...my mistake.
This OP is a work in progress. Any useful info will be added. This thread was solely created to help those who might overlook the thread that I linked below. ALL CREDIT for this solution goes to Buster99.
This is big news for me, and I hope that some of you can save some money in the future on new motherboards. Try this before you buy another!
Now, this solution is for those who:
- flashed the wrong recovery, and wiped data
- are able to boot into recovery, but cannot flash anything
- no adb access (although, if you DO have adb access, this will still work for you...)
Here is what you need to do, quoted from the link below.
Here how i restored my TF300T JB
download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file
install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)
Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot
(the folowing i did at least 10 times already but didn't erase misc)
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot
* it also took a lot longer as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s
im now setting my tab up to get back to CM (which initially caused this sh1theap due to autoupdate error, same as my A700 got bricked )
hope i could help you out!
cheers
-Buster
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=44244313
I hope that this has helped someone, as it has surely solved my problem.
THANKS, Buster for saving me money that I can't afford right now!
Side notes:
- The tablet seems to be a little slower, and lags/stutters a little bit. Not sure if that is because of the Stock 4.2 rom. I don't have much experience on it.
- Update: The stock rom was the cause of the lag. I'm flashed on a custom rom and enjoying the benefits!!!!
______________________________
HTC Evo 4G LTE

aarsyl said:
Mods, please move this to the General section...my mistake.
This OP is a work in progress. Any useful info will be added. This thread was solely created to help those who might overlook the thread that I linked below. ALL CREDIT for this solution goes to Buster99.
This is big news for me, and I hope that some of you can save some money in the future on new motherboards. Try this before you buy another!
Now, this solution is for those who:
- flashed the wrong recovery, and wiped data
- are able to boot into recovery, but cannot flash anything
- no adb access (although, if you DO have adb access, this will still work for you...)
Here is what you need to do, quoted from the link below.
http://forum.xda-developers.com/showthread.php?p=44244313
I hope that this has helped someone, as it has surely solved my problem.
THANKS, Buster for saving me money that I can't afford right now!
Side notes:
- The tablet seems to be a little slower, and lags/stutters a little bit. Not sure if that is because of the Stock 4.2 rom. I don't have much experience on it.
______________________________
HTC Evo 4G LTE
Click to expand...
Click to collapse
Good idea mate!! maybe we can have a sticky for softbrick issues(looking at you MOD )
and I'm happy you saved your money since i had to get a replacement screen and know how much it hurts your wallet
cheers
-Buster

Buster99 said:
Good idea mate!! maybe we can have a sticky for softbrick issues(looking at you MOD )
and I'm happy you saved your money since i had to get a replacement screen and know how much it hurts your wallet
cheers
-Buster
Click to expand...
Click to collapse
Thanks I've been looking at my tablet depressed for months your method worked and i had tried just about everything good look
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

Thanks a lots !
U're save my tablets !

Hi guys, help me please!!! when i try to flash system blob everything is ok, but i stuck on boot loop! Why??
So i try this guide, but it says ''waiting for device'' when i do ''fastboot erase system''.

sounds like you are not in fastboot anymore. please check that you still in fastboot.
gl
Sent from my GT-I9505 using xda app-developers app

I was about to send my tablet in but tried what you posted and saved my tablet !!!
Thanks a lot !
:good:

Wow this worked
After 6 months of trying almost every method out there this saved my tablet. Thank you so much.

Do I need to just press the reset button and volume down keys to power on the tablet or should I also press the power button?
Please help because my tablet just boots directly to twrp recovery and I can't do anything from the recovery as none of the partitions can be mounted.
Please help!

juzerali said:
Do I need to just press the reset button and volume down keys to power on the tablet or should I also press the power button?
Please help because my tablet just boots directly to twrp recovery and I can't do anything from the recovery as none of the partitions can be mounted.
Please help!
Click to expand...
Click to collapse
I am having the same problem right now (well - literally, as I was typing this reply, I was most of the way through the fix).
You want to get to fastboot mode (vol down).
Here is my situation as best as I can recall.
I have an unlocked bootloader from 10.6.1.27
I have (just removed) twrp-2.5.0
I am presently halfway through the second last step of the above instructions, and just waiting for the progress bar to finish.
(I got into my mess through playing around with encrypted partitions and then forgetting about it for a few weeks, coming back to I wasn't really sure what state the tablet was in other than what you described).
Progress bar has just finished, and I have a nice silver ASUS logo indicating that I'm likely back on stock.
Moral of the story: pays to read the instructions before asking for help. Good luck
Big thanks to OP too

carneeki said:
I am having the same problem right now (well - literally, as I was typing this reply, I was most of the way through the fix).
You want to get to fastboot mode (vol down).
Here is my situation as best as I can recall.
I have an unlocked bootloader from 10.6.1.27
I have (just removed) twrp-2.5.0
I am presently halfway through the second last step of the above instructions, and just waiting for the progress bar to finish.
(I got into my mess through playing around with encrypted partitions and then forgetting about it for a few weeks, coming back to I wasn't really sure what state the tablet was in other than what you described).
Progress bar has just finished, and I have a nice silver ASUS logo indicating that I'm likely back on stock.
Moral of the story: pays to read the instructions before asking for help. Good luck
Big thanks to OP too
Click to expand...
Click to collapse
The thing is that i just cant go to fastboot mode. Vol down + power key shows the asus logo screen and then goes directly to twrp. There seems to be no way to get into fastboot.
can you help with that?

when in twrp connect to your pc type: adb reboot bootloader. shoild boot into fastboot
gl
-buster
Sent from my GT-I9505 using xda app-developers app

I LOVE YOU GUYS <333 Thought my tablet was dead for sure

Buster99 said:
when in twrp connect to your pc type: adb reboot bootloader. shoild boot into fastboot
gl
-buster
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the info, buster. However, ive already tried connecting via adb when in twrp but adb doesn't recognize my device as connected even though i have all the drivers correctly installed. Don't know what to do anymore

I've had this problem. Luckily, I had a computer with Ubuntu on it, and it recognized the device immediately. If you don't have a pic with a version of Linux, then you can look into making a LiveCD to boot Linux.
______________________________
HTC Evo 4G LTE

please bear in mind that you probably have to install the adb / fastboot drivers via apt-get. but true, i use for debugging mainly my linux now. If you new to linux try linux mint with cinnamon desktop its windowsesque. ubuntu with unit might be too confusing to start with for a quick adb / fastboot swith (but thats only imho)
gl
buster

Buster99 said:
please bear in mind that you probably have to install the adb / fastboot drivers via apt-get. but true, i use for debugging mainly my linux now. If you new to linux try linux mint with cinnamon desktop its windowsesque. ubuntu with unit might be too confusing to start with for a quick adb / fastboot swith (but thats only imho)
gl
buster
Click to expand...
Click to collapse
Thanks for your 2 cents (no sarcasm). Forgot about that extra step. But Linux actually tells you to go that within the terminal.
______________________________
HTC Evo 4G LTE

aarsyl said:
I've had this problem. Luckily, I had a computer with Ubuntu on it, and it recognized the device immediately. If you don't have a pic with a version of Linux, then you can look into making a LiveCD to boot Linux.
______________________________
HTC Evo 4G LTE
Click to expand...
Click to collapse
Thanks for your tips, aarsyl and buster.. ADB in Ubuntu is recognizing my device now! But when I give the 'adb reboot bootloader' command, it gives me this message:
error: insufficient permissions for device
---------- Post added at 03:00 PM ---------- Previous post was at 02:53 PM ----------
Never mind... I ran the adb command via sudo and my device is showing 3 icons now!! I'm going to flash the latest JB blob now.. Will keep you posted on the progress

Holy crap, I'd given up on my TF201, thought it was gone, after doing this it lives! ! ! Thank you so much! ! !
Sent from my HTC_PN071 using Tapatalk 4

And finally I was able to restore my tablet to Stock JB 4.2.1!
Thanks a lot for the original recovery steps, Buster99! You're the man! I can't thank you enough!
Thanks for the Linux tip, aarsyl. Yet another reason why Linux rules over Windows!

Fastboot issue.

So I got my phone fully working minus getting into fast boot to flash TWRP (though I already have it).
This is the rundown of what happened (mind you I was drunk).
I went to change the fastboot image after drinking like 10ish or so beer not really sure anymore. Anyways I tried flashing it through TWRP. Later I realize how silly it was but it doesn't let me into fastboot anymore. (found this out later when I went to update TWRP.)
I am looking for a relatively way safe way to fix it as I'm sure I am not the first.
Some Advice on how to fix as I really don't wanna risk bricking it would be fantastic.
Thank you,

Shinobi_warrior said:
So I got my phone fully working minus getting into fast boot to flash TWRP (though I already have it).
This is the rundown of what happened (mind you I was drunk).
I went to change the fastboot image after drinking like 10ish or so beer not really sure anymore. Anyways I tried flashing it through TWRP. Later I realize how silly it was but it doesn't let me into fastboot anymore. (found this out later when I went to update TWRP.)
I am looking for a relatively way safe way to fix it as I'm sure I am not the first.
Some Advice on how to fix as I really don't wanna risk bricking it would be fantastic.
Thank you,
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851

Maybe It's a driver issue I am having. Because what happens more specifically is fastboot menu vibrates a few times and goes to teh charging screen and doesn't allow me to flash anything (mind you this previously worked) I don't believe it is a driver issue though. Simply put I am unable to get into adb without loading the os and when the os is loaded It hangs on waiting for device. I tried manually flashing the stock logo.bin with no success..
Not sure if maybe im missing something here. Like my fastboot loads a little penguin on it instead of the stock image and then vibrates a **** load then loads the battery charger.

Shinobi_warrior said:
Maybe It's a driver issue I am having. Because what happens more specifically is fastboot menu vibrates a few times and goes to teh charging screen and doesn't allow me to flash anything (mind you this previously worked) I don't believe it is a driver issue though. Simply put I am unable to get into adb without loading the os and when the os is loaded It hangs on waiting for device. I tried manually flashing the stock logo.bin with no success..
Not sure if maybe im missing something here. Like my fastboot loads a little penguin on it instead of the stock image and then vibrates a **** load then loads the battery charger.
Click to expand...
Click to collapse
Are you able to boot into twrp? If yes,then flash this firmware.It should solve any firmware corrupt issues,i.e. you should be able to boot into fastboot again.

Thank you, YES this is exactly what I needed/looking for.
.

You have fixed/saved the Day confirmed now.