[Solved] Market downloads frozen - G1 Q&A, Help & Troubleshooting

Just a couple of days ago my Market seems to have frozen. I'll try to start downloading something (or updating) and all it does is say "starting download". Never progresses beyond that. I've canceled the download and restarted a million times. I've tried to download any application on the market and get the same results. I've flashed back to a nandroid backup that was several days before this happened. I've turned wifi on/off several times, turned airplane mode on/off several times. Restarted more times than I can count.
No idea. Nothing changed from when downloads worked to now. No new apps, no settings changed. Just stopped downloading.
[Solved] - See post #7

Likely to be an issue at google's end...

try
Code:
adb shell mount -o rw /dev/block/mtdblock3 /system
adb shell echo "ro.config.nocheckin=1" >> /system/build.prop

B, what Does that code do? Do I just drop the adb commands if in terminal (same otherwise)?

B-man007 said:
try
Code:
adb shell mount -o rw /dev/block/mtdblock3 /system
adb shell echo "ro.config.nocheckin=1" >> /system/build.prop
Click to expand...
Click to collapse
What exactly does that do? First line mounts /system form editing, but I have no idea what the second line is about.

For cyanogen roms, cyanogen has a setting to disable the checkin service by google in his build.prop
the checkin service is required for setup wizard when coming from a wipe, but is not needed after. this is why its not disabled by default. Its what causes the market freezes most of the time. if its still giving errors, there may be a bigger problem.

Problem solved.
Didn't do your lines of code there B, but what I did do worked.
Went to Manage Applications and then Google Apps and cleared the data for it. That required that I resign into my Google Account when I went back to the Market.
On another note that may or may not be related, I keep getting gapps forcecloses. They seem to come randomly, not sure why. Don't know if that could be related, seems like it could be though.

Related

[Q] Need help with my semi-broken NC - what did I do wrong?

