Related
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.
So I'm rooted on my Evo and as far as I can tell I've flashed the stock rom that should allow me to uninstall the bloatware, however, I dont see any uninstall options for that crap like facebook.
Anything I'm doing wrong?
I followed this guide to root and flash. I've tested my root using the "Terminal Emulator" and typing "su" and it returned a "#"
Thanks XDA, I love most of you
You know you need to uninstall from your computer using adb
Sent from my EVO using Tapatalk
I've installed Android Debug Bridge but I was under the impression that rooting my phone would allow me to do things on my phone, such as install and uninstall what I want.
Could you explain the process more or send me to a link that does?
If you want to do it in android you either need console program or a file manager. Root explorer us the best one and easiest. Looks just like a typical explorer, tap the rw/ro button for read only or read write and delete away.
You have to have completed the second part of unlocking nand. Otherwise your only option is using a computer and adb in recovery.
They dont make this easy do they? I would have figured Android to be very open for things like this, I'm starting to feel like I have to "jailbreak" again, only this time it's to remove crap.
This seems like so much work to get rid of facebook and sprint tv.
It took me 10 minutes total including the file downloads. Its a one time thing and there is a learning curve with any new platform.
Aridon, is there a free explorer you'd recommend? I dont mind buying software, just want to make sure I'm not mistaken before I buy something that is worthless to me.
You get a trial on any purchased software in android. After its installed if you go backto market and pull it up again there will be a refund option. So no risk. I think its for 24 hours.
As for a free one I'm not sure when I first started messing around with android I bought it because people said it was the best. I don't have any regrets.
Just remember to tap the top button for rw. Long press brings up options. Menu had an option for multiple file select and other goodies. its very powerful.
Aridon, thanks for everything, just 1 more question. I bought it, and the program is slick. I went to /system/app and deleted facebook, is that all I need to do?
Cause I still see it in the menu
I may have done a bad thing, my phone just reset itself.... I need a trainer to be with me at all times.
So after that restart, the files I thought I deleted are back.
Yes just go into system/app, make sure it says rw up top which means read write access, then select the file, general an .apk and .odex and delete. Not all files have both and some roms don't have any .odex files.
I'll be up for another 30 min or so and I'll keep an eye on this thread in case you have any questions.
Ok that means the second part where you unlocked nand wasn't done correctly. Make sure you go slow, download the files again because they are different and watch for errors.
The only hiccup I had was when I copied the new recovery and other files to my sd and tried to adb push it gave me some kind of can't find file error. I had to reboot and it was fine. It send after the boot I could go back in and adb the files it must have been some kind if a refresh error on the sd while in recovery.
Edit. I'm responding on my evo and in bed so excuse errors.
Go to sleep, I'll resume this thread tomorrow if I'm still having trouble. You Sir, are a life saver. This is why XDA is THE FORUM for anything mobile.
Good night then.
I know it can be a bit of a pain to do this but I promise you it will be worth it. Things have only just started and the custom roms are already awesome. Once we get the source code things are going to be insane over here.
Got it! Everything is working well. However, now my voice mail says it can not download messages.... Rebooted and it's all good.
Facebook and Twitter Free! Also, no more Sprint crap.
Life is good, again.
Another terminal substitute is Android Commander, out is naturally a file explorer that allows transfer and deletion off whatever you want. This program runs in your pc.
As Was mentioned above, root explorer is the easiest way.
Aridon said:
If you want to do it in android you either need console program or a file manager. Root explorer us the best one and easiest. Looks just like a typical explorer, tap the rw/ro button for read only or read write and delete away.
You have to have completed the second part of unlocking nand. Otherwise your only option is using a computer and adb in recovery.
Click to expand...
Click to collapse
So with Android - one simply deletes the application rather than un-installing it? That doesn't cause problems with the system thinking the application still exists somewhere?
DrawnToScale said:
So with Android - one simply deletes the application rather than un-installing it? That doesn't cause problems with the system thinking the application still exists somewhere?
Click to expand...
Click to collapse
It depends on where it is installed. /system/apps do not allow you to just uninstall you have to delete it. One this is done its gone. Obviously if you delete phone.apk you are going to have issues or if you delete a process that is running you may get a force close but for the most part unless you delete an app like people or dialer you are fine. After the single force close everything works properly.
Some custom roms moved programs to /data/app which allows them to be removed the other way.
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.
Hi guys, I just got my Kindle Fire for xmas today. I want to root, but I've been reading the forum and see that a recent OTA update came out and there's been problems. I'm not super computer savy and I really don't want to mess it up. Do I have to wait for a new method to root? If someone wants to take a newb under their wing and tell me what roms etc I should get it would be much appreciated! Just a little overwhelmed with all the posts, not sure where to get consolidated current info.
I haven't even turned it on yet, I'm not sure if I should wait to turn it on, so that if it doesn't have the OTA update it doesn't send through as soon as I turn it on... whatever advice anyone can give would be much appreciated!
For Windows, Use this http://forum.xda-developers.com/showthread.php?t=1399889
Tired that version today works wel..
I haven't turned my Kindle on yet, can I avoid all the complications by somehow keeping it from getting the OTA update when it turns on? (I'm assuming it's not running 6.2.1 yet because that just came out?) I'm afraid to turn it on and I really want to play with it so if someone can let me know that would be great!
And if anyone wants to talk me through it, my screenname is Insidious Lily on aim, I need moral support/help, lol.
Just keep WiFi off until you are done... no issues.
Okay.. I'm a little overwhelmed by all the stuff in that post but I'll do my best. I'm in that IRC chat with another newb if you want to come help us, haha.
And high five, I have a HTC incredible too.
How about current method for Mac users?
ty!
So here's what I did...
(I have a Mac running snow leopard).
I downloaded the KindleFireRootMacLinux folder referenced in the old Mac root thread. This gets adb running on the mac. Use whatever system you need to get adb running on your PC. The command adb on the PC is replaced by ./adb-mac on the Mac.
Then I used the burrito root method and pushed super user to the kindle fire. using the adb commands from terminal.
Finally, I downloaded the google apps folder, installed Googleservicesframework *FIRST* and rebooted.
Then I installled the remainder of the apps EXCEPT market.
Then I used the ES Folder program with root explorer etc enabled to copy the market.apk file to system/app and changed permissions and ran it.
Everything worked fine.
THEN I installed DroidWall to take away the internet communication capabilities of all the Amazon apps (and browser) to try and keep another stealth push from Amazon from breaking root.
Someone else will have to link to the files because I haven't posted enough to include links.
Current root is BurritoRoot http://forum.xda-developers.com/showthread.php?t=1410223
if your particularly lazy Vashypooh's utility has been updated to use it here http://forum.xda-developers.com/showthread.php?t=1399889
I'll just join in to mention something the OP may not realize. Although I'm basically a newbie rooting the KF also, the current root method works with the new update from Amazon, so you don't have to worry about preventing the update to download. In fact, it's probably best to let it update first, otherwise you'll just have to repeat rooting it.
Anyone feel free to correct me if I have that wrong.
leebo said:
I'll just join in to mention something the OP may not realize. Although I'm basically a newbie rooting the KF also, the current root method works with the new update from Amazon, so you don't have to worry about preventing the update to download. In fact, it's probably best to let it update first, otherwise you'll just have to repeat rooting it.
Anyone feel free to correct me if I have that wrong.
Click to expand...
Click to collapse
Yep, but we did discover it doesnt work with 6.0 this morning. Seems what I used wasn't fully introduced until after 6.0
This is an Android TV box, equipped with a deeply modified android 4.4 system, while the device is shielded from usb interface adb debugging, the only way to adb is to use root privileges to actively start adb wifi from the device.
I tried kingo root yesterday, and it's the only root tool I've found so far that still works with one click.
Seemed to have good luck as it worked once, but after I rebooted it today, kingo superuser tells me the device is not rooted yet.
I noticed that the location /system/bin/su still has a valid binary file (about 70KB in size).
I even installed a terminal emulator to actively execute the su command, but the result should also be as you guessed, no errors reported and no log output, and again, my permissions did not change from $ to #.
I've tried Google, but haven't found anything useful.
Is there anything I can try to solve this problem? I've tried sending a tweet to kingo root and sending feedback to the official website, but the last tweet on its Twitter feed was sent in 2018 and I think it's unlikely that anyone from the official team will be able to see my feedback.
So I'm trying to ask for help on the XDA forums, this is my first post here and I hope I'm not sending it to the wrong partition.
Thank you all.
===
Finally, I'd like to add a bit of information.
Since kingo root thinks the device is rooted, there is no way for me to get it to perform the root steps all over again.
Also, although kingo superuser provides the ability to remove root, there is no way for me to use it to remove this su file and kingo superuser since it suggests the device is not rooted, which seems to be stuck in a dead end loop
Even because it's a box, I don't even seem to have a way to get into fastboot
===
这是一台安卓的电视盒子，搭载的是经过深度修改的android 4.4系统，同时设备从usb接口上屏蔽了adb调试，想要进行adb的唯一办法就是使用root权限从设备上主动启动adb wifi。
我昨天尝试了kingo root，这是我目前找到唯一的一个还能够运行一键的root工具了。
看起来运气不错，因为一次就成功了，但是我今天重启了它之后，kingo superuser告诉我设备尚未root。
我注意到/system/bin/su这个位置依然存在着有效的二进制文件（大约70KB大小）。
甚至我还安装了一个终端模拟器，主动去执行su命令，但是结果也应该正如你所猜测的那样，没有报错，也没有输出log，同样的，我的权限也没有从$变成#。
我尝试过谷歌，但是没有查到过什么有用的东西。
请问我有什么可以尝试的办法去解决这个问题吗？我已经尝试向kingo root发送推特和向官网上发送反馈，但是它的推特上最后一条推文是在2018年发送的，我认为官方团队不大可能能够有人看到我的反馈。
所以我尝试在XDA论坛上寻求大家的帮助，这是我第一次在这里发帖，希望我没有将帖子发送到错误的分区。
谢谢大家
===
最后，我想补充一点信息。
因为kingo root认为设备已经root了，所以我也没有办法让它重新执行一遍root的步骤。
另外，虽然kingo superuser提供了移除root的功能，但是由于它提示设备无root权限，我也没有办法用它把这个su文件和kingo superuser移除掉，这看起来似乎陷入了一个死循环
甚至因为它是一个盒子，我似乎连进入fastboot的办法都没有