Develop Bugs

Dealing with Sprint / HTC Preinstalled Junk - Startup Auditor or Just wait for Root?

I would like to get everyone's opinion, I'm looking at a couple options of how to get rid of Sprint / HTC Junk that runs at startup and continues to startup - Sprint Nav, Sprint Zone, Nascar, all those things. I'd love to hear alternate suggestions as well.
1. Startup Auditor - Seems to do a decent job of keeping things from starting, definitely reduced boot time, but I'm unsure of how it actually operates - is it just another task killer? Or does it actually take things out of a startup list without running in the background? I've been playing with it for close to a day and am still undecided, at times it seems to help, but other times I don't think it really did anything. It seems like having root would make it completely pointless, since you could edit things yourself.
2. Wait for Root - I already did the OTA update so root is not possible, from what I understand. With root access, I'm sure it would be much easier to remove the actual applications, and furthermore install custom roms without the bloat.
3. ?? You tell me please
Thanks guys!

If you're comfortable using adb, you can root here: http://forum.xda-developers.com/showthread.php?t=718889
I rooted my yesterday after the OTA and flashed Fresh 0.5.3. It doesn't have most of the crapware.

gx1400 said:
If you're comfortable using adb, you can root here: http://forum.xda-developers.com/showthread.php?t=718889
I rooted my yesterday after the OTA and flashed Fresh 0.5.3. It doesn't have most of the crapware.
Click to expand...
Click to collapse
Funny I was just reading that. I have zero experience with ADB, but perhaps that is the best route. Can't be too hard to learn, right?
Thanks for posting that. If you have root, it mostly eliminates the need for a program like startup auditor, right?

berardi said:
Funny I was just reading that. I have zero experience with ADB, but perhaps that is the best route. Can't be too hard to learn, right?
Thanks for posting that. If you have root, it mostly eliminates the need for a program like startup auditor, right?
Click to expand...
Click to collapse
Correct. Most ROMs already have the crapware removed, however, once rooted you'll also have the ability to remove and do anything else you want.
If you are uncomfortable with adb, don't be. There are enough tutorials and videos around to walk you through the process. Not only was I a complete noob when I moved to Andriod from the iPhone but I am also using a Mac which means the commands are slightly different. However, with a little trial and error I was able to root via adb the very weekend the phone was released when only adb instructions existed.
And, going forward you'll never have to wait for "Idiot Guides" again. Whenever something new and great comes along you'll have the skills to implement it right away.

okolowicz said:
Correct. Most ROMs already have the crapware removed, however, once rooted you'll also have the ability to remove and do anything else you want.
If you are uncomfortable with adb, don't be. There are enough tutorials and videos around to walk you through the process. Not only was I a complete noob when I moved to Andriod from the iPhone but I am also using a Mac which means the commands are slightly different. However, with a little trial and error I was able to root via adb the very weekend the phone was released when only adb instructions existed.
And, going forward you'll never have to wait for "Idiot Guides" again. Whenever something new and great comes along you'll have the skills to implement it right away.
Click to expand...
Click to collapse
I'm trying to setup ADB right now but I'm stuck here:
http://forum.xda-developers.com/showthread.php?t=694250
3. Enabling ADB support on EVO
If using completely stock EVO, adb will be disabled in recovery and can't be enabled.
Click to expand...
Click to collapse
So if you can't enable ADB on stock EVO, but you need ADB to root - what to do?
EDIT : Nm I think I got it

I want to say that if you plug your phone into your computer and select sync option, that it will install the necessary drivers. Just make sure to turn on usb debugging in your settings menu: menu,settings, applications, development, usb debugging- check the box.

elegantai said:
I want to say that if you plug your phone into your computer and select sync option, that it will install the necessary drivers. Just make sure to turn on usb debugging in your settings menu: menu,settings, applications, development, usb debugging- check the box.
Click to expand...
Click to collapse
Thanks got it..
I'm following these instructions, they seem the most complete. I followed every step successfully and refreshed the pages, and it told me to reboot and run part2. However when I hit
adb reboot
it returns
adb: permission denied
What did I do wrong here?
EDIT: Missed hitting exit. That step wasn't there in original, it is in the recompiled though.

go read up on that thread, do a search for 'permission denied' or the like and I am sure something will come.I saw it a few times while reading that thread
err... Are you sure it didnt just mean reboot your phone?

elegantai said:
go read up on that thread, do a search for 'permission denied' or the like and I am sure something will come.I saw it a few times while reading that thread
err... Are you sure it didnt just mean reboot your phone?
Click to expand...
Click to collapse
haha thanks I was messed up because the original instructions didn't say to exit the adb shell (I probably should have known though) but now I'm past that, now to reboot and hit adb shell /data/local/part2 in time lol this is fun :-D

