yashsingh1/xdaforums huggingface dataset:
[T-Mobile LG G2x] Minker17:
I decided to get a replacement phone to see if a newer one fixes any of my issues, but I have a few questions.

- It's rooted w/nvflash/CWM. Do I just need to use the nvflash app to replace the stock bootloader, then unroot, then factory reset?

- If I make a nandroid backup before doing this, once I get the new one, can I root it, nvflash it, and then flash my nandroid to it? Or is that not possible?

Thanks guys!
[T-Mobile LG G2x] booch137:
That's exactly what I just did yesterday waiting for my replacement to show up. Stock bootloader -> unroot -> factory reset. Dunno about the nandroid backup, I won't be using mine. I want to start fresh.
[T-Mobile LG G2x] KiNG OMaR:
Nandroids are fine as long as the device your restoring is the same :)
[T-Mobile LG G2x] Minker17:
Just for reference. I got the new phone, rooted/nvflash'd and restored my nandroid to the new device with no issues. I then un-nvflash'd, un-rooted, and did a factory reset to send the old one back to T-Mo.

No issues so far.
[T-Mobile LG G2x] EmceeGeek:
I'm on my 4th replacement and it should be arriving any minute. I just unrooted and reset, like the other person said. With the one I have arriving I'm going to root and restore from my other backup. Its very possible my friends, cheers!
[T-Mobile LG G2x] Minker17:
I just wanted to update again and felt it wasn't necessary to start a new thread.

The replacement I got was significantly worse than my original. It was rebooting every 5-10 and sometimes it would reboot immediately upon rebooting. My rep sent me out my 2nd replacement and it has been up for 21 hours without a single reboot. This time I did not restore my Nandroid and started fresh. Like I said, just wanted to update.
[EVO 4G Q&A, Help & Troubleshooting] tsilenzio:
I am in the process of learning how to modify/develop ROMs. Is it possible to take the Quicksettings from Sense 2.1/3.0 and put it on ROMs that run 2.0/2.1 that currently do not have it?

If so any pointers on how to achieve this? I am still in the learning phase and just trying to learn from what others have done already until I can spread my own wings.

Thank you in advance :)
[HTC Incredible S] Hawkysoft:
Could anyone make me an vendor overlay for the incS aka vivo? ^^
[Galaxy S I9000 Q&A, Help & Troubleshooting] aBONiE:
I'm having a major problem with MIUI (or anything based on CM7 for that matter):

- Can't get signal on MIUI or CM7 no matter what I do. I've tried wiping and reflashing, tried reverting to 2.2 and reflashing from there, I've disabled SIM lock, tried flashing without SIM, then WITH SIM and nothing. It seems as if the phone did not recognize the SIM card in it. (SIM works fine in other phones and also on other roms, it's just CM7)

- Random reboots

Anyone experienced anything like this? Or just heard of someone experiencing anything like this? Or anything really, I'd love to use MIUI, but a phone without signal is seriously gimped...
[Galaxy S I9000 Q&A, Help & Troubleshooting] azzledazzle:
right firstly check that your IMEI number is intact, sometimes this can get corrupted along the way..

if it is fine, boot into recovery, Format /system /cache /dalvik cache - then re flash MIUI in recovery.

if the problem still persists, flash back to froyo again, make sure its a froyo rom - with froyo bootloader (im not sure which)

flash that in odin and start all over again - trust me it will be worth it .

can i just ask what rom did you come from before going to CM7 - MIUI
[Galaxy S I9000 Q&A, Help & Troubleshooting] aBONiE:
Thanks for your reply! First I tried flashing from a kitchen-cooked ZSJPK, and after that EZBase JVE. My IMEI is fine, and I followed all instructions correctly, of that I'm positive, but still CM7/MIUI gets no signal.
[Galaxy S I9000 Q&A, Help & Troubleshooting] jay_993:
As above, check IMEI. If corrupt or unknown, flash EZbase froyo then if going to MIUI, flash RC7 stock. You won't get any signal problems then. If you want to move and update from there, you can but just make sure to format etc.
[Galaxy S I9000 Q&A, Help & Troubleshooting] aBONiE:
Is RC7 a requirement? The link to it in the MIUI thread seems to be down...
[Galaxy S I9000 Q&A, Help & Troubleshooting] aerismel:
I have this problem also with MIUI (1.12.30). I have checked my IMEI and it's good. However, I don't understand what to do now. I'm very new at this. I would appreciate a lot if I could get more detailed explanation. I really need help.

