yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] ericshmerick:
Terrible decision. I have the 16gb GSM version (imported) and it is fine for me since I have unlimited data, but it seems like a no-brainier to just use the 32gb chip for those who have data limits.

What could the raw material cost differential possibly be between the 16/32 chip? Like 5 dollars?

Developer phone or not, it's 2012 and not having expandable memory is bad enough...stifling this phone to just 16gb is a curious decision by google/Samsung.
[Samsung Galaxy Nexus] [hfm]:
Stop saying it's a developer phone. It is not. Google has been advertising it to the general public in many high profile media channels, and it definitely never said 'developer phone expect problems' anywhere in the creative or spots.

This developer phone argument needs to stop.
[Samsung Galaxy Nexus] ericshmerick:
If it isn't, what's the current developer phone model?
[Samsung Galaxy Nexus] p00kienrayray:
I agree. Just bc it's google's own branded phone and developers like to tinker with it doesn't make it a "developer phone." Some people get it not to flash buttloads of roms, but simply bc they want an unbranded android experience.
[Samsung Galaxy Nexus] [hfm]:
There isn't one. What's the current apple dev phone?
[Samsung Galaxy Nexus] haydonxda:
Hmm. Don't know. I watched the entire GN launch and I can't remember them going on for hours to an audience of developers talking about all of the new APIs and how to call them.

It sort of seemed like - a phone launch. Go figure. It was targeted at people interested in using the device, like how awesome the camera was, how cool face unlock was, etc.

I have an Android development platform. Guess what, no slick case, no mention of an AMOLED screen (no screen at all actually), and no battery/charger.

That's a development system.

... Not the GN's highly polished and styled, mass marketed, feature laden, slick encased self.

People need to stop calling these "phones" and "developer phones" just as an excuse for things that don't work or aren't delivered. (If you haven't noticed, it's not just "developer phones" that get this "special" treatment.)
[Samsung Galaxy Nexus] [hfm]:
Truth. Again, I love Android and what Google has accomplished, but the apologist attitude towards these real and annoying problems is strange.
[Samsung Galaxy Nexus] Sleuth255:
I've never seen so many developer options in phone settings as this phone has. Fastboot makes it pretty much unbrickable. Complete set of AOSP tools and stock images for it. Yeah, its a developer phone all right.

That being said, its also a Nexus which brands it as a Google flagship phone. So everybody's right.
[Samsung Galaxy Nexus] Super Chimp:
It's not being sold as such. When I see the current adverts for it I saw no mention or concentration on these things. So to me, yes it does these options, but that doesn't make it a developer phone.
[HTC Incredible S] turtle*:
Its been a while since i've played with phones. I had my N1 for 2 years on CM7 stuff.

I just got this incredible S, so i figure now is the time to update stuff if needed. The previous owner told me he got the S-off done by a pro using the CLIP.

