yashsingh1/xdaforums huggingface dataset:
[Vibrant Q&A, Help & Troubleshooting] davemw2:
Ah. Ok that makes sense. ****ty. Twlauncher is so laggy compared to the other ones. Thanks.

sent from premium app

rom: trigger 3.2 w/kb5

kernel: bali 1.8.3

theme: stock trigger... for now
[Vibrant Q&A, Help & Troubleshooting] kgail76:
I have a new (one week old) Vibrant. I haven't done any mods, or rooted or anything like that. My GPS sucks (as most do), so I changed some settings under LBSTestMode. Now my phone is really screwed up. I don't know why, but it randomly turns itself off, locks up when running ANY app, and if I allow the screen to sleep, I can't get it to turn back on. My battery was almost completely dead, so I plugged in, and now I see the "Swipe to Unlock" screen, but I can't swipe it or do anything at all.

I've done a couple of battery pulls but no change. I'm at a complete loss for what to do. I'm sure it's something silly I'm missing, but I'm brand new to Android and freaking out.

Can anyone help a stressed-out noob? :)
[Vibrant Q&A, Help & Troubleshooting] flipnotiq:
Try odin to stock . Can you get to download mode? Pull battery plug in usb hold volume up and down and put the battery . Should see android with a broom and should be yellow
[Vibrant Q&A, Help & Troubleshooting] kgail76:
Can I do all of that with a (basically) dead battery? Or should I charge first? I tried plugging in to charge but it wasn't charging. So I pulled the battery, then plugged in the phone without turning it on to see if it would charge.
[Vibrant Q&A, Help & Troubleshooting] flipnotiq:
Try the method i post but make sure you have the drivers installed on your oc
[Vibrant Q&A, Help & Troubleshooting] nhorn1983:
download vibrant toolbox it will help u
[Epic 4G General] styckx:
Is there a solution to the problem of the browser recognizing touches to links on websites and not registering the touch correctly? I get a lot of instances where when I touch a link on a webpage I see it acknowledged by the link being highlighted briefly, but doesn't actually do anything except that. Usually hitting it a second time will then acknowledge the link and go to wherever the link directs. Also sometimes a longer press is required to get the link to work.

This is only browsing the web. Currently using Dolphin mini.
[Epic 4G General] gTen:
Its prob a browser thing...if it annoys you try another browser... remember that it has to differentiate you scrolling down the page or actually hitting a link to prevent mistakes of accidental clicks...
[Android Q&A, Help & Troubleshooting] 09polaris600:
Hopefully this is in the right place, but I cannot put it in a specific area since I am new to the forums. THANKS ALL!

HELP…

I need to enter my MSL to “fix” the SiriusXM app (or other streaming apps). Before I was able to use the instructions below. With this new rom (I am thinking any 2.3, but I am running Fresh EVO 2.3.3) , it takes the code, but nothing comes up. Does anyone have a work around???

1) Dial ##3282#

2) Choose Edit Mode

3) Enter MSL

4) Choose Advanced

5) Change HTTP PD Proxy Port to: 0 (old 8085)

6) Change HTTP PD Proxy Address to: 0.0.0.0 (old pd.vog.sprintpcs.com)
[Android Q&A, Help & Troubleshooting] kofkorn:
Same problem here. I've been looking for an alternate, but I haven't seen anything yet. Any one had any success getting into the MSL menu with 2.3???
[Android Q&A, Help & Troubleshooting] llcobbs:
Reading Msl

I saw the method for reading msl code via cdma workshop but the pics showed cdma ws 3.5 and i have 2.7 will that proccess still work
[Android Q&A, Help & Troubleshooting] Bierce22:
u can get the msl from programs like dfs tools cdma workshop and qpst as well as msl reader from the market but i always find it easier calling your carrier and telling them you want to do a data restore or something like that.

