yashsingh1/xdaforums huggingface dataset:
[HD2 General] chrisizzle492:
its horrible to see how fast the hd2 lost value. if im lucky i can get 200 on craigslist. it was like this like 3-4 months after the phone came out. even luckier is how it hasnt gone down since then.

i guess im waiting for the sensation :(

most likely 3 months away
[HD2 General] arctic84:
I'm not sure what experiences other people have had with asurion, but mine sucked. Filed my claim and paid accordingly (which took 24 hours to actually process) then they stated the phone was shipped out "next day" , however not providing a tracking number. Finally 2 days later providing a tracking number, no update whatsoever regarding it until I called it in. Then they tell me there was a "problem" with my shipment and that they're going to order a replacement phone for me the same day.
[HD2 General] tabii:
Had a very bad experience with Asurion, so no more phone insurance
[HD2 General] Drashna:
Agreed. Asurion isn't worth it. yes, $130 to replace the phone. Except, I've had T-Mobile for 6 years, and been paying $6.99/month on two lines and have never had a reason to use it till recent. Which is to say, I've paid $500 into the service, and still had to pay $130 "desposit fee". And they wouldn't do anything to help me, other than charge me to use a service I've paid for. I would have enough money to pay out of pocket for the phone easily if I'd set asside the money myself. Which is what I'm doing as soon as I go and cancel the insurance. Especially as now they're going to start charging $5 to file a claim, as of June. Screw you, Asurion. For doing nothing.
[HD2 General] songokussm:
in my area ive never paid over 200 for an hd2. usually around 150. off of cs.
[HD2 General] rhomie:
I just cracked my screen, I looked on the tmobile website and there isnt a hd2 new hd2/refurbished for sale...I would pay the deduct if it they would upgrade similar model but if not I might as well get a 40 dollar digitizer replacement on ebay. Anyone know a updated answer on this?
[HD2 General] Drashna:
Tis what happened to me. Dropped the phone onto cement, and it landed corner first. Broke the screen. And yeah, T-Mobile and Asurion (the equipment protection company that the insurance goes to) are both out of stock of HD2's now. You'll be stuck getting an HD7. And no other options. Peroid. Trust me, I asked, begged, yelled, etc at them to get me a different phone. Heck, tried to get them to lower or waive the fee, as per previous post in this thread. Honestly, I really do need to file a complaint against Asurion. It's a scam, IMO.

If you love your HD2, and don't mind voiding your warrantly permanently, getting a replacement screen/digitizer is worth the money. $60 at most, which is better than the $130 "replacement" fee for an HD7 instead. >:(
[HD2 General] thebest1:
Last month my Tmobile HD2 fell on the cement also and had a broken screen. File with Asurion and i also had to pay a fee of $130. But i received withing 2 days another refurbished HD2. Im surprise how Drashna said that there our of stock of HD2. Drashna im curious but did you received a New or Refurbished HD7 phone?
[G Tablet Q&A, Help & Troubleshooting] forgiventhief:
Thanks. i figured it out.
[Xperia Arc General] Step666:
I was wondering, any objections if I start working on a guide to all things modding-related on the Arc?

I'm not the most technically-proficient so I'll probably need some help to start off with.

But once I understand something, I can generally explain it pretty clearly.

So anyone mind if I get to work on it?

And anyone feel like lending a hand?
[Xperia Arc General] Nimche:
It is a good idea but first we need to find subject many people are interested. You are serving this community the best as you could, why would anyone mind it?

Thanks for offering it.
[Xperia Arc General] Step666:
Well, it would be a guide to rooting, unlocking the bootloader, all that stuff.

But unlike the current guides, it would all be in one place and it would basically start from scratch.

In my experience, one of the more common problems around here is that guides are patchy, they assume varying amounts of prior knowledge, some use confusing or conflicting terms.

My intention is to start from scratch, explain everything in order and make it as simple as possible to find out what you want to do.
[Xperia Arc General] commodoor:
Like a wiki?
[Xperia Arc General] Step666:
Not quite.

More like this.

The first post is like the contents, with links to subsequent posts, one of which would be a guide to unlocking your bootloader, another would be a guide to rooting, another would be a guide to updating your software etc etc.

Basically, a single guide to replace the miscellany of different guides we'd end up with otherwise and much clearer/easier to follow.

No offence to Bin4ry, his work in rooting the Arc is amazing but his 'how-to' is a little unclear...
[Xperia Arc General] Mano1982:
Great idea Step :) I am a noob & i will definetely love this kind of guide :)
[Xperia Arc General] Step666:
So trhe first question is, apart from unlocking the bootloader, rooting and updating the phone, what else would such a guide need to cover?
[Xperia Arc General] diggedy:
its always good to see these types of threads in the different phone sections. Definitely a good thing mate, you go for it
[Xperia Arc General] Step666:
I will, just as soon as I can get answers to a few questions first.
[Xperia Arc General] commodoor:
Looks great it will help alot people.