Phone says LOCKED on top =(

Let me know.
[HTC Incredible S] tpbklake:
You are indeed S-OFF. The LOCKED is from the latest bootloader 2.00, but since you are S-OFF, you can still flash CWM recovery and root the phone without 'unlocking' the bootloader.
[HTC Incredible S] turtle*:
god its a little annoying. all my buttons are goofy.

My power button on the N1 is top left. on the incred its top right. I keep pushing a non-existent button. Plus my backarrow button on the N1 is 1st button VS 3rd on the incred.

I see a lot of people using 4ext instead, is that better? I'm kinda wanting to try OEM stuff first since i never used sense.

Why is the vibration so weak for the keypad? Its almost nothing. but the vibration during a call is decent. I thought my motor was bad.

Should i update the radio or anything else.
[HTC Incredible S] tpbklake:
You've already got a really recent radio, so I wouldn't bother.

4ext Recovery is required to flash some of the custom ROMs and is completely backward compatible with CWM as far as backups are concerned. Again since you have S-OFF, you can try 4ext and if you don't like it just flash CWM instead.
[Samsung Galaxy Nexus] The_other_ray:
I heard about this. Is it true?
[Samsung Galaxy Nexus] martonikaj:
Read the freaking threads and articles.

The 32gb GSM version is rumored to be cancelled and won't be coming out.

Seriously. All you have to do is read just one article from a major tech blog and you'll understand it.
[Samsung Galaxy Nexus] sn0warmy:
People are absolutely terrible at this today. Not a single one of the people who posted a thread about this took even 10 seconds to notice the other 2-3 threads about the same thing within the same section.
[Samsung Galaxy Nexus] The_other_ray:
I tried searching for something about it on the forums but the Android tapatalk app's search feature looks through everything rather than isolating it to the galaxy nexus so I couldn't easily find it.

But thanks for the help.
[Samsung Galaxy Nexus] nabeelster25:
if you took the time to scold the person who posted this thread, you could've just given them a straight answer. Freakin' people these days....
[Nook Color Q&A, Help & Troubleshooting] blackpiranha:
Hello!

I have some problems rooting my nc with manualnooter 5.02.12. Before this I unrooted my device (by doing that: http://www.youtube.com/watch?v=szlGSBtWbKY) and then updated to 1.4.1 (working fine). Then I copied the manualnotter-zip-file on my "8gb_clockwork-3.0.2.8.img"-sd-card and installed the zip-file.

But at next start, my nook gets stuck at the "read forever"-screen forever. I tried this three times, always with the same negative result.

What am I doing wrong?
[Nook Color Q&A, Help & Troubleshooting] Lanternoil:
it seems your new image that you were installing may have had an error. I would try to download a new image, possible from a different site. It sounds like after wiping the boot not much else was installed
[Nook Color Q&A, Help & Troubleshooting] hoangtu2410:
try wipe all, wipe cache and wipe dalvik cache, it's work for me
[Nook Color Q&A, Help & Troubleshooting] dadmarshall:
I had the same issue. I found that if I updated my sd card to CWM 3.2.0.1 and reloaded both the MN 5.02.12 and Dal's OC kernel zips I corrected the problem and didn't have to wipe or rebuild anything else.
[Nook Color Q&A, Help & Troubleshooting] ahfo:
edit the file in manualnooter-5.02.12.zip\tmp\scripts\uramdisk.sh

change the line below

mv /boot/uImage /boot/uImage.cwbak

to

#mv /boot/uImage /boot/uImage.cwbak

save and flash again，it work for me
[Nook Color Q&A, Help & Troubleshooting] blackpiranha:
sorry for my late feedback, had not much of time.

I will try your proposals later that day, thanks!
[Nook Color Q&A, Help & Troubleshooting] myl0h:
Ive been having the same problem as well. So I updated CWM , redownloaded mn, read some of the tips and finally got it working. I ended up having to wipe cache and i used the app2sd w/ the dalingrin kernel. Rebooted and then it was good. I assumed app2sd needs a sd card, but apps from the market saves to internal memory. I'm confused, but at least its working.
[Nook Color Q&A, Help & Troubleshooting] GMPOWER:
I fixed the script problem in the 5.02.19 release. You can flash one of the kernel images to fix the problem. I am sorry about the problem.
[Samsung Epic 4G Touch] alizonmi:
Hi everyone i need help! Im trying to use odin to undo root on my epic touch. Unfortunately, my computer is not able to detect my phone. When i plug in the phone to the computer all it does is charge. USB debug is off and im not sure what else i need to do. The computer does have samsung kies drivers installed.
[Samsung Epic 4G Touch] Epix4G:
And search this has been covered a hundred times

First thing is try different USB cable and I'd then reinstall drivers I'd that doesn't help
[Samsung Epic 4G Touch] jprocha101:
USB debugging needs to be on, not off
[Samsung Epic 4G Touch] avianp:
It doesnt sound like you are in Download Mode. Bottom volume + Power.
[Samsung Epic 4G Touch] JohnCorleone:
Also try rebooting PC, someone already mentioned different USB ports, reinstall Odin, etc.
[Samsung Epic 4G Touch] alizonmi:
I tried rebooting the pc, using a different cable, and reinstalling Odin. I still cant get my phone to detect in odin mode. Any advice or help please?
[Samsung Epic 4G Touch] Ja5oN:
Any dinging noises when pluugged into the computer? Is your phone recognized in device manger?
[Samsung Epic 4G Touch] Epix4G:
http://www.youtube.com/watch?v=xJ5XZIlGwNY&feature=youtube_gdata_player
[Samsung Epic 4G Touch] rbtrucking:
This sounds like your problem. Same thing happened to me first time I tried to root.
[Samsung Epic 4G Touch] alizonmi:
No dinging noise and the phone is NOT recognized in device manager. I think i may have a faulty USB port on the phone.
[Samsung Epic 4G Touch] patrao_n:
although the op doesn't say I have to ask. what did you flash before trying to unroot. did you put the international ics on there?
[Samsung Epic 4G Touch] alizonmi:
I did not put on ICS. I am currently runnning caulkin rom
[Samsung Infuse 4G] ntorresla:
hi everybody, here in Ecuador, data speed connections are not the fastest in the world, I mean, with 2g (edge) I can download (in a very good day) at 22.6 kb/s and with 3g at 178 kb/s.

I see a lot of modems and tested several, but I want an opinion, and heres my question.

since I dont have fast connections, wich modem can I use to help me improve my battery life?

I sacrifice speed but i least i can have some battery.

Im currently using CWM-UCKK4, and easy battery saver in advance because I like my sync every couple of hours.

thanks in advance
[Samsung Infuse 4G] diablo009:
Try KI3.. on 2G I got over 3 days standby with a few hours of calls and a couple hours display.
[Samsung Infuse 4G] Erik_T:
That's the modem man right there. Problem solved for you. :D

Next time, that would be a good question for his thread, sticked in dev.

Watch this http://www.youtube.com/watch?v=JmvCpR45LKA
[Samsung Infuse 4G] ntorresla:
Thank you for the attention both, of course I watches the video, but my newly account didnt let me ask in diablo thread.

:o
[Samsung Infuse 4G] diablo009:
Wow. I didn't notice until now that my thread was stickied. Thanks for letting me know this :)

By the way, I am on vacation for my sis wedding for about 10 days starting this weekend.
[Samsung Infuse 4G] ntorresla:
Congratulations!!!!
[Samsung Infuse 4G] diablo009:
thank you...
[Atrix 4G General] nvd425:
hi. i'm pretty new to all this. a few months ago, i unlocked the bootloader on my atrix 4g and also rooted it. i then flashed the ICS CM7 rom using cwm. after a few days of playing with the new rom, i decided to go back to 2.3.4 by flashing the 2.3.4 fruitcake. i see now that 2.3.6 ota update is available when i check for updates from my phone. if i install this ota update, will i brick my phone? i still have the unlocked bootloader but no longer have root.
[Atrix 4G General] gnahc79:
Applying the 2.3.6 OTA on a fruitcake 2.3.4 may cause a soft brick/boot loop. IMO wait until others respond with more definitive results. Don't be the first guinea pig :). I had a stock, locked and rooted 2.3.4 prior to the 2.3.6 update.
[Atrix 4G General] stewartsoda:
Don't quote me on this, but if you flashed back to 2.3.4 using RSD and then applied the update you should be okay. Caveat emptor, as always, and do it at your own risk.

There may be some unknown consequences, though. Maybe flashing back to 2.3.4 after applying the update will brick your phone, like the 2.3.4 update did with 1.8.3. You will definitely lose root, and from what I hear some of the old rooting methods don't work anymore.
[Atrix 4G General] RobKort:
If you are rooted and unlocked and had modified systems flashing worth RSD lite to get back to stock is the way to go before the update. Flashing back to .91 after installing the update WILL brick the phone for sure so don't.

Sent From Rob's ATRIX.
[Atrix 4G General] Miguelyl:
If you are using fruitcake 2.3.4, the OTA update to 2.3.6 will work, as the difference between a fruitcake 2.3.4 and the official one is that it does not touch the recovery and boot. As your phone was running official 2.3.4 before cm7, the changes to boot and recovery are already in place. The only possible downside is that you will not be able to roll back to "official" 2.3.4. You will have to flash CWM and flash fruitcake 2.3.4 to roll back.
[Atrix 4G General] Dogie52:
This isn't stock ICS is it?
[Atrix 4G General] Miguelyl:
No, it is the latest gingerbread update.
[Atrix 4G General] Dogie52:
Alright thanks :)
[Atrix 4G General] gnahc79:
I think I get it...almost :).

