yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] scelera:
Only in the beginning, or if you brick it. ;) There are a bunch of ways to do this but this is the method that has worked for me everytime

1. Download all these files https://www.dropbox.com/sh/96j1jiukicra9oc/gAvmNYf7ZQ

2. Download drivers for your phone if you haven't already

3. Put the teamhacksung-ota-eng.BUILD2.zip and the JB ROM and gapps that you want on the root of your SD card

4. Power down the phone and pull the battery.

5. Open Odin and plug the phone in while holding the down volume rocker button, a yellow triangle should appear

6. In Oden click on PDA on the left hand side and find the cwm-recovery-ALL.tar file

7. Click start

8. Once that has completed click on PDA again and this time pick GBBootloaders.tar, I don't know if this is still necessary but without it you can't see the boot animations. You'll have to hold down the down volume rocker until you get the triangle again. Then click start.

9. Once it has completed, unplug the phone and put the battery back in. Then hold the Power and both volume rocker buttons (know as the 3 finger method) down until you see Samsung twice. Phone should boot into Recovery.

10. Once in Recovery choose 'Install update from zip' (or something like that, sorry it's been awhile) then 'Select zip from SD card' (I think) and pick teamhacksung-ota-eng.BUILD2.zip, select yes on the next screen. It will automatically boot into ICS when finished flashing.

11. After it boots up, hold down power button and choose 'Reboot' then 'Reboot Recovery'

12. Wipe all 3 (do a factory wipe, wipe cache, and then in the advanced menu wipe dalvik)

13. Repeat step 9 only with the JB Rom. The first time you tell it to flash it will crash, it's supposed to do that. Just select it again and it should work. I've found that best practice is to flash the ROM 3 times, it sounds excessive but I've personally got better results from it. It was a tip from JT (he's like the android mad scientist, if anybody can fix it or make it work, he can)

14. Flash Gapps and then reboot. You should be in the money.