I have sucessfully rooted my nook and I can load apks from dropbox, installers or via adb so I am a happy camper, all is good....
But I got greedy. The ComicViewer doesn't work well without menu keys so I decided to install softkeys.apk and that is where the trouble started, something is amiss.
I am not an expert here, just a novice, so forgive my patchwork explanation.
Here's what I know and what I did, maybe someone can spot my error?
I can fully access adb.
I remember installing SuperUser and SU using the commands:
# adb shell
# cd /system/bin
# mount -o remount,rw /dev/block/mmcblk0p5 /system
# cat /data/local/su > su
# chmod 6755 su
# ls -l su
And all was fine, SuperUser shows up in the drawer. Then I tried installing SoftKeys and it never showed up or worked.
So I figured I fubared the SuperUser install somehow or have an old version of SU or SuperUser. So I downloaded the most recent versions and went to uninstall the original with uninstall utilities and it's not listed in any of them, so I tried using adb (adb shell ls /data/app) and it's still not in the list.
I even reset the Nook to factory and rooted again with nooter and when I tried to install SuperUser again (downloaded the latest version here on the forum) it said "Install Failed already exists!"
So I cannot uninstall the SuperUser or overwrite it with a newer version, and a factory reset doesn't fix it??
I cannot use any root utilities like SuperUser or z4root, SuperUser has all blank screens and I cannot update it and 4zroot just doesn't seem to do anything but reboot the nook.
Titanium Backup says I don't have root access and other utilities say the same thing,
I can mount system partition as read-write
> adb shell
# mount -o remount rw /system
# exit
That works...
So I tried the commands again to install SuperUser and SU and when I try to install SU
# cd /system/bin
# mount -o remount,rw /dev/block/mmcblk0p5 /system
are OK but when I do:
# cat /data/local/su > su
I get:
Cannot create su: remote access failed
I have also tried a few other things that seem to be available to root users and all come back with write or access errors.
What could I be doing wrong?
Note: I also tried to do a full wipe by using that Power and Volume Down and nothing happens...
Power the nook on and off immediately 8 times until it does a full factory reset. When I've done the Power+VolUp+Nook button reset it doesn't always seem to do a FULL reset. When the nook fails to boot 8 times it does a different reset that takes a good deal longer and (at least in my experience) seems to be the real deal.
z4root will work and install superuser for you.
mhoepfin said:
z4root will work and install superuser for you.
Click to expand...
Click to collapse
I have already mentioned that that did not work, but thanks for the suggestion anyway.
Ok, something VERY weird is going on.
I have reset it to factory twice
Each time I did it by powering on and off 8 times in a row
The first time after it indicated it was updating th software, it went into a stuck at NookColor Logo boot loop again.
The second time I left in the nooter microSD card and it booted properly.
But it booted to a "clean" system with all my programs.
All my settings and data was gone, but all my apks were still installed.
So what exactly did it reset? Just data?
I tried to get it to flash both ways, the quick (power/home/volume) and now twice with the 8 power cycles. Neither reset the Nook entirely.
Am I screwed?
I want to go back to factory to fix this thing
EDIT:
Looks like I am locked out of the system entirely, none of my apps work, some of them come back and say no write access.
I cannot do an app listing like:
adb shell ls /data/app
I get:
opendir failed, Permission denied
I can't do a simple mount
mount -o remount rw /system
I get:
mount: operation not permitted
This should help you with what type of reset you want to do. I think you should do another 8 power on/off reset followed by a power-up-home reset to get it fully reset.
axe2 said:
This should help you with what type of reset you want to do. I think you should do another 8 power on/off reset followed by a power-up-home reset to get it fully reset.
Click to expand...
Click to collapse
I tried that...
Now it's completely dead.
Won't power up at all.
It had plenty of battery life left and plugging it in will not boot it either...
gormly said:
I tried that...
Now it's completely dead.
Won't power up at all.
It had plenty of battery life left and plugging it in will not boot it either...
Click to expand...
Click to collapse
Well that's a bummer! Maybe something went wrong in one of the resets. Did they seem to complete? If it's not a hardware problem you should still be able to revive it via nooter. I would suggest PMing pokey9000 and see if he can walk you through a recovery. You might be the first near brick that requires running some of the recovery commands by hand. I think Pokey9000 knows the most about that.
axe2 said:
Well that's a bummer! Maybe something went wrong in one of the resets. Did they seem to complete? If it's not a hardware problem you should still be able to revive it via nooter. .
Click to expand...
Click to collapse
Yea, but it won't respond to anything, it won't boot meaning no power at all.
It's just completely black screen.
Nothing I do does anything.
gormly said:
Yea, but it won't respond to anything, it won't boot meaning no power at all.
It's just completely black screen.
Nothing I do does anything.
Click to expand...
Click to collapse
Whatever you do make sure the battery is getting charged somehow.. Try to leave it plugged into the wall or in a usb. Does the computer see the device when plugged in? HAve you tried to remove the SD card from the NC while powering up?
norkoastal said:
Whatever you do make sure the battery is getting charged somehow.. Try to leave it plugged into the wall or in a usb. Does the computer see the device when plugged in? HAve you tried to remove the SD card from the NC while powering up?
Click to expand...
Click to collapse
Yep tried all those things...very frustrating afternoon so far
However...I did get it to boot.. here is how:
Press and hold the power button while inserting the USB charger connected to a computer, continue to hold (I think it was 10 seconds or so).
I remember doing this to reset a device a long time ago, not sure what.
But it worked, not only that but I was able to do a pwer/up/home rest and this time it completely wiped the nook. It looks like I am back to factory!
YES!!
Thanks for alll the help and suggestions guys. Hopefully this struggle will help someone else in the future.
gormly said:
But it worked, not only that but I was able to do a pwer/up/home rest and this time it completely wiped the nook. It looks like I am back to factory!
YES!!
Thanks for alll the help and suggestions guys. Hopefully this struggle will help someone else in the future.
Click to expand...
Click to collapse
OK. This time around, do this:
(1) nooter
(2) use ADB to enable Non-Market Apps
(3) use ADB to enable multitouch
(4) Use ADB to push z4root over to the NC
(5) Run z4root and do a full-root (whatever is NOT the "temp" option)
(6) Use ADB to install Astro
(7) Use ADB or Astro to install a market
(8) Install the rest of your apps however you choose.
johnopsec said:
OK. This time around, do this:
(1) nooter
(2) use ADB to enable Non-Market Apps
(3) use ADB to enable multitouch
(4) Use ADB to push z4root over to the NC
(5) Run z4root and do a full-root (whatever is NOT the "temp" option)
(6) Use ADB to install Astro
(7) Use ADB or Astro to install a market
(8) Install the rest of your apps however you choose.
Click to expand...
Click to collapse
I did 1,2,3,6,7,8 and in place of 4/5 I used the most recent version of SU and SuperUser and all is good on my Nook! Not sure what happened before but it must have been a bad version of su or superuser. In any case, all seems fine, only Titanium doesn't work, all the rest of the root requesting apps work fine.
Thanks!

[Q] Help upgrading Market

