yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] Lim Wee Huat:
Take a look and compare the development threads of both devices and you'll find that Samsung Note 10's development had slowed down a lot. Not much of choices too. If you like ROM and kernel developments, go for the Nexus 10. If you like extra features like S-pen, ext SD and stuff, go with Note 10.
[Android Q&A, Help & Troubleshooting] TechMasta:
10 inch tablets on android currently are not that great. I would much rather get a nexus 7 :good:
[Android Q&A, Help & Troubleshooting] teodor79:
Reply

I ave a nexus 7. It's great, powerfull, great gaming experience and it's not expansive. You can buy it, but if you want a 10.1 tablet, nexus 10 has a better resolution, and cortex A-15 processor, or you can wait for the new samsung tablets (coming soon this year).
[Android Q&A, Help & Troubleshooting] rumba:
Thanks guys , i guess i will go for nexus 10 cuz am looking for many choices of roms
[HTC Sensation] fiskeryatigo:
Out of pure curiosity, what're the differences between the MIUI v5 ROM by stickman89 here and the "unofficial" ROM linked on the en.miui.com forum? (direct link to that rom on baidu)

It looks like they're both based on 4.1.2, but that's all I really know about them. Could anyone care to explain any differences in usability, bugs, etc?
[AT&T Samsung Galaxy S II SGH-I777] Kadin:
My internal /sdcard seems to always accumulate a large chunk of files. Just went in there and one file in particular was 2GB in size. I went ahead and wiped them all like I have in the past but I'm wondering if I'm creating the problem with frequent ROM changes, etc.

I've read that this directory can potentially indicate issues with the sd card itself and was just looking to get some clarification. Or is it just the frequent wipes/installs/reinstalls, etc. that I do a fair bit of?
[AT&T Samsung Galaxy S II SGH-I777] Phalanx7621:
I always delete my lost.dir when flashing. As well as any files that accumulate that are unnecessary. Every rom (well nearly every rom) comes with everything needed to make it work built into the rom. Deleting unnecessary files and folders is fine as long as they weren't put there by the rom you're currently flashing.
[AT&T Samsung Galaxy S II SGH-I777] Kadin:
Yeah I've never gone as far as to clean my sdcard in any fashion between rom changes. I like to keep as much on there that I can from previous roms like photos, ringtones, etc. and with my luck I'd delete something that was necessary that I'm not aware of. This kind of brings up another question, is there a guide out there for a general 'how to' on cleaning up old files and what's safe to delete, etc.? I have to believe I've got a lot of wasted space on stuff that's completely useless now that I'm to another rom (which rocks btw).

[EDIT] I of course always do a full wipe and wipe cache/dalvik but I imagine there's still stuff left over... right? Never really looked into it to be quite honest.
[Sony Xperia ZL] bothfly:
Anyone figure out how to get it working over ATT?

I thought it was good to go, but after turning on NFC and downloading the app, it says not compatible.

Which is weird since its an unlocked phone.
[Sony Xperia ZL] frothe3:
Do you need to turn on NFC while downloading? Did you try downloading with NFC off?

Maybe either the frequency or software might not be compatible.
[Sony Xperia ZL] djruckuss66:
Someone with an Xperia Z was able to get it to work. Maybe you could test yourself and report back.

http://xdaforums.com/showthread.php?t=2203482
[Sony Xperia ZL] nik.taylor:
Is anyone else having an issue with NFC. Mine wont switch on. When i tick the box, it automatically unticks. I did copy down a load of app data so maybe i copied over a system one automatically. Any ideas?

Edit: Uninstalled the re-installed Google Wallet. Went in to apps -> NFC service. Cleared all the data and stopped the service. Rebooted the phone and it worked fine. Chose Google Wallet as wallet provider, turned the screen off, then turned it back on and now i'm back to the same problem.
[Sony Xperia ZL] djruckuss66:
Are you rooted?
[Sony Xperia ZL] nik.taylor:
Yes. With locked bootloader.
[Sony Xperia ZL] djruckuss66:
There's a fix. Check this out.

