Database Users

XDA Mini S Screen problem - Photo's now available

I've got a problem with my XDA Mini S. It's been sitting in a box in my shed for about a year, before I got it out yesterday to have a play around with it, and possibly try some software I found on it.
I put my sim card in, plugged it in to charge, and turned it on. It worked absolutely fine.
I haven't done anything with it yet, but I've turned it on now, and the colours are messed up on the screen. For example there is a red hue over the today screen, and on certain screens (like in bootloader mode) the colours appear to be inverted (I will post pictures later if needed).
I've tried reformatting the device, but this has not fixed the problem. I thought I would try reflashing the rom on it. I used to have the original o2 rom on my old laptop, but lost that when I had to reload windows.
I downloaded the original rom from here, along with the Rom Update Utility, and attempted to reflash it. It gets as far as 'verifying the information on your PDA phone', then crashes with the error: Rom update utility MFC application has stopped working.
I'm running windows vista on my laptop, and read that the RUU won't work until the drivers are updated. Following the instructions on mrvanx.org, I have downloaded the driver for vista and installed it, but i'm still getting the problem when I try and reflash the device.
I've also tried running the RUU in compatibility mode for XP as it worked fine on my old laptop which was running xp, but it still crashes, every time.
I'm beginning to wonder if reflashing it will even work though, since the colours are messed up in bootloader mode as well, which leads me to think it may be a hardware problem.
I know next to nothing about repairing these though, and probably wouldn't bother if it's a hardware problem, but until I can reflash the firmware, I won't know whether this is a case.
I'll get the photo's of what the screen is like uploaded to my server later on, and post the links here, so you can see what the problem is.

Photo's now available
I've uploaded a couple of photo's to show what the screen is like:
http://csc2ya.co.uk/images/bootloader.jpg
http://csc2ya.co.uk/images/startup.jpg

Update
i've got my old laptop out, reloaded xp on that, and attempted the flash using that. However, I get the message 'rom update utility MFC has encountered an error and needs to close'
I just want to get it to reflash to see if it fixes the screen, but so far i'm having no luck at it.
I've sucessfully reflashed it in the past with the o2 rom using my old laptop, so I can't figure out why it isn't working now.
Update: I didn't have activesync installed on my laptop which was why the updater was crashing. I've installed activesync, but now i've got another problem that is preventing me from reflashing it. I start the updater, and click through the prompts. It gets to 'verifying the information on your pda phone', stays like that for about 30 seconds, then activesync disconnects, and I get the error: microsoft activesync cannot recognize this device for one of two reasons: then the other information that the dialog gives. I'm not going to bother typing it all out, as i'm sure nearly everyone has seen it at least once before.
Additional info: No idea if this is relevant or not, but the extended rom has been formatted using the service tool.
Another update: I have now managed to get the device to reflash, but it boots up afterwards as if I had just turned it off and back on again. I have tried a hard reset afterwards, but cannot seem to get any of the o2 stuff back. It appears that the screen problem is hardware related though, as it is still present even after reflashing.
I can also no longer get it to go into bootloader mode, but the phone will still boot normally.

csc2ya said:
It's been sitting in a box in my shed for about a year.
Click to expand...
Click to collapse
Not to be flippant, but there's your problem right there. Two things: extreme temperature, and moisture. Both are the enemy of electronics. Chances are very good that you're screwed.
The first thing I'd do is buy (or even better, borrow) a new battery. Yours is probably done for.
If that doesn't fix the problem, I recommend disassembly and thorough cleaning with isopropyl alcohol, followed by at least 24 hours of strong, dry airflow between 50-80 Fahrenheit. Any floor or desk fan would do. Reassemble and pray. If that doesn't do it, you're going to have to find your fun elsewhere, I'm guessing.

