Database Info

stuck on Google logo

After updating around 20 apps (altogether ), I noticed the phone was not functioning normally so I tried to reboot it but now it is stuck on Google logo. I've never unlocked the phone nor used any custom roms. I'm on the latest stock rom 2.3.4
I tried removing the battery and putting it back but didn't work. Vol. up + power and then Recovery didn't work either. It gives me a triangle with ! in it and stops right there.
I also tried the USB Jig that forces the phone into downloading mode but it gave me a screen that asks (Unlock bootloader?) with some warnings but I don't know how to accept that. Niether Vol buttons nor Power button worked there
I didn't want to mess up with the phone until I hear from you guys. Please help

up.......

You might have to actually root it or use the Samsung exe back to factory. That is if you don't want to mess with it because if I ware in your position I'd be going back for a new phone. You did nothing wrong and you have 1 year warranty on it.

FYI, the triangle with ! actually is recovery. The UI is hidden until you hold power and press vol down.

matt2053 said:
FYI, the triangle with ! actually is recovery. The UI is hidden until you hold power and press vol down.
Click to expand...
Click to collapse
Thanks man, I didn't know about that
Is wiping the data (factory reset) going to delete my stuff stored on my SD card? like pic., music, vid. etc?
and do I need to actually wipe the data or will wiping the chache only work?

Factory reset reverts your phone back to the way it was when you got it.
That means all your account settings, device settings, installed applications etc are gone. Everything stored on your SD card will remain there - it's a different storage. The good thing about our Google phones is that you only have to login to Google once and all your stuff is back.
You can try wiping the cache first and see if that works, it won't harm anything. But if that doesn't work, I'm sure a factory reset will.
Good luck.
Greetz

frutelaken said:
Factory reset reverts your phone back to the way it was when you got it.
That means all your account settings, device settings, installed applications etc are gone. Everything stored on your SD card will remain there - it's a different storage. The good thing about our Google phones is that you only have to login to Google once and all your stuff is back.
You can try wiping the cache first and see if that works, it won't harm anything. But if that doesn't work, I'm sure a factory reset will.
Good luck.
Greetz
Click to expand...
Click to collapse
Thanks a lot. I already tried wiping the Cache but it didn't work. I guess I'm going with the factory reset now
Thanks again

the factory reset didn't work !
still stuck on Google logo
any advice?

farisallil said:
the factory reset didn't work !
still stuck on Google logo
any advice?
Click to expand...
Click to collapse
Can you connect your device to your computer via USB and start "adb logcat" at the Terminal/Command prompt? Does it give you any kind of readout at all?

Try doing a hard reset.

GchildT said:
Can you connect your device to your computer via USB and start "adb logcat" at the Terminal/Command prompt? Does it give you any kind of readout at all?
Click to expand...
Click to collapse
I'm not an expert in these things ... is there any post I can follow to do the things you talked about? I'm not sure that I have all the drivers needed on my pc
I do appreciate your help

farisallil said:
I'm not an expert in these things ... is there any post I can follow to do the things you talked about? I'm not sure that I have all the drivers needed on my pc
I do appreciate your help
Click to expand...
Click to collapse
One thing you should consider is just returning the phone, especially if you never flashed or rooted or unlocked bootloader.
Sent from my Nexus S using XDA App

matt2053 said:
One thing you should consider is just returning the phone, especially if you never flashed or rooted or unlocked bootloader.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I would if I was in the States

just unlock it and flash a nice CM7 with Trinity on top
Here's a rooting guide: http://forum.xda-developers.com/showthread.php?t=895545
There's another guide out there for the i9023 (European version).

GchildT said:
Can you connect your device to your computer via USB and start "adb logcat" at the Terminal/Command prompt? Does it give you any kind of readout at all?
Click to expand...
Click to collapse
No. The device doesn't even show up when I type "adp devices"
Is there anything else I should try?

Thanks
I can perform things with Fastboot
I don't want to root or unlock the phone. Is there anything else I can do?
I tried typing Fastboot update update.zip after downloading the stock rom update 2.3.4 and putting it in the SDK tools directory but it gave me the msg "faild to upload update.zip"

Try to reset with Odin.

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

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

Saweet
Sent from my Nexus 7 using xda premium

Just trying to make it easy

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Q] One S Brick? HELP!

