yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Q&A, Help & Troubleshooting] khukman:
Me too

:(

My phone has also been experiencing the loss of 3G service as well. I checked my wife's Moto Droid 1 and it was also having difficulty connecting as well. I called Verizon and they were absolutely no help whatsoever. I am either getting nothing or 1X in places where I have always had 3G. This is very frustrating. I have flashed 3 different ROMs (all of which have worked fine in the past), but the result always seems to be the same. Anyone else out there with this issue?
[Droid Incredible Q&A, Help & Troubleshooting] Shaundiesel:
Someone help! Same issue! I can no longer get data....PERIOD. I have to stay connected to wifi, or I don't get my emails, internet, etc.

Need to fix this!
[Droid Incredible Q&A, Help & Troubleshooting] khukman:
3G connection issues

I just got off the phone with Verizon Tech support. They are CONVINCED that it is an issue with my phone (and my wife's). Gee, how can 2 different phones, from different manufacturers have the SAME issue at the SAME time? Hmm, doesn't sound very promising to me.

They are sending out a replacement for my wife's Moto Droid to see if it is a phone issue (she has been having other issues with it anyway...). If hers improves, I may send mine back, but I don't want to have to unroot, etc. Plus I like the Super-Amoled screen :(. When did trouble-shooting turn to "replace the hardware first" ???

Regards!
[Droid Incredible Q&A, Help & Troubleshooting] XideXL:
This happened to me recently as well and was fixed with a factory reset.

I am rooted with S-off, so a normal factory reset via Menu->Settings->SD & Phone Storage-> Factory Data Reset didn't go well for me. Not sure of the exact reason, but I just followed the instructions in this post to restore: http://xdaforums.com/showthread.php?t=786436

Programming your phone by dialing *228 is necessary afterwards as well, as khukman states below. Thanks for pointing that out.

After I completed this, I redid root, restored my nandroid backup and didn't lose a thing, plus my 3G is working again!

*A fair warning: Doing this formats the internal storage (emmc). I'd recommend backing up any photos, music, etc that you have stored on emmc before doing this!

Sent from my Droid Incredible
[Droid Incredible Q&A, Help & Troubleshooting] khukman:
So I tried the above suggestion about going back to completely stock 2.2 and I have the same results. On one hand, I am now back to S-ON and stock Froyo, so if I want to send it back to Verizon, they are none the wiser that I was rooted, but on the other hand I STILL HAVE CRAPPY 3G SERVICE!!! Man, I feel like I'm on AT&T or something LOL! I'll keep an eye on it for the rest of the day and see how it does and report back.
[Droid Incredible Q&A, Help & Troubleshooting] khukman:
Back in 3G!!!!! :)

After getting back to stock Froyo, as described in the previous post, I was still unable to get a good 3G lock. I read in another thread where someone did a 'Factory Data Reset' and it took care of it. When you do this, you have to dial #228 and let it program your phone as it did the first time when you got it. Once I did this, I had (and still have) a solid lock on 3G like I used to. I think that it was one of the Sprint ROMs that screwed this up in the first place (the OP states that you have to backup your PRLs, etc. before installing, then re-install them afterwards). I can't remember if I did this or not, so it may be my fault after all, but regardless, I am thrilled that once again I have a connected smartphone thanks to the resources contained on XDA!

Regards!
[Droid Incredible Q&A, Help & Troubleshooting] Gornul:
I myself am now rocking a refurb that has no trouble at all... A complete revert to stock did absolutely nothing to resolve my trouble.

Though I didn't try doing a factory reset AFTER reinstalling the stock ROM. Hmm. Maybe there was something in the cache still. I suppose in my case I'll never really know, but I'm glad you guys were able to resolve the situation with your original hardware.
[Droid Incredible Q&A, Help & Troubleshooting] XideXL:
Did you follow the steps in the thread I posted above? Doing that should completely format and re-image your phone. Much more than just installing a stock ROM. I myself tried so many different variations of ROMs, radios, etc and nothing did the trick until I followed that thread.

Sent from my Droid Incredible
[XPERIA X10 Themes and Apps] RichyH:
It has been posted in a few other forums, but I didn't want the X10 users to miss out on this great app.

I was a big fan and frequent user of MPE for my w810i.

With my X10 & X10 Mini Pro really misses that app.

But version 1.8.0 now supports Android.

Tried it today an it works like a charm.

And best of all .... it's for free ...

Thanks to freya09 for the heads up.
[XPERIA X10 Themes and Apps] qwer23:
don't think I'll use it, but for everyone interested, here's the link: click
[XPERIA X10 Themes and Apps] Shiwantha:
MyPhoneExplorer was simple and effective. i missed it when i migrated to android. thanks for the information im sure more people will enjoy this information.:)
[XPERIA X10 Themes and Apps] black97one:
yes it's very usefull!!:D
[Windows Mobile Development and Hacking General] fishel:
I am trying to make make a simple program in Visual Studio 2008 (VB) for Windows mobile 6 and cant find a clear example of how to read a reg key value.

If this is the wrong venue please let me know. This is my first attempt in writing a program for WM

Thanks
[Windows Mobile Development and Hacking General] lyriquidperfection:
Hi mate seeing how ignorant everyone seems to be in here lately check out this link:

http://www.dreamincode.net/forums/topic/31219-working-with-the-windows-registry-in-vbnet/

This gives code snippets that you can easily be changed and turned into your own class.

BR

Gaz
[Windows Mobile Development and Hacking General] fishel:
Thanks. That got me going...on my way.
[EVO 4G Q&A, Help & Troubleshooting] fireguy0306:
So my EVO seems to have bad blocks in BOOT, i can't flash a few of these roms as i get various "line #" errors when writing to BOOT. It seems to be bad blocks, but i'm not 100% sure.

If it is bad blocks is there anything i can do besides get a new EVO??
[EVO 4G Q&A, Help & Troubleshooting] jimbobtexas:
How much free space is there on your SD card? You might need to just free up space...
[EVO 4G Q&A, Help & Troubleshooting] Calkulin:
Easy fix would be to change the update-script in the zip to a updater-script and it should fix those line issues
[EVO 4G Q&A, Help & Troubleshooting] fldash:
Nothing you can do. Flash memory is shipped with bad blocks many times. You'll have to get a new EVO. You can try warranty, but I think all the released kernels will fit just fine in the boot partition regardless of bad blocks.

Edit: meant to say officially released kernels...
[EVO 4G Q&A, Help & Troubleshooting] snandlal:
Try flashing mtd-eng.img to the misc partition
[EVO 4G Q&A, Help & Troubleshooting] fireguy0306:
The SD card has about 8gb free. I have been wanting to try the different ROMs, i like CM6, but i'm up for a change. The issue is i get various line errors on "writing BOOT".
[EVO 4G Q&A, Help & Troubleshooting] snandlal:
Yes writing boot errors...flashing mtd-eng.img will help

This is not a rom it is engineering partition
[EVO 4G Q&A, Help & Troubleshooting] fireguy0306:
Alright,

The way i understand it, this is already done as i did a full root and not an unrevoked root. Is there something i'm missing?

Thank you

EDIT: After double-checking i do have the Engineering Bootloader, and RA Recovery
[EVO 4G Q&A, Help & Troubleshooting] snandlal:
Im not gonna say anymore...if you dont wanna re-flash it, as sometimes needed, then dont...bad blocks....what do you think mtd-eng.img flashes?...good luck to you
[EVO 4G Q&A, Help & Troubleshooting] fireguy0306:
Alright, i appreciate it, as i was not aware.

I will try this now.
[EVO 4G Q&A, Help & Troubleshooting] fireguy0306:
Alright well i reflashed the bootloader, still getting errors when i try and load certain "larger" ROMs....boo i'll have to find a way to get a new EVO.
[Droid 2 General] spaceragnar:
I know it might be a dumb questioh but do custom roms do after u root?
[Droid 2 General] theecho:
yes would have to have root before running a custom rom.
[Droid 2 General] JDunc:
Maybe your asking what do custom ROMs do after you root?

They do whatever the dev was after doing. Epic removes alot of bloatware(unwanted apps) and Moto blur widgets.
[Touch Diamond2, Pure General] amcd1982:
Hi guys

While looking through my registry using Total Commander, my phone had a little fit and decided to rename a folder. I didn't see what the folder was called before my phone called it ,, and then crashed.

Now nothing is working properly, such as Comm Manager or my signal, I assume because they are pointing to the folder that has been renamed, and which needs to be changed back to what it should be called.

I would attach 2 pics of the problem - the first of the parent folder and where it sits in the registry, the second of the folders that appear in the problem folder - but as a new user I can't, so hopefully I can PM these?

Does anyone have any idea what the folders in \\\registry\HKLM should be called so I can change it back to what it should be? All I know is that it starts with a letter around m-p.

I really don't want to have to hard reset.

Thanks in advance for your help!
[Touch Diamond2, Pure General] Bruce Inman:
You have;

MUI

, contains 2 keys for SysLang

nls

, contains subfolder Overrides

Platform

, contains 2 keys for Provxml
[Touch Diamond2, Pure General] amcd1982:
I've got the MUI folder already, but thanks for replying
[Touch Diamond2, Pure General] Bruce Inman:
What about nls and Platform?

You said m-p, right?
[Touch Diamond2, Pure General] amcd1982:
I have those as well. I assume it's m-p due to what folders I saw before it crashed. I guess it could be a folder around that area though

Cheers for your help
[Touch Diamond2, Pure General] amcd1982:
I gave in - hard reset it was!
[Epic 4G Android Development] mkasick:
Update: One click root has been using this "simple" method since version 2.2.7. If you're rooting your phone for the first time, please try that first. Consider this thread to be purely informational for those who want step-by-step details of how the process works.

I've been suspicious of the joeykrim root method since it was first posted at SDX. I finally got my Epic yesterday and confirmed that is, indeed unnecessary. I don't fault joeykrim though, he ported the working root method from the Moment to the Epic without actually having access to an Epic himself.

Anyways, the joeykrim root method is unnecessarilly complex becuase it works around an RFS permissions bug which loses the setuid bit on the Moment. It appears the Galaxy S phones have this bug fixed, which is why the root methods on the I9000, Vibrant, Captivate, Fascinate, etc., are much simpler.

So, for the simple root:

First, make sure joeykrim root is not installed.

Upgrade to DI18 (not strictly necessary, but you'll want to do it).

Setup a working adb from the Android SDK and whatever drivers are necessary for your platform.

Download rageagainstthecage-arm5.bin from the C skills blog (link removed due to my newbieness) or from any of the one-click root packages.

Download su-2.3.6.1-ef-signed.zip and extract "system/bin/su" and "system/app/Superuser.apk" to a temporary directory you'll be working from.

Enable USB debugging on your phone and connect it to your computer.

Now, open a command prompt/shell on your computer and cd to the appropriate temporary directory. Run:

adb push rageagainstthecage-arm5.bin /data/local/tmp
adb shell chmod 755 /data/local/tmp/rageagainstthecage-arm5.bin
adb shell /data/local/tmp/rageagainstthecage-arm5.bin

and confirm you have a working root shell. Then continue with:

adb push su /system/xbin
adb shell chmod 4755 /system/xbin/su
adb install Superuser.apk

That's it! You should have a working root via su & the Superuser package. At least, I did.

Note that the preceeding steps installs Superuser.apk to /data, which is what I prefer to do. This means if you do a "Factory data reset" su will be temporarilly broken until you reinstall the Superuser.apk package. Since installing the package itself doesn't require root, this is easily done after a /data reset.

Also note that I did not perform a /system remount-rw anywhere. At least on my Epic, /system appears to always be mounted read-write so it's an unnecessary step. It's actually the "joeykrim-root.sh" script that remounts /system read-only during the boot process, which is why folks who don't use root kernels have run into this problem before. I'm not sure why joeykrim's script does that, I guess he probably assumed /system is mounted read-only by default. There's arguments that /system should be read-only, but I didn't touch it in case some Samsung stuff depends on it being read-write.

Finally, if you're already rooted via joeykrim or are running a root kernel, there's nothing really to be gained by doing this. I'm just throwing this out there as I perfer to make the minimum invasive changes possible to obtain root.
[Epic 4G Android Development] ZenInsight:
Wow, that was really informative. To check for Super user you:

Type: adb shell

then type: SU

You should get a # sign if you have root. Correct?

In the original Noobln post method would the Epic keep root even after a wipe therefore not needing to re-apply the superuser apk again? That might be a reason why folks would want to go the more invasive route (considering rooters seems to change ROMS fairly often which requires wipes sometimes). Either way, keeping a copy of the apk file on your SD card is no big deal.
[Epic 4G Android Development] jimmyz:
This explains a lot of problems! thanks

EDIT- another noob question- why do you prefer to have superuser installed to /system/data- why not put it in /system/app? Also if I want to install busybox where is the best location to put it?
[Epic 4G Android Development] mkasick:
Once you run rageagainstthecage-arm5.bin, you should get a root-shell automatically every time you run "adb shell" after until you reboot the phone. Yes, you can tell it's a root shell since it uses the "#" prompt. This is the important part to check, since if the exploit doesn't work, you'll have to run it again. But I haven't seen it not work.

After su is installed and you reboot, your steps are correct: run "adb shell", run "su", then you'll be prompted on the phone scren to authorize access and once you allow it you'll end up with a "#" prompt.

noobnl installs Superuser.apk to /system, you can do that here too. Just replace the "adb install Superuser.apk" step with "adb push Superuser.apk /system/app". It's independent of the joeykrim scripts.
[Epic 4G Android Development] jhnstn00:
With my captivate we have many update.zip root methods to choose from. Any chance this will be coming to the epic? Have a friend with an epic and command lines would be too much and one click didn't work.
[Epic 4G Android Development] mkasick:
I prefer to keep consistent with the idea that user-installed applications go in /data, and stock-installed-and-unmodified applications remain in /system/app. This way, upgrading Superuser.apk doesn't require a root-shell/root-explorer, you can remove it or upgrade it the way you do with any user installed application--adb install, side-loading via an sdcard, or downloading it from the market.

Plus, in general I prefer to keep my /system as untouched as possible. For example, I don't remove stock apps either. The "su" binary has to be installed in /system to persist after a /data wipe, and busybox is best installed to /system so it's in PATH (haven't looked into modifying the default PATH yet). Otherwise I try to keep /system alone.

Android's default PATH provides four places for busybox to be installed: /sbin, /system/bin, /system/sbin, and /system/xbin. /sbin is part of the initramfs, in other words it's controlled by the kernel you're running. You can install busybox to any of the three /system/*bin directories, but I prefer /system/xbin.

In the traditional Unix conventions, "/usr/bin" is for user-runnable stock-installed programs, and "/usr/sbin" is for root-requiring (superuser-runnable) stock-installed programs. "xbin" isn't part of the standard convention, but I'd guess it's intended for "extra binaries" that are not part of the stock installation (much like /usr/local/bin), thus it seems like an appropriate location for a user-added "su" and "busybox" programs.

The second reason is that "xbin" is relatively empty, so if you want to create the applet symlinks (i.e., so that you can call "cp" instead of "buybox cp") it won't overwrite the stock toolbox symlinks. Also, since "xbin" is last on the default PATH, any programs provided by both toolbox and busybox will default to the toolbox version--which would be important for stock system scripts that might run into compatibility issues if they were to use the busybox versions instead.

To install busybox, grab a copy of the binary from somewhere (one click packages, a copy of stericson.busybox.apk, etc.). Then, once rooted run:

adb push busybox /data/local/tmp
adb shell
su # Authorize on phone screen
cat /data/local/tmp/busybox > /system/xbin/busybox
chown root.shell /system/xbin/busybox
chmod 755 /system/xbin/busybox
rm /data/local/tmp/busybox
/system/xbin/busybox --install -s /system/xbin
[Epic 4G Android Development] mkasick:
I don't believe so. The I9000/Vibrant/Captivate have recoveries that don't check the signature of update.zip (as I understand, or maybe they do but only require test keys) which makes rooting-via-recovery possible. Unfortuntaely the Epic and Fascinate do perform signature checks, so we can't enable root via stock-recovery.

That said, the Fascinate one-click methods should also work on the Epic. Although depending on why your friend couldn't get the Epic one-click to work, the Fascinate one may not work either.
[Epic 4G Android Development] jimmyz:
You sir are a true gentleman! Thank you for the informative answers- its great to have you over here! I have one more question- why can't I usually push directly to /system ?
[Epic 4G Android Development] mkasick:
Pushing directly to /system requires running the adb service on the phone as the root user, so that it has permissions to write to that directory. Usually adb runs on the phone unprivileged, so you can only push to world-writable directories.

Running rageagainstthecage-arm5.bin actually changes this. The exploit forces the adb service to run as the root user, which is why "adb shell" gives you a root shell and "adb push" to /system does work, until the phone is restarted.

Interesting enough, the adb service also runs as root by default in the Android emulator. So there's probably a configuration setting, somewhere, to make it do that. In general it's safer to run adb unprivileged though, and "su" to move files to /system once uploaded elsewhere on the phoe.
[Epic 4G Android Development] jimmyz:
I am learning a lot!!! Could you take a look at koush's kernel here, with it I noticed that when using adb I got the # prompt right away and was able to push to /system- maybe he was able to figure out the config settings? Once again thanks!!!

one more ? (feel free to ignore this one) what actually happens when you do

adb shell /data/local/tmp/rageagainstthecage-arm5.bin

and how does that give you permanent root?
[Epic 4G Android Development] Firon:
It is indeed a config option in default.prop. However, this is in the initramfs and you can't change it on the fly, so you need to rebuild the kernel to change it. With some work you can modify the stock kernel to do it, but I personally haven't tried it.
[Epic 4G Android Development] AndroidSPCS:
Thank you, this worked perfectly for me, running stock DI18 ROM that I flashed tonight!!! I confirmed by installing the wireless tethering pre-9 apk, and successfully ran the wireless tethering without any errors.

Quick question: do we need to do this after root or is it not needed?

NEEDED?? ===> SuperUser App to help with Security Concerns for the Epic - h**p://forum.sdx-developers.com/epic-development/superuser-app-to-help-with-security-concerns/

Also, Titanium Backup failed to work - it gave an error of denied root access, and said busybox was not installed. What needs to be done to make it work? Do I need to install clockwork mod (not exactly sure what it does though) or a custom ROM?
[Epic 4G Android Development] mkasick:
Not sure exactly what you're asking. This is an alternative to the joeykrim-based one-click roots and rooted kernels. If you already have one of those this isn't really necessary.

Yes, the su binary used here requires the Supruser appto be installed to authorize su requests. Otherwise they'll always be denied. Other su binaries might not require it, but then all apps have root access which isn't really a good thing.

Did you authorize Titanium Backup when the Superuser prompt came up (requies the Superuser app to be instald too)?

Titanium Backup has an option to download and install it's preferred version of busybox. Follow the prompts to do that.
[Epic 4G Android Development] AndroidSPCS:
Thanks, actually this was referring to the thread where the instructions for going to adb shell or terminal and typing in the following commands:

adb shell

su

mount -t rfs -o remount,rw /dev/block/stl9 /system

cp /system/bin/su /system/bin/jk-su

exit

Yes same as above, the question is not whether we need SU app (I know we do), but whether we needed to type the additional commands:

adb shell

su

mount -t rfs -o remount,rw /dev/block/stl9 /system

cp /system/bin/su /system/bin/jk-su

exit

What do these commands do? It seems to me my Superuser app is working fine with wifi tether - popping up with allow / disable permission boxes, etc. Do these commands add something else to Superuser?

There was no Superuser prompt during the install of the app, nor anytime when it said it had a failure with root access. However there is an option to install BusyBox, which I have not done yet, because I am not sure what busybox is, or what it does. I'd like to find out why I need it and what it does, so I can feel comfortable with installing it.

Thanks again.
[Epic 4G Android Development] Firon:
echo "root::0:0:root:/data/local:/system/bin/sh" > /etc/passwd

echo "root::0:" > /etc/group

you need to do that in a shell to make sure su works properly.

I'm updating the one click root right now to be less silly.
[Epic 4G Android Development] Firon:
http://xdaforums.com/showpost.php?p=8543226&postcount=455

I just cleaned up the one click root to not do many of the silly things joeykrim's root does. It also means your system will be mounted as rw after a reboot and it won't overwrite your su with jk-su every boot (no more modified playlogo).

Cleaned up all the old stuff from the root so it should work fine even if you were using one of the older one clicks. I made sure su works, incl titanium backup.

I'm still installing superuser.apk to /system/app because I think it belongs there. :P

Thanks for doing the footwork, mkasick!
[Epic 4G Android Development] jimmyz:
Firon- why are these lines still needed?

adb push playlogo /system/bin/playlogo

what is playlogo? Does this just put the stock one back in case you used the joeykrim method in the past?

adb push remount /system/xbin/remount

Are the remount scripts still needed?

adb shell ln -s /system/xbin/su /system/bin/su

why is this link needed? why cant su just be in xbin

thanks in advance!
[Epic 4G Android Development] Firon:
This is just pushing the stock playlogo, since joeykrim's method overwrites it with some custom script.

The script allows you to easily remount system as ro or rw at will. Why not? :P

I don't know if any apps depend on it being in a particular location. It is in xbin, but I'm also linking it to /system/bin to be safe.