Thank you very much.
[Thunderbolt General] canthus90:
so i live in beaverton and noticed my 4g was on
[Thunderbolt General] canthus90:
ok maybe not.......... i guess they were testing i called and asked they said yes... then they turned it off 45 minutes later so i called a local store they said there just testing in the area
[Thunderbolt General] tmoe:
Testing in Vancouver

They have it on hit and miss across the river here in Vancouver, too. I have it fairly consistently at my house, but lose it elsewhere. The handoff from 4g to 3g is killing me. I lose data entirely for 60-120 seconds with regularity.
[Thunderbolt General] aestibar:
4g on in some spots.

definitely 4g in the pdx (by airport) area. i go to school at ITT tech @ Cascade station, But i live in Vancouver, WA by the mall. I also get 4g at my house. I've been doing some testing and the only areas with 4g turned on are places that have a verizon store near by. i assume that they turned on the closest 4g tower to the stores demostrate 4g speeds.

areas near here that i know have 4g include:

Portland PDX - near the airport (verizon store @ cascade station)

Fishers Landing area in Vancouver (Verizon store on 164th)

Vancouver Mall area (verizon store @ vancouver plaza)

Downtown vancouver (not sure of a verizon store here, but i know there is one across the bridge in Jantzen beach, OR)
[XPERIA X10 Android Development] Eddie_Brock:
With all due respect to the developers who I know have been working hard on custom ROMs for us all to enjoy... How long until we can expect to see a fully working Gingerbread ROM?

It seems that it's the camera holding all of the ROMs back from being fully functional (except for Scamble, which doesn't have GPS instead). I know that with Froyo, this was the final step to be implemented before they were fully functional.

I'm still at 2.1, and would like to wait until 2.3 is fully operational before I flash.
[XPERIA X10 Android Development] ImS0Raw:
If you would like to wait why do you ask it. And why do you even ask it in the wrong forum?
[Captivate General] yamahakid:
my problem is very similar to this: http://xdaforums.com/showthread.php?t=1024733

i took my original captivate, that i got when they first came out in to att yesterday because my lock/power button was giving me problems. They gave me a new phone and i was on my way. i was happy with this phone at first, because the gps was great and the one in my old cappy might has well not even been in there it sucked so bad. When i got home, i set it down on my desk, and it shut off. anytime i set it down without gently placing it on the surface, it shuts off.

it seems that the top corner of the phone, by the camera and charging port is the most sensitive; i can tap it with my finger and the phone turns off.

has anyone else had this problem? my original captivate had the actual random shutdown problem, but when i flashed any roms besides stock, that went away, and that is not the case with this phone. AT&T are sending me another phone, but i was just wondering if anyone else has experienced this.
[Captivate General] diablo009:
Best bet, get it replaced. Could be loose connections anywhere inside the phone.
[Captivate General] faroid:
After I had my battery replaced I started having shutdown issues so I figured the battery could be loose. I put a piece of paper to hold it tight to the back cover. since then never had a shutdown.
[Captivate General] phatninja13:
Yeah sounds like a loose connection object the battery. Best to just get it replaced or buy a new battery. If the new battery doesn't fix it you will still have a spare.

sent from a cabin in space using GR-10
[Nexus S Q&A, Help & Troubleshooting] fraspas:
Hi, I just registered on this forum hoping to learn the ins and outs of rooting. Been doing a lil research reading a couple of sites on the topic. Bear with me, but I feel like a complete noob cause a lot of the language is sailing straight over my head. I think I have the gist of it, but it seems a lot of the information are scattered and there's a lot of different ways to root.

