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.

recover options for bricked TF700 Please Help!!!

I just got my TF 700 and rooted an unlocked it, and all was ok, but then installed an app from the app store and now I only get "booting recovery kernel image" I was able to boot to APX mode install the driver and use Universal root toolkit for the TF and install the firmware from ASUS website but I think the boot image file is the problem. The transformer.bct is not for the TF700. Thanks in advace for any help.

xdatester11 said:
I just got my TF 700 and rooted an unlocked it, and all was ok, but then installed an app from the app store and now I only get "booting recovery kernel image" I was able to boot to APX mode install the driver and use Universal root toolkit for the TF and install the firmware from ASUS website but I think the boot image file is the problem. The transformer.bct is not for the TF700. Thanks in advace for any help.
Click to expand...
Click to collapse
Are you able to boot in recovery?
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

Pretoriano80 said:
Are you able to boot in recovery?
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
No I cannot boot into recovery only APX mode and use nvflash. I am able to flash files. I have flashed the factory firmware from Asus. I think it is the boot image that is still bad. I used the recovery tool BRK_RootKit_v8.0_final to flash the image file but it tries to flash the original TF transformer.bct boot file. I think If I had the correct transformer.bct for the TF700 it would work.

xdatester11 said:
No I cannot boot into recovery only APX mode and use nvflash. I am able to flash files. I have flashed the factory firmware from Asus. I think it is the boot image that is still bad. I used the recovery tool BRK_RootKit_v8.0_final to flash the image file but it tries to flash the original TF transformer.bct boot file. I think If I had the correct transformer.bct for the TF700 it would work.
Click to expand...
Click to collapse
AFAIK the nvflash method doesn't work for TF700 and is possible that you really bricked your device... The only solutionn i can see is to flash a recovery in fastboot mod and flash the Asus stock from there,but if you can't even boot in fastboot then i don't see any other way to recover the device.

xdatester11 said:
No I cannot boot into recovery only APX mode and use nvflash. I am able to flash files. I have flashed the factory firmware from Asus. I think it is the boot image that is still bad. I used the recovery tool BRK_RootKit_v8.0_final to flash the image file but it tries to flash the original TF transformer.bct boot file. I think If I had the correct transformer.bct for the TF700 it would work.
Click to expand...
Click to collapse
I was hoping someone would be willing to make a backup of their file using nvflash. I think the zip should help.

xdatester11 said:
I was hoping someone would be willing to make a backup of their file using nvflash. I think the zip should help.
Click to expand...
Click to collapse
attachment

NVFlash works with the TF700??? That's news to me!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

xdatester11 said:
I was hoping someone would be willing to make a backup of their file using nvflash. I think the zip should help.
Click to expand...
Click to collapse
Sorry mate,but according to this --> http://androidroot.mobi/2012/07/15/nvflash-for-tegra3-transformer-prime/ <-- i don't think you will be able to use nvflash for recovery and it clearly states that you need to get fastboot working in order to use that method. (to get in fastboot mode press Volume down + Power and release the buttons when the message about having 5 second to press Volume Up shows...if this work you will get to a menu with the "USB icon" wich means boot in fastboot mode).
P.S : Can you tell us why you had to mess with nvflash?That is the most advanced way to recover/backup the Transformer 101/201 series and you have really high chances to brick your device for good.
EDIT: I don't think someone here will be able to make a backup for you with nvflash...it will only lead to more bricks.
EDIT 2: Can you please tell us the name of the app that bricked your device so we can avoid other people bricking their device?

The app was transformer reboot recovery I think.
I only used nvflash because it was the only option left as the tab wouldn't work with adb or fastboot.
I guess I'll keep it as a paper weight.

xdatester11 said:
The app was transformer reboot recovery I think.
Click to expand...
Click to collapse
weird, ive been using that app for a couple of days with no issues. but now I think I will uninstall it until someone can confirm that this causes problems.

henbone11 said:
weird, ive been using that app for a couple of days with no issues. but now I think I will uninstall it until someone can confirm that this causes problems.
Click to expand...
Click to collapse
Yes,i also used that app with no issue,but one of the developers behind TWRP advised to not use it at all,because if for some reason your recovery gets corrupted (that app send a custom command to boot into recovery) the device will boot loop trying to get in recovery and without nvflash we don't have many options to recover from that.
"
KEEP AWAY from that app for the moment,just stick with the old good " Volume Down + Power and then Volume UP " method to get into recovery.