Damn its been long time ago I have seen that site again :p
[Xperia Arc General] Step666:
It's a long time since I was active there ;)
[Xperia Arc General] PollPixx:
Good idea. Needs some loyalty from the ts to update the topic in order to keep it up to date (and therefore successful), but if you think you can do it, please do, it will help a lot of people for sure.
[Xperia Arc General] im_iceman:
I'd like to see a section on Performance mods - overclocking and anything else that can be done to improve performance.
[Xperia Arc General] Step666:
Overclocking is just a matter of installing an app like Set Vsel.

It's not really quite the same as flashing and so on.
[Xperia Arc General] im_iceman:
don't think the kernel supports overclocking at the moment.. can't get it to go above 1024Khz..
[Xperia Arc General] Step666:
I think it's more a matter of the app being updated to support the Arc but I may be wrong.
[Xperia Arc General] dh2311:
No, sadly its not that easy, the kernel restricts the processor from going over that value. Set CPU merely reads that value, to prevent people overclocking 500mhz to 2Ghz and melting there phones.

The kernel needs to be tweaked to allow higher values. But that should be in the pipeline now that bootloaders are unlocked and phones are rooted.
[Xperia Arc General] Step666:
Then how do you explain handsets like the Motorola Defy which can be OCed despite the fact it's impossible to modify the kernel? :confused:
[Xperia Arc General] im_iceman:
I guess Moto mustn't have restricted it in their stock kernel
[Xperia Arc General] Step666:
I guess - though it's not like Motorola to do anything modder-friendly ;)
[Nook Color General] tuxhacker:
I noticed more people are having same issue as me and I wanted to create a thread to find the solution.

I was running CM7 RC4 / OC 40311 - It was running fine and one day system hung and so I rebooted and that was it.

Symptom :

System boots and pass the "Touch the future Reading" and displays "ANDROID _" on the bottom of the screen and after 10-15 sec it reboots and loop this process.

Things I tried so far :

CWR 3.0.0.5

- Repratition to stock nook.

- Getting error when I try to format system and data - I thought it was because CM7 was setting system to ext4.

- ADB and DD boot.img, System.img and copy Factory to mmcblk0p3

- Try to restore from back up I made

- Nothing works but goes back to boot loop

CWR 3.0.0.6 - One I got from CM7 install to emmc thread

- System format works

- Install latest nightly

- Restore from back up

- ADB can't find device - This is odd and couldn't find a way to fix it yet.

- Tried to install Stock zip but going back to CM7 boot loop

CWR 3.0.1.0

- Can't format data/system

- ADB to delete partitions and create them again but it doesn't help

- Tried all zip files to bring it back to stock - no go

- ADB to copy Factory.zip to emmc partition - umount and mount again then file I copied is gone.

- Deleted partitions and reboot but some how I got back to CM7 loop