I hope I didn't forget anything. And I hope this isn't confusing, I'm not real good at writing guides. Good luck!! :good:
[Fascinate Android Development] newbie4ever:
Holy crap Bdogg! This is a great ROM for this old of a phone... I don't use it as a phone (have an S3 for that) but I do use it as a music player, camera, or sometimes for geo caching.. Battery is great.. UI looks sweeter than my S3 and after all the apps settle down for a day, this phone just flys!!! So this post is just to say thank you for supporting such an old relic of a phone
[Fascinate Android Development] nm3210:
You haven't needed to flash that original ICS rom in a LONG time. You should be able to just Odin the 'fixed-for-cmw4' recovery and then install this ROM. If i've been following things correctly the past year+, there have been a few updates to the partitions after that Build2 first came out (remember, that's really old) that completely make it pointless to flash first. Our current rom (this DU-4.3) should have all the MTD partitions built in and since it has it's own recovery, again, you shouldn't need to flash anything but it.
[Fascinate Android Development] scelera:
Like I said, it's been a long time since I've flashed anything from stock. And I had remembered when I first started out reading about the 'fixed-for-cmw' but it never worked for me. But then again, I haven't come from stock since the first JB Rom that I tried.
[Fascinate Android Development] PwnFx:
I've tried using both recommended methods by you two guys, and I either get an error "unable to mount /data and unable to mount /cache".

And using the fixed-for-cmw4, I get the installing failed again, "getprop("ro.build.product") == fascinatemtd and the status 7 error.

I'm not sure what's going on here.

I had successfully flashed this rom one time but I was stuck bootlooped on the dirty unicorn logo, to make sure I let it sit there for about 40 minutes to make sure since I know the first boot takes time, after rebooting, it just brought me back to the twrp built in, and I had to flash it back to the hacksung originally linked. Which it flashes that rom just fine, but still gives me the unable to mount data and cache..

Thanks for your help thus far fellas.
[Fascinate Android Development] nm3210:
It could be an SD card problem? Have you tried flashing a 4.1 or 4.2 rom? And for the record, you should be using the 'cwm4_fixed_for_cm7' if you're going to flash an MTD rom (which is basically anything newer than 4.0). I fully support the method that scelera put in his post, that SHOULD work just fine - I only suggest that you don't have to do the double flash anymore (since 4.1+).
[Fascinate Android Development] PwnFx:
I have not tried any other rom, the hacksung ones both flash just fine, but when it boots into twrp after the double flash selection and I try to install dirty unicorns through twrp, it gives me "E:Error excuting updater binary in zip /sdcard. Updating partition details..

E:Unable to mount /system

E:Unable to mount /data"

Am I doing something wrong when it reboots into twrp?
[Fascinate Android Development] nm3210:
You need to start over. Odin a completely stock rom, you need to download "CI500_VZW_EH03_GB_CM.tar.md5" (google) and the PIT file which will repartition back to stock, and then start at step 4 of scelera's post (and use the cwm4_fixed_for_cm7).
[Fascinate Android Development] PwnFx:
Thank you very much.

I'll post back with the results.

This 449mb file is taking an hour to download, I assume it's from a slow host, so I'll post back then lol.

I appreciate you guys helping me, and I can't wait to give her a working phone! :)
[Fascinate Android Development] aircooledbusses:
http://xdaforums.com/showthread.php?t=1238070

this is the tutorial I used to get my fascinate up and running with 4.3

I don't know much but have a feeling it may have to do with the bootloaders, but if you follow the tutorial you will be able to flash this AEWSOME dirty unicorn ROM.
[Fascinate Android Development] hhp_211:
probably late to the party,,, but I have that file in a 325MB zip up in my AFH folder Here [fast servers] along with any of the other needed files for odin and recovery on our fascinate
[Fascinate Android Development] PwnFx:
I have it back to stock as directed, just got to this step in the new flash. Fingers crossed.

Thank you guys so much, I can't believe how alive the forums for this phone are, when I post in the Droid RAZR forums for my phone it usually takes a few days to get replies or I get totally ignored lol. This is wonderful.
[Fascinate Android Development] BDogg718:
We are a small, but close community. :good:
[Fascinate Android Development] PwnFx:
Yes indeed.

I followed all of those instructions to a T, it all seemed to go very smooth.

I'm currently at the Dirty Unicorns splash logo spinning, and was curious if I am stuck at it or if it's just taking a long time, it's been maybe 5 minutes so far, should I be waiting any longer than this?
[Fascinate Android Development] ConstantHero:
When I flash rom to rom I've got in the habit to "format system" found in recovery under 'mounts and storage'. In addition to the big three (factory wipe, cache and dalvik) before I flash a new rom. Might be helpful in the future.
[Fascinate Android Development] swapnilss:
Yes. I second that. Had to do the same while flashing this DU rom.
[Fascinate Android Development] avalasan:
Anyone else having an issue with the keyboard crashing whenever you try and use swipe?
[Fascinate Android Development] Unjustified Dev:
Use this lib http://d-h.st/5w0 put this in system/lib makes sure you delete the original one first and set the correct permissions
[Fascinate Android Development] PwnFx:
Well, it has turned out unsuccessful. I don't know what I'm doing wrong, but it's just not working.

I'm sure I've properly followed all the steps, I just don't know what to do next.

I even tried a different rom, (Helly_Bean) and same nonsense, unable to mount all of the different directiories.

All of the hacksung ones flash fine, but I can't seem to get these JB roms to happen. :(
[Fascinate Android Development] Unjustified Dev:
Go back to stock and use cm4 fix for cm7 then flash this ROM
[Fascinate Android Development] PwnFx:
That's what I used.. :s
[Fascinate Android Development] Unjustified Dev:
Which stock are you using? Don't wipe anything when flashing from stock
[Fascinate Android Development] PwnFx:
I used this: CI500_VZW_EH03_GB_CM.tar.md5

When I flash to a new rom from the stock one, don't wipe after flashing? Or before?
[Fascinate Android Development] Unjustified Dev:
Just flash the ROM. Once in new cwm or it might continue bml to mtd and flash the ROM. Just pull the battery after the phone starts booting the ROM . wipe data , system , and dalvik. Then flash the ROM again and then flash gapps . Sometimes it happens to me the ROM won't boot so I just wipe everything and reflash it and it boots . Might take a while some ROMs take longer to boot
[Nook HD, HD+ General] rushless:
First of all, Very and Leap- you two rock something fierce! :)

I did a review before of the HD+ with 2.1. I gave it a good review, but three things slowly eroded my opinion after time and I returned it.

1- Intermittent stutter that seemed to correlate with on the fly data loads and library sync. This stood out with games.

2- Games loading slow and some REAL sloooooow