Could you verify #2 and fill in #3?

1) locked, stock 2.3.4: recovery and boot are stock

2) unlocked, flash CM7 or other ROMS: recovery and boot are NOT stock...applying the 2.3.6 OTA at this point can semi-fubar your phone with a bootloop and/or softbrick

3) fruitcake 2.3.x : recovery and boot are ???...applying the OTA = ???

I searched xda and could not find anything stating that applying future OTAs over a fruitcake 2.3.x will be successful. My search skillz could be lacking, so apologies ahead of time :).
[Atrix 4G General] Miguelyl:
2) You cannot OTA update from those roms, there is no way to do it. I doubt anyone will even try to update.zip the OTA over CM7 or any other custom rom.

3) Recovery is non stock, boot is stock (as last official update installed). After the update, stock recovery will be installed, boot will change to 2.3.6 so it will prevent downgrade. Will have to flash CWM again to have access to custom roms and fruitcakes.

This is as I understand it. If anyone has more info you are welcome to share.
[Atrix 4G General] Miguelyl:
Update on this. DO NOT UPDATE ON AN UNLOCKED BOOTLOADER!!! FRUITCAKE OR ANY OTHER CUSTOM ROM. YOU WILL BRICK. WAIT FOR FRUITCAKE.
[Atrix 4G General] Eionai:
Well, crap. Wish I had seen this beforehand. My phone is currently stuck with 3 green Chinese characters on the screen with the goapk website subtitle.