All done!!! :-D now to flash rom... good times!
Thanks all

[Solved] Phone malfunctioning after flashing Voodoo lagfix

http://forum.xda-developers.com/showpost.php?p=7975002&postcount=4
A few days ago I flashed to JPC, but in my opinion it has way to much bugs so I flashed to JM7. I followed the guide to recover the orginal product code and, for as far as I know, it worked succesfully. But... After that I installed some applications and flashed the the voodoo lagfix to my device. I also tried to flash the OC-kernel but that didn't work, probably because the voodoo lagfix uses zImage too, so my phone didn't boot anymore. I went to download mode and flashed JM7 again. After that I flashed the voodoo lagfix to my phone and then I wiped the data and cache using the recovery mode. When I booted up my phone, the apps I installed earlier(eBuddy, Root Explorer) were still installed on the phone. I thaught it would be no problem, but when I tried to install some other applications from the market they didn't download. Then I tried to connect my phone to my computer to check the product code in Kies, but my computer didn't recognize my device, neither did Kies. I flashed to JM6, hoping that would fix the problem, but after following the same steps as I did after I flashing to JM7(applying voodoo,wiping data) and booted my phone, the applications were still installed and my phone was still not recognized by my computer! So now I can't connect my phone to my computer and I can't wipe the data and cache, although it seems to work when I'm in recovery mode. Can somebody please help me? I really don't know what to do now..
Thanks in advance,
Jasper

Do a factory reset in Settings > Privacy.

BaalBehrit said:
Do a factory reset in Settings > Privacy.
Click to expand...
Click to collapse
Doing right now, I'll post the results in a moment.
[Update]
The applications have been removed, but my computer does still not recognize my phone. Any advice?
[Update]
Flashing to JM7 at the moment, maybe it'll work now.
[Update]
I can connect my phone to my computer now. Thanks

Bump!
I just updated my post saying everything was working fine, but right after I flashed the Voodoo lagfix to my device the same problems occured again. Almost 100% sure Voodoo is causing them! Anyone else experiencing these symptoms?
Now I'm 100% sure. I connected my phone to my computer, turned my phone of and rebooted into download mode, flashed Voodoo onto it, rebooted and tried to connect again. Didn't work

you should join #project-voodoo on freenode ( IRC even on webchat.freenode.net )
as the developer says:
<curio_> forum is really innefficient for beta debugging kind of stuff

Ok, let's be clear.
Voodoo lagfix can't do harm to your phone.
Beta 1 meant to be a private beta, beta 2 will deal better with some stupid scenarios when you flash something and then something else etc..
Voodoo causing problems connecting to computer and wiping data < WTF is this topic title
I removed beta1 from the download site.

very misleading title , im sure you could have picked some nicer words for it considering supercurio hasnt released anything yet and you used a private beta file which is private for a reason, its still being tested.

I do have to say that I've had some issues with my computer connecting via USB. It only works through Kies- ADB gives me a device not found whenever I try to use it (Yes Kies is closed =P and it's in debug mode). I also have been unable to mount drives for mass transfer.
I had chalked this all up to running a Captivate with a I9000 kernel though- and it still might be, just figured I'd chime in since it sounds like someone has a similar problem- but what can you expect? It's beta 1 Just something to look out for curio in case it ISN'T just because of my unholy amalgamation of firmware pieces
No wiping of my data though =P

hmmm works fine here.
Although b4 doing all these I did do a full format of internal storage and factory reset. I did the hard reset through the service mode codes as well.
Everything's working smoothly and I do have the voodoo fix as well

Voodoo is in private beta!! You should not mention it on the forum I think, especially when discussing issues...someone should remove this thread asap! Issues with it should be discussed on irc only as per developer request (and better feedback also)! ...you should also apologize to supercurio who is working very hard for us all...
Sent from my GT-I9000 using XDA App

Forum Fail.

could you clarify the intention of your thread? this is a private beta, by downloading and installing it you are implicitly agreeing to be a tester, and report issues on the irc. This would cause unnecessary noise. mod should remove this thread.
japperrrr said:
Bump!
I just updated my post saying everything was working fine, but right after I flashed the Voodoo lagfix to my device the same problems occured again. Almost 100% sure Voodoo is causing them! Anyone else experiencing these symptoms?
Now I'm 100% sure. I connected my phone to my computer, turned my phone of and rebooted into download mode, flashed Voodoo onto it, rebooted and tried to connect again. Didn't work
Click to expand...
Click to collapse
Sent from my GT-I9000 using XDA App