Novice here.
Ran the All-in-One utility today and after the CWM installed I hit "Perm root" without reading the thing below telling me to boot to recovery first. It's now stuck in boot loop. Everything went off fine up until the Perm root. Even that said successful and then restarted. Only after the process was completed did the recovery loop begin. No HTC logo loop. Just reboots into CWM over and over no matter what technique I use (except for opening the case).
I've read this: http://forum.xda-developers.com/showthread.php?t=1599363
And am trying to install ADB to push ANY possible ROM over to the SD card. My recovery allows the toggle of /mount sdcard and /mount system, however adb fastboot push doesn't work. "error: device not found"
And I can't do this: http://forum.xda-developers.com/showthread.php?t=1644730 because my phone is stuck in the recovery loop. If I try volume down + power, it just comes back to recovery screen. I've tried factory reset, I've tried wiping cache, I've tried wiping Dalvik, and still nothing. I did flash the SuperSu.zip after I had used the Perm Root button on Haroon2000's app.
I'm incredibly flustered as I've rooted devices for years and this is my first problem. I've seen similar complaints all with ideas of breaking into the phone and unplugging it's battery so I can get to the bootloader etc, but I'm so very confused. So many posts telling me to do so many things.
Can someone please help break down a tangible solution here? I'm freaking out.
Cheers
EDIT: If someone can get my phone fixed, I'll Paypal them $50 USD. I really need my phone back ASAP :\

I don't know if this is your solution, but you did not mention it as one of your attempts.
Have you looked into running an RUU?
Sent from my HTC One S using xda premium

beats4x said:
I don't know if this is your solution, but you did not mention it as one of your attempts.
Have you looked into running an RUU?
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
I'll update this again once I try breaking the phone down and yanking the battery. But I have tried running the RUU. I can't get to the bootloader right now and it's not listing the device when I adb devices.
I'm going to go home from work since I've spent 7 hours on two machines (XP/7) trying to fix this PoS and redo everything from the ground up. Hopefully my anger will have overcome it.
Something I've noticed however, is that within the CWM recovery, I can use the All-in-one tool to reboot the phone. So it is reacting to ADB commands. Perhaps trying to use ADB fastboot (Right-click method) instead of full ADB installation could be a problem with trying to push a ROM zip. Also, as far as the RUU goes. I don't remember what happened there. I'll edit this when I get home.

nik.the said:
I'll update this again once I try breaking the phone down and yanking the battery. But I have tried running the RUU. I can't get to the bootloader right now and it's not listing the device when I adb devices.
I'm going to go home from work since I've spent 7 hours on two machines (XP/7) trying to fix this PoS and redo everything from the ground up. Hopefully my anger will have overcome it.
Something I've noticed however, is that within the CWM recovery, I can use the All-in-one tool to reboot the phone. So it is reacting to ADB commands. Perhaps trying to use ADB fastboot (Right-click method) instead of full ADB installation could be a problem with trying to push a ROM zip. Also, as far as the RUU goes. I don't remember what happened there. I'll edit this when I get home.
Click to expand...
Click to collapse
Okay, update.
I was able to get ADB working and detect my phone.
Next, I was able to push Venom Rom to phone. I factory reset, wiped cache, wiped Dalvik, and was able to install Venom.zip. It then asked to reboot (per Venom screen) and I said okay. It then returned to CWM Recovery. I was confused but left everything as is. I have now reset the phone by holding the power button for around 10 seconds. It then restarted to the HTC Quietly Brilliant screen. I have been looking at that screen for about 5 minutes.
Also pertinent: I did try to run the RUU, but it didn't connect through USB. (I forget what it said verbatim). So that didn't work. I also was able prior to this entire process get into the bootloader via dumb luck.
Any suggestions? I am staring at the HTC boot screen still. Do I try to restart and enter bootloader? If so, then what? It seems there is something wrong with CWM. Can I switch recoveries? Can I uninstall it?

Calm down we have all been there,
When you flashed venom did you flash the boot image? Also i use twrp instead of cwm i find twrp better .
To enter bootloader hold power button and down vol together .

As gazknight said, this seems like proper kernel not being flashed or having an issue. If you flashed the boot.img with fastboot, try again erasing cache from fastboot first. The commands are as follow:
fastboot erase cache
fastboot flash boot boot.img (where this boot.img is the one inside the zip from the rom you choose and must be left in the same folder than fastboot)
It happened to me a couple times when i was on hboot 1.14 that I had to flash the boot.img a second time sometimes, somehow it was not working the first time, randomly, even though the flash had completed ok on fastboot.
If still doesn't work try doing a factory reset from TWRP and flashing ViperOneS again.
If that still doesn't work, you might want to try another rom, like TrickDroid, you would then have to flash the boot.img from this other room with fastboot, remember that.
Try and let us know

Hold down volume down while you're trying to boot, that will get you in boot loader, go to fast boot by pressing the power key, connect your phone to your computer, run the flash viper boot img thingy and you're set!
Envoyé depuis mon HTC One S avec Tapatalk

