Database Users

How to fix market download "freezes"

I think I've found the cause of this, where you download something from the Market and it says downloaded but just sits there forever. Google has something called a "checkin" service that sends them anonymous usage data, bug reports, crash logs, etc, but it fails a lot. When you download something from the Market, it sends a message to Google about it, and if it fails it just freezes.
You can turn this off easily with a system property. I haven't seen any issues with doing this except that it will break the setup wizard if you have this set during boot after a wipe.
All you need to do is add this line to the end of /system/build.prop:
Code:
ro.config.nocheckin=1
So, something like this:
Code:
adb pull /system/build.prop .
(edit file with notepad, vim, emacs if you hate yourself)
adb remount
adb push build.prop /system
adb shell reboot
Hopefully this helps someone and Google doesn't shoot me down from space

build.prop reverts after reboot
hey
followed instructions
- pulled build.prop
- added ro.config.nocheckin=1 to end
- adb remount (RW filesystem)
- pushed new build.prop, says 2593 bytes written
- rebooted device
upon reboot: /system/build.prop reverts back to original
any idea for a Rogers Dream user here

Just wanted to clarify that the steps should actually be:
Code:
adb remount
adb pull /system/build.prop .
*(edit file with notepad, vim, emacs, whatever)*
adb push build.prop /system
adb shell reboot
Otherwise, people are going to reboot their computers willy-nilly, and not their androids.

cyanogen said:
Hopefully this helps someone and Google doesn't shoot me down from space
Click to expand...
Click to collapse
Google is going to have you wacked for figuring this out.

terminal commands plz?

G1-evolve said:
terminal commands plz?
Click to expand...
Click to collapse
Code:
su
mount -o remount,rw /system
echo "ro.config.nocheckin=1" >> /system/build.prop
reboot

cyanogen said:
Code:
su
mount -o remount,rw /system
echo "ro.config.nocheckin=1" >> /system/build.prop
reboot
Click to expand...
Click to collapse
Thanks alot! What would be the "Undo" to this incase one day I need to wipe/flash a rom?
edit: seems to still "hang" and not work. Only works if I log into "gtalk"

After having completed this procedure, I've still managed to "hang" the market once. Though in all fairness, once is fine, because it used to happed daily.
However, I've noticed something that some people might consider a "down side" - when you uninstall apps, they remain in your downloads. That's exactly the same behavior that people were complaining about before cupcake came out.

besides anonymous usage data, bug reports and crash logs, what else would i be disabling by doing this?

AlfaTrion said:
besides anonymous usage data, bug reports and crash logs, what else would i be disabling by doing this?
Click to expand...
Click to collapse
Well, as I've mentioned in my post above yours, all apps that you ever downloaded while having check-in disable, will stay in your My Downloads. Again, it doesn't bug me as I use aTrackDog primarily for update checks, but I know some people don't like this.

Have you tried clearing the market cache in Settings > Applications > Manage Applications > Market? I'm curious to know if that assist with that at all.

jordanjay29 said:
Have you tried clearing the market cache in Settings > Applications > Manage Applications > Market? I'm curious to know if that assist with that at all.
Click to expand...
Click to collapse
I haven't, but I'll try. Though I am quite sure it will not do anything because that list remains the same through flashes and upgrades, so I'm sure it's pulled from Google servers.

my solution......
Whenever the market hangs when I download [email protected] reboot and it works fine. I don't get the hang problem a lot so it doesn't bother me to reboot.

pistol4413 said:
Whenever the market hangs when I download [email protected] reboot and it works fine. I don't get the hang problem a lot so it doesn't bother me to reboot.
Click to expand...
Click to collapse
It's not only about Market hanging. After disabling check-in, Market actually works much faster because data does not get sent to Google every time you do something (download / remove / update / etc.)

Would there be a way to schedule this checkin? Or make it run only once every x times? That might bridge the difference between no hangs and retaining all past downloads, and many hangs but clearing the downloads list.

jordanjay29 said:
Would there be a way to schedule this checkin? Or make it run only once every x times? That might bridge the difference between no hangs and retaining all past downloads, and many hangs but clearing the downloads list.
Click to expand...
Click to collapse
The framework could be modded for that, but thats a lot of work. Right now, the checkin code is a listener, and just wakes up for certain events (like an app install).

I THINK this could happen if one changes or deletes the APN of the phone.. for me it started to freeze the download after I completely closed the 3g/2g connection. So maybe google uses that connection in order to gether the data instead of the wifi. Can that be changed so that both use the wifi?

