Related
I want to root but want to be reassured I can unroot for warranty purposes.
In theory couldn't you just restore to factory settings?
Sent from my SGH-T959 using Tapatalk
JWhipple said:
In theory couldn't you just restore to factory settings?
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
Restoring factory settings does not remove root.
Just open terminal on your computer and type
Code:
adb shell
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
That'll remove the components that rooting installs.
*obviously to use adb shell you'll need the SDK installed
mmm easy
Ahh, easiest root/unroot makes me happy
Xyber3364 said:
Ahh, easiest root/unroot makes me happy
Click to expand...
Click to collapse
Yeah, the Vibrant is ridiculously simple so far.
bahnburner said:
Just open terminal on your computer and type
Code:
adb shell
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
That'll remove the components that rooting installs.
*obviously to use adb shell you'll need the SDK installed
Click to expand...
Click to collapse
could you just use the terminal on the phone ?
Yeah, I just don't like BetterTerminal. For some reason it always gives me hell, and it's the only terminal emulator that allows for an on screen keyboard.
To do this in terminal on the phone:
Code:
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
bahnburner said:
Yeah, I just don't like BetterTerminal. For some reason it always gives me hell, and it's the only terminal emulator that allows for an on screen keyboard.
To do this in terminal on the phone:
Code:
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
Click to expand...
Click to collapse
actually you can use any terminal and just hold the menu button to pull up the keyboard... it worked for anything i needed on the mt3g seems to still work on the vibrant but havent tested in terminal so whoever tries it out let us know
bahnburner said:
Yeah, I just don't like BetterTerminal. For some reason it always gives me hell, and it's the only terminal emulator that allows for an on screen keyboard.
To do this in terminal on the phone:
Code:
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
Click to expand...
Click to collapse
skater4690 said:
actually you can use any terminal and just hold the menu button to pull up the keyboard... it worked for anything i needed on the mt3g seems to still work on the vibrant but havent tested in terminal so whoever tries it out let us know
Click to expand...
Click to collapse
Sweet, thanks guys. Im gonna root now. Even if the terminal on the Phone dont work, atleast I can install the drivers and go the adb route.. AWESOME..
skater4690 said:
actually you can use any terminal and just hold the menu button to pull up the keyboard... it worked for anything i needed on the mt3g seems to still work on the vibrant but havent tested in terminal so whoever tries it out let us know
Click to expand...
Click to collapse
Wouldn't hard resetting put those back even after deleting?
ok my phone is having hardware issues home key and search buttons are not working so i have to return my phone problem is that im rooted. i just downloaded terminal emulator and am trying to put that code in but its not working any advice
mx4life921 said:
ok my phone is having hardware issues home key and search buttons are not working so i have to return my phone problem is that im rooted. i just downloaded terminal emulator and am trying to put that code in but its not working any advice
Click to expand...
Click to collapse
Try hard resetting to make sure?
only thing I suggest is install the drivers on your pc and the sdk and do it that way.. I'd link ya to the instructions but I'm still trying to find this instructions myself....
Anyone got a link?
where can I find the terminal On my pc?
temperbad said:
where can I find the terminal On my pc?
Click to expand...
Click to collapse
press "Control+r"
type "cmd"
press enter
bahnburner said:
Yeah, I just don't like BetterTerminal. For some reason it always gives me hell, and it's the only terminal emulator that allows for an on screen keyboard.
To do this in terminal on the phone:
Code:
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
Click to expand...
Click to collapse
Good 'ol "Terminal Emulator" has a soft keyboard toggle as well, works just fine.
My only gripe is the Swype backspace doesn't work right in any of the terminal applications including connectbot so you have to change your input method first if you have any desire to use the backspace key... Original android one works ok.
bahnburner said:
press "Control+r"
type "cmd"
press enter
Click to expand...
Click to collapse
Ok so after opening that it and when I press SU it errors, says superuser error. Do I got to get it to recognize my device first somehow? I got the drivers installed and in cmd it recognizes my device... What does the line you enter the command got to say when I enter in the commands?
Quick question. I am rooted and going to exchange under warranty. Can I do a factory data reset without causing any problems? I thought I read where someone tried when they were rooted and it wouldnt boot after. Thanks
temperbad said:
Ok so after opening that it and when I press SU it errors, says superuser error. Do I got to get it to recognize my device first somehow? I got the drivers installed and in cmd it recognizes my device... What does the line you enter the command got to say when I enter in the commands?
Click to expand...
Click to collapse
In Windows it should look like this:
Code:
C:\Users\Bahnburner.MacbookPro>adb shell
$su
#
it may also include this, but don't worry about it if it doesn't:
Code:
* daemon not running. starting it now *
* daemon started successfully *
dashed said:
Quick question. I am rooted and going to exchange under warranty. Can I do a factory data reset without causing any problems? I thought I read where someone tried when they were rooted and it wouldnt boot after. Thanks
Click to expand...
Click to collapse
I have done a factory reset to solve a browser issue and had absolutely no problems, however, the phone will remain rooted. You will still have to manually delete Superuser.apk, su and busybox.
hopefully this will help when people want to unroot if the update won't work without unroot
ONLY WORKS WITH ANDROID 2.2 (FROYO)
For those of you that don't know, Google released a new Voice Search that allows "actions". For more info go Here.
First off, I wanna thank Tsenru, klinster, devlogic, BinaryMan, and Synchromatic @ the CM forum for all the info.
This is instructions for ubuntu so make the proper adjustments for windows if needed.
From ADB
Code:
adb pull /system/app ~/Desktop/app/
adb remount
adb shell rm -f /system/app/VoiceSearch.apk
adb shell pm uninstall com.google.android.voicesearch
adb shell rm -f /system/app/GoogleQuickSearchBox.apk
adb shell pm uninstall com.google.android.googlequicksearchbox
Once this is done you can search market for "voice search" and "google search" then after they're installed, reboot.
Now for the next step.
If the search hard key doesn't bring up the quick search box (keyboard input), do this.
Code:
adb remount
adb shell ln -s /data/app/com.google.android.googlequicksearchbox-1.apk /system/app/com.google.android.googlequicksearchbox.apk
adb reboot
Now all should work!
I had a wierd name for quick search box (com.google.android.googlequicksearchbox-1) so keep that in mind if you have any issues.
Now enjoy you fancy new voice search!
tried everyone's suggestions so far, with your suggestions I get:
rm failed for -f, Read-only file system
Worked for me, thanks!
beyondinferno said:
ONLY WORKS WITH ANDROID 2.2 (FROYO)
Now for the next step.
If the search hard key doesn't bring up the quick search box (keyboard input), do this.
Code:
adb remount
adb shell mv /data/app/com.google.android.googlequicksearchbox /system/app
adb reboot
Now all should work!
I had a wierd name for quick search box (com.google.android.googlequicksearchbox-1) so keep that in mind if you have any issues.
Now enjoy you fancy new voice search!
Click to expand...
Click to collapse
Rather then using the command adb shell mv /data/app/com.google.android.googlequicksearchbox /system/app
I suggest the command ln -s /data/app/com.google.android.googlequicksearchbox-1.apk /system/app/com.google.android.googlequicksearchbox.apk
ln -s creates a symbolic link to the file rather then moving the file. It keeps the google search file where the installer put it. If you move the file are you causing an issue in the future when the next upgrade comes around?
mmace said:
tried everyone's suggestions so far, with your suggestions I get:
rm failed for -f, Read-only file system
Click to expand...
Click to collapse
adb remount first... and when using rm try busybox...
busybox rm <<file>>
painter_ said:
Rather then using the command adb shell mv /data/app/com.google.android.googlequicksearchbox /system/app
I suggest the command ln -s /data/app/com.google.android.googlequicksearchbox-1.apk /system/app/com.google.android.googlequicksearchbox.apk
ln -s creates a symbolic link to the file rather then moving the file. It keeps the google search file where the installer put it. If you move the file are you causing an issue in the future when the next upgrade comes around?
Click to expand...
Click to collapse
Thanks for the tip!
Changing how to now.
Can't wait to try this tonight.
Sent from my HERO200 using XDA App
Worked great! thank you!
This worked for me as well. Thanks.
Not having much luck reactivating the search button.
I can confirm that it got the job done cause when I tried again, it popped up an error that the file already exists, so it succeeded in creating the link... any suggestions?
Just tried it, works great. Thanks!
what does adb shell PM uninstall do as opposed to adb shell uninstall
If you have TB, uninstall voice search and google search from backup/restore, then reboot phone and go to market install both, worked for me
andygu3 said:
If you have TB, uninstall voice search and google search from backup/restore, then reboot phone and go to market install both, worked for me
Click to expand...
Click to collapse
thanks that worked and it was way easier than adb.
I'd love to have this feature, but I get "failure" when I enter the adb shell pm uninstall com.google.android.voicesearch command. I can't figure out what I'm doing wrong, except that I have no idea what the difference between Ubuntu and Windows commands are.
Thanks for all the hard work. Any help is greatly appreciated.`
EDITED: I got it working. Not sure how. Even though I got a "failure" during the adb uninstall, the old voice search appears to have uninstalled already. Went to the market and downloaded the new app and it works!
Perilousp69 said:
I'd love to have this feature, but I get "failure" when I enter the adb shell pm uninstall com.google.android.voicesearch command. I can't figure out what I'm doing wrong, except that I have no idea what the difference between Ubuntu and Windows commands are.
Thanks for all the hard work. Any help is greatly appreciated.`
Click to expand...
Click to collapse
I should add I'm running FROYO 2.1, vanilla based on Cynogen's Aug. 13 mod
Working!
10chars
DirtyShroomz said:
Working!
10chars
Click to expand...
Click to collapse
Can you tell me how you did it? I noticed you had problems earlier.
Perilousp69 said:
Can you tell me how you did it? I noticed you had problems earlier.
Click to expand...
Click to collapse
Used SUFBS (or any file explorer). Went to system/app and deleted voicesearch.apk, rebooted, went to market and downloaded voice search
Sorry for bumping the old topic, but does anyone know the difference
between:
com.google.android.voicesearch.x and
com.google.android.voicesearch ??
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
Hey gius Im trying to reboot via terminal but I cant seem to get it to work. Keep getting "Nor premited!" error.
I tried with both commands and am using a rooted G2 with stock rom.
su reboot - same error
su reboot now- same error.
any ideas? I know there are apps to do it but why is it not working via terminal?
Any reason why you can't just hold the button in and press reboot?
$ su -
# shutdown -r now
it shoulda outta do it then
for just turning off:
# shutdown -h now
ohgood said:
$ su -
# shutdown -r now
it shoulda outta do it then
for just turning off:
# shutdown -h now
Click to expand...
Click to collapse
Hmm Tried that right now and it says shutdown: not found.
I'm getting the same error! I only tried terminal when Gscript Lite gave me a "not permited". Don't know if it's related, but terminal always starts with $ rather than #. The weirdest part is that it DID work through ADB.
I'm S-OFF, root verified. Has anyone else seen this? I've been searching the forums for a while now...
Try
$ su
# busybox killall system_server
Sent from my HTC Vision using Tapatalk
I get busybox: not found, but since I initially thought it was a busybox issue, I have already updated busybox. Per Titanium Backup, I have version 1.18.4-Titanium. Could it be the titanium busybox?
PanCubano said:
Try
$ su
# busybox killall system_server
Sent from my HTC Vision using Tapatalk
Click to expand...
Click to collapse
Having a similar problem with rebooting from terminal "not permitted", I am using Virtuous Unity,and my phone is rooted etc,anybody having any joy getting reboot from terminal working?double checked busybox permissions and are RWX so whats going on???????????????????
Ok restored my nandroid backup of CM7 and reboot from terminal works so for the problem is connected to Virtuous Unity.
got it ! command is:
$su
#reboot -f
hay presto!!!!!!!
EDIT BUT when using a gscripts reboot doesnt work???????????
I have to use the command busybox killall system_server in the script????
I dont get it,what is the problem !!!!!!!!!!!!!!!!
xsteven77x said:
Any reason why you can't just hold the button in and press reboot?
Click to expand...
Click to collapse
This.
Sent from Space using Tapatalk Pro
I know I could, just trying to understand the android system,how it works and why the reboot command works on CM 7 but not on Virtuous Unity, the search for a solution continues...........................
bombadier said:
I know I could, just trying to understand the android system,how it works and why the reboot command works on CM 7 but not on Virtuous Unity, the search for a solution continues...........................
Click to expand...
Click to collapse
I had the same problem on rooted stock, and it has since gone away since I put on CM7. The reason is that it is not just reboot that didn't work. Almost no scripts would run either, and those can be quite helpful. I believe it's a symptom of something larger, but I can't quite place my finger on what.
mjasmin said:
I had the same problem on rooted stock, and it has since gone away since I put on CM7. The reason is that it is not just reboot that didn't work. Almost no scripts would run either, and those can be quite helpful. I believe it's a symptom of something larger, but I can't quite place my finger on what.
Click to expand...
Click to collapse
I can get reboot -f which works but I have to use busybox killall_server to get it work from a script,have tried a few things but literature on the subject is pretty sparse,its not so important but would still like to understand the whole process, but I seem to be in the minority trying to solve this.......
Why I have to use reboot -f on Unity where reboot will do on CM is a mystery,have found a file that seems to define functions on Unity(virtuous-functions.sh), have tried adding REBOOT="$BUSYBOX reboot" to this but doesn't help.
reboot -f it is then!
I wanted to start an official thread on performing build.prop edits on KFHD since no one has of yet. I have tinkered for several hours yesterday trying to get one that allows Google Play apps to install that show "unsupported device". I have had zero luck unfortunately, and am hoping some others want to take up the challenge and find a solution.
I suggest you get busybox before attempting this, it makes copying files easier. Get it in the GooglePlay store:
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
Make sure you back up your file first!!! I did these steps:
Code:
# adb shell
# su
# mount -o remount,rw /system
# cp /system/build.prop /system/build.prop.orig (cp comes with busybox see link above)
# cp /system/build.prop /sdcard/build.prop.orig
# exit
NOTE: If you didn't install busybox, then you can do the cp commands as below:
Code:
# cat /system/build.prop.orig > /system/build.prop
Word of caution, I have managed to get my Kindle into a boot loop several times through this, but fortunately have been able to recover (details below). I cannot guarantee that you won't damage your Kindle in the process, and prevent it from booting.
I am also attaching a copy of the stock build.prop in case you manage to damage yours. I can't guarantee you will be able to put it back if you get in a boot loop, but you should be able to at minimum "vi" the existing one and manually enter everything to fix you up.
Here are my recovery steps if you manage to get stuck in a boot loop (I notice this happens a lot if you modify the ro.product.board entry). All credit for saving my bacon (and showing us how to root) goes to jcase and sparkym3. One note, you cannot use "su" if you get in this state, you get some exception and the binary errors out about you not being fully booted.
Code:
# adb shell
# echo 'ro.kernel.qemu=1' > /data/local.prop
# exit
# adb reboot
# adb shell
# mount -o remount,rw /system
# cp /system/build.prop.orig /system/build.prop (cp comes with busybox see link above)
# rm /data/local.prop
# exit
# adb reboot
Your device "should" boot after this.
nvrmore100 said:
I wanted to start an official thread on performing build.prop edits on KFHD since no one has of yet. I have tinkered for several hours yesterday trying to get one that allows Google Play apps to install that show "unsupported device". I have had zero luck unfortunately, and am hoping some others want to take up the challenge and find a solution.
I suggest you get busybox before attempting this, it makes copying files easier. Get it in the GooglePlay store:
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
Make sure you back up your file first!!! I did these steps:
Code:
# adb shell
# su
# mount -o remount,rw /system
# cp /system/build.prop /system/build.prop.orig (cp comes with busybox see link above)
# cp /system/build.prop /sdcard/build.prop.orig
# exit
NOTE: If you didn't install busybox, then you can do the cp commands as below:
Code:
# cat /system/build.prop.orig > /system/build.prop
Word of caution, I have managed to get my Kindle into a boot loop several times through this, but fortunately have been able to recover (details below). I cannot guarantee that you won't damage your Kindle in the process, and prevent it from booting.
I am also attaching a copy of the stock build.prop in case you manage to damage yours. I can't guarantee you will be able to put it back if you get in a boot loop, but you should be able to at minimum "vi" the existing one and manually enter everything to fix you up.
Here are my recovery steps if you manage to get stuck in a boot loop (I notice this happens a lot if you modify the ro.product.board entry). All credit for saving my bacon (and showing us how to root) goes to jcase and sparkym3. One note, you cannot use "su" if you get in this state, you get some exception and the binary errors out about you not being fully booted.
Code:
# adb shell
# echo 'ro.kernel.qemu=1' > /data/local.prop
# exit
# adb reboot
# adb shell
# mount -o remount,rw /system
# cp /system/build.prop.orig /system/build.prop (cp comes with busybox see link above)
# rm /data/local.prop
# exit
# adb reboot
Your device "should" boot after this.
Click to expand...
Click to collapse
Do you means that if we get stuck in the boot loop, we can try the third code to recovery?
It should let you get back to the device if you are in a loop like you would experience with the build.prop edit. Meaning you can still use adb shell to access the system even though its not entirely booted up, and you can't use SU.
No one willing to try more build.prop edits? I spent another few hours at this, I'm still no farther. I am able to trick play.google.com into thinking I have a different system (Nexus S in this case) but the play store on the kindle doesn't allow me to install several apps. If I tell it to download via the web site, it does not push them down to my device. Also, if I try to do a combination of website / play store app at various stages of the process, I can get all the way to install portion and then it tells me its not compatible...
Does anyone ever try to change DPI to 160 or lower?
Sent from my KFHD rooted
Yes, with a lower dpi, the normal android lock screen returns, however, the keyboard gets seventy messed up and becomes unusable. This was at 130 dpi.
Sent from my KFTT using XDA Premium HD app
Has any progress been made on installing incompatible apps from the play store?
Sent from my KFTT using xda app-developers app
madddoggj said:
Has any progress been made on installing incompatible apps from the play store?
Sent from my KFTT using xda app-developers app
Click to expand...
Click to collapse
use market unlocker.its ok.
madddoggj said:
Has any progress been made on installing incompatible apps from the play store?
Sent from my KFTT using xda app-developers app
Click to expand...
Click to collapse
Yes, when Google says no, I go look for the apk and download it anyways. So far nothing has crashed. But I try to stick with things for ICS.
I messed with the ro.product.board entry... and now when reboot it got stuck at "Kindle is Upgrading... Starting application..."
Tried adb but device not attacked.
Is there a way to boot it up again?
dexd, http://forum.xda-developers.com/showthread.php?t=1930656
nvrmore100 said:
Here are my recovery steps if you manage to get stuck in a boot loop (I notice this happens a lot if you modify the ro.product.board entry). All credit for saving my bacon (and showing us how to root) goes to jcase and sparkym3. One note, you cannot use "su" if you get in this state, you get some exception and the binary errors out about you not being fully booted.
Code:
# adb shell
# echo 'ro.kernel.qemu=1' > /data/local.prop
# exit
# adb reboot
# adb shell
# mount -o remount,rw /system
# cp /system/build.prop.orig /system/build.prop (cp comes with busybox see link above)
# rm /data/local.prop
# exit
# adb reboot
Your device "should" boot after this.
Click to expand...
Click to collapse
Worked like a charm on 7.2.1 jcase and sparkym3 are brilliant. I have no idea how this code works or what makes sense about it, but it's fantastic. Also, since this code lets you copy files without root, could this be another method for rooting my device?
Yuretz said:
dexd, http://forum.xda-developers.com/showthread.php?t=1930656
Click to expand...
Click to collapse
I followed the guide and got myself this factory cable and I can boot it up again
My build.prop
Quadrant 2450
No need to block accelerometer in games
Fast worm program start
Suddenly deleted strings about fast restart and unlock, will add tomorrow. Issue's is cold start takes a sec but it doesnt bother
Thank you for your post, this thread may be quite useful for who has had a bricked device.
Yuretz said:
My build.prop
Quadrant 2450
No need to block accelerometer in games
Fast worm program start
Suddenly deleted strings about fast restart and unlock, will add tomorrow. Issue's is cold start takes a sec but it doesnt bother
Click to expand...
Click to collapse
I don't know what the other two things mean, but the "No need to block accelerometer in games" is something I need! Are you sing a Kindle Fire HD 7"? If so, I'm definitely doing this!
macravin said:
I don't know what the other two things mean, but the "No need to block accelerometer in games" is something I need! Are you sing a Kindle Fire HD 7"? If so, I'm definitely doing this!
Click to expand...
Click to collapse
Yes, I'm KFHD 7 user. DPI 160!!! Stock launcher won't be usable.. If U have so, need to change string about dpi to 260, if i'm not mistaken.
On ADW Launcher or any other sideloaded everything work like a charm.. APPS switch to TABLET mode if support
Yuretz said:
Yes, I'm KFHD 7 user. DPI 160!!! Stock launcher won't be usable.. If U have so, need to change string about dpi to 260, if i'm not mistaken.
On ADW Launcher or any other sideloaded everything work like a charm.. APPS switch to TABLET mode if support
Click to expand...
Click to collapse
So you can download apps from marked which are marked as "incompatible device" with stock build.prop ? Thank you for your answer! :fingers-crossed:
Yuretz said:
Yes, I'm KFHD 7 user. DPI 160!!! Stock launcher won't be usable.. If U have so, need to change string about dpi to 260, if i'm not mistaken.
On ADW Launcher or any other sideloaded everything work like a charm.. APPS switch to TABLET mode if support
Click to expand...
Click to collapse
I did this, but the dpi made my keyboard unuseable (the keyboard doesn't fit on screen idk why it became big when everything else became small)... does anyone know of a fix for this? That would be really great!
Does this work on Kindle Fire HD 8.9?
Yuretz said:
My build.prop
Quadrant 2450
No need to block accelerometer in games
Fast worm program start
Suddenly deleted strings about fast restart and unlock, will add tomorrow. Issue's is cold start takes a sec but it doesnt bother
Click to expand...
Click to collapse
Ok I am very excited.I saw this possible solution to my problem, as I would like to download NBA Jam for android (that I modded with Jordan in it that I have working on my rooted Kindle Fire with CM10 linaro on it, but what I wonder is if this will work for a rooted Kindle Fire HD 8.9 as well as a Kindle Fire HD 7? Thank you in advance.