{
"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
Related
Hi. I just received my Xoom back after the 4G upgrade and now I'm unable to root. I've followed all the steps, but when I type fastboot oem unlock, the command prompt just says <Waiting for Device> (I've confirmed that ADB can see the device), and that's it....it just sits there. Can anyone help me?
Did you boot up the xoom? And do a DB reboot bootloader? Then fastboot OEM unlock?
Sent from my Xoom using xda premium
Yes I did...
Was it unlocked when you sent in? If so it may still be unlocked.
Sent from my Xoom using xda premium
It was unlocked, but they've upgraded the software to 3.2.2 and it's locked again.
It might not be. They don't have to lock it to flash it. And they probly didn't check either.
Sent from my Xoom using xda premium
Ok....pardon the ignorance but how can I tell? I no longer have Superuser. I can't even flash a custom image. Should I downgrade it to 3.0, Root, and then flash it with the Custom 3.2.2 found here on XDA?...
No not that way it screws it up! Use this and only this! Skip the unlock and see if the files work, then you know you were still unlocked.
http://forum.xda-developers.com/showthread.php?t=1242241
Sent from my Xoom using xda premium
Hammer....tried that....no matter what, once the Xoom bootloader reboots, all I get is: Starting Fastboot Protocol Support. Nothing else happens and my adb windows just sits there and says Waiting for Devices.
tdetroit said:
Hammer....tried that....no matter what, once the Xoom bootloader reboots, all I get is: Starting Fastboot Protocol Support. Nothing else happens and my adb windows just sits there and says Waiting for Devices.
Click to expand...
Click to collapse
That's because your timing is slightly off, and you're letting the stock recovery overwrite your custom recovery. You have to "catch the boot"
You can follow these steps:4. Install recovery image (CWM)
If you haven't done it already, download the recovery image file and save it to your computer in the Platform Tools folder.
(Download the recovery image from this link: http://forum.xda-developers.com/show....php?t=1074979 only the img file flashed through fastboot Remember, never try to flash a zip file through fastboot!)
4.1 Boot into flash mode with 'adb reboot bootloader.'
4.2 Install your downloaded recovery image: 'fastboot flash recovery recovery-solarnz-100611-1150.img' or whatever is the exact name of the recovery img file you are flashing.
4.3 Enter CWM recovery with the procedure below.
4.4 Restart the device with 'fastboot reboot'. Timing is essential here, so be alert when the device restarts, or you will have to redo section 4.
4.5 Once the Motorola logotype is shown, start counting to 3. At 3, press the Volume Down button. This should result in the text 'Android Recovery' in the top left corner. If it does not work (if you see Starting Fastboot Protocol), experiment with the timing (see below).
4.6 When 'Android Recovery' is shown press the Volume Up button. This should invoke the CWM recovery menu. If that works, then congratulations for getting this far!
Here is a potential pitfall. If you are unable to enter CWM *before* the device boots into Honeycomb, then the newly installed recovery image will be overwritten by the system default recovery. Just repeat steps 4.1 through 4.6 if that happens.
tdetroit said:
Hi. I just received my Xoom back after the 4G upgrade and now I'm unable to root. I've followed all the steps, but when I type fastboot oem unlock, the command prompt just says <Waiting for Device> (I've confirmed that ADB can see the device), and that's it....it just sits there. Can anyone help me?
Click to expand...
Click to collapse
I got mine back yesterday morning then used the Universal Xoom Root instructions and files to root it yesterday afternoon. Perfect!
-ts
I've tried that...won't work. As far as my timing being off....I'm literally watching the Screen the whole time...I never even get anything except the Fastboot Protocol screen...nothing changes. I simply can't go further. I've tried loading the img file (Step 4), but can't even get that far. I've spent an hour on the phone with Motorola yesterday and after being bounced to 5 different techs, they told me to contact the developer.....which I've done, with no success. I'm almost tempted to send this damn thing back and ask them to revert my device and install an older OS onto it.
Let the device boot all the way and make sure debugging is checked.
Sent from my ADR6400L using xda premium
hammer4203 said:
Let the device boot all the way and make sure debugging is checked.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
It is. That was the first thing I've checked.
Then androidsdk may be fubar. Reload your sdk and try again. Make sure to use the newest and download all the files it needs. Redownload the root files too. Then see what happens. My sdk had to be updated when I bought my xoom.
Sent from my ADR6400L using xda premium
hammer4203 said:
Then androidsdk may be fubar. Reload your sdk and try again. Make sure to use the newest and download all the files it needs. Redownload the root files too. Then see what happens. My sdk had to be updated when I bought my xoom.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
Ah, I will do that. Matter of fact, I'll download it to my other laptop...which never had any sort of anything SDK related on it, give it a fresh start. Thanks....will do this when I get home this evening.
No such luck. Step two: Fastboot oem unlock....window says: < waiting for device > and my xoom just sits there and says: Starting Fastboot Protocol Support.
I've tried this on a totally different laptop, brand new SDK installed, fastboot, and the motorola drivers for the xoom. I'm at my wits end.
tdetroit said:
No such luck. Step two: Fastboot oem unlock....window says: < waiting for device > and my xoom just sits there and says: Starting Fastboot Protocol Support.
I've tried this on a totally different laptop, brand new SDK installed, fastboot, and the motorola drivers for the xoom. I'm at my wits end.
Click to expand...
Click to collapse
Nevermind. IT WORKED. I ended up using my work laptop. Something's wonky with both of my personal laptops....either way, it's now unlocked. Thanks for everyone's help and patience.
Ur welcome! Also remember your mouse on a desktop? Took me weeks to figure out the damn thing was causing the bsod errors, and it seemed to work perfectly fine. I would back up your computers you have issues with and do a fresh install on them. I do every 6mo or so.
Sent from my Xoom using xda premium
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?
i may be up a creek now. i've tried everything i can.
here's the whole situation, maybe someone can offer some guidance on how i can get my phone back.
i installed this rom, http://forum.xda-developers.com/showthread.php?t=1835478, but did not see that there was a problem with people getting stuck at the initial google boot logo. i wouldn't have tried it if i did.
but it's too late now. so i too have that problem. in addition, i also have that problem with the nexus s in that the power button is busted, works only to boot the phone.
so i boot the phone normally, i get to that boot logo indefinitely.
i press up and power button i get to fastboot screen. for some reason the volume buttons don't work on that screen so i can't pick recovery there. only thing that works is hitting the power button and reboots the bootloader.
i plug the phone into my pc and i can't access it through adb, fastboot... does not recognize a device is connected.
so in summary, all i can do is access the fastboot screen or the boot logo screen.
if someone can help me figure out how to do one of the following: boot into recovery instead of fastboot, figure out how to use the volume buttons in fastboot, or get the phone recognized by my pc so i can use adb, that would be awesome.
i feel like i just bricked it for good....
thanks
Install the SDK. Launch it. Find the drivers to download in the SDK. Install them. Boot the phone into fastboot and connect it to pc. Open up a command prompt IN the directory that has fastboot in it. Type in the command prompt fastboot devices.
If your serial number shoes your good to go. Get the .img of your custom recovery and type fastboot flash recovery nameofile.img. with that being the exact file name ( hint type the first letter of the recovery and hit tab)
Yep, you gotta get fastboot working again. It's pretty important.
Sent from my Nexus S 4G using xda premium
i've had the sdk/driver installed already.
like i said, the phone when it boots is not being recognized by the laptop at all, as if it's not even plugged in. so when i do fastboot devices, nothing shows up.
Was it recognized prior?
Sent from my Nexus 7 using Tapatalk 2
in the prior rom it was recognized by the laptop, before i tried to flash the rom i linked above that created this mess...
albundy2010 said:
Install the SDK. Launch it. Find the drivers to download in the SDK. Install them. Boot the phone into fastboot and connect it to pc. Open up a command prompt IN the directory that has fastboot in it. Type in the command prompt fastboot devices.
If your serial number shoes your good to go. Get the .img of your custom recovery and type fastboot flash recovery nameofile.img. with that being the exact file name ( hint type the first letter of the recovery and hit tab)
Click to expand...
Click to collapse
AlphaEchoViktorSierra said:
Yep, you gotta get fastboot working again. It's pretty important.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Yep fastboot is a great tool, if you have a nexus s then you MUST get it working!
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
wookietv said:
i've had the sdk/driver installed already.
like i said, the phone when it boots is not being recognized by the laptop at all, as if it's not even plugged in. so when i do fastboot devices, nothing shows up.
Click to expand...
Click to collapse
Seems like your nexus s drivers are not installed in your laptop
google the nexus s usb drivers download them and put in the respective folder
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
albundy2010 said:
Was it recognized prior?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
was gonna ask the same question
like i said, i already had the sdk and drivers installed.
they worked fine before i installed that rom.
this definitely seems like it's on the fault of the phone, not the laptop.
looks like you got busted like a SIR!!
Just kidding man dont take it seriously...
I might sound silly but i hope you have tried this but if you have not then do try
Go here and try changing the usb plugs
http://forum.xda-developers.com/showthread.php?t=1785672
IT shows flashboot steps, you need to connect phone in bootloader mode which you are achieving atm, and see if it works
and if it doesnt then let me know i will try to help out more if i could
P.S I am also new in android so pardon my noobnes
i went another route...
i figured i had nothing to lose at this point... so i ripped the phone apart and attempted to fix the power button, which i believed in turn would fix not being able to use the volume keys in the fastboot screen.
i was correct. i jiggled with the power button inside and it seemed to work. the volume keys now reacted in the fastboot screen.
i was able to then get into recovery, wipe the phone, connect the phone to the laptop and put a new rom on it.
i'm not sure if its fixed the button completely, but at least i can get into the new rom :laugh:
well thats a relief and i am glad that you problem is solved
a little advice, get repaired that power button for good so that you have no hassle in near future
converse5 said:
well thats a relief and i am glad that you problem is solved
a little advice, get repaired that power button for good so that you have no hassle in near future
Click to expand...
Click to collapse
+1, I agree with you. It does not cost much as well. I had this problem and was managing with apps. But finally got it replaced for good.
--------------------------------------------------------------------------------
M new to android. Bought this HTC one s T-Mobile which is rooted and runs cm10 and and android 4.1.2. I have updated it to 10-20121012-nightly-villw in d hope that the WiFi tethering would work. Well it never did. But that is not my prob right now.
I tried a hard reset from bootloader screen and now it says safe to remove SD card. I installed SDK ADT bundle. But the command 'ADT devices ' returns blank. Does not recognise my phone. I downloaded all in one kit and also installed htc drivers given on the same post. Even all in one kit does not recognise my phone. Says device not found. M running vista home premium. I have followed all d steps like putting d phone in debug mode. M I missing something. Pl help. M really stuck now.
sadrulez said:
--------------------------------------------------------------------------------
M new to android. Bought this HTC one s T-Mobile which is rooted and runs cm10 and and android 4.1.2. I have updated it to 10-20121012-nightly-villw in d hope that the WiFi tethering would work. Well it never did. But that is not my prob right now.
I tried a hard reset from bootloader screen and now it says safe to remove SD card. I installed SDK ADT bundle. But the command 'ADT devices ' returns blank. Does not recognise my phone. I downloaded all in one kit and also installed htc drivers given on the same post. Even all in one kit does not recognise my phone. Says device not found. M running vista home premium. I have followed all d steps like putting d phone in debug mode. M I missing something. Pl help. M really stuck now.
Click to expand...
Click to collapse
Does QHSUSB_DLOAD appear in device manager?
I looked up d device manager could not find anything like this. Anywhere specific I need to look at ?
sadrulez said:
--------------------------------------------------------------------------------
M new to android. Bought this HTC one s T-Mobile which is rooted and runs cm10 and and android 4.1.2. I have updated it to 10-20121012-nightly-villw in d hope that the WiFi tethering would work. Well it never did. But that is not my prob right now.
I tried a hard reset from bootloader screen and now it says safe to remove SD card. I installed SDK ADT bundle. But the command 'ADT devices ' returns blank. Does not recognise my phone. I downloaded all in one kit and also installed htc drivers given on the same post. Even all in one kit does not recognise my phone. Says device not found. M running vista home premium. I have followed all d steps like putting d phone in debug mode. M I missing something. Pl help. M really stuck now.
Click to expand...
Click to collapse
Your description is confusing to me. Your thread title says it is softbricked but then you say that you put the phone in debug mode? Does your rom boot fully?
Are you trying to toolkit from the Rom, bootloader or fastboot?
If you typed adt devices it won't show anything lol
Sent from my HTC VLE_U using xda app-developers app
Spastic909 said:
If you typed adt devices it won't show anything lol
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Sorry I meant adb devices. I thought the SD card error means soft brick. Sorry for my ignorance. M able to boot and use my phone. Just that sd card won't work and I am not able to connect to adb or all in one kit to fix my issue. I tried connecting after normal boot and from recovery mode and even from boot loader screen. No luck with either of them.
I had an issue with softbricking my phone. A good last resort is to flash the RUU (thats what i was told to do and it worked like a charm). It will totally reset your phone to factory settings...and you will need to re-lock your bootloader (just use the All-In-One Toolkit) but besides that, you will once again have a working phone and can just re-root it. If you need the RUU file I can supply the link to it with a little bit of searching. Good Luck!
sadrulez said:
Sorry I meant adb devices. I thought the SD card error means soft brick. Sorry for my ignorance. M able to boot and use my phone. Just that sd card won't work and I am not able to connect to adb or all in one kit to fix my issue. I tried connecting after normal boot and from recovery mode and even from boot loader screen. No luck with either of them.
Click to expand...
Click to collapse
Everyone's so ready to have a guy run a RUU. Even if he did that it he still would be stuck.
If the toolkit isn't working then you have done something wrong.
Check in device manager and look if you see a category that says "android usb devices"
{
"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"
}
If it's not there you don't have the driver installed correctly. If it is there, double check that you have developer options enabled. In the develop options menu check for something that say enable android debugging.
While you phone is booted normally, plug it into your computer. Can you see something in the notification area that says something about debugging mode?
If you got all that done is the toolkit still not working?
I recommend using a Windows 7 PC to install HTC Sync, then copying the folder to your computer. Then install the drivers manually through device manager, selecting the previous folder that you copied. The drivers should detect your phone then.
@dc211 I can't believe your still using XP lol
Sent from my HTC One S using Tapatalk 2
I connected my phone to a Windows 7 computer and it recognised my phone.
I downloaded All-in-One.
I did not know what is flashing stock recovery. So here is what I did :
I flashed CWM 5.8.3.1(S4).
Then i booted in bootloader and did 'clear storage'. then i did wipe data/factory reset
then i reflashed CWM 5.8.3.1(s4)
Now my phone goes directly into cwm recovery screen automatically.
My SD card still does not mount.
when i try to get into bootloader using All-in-one kit it keeps saying 'waiting for device' on the computer screen and the phone reboots and goes back to CWM recovery screen.
As you are aware there is no removable battery in this phone. I am stuck now. If I hold down the power and Vol down button for as long as one minute nothing happens. Phone eventually comes back to CWM recovery screen.
I tried everything possible from CWM recovery screen. Wiped cache/dalmik cache. Format system/data. Cant format SD card it says unable to mount.
Please HELP !!
sadrulez said:
I connected my phone to a Windows 7 computer and it recognised my phone.
I downloaded All-in-One.
I did not know what is flashing stock recovery. So here is what I did :
I flashed CWM 5.8.3.1(S4).
Then i booted in bootloader and did 'clear storage'. then i did wipe data/factory reset
then i reflashed CWM 5.8.3.1(s4)
Now my phone goes directly into cwm recovery screen automatically.
My SD card still does not mount.
when i try to get into bootloader using All-in-one kit it keeps saying 'waiting for device' on the computer screen and the phone reboots and goes back to CWM recovery screen.
As you are aware there is no removable battery in this phone. I am stuck now. If I hold down the power and Vol down button for as long as one minute nothing happens. Phone eventually comes back to CWM recovery screen.
I tried everything possible from CWM recovery screen. Wiped cache/dalmik cache. Format system/data. Cant format SD card it says unable to mount.
Please HELP !!
Click to expand...
Click to collapse
Try holding volume down and power. Out should boot into the bootloader.
Sent from my HTC One S using Tapatalk 2
I already tried that. Holding vol button down + power button restarts the phone in CWM recovery mode
i tried it least 20 times and was finally able to get the phone to boot to bootloader mode
can you guide me to the next set of steps ..
I am totally relying on this forum at the moment.
sadrulez said:
i tried it least 20 times and was finally able to get the phone to boot to bootloader mode
can you guide me to the next set of steps ..
I am totally relying on this forum at the moment.
Click to expand...
Click to collapse
Run an RUU, whichever suits your CID /bootloader version.
Sent from my HTC One S using Tapatalk 2
So i'm not super competent in adb and what not, but just competent to use wuggs toolkit. I went to google's website to download lollipop 5.0 for my nexus 5. Then i set the phone back to stock, flash 5.0 and its running well. Then i go back in to settings, developer options, and to root my nexus 5 and install TWRP on it through wuggs. Now it has twrp, but will not boot up past the google name with the unlock. I only have the fastboot page and TWRP. The big kicker here is that my pc says does not recognize device and it flickers back and forth with connection every two seconds to my PC. When i go into device manager it shows android device though. So well hey i figure since i have a softbricked nexus i'll just click the button for it and reset. Well it wont do it, it pulls up fastboot.exe goes through a few commands, some saying it failed then it stops and windows tells me to close fastboot.exe
Any help from the very respected XDA?
oh, gawd.. fastbooting a factory img would have been so much faster. sorry, toolkit, i cant help you with it.
hayden55 said:
So i'm not super competent in adb
Click to expand...
Click to collapse
There's your answer right there. That's how ppl like Op brick their devices everyday
Do some research, read read and lastly Read
If you can adb the factory image you can adb a recovery. Google how to. Its literally one comand line.
Stop tossing the word bricked around, a brick is a phone that doesn't turn on and don't blame other things if you don't know how to use them.
Google is your best friend. No one is going to hold your hand.
jayRokk said:
Do some research, read read and lastly Read
If you can adb the factory image you can adb a recovery. Google how to. Its literally one comand line.
Stop tossing the word bricked around, a brick is a phone that doesn't turn on and don't blame other things if you don't know how to use them.
Google is your best friend. No one is going to hold your hand.
Click to expand...
Click to collapse
aww but i really wanted a hand hold.
hayden55 said:
aww but i really wanted a hand hold.
Click to expand...
Click to collapse
here is an extra long :highfive: for your hand holding
chapelfreak said:
here is an extra long :highfive: for your hand holding
Click to expand...
Click to collapse
Hey thanks bud! Problem was it couldnt connect to the computer for more than 5 seconds...
SOO.... i messed with mounting an OTG jump drive and it had my old TWRP back with android 4.4.4. IT Worked!
p.s. i tried just mounting system data etc... the turn on mtp connection button and it Would show up better than just plugging in but couldnt download anything big. and no adb connection
dicecuber said:
There's your answer right there. That's how ppl like Op brick their devices everyday
Click to expand...
Click to collapse
i do not need your input if you aren't going to contribute to the problem just antagonize the op
Current problem at hand: phone now will only connect to pc for 5 seconds at a time. What could do this and how do I reflash to normal?
Still using toolkits?
hayden55 said:
i do not need your input if you aren't going to contribute to the problem just antagonize the op
Click to expand...
Click to collapse
It's a suggestion
Disclaimer: I use OS X/Terminal to fix these things normally and honestly found that after the initial learning curve, it's easier than using Windows or Wugfresh. I'm not a developer, just a hobbyist user.
Make sure you're using an OEM cable to connect to the computer if you're getting dropouts. Also, attempt to uninstall and reinstall OEM drivers (I believe Wugfresh has instructions on how to do this) for Windows.
If you have confirmed that you have TWRP 2.8.1.0 installed, try to boot to TWRP --> ADB Sideload. Connect phone to computer, open Terminal/Console and type the command 'adb devices' (without the apostrophes. I haven't used Windows since I stop using Wugfresh, so the command probably differs). If the device can be seen through this, you should be able to return to the bootloader and start issuing fastboot commands to flash the image.
Let me know how I can help!