If you are having same issue please post and share your experiences so we can find the solution!!!
[Nook Color General] fattire:
This means the kernel is loading, and most likely the init.encore.rc is running as well. Have you tried grabbing a log from adb logcat? Or perhaps checking if the shell works?

How are you repartitioning?

What is the error?

Again- if its getting an error, what is that error? Have you tried formatting manually?

Errors? Logs?

You have to be more specific.
[Nook Color General] tuxhacker:
- I was flashing "repartition-boot-with-stock.zip" also tried to delete the partitions using fdisk - from adb shell

- And I was getting "Error formatting / system!" and "Error formatting /Data!" from CWR format system and format data

I also tried to format it manually using "mke2fs /dev/block/mmcblk0p1,2 and 3..."

And could you please tell me how to get the log?

Thank you.
[Nook Color General] john10101:
have you tried booting off an cwr 3.0.1.0 bootable sd card and formatting reinstalling?
[Nook Color General] tuxhacker:
Yes I have. I tried several times. It seems like my nook is a read only device now. It won't take any changes.
[Nook Color General] chisleu:
unpossible!
[Nook Color General] tuxhacker:
Here's one example. I did this from CWR 3.0.1.0.

- Mount mmcblk0p3 to emmc

- Copied factory.zip to emmc

- ls -l /emmc to check the new file

- umount /emmc

- Mount /emmc again