script to disable checkin service:
Code:
#!/bin/sh
su
if ! grep -q "^ro.config.nocheckin=" /system/build.prop; then
echo "Mounting system as read/write"
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
echo "Disabling Checkinservice"
echo "ro.config.nocheckin=1" >> /system/build.prop
echo "rebooting.."
reboot
else
echo "CheckinService already disabled"
fi

jordanjay29 said:
Would there be a way to schedule this checkin? Or make it run only once every x times? That might bridge the difference between no hangs and retaining all past downloads, and many hangs but clearing the downloads list.
Click to expand...
Click to collapse
I disassembled the classes.dex from the checkin.apk with baksmali and in the CheckinService.smali these fields are defined:
Code:
.field private static final CHECKIN_INTERVAL:J = 0x6ddd00L
.field private static final CHECKIN_INTERVAL_MAX:J = 0xa4cb800L
.field private static final CHECKIN_INTERVAL_MIN:J = 0x927c0L
Values in decimal(dont take the last character for conversion!). I think they should represent milliseconds:
0x6ddd00L: 7200000
0xa4cb800L: 172800000
0x927c0L: 600000
Maybe you can "schedule" the checkin service by changing these values, assemble the dex again with smali, replace the original classes.dex in the apk and push it back to the Phone.
Code:
adb remount
adb pull /system/app/checkin.apk .
Make a backup copy of the apk ;)
extract the classes.dex
java -jar -Xmx512m baksmali-0.94.jar -o ./checkin classes.dex
Edit the File
java -jar -Xmx512m smali-0.94.jar -o classes.dex ./checkin
Replace the classes dex in the pulled checkin.apk
adb push checkin.apk /system/app/checkin.apk
adb shell reboot
You can get smali and baksmali from here:
http://code.google.com/p/smali/

I was talking about the explicit checkin that happens after apps are installed, etc..

[EXPERIMENTAL]-PROJECT JIT-(Just in time)EXPERTS ONLY |Aug 13th|

New as of Saturday August 8th
I will update the files every time I find a problem​
WARNING PLEASE READ:
Project JIT is highly highly experimental! If you are to do this, MAKE A NANDROID BACKUP IN ROM MANAGER OR RECOVERY! There are always chances of something going wrong. I nor anyone else is responsible of what happens.
Experienced users please know the possible risks:
Boot Looping, requiring a restore
Constant FC's
Wiping everything
These are just the risks, please note it is not 100%​
JIT stands for Just in time compiler. It does not like Touchwiz, so download ADW.Launcher or LauncherPro before starting and set it as default.
This whole process is in ADB. If you dont know how, or what it is, DONT DO IT!
Things to do before you start:
-Download a different launcher than TouchWiz
-Make a backup in recovery or Rom Manager
-Did I mention DO A BACKUP!
-If you have an external SD card, pull it out
-Download the vmlibs file
What I expect you to know before you start:
-ADB
-What JIT is
-How this will effect the performance
-The risks
-How its not my fault if you screw your phone over
-How experimental this is
-How to make a nandroid backup
-How to make a nandroid restore
Remember, this is experimental and I cannot guarantee for it to completely work.
Download This- vmlibs.zip
Then follow these steps:
-Make a backup!!!
-Create 2 folders on your internal sdcard: “jit” & “dalbk”
-Extract the vmlibs.zip to the “jit” folder on your sdcard
-Using ADB pull your build.prop
Code:
adb remount
ADB pull /system/build.prop build.prop
-It will place the file in your c:/android/tools folder
-Edit this using notepad, text edit or similiar program.
-Add the following line to the end of the build.prop: dalvik.vm.execution-mode=int:jit
-Edit the following line:dalvik.vm.startheapsize=8m
to: dalvik.vm.startheapsize=12m
-Save the changes
-Push it back to your “jit” folder on the sdcard
Code:
ADB push build.prop /sdcard/jit/build.prop
This will back up your current files. So you can disable jit, but if your phone boot loops, thats why you have A BACKUP!
Code:
ADB shell
su
cp /system/build.prop /sdcard/dalbk/
cp /system/bin/dalvikvm /sdcard/dalbk/
cp /system/lib/libdvm.so /sdcard/dalbk/
cp /system/lib/libnativehelper.so /sdcard/dalbk/
This will enable jit on your phone.
Code:
cd /sdcard/jit/bin
cp -f dalvikvm /system/bin/
busybox chmod 755 /system/bin/dalvikvm
cd /sdcard/jit
cp -f libdvm.so /system/lib/
cp -f libnativehelper.so /system/lib/
cat build.prop >/system/build.prop
chmod 644 /system/lib/libdvm.so
chmod 644 /system/lib/libnativehelper.so
chmod 666 /system/build.prop
sync
reboot recovery
While in recovery, wipe the dalvik cache, this will prevent it from boot looping.
To Disable
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /sdcard/dalbk/
cat build.prop >/system/build.prop
cp -f dalvikvm /system/bin
busybox chmod 755 /system/bin/dalvikvm
cp -f libdvm.so /system/lib/
cp -f libnativehelper.so /system/lib/
chmod 644 /system/lib/libdvm.so
chmod 644 /system/lib/libnativehelper.so
chmod 666 /system/build.prop
sync
reboot
If that fails, that is why you have a backup. To restore, go to recovery, click on nandroid, and restore from your backup.

