Database Info

Need help restoring device, big problem, read inside

Could someone please help me with this? I have posted a thread over on Android Forums with all the problems.
http://androidforums.com/asus-eee-p...restoring-device-big-problem-read-inside.html
Also, I have posted on here in the past about this, but I honestly am a giant noob at android and did not know what they were telling me to do.
Any help would be really great, thanks!

Since you can still boot your OS, you should be in good shape.
Try installing GooManager from the Play Store.
After installed, open it and grant root permissions.
Next, tap the menu key in the top right (3 stacked boxes) and then choose the Install OpenRecovery Script. This will install TWRP recovery which is far superior to any CWM I have ever run.
See if that installs properly (if yes, you will end up in TWRP recovery during a reboot)
TWRP allows you to see the internal and external memory to flash new ROMs.

frederuco said:
Since you can still boot your OS, you should be in good shape.
Try installing GooManager from the Play Store.
After installed, open it and grant root permissions.
Next, tap the menu key in the top right (3 stacked boxes) and then choose the Install OpenRecovery Script. This will install TWRP recovery which is far superior to any CWM I have ever run.
See if that installs properly (if yes, you will end up in TWRP recovery during a reboot)
TWRP allows you to see the internal and external memory to flash new ROMs.
Click to expand...
Click to collapse
I will try this out when I get home. Thank you. I will report back with what happens.
Edit: Also congratulations on 100 thanks.

format your micro SD and only put the ROM you want in it. Now install twrp as other guy said and reboot into twrp recovery in go to wipe and wipe (dalvik, cache, internal memory, system and everything else expect micro SD). Then do a clean installation of ROM and you should be good to go.. if that doesn't work then try easy flash
Sent from my Transformer using xda app-developers app

frederuco said:
Since you can still boot your OS, you should be in good shape.
Try installing GooManager from the Play Store.
After installed, open it and grant root permissions.
Next, tap the menu key in the top right (3 stacked boxes) and then choose the Install OpenRecovery Script. This will install TWRP recovery which is far superior to any CWM I have ever run.
See if that installs properly (if yes, you will end up in TWRP recovery during a reboot)
TWRP allows you to see the internal and external memory to flash new ROMs.
Click to expand...
Click to collapse
This did not work, I still boot into cwm when the device restarts after downloading it.

Here is another thing to try:
If you can boot and want to try TWRP, here is another way to install it so long as you are rooted:
Download the 2.3.2.3 blob from HERE
Place the recovery blob in the /sdcard/ directory. We are going to pretend the downloaded file is called TWRP.blob
Open a terminal window and enter these commands
Code:
su
cd /sdcard/
ls
dd if=TWRP.blob of=/dev/block/mmcblk0p4
reboot recovery
the ls will tell you if the blob is indead where it is supposed to be, if it can be seen, you should be good to go on to the dd command, if you don't see the file, do not procede.
Make sure to change TWRP.blob to the actual name and location of the file you downloaded
Let me know how it goes

frederuco said:
Here is another thing to try:
If you can boot and want to try TWRP, here is another way to install it so long as you are rooted:
Download the 2.3.2.3 blob from HERE
Place the recovery blob in the /sdcard/ directory. We are going to pretend the downloaded file is called TWRP.blob
Open a terminal window and enter these commands
Code:
su
cd /sdcard/
ls
dd if=/TWRP.blob of=/dev/block/mmcblk0p4
reboot recovery
the ls will tell you if the blob is indead where it is supposed to be, if it can be seen, you should be good to go on to the dd command, if you don't see the file, do not procede.
Make sure to change TWRP.blob to the actual name and location of the file you downloaded
Let me know how it goes
Click to expand...
Click to collapse
I cannot connect the device to my computer at all. I have usb debugging enabled and everything. It freezes for a couple of seconds when I plug the device in, and then says that installing the drivers has failed in windows. I am trying to run adb and it says no devices are connected.