3- Accumulative lag. Over a few days, the device got real slow and cache cleaning and restarts were hit and miss to fix it.

Best Buy had it on sale for $20 less this time ($180), so based on folks opinion of CM 10.1, I thought I would test it out again- due to the price and sweet display.

Where 2.1 was a big improvement over 2.0, the improvement from 2.1 to CM 10.1 is fluken' huge!

1- The intermittent stutter is gone along with library sync is gone.

2- Games load a LOT faster. I would not have thought the stock rom would be what was slowing it down, but I tested fresh installs two times with the same sloooow results with 2.1.

3- So far, the accumulated lag has not showed up.

4- Overall device is faster

I also added the "full screen" app to get rid of the navigation bar when I want. More just to test it out, but nice to have an iPad like full display view :)

Jeepers, it is wild how it is so easy to flash the device with 10.1 and equally wild to have the results of 10.1 with this hardware for the price. Superb so far :)

Of course, with anything in life comes the negatives:

1- exFAT worked with 2.1, but does not with CM 10.1. I had to transfer, format and recopy back to the sd card with FAT32. I wish there was a simple install fix using the boot card like the unknown sources fix for stock 2.1.

2- Buggy Blitz does not work. I love that game :( Ditto for Shine Runner. Same company.

3- I have had one instance so far where the device had charged and there was a flashing green light. The device would not wake up with neither home or power button. I had to hold the power down for a while and repeat that a few times. It would get stuck on the spinning boot-up ring. It would freeze up after after "several" seconds. Seems to be working now, but this never happened with stock 2.1 and used the device for a month. Fluke?

4- Quake 3 keeps expecting to see "sdcard" rather than "sdcard0". Touch Quake 1, 2 and Quake Arena mods work fine though. These are examples of games that loaded SLOW with stock 2.1, but are near instant with CM 10.1.

5- The CM 10.1 launcher was jittery and slow. I tried to get used to it, but went back to Nova, which is smooth and fast.

Folks, Nook HD+ plus CM 10.1 equals insane value for the price!
[Nook HD, HD+ General] verygreen:
there's 3rd party zip you can flash that restores it somewhat..

I also plan to look into this eventually and use texera fat module from the stock rom.

That seems to be their bug related to new sgx drivers. Same crash happens on Kindle fire, for example. Nothing I can presently do about it.

Not sore about not waking up - never saw that. But rare boot problems will be fixed in next release. (esp. those that produce garbage on screen).

Still no camera, so it cannot serve as full TP replacement :(
[Nook HD, HD+ General] rushless:
No problem on the games not working, since works on my Excite 7.7 and S3!

Exfat and NTFS would be nice, down the road!

Thanks!
[Nook HD, HD+ General] View92612:
I think B&N could have done much better with this hardware if they hired someone like verygreen in the first place... :)

I still don't think this is a very good gaming device, though, especially for 3D.

But the screen is amazing and got me really spoiled. Now I look at Nexus 7 and feel the display is too cheap and low in quality. Comparing it with the TP in my opinion is a bit of an apple to orange comparison as it is mainly a media consumption device while TP's display quality is even worse than Nexus 7.

Someone was complaining the Nook being slow and laggy vs a $499 Galaxy Note 10.1 with 2GB ram, quad core and much lower resolution. That is just unfair. But I guess people are entitled to their opinions.

Honestly I would not have bought this without seeing the CM10 and CM10.1 ports in progress. B&N really owes verygreen a commission. I like this combo so much that I hardly touch my Nexus 7 now.

BTW, donation sent. :)
[Nook HD, HD+ General] verygreen:
While I somewhat agree here, in reality I distributed Touchpads to my relative and they use them for things like Skype.

Nook, having no camera, cannot replace them and would be useless for such purposes.
[Nook HD, HD+ General] e.mote:
I agree that the Nook has deficiencies (proprietary ports are a downer). When it comes to cheap toys we pick our poison, eg Nexus w/ no SD slot. If I want a cam or HDMI, there are a flood of cheap 7" tabs that have both, but none of them has a really great 1080p screen in an IMO perfect size and weight for one-handed use. I don't see any tablet with comparable display quality under $400.

Display quality aside, as a reader my preference is for a 4:3 aspect, since I use the tab mostly in portrait mode. But outside of the iPads, most Android tabs hewed to 16:10, which makes the display smaller than their diagonal size would indicate. The HD+ is the only one to eschew the norm in going with 3:2. That's actually better than 4:3, because the present Android UI takes off a couple slices at top and bottom, so the remaining space comes out pretty close to 4:3.