I just recently got the Nexus S (Sprint's 4G version) and I have been reading some of the ROMs aren't compatible with the 4G version yet. This has me a little worried...would rooting the phone be any different since its a 4G model? I really don't want to brick my phone on my first try. Is there a comprehensive guide with easy step by step instructions on how to root this particular version of the phone?

I do agree the 4G version needs its own tab to prevent confusion since a lot of the guides here are for the regular Nexus S. Many thanks in advance.
[Nexus S Q&A, Help & Troubleshooting] mzahiri:
If you look in the developers section there is a sticky at the top for the Sprint variant of the Nexus S. In it there are rooting instructions and such.
[Nexus S Q&A, Help & Troubleshooting] krohnjw:
It's actually quite hard to brick the Nexus devices. The gist of it is as follows:

Boot into fastboot (hold pwr up and turn the phone one).

Fastboot oem unlock to unlock the device (this wipes)

Install a custom recovery via fastboot (fastboot flash recovery downloaded-image.img)

flash the su binary package via recovery

This is the same process for all variants of the phone - there's nothing 4G specific about it other than don't try to use an old version of CWM (the i9023 can't either).

Guides are here for the 4G though: http://xdaforums.com/showthread.php?t=1071500

The only way you are going to brick your device is:

- Flashing a GSM radio to your CDMA device

- Pulling the battery DURING a radio flash

- Using ODIN and flashing a full rom package not meant for your device.
[Nexus S Q&A, Help & Troubleshooting] tailsthecat3:
pretty sure I used this guide.

http://theunlockr.com/2010/12/17/how-to-root-the-samsung-nexus-s/

then i deleted a bunch of stuff i had no use for and am happy.

good luck
[Nexus S Q&A, Help & Troubleshooting] derekwilkinson:
I've actually seen people unbrick after flashing the wrong radio... LOL pretty amazing.
[Nexus S Q&A, Help & Troubleshooting] dazednconfused:
I could really use some help please. Im using these guides to root and I've gotten the bootloader unlocked, but when I get to the part where I flash CWM recovery in the command prompt, I get a message that says:

cannot load recovery-clockwork-3.0.2.4-crespo

That is the file they said to download, and I inserted it into the tools section of android sdk folder. Any ideas? The unlock bootloader command worked perfectly, but Im getting stuck at this step.

EDIT: I figured out my problem. I wasn't placing the recovery file in the Platform-tools folder, I was putting it into the regular tools folder. I have my moments.
[Nexus S Q&A, Help & Troubleshooting] wild1z:
Make sure you rename the image too. :)
[Nexus S Q&A, Help & Troubleshooting] dazednconfused:
I finally got it. Worked like a charm once I figured out what I was doing wrong. Do we still have to rename the file (install-recovery.sh and rename to install-recovery.sh.bak) in root explore to make it stick? I have rebooted several times and it is still there so I was just wondering.
[Nexus S Q&A, Help & Troubleshooting] fraspas:
These are pretty great instructions, especially the link. Since Sprint shipped with version 2.3.4 of Android with the build GRJ22, do the rooting instructions still work for our model?
[Nexus S Q&A, Help & Troubleshooting] wild1z:
Got no idea. I was referring to renaming the clockwork image file. But I think you answered your own question since root has um... rooted. :) Cheers.
[Nexus S Q&A, Help & Troubleshooting] wild1z:
I rooted mine just fine. You should be good.
[Nexus S Q&A, Help & Troubleshooting] fraspas:
Which method did you use? I'm reading a lot about bootloader being unlocked/locked and some methods requiring a backup and some without. This really adds to the confusion. Then there's a Superboot method which seems a lot easier but it doesn't seem to have the GRJ22 model. I'm pretty sure its easy once I get to it, but the overwhelming information makes it extremely difficult to follow lol. Information overload.
[Touch Cruise Android Development] ktutza2006:
i'm running froyo with 2.6.25 kernel. is there a way for microsd card to work? astro file manager see it, i can acces it there, but the android sistem don't detect it. in setting it appears to be unavailable, when i try to transfer something on bluetooth or so acces gallery, i receive a message to insert a card.

Does anyone know a fix for that?
[Xoom General] Gr3yghost:
After several unsuccessful attempts to mount 3.1 on my Xoom, something seems to have caused the display to reverse. That is, the display is a mirror image of what it should be! This starts with the boot-up image of the Motorola Icon and carries all the way through till it's up. Several restarts have failed to resolve it, and it has me in a bit of a panic. :confused:

Have I just bricked my Xoom? Has this happened to others? Ideas? Suggestions? There's nothing on it that I have to save, so I could re-flash it, but I am not sure if/how to do this.

Many thanks in advance for any suggestions/fixes!:)

Phillip
[Xoom General] csseale:
Its not bricked if it boots...

That is strange though. May have to reflash stock images.
[Xoom General] djsaad1:
Try bringing everything back to stock?
[Xoom General] Gr3yghost:
Thanks, I would be happy to do that, but it's kind of hard to do it with everything backwards!

I had to hold my cell phone up to the screen to (barely) read the mirror image text in the System Recovery. But, when I selected (what I thought was) the 'Restore Defaults' option in the blue recovery area, I got another screen with a list of selections that I also couldn't read! Rather than choose the wrong thing, I opted to reboot, but no luck, alas.
[Xoom General] csseale:
No push the images using adb
[Xoom General] Gr3yghost:
I figured it could be done. Could you please point me to a thread explaining how to push images using adb?
[Xoom General] djsaad1:
Not sure if you have 3g or wifi but here are the 3g instructions