http://xdaforums.com/showthread.php?p=39030221#post39030221
[Sony Xperia ZL] nik.taylor:
Fantastic. Thanks very much.

Edit: Worked perfectly. Now i'm hoping someone creates a flashable fix for Google Wallet. I dont like manually fiddling with prop files.
[Sony Xperia ZL] paullu:
it this can work on tmobile?

or everyone know how to make gwallet working on tmobile zl?
[Sony Xperia ZL] paullu:
Follow third post I successful installed Google wallet

On my zl c6506 at T-Mobile but not buy anything yet
[Sony Xperia ZL] spielnicht:
Installed it this morning via the method listed and used it to pay for a purchase an hour later. Suddenly, I don't miss my Galaxy Nexus any more.
[Sony Xperia ZL] enrique71:
Me too, followed the instructions on the Z forum @ http://xdaforums.com/showthread.php?p=40897879#post40897879

The only thing was I left the build.prop with the Galaxy Nexus settings .. changing them back to the Xperia entries broke Wallet after a reboot.
[Sony Xperia ZL] paullu:
why u can't change it back??! I can change back to sony without problem

there is one thing after install wallet don't update from market.
[Sony Xperia ZL] enrique71:
No idea, each time I revert back to the Sony build.prop after a reboot I get the Google Wallet message "Your device is not supported". When I use the Nexus build.prop is works fine. Odd that I'm getting this error.
[Sony Xperia ZL] paullu:
strange!! I am c6506 tmobile
[Sony Xperia ZL] wingzero2085:
So, by all the posts here, Google Wallet does not work without some hackery? I find that interesting, considering it seems that the phone intentionally supported it. I'd love to know who dropped the ball here, Sony or Google. I would love to have Google Wallet working on my ZL, but I refuse to root my phone and alter the build.prop to get it there.
[Sony Xperia ZL] spielnicht:
It's definitely Google's fault here. They update Google Wallet every so often with new handset support. Maybe in the next update...maybe.
[Sony Xperia ZL] wingzero2085:
I kind of figured that would be the case. I hope Google decides to support the ZL as having a non-carrier branded phone (and thus choices like Google Wallet) was half of the allure of the ZL for me.
[MDA II, XDA II, 2060 Accessories] Eggert:
Hi,

I am new to the board, great that I found it.

I am planning to create some cool accessoires for th XDA2 but I neet your help.

Do you know how the O2-keyboard (foldable) works? I think it connects to the interface? Is it a "standard" keyboard with an adapter maybe PS2 -> Interface of the XDA2?

It is so expensive that I want to build a homemade one.

Next step would be to create a remote control for the MP3-Player. Pressing one button opens it, then one for play, stop etc. I think you can program the buttons like Winamp, pressing "X" is play and "C" is pause or something else. The buttons for accepting a call/ignore it may not be missed.

Third Idea is an external battery pack. The official backpack is hard to get and again really expensive! My Discman has something like that, put 2 AA-batteries into a box which can be connected to the power-supply-port. I think input is 5V, correct? Are the pins the same like the ones of the XDA1?

Thanks,

David
[MDA II, XDA II, 2060 Accessories] Rudegar:
the problem is that unless you can get all the info here you kinda need to buy the org extre batt and keyboard to see how they work

you might also be prepared to write your own drivers for your own accessoires

making a good quality home made accessoi may end up being more expensive then buying what you can already get, same thing apply to every prototype of an accessoi

good luck though

this page is of cause a good place to start

http://xda-developers.com/connectors/
[MDA II, XDA II, 2060 Accessories] Eggert:
Maybe...

but I think making an adapter for PS2-Keyboards to the interface of the XDA cannot be such expensive.

We'll see... :)

David
[Nook Color Q&A, Help & Troubleshooting] jmh363905:
Long story short, I screwed up my internal memory partition table and believe I've got it back.

Problem: I need a dump of /dev/block/blkmmc0p1 (and p5) if at ALL possible from anyone that has a working Nook.Color.

My problem is similar to this one: http://xdaforums.com/showthread.php?t=918772

