yashsingh1/xdaforums huggingface dataset:
[Nook Color General] racks11479:
Well, it seems that you somehow in someway in some miracle of unpleasantness wiped your /rom partition. This partition is where your DeviceID, SerialNumber and many other specific device identifiers resides. Can you list what files are it your /factory partition (mmclbk0p3)? If that is intact, you should be able to restore with the 8 failed reboots. This partition stores a backup of your /rom and /system zips. If that partition is wiped as well, then there's only one option left for you to do:

-Have someone do a dump of /rom (mmcblk0p2)

-Only thing is, before restoring that partition, make sure you edit all files below according to your device (you can find the info on the Orig box that the nook color came in:

DateManufactured
DeviceID
EAN
MACAddress
MainboardSN
ModelNumber
ProductID
SerialNumber

-Create a random MACAddress for your nook.

-One other important file for you to edit is the "WiFiBackupCalibration" file. this is the file that your MACAddress is actually read from. You will need a hex editor to change the values to match the "MACAddress" file. It should be at the top, first line i believe. It's also read backwards in pairs. So if your MACAddress says "58671A1DEBC". In the hex editor it should read

|BC|DE|A1|71|86|50|* and so on...

-It is important for you to change these values because if you restore and sign into your B&N account. It will send a signal that will error out on their server because their are two devices using the same ID's.

Or you could have someone do a dump of /factory partition. In there you will find the factory.zip and rom.zip. Just unzip the rom.zip and edit the files as stated above. Rezip. And copy both files to /mmcblk0p3, then try the 8 failed reboots and it should restore /system and /rom.

Good luck! Let me know how it works out for you. :)

-Racks
[Nook Color General] 12paq:
Hi Dizzy, thanks for your time.

When I mount mmcblk0p3 I have only have factory.zip and lost+found

Edit:

Thanks Racks, as you can see ^^ above my contents of mmcblk0p3. I am not sure I have my original Nook box with the ids and other info. But I am looking now..

Edit 2:

Racks, I found the OEM box. phew

and I am surprised ur not giving me more **** for hosing my back up patitions, lol you kno i kno better.. :D

One question tho, How much of the above information do i need to run custom roms, not* B&N stock. wifi info and mac address for sure but, the others?
[Nook Color General] racks11479:
Lol glad to hear you have the info. And the reason I'm not giving you ish about all this is because I did the exact same thing when I first received my nook! I :p Lol, lesson learned!! Lol

For cm you really don't need to edit the other files besides the wifi an mac ones. But since your doing it anyways. Might as well do it right. :)

Good luck! :D
[Nook Color General] 12paq:
Dizzy,

Looks like I need the images and I need to understand what goes where.

I really appreciate it.

Racks, I might need a bit more information on how and what to edit. I do have a hex editor.

thanks.
[Nook Color General] bobtidey:
There is a recent post here on Mac Address and WifiBackupCalibration

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

Further Info:

There is also some related info in some threads Nook Touch forum which has the same ROM partition info. I haven't gone through it in detail but it looks like there are a few things to think through if you use a ROM partition from another device.

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

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

Wifi calibration and battery files may cause issues. The Public key and hash Private key might stop you using it with B & N directly. Having said that it is probably the most promising / only route if your rom partition is gone and you don't have the factory restore zip.

I must admit I backed up the ROM partition when I first got the Nook as soon as I realized it had device unique stuff in it as I thought that was the one bit I would not be able to recreate. Cold comfort, I'm afraid; but a wise precaution for others to take.
[Nook Color General] DizzyDen:
12... i'll upload my edited rombackup.zip file for ya... you'll have to look at the notes about what goes into which file... I know some info was posted in the old thread about fixing the partitions... I'll search for it for ya too.

The following are the files I edited (All are one line files.):

DeviceID = 16 Digit numeric

ean = 13 Digit numeric

HashOfPrivateKey = 27 digit alpha numeric-"=" (ends with =)

MACAddress = 12 bytes hex

MainboardSN = 10 digit alpha numeric

ProductID = "POC" 6 digits "D"

PublicKey = begins "modulus="-309 numeric digits-";exponent=65537;"

SerialNumber = matches DeviceID

Hopefully you can edit the files as needed and put this on the factory partition (mmcblk0p3) and 8 failed boots will work for you.
[Nook Color General] 12paq:
Thanks man! I will search also. I have a few bookmarked already. :)
[Nook Color General] DizzyDen:
http://xdaforums.com/showthread.php?t=942324

I came in on post 8 on that thread...

---------- Post added at 03:27 AM ---------- Previous post was at 03:15 AM ----------

