Database Info

[Q] Bricked from rom manager :(

So I figured that since I've used rom manager before on other devices and had no issues that I would just flash clockworkmod via the app. WRONG. Now I'm bricked with no access to adb and presumably no access to fastboot (my TF doesn't show up under fastboot devices). My computer still recognizes the tablet as a media device or something though, evidenced by the "bloop" noise when I turn it on while connected to my PC.
I am however able to access the recovery kernel (the android lying on its back with the chest open and a warning symbol above it?). I was wondering if there was ANY way at all to reflash with a proper CWM or simply revert to stock or something? Honestly I have no qualms with cracking open the device and manually accessing and editing the filesystem from its hard-drive (if that's even possible...)
Failing this, is there any way to convince Asus to replace my tablet for me? I've already gone through the root process, so it's unlocked and I assume that means there's no way to get the warranty back. I'm open to any suggestions that will make my tablet more than just a $400 hunk of plastic. I will definitely be sending the dev team for rom manager all of my annoyance... but any and all replies are appreciated...
*edit* maybe not so bricked after all?
I was able to send the recovery.img from http://forum.xda-developers.com/showthread.php?t=1668173 to the device and presumably flash it to the device...
C:\Fastboot>fastboot -i 0x0B05 flash recovery recovery.img
sending 'recovery' (5306 KB)... OKAY [ 2.424s]
writing 'recovery'... OKAY [ 2.069s]
finished. total time: 4.493s
Click to expand...
Click to collapse
I also was able to reboot the device from fastboot, so I suppose fastboot works. I think this means I can save it? I guess I'll keep looking, but I'm still not quite sure...
edit2* Yay! Able to access CWM because of the previous link! Now to see if I can flash one of the official ICS roms...
edit3* K, well I don't have a microSD converter on hand, but every attempt to flash or boot via fastboot has failed, IDK why. I guess if I figure it out tomorrow by putting update.zip on the SD and flashing via clockworkmod, I'll post it...

power off
Were you able to power the tab off and the power it up using power+ vol down?
I can't get into the usb debugging mode. The CWM cannot see ( tried to mount it) the SD.
Thanks

I am in the same boat. What I did is a CWM backup, then loaded the Cyanogen mod. Decided to go back to my backup so I went to CWM Recovery. Seemed to load everything just fine but when it reboots it is just a black screen......I also cannot see the sd card in CWM and cannot access Fastboot because the MTP driver will not install (maybe because of Cyanogen)........still working on it. Pass along anything you can think of.....I will try anything at this point.
---------- Post added at 11:26 AM ---------- Previous post was at 11:25 AM ----------
abe_cedar said:
Were you able to power the tab off and the power it up using power+ vol down?
I can't get into the usb debugging mode. The CWM cannot see ( tried to mount it) the SD.
Thanks
Click to expand...
Click to collapse
Probably becasue your MTP drivers are not installed. I am having the same issues, but windows will not install the MTP driver......

Did you try to restore the recovery from rom manager? Or all you did was back it up? I ask because I too backed up recovery from rom manager but my tf300 is fine. I no now not to restore the back up.
If you did restore from rom manager. Why?

MTP
My drivers I believe are fine. I was able to adb flash the CWM before I did flash from the CWM app the wrong one. Xplodwild was saying that with the wrong CWM on the tab ( I have now the tf201 version on ) no one was able to recover. I guess I am stuck.

abe_cedar said:
Were you able to power the tab off and the power it up using power+ vol down?
I can't get into the usb debugging mode. The CWM cannot see ( tried to mount it) the SD.
Thanks
Click to expand...
Click to collapse
Hmmm... I can make it reboot by holding down the power button, then get into the recovery settings via the volume buttons. All that's really stuck is the bootup stuff. Although half the time fastboot recognizes it and half the time it doesn't... CWM doesn't recognize my SD either, just shows me a CWM folder.

trevor7428 said:
Did you try to restore the recovery from rom manager? Or all you did was back it up? I ask because I too backed up recovery from rom manager but my tf300 is fine. I no now not to restore the back up.
If you did restore from rom manager. Why?
Click to expand...
Click to collapse
All I did from rom manager was flash CWM. I didn't restore anything or backup anything... I should have backed it up though... Anyways, CWM works fine, so I don't think that's the problem at this point. I wish I understood more about the Android operating system, cuz I'm not sure what exactly I can blame at this point...
I flashed the Team Win Recovery Project kernel, which seems to work pretty well... it allows me to see that... there's an SD CARD partition on my main drive? wtf? lol. Anyways, it doesn't have external storage support, so that option is out. But it means that I'm able to flash things still... maybe I just need the right system file? I'll keep trying.

To push files in recovery try installing the drivers from my thread: http://forum.xda-developers.com/showthread.php?t=1680570
Recovery doesnt support external SD so this should work for you.

Northern-Loop said:
To push files in recovery try installing the drivers from my thread: http://forum.xda-developers.com/showthread.php?t=1680570
Recovery doesnt support external SD so this should work for you.
Click to expand...
Click to collapse
Hmmm... it does show up in adb devices, however I'm unable to push this way. This is what I'm seeing:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I very well may be doing something wrong, but I don't know what... This is the closest I've been so far though

BlakeC90 said:
Hmmm... it does show up in adb devices, however I'm unable to push this way. This is what I'm seeing:
[IM]http://screensnapr.com/e/IJ4Zru.png[/IMG]
I very well may be doing something wrong, but I don't know what... This is the closest I've been so far though
Click to expand...
Click to collapse
Error seems to relate to "USB Debugging Mode" I guess you didn't enable this before the brick happened?
Try "adb shell" then su
Well reading more debugging is switched on in recovery.

Northern-Loop said:
Error seems to relate to "USB Debugging Mode" I guess you didn't enable this before the brick happened?
Try "adb shell" then su
Well reading more debugging is switched on in recovery.
Click to expand...
Click to collapse
USB Debugging WAS enabled when I started all this debauchery, but I've cleared so many things and reflashed stuff so many times it very well could have reset itself or something. I'll try what you suggested though and post the results. Thanks for the suggestions, btw

Not sure it will make any difference but try putting the path in quotes
ie
adb push "c:\romfolder\roms.zip" \sdcard\ROMs
SU command wont work, doesnt work on my tab.

Northern-Loop said:
Not sure it will make any difference but try putting the path in quotes
ie
adb push "c:\romfolder\roms.zip" \sdcard\ROMs
Click to expand...
Click to collapse
using adb shell > su doesn't appear to work for me, perhaps because of it being set up in recovery?
I have little experience with adb in general, let alone adb shell, so once again I could be doing it wrong. But I don't think so...
Using quotes, however, it's taking a lot longer to run the line... I hope that means it's working XD
edit* Hmmm... can't tell if it worked or not. It won't show in recovery, but this is what showed in cmd:

BlakeC90 said:
using adb shell > su doesn't appear to work for me, perhaps because of it being set up in recovery?
[IG]http://screensnapr.com/e/A96dAy.png[/IMG]
I have little experience with adb in general, let alone adb shell, so once again I could be doing it wrong. But I don't think so...
Using quotes, however, it's taking a lot longer to run the line... I hope that means it's working XD
Click to expand...
Click to collapse
Yes it should return file sent now

Northern-Loop said:
Yes it should return file sent now
Click to expand...
Click to collapse
*sigh* it worked once, but after that just more protocol errors. I don't know if it technically worked because it doesn't show in recovery and it didn't say file sent.
...I have an option to wipe the system... that would screw things up as badly as I imagine, correct? I think I want to shy away from that, but it's the one thing in recovery I haven't tried...

Try unplugging USB cable or rebooting into recovery?
Protocol error seems to be generic error
Sent from my GT-I9100 using xda premium

Northern-Loop said:
Try unplugging USB cable or rebooting into recovery?
Protocol error seems to be generic error
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Continues to do the same thing... protocol failure... I keep messing around, but honestly I'm confused as to why it won't work... I mean what could the possible reasons be?
I've also tried flashing through fastboot, to no avail.
YESYESYES! I don't know why it decided to work this time, but for some reason, I got it! Fastboot saved me, somehow...

Great news - Has it booted now?
If so I will update my ADB/Bricked Recovery thread with the details on how to recovery from TF201 Recovery Firmware?

Northern-Loop said:
Great news - Has it booted now?
If so I will update my ADB/Bricked Recovery thread with the details on how to recovery from TF201 Recovery Firmware?
Click to expand...
Click to collapse
It's up and running fine! As far as I know, all that should be necessary is the fastboot stuff, so long as you're able to access it... If not, then I think you're SOL... I guess just flash the .29 update blob and it will work? XD I'd try it again and make sure, but I don't have the balls. I guess just tell people to try that though, and if it works, it works. Thanks so much for your help!

BlakeC90 said:
It's up and running fine! As far as I know, all that should be necessary is the fastboot stuff, so long as you're able to access it... If not, then I think you're SOL... I guess just flash the .29 update blob and it will work? XD I'd try it again and make sure, but I don't have the balls. I guess just tell people to try that though, and if it works, it works. Thanks so much for your help!
Click to expand...
Click to collapse
Thanks I'll add credit to you for being the unlucky/though lucky for getting recovery back. As we have a separate recovery I always thought it would of been possible to recovery if you flash bad rom or bad recovery.
Can you vet the info I have put into my thread http://forum.xda-developers.com/showthread.php?p=26724020#post26724020
Installed drivers, boot into to fastboot to flash recovery then fast boot system blob file?

[Q] PLz Help Google logo Stuck

My nexus s m200 ( Korean) phone is stuck with google logo . i was talking on a call when phone hung. I tried to restart it but none of the buttons (Power, Up and Down) worked. so i pulled of my battery reinserted and there it was the horrible google logo sign. I tried every thing i tried to recover by going into recovery but recovery failed then i format wipe user data/ sd card but it didn't resolve my issue i even wiped the cache files as well.....
The Bootloader is locked i have tried everything but it just doesn't unlock... i cannot root from sd card because i have no access on it. i gave it to couple of repairmen but they also failed to understand the issue..........??
I cannot root from any software because the bootloader is locked... i even tried in command by typing "fastboot oem unlock" it does give caution the screen but it when i accept it.. it simply says unlock failed..........??????
i even use Nexus Root Toolkit v.1.6.1 . after unlocking when it reboots the cell phone it again hang up on the google logo. and again i have to pull out the battery inorder to go to bootloader menu... and then it is again locked.. kit has also failed to unlock and resolve my issue...
PLz Helpppppp
What SHould I do...........?? Plz can anyone poit me in the right direction.
Plz help its my first time that i hav bought anything this expensive out of my own hard earned moneu :crying:

Faizan.Waheed said:
My nexus s m200 ( Korean) phone is stuck with google logo . i was talking on a call when phone hung. I tried to restart it but none of the buttons (Power, Up and Down) worked. so i pulled of my battery reinserted and there it was the horrible google logo sign. I tried every thing i tried to recover by going into recovery but recovery failed then i format wipe user data/ sd card but it didn't resolve my issue i even wiped the cache files as well.....
The Bootloader is locked i have tried everything but it just doesn't unlock... i cannot root from sd card because i have no access on it. i gave it to couple of repairmen but they also failed to understand the issue..........??
I cannot root from any software because the bootloader is locked... i even tried in command by typing "fastboot oem unlock" it does give caution the screen but it when i accept it.. it simply says unlock failed..........??????
i even use Nexus Root Toolkit v.1.6.1 . after unlocking when it reboots the cell phone it again hang up on the google logo. and again i have to pull out the battery inorder to go to bootloader menu... and then it is again locked.. kit has also failed to unlock and resolve my issue...
PLz Helpppppp
What SHould I do...........?? Plz can anyone poit me in the right direction.
Plz help its my first time that i hav bought anything this expensive out of my own hard earned moneu :crying:
Click to expand...
Click to collapse
First off, CALM DOWN. The fact that you can see the google logo means your phone isn't dead.
Second, do not pull off the battery when you're stuck. Use Nexus root toolkit if you want to do a reboot. Go to Advanced Utilities, Click "Launch", then click Reboot, Reboot Bootloader, or Reboot Recovery.
Make sure you installed the correct drivers for your specific phone model (m200).
Try using the toolkit and set-up your phone correctly. Use PdaNet drivers. Then try to unlock the bootloader again.

Plz Help
ej8989 said:
First off, CALM DOWN. The fact that you can see the google logo means your phone isn't dead.
Second, do not pull off the battery when you're stuck. Use Nexus root toolkit if you want to do a reboot. Go to Advanced Utilities, Click "Launch", then click Reboot, Reboot Bootloader, or Reboot Recovery.
Make sure you installed the correct drivers for your specific phone model (m200).
Try using the toolkit and set-up your phone correctly. Use PdaNet drivers. Then try to unlock the bootloader again.
Click to expand...
Click to collapse
Yes i did install the PdaNet Drivers and then unlocked it that but still it is somehow locked... The thing is that when i simply turn on phone it stucks with the google logo on it. Then any command that i may type is just ineffective.. Command windows says "Device searching" but if i start the phone in bootloader menu then computer recognizes the device.....?? i just cant figure out what to do.......I have been trying to sort this issue since last monday but all in vein...
So any solution that might entertain this problem

Go to bootloader, flash a custom recovery, then flash a new rom.

ej8989 said:
Go to bootloader, flash a custom recovery, then flash a new rom.
Click to expand...
Click to collapse
Thank you so very much for your concerned and valuable advices.... i Really appreciate it but
PLz can u direct me through some instructions that how to flash a custom recovery and then flash a new room...? What soft wares i will be needing and wht will the procedure........??

amydacus3 said:
Central and elegant location.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Didn't get you bro.....??

[Q] Is it bricked or hardware?

Hey.
So i bought a tf101 and it was never rooted before if you believe the previous owner. I used easyflasher to install, then installed cm10.
So yesterday i was going to bed, open the tablet and boff. Just died.
I could enter the APX mode (i saw it popped up when i connected it to the computer) but nothing else. So since it was late i thought i'l do the unbrick with easyflasher today.
Now i can't even enter APX mode.
So how do i know if it's bricked or hardware issues? Cause i've got ½ year of guarantee left on it.
EDIT: I can now enter APX mode for some reason, tried the unbrick on easyflash. Im using the WW SKU version. The easyflasher seems to have trouble cause the "wheele.exe" get's closed everytime after it uploaded the bootloader to 100%. But the installation still says it's done and no other errors shows up. But still not able to boot anything on the device.

One way to know if it's "dead" or not is this:
- Power off the device completely (hold the power button for 5 seconds and make sure it's not detected in your computer)
- Make sure ADB is installed (download)
- Run "adb logcat" (without the quotes - see this for more details)
- Boot the device
ADB should say something like "waiting for device..." when you run logcat, and when you boot up you should start seeing the booting process in ADB. If it boots (basically adb will just print stuff forever), then you can probably start suspecting hardware, like the screen for instance. If it stalls during boot, let us know where and what's the error message; it could be corruption somewhere or something alike. If you get nothing at all then I would suspect hardware failure of some sort that's more serious than the screen. If you want to bypass the screen as possible culprit, plug it into HDMI, however you may not get any signal until it's fully booted.
Edit: What's your exact model?

Lethe6 said:
One way to know if it's "dead" or not is this:
- Power off the device completely (hold the power button for 5 seconds and make sure it's not detected in your computer)
- Make sure ADB is installed (download)
- Run "adb logcat" (without the quotes - see this for more details)
- Boot the device
ADB should say something like "waiting for device..." when you run logcat, and when you boot up you should start seeing the booting process in ADB. If it boots (basically adb will just print stuff forever), then you can probably start suspecting hardware, like the screen for instance. If it stalls during boot, let us know where and what's the error message; it could be corruption somewhere or something alike. If you get nothing at all then I would suspect hardware failure of some sort that's more serious than the screen. If you want to bypass the screen as possible culprit, plug it into HDMI, however you may not get any signal until it's fully booted.
Edit: What's your exact model?
Click to expand...
Click to collapse
This is just wierd. Now it will boot, but only if it's in the charger... When i plug it out it dies. The battery says 76% and haven't moved so the battery seems dead?
And i've got the b50.
This is how it looks when i use easyflasher when it's on APX mode (as it was when i flashed recovery with easyflash). But when i boot up the tablet with charger it's still cw10.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Are you using the APX drivers suggested in the Easy Flasher post? If wheelie closes chances are it's not doing anything to your device at all, which would explain why you still boot CM10. For problems with EF I suggest posting in their thread, I never really had issues so I can't troubleshoot the issue further.
If you're using the drivers maybe there's a hardware related issue, like the internal SD for instance. I've seen some posts here where people have to keep it plugged to USB but I haven't followed them, you can probably find them through a search of this section.

Lethe6 said:
Are you using the APX drivers suggested in the Easy Flasher post? If wheelie closes chances are it's not doing anything to your device at all, which would explain why you still boot CM10. For problems with EF I suggest posting in their thread, I never really had issues so I can't troubleshoot the issue further.
If you're using the drivers maybe there's a hardware related issue, like the internal SD for instance. I've seen some posts here where people have to keep it plugged to USB but I haven't followed them, you can probably find them through a search of this section.
Click to expand...
Click to collapse
I've installed the drivers as wanted by EF. I can browse the internal SD without any problems so i'm not sure about that. Anyway to test that?
I think im gonna download some other rom right to the tablet and try install it. Otherwise i have to go and buy a sd-card thingy for the computer so i can try install stock rom that way i guess.
edIt: Installed Team EOS 4 *JELLYBEAN MR1* but diden't make any diffrence. Now i just need to try get stock and un-root so i can send it to asus :/

So i kinda got it to work out. I think.
I could keep the tablet alive after a while using the keyboard dock after having it being charged for about 10 min. So i had do unistall the "normal" drivers which i could not accsess before and then i worked to make normal rom with easyflash.
But question is:
Is the WW SKU right one for me (im from sweden.)?
Does the recovery go back to orignal also? When i tried to accses recovery all i got was the android green guy who had something wrong with his stomach. Means im back to orginial recovery?
Cause im gonna go back to the store as warranty issue, but i'd like to make it looked as much as possible that it was never rooted or had diffrent roms the the orgiinal.

Yup the WW firmware is the one for non-US non-Asian and will bring recovery back to stock. You now have a 100% stock device unless you re-rooted it.

Lethe6 said:
Yup the WW firmware is the one for non-US non-Asian and will bring recovery back to stock. You now have a 100% stock device unless you re-rooted it.
Click to expand...
Click to collapse
I downloaded some "check if rooted" app an it says it was not properly rooted which i guess means there is no root existing. Ty for your help man, been awsome. Just hope i won't get charged by asus somehow

Yeah hope so too! Let us know how it ends up going

Worse comes to worse, use PERI http://forum.xda-developers.com/showthread.php?t=1681155
Sent from my Transformer using Tapatalk HD

Lethe6 said:
Yeah hope so too! Let us know how it ends up going
Click to expand...
Click to collapse
So, just wanna update the thread.
The battery was dead so switched it myself after buying one for 50-60 dollars on ebay. Was quite easy, only painful part was putting on the thing around the screen with the power button etc so it would work.

Sweet, glad you got it fixed

[Mac Toolkit] Root, Recovery, Unroot, Stock, One-Click! [Update 12/14/2013]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am not responsible for anything that happens to your Nexus 7 tablet when you use my toolkits below!!
Based on script by: 1KDS link to his script/tool: Here
What Does This Nexus 7 Toolkit Include?
* Root Nexus 7 - Now works with Android 4.4.X!
* Install ClockworkMod Recovery on Nexus 7
* Unroot/Stock on Nexus 7
* Unlock Bootloader on Nexus 7
* Lock Bootloader on Nexus 7
I Have Made Separate Scripts So You Only Have To Download The Specific Files You Need.
How Do I Use These Toolkits?
1. Download the toolkit of your choice using the links below.
2. Unzip the file and click on click on the green Android icon.
3. Enter your phone into bootloader mode:
First power off your tablet and make sure it's unplugged then,press the volume up, volume down, and power button all at the same time. When your phone vibrates let go of the power button, but keep holding onto the volume up and down button. You will now see a green start screen.
4. Follow directions on the screen.
All Toolkits Can Be Found Using The Link Below:
http://www.androidrootz.com/2013/08/nexus-7-one-click-toolkit-for-mac-2013.html
Changelog:
August 6 2013:
* Initial Release
August 11 2013:
* Added One-Click Unroot/Stock toolkit
December 14 2013
* Updated One-Click Root Toolkit to support Android KitKat
* Added ClockworkMod Recovery One-Click Toolkit to support KitKat
* Removed TWRP One-Click Toolkit - No support for KitKat yet
Please leave feedback!:
Please Hit The Thanks If You Found These Tools Helpful!
Donations Are Greatly Appreciated!
To Donate Please Click the Link Below. Thank you!

TWRP requires me to enter password when I first enter recovery mode, but I haven't set any password before, any idea? thanks

dimchan said:
TWRP requires me to enter password when I first enter recovery mode, but I haven't set any password before, any idea? thanks
Click to expand...
Click to collapse
You should just be able to slide to unlock.

I may have just soft bricked my N7. So after I completed the unlock process, I tried to flash SU and it said no such file or directory. I am able to get to TWRP, but every time I try to boot, it loops on the X logo. I am able to get to fastboot and recovery modes, and ADB sees my device, so I tried to push the SU zip, but it says device not found, even though it shows the device before. I'm at a loss here. Any help would be greatly appreciated.

Airwolf79 said:
I may have just soft bricked my N7. So after I completed the unlock process, I tried to flash SU and it said no such file or directory. I am able to get to TWRP, but every time I try to boot, it loops on the X logo. I am able to get to fastboot and recovery modes, and ADB sees my device, so I tried to push the SU zip, but it says device not found, even though it shows the device before. I'm at a loss here. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Enter into recovery mode and select "Wipe" reboot and you should be able to boot up.

I tried that, but it still sticks on the "x" logo for a long time, like 15 min +. I wiped the boot.IMG in adb, cuz I was trying to restore a fresh one but it wouldn't see my device. How long should it take to boot up?

Finally got it to work. I flashed the boot, system, and recovery img's from ATGadmin's "One click factory restore" thread through fastboot on my mac. Here's the commands I used. (My device was unlocked during process) First I downloaded and navigated to the Nexus_7_Restore_F folder in terminal (cd /users/.....), made sure it saw my device in fastboot mode (fastboot devices), then
fastboot erase boot
fastboot erase system
fastboot erase recovery
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
I think I may not have followed the instructions the first time in this thread. I didn't reboot right after the unlock process to reenable usb debugging. I don't understand why I boot looped after that, and I'm no dev, but certainly not a noob, but it's a lesson to myself and others to take our time and follow instructions exactly! Thanks OP!!!!!

OP, thanks for this!! I haven't used the yet, but I'm going to be shortly. I fully intended to unlock and root manually, but I can't get ADB to recognize my device no matter what I try! That's on my laptop, which is an HP Envy, 64 bit, Windows 7, and i7. I've unlocked, rooted, S-Off'ed, MANY different devices using my laptop, but it just refuses to see my '13 N7 in ADB!! I've tried every driver I could find, even downloaded some of the other toolkits to see if their drivers were any different but I've still had no luck whatsoever. Anyway, my Dad has a year old Macbook Pro laptop and I'm going to borrow it from him to give this a try on his, hoping I FINALLY have some luck!! Thanks for giving everyone the option of using an Apple computer!!! I'll report back with whether this works for me or not. If I still can't get my device recognized even after trying this toolkit, then I guess an exchange at my local Best Buy will be my only other option. Really didn't want to, as this device has no dead pixels, no dust under the screen, and VERY minimal light bleed (don't think it could be much less). I guess I'll have no other choice though if it still isn't recognized even after trying an Apple computer.
EDIT : Meant to ask, is everything that I'll need to do this on his laptop included in the toolkit? Just looked at the download link, will I need the 3 separate toolkits to unlock, root, and flash TWRP? Finally, are there any commands that I'll need to type in to ADB while using your toolkits? (I have never used ADB on a Mac, so I have no experience with that)
Thanks to anyone who can answer my Mac-noob questions
SwiftKey'ed from my '13 Nexus 7 using XDA Premium HD

stanglifemike said:
OP, thanks for this!! I haven't used the yet, but I'm going to be shortly. I fully intended to unlock and root manually, but I can't get ADB to recognize my device no matter what I try! That's on my laptop, which is an HP Envy, 64 bit, Windows 7, and i7. I've unlocked, rooted, S-Off'ed, MANY different devices using my laptop, but it just refuses to see my '13 N7 in ADB!! I've tried every driver I could find, even downloaded some of the other toolkits to see if their drivers were any different but I've still had no luck whatsoever. Anyway, my Dad has a 1 year old Macbook Pro laptop (I think that's what it's called) and I'm going to borrow it from him to give this a try on his, hoping I FINALLY have some luck!! Thanks for giving everyone the option of using an Apple computer!!! I'll report back with whether this works for me or not. If I still can't get my device recognized even after trying this toolkit, then I guess an exchange at my local Best Buy will be my only other option. Really didn't want to, as this device has no dead pixels, no dust under the screen, and VERY minimal light bleed (don't think it could be much less). I guess I'll have no other choice though if it still isn't recognized even after trying an Apple computer.
EDIT : Meant to ask, is everything that I'll need to do this on his laptop included in the toolkit? Just looked at the download link, will I need the 3 separate toolkits to unlock, root, and flash TWRP? Finally, are there any commands that I'll need to type in ADB while using your toolkits? (I have never used ADB on a Mac, so I have no experience with that)
Thanks to anyone who can answer my Mac-noob questions
SwiftKey'ed from my '13 Nexus 7 using XDA Premium HD
Click to expand...
Click to collapse
Read my post above urs. Also, make sure u have USB debugging enabled, before AND after unlocking. I don't think its just ur device that's like that. I had a hard time getting my computers to recognize my device too.

Airwolf79 said:
Read my post above urs. Also, make sure u have USB debugging enabled, before AND after unlocking. I don't think its just ur device that's like that. I had a hard time getting my computers to recognize my device too.
Click to expand...
Click to collapse
Cool, thanks!
EDIT : No commands have to be typed in by the user when using these toolkits. Everything is automated through the toolkits, so even a Mac-noob like myself can breeze right through the entire process. Couldn't be any easier!
SwiftKey'ed from my White Sprint Note 2 using XDA Premium

Can't believe it how incredibly fast that was! I'm finally unlocked, rooted, and have TWRP installed!!!!! Can't believe how FAST your toolkits worked!! Wish I would have known that I wasn't gonna have any luck getting ADB to recognize my device with my laptop, and I woulda borrowed my Dad's Macbook Pro and used your toolkit when you first released it!!! I was gonna do it all manually, but no big deal, just glad it's FINALLY unlocked! Now I've just gotta find a driver so that my laptop recognizes my device via MTP an PTP.
I'm on the XDA app, so I don't see standard signatures. I'm assuming you have a Donate link in yours, but if not then please post it for me. You are definitely getting a donation from me!!!! I'm still just amazed that after the hours I spent trying to get ADB to recognize my device on my laptop, I borrow my Dad's Mac and your toolkits have EVERYTHING done in less than a minute (for those reading this, less than a minute is NOT an exaggeration, these toolkits have you unlocked and rooted with TWRP remarkably fast)!!!!!! You sir, are my hero tonight
SwiftKey'ed from my White Sprint Note 2 using XDA Premium

stanglifemike said:
Cool, thanks!
EDIT : No commands have to be typed in by the user when using these toolkits. Everything is automated through the toolkits, so even a Mac-noob like myself can breeze right through the entire process. Couldn't be any easier!
SwiftKey'ed from my White Sprint Note 2 using XDA Premium
Click to expand...
Click to collapse
You're right, but I forgot to reboot after unlocking and re-enable USB debugging. Then my N7 boot looped and I couldn't get any tool kits to work, so the commands I posted are really more for people that can't get their device to boot (or just can't read instructions, like me! Lol).

^^Lol! As long as you got it figured out man, that's what's important! Hopefully no one else will need those commands, but thanks for posting them in case they do!
SwiftKey'ed from my '13 Nexus 7 FHD using XDA Premium HD

stanglifemike said:
Can't believe it how incredibly fast that was! I'm finally unlocked, rooted, and have TWRP installed!!!!! Can't believe how FAST your toolkits worked!! Wish I would have known that I wasn't gonna have any luck getting ADB to recognize my device with my laptop, and I woulda borrowed my Dad's Macbook Pro and used your toolkit when you first released it!!! I was gonna do it all manually, but no big deal, just glad it's FINALLY unlocked! Now I've just gotta find a driver so that my laptop recognizes my device via MTP an PTP.
I'm on the XDA app, so I don't see standard signatures. I'm assuming you have a Donate link in yours, but if not then please post it for me. You are definitely getting a donation from me!!!! I'm still just amazed that after the hours I spent trying to get ADB to recognize my device on my laptop, I borrow my Dad's Mac and your toolkits have EVERYTHING done in less than a minute (for those reading this, less than a minute is NOT an exaggeration, these toolkits have you unlocked and rooted with TWRP remarkably fast)!!!!!! You sir, are my hero tonight
SwiftKey'ed from my White Sprint Note 2 using XDA Premium
Click to expand...
Click to collapse
Your welcome! :good: Glad everything worked out! Here is the donate link if you would like to donate, thanks.

Everything worked perfectly and was crazy fast and easy. Thanks! I did notice that to get into fastboot, you only need to hold down the volume down and power button, and not the up/down/power like the instructions say.

steveo11284 said:
Everything worked perfectly and was crazy fast and easy. Thanks! I did notice that to get into fastboot, you only need to hold down the volume down and power button, and not the up/down/power like the instructions say.
Click to expand...
Click to collapse
This is very true! I also noticed that the instructions were wrong, when I was reading through them. A couple times I actually tried what the OP said to do, just in case it was some new method I hadn't heard of, or something specific to Mac
No big deal, but you'll probably want make the corrections in the OP.
SwiftKey'ed from my White Sprint Note 2 using XDA Premium

Mine is stuck at < waiting for device >.
After a while the Nexus boots up and the script continues to say < waiting for device >.
Any ideas?
I was in fastboot when I started the script.

mallize said:
Mine is stuck at < waiting for device >.
After a while the Nexus boots up and the script continues to say < waiting for device >.
Any ideas?
I was in fastboot when I started the script.
Click to expand...
Click to collapse
Try it manually. In terminal, navigate to the folder where u put the script, or any folder that has adb and fastboot, make sure it sees ur device (fastboot devices), then type fastboot oem unlock. Reboot, re-enable USB debugging. Then copy the supersu.zip to ur device, reboot to recovery, and flash it.
---------- Post added at 12:12 PM ---------- Previous post was at 12:04 PM ----------
If u need help with terminal' this thread is very helpful. I wouldn't download the whole SDK, unless u plan on developing, its really not necessary. http://forum.xda-developers.com/showthread.php?t=1917237

Worked great! Thank you! The only thing I had to do on my own was drag the SuperSU zip onto my device. For some reason when the toolkit tried to apply it, it would say cannot read device for a moment. Other than that small issue the toolkit was awesome. My first time using a toolkit of any kind so thanks for a great n easy experience.
Sent from my Nexus 7 using XDA Premium HD app

Today I tried to unroot my nexus 7 with the toolkit but at the sending system I get an error saying that it failed, only thing that worked is to send the stock recovery and the boot loader after it failed any idea why?
Sent from my Nexus 4 using xda app-developers app

Bricked again ?

Hi all,
I just got my TF300T back from Asus after i bricked it.
New software has been installed be Asus and ofc. it was on stock Android 4.2.1
I used Motochopper Rooting Toolkit to root the device and i installed TWRP 2.6.3.0
All went fine up untill here, i copied CM 11 to the tablet and booted up in recovery.
The install of CM 11 failed for some reason so i tried formatting the whole internal storrage.
On top of that i thought it might have been the recovery so i flashed CWM 6.0.2.3 to see if that worked.
I didnt realise i just had deleted the CM 11 .zip file so its not on the tablet anymore.
When i boot up the tablet i can get into recovery (CWM) but i cant get a valid rom in the internal memory.
When i put CM11 or any other rom on a micro SD card the tab/cwm doesnt see the external card.
Also i tried the mounting options and all fail.
I have used a 64Gb card and a 16Gb card, both arnt recognized.
Is there a way to get the .zip rom to my tablet and flash it in CWM?
I think fastboot is broken as well because when i fastboot devices the tab isnt recognize.
At first i could get into fastboot screen but after the tab said cold booting linux its broken as well.
So now i cant boot into the RCK / android / wipe data icon screen anymore since i also wiped data through the wipe data icon.
Only thing that happens now the tablet boots in Asus screen and directly goes into CWM.
Any idea's ?
Cheers

Good news, i got ADB working.
What should i do?
Rgds !

Cheered to soon, seems like all the ADB commands do not work, see ataached image.
ADB devices show a device and when i unplug it it doesnt show a device.
Funny the device name is 12345789ABCDE.....
Any ideas someone ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Nobody knows an answer ?

martyzzz said:
Nobody knows an answer ?
Click to expand...
Click to collapse
Did you do NvFlash? that could restore it. Usually Wiping data from that screen ends up in a hard brick.

cmendonc2 said:
Did you do NvFlash? that could restore it. Usually Wiping data from that screen ends up in a hard brick.
Click to expand...
Click to collapse
Unfortunately i didnt do NV flash, it all happened so fast
Im giving up, to bad, the tablet had just been fixed grrr
Any1 wanna take the tablet off my hands ?
Rgds

martyzzz said:
Unfortunately i didnt do NV flash, it all happened so fast
Im giving up, to bad, the tablet had just been fixed grrr
Any1 wanna take the tablet off my hands ?
Rgds
Click to expand...
Click to collapse
It's almost frustrating to see a tablet wrecked that way. I'm not faulting you, just that all of it was totally avoidable with 10 minutes spent skimming the basics. CWM has no version that works with 4.2 bootloader, except the one embedded in the NVflash image which, of course, you ignored. Now if you get to CWM, and type "adb reboot-bootloader", what happens? If it takes you to fastboot, flash the correct version of TWRP 2.6.x.x-4.2). Failing that, search for Buster99's method. Good luck.

graphdarnell said:
It's almost frustrating to see a tablet wrecked that way. I'm not faulting you, just that all of it was totally avoidable with 10 minutes spent skimming the basics. CWM has no version that works with 4.2 bootloader, except the one embedded in the NVflash image which, of course, you ignored. Now if you get to CWM, and type "adb reboot-bootloader", what happens? If it takes you to fastboot, flash the correct version of TWRP 2.6.x.x-4.2). Failing that, search for Buster99's method. Good luck.
Click to expand...
Click to collapse
Thanks for your reply, i will give it 1 more go before i trash the TF300.
BTW i did use TWRP 2.6.X.X-4.2 i just wasnt able to flash a working rom with it, tried several but no dice...
Ill get back when i have tried.
Again thanks