If only the files on this page were still active on Mediafire: http://xdaforums.com/showthread.php?t=919353

That's the long and short of it. If you guys want some additional info I can provide any information, but as I said, a dump of someones boot partition would definitely help.

Thanks all!

-Josh
[Nook Color Q&A, Help & Troubleshooting] leapinlar:
Your PM to me says you flashed my 3 zips. I generally don't respond directly to PMs, I prefer the forums. I assume you meant my three zips in my partition repair thread. The repair 145678 zip has a dump of that partition built onto it. So if that flashed successfully, and it still will not let you boot, finding another dump file will not help. If you want one, extract the one from there.

You may need to describe more what you have done and how it is acting now.

Sent from my Nook HD+ running CM10 on Hybrid SD
[Nook Color Q&A, Help & Troubleshooting] jmh363905:
OK, I'll just start from the beginning with what I've done:

I have a Nook Tablet (not talking about it, just saying... I'm in the right forum lol) and a friend got a Nook Color and wanted to know if I could soup it up the same way.

Well I had it working and like an idiot, I accidently used the Nook Tablet "swap storage" routine to make /sdcard1 <-> /sdcard0 instead of the one for the Nook Color. It took the flash fine and upon reboot it claimed that the SD Card needed to be prepared so I let it format the "card"

That's all she wrote so far. I rebooted it again and it wouldn't even come on. It was at 30% power when I told it to reboot, so I figured it was plagued by the sleep of death so I let it charge all night.

Woke up, still nothing.

I made a CWM bootable SD card and LO AND BEHOLD, it started up without a hitch!!! But it complained constantly of "/cache" not mounting to store its log files (that was earlier today and it has been a LONG day so I cant recount the exact error message). When I tried to install the ROM again, however it failed all around.

Your partition 2 repair file failed at first for me, that's how bad it was.

After many different attempts, I setup a bootable SD card with Nookie and get a little further.

With Nookie, I was able to FINALLY adb into the device and fdisk -l /dev/block/mmcblk0 which revealed an empty table and with wrong cylinder, head, and sector count, which I fixed by using the information found here: http://xdaforums.com/showthread.php?t=942324

After that, I remade my CWM bootable SD card and got better results. /cache errors are gone and I was able to use all three of your zip files for repairing partitions (forgive me for not having the file names handy).

That has gotten me a little further, but now I keep getting errors about /boot not mounting.

Also, I haven't just been using CWM, but also TWRP (which thinks my serial number is all 0s), but when I manually mount /rom I can see in the devconf folder that my serial number has been restored (before I recreated partition table and ran your 3 zips, that wasn't even the case).

I'm sorry this is so scatter brained. I've been at it for a solid 10 hours all while laid up in bed with walking pneumonia, so..yeah...fun times..
[Nook Color Q&A, Help & Troubleshooting] jmh363905:
It could also be that I didn't partition it properly because partition 1 (the only 1) seems to lose it's file system type every time, while the other 7 remain intact.
[Nook Color Q&A, Help & Troubleshooting] leapinlar:
If it did not have the proper cylinder head count, how did you repartition it? That quoted thread just says what the proper layout should be, not how to repartition it.

Sent from my Nook HD+ running CM10 on Hybrid SD
[Nook Color Q&A, Help & Troubleshooting] jmh363905:
Well, I'm not EXACTLY a total n00b. I looked up the busybox/fdisk syntax.

First I did fdisk -C 965 -H 255 -S 63 /dev/block/mmcblk0 (as it was reporting nothing right)

That command got me the proper size of the disk and I, with help of the "m" help command" recreated it to this (now that I have adb working in TWRP, I'm back to my preferred parted, so this is not an fdisk printout, but a parted printout):

Number Start End Size Type File system Flags

1 32.3kB 74.0MB 74.0MB primary fat32 boot, lba

2 74.0MB 148MB 74.0MB primary fat32 lba

3 148MB 461MB 313MB primary ext2

4 461MB 7937MB 7477MB extended

5 461MB 938MB 477MB logical ext2