Well, if it cause you problem, then don't install. This is BETA release!!! It is absolutely ludricrous to give such a sweeping statement that xxx cause this or yyy cause that. There is a reason the dev has not released it here.
Just because it worked for others, and you can't get what you want, and just start ranting. This won't do, OP! Go figure....

100% agree with others that this topic is totally out of line. It's a private BETA - report the issues to the dev in the appropriate place.
Zilch25 said:
I do have to say that I've had some issues with my computer connecting via USB. It only works through Kies- ADB gives me a device not found whenever I try to use it (Yes Kies is closed =P and it's in debug mode). I also have been unable to mount drives for mass transfer.
Click to expand...
Click to collapse
I have had issues connecting my SGS to my Mac via USB since day one out of the box. The drivers on the phone are flakey, in my opinion.

distortedloop said:
I have had issues connecting my SGS to my Mac via USB since day one out of the box. The drivers on the phone are flakey, in my opinion.
Click to expand...
Click to collapse
Yeah that's also true, though it never manifested before this point. I never bothered to report this to supercurio because I'm not even using the hardware that's compatible with the kernel in the first place It's working fantastically anyway, I just figured I'd throw my 2 cents into the hat that it's worth keeping an eye out for just in case it *isn't* related to my cross pollination of firmwares.
Keep up the fantastic work supercurio I've nothing but good things to say about the project and the performance on my phone!
OP: You might want to change the thread title to something a little less scary =P It kind of paints the project in a negative light, and most people won't read through the thread to see what's really going on.

delete thread.

The people who are blaming me for starting a topic to report a bug in the Voodoo lagfix should read my startpost. I was experiencing problems with recovery mode and connecting my phone to my computer, and could not find another topic about it. That's why I started this topic, not to report bugs in Voodoo. After I found out Voodoo was causing it, I changed the topic title to possibly warn other people who're using of planning to use it.

japperrrr said:
The people who are blaming me for starting a topic to report a bug in the Voodoo lagfix should read my startpost. I was experiencing problems with recovery mode and connecting my phone to my computer, and could not find another topic about it. That's why I started this topic, not to report bugs in Voodoo. After I found out Voodoo was causing it, I changed the topic title to possibly warn other people who're using of planning to use it.
Click to expand...
Click to collapse
Wow, you sounded so noble. :speechless:

trash it!/change title/ erase post.
First rule of closed beta: you dont talk about closed beta.
Second rule of closed beta: you dont talk about closed beta.
Third rule of closed beta: you dont talk about closed beta.

xan said:
trash it!/change title/ erase post.
First rule of closed beta: you dont talk about closed beta.
Second rule of closed beta: you dont talk about closed beta.
Third rule of closed beta: you dont talk about closed beta.
Click to expand...
Click to collapse
Didn't know it was a closed beta since I downloaded it from another forum where no one said it was.. Sorry?

[Q] Custom ROM that allows adb debugging?

Hi,
I develop Android app, last time i tried, some custom ROMs disable debugging via eclipse and adb.
What ROMs are recommended for a developer like me?
Thanks

kenyi25 said:
Hi,
I develop Android app, last time i tried, some custom ROMs disable debugging via eclipse and adb.
What ROMs are recommended for a developer like me?
Thanks
Click to expand...
Click to collapse
I have been pulling my hair out trying to figure out why I can no longer connect to my Desire HD via eclipse since I rooted my phone two days ago and installed the virtuous unity rom. It connects temporarily then gives the following errors:
Code:
[2011-06-29 23:23:44 - adb]This application has requested the Runtime to terminate it in an unusual way.
[2011-06-29 23:23:44 - adb]Please contact the application's support team for more information.
[2011-06-29 23:23:44 - DeviceMonitor]Adb connection Error:An existing connection was forcibly closed by the remote host
I can open up a shell and type commands on the device, but the debugging doesn't work. When you google these errors it is usually people not having enabled usb debugging on their phone. I have of course done this.
I spent a large amount of time uninstalling droid explorer and moving adb.exe and adbwinapi.dll's around today trying to fix this issue before realising it's the phone not the PC.
I took my wifes HTC ChaCha with stock ROM, connected it and it works fine in eclipse, same cable, just different phone.
I can't believe as this poster suggests that this is standard with custom ROMs.
I tried the leedroid sense 3 ROM but this too had the same issue. Each time I did a full wipe before installing the ROM, and I installed nothing on the phone before testing.
Whats going on?