Same issues here as well
I had rooted the TF700 ( as i wanted to download a market fix for my region, as i wasnt able to download GTA III) and had installed the eris market fix app :sillymy stupidity) it changed certain values to the original market application. After a reset/ reboot i was stuck at the powered by Nvidia Screen. I tried colding booting/ wiping etc non would work. I tried reinstalling the boot/system files through fastboot still no luck. what i cant understand is the fastboot setup seems to work when i id the Device it shows:
"? Fastboot"
i can reboot, push the system/ boot and recovery files, but cant boot into recovery mode. i have even pushed the twrp 2.2 file through fastboot. My only bet would be to boot into recovery so that i could mount and push custom roms.
I have even tried flashing the rom update through the following command "Fastboot flash update filename" however i get the archive cannot find android-info.txt error .
Is there anyway i could boot into recovery. (previously i could boot into recovery, but when i formatted/ erased the system and boot files i only get 2 options 1. Wipe Data & Cache & 2. Fastboot (USB). I tried holding the vol down button and the power button but that just puts me into blank screen mode and the APX driver pops up on the device manager.
I had to uninstall all my current drivers supporting asus and manually select the asus fastboot interface to get the fastboot working.
Any ideas would be helpful.

shasan2 said:
I had rooted the TF700 ( as i wanted to download a market fix for my region, as i wasnt able to download GTA III) and had installed the eris market fix app :sillymy stupidity) it changed certain values to the original market application. After a reset/ reboot i was stuck at the powered by Nvidia Screen. I tried colding booting/ wiping etc non would work. I tried reinstalling the boot/system files through fastboot still no luck. what i cant understand is the fastboot setup seems to work when i id the Device it shows:
"? Fastboot"
i can reboot, push the system/ boot and recovery files, but cant boot into recovery mode. i have even pushed the twrp 2.2 file through fastboot. My only bet would be to boot into recovery so that i could mount and push custom roms.
I have even tried flashing the rom update through the following command "Fastboot flash update filename" however i get the archive cannot find android-info.txt error .
Is there anyway i could boot into recovery. (previously i could boot into recovery, but when i formatted/ erased the system and boot files i only get 2 options 1. Wipe Data & Cache & 2. Fastboot (USB). I tried holding the vol down button and the power button but that just puts me into blank screen mode and the APX driver pops up on the device manager.
I had to uninstall all my current drivers supporting asus and manually select the asus fastboot interface to get the fastboot working.
Any ideas would be helpful.
Click to expand...
Click to collapse
1The first step is to get your recovery back and working...here's a how-to:
1) Download the recovery from here
2) Follow the instruction on how to flash the recovery in fastboot mode
If the flash went good and you can get in recovery mode follow this steps:
1)Download the 9.4.5.26 firmware from Asus site (the SKU for your region)
2)Extract the .zip file somewere on your desktop (the result will be another .zip file,use it for step 3)
3)Put the extracted zip to a MicroSD card
4)Insert the MicroSD card in your tablet and boot into recovery
5)Install the zip from recovery and restard when done
If all goes well your tablet will be again up and running

Ray of Teamwin
:good::good::good:Thanks a million, seeing the team win screen relieved me. The only problem is i cant boot into recovery (teamwin screen is visible)through the wipe data mode, wherein everything is wiped and it reboots automatically. I cant seem to force the table into recovery without this is there any fastboot command which i can use to force the tablet into recovery.

Need Stock Boot, Recovery, System img
Still no luck with the recovery mode. Every time i wipe the device it automatically reboots. I was wondering if i could get hold of stock recovery, boot and system .img files so that i can push them or flash them through fastboot.
i tried using the blob pack and unpack but i cant seem to get around the blob header thing.
Anyone to spare me stock .img files

End of Infinity
Okay my frustration has led me to "fastboot erase bootloader" and now i am permanently stuck in APX mode.
However as nvflash is not avaliable for tf700t i guess i wont be using this for quiet sometime. Unless nvflash is made available