BloodyRory said:
I cannot connect the device to my computer at all. I have usb debugging enabled and everything. It freezes for a couple of seconds when I plug the device in, and then says that installing the drivers has failed in windows. I am trying to run adb and it says no devices are connected.
Click to expand...
Click to collapse
You don't need to do this on your PC, so long as you can boot you can do it on your tablet.

frederuco said:
You don't need to do this on your PC, so long as you can boot you can do it on your tablet.
Click to expand...
Click to collapse
Ah, sorry, long time since I've done this. Alright, well I've gotten into terminal emulator and I've typed that exactly, switching over my directory to my microsd though and changing the file name to the exact one. I'm getting a "cannot open for read: No such file or directory" error when I do this. I have also tried moving the file to /sdcard/ and I have named the file twrp.blob, and neither of these have helped.

Did you issue the su command and get a popup for root access?

frederuco said:
Did you issue the su command and get a popup for root access?
Click to expand...
Click to collapse
Yes, that was the first thing I did. I did exactly as you said. I've tried changing file names, changing directories and everything but for some odd reason I'm getting the same error.
Edit: and yes, I'm changing those when I enter them in terminal as well.

Strange.
I'll have to troubleshoot this in a bit. I'll let you know what I find.

frederuco said:
Strange.
I'll have to troubleshoot this in a bit. I'll let you know what I find.
Click to expand...
Click to collapse
Thank you. Here is an image of what I have typed in case it is an error on my part.
http://i.imgur.com/lyJU8MR.jpg

Nope, error is on my part. Remove the "/" after the if=
It should be
dd if=TWRP.blob of=/dev/block/mmcblk0p4
Will update the other posts above.

frederuco said:
Nope, error is on my part. Remove the "/" after the if=
It should be
dd if=TWRP.blob of=/dev/block/mmcblk0p4
Will update the other posts above.
Click to expand...
Click to collapse
And it appears that I am still in clockworkmod when the device boots up.

BloodyRory said:
And it appears that I am still in clockworkmod when the device boots up.
Click to expand...
Click to collapse
Try a normal reboot at the end instead of reboot recovery and see if that works.
If not, run through this and download one of the flashable .zip files (it is version 2.2.X.X) and see if that works. If so, then run through GooManager to get the 2.3.2.3.

possible bricked Tf300t

Hi there guyz......not a newb....but not a pro.....usually sit back and read........but I was trying to change my recovery from TWRP to CM an some how i think I bricked my tab.....tablet boots to main asus screen......with unlocked in top left and nvidia in lower right......thats it....I cannot shut it down or get into recovery.....any help....thanx in advance !

_shakabra_ said:
Hi there guyz......not a newb....but not a pro.....usually sit back and read........but I was trying to change my recovery from TWRP to CM an some how i think I bricked my tab.....tablet boots to main asus screen......with unlocked in top left and nvidia in lower right......thats it....I cannot shut it down or get into recovery.....any help....thanx in advance !
Click to expand...
Click to collapse
Does it connect to fastboot using the universal naked drivers? If so, try this: http://forum.xda-developers.com/showthread.php?t=2425581

Nope..... It's was stuck on the Asus loading page all day..... Wouldn't shut down or anything........ It is currently dead battery...... I have connected the charger...... But got no charging light on the power button!

i think im having a similar issue. Charged up my tablet since i havent used it in a while. Went to go into recovery and it wont boot. Stuck on ASUS screen. Im on the old boot loader.for 4.1 and i dont know how to upgrade. I can boot back into the rom and use the tablet etc but no recovery.