12... if you need the img files for all the partitions... let me know.

Also note... in the MACAddress file... the line should be:

58671aXXXXXX where XX's are different for each device... perhaps can get from the dump of WiFiBackupCalibration
[Nook Color General] 12paq:
...and I'm back.

All is well and back to booting CM9 from emcc.

Thanks to Racks, fattire and Dizzyden and everyone else who chipped in.

Man! that was fun!
[Nook Color General] DizzyDen:
Glad we got you working again buddy!
[Nook Color General] racks11479:
Word! What Dizzy said ^^ !!

:D

-Racks
[Nook Color General] dumper1234:
@12paq, I am having the same issue as your, would you give me some step by step solution. I tried to follow your post here, but I am not sure which method was the actual working one.

Thanks in advance.
[Nook Color General] 12paq:
I would be happy to help.

First thing, are you trying to go back to stock or CM?

And what do you think caused it? And what have you tried so far?

Edit:

to answer you question more directly I used this:

The reason I asked you about more detail in regards to what you have tried, is because more often or not, you can fix this problem without going to the lengths I had to go. So, hopefully this might be easier for you.

Can you see your 2nd partition and it contents?
[Nook Color General] dumper1234:
No stock, I was flashing the cm9 nightly, no problem so far. I was flashing the 02-17 nightly, and I just formatted cach and factory reset.. the typical procedure before the flash the nightly, I push the reboot instead of choosing the nightly zip. While it was rebooting I hold the power forcing it to power off. And I started it to cm recovery and tried to flash the nightly zip. but it kept going back to the recovery.

I tried to use restore, but didn't work, and even using the reboot-able sdcard to reinstall the emcc-eyeballer... but didn't work.

I can't adb shell the nook, no devices found...

I am not sure how you access the nook, beside the cm recovery.

Please advice...I really really appreciate it.
[Nook Color General] 12paq:
Do you always factory reset for a nightly? No biggie, but just trying to nail down the problem exactly.

The reason I asked you about more detail in regards to what you have tried, is because more often or not, you can fix this problem without going to the lengths I had to go. So, hopefully this might be easier for you.

Are you in CW recovery when u are trying to ? Try powering off and reboot to recovery and see if you can connect then. Also sometimes I have to disconnect some of my USB devices on my PC to fiddle around to get ADB to work.

Can you see your 2nd partition and it contents? We really need to do this first, so we can really identify then problem before we try to correct it.

Additionally here are some links to try to go back to stock. Creating a bootable usd card is key for any of these attempts.

We may need these links and tools:

Dummies guide to my Nook wont boot:

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

_____________________________

Eyeballer's bootable CWM:

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

And/or here:

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

__________________________________

Back to stock:

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

___________________________________

samuelhalff's Color USB Mass Storage utility:

http://xdaforums.com/showthread.php?t=952456
[Nook Color General] dumper1234:
For the 2nd partition, all I can see is the cm recovery v3.2.0.1:

-reboot system

-apply update from sdcard

-wipe date

-wipe cache partition

-install zip from sdcard

-backup and restore

-mounts and storage

-advanced

I looked thru all, sorry not sure where I can see the info on the 2nd partition?
[Nook Color General] 12paq:
For clarification, you have tried to go back to stock and then the eight failed Boots? Because that is the standard go to recovery save the Nook method. This is far easier and definitely has to be thoroughly tried and vetted before we go on to the following:

See if you can get ADB to work, then try this from recovery... we'll use /data as a mount point but you'll really be mounting /rom (p2). First make sure that /data isn't already mounted, then try this from ADB and the Nook in recovery.

ADB shell

then at the # enter:

mount /dev/block/mmcblk0p2 /data

cd /data

ls

To make sure that this is in fact rom with the bcb and bootcnt .. etc..
[Nook Color General] dumper1234:
1st: I haven't tried to go back to stock, yet.

sounds like going back to stock will be more straight forward (easiest) way to making it work again?

2nd: I am using a old "c:\android-sdk-windows\tools", should I update the new android-sdk to access my nook?

Thanks for your patient.. really..
[Nook Color General] 12paq:
Yeah, If you have tried to flash CM multiple times and you keep going back to CWR, you really should try the above links (see the 41st post in this thread) and try to go back to stock and then do the 8 failed boots, first. This is really the go to method before* you try what I had to eventually do to repair my Nook here in this thread.

The good news is many have been in your spot and have recovered far more easily then rebuilding your private files on your 2nd partition, like I had to do.