6 938MB 1941MB 1003MB logical ext3

7 1941MB 2311MB 370MB logical ext3

8 2311MB 7937MB 5626MB logical fat32 lba

In the past 5 minutes I have used mklabel to wipe partition table (shown above) again and am recreating them... again.

----EDIT-----

Here is that redone partition table:

Model: MMC SEM08G (sd/mmc)

Disk /dev/block/mmcblk0: 7944MB

Sector size (logical/physical): 512B/512B

Partition Table: msdos

Number Start End Size Type File system Flags

1 512B 74.0MB 74.0MB primary fat32 boot, lba

2 74.0MB 148MB 74.0MB primary fat32 lba

3 148MB 461MB 313MB primary ext2

4 461MB 7944MB 7483MB extended lba

5 461MB 938MB 477MB logical ext2

6 938MB 1941MB 1003MB logical ext2

7 1941MB 2311MB 370MB logical ext2

8 2311MB 7944MB 5633MB logical fat32 lba
[Nook Color Q&A, Help & Troubleshooting] leapinlar:
I'm not exactly a noob either and I could not find that -c -h -s command. I've been looking for that forever because I have a device that is showing the wrong count. So thanks.

Let me know how that new repartition comes out. I'll help if I can. I have all the images if you need them.

Sent from my Nook HD+ running CM10 on Hybrid SD
[Nook Color Q&A, Help & Troubleshooting] jmh363905:
New layout:

Number Start End Size Type File system Flags

1 512B 74.0MB 74.0MB primary fat32 boot, lba

2 74.0MB 148MB 74.0MB primary fat32 lba

3 148MB 461MB 313MB primary ext2

4 461MB 7944MB 7483MB extended lba

5 461MB 938MB 477MB logical ext2

6 938MB 1941MB 1003MB logical ext2

7 1941MB 2311MB 370MB logical ext2

8 2311MB 7944MB 5633MB logical fat32 lba

Of your 3 zips, 1, 4, 5, 6, 7, 8 repair seemed to work without error, but I'm back to partition 2 repair not working. ARGH, talk about a step backwards LOL.
[Nook Color Q&A, Help & Troubleshooting] leapinlar:
I hope you saved an image of p3. That is critical.

Sent from my Nook HD+ running CM10 on Hybrid SD
[Nook Color Q&A, Help & Troubleshooting] jmh363905:
Hope of backing up any partitions went bye bye when I had to recreate the partition table the first time.

Now, is that the partition with devconf files or the factory.zip partition?

I'm still a bit unclear on that.
[Nook Color Q&A, Help & Troubleshooting] leapinlar:
P2 is the one with the devconf files. P3 has the factory.zip, but more importantly it has the rombackup.zip which was the backup of p2 when it was manufactured. That is what my p2 repair zip uses when it reconstructs p2. If you don't have that info, you will never be able to boot to stock again. But we can make dummy info so it can boot to CM. If you got a backup of the p2 before it died, you will be ok.

BTW, I just used your fdisk commands to fix my bad cylinder count. Thank you.

Sent from my Nook HD+ running CM10 on Hybrid SD
[Nook Color Q&A, Help & Troubleshooting] jmh363905:
No prob. That file is LOOOONG gone, but my only hopes are running CM10. Stock is for lusers. I have the serial number and wifi mac address written down so if we need to fake a few things, ANY help you can offer to get this thing working will be great.

I DID forget to mention that I have a TWRP backup of the Boot, Cache, System, and Data, but it won't restore :-/ I'm sure they're filled with all kinds of goodies.

Again, ANY HELP would be so great.

You tell me what you need me to submit and I'll be more than happy.
[Nook Color Q&A, Help & Troubleshooting] jmh363905:
assert failed: (getprop("ro.product.device:") == "zoom2" || get prop("ro.build.product") == "zoom2") || getprop("ro.product.overallname:" == "NOOKcolor")

^^^ an error I'm getting trying to "install" the romrestore.zip file from my TWRP backup files. I'm not an expert, but is that saying my device and product name have been changed to something they shouldn't be?
[Nook Color Q&A, Help & Troubleshooting] leapinlar:
You need to make three files to put in the devconf folder.

