Database Users

MT3G "SU" Issue. Need help.....

Hello Guys,
I'm in great trouble with my MT3G. Last couple of days i'm facing "Superuser Permission" issue with any rooted ROM. After installing the rom with any installed root based software "SU" is just black screen, nothing happens. I'm running Amon Ra's 1.2.3 MT3G version. I've tried formatting the sd as FAT32 and then using the recovery utility to make Fat32/ext2/swap and also tried the built in fix in AR's 1.2.3 looks like nothing is fixing this issue.
Also i've tried clearing the cache through settings>apps>manage apps>su and it didn't help either.Plzzzzzzzzzzz need some help asap.Thanks

do you have any apps that require superuser permissions? because if you dont, then it kinda just chills there, and it SHOULD show a black screen if nothing is accessing those secret files.
to see if its working, go to terminal and type in "su" and hit enter. if nothing happens...then yeah, somthing is wrong. if nothing happens, runn "fix_permissions" in adb shell

oshizzle1991 said:
do you have any apps that require superuser permissions? because if you dont, then it kinda just chills there, and it SHOULD show a black screen if nothing is accessing those secret files.
to see if its working, go to terminal and type in "su" and hit enter. if nothing happens...then yeah, somthing is wrong. if nothing happens, runn "fix_permissions" in adb shell
Click to expand...
Click to collapse
Thanks for the reply. i'm trying to use "setCPU" and "Wifi Tether" and still getting the black screen on "su".I've tried to go through the terminal and after the # su nothing happens.Tried the adb "fix" also but no luck. No idea whats going on.

i suggest removing the su app and then installing it from the market. you can remove it via adb/terminal. i dont remember the code to remove stuff, search around the dream forums for that answer.

Make sure usb debugging is enabled.

[SOLVED] Not all apps showing in Market on 1.6 roms

The problem: After installing AOSP 1.6, I noticed protected apps weren't showing in Market, including some I had bought in 1.5. I restored my 1.5 backup and found the same thing. Instructions on this thread (http://forum.xda-developers.com/showthread.php?t=605028) were able to get my apps back in 1.5, but upon reflashing 1.6 I was back to square one.
Update:
----------
I started fresh to test things out, trying both AOSP 1.6 and gbhil's modded AOSP 1.6. I wiped, then flashed and booted, then flashed gbits and booted, then setup my google creds, then rebooted and flashed superuser, then installed busybox then rebooted.
That's my baseline. From that point, I observed:
- Market showed a limited amount of apps. One time My Downloads had all my apps, but upon trying to install one I got a "Download unsuccessful" error. I'm assuming when the download was initiated my fingerprint was sent out, and then Market filtered My Downloads to reflect that unofficial fingerprint. Meaning, most apps were missing again.
- I updated build.prop with the fingerprint from stock 1.5 (see below for instructions). I downloaded a random app (Twidroid Free) so it'd send out my "new" fingerprint, and thus remove the filter limiting my apps. Soon after all apps were appearing again. Be patient here, sometimes it doesn't update instantly. One gave a download error, but trying to install it again solved it.
- Just to test, I edited my build.prop back to whatever was default with the 1.6 rom I was using, then rebooted. My Downloads still showed everything, but as soon as I installed any random app, that unofficial fingerprint was sent out and my apps were limited again.
I don't know enough about Market to know the repercussions of what I did - does it think I have 1.5, so will it be showing me only 1.5 compatible apps? Either way, I'd rather have access to all 1.5 apps than only some 1.6 apps. And aren't most (not all, but most) 1.5 apps backwards compatible with 1.6 anyway? So the only real downside is 1.6+ apps will be hidden. If someone has the fingerprint for an "official" 1.6 device, they could change their fingerprint to that and conceivably have the best of both worlds (protected apps AND 1.6+ apps).
How To Change Your Build Fingerprint:
--------------------------------------------
1. Connect your phone.
2. Pull /system/build.prop | For Mac users: ./adb pull /system/build.prop ./
3. Using your favorite editor, find the line that starts with ro.build.fingerprint and put a # in front of it.
4. On a new line, put: ro.build.fingerprint=sprint/htc_heroc/heroc/heroc:1.5/CUPCAKE/85027:user/release-keys
5. Save the file.
6. Remount the filesystem as read/write | For Mac users: ./adb remount
7. Log into the phone | For Mac users: ./adb shell
8. Exit the shell by typing: exit
9. Now push the file back. | For Mac users: ./adb push ./build.prop /system/build.prop
10. Reboot | For Mac users: ./adb reboot
11. Go to Market, and install something to send out the new fingerprint.
12. Within a few minutes you should see all apps. If not, try rebooting. If still not, try clearing Market's cache (Settings->Applications->Market->Clear Cache)
--------------------------------------------
Hope this helps someone.
-TM