Reserved for future posting

Will this work with the sd card cache hack?
Sent from my SAMSUNG-SGH-I897 using XDA App

LGSilva said:
Will this work with the sd card cache hack?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
It didn't here. Not sure if that is due to other fsckup or the fact that I was running I9k rom with my kernel and sdcard hack...

Restoring to stock to give this a whirl

tommarow I will update the vmlibs file and see if it works better.
Oh, and tell me what your problems are

hansmrtn said:
tommarow I will update the vmlibs file and see if it works better.
Oh, and tell me what your problems are
Click to expand...
Click to collapse
Doesn't boot past the white at&t screen. Again, I was running I9k rom with custom kernel and ext hack, not exactly the cleanest test bed. Flashing stock to test now (can't get into recovery on this thing anyway it seems).

NukaCola said:
Doesn't boot past the white at&t screen. Again, I was running I9k rom with custom kernel and ext hack, not exactly the cleanest test bed. Flashing stock to test now (can't get into recovery on this thing anyway it seems).
Click to expand...
Click to collapse
Hold on. Before you do that, let me up the file.
EDIT:
Here is the updated one, its in the first post too
It should work better. I used it just now, and it works for me

hansmrtn said:
Hold on. Before you do that, let me up the file.
EDIT:
Here is the updated one, its in the first post too
It should work better. I used it just now, and it works for me
Click to expand...
Click to collapse
Too late
Same story with the stock rom and old file, just FYI. Flashing back and trying the new one.

NukaCola said:
Too late
Same story with the stock rom and old file, just FYI. Flashing back and trying the new one.
Click to expand...
Click to collapse
Yeah, thats why I had to fix some stuff lol. I noticed that it wouldnt go past the att screen. Now it should work correctly. The worst that could happen now is it boot loops on the Galaxy S screen

Haha I was just about to post the same problem, downloading new file and trying it again!

Zilch25 said:
Haha I was just about to post the same problem, downloading new file and trying it again!
Click to expand...
Click to collapse
Hey, when you edit the build.prop to add the dalvik vm line, can you look for the vm heap size and change it from 48 to 32? I am about to test doing that, and I would like more feedback

Doh, didn't read this until after applying it all... it's in the process of booting though- it got past the AT&T logo so that's progress!

Zilch25 said:
Doh, didn't read this until after applying it all... it's in the process of booting though- it got past the AT&T logo so that's progress!
Click to expand...
Click to collapse
Dont worry, I will try it

ATM I'm now stuck sitting at the GalaxyS logo, I'm going to give it a little more time, but I suspect it might be stuck.

Zilch25 said:
ATM I'm now stuck sitting at the GalaxyS logo, I'm going to give it a little more time, but I suspect it might be stuck.
Click to expand...
Click to collapse
Do you know how to run a logcat?
Its gonna take a while because its re writing the dalvik cache

That I do not, but I'm willing to try it if you can give me a quick crash course

Zilch25 said:
That I do not, but I'm willing to try it if you can give me a quick crash course
Click to expand...
Click to collapse
Well I am looking at my logcat now, and it is just repeating boot animation.
A logcat is useful, so how you do it is adb logcat.
I changed a couple things to test around with here is what I did-
I added all of this to the build.prop-
#JIT
dalvik.vm.execution-mode=int:jit
and changed:
dalvik.vm.heapsize=48m
to
dalvik.vm.heapsize=32m
Right now I am resorting to try the older vmlibs with the new settings