DeviceID has your 16 digit serial number

SerialNumber has the same info

MACAddress has your 12 digit MACaddress with no spaces or colons.

Also BootCnt should automatically get made by the system. It will not hurt to have a dummy one there. 4 bytes with nothing in it. That is the one that triggers an 8failed boot reset if it ever gets up to 8 in that file.

Also in the main folder should be a file call BCB (which means Boot Control Block). That should get created automatically by TWRP or CWM.

You get all that in there and flash a CM ROM and it should boot.

P3 does not matter unless there is a problem and stock recovery needs it. As long as you make sure that the DeviceID file is intact, you will never need p3.

Sent from my Nook HD+ running CM10 on Hybrid SD

---------- Post added at 06:50 PM ---------- Previous post was at 06:47 PM ----------

No, it is because the original device name was zoom2. You do not want to flash that anyway, since you do not have a working p3. It does the same as my repair p2 zip.

Sent from my Nook HD+ running CM10 on Hybrid SD
[Nook Color Q&A, Help & Troubleshooting] jmh363905:
OK from ADB Shell, here are my commands so far:

cd /

mkdir rom

mount /dev/block/mmcblk0p2 rom

cd /rom

mkdir devconf

echo 2011460062572006 > DeviceID

echo 2011460062572006 > SerialNumber

echo 58671A19B85F > MACAddress

Do I need to chmod these files as well?
[Nook Color Q&A, Help & Troubleshooting] leapinlar:
Nope, once you verify those files are really there, just flash a CM ROM.

edit, well now that I think about it you might want to set it for 644. I usually flash those and that is what CWM sets them as.

Sent from my Nook HD+ running CM10 on Hybrid SD
[Nook Color Q&A, Help & Troubleshooting] jmh363905:
-- Install /sdcard/cm-10-20130324-NIGHTLY-encore.zip ...

Finding update package....

Opening update package....