This affects the MoDaCo rom I installed, and the AOSP 1.6 rom I was playing around with. Things like WeatherBug Elite, and tons of other stuff are hidden from the Market. In the case of MoDaCo, which I installed overtop my existing 1.5 stock (after backing up of course) the apps ran fine since they were grandfathered in from the stock rom, but still weren't listed in the marketplace. I'd really appreciate any help, as these speedy roms are useless if I can't run any of my apps on them.

search is king
this should help you
Link here

This reply isn't valid anymore and may be deleted.

Can you please post the code for this. I'm having a hard time getting this to work. Thanks

dathryl said:
Can you please post the code for this. I'm having a hard time getting this to work. Thanks
Click to expand...
Click to collapse
Code for what? What problems are you having?

Newbie question, how do you "pull" the file. I'm on shell but don't know what to input in order to edit the file.

PRGUY85 said:
Newbie question, how do you "pull" the file. I'm on shell but don't know what to input in order to edit the file.
Click to expand...
Click to collapse
You need to have ADB installed (which you do if you've rooted your phone, as ADB is required to do so). So you'd need to go into a command prompt (Windows) or Terminal (Mac), navigate to your adb/tools directory (that has adb.exe in it) and type "adb pull fileonyourphone fileonyourcomputer". Obviously replace fileonyourcomputer with the actual paths and filenames of what you're pushing/pulling. When you push the file back to the Hero, you swap the syntax, so it'd be "adb push fileonyourcomputer fileonyourphone".

OK, sorry again for noobness...
He says adb remount as read write, how do I do that?
He says log in to the phone...how do I do that on the shell?

So just to be sure, this fix will allow me to download the apps that I just can't find on the market that my friends with stock Heros can, right?
Someone recommended a new twitter client (twicca) but I couldn't open it on the market and I'm assuming it's because I'm running AOSP 1.6.
Thanks.

I just did this, and it seemed to work, but when Weatherbug Elite was downloading the phone went into the "Android" boot screen and just looped it over and over. After a battery pull it still won't boot up, and it keeps getting stuck at the boot screen. Is there anyway to fix this?

sure is nice to have sufbs back.
thanks for this.

Thanks, worked like a charm.

Simtook kit removing

Hi guys/girls
Just rooted and installed CM7 however the build has the simtool kit in it which puts a icon in my top bar that drives me nuts (the icon has no info in the drop down) I tried to force stop and uninstall however does not give an option for that, can anyone tell me how to remove it via sdk
Cheers

adb remount
adb shell rm /system/app/Stk.apk

Can i do that by the terminal emulator on the phone ? (at work at the moment and dont have the sdk installed).
thanks for your help as well
Im learning but its taking a little time to get my head around things lol

You can also use Titanium Backup. (free version in market).
Sent from my Nexus One

SiNJiN76 said:
You can also use Titanium Backup. (free version in market).
Sent from my Nexus One
Click to expand...
Click to collapse
Cheers, already have that installed and paid for it as well, did not you can uninstall from it
tool kit gone now

[Q] I need help with Ice cream Sandwich loop

I updated my new kindle fire, then rootet it successfully.
After that i installed the Ice Cream Sandwich 4.0 and made it the default launcher.
But this failed, when i now start the kindle fire i get caught into the loop of this error:
! Sorry
The application Ice Cream Sandwich 4.0 (process androd.process.acore) has stopped unexpectedly. Please try again. [Button: force close]
Which i can press, and then the loop starts again.
I am a noob, so please how do i get rid of this launcher ? I could need a reset or factory default or whatever, but the normal ways dont work, because i cant reach them anymore. Any Ideas how to fix this ?
/edit: I have access to my device with adb shell. so i think i can somehow change the default launcher, if someone tells me which file to change because i have no idea which is the right.

You need to figure out what the package name is "adb shell pm list packages" without quotes. Once you figure out what the package name is you can "adb uninstall name.of.package"

Hard reset it with power button.
Guide - How to hard reset Kindle Fire?

Fyi.....I just tried the hold power for 20 seconds hard reset, and it doesn't work......
Sent from my Kindle Fire using Tapatalk

I've had this problem with a different launcher and posted my solution here : http://forum.xda-developers.com/showthread.php?t=1361138
... don't worry... you can fix it... all you need to do is install another launcher or uninstall the ICS launcher... and you may be wondering how you can do that if you can't get to a usable screen.
You can still install/uninstall apps using the adb service you used while rooting. FoxDog66 mentioned how to do this if you know the package name. In my case, I could not find out the package name of the offending package, so what I did was install another launcher via the same method I installed my google apps to the sys/apps folder. with another launcher installed, I get a choice again which launcher should run when turning on.
I suggest you try foxdog's suggestion first, but if you can not find the package name then get another launcher.apk install file like GOlauncher or ADW Launcher and push or install that app the way you see google apps being pushed via the following method:
Download GOlauncher http://61.145.124.93/soft/3GHeart/golauncher/v2.68/go_launcher_ex_v2.68.apk
now make it a system app:
adb remount
adb push c:\androidApps\go_launcher_ex_v2.68.apk /system/app/go_launcher_ex_v2.68.apk
adb reboot
After reboot you should be able to choose your launcher of choice. Don't make anything default until you know you like it!!!
Now that GO Launcher just installed via my method makes it a system app. You can't uninstall system apps in the normal way, so use a program like Titanium Backup to make that pushed launcher app a NON-system app (moves it and makes it easy to uninstall the way other apps do). Titanium Backup is just a great program to have if rooted.
Good Luck.

how to uninstall buggy launcher which is set to default
Thanks for helping me.
Yes thats exactly my problem and i am now trying to follow your instructions.
The hardware reset works, but it will not get rid of the launcher.
So i try to find out the right application name to uninstall it. But *blush* i have not idea which is the right name and i dont want to uninstall something randomly.
I have some very basic skills with linux which i uses 10 years ago or so, so i am able to make a list which i attached here.
OK, i am now trying to do this:
adb remount
adb push c:\androidApps\go_launcher_ex_v2.68.apk /system/app/go_launcher_ex_v2.68.apk
adb reboot
but "adb remount" gives me back a
remount failed: Operation not permitted
I need to look closer how to install and uninstall packages now.
/edit: what i can do is:
adb shell
$
su
#
so this looks like to me that i am superuser. I also see the file system, and i can do some stuff with this shell, but its very limited because this shell is different from the shells i knew long time ago.
/edit:
ok, found something:
i am in the file system in
/data/app
here i have 3 apk:
net.adisasta.androxplorer-1.apk
mobi.SyndicateApps.ICSv2-1.apk
mobi.SyndicateApps.ICS-1.apk
and i think this is the package i installed.
/last edit:
OK folks. SUCCESS..
I just did adb uninstall mobi.SyndicateApps.ICSv2 and i immidiatly got success and got rid of the fail launcher.
VERY NICE and a warm THANK YOU for helping me.
I think i will try more now -- hehe.
Just tasted some blood now. Probably i will be soon here with the next problem. But i really appriciate your help. Hopefull soon i will be more into it and be able to help other noobs, too.
Also if someone needs german help because of language barrier, i can help translating.
Best Regards
Usurpine

Glad you got it fixed
A few tips.... adb remount just remount's the system partition read-write which isn't needed unless the app is installed to /system/app (it also does not work. It does work with doomlord's kernel, i think because of the insecure ramdisk)
The "./" part of your command just means to run in the current directory, if you have fastboot or adb in path then you don't need that part and you can also run the commands from any directory. if you don't have them in path then you would need to have what you wanted to flash, boot, whatever in the same directory as fastboot/adb. To check if something is in path (let's say fastboot) you can type "which fastboot" and it will either tell you where it is (something like ~/Android-sdk/platform-tools/fastboot) or it will say, couldn't find fastboot and it will list out a bunch of directories.
One last thing, you can chain commands together with "&&" so say i want to "fastboot boot newboot.img" i would plug my kindle in, press the disconnect button that pops up on the kindle then type in terminal "adb reboot && fastboot boot newboot.img" if/when the first command runs successfully then it will run the second command. If it does not run successful, it won't run the second command. Also, for me, adb reboot takes a few seconds to work and fastboot waits for the device for a few seconds also.
Hope this is useful, I'm not always good at explaining things. I'm also not a Linux pro lol these are just a few things i have learned that are pretty useful

Well, this is useful. Basically you are talking about how to work with linux. Once i understood that inside my kindle there is just a typical linux i can take one of my old linux books and use any command (like the && and other stuff).
I am not a pro with linux (forgot almost everything) but now i know how to look after it and be able (limited) to use it after some testing.
That said, i now was able to do a lot of funny stuff with my kindle, i installed tons of applications just to look how it works (and it works great) and uninstalled them after that.
Now i can watch movies, listen music, play games and can do almost everything what you normally cannot do with a kindle due to amazons restrictions.
What i want to know is how i can extend the linux inside my kindle so it is using a shell which can do even more stuff, like a ksh (korn shell) or something. A shell with commands like i can find in a "normal" linux installation. Is that possible ?
And how about installing a more linux like grafical userinterface ? Or use the kindle as a normal linux pc, just for fun ?

Ummm..... Have you looked at busybox? It is possible to port command line tools to Android. I've seen things like cURL and lynx that worked. Porting and compiling is a little out of my league (wish it wasn't lol, I'd like a updated cURL binary with https support) i know bash scripts work, I've written a few and "run-parts" (part of busybox) will run a directory of scripts.
You should get into (or look into) custom Android development and/or kernel development. There is a lot that can be done

Help, im a real newbie
usurpine said:
I updated my new kindle fire, then rootet it successfully.
After that i installed the Ice Cream Sandwich 4.0 and made it the default launcher.
But this failed, when i now start the kindle fire i get caught into the loop of this error:
! Sorry
The application Ice Cream Sandwich 4.0 (process androd.process.acore) has stopped unexpectedly. Please try again. [Button: force close]
Which i can press, and then the loop starts again.
I am a noob, so please how do i get rid of this launcher ? I could need a reset or factory default or whatever, but the normal ways dont work, because i cant reach them anymore. Any Ideas how to fix this ?
/edit: I have access to my device with adb shell. so i think i can somehow change the default launcher, if someone tells me which file to change because i have no idea which is the right.
Click to expand...
Click to collapse
Please help me, I really have no experience and I followed a link that made it look very easy to install the ICS Launcher. Now I keep getting that same page and it's driving me up the wall.
I have tried the adb so I can uninstall the faulty apk myself but my mac wont detect it even though it still mounts.
Iv done the adb devices but the list is empty.
Please help me in a very easy way to understand.

[Q] Writing an app, works in emulator, crashes on device

Hi Folks, Hopefully this is the right place for this thread. I don't get over here very often so I'm guessing right now.
I wrote an app for my phone (Sprint Galaxy SIII) in Eclipse to control a IOIO (not terribly important to know for this question). I run the app in the emulator and it fires up just fine, but when I run it on my phone (with supposedly the same settings as the emulator--Android version, AP level, etc) it crashes on startup, saying "Unfortunately, <My App> has stopped".
Since it works in the emulator I can't track LogCat to check for errors, so I have no idea where to start looking for the cause. It only crashes on my actual device. My questions are as follows:
1) What would cause an app to work in the emulator but fail to start up in a device with (supposedly) the same settings?
2) Where can I go to look for errors on my phone (if possible) that might point me to the problem?
Thanks!
Matt

DerStrom8 said:
Hi Folks, Hopefully this is the right place for this thread. I don't get over here very often so I'm guessing right now.
I wrote an app for my phone (Sprint Galaxy SIII) in Eclipse to control a IOIO (not terribly important to know for this question). I run the app in the emulator and it fires up just fine, but when I run it on my phone (with supposedly the same settings as the emulator--Android version, AP level, etc) it crashes on startup, saying "Unfortunately, <My App> has stopped".
Since it works in the emulator I can't track LogCat to check for errors, so I have no idea where to start looking for the cause. It only crashes on my actual device. My questions are as follows:
1) What would cause an app to work in the emulator but fail to start up in a device with (supposedly) the same settings?
2) Where can I go to look for errors on my phone (if possible) that might point me to the problem?
Thanks!
Matt
Click to expand...
Click to collapse
Only log could tell you the possible reasons.
Install catalog and look for the error log
Sent from my A0001 using Tapatalk 2