Ran logcat, it's also trapped at looping animation, and I didn't touch the heapsize
W/BootAnimationSEC< 2194: ms4631 - Repeat Loop Animation
Over and over and over, is there something else in the buffer you'd like me to look for?

Zilch25 said:
Ran logcat, it's also trapped at looping animation, and I didn't touch the heapsize
W/BootAnimationSEC< 2194: ms4631 - Repeat Loop Animation
Over and over and over, is there something else in the buffer you'd like me to look for?
Click to expand...
Click to collapse
No thanks for the feedback. Its only worked for me once, and then when I rebooted it got stuck in a boot loop.
Whats a device thats running android 2.1, and has a jit hack that is extremely similar to the Galaxy S series?

[Tutorial] Remove Default Bootanimations

If you want to remove the carrier branded boot and shutdown animations or the default Samsung animations that you see upon startup and shutdown, you can enter these commands via adb shell or in a terminal emulator on your Galaxy Tab. This code renames the files so that they are no longer accessed when the device is started while keeping them from auto-replicating. Deleting or moving the files with root explorer will not work because the files will be replaced almost immediately. You have to be rooted in order to gain the superuser privileges needed to edit the files in /system.
If you aren't already rooted, you can use z4root or superoneclick.
After that, if you choose, you can enter the commands through adb shell or through a terminal emulator available through the market. If you are not familiar with adb, you can get information on it here: basic adb/shell info
If you don't want to be tethered to the computer, you can take the terminal emulator route. I used "Android Terminal Emulator" by Jack Palevich. It is free on the market, but I'm sure that any of the other ones will work just as well.
If you have a Sprint Galaxy Tab and want to remove the Sprint animations/sounds at startup and shutdown, enter the following commands. Be careful, because you are editing /system files.
Code:
su
mount -o remount,rw /dev/mtdblock3 /system
mv /system/media/bootani.qmg /system/media/_bootani.qmg
mv /system/media/video/shutdown/shutdown.qmg /system/media/video/shutdown/_shutdown.qmg
mv /system/media/audio/ui/PowerOff.wav /system/media/audio/ui/_PowerOff.wav
mv /system/etc/PowerOn.snd /system/etc/_PowerOn.snd
mount -o remount,ro /dev/mtdblock3 /system
exit
For those of you with tabs other than the Sprint Tab, you may have to add the line:
Code:
mv /system/etc/PowerOn.wav /system/etc/_PowerOn.wav
This line goes after the command to move "PowerOn.snd"
These commands will leave the standard Samsung bootanimation. If you want to get rid of all bootanimations completely you can enter the following code:
Code:
su
mount -o remount,rw /dev/mtdblock3 /system
mv /system/media/bootani.qmg /system/media/_bootani.qmg
mv /system/media/samsungani.qmg /system/media/_samsungani.qmg
mv /system/media/video/shutdown/shutdown.qmg /system/media/video/shutdown/_shutdown.qmg
mv /system/media/audio/ui/PowerOff.wav /system/media/audio/ui/_PowerOff.wav
mv /system/etc/PowerOn.snd /system/etc/_PowerOn.snd
mount -o remount,ro /dev/mtdblock3 /system
exit
Now open your terminal or adb shell again.
Now enter:
Code:
su
cd /data/local
chmod 777 nobootani.sh
./nobootani.sh
exit
Now restart your tab. You will see that the shutdown animation is gone. When the tab restarts, the carrier/default animations are gone.

thanks
thanks a lot rkmj - I can confirm that this is working on my Sprint CDMA Galaxy Tab. The animations has been removed.
I just got it a couple of days back and I am in the process of removing all the junk from samsung and sprint without flashing a custom ROM cuz seriously there isnt any worth taking the risk.
I have cleaned almost all of them and with this fix my TAB just feels like totally unbranded now.
Next step is to make it faster without a custom ROM, ideas are welcome or maybe a safe list of services I can disable without breaking my tab.

Nice, thanks man
Sent from my GT-P1000 using XDA App

The at&t startup logo and sound is gone with overcome rom, but the t-mobile startup logo is still there.
So what will remove the t-mobile start screen?

I'm pretty sure this will remove the T-Mobile startup. Most of the carrier-branded startup routines are in the same locations. If this doesn't work though, you might check /system/media for a file called "bootanimation.zip" If that fails to produce, check /data/local for the same file. If you have that "bootanimstion.zip" file, you can either swap that bootabimation file for a custom one or get rid of it altogether.
Sent from my Samsung Galaxy Tab