Phew, finally somebody with the same issue. Could somebody try Raidroid 1.32.405.6 to see if it works then?
Sent from my Desire HD using Tapatalk

jkoljo said:
Phew, finally somebody with the same issue. Could somebody try Raidroid 1.32.405.6 to see if it works then?
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Hi jkoljo,
Thanks for the suggestion. I tried Raidroid 1.32.405.6, but unfortunately I had exactly the same issue.
I also tried the suggestions in the following thread which suggested setting persist.service.adb.enable=0 in default.prop, but this didn't work either.
http://forum.xda-developers.com/showthread.php?t=1051798&highlight=adb
Any other ideas? I'm willing to try anything you can suggest. It's really weird that even with an almost stock ROM the issue is still there...

CheesyPeteza said:
It's really weird that even with an almost stock ROM the issue is still there...
Click to expand...
Click to collapse
Exactly. There is basically no additional mods in raidroid, only root. Does it have unsecured boot.img? So if you go to terminal emulator (get it from market), does it open up with $ or #?

It starts with $, but if I sudo to root I get the superuser app requesting permission then I get root with the # prompt.
I thougt that was the way it was supposed to work, should I be going straight in as root? Should I uninstall the superuser app?

OK. With everything else ruled out clutching at straws I tried taking the sdcard out and it started working!
I put the sdcard back in and immediately it stopped working.
So it's something to do with the sdcard...
This should be solvable through a process of elimination.
I need to go to bed now, but tomorrow I'll try a spare completely blank sdcard and start the elimination process from that. Hopefully it is just a file on the sdcard causing the problem, not the presence of an sdcard itself.

I spoke to soon, looks like I just got lucky and it happened to work when I took the sdcard out. Occasionally it will work for a minute then it will stop working again. I'm no closer to solving this.

Same issue
I have installed custom ROM on my SPICE MI 270 and it does not connect to ADB. Though it showed only once in the "list of devices" but thereafter i have never been able to connect it. Please help.

ajparag said:
I have installed custom ROM on my SPICE MI 270 and it does not connect to ADB. Though it showed only once in the "list of devices" but thereafter i have never been able to connect it. Please help.
Click to expand...
Click to collapse
Unfortunately, you're in the Desire HD forums, so it's hard to help you when you're using different hardware. For all I know, the Spice MI could have known ADB connection problems. I would recommend finding forums specific to your hardware.

[Q] Android Falls Over in Revovery Mode

First of all let me say THANKS to all of the dedicated folks on this website that I have found to be most useful while looking for help.
My problem may have been discussed previously, but after doing much browsing I must not be using the right keywords to find a resolution.
I am having issues with a SGH-i747 running stock 4.3 that I just purchased, so I have no clue what may have been done to it in the past.
So as the title says - The green android while booting into recovery mode just falls over with red triangle, and underneath it flashes - No command - Error - No command.
Also if I do try to flash anything - I get several RED errors in a row basically saying - E: No data folder found and a few other things before it quickly reboots and I can't see what the other errors are.
Would appreciate any ideas you folks may have - Thanks.

TWRP had an Odin flashable .tar. If you need recovery you should be able to just use that or terminal command to install.

Odin Fails Too
BCSC said:
TWRP had an Odin flashable .tar. If you need recovery you should be able to just use that or terminal command to install.
Click to expand...
Click to collapse
This is how I discovered the android falling over issue.
While attempting to install clockworkmod.tar through Odin which will PASS
But then when entering recovery mode I get the stock recovery with green android falling over & data errors.
I have performed this same procedure on my other phone which is identical make and model but starting off with stock 4.1.2 without any issues.
I have also tried flashing philz_touch_6.0.7.9-d2att.tar.md5, but that creates a whole new set for errors & fails.

Deeeno said:
This is how I discovered the android falling over issue.
While attempting to install clockworkmod.tar through Odin which will PASS
But then when entering recovery mode I get the stock recovery with green android falling over & data errors.
I have performed this same procedure on my other phone which is identical make and model but starting off with stock 4.1.2 without any issues.
I have also tried flashing philz_touch_6.0.7.9-d2att.tar.md5, but that creates a whole new set for errors & fails.
Click to expand...
Click to collapse
Push it in Terminal Emulator app. Instructions here. http://forum.xda-developers.com/showthread.php?t=2170635&highlight=recovery+terminal. This forces it top the memory block, so should work. I'm asuming the phone boots and you are rooted.