Vivek_Neel said:
Only log could tell you the possible reasons.
Install catalog and look for the error log
Sent from my A0001 using Tapatalk 2
Click to expand...
Click to collapse
Thanks Vivek_Neel. I tried a couple of log viewer apps but they all require superuser access for use on Android 4.1+. I forgot to add it to my profile, but I currently have a Galaxy SIII running Android 4.4.2.
Any other suggestions? I'd rather not root my phone if I don't have to.
Thanks,
Matt

DerStrom8 said:
Thanks Vivek_Neel. I tried a couple of log viewer apps but they all require superuser access for use on Android 4.1+. I forgot to add it to my profile, but I currently have a Galaxy SIII running Android 4.4.2.
Any other suggestions? I'd rather not root my phone if I don't have to.
Thanks,
Matt
Click to expand...
Click to collapse
Running the app on your phone with it plugged in to a pc and eclipse open should mean that eclipse catches the log, no root access needed, you would need to allow adb debugging though. If it doesn't work with eclipse I know for definite that it works with Android Studio.

Jonny said:
Running the app on your phone with it plugged in to a pc and eclipse open should mean that eclipse catches the log, no root access needed, you would need to allow adb debugging though. If it doesn't work with eclipse I know for definite that it works with Android Studio.
Click to expand...
Click to collapse
Eclipse doesn't seem to recognize my phone. It only brings up the emulator as an available device. Perhaps I should dig more into the cause of that first. You're saying if I load the app on my phone while connected to the PC it'll still show up in the logcat? That would be a huge help if that's the case!