shasan2 said:
Okay my frustration has led me to "fastboot erase bootloader" and now i am permanently stuck in APX mode.
However as nvflash is not avaliable for tf700t i guess i wont be using this for quiet sometime. Unless nvflash is made available
Click to expand...
Click to collapse
There's a thread (I can't find it again) that talks about this "Reboot into Recovery" app and how it might be bricking TF700T's. This guy wrote in, because he could not get to the recovery menu at all any more and could not do the "PWR+VOL-DOWN" combo. Nothing would happen. Maybe this was the thread, I don't know.
An XDA Mod in another thread said the app *might* be bricking them, but was waiting for confirmation before posting that it does.
I wish to confirm that IT DOES BRICK TF700T's! IT DOES!!!
And there is NOT A DAMN THING you can do! Your PC will not even recognize that the device is connected! You cannot get to the little icons to pick USB Mode, or whatever it's called.
This is the free app, not the other pay one in the Market. I don't know about that one, but this one is called, "Reboot into Recovery" and if you can somehow find that thread if I don't and just copy my post there, I would really appreciate it! I just want to warn people, ya know?
Also, using ANY of the "ROM Managers", whether it's CWM's, or GooMgr's, will take away all ability to get to a recovery menu at boot, at all! The device will still work and everything and boot to your Home Screen and everything. It won't be bricked like the app listed above does to it, but it will take away your recovery menu altogether and the PWR+VOLDOWN thing won't work any more either.
You can Unlock the TF700T, you can Root it. But you cannot use ANY ROM Mgr and you cannot use that Reboot into Recovery app.
But the app I listed above WILL BRICK YOUR DEVICE BEYOND ANY RECOVERY METHOD!
Please pass this on, I am confirming the experience. It doesn't matter if others say it worked for them. It is bricking them at random and even one of the guys who reviewed the app (diff guy than the one who posted here) said it bricked his. It is happening! It is not the user messing up! I did do it right!
Thanks!

I'm not sure if you are talking about the app named "Transformer Reboot to Recovery", but that particular app works fine on the TF700 - I use it all of the time.
The only time that it *can* cause problems is if your recovery is already corrupt or there is some other issue, in which case it can cause a bootloop.
But, if there are no issues, it works fine... There is a risk involved, like I said, if there are pre-existing problems with your device, but if you know that everything is working fine on your device, the app mentioned above works fine.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

jtrosky said:
I'm not sure if you are talking about the app named "Transformer Reboot to Recovery", but that particular app works fine on the TF700 - I use it all of the time.
The only time that it *can* cause problems is if your recovery is already corrupt or there is some other issue, in which case it can cause a bootloop.
But, if there are no issues, it works fine... There is a risk involved, like I said, if there are pre-existing problems with your device, but if you know that everything is working fine on your device, the app mentioned above works fine.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
No offense, but I think a huge problem in forums, is that people don't read carefully.
1) I think you are referring to the paid app. Read what I said about that.
2) You're saying what you're saying, in a thread started by a guy who had a running device and who didn't after using the app.
3) I said that it bricks them AT RANDOM.
4) Another problem with forums, is that whenever someone has a problem, A LOT of users want to post responses that ignore the users' experience and they want to act like the problem doesn't "really" exist. If multiple people are posting the same problem, then IT DOES EXIST. It just doesn't exist for YOU! But something working for you, does not mean it works for everybody and it does not mean there is a problem with their device, nor that they did something wrong.
5) And yet another problem with forums, is that when someone like me points things like this out, many users will respond by jumping on me, instead of those who try to make the guy feel like he's hallucinating and who, instead of trying to help him out, or just keep their mouths shut if they have nothing helpful to offer, think the right thing to do is to argue with the person having the problem.
These forums are for help and information. If someone has neither to offer the person, or at least warn others, then why are they responding at all? And why would anyone defend someone doing that?! It's ridiculous! But that's what typically happens, especially in XDA doe some reason (lots of snobs here, who like to prove they are, by doing as I just described).
The bottom line is, you do not run the app I talked about and even if you did, that does not take away from the experience that some have had and the best thing, is to avoid the app, because there's a risk involved and there is no recovery from it. I decided to warn people. You decided to tell us that we're hallucinating and that people should use the app. You did not carefully read what I wrote, or you would have checked the Market to see what the name of the app that does not have a pay version is. The one I am talking about does not.
I will tell you this. I am posting this from my laptop, because I had to return my Tablet and have a replacement shipped and now I have to spend a few days getting it all set up again the way I had it.
Avoid the ROM Mgr apps on the TF700T. And avoid the free app called "Reboot into Recovery". A user told me about it for my device, who had seen it used successfully. However, if you look at the reviews in the Market, you'll see that one of them says it bricked his *WORKING* *FINE* tablet and this thread right here has told you about two more. So just believe it and don't criticize, huh?
Okay Mods, feel free to jump on me again, just like last time.