http://xdaforums.com/showthread.php?t=988942
[Xoom General] Gr3yghost:
That's great, thanks for the info. I'll have to do this later today when I am at a PC (now at a Mac).

Any ideas about why this would happen in the first place? I've looked through the forums but haven't seen any other threads about this issue. It may be fixable with a reflash, but it sure was 'easy' to 'break' today without even knowing why...:^(
[Xoom General] Gr3yghost:
I have the 3G model. Looking at the instructions in that post, I have to admit I am not sure about a few (like most!) of the steps. It may become more apparent when I am doing it, but right now I am not clear as to where these steps take place.

[edit] Ok, I have just done some more reading and it appears I have quite a bit of work ahead of me, and that's just to get back to square one. Dang this was too easy to mess up!
[Xoom General] djsaad1:
I am confused now, I figured you would have adb installed since you already tried upgrading to 3.1 a few times.

All you need to do is flash the stock system, recovery, and boot image files.
[Xoom General] Gr3yghost:
Sorry for the confusion, but I haven't been using adb. I was trying to install the update manually with a usb data stick and the microsd cord that came with my Xoom. That's how I got myself into this pickle...way too easy it was!
[Xoom General] Gr3yghost:
Sent it back

Thanks to all who helped here. I ended up taking it back to Verizon and asking for a replacement. This they did, and even shipped it overnight at no charge (though I had to ask them to do that--they were going to charge me). The fellow at the counter was as perplexed as me. Apparently this is not a common problem.
[G Tablet Q&A, Help & Troubleshooting] rcjpth:
Ok - so if I got my Google user password change, how the Tablet's Market app will be responding? does it prompt to enter the new password? or completely no-no password change and it will break the Market?

thx,

rcjpth
[Networking] Jamielawther:
Hey there :)

I'm speaking on behalf of the GT540 Hero Rom Port Thread at http://xdaforums.com/showthread.php?t=1072546

We're having abit of trouble getting WiFi to work , I personally I have tried replacing the Wireless.ko file , but it doesn't work :(

Is there anything else we can try? That and the camera , they're the main points which need to be worked on right now , If anyone can help , please please please help us :D we are very grateful of any help :D

Thanks , Jamie.
[Droid X General] marcos.lennis:
Is the Z4Root method supposed to last more than 20 minutes? I ADB pushed the app to the phone and all normal. When I run Z4Root app and click on the Permanent root it, it just hangs there for a really long time. Is that normal? How long does it take to root the phone?

Any insight will be greatly appreciated.
[Droid X General] taterDX:
sometimes when it gets stuck I have to reboot then try again & it works the 2nd time is pretty fast & its immediately after I've sbf'd
[Droid X General] Jmoney47:
Pull the battery and try again. It will work quickly
[Droid X General] zwade01:
After an SBF I don't even try to run z4root right after I install it anymore. I usually just install, reboot, and perm root and it takes like 10-15 seconds.
[Droid X General] djsupersoak:
It took mine and a friend of mine a fair time to root as well but it will complete successfully if you just wait a bit.
[Galaxy Tab Q&A, Help & Troubleshooting] famanfwppc:
I thought naively it was possible with SuperOneClick 1.9.1 that features Gingerebreak, but it seems is stuck on execute it after push it.

I really don't know what i'm doing, so humbly ask your help.

Please don't tell me it'll take a long wait to solve root problem.

I've a lot of things to do with my tab and i need to run Titanium Backup first.
[Galaxy Tab Q&A, Help & Troubleshooting] DarkPal:
http://xdaforums.com/showthread.php?t=885734

CF ROOT in the Gingerbread thread :D
[Galaxy Tab Q&A, Help & Troubleshooting] famanfwppc:
Done! Not without your help and Chainfire work. Thank you both.
[Galaxy Tab Q&A, Help & Troubleshooting] shekarbasha@gmail.com:
Darling... u r the great i love you cfroot worked for me. i was trying for 7days

i tried z4root superclick ginger break... nothing worked cfroot is the simplest u people great...
[Wildfire General] rzr09:
So i was thinking of changin my rom to Cm7 just for android 2.3, is it laggy? dose it drain the battery more ?? Advice please :-)
[Wildfire General] nabbycs:
Im using CM7 and im loving it my battery seems to be better with cm7 running and its not laggy. However i did mess with the cpu settings and my battery died proper quick but now ive restored its all good again. Try it out and see if you like it :)
[Wildfire General] Eddster3000:
IMHO CM7 provides loads of additional features to the Buzz handset. O.k, as a custom rom it has bugs here and there but that's par for the course and most major ones get sorted. CM7 is the way forward ... there are new roms challenging the top spot but aren't quite there yet. You can always backup current rom and restore it if you don't get on with CM7 so no harm in trying it!
[Wildfire General] 3xeno:
As said above, I would say to give it a try. Take a Nandroid backup beforehand, and, if CM7 doesn't suit you, you can always get back to your backed up Stock ROM.