DerStrom8 said:
Eclipse doesn't seem to recognize my phone. It only brings up the emulator as an available device. Perhaps I should dig more into the cause of that first. You're saying if I load the app on my phone while connected to the PC it'll still show up in the logcat? That would be a huge help if that's the case!
Click to expand...
Click to collapse
It should do - worked this way around a year ago when I was using eclipse myself before jumping ship to AS.

You might want to handle uncaught exceptions and either debug, write to a file or what ever is the best way for you.
You can see an implementation example for handling uncaught exceptions here: http://stackoverflow.com/questions/8943288/how-to-implement-uncaughtexception-android.
Please note that some crashes are not caught using this technique so you'll need to use the above mentioned methods to view logcat.
If you have root on your device, install a logcat viewer application. most likely that filtering the display by your package name (or parts of it) we'll lead you to the error cause.

Thanks everyone for the help, I have found the solution. Eclipse wasn't recognizing my phone because apparently the driver was no longer installed (I thought I had installed it a long time ago, but that must have been on my laptop--I'm on my desktop now). I installed it and Eclipse found the phone no problem. I loaded the app while watching LogCat and found the following:
java.lang.SecurityException: Need BLUETOOTH permission: Neither user 10211 nor current process has android.permission.BLUETOOTH.
Click to expand...
Click to collapse
Well that was embarrassing! Added the Bluetooth permissions to the app et voila! The app works just fine.
Thanks for your time!
Matt

DerStrom8 said:
Thanks everyone for the help, I have found the solution. Eclipse wasn't recognizing my phone because apparently the driver was no longer installed (I thought I had installed it a long time ago, but that must have been on my laptop--I'm on my desktop now). I installed it and Eclipse found the phone no problem. I loaded the app while watching LogCat and found the following:
Well that was embarrassing! Added the Bluetooth permissions to the app et voila! The app works just fine.
Thanks for your time!
Matt
Click to expand...
Click to collapse
:laugh::laugh:
Haha glad you got it sorted!