Hello.
First sorry for my poor english and my newb-ness ...
My xoom is stuck in boot animation (the honeycomb animation).
It is recognised by my computer, I can access it via adb.
I wish I could unbrick it without having to reset it.
The last thing I did before reboot was to install ADW.launcher.
So I thought I only had to remove the apk/odex from my system/app folder, but the files actually do not exist.
Is there a way to know what is happening, and to repair without having to do a full reset ?
Thanks for your help.
davpitdavpit said:
Hello.
First sorry for my poor english and my newb-ness ...
My xoom is stuck in boot animation (the honeycomb animation).
It is recognised by my computer, I can access it via adb.
I wish I could unbrick it without having to reset it.
The last thing I did before reboot was to install ADW.launcher.
So I thought I only had to remove the apk/odex from my system/app folder, but the files actually do not exist.
Is there a way to know what is happening, and to repair without having to do a full reset ?
Thanks for your help.
Click to expand...
Click to collapse
How are you seeing system/app folder. Try looking in data/app folder instead.
Sent from my Xoom
Thanks for the answer.
The installed apps are in data/apps ? Or is it the data for each app ?
I am rooted. I am seeing files with adm remount, adb shell, and then shell commands.
I tried lots of bizarre stuff yesteday night, removing or pushing files to the system dir, but off course I didn't manage to do anything usefull.
So I decided to flash STOCK MZ604_HW169 root, recovery, system and userdata.
I lost my userdata but kept my apps.
Anyway:
1. I would be pleased to know how could I have been able to know what is wrong ( is there a bootlog ?) and what should I do if and app prevents me to accomplish full boot.
2. My xoom is a french wifi, and stock us wifi works like a charm on it.
(JaymZ37 is asking the question in this thread:
http://forum.xda-developers.com/showthread.php?t=1052644&page=5
and I am not allowed to post the answer)
Hello friends, Please note that i tried installing ClockworkMod 3.1.0.1 but it refused to setup for some reason, even though i did everything right i.e. holding down the down vol key and power button etc but like others i only get the green android with the exclamation mark in the middle, so i do not have a backup unfortunately ;(
Anyway the story starts here:
Please be patient with me though as i am new to all this but learning fast.
Got a new Asus transformer TF101 (with keyboard) for only 5 days with
Device serial: B70KAS3?????
Build number: HMJ37.WW_epad-8.4.4.11-20110711
Android version: 3.1
Didnt know about Razorclaw ability to root B70 :-(
Anyway on going online on the TF101 for the first time, I immediately got a message saying there was a new os update available, the TF101 auto downloaded it and i then immediately updated it, thinking that the new update was best for me :-(
After the update, i then had -
Build number: HTK75.WW_epad-8.6.5.21-20111216
Android version: 3.2.1
Razorclaw doesnt work on my TF101 however i was able to use use the WW_epad-user-8.6.6.19.zip update on it and then was able to root using Razorclaw.
After that everything worked fine until i used 'Rom Manager' to create a script that was to change my hostname to my preferred one instead of the usual 'android_????????????', i then set it to do so on boot within 'Rom Manager'.
I then used 'Rom Manager' 'reboot' script to reboot the TF and now it boots then flashes locked screen for a second and shuts down and the same thing happens when i power it up again
If i am lucky and quick, i can put in the password and see the desktop just before it shuts down.
I have a feeling it the script i created and set to execute on boot is what is causing the shutdown.
Is there anyway to fix this?
It not a low battery issue, already checked that.
Was thinking along the lines of a key combination to prevent scripts running on boot time.
Dont really want to wipe the TF, as it already taken me 5 days to get it setup how i want it and now this!
It sounds like you have a stock recovery and a buggered up system.
You might be able to recover with adb, but you'll have to know what to stop/kill before it reboots. If it's enable, adb will be active well before you see the lock screen. There might also be some tools in the android sdk, perhaps ddms.
What exactly is in this rom manager script? Perhaps it is passing a reboot via one of the partitions. You would need to clear the command to stop the reboots or just kill the process that is rebooting.
That's all I gots. Good luck!
gee one said:
It sounds like you have a stock recovery and a buggered up system.
You might be able to recover with adb, but you'll have to know what to stop/kill before it reboots. If it's enable, adb will be active well before you see the lock screen. There might also be some tools in the android sdk, perhaps ddms.
What exactly is in this rom manager script? Perhaps it is passing a reboot via one of the partitions. You would need to clear the command to stop the reboots or just kill the process that is rebooting.
That's all I gots. Good luck!
Click to expand...
Click to collapse
thanx for responding mate...appreciated.
the script is just a simple script with just one line with tr3ble being the new hostname, its exactly as below:
setprop net.hostname tr3ble
I'll have a tinker with adb but what how do i search for processes to stop/kill using adb as im not that clued up with linux commands
I'm not a pro either, but I think "ps" will show you the process and "kill <pid>" will kill them. There might be a better way and I haven't tested this, so if you end up in a worse situation than then one you are in, it's all on you.
I don't think that changing the hostname will cause a reboot. I think the "reboot" command from rom manager is somehow stuck. I think it passes a reboot command via one of the partitions so that it can "find" it when it restarts. You would just have to clear the command. I think it's somewhere in the /cache directory, but that is just a guess.
gee one said:
I'm not a pro either, but I think "ps" will show you the process and "kill <pid>" will kill them. There might be a better way and I haven't tested this, so if you end up in a worse situation than then one you are in, it's all on you.
I don't think that changing the hostname will cause a reboot. I think the "reboot" command from rom manager is somehow stuck. I think it passes a reboot command via one of the partitions so that it can "find" it when it restarts. You would just have to clear the command. I think it's somewhere in the /cache directory, but that is just a guess.
Click to expand...
Click to collapse
Wow...you are definitely pointing me in the some direction though, in the begining i didnt have a clue what to do and where to look but now i have a few things to try...i'll see how things go with adb and report back.
Thank you for your time and patience mate
Update:
I tried everything i could but just didnt seem to have much time to do much using adb so i bit the bullet and did a data wipe, but to my joy, after the data wipe the TF was still rooted and my adhoc hack was still in place. If only took me bout an hour to then reinstall all my apps, which was more or less easy as i had them all in one folder on my microSD.
So all in all, the data wipe which cured the shutdown after restart wasnt sooo bad afterall.
Thank for your help mate!
....Happy New year!
b00b said:
Update:
I tried everything i could but just didnt seem to have much time to do much using adb so i bit the bullet and did a data wipe, but to my joy, after the data wipe the TF was still rooted and my adhoc hack was still in place. If only took me bout an hour to then reinstall all my apps, which was more or less easy as i had them all in one folder on my microSD.
So all in all, the data wipe which cured the shutdown after restart wasnt sooo bad afterall.
Thank for your help mate!
....Happy New year!
Click to expand...
Click to collapse
Did the same exact procedure when the same thing happened to my TF earlier this month.... Good to know that i wasn't the only one that faced this situation.
Sent from my Transformer TF101 using xda premium
Hi guys,
I've been reading you for a while, but this is actually my first post.
Currently stuck with a "Unfortunately, Launcher has stopped" on my tablet, with no access to any menus except my Settings. The menu bar (back, home and multitasking) is now gone. I've got my keyboard to navigate, but something in the display is also quite wrong, image seems to be zoomed, or set at the wrong resolution. Tried to search on the forum, but all posts found were not about the same rom or the same issue. Sorry if I missed one.
Here's a little background story:
I've rooted my TF300T about a month ago and installed Hydro 4.1. It has been working very well since then, but in the last days, I thought that my tablet felt a little slower than usual, so I started searching if an update to 4.2 was available.
I'm not sure if this is what caused the issue or not, but I went into my "Power button" menu and went into "Recovery" mode (instead of Shutdown, reboot, etc.), which then restarted my unit into TWRP menu.
I then selected the "System" submenu and simply touched "Reboot". (terms might not be exact). At the first reboot, I got the problems that I described.
Can't do much, popup keeps appearing on my screen. I haven't tried yet to clear the cache of my Launcher, which I'm trying to avoid as I would prefer to avoid rearranging 5 pages of icons, but between that and reinstalling everything, obviously I prefer to simply lose my display preferences.
Can anyone help me about what caused my issue, and what can I do now?
Here are 2 screenshots that I took, showing that my bottom menu is missing and that the fonts aren't set right (clock and left icon). Also, my notifications menu now appears near the middle of my screen.
EDIT: I unfortunately cannot post links yet
I remember installing an app (with root access) that gave me a menu about my resolution. One thing that I'm wondering, could it be that the resolution got changed and I simply never rebooted since the change, which now caused my Launcher to crash? How can I launch an app without having access to the app menu?
Thanks in advance for your help.
irepressed said:
Hi guys,
I've been reading you for a while, but this is actually my first post.
Currently stuck with a "Unfortunately, Launcher has stopped" on my tablet, with no access to any menus except my Settings. The menu bar (back, home and multitasking) is now gone. I've got my keyboard to navigate, but something in the display is also quite wrong, image seems to be zoomed, or set at the wrong resolution. Tried to search on the forum, but all posts found were not about the same rom or the same issue. Sorry if I missed one.
Here's a little background story:
I've rooted my TF300T about a month ago and installed Hydro 4.1. It has been working very well since then, but in the last days, I thought that my tablet felt a little slower than usual, so I started searching if an update to 4.2 was available.
I'm not sure if this is what caused the issue or not, but I went into my "Power button" menu and went into "Recovery" mode (instead of Shutdown, reboot, etc.), which then restarted my unit into TWRP menu.
I then selected the "System" submenu and simply touched "Reboot". (terms might not be exact). At the first reboot, I got the problems that I described.
Can't do much, popup keeps appearing on my screen. I haven't tried yet to clear the cache of my Launcher, which I'm trying to avoid as I would prefer to avoid rearranging 5 pages of icons, but between that and reinstalling everything, obviously I prefer to simply lose my display preferences.
Can anyone help me about what caused my issue, and what can I do now?
Here are 2 screenshots that I took, showing that my bottom menu is missing and that the fonts aren't set right (clock and left icon). Also, my notifications menu now appears near the middle of my screen.
EDIT: I unfortunately cannot post links yet
I remember installing an app (with root access) that gave me a menu about my resolution. One thing that I'm wondering, could it be that the resolution got changed and I simply never rebooted since the change, which now caused my Launcher to crash? How can I launch an app without having access to the app menu?
Thanks in advance for your help.
Click to expand...
Click to collapse
What you describe is likely caused by changing the resolution. Are you still running hydro 4.1?
You can likely recover by replacing your build.prop or editing the one you now have. build.props are usualy rom specific so you need one from the rom you are using.
tobdaryl said:
What you describe is likely caused by changing the resolution. Are you still running hydro 4.1?
You can likely recover by replacing your build.prop or editing the one you now have. build.props are usualy rom specific so you need one from the rom you are using.
Click to expand...
Click to collapse
Yes, still using Hydro 4.1. I do have a build.prop editor installed on my tablet, but since I can't launch app, I don't know how to do it.
I'll try to connect the tablet to my PC and see if I can get access to my file from there.
Thanks!
irepressed said:
Yes, still using Hydro 4.1. I do have a build.prop editor installed on my tablet, but since I can't launch app, I don't know how to do it.
I'll try to connect the tablet to my PC and see if I can get access to my file from there.
Thanks!
Click to expand...
Click to collapse
I'm presently downloading 4.1 hydro to retrieve the build.prop. If you unzip it the build.prop is /system/build.prop also located there on your tab. I have another fifteen minutes to download if you wish for me to supply the file!
tobdaryl said:
I'm presently downloading 4.1 hydro to retrieve the build.prop. If you unzip it the build.prop is /system/build.prop also located there on your tab. I have another fifteen minutes to download if you wish for me to supply the file!
Click to expand...
Click to collapse
If you could, I would appreciate it!
Only thing left, how can I send the file to my TF300T without access to my apps? I'm currently trying to cheat by opening my apps using the Share feature with screenshots taken, but so far, no success.
irepressed said:
If you could, I would appreciate it!
Only thing left, how can I send the file to my TF300T without access to my apps? I'm currently trying to cheat by opening my apps using the Share feature with screenshots taken, but so far, no success.
Click to expand...
Click to collapse
We should be able to push with adb, set permissions, and reboot.
---------- Post added at 04:58 PM ---------- Previous post was at 04:36 PM ----------
http://www.mediafire.com/?tk3cifzci0vw24e
place the build.prop from the zip file into the directory with fastboot.
Open terminal or cmd in the directory with fastboot.
Boot into twrp – twrp provides adb access by default.
Use twrp mount menu and check mount system.
Then type
adb push build.prop /system/build.prop
adb shell chmod 644 /system/build.prop
in twrp reboot system
type
adb kill-server
tobdaryl said:
We should be able to push with adb, set permissions, and reboot.
---------- Post added at 04:58 PM ---------- Previous post was at 04:36 PM ----------
place the build.prop from the zip file into the directory with fastboot.
Open terminal or cmd in the directory with fastboot.
Boot into twrp – twrp provides adb access by default.
Use twrp mount menu and check mount system.
Then type
adb push build.prop /system/build.prop
adb shell chmod 644 /system/build.prop
in twrp reboot system
type
adb kill-server
Click to expand...
Click to collapse
Ok, my Fastboot folder is currently at the root of my C drive on my PC
I entered your command and got after the first one "adb server is out of date. killing...
* daemon started successfully *
error: device not found
FYI, before I got your last post, I used Android commander to push the build.prop that I still had on my PC when I installed the custom hydro 4.1 rom.
After my reboot, I got the Asus logo, than a black screen that does nothing.
I then rebooted in Fastboot and followed your instructions.
So now, it seems that my pc doesnt see my tablet anymore when in TWRP. is this normal? Do I need to restart it after checking "Mount system"?
irepressed said:
Ok, my Fastboot folder is currently at the root of my C drive on my PC
I entered your command and got after the first one "adb server is out of date. killing...
* daemon started successfully *
error: device not found
FYI, before I got your last post, I used Android commander to push the build.prop that I still had on my PC when I installed the custom hydro 4.1 rom.
After my reboot, I got the Asus logo, than a black screen that does nothing.
I then rebooted in Fastboot and followed your instructions.
So now, it seems that my pc doesnt see my tablet anymore when in TWRP. is this normal? Do I need to restart it after checking "Mount system"?
Click to expand...
Click to collapse
Ok, I just killed my adb.exe, tried the command again and that got rid of the out of date error.
But, still stuck with the "device not found".
irepressed said:
Ok, my Fastboot folder is currently at the root of my C drive on my PC
I entered your command and got after the first one "adb server is out of date. killing...
* daemon started successfully *
error: device not found
FYI, before I got your last post, I used Android commander to push the build.prop that I still had on my PC when I installed the custom hydro 4.1 rom.
After my reboot, I got the Asus logo, than a black screen that does nothing.
I then rebooted in Fastboot and followed your instructions.
So now, it seems that my pc doesnt see my tablet anymore when in TWRP. is this normal? Do I need to restart it after checking "Mount system"?
Click to expand...
Click to collapse
Slowdown, I'm getting behind. I'm willing to help but you are now worse off than before.
Sit tight for five minutes and I'll try to give you a twrp flashable zip for your build.prop and hope that is the extent of the damage.
If not we'll try to go from there.
http://www.mediafire.com/?ybplc1ws8uvskhf
This is a twrp flashable zip that only replaces your build.prop with the one from hydro 4.1.
tobdaryl said:
Slowdown, I'm getting behind. I'm willing to help but you are now worse off than before.
Sit tight for five minutes and I'll try to give you a twrp flashable zip for your build.prop and hope that is the extent of the damage.
If not we'll try to go from there.
This is a twrp flashable zip that only replaces your build.prop with the one from hydro 4.1.
Click to expand...
Click to collapse
Alright, I'll wait for your answer before trying anything else.
So now, I've got your latest .zip file.
Still can't see my TF300T from my PC, so, ADB is a no go for now.
In fact, I do see it in the Device Manager, but since my last reboot, it now shows an exclamation mark on it as if my drivers weren't good.
Since you mentioned the file is a flashable zip, I'm guessing that I can flash it using TWRP without going through my PC?
Can you give me precise info on that, since I do not want to mess with my system more than I already did.
Thanks
irepressed said:
Alright, I'll wait for your answer before trying anything else.
So now, I've got your latest .zip file.
Still can't see my TF300T from my PC, so, ADB is a no go for now.
In fact, I do see it in the Device Manager, but since my last reboot, it now shows an exclamation mark on it as if my drivers weren't good.
Since you mentioned the file is a flashable zip, I'm guessing that I can flash it using TWRP without going through my PC?
Can you give me precise info on that, since I do not want to mess with my system more than I already did.
Thanks
Click to expand...
Click to collapse
Look at the bottom of my previous post. You will find a new link there. Just flash with twrp and reboot. Don't worry about wiping or any of that, just flash and reboot.
tobdaryl said:
Look at the bottom of my previous post. You will find a new link there. Just flash with twrp and reboot. Don't worry about wiping or any of that, just flash and reboot.
Click to expand...
Click to collapse
Yep, that's the file I was talking about.
I now need to flash and reboot, your file is at the root of an SDcard in my TF300T, I go through the Install menu and then, can't seem to view the content of my sdcard. Tried to mount it first but can't select it either, it will simply stay on "Internal Storage".
EDIT: The RCK icon is the only one right now that boots me into something. If I try the USB icon, it just stays on that screen forever.
Trash the two zips you have downloaded. I'm providing a new one for when we get back to that point. And there will be no doubt about which zip you are using.
http://www.mediafire.com/?hagehu5qu5ky6sf
OK. First I'll explain your earlier comment about adb being old. Twrp expects a recent adb or refuses to allow adb access ( we'll not worry at the moment about that but it is something you need to address later (I hope).
If you have a cord between your tablet and pc remove it. The sdcard may be mounted as data on the pc and not allow twrp to mount it.
You have been using this sdcard prior to this exercise?
Do you have any backups or flashable zips or anything of that nature on your internal sdcard?
If so what?
tobdaryl said:
Trash the two zips you have downloaded. I'm providing a new one for when we get back to that point. And there will be no doubt about which zip you are using.
OK. First I'll explain your earlier comment about adb being old. Twrp expects a recent adb or refuses to allow adb access ( we'll not worry at the moment about that but it is something you need to address later (I hope).
If you have a cord between your tablet and pc remove it. The sdcard may be mounted as data on the pc and not allow twrp to mount it.
You have been using this sdcard prior to this exercise?
Do you have any backups or flashable zips or anything of that nature on your internal sdcard?
If so what?
Click to expand...
Click to collapse
Zips trashed, kept only the one provided in your latest answer.
No cord between PC and tablet. Still unable to click on "Using external SD" or "Mount SDCard". It simply won't let me check the box or switch the bullet.
As for using this SDcard before, yes in a PC, but no, first time in my Asus. Also tried with another one just in case and same result.
As for backups and flashable zips, I kept everything from when I did my root and rom install.
I do know that I have a backup in the Restore menu of TWRP, which seems about the time I installed it. I suppose I could simply do a restore and avoid additional headaches, but my question is, what exactly will it restore? At this point, I'm mentally prepared to go back to what I had after installing Hydro 4.1, as long as I can use the tablet ASAP.
Asap = restore your backup.
If I'm restoring a different rom I'll wipe Cache, Dalvik Cache, and Factory Reset. If the backup is from the same rom I'm flashing and I want to keep the apps I have Installed since the backup I won't Factory Reset.
Good Luck!
tobdaryl said:
Asap = restore your backup.
If I'm restoring a different rom I'll wipe Cache, Dalvik Cache, and Factory Reset. If the backup is from the same rom I'm flashing and I want to keep the apps I have Installed since the backup I won't Factory Reset.
Good Luck!
Click to expand...
Click to collapse
So, I did the restore, and I'm up and running, but, no more Hydro 4.1. I guess my backup was probably what got done right before the installed it.
The good thing is, my tablet is working again and my root is still active. The bad part is that I'm gonna have to dig my head again in all the tutorials and try to find the best one.
Hey, I wanted to say a huge thank you for all your help, if it wasn't for guys like you, newbies like me would be stuck with useless thin computers.
irepressed said:
So, I did the restore, and I'm up and running, but, no more Hydro 4.1. I guess my backup was probably what got done right before the installed it.
The good thing is, my tablet is working again and my root is still active. The bad part is that I'm gonna have to dig my head again in all the tutorials and try to find the best one.
Hey, I wanted to say a huge thank you for all your help, if it wasn't for guys like you, newbies like me would be stuck with useless thin computers.
Click to expand...
Click to collapse
Great I'm glad you are happy. I had hoped for the outcome you expressed but this works also.
You're welcome!