yashsingh1/xdaforums huggingface dataset:
[Asus  Eee Pad Transformer Prime] sdelliott31:
I have owned an iPad which I still have, the TF which I just sold and a Dell Streak 7. Phones, I've owned all 3 major platforms and multiple of each.

I was deciding between the TF Prime and the iPad 2. I'm unhappy with some of the fc's of honeycomb with the lag, no matter how much you overclock it. Even the custom roms though cool features can't get rid of the occasional stutter. Therefore I was heavily leaning to the iPad 2 until today.

I've been getting reacquainted with my OG iPad as mainly my kids use it. But I've always enjoyed the AirPrint feature, since 4.2 update. I recently upgraded this to 5.0. Today I needed to print out my schedule tomorrow and realized e iPad could not find a printer.

After a couple hours of resetting and Internet searching it turns out the update did away with universal airplay sharing. WTF!!!!! This was one of the big features of the 4.2 update in your commercials now to take it away unless I jailbreak, upgrade printers, or buy an app that I didn't have to pay for before, is crap.

RIP Steve Jobs but a big FU!! To Apple it's crappy camera, lack of ports, lack of gps, and lack of looking out for the customer. I may just wait a few months on android tablets which is disappointing but I'm done with Apple and their shady business schemes, much the same that they cried about with microsoft in the 80's and 90's when they were the little guy.

I'm a very angry little elf!!!!
[General Questions and Answers] Briteyez83:
Purchased clockwork mod bootstrap recovery, installed and i am currently unable to boot into recovery. Every time i try, the m logo comes up and then i get a blank glowing screen. So then i have to pull battery and power back up. Does anyone have any suggestions on what i should do?
[Eee Pad Transformer General] lemonoid:
Okay, I figured I wouldn't have the money to get the Prime and I've heard so many good things about the Transformer, I couldn't wait any longer. I am not a noob to rooting, ROM's, kernels, and unbricking devices I've had an Android devices since the first week they were sold in the US. I have a newer B70 device, which I just rooted with Razorclaw one-click root. I checked root with TItanium and all is well. I've browsed through the forums doing some homework and just had a couple of questions. I don't know if I can use NVFlash with the newer model since a newer root method had to be used? I want to flash custom ROM's, particularly the Prime and check out newer kernels. Could anyone help me in this area. As in does anyone know what I can and cannot do with the newer model? I'm running the 8.6.5.19 update right now. This is a non-3G 16GB device. Sorry if there was a reference thread that I looked over, but I did indeed browse for a while. I also mainly want to know what's up with CWM and the B70 models. Also, I am running linux mint and have my ADB rules file and environment set up correctly, as I use ADB on my bionic and incredible on a pretty regular basis. I made sure that I had the ASUS vendor ID in there, which I already did (guess I knew I was gonna buy one), turned on USB debugging and tried to check if it was working. I get

List of devices attached

????????????? no permissions
[Eee Pad Transformer General] baseballfanz:
For CWM recovery you can use this to install it.

http://xdaforums.com/showthread.php?p=319421

As for B70 andNVFlash, the early B70 with SBK V1 is compatible with NVFlash.

Look for SBK Detect app in dev section, run it to see if your B70 is SBKV1 or SBK V2
[Eee Pad Transformer General] lemonoid:
So pretty much as long as i can get into working custom recovery i can flash any ROM unless otherwise stated though?
[Eee Pad Transformer General] atothis:
I have a B70 SBKv2, using only a rooted stock, without CWM.

The main difference between older and newer SBK is the ability to use NVFlash to either flash a rom or, most important imo, return to a clean stock rom and recovery in a very easy way.

If you have a SBKv2, consider that you can use CWM for flashing and reflashing like any other TF model, BUT it's more risky if your device bricks.

NVFlash is the only method to recover from an hard brick, and atm newer devices can't count on that.
[About XDA developers] lexyin:
I find the GT5830 ROM,then flash it,but non of this hava chinese language ，China hava so many people like GT5830 ，why not give them a chinese ROM?:confused:
[About XDA developers] Spex:
find them on samfirmware.com if your looking for stock rom
[Upgrading, Modifying and Unlocking] FailLord:
Hello, I have rooted my LG Genesis from US Cellular and would like to flash 2.3.4 onto it. This is a 2.2.2 phone, if that is of any significance. I have looked everywhere and cannot find a solution to this problem. Any help is appreciated. Also, ROM manager does not have this phone in its supported phone list. I need to make a backup before I flash the ROM, obviously. Thank you in advance.
[Upgrading, Modifying and Unlocking] Applesarekool:
Getting This Phone Soon.