rkmj said:
I'm pretty sure this will remove the T-Mobile startup. Most of the carrier-branded startup routines are in the same locations. If this doesn't work though, you might check /system/media for a file called "bootanimation.zip" If that fails to produce, check /data/local for the same file. If you have that "bootanimstion.zip" file, you can either swap that bootabimation file for a custom one or get rid of it altogether.
Sent from my Samsung Galaxy Tab
Click to expand...
Click to collapse
I have a tmobile galaxy tab, and the bootanimation.zip is just the startup movie that plays. Mine has been replaced with anouther. The white tmobile screen bugs the heck out of me, is not part of my custom boot animation but still shows. So does the samsung galaxy tab black screen.
Can I get rid of these two screens?
Sent from my GT-P1000 using XDA Premium App

There's an app called BAC or Boot Animation Changer that works with my rooted Moto Droid but not with my rooted Sprint Galaxy Tab. Would you have any idea whether after removing the boot animation if it will work? TIA
I'll test and see what results I get; just thought it might be good to have an informed opinion first. And many thanks for the post.

Thanks for this; just wanted to get rid of my carrier branding (Telstra) on my Galaxy Tab. I'm rather happy with the Samsung animation and even the on/off sounds.

good work
works beaut on Telstra 8.9.. give or take file names changes of course but the result is spot on...out with Tesltra crap...

rkmj said:
I
Now restart your tab. You will see that the shutdown animation is gone. When the tab restarts, the carrier/default animations are gone.
Click to expand...
Click to collapse
is that work other devices ? mean note 4 etc? and another cariror like sprint verizon etc?

Fix Mobile Data drain.

After 2 days of testing i think i have a clean solution to fix the mobile data drain by setting the preferred network mode to 1 (GSM only). No need to delete or rename anything. Just update the db that is already there .
You need a rooted device for this.
Extract the sqlite3.zip and push to your device with the following commands:
Code:
adb shell mount -o rw,remount /dev/block/mmcblk0p3 /system
adb push sqlite3 /system/bin
adb shell chmod 6755 /system/bin/sqlite3
adb shell
su (to gain root permissions)
sqlite3 /data/data/com.android.providers.settings/databases/settings.db 'update secure set value="1" where name="preferred_network_mode"'
reboot

I'll give this a try. Thanks
Edit: Is it possible I can do this on the device without adb? Adb doesn't want to detect my tablet with debugging enabled.

agentdax5 said:
I'll give this a try. Thanks
Edit: Is it possible I can do this on the device without adb? Adb doesn't want to detect my tablet with debugging enabled.
Click to expand...
Click to collapse
Sure, as long as you have some sort of terminal emulator installed.

agentdax5 said:
I'll give this a try. Thanks
Edit: Is it possible I can do this on the device without adb? Adb doesn't want to detect my tablet with debugging enabled.
Click to expand...
Click to collapse
with root explorer and a terminal app (eg connectbot) you can do it.

What exactly does this do? Is it the same result as renaming the phone and telephone apks?
Sent from my SPH-D700 using XDA App

Thanks! Mine is done. I'll report back later after I charge and give it a go.

mrkrabs said:
What exactly does this do? Is it the same result as renaming the phone and telephone apks?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
This updates the database configuration setting that causes the phone to not to look for 3G networks only 2G (GSM which includes GPRS and EDGE). I'll let the OP elaborate more, but this config change must reduce the battery usage by causing the phone and telephony services to chill out out a bit when in standy mode.

_motley said:
This updates the database configuration setting that causes the phone to not to look for 3G networks only 2G (GSM which includes GPRS and EDGE). I'll let the OP elaborate more, but this config change must reduce the battery usage by causing the phone and telephony services to chill out out a bit when in standy mode.
Click to expand...
Click to collapse
couldn't describe it better

2g = only poll cell if request is made that needs cell, 3g = poll all the time, which means that if you change to only 2g then it should not check for cell if you are in wifi range.
I am sure thats how the tech works if i remember my time at nokia right LOL

