Related
I have a WiFi only Xoom and it is unlocked/rooted.
I decided to use the hack on the stock browser which enables fulltime desktop mode. I downloaded the apk, renamed it to framework-res.apk and dropped in system/framework and overwrote the existing file. I dl the file from http://forum.androidcentral.com/xoom-rooting-roms-hacks/75616-full-browser.html
I've since discovered that had I read further into the thread, I would have known not to use the file on a WiFi Xoom.
The gist of my problem is I have managed to finally get the Xoom to boot to the homescreen but It's force close city. As soon as I force close one app, others come up (FC) too. The one FC that will not go away is Launcher. it will FC loop forever. The Google/Mic in the top left corner is missing but the bottom bar has the normal icons, but I can't use them because I am stuck in a FC loop. I also get stuck/locked up while rebooting using the power button and volume down and have to use the power/volume up to restart.
I'm wondering if I use the the same one click root file (with kernel) that I still have and root again if this may fix the issue?
Perhaps their may be an easier method if I am only missing the one (framework-res.apk) file I overwrote?
Any help would be most appreciated.
You wanted a new theme right?
http://forum.xda-developers.com/showthread.php?t=1015434
This theme has the framework you are looking for.
Or.. this is the original Wifi Xoom system dump. It may be in there. (I'm at work so i cant check myself)
http://forum.xda-developers.com/showthread.php?t=1011484
Just got home and read your post and do appreciate it.
I was going to begin but just discovered that my Xoom will no longer mount on my pc. Not sure what to do....
yooper said:
I have a WiFi only Xoom and it is unlocked/rooted.
I decided to use the hack on the stock browser which enables fulltime desktop mode. I downloaded the apk, renamed it to framework-res.apk and dropped in system/framework and overwrote the existing file. I dl the file from
I've since discovered that had I read further into the thread, I would have known not to use the file on a WiFi Xoom.
The gist of my problem is I have managed to finally get the Xoom to boot to the homescreen but It's force close city. As soon as I force close one app, others come up (FC) too. The one FC that will not go away is Launcher. it will FC loop forever. The Google/Mic in the top left corner is missing but the bottom bar has the normal icons, but I can't use them because I am stuck in a FC loop. I also get stuck/locked up while rebooting using the power button and volume down and have to use the power/volume up to restart.
I'm wondering if I use the the same one click root file (with kernel) that I still have and root again if this may fix the issue?
Perhaps their may be an easier method if I am only missing the one (framework-res.apk) file I overwrote?
Any help would be most appreciated.
Click to expand...
Click to collapse
I did the same thing my friend, twice in fact. Actually it was likely my post you are referencing above Second time around I still had USB debugging turned on so I didn't have to reload the images.
Do you have the original .apk backed up? If not, i'm attaching it. What I did to fix this was using the adb shell, I remounted the file system as rw and adb pushed the original .apk. You're good to go after that. Hope you have your USB Debugging still turned on
Hope this helps.
yooper said:
Just got home and read your post and do appreciate it.
I was going to begin but just discovered that my Xoom will no longer mount on my pc. Not sure what to do....
Click to expand...
Click to collapse
Are you stuck at the dual core screen? If so can you get into fastboot? You would have to flash the system and boot .img I believe. This is what I had to do when i bricked my wifi without having the USB Debugging turned on. Don't lose hope, you likely do not have a $600 paperweight on your hands.
joen1ce,
I cant thank you enough for your help and time as well as uploading the file for me. Thank you.
I do have dubugging turned on and can boot to the home screen. Actually I have gotten a bit further. I found that if I hit "ok" and force close and quickly continued to hit the time on the lower right corner, I could eventually get into the setting menu. Takes a lot of "tapping" to get it to work, but it did. I am able to get into the reset option but it simply wont work. I push the button and nothing happens. I even tried using bluetooth via my Fascinate and Xoom to see what I could do with the apk you uploaded within the xoom since I could get into the bluetooth downloads, but no worky.
Upon startup, I find that I can get into "Starting fastboot protocol support" as well as well as RSD - Fastboot and NvFlash. Although, I still cant get the Xoom to talk with the computer. I have a Mac with Windows installed and have neither will communicate with the Xoom.
I'm not overly savy with ADB and am not sure if I would know what to do with a boot.img nor where to put it let alone the commands needed to make it work with no communication between devices.
I do have SDK/ADB and the Fastboot (.exe) both on the Mac and Windows side.
I can do an exchange on the Xoom but would rather fix it myself and consider it a valuable learning experience, but I'm at my wit's end.
yooper said:
joen1ce,
I cant thank you enough for your help and time as well as uploading the file for me. Thank you.
I do have dubugging turned on and can boot to the home screen. Actually I have gotten a bit further. I found that if I hit "ok" and force close and quickly continued to hit the time on the lower right corner, I could eventually get into the setting menu. Takes a lot of "tapping" to get it to work, but it did. I am able to get into the reset option but it simply wont work. I push the button and nothing happens. I even tried using bluetooth via my Fascinate and Xoom to see what I could do with the apk you uploaded within the xoom since I could get into the bluetooth downloads, but no worky.
Upon startup, I find that I can get into "Starting fastboot protocol support" as well as well as RSD - Fastboot and NvFlash. Although, I still cant get the Xoom to talk with the computer. I have a Mac with Windows installed and have neither will communicate with the Xoom.
I'm not overly savy with ADB and am not sure if I would know what to do with a boot.img nor where to put it let alone the commands needed to make it work with no communication between devices.
I do have SDK/ADB and the Fastboot (.exe) both on the Mac and Windows side.
I can do an exchange on the Xoom but would rather fix it myself and consider it a valuable learning experience, but I'm at my wit's end.
Click to expand...
Click to collapse
Copy the apk file I uploaded to the directory where you have the adb files. Go to the command line and switch to that same directory.
Let the device reboot to the point where you get those damn force close messages.
at the command line type:
adb devices
you should see your device listed there. If so, do the following:
adb shell
mount
You should see all the mounts on your device listed. Copy the path for system you will need it for this next part. It may be exactly like mine. So next you will type in:
mount -o rw,remount /dev/block/platform/sdhci-tegra.3/by-name/system /system
the "/dev/block/platform/sdhci-tegra.3/by-name/system" above is the true path
to my /system mount. Use whatever the path yours is mounted to from the previous command.
Next hit ctrl + c to exit out of the shell and at the command line type this:
adb push framework-res.apk /system/framework/framework-res.apk
If the above was successful you should be able to reboot the device and be back in business.
You fixed it!!
joen1ce, I can't begin to thank you enough for your help Took me a couple tries as well as rebooting the Xoom for it to take but by god it worked!!!
I'm sure your post will help others out out in future too. As the WiFi Xoom becomes more popular, I'm sure this will happen again to more people looking to modify their Xoom stock browser to desktop mode.
I'm thinking their should be a sticky on bricking with possible fixes and your post should be noted for sure.
People like you really help make this site the cat's a**.
Thanks again,
Mark
yooper said:
joen1ce, I can't begin to thank you enough for your help Took me a couple tries as well as rebooting the Xoom for it to take but by god it worked!!!
I'm sure your post will help others out out in future too. As the WiFi Xoom becomes more popular, I'm sure this will happen again to more people looking to modify their Xoom stock browser to desktop mode.
I'm thinking their should be a sticky on bricking with possible fixes and your post should be noted for sure.
People like you really help make this site the cat's a**.
Thanks again,
Mark
Click to expand...
Click to collapse
No problem, glad I could help. I bricked my Xoom basically within an hour of buying it and I know how it feels, especially when trying to be moral and not return it! Had it about a week now and it's my first Android device so I'm new to these forums. But the helpfulness of the community is very impressive indeed.
Regards,
Joe
joen1ce said:
Are you stuck at the dual core screen? If so can you get into fastboot? You would have to flash the system and boot .img I believe. This is what I had to do when i bricked my wifi without having the USB Debugging turned on. Don't lose hope, you likely do not have a $600 paperweight on your hands.
Click to expand...
Click to collapse
joen1ce. Could you please help? I am stuck at the Dual Core Screen and cannot get my computer to recognize my device in adb. I am trying to return to stock 3.2.1.
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
Alright so looks like I did something completely stupid and now my phone won't finish the boot process. I was looking at some remappings for the recent key to the menu option and from a post in the development section I found a thread in the International One X development forum that had re-odexed files so that the recent key stayed as the recent key and holding the home button became the menu key. Since they were re-odexed and I had root access I figured I would just manually replace them on my phone with Root Explorer...bad idea. The files were:
System/Framework/android.policy.odex
System/Usr/keylayout/qwerty.kl
After I moved them and reset permissions I rebooted my phone and now it goes through the first couple of boot animations but gets stuck on screen that displays beats audio at the bottom.
I really need to know what to do to fix this. When I plug my phone into my computer it recognizes it as a new \drive, but I don't have access to any of it (still says I need to mount). I also have the android SDk and adb installed if thats of any help. I would really like to not lose any data so hopefully thats possible.
Please help me with this if you have any knowledge of what to do.
Just one little quick update. Even though my computer won't let me access my One X as a drive, when I use command prompt and adb to check for adb devices my One X is listed.
Run the at&t ruu exe file, located in the Dev section.
tanman21 said:
Run the at&t ruu exe file, located in the Dev section.
Click to expand...
Click to collapse
Alright I'm downloading that now.
In the meantime, how do I get root access with adb/give it permission to overwrite read only files? I pulled the two files that caused this messed and pulled my backups, but when I push them back to the phone it tells me I can't because their read only. I'd rather do it this way since I will be changing only the files that caused the problem.
EDIT: Is the RUU really going to delete all the information on my device? If thats the case I would really appreciate figuring out how to get adb to push my backuped files to the /system directory instead
ErikWithNoC said:
Alright I'm downloading that now.
In the meantime, how do I get root access with adb/give it permission to overwrite read only files? I pulled the two files that caused this messed and pulled my backups, but when I push them back to the phone it tells me I can't because their read only. I'd rather do it this way since I will be changing only the files that caused the problem.
EDIT: Is the RUU really going to delete all the information on my device? If thats the case I would really appreciate figuring out how to get adb to push my backuped files to the /system directory instead
Click to expand...
Click to collapse
Yeah, the RUU returns your phone to factory (but doesn't touch your personal files)
EDIT: Also, just pulling this off the top of my head so take it with a grain of salt...
adb devices
adb shell
su
*grant the su request on your device*
adb push <from> <to>
stnguyen09 said:
Yeah, the RUU returns your phone to factory (but doesn't touch your personal files)
EDIT: Also, just pulling this off the top of my head so take it with a grain of salt...
adb devices
adb shell
su
*grant the su request on your device*
adb push <from> <to>
Click to expand...
Click to collapse
Thanks for your comment. I used the RUU and it kept my personal data so its not a big lose. Had to reinstall a few apps, but for most of them (games at least) my saved data was still there.
I tried a lot using adb and just couldn't get it to work. I don't the phone got far enough through the boot process for root access to be allowed. I was able to run the one click root tool while it was in its stuck boot phase, but it still wouldn't give me permission to modify the /system portion of the phone to be read/write.
All in all though this was a great learning experience. Prior to this happening I knew nothing about adb and now I know commands for pulling, pushing, remounting, shell commands, and other things. I also learned how to fix a softbrick (first one) and what RUU is.
I've recently started having problems after changing ROMs a couple of times.
I tried installing a new Rom (CM12.1) but it is still happening and I've installed a new GAPPS each time too so I guess the problem runs deeper than that.
The ROM runs fine for a bit but then all of a sudden I get a force close which constantly keeps coming up no matter how many times I press 'Ok'.
I've had a few different processes stop but the last two that spring to mind are 'process.android.phone', 'Swiftkey' and 'Google Play'.
I have to reboot but then end up stuck at the splash screen at boot. I then have to Power+Vol Down to go into recovery and then reboot system from there. It then runs through the App optimisation screen brfore restarting.
I've never touched kernels since I've been changing ROMs so whether thats the issue.
Any help with this would be great as otherwise this is the best Rom Ive used.
Thanks in advance
A logcat showing traces of these force closes would help
Aquous said:
A logcat showing traces of these force closes would help
Click to expand...
Click to collapse
I didnt do one on account of me not having a clue what the hell one was
Luckily my friend Google does know what the hell one was.
I've attached a couple of log files created around the time of the unpleasantries which hopefully might shed some light.
This one attached might be better, this was taken after I sorted out my Root Access again so might have more info.
Regards
Looks like a resources issue. Are you running any custom CM10 theme? What happens if you install such a theme providing an icon pack?
Aquous said:
Looks like a resources issue. Are you running any custom CM10 theme? What happens if you install such a theme providing an icon pack?
Click to expand...
Click to collapse
Hi, thanks for your reply. I havent been near any other custom themes. I've had this problem over a couple of Roms too.
I've tried to generate a catlog to get some error messages around the time its happening but I keep getting constant force close boxes which stop me doing anything (for a couple of different processes). The only way to stop them is to reboot but then the logs stop and reset when it boots so I cant get the info.
I've had to reboot about three times today and each time it has had to optimize the apps for some reason.
I've tried to get a catlog through ADB but I cant run the Android SDK as I need to install the JDK which keeps giving me 'Error 1500' on the install (even though I am most definately not already trying to install it).
Thanks for your help so far though and taking the time to read through the previous log.
Every solution I try just seems to create more problems
I've managed to attach a text file of all the error files its had since it started up (they are all in the space of about 10mins)
I'm not seeing any force closes in there. In your previous log, I saw these lines:
Code:
07-15 18:24:07.919 W/ResourceType(2356): No package identifier when getting value for resource number 0x00000000
07-15 18:24:07.919 W/PackageManager(2356): Failure retrieving resources for [insert any package here basically]: Resource ID #0x0
which led me to identify resources (i.e. icons, drawables, etc) as your culprit.
What we need to do with that information, I wouldn't know. Ask the rom dev, I suppose?
Aquous said:
I'm not seeing any force closes in there. In your previous log, I saw these lines:
Code:
07-15 18:24:07.919 W/ResourceType(2356): No package identifier when getting value for resource number 0x00000000
07-15 18:24:07.919 W/PackageManager(2356): Failure retrieving resources for [insert any package here basically]: Resource ID #0x0
which led me to identify resources (i.e. icons, drawables, etc) as your culprit.
What we need to do with that information, I wouldn't know. Ask the rom dev, I suppose?
Click to expand...
Click to collapse
Well I'm assuming their force closes. I get a white box popping up that says 'unfortunately XXXXX has closed' and when I click 'ok' the box goes away but either comes straight back or another similar one pops up. Its Trebuchet quite a lot.
I can't do anything then, if I try to get to LogCat that closes too and I can't really do anything until I reboot.
Its happened over 3 different Roms so dont think theres much the Rom compiler (is that what they're called, lol) can do.
I'm am probably going to have to see if I can get a Log through ADB, if I can remember how to use it, when I have time.
Cheers
I've managed to connect the tablet through ADB and managed to get some errors taken at the time I started getting all the 'Unfortunately XXXXX has closed [ok]' boxes kept coming up.
All the error messages attached came up in the space of a few seconds.
Ahh, now this is interesting. The main cause of your problem is that your filesystem is remounted read-only, which Play Store Services doesn't like.
As to why this is going on I can only guess, but it's possible that it's due to filesystem corruption. Can you try running fsck from recovery?
Aquous said:
Ahh, now this is interesting. The main cause of your problem is that your filesystem is remounted read-only, which Play Store Services doesn't like.
As to why this is going on I can only guess, but it's possible that it's due to filesystem corruption. Can you try running fsck from recovery?
Click to expand...
Click to collapse
Hi,
Thanks for looking through them errors.
To be honest I haven't heard of fsck. Is it something I can pick up fairly simply or am I more likely to do more damage? I've done a few searches and it looks a bit difficult and couldn't really find any threads that sounded similar to what I might need.
Thanks again
Update : I've gone into recovery and found files in /system/bin called fsck.exfat and fsck.f2fs is it a case of running a command through terminal command in recovery from this directory?
Fsck is the linux file system checker. The binary is named e2fsck. I think the command should be:
Code:
e2fsck -pv /dev/block/platform/omap/omap_hsmmc.1/by-name/DATAFS
This will try to automatically fix any errors (be sure to note whether there are any). If it complains about unexpected inconsistencies, you'll need to remove the 'p' argument to prevent it from trying to do any automatic fixing.
Note: the whole point of this command is to check and, if needed, modify low-level filesystem structures, so there is a risk of data loss on your DATAFS (i.e. /data) partition.
Be sure to note if there are any errors. If there are, we need to investigate where those are coming from. If not, something else is causing your fs to remount readonly (because THAT is ultimately what is triggering your system to flip out).
(Apologies for the delay, it's been a busy week)
Aquous said:
Fsck is the linux file system checker. The binary is named e2fsck. I think the command should be:
Code:
e2fsck -pv /dev/block/platform/omap/omap_hsmmc.1/by-name/DATAFS
This will try to automatically fix any errors (be sure to note whether there are any). If it complains about unexpected inconsistencies, you'll need to remove the 'p' argument to prevent it from trying to do any automatic fixing.
Note: the whole point of this command is to check and, if needed, modify low-level filesystem structures, so there is a risk of data loss on your DATAFS (i.e. /data) partition.
Be sure to note if there are any errors. If there are, we need to investigate where those are coming from. If not, something else is causing your fs to remount readonly (because THAT is ultimately what is triggering your system to flip out).
(Apologies for the delay, it's been a busy week)
Click to expand...
Click to collapse
Hi,
No worries mate, I wasn't sure if what I said didn't make sense thats why there were no replies
The problem seems to be a lot better now but I've still had it a couple of times over the last two days.
I've tried to run the command above but with no joy. I'm still only learning the basics of ADB so still having some trouble.
I wasn't sure exactly where to run the commands from through the SDK so just went to the Terminal Command in Recovery and after navigating to the system/bin folder tried that command but it came up with the following:
/dev/block/platform/omap/omap_hsmmc.1/by-name/DATAFS is in use
esfsck: cannot continue, aborting
I apologise if some of what I am doing seems nonsense but I am trying to pick up what I can by myself from various sketchy threads to avoid being a 'tell me what to do cos I can't be bothered looking myself' person. I dont know if this is doing more harm then good
Thanks again in advance for your help.
You cannot check a filesystem while it is in use. Solution: boot to recovery (sorry, I should have specified), then make sure your data partition is not mounted (in CWM it isn't by default, which is good). Then it should be able to run.
(so: boot tablet to recovery, on computer run 'adb shell', in adb shell copy/paste the actual fsck command)
Aquous said:
You cannot check a filesystem while it is in use. Solution: boot to recovery (sorry, I should have specified), then make sure your data partition is not mounted (in CWM it isn't by default, which is good). Then it should be able to run.
(so: boot tablet to recovery, on computer run 'adb shell', in adb shell copy/paste the actual fsck command)
Click to expand...
Click to collapse
For some reason I cannot get my PC to pickup the tablet in a command window when in TWRP so I was unable to run through ADB. 'ADB Devices just did not show anything.
In the end I did it all on my tablet in TWRP through the 'Command Terminal'. I navigated to the necessary folder (the one with fsck.exfat and fsck.f2fs in - /system/bin) through the Command Terminal and after typing the command in I got the following:
/dev/block/platform/omap/omap_hsmmc.1/by-name/DATAFS clean, 9086/791520 files, 694414/3160055 blocks
Is that good?
It means that your emmc is fine and that there's a different reason why you're getting force closes. Can you post a dmesg next time it happens?
Aquous said:
It means that your emmc is fine and that there's a different reason why you're getting force closes. Can you post a dmesg next time it happens?
Click to expand...
Click to collapse
Hi, yea sure. I could use a bit of guidance with exactly how to do that though. I take it that is something I would have to run through ADB from my PC before I reset my tablet? Step by step instructions would be appreciated a lot (as has your extensive help already, creep creep ).
Boot to normal android. Wait until you start getting force closes. Stick your tab into your computer, run 'adb shell', then run 'dmesg'. If it says permission denied, run 'su' first and then run 'dmesg' again. Post the output.
Aquous said:
Boot to normal android. Wait until you start getting force closes. Stick your tab into your computer, run 'adb shell', then run 'dmesg'. If it says permission denied, run 'su' first and then run 'dmesg' again. Post the output.
Click to expand...
Click to collapse
Right, first thing this morning I had some errors, so I've managed to paste the results of a dmesg into the log file attached.
Cheers!
Hmmmm, now this is interesting. It looks like random services are failing to load - they are immediately exiting after being restarted. This is basically the same problem as with your apps force closing - something at the lower layers is causing everything to crash immediately upon launch.
Yet you're able to run basic programs (e.g. adb, dmesg) just fine, meaning that it's not likely to be a hardware issue.
What happens if in adb shell you run su and then 'stop' followed by 'start'? What should happen: when you run 'stop', the whole system freezes, and when you run 'start', you see your boot logo and android starts booting up again. Is this indeed what happens in this case, or do you get a bootloop? If so, post another logcat when you're stuck in the loop; you can get out of it by simply entering 'reboot' in your still-open adb shell.
Pressed the home button while using Snapchat, phone froze, had to hard reset it, phone got stuck in constant Google logo bootloop. Getting a replacement shipped out...but I have a video I recorded yesterday morning that never backed up on Photos, any possible way to save it? Someone mentioned an ADB method..? But with my little research I think you need to factory reset the phone for that, which would make this method a waste as I need to get this video off it.
I never rooted this phone, I didn't unlock the bootloader. I did turn on developer settings. That's all I know regarding that.
Other information regarding the fastboot screen: Boot-slot: a, Console: DISABLED, Secure Boot: PRODUCTION, Device is LOCKED.
I've turned it off and on multiple times, same thing. Rebooted it during loops, or at least tried to, same thing. Went into fastboot mode from loops, pressed start, same thing. Went into fastboot mode from phone off, same thing. I don't know what else to do. There is no way to clear a memory cache apparently. And I am sort of n00bish in this world.
Anyways, what could I possibly do to save this video, or to fix my phone out of this bootloop to take the video off the right way before my replacement comes in? Anyway to do either of that via 'ADB', some lowkey program I don't know about that can rip the entire phone's data onto some type of file I can decrypt, a program like Recuva that will find the file(s) for me and yank them out, etc? I know there has to be somebody out there with the skills or capabilities to do something like this... I hope. Please help out and let me know, thanks.
If you could do something like that with a locked bootloader / unrooted device then all security for Android would be a sham. I'd be very discouraged if someone could hack into a secure device and pull out information such as pictures, phone numbers, messages etc.
If it is locked, you are done. It's encrypted. If it were unlocked you could easily get it off the phone.
Well, I'm not feeling optimistic at all now. So there is 0, nada, nothing I can do to save this video/file or fix my phone? All because the device decided to randomly get stuck in this bootloop, I am absolutely screwed?
Unless you can get it to boot up then I do believe you are out of luck. You can't get into recovery menu?
Sent from my Pixel using XDA-Developers Legacy app
bobby janow said:
Unless you can get it to boot up then I do believe you are out of luck. You can't get into recovery menu?
Sent from my Pixel using XDA-Developers Legacy app
Click to expand...
Click to collapse
Fastboot > Recovery mode > No command screen > Power button hold + Volume up tap > Android Recovery screen with Reboot system now, Reboot to bootloader, Apply update from ADB, etc?
If that's what you mean, I can get there, I'm there right now.
czbwoi said:
Fastboot > Recovery mode > No command screen > Power button hold + Volume up tap > Android Recovery screen with Reboot system now, Reboot to bootloader, Apply update from ADB, etc?
If that's what you mean, I can get there, I'm there right now.
Click to expand...
Click to collapse
Sorry afk. Yes, that is exactly where you want to be. Try an adb sideload of the latest OTA or even the last full image. I do believe you can sideload that but if not then the OTA. You might be able to recover that way. If something got corrupt then the sideload might fix it. Or is there an option to clear cache? I think there is, you can try that first.
bobby janow said:
Sorry afk. Yes, that is exactly where you want to be. Try an adb sideload of the latest OTA or even the last full image. I do believe you can sideload that but if not then the OTA. You might be able to recover that way. If something got corrupt then the sideload might fix it. Or is there an option to clear cache? I think there is, you can try that first.
Click to expand...
Click to collapse
No option to clear cache, the rest of the options are: Apply update from SD card, Wipe data/factory reset, Mount /system, View recovery logs, Run graphics test, Power off.
I have no idea how to sideload an OTA or image to try to fix this...if you could point it out to me step by step, literally, I'd appreciate it.
czbwoi said:
No option to clear cache, the rest of the options are: Apply update from SD card, Wipe data/factory reset, Mount /system, View recovery logs, Run graphics test, Power off.
I have no idea how to sideload an OTA or image to try to fix this...if you could point it out to me step by step, literally, I'd appreciate it.
Click to expand...
Click to collapse
Don't have directions atm for sideload online but the way it works is you download the OTA from here: https://developers.google.com/android/ota Scroll down to Pixel latest U build 7.1.1. Download it and place it in your fastboot android sdk folder, I put it in the platform-tools so it's easy. Then click apply update from sd card by highlighting it with the vol keys and then power key to select. It will tell you what to do. I forgot exactly but it's something like "adb sideload <ota.zip> whatever the name is and then let it go. It will take about 10 min and after it's all done, highlight the reboot option. Power key and reboot. Hopefully that should fix it. If not, sorry I'm all out of ideas. Well other that adb sideload the full image although someone will have to verify if that would work.
bobby janow said:
Don't have directions atm for sideload online but the way it works is you download the OTA from here: https://developers.google.com/android/ota Scroll down to Pixel latest U build 7.1.1. Download it and place it in your fastboot android sdk folder, I put it in the platform-tools so it's easy. Then click apply update from sd card by highlighting it with the vol keys and then power key to select. It will tell you what to do. I forgot exactly but it's something like "adb sideload <ota.zip> whatever the name is and then let it go. It will take about 10 min and after it's all done, highlight the reboot option. Power key and reboot. Hopefully that should fix it. If not, sorry I'm all out of ideas. Well other that adb sideload the full image although someone will have to verify if that would work.
Click to expand...
Click to collapse
Just sideloaded the latest OTA with the help of a friend, and no luck. Same old stuff. And I think sideloading an image would require the bootloader to be unlocked which would require a factory reset...
Here's another thing that crossed my mind, have any of you ever used EaseUS MobiSaver for Android? It's a tool that allows you to recover deleted files from your phone, similar to Recuva and hard drives. I used it before on my parents' Galaxies, this program is from circa 2014 though so I don't know if it would have much success on a new phone like this...but you never know?
For it to work you need to have your phone on (derp) and have it rooted. Here's the tricky part...if you erase your hard drive and use a tool like Recuva, even though you erased your drive the remnants are still "there" and files are recoverable with a tool like that. Do you think that the same concept would work with phones and EaseUS MobiSaver? Say that I factory reset the phone, set it up as a new device and don't transfer over any backup, I root it, and run said program to scan the deep contents of the phone's hard drive for old data. Do you think this will work in any way possible, like how regular hard drives that got erased work, or is the phone world completely different and incomparable?
EaseUS will not work on a factory reset. You can't recover anything.
bobby janow said:
EaseUS will not work on a factory reset. You can't recover anything.
Click to expand...
Click to collapse
Well then what about programs like these: https://youtu.be/iPCoyRpMrqw?t=58s
http://www.jihosoft.com/recover-data/recover-data-after-factory-reset.html
http://androiddatarecovery.co/recover-data-after-factory-reset-from-android-mobile/
Some people say they have had some success with these...
Let us know. I'll wager you won't get anything back on the Pixel. Good luck.
czbwoi said:
Pressed the home button while using Snapchat, phone froze, had to hard reset it, phone got stuck in constant Google logo bootloop. Getting a replacement shipped out...but I have a video I recorded yesterday morning that never backed up on Photos, any possible way to save it? Someone mentioned an ADB method..? But with my little research I think you need to factory reset the phone for that, which would make this method a waste as I need to get this video off it.
I never rooted this phone, I didn't unlock the bootloader. I did turn on developer settings. That's all I know regarding that.
Other information regarding the fastboot screen: Boot-slot: a, Console: DISABLED, Secure Boot: PRODUCTION, Device is LOCKED.
I've turned it off and on multiple times, same thing. Rebooted it during loops, or at least tried to, same thing. Went into fastboot mode from loops, pressed start, same thing. Went into fastboot mode from phone off, same thing. I don't know what else to do. There is no way to clear a memory cache apparently. And I am sort of n00bish in this world.
Anyways, what could I possibly do to save this video, or to fix my phone out of this bootloop to take the video off the right way before my replacement comes in? Anyway to do either of that via 'ADB', some lowkey program I don't know about that can rip the entire phone's data onto some type of file I can decrypt, a program like Recuva that will find the file(s) for me and yank them out, etc? I know there has to be somebody out there with the skills or capabilities to do something like this... I hope. Please help out and let me know, thanks.
Click to expand...
Click to collapse
You can often get ADB while it's booting. It just depends how far into the boy process is made it. I would power it up and see if you can ADB pull the file.
TCPDump said:
You can often get ADB while it's booting. It just depends how far into the boy process is made it. I would power it up and see if you can ADB pull the file.
Click to expand...
Click to collapse
My friend was able to give it ADB commands on the fastboot/recovery menu, we sideloaded the latest OTA like that to see if it would fix it. What are you describing though, how would I be able to do that? Do you have any instructions or links on what to do? I don't know the file name for instance. The last video before that one was named VID_20170104_011325.mp4, I don't know how to find out the name of the next video file to even try to attempt what you're saying, unless you know of some way...
czbwoi said:
My friend was able to give it ADB commands on the fastboot/recovery menu, we sideloaded the latest OTA like that to see if it would fix it. What are you describing though, how would I be able to do that? Do you have any instructions or links on what to do? I don't know the file name for instance. The last video before that one was named VID_20170104_011325.mp4, I don't know how to find out the name of the next video file to even try to attempt what you're saying, unless you know of some way...
Click to expand...
Click to collapse
Well, IF it had booted enough to mount storage and start the adb daemon then you would use adb shell to locate the file.
Example:
adb shell
cd /sdcard/DCIM/
ls -la
Assuming your filename is in there, it its name is VID_20170104_011325.mp4 then you could exit the shell and do this:
adb pull /sdcard/VID_20170104_011325.mp4
TCPDump said:
Well, IF it had booted enough to mount storage and start the adb daemon then you would use adb shell to locate the file.
Example:
adb shell
cd /sdcard/DCIM/
ls -la
Assuming your filename is in there, it its name is VID_20170104_011325.mp4 then you could exit the shell and do this:
adb pull /sdcard/VID_20170104_011325.mp4
Click to expand...
Click to collapse
Only place I can seem to enter adb commands is when I go to apply update from adb, and when I do so the only thing it responds to is adb devices and sideloading, presumably because that is all it allows me to do in that mode. When I enter adb shell I get error: closed