I recently rooted my Nook color with Auto Nooter 2.12.25. It gave me the Google Market but it is the old one and it only displays 10 apps in portrait mode and some of the buttons have problems working. I read in a thread that the newer market fixes that and I downloaded an apk named com.android.vending02.apk but when I try to install it, the app manager doesn't have an install tab. I downloaded a 3rd party install manager and when I try to install it says that 'There is a problem parsing this package'.
I have read that people have installed the updated market but no one gives an explanation how. Does anyone know how do this? Thanks for your help.
Found solution
I found a solution.
Dont just post you found a solution, that helps no one. post what the solution was or atleast a link to the fix.
Good Call
I installed the APK at the top of this thread http://forum.xda-developers.com/showthread.php?t=872621 and then reset my NC and the new Market worked. Apparently, after reading through the thread, this method doesn't work for everyone. There are further instructions that may be of some use.
Now my market isn't working. After trying to install this and switch back both times when I open market it just disappears.
buffnutz1 said:
Now my market isn't working. After trying to install this and switch back both times when I open market it just disappears.
Click to expand...
Click to collapse
I had the same problem on my 1.1.0 NC rooted with Decad3nce's V1.1.0_r2 [01/29/2011] method (there's a huge long thread on that in the Development forum). I was dreading the possibility of having to wipe the machine and start over, but I just re-flashed the zip file, and everything's working fine again. Unfortunately, I'm still stuck with the old Market.
If you're feeling like you can handle cmd-line stuff, try this method out.
First download the attached newmarket.apk
open/connect adb
adb shell
mount -o remount,rw /dev/block/mmcblk0p5 /system
exit
adb pull /system/app/Vending.apk (notice the cap V, also this will get put into your platform-tools folder. Back it up!)
adb push pathtonewmarket.apk /system/app/Vending.apk
adb reboot
Once you've rebooted then go into settings->applications->manage->all
Find the market and clear the cache
Then find google services framework and clear the data then force quit
reboot once more
After that the new market should work just fine.
Thanks Woot! does this work on Froyo 0.6.7 too?
woot1524 said:
If you're feeling like you can handle cmd-line stuff, try this method out.
First download the attached newmarket.apk
open/connect adb
adb shell
mount -o remount,rw /dev/block/mmcblk0p5 /system
exit
adb pull /system/app/Vending.apk (notice the cap V, also this will get put into your platform-tools folder. Back it up!)
adb push pathtonewmarket.apk /system/app/Vending.apk
adb reboot
Once you've rebooted then go into settings->applications->manage->all
Find the market and clear the cache
Then find google services framework and clear the data then force quit
reboot once more
After that the new market should work just fine.
Click to expand...
Click to collapse
necroscopev said:
Thanks Woot! does this work on Froyo 0.6.7 too?
Click to expand...
Click to collapse
I can confim that it does, I used it my self to get the new market installed.
If you're booting off of an SD card and want to install the new market there. All you need to do is change one line.
FROM: mount -o remount,rw /dev/block/mmcblk0p5 /system (eMMC system partition)
TO: mount -o remount,rw /dev/block/mmcblk1p2 /system (SD-card system partition)

[Q] busybox and nandroid issues