Myrddin Wyllt said:
Not to be flippant, but there's your problem right there. Two things: extreme temperature, and moisture. Both are the enemy of electronics. Chances are very good that you're screwed.
The first thing I'd do is buy (or even better, borrow) a new battery. Yours is probably done for.
If that doesn't fix the problem, I recommend disassembly and thorough cleaning with isopropyl alcohol, followed by at least 24 hours of strong, dry airflow between 50-80 Fahrenheit. Any floor or desk fan would do. Reassemble and pray. If that doesn't do it, you're going to have to find your fun elsewhere, I'm guessing.
Click to expand...
Click to collapse
The battery appears to be fine. I charged it overnight, and it still seems to hold a decent charge.
I haven't really got the tools to dissasemble it fully, but I will give it a go sometime in the next few weeks (i've got a copy of the service manual on my computer, so that shouldn't be a problem).
I only really got it out to play around with it again, and possibly try some apps on. It still appears to work fine apart from the screen (and the o2 applications now missing due the extended rom format, but i'm not bothered about those). I've installed the my mobiler screen program on my laptop so I can at least view the screen properly using that.
Thanks for the suggestions anyway.

csc2ya said:
I've installed the my mobiler screen program on my laptop so I can at least view the screen properly using that.
Click to expand...
Click to collapse
Well, this certainly changes things. You have a bad screen, or a bad connection to the screen. You can get replacement for around $100USD, or you can try to get a broken unit with a good screen for less (maybe). I'd still disassemble it first, though, in case it's just a weak connection.

[Fix]boot freeze-up

hello folks,
I have seen some threads talking about some WM device freezing in bootup, and stick in the 1st screen when it says "stick together", I had the same problem, and I did contacted HTC for support, it seems they dont have a solution for that problem but to send the phone to them, whicj gonna take around 10 or 15 days to get back -if the warranty still in effect- and they probably gonna charge you something more than the shipping back fees, cause you flashed your device.
I was Planing to send my phone this monday, but i though lets try something and see what gonna happen, so what i did is :
1 - take you SIM card and your SD card, (don't connect your phone to your PC)
2 - While holding the VolUp press the Power button, you will see a screen with your device information
3 - Now connect your device to you PC, and use one of the Wm costume ROM, don't worry about the guide line, and about the winSync instruction, cause it do work without windows Sync
4 - follow the instruction on the costume ROM application, and just ignore the WmSync one.
your phone will reboot, and you probably gonna see your device radio and room information.
I just did the sameting to fix my device, I don't know if just got lucky
But I do have a problem now, I cant install android on my device, and when i try to lunch CLRCAD, it does not start, even when i lunch haret, the device reboot, if someone know a fix to that problem, so may help me.

dude, out of your three posts, two have been new threads that are strictly related to user-problems in a developmental sub-forum, which just isn't cool.
its like someone walking into your work meeting and asking about the lunch schedule (not the best analogy, but you get the point)
if you're really stuck in something, a hard reset always restores things nicely

bravo261 said:
dude, out of your three posts, two have been new threads that are strictly related to user-problems in a developmental sub-forum, which just isn't cool.
its like someone walking into your work meeting and asking about the lunch schedule (not the best analogy, but you get the point)
if you're really stuck in something, a hard reset always restores things nicely
Click to expand...
Click to collapse
i'm just trying to stay in the dark, waiting for the moment to say something useful, by the way hard reset does not work all the time

The only time a hard reset does not work is if there is something wrong with your phone or somehow you corrupted your ROM. In that case going into Bootloader and upping a new ROM does the trick. A Task29 will really fix things well.
As far as "launching" CLRCAD...it does nothing ANYWAY! You just tap it and that is it...it merely sets up the phone for Android to have sound, nothing more...no prompts, no hour glass nothing. (A SEARCH or reading the first post would have told you this.)
If you get resets in Haret then Android did not load correctly. Merely delete your data.img and start over. If that does not work then you likely corrupted your Android build....format your SD card and reload Android from scratch.
I personally have backed up my working daily build on a weekly basis so in case my Android gets hosed, I merely have to copy my entire backup (which is just a copy of my SD card on my computer) back to the SD card after a format (but have yet to really have a need for this except months ago).

Stuck in bootloader --> Volume down is broken/stuck

Edit: Im stuck in bootloader with the only option to press power on is fastboot. and from there i cannot select any options because the navigation is broken. Im looking to restore it to factory so i can take it to the sprint store to have replaced. Please help me! Most likely an autorun from fastboot or a computer pushed through usb command promt that i can take over the phone. PLease HELP!

Have you tried the ruu? Its an executive file that you run from your computer and it restores your phone to stock. I've never had to run it so I cant tell you the exact details of how it works, but that could do the trick. I think there is a way also via using fastboot commands, but someone more intelligent then I will have to provide you with links. Also have you tried putting unrevoked forever s-on on your sd card and naming it PC36100.img then butting into hboot and letting it scan for that? Once it finds it, it should flash it on its own, then once youve done that, you can pull your sdcard again, delete that PC36100.img and put the PC36100.img that returns you to stock on your sdcard then boot into hboot again. It should find that image then flash you back to stock.

Ill try that. My down button is definatly either stuck, disconnected or something. When i press the up button and power it will Vibrate 5 times.
Ok i got the zip to load but my down and up buttons do nothing. is there a way i can have recovery auto run? or edit the hboot so that it automatically runs the recover.img?
Update: It's stuck in bootloader i guess... I restart and the volume down is stuck im pretty sure so it always goes to that. I have it hooked up to my computer, can i push commands through usb to it in bootloader menu...
Fastboot
...
....
Sim-lock
etc.
my only working option is to click power and have the fastboot initiate and then give me an option [1] ........ that i am unable to highlight or get to because of the stuck down button.

y0ungcitty said:
Ill try that. My down button is definatly either stuck, disconnected or something. When i press the up button and power it will Vibrate 5 times.
Ok i got the zip to load but my down and up buttons do nothing. is there a way i can have recovery auto run? or edit the hboot so that it automatically runs the recover.img?
Update: It's stuck in bootloader i guess... I restart and the volume down is stuck im pretty sure so it always goes to that. I have it hooked up to my computer, can i push commands through usb to it in bootloader menu...
Fastboot
...
....
Sim-lock
etc.
my only working option is to click power and have the fastboot initiate and then give me an option [1] ........ that i am unable to highlight or get to because of the stuck down button.
Click to expand...
Click to collapse
all you need is fastboot mode, from there you can run the RUU

xHausx said:
all you need is fastboot mode, from there you can run the RUU
Click to expand...
Click to collapse
What driver do i need for the device?
For some reason its not showing up as ready to do it.

The htc sync drivers
y0ungcitty said:
What driver do i need for the device?
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App

Both my volume keys are broken so I took my evo apart and used a thin metal to push the spring that controls the keys and load up a nandroid. Hope this helps.

alexisprz said:
Both my volume keys are broken so I took my evo apart and used a thin metal to push the spring that controls the keys and load up a nandroid. Hope this helps.
Click to expand...
Click to collapse
Load up nandroid?? im so out of the whole evo scene. can i have a link or procedure.... sorry for being a big noob.

If I can remember, running the stock ruu exe will do everything for you without any need for you to do anything with the phone to help it. Just make sure you have the htc sync program installed. Next make sure the phone is on and running (not in hboot or recovery). Plug the phone into the computer with the data cable. Make sure it's only in charge mode. Run the ruu exe. Be patient because it might take some time to start up. Make sure you have nothing running in the background on the pc. No antivirus or anything and I do mean anything. Don't touch or move the phone or cable while the ruu is running or you might risk bricking the phone if the connection between the phone and pc is interrupted. Don't let the computer go to sleep or standby. Make sure your phone's battery has a full charge. The ruu will make the phone reboot into upload mode. Then it will upload all the stuff the phone needs to be put back to factory. It might reboot the phone a few times. This is normal. You don't have to worry about the broken volume buttons interfering with ruu.
Lastly, make sure you remove your sd card before you get to the store to let the tech check it out. Don't offer any additional information. Just tell them the volume buttons stopped working and you did a full factory reset before you got there.
After running the ruu, don't sign into google account so your personal information won't be on the phone and none of the programs you bought will show up in the market. You should have a backup old phone with you so you or they can activate it for you in case they want to keep or swap it out. If they give you a refurb, power it up and test it at the counter to your satisfaction BEFORE you leave the counter and store. I noticed something wrong with the refurb they gave me and I'm glad I didn't walk away. The tech fixed the problem with the refurb (uneven backlighting on the screen). I was able to use my old screen with the refurb's guts and my screen didn't have any flaws in it.
You do what you want but this is my suggestion based on my experience with exchanging a defective phone. I have full insurance and or tep so it was a hassle free experience.

herbthehammer said:
If I can remember, running the stock ruu exe will do everything for you without any need for you to do anything with the phone to help it. Just make sure you have the htc sync program installed. Next make sure the phone is on and running (not in hboot or recovery). Plug the phone into the computer with the data cable. Make sure it's only in charge mode. Run the ruu exe. Be patient because it might take some time to start up. Make sure you have nothing running in the background on the pc. No antivirus or anything and I do mean anything. Don't touch or move the phone or cable while the ruu is running or you might risk bricking the phone if the connection between the phone and pc is interrupted. Don't let the computer go to sleep or standby. Make sure your phone's battery has a full charge. The ruu will make the phone reboot into upload mode. Then it will upload all the stuff the phone needs to be put back to factory. It might reboot the phone a few times. This is normal. You don't have to worry about the broken volume buttons interfering with ruu.
Lastly, make sure you remove your sd card before you get to the store to let the tech check it out. Don't offer any additional information. Just tell them the volume buttons stopped working and you did a full factory reset before you got there.
After running the ruu, don't sign into google account so your personal information won't be on the phone and none of the programs you bought will show up in the market. You should have a backup old phone with you so you or they can activate it for you in case they want to keep or swap it out. If they give you a refurb, power it up and test it at the counter to your satisfaction BEFORE you leave the counter and store. I noticed something wrong with the refurb they gave me and I'm glad I didn't walk away. The tech fixed the problem with the refurb (uneven backlighting on the screen). I was able to use my old screen with the refurb's guts and my screen didn't have any flaws in it.
You do what you want but this is my suggestion based on my experience with exchanging a defective phone. I have full insurance and or tep so it was a hassle free experience.
Click to expand...
Click to collapse
I already have a pre activated but i cannot get the phone to start without going into the Power+Down Menu... Can i run RUU from that? im not able to get it running on Android

I don't know. Something worse could happen but there's also a chance it might work. I am guessing ruu would tell it to reboot into upload mode. If the phone couldn't get into that mode the ruu might stop. This is just speculation. If you knew that the tech wouldn't bust you for having root, then I'd say to just take it in. It's a big risk in my opinion.
I don't know if there is a img file to fastboot flash a stock recovery. I don't know if that would help. Need to figure out a way to get the s-on and push stock back into it, or at the very least get s-on in hboot.
I'm thinking that because if the button is broke, and you can't get the phone past the hboot screen, then maybe the tech might not want to waste anymore time on it and just order a replacement. The hboot screen would be the only thing he could get into. I don't know but I think it could be helpful, maybe, if adb or something else could push an original rom into it at the screen it's stuck in. I think if you tried, if it wasn't working, the phone and adb wouldn't be communicating like normal and adb would not continue. I am guessing pushing a stock recovery wouldn't turn s-on. It would be great if it did.
I would say that talking with one of the devs that has got their hands dirty in hboot and fastboot, might give better advice. Perhaps they know of a way to force things into the phone that the general public wouldn't normally need to know or do. I am no expert. I suggest talking to people that developed in those areas. Didn't toast work with that?
I don't know what else to suggest. I'm running out of ideas.

I just had another idea. What if you could get a pc36img.zip, or whatever it's called, into root of the card and the phone will want to flash it. Only snag I can think of is I think hboot will ask if you want to flash or update or whatever it's called. That might be the down button. Maybe someone could run with that idea?
I would say read the rooting articles and see if you can adapt what they are saying to push stock everything back in instead of trying to root.
Even if you can't get the updated rom to install, if it can be pushed into the phone and the phone is made to boot like normal, the phone "should" try to apply it if anyone can get it to boot normally. I'm thinking that's another way to cover your ass.
If all else fails, then I would suggest to say a little prayer before going to the store and hope for a tech that isn't going to be a **** about it. Don't get an attitude towards the employees because that could make things much more difficult for you. A seasoned dev or a tech might be the only people that could help. Going into the irc channel for the evo and hanging around in there might get you hooked up with someone that could help more than the people that hang in the forums. I don't see serious devs hanging around the forum and bullshitting with the people there. Go where they might be, in irc. Be cool with them, don't be aggressive or flaky. If you are nice/cool with them, they might take the time away from what they are working on to help you.

herbthehammer said:
I just had another idea. What if you could get a pc36img.zip, or whatever it's called, into root of the card and the phone will want to flash it. Only snag I can think of is I think hboot will ask if you want to flash or update or whatever it's called. That might be the down button. Maybe someone could run with that idea?
I would say read the rooting articles and see if you can adapt what they are saying to push stock everything back in instead of trying to root.
Even if you can't get the updated rom to install, if it can be pushed into the phone and the phone is made to boot like normal, the phone "should" try to apply it if anyone can get it to boot normally. I'm thinking that's another way to cover your ass.
If all else fails, then I would suggest to say a little prayer before going to the store and hope for a tech that isn't going to be a **** about it. Don't get an attitude towards the employees because that could make things much more difficult for you. A seasoned dev or a tech might be the only people that could help. Going into the irc channel for the evo and hanging around in there might get you hooked up with someone that could help more than the people that hang in the forums. I don't see serious devs hanging around the forum and bullshitting with the people there. Go where they might be, in irc. Be cool with them, don't be aggressive or flaky. If you are nice/cool with them, they might take the time away from what they are working on to help you.
Click to expand...
Click to collapse
thanks! were can i go to find this irc? ive gotten a recovery image on the evo's root micro sd in a pc3600 or w.e zip and gotten it to ask me if id like to run it but it wont go any further than that because i cant chose the option. I have a bit of nail glue and im thinking about trying to glue a hair pin to the down button and giving it a pull while i try and run or maybe i can break the button and say oh well... and then from there do it. I dont have any hex or w.e screw driver that are small enough to open the case and do the option described in page one of this forum. Thank you everyone for the help! and keep the ideas coming. I refuse to let this turn out bad, worst comes to worst ill replicate water damage or something and fry the damn thing. then bring it in as a brick.

Any guru's have a quick idea because i want to do this swap.. im so sick of the palm pre. Its like a baby compared to android.

The irc info should be on one of the stickies at the top of the forum. Shouldn't it say something like join us at #evo or something like that.
This is where you can be opening a can of worms, so you've been warned. You can go to sears I think and the tool section and I think they might sell those wierd screwdrivers. I found one that worked for my macbook's harddrive brackets. It's long, has a black handle and generally different colored caps on top of the handle. I kinda doubt radio shack would have it but you could try. Oh, and get a guitar pick to use a the tool to separate the two halves of the phone. I wouldn't use anything else or it might f up the plastic and be obvious you was inside. Maybe look for an evo teardown video somewhere to show you what to expect. Don't force anything!

herbthehammer said:
The irc info should be on one of the stickies at the top of the forum. Shouldn't it say something like join us at #evo or something like that.
This is where you can be opening a can of worms, so you've been warned. You can go to sears I think and the tool section and I think they might sell those wierd screwdrivers. I found one that worked for my macbook's harddrive brackets. It's long, has a black handle and generally different colored caps on top of the handle. I kinda doubt radio shack would have it but you could try. Oh, and get a guitar pick to use a the tool to separate the two halves of the phone. I wouldn't use anything else or it might f up the plastic and be obvious you was inside. Maybe look for an evo teardown video somewhere to show you what to expect. Don't force anything!
Click to expand...
Click to collapse
Thanks I baught a T5 screw driver that will be here the 10th or the 11th and im excited to crack it open haha. Ill let you know the updates of what happens and how the sprint reps react. To w.e damage i decide to throw at it

y0ungcitty said:
Thanks I baught a T5 screw driver that will be here the 10th or the 11th and im excited to crack it open haha. Ill let you know the updates of what happens and how the sprint reps react. To w.e damage i decide to throw at it
Click to expand...
Click to collapse
Came in. and i opened the phone up jiggled the down button got it unstuck and then I was able to re-flash a custom rom so im just going to use this phone untilll it really ****s the bed again.

[JUL2] [Q] Help I accidentally the whole thing...

Well, technically I didn't do anything.
I just bought an HD2 off Craiglist, T8585, previously unlocked, so it would already play nice with my AT&T.
It had some SPB shell on it, so I went in to do a full data wipe and it reboots into something not stock-sense.
I attempted to boot into the bootloader and nothing happens--it just boots normally.
((Vol. down does work normally, mind you--the button is not broken.))
Any ideas as to what might be going on? I'm trying to see if they have the stock bootloader on this still, but the non-stock reset is throwing me off, as is the fact that I can't actually boot into the bootloader.
If I hold down both volumte buttons, I get a tricolor+white screen with an error, "Error: Copying file from SD Card failed, system will shut down."
Pictures attached to show current home-screen and error screen.
Thanks for your help.

Did you try without SD card? If there is something "flashable" on it, maybe your device tries to do something, but reading existing data fails.

My bro if im not wrong this hd2 seems like hd2 clone not original... so be very carefully when you try something with flashing ....

vegaobscura said:
Well, technically I didn't do anything.
I just bought an HD2 off Craiglist, T8585, previously unlocked, so it would already play nice with my AT&T.
It had some SPB shell on it, so I went in to do a full data wipe and it reboots into something not stock-sense.
I attempted to boot into the bootloader and nothing happens--it just boots normally.
((Vol. down does work normally, mind you--the button is not broken.))
Any ideas as to what might be going on? I'm trying to see if they have the stock bootloader on this still, but the non-stock reset is throwing me off, as is the fact that I can't actually boot into the bootloader.
If I hold down both volumte buttons, I get a tricolor+white screen with an error, "Error: Copying file from SD Card failed, system will shut down."
Pictures attached to show current home-screen and error screen.
Thanks for your help.
Click to expand...
Click to collapse
wats d purpose of you wanting to check bootloader ?
I assume all you want back is Sense UI ?

Sense UI would be a start, yes, but I would have liked to flash WP7 and/or Android onto it, too.

Emm, i think that thats not HTC HD 2, thats MKT HD2, a clone looks almost 1:1 compared to htc hd 2.

vegaobscura said:
Sense UI would be a start, yes, but I would have liked to flash WP7 and/or Android onto it, too.
Click to expand...
Click to collapse
Simply go to Start--Settings--
home--Items--Check HTC Sense and uncheck all the rest
that should do...

also if it is an hd2 and you have wm on it there are many endkeys / apps that have a reboot into bootloader.
ex:
http://forum.xda-developers.com/showthread.php?t=786524

vegaobscura said:
Well, technically I didn't do anything.
I just bought an HD2 off Craiglist, T8585, previously unlocked, so it would already play nice with my AT&T.
It had some SPB shell on it, so I went in to do a full data wipe and it reboots into something not stock-sense.
I attempted to boot into the bootloader and nothing happens--it just boots normally.
((Vol. down does work normally, mind you--the button is not broken.))
Any ideas as to what might be going on? I'm trying to see if they have the stock bootloader on this still, but the non-stock reset is throwing me off, as is the fact that I can't actually boot into the bootloader.
If I hold down both volumte buttons, I get a tricolor+white screen with an error, "Error: Copying file from SD Card failed, system will shut down."
Pictures attached to show current home-screen and error screen.
Thanks for your help.
Click to expand...
Click to collapse
from looking at the picture, its hard to tell if it is a clone...if it is not an HTC HD2, but rather a clone, more photos of the device would clarify it. the body is not clearly visible in the two pictures you've attached.
if it is a clone, that would explain the little "surprises" you are encountering here and there

Further investigation yields that the hard-reset ROM does not have Sense stock, so I'm guessing that this is, sadly, a clone.
I had no way to tell at the time, as the previous owner had some shell installed and I couldn't tell from the body alone--it looks like a real one, and it was advertised (and had the box/materials of) a legit HTC phone...
Sucks that I've been scammed and that I'm out the amount I paid. First time I've ever been burned off CL.

vegaobscura said:
Further investigation yields that the hard-reset ROM does not have Sense stock, so I'm guessing that this is, sadly, a clone.
I had no way to tell at the time, as the previous owner had some shell installed and I couldn't tell from the body alone--it looks like a real one, and it was advertised (and had the box/materials of) a legit HTC phone...
Sucks that I've been scammed and that I'm out the amount I paid. First time I've ever been burned off CL.
Click to expand...
Click to collapse
how do you know its a clone ? may be the ROM is a NON-Sense D) ROM !!!

"MTKProfessional" is an appearance type on the phone. This, combined with the quirks and comparing it to a review of the "HD9" leads me to believe it's in fact a clone--and not even the pretty impressive v2 clone.
I'm disappointed, really.

it looks so real !

Holy ****, Vagues.

theres previous news & complain about the HD2 KIRF edition, almost look the same but weight & hardware quality is different.
try to get a refund

Sent an email. No response.
He obviously knew...further investigation yielded an account bearing his name on "asianfoneforums".
I'm disappointed in people right now, man.

vegaobscura said:
Sent an email. No response.
He obviously knew...further investigation yielded an account bearing his name on "asianfoneforums".
I'm disappointed in people right now, man.
Click to expand...
Click to collapse
To be honest, I wouldn´t have noticed that you might have a clone just from the pictures you posted - but another poster discovered that fact.
Now, that´s what I call criminal - no less. A fake with a kind of a "phantasy" name is one thing, but to sell a copied device, which carries the real brand, as a real product, is indeed criminal. In my country, it´s even an official crime.
I´m sorry for you, mate. It´s not nice getting ripped off like this.

I wonder if you can't turn that guy in at the police.
I think you have all the evidence that he know this was a fake.
Also if you look at the loudspeaker grill (where you put your ear at), mine is black and this one looks silver.

seems like a clone to me. the sensors (light and proximity) are larger, and the bootloader screen is a bit different.

Hw do u know if one is a clone?

[Q] new nook touch, stuck after root failed

I hate to have to write this asking for help but I wasn't able to use the other posts I found to help me. The directions for touchnooter seemed straight forward, but I am stuck anyway. Here is what I did and what is happening, and what I have tried to remedy situation. It is a bit long, but I wanted to be as complete as I can.
I have a new nook bought at end of March so assuming it has latest update. I followed directions and was able to get touchnooter onto microsd card. I stuck it in nook and turned on. I got an instruction screen saying to take card out when screen goes black and reboot. My screen did go dim but you could still see the writing behind. I wasn't sure if this what they meant by going black or if I was waiting for complete darkness. I think I panicked for a second (don't know why) and might have rebooted with the card still in (would this have created a problem that I will be describing).
So upon rebooting, it goes through the same reboot nook screen, gets to a screen with an n and the balls and that is the furthest I have gotten it. Messing with the power key seems to initiate a reboot, but it still never makes it past the n screen. Cannot turn off the nook. I was able to get it to give me the factory reset message by doing the failed reboot 8 times. I tried that a couple times but wasn't able to get any further past the screen with the n, so it seems it may not be doing any resetting. I tried repeating the rooting process (except for the shuting down the nook part since I can't actually get it to shut down) and it gave me the same rooting instruction page but no change the problem of not getting past n screen.
I have seen people asking similar questions about rooting with something else called CNW or something because the touchnooter didn't work for them but I didn't understand the instructions and wanted to get help first before trying something else. I had also read that there is something called a factory restore, which is supposed to be different from reset but I don't know how to do that. I downloaded barnes and nobles latest update thinking I would just reload it/ but I can't see my nook from my computer (do I need to download some drivers? Or is this because it can't get past the n screen?). I tried using a different microsd card in case the first was faulty, but didn't help.
Does it seem there is something wrong with the touchnooter content on the card, like maybe it doesn't work with the latest nook update? Also wanted to mention, I did not do a backup before trying to root. I originally planned to but after I was done researching what I needed to do and got to the touchnooter downloading directions, they didn't mention it, so I didn't do it (besides that, I don't know how to do it and don't know if it would help in this situation anyway). Could it be that the nook itself has a problem?
Anyway, I would still like to root but would be happy to at least get a basic nook back. If you have made it this far in reading my problem, what do you think I should try? I am thinking of taking it back since I don't think it actually rooted but if I can fix it, that would be better. Thanks in advance for anyone who takes the time to work on this with me. I wish I had someone right in front of me to ask questions to but this the next best thing.
Thanks!
Tara

I am really leaning towards just seeing if I can return it. The instructions for touchnooter seemed so straight forward and I thought I could handle it. Since it didn't work and I don't even know if it was a problem with something I did, the device, or the touchnooter (since other people with new nooks are having similar problems), then I don't even know if it is something that will work at all. Trying to use some of the other methods are just way beyond my ability without more detailed instructions. Sigh.

http://forum.xda-developers.com/showthread.php?t=1289233
Should help You to restore to factory state. After You can use any other ways to root(if You want )
PS: From what You say, You haven`t done anything irreversible yet. So calm down reread the forum and go on

Thanks for the reply! I did come across that at one point but didn't try it. But I will give it a go once I get the nook charged (it discharges by the end of everyday while having this prob so I have to charge it back up everyday). These directions look pretty straight forward though, so I am crossing my fingers.

"I did not do a backup before trying to root...besides that I don't know how to do it and don't know if it would help in this situation anyway."​
After you get your Nook back to stock state don't shy away from making the backup. And do it before you make any other changes. Having a pristine image of your Nook's original state will make you nearly bulletproof. Give yourself time to understand the issues involved in making the backup. This new knowledge will generalize to other aspects of rooting.
The instructions for making the backup are here but you may find this isn't enough information. I found this post from Renate extremely helpful.
Finally, it will be helpful to know that, done correctly, your Nook v.1.1.2 backup will be exactly 1,958,739,968 bytes.

Efemmeral said:
Finally, it will be helpful to know that, done correctly, your Nook v.1.1.2 backup will be exactly 1,958,739,968 bytes.
Click to expand...
Click to collapse
Depend on nook memory chip used (manufacturing date) it should be either 1,958,739,968 or 1,962,934,272 bytes

ApokrifX said:
Depend on nook memory chip used (manufacturing date) it should be either 1,958,739,968 or 1,962,934,272 bytes
Click to expand...
Click to collapse
Yes? I have always gotten 1,957,616,640.

Hmm, mine is 2.000.683.008.
EDIT: I think that was 1.1.0 (or 1.1.1?)