Have unlocked bootloader, upgraded to previous firmware OTA (didn't flash pudding), no ROMs.

Any suggestions would be much appreciated.
[Atrix 4G General] gnahc79:
thanks for the update. that's what I thought...once you unlock you can never apply any future OTA updates. After unlocking you can get 'stock' only through fruitcake.
[Atrix 4G General] Miguelyl:
You are stuck on recovery. Goapk is tenfar cwm recovery. Fastboot wipe and then flash 2.3.4 fruitcake.

---------- Post added at 10:31 PM ---------- Previous post was at 10:24 PM ----------

You can normally rsd lite to 4.5.91 but there are reports that after doing that, updating

to 4.5.141 results in a brick. Some have succeeded, some don't.

So the safe route is to wait for fruitcake.
[Atrix 4G General] Dark9781:
For those afraid of losing root

It is true you will lose root after updating and the current root methods no longer work. However, there is one method that still does; the fastboot method. Instructions and files can be found here:

http://www.atrixforums.com/forum/mo...ons-including-stock-locked-2-3-4-2-3-6-a.html

(Note: Instructions are right after Pete's Root Tools Method)

In order for this to work you will need to make sure that all traces of root has been removed from you phone or it will fail to write su to the correct directory due to not enough memory being available. There are a few ways to remove all traces of root. One way is to flash the sbf file of the current version you are on. After flashing just uninstall superuser like you would uninstall any other app.

Another method of completely removing all traces of root is through the preinstall root method. It can be found at the same link from above under How to Un-root after using the /preinstall root method (I think this will only work if you used the fastboot method to gain root, I have not tried it myself).

You could also use the Motorola Software Update Tool to flash the update which should remove all traces of root. It can be found here:

http://direct.motorola.com/hellomot...SoftwareUpdateforATTATRIX4Gversion.4.5.91.pdf

As of right now the fastboot method seems to be the only way to root this version of the software. I actually tried all the current methods including the recent Motofail method that was discovered by Dan Rosenburg, but all have failed.

As a side note, those that are waiting for an official ICS rom will be getting one in the 3Q. Check it out on Motorola's Software Upgrade News page.

https://forums.motorola.com/pages/00add97d6c
[Atrix 4G General] jaketc:
Not sure if this helps anyone, but I had...

1) Stock 2.3.4

2) unlocked bootloader