Using the dpi calculator here,

http://members.ping.de/~sven/dpi.html

The 9" HD+ screen has a portrait width of 4.99". The 8.9" KF HD's is 4.72", or 0.27" smaller and not just 0.1" shorter diagonal. For tablet display size, every fraction of an inch is a big deal when you're squeezing a whole web page into portrait.

Some other display portrait widths, which I view as the tablet's true size measurement:

iPad Mini 4.71"
Nexus 7 3.71"
Galaxy Note 8 4.24"

Nexus 10 5.3"
iPad 5.82"
[Nook HD, HD+ General] rushless:
Oh yeah, e.mote: Thanks for the "dummies" thread!

True on the lack of camera, but I got it for books, comics (more than books) and games (mainly emulators). There are a few games that my Excite 7.7 plays smoother, but most play the same and game emulators like MAME and N64 are faster on the Nook HD+. Also, CM 10.1 closed the gap on the 3D games that are smoother on the Excite 7.7. GTA is a good example. It plays smooth now, where with 2.1, it did not. Asphalt 7 though is an example that plays smoother on the Excite. Asphalt 7 though is now very playable on the Nook HD+. The TF700 also struggles with some 3D games, BTW.

For game emulators. this thing rocks. $180 for a great display and plays emulators better than any other Android I have used- including the S4 and its quad Qualcomm. Bluetooth game pads work fine and no response lag noted so far and fits the iCade :)

Sad that we get the stock firmware we get when folks here do a better job for user experience. I appreciate the Nook was designed to be mainly a reader, but their premise was also part of their undoing and the convention of poor stock firmware goes way beyond the Nook.
[Nook HD, HD+ General] e.mote:
>Thanks for the "dummies" thread!

I actually wrote that for myself, since I have a stack of HD+'s here that I'm retrofitting to pass along to the family. Credit where it is due, it's all a rehash of what leapinlar has written, but just a bit more digestible. And of course to verygreen that made this all possible.

Glad to hear Nook is good for games. I'm not a gamer, but other peeps in the household would be appreciative. Any good guides for emulators you can point to? How about some strategy/tactical games? I liked Call of Cthulhu and Rebuild.

BTW, little known factoid: The Nook's serial # is printed on the inside of the SD slot's rubber flap. I found that out when returning a HD+ for uneven backlighting.

>I appreciate the Nook was designed to be mainly a reader, but their premise was also part of their undoing and the convention of poor stock firmware goes way beyond the Nook.

I view it as a good-thing-bad-thing situation. If B&N had made a great Android tab, it wouldn't be holding a firesale to clear out the Nooks, and we wouldn't be here yakking away. So yes, I'm kinda glad the HD's didn't sell well (until now).
[Nook HD, HD+ General] rushless:
Very ironic.

As far as emulator guides, there is a very good one over at Phandroid forums. It is in the Android game forum.

This tablet is an old school gaming, comic reading, web and Flash slinging bargain.
[Nook HD, HD+ General] View92612:
Totally agree. What controller do you use for the emu, though?

I found it extremely difficult to trigger complex moves (in games that require those) using just touch control..... I'm sure it would not be an issue for games that do not require those.
[Nook HD, HD+ General] rushless:
I use a generic Android controller from Gamestop, two Nyko Android pads and iCade. All work fine.

I found another game that worked with 2.1 but not with CM. NBA 2013. Another of my favorites. What are the odds of that? It loads to the point of showing the team logos at start up and then crashes.

Also, most games like NFSMW that took a long time to load up with 2 .1 now load fast like other tablets. The only exception found so far is Asphalt 7. It still loads crazy slow. About two minutes or more per track. Should take about ten seconds. The London level just took over two minutes. Almost three.

The game plays good though. Much smoother (no stutter) than 2.1, but that is the case for all games so far. Odd how Asphalt 7 seems the only slow load hold out. I have tested a ton. A7 appears to be an anomaly.

CM 10.1 BTW also confirms to me the main stutter was not the gpu, but the stock rom. As per Anandtech, the 4470 is still a capable chipset.