I've been looking into this phone, because it's actually going to be my father's first smartphone. In terms of flashing 2.3.4 on it.... I'll cross my fingers, but I'm not holding my breath. It has a unique form, because of it's dual screens, which in my mind would make it harder to port, and another problem is that as far as I can see, no dev has given any love to creating a custom recovery. I'm just starting out on the whole developing side, instead of just using what others have created. I hope for both our sakes it gets ported. For now, we need a custom recovery and a custom built rom. X.x Joy.
[Upgrading, Modifying and Unlocking] moparfreak426:
There isn't even any where ive found about rooting the Genesis.... Would love to be able to get ics on it..... Great phone. Love the physical keyboard. Any pointers to any development for this phone?
[Upgrading, Modifying and Unlocking] Applesarekool:
Rooting Genesis

Its been talked about before on Android Forums or something. The genesis is STILL running Froyo, so Gingerbreak.apk works like a charm.
[HD2 Android Q&A, Help & Troubleshooting and Genera] hd2droid1:
Hello all, I have been running android on my hd2 for almost a year now with close to 0 problems, I love it! I am currently running cm7 and it boots from nand. That's all I know about what I am running, I am getting a little bored and would like a new rom (stock as possible) that is running sense 3.5. I need help, I am afraid to try something new, I am afraid to screw everything up. Also, is there a rom from the sensation XE that can be ported to HD2? Thanks and please help
[HD2 Android Q&A, Help & Troubleshooting and Genera] saeid63t:
try this one

http://xdaforums.com/showthread.php?t=1275119

recommend

task 29

if you use mgldr flash 230 CRW for EU and 330 for tmob

wipe data and dalvik catch

make secound ext3 or ext 4 partition on sdcard

copy crw zip to sdcard fat partition and flash it

follow instructions

reboot phone after ROM flashing end

wait 15- 20 min for first boot
[HD2 Android Q&A, Help & Troubleshooting and Genera] luba6ky:
For the first question ... you can't screw nothing unless you install wrong radio.

You can try this stock 3.5 sense - http://xdaforums.com/showthread.php?t=1316632.

For the second question ... the XE and the Pyramid are very simmilar and that is the reason for no seperate section for XE. If you want Sensation Rom try - http://xdaforums.com/showthread.php?t=1075703
[HD2 Android Q&A, Help & Troubleshooting and Genera] saeid63t:
http://xdaforums.com/showthread.php?t=1075703

this rom is out of date and dungphp stop development of this rom and he work on Runnymede roms

could be find under http://xdaforums.com/showthread.php?t=1268580
[HD2 Android Q&A, Help & Troubleshooting and Genera] m-dimitris:
hd2 android help

hello i need some help with an htc hd2, i am trying to flash android rom from win 6.5. i flashed the hspl 2.08 flashed the ratio and after flashing the magldr the phone stucks on htc white screen. need some help please.....
[HD2 Android Q&A, Help & Troubleshooting and Genera] saeid63t:
Probably your radio version was wrong flash a radio that ended to x.x.50
[HD2 Android Q&A, Help & Troubleshooting and Genera] stevedebi:
This rings a bell. Isn't that normal until one flashes a ROM?
[HD2 Android Q&A, Help & Troubleshooting and Genera] saeid63t:
No after flash mgldr

Mgldr menu must come up
[HD2 Android Q&A, Help & Troubleshooting and Genera] tecle2595:
+1

sent from my HTC NexusHD2 provided by Tytung

---------- Post added at 06:06 PM ---------- Previous post was at 05:39 PM ----------

actually if you hold the power button it will take you straight into magdlr
[HD2 Android Q&A, Help & Troubleshooting and Genera] n311.dunkle:
So if the magdlr screen comes up with a blank menu then I can conclude I missed a step.

Sent from my SGH-I897
[Samsung Galaxy Nexus] Luxferro:
I just went to update my gnex manually, and both stock recovery and CWR told me that the signature was wrong.

So I looked in the update zip and saw the following

assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "google/yakju/maguro:4.0.1/ITL41D/223971:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "google/yakju/maguro:4.0.1/ITL41F/228551:user/release-keys");

Then I looked in my build.prop and saw that I have a different fingerprint, and that is why I won't let me manually update.

ro.build.fingerprint=samsung/yakjuxw/maguro:4.0.1/I9250XWKK5_ITL41D/163402:user/release-keys

looks like mines from samsung rather then google.