I agree with many of your points, Zeuszoos, and thanks for pointing that out, but I believe there are many senior members at XDA willing to help if they have knowledge/abilities to do so, that's been my experience so far and hopefully it can be yours too. Of course, a little SEARCH won't hurt before posting one's problem, as you reasonably mentioned yourself
"reboot to recovery" has been in my apps STICKY thread in the sections "apps to avoid" (RED) for quite some time now after first reports of bricking users' devices started popping up and I believe it has helped some users who did a little reading before clicking...

Potentially F'ed TF300T

I was wiping my tab getting ready to sell it to my cousin. I was in recovery TWRP 2.22 I think. I walked away when my 4 yr son got a hold of it. I came back to see he wiped everything meaning the system. So tried to recover from my nandroid back up but it was gone with everything on my internal SD. I tried mounting the tab to my PC to transfer the old ROM back on but it wouldn't see it with any drivers I've tried. I also tried putting it on my microSD that was in there and it's also not being seen by TWRP 2.22.
I tried to fastboot flash the OEM JB ROM on it when all else failed in TWRP recovery. That didn't work. I tried flashing a CWM recovery to see if it would work better than the old TWRP I had. But after flashing that, my tab won't boot to fastboot and goes in a constant boot loop lol. SMFH at this madness. When the until turns on, it shows the device is unlocked. If I hold the vol down, it will say it's going to recovery then restarts every time no matter what. All I want to do is see if this is even remotely possible to recover from. If not this joint is going on Feebay to game some cash back. So if anyone has any good idea's. I'm open to whatever. What's he worst that can happen. My tab becomes an even bigger bricked unit lol.

Anybody know what options I got? I've read through many threads and none seem to have the answer I'm looking for.

So you extracted the blob file from the Asus official firmaware and flash system blob in fastboot? And that failed?
Sent from my Galaxy Nexus using xda premium

larryv1979 said:
So you extracted the blob file from the Asus official firmaware and flash system blob in fastboot? And that failed?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yeah I tried that about 40 times. On 3 PCs with the Asus transformer pad usb drivers on all. I could fastboot TWRP latest recovery then it caused my tab to go into a endless boot loop. I can't get into fastboot mode no more.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

Does it get recognized by the PC? Check Device Manager and see if its recognized. If it is and it has an alert (meaning it needs troubleshooting) right click the device update driver and when it asks you select the option where you search manually through a list of drivers. In there try looking for android ADB driver should be one of the first, install it and try again.

It shows up as Asus ADB Interface. But as soon as I attempt to get the to get back to fastboot or even recovery it reboots. So I think the system is dead because nothing I've read seems to be related or can help this system out.

Don't know if this will help, but have you tried the hard reset button?

Where's that? I know that's a potentially a [email protected] question but I didn't realize there was a hard reset button.

JayWheelz said:
Where's that? I know that's a potentially a [email protected] question but I didn't realize there was a hard reset button.
Click to expand...
Click to collapse
AFAIK its the small hole under the microsd slot.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2

I tried that hard reset button and it doesn't help. But I managed to put the tablet in a state where it's recognized by my PC looking for a APX driver. Then I found a Asus APXusb driver but still don't know what I can do from here. After installing the driver. I still can't fastboot or adb to the device. So again I think this tab is a brick.

[Q] Bricked TF300TG