I also compared A7 on the GS3. They appear to play very similarly as far as smoothness. GS3 might be a tad smoother, but does not stand out. The GS3 plays all of my games smooth, but the Nook smacks it down as far as MAME. 4470 appears to be a great emulator chipset.
[Nook HD, HD+ General] rushless:
I figured out why a few games do not work. Quake 3 need the files on the SD card and looks like NBA 2013 is trying to run the game from there too. It installs to internal, but installs a directory also in the SD with no files. I am going to move it to the SD and see what happens.

Update. Looks like ports like Quake 3 work fine, but commercial games do not work when moving the files.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] CL55:
I just got off the phone with O2 support, and they told me there're unofficial 1.31 ROM upgrade available thru the repair center!!
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] :
Well how do we get hold of it???? 8)
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] CarlnAdele:
I second that !!!
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] :
Yeah, right.

An unofficial ROM is available from the Warranty centre, on which thousands of people rely on for support.

That's kinda like saying that Microsoft have released Longhorn as it is now (bugs and all) and are supporting it anyway! :roll:
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] CL55:
Hmmm... Appearently, they DID have the 1.31 ROM at the service center, but the place I went to is only a collection point and they need to send the unit over to the workshop to have it flash, and they said FIVE days!!!

And after chatting with the rep there, the only difference between O2's 1.31 ROM and the launch ROM is the BT patch! Leochan2005 in this forum already has the 1.31 ROM and looking at the info he has posted... It does look like it's only the BT patch.. Why on earth would O2 change the ROM version to 1.31 if it's only the BT patch????????

Here's Leochan2005 ROM info...

ROM: 1.31.00 WWE

ROM Date: 31 Dec 2004

Radio Version: 1.02.00

Protocol Version: 1.337.32

ExROM version 1.31.920 WWE
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] leochan2005:
Sorry for late reply: My 1.31 version, the bluetooth version is 1.0.0 Build 3500.

It detects bluetooth device much faster than my XDAII

But do not know why the radio rom is still 1.02, and do not know whether I can only update this radio rom into more latest version
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] leochan2005:
I remembered that I bought my machine on 27 or 28 Dec 2004, do not know why the rom date is 31 Dec 2004
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] mamaich:
You can update only radio ROM. To do this backup your device, download official ROM update, extract it with WinRar into any directory, delete files ms_.nbf and nk.nbf. Then enter bootloader, place your device into cradle and run BaUpgradeUt.exe. This would update only radio ROM.

Can you dump your ROM to SD-card and upload to XDA-developers FTP? You may use this tool: http://mamaich.kasone.com/imate/ROMDump.rar

To use it copy ARMV4Rel\ROMDump.exe to your device and run it. It would create a 64-mb file on your SD-card.

And can you also make a copy of your extended ROM? The easiest way to do this is to install TotalCommander on your device, open directory "\extended_rom\" (without quotes, you have to type its name manually, it is hidden) and copy its contents somewhere.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] FOSA:
RE

Is this ROM meant for the XDA II? What does it contain? WM2003SE, WMP 10, landscape mode support...?

:roll:
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] zohaer21:
so any1 putting this rom up for downloading?
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] leochan2005:
Dear all

Can you tell me how can I dowload the rom update in order to update my radio rom?

Also, if failure during update, can I revert back to the rom backup in the SD card using the method mentioned above? Can you tell me how to do this?
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] leochan2005:
Dear all

By the way, can I use the radio rom from XDAII for my XDAIIs as I understand XDAIIs is a 4 brand radio but XDAII is only a 3 brand?
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] mamaich:
Of cause you cannot. Hardware is completely different.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] numanoids:
I think you should be asking if anyone actually has it yet?
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] :
I already got the latest ROM from the O2 service center.

ROM Version: 1.31.00 WWE

ROM Date: 12/13/04

Radio version: 1.02.00

Protocol version 1337.32

ExtROM version 1.12.925 WWE

I didn't notice any major difference and the Bluetooth stack comes with Build 3500.

Btw guys, I am a newbie here. Any ways to make the Blue Angel to hav
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] :
Sorry accidentally press on enter.

Any ways to make the Blue Angel to support the Bluetooth Audio Gateway preference in order to listen musics through a BT headset? Thank you for answering
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] zohaer21:
can you post this rom for downloading???

thanks
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] benyeap:
Can u guide me how do I extract the ROM with XDA Tools??
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] :
I heard at the CEBit conference in Las Vegas, i-mate released a BT patch that did that.