I have been experimenting with my new droid/milestone the past couple of days, odd problems which I am past now but still curious about.
Firstly after flashing the 2.1 sbf with rsd it will autoboot and screen slider will be there, then when I reboot, screen slider will be missing. This only happend when I flashed an sbf from the sbf site(2.1 uk version, not service), doing a factory reset didn't have any problem -could reboot as many times and slider would be there.... then suddenly after factory boot it would dissapear after first boot. Anyway solved this problem by installing screen mode widget after first boot after flash, solved problem, but still weird. Fixed this now but still curious about it.
Next, nandroid backup is missing from recovery menu, I have rooted and can execute root commands after typing "su" via Android Terminal emulator, so pretty sure is rooted. So why no nandroid? I thought I could do nandroid backup after rooting.
Next busybox won't install, tried the app, did the "searching system" for over an hour(not exagerrating), eventually gave up and uninstalled.
Trying to do a "manual busybox install" now, using this guide:
Busybox How-to? - Android Forums
Can't execute commands via usb/adb in recovery mode as the other guy suggested so been trying these commands both with terminal emulator on phone, and usb-debugging mode with windows shell. Using these I can go "su" and type "ls" to see files on my droid phone....but when I try to "mount /system" or /sdcard from windows I just get a print about mount options, when I try to "cat /sdcard/busybox > /system/xbin/busybox" I get a "file is read only" error.
I would like advice on how to install busybox, I would like to do it manually(because the app seems to not work for me, remember I waited over an hour while it "searched") and I want to learn to manually do stuff anyway. I tried to chmod /system/xbin too, but that didn't seem to change it from read only.
Also any thoughts on why nandroid backup is missing from my recovery menu even though my droid is rooted. I thought it was meant to appear.
I am still learning and researching, and appreciate any links or tips.
droidtech1 said:
Next, nandroid backup is missing from recovery menu, I have rooted and can execute root commands after typing "su" via Android Terminal emulator, so pretty sure is rooted. So why no nandroid? I thought I could do nandroid backup after rooting.
Click to expand...
Click to collapse
This is odd. Which OpenRecovery did you install? Androidiani? GOT? Or the "original" OpenRecovery? Are you aware, that you come into OpenRecovery by starting Recovery Mode and apply update.zip?
droidtech1 said:
Next busybox won't install, tried the app, did the "searching system" for over an hour(not exagerrating), eventually gave up and uninstalled.
Trying to do a "manual busybox install" now, using this guide:
Busybox How-to? - Android Forums
Click to expand...
Click to collapse
Using the app from the market worked like a charm for me. No idea, what might have gone wrong for you...
droidtech1 said:
Can't execute commands via usb/adb in recovery mode as the other guy suggested so been trying these commands both with terminal emulator on phone, and usb-debugging mode with windows shell. Using these I can go "su" and type "ls" to see files on my droid phone....but when I try to "mount /system" or /sdcard from windows I just get a print about mount options, when I try to "cat /sdcard/busybox > /system/xbin/busybox" I get a "file is read only" error.
Click to expand...
Click to collapse
For remounting, try "mount -o rw,remount /dev/block/mtdblock6 /system" and for undoing this, use "ro" instead of "rw".
droidtech1 said:
I would like advice on how to install busybox, I would like to do it manually(because the app seems to not work for me, remember I waited over an hour while it "searched") and I want to learn to manually do stuff anyway. I tried to chmod /system/xbin too, but that didn't seem to change it from read only.
Click to expand...
Click to collapse
You should download busybox and put the "busybox"-file in the directory /sdcard. After that do:
Code:
# su
# mount -o rw,remount /dev/block/mtdblock6 /system
# cp /sdcard/busybox /system/xbin
# cd /system/xbin
# chmod 755 busybox
# ./busybox --install
# mount -o ro,remount /dev/block/mtdblock6 /system
One thought at the end: How did you root?
I rooted by flashing "vunerable recovery" using RSD lite, copied milestone-root.zip to sd card, renamed it update.zip, rebooted into recovery mode, flashed update.zip from there.
I didn't realise I had to install something like open recovery, think because I remember not having to do that on my pulse? Anyway will try and install one of those now.
Thanks those commands at the end helped, actually managed to copy busybox to /system/xbin, however the 2nd last one "./busybox --install" gave me a load of errors -all being no such file or directory, for example "/usr/bin/wc: no such file"
about 30 of those path errors. Maybe the command path "./busybox" needs to be something else?
ah, okay. sorry, I thought you already installed an openrecovery. for many cool features you will need it (e.g. nandroid, for overclocking it's not a must but a nice-to-have). please don't use GOT, it's rather old already. androidiani is okay, I think.
I think your previous attempts to install busybox via the app etc. mixed up some internal links in the device. please reboot and try again (the above steps except the "cp ..."). seems like the app tried to install busybox to /usr/bin but failed... I hope this failed attempt will be fixed by a simple reboot. otherwise it would be great to have the output of:
Code:
# su
# ls /usr/bin
No I re-flashed my main sbf and also did a factory reset to do a clean start, only thing since that full wipe I have done is rooting in the method I described, installed the screenmode widget, textedit, and android terminal emulator.
I have no such file /usr, are you sure I should have this in droid/milestone?
Here is my full output of my root system using ls:
tmp
pds
cdrom
sqlite_stmt_journals
config
cache
sdcard
d
etc
system
sys
sbin
proc
init_prep_keypad.sh
init.rc
init.mapphone_umts.rc
init.mapphone_cdma.rc
init.goldfish.rc
init
default.prop
data
root
dev
perhaps "/usr" is a sub inside one of the above folders? I tried using "find" to find it but that command dosn't seem to work since it won't even find the ones I can see with ls
I found it, /usr is inside /system... so if busybox was moved to /system/xbin, I'm guessing the ./ means install it to the parent directory which was /system which /usr is also in.
The errors I got said no such file "/usr" so It seems like it is trying to install to the wrong directory.... perhaps the command should be "busybox --install" or "/busybox --install" I don't want to experiment and mess things up before your opinion on this.
*edit almost forgot, output of /system/usr is
keychars
bin
srec
keylayout
share
output of /system/usr/bin is
panic_daemon
gki_pd_notifier
nvm_daemon
clean_dex.sh
brcm_guci_drv
bplogd_daemon
This is really strange. Maybe your busybox-file is corrupt.
Where did you download the busybox-file?
Which sbf did you flash?
So for explanation-purposes: When you put an executable or script file in any directory, you can execute it by first making it executable ("chmod 755 /system/xbin/busybox"), changing to that directory ("cd /system/xbin") and then executing it by adding "./" in front of it. The dot slash always stands for the _current_ directory. The _parent_directory has two dots "../".
If you want, you may try:
# /system/xbin/busybox --install
instead of
# ./busybox --install
Or maybe try this one:
# /system/xbin/busybox --install -s /system/xbin
Last time, I installed busybox into the directory /data/busybox, which worked brilliantly, but this path turned out to be unpractical. So I wanted to reinstall it in a different directory. I removed everything from /data/busybox including the directory itself and tried to start the whole procedure with /system/xbin. But that time it protested, that there were no files in "/data/busybox/...". Conclusion: The last busybox-install affected the second one. When I remember correctly I rebooted after that and used the app from the market *g*
My main sbf I flashed was android 2.1(uk version).
I downloaded busybox 1.17.2(won't let me post url here), was from droidforums dot net.
I don't remember if I tried all of his commands, but the last one on that forum seems to have worked.. I think......... it was:
"busybox --install /system/xbin/"
After remounting with your commands and typing the above command, I didn't get any errors, I synced and rebooted and now when I "ls /system/xbin" it shows a bunch of files/names which look like busybox commands. When I type "busybox" it outputs a bunch of commands too... so I am guessing this means it has succesfully installed? I can't say I tried these before attempting install so I have no comparison but I assume I would have a different output if busybox wasn't installed.
So assuming it worked, why would
"busybox --install /system/xbin/" work, and
"/system/xbin/busybox --install" not?
I also managed to install open recovery and do a nandroid backup succesfully
I have another short question, not specific to android but happens in all terminals I use, windows and linux alike. Sometimes I cannot execute commands anymore and it just becomes text in the terminal(just re-echo'ing my text output, without executing any functions)... can't remember specifically when it happened on my windows or linux pc shells, but on my android it happens whenever I have to give "SU" permission to the terminal, I have to quickly close the terminal and reload it again to get su access. I'm sure there is a name for this "state" where you are locked out of using commands in the shell and just typing text but I can't find a way to get out of it(without closing and re-opening terminal), there must be some key combination to be able to execute commands again in the current terminal session. If you have any idea what I am talking about?
Thanks for all your help so far.
droidtech1 said:
My main sbf I flashed was android 2.1(uk version).
Click to expand...
Click to collapse
Don't want to try one of the 2.2?
droidtech1 said:
I downloaded busybox 1.17.2(won't let me post url here), was from droidforums dot net.
I don't remember if I tried all of his commands, but the last one on that forum seems to have worked.. I think......... it was:
"busybox --install /system/xbin/"
After remounting with your commands and typing the above command, I didn't get any errors, I synced and rebooted and now when I "ls /system/xbin" it shows a bunch of files/names which look like busybox commands. When I type "busybox" it outputs a bunch of commands too... so I am guessing this means it has succesfully installed? I can't say I tried these before attempting install so I have no comparison but I assume I would have a different output if busybox wasn't installed.
Click to expand...
Click to collapse
Yes, this sounds very much like installation was successful.
droidtech1 said:
So assuming it worked, why would
"busybox --install /system/xbin/" work, and
"/system/xbin/busybox --install" not?
Click to expand...
Click to collapse
typing "busybox" without the path in front of it worked, because busybox is in the directory /system/xbin, which is already in your $PATH-variable (try "echo $PATH"). So the command interpreter (shell) will automatically look up "busybox" in /system/xbin.
I had a look at the busybox syntax and it's actually
Code:
busybox --install [-s] [INSTALLDIR]
So you have to put the directory you want to install in at the end. That's what your last command makes use of
droidtech1 said:
I have another short question, not specific to android but happens in all terminals I use, windows and linux alike. Sometimes I cannot execute commands anymore and it just becomes text in the terminal(just re-echo'ing my text output, without executing any functions)... can't remember specifically when it happened on my windows or linux pc shells, but on my android it happens whenever I have to give "SU" permission to the terminal, I have to quickly close the terminal and reload it again to get su access. I'm sure there is a name for this "state" where you are locked out of using commands in the shell and just typing text but I can't find a way to get out of it(without closing and re-opening terminal), there must be some key combination to be able to execute commands again in the current terminal session. If you have any idea what I am talking about?
Click to expand...
Click to collapse
Sounds like this is just the state, when shell is busy, i.e. when the last process you started is still running and no prompt ($ or #) is displayed. You may kill the last process in linux using CTRL+C, which will hopefully bring back the shell prompt. No idea which shortcut replaces this on the milestone/droid. I never use any android terminals, but only the ADB-Shell: http://developer.android.com/guide/developing/tools/adb.html
I'm learning to build apps for android so I thought having 2.1 on my droid would be better for testing (instead of 2.2). I also have a Nexus-S with 2.3 and a tmobile-pulse with 1.5. So I want to keep the most native version on each phone since most consumers won't install custom roms, although some will get updates anyway.
I use my droid a lot when I am out and use the terminal a lot so having busybox too has given me more to play around with. I actually find my droid much better working on than the nexus s, love the keyboard and dpad.

[Q] Droid3 system corrupt and unable to fix

Okay, so this is a doozy. I recently got a Droid3 to replace my original Droid. I've had it for less than 3 months. Its been rooted using Pete's One Click Root for this entire time without any issues.
Last week the following symptoms manifested:
1) Most applications, including system applications, force close constantly.
2) I'm usually unable to run any applications, including the Market.
3) What applications are having issues is not consistent.
4) The phone will reboot itself randomly, sometimes constantly.
5) Sometimes after a reboot it gives me no service and has the "Touch Android to begin" screen again. The phone is completely unusable when it does this, and the only fix is to pull the battery and then its back to its previous state.
5) Any changes made to the phone do not survive a reboot.
This last one is the real kicker. I can go through, uninstall every application I've ever downloaded but if you restart the phone or it restarts itself they will all return. This goes for everything on my Internal Storage. The SDCard seems unaffected...
I tried the SBF trick here from rootzwiki. (can't link since I'm new)
This did not work. How it failed might be important:
1) The primary method (psouza4's) acts like its successful but doesn't actually do anything.
2) RSDLite method will fail in step 3 (mbmloader.bin) every time, no matter what fastboot file I try to use.
3) After doing RSDLite I had the "flashboot flash failed" error and the phone was unusable. I then tried psouza4's method again and my phone has reverted to the same broken state it was in when I started.
So I'm not at all sure what I can do here. Since the bootloader isn't cracked yet I have no means to load another ROM. The only method I can find for Droid3 is through a Marketplace app that, on the rare instances I can install it, force closes immediately!
Any advice or ideas at all would be nice.
As for what started this, only two things happened out of the normal phone usage:
1) My girlfriend tried to text me a picture for the first time (of some chairs she wanted to buy for those curious/suggestive ) which never got to me initially but when it finally did after the 4th attempt I was never able to download the image.
2) I put a PDF file on the Internal Storage. Its one I've had for years and its just some manual I needed mobile and I don't have a laptop. Confirmed its malware free as far as any software can tell.
Working theory is I unplugged my phone from the USB too quickly after uploading the file but I don't know for sure. Nothing else was done unless Verizon had a OTA update that would break a rooted phone (guessing not since no one else seems to have this issue anywhere).
Again, any help someone can provide would be excellent. I'm going to have to load up my broken Droid in the mean time. Keyboard doesn't work and the touchscreen is failing but it can take calls more reliably than my Droid3 currently!
Cowmonaut said:
Okay, so this is a doozy. I recently got a Droid3 to replace my original Droid. I've had it for less than 3 months. Its been rooted using Pete's One Click Root for this entire time without any issues.
Last week the following symptoms manifested:
1) Most applications, including system applications, force close constantly.
2) I'm usually unable to run any applications, including the Market.
3) What applications are having issues is not consistent.
4) The phone will reboot itself randomly, sometimes constantly.
5) Sometimes after a reboot it gives me no service and has the "Touch Android to begin" screen again. The phone is completely unusable when it does this, and the only fix is to pull the battery and then its back to its previous state.
5) Any changes made to the phone do not survive a reboot.
This last one is the real kicker. I can go through, uninstall every application I've ever downloaded but if you restart the phone or it restarts itself they will all return. This goes for everything on my Internal Storage. The SDCard seems unaffected...
I tried the SBF trick here from rootzwiki. (can't link since I'm new)
This did not work. How it failed might be important:
1) The primary method (psouza4's) acts like its successful but doesn't actually do anything.
2) RSDLite method will fail in step 3 (mbmloader.bin) every time, no matter what fastboot file I try to use.
3) After doing RSDLite I had the "flashboot flash failed" error and the phone was unusable. I then tried psouza4's method again and my phone has reverted to the same broken state it was in when I started.
So I'm not at all sure what I can do here. Since the bootloader isn't cracked yet I have no means to load another ROM. The only method I can find for Droid3 is through a Marketplace app that, on the rare instances I can install it, force closes immediately!
Any advice or ideas at all would be nice.
As for what started this, only two things happened out of the normal phone usage:
1) My girlfriend tried to text me a picture for the first time (of some chairs she wanted to buy for those curious/suggestive ) which never got to me initially but when it finally did after the 4th attempt I was never able to download the image.
2) I put a PDF file on the Internal Storage. Its one I've had for years and its just some manual I needed mobile and I don't have a laptop. Confirmed its malware free as far as any software can tell.
Working theory is I unplugged my phone from the USB too quickly after uploading the file but I don't know for sure. Nothing else was done unless Verizon had a OTA update that would break a rooted phone (guessing not since no one else seems to have this issue anywhere).
Again, any help someone can provide would be excellent. I'm going to have to load up my broken Droid in the mean time. Keyboard doesn't work and the touchscreen is failing but it can take calls more reliably than my Droid3 currently!
Click to expand...
Click to collapse
I can say a couple words to describe my reaction.. OH ****. Your phone seems to have too many problems to be software related. Try to flash back to stock 5.6.890 and get a new phone.
Sent from my DROID3 using XDA App
Hmm, I guess for the mean time I'll just have to keep trying to get the Marketplace ROM Manager to install and launch. Should be a way to install straight to the SDCard that doesn't have problems.
Thinking it over, my Internal Storage may just have a bad sector... Yeesh.
Have you tried formatting /system in mounts and storage in CWM? Then reinstalling a fresh rom on top?
Sent from my DROID3 using xda premium
Negative. I didn't have CWM installed (stock ROM just rooted for certain apps) and apps are usually crashing now.
I'll give that a shot though. Sometimes I can use an app so maybe if I'm persistent...
and to verify, you are using the verizon droid 3 xt862? Are you on 5.5.959 or 5.6.890 (or possibly 5.7.894)?
Yea can't get any new apps to run. Interestingly, the camera app seems to crash the OS at the moment.
I think I'm going to have to try to RMA...
MrJudylicious said:
and to verify, you are using the verizon droid 3 xt862? Are you on 5.5.959 or 5.6.890 (or possibly 5.7.894)?
Click to expand...
Click to collapse
Its running 5.6.890. Unless I'm mistaken its the xt862. I've only had it since September.
well as long as root isnt showing and the /system hasnt been changed from stock rom, it should work. i do find it bad that rsd didnt work. i wonder if you were trying to flash the .959 sbf on your .890 system? I would def try again to sbf and wipe data/cache through stock recovery after that using volume buttons (android!)
Well, that's kind of the problem. Changes don't survive a reboot so i haven't been able to unroot the phone. I double checked and the file was the .890 flashboot. Wiping data/cache literally does nothing.
Is there a way to format this offline, from a PC? Going to try some more Google searches...
wiping data/cache should erase all of your saved data and force you to *228. Make sure USB debugging is on, set usb to Charge Only, try petes motorola tools to unroot but using RSD 5.5 fastboot .890 found http://forum.xda-developers.com/showthread.php?t=1255198
MrJudylicious said:
wiping data/cache should erase all of your saved data and force you to *228. Make sure USB debugging is on, set usb to Charge Only, try petes motorola tools to unroot but using RSD 5.5 fastboot .890 found http://forum.xda-developers.com/showthread.php?t=1255198
Click to expand...
Click to collapse
1) How do you unroot with Pete's motorola tools? Is it a different version than the one click root? Cause that's how I rooted my phone in the first place but it doesn't seem to have an option to unroot...
2) The link for the flashboot file gives a 404 error. The attached .RAR only has the .XML file.
Any place else I can get that version?
just enter stock recovery by holding down the x key on the keyboard when you boot up and wipe data
Edit: srry didnt read the full post
jellydroid13 said:
just enter stock recovery by holding down the x key on the keyboard when you boot up and wipe data
Click to expand...
Click to collapse
If you read the original post, that doesn't work.
Okay so I had an outdated version of Pete's tools which is why I didn't see the unroot option. Mine is the older one that was a batch file, not a application.
Got that sorted out and it still doesn't work. Seems I may have some permissions issues:
Code:
> su
> /system/xbin/su
> mount -o remount,rw /dev/block/mtdblock3 /system
> if [ -e /data/local/12m.bak ];
> then
> rm /data/local/12m.bak
> fi
> exit
> exit
[email protected]_solana:/$ su
exit
exit
exit
Permission denied
sh[email protected]_solana:/$ /system/xbin/su
Permission denied
[email protected]_solana:/$ mount -o remount,rw /dev/block/mtdblock3 /system
mount: Operation not permitted
[email protected]_solana:/$ if [ -e /data/local/12m.bak ];
> then
> rm /data/local/12m.bak
> fi
[email protected]_solana:/$ exit
(success)
That's part of the ADB log. There are a lot of other permission denied messages, which is a little comforting. The only thing I could think of that happened is permissions didn't get set right when Internal Storage was unmounted from my PC.
Since I can use ADB to access the shell, how can I format /system on the droid3? I can't seem to find the correct root name to use.
Cowmonaut said:
Okay so I had an outdated version of Pete's tools which is why I didn't see the unroot option. Mine is the older one that was a batch file, not a application.
Got that sorted out and it still doesn't work. Seems I may have some permissions issues:
Code:
> su
> /system/xbin/su
> mount -o remount,rw /dev/block/mtdblock3 /system
> if [ -e /data/local/12m.bak ];
> then
> rm /data/local/12m.bak
> fi
> exit
> exit
[email protected]_solana:/$ su
exit
exit
exit
Permission denied
[email protected]_solana:/$ /system/xbin/su
Permission denied
[email protected]_solana:/$ mount -o remount,rw /dev/block/mtdblock3 /system
mount: Operation not permitted
[email protected]_solana:/$ if [ -e /data/local/12m.bak ];
> then
> rm /data/local/12m.bak
> fi
[email protected]_solana:/$ exit
(success)
That's part of the ADB log. There are a lot of other permission denied messages, which is a little comforting. The only thing I could think of that happened is permissions didn't get set right when Internal Storage was unmounted from my PC.
Since I can use ADB to access the shell, how can I format /system on the droid3? I can't seem to find the correct root name to use.
Click to expand...
Click to collapse
Have you tried to root manually? Here are the original instructions vulnfactory.org/blog/2011/08/25/rooting-the-droid-3/
[edit] I guess I miss read that you are trying to unroot.
try http://rootzwiki.com/topic/4370-sbf-droid-3-fastboot-files-55959-and-56890/ but you cant go from .890 back to .959! no idea about mounting, sorry.
MrJudylicious said:
try http://rootzwiki.com/topic/4370-sbf-droid-3-fastboot-files-55959-and-56890/ but you cant go from .890 back to .959! no idea about mounting, sorry.
Click to expand...
Click to collapse
That's the reference to Rootzwiki I made in the original post, doesn't work sorry.
Using ADB I mounted /system as rw and tried to manually remove certain apps. Once I re-mounted they were there again. So something is preventing me from making real changes to the Internal Storage.
Cowmonaut said:
That's the reference to Rootzwiki I made in the original post, doesn't work sorry.
Using ADB I mounted /system as rw and tried to manually remove certain apps. Once I re-mounted they were there again. So something is preventing me from making real changes to the Internal Storage.
Click to expand...
Click to collapse
You don't have superuser permissions.. In the ADB shell your command line should start with a # indicating superuser permissions.. you have a $
ChaoticWeaponry said:
You don't have superuser permissions.. In the ADB shell your command line should start with a # indicating superuser permissions.. you have a $
Click to expand...
Click to collapse
Where do you get that idea?
When I do this manually:
1) I'm running the command prompt as Administrator
2)I'm launching into adb using the command "adb shell".
3) First thing I do is type in "su"
4) second thing I do is approve "unknown" in the superuser app on account of it never remembering I already did that.
5) I use the command "mount -o rw,remount -t yaffs2 /dev/block/mtdblock4 /system"
6) I use the "ls" command on /system/app and find an .apk to uninstall (not all my apps seem to be installed in this location either...)
7) I use the "pm list packages" command to find the rest of the files for that .apk
8) I use "rm <filename>.apk" followed by "pm uninstall <whatever that developer chose to name things>" command to fully uninstall.
I should note on my phone at this point it disappear from the application list.
9) I use the command "mount -o ro,remount -t yaffs2 /dev/block/mtdblock4 /system"
10) I use the "ls" command on /system/app to confirm and voila, the apk file is back!
The app doesn't show up in my app manager until I reboot the phone. Changes to /system and /data are not persisting and I have no idea why.
I can't seem to unmount them either so I can't format via ADB...