edit: just to clear up for what region this build is meant for
[Samsung Galaxy Nexus] matt2053:
Will you post the rest of your build.prop?
[Samsung Galaxy Nexus] Chirality:
Looks like it's also running an older baseband - XWKK5 rather than XXKK1. Perhaps, like the first person who got the GN in the UK, you got a prerelease phone that was never meant to be sold at retail?
[Samsung Galaxy Nexus] xHausx:
Is it normal for Samsung to use release keys on their test software though?
[Samsung Galaxy Nexus] Luxferro:
My baseband is K1, just says otherwise in the fingerprint. Here's the build.prop

# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=I9250XWKK5_ITL41D
ro.build.display.id=I9250XWKK5_ITL41D
ro.build.version.incremental=163402
ro.build.version.sdk=14
ro.build.version.codename=REL
ro.build.version.release=4.0.1
ro.build.date=Sun Nov 13 04:05:52 KST 2011
ro.build.date.utc=1321124752
ro.build.type=user
ro.build.user=dpi.sec
ro.build.host=DELL159
ro.build.tags=release-keys
ro.product.model=Galaxy Nexus
ro.product.brand=samsung
ro.product.name=yakjuxw
ro.product.device=maguro
ro.product.board=tuna
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=omap4
# ro.build.product is obsolete; use ro.product.device
ro.build.product=maguro
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=yakjuxw-user 4.0.1 I9250XWKK5_ITL41D 163402 release-keys
ro.build.fingerprint=samsung/yakjuxw/maguro:4.0.1/I9250XWKK5_ITL41D/163402:user/release-keys
ro.build.characteristics=nosdcard
# end build properties
#
# system.prop for maguro
#

rild.libpath=/vendor/lib/libsec-ril.so
rild.libargs=-d /dev/ttys0
telephony.lteOnCdmaDevice=0

#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-google
ro.error.receiver.system.apps=com.google.android.feedback
ro.error.receiver.default=com.samsung.receiver.error
ro.setupwizard.mode=ENABLED
ro.setupwizard.enterprise_mode=1
ro.config.ringtone=Girtab.ogg
ro.config.notification_sound=Proxima.ogg
ro.config.alarm_alert=Cesium.ogg
keyguard.no_require_sim=true
drm.service.enabled=true
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
ro.opengles.version=131072
ro.sf.lcd_density=320
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
ro.com.google.gmsversion=4.0_r1
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt

I guess I'll have to use the full system images to update my phone, as I'll never get the update.
[Samsung Galaxy Nexus] Chirality:
The product name is different, it's yakjuxw instead of yakju, which means it's meant to be a different device than the normal release device that most people got (though that doesn't necessarily mean there are any hardware differences.)
[Samsung Galaxy Nexus] Luxferro:
Yeah, I initially noticed that too. Hopefully the hardware is the same and I won't run into any further issues once I flash the latest images. I created a nandroid just in case though.
[Samsung Galaxy Nexus] Luxferro:
The odd thing is I only got the phone Friday from Expansys. Appeared to be brand new :confused:
[Samsung Galaxy Nexus] waylo:
I have the same thing on mine! No wonder... I've been waiting forever for the OTA update.

Shipped to me Thursday from Negri, here in the US. Picked it up at the Fedex depot on Saturday.
[Samsung Galaxy Nexus] Chirality:
Hmm...maybe Samsung pushed out their own update to fix the volume bug because they thought Google was taking too long. Perhaps this is what those retailers meant when they said that Samsung did additional testing and fixed some batches?
[Samsung Galaxy Nexus] Luxferro:
Yeah, that's probably why a lot of people aren't getting the update.

I'd assume if there are enough people out there with the same builds, google will have to make another update for us. I just want to know if the would be any further issues if we updated using the full system images. Like will we get updates in the future, or is something different with our phones? or the IMEI's
[Samsung Galaxy Nexus] Luxferro:
I doubt it, cause the build date in the build.prop is ro.build.date=Sun Nov 13 04:05:52 KST 2011
[Samsung Galaxy Nexus] waylo:
So I'm guessing this means we can't apply the updates that are made for the newer builds then?

Hmm...

Well actually, if you take the factory images released, you/we can write over our existing data.

http://code.google.com/android/nexus/images.html

EDIT: Oops, saw that you already realized that in one of your first posts.

Crap, that means a lot of erasing and restoring again!
[Samsung Galaxy Nexus] serialtoon:
Man i feel like waking up extra early tomorrow to cancel my GN pre-order. This is turning out to be a huge fiasco.
[Samsung Galaxy Nexus] zyo:
lol honestly what?

Its not a hardware problem, calm down...
[Samsung Galaxy Nexus] Luxferro:
Can someone post the build.prop from normal itl41d?

I'm curious of the build date list in it.
[Samsung Galaxy Nexus] Chirality:
That makes perfect sense. Samsung discovered that they forgot to add debounce to the keys on Nov 10 and patched it on that day. But that patch didn't make it into Google's release build, which was built on Nov 11. Samsung probably realized how bad this would be for their reputation, and since Google wasn't acting fast enough to include the patch in a new build to push out to phones, made their own build of the software image on Nov 13 and flashed it on some batches of phones. Earlier batches did not get the new Samsung image but some later ones did get the fixed image.
[Samsung Galaxy Nexus] blunden:
That's just baseless speculation unless you can prove that the volume issue had already been fixed in that build.
[Samsung Galaxy Nexus] El Daddy:
I have the same build as the OP. I also got mine from expansys-usa last friday.

No update for me.
[Samsung Galaxy Nexus] swapnil:
Just tried it using Astro. Didn't know I could go into /system/ without root. Got a yakjuux :(
[Samsung Galaxy Nexus] demzzy:
...so.... are we gonna take the plunge guys? (those of us that have everything else BUT the yakju) with the google images?
[Samsung Galaxy Nexus] Luxferro:
Did you buy your's from a carrier in canada?

Pretty much how it works, there is the google generic build, and then there are carrier builds depending on region and where you buy it. Some of us who bought imported devices from the UK were givine devices that were obviously meant for either a carrier, or a specific region.

While there is no official confirmation from either google or samsung, they are all the same devices, hardware wise. So you if you want the generic google build just reflash your phone. there are steps in this thread, and elsewhere in the forums. People are making a bigger deal then it already is.
[Samsung Galaxy Nexus] demzzy:
yeah i pretty much came to the conclusion...if u want ota from google flash the images... its the same hardware for alllll the gsm gnexs
[Samsung Galaxy Nexus] 69Pwned:
So if I buy one that's already on 4.0.1 it should be pure Google??
[Samsung Galaxy Nexus] waylo:
Thank you for trying to control the madness here. The rampant speculation is ridiculous.
[Samsung Galaxy Nexus] maybelying:
Regarding the question of whether there are slight hardware differences, can we just compare FCC IDs (or the equivalent for elsewhere in the world)? My understanding is that any changes in the hardware design require a new FCC approval, and since only one GSM model moved through the FCC, couldn't we safely assume the hardware is identical? (And equivalent licensing agencies worldwide for other regions)

Or am I way off base?
[Samsung Galaxy Nexus] demzzy:
well i bit the bullet and all is perfect
[Samsung Galaxy Nexus] nxt:
Bit the bullet here too, turned my yakjuxw to yakju

Update showed up immediately (for the ITL41F)
[Samsung Galaxy Nexus] demzzy:
yup.. as soon as it rebooted the update came up...

i reflashed my radio that my nexus came with.. the kk7 baseband

---------- Post added at 10:27 PM ---------- Previous post was at 09:41 PM ----------

those of you that didnt flash with the google images.... got to settings > about > system updates... and i believe there should be an update waiting..

a friend of mine got the update just now.. and his baseband is now ugkl1
[Samsung Galaxy Nexus] enumBoss:
Still no OTA available for yakjuxw.
[Samsung Galaxy Nexus] demzzy:
his was uux the canadian version..
[Samsung Galaxy Nexus] KayvinM:
Just checked and no update yet. I'm using it on Rogers but I don't think that should make any difference.
[Samsung Galaxy Nexus] scratch42069:
I just got my Galaxy Nexus from Bell Mobility a few days ago and it's a yakjuux. I unlocked the bootloader this evening and on restart I got the OTA update. My baseband is now I9250UGKL1 and the build is ITL41F.
[Samsung Galaxy Nexus] Luxferro:
Do you have adb setup and know how to use it? If so, feel like dumping your baseband? I'm collecting all the different versions :)

Here's what you need to do from adb. This copies the radio into radio.img on the root of your sdcard.

dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/radio of=/sdcard/radio.img
[Samsung Galaxy Nexus] enumBoss:
Any reason you're collecting them?
[Samsung Galaxy Nexus] Luxferro:
Some people have better reception or battery life with different ones. I guess depending on may variables, such as location, carrier, maybe their phone, ect. Go read some of the baseband threads in the development section just to get an idea
[Samsung Galaxy Nexus] dnlsmy:
Got a yakjuxw, when I registered it on Google Music and the Market, it showed up as "Samsung Samsung Galaxy Nexus" and "Samsung Galaxy Nexus"

After flashing the Google image, I can report that the Market now registers it as "T-Mobile Galaxy Nexus" and Google Music registers it as "Google Samsung Galaxy Nexus". My box lists it as GT-i9250. I think the Sammy FW is only a coverup for the volume problem in the UK and they should all go back to Google's image after 4.1, or at least stay consistent in their updates. The only HW difference I can see as being possible is the fact that some chips are able to overclock to 1.4 GHz while others cannot, so this may be where the problem lies.
[Samsung Galaxy Nexus] nxt:
I have a yakjuxw, Google Music says the same thing, but the Android Market website says "T-Mobile Samsung Galaxy Nexus"
[Samsung Galaxy Nexus] dnlsmy:
Strange, Mine only recognized the carrier after going back to the Google Build. I only switched to the Google Build for Google Wallet support, I could really care less if it was yakjuxw...
[Samsung Galaxy Nexus] enumBoss:
Market for me says AT&T Samsung Galaxy Nexus on yakjuxw.
[Samsung Galaxy Nexus] nxt:
Well cuz you're on AT&T. I'm on T-Mobile.
[Samsung Galaxy Nexus] hooman64:
finally someone else with the same question :D ... I felt so alone here, no one seems to know or care to answer, I also posted on few other topics/forums no one answered.

---------- Post added at 06:34 AM ---------- Previous post was at 06:32 AM ----------

where did you order it from?
[Samsung Galaxy Nexus] dnlsmy:
Negri has all yakjuxw's. Expansys' first batch had yakju's. (Firsthand experience)

Negri will give you a US wall-adapter in the box, while Expanys's first batch had the UK plug with US adapter. If you want to check without even opening the box, simply check how the box was sealed. If it has one sticker that says "Do not accept if broken" by Samsung, it's Yakju. If you have a different seal (Like 2 circle stickers) you have a different unit. Expansys and Negri are out of yakju's I believe, but you can always just flash it on later.
[Samsung Galaxy Nexus] hooman64:
hey dude tnx for the quick reply. one question tho, from what I read you had a "yakjuxw" and flashed it with Google image right? where did you get yours?
[Samsung Galaxy Nexus] scratch42069:
Got adb set up and I'll get you a dump of the radio.

Edit: ADB is acting up on me and isn't detecting the galaxy nexus. As soon as I get it straightened out, I'll get that dump of the baseband.
[Samsung Galaxy Nexus] dnlsmy:
Use this thread. Download the files and double-click "flash-windows.bat" while in Fastboot. All instructions are in the first post.
[Samsung Galaxy Nexus] enumBoss:
Yeah. I have a yakjuxw from Popular Electronics' first batch. They said it came from Latin America. US adapter in the box and seals broken.
[Samsung Galaxy Nexus] nbeebe24:
The version doesn't matter to me whatsoever, but I kinda wish I knew. I started rooting my nexus literally seconds after turning it on
[Samsung Galaxy Nexus] premler:
I have now transformed my swedish "yakjuxw" to a "yakju" using this method.

http://xdaforums.com/showpost.php?p=20196513&postcount=129
[Samsung Galaxy Nexus] kinggheedora:
Are you saying that you didn't check the ROM version that your phone shipped with before you flashed over it, and now you have no way of finding out what it was?
[Samsung Galaxy Nexus] efrant:
I'm planning to flash the yakju build as well, but I would like to pull a backup of my current bootloader (which is different from the one included in the yakju build) before I do so. My current bootloader is PRIMEKK14, while the version included with the yakju shipped image is PRIMEKJ10.

Can anyone tell me how to dump the bootloader? I'd be more than happy to post it once I do.

(As an aside, has anyone seen an engineering bootloader floating around yet?)
[Samsung Galaxy Nexus] dnlsmy:
Thanks I forgot to be back up mine. Is it a yakjuxw?
[Samsung Galaxy Nexus] hooman64:
no I meant where did you order it from?
[Samsung Galaxy Nexus] nbeebe24:
Yes that would be correct
[Samsung Galaxy Nexus] as0k:
Did you notice any difference, or is everything the same as before?

I also have a swedish yakjuxw.
[Samsung Galaxy Nexus] mantrain42:
I just did this, though with a danish bought phone - It works, looks pretty much the same. Only thing I've noticed is more add-on dictionaries installed - Still no option for danish though.
[Samsung Galaxy Nexus] efrant:
Did you manage to dump the radio and post it somewhere? Thx.
[Samsung Galaxy Nexus] Guto ViP:
Can i access build.prop file without root? with some code? I ask because my friend (in another country) has buyed one Nexus to me and i want to know this info...

Sorry about my english.