yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] vendetta718:
Ill get right into it.

I'm trying to unlock my boot loader using The 7.4 Gnex Toolkit but under phone model and build my phone is not shown.

I have a WHITE GSM/HSPA+ MODEL running OTA 4.0.4 and the build number is IMM76K.I950WLD2

I did some research and it seems that I have a korean version of the device.

Im on t mobile btw ($30 4G plan)

Which build should I click on in the program. obviously I can't click on the Verizon one

Help

When I hold down volume buttons plus power it shows : MAGURO as the verdant name name also I don't have wallet installed
[Samsung Galaxy Nexus] ÜBER™:
Don't use toolkits. Unlocking the boot loader is the simplest on this device. Google how to unlock galaxy nexus boot loader. The one from the droid forums is like the first one. Has a step by step.

Sent From My Sprint Galaxy Nexus
[Samsung Galaxy Nexus] Gunthy`:
Maguro is the GSM version, so you can choose any GSM is think. But indeed if you're not sure, don't use the toolkit and unlock manually.
[Samsung Galaxy Nexus] Mach3.2:
How hard is it to type fastboot oem unlock?

People these days are seriously lazy to even type 3 "words"
[Samsung Galaxy Nexus] Gunthy`:
I don't think that is usually the problem... It's setting up fastboot that can be confusing for some people I suppose ;)
[Samsung Galaxy Nexus] Mach3.2:
Here's the fastboot + adb files if OP needs it.

https://www.dropbox.com/sh/p1wn5ywy6bd14hb/MvP3wpoNfx
[Samsung Galaxy Nexus] watala:
I had the exact same problem when I got my galaxy nexus. Please note that the build number IMM76k is a software build not a MAKE of the phone. Your phone is gsm. Now all you simply need to do is change the build number to Google stock. I change it to IMM76i. So using gnex toolkit v 7.4. Choose the right build for your phone NOW which is IMM76k . I believe it is number 12. Then unlock the boot loader by choosing number 3. Then choose number 9 which I believe downloads and extracts and flashes the Google stock image. You will then have the build IMM76i on your gsm phone. You then simply using gnex toolkit v 7.4 do the things you would like to do. Rooting, flashing and the rest. I now AOKP installed on my galaxy nexus Korean variant. Hope this works for you too.
[Samsung Galaxy Nexus] Mach3.2:
No, don't do this.

Option 12 is a CDMA device, bad idea doing CDMA stuff on a GSM device.

Anyway, doing a "fastboot oem unlock" command should not do anything to the device other than nuking all your data.
[Samsung Galaxy S (4G Model)] xr1charxx:
I was on GB and had amazing battery life!

Just flashed AOKP milestone 6 and I can can't watch

The battery drain.

I've read forums and not much help.

I DL better battery but don't really know how to use.

I tried formatting battery stats.

Any solutions?
[Samsung Galaxy S (4G Model)] johnadelic:
I am having the same issue. I am going yo try cMIUI. what are you getting for battery life?
[Samsung Galaxy S (4G Model)] hwchan:
Are y'all sure it's not just because you're doing lots of stuff with your phone right now, having just flashed a new ROM?

If it's an extreme amount of battery drain, it might be some leftovers from whatever you had last. You could try a factory reset and then see how stock AOKP handles battery drain.

I know I don't get battery life as good as I did with Octane, but a big part of that is because I've been flashing the new AOKP builds every couple of days, so things don't get a chance to settle down. (Granted, battery life still isn't as good as when I just flashed Octane.)
[Samsung Galaxy S (4G Model)] eollie:
There is tons of things regarding this very issue in the AOKP q & a thread. Please use the search this thread button in that thread. Ive typed a response atleast four times today. And atleast four yesterday and more the day before and the day before that. NOt trying to be a ****, but Im tired of typing and responding. If you cant be bothered to read the thread or search I cant be bothered to respond anymore.
[Samsung Galaxy S (4G Model)] xr1charxx:
Not sure for sure.

But I get 5-6 hours on full charge with medium use(text. Instagram. Web.)

How can I get exact info?
[Samsung Galaxy S (4G Model)] jeffsf:
Read the AOKP Q&A, yes, the whole thing

Read the OP's instructions on the AOKP dev thread

Read the thread on Bettter Battery Stats

Listen to what people say about battery use

Think about what you have done and what to try next

Do

Rinse

Repeat