- ls -l as you can see old file date again. :(

~ # mount -w /dev/block/mmcblk0p3 /emmc
mount -w /dev/block/mmcblk0p3 /emmc
~ # mount
mount
/dev/block/mmcblk0p3 on /emmc type ext2 (rw,errors=continue)
~ # exit

C:\Program Files\Android\android-sdk\platform-tools>adb push factory.zip /emmc
3779 KB/s (168335604 bytes in 43.492s)

C:\Program Files\Android\android-sdk\platform-tools>adb shell
~ # ls -l /emmc
ls -l /emmc
-rw-rw-rw- 1 root root 168335604 Apr 17 04:06 factory.zip
drwx------ 2 root root 12288 Oct 23 05:27 lost+found
-rw-rw-rw- 1 root root 2567 Nov 17 22:27 rombackup.zip

~ # umount /emmc
umount /emmc
~ # mount /dev/block/mmcblk0p3 /emmc
mount /dev/block/mmcblk0p3 /emmc
~ # ls -l emmc
ls -l emmc
-rwxrwxrwx 1 root root 168332495 Nov 11 23:35 factory.zip
drwx------ 2 root root 12288 Oct 23 05:27 lost+found
-rw-rw-rw- 1 root root 2567 Nov 17 22:27 rombackup.zip
~ #
[Nook Color General] lechiffre:
May I ask why you had to mess around with the partitions at all?
[Nook Color General] tuxhacker:
It was keep rebooting itself so I was trying to reflash CM7 but didn't work. Next I was going back to stock to start over and that didn't work. Found one thread about DD boot.img, system.img and factory.zip to mmcblk0p3 then 8 failed attempt to restore to stock. etc...

I'm sure that while I was trying to fix I made more mess. :(
[Nook Color General] tuxhacker:
I did adb logcat and got the permission denied error.

C:\Program Files\Android\android-sdk\platform-tools>adb logcat
- waiting for device -
- exec '/system/bin/sh' failed: Permission denied (13) -
[Nook Color General] reaper12:
Did you try going into clockwork recovery and using the fix permissions option?
[Nook Color General] lechiffre:
I still don't get why you decided the partitions were faulty.

This might not help you now but might help others in you situation. IMO the process should be when you encounter bootlooping:

1. Reflash current OS using CWR 3.1.0 uSD.

2. If Step 1 fails, using CWR 3.1.0 uSD: format /system /data /cache. Attempt to install CM7. If CM7 install fails, attempt to install stock.

3. ***Requires a a working CWR backup which should contain your original boot partition***

If Step 2 fails, using CWR 3.1.0 uSD: format /system /data /cache and /boot. Restore stock /boot partition only via advanced restore. Attempt to install CM7 or stock.

4. ONLY if the previous steps fail should you even touch any partition tool. I've never had to use any, but I've never messed with the partitions in the first place (ie double booting off eMMC).
[Nook Color General] themitchy:
Just wanted to share that getting stuck on the boot screen may not have anything todo with what or how you've flashed.

On a fresh install/flash of CM7 I can reboot just fine as many times as I want. As soon as I restore all my apps and reboot I get stuck on the boot screen.

So SOMETHING amongst all the apps I have backed up gets me stuck on the boot screen. Really don't want to go through a reboot for each app one at a time though :confused:
[Nook Color General] turbo.dex:
FIXED - wipe battery status in CWM

This problem seems to occur when the battery runs out, Nook is plugged in and then it hangs at "the future..."

So to fix this problem, boot into CWM (using CWM for SD) and go to Advanced-Recovery and Wipe Battery Status. Remove the CWM SD and go back to the root menu and reboot.

Your CM7 would boot now just fine. I don;t know what the problem is yet, but that seems to fix it. It saved me from reinstall.

the Nook gets into this state only when the battery is completely drained.
[Nook Color General] drazil22:
TuxHacker, did you ever resolve your issue of what seems to be the internal memory being in a write-protected state? I'm in the exact same boat you are :( but instead of CM7 I got CWR 3.0.0.5 installed on my boot and brianf's custom froyo installed.

I agree it seems like the device is now write protected as I've mounted boot/system/media and deleted everything in there, ls'd to double check, but once I remount, all the old stuff is back there again.

I also tried using samuelhalff's NookUMC app to mount all the partitions in windows, deleted everything, and upon remount, all the files are back. The NookUMC app was the one I initially used to copy a bunch of mp3's and vids to the media partition in the first place and now this partition behaves as if it was write-protected as well.

I can't speak for TuxHacker, but mucking around with the partitions seems to be a last ditch effort to at least *change* anything on the device. I've followed a few guides on here about showing the partition table and mine matches a stock partition table. I haven't gotten around to actually modifying any of the partitions yet though...

In all of your steps, the first sub-step is to format one or all of /system /data /cache /boot. This is precisely the step that fails for us with "Error Formatting /system!" or any of the others :confused: The only CWR that it doesn't fail on is CWR 3.0.0.6, but any flashes don't take, the NC just reverts back to what it was just before the system decided to go read-only.

I'm running off SD now but that is a pretty crappy experience... if anyone can fix the mess we got ourselves into I will def buy that guy a cold one!
[Nook Color General] tuxhacker:
Yes. And on CWR 3.0.0.6 I can't connect via ADB so can't do much with it. On CWR 3.0.1.0 and CWR 3.0.0.5 I can connect via ADB but can't format. I tried all the ADB connect tips and tricks but no go.

I think it coubd be a permission issue since I get - exec '/system/bin/sh' failed: Permission denied (13) - when I tried ABD logcat while its rebooting.

I'm also running off SD now and it is really bad. :(
[Nook Color General] getllamasfast:
I'm in the same boat as you guys and I just wanted to add my two cents.

I've tried multiple times to use the partitioning tools that drazil22 is talking about, but every time I reboot, the partitions come back. What is weird is that while I'm still in adb, after I've written the partition table back to the device, is that it shows the new partition table when I tell it to print it out. I can exit all the way out of adb and, unless I've rebooted my nook, the partitions are back to the way they were. However, once I reboot my nook, the partitions come back...

I've gone as far as deleting every single partition and then rebooting just so that I could have a brick to take back to B&N, but the stupid partitions keep coming back...
[Nook Color General] drazil22:
lol that's what I was thinking too... brick the thing and get the store to reflash it, as someone else with a bricked nook did. I think the store must have another utility or device to reflash it back to stock.

The weird thing is any changes I make stay for the session until I unmount. I tried to copy the system.img and boot.img which is a little over 500MB to the /media partition (mmcblk0p8) but because I filled it with mp3's and videos, only about 200MB was free and of course the adb push errored out saying not enough space. I then navigated to the /media partition, deleted a bunch of videos and was able to adb push the two files over. I was also able to run the dd commands and got the expected results. Upon reboot, of course nothing got dd'd, the two .img files I copied to /media were gone, and the videos I deleted to free up space were back!

I was also hoping that with the new B&N update to 1.20, they might have released a flashing utility but I guess that was wishful thinking...

Edit: one other peculiar thing I noticed is that when I use adb when booted into CM7 (using the SD), it shows the serial number as 11223344556677. When I use adb booted up using the CWR on my boot partition, or with a bootable SD, it shows the actual serial number written on the sticker behind the sd cover.
[Nook Color General] RileyGrant:
This is odd, but I dont think this is limited to CM7 as I've seen it happen with different phones running AOSP. Over on the Evo there was numerous accounts of peoples devices suddenly rebooting and then getting stuck in a bootloop, all partitions seemed to be corrupted including the recovery partition and there was absolutely no way to write to the system anymore. Complete booting brick. No one was able to find the cause and no one was able to find a fix.
[Nook Color General] getllamasfast:
:(

I really hope this isn't true...

On an unrelated note: Do you think that B&N would notice if I microwaved my nook for a few seconds?
[LG Optimus 2x] Kickasskev:
Ok people I dont want you to do my local shopping at Asda but I'm after a couple of things and can't find them

Docking stand similar to this

http://cgi.ebay.co.uk/HTC-Desire-HD...ories_MobilePhoneChargers&hash=item3cb26ac14c

And I also want some screen protectors that don't have floppy loose edges where the screen curves, as when I put my Silicone case on it lifts the protector, I have had my phone a week now and am on to my 5th screen protector.

Any help appreciate in advance

Im in the UK by the way and don't wanna shop abroad
[Desire Q&A, Help & Troubleshooting] steph_htc:
Hi,

Does anyone has a disk space issue with this ROM: InsertCoin_GB_Sense2.1_CM7_v03.zip?

Configuration: CM7 and alpha HBOOT

Thanks
[Desire Q&A, Help & Troubleshooting] 852456:
Are you using a costom h-boot?

+ the right partitions - ext3?
[Desire Q&A, Help & Troubleshooting] steph_htc:
More informations:

---Alpha rev---

BRAVO PTV1 S-OFF

HBOOT 0.93.0001

Radio 5.11.05.27

recovery 2.5.1.8 (blue) from AlphaRev. But when I flash the zip, the recovery was the 3.0.0.5 (orange).

I try also w the 2.5.1.8, till have the same issue...
[Desire Q&A, Help & Troubleshooting] steph_htc:
you have conversion tools 2nd page or with cwm 3.0.0.5 just wipe user data the recovery will reformat your partition to EXT3

so I guess it's now EXT3...
[Desire Q&A, Help & Troubleshooting] 852456:
Hmmm i dont think you have the cm7 h-boot, you are only s-off with alpharev... go to alpharevs site and download the pb.img witg cm7 and change it (read the tut on the side) copy to sd and go on fast boot and say yes and yes for upgrading.

Here you gohttp://alpharev.nl/:

You can also download the corresponding PB99IMG zipfile, put it on your sdcard, and rename it to PB99IMG.zip. Then start the phone in HBOOT mode (VolDown+POWER) to flash the HBOOT without a PC. It is however still necessary to either restore your nandroid, or reflash your ROM after doing this. The partition LAYOUT has changed, the actual data still needs to be 'moved'.
[Desire Q&A, Help & Troubleshooting] steph_htc:
Thanks for the help :)

But, I already done that and I think it's ok because when I did a backup I have:

system: 123.52M

sd-ext:235.75M

data:137.34M

so it's ok no?

But the disk space avalable is 23Mo, when I install new apps, I have the warning of disk space :(
[Desire Q&A, Help & Troubleshooting] 852456:
Its not ok, my friend had the seme problem as you, and he had stock h-boot...

On h-boot

It must say:

Alpharev CM7
[Desire Q&A, Help & Troubleshooting] steph_htc:
ok thanks.

I try again and w the zip file I have a CID error :(

I had a look on the forum and try the fastboot method.

I will keep you updated
[Desire Q&A, Help & Troubleshooting] 852456:
OK, if you are not so experienced you can try this to push the h-boot on:

http://xdaforums.com/showthread.php?t=823315
[Desire Q&A, Help & Troubleshooting] samreedy:
Ive had the same problems... might give a few of your suggestions a try and see if it works :)
[Desire Q&A, Help & Troubleshooting] steph_htc:
thanks for your help, I'm currently reading this article ;)
[Desire Q&A, Help & Troubleshooting] steph_htc:
now I have the hboot CM7.

full wipe and install of the rom. So wait and see :)

Thanks again for your help.
[Desire Q&A, Help & Troubleshooting] 852456:
It must be all ok now... :D
[Desire Q&A, Help & Troubleshooting] steph_htc:
Thanks a lot. It's working. Available memory >180mo

:D

Subject close :)
[Desire Q&A, Help & Troubleshooting] samreedy:
how did you fix it?
[Desire Q&A, Help & Troubleshooting] 852456:
You have the wrong h-boot!! See the whole thread...
[Desire Q&A, Help & Troubleshooting] steph_htc:
HBOOT CM7 & CW3: how to