as for it not recognizing the ##codes the person who made the rom couldve taken the epst apk in order to save room.
[Android Q&A, Help & Troubleshooting] llcobbs:
Ok, I opened chat to sprint support and asked for msl code. They told me that my device doesn't have MSL but then gave me what they called a 6 digit security code to reprgram my phone. Is this security code the MSL and they just didn't want to tell me.
[Android Q&A, Help & Troubleshooting] stretchwookie:
yea thats probably it.

also, for anyone stuck in a 2.3 rom, try these codes

*#*#3282#*#* Data Restore

*#*#786#*#* Reverse Logistics Support (device wipe)

*#*#(your msl)#*#* reprogram phone # and msid

these are the codes we use at my store for the nexus s 4g. hope it helps

:D:cool::p
[Android Q&A, Help & Troubleshooting] ErlyD:
I have an issue. I have my msl and enter it. Using getprop (ril.MSL 123456) then use *#*#3282#*#* enter the msl. Always get invalid code. Using the number given to me by getprop.

Would being unrooted cause this?
[Android Q&A, Help & Troubleshooting] ErlyD:
Now it doesn't say invalid anymore after reboot. Now it just exits back out to menu to select what data setting I want to edit. I select wimax and it asks for msl again.type it back out to the menu I go.

Any suggestions?
[Android Q&A, Help & Troubleshooting] llcobbs:
hello any answers
[Android Q&A, Help & Troubleshooting] ErlyD:
Someone please read this!
[Galaxy S II Q&A, Help & Troubleshooting] jameslfc5:
Is there any app?

Also with my HTC Desire, I can go to www.gutenberg.org and download any file straight to the phone, with the SGS2 it attempts it, then says failed? :/

Any suggestions?

Thanks
[Galaxy S II Q&A, Help & Troubleshooting] JJEgan:
Problem with the web site it is not opening in a PC browser .

jje
[Galaxy S II Q&A, Help & Troubleshooting] jameslfc5:
It works on the htc tho ? :/
[Galaxy S II Q&A, Help & Troubleshooting] JJEgan:
It may be a delivery /server/network problem that Gutenberg rare having is what i would conclude from you being unable to connect and my pc failing to load the web page .

jje
[Captivate Q&A, Help & Troubleshooting] wdlamb:
Ok I'm trying to search the forum but not having much luck because my terms are far too generic.

I have the Captivate on the stock AT&T 2.2 firmware, although it is rooted and I'm strongly considering flashing a new ROM right now if it solves this issue.

I just purchased a creative D100 bluetooth speaker and I cannot get the Captivate to play through the speaker. It pairs correctly with the speaker, and if I look under the "Options" on the pairing, I see a checkbox for "media playback". However, checking this box makes no difference, I never get audio output from anything but the built-in speaker on the phone.

Anybody have any suggestions? Thanks,
[Nexus One General] DownloaderZ:
All,

I have updated to 2.3.4, lost root as expected and tried to reroot 2.3.4.

I had no luck, once i ran ./Gingerbreak the script would sit and not do anything after displaying the initial text.

Has anyone successfully done this?

I thought about updating with the prerooted 2.3.4, but the devs started to add all sorts of stuff in there, and right now that is not what I am after.

Thanks!
[Nexus One General] 51Cards:
Also anxiously waiting for a 2.3.4 root option.

- No custom boot loader means I can't use the current SU.zip process.

- I didn't unlock the boot loader on the phone and now really don't want to go through the hassle of having the phone reset when I do... too much on it.

- Can't do a nandroid backup (to unlock) because I don't have root.

Catch 22 circle. Am keeping my eyes open, hopefully someone comes up with an alternate method. Once I get root again I will unlock the boot loader after making a backup so this doesn't happen again.
[Nexus One General] ATnTdude:
Custom bootloader? Just unlock the one you have and flash a new recovery. It takes a whopping 3 minutes to flash recovery, then SU, and reboot. If you want to keep everything stock so you can OTA, the stock ROM will overwrite the recovery when you boot and you'll end up with rooted stock ROM with OEM recovery. If you want to then flash a custom rom, you can do so through ROM manager.

