Database Develop

[Solved] Market downloads frozen

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.

[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] XXLSA Android 4.1.2 and Low Battery: Stuck at Boot. Data Recovery?

Recently my phone had a low battery status. It booted up but apparently lost power somewhere when restoring the Apex Launcher screens.
Since then it just shows the Samsung logo and gets rather hot. I left it in this state for over an hour with no progress.
Boot and recovery mode work fine. Unfortunately adb is not in root by default, as such pulling is useless as nothing is mounted.
issuing
Code:
adb root
will result in:
Code:
adbd cannot run as root in production builds
I can issue for instance:
Code:
adb shell
su
e2fsck -pv /dev/block/mmcblk0p10
mount -t ext4 /dev/block/mmcblk0p10 /data
Unfortunately I cannot tar gzip and copy to the externalSD nor pull the data folder.
Starting dalvikvm fails:
Code:
127|[email protected]:/ # dalvikvm
dalvikvm
Dalvik VM init failed (check log file)
What options do I have to backup my data? Please provide me with concrete ideas and steps.
Many people are having similar problems, and I sincerely thank you if you can help me figure out a way to backup my data at this stage.

After reading the first two sentences and the title:
Buy a new battery.
Install something else, you are still on an early leak and not an official release.

I found a quick solution. All kudos and thanks go out to Philz as well as
TAHER128
Instructions and files are here:
http://www.youtube.com/watch?v=1TinSwsehZ8
After the new recovery mode and kernel is installed, reboot into recovery mode and go to the mount menu in order to select "mount USB storage". Backup everything to your PC.
From hereon out you are safe.
Install busybox if you want. Reflash a stock or custom rom if you want and/or dig your way through logs and fixes within a now powerful bash shell.

blairmiller said:
This problem is difficult to solve by your phone itself. Maybe you need to install some software to help you.
Click to expand...
Click to collapse
This thread is 2 months old

root
The reasons for getting a bootloop on your Android device might be anything. If you wish to know the reason why your Android phone is stuck on the bootloop, you need not type your problem on the Google search box. Just calm yourself for a while and think what you did just before. It could be anything! Here are some major reasons why your Android device is caught in a bootloop.

[Q] Pull data with broken screen

Hello,
I googled and searched the forum but none o the threads apply to my problem as far as I can see. :/
So my old phone finally dies more or less... and I am trying to get the picture from the internal storage.
My setup: I9000, running CM11 (not sure which nightly exactly), rooted, BUT usb-debugging could be off I dont know for sure.
I can go to recovery mode but as the screen is broken I am limited with my actions. So using
Code:
adb devices
I can see my device
Code:
<long number here> recovery
Here is what I tried:
Code:
adb pull / H:/backup
This does not work because after a short while it aborts with an error message: "... no such file or directory"
Using
Code:
adb shell
followed by cd sdcard gives me a "cant cd to sdcard"
If I try to cd into other directories they are empty when trying to list them with ls.
su is also not found but adb root shows that it is already running as root.
Afterwards I tried Android Commander but that also did not work for me because Android Commander did not show my device and it also crashed after a while.
To make a long story short I am desperate...
What else can I try to get my data?

push
no one?

SaphirX said:
push
no one?
Click to expand...
Click to collapse
I don't think you can just PULL the whole "/" partition. The long number you listed there is likely to be your IMEI number (Just a guess).
EDIT: You might want to check this out: http://stackoverflow.com/questions/19225467/backing-up-android-device-using-adb

[GUIDE] Fix fingerprints and Wi-Fi after failed Oreo update