3) rooted via fastboot (never flashed custom recovery)

4) used Voodoo OTA bootkeeper

5) followed bootkeeper instructions

6) updated to 2.3.6

7) re-rooted

8) currently i have no unlocked bootloader
[Atrix 4G General] G-Man.:
I am unlocked, and RSD'd back to stock .91 and then applied the update and got a soft-brick - I did discover that I was able to flash the 2.3.6 sbf and it worked fine.... The preinstall method gave me root access back... I would not recommend trying to downgrade back to 4.5.91 after upgrading to 4.5.141 until we have more info about it....
[Atrix 4G General] NameLessThugZero:
Okay so if I used the pudding method(2.3.4/4.5.91):

1)am I unlocked, or just rooted?

2)what method should I use to install the 2.3.6 update?

OTA obviously isn't working, and I'm thinking I can just flash back to another rom, then OTA update ..any suggestions?
[Atrix 4G General] anupash:
How is the overall feedback of this OTA update? Ya I have seen the change logs but real world feedback from users is always important.
[Atrix 4G General] Domingo2010:
Excause me guys but what languages are inclueded in this new firmware?;)
[Atrix 4G General] gnahc79:
Nothing major really...I can't tell much of a difference. Some are experiencing better wifi stability, some are experiencing much worse wifi stability,
[Atrix 4G General] rjohnstone:
No, you will not brick your phone.:rolleyes:

The OTA update will simply fail to install.

The OTA update requires the stock recovery. It will fail if you have CWM or any other custom recovery installed.

The failure will not brick or even soft brick your device. It will simply abort before any changes are made.

You will not get a brick if you RSD to stock 4.5.91 and update via OTA process.

I used RSD to get back to stock during the SOAK tests... worked perfectly.

You can safely RSD back to stock 4.5.91, even with the blown fuse.

This will not brick your device.

I did it 4 times during the SOAK tests to verify it works.

You will not lose your unlock, it will just be hidden until you rerun fastboot oem unlock.

Once you're back on the stock image with the stock recovery, the OTA will work just fine.

You can then proceed to reroot your phone and load CWM or any other custom recovery.

All the same methods to gain root on 4.5.91 work on 4.5.141. ;)

I've tried running the OTA update with a fruitcake stock 4.5.91 and it failed due to the lack of the stock recovery.

Not once did I run into a softbrick.

The OTA update either worked or failed before any changes were made.

As with all things, if you are unsure what you're doing, stop and ask questions.

Better to ask a dumb question than risk bricking your phone. ;)
[Atrix 4G General] modman21:
How to ignore/hide the update message

I tried searching for an answer to this but nobody seems to mention it. Does anyone know how to hide the update message permanently? Right now the message only gives me options to postpone for 1 hour or download. I don't want to update because I'm going to be flashing the CM9 in a week or two and I don't want to mess with my bootloader or root since all the tools right now are designed for 2.3.4.
[Atrix 4G General] tobnddl:
Stopping the OTA Update message

I used Titanium Backup to freeze the FOTA process. This seems to have calmed the storm with no repercussions. (ATT MB860 (US) running Alien with v6 Supercharger and some custom tweaks)