Want to unroot? Download the FRG33 passimg.zip and boot into bootloader.

This stuff is stupid easy on the N1.
[Nexus One General] 51Cards:
Ok so feeling like a newb here.

First I meant 'custom recovery', not 'custom boot loader'... mixup in terms on my part.

But to put in a custom recovery I need to unlock the phone. Once I unlock the boot loader doesn't the phone reset to factory state? I had seen that mentioned several times and in the unlock video I was watching. After the phone was unlocked it went back to "Welcome to Android" etc on the next startup. Have far too much in the phone I don't wish to loose and I can't Nandroid it without root.

Thanks for the info.
[Nexus One General] MitchRapp:
I had used Gingerbreak on my 2.3.3 - after 20 seconds of searching on XDA I found that you can simply install ROM Manager, flash RA custom recovery, boot into recovery, remove signature verification, flash update.zip followed by su.zip and you keep root .... all this WITHOUT an unlocked bootloader...
[Nexus One General] DownloaderZ:
I am attempting to keep my phone as stock as possible and only root to block ads and sometimes push some new app that google wont release to the n1.

I really don't want to mess with custom anything on my daily driver (used for business also). I have my g1 for that :D

SO....has anyone used gingerbreak successfully on 2.3.4?
[Nexus One General] efrant:
Disregard. I misread the post.
[Nexus One General] 51Cards:
Yeah, the ROM manager option would have worked well before I did the OTA for 2.3.4 and lost root. I will keep it in mind for the future, thanks!
[Nexus One General] GnatGoSplat:
I'm sure there's a better, faster, more direct way, but here's how I went from 2.3.4 stock to 2.3.4 rooted without unlocking the bootloader.

1. Flash FRG33 as passimg.zip on SD card.

2. Flash FRG33 to GRI40 as update.zip on SD card using stock recovery.

3. Root GRI40 2.3.3 using Gingerbreak.

4. Install ROM Manager app and install Clockworkmod Recovery.

5. Open GRI40 to GRJ22 update zip file and REMOVE Recovery folder from it.

6. Boot into Clockworkmod Recovery and flash modified update.zip from step 5.

7. Install SU.zip from Clockworkmod right.

Voila! Rooted GRJ22 2.3.4 with locked bootloader. Lot of steps, but I don't think it took more than 10-15 minutes.
[Nexus One General] _raz_:
Exactly what I did. Works smoothly and you're all set in minutes. As long as you had root in the first place, on 2.3.3.
[Nexus One General] droidexplorer:
This was the same lesson I learned when I rushed in with Froyo --> GRI40 update the moment it became available. I lost my root and had to wait for Gingerbreak release. Now when they release OTAs, I wait until I understand how to keep the root under the new update before accepting it. Seems like a better approach to me.
[Nexus One General] brettbellaire:
I'm looking to download all the files for this so I'm set from the start. I found FRG33 here but I haven't found the GRI40 update yet (although I haven't really looked yet either, that's not my question). I'm wondering, the site I listed has FRG83 as well as 33, does it matter which to use? 33 mentions a possible error.

What's the deal?

Thanks,
[Nexus One General] GnatGoSplat:
I think you should be able to use FRG83 instead. All you really need is something that can be named passimg.zip installed by the bootloader itself.

I got the GRI40 update from here:

http://android.clients.google.com/p...b119f8.signed-passion-ota-102588.656099b1.zip

GRI22 update:

