Database Users

[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.

[Q] sdcard permission denied

I have rooted my OG MyTouch 3g, so I am familiar with the process, and now I am trying to root my MyTouch 4g.
I am trying to:
Code:
adb push su /sdcard/su
and every time i try it says:
Code:
failed to copy 'su' to '/sdcard/su': Permission denied
Any suggestions?

rbmako69 said:
I have rooted my OG MyTouch 3g, so I am familiar with the process, and now I am trying to root my MyTouch 4g.
I am trying to:
Code:
adb push su /sdcard/su
and every time i try it says:
Code:
failed to copy 'su' to '/sdcard/su': Permission denied
Any suggestions?
Click to expand...
Click to collapse
Okay what Rooting process are you trying to follow? And in what step are you.
The main reason you are getting that error is the file "su" doesn't exist.... but if you answer the question above we can help you more.

I am trying the Cyanogen Mod: TMobile_myTouch_4G:_Full_Update_Guide

rbmako69 said:
I am trying the Cyanogen Mod: TMobile_myTouch_4G:_Full_Update_Guide
Click to expand...
Click to collapse
Make sure you have ADB Debugging turned on
- Settings > applications > development
Make sure you have the SD Card mounted to the computer
Make sure you changed your ADB target folder to the one store that rooting package.
Those would be the three places i'd start if i were you.
However alot of people will contest that this method is simpler with a high percentage of "" when you are done with the rooting process.

neidlinger said:
Make sure you have ADB Debugging turned on
- Settings > applications > development
Click to expand...
Click to collapse
Yes, I did that.
neidlinger said:
Make sure you have the SD Card mounted to the computer
Click to expand...
Click to collapse
I have access to all the files on the SDCARD on my mac
neidlinger said:
Make sure you changed your ADB target folder to the one store that rooting package.
Click to expand...
Click to collapse
Not sure what you mean by this.
Those would be the three places i'd start if i were you.
However alot of people will contest that this method is simpler with a high percentage of "" when you are done with the rooting process.[/QUOTE]

I'm going to try the method that you linked.

rbmako69 said:
I have access to all the files on the SDCARD on my mac
Click to expand...
Click to collapse
Being that you are using a Mac you might run into some problems along the road. I've see quite a few "problematic" threads pop up regarding Mac and Android's ADB not working correctly.
you could also try This Method < it doesn't require the use of a PC @ all.

I did that other method and it seems to have worked.
Now do I continue with the walkthrough of installing cyanogen now that the phone is rooted?

rbmako69 said:
I did that other method and it seems to have worked.
Now do I continue with the walkthrough of installing cyanogen now that the phone is rooted?
Click to expand...
Click to collapse
Do you have a Super User icon on your screen?
If you do
-Downloaded Terminal Emulator from the market.
- go to it and type "su" you should get a window asking you to approve the Super User request.
If the dollar sign ($) changes to a pound (#) sign then you are rooted.
next turn off the phone and hold the volume down rocker and the power button that will boot into engineering scree (HBoot) look on the top line and see if you have "s=off"...
If the s=off then you are perma rooted w/o the security check. temp root with VISIONary one last time, then install Clockwork ROM Manager and change the Recovery Image to 3.0.0.06 (Here or Here) From their you can do what you want to do regarding Cyanogen(mod).
*The reason i recommend flashing 3.0.0.6 prior to flashing it ROMs is it handles 2.2 (ext3) and 2.3 (ext4) style roms. Where every other version is either or, not both.

I sucessfully installed cyanogen, and everything seems to be working correctly, but i must not have installed the google apps, and i do have the market place to download them again.
Where can i get those from?
EDIT: I found them.

rbmako69 said:
I sucessfully installed cyanogen, and everything seems to be working correctly, but i must not have installed the google apps, and i do have the market place to download them again.
Where can i get those from?
Click to expand...
Click to collapse
http://android.d3xt3r01.tk/cyanogen/gapps/gapps-gb-20110120-signed.zip
wipe (factory reset) before flashing the g/apps via the recovery image.

I had found them before, but the market wasn't working, and I was trying to sync my contacts back to the phone from my gmail account. I didn't do a factory reset through, so I'm trying again. Hopefully it works this time.

I'm guessing the market isn't working because I haven't signed in with my gmail account.
Any idea on how to set that back up?

rbmako69 said:
I'm guessing the market isn't working because I haven't signed in with my gmail account.
Any idea on how to set that back up?
Click to expand...
Click to collapse
Settings > accounts & Sync > menu button > add account.

Unable to Re-Root Droid 2 after Gingerbread OTA

Here's my problem,
I had the Droid 2 with stock ROM rooted and all was well. My phone installed the Gingerbread ROM (4.5.601) when Verizon pushed it out a few days ago. Thankfully, this did not totally jack up my phone. However, I no longer have root access.
I have tried three different 1 click root methods for the Gingerbread ROM but none of them worked. I tried un-rooting and re-rooting with one clicks and that's not working. I tried manually removing the Superuser app and rooting, no joy.
The one clicks are connecting with the phone but the phone does not seem to want to allow access to change files.
Before anyone asks, YES I have the drivers installed and the connection with the PC is good. I have attempted to run the 1 click roots in "charge only" AND "PC Mode". Debugging is on and I am set to allow non-market applications.
Suggestions?
Thanks,
Tracker

Update: in trying to manually remove old superuser file with adb shell, I just can't seem to get the # prompt to execute the commands even after running Pete Souza's exploits.
suggestions?

Hope somebody comes up with an answer - same thing happened to me.

did you use the d3 root method? thats the only one that works 100% on gingerbread.

Yes. I used the "Pete's Motorola Root Tools.exe" program on Win7:
psouza4.com/droid3/#root
I also followed the "Droid X Notes" section at the bottom even though I have the D2 and I'm not able to get the "adb shell" ending with #.

SOS!!
Thank you for such a clear, concise post! I am in the same boat with no luck. I used the one click root for D3 which says it will work for a number of Android phones, including the D2 Global, but is NOT working with my D2. I have run the application two times and both times it went through the entire process, rebooted my phone three times and said success but...no success... I am sooo bummed as the only way I get internet at home is via Wireless Tether which I can no longer use because I do not have Root access!
Desperate in Cool (the name of the town I live in), I need help!!
Thanks in advance,
Jeni

Yeah, still no joy here. I've retried everything that I mentioned in the OP and still can't get the # so I can execute an un-root and/or re-root as described on Pete's website.
I've tried it on both a Win XP and a Win 7 machine.
Anyone have any suggestions? It appears the D2 Gingerbread firmware doesn't want to allow permissions to modify certain portions that were allowed before.

Success
I didn't so much fix the problem as hit it with a bat until it shattered, then rebuilt it.
My fix was to SFB the phone back to Froyo with factory defaults, activate it with Verizon (at this point I have no software added or accounts set up on it so obviously no root), apply the OTA update to GB, perform the 1-click Root which worked this time, then setup my google accounts and install Titanium Backup which I had previously used, and restored all my data from it.
At this point I'm getting some force-close errors which I'm sure are related to the Titanium restore but I was able to ADB Shell in and SU so I know I have rooted it properly and at the very least I will do another clean wipe and restore individual applications one at a time so I know which aren't working right and go from there.
Good luck everyone!

My fix was to SFB the phone back to Froyo with factory defaults, activate it with Verizon (at this point I have no software added or accounts set up on it so obviously no root), apply the OTA update to GB, perform the 1-click Root which worked this time, then setup my google accounts and install Titanium Backup which I had previously used, and restored all my data from it.
Click to expand...
Click to collapse
I kinda figured that this would work. I'm trying to avoid a full nuke of the phone, but so far it appears that this is the only work around.
Anyone else got a plan?

Only option I was going to provide was SBF to 2.3.2 with RSDlite and re-flash the OTA, then run the Droid3 exploit.

I have a D2G and I had the exact same problem. I did an OTA upgrade without un-rooting (I was earlier rooted using z4root). I had a long discussion with Pete Souza, the guy who created 1-Click root. And he agreed to help me out. He did a remote to my computer and rooted my D2G. I am going to try to reproduce all the steps here.
Situation: Was rooted using z4root. Had Superuser and su binary both on my phone but root was not recognized by titanium Backup, SetCPU, etc.
Resolution:
Run Psouza's 1-cick root http://www.psouza4.com/droid3 (ensure u have motorola drivers)
First try the Root, and if that does not work only then continue with the following steps. I got an error after step 3 which said the phone cannot be rooted (or something like that). The first two steps were a success.
Now that the root is not working, run the Temp ADB Root from the same app. In my case even that failed - but Pete said that ignore the failure message.
Now, I need to delete the su and busybox which are leftovers from the earlier root.
Open a command prompt in the support_files folder where adb is located.
Get into the shell by typing: "adb shell"
type "/system/xbin/su"
This will pop-up a prompt on your phone to allow Superuser access - just click Okay.
The $ sign will change to #
Now type "busybox mount -o remount,rw /dev/block/mtdblock3 /system"
now type "cd /system/bin" This is where your su and busybox are.
Type "rm su"
Type "rm busybox"
After this just exit out of everything and run the 1-click root again. It should work now.
======================
All credits to psouza www.psouza4.com
======================

drumster said:
I have a D2G and I had the exact same problem. I did an OTA upgrade without un-rooting (I was earlier rooted using z4root). I had a long discussion with Pete Souza, the guy who created 1-Click root. And he agreed to help me out. He did a remote to my computer and rooted my D2G. I am going to try to reproduce all the steps here.
Situation: Was rooted using z4root. Had Superuser and su binary both on my phone but root was not recognized by titanium Backup, SetCPU, etc.
Resolution:
Run Psouza's 1-cick root http://www.psouza4.com/droid3 (ensure u have motorola drivers)
First try the Root, and if that does not work only then continue with the following steps. I got an error after step 3 which said the phone cannot be rooted (or something like that). The first two steps were a success.
Now that the root is not working, run the Temp ADB Root from the same app. In my case even that failed - but Pete said that ignore the failure message.
Now, I need to delete the su and busybox which are leftovers from the earlier root.
Open a command prompt in the support_files folder where adb is located.
Get into the shell by typing: "adb shell"
type "/system/xbin/su"
This will pop-up a prompt on your phone to allow Superuser access - just click Okay.
The $ sign will change to #
Now type "busybox mount -o remount,rw /dev/block/mtdblock3 /system"
now type "cd /system/bin" This is where your su and busybox are.
Type "rm su"
Type "rm busybox"
After this just exit out of everything and run the 1-click root again. It should work now.
======================
All credits to psouza www.psouza4.com
======================
Click to expand...
Click to collapse
IMO this instruction should be stickied.

This worked perfectly on my wife's D2G. Rooted Gingerbread = a good start to the day!

Awesome! Thanks!

Just wanted to say I think i love you...this worked for me after two tries on my Droid 2.
First time I was able to remove su and busybox...then when I applied the one click root again, it said there were a bunch of errors but still succeeded. After the reboot I didn't get superuser access yet so I went through deleting su and busybox again (but busybox wasn't found)
The second time i decided to restart my phone before running the script again and when attempting to verify if su was still installed by going into adb shell...it said my phone was already rooted.
Thanks!!

Awesome!
Thanks! This worked for me as well! (after additional reboot)

Good Info but one problem for me
Since I did the OTA Gingerbread, I cannot get into debugging mode. I have uninstalled the Moto drivers & reinstalled using my administrator profile on Windows 7. I have also sbf my phone. Wipe cache. Factory reset. Activate service (NOT download or sync w/ google). OTA Gingerbread. This is on a regualr D2. Anyone have any ideas on how I can get into debugging mode. Otherwise I can't do anything.

Thank you!
I am so glad I found this post and the directions posted by drumster. I had previously used z4root and had not unrooted before allowing the Gingerbread upgrade. Pete's application fixed my Droid 2 on the first attempt; no other steps were needed.
Thanks again,
Andrew

awesome
psouzas 1 click worked for me. Droid 2. previously had rooted with deroot method until it updated by itself to gingerbread which broke root.
enabled usb debugging
in pc mode, clicked on souza's link and followed instructions
i have win 7 64 bit computer

It works
I just got it to work. I was on rooted froyo. Sbf'd back to stock froyo. Downloaded and installed OTA G bread. Then I had to run the D3 one click root method twice but the 2nd time it worked fine.

[Gingerbread Root] Pete's Motorola Root Tools

This does not work with Droid X System Version .621.
(Information on this post was taken from Pete's website: http://www.psouza4.com/Bionic/)
NOTE: If you were rooted on the original OTA and took the update to .602 and lost root, read the 'Droid X' notes under the how-to.
-----------------------------------------------------------------------------
How to: One Click Root for Windows 7/Vista
1. Your phone must be connected via USB data cable to your computer and be recognized.
2. If your phone is connected, but not recognized, you may need to install one of these software drivers:
-Windows universal 32-bit Motorola drivers version 5.2.0
-Windows universal 64-bit Motorola drivers version 5.2.0
3. Download this one-click root package: PetesMotorolaRootTools_v1.08.zip
4. Extract the contents of the one-click root package to a new folder on your computer.
5. Make sure USB Debugging is enabled on your device. This should be under Settings -> Applications -> Development -> USB Debugging.
6. From the new folder on your computer, double-click on Pete's_Motrola_Root_Tools.exe to begin the root process.
7. Click 'Root My Phone'.
-----------------------------------------------------------------------------
Droid X Note:
Droid X Notes
Your phone may need to be in either charging mode or PC mode or you may need to toggle it a number of times for the device to recognized correctly.
If you are trying to root from the OTA Gingerbread update and you were previously rooted, you will probably experience problems with this root method because of the pre-existence of busybox and superuser.apk. For that reason, you may need to attempt both the script method (for Windows XP users) and program executable method (Windows Vista/7 users). If you are still having problems, please follow these instructions:
Open a Command Prompt in the folder where you extracted the one-click root package (see instructions for rooting). If you are using Windows 7, you can just use Shift+Right-Click on the folder you extracted the package and choose to "Open a command prompt here". For other operating systems or versions of Windows, you may require some DOS experience or need to Google how to change directories.
In the command prompt, type the following command:
adb shell
Click to expand...
Click to collapse
If you receive any kind of error, then you may not be in the folder where you extracted ADB.exe or you may need to reboot your computer, your phone, or check the connection. You should receive an ADB prompt ending with either a # or a $.
If the line ends with a $, then run the one-click exploit for Windows XP (even if you have Windows Vista or 7) and only complete step 1.
When you have adb shell ending with a #, type the following commands:
mount -o remount,rw /dev/block/system /system
rm /system/bin/su
rm /system/xbin/su
Click to expand...
Click to collapse
Ignore any messages that warn you about the file not being found/missing. We're removing old copies of su/superuser which are causing this one-click root method to fail.
(credit: KevlarGibs)
Additionally, during the parts of the one-click root that reboot your phone, your phone will most likely reboot into recovery instead of into the standard Android lock screen. If this is the case, simply unplug the cable and reboot the phone manually. When you are finished rebooting, plug the phone back in again. Some people have had to reboot their PC too.
Finally, some users have mentioned that the root isn't taking affect right away for all apps. Eventually, after several reboots, the phone finally takes root. We're not sure why this is (I don't have a Droid X -- I'm just re-posting this information for brevity).
-----------------------------------------------------------------------------
Please try the Windows Vista/7 method first! It will work better for most Windows XP users.
Only use this method if the other has not worked yet.
http://www.mediafire.com/?pj5lk8u2s0zhqo8
----------------------------------------------------------------------------
Nothing you see here is my work. All credit goes to Pete and everyone he's credited. I simply created this thread on XDA using Pete's information.

Reserved for future information.

Awesome
Great tool, thanks so much!

Confirmed OTA
Works fine!!!

Awesome! Works perfectly!

Nice, I may give it a go (may sbf to 602 for a clean start)
D.

I SBF'd to .602 on my DX and the root was successful but I can't get my phone to boot into CWM Recovery. I tried following the special DX instructions but can't get the ADB Shell to show anything but a $.
Whats next for me to try to get this working?

Hi I'm trying to unroot my x2 and it keeps saying Error: you are missing adb.exe, which was packaged with this program. The adb.exe is in the same folder as all of the other files i extracted to my restore folder. Any ideas?

I will try this at thanksgiving for my dad's X
It was rooted froyo and got the ota GB and wont root. Hopefully this works

choonami said:
I SBF'd to .602 on my DX and the root was successful but I can't get my phone to boot into CWM Recovery. I tried following the special DX instructions but can't get the ADB Shell to show anything but a $.
Whats next for me to try to get this working?
Click to expand...
Click to collapse
Your preinstall is full. With Root Explorer go to preinstall/app/ and delete something (NFS). Reflash Clockwork mod. Then try again.
Sent from my PC36100 using XDA Premium App

I have just updated from 602 to 605 ota official.
Did run the process as guided above, but nothing seemed to happen on my droidX, and I cant see any super user. and did try to instal CWM to my device, its said the device has not rooted.
Any one got the same issue?

Greatdane said:
I have just updated from 602 to 605 ota official.
Did run the process as guided above, but nothing seemed to happen on my droidX, and I cant see any super user. and did try to instal CWM to my device, its said the device has not rooted.
Any one got the same issue?
Click to expand...
Click to collapse
Were you previously rooted on .602? If so, you may need to follow the Droid X notes.
Sent from my DROIDX using XDA App

This worked perfectly on my Droid X....thanks for making it so easy!!

Finally worked up the cajones to use Pete's Tools and rooted my DX. *whew*
Doing a complete TiBu right now. Couple quick questions.......
1. Is CWM installed? If so, how does one access. If not, ROM Manager perhaps?
2. Renamed blurupdater_VZW.apk to .bak to block updates
3. Any "landmines" I should NOT uninstall?
Sorry if I sound noobish but this is my only phone number and am proceeding cautiously.
Thanks

skeeterpro said:
Finally worked up the cajones to use Pete's Tools and rooted my DX. *whew*
Doing a complete TiBu right now. Couple quick questions.......
1. Is CWM installed? If so, how does one access. If not, ROM Manager perhaps?
2. Renamed blurupdater_VZW.apk to .bak to block updates
3. Any "landmines" I should NOT uninstall?
Sorry if I sound noobish but this is my only phone number and am proceeding cautiously.
Thanks
Click to expand...
Click to collapse
First of all, let me reassure you that anything you do to your phone can be reversed with a simple SBF. ^_^
Install ClockworkMod Recovery through Droid 2 Bootstrapper, then use ROM Manager to update it to the latest version.
There is plenty of things that you can remove that will cause issues =P It's pretty much trial and error, there are lists you can look up that will tell you what can and can't be removed, but regardless, always make a backup in CWM.
Sent from my DROIDX using XDA App

Thanks again.
Droid 2 Bootstrapper via Android Market will do it, one presumes?

skeeterpro said:
Thanks again.
Droid 2 Bootstrapper via Android Market will do it, one presumes?
Click to expand...
Click to collapse
You are correct.
Sent from my DROIDX using XDA App

I amaze myself sometimes. lol
Has anyone flashed working CWM via ROM Manager?
Can't say I have interest in flashing ROMs. Just want CWM for nandroid system backups actually.

STRANGE!
DroidX, 2.3.3, original Moto ROM, LauncherPro+
First time I did Pete's it worked perfectly.
After .605 OTA it had a problem, so I re-Peted.
Each time Pete tried to reboot the phone, I had to pull the battery. Eventually, the process finished and I had a rooted Droid. It's fast, stable, has fine battery life. TitaniumPro, QuickBoot, and other root-only tools work properly. Various things ask for Superuser permission, and I give it, and they work properly.
But the SUPERUSER app has disappeared. When I go to Market, it says "Installed". It doesn't appear on my app list, and was never frozen. It's there, but invisible.
Everything else works, so should I just leave it alone?

noguru said:
DroidX, 2.3.3, original Moto ROM, LauncherPro+
First time I did Pete's it worked perfectly.
After .605 OTA it had a problem, so I re-Peted.
Each time Pete tried to reboot the phone, I had to pull the battery. Eventually, the process finished and I had a rooted Droid. It's fast, stable, has fine battery life. TitaniumPro, QuickBoot, and other root-only tools work properly. Various things ask for Superuser permission, and I give it, and they work properly.
But the SUPERUSER app has disappeared. When I go to Market, it says "Installed". It doesn't appear on my app list, and was never frozen. It's there, but invisible.
Everything else works, so should I just leave it alone?
Click to expand...
Click to collapse
You should be able to find Superuser by using the search key. It's not really important to have, it just manages the superuser permissions. I think of it as a background app.
Sent from my DROIDX using XDA App

[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.