Same issue with HTC One S bricked but in European version, Stock ROM
hello,
I did't want to start a new topic, as I'm experiencing a similar issue with my HOS. Briefly, yesterday morning I plug the phone from charger at 06.00 am. Play with it for a while and then go to work. Used it at work for a few phone calls until 10.00 am (so 4 hours on fully charge battery). Then at 10.00 am I went into a meeting and left the phone out of my sight for 20-30 minutes. When I came back from the meeting I realize that the phone was closed. I try to open it (power button) but nothing. Press power for 10-30 seconds with volume down - still no effect.
Then I took the charger (the original one that I always use to cherge it) and plug it, left it for 2-3 minutes and press power. The phone starts but all I have is the white screen with HTC logo and if I press the power button + volume down the phone goes into bootloader. That's all I can do with it for now.
I have stock rom, bootloader is locked and I never try to root the phone. Is it any chance to repair it by myself or I have to sent it to the repair shop.
many thanks in advance.

Alright so I feel like I'm getting closer.
Here's whats happening now. It's in the HTC boot screen loop. I can get it into bootloader whenever I want, but now it's not detecting /sdcard in recovery. Within the bootloader, fastboot won't detect my device and my computer (Windows 8) claims the device is malfunctioning. I can still use fastboot adb commands from my computer when it is in recovery. I have gone into bootloader and cleared storage, as well as factory reset after. Also, it used to reboot into recovery endlessly. Now it appears that isn't hte case and reboots from recovery into the OS, but will not work.
I'm going to try and flash using adb w/o sdcard the boot.img as suggested above. I'll keep updating so others can know the process if they soft-brick their phone (I'm assuming this is a soft brick because I can still run things etc).
Update: trying to do fastboot erase cache from within recovery gives me "Waiting for device". As I've said, for some reason, it says the device is malfunctioning/not detected when I'm in the 1.14 Hboot Bootloader. But again, I can issue adb devices from within recovery. Sdcard still not mounting.
Edit: I'm issuing adb commands through adbfastboot files. Do I need to have the Android SDK fully installed with the Manager thing, or does the basic adbfastboot work (From here: http://www.htconeforum.com/forum/ht...e-your-htc-one-s-back-100-stock-relocked.html). That adb fastboot has the following files: adb, fastboot, adbwinapi.dll, adbwinusbapi.dll.
I think the source of the current problem is that I can no longer access my /sdcard or mount it. One step forward, then two steps back -_-.

nik.the said:
Alright so I feel like I'm getting closer.
Here's whats happening now. It's in the HTC boot screen loop. I can get it into bootloader whenever I want, but now it's not detecting /sdcard in recovery. Within the bootloader, fastboot won't detect my device and my computer (Windows 8) claims the device is malfunctioning. I can still use fastboot adb commands from my computer when it is in recovery. I have gone into bootloader and cleared storage, as well as factory reset after. Also, it used to reboot into recovery endlessly. Now it appears that isn't hte case and reboots from recovery into the OS, but will not work.
I'm going to try and flash using adb w/o sdcard the boot.img as suggested above. I'll keep updating so others can know the process if they soft-brick their phone (I'm assuming this is a soft brick because I can still run things etc).
Update: trying to do fastboot erase cache from within recovery gives me "Waiting for device". As I've said, for some reason, it says the device is malfunctioning/not detected when I'm in the 1.14 Hboot Bootloader. But again, I can issue adb devices from within recovery. Sdcard still not mounting.
Edit: I'm issuing adb commands through adbfastboot files. Do I need to have the Android SDK fully installed with the Manager thing, or does the basic adbfastboot work (From here: http://www.htconeforum.com/forum/ht...e-your-htc-one-s-back-100-stock-relocked.html). That adb fastboot has the following files: adb, fastboot, adbwinapi.dll, adbwinusbapi.dll.
I think the source of the current problem is that I can no longer access my /sdcard or mount it. One step forward, then two steps back -_-.
Click to expand...
Click to collapse
You might need to do it as administrator.

I think I've got it. One last tip. All of the above has been helpful, but I think the problem was trying to use my Windows 8 laptop. The second I got to work, I plugged it in on the bootloader to my XP machine and voila! it recognized fastboot and listed devices.
I have tried to run the RUU 2.35.531.7 but just like unrooting my old phone, I had issues because that update was already on this phone, so it goes through the entire process only to tell me on the windows XP utility that it had failed because it was the wrong update. When I did this to my old One S right before I sent it into Tmobile for warranty, it did the same thing with the 1.53 RUU, then when I found the 2.35, it worked like a charm.
So my last question (hopefully) then is, am I missing something as for installing an OLD or exact same RUU? Or is there a newer one than the 2.35.531.7?
I haven't tried on a Windows 7 machine, but I have one available here at work. I'm wondering if I should try to fastboot a ROM. Any suggestions what I can do to get it back to stock, or an old old stock version? I'd like to root it so I can use my Titanium Backup.
Update: Before ending this reply, I read that the RUU may be failing because the bootloader is unlocked/tampered still. I'm going to run it again to grab the error code to make sure of the issue, because it seems you should be able to revert or use any RUU (correct?).

nik.the said:
I think I've got it. One last tip. All of the above has been helpful, but I think the problem was trying to use my Windows 8 laptop. The second I got to work, I plugged it in on the bootloader to my XP machine and voila! it recognized fastboot and listed devices.
I have tried to run the RUU 2.35.531.7 but just like unrooting my old phone, I had issues because that update was already on this phone, so it goes through the entire process only to tell me on the windows XP utility that it had failed because it was the wrong update. When I did this to my old One S right before I sent it into Tmobile for warranty, it did the same thing with the 1.53 RUU, then when I found the 2.35, it worked like a charm.
So my last question (hopefully) then is, am I missing something as for installing an OLD or exact same RUU? Or is there a newer one than the 2.35.531.7?
I haven't tried on a Windows 7 machine, but I have one available here at work. I'm wondering if I should try to fastboot a ROM. Any suggestions what I can do to get it back to stock, or an old old stock version? I'd like to root it so I can use my Titanium Backup.
Update: Before ending this reply, I read that the RUU may be failing because the bootloader is unlocked/tampered still. I'm going to run it again to grab the error code to make sure of the issue, because it seems you should be able to revert or use any RUU (correct?).
Click to expand...
Click to collapse
The bootloader does need to be relocked for the RUU too work and the RUU you used before should work because I have used the same RUU a few times and it worked fine.

Darknites said:
The bootloader does need to be relocked for the RUU too work and the RUU you used before should work because I have used the same RUU a few times and it worked fine.
Click to expand...
Click to collapse
I'll try that. thanks.
Now on the same XP computer, it's not showing when I adb devices, however it does show in device manager. This changed after trying to do the RUU without relocking.

Yeah! Fixed!
After enough toggling, I changed the recovery to the T one and relocked my bootloader. It turns out detecting the device wasn't necessary somehow. Then I ran the RUU and voila!

nik.the said:
I'll try that. thanks.
Now on the same XP computer, it's not showing when I adb devices, however it does show in device manager. This changed after trying to do the RUU without relocking.
Click to expand...
Click to collapse
Not sure whats up with that, never had any issue on win7.

Windows 8 fastboot works on my laptop for some reason. I installed the drivers from the HTC Sync folder.
Sent from my HTC One S using Tapatalk 2

[Q] New tf300 unlocked and no longer registering touch

Hi everyone, hate for my first to be a call for assistance, but here goes. Bought an Asus tf300t earlier today. I unlocked the device, then attempted to begin walking through this guide(http://forum.xda-developers.com/showthread.php?t=1845377) in order to have root+jb. In order to install clockworkmod, set up fastboot. After getting an error of "cannot load" in fasboot for the recovery image, I gave up, used the cmd prompt to reboot the device. On reboot, the touch screen no longer responded. I went to recovery, wiped data, to no avail. Now its simply showing the welcome screen, where you choose english, but can't select start. I've rebooted, wiped, and swore. A lot. My OS is windows 7, if that helps. Thanks everyone.

Shourisha1 said:
Hi everyone, hate for my first to be a call for assistance, but here goes. Bought an Asus tf300t earlier today. I unlocked the device, then attempted to begin walking through this guide(http://forum.xda-developers.com/showthread.php?t=1845377) in order to have root+jb. In order to install clockworkmod, set up fastboot. After getting an error of "cannot load" in fasboot for the recovery image, I gave up, used the cmd prompt to reboot the device. On reboot, the touch screen no longer responded. I went to recovery, wiped data, to no avail. Now its simply showing the welcome screen, where you choose english, but can't select start. I've rebooted, wiped, and swore. A lot. My OS is windows 7, if that helps. Thanks everyone.
Click to expand...
Click to collapse
Do I understand correctly that you've never successfully installed a custom recovery on your tab? So how did you wipe data? You chose the fourth option in the stock recovery?

graphdarnell said:
Do I understand correctly that you've never successfully installed a custom recovery on your tab? So how did you wipe data? You chose the fourth option in the stock recovery?
Click to expand...
Click to collapse
There were only 3 options--Wipe Data, usb, and android. I'd had success rooting the tablet earlier, but believed I'd made an error somewhere so followed that guide to try and begin again from the beginning. The wipe wasn't what caused the issue. It was working fine, until the reboot using the cmd line. Thats what makes so little sense to me.

Shourisha1 said:
There were only 3 options--Wipe Data, usb, and android. I'd had success rooting the tablet earlier, but believed I'd made an error somewhere so followed that guide to try and begin again from the beginning. The wipe wasn't what caused the issue. It was working fine, until the reboot using the cmd line. Thats what makes so little sense to me.
Click to expand...
Click to collapse
You didn't have the RCK option on your recovery? You said the wipe wasn't the culprit and it was working fine. Did you get to reboot the tab successfully after the wipe? Now everything seems to work fine on your PC monitor doesn't mean it is so. Lots of people using NVflash derivatives witness a smooth transition on papers until they find out it isn't so. Reboot command from ADB doesn't do anything special. I can't think of it doing any damage to the firmware if successfully installed earlier.

graphdarnell said:
You didn't have the RCK option on your recovery? You said the wipe wasn't the culprit and it was working fine. Did you get to reboot the tab successfully after the wipe? Now everything seems to work fine on your PC monitor doesn't mean it is so. Lots of people using NVflash derivatives witness a smooth transition on papers until they find out it isn't so. Reboot command from ADB doesn't do anything special. I can't think of it doing any damage to the firmware if successfully installed earlier.
Click to expand...
Click to collapse
Uhm, well, its simply started registering touch again. Like nothing had happened. Makes me worry about the tablet itself. But, its working fine now, and I didn't do a thing. Sigh. I'm not sure. Not I just have to figure out why fastbooter keeps giving me the "cannot load recovery.img" error. Thanks for the help!

Sounds like you are on the old bootloader. Be careful about wiping.
I'd update to the latest Asus Stock ROM for your device from their website which will bring you up to the latest bootloader.

I've made a few extremely rash decisions, and I'm not sure if I can fix this.

Okay, this all happened because I tried to install CyanogenMod without taking into consideration the fact that I'm using the SV version, of which there does not seem to be any easy way to install CyanogenMod on.
My provider is Boost Mobile if that's important.
The first step I took was to unlock the bootloader, which was successful (I did use the HTCDev website, submit my identifier token, and it definitely worked).
The real trouble was when I tried flashing my recovery and boot .img's using the files in this link (for the HTC One S): ((I can't post links as a new user, but I tried acquiring my .img's from the CyanogenMod wiki, in the guide for the HTC One S, which was probably the root of this problem)
Terrible mistake, I know. I think my phone is bricked, but I'm not 100% sure because this is the first time I've tampered with any phone on this level. The only comparable mistake was when I accidentally formatted my hard drive when I tried installing Arch on my desktop, two years ago.
Right now, my phone won't start properly. When I do a normal bootup, by simply holding down the power button, I get treated to the HTC logo followed by a blank blackish-grey screen. I have to remove the battery to exit it. I can access fastboot, but when I attempt to access recovery I get taken to a perpetual load screen with an HTC logo and "Entering recovery mode..." on top of it. I have to remove my battery at this point because it never goes beyond that screen.
The other trouble is that while I seem to be able to access my phone through a USB cable, and apparently detect it using the "fastboot devices" command, the device itself doesn't seem to show up on Windows (as C525c, like it did before). I'm not sure if this has to do with me screwing up my boot and recovery .img's or my USB drivers.

Ok, this was not a good idea, to flash a boot.img from different device!
If there is any chance for your device, then try to flash the recovery from here (boost version).

old.splatterhand said:
Ok, this was not a good idea, to flash a boot.img from different device!
If there is any chance for your device, then try to flash the recovery from here (boost version).
Click to expand...
Click to collapse
Okay, I just did. I am finally able to boot into recovery! Thanks!
I'm not sure what I should do next though, because I don't want to screw it up again. Which options should I choose?
They are: Install, Wipe, Backup, Restore, Mount, Settings, Advanced, Reboot.

I'll guess you don't have a backup to restore?
Then you can try to restore some from here.
Or somebody gives you an backup from 4.2.2 boost version.

old.splatterhand said:
I'll guess you don't have a backup to restore?
Then you can try to restore some from here.
Or somebody gives you an backup from 4.2.2 boost version.
Click to expand...
Click to collapse
I'm unable to use any of the mega.co.nz links. I get taken to a loading screen, but it never actually starts downloading.

Try another browser.