http://android.clients.google.com/p....signed-passion-GRJ22-from-GRI40.71d2f9ec.zip
[Nexus One General] brettbellaire:
That sucked!!! I lost all my settings and apps when I moved back to froyo?? I wasn't expecting that :(
[Nexus One General] GnatGoSplat:
Oh yeah, I forgot about that. Flashing PASSIMG.zip wipes out everything because it's a full flash.
[Nexus One General] efrant:
There is no way to downgrade Android without wiping everything, as a downgrade is only possible with leaked shipped ROMS (i.e., ROMs that re-write the entire NAND flash memory on the device...
[Nexus One General] Phoenix84118:
I do that as well now. However I have some steps I figured out that work for me. It's more direct (only 2 flashes, plus su), but you have to pay attention. If you didn't already have a CWM backup though, it will wipe everything:

1) Flash to FRG33 using PASSIMG_Passion_Google_WWE_2.16.1700.1_FRG33_release_signed.zip (rename to PASSIMG.ZIP), takes you to 2.2

2) Root using Super-One-Click

3) Install ROM Manager and flash CWM

4) Flash b90257ed8cd3.signed-passion-GRJ22-from-FRG33-121341.b90257ed.zip, takes you directly to 2.3.4

5) DON'T LET PHONE REBOOT into Android, go to recovery then Flash su-2.3.6.1-ef-signed.zip

6) Remove/rename /system/etc/install-recovery.sh via ADB

7) If you have a recent backup, use CWM to 'advanced restore' the data portion.

8 ) Profit! (or root)

Step 5 may require explanation:

Android will reboot at least once during the flash, this is ok, as it loads right back into recovery. However after the second reboot, it will boot normally. You must INTERRUPT this boot process (hold power button, battery pull, etc). At this point CWM is still on there (don't know why, I thought flash was going to wipe it).

The reason you have to interrupt the boot process (for anyone who doesn't know) is because of the install-recovery.sh script. Stock android will automatically flash the stock recovery on bootup.

So boot into CWM, then flash su. After bootup up again, CWM will be gone, but we have root! So remove (I renamed) that file (/system/etc/install-recovery.sh), then reflash CWM using ROM Manager.

EDIT: After posting this, I had a thought: it should be possible to remove install-recovery.sh via CWM using ADB. That would remove the step of reflashing CWM a second time. I updated the step-by-step, but left the explanation as-is.

When I originally wrote these steps a few months ago, gingerbreak wasn't released. So I don't rely on it.
[Nexus One General] GnatGoSplat:
Just wondering, but would you always be safe and able to root by flashing SU.zip if you just never let it overwrite the custom recovery?

I thought you can always pull out the Recovery folder from the update zip file and it won't overwrite your custom recovery. Granted, that will require you to download updates manually rather than OTA, but that's easy enough.
[Nexus One General] Phoenix84118:
In theory. It does seem to work for other devices (gTablet). I haven't had much luck with modifying the updater-script inside the zip file however. Whenever I change one, I get errors when I flash the zip. That's why I haven't tried that method.

I wanted to make my own flashable zips to tweak ROMs on my own, but never could get it to work, so I abandoned my work.

In addition though, you could just try to replace the recovery.img in the zip file with CWM. That might work too, as long as signature verification is off. I don't remember if I tried that.

EDIT: Forgot one key thing: Doing this won't prevent the OS from reflashing the stock back anyway on bootup (using install-recovery.sh). You MUST remove that file regardless, if you're on a stock ROM. If you want to remove that from the zip you can, but again requires updater-script changes. However if you want to OTA, then I'd recommend just renaming it, since some OTA's update that file. That way you can rename it back for the update.
[Nexus One General] GnatGoSplat:
On the GRI40 to GRJ22 update, I didn't have to do anything too complicated like modifying scripts. I simply yanked the Recovery folder out of the update and that seemed to do the trick with no error messages and CWM still intact.
[Nexus One General] Phoenix84118:
You know what, I just looked over the updater-script for GRJ22-from-GRI40, and it doesn't look like it actually flashes the recovery during this process.

It looks like it copies it to the system, then relies on the install-recovery.sh script to update it on the next boot.

That would explain why I still had CWM after I flashed to GRJ22 from FRG33. :)
[Nexus One General] efrant:
That is correct. OTA updates from Google never flash the recovery. They just copy the /system/etc/install-recovery.sh and /system/recovery-from-boot.p to the device. Then, once the device reboots, those two files re-flash the recovery (on every boot actually).
[Nexus One General] vtrandal:
I wish I had rooted my Nexus One retail phone before it got the Gingerbread 2.3.4 update OTA. I would even pay someone to root it if they could - really:) I have another Nexus One that is developer phone. I got it about a month ago and wasted no time putting my custom ROM on it. I think as a result of how I did it, it has not upgraded to 2.3.4 OTA.