And yes you should update your ADB and Android SDK and the Nook drivers on your Mac, pc or Linux machine.

If then you still have trouble, come back and I will be glad to help where I can.

Good luck! :)
[Nook Color General] dumper1234:
Thanks you I will try the stock method first, one quick question, after back to stock, why it requires the 8x failed boots?

thanks and will keep you posted.
[Nook Color General] 12paq:
That is a way to trigger a B&N recovery to restore your Nook completely to out of the box stock. I am not sure of the specific files that are involved, but there are private files and backups to backups and factory recoveries on various partitions and this restores, and in your case hopefully repairs, everything back to factory original condition.

The eight failed boots is a method that could not be accidentally reproduced by a user, often with other devices there are button or key combinations that are "double secret" and are used by OEM techs to restore a device to factory condition.

So to be clear some of the above links can get you back to stock without eight failed boots. In your case I would try the 8 failed boots anyway, because the restore links might not repair your actual problem (speculation here). You will have to research and try the different back to stock methods and hopefully it will repair your issue.

Be careful because we still do not exactly know what your issue is, we only know the symptoms. So do your research and have fun. As you know the Nook is really hard to completely brick and at times it's really hard to get it back too..

Good luck! :)
[Nook Color General] dumper1234:
I can't say thank enough, it works. I restored the B&N and reflashed cm9. It is working again... thank you so much.
[Nook Color General] 12paq:
Alright!! Great news!
[Atrix 4G General] soudy1994:
my motorola atrix 4g i ordered from ebay just arrived and it asks for unlock code

where can i find this code?

if i install a new rom will this unlock my phone?

P.S am from egypt
[Atrix 4G General] mysticdrew:
No a new rom will not unlock it. It's unrelated.

You need a sim unlock code... you can purchase one from some online sites (google around) or you can try calling your cell phone carrier to see if they can help.
[Atrix 4G General] soudy1994:
now i hard bricked my phone :(

how can i fix this
[Atrix 4G General] msd24200:
If it's a hard brick it is not fixable, sorry!
[Atrix 4G General] CaelanT:
Define what you think is a hard brick. You may have a soft brick which you can recover from.
[Atrix 4G General] littleemp:
How in the world did you brick your phone trying to unlock the network?
[Atrix 4G General] nthon9:
Sorry if this is harsh, but..
[HTC Rezound] crdnilfan:
Found this on YouTube today, doesn't have many views but it's all in 1080p and it's pretty clear and takes you through step by step how to get a stock Rezound to an unlocked, rooted, custom recovery, ICS Rezound.

If you don't like text tutorials this series is definitely worth checking out.

https://www.youtube.com/playlist?list=PLD3B6F32EAE315098&feature=view_all
[HTC EVO 3D] chlehqls:
Looks like they finally updated their software to support dual core devices and ICS based phones. :)

I got 3044, not this phone though.

Have it at benchmark junkies...
[HTC EVO 3D] dylan6879:
Ha not bad can't wait to see how we compare just tried on my 3d got 2774
[HTC EVO 3D] eXplicit815:
Just ran a 2419 on mine. Faster than the Galaxy Tab and Galaxy Nexus... :-)

I'm running the rooted stock ROM, 2.17.651.5.
[HTC EVO 3D] bloodrain954:
Awesome, now I have updated random numbers that don't really tell me anything useful about my device!
[HTC EVO 3D] SketchyStunts:
2881 CM7 kang with ICS009 kernel
[HTC EVO 3D] sgt. slaughter:
Only took them a year LOL

Running stock rooted and hit 2611...
[HTC EVO 3D] blazerboy567:
Stock everything at 2609
[HTC EVO 3D] Serren:
2742 on Fresh Rom.

It's interesting to see how close the stock ROMs scored from the prior posts above.
[HTC EVO 3D] 84guy:
stock unrooted 2875

edit: not that it matters but just ran it again and it did a 2878
[HTC EVO 3D] jamexman:
Same here. Seems its more consistent between tests than before.
[HTC EVO 3D] chlehqls:
I know right? Haha. At least they acknowledged they needed an update before it was all over...

Pretty impressed that scores are not too far apart from my Galaxy S2 from the Evo 3D (dang you T-Mo for opting out the Exynos). Then again I'm not on a stock ROM...

Sent from my Galaxy SII
[HTC EVO 3D] ryanalan82:
Cm 7.4

Swyped from my eVo 3d
[HTC EVO 3D] Bear gri11z:
id hate to compare my epic touch to these scores :)
[HTC EVO 3D] sprintuser1977:
4838 :-)