Its definitely worth switching though. I am extremely pleased with it.
[Wildfire General] bynge:
Only bad thing about CM7 is the font size. It is extremely small that it looks pixelated and takes out the wow out of the UI.

HTC sense looks best IMO, only reason I root is to get app2SD. Thats it.

I always use stock ROMs. Sorting out the bugs itself is a big time eater. I hate it.
[Wildfire General] kevin2516:
Wtf is wrong with the font size on CM7? It's the same for me and was the same on stock/wildpuzzle... and bugs? pfft lol, that's why you stick with the stable release.

Anyway it's your choice, if you're happy with sense/stock, stick with stock or wildpuzzle or the DK sense rom, if you don't like it and wanna try something new and has heaps of themes, get CM7.
[Wildfire General] 3xeno:
Besides, Font Size can be increased as per your will in CM7.
[Wildfire General] frodo18:
stay with the stock rom, is better, CM7 allways have a lot of bugs
[Wildfire General] bynge:
Most of the designs on CM7 are made for high resolution phones, Wildfire having a lower resolution doesn't look great. Post screen shots of your app-drawer, desktop so on.

Bugs are not enough reason to ditch an OS ?. One bug scares people away. Just one bug.

I am not a developer, just an average user. If you can't satisfy me, then you won't sell anything big. Unfortunately, its so.

I don't get orgasm about any new version of anything. I want things that work seamlessly. Changing versions without solving bugs won't help.
[Wildfire General] 3xeno:
This was true, not any longer, after nhnt11 made the required changes to make CM7 look like it is supposed to on LDPI Devices.

Anyway, its unfortunate that CM didn't suit you, but that is exactly why I think all posts in this thread ask the OP to

try

out CM, No ROM is perfect, everyone knows this, but, a particular bug for someone may be no big deal to another person. It's all about preference. As for me, even I am an average user, not a dev, and, yes, I am not saying CM is bug free, but, for me, they are no deal breakers.
[Wildfire General] kevin2516:
Who said anything about changing versions? I just said stick to the stable releases, not change whenever a new nightly is released, and if you want the bugs to be resolved, post it to the issue tracker, or tell the devs about the bugs and don't whine about it.

It will get fixed eventually, all you have to do is wait.
[Wildfire General] bynge:
I spend money/time on something not to wait(spend more time) but to use it. You still don't seem to be able to understand the viewpoint of someone else. And haven't posted any screenshots. What else would be a way to compare ?

Stable release ?. The number of stable releases devs make kinda doesn't go with "stable" actually. There hasn't been a developer version of ROM without bugs.

I go for perfection, bugs just puts me off.

A guy asked which he should use Stock or CM7. And we gave our views from experience with both. As 3xeno said, its all about preferences.
[Wildfire General] ErwinP:
Even this stock ROM has bugs, but chances are big that you will find some more on CM7, altough I've never worked on it. But the nice thing about it that on CM bugs will be fixed eventualy, whilest on stock ROM you're left alone with it..

Perhaps a first step is to go away from sense. I liked sense, but installed Homelauncher pro just to try, and I have found out that I liked it even more than sense. I am now in the stage where I gradualy change all the stock things on my ROM (for so far it is possible). So I know now that I ceryainly will change my ROM once I can.

So you really have to try: you don't realize what can get better unless you have seen other options. And if you are hesitating because of the 'big' step of changinf ROM, perhaps try to change some typic stock things. You will see for yourself if you want to go and see more of what other ROMs have to offer you.

Or that is at least my oppinion: as stated, I've always worked and am still working on the stock ROM.

Erwin
[Nexus S Themes and Apps] Paleryder:
Can anyone confirm that we can get a working version of Swype on our NexusS4G and a possible link it TYVM I also miss the voice mail off the epic where we could see and control the sound file. Any Apk recommendations on a replacement?
[Nexus S Themes and Apps] krohnjw:
Does the official Swype APK fail?
[Nexus S Themes and Apps] matt2053:
Google Voice of course.