Ask yourself "Why am I flashing ICS at all?" -- ICS in the SGS4G is still very much in development.
[Samsung Galaxy S (4G Model)] adobrakic:
I don't think you realize how unreasonable it is to ask someone to read that entire Q&A. I've followed the thread from its beginning, and there's no real solution to the battery issue being described here. You'd only be wasting everyone's time who took your advice. I've also read all of OP's instructions in the AOKP dev thread, and have even tried the gremlin remover prior to flashing AOKP. This does not solve the battery issue. You're seeming to imply that the battery issue is the user's fault, and I think that's not even remotely close to the truth. I've done multiple flashes, each time trying something different, to see if I did anything to cause the horrible battery in AOKP, and they all concluded the same way. With that said, we need to actually try to fix this, instead of sending people in circles and pretending to fix it.
[Samsung Galaxy S (4G Model)] jrgbx:
First of I dont have battery issues at all with AOKP I am a User a very grateful user (thx 2 our devs). Just factory reset, after that wipe cache, system, everything except your sd card of course) and the flash your rom. Its really a matter of re-assuring everything is wiped. Also leave your phone alone for awhile I left mine around 2 hrs alone, while the rom settles.
[Samsung Galaxy S (4G Model)] Wodensman:
Go to the Gremlin Remover dev thread, and try steps 1-3. If you are STILL having exaggerated battery loss, try using gremlin remover it'self. If you still have problems, after making it back to your preferred rom, just put the phone down for a while.
[Samsung Galaxy S (4G Model)] Manumission:
Some of us are getting good-very good battery life, and some of us are not - using the same exact ROM. I don't know what that tells you, but what it tells me is that it *is* likely to be a user issue.

People complain about battery life, but they hardly ever talk about the total time they are using it (including fiddling around with it), what programs they have used or have installed, and how they are restoring after they flash (i.e., if there is a chance they are bringing along bad stuff from a previous incarnation of the phone). More information about these things and - yes - doing tedious things like the process of elimination might be enlightening here.
[Samsung Galaxy S (4G Model)] eollie:
Ya know when I first came here I said something similar. But Ive kept up with these threads now and I know for a fact battery life issues have been discussed to a point that the devs are ready to pack up and leave. Nobody wants to read or even search. Instead the battery life issues are blamed on the shotty coding of the people building these roms. If you are getting bad battery life it is plain and simple a user error. Unless you can provide logs stating otherwise then just drop it try what is being suggested or go back to stock roms. Install all the apps you need to customize the phone like it is on the ics variants and then report back here. I garandamntee you will have ****ty battery life.

These custom roms have so much stuff added to them that is hard coded in for customization that its not going to have super battery life like a unbloated stock rom. But you cant expect it to. A good comparision was made earlier in another thread. Would you expect to get 8 hours out of a laptop battery?
[Samsung Galaxy S (4G Model)] sublimespot:
I always tell people to make sure to completely drain the battery....all the way until it shuts off, because mine will sometimes stay at 1% for nearly 2 hours.

Seems like it doesn't know its own scale until you do that a few times.

Also never ever ever restart this phone while having it plugged in or turn it on while plugged in.

Let me give you the scenario, it will be charging let's say around 50% and then after restart while plugged in right around 75-80% and that little act took me a long time to recalibrate my battery and I'm not talking about deleting the battery stats, I don't delete battery stats anymore at all (read an article from Google saying its pointless)

All that said I'm a very heavy user, and I like a bright screen and I'm getting (what I would consider) good battery life. But I have a 3500mah so its never too bad for me :)

Hope this helps someone:)
[Samsung Galaxy S (4G Model)] pakiyoungster:
well me too experiencing super fast battery drain

i have flashed aokp milestone latest build by wiping factory reset.

also allowed to sit the phone for 1o mins

my wifi,bluetooth,gps remains off all the time, also screen brightness is at its lowest.

on moderate texting the phone wont last more then 4 hours
[Samsung Galaxy S (4G Model)] Shortbus-Driver:
I'm on aokp
[Samsung Galaxy S (4G Model)] Wodensman:
I'm on AOKP, and my battery life is GREAT. There are plenty of steps and tips mentioned here to find out what your battery problem is.
[Samsung Galaxy S (4G Model)] eollie:
I would like to see screen shots of the battery usage of people that have crappy battery.

From home hit menu>settings>scroll down a bit to battery.

Take two screenshots one of the initial screen, then touch the graph at the top and take one of that screen.