I heard/read someone has Gingerbread 2.3.3 OTA in a zip. Maybe I could use this to downgrade and root my retail phone. I say this because whenever I flashed my dev phone I always downgrade to the Official 2.2, let it take an OTA (not sure why I do this part), and then flash my 2.3.3 images. But I guess this won't work anymore either because my dev phone will get 2.3.4 OTA and won't be able flash 2.3.3 images on top of that. Not sure.

So I guess my question is: Is there a way to downgrade to 2.3.3, root my phones, then upgrade to 2.3.4 and KEEP root? I think there is a process for doing this, but I just can't remember where I saw it.
[Nexus One General] brettbellaire:
Yes... the explanation found on the first page of this thread.

You have to downgrade back to Froyo, not just 2.3.3, but following this process will result in rooted 2.3.4.
[Nexus One General] brettbellaire:
I'm done step three, can someone clarify the next steps? Will this wipe anything?
[Nexus One General] LFact:
Rooting the device and installing custom recovery do not wipe your device.

4. Download and install ROM Manager from Market, then flash Clockwork recovery via ROM Manager.(Or you can change it to RA Recovery, if you prefer it)

5. Put GRI40 to GRJ22 updater patch to SD Card, open it with any archive utility, delete 'recovery' directory from the zipped file.

6. Boot into recovery, flash modified update.zip. You may need to disable signiture verification.

7. After updating is finished, do not reboot your device yet. Flash su.zip to install Superuser.apk.
[Nexus One General] brettbellaire:
What about step 7? Do I have to do that?
[Nexus One General] LFact:
If you don't do step 7, you won't get root.
[Nexus One General] brettbellaire:
do I just do that in clock work?

Sent from my Nexus One
[Nexus One General] brettbellaire:
Heh, that's a dumb question. I didn't see that you had a step seven too. For some reason I thought you skipped it.

Sent from my Nexus One
[Nexus One General] CapStone:
I have an unlocked bootloader but don't have root. What options do I have to gain root?
[Nexus One General] GnatGoSplat:
If you have an unlocked bootloader, then gaining root is even easier.

If you are already on 2.3.4, unrooted, then simply flash a custom recovery following the steps here:

http://wiki.cyanogenmod.com/index.php?title=Nexus_One:_Full_Update_Guide

You only have to do the "Installing a Custom Recovery Image" part. Choose either AmonRa or Clockworkmod. The RomManager stuff does not apply as you can't install that without root.

Now that you've installed a custom recovery, boot into Recovery and flash SU.zip and you will be rooted. You may also need to install SuperUser app from the Marketplace (not sure on this because I already had it installed before SU.zip).
[Nexus One General] CapStone:
I've tried that a couple of times but it hangs at waiting for < waiting for device > and nothing happens no matter how long I leave it.
[Nexus One General] GnatGoSplat:
Have you enabled USB Debugging?

It's in Settings -> Applications -> Development -> USB Debugging.
[Nexus One General] danger-rat:
Boot the phone into the fastboot screen (power + volume down).