If, like me, you tried to update to Oreo while you were on Nougat rooted, you should have been greeted with some encryption problems, leading to an almost complete loss of data. Except Joocx posted a guide for how to get the data back, so you could get the data back. Nice, but how do we get a working phone back? Maybe you flashed Nougat again and restored your /data and internal storage backups, hoping it would work. It did work. Except Wi-Fi was broken and fingerprints didn't work.
If you haven't managed yet to get a working phone back, you can have a look here.
Restore Wi-Fi and fingerprints on Nougat or Oreo, without data loss
Reboot in TWRP (no matter which version, as long as you use 3.2.1-0 if you're on Oreo), and from your PC run the following commands.
If you feel like it, you can also run the three rm commands from the TWRP terminal, but it's hard.
Code:
C:\> adb shell
~ # rm /data/misc/wifi/wpa_supplicant.conf
~ # rm -rf /data/system/users/0/fpdata
~ # rm /data/system/users/0/settings_fingerprint.xml
Reboot to system, and voilà.
Update: 3DSammy has pointed out that plugging in your phone to your computer is actually not required. All the file management operations can be done using TWRP's file manager (in the "Advanced" section), the commands can be run directly on the phone using TWRP's terminal and OTG storage can be used for the ROM and Magisk. I had forgot about that file manager since I thought it was only for reading (not for writing/deleting).

Just so others know, TWRP under the "Advanced" menu item has a "File Manager" which allows you to remove each of these files. That's important for those who can't get to a PC with a working adb to mount the shell. I used OTG external storage to access the OTA and Magisk zips for flashing and storage of my nandroid backup.
Personally I would need the File Manger as I have a fully functioning PC fastboot but for some reason can't see my OP5 using adb. Not a big deal but there is a user-friendly built right into TWRP which always has "root" privileges to "/data".

zdimension said:
If, like me, you tried to update to Oreo while you were on Nougat rooted, you should have been greeted with some encryption problems, leading to an almost complete loss of data. Except Joocx posted a guide for how to get the data back, so you could get the data back. Nice, but how do we get a working phone back? Maybe you flashed Nougat again and restored your /data and internal storage backups, hoping it would work. It did work. Except Wi-Fi was broken and fingerprints didn't work.
If you haven't managed yet to get a working phone back, you can have a look here.
Restore Wi-Fi and fingerprints on Nougat or Oreo, without data loss
Reboot in TWRP (no matter which version, as long as you use 3.2.1-0 if you're on Oreo), and from your PC run the following commands.
If you feel like it, you can also run the three rm commands from the TWRP terminal, but it's hard.
Code:
C:\> adb shell
~ # rm /data/misc/wifi/wpa_supplicant.conf
~ # rm -rf /data/system/users/0/fpdata
~ # rm /data/system/users/0/settings_fingerprint.xml
Reboot to system, and voilà.
Update: 3DSammy has pointed out that plugging in your phone to your computer is actually not required. All the file management operations can be done using TWRP's file manager (in the "Advanced" section), the commands can be run directly on the phone using TWRP's terminal and OTG storage can be used for the ROM and Magisk. I had forgot about that file manager since I thought it was only for reading (not for writing/deleting).
Click to expand...
Click to collapse
Hey Z,
I was hoping you can walk me through this process as I'm still unable to fix this Wifi Issue. I've done exactly as you said in the guide but my wifi is still not working. It will turn on and everything but will not connect to a network. It just says "configuring ip address".

Dchoi229 said:
Hey Z,
I was hoping you can walk me through this process as I'm still unable to fix this Wifi Issue. I've done exactly as you said in the guide but my wifi is still not working. It will turn on and everything but will not connect to a network. It just says "configuring ip address".
Click to expand...
Click to collapse
Indeed, it's weird that it's still not working. But if I understood correctly, you are able to turn it on and scan networks, which is a step forward fixing the problem. The message you are getting means that there is a problem while requesting an IP address through DHCP. Try using a static IP on that network. If it works, then there may be a conflict it some other DHCP problem on your router. Otherwise, try on another WiFi network. If neither if those works, then I don't know.

zdimension said:
Indeed, it's weird that it's still not working. But if I understood correctly, you are able to turn it on and scan networks, which is a step forward fixing the problem. The message you are getting means that there is a problem while requesting an IP address through DHCP. Try using a static IP on that network. If it works, then there may be a conflict it some other DHCP problem on your router. Otherwise, try on another WiFi network. If neither if those works, then I don't know.
Click to expand...
Click to collapse
Thanks for the response Z! I just tried it and my wifi isn't stable at all when trying to connect to wifi. It's my workplace wifi that I usually have to sign into to access. It'll connnect and disconnect constantly. Is there anything you'd advise me to do?

Ok so I'm a little confused.
Are we running the command in one full line? eg:
C:\> adb shell ~ # rm /data/misc/wifi/wpa_supplicant.conf
My fingerprint sensor never died so I don't require that fix. I just cannot connect to wifi network. Detects it but once connection attempts in just reverts to 'saved' and tries to reconnect.
Also are you sure this is run once you boot into TWRP and not Fastboot mode?
Running from TWRP via ADB:
C:\>adb shell ~ # rm /data/misc/wifi/wpa_supplicant.con
/sbin/sh: /: Permission denied
From TWRP terminal manager I ran the same command and errored with sh: adb: not found.
I'm rooted and encrypted.
Cheers.

buzzfuzz1 said:
Ok so I'm a little confused.
Are we running the command in one full line? eg:
C:\> adb shell ~ # rm /data/misc/wifi/wpa_supplicant.conf
My fingerprint sensor never died so I don't require that fix. I just cannot connect to wifi network. Detects it but once connection attempts in just reverts to 'saved' and tries to reconnect.
Also are you sure this is run once you boot into TWRP and not Fastboot mode?
Running from TWRP via ADB:
C:\>adb shell ~ # rm /data/misc/wifi/wpa_supplicant.con
/sbin/sh: /: Permission denied
From TWRP terminal manager I ran the same command and errored with sh: adb: not found.
I'm rooted and encrypted.
Cheers.
Click to expand...
Click to collapse
Nah, the command is supposed to be run when the phone is in TWRP.
First, you use adb shell to open a terminal from your PC (ignore this step if you want to use TWRP's integrated terminal directly on the phone).
Then, when you're in the shell, run the rm command.

Well it seems this fix didn't work unfortunately :/ Wifi still cannot connect to any network.
Is the command simply deleting the file and it regenerates upon reboot?

buzzfuzz1 said:
Well it seems this fix didn't work unfortunately :/ Wifi still cannot connect to any network.
Is the command simply deleting the file and it regenerates upon reboot?
Click to expand...
Click to collapse
The file the command deletes is basically the "Wi-Fi" settings file, which contain identification settings for the network card amongst other things. If you keep the Nougat one while you're on Oreo, you can't turn on Wi-Fi, or use anything related to the Wi-Fi antenna; Thus, we delete it. That solves the problem "Wi-Fi doesn't turn on". Here, you've got another problem: "Wi-Fi can't connect". I have no clue of what could be causing this, this issue never happened to me. I'm gonna search a bit and update here if I find anything.