I keep hearing battery life is horrible I only get 4 hours, please fix this, hows battery life..blah blah blah battery. Yet nobody will drop usage stats, logs of a days use, offer anything but i use my phone moderately. I call bull**** on that, How many texts do you get/send in a day? How long are you on the phone making calls? Do you live in a poor service area? Give some info.

On a average day I get about 50 texts, might make a 20 minute call, use tapatalk a half dozen times, and use tweetcaster and flipboard a dozen times. I can get 12-15 hours out of a full charge. To me that is light to moderate use. I get crappy data where Im at right now so Im on wifi A LOT. When Im actually using t-mo data more I can get closer to 18 hours out of a charge

People if your having problems with battery life stop rebooting the phone a hundred times a day. Stop shutting off all the radios thinking it will help. use the dang phone like it was meant to be used. None of the code is optimized for people to shut radios off and turn the phone into a dumbphone. You are making it worse by shutting these things down and turning them back on. It takes power to properly shut off bt, wifi, data. Next time you do watch the radio will not just instantly shut down. It has to power off all the service that is using it and then power down. Otherwise you would be here *****ing about tons of force closes.
[Samsung Galaxy S (4G Model)] blazen2000:
I get about 17hours on my phone and i have a stock battery. I use all the extras PROVIDED TO US BY THE DEV like turn off wifi/date off or to 2g while phone screen is off. Auto bright and all the extras.
[Samsung Galaxy S (4G Model)] sunsurfer42:
^ THIS

I usually get 14-17 hrs doing the same. No battery issues. If you leave data/wifi on all day and are constantly checking email, Twitter, and Facebook what do you expect? Battery is fine.
[Samsung Galaxy S (4G Model)] Alarmmy:
How much time do you spend on "screen"?

My phone usually drains 10% each 5hours of sleeping (air plane mode). Is that normal? I can get around 3hours of web surfing,which is less than it was on SCOM (4hours).
[Samsung Galaxy S (4G Model)] mikhail777:
Close to a day of battery , I turn on data when I want. Poor service area, my only issue is it stays awake more, but all functions work :)
[Samsung Galaxy S (4G Model)] DragnzKlaw:
AOKP has gone a long ways since the OP post.
[Samsung Galaxy S (4G Model)] FBis251:
More precisely, the team acid kernel has with contributions from members within and outside of team acid. All the other roms are benefiting from this too. :D
[Android Q&A, Help & Troubleshooting] josephlor:
Am running Rcmix3d v4 The brightness seems to be getting dimmer. Does anyone have a fix?

Sent from my PC36100 using Xparent Green Tapatalk 2
[HTC One X] mahdi1234567:
I want to remove the Vol+ as Camera Button in this path.

what I do ?
[HTC Vivid, Raider, Velocity] yokozuna82:
Is anyone else experiencing this problem ...with a case on people say I muffled withoit one on I sound crystal clear ...all ports for both mics are open ....any insight would help
[HTC Vivid, Raider, Velocity] l0000l:
i have this problem too
[HTC Vivid, Raider, Velocity] tjubrock:
I was also told by multiple people that I sound muffled too and I have a case on my phone

HTC Vivid

s-off

DarkRaider 1.5.5

KozmikKernel Beta 7
[HTC Vivid, Raider, Velocity] yokozuna82:
Is there any tool that would increase the microphone sensitivity...I know that my old inspire had such a tool built in the option appeared when on a voice call and pressing the menu button
[Galaxy S III Q&A, (US Carriers)] circuit.007:
i want to switch from super user to super su. Just because i think it looks better with ics. So what i did was download super user from play store, and open it. I granted it access and let it update its binary. Now super su grants all my apps access. So the next logical step i thought would be to uninstall the regular super user. but i cant find it in titanium backup? (i search for superuser, super, user and neither super su nor superuser come up)

Also once i manage to get the regular superuser removed i would have to move the super su to system apps via titanium right?
[Galaxy S III Q&A, (US Carriers)] Pyrolectic13:
You ever come right with this bud? Also can't remove superuser app from foxhound Rom. Deleted it from system/app using root explorer but it comes back after reboot.
[Galaxy S III Q&A, (US Carriers)] pdinphx:
1. Install SuperSu from Play and update binaries. Make sure it achieves root.

2. Delete Superuser.apk from system/app using a root file manager.

3. Install Superuser from Play.

4. Uninstall Superuser thru Play.

5. Reboot phone.

No more Superuser and SuperSU should retain root functionality.
[Galaxy S III Q&A, (US Carriers)] Pyrolectic13:
cheers mate. Updated to the latest foxhound and superuser went away. Having this issue on a buddies phone so will try your method this weekend and give feedback.