From the Beast : Galaxy Note
[HTC EVO 3D] Bear gri11z:
OC? Or stock

I got a 47xx @1.4ghz
[HTC EVO 3D] egodriver07:
View attachment 900993
[HTC EVO 3D] chlehqls:
The Note comes with 1.4 stock so it seems to match your scores fairly well.

Sent from my Galaxy SII
[HTC EVO 3D] freeza:
2894 (1st try)

My ROM, stockmod kernel.
[HTC EVO 3D] xPSYCHOTRONx:
2775—2824 on the 3d and i get 4500—4617 on my Transformer Prime, both stock.

Sent from my EVO 3D w/ Tapatalk
[HTC EVO 3D] gilbydakid:
freevo ROM, modified dual core stock kernel.
[Bada Software and Hacking General] AbhishekS:
Many Wave users want WhatsApp for bada but I can't see a native app being officially released and so I've created this thread.

We all know that there is a JAR (J2ME) version of WhatsApp available for some models of Nokia feature phones (series40 phones). Can some of the developers here try making that JAR work on bada?

I'm pretty sure that many bada users want WhatsApp.

Thank you!
[Galaxy S II Q&A, Help & Troubleshooting] rez1:
Hello I have been using my sgs2 for 4 months now and for less than a month ago after I installed SPB SHELL 3D using lucky patcher, at first things were fine for 1 week or something and suddently it started boot looping. I can only get it to work again if I do a delvik cache clean up. Basically my situation right now is, I have to do a delvik cache clean up everytime I restart my phone or else the phone will keep boot looping. It loops right after or while the media scanning takes place. Sometimes long after I keep it idle n unlock the screen to select my launcher, then it crashes n reboots. But after a delvik cache clean up everything works fine as long as I keep my phone on.

One more thing, even if I select the default launcher I always have to select which launcher in ever boot. Setting are not saved for some reason.

What could be the problem? I really dont want to do a factory reset, I never did one before and im sure ill loose all setting and all data in each apps.

Btw I have a rooted phone...

Thanks....
[Galaxy S II Q&A, Help & Troubleshooting] nikzDHD:
Grab titanium backup pricey but worth every penny, use that to backup your apps and settings, and then factory reset and restore back.

Otherwise backup apps and data for apps with titanium and upgrade your rom to a newer version.
[Galaxy S II Q&A, Help & Troubleshooting] rez1:
Im waiting for ICS, but ill loose root if I update rom. N finding the root process for new rom is a whole new story...

Update on my phones problem:

I noticed, it does a bootloop cuz SPB is patched n it keeps tryin to check licence n crashes n for some reason IM+ lite autostart makes it worse... Though nowadays im+ gets removed along with many other apps for no reason.
[Galaxy S II Q&A, Help & Troubleshooting] rez1:
Update:

The problem feels like its related to my SD Card... Maybe because of too many apps installed in SD... About 310 apps in total
[Desire Q&A, Help & Troubleshooting] Kroged:
Hi!

I've had lots of problems with my desire, freezing when someone calls me. Last week a friend of mine gave me his desire with broken digitizer. So I made a switch to my digitizer to his phone, rooted and flashed (latest leedroid a2sd).

On my old phone I hade no problems pairing my mw600 and the phone together but now I seem to have a hickup of some sort cause it doesnt matter how I try, my phone simply doesnt find the headset. I also tried to load a data-backup via tiberium backup but without results.

What could this be caused by?
[Desire Q&A, Help & Troubleshooting] neXus PRIME:
Try unpair, turn off mw600, then turn off Phone BT(reboot just to be safe), Turn Phone BT ON, then turn MW600 ON..... Hopefully this will fix it............ Btw, what ROM and Kernel are u using?
[T-Mobile Samsung Galaxy S II SGH-T989] savagepagan:
I read a post in these forums that a guy flashed his T989 galaxy s2. When he went into the network settings, he discovered he had a new option to select LTE bands. Now, after flashing my t989 with Foxstar beta v1.0.2, I now find I have the same option of selecting LTE bands under Network mode settings

Here are some screen shots.

http://http://i877.photobucket.com/albums/ab338/savagepagan/Foxstarbetav102C.jpg

http://http://i877.photobucket.com/albums/ab338/savagepagan/Foxstarbetav102C.jpg

http://http://i877.photobucket.com/albums/ab338/savagepagan/Foxstarbetav102C.jpg

http://i877.photobucket.com/albums/ab338/savagepagan/Foxstarbetav102.jpg

http://i877.photobucket.com/albums/ab338/savagepagan/Foxstarbetav102C.jpg