EDIT: After getting no message for ~24 hours since freezing FOTA, I just got another message. I just froze "Updater 2.3.4", and will freeze "Upgrader 1.00" if this doesn't work. Will post results as I get them.

EDIT 2: Updater 2.3.4 was the key file. Freeze this and the update messages stop.
[Atrix 4G General] gnahc79:
sweet, a definitive answer :). Stock recovery is required for the OTA update.
[Atrix 4G General] Eionai:
@rjohnstone, I think there is quite a risk of soft-bricking your device. I was on a unlocked bootloader with a stock ROM and bricked my phone when trying to OTA. My phone has already failed flashing a SBF once and I have to try again later today.
[Atrix 4G General] bwshockley:
This is not completely true. I used RSD Lite to get back to stock 4.5.91, Wiped everything, Factory Reset as much as possible. No Root, No custom recovery etc. and each and every time I tried the OTA update to 4.5.141 I got a soft brick, Failed to Boot Error 4. The OTA would "install" get through the entire process and reboot the phone, get stuck in boot for about 30 seconds, then the error 4 appeared. RSD the sbf and was running again, but it did soft brick. I am unlocked. I have been rooted, installed numerous different custom ROMS, CWM etc in the past. Somewhere something must have messed up my phone just enough that even an sbf back to stock could not reset it.

YMMV - but each case is different.
[Atrix 4G General] rjohnstone:
Did you have a custom recovery or was your stock ROM rooted?

A rooted stock ROM "can" cause issues with the update process.

Also, if you used TiBu to freeze any system apps prior to the update process, you will risk a soft brick as well.

When I say this works with the stock image, that's what I mean... you have to be completely stock 4.5.91 with the stock recovery before you run the OTA update.

Some users were able to run the OTA pdate with a rooted device, but that's all they had done.

They still had stock recovery and the system apps were untouched.

Having an unlocked bootloader is a non-issue and the OTA update does not re-lock it.

If you used RSD back to a stock 4.5.91 image, there would be no need to do a factory reset/wipe.

RSD to stock, run through the new phone setup process and then run the OTA.

Error 4 is usually caused by a bad flash.

Check your RSD version (should be 5.5 or higher) and make sure your USB drivers are up to date, also make sure your battery is fully charged before using RSD.

I know it sounds trivial, but an outdated driver can cause a bad flash.
[Atrix 4G General] bwshockley:
Were you the guy who sent me a link for the stock SBF on the Motorola SOAK forums? I used a "stock" 4.5.91 sbf. However, i was going to try another one, but the link died (megashare or whatnot). I never got another sbf to try. I used an SBF from XDA - can't remember which thread. I even tried moto-fastboot from this thread: xdaforums.com/showthread.php?t=1163342 to flash back to stock and that didn't quite do it. The one last thing I haven't tried yet, but might, is to format the system first using CWM before resetting and sbfing again.
[Atrix 4G General] The Balvenie:
Yep, this happened to me.

the only way out of it (for me) was to get a cwm flashable 2.3.6 from http://xdaforums.com/showthread.php?t=1163009&page=55 and the radio posted http://xdaforums.com/showthread.php?t=1163009&page=54

i was on fruitcake 2.3.4 rooted, unlocked
[Atrix 4G General] bwshockley:
Was using RSD 5.6, Latest Moto drivers (installed them just before flashing), full battery. RSD went through fine with no errors. Reboots phone. Phone starts up just fine, log into motoblur etc. redownload OTA and flash and soft brick. :) Maybe it was a bad sbf.
[Atrix 4G General] rjohnstone:
Yes, I sent you the link to the stock SBF. It's the same one I used.

The moto-fastboot versions (fruitcakes) don't include the stock recovery image and are pre-rooted. The OTA won't work with these.
[Atrix 4G General] bwshockley:
It wasn't a fruitcake version, it was "stock" according to kennthepenn's post. Anywho. I'll wait a bit and see if someone creates a CWM flashable 4.5.141 update. OR just go straight to CM9.