Appreciate the response.

Sent from my Foxhound powered S3. Awe
[HTC Inspire 4G] thedailyl3af:
I'm about to flash the att stock radio 8-somthing-2011 and I just would like to know
[HTC Inspire 4G] CYRAXDroid:
http://xdaforums.com/showthread.php?t=1126069
[Galaxy Note GT-N7000 General] nebreprah:
A Little History: :silly:

I have been running i9220ZCLP1...known bad kernel since whenever it was first available, April I think. Anyways, acquired that through flashing Rocketrom v5, according to the instructions provided at the time. Everything worked fine, other than contacts crashing and the wlan some times not enabling until reboot...common issues, as far as I've seen on these forums. One thing to note, is that unless the instructions at the time asked for a full wipe after flashing 5 (I'm almost certain they did not), then there has not been a full wipe performed while in this kernel.

The current issue: :confused:

The other day my phone froze on me...months after flashing and having used this kernel, waiting for something more solid to come out. After it froze...holding the power button turned it off, but the phone would not boot afterwards...to ics, to recovery, to download mode, nothing.

After some fiddling, I realized that it will charge and once it buzzes and the screen comes on showing a full battery, I can turn the phone on and it will boot...then freeze after getting past unlock screen. Or freeze and go black in download mode...didn't try recovery, wasn't interested in it at the time, but I'd imagine the same.

After removing the battery for a few days, then plugging it in til full charge notification, I was able to get it to boot again, where it froze at the boot screen, but went dark. After one more full charge...oddly, like a minute later, it booted to ICS fine and worked for 24 hours or so.

Now: :(

With a mind to flashing away from the bad kernel, I restarted the phone tonight from the menu in ics... it booted fine, so I left it plugged in to get a full charge and came back to a phone, screen still on, that shows same battery % as when I left it. And I'm back to where I started with this problem, powered off after holding power button a few seconds and now nothing.

Waiting for a full charge again, to see what happens...I'm guessing/hoping I'll be able to get it to boot again, with some more fiddling...:rolleyes:

My question is whether this sounds like it's hardware (battery etc) or software (bad kernel etc) that is causing the problem.

If I can get it into download mode...plugged in, obviously, should I try OdinPC to a safe kernel?

Thoughts would be awesome. :fingers-crossed:
[Galaxy Note GT-N7000 General] apurvapatel:
How about flashing stock GB via pc odin first and getting safe? ;)
[Galaxy Note GT-N7000 General] SpyderTracks:
+1 I've read a few people on ICS having charging/battery related issues over time. Worth seeing if it still happens on a gb kernel.
[Galaxy Note GT-N7000 General] nebreprah:
OK, that's one vote for flash if I can get it running again. Thx, glad you read my post.
[Galaxy Note GT-N7000 General] nebreprah:
Hmm, but how to get there...GB and all.

So now the vote is software. Any idea why this would happen much much later? No battery issues at all, just suddenly.

Maybe I'll buy a battery.
[Galaxy Note GT-N7000 General] apurvapatel:
A little searching would show you DrKentan's guide @ http://xdaforums.com/showthread.php?t=1424997
[Motorola Droid Bionic] 5thAgent:
Master qa1 and 2 got updated at 8:30. Same with master qa300 and sdc100. I don't wanna have to FXZ back to check and be let down.

Edit: spoke too soon. qa200 was updated today, the 12th. Please check! D:
[Motorola Droid Bionic] 5thAgent:
Ugh, whatever. I'm gonna test out the shell script I just wrote to do a full restore, OTA to 905, then check cheesecake. I may do it tonight, but if I don't, I will tomorrow. Maybe someone who's already on 905 will beat me to it ;)

Edit: damn thing won't boot. fml. Trying to FXZ to 902. Not working. Um uh er uh. Great.
[Motorola Droid Bionic] Reserved Name:
bionic cheesecake

I've check those servers today and only have .232 showing up from a few servers. I also see a bunch of "simpsons" servers named after simpsons characters. So I'm about to check those but i've already checked the rest without seeing anything other than .232
[Motorola Droid Bionic] josdad00:
.235?