Help
I am in the strangest situation.
Apparently while trying to upgrade CM 4.3 I flashed the wrong TWRP and checked closely because I love CWM-R
I have lost fastboot capabilities but with using the "adb reboot bootloader" I can get into android 4.3 (no GAPPS).
With any reboot it takes me to the ASUS screen and then directly to TWRP version 2.6.3.0
However nothing seems to work in there. I have used adb to push file to the tablet and when I hit install from the zip nothing happens even though I saw the file, then it disappears. All except system will not let me format etc. ADB does work and at time the TWRP will let me use ADB Sideload.
The problem is getting to install a new TWRP that works and sees a micro SD card. Also I have installed zip files hundreds of times but everything I see for this all I find are blob and img files to down load and have no idea how to make them install when all explain use of the fastboot. I do not believe I am bricked but it ain't good!
Any help greatly appreciated. The problem is getting to install a new TWRP that works and sees a micro SD card.
norm883

_shakabra_ said:
Nope..... It's was stuck on the Asus loading page all day..... Wouldn't shut down or anything........ It is currently dead battery...... I have connected the charger...... But got no charging light on the power button!
Click to expand...
Click to collapse
Asus repair is probably your only option. If it cant charge or boot up, theres nothing I can do.
---------- Post added at 01:55 PM ---------- Previous post was at 01:53 PM ----------
norm883 said:
I am in the strangest situation.
Apparently while trying to upgrade CM 4.3 I flashed the wrong TWRP and checked closely because I love CWM-R
I have lost fastboot capabilities but with using the "adb reboot bootloader" I can get into android 4.3 (no GAPPS).
With any reboot it takes me to the ASUS screen and then directly to TWRP version 2.6.3.0
However nothing seems to work in there. I have used adb to push file to the tablet and when I hit install from the zip nothing happens even though I saw the file, then it disappears. All except system will not let me format etc. ADB does work and at time the TWRP will let me use ADB Sideload.
The problem is getting to install a new TWRP that works and sees a micro SD card. Also I have installed zip files hundreds of times but everything I see for this all I find are blob and img files to down load and have no idea how to make them install when all explain use of the fastboot. I do not believe I am bricked but it ain't good!
Any help greatly appreciated. The problem is getting to install a new TWRP that works and sees a micro SD card.
norm883
Click to expand...
Click to collapse
Have you seen this:
http://forum.xda-developers.com/showthread.php?t=2403674
---------- Post added at 01:56 PM ---------- Previous post was at 01:55 PM ----------
olster said:
i think im having a similar issue. Charged up my tablet since i havent used it in a while. Went to go into recovery and it wont boot. Stuck on ASUS screen. Im on the old boot loader.for 4.1 and i dont know how to upgrade. I can boot back into the rom and use the tablet etc but no recovery.
Click to expand...
Click to collapse
Did you try reflashing the recovery with the correct TWRP verison from fastboot or the tablet in Android?

Follow-up
cmendonc2 said:
Asus repair is probably your only option. If it cant charge or boot up, theres nothing I can do.
---------- Post added at 01:55 PM ---------- Previous post was at 01:53 PM ----------
Have you seen this:
Did you try reflashing the recovery with the correct TWRP verison from fastboot or the tablet in Android?
Click to expand...
Click to collapse
Yes I did see that. It was what got me to the adb possibility. However I am not able to fast boot due to the fact that it goes straight to the TWRP on any start. And the TWRP is dysfunctional. My only choice I can see is going to be terminal emulator and I am not sure of its capabilities.
norm883

norm883 said:
Yes I did see that. It was what got me to the adb possibility. However I am not able to fast boot due to the fact that it goes straight to the TWRP on any start. And the TWRP is dysfunctional. My only choice I can see is going to be terminal emulator and I am not sure of its capabilities.
norm883
Click to expand...
Click to collapse
That is very doable, just google it.

norm883 said:
Yes I did see that. It was what got me to the adb possibility. However I am not able to fast boot due to the fact that it goes straight to the TWRP on any start. And the TWRP is dysfunctional. My only choice I can see is going to be terminal emulator and I am not sure of its capabilities.
norm883
Click to expand...
Click to collapse
Try to send "adb reboot-bootloader" command from Your PC. Or You can try "reboot bootloader" command in TWRP terminal.