is there a post around here to explain how to get ADB working on this thing? i can ADB shell in but i get "operation not permitted" when i try to mount /system as r/w
(yes i'm rooted)
thanks guys
edit: i got permission to mount the /system as r/w but when i try to push the sqlite3 i get "Device not found"
i suppose i can give a little more info
i'm running windows 7 ultimate 64 bit with an administrator command prompt and the newest iconia a500 usb drivers from acer's support site and i have my SDK up to date

I did this and it doesn't seem to have a big effect. 2 hours on battery mostly in sleep, Display 33%, Cell 31%, Idle 18%, etc.

Richard:
Just out of curiosity (Yes, I fully acknowledge I should have done something like "select * from secure where name='preferred_network_mode'" beforehand! ) what is the default value of "preferred_network_mode" before this modification sets it to "1"?
-----
Doc Kinne
Somerville, MA

kinnerc said:
Richard:
Just out of curiosity (Yes, I fully acknowledge I should have done something like "select * from secure where name='preferred_network_mode'" beforehand! ) what is the default value of "preferred_network_mode" before this modification sets it to "1"?
-----
Doc Kinne
Somerville, MA
Click to expand...
Click to collapse
Default value is 0 (zero).

agentdax5 said:
I did this and it doesn't seem to have a big effect. 2 hours on battery mostly in sleep, Display 33%, Cell 31%, Idle 18%, etc.
Click to expand...
Click to collapse
It's not about what your stats say, but what your mA drain is. i loose only a couple of % in a night (sleep).

edgemaster191 said:
is there a post around here to explain how to get ADB working on this thing? i can ADB shell in but i get "operation not permitted" when i try to mount /system as r/w
(yes i'm rooted)
thanks guys
edit: i got permission to mount the /system as r/w but when i try to push the sqlite3 i get "Device not found"
i suppose i can give a little more info
i'm running windows 7 ultimate 64 bit with an administrator command prompt and the newest iconia a500 usb drivers from acer's support site and i have my SDK up to date
Click to expand...
Click to collapse
@edgemaster191
I am getting the same error; I also am rooted, running ADB from Windows 7 (and Mac OS X - tried both, same error). I also have latest drivers, and latest ADB.
I get "operation not permited error." Did you have any luck on getting further?

try this instead as a work around:
adb push sqlite3 /sdcard/sqlite3
adb shell
$ su
# mount -o remount,rw /system
# cp /sdcard/sqlite3 /system/bin/sqlite3
# chmod 6755 /system/bin/sqlite3
# sqlite3 /data/data/com.android.providers.settings/databases/settings.db 'update secure set value="1" where name="preferred_network_mode"'
# reboot
I've never been able to use root level adb cmnds with this device from outside the adb shell env, I think you need to update the default.prop, but this gets overwritten on reboot, I'm sure there is a way to fix this, and has proabably been discussed in another thread I've been too lazy to go find lol.

nycbjr said:
try this instead as a work around:
adb push sqlite3 /sdcard/sqlite3
adb shell
$ su
# mount -o remount,rw /system
# cp /sdcard/sqlite3 /system/bin/sqlite3
# chmod 6755 /system/bin/sqlite3
# sqlite3 /data/data/com.android.providers.settings/databases/settings.db 'update secure set value="1" where name="preferred_network_mode"'
# reboot
I've never been able to use root level adb cmnds with this device from outside the adb shell env, I think you need to update the default.prop, but this gets overwritten on reboot, I'm sure there is a way to fix this, and has proabably been discussed in another thread I've been too lazy to go find lol.
Click to expand...
Click to collapse
FTFY. 10char.

I am going to have to run some logs....just not seeing any drain that would justify doing this ....will definitely keep an eye out for it though

nycbjr said:
try this instead as a work around:
adb push sqlite3 /sdcard/sqlite3
adb shell
$ su
# mount -o remount,rw /system
# cp /sdcard/sqlite3 /system/sqlite3
# chmod 6755 /system/bin/sqlite3
# sqlite3 /data/data/com.android.providers.settings/databases/settings.db 'update secure set value="1" where name="preferred_network_mode"'
# reboot
I've never been able to use root level adb cmnds with this device from outside the adb shell env, I think you need to update the default.prop, but this gets overwritten on reboot, I'm sure there is a way to fix this, and has proabably been discussed in another thread I've been too lazy to go find lol.
Click to expand...
Click to collapse
such things will be able with kernels that overwrite the default.prop

matguard said:
@edgemaster191
I am getting the same error; I also am rooted, running ADB from Windows 7 (and Mac OS X - tried both, same error). I also have latest drivers, and latest ADB.
I get "operation not permited error." Did you have any luck on getting further?
Click to expand...
Click to collapse
i was able to finally get it, i copied the splite3 to /system/bin using root explorer, ran chmod through terminal emulator then ran the final command from adb shell.
not ideal but it worked

[Q] Editing Build.prop results in failure to boot [bricked]

As you may know, some Android games especially most Gameloft games are not compatible with the Kindle Fire. So in efforts to find a way to make certain Gameloft games to work such as Modern Combat 2 and Shrek Kart and others, I resorted to editing my build.prop in the systems folder to make my device compatible with the apps. So I copied the original build.prop file, renamed it, and saved it to my SD Card folder. I took the copy I made and I then replaced it with the build.prop from HTC Glacier. (I never knew what could possibly happen) So then to apply those settings you have to reboot the device. I rebooted the Kindle and now it won't boot up. It get's to the Kindle Fire screen when booting up but after several seconds it just shows a black screen. No physical damage has been incurred to it but I feel like my stupid mistake of modding the build.prop resulted in the Kindle Fire unable to boot up correctly. It also isn't recognized by the PC when I hook it up to a USB cable. So far I've found nothing that could help to solve this. I've seen a Factory Default Settings Cable which is a special cable to reverts the device to its factory default settings but I'm not too sure if that would work. I'm in desperate need of help as in I use my Kindle Fire for everyday work and play. Thanks.
EDIT: I've tried adb push and renaming and moving the build.prop into the /system/ but returns that it is a Read-File System Only. Also adb shell and su doesn't work as in it ends up with segmentation fault. I've tried to zergRush root it and permanently root it using KFU but it ends up with 'Cannot Access Package Manager. Is System running?' Also the mount -o rw,remount.....command doesn't work either as it says Permission Denied. All of this would be easy to accomplish if only it ADB allowed me to write onto the /system file.
EDIT**: The biggest issue I'm faced with is the permission settings that prevent my from editing anything. You cannot simply change it from RO to RW because apparently the ADB is not rooted. And I also can't root it because problems exist when accessing either Package Manager or Activity Manager. What I need is a way to access the /system files without a root (non-rooted). Either that or enable fastboot because I cannot access that either. On a reply on the second page is the resulting lines when changing bootmodes on the KFU.

Don't know how to fix your problem, but just wondering, did you just completely replace the kindle fire build.prop with the HTC glacier? Because you can't do that, it will, as you have learned, mess up your device.. Your supposed to edit the build.prop and just change a few things. Next time read up on the subject before deciding to mod the device you use everyday...

the cable you'r talking about is a "factory cable" it forces the kf to fastboot mode - it don't restore any settings !
you need fastboot mode to install fff (firefirefire - custom bootloader) and twrp (recovery)
do you allready have installed fff & twrp (or cwm) ?
if you have twrp installed and booted into then you have adb command available and can copy back the original build.prop

Did you remember to restore the read/write permissions to build.prop? It should be set to 644.

As already stated, your not supposed to replace the whole file, build.prop tells android which device you have, so now Android thought and configured itself to different hardware config. which is not available to it. Adb seems like the only option.

I should have really looked more into it before modifying the build.prop. I replaced the ENTIRE build prop with the build.prop of HTC Glacer. (I know, i know I was stupid) And referring to the factory cable, I don't think I'll resort to that: too time consuming. In regards to the last person that posted before me who said that my only option was ADB could you elaborate? Thanks for all your feedback.

gococogo321 said:
I should have really looked more into it before modifying the build.prop. I replaced the ENTIRE build prop with the build.prop of HTC Glacer. (I know, i know I was stupid) And referring to the factory cable, I don't think I'll resort to that: too time consuming. In regards to the last person that posted before me who said that my only option was ADB could you elaborate? Thanks for all your feedback.
Click to expand...
Click to collapse
Your going to have to use adb to basically remove the HTC Glacier build.prop and replace it with the original build.prop.
For example:
Adb remount <- allows you to mount system as rw
Adb pull /path-to-original/build.prop
Adb push build.prop /system
Adb shell chmod 644 /system/build.prop <- sets permissions to rwrr
Adb reboot
Sent from my Kindle Fire using xda premium

You dont have access to recovery? Either TWRP or CWM?

daggy1985 said:
Your going to have to use adb to basically remove the HTC Glacier build.prop and replace it with the original build.prop.
For example:
Adb remount <- allows you to mount system as rw
Adb pull /path-to-original/build.prop
Adb push build.prop /system
Adb shell chmod 644 /system/build.prop <- sets permissions to rwrr
Adb reboot
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
I tried doing that but it says something like Access Denied or Read-Only File System when i try to push the build.prop into it.

gococogo321 said:
I tried doing that but it says something like Access Denied or Read-Only File System when i try to push the build.prop into it.
Click to expand...
Click to collapse
Did you use the 'adb remount' command? Sometimes, when attempting to push a file to the system, I get the 'read-only file system' and I have to issue adb reboot followed by adb remount and then push the file again. It seems after a time the mount system as read write automatically goes back to read-only.
Sent from my ADR6400L using xda premium

Have you got TWRP or ClockworkMod?
Because you could flash a new rom then.

abd - root mode
Perhaps, running adb in root mode will
allow you to push the original build.prop
back. Then execute "adb remount / rw" to mount the
root directory as read/write. Hopefully you will be able to push
it then follow daggy1985's instructions.
* In Win 7, type "cmd " at the 'SEARCH/RUN' and hold
shift + ctrl while hitting 'Enter' to put yourself
in Admin mode which apparently makes adb work in root mode when you launch it.
* Xda-dev is the coolest site for Android that I have seen. Kudo's to everyone participating.

sum1nil said:
Perhaps, running adb in root mode will
allow you to push the original build.prop
back. Then execute "adb remount / rw" to mount the
root directory as read/write. Hopefully you will be able to push
it then follow daggy1985's instructions.
* In Win 7, type "cmd " at the 'SEARCH/RUN' and hold
shift + ctrl while hitting 'Enter' to put yourself
in Admin mode which apparently makes adb work in root mode when you launch it.
* Xda-dev is the coolest site for Android that I have seen. Kudo's to everyone participating.
Click to expand...
Click to collapse
Thanks but I have actually been running it from Administrator from the very beginning. I've used Kindle Fire Utility KFU and it says that ADB Server is Online and my Bootmode is 4000 but it says ADB root: No. And whenever I choose any bootmode whether it be Normal, Fastboot, or Recovery, it always shows this:
***********************************************
* Activating Normal (4000) *
***********************************************
Installing BurritoRoot, Courtesy of Jcase of TeamAndIRC!
1393 KB/s (1164225 bytes in 0.816s)
Error: Could not access the Package Manager. Is the system running?
Activating BurritoRoot...
Error type 2
android.util.AndroidException: Can't connect to activity manager; is the system
running?
Elevating the Shell...
* daemon not running. starting it now *
* daemon started successfully *
/data/local/tmp/BurritoRoot3.bin: permission denied
mount: Operation not permitted
mount: Operation not permitted
failed to copy 'files\rbfb' to '/system//rbfb': Read-only file system
Unable to chmod /system/rbfb: No such file or directory
Unable to chmod /system/rbfb: No such file or directory
mount: Operation not permitted
mount: Operation not permitted
***********************************************
* Root Activated *
***********************************************
The kindle is successfully running in root mode.
<idme> Invalid permission
reboot: Operation not permitted
Same goes for the Temp Burrito Root and installing FFF and TWRP. It always shows something about cannot access Package manager. I have no clue what the Package Manager even does but apparently I cannot find a solution to that.

I think you need to get a factory programming cable like we talked about on gtalk. I'm confident that will fix this.
Sent from my DROIDX using Tapatalk

I used android commander for windows, mounted system in TWRP and used android commander to copy a new working build.prop to the right place.
With a cable from my htc desire.

would make a little test:
issue "adb shell"
if you get a error message your up to a factory cable because the system shell is messed up and you have no possibility to get to fastboot mode to install fff & twrp
if you get a $ or # prompt you can resume and try "mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system" to mount system in read/write mode

daggy1985 said:
Your going to have to use adb to basically remove the HTC Glacier build.prop and replace it with the original build.prop.
For example:
Adb remount <- allows you to mount system as rw
Adb pull /path-to-original/build.prop
Adb push build.prop /system
Adb shell chmod 644 /system/build.prop <- sets permissions to rwrr
Adb reboot
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
hey, I've tried to remount my rooted galaxy y, fall in for same problem.but there show this message; "remount failed: Operation not permitted"
my device's usb debugging mode was off in last entire.
what I have to do now?

how did u edit build.prop in the first place if u don't have root and this might help
http://yaseminavcular.blogspot.com/2012/01/how-to-get-bricked-kindle-fire-back-to.html?m=1
Sent from my R800i using Tapatalk