Hello all,
I seem to have really soft bricked my TF300TG. I've now run out of ideas and maybe someone in here can help.
The following happend: I wanted to update my rooted TF300TG from running JB (CleanRom 3.0.4) with Bootloader ww_epad_10.4.3.9 to the current stock Rom from ASUS ( V10.6.2.6 ). I did unzip the zip from ASUS once and used the resulting zip for the flash.
I attemted this via Method 3: TWRP v. 2.5.0.0, following this guide (http://forum.xda-developers.com/showthread.php?t=2187982), guess I should have read the whole thread, not just the first 20 pages.
What happend was, that during the flash in TWRP I got an error with no error message. I tried to flash again for three times with the "same" error. Thats when I panicked and rebooted the device.
Since then its sitting here, just showing the ASUS logo and doing nothing. I think I understand why its doing nothing since I have still the old bootloader v 10.4.3.9 but a new 4.2 Stock ROM (albeit maybe damaged).
Sadly I have also had no success communicating with the device via ADB or Fastboot.
I still can access the bootloader menue which shows 4 icons: RCK, Android, USB and Wipe. But: the volume up key is not working (did work in Android though) and the volume down key traverses the item entries. So I have no way to select USB which should put me into fastboot mode.
Does anyone have any idea? Otherwise I'm declaring this my last Android tablet (loved it but it didn't quite live up to expectations, Tegra 3 just sucks) and move on.
Thanks for reading!