BCSC said:
Push it in Terminal Emulator app. Instructions here. http://forum.xda-developers.com/showthread.php?t=2170635&highlight=recovery+terminal. This forces it top the memory block, so should work. I'm asuming the phone boots and you are rooted.
Click to expand...
Click to collapse
Boots up just fine & Unlocked, but is not rooted yet - This is why I tried getting clockworkmod.TAR & CWM_SuperUser_v3.0.7 (1).zip flashed.
But my main concern is getting the android falling over issue fixed at the moment, and I think the rest will resolve itself once that's accomplished.
I realize I am no rocket scientist with android phones (Galaxy S3), or I wouldn't be looking through these help forums, and asking for advice.
But it seems to me it's like fixing your car - You need to figure out the root cause of the issue rather than putting band aid patches on it.
Seems like the operating system has other issues to deal with other than obtaining root access at the moment, or it wouldn't keep giving me errors stating that it can't access the DATA files.
Maybe my way of thinking is way off base? Thanks for all your input anyways & I will click the THANKS button if it lets me.

Deeeno said:
Boots up just fine & Unlocked, but is not rooted yet - This is why I tried getting clockworkmod.TAR & CWM_SuperUser_v3.0.7 (1).zip flashed.
But my main concern is getting the android falling over issue fixed at the moment, and I think the rest will resolve itself once that's accomplished.
I realize I am no rocket scientist with android phones (Galaxy S3), or I wouldn't be looking through these help forums, and asking for advice.
But it seems to me it's like fixing your car - You need to figure out the root cause of the issue rather than putting band aid patches on it.
Seems like the operating system has other issues to deal with other than obtaining root access at the moment, or it wouldn't keep giving me errors stating that it can't access the DATA files.
Maybe my way of thinking is way off base? Thanks for all your input anyways & I will click the THANKS button if it lets me.
Click to expand...
Click to collapse
I understand exactly what you mean, but root access can be a key to you here. Your recovery is broken or at least something in a system file is harming what recovery is trying to do. Problem is these are not accessible without root. Root is not the band aid, it's the scalpel Try fixing that car without wrenches. The problem with recovery is that it is protected. You could flash a new stock one as part of an official firmware, but if you are stock 4.3 you are going to run into bootloader issues (nevermind the fact that Samsung hasn't released one. This leaves your other fix as replacing your recovery and requires access to the root system files.
++On another note, I just found this and don't want to delete everything I just typed. See this thread here and see if it pertains to you. http://forum.xda-developers.com/showthread.php?t=2520115
Either you or someone else have already installed a custom recovery. Without root access recovery will fail, the android will fall and you will see red. Use this to root and fix your phone...http://forum.xda-developers.com/showthread.php?t=1963790

Good point on having no wrenches to fix the car --- I will head your advise, and move forward with getting it rooted.

BCSC said:
the android will fall and you will see red. Use this to root and fix your phone...http://forum.xda-developers.com/showthread.php?t=1963790
Click to expand...
Click to collapse
You nailed it on the head - I'll be sure to also hit the Thanks tab for chainfire also since he deserves credit also.
CF Auto Root did the trick and the poor little green android no longer falls over.
Moderators can mark this thread as resolved & Thanks again for all your help.

XT1789-04 Wireless is missing

I've done many dumb things to this phone but I've finally found something I have not been able to recover from. Let's start with the list of things you guys will have me try that I've already done.
- FlashAll to the latest as well as the "Return to Stock" thread here on XDA
- Lenovo's Recovery Tool (I thought someone on XDA might be wrong about something and went with the Mfg's software, sorry I doubted you guys.)
I'm using linux so I convert your Flash bat to an sh but I've never had issues doing so before. I've rooted this and three other phones and I'd like to think I know what I'm doing I've spent about two weeks on here and other Android forums but this time I need to actually ask for your help.
Now on to my issue.
I installed Lineage OS using their lovely guide and everything was great until I found out my WiFi isn't working. Well can't have that, return to stock! Oh my WiFi is still dead. Wait now I can't even enable dev options because I cannot get past the initial setup without WiFI. OK full reset wipe and restore. Nope nothing doing.
It shows MAC unavailable in the initial setup. adb shell over via recovery shows no wlan0 then I tried TWRP and also OrangeFox because I saw a similar fix with it. I try ip link show but ip isn't there tried to su but it's not going. I think I have eveything mounted right but I'm more Arch than Android :\
And in 5 seconds someone is going to link a thread on here I couldn't find in the search with a easy 3 step procedure. But just in case that doesn't happen feel free to ask for any logs.

I'm a dumb. Be sure you do the Pre-install instructions as these are what fixed my issues.

Hi, is your phone ATT version? Thanks.