[Q] After rebooting always getting Factory Test

Hello guys,
Here is my problem: When I reboot the phone I always get this black banner with yellow words. I found that it is related to a process running called factory test. When I stop it through Application manager, the banner vanishes. Looking at the forum, I found that by changing /efs/FactoryApp/factorymode to ON, I can solve this issue. Well, it does (temporally). After rebooting the phone, the file is back on off and I still get the banner.
I can live with this problem, and change it manually every time after reboot. However, my phone is almost unusable. In my baseband is showing XXX. Again, looking for a solution in the forum I found that the problem could be on the missing NV.DAT file in /modemfs/PERM/PROT/. I did push the file there, however, after rebooting the file is gone.
On the top of it all, I'm getting the "not enough space" message. I do not have an external sd card. It seems that it's a mounting problem related. I don't know if those problems are related to each other or independent.
I tried to flash a stock rom. However I still getting those problems. I had (and was using) the Maclaw CM10.1 when the phone entered in boot loop. I am running a rooted rom (Jelly Bean).
In resume, it is really messed up. So, the question is: Have any one faced those problems all together? Or have any idea what may be the cause and possible solution for those problems?
Thanks for any help.
kent13 said:
Hello guys,
Here is my problem: When I reboot the phone I always get this black banner with yellow words. I found that it is related to a process running called factory test. When I stop it through Application manager, the banner vanishes. Looking at the forum, I found that by changing /efs/FactoryApp/factorymode to ON, I can solve this issue. Well, it does (temporally). After rebooting the phone, the file is back on off and I still get the banner.
I can live with this problem, and change it manually every time after reboot. However, my phone is almost unusable. In my baseband is showing XXX. Again, looking for a solution in the forum I found that the problem could be on the missing NV.DAT file in /modemfs/PERM/PROT/. I did push the file there, however, after rebooting the file is gone.
On the top of it all, I'm getting the "not enough space" message. I do not have an external sd card. It seems that it's a mounting problem related. I don't know if those problems are related to each other or independent.
I tried to flash a stock rom. However I still getting those problems. I had (and was using) the Maclaw CM10.1 when the phone entered in boot loop. I am running a rooted rom (Jelly Bean).
In resume, it is really messed up. So, the question is: Have any one faced those problems all together? Or have any idea what may be the cause and possible solution for those problems?
Thanks for any help.
Click to expand...
Click to collapse
type in terminal emulator:
Code:
su
rm /efs/FactoryApp/factorymode
echo -n ON >> /efs/FactoryApp/factorymode
chown 1000.1000 /efs/FactoryApp/factorymode
chmod 0744 /efs/FactoryApp/factorymode
reboot
samersh72 said:
type in terminal emulator:
Code:
su
rm /efs/FactoryApp/factorymode
echo -n ON >> /efs/FactoryApp/factorymode
chown 1000.1000 /efs/FactoryApp/factorymode
chmod 0744 /efs/FactoryApp/factorymode
reboot
Click to expand...
Click to collapse
Hi samersh72,
I have tried it before and didn't help. When I reboot the phone, the problem persists and the file still with 'OFF'. I don't know if it makes any differences, but I'm running those commands through adb, since I could not install any app. (I tried to push the apk file of terminal emulator to /syste/app/ but it crashes when I try to open it. I also tried to do it using Root Explorer.. Both cases, no success.)

Categories

Resources