Confirm connection with "fastboot devices"...
[Nexus One General] CapStone:
Yep USB debugging is enabled. It says fastboot USB, on the phone. when I run fastboot devices nothing shows up. It simply brings up a new line in the terminal.
[Nexus One General] albundy2010:
All nexus ones are dev phones. There are only two models ever sold. The only difference is the radios.
[Nexus One General] efrant:
Do you have the driver properly installed?
[Nexus One General] CapStone:
This problem has been moved to the qna section. When I get home I'm going to update the driver than go from there.
[Nexus One General] brettbellaire:
I'm finally trying to do this. The file I am using doesn't seem to be the right one, but as far as I can tell it is 2.3.3 -> 2.3.4 (71d2f9ecd610.signed-passion-GRJ22-from-GRI40.71d2f9ec.zip).

Also, is it right that I have to reinstall CWM everytime?
[Nexus One General] efrant:
How do you know it is not the right one? That is the correct file. Don't forget that you need to turn signature verification off in your recovery before you flash that file, otherwise it will not work.

As for your second question, there are two files that you need to delete in a stock ROM in order for your custom recovery to not be overwritten by the stock one:

/system/recovery-from-boot.p

/system/etc/install-recovery.sh
[Nexus One General] brettbellaire:
Hmmm, well I tried both enabled and disabled signature, but I'm getting an error both times. I'm going to reupload the file and try again. I'll post the error message if it comes up again.
[Nexus One General] brettbellaire:
assert failed: apply_patch_check("a bunch of crap")

E:Error in /sdcard/update.zip

(Status 7)

Installation aborted
[Nexus One General] efrant:
What ROM are you currently running? You're not trying to flash this update on a de-odexed ROM, are you?
[Nexus One General] brettbellaire:
It's just stock 2.3.3 routed with the gingerbreak app.
[Nexus One General] efrant:
Are you removing the recovery folder from the zip? If so, try keeping it in. (That may be corrupting the file.) Just make sure you don't reboot after you flash it. You need to flash the superuser zip before you reboot.
[Nexus One General] efrant:
And what recovery are you running? Some have had issues with the latest clockworkmod. I'd stick with amon_ra.
[Nexus One General] danger-rat:
I believe the assert is checking for specific files, recovery, radio etc. The bunch of crap may tell you what is missing, then you can remove the assert check from the script...
[Nexus One General] brettbellaire:
OK so wait... all I have to do is flash superuser before rebooting and I keep root?

How does that work?

su 2.3.6.1???
[Nexus One General] brettbellaire:
bunch of crap = "/system/framework/framework-res.apk", "c13b4c289e753dfa194972bc12a083a1305c5f49", "2c1530db1d1c748aedf054da0f52267f8889cd4d"

using CWM in rom manager.
[Nexus One General] efrant:
Correct.

Let me try to explain a bit: "rooting" an Android device, to keep it simple, essentially means placing a file (su) in the system partition. However, you don't have r/w access to that partition if you are booted into a stock ROM/recovery. So how do we do this? You need some sort of exploit (e.g., rageagainstthecage, psneuter or GingerBreak) that, well, "exploits" a vulnerability in the OS and grants you that r/w access to the system partition. Once you have r/w access, you can place the su file where it belongs, and then you are "rooted". From there, you can run root apps, flash custom recoveries, etc, etc. Now, if you already have a custom recovery (which is essentially a separate OS in itself), you can already write to the system partition. So, once you flash the update to 2.3.4, all you have to do is flash ChainsDD's superuser zip (use the Eclair/Froyo version) and it places the su binary (as well as another file) where it is supposed to go. HOWEVER, stock ROMs reflash the stock recovery on every reboot, so you need to flash the superuser zip BEFORE rebooting (after flashing the 2.3.4 update), or else you are stuck again. Once you have root after the update, just delete those two files I mentioned a few posts above, and reflash your custom recovery.
[Nexus One General] cmangalos:
how can i downgrade from 2.3.4 to froyo, or 2.3.3, please privide links, thank you, ,

can find a tutorial here, as well as the file to download
[Nexus One General] LFact:
Have you read this first?