Installing update.... (a couple minutes like it's doing something)

*Verifying filesystems....

* Verifying partition sizes...

E: Unable to mount '/boot' (tw_mount)

E: Unable to mount '/emmc' (tw_mount)

E: Unable to mount '/emmc' (tw_mount)

E: Failed to mount /emmc (Invalid argument)

E: Failed to mount /emmc (Invalid argument)

E: Failed to mount /emmc (Invalid argument)

Rebooting system after that yields in the same ole same ole: First, using the software reboot failes.....always.. I'm taken to a blank (not backlit) screen that I have to press and hold Power + Nook. If I press both of these and an SD card is present, I'll get recovery again. If an SD card isn't present, it just sits there with a blank screen. (not backlit)

Ready to put a hole through it. LOL
[Nook Color Q&A, Help & Troubleshooting] leapinlar:
Two things, look at my edit above. And did you format those partitions after creating them? You need to. flashing my repair zip and format zips will take care of 145678. You still need to manually format p2 as fat32.

Edit: It looks to me like TWRP is doing some more checking that CWM does not do. You might try using CWM while trying to fix this. Also the new TWRPs do not like my zips.

Sent from my Nook HD+ running CM10 on Hybrid SD
[Nook Color Q&A, Help & Troubleshooting] jmh363905:
I verified that the files were still present after a reboot and they were (plus a Lost+Found directory indicates that there's an active, formatted partition), but I am going to go ahead and format both boot and rom with FAT32 file system:

ADB Shell Commands:

mkfs.vfat /dev/block/mmcblk0p1

mkfs.vfat /dev/block/mmcblk0p2

Then attempted restoring again. Same process as before, except NO errors AT ALL this time, so seeing it as a ray of hope, I followed it up with the GApps package (in hopes that THIS IS IT....)

Good news, PROGRESS has been made:

Now, WITHOUT an SD card, the unit will power on and give me the Cyanoboot Bootloader, but just hangs at loading from EMMC 01

What do you suggest now? ( and when this is all said and done with I'm gonna be needing your PayPal account so I can thank you)
[Nook Color Q&A, Help & Troubleshooting] leapinlar:
Those other partitions need formatting too. Use my 5678 format zip.

Sent from my Nook HD+ running CM10 on Hybrid SD
[Nook Color Q&A, Help & Troubleshooting] jmh363905:
OOOOOOK. I went in and used your two tools for 5-8 & 1, 5-8 again. Mkfs.vfat partition.. again. CM and GApps... Again... and THIS time it BOOTED!!!

Wifi Works! Bluetooth works!

EVERYTHING WORKS!!!

I cannot thank you enough, leapinlar!!!!! I was right in my PM that you would be my savior!!! I've been a member since 09 but never had to post until today and I'm thankful I did!

I'm so excited I am bursting at the seams!
[Nook Color Q&A, Help & Troubleshooting] leapinlar:
Thanks for the feedback. Really glad it is working for you. And you did help me too. That borked device works just fine now.

Sent from my Nook HD+ running CM10 on Hybrid SD
[Nook Color Q&A, Help & Troubleshooting] jmh363905:
Get yours working too?
[Nook Color Q&A, Help & Troubleshooting] leapinlar:
Yep, I was able to use the -c -h -s fdisk commands to fix it. Then I repartitioned everything with fdisk. I had backup images so I just dd'd them and all is well. Did it all with terminal emulator in CM10.

Sent from my Nook HD+ running CM10 on Hybrid SD
[Nook Color Q&A, Help & Troubleshooting] jmh363905:
Well glad I could help, although it dulls in comparison to the help you offered.
[HTC One X] BrunoSlivar:
Hi people. Wich cable i need to connect my hox with samsung lcd tv? :confused:

sent via htc one x power by ARHD
[HTC One X] Jerobakker:
you need this : http://en.wikipedia.org/wiki/Mobile_High-Definition_Link
[Galaxy S II Q&A, Help & Troubleshooting] Danielsson:
I have a problem after each installation and configuration rom wifi crashes assigned to me and the hot reboot after installing 4.1.2 Odin is the log of 4.2.2 samsung passed as is.?!?!

Wysyłane z mojego GT-I9100 za pomocą Tapatalk 2
[Galaxy S II Q&A, Help & Troubleshooting] Danielsson:
Odp: Problem with google account and original software

close please

Wysyłane z mojego GT-I9100 za pomocą Tapatalk 2
[AT&T Samsung Galaxy S II SGH-I777] mrdreamers:
i heard deleting everything then reflashing would work but i was wondering if anyone knew any other tricks before i do that, just don't want to go through all the trouble ;) ty:)
[AT&T Samsung Galaxy S II SGH-I777] Phalanx7621:
So are we supposed to just GUESS what rom you're running, what kernel, any mods you installed....
[AT&T Samsung Galaxy S II SGH-I777] mrdreamers:
sry

sry noobin it still, im using samsung galaxy s2 sgh-i777,

cm10.1 nightly,

3.0.31-cm-gb4d6b0a

anything else ya need to know let me know ty in advanced :)
[AT&T Samsung Galaxy S II SGH-I777] fiffan86:
Who is your carrier and what are your APN settings?
[AT&T Samsung Galaxy S II SGH-I777] Freakshow116:
I've been having this exact same problem.

But to the place where I can't even use my internet while on just data.

I'm running the same ROM and Kernel as the OP.
[T-Mobile Samsung Galaxy S II SGH-T989] PopperJuan:
Okay so I put a custom rom in.. Pacman jb 4.2.2 and added the cerux kernel with it... But when I installed wifi tether for root users it says configure AP failed and it seems like it working its really not.. The ssid doesn't even show up on my laptop.. So I need help.. I did a cwm back up but no titanium back up...anybody has the same problem?
[T-Mobile Samsung Galaxy S II SGH-T989] yuyuyuyu1:
Reboot the phone and use the default, built-in tether (Settings -> More -> Tethering & portable hotspot). You might want to give it a few seconds/1 minute for devices to properly connect. The app WiFi Tether for Root Users does not play well with 4.2.2.