martyzzz said:
Hi all,
I just got my TF300T back from Asus after i bricked it.
New software has been installed be Asus and ofc. it was on stock Android 4.2.1
I used Motochopper Rooting Toolkit to root the device and i installed TWRP 2.6.3.0
All went fine up untill here, i copied CM 11 to the tablet and booted up in recovery.
The install of CM 11 failed for some reason so i tried formatting the whole internal storrage.
On top of that i thought it might have been the recovery so i flashed CWM 6.0.2.3 to see if that worked.
I didnt realise i just had deleted the CM 11 .zip file so its not on the tablet anymore.
When i boot up the tablet i can get into recovery (CWM) but i cant get a valid rom in the internal memory.
When i put CM11 or any other rom on a micro SD card the tab/cwm doesnt see the external card.
Also i tried the mounting options and all fail.
I have used a 64Gb card and a 16Gb card, both arnt recognized.
Is there a way to get the .zip rom to my tablet and flash it in CWM?
I think fastboot is broken as well because when i fastboot devices the tab isnt recognize.
At first i could get into fastboot screen but after the tab said cold booting linux its broken as well.
So now i cant boot into the RCK / android / wipe data icon screen anymore since i also wiped data through the wipe data icon.
Only thing that happens now the tablet boots in Asus screen and directly goes into CWM.
Any idea's ?
Cheers
Click to expand...
Click to collapse
Have you tried this, saved my bricked tab. Thought I was going to have to geta new motherboard at first...
How to unbrick TF300T