I saw on droid hive that .235 is out. Can anyone here check?
[Motorola Droid Bionic] fastpakr:
Where did you see that? I'm not finding anything about it over there.
[Motorola Droid Bionic] cromanorn:
I can't find anything there either. Can you post a link?
[Motorola Droid Bionic] Dave12308:
Someone mentioned it in the Droidhive Shoutbox without any details, and never provided a link. Since then, they haven't been in the Shoutbox and never did create a thread. You might find it digging through the Shoutbox archive, but with no details provided, the only way to know for sure is if someone else checks cheesecake.
[Motorola Droid Bionic] josdad00:
They're talking about it on droid hive in the shout box but no links for download. Several people are saying they are downloading.
[Motorola Droid Bionic] SamuriHL:
Noooooooooooooooooooooooo :D
[Motorola Droid Bionic] josdad00:
There's a guy on Droid Hive uploading it right now.
[Motorola Droid Bionic] SamuriHL:
Yes indeed. I'm going to check it once we have a link and see if they updated the security to disallow going back to 902 from it. So far it's unlikely but never hurts to check.
[Motorola Droid Bionic] josdad00:
http://www.megashare.com/4392491
[Motorola Droid Bionic] darklite41:
I was reading on DroidHive that if you flash .235 you can't go back to gingerbread.
[Motorola Droid Bionic] SamuriHL:
WOA WOA WOA. A big word of caution guys. If you do 235 you will *NOT* be able to FXZ back to 902! The security has been updated. This is a one way trip forward if you do this one.
[Motorola Droid Bionic] linuxgator:
So, over on the Droid 3 forums, there was a similar situation with the .906 update, you couldn't revert back to .890. They figured out that there were certain .img and .bin files that couldn't be written over, but someone managed to put together a modified fxz replacing the files that couldn't be changed with ones from the update, and a modified xml file. Once this was done, you could install the modified .890, and then update to the newer software. It turned out that the .906 leak was in fact what would become the OTA. Does anyone think that something like this is possible for the .235 leak? Thanks to these guys for originally figuring it out on the D3 Q9nap, Redsox985, Psouza4, and Ovelayer.

Here's a link to the D3 thread: http://xdaforums.com/showthread.php?t=1686911
[Motorola Droid Bionic] SamuriHL:
I'm aware. NOT going to happen in our unique situation. The reason is that the leaks require 905. The method they used on the D4 and RAZR require FXZ files from the version you're updating from. We only have one for 902. And there's no way to get back to 905 from that once you install 235+. Hence, if you install 235, you're stuck there for a long time. Unless an FXZ comes out for 905 or the OTA ICS build. IOW, stick to 232 until the OTA comes out.
[Motorola Droid Bionic] fastpakr:
Pretty sure I know the answer to this already... Is there any chance the .235 update can be reached from both .902 and .905? I'm aware the previous updates didn't allow that.
[Motorola Droid Bionic] SamuriHL:
No chance at all. Updates well, um, update files on the system they were designed to update from. 902 != 905 so when patching files you'd be left with a mess. lol :)
[Motorola Droid Bionic] brandogg:
No. You have to be on 905.
[Motorola Droid Bionic] fastpakr:
Fair enough. Noticed the new update was slightly larger than the previous ones, hoped it might have been designed to allow more than one upgrade path. Oh well.
[Samsung Galaxy Nexus] Nasdel:
So I was trying to put JB on my GN using this:

pcworld.idg.com.au/article/429778/how_update_your_galaxy_nexus_jelly_bean/[/url]

I reached to apoint where i had 4.04 yakju, but when I put the file to get JB, It said error and aborted, i went to wipe data and reboot, wipe data worked fine, reboot led me to the google home screen and is stuck there.

I can access fastboot. Recovery mode takes me to that android with the danger sign, doing another reset doesnt work, clicking reboot doesnt work.

I'm pretty nooby at this. I read a few other forums and they said something about flashing a new rom or something but I don't understand.

Please help! The phone isn't mine! Need help ASAP before owner finds out I messed up their phone, thanks!
[Samsung Galaxy Nexus] xjman:
If you can access fastboot and your bootloader is unlocked just flash a stock system image.

These are the reasons people shouldn't just one click everything they do. If you understood how fastboot worked you would be golden.
[Samsung Galaxy Nexus] maxearing:
Reflash recovery. Then mount USB storage and then get a ROM on there and flash it.
[Samsung Galaxy Nexus] Nasdel:
The site I went to dumbed down everything, and all i had to do was input numbers into some program. I double checked what a fastboot was. I definitely don't know how to work that. I mixed up the fastboot with the bootloader...
[Samsung Galaxy Nexus] Nasdel:
how do i reflash recovery and get a rom on there? I know this is asking alot....sorry

My bootloader is unlocked but im not rooted. I will (figure out how to) root if needed.