follow these instructions:

- step 0:

- device has to be S-OFF

- step 1:

Here you go http://alpharev.nl/

You can also download the corresponding PB99IMG zipfile, put it on your sdcard, and rename it to PB99IMG.zip. Then start the phone in HBOOT mode (VolDown+POWER) to flash the HBOOT without a PC. It is however still necessary to either restore your nandroid, or reflash your ROM after doing this. The partition LAYOUT has changed, the actual data still needs to be 'moved'.

If you have a CID error message in HBOOT mode. Go to step2...

- step 2:

- donwload the bravo_alphaspl-cm7.img file.

- install FastbootCommanderV.1.1.zip. Read this: http://xdaforums.com/showthread.php?t=823315

You need java (cf java web site).

For W7, I had to modify the windows path variable in the windows advance seatings to add the java path (C:\Program Files (x86)\Java\jre6\bin). I also add admin privilege on java.exe, javaw.exe

- Create a IMGFiles directory and put inside the bravo_alphaspl-cm7.img file.

- reboot your phone in HBOOT

- plug to PC w USB

- run the FastbootCommanderV.1.1.jar

- click on HBOOT/spl button and select the bravo_alphaspl-cm7.img file

- click on recovery button and select the recovery-bravo-3.0.0.5-r3.img file

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

- click on flash spl

- click on flash recovery

On MISC tab, you can reboot your phone in HBOOT and check that you have the new HBOOT CM7 :)

- last step:

- enter in recovery

- wipe full

- go to select zip and pick your ROM

It takes a while for the first boot.

Hope it helps. If you need more details, ask :)
[Desire Q&A, Help & Troubleshooting] flitz:
How come :

I've downloaded rom and setup gmail etc..

It automaticly downloads my apps ? Where can I choose wich apps and wich dont ?
[Desire Q&A, Help & Troubleshooting] steph_htc:
Hi,

From my experiences...:

If you used a gingerbread before, it will be done automatically.

The market will reinstall the app you downloaded....

If it's the first time you are using gingerbread, you have to pick your apps in the market.

with this ROM, you can move all apps to the SD :).

Can be done in app settings.

Hope it help.