jak4kaj said:
Hello all,
I seem to have really soft bricked my TF300TG. I've now run out of ideas and maybe someone in here can help.
The following happend: I wanted to update my rooted TF300TG from running JB (CleanRom 3.0.4) with Bootloader ww_epad_10.4.3.9 to the current stock Rom from ASUS ( V10.6.2.6 ). I did unzip the zip from ASUS once and used the resulting zip for the flash.
I attemted this via Method 3: TWRP v. 2.5.0.0, following this guide (http://forum.xda-developers.com/showthread.php?t=2187982), guess I should have read the whole thread, not just the first 20 pages.
What happend was, that during the flash in TWRP I got an error with no error message. I tried to flash again for three times with the "same" error. Thats when I panicked and rebooted the device.
Since then its sitting here, just showing the ASUS logo and doing nothing. I think I understand why its doing nothing since I have still the old bootloader v 10.4.3.9 but a new 4.2 Stock ROM (albeit maybe damaged).
Sadly I have also had no success communicating with the device via ADB or Fastboot.
I still can access the bootloader menue which shows 4 icons: RCK, Android, USB and Wipe. But: the volume up key is not working (did work in Android though) and the volume down key traverses the item entries. So I have no way to select USB which should put me into fastboot mode.
Does anyone have any idea? Otherwise I'm declaring this my last Android tablet (loved it but it didn't quite live up to expectations, Tegra 3 just sucks) and move on.
Thanks for reading!
Click to expand...
Click to collapse
Try resetting the device (the little hole beneath the volume rocker and try to get to fastboot. there is no real reason other than broken PITs or trashfiles in /misc that should prevent you form getting fastboot.
also read my post here (or better the threat)
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
gl
buster

Buster99 said:
Try resetting the device (the little hole beneath the volume rocker and try to get to fastboot. there is no real reason other than broken PITs or trashfiles in /misc that should prevent you form getting fastboot.
also read my post here (or better the threat)
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
gl
buster
Click to expand...
Click to collapse
Hi buster,
thanks for the reply. Sadly I can't seem to enter fastboot since "fastboot erase system" stays at "waiting for device" when I reset the device with a paper clip and press the volume down button.
I'm trying this on linux but that should be a plus versus using windows.
Thanks again
jak4

jak4kaj said:
Hi buster,
thanks for the reply. Sadly I can't seem to enter fastboot since "fastboot erase system" stays at "waiting for device" when I reset the device with a paper clip and press the volume down button.
I'm trying this on linux but that should be a plus versus using windows.
Thanks again
jak4
Click to expand...
Click to collapse
yeah - linux sometimes is less of a nightmare when it comes to fastboot commands - but remember to install adb and fastboot
gl
Buster

Buster99 said:
yeah - linux sometimes is less of a nightmare when it comes to fastboot commands - but remember to install adb and fastboot
gl
Buster
Click to expand...
Click to collapse
Yes I have fastboot and adb installed. They come with the Android SDK which I need for work.
jak4

I have the same problem. Difference is that I did a reset after a failed install of CM11. Stuck at ASUS splash. Cannot access recovery or any other option that was previously available. Nothing is detecting the device as it sits...Tried Ubuntu, Win 7, Win 8.1. I have tried installing all drivers I could find, even tried installing as legacy device, but all drivers give an error that device cannot start. Did A LOT of searching around, and it seems to come down to the tablet not being detected by PC in the state it's in. Seems like there is a lot of help out there for folks that can get their computers to at least see the device.
Would die for some help!

coppervines said:
I have the same problem. Difference is that I did a reset after a failed install of CM11. Stuck at ASUS splash. Cannot access recovery or any other option that was previously available. Nothing is detecting the device as it sits...Tried Ubuntu, Win 7, Win 8.1. I have tried installing all drivers I could find, even tried installing as legacy device, but all drivers give an error that device cannot start. Did A LOT of searching around, and it seems to come down to the tablet not being detected by PC in the state it's in. Seems like there is a lot of help out there for folks that can get their computers to at least see the device.
Would die for some help!
Click to expand...
Click to collapse
what recovery did you use for installing cm11?

Buster99 said:
what recovery did you use for installing cm11?
Click to expand...
Click to collapse
CWM from probably close to a year ago. I attempted to use Rom Manager to flash a newer recovery that would work with CM11, and got stuck in a bootloop. Then I stupidly did a factory reset from boot menu . Wish there was a way around this...and I think I could work some magic if I could get a computer to detect the brick.

coppervines said:
CWM from probably close to a year ago. I attempted to use Rom Manager to flash a newer recovery that would work with CM11, and got stuck in a bootloop. Then I stupidly did a factory reset from boot menu . Wish there was a way around this...and I think I could work some magic if I could get a computer to detect the brick.
Click to expand...
Click to collapse
yeah well with an old recovery kitkat gets you a brick - try to get it somehow to fastboot and you should be able to get it working again
gl
buster

Buster99 said:
yeah well with an old recovery kitkat gets you a brick - try to get it somehow to fastboot and you should be able to get it working again
gl
buster
Click to expand...
Click to collapse
I would hate to think that my USB cable could be bad...it's been a LONG time since its done anything other than charge. Just need the pc to see the damn thing. ANY insight would be helpful.

APX
I was able to get to APX mode with the universal drivers (Vol +reset)...looking around to see if anyone else has had success. I never installed Nvflash...

in the other threat a guy just needed a working cable to get it to work. it's a pain with asus and the cable
gl
buster
Sent from my GT-I9505 using XDA Premium 4 mobile app

Buster99 said:
in the other threat a guy just needed a working cable to get it to work. it's a pain with asus and the cable
gl
buster
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
What thread? Not sure I understand what you mean...

http://forum.xda-developers.com/showthread.php?t=2179759
Sent from my TF300T using XDA Premium 4 mobile app

Buster99 said:
http://forum.xda-developers.com/showthread.php?t=2179759
Sent from my TF300T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Since i have apx access, i'm assuming the data side of the cable is working...plus, without being able to get into adb/fastboot on the tablet a new cable would be useless. Thinking about getting a mobo on ebay...one for 50 and one for 75$ i think. will have to get wife's approval first

coppervines said:
Since i have apx access, i'm assuming the data side of the cable is working...plus, without being able to get into adb/fastboot on the tablet a new cable would be useless. Thinking about getting a mobo on ebay...one for 50 and one for 75$ i think. will have to get wife's approval first
Click to expand...
Click to collapse
So I'm assuming there is no solution to this problem without sending it to ASUS or getting a new Motherboard?
I'm in the exact same position...

coppervines said:
CWM from probably close to a year ago. I attempted to use Rom Manager to flash a newer recovery that would work with CM11, and got stuck in a bootloop. Then I stupidly did a factory reset from boot menu . Wish there was a way around this...and I think I could work some magic if I could get a computer to detect the brick.
Click to expand...
Click to collapse
Wipe data from the bootloader erases everything, if you don't have nvflash blobs I think you're done for.

ebildude123 said:
Wipe data from the bootloader erases everything, if you don't have nvflash blobs I think you're done for.
Click to expand...
Click to collapse
"bootloader wipe data" soft brinks your tab.
always use custom recovery or fastboot to wipe the tf300t.
otherwise you need to erase all partitions and reflash recovery and start from scratch. assuming that fastboot still works.
cheers
buster
Sent from my GT-I9505 using XDA Premium 4 mobile app

Buster99 said:
"bootloader wipe data" soft brinks your tab.
always use custom recovery or fastboot to wipe the tf300t.
otherwise you need to erase all partitions and reflash recovery and start from scratch. assuming that fastboot still works.
cheers
buster
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Boot loader wipe is a hard(ish) brick unless you have nvflash blobs since all you have access to is apx mode, no boot loader, no recovery, etc.
Sent from my TF300T on OmniROM (4.4.2) using Tapatalk 4

not necessarily, I did it for cm10.1 (drunken flashing not advised ) and i don't have an NV backup.
and i had fastboot to work with.
but things may have changed since then.
cheers
buster
Sent from my GT-I9505 using XDA Premium 4 mobile app

[Q] ADB Sideload

I'm attempting to get my Memo Pad 8 fixed. I've got it into a bootloop by modifying build.prop and the only way to fix it is to change it back. I used a DPI changer app, and I felt that I was close to success yesterday, but may have been farther than I'd hoped. I went into recovery and when I used adb devices I got a set of numbers and then the word "sideload". A few commands worked. At the beginning, I attempted "adb pull /system/build.prop C:\Users\user\Desktop", replacing user with my computer name, and got "error: closed". Eventually, I did some things and then got that long list of suggested commands. I don't know what I'm doing wrong. My tablet is able to power on but I can't get into adb because I attempted at a factory reset before all of this. Can someone help me, is there anyway to change build.prop, or am I done for?

Any help?

@Klamman What recovery?

AJM-hackers said:
@Klammanmann What recovery?
Click to expand...
Click to collapse
I'm using the stock Memo Pad 8 recovery. I'm a newbie when it comes to these things. I'm using Android system recovery <3e>, recovery system version 4.2.31 apparently.

Klamman said:
I'm using the stock Memo Pad 8 recovery. I'm a newbie when it comes to these things. I'm using Android system recovery <3e>, recovery system version 4.2.31 apparently.
Click to expand...
Click to collapse
Maybe root is too much freedom for me to handle xD
(I am still in need of help )

Error: Closed
Nevermind... I'm still getting error: closed... please don't tell me that my situation is that hopeless... :'(

Klamman said:
Nevermind... I'm still getting error: closed... please don't tell me that my situation is that hopeless... :'(
Click to expand...
Click to collapse
Don't stress, it can be fixed! When booting hold the power button and Vol down key (it might be up I'm not sure). This will show you three icons (or maybe four). Go to the one saying factory reset/wipe data using volume down, and select it using vol. up. It''ll wipe everything and return everything to stock

AJM-hackers said:
Don't stress, it can be fixed! Your problem is that you need to install TWRP.
Click to expand...
Click to collapse
I'm asking some others for a copy of their build.prop (memo pad 8)
If I have this, would I need to use TWRP? I'd rather not change my recovery, as I've still got warranty for the place I got it from.

Okay, I've got the file.
Now, uhm, what do I do next?

Also, a factory reset is not deep enough, the system files have been edited, namely build.prop

Klamman said:
Also, a factory reset is not deep enough, the system files have been edited, namely build.prop
Click to expand...
Click to collapse
Did you at least attempt a full wipe/ factory reset? build.prop is in /system which it wipes. To use that file remove the .txt extension, go to recovery, mount system(which I'm pretty sure stock recovery can'' do) and adb push the new file.

AJM-hackers said:
Did you at least attempt a full wipe/ factory reset? build.prop is in /system which it wipes. To use that file remove the .txt extension, go to recovery, mount system(which I'm pretty sure stock recovery can'' do) and adb push the new file.
Click to expand...
Click to collapse
Yeah, I attempted multiple wipes which is why my usb debugging was disabled. I'm really new to adb, how do I mount /system? I've tried multiple commands, but most of them come up to error: closed.

Klamman said:
Yeah, I attempted multiple wipes which is why my usb debugging was disabled. I'm really new to adb, how do I mount /system? I've tried multiple commands, but most of them come up to error: closed.
Click to expand...
Click to collapse
I meant the factory reset option not wipe, as I said dig through recovery options I really don't think it'll be there though. BTW I think you should go to your respective forum on XDA I only have an ASUS TF700 and can't really help you unless you take pics of your bootloader options and recovery options and upload them here.

AJM-hackers said:
I meant the factory reset option not wipe, as I said dig through recovery options I really don't think it'll be there though. BTW I think you should go to your respective forum on XDA I only have an ASUS TF700 and can't really help you unless you take pics of your bootloader options and recovery options and upload them here.
Click to expand...
Click to collapse
http://www.smartmobilephonesolutions.com/content/stuck-android-system-recovery
If you go to that link, the first photo shows you what my recovery looks like.
Is there a specific forum for the Memo Pad 8?

AJM-hackers said:
I meant the factory reset option not wipe, as I said dig through recovery options I really don't think it'll be there though. BTW I think you should go to your respective forum on XDA I only have an ASUS TF700 and can't really help you unless you take pics of your bootloader options and recovery options and upload them here.
Click to expand...
Click to collapse
I'm not 100% sure what my bootloader is... is it the first thing that shows up when I hold down vol+ and power? When I do that, I get "No Command", then I have to do a series of taps (one quick power tap, then one quick power and vol+ tap) to get into the place where I can choose what to do.

Klamman said:
I'm not 100% sure what my bootloader is... is it the first thing that shows up when I hold down vol+ and power? When I do that, I get "No Command", then I have to do a series of taps (one quick power tap, then one quick power and vol+ tap) to get into the place where I can choose what to do.
Click to expand...
Click to collapse
Yes, when you first power on using vol+pwr that's it, can you take a pic of this "no command". Did you do data/factory reset in recovery? I'm you beg someone else for a rom.zip you can adb sideload it using the option that says install from adb

AJM-hackers said:
Yes, when you first power on using vol+pwr that's it, can you take a pic of this "no command". Did you do data/factory reset in recovery? I'm you beg someone else for a rom.zip you can adb sideload it using the option that says install from adb
Click to expand...
Click to collapse
Originally Posted by Klamman View Post
"But it seems that, due to the Memo Pad 8's limited recovery settings, a full ROM is required to unbrick my device.
If anyone can provide the full ROM for the stock Memo Pad 8, I'd be forever grateful, and I'm sure other people would be as well!
If you need instructions, I can provide them as well
Thank you so much in advance!"
I may be able to help. Am I just dd'ing partitions?
Is this was he has to do? It seems that my hopes of reviving my Memo Pad may come to reality!

Klamman said:
Originally Posted by Klamman View Post
"But it seems that, due to the Memo Pad 8's limited recovery settings, a full ROM is required to unbrick my device.
If anyone can provide the full ROM for the stock Memo Pad 8, I'd be forever grateful, and I'm sure other people would be as well!
If you need instructions, I can provide them as well
Thank you so much in advance!"
I may be able to help. Am I just dd'ing partitions?
Is this was he has to do? It seems that my hopes of reviving my Memo Pad may come to reality!
Click to expand...
Click to collapse
Do you still have the problem? If so tell whoever it is to make a system dump of the firware, it;s very straightforward, it's like the first result on Google. Cheers, you're almost there!

Klamman said:
Originally Posted by Klamman View Post
"But it seems that, due to the Memo Pad 8's limited recovery settings, a full ROM is required to unbrick my device.
If anyone can provide the full ROM for the stock Memo Pad 8, I'd be forever grateful, and I'm sure other people would be as well!
If you need instructions, I can provide them as well
Thank you so much in advance!"
I may be able to help. Am I just dd'ing partitions?
Is this was he has to do? It seems that my hopes of reviving my Memo Pad may come to reality!
Click to expand...
Click to collapse
As I've already written a how to in german,I think I could help you:
Obviously there is a stock rom indeed, but you have to modify it (dl link is saved as a txt file in the attachments, because i'm not allowed to post URLs
After you have downloaded it you open it with 7zip and navigate to X:\UL-K00L-WW-2.0.0.4-user.zip\META-INF\com\google\android\
and push the modified updater-script to there(it is attached as a .txt file but remove the extension, otherwise it won't work) .
i hope i could help you

AJM-hackers said:
Yes, when you first power on using vol+pwr that's it, can you take a pic of this "no command". Did you do data/factory reset in recovery? I'm you beg someone else for a rom.zip you can adb sideload it using the option that says install from adb
Click to expand...
Click to collapse
if there's a "no command" you're already in the recovery, just press power and vol+ and then it shows you the recovery.
I recommend installing cwm although, you're not able to update OTA anymore, but its way better than the stock recovery