Have done that, "partial brick"
Graiden05 said:
Try to send "adb reboot-bootloader" command from Your PC. Or You can try "reboot bootloader" command in TWRP terminal.
Click to expand...
Click to collapse
That does work, but the problem is it does not stay. You need to do each time you want to use the table (shut down / reboot etc.). But it does allow me to boot into Android 4.3 but it is only a partial load since GAPPS was never loaded. I can push via ADB but nothing seems to stick! I believe all except /system has a no write or no permission granted. In the Android part (4.3) with Root Explorer I have granted the permissions? It appears that TWRP is both the bootloader (fastboot) and recovery. So any fastboot commands are futile, (waiting for device. I did see somewhere there is an administrative function for fastboot but have not been able to locate in all my readings. Except one persons mention of it to eliminate the waiting for device.
norm883

Partial Brick
If this helps anyone I found in a post:
I used it in Terminal Emulator while in Android 4.3 from (adb reload bootloader)
• # dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1
• # dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1
• # reboot
This now stops when I reboot or turn off the tablet from going directly to TWRP which basically allows me to do nothing, except pretend to do ADB then on a reboot nothing happened.
norm883

Terminal Emulator in Android 4.3
Can anyone tell me where to read on how to use this?
ADB commands seem much different and really need to know how to push from microSD etc and do not setup.
Files I wanted to push I placed in the same folder as the program on the base of C:\ but do not understand how to map here.
I will read and nice to have examples.
Thanks,
norm883

norm883 said:
Can anyone tell me where to read on how to use this?
ADB commands seem much different and really need to know how to push from microSD etc and do not setup.
Files I wanted to push I placed in the same folder as the program on the base of C:\ but do not understand how to map here.
I will read and nice to have examples.
Thanks,
norm883
Click to expand...
Click to collapse
To push file to tablet microSD through adb:
tablet booted into android
adb push C:\\some_file /Removable/MicroSD/
tablet booted into TWRP(don't remember path for sure)
adb push C:\\some_file /ext_sdcard/
To get file from tablet internal memory:
adb pull /sdcard/some_file C:\\some_path\
or
adb pull /sdcard/some_file -should put file in directory where cmd now.

BAHHH Hummbug
Graiden05 said:
To push file to tablet microSD through adb:
tablet booted into android
adb push C:\\some_file /Removable/MicroSD/
tablet booted into TWRP(don't remember path for sure)
adb push C:\\some_file /ext_sdcard/
To get file from tablet internal memory:
adb pull /sdcard/some_file C:\\some_path\
or
adb pull /sdcard/some_file -should put file in directory where cmd now.
Click to expand...
Click to collapse
All seem to be different say directory does not exists etc Crazy program.
Is it possible that from a corrupt there could be 2 layers here? Because in the recovery mode it tells me that there is not OS installed?
Yet I know I can boot to CM Android 4.3.
Wish I could think of a way to clear and start fresh, but without fastboot I am up the creek.
Thanks,
norm883

[Q] Black Screen Brick / Android Logo - Different than the others

A pretty girl here in Zambia found out I know a bit about technology and brought me her Tab 2 GT3100.
Upon Power or USB insertion it boots to the 2nd Android Screen, and that's where it sits over and over again.
Upon trying to enter Recovery Mode - I get the fallen android with the stomach open.
Upon trying to enter Download mode, well, I can't.
I've managed to get an adb connection off and on upon bootup and can even get a logcat.
I cannot enter download mode via adb reboot download.
I can get access to the root filesystem via adb shell - and just for fun, I deleted contents of /dalvik-cache /cache and many 3rd party apps in /data
Still, the unit doesn't want to boot.
Any idea on this one? Is there a way that it can be reflashed via an SD Card? Can I push an image via ADB? ADB shell?
If I can get this to work, my days might just become brighter.

tiredofit said:
A pretty girl here in Zambia found out I know a bit about technology and brought me her Tab 2 GT3100.
Upon Power or USB insertion it boots to the 2nd Android Screen, and that's where it sits over and over again.
Upon trying to enter Recovery Mode - I get the fallen android with the stomach open.
Upon trying to enter Download mode, well, I can't.
I've managed to get an adb connection off and on upon bootup and can even get a logcat.
I cannot enter download mode via adb reboot download.
I can get access to the root filesystem via adb shell - and just for fun, I deleted contents of /dalvik-cache /cache and many 3rd party apps in /data
Still, the unit doesn't want to boot.
Any idea on this one? Is there a way that it can be reflashed via an SD Card? Can I push an image via ADB? ADB shell?
If I can get this to work, my days might just become brighter.
Click to expand...
Click to collapse
buddy as you are not able to boot in download mode or recovery i think it is bricked as you say black screen is observed
try triangle away to unbrick it
or customer care center always welcome you

tiredofit said:
A pretty girl here in Zambia found out I know a bit about technology and brought me her Tab 2 GT3100.
Upon Power or USB insertion it boots to the 2nd Android Screen, and that's where it sits over and over again.
Upon trying to enter Recovery Mode - I get the fallen android with the stomach open.
Upon trying to enter Download mode, well, I can't.
I've managed to get an adb connection off and on upon bootup and can even get a logcat.
I cannot enter download mode via adb reboot download.
I can get access to the root filesystem via adb shell - and just for fun, I deleted contents of /dalvik-cache /cache and many 3rd party apps in /data
Still, the unit doesn't want to boot.
Any idea on this one? Is there a way that it can be reflashed via an SD Card? Can I push an image via ADB? ADB shell?
If I can get this to work, my days might just become brighter.
Click to expand...
Click to collapse
Try it it recognised with pc odin. ...
If yes flash stock rom your issues will be solved
Dont Forget To HiT Thanks Button

Please help to unbrick

Hi,
I am looking for some help as I did something stupid...
I came across some posting that explained that the moto has an unused partition under /cache that could be used for the dalvik-cache.
So I tried to move the dalvik-cache there and link /data/dalvik-cache to this new location.
Now the problem is that I get an "unfortunately the location-service has stopped" message all the time that makes the device unusuable (as soon as I press ok the same warning appears again).
When I try to boot into recovery I get a "dead android robot".
I can however access the device via adb, unfortunately I am not able to get a root shell. My device is rooted, but su in an adb-shell just hangs.
If I could only get a root-shell I could undo my changes and hopefully my device will work again, but I have to idea on what to try...
Can anone help me here?

morgonhed said:
Hi,
I am looking for some help as I did something stupid...
I came across some posting that explained that the moto has an unused partition under /cache that could be used for the dalvik-cache.
So I tried to move the dalvik-cache there and link /data/dalvik-cache to this new location.
Now the problem is that I get an "unfortunately the location-service has stopped" message all the time that makes the device unusuable (as soon as I press ok the same warning appears again).
When I try to boot into recovery I get a "dead android robot".
I can however access the device via adb, unfortunately I am not able to get a root shell. My device is rooted, but su in an adb-shell just hangs.
If I could only get a root-shell I could undo my changes and hopefully my device will work again, but I have to idea on what to try...
Can anone help me here?
Click to expand...
Click to collapse
The dead android bot is normal for stock recovery, if you didn't install a custom one. You can always flash a custom recovery using fastboot, and wipe the dalvik-cache and regular caches. Or, in the "dead android bot" screen, you can press the Vol+ key for about 15 secs, then tap the Power button, then scroll using the Vol buttons to something that says wipe cache. You might have to wipe dalvik-cache as well, if you can. I forget where the options are, since I haven't used the stock recovery in so long, sorry!

Ok, I managed to get beyond the "dead android" and from the menu I did a "wipe cache parition". That ran for some minutes, then it rebooted.
But after that I still have the same problem. The continuous "unfortunately the location-service has stopped" messages still persist.
Any other ideas?

Do you have an unlocked bootloader? If you do, the simplest solution may be to flash back to a stock ROM.

audit13 said:
Do you have an unlocked bootloader? If you do, the simplest solution may be to flash back to a stock ROM.
Click to expand...
Click to collapse
Yes my bootloader is unlocked. But I don't want to loose too much...
I believe the problem is only a permission-problem in my new /cache/dalvik-cache directory (/data/dalvik-cache now links there).
So all I would need is a way to get a root-shell (the device is rooted).
I can do a "adb shell" as normal user but that does not have the permissions to even look into /cache and for whatever reason when I type "su" I don't get an error nor do I become root but the command simply hangs...
The system as such still seems to work, e.g. my Moto still connects to my hotspot and I can ping it from there.
The even seems to be an "adb root" command, but that does not work on my adb. Is there a version of adb somewhere that would honor adb root?
Anyone with another idea on how to get a root-shell in my situation

Sorry, I don't know enough about adb commands to change the directory back to the default.
I assume you have usb debugging enabled and your computer is a trusted machine?

USB debugging is definitely enabled, whether or not I've set up my PC as trusted I don't remember.
If I didn't could that explain why I can get a shell but not as root or would you without a trusted computer not even get a shell?

Ok, issue resolved.
I've flashed clockworkmod recovery and cleared the dalvik-cache with that. That did the trick.
And moving my 300MB dalivk-cache to /cache seems to have worked and frees up memory for me, even better.
Finally the reason I could not get root in the adb shell was that when I type su in the adb-shell a superuser-request pops up on the phone that you have to acknowlege. But with constant warnings poping up I did not even see that...
Thanks for all support.

For the Developer options, look under Root access. Did you grant root access to ADB and apps?
When you type su, look at the phone's screen. Are you prompted to grant root access to ADB?

Android Automatic Boot into Recovery via Micro SD card?

Good day just wondering if there's a way to automatically boot into recovery via Micro SD card being installed/inserted in to Android device?
Kinda like a boot disc, why well there has been time where booting into recovery via the 3 button combo does not work, (home button faulty) or one of the other keys and maybe one doesn't have access to a computer.? So is the Suck a way?
Thanks

Nyssa1104 said:
Good day just wondering if there's a way to automatically boot into recovery via Micro SD card being installed/inserted in to Android device?
Kinda like a boot disc, why well there has been time where booting into recovery via the 3 button combo does not work, (home button faulty) or one of the other keys and maybe one doesn't have access to a computer.? So is the Suck a way?
Thanks
Click to expand...
Click to collapse
Is the device rooted? Will the device boot to system normally? If so, install terminal emulator, open terminal emulator, then type:
su (press enter, grant superuser permission if/when prompted)
Then type:
reboot recovery (press enter, it will boot to recovery)
There are also other apps that have features that will boot you to recovery.

@Droidriven yes device is rooted. Reason l was for the above question is there been times not able to access apps or boot up, recovery etc without the aid of a computer and used andriod sdk to push add to recovery. A boot up. SD card would be useful in this case..
Thanks for your help.

Nyssa1104 said:
@Droidriven yes device is rooted. Reason l was for the above question is there been times not able to access apps or boot up, recovery etc without the aid of a computer and used andriod sdk to push add to recovery. A boot up. SD card would be useful in this case..
Thanks for your help.
Click to expand...
Click to collapse
You have something wrong then, what you're asking won't fix your issue with booting. Solve whatever is causing your device to not function properly.

@Droidriven there is a problem home button doesn't function on Samsung Galaxy S5. There nothing wrong with the actual button but more like the contact switch on the daughter board (USB main board) common problem with Galaxy S5. Just to note this board has been swapped out with a know working and all brand new USB charging port PCB and home button fails to work. I even back up my device and did a clean install by push the commands via computer to boot into recovery. Hence why l had ask such a question. Thanks for your help.