http://i877.photobucket.com/albums/ab338/savagepagan/Foxstarbetav102B.jpg

Here is the link for the other post I referred to.

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

A forum link for [RADIOS] CWM Flashable Modems. There is a CWM flashable modem for the Skyrocket series.

http://xdaforums.com/showthread.php?t=1426001
[T-Mobile Samsung Galaxy S II SGH-T989] Teo032:
wait what? you did your research.. wait... what is your question? doesn't the threads you post answer your question?
[T-Mobile Samsung Galaxy S II SGH-T989] KillaHurtz:
l o l
[Motorola Droid RAZR] vince.26:
I tried flashing a team for artic and now i'm stuck in a boot loop, how do I get to recovery?
[Motorola Droid RAZR] aktrazer:
If you turn off the phone, (Volume Down and Power, you should see the screen glitch). Then hold down both volume buttons while it's off and press the power button. That will take you to the recovery console.

Navigation note: You can only scroll down, pressing the vol+ key will be the same as hitting enter.

From this screen you can fastboot, recover, etc.

Let me know if you have any more questions!
[Motorola Droid RAZR] MattyOnXperiaX10:
IM sorted

I sorted out the problem by following

http://www.youtube.com/watch?v=WBySMO8n1r4&feature=relmfu
[Motorola Droid RAZR] vince.26:
which roms should I use for fastboot? I have a rogers one, brazil?
[Motorola Droid RAZR] knives809:
Dont you have a backup?

You can try the stock brazil rom.

Check out this link http://xdaforums.com/showthread.php?t=1362956
[Motorola Droid RAZR] vince.26:
I can flash backups? I made one with CWM and its stored on my sd card
[Android Q&A, Help & Troubleshooting] MrDrumngun:
I can't access voicemail anymore. When I dial *86 it says invalid and when I try just 1 it asks for area code. Any suggestions?
[Android Q&A, Help & Troubleshooting] jonasbull:
There's a setting in the phone for what to dial for voicemail, double-check that is *86. If you are coming back from Google Voice integrated you may need to call customer service to get it "unstuck".
[Droid Incredible Q&A, Help & Troubleshooting] Div033:
Hello all, I was wondering if someone more experienced with Sense 1.0 theming could help me out.

I'm trying to re-theme rosie from Jermaine's stock plus rom. I found the 8 pngs I need to edit and went to town on them. I placed the edited pngs into my htc.resources project folder (using apkmanager) and recompiled. I then flashed a from with the new HTC framework apk but Rosie would not load and kept force closing upon first boot.

I know there's an issue with my pngs, but what could it be? I'm a little curious as to how a simple image change could cause an application to crash. I retain the same dimensions and format (PNG) but I still get infinite crashes.

Is there a certain way I need to be saving the PNGs? Are there any other restrictions with how the images need to be? I know .9 patch images are insanely touchy with where pixels can and can't be, so is it a similar issue here? I'm not working with 9 patch images at all in this instance, so I am very confused. Do I have to edit some smali or XML files when I change image data?

I use Photoshop to do all my work and use the save for web and devices option. I leave the PNGs at 24-bits and take out all the metadata.

Any insight would be greatly appreciated!

Sent from my Droid Incredible using the XDA app.
[Droid Incredible Q&A, Help & Troubleshooting] cmlusco:
If all your changing is images in an apk file you can just open (not unzip) the framework-res.apk file with 7-zip, navigate to the res\drawable-hdpi folder, and replace the images you want changed (drag and drop). Once done close 7-zip and push the edited framework-res.apk file to the phone.
[Droid Incredible Q&A, Help & Troubleshooting] Div033:
I'm actually editing com.HTC.resources.apk, is it still okay to do it like that?

Sent from my Droid Incredible using the XDA app.
[Droid Incredible Q&A, Help & Troubleshooting] CondemnedSoul:
Yes it is. As long as its image files and not xml or anything else.
[Droid Incredible Q&A, Help & Troubleshooting] Div033:
Alright. I messed with some images (a couple were blank -- pure transparency, that a problem?) am I'm gonna try again. I also read never to sign HTC apks, which I was doing.

Thank you for the help everyone.

Sent from my Droid Incredible using the XDA app.
[Droid Incredible Q&A, Help & Troubleshooting] Div033:
Success!

Thanks again everyone. I'm not sure if not signing or adding some data into those blank pngs fixed it, but at least I can move on.

So here's another question: if I want to edit 9 patch images, I do need to decompile, edit the 9 patch images correctly and recompile right?

Sent from my Droid Incredible using the XDA app.