Database Info

Htc touch diamond need help

Hi Lads,
My HTC touch diamond is doing strange, one day I woke up and suddenly it gave me a Red,Green,Blue,White screen. As I understood it's called bootlloader or something like that.
I tried reset+volumebutton after that it is starting normal and Ive got my phone back, but if I turn my phone back off its gaving me the terrible Red, Green, Blue, White screen back.
Ive tried to do a hard reset ( reset button + volume + round button) but then I have to press the volume button again to accept, but it isnt doing anything then.
Ive looked for some solutions but everything is chinese for me.
I just want my phone back to normal and I hope I dont have to loose all my files.
Can anyone help ?
Thanks anyway lads

Well, if possible, Backup all of your Data using either SPB Backup or Microsoft MyPhone, and reflash a new ROM.
This is what most users will tell you to do.
I think once a device encounters the Bootloader Infinite Loop issue, the only solution is to Flash a New ROM.

and how can I do that ? I am really a dummie at this point.
But it still works only if I put it back on I see the bootloader again.

jonaszw said:
and how can I do that ? I am really a dummie at this point.
But it still works only if I put it back on I see the bootloader again.
Click to expand...
Click to collapse
..better post in the diamond thread. I am sure you will get help!
Maybe HardSLP?

Any update on your progress?
Curious as to whether or not you got the issue fixed.
[If you can get into the Bootloader, you can Re-Flash your device.. just keep it plugged into your computer when you restart your device.]

check my sig for a n00b tutorial

[Q] bricked htc inspire frozen on htc boot up and cant get to fastboot

hello.. i have looked for the answer to my question but i cant seem to find it, therefore i created this post.. sorry if i posted in the wrong section or if it is already out there.. i hope mr clown doesnt close my thread.
i rooted my phone doing it with the one click tool, and it worked perfectly fine.. the problem started when i tried to install a custom rom on it.. i installed rom manager and cwm fine.. but the problem is that i was following this instructions..
http://forum.xda-developers.com/show...php?p=11557769
which i read i had to get this rom...
http://forum.xda-developers.com/showthread.php?t=868720
the problem is that i didnt realize that i needed eng s off and i had s off wich therefore i wasnt able to see the cwm screen..
following the steps that told me to wipe the data with the wipedat.zip.. i did it through rom manager.. when the phone rebooted it went to a dark screen slowly so i took the battery out, and now is frozen in the htc logo... i have tried the up/down/power combo but the phone vibrates 3-4 times and then it goes to a black screen with the light on... but i dont get anything else.. so im really stock at either htc screen or black screen... i need help!!! i hope some one nows a good way for me to fix this.

have you tried...
adb restart fastboot
or adb restart recovery or whichever it is
someone more familiur with adb can explain alil more on this

Download the stock ruu exe and run that from your computer.
Sent from me using this thing.

Try running adb reboot bootloader but first off run adb kill-server then adb devices to see if it is picking up your phone. If that doesnt work download the stock ruu and run it, hopefully all goes well with either method.

Just FYI - this was taken care of over in the General Forum.
Haven't heard from him since, but he was able to get into hboot.
http://forum.xda-developers.com/showthread.php?t=1021246

puneta26 said:
when the phone rebooted it went to a dark screen slowly so i took the battery out, and now is frozen in the htc logo... i have tried the up/down/power combo but the phone vibrates 3-4 times and then it goes to a black screen with the light on... but i dont get anything else.. so im really stock at either htc screen or black screen... i need help!!! i hope some one nows a good way for me to fix this.
Click to expand...
Click to collapse
I had this problem. I just plugged it back into the PC turned off and cwr booted up for me. Hope that helps.
sent from my HTC Inspired Desire HD 4G

Hey man i had a problem like that i used ace hack kit v9...Just do everything over again and it will work..

This is in the wrong section. Questions should be posted in the general section.
Its not volume up/down/power. Its just volume down + power. What is sounds like you did was restart your phone while it was trying to flash the rom. You should be able to get to the hboot menu just by holding power and volume down to power up the phone and wait till hboot shows up.

This will be probably the best answer I got.
1. Turn your phone off
2. Take out the battery and insert it back it
3. Don't turn your phone on
4. Plug in your USB cord,connected to your computer
5. Your phone will Automatically Boot up
6. You will be in the ClockWork Recovery
7. There will be many options
8. Select "BACK UP AND RESTORE"
9. Restore EVERYTHING.
10. youre phone will start normally, but it will be really LAGGY
11. Then ROOT your phone again to make it normal.
What has happened to yours has happened to mine. This is the way I fixed mine.
If you have any problems or issues, PM ME

Moved to proper forum

[Oh Crap] XOOM is dead and it won't boot up!

I don't have a history of random reboots other than the once in a blue reboot because the browser gets stuck. I was using my Xoom last night before going to bed checking out a couple of website. I laid it down and went to bed and this morning I just put it in my bag and left to work.
The Xoom doesn't get past the Motorola logo and then the screen dims a black-blueish tint as if it were on but not on. I booted into recovery and tried to do a nandroid restore to a prior date. The restore finishes but when I reboot the Xoom still has the same issue.
The last thing I downloaded on the Xoom was that new market but I didn't like it so I uninstalled it. Right now the Xoom is plugged in charging. I don't believe it's the screen because I'm able to navigate through recovery without it shutting off. I'm stuck. What could it be?
By the way I pressed Vol Up + Power to force reboot and it's not working. Still a blackish blue tint screen.

Not sure where to put this but I can't post in the development thread. I flashed to 3.2 stock from rooted 3.1 stock and I'm stuck in a bootloop.
Any thoughts?

fleury14 said:
Not sure where to put this but I can't post in the development thread. I flashed to 3.2 stock from rooted 3.1 stock and I'm stuck in a bootloop.
Any thoughts?
Click to expand...
Click to collapse
Not for nothing but you're thread jacking.

Not trying to. Just didn't want to litter with a whole new thread.
Sent from my Nexus S 4G using Tapatalk

It's cool but my Xoom is still dead
I'm going to try and do the update.zip for 3.2 after class and see if it boots up with that. This sucks.
Sent from my PC36100 using XDA App

Update:
I downloaded the 3.2 update that's in the development section and installed it. It still won't boot past the Motorola logo. It goes to the Motorola logo and then the screen turns blackish blue. If I hit the power the screen goes black. It was working g fine yesterday and I'm out of ideas.
Sent from my PC36100 using XDA App

Try going back to the beginning. Flash stock 3.0 and lock. If your xoom boots then you're back in the game. If not, at least its stock to send in for warranty repair.
Sent from my HD2

That will have to wait until tomorrow. What could have caused it?
Sent from my PC36100 using XDA App

Dunno........just blame Motorola......Its fun! Seriously I have no idea, I hope you get it worked out. At least you can get into fastboot & recovery.
Sent from my HD2

jase33 said:
Dunno........just blame Motorola......Its fun! Seriously I have no idea, I hope you get it worked out. At least you can get into fastboot & recovery.
Sent from my HD2
Click to expand...
Click to collapse
I hope it's not an issue with my screen. I just find it weird that the screen shows that weird tint and if I hit the power button it goes black. It's as if the tablet is on but I'm not seeing an image on the screen. When I did a nandroid restore it got past the Motorola logo and went into the next phase (boot animation). It froze on the boot animation within 1 second of entering it. I left it alone for 30 minutes and it didn't do anything.
I don't want to send it back to Moto because G-D only knows when I'll get it back. Does anyone have experience with their repair ETA's? I'm nervous on sending it in because I read a thread where some Xoom owner got accused of having water damage. I don't want to them use that as an excuse so they won't fix it.

I have no personal experience. But there were a couple of posts in the General section (April, May time frame) from users who sent there Xoom to Moto for repair. All reported outstanding service. Call Motorola customer service and they will send you a shipping box overnight. Turn around in most cases was only 2 days. All had their devices back in under a week (departure to return). Good luck. Won't hurt to call Moto and talk to them about it.

Thanks. I'm going to have to return this to stock and relock it again before I can do that. I will call today and have them send me the box. I'm frustrated that I have nothing to play with.

gqstatus0685 said:
Thanks. I'm going to have to return this to stock and relock it again before I can do that. I will call today and have them send me the box. I'm frustrated that I have nothing to play with.
Click to expand...
Click to collapse
You didn't use an app like screen off and lock did you? I had a problem with that app after the update...at one point my screen went completely black, I could see my soft keys and could access settings but that was it. Had to boot to recovery and wipe all over again.
It's a long shot but sometimes apps that behaved before an update can act whacky.

No nothing like that. I remember I was watching some YouTube videos and ended my night. The last thing I downloaded was the new market but it looked hideous so I removed it. I'm trying different things and I can't get it to work.
Sent from my PC36100 using XDA App

I've not got a tablet (hanging out here since I'm considering buying a xoom), but have you tried wiping data, cache, and dalvik in cwm? That, or don't you guys have some sort of computer based flashing program like Samsung's ODIN? Wiping or a fresh reinstall has always fixed that issue on my Vibrant.
Goodluck!
Sent from my GT-I9000 using XDA App

Oxirane said:
I've not got a tablet (hanging out here since I'm considering buying a xoom), but have you tried wiping data, cache, and dalvik in cwm? That, or don't you guys have some sort of computer based flashing program like Samsung's ODIN? Wiping or a fresh reinstall has always fixed that issue on my Vibrant.
Goodluck!
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
No such odin for us...and I don't think an SBF has been released, but we do have stock images from motorola for 3.0 and unofficial 3.1 and they can be flashed quite simply using fastboot. In your case, if you can still get into recovery, I don't believe this is a screen issue. It just sounds like you completely botched your software...not sure how this could have happened...but honestly, if you are curious to see exactly whats going on and you have ddms, just type ddms.bat into CMD while in your platform-tools folder, and then boot up your xoom and read the output. This will tell you exactly whats going on. If it says cannot detect device, it may be an issue with debugging not being activated from your last flash...that being said, I have been stuck at the Moto screen several times and luckily, restoring to stock 3.0 has ALWAYS gotten me out of it, as long as you can get into fastboot, you should be good to go.

Wipe, wipe, repeat!
This most certainly is a software issue. The fact alone that the device is showing the boot logo proves that the screen is functional. Sounds like a boot img problem.
I have had similar issues on a few occasions with my Evo, doing a full wipe and restore has always done the trick as has been posted above.
Good luck Gq.

dhemke17 said:
No such odin for us...and I don't think an SBF has been released, but we do have stock images from motorola for 3.0 and unofficial 3.1 and they can be flashed quite simply using fastboot. In your case, if you can still get into recovery, I don't believe this is a screen issue. It just sounds like you completely botched your software...not sure how this could have happened...but honestly, if you are curious to see exactly whats going on and you have ddms, just type ddms.bat into CMD while in your platform-tools folder, and then boot up your xoom and read the output. This will tell you exactly whats going on. If it says cannot detect device, it may be an issue with debugging not being activated from your last flash...that being said, I have been stuck at the Moto screen several times and luckily, restoring to stock 3.0 has ALWAYS gotten me out of it, as long as you can get into fastboot, you should be good to go.
Click to expand...
Click to collapse
Thanks for the advice. I was too busy yesterday (Full Time Work and Student) to fix it. I will try today since I don't have class. I really want to see what caused the problem so I will try that command in CMD and will post the output on these forums. Hopefully a dev can use it in the future to prevent this from happening to someone else.
I miss my Xoom.
I'm assuming I would CD to the directory and then run that command, correct?

Ok I guys I included the attachment so maybe someone can tell me what's wrong with my Xoom.
When I ran that command in command prompt a debug window popped up. Let me know if the attachment makes sense.
Uncaught Exception most likely has to do with software as I remember fixing Blackberry's that always had those issues but I could be wrong.
Update:
I followed this thread
Re-Lock & Unroot
http://forum.xda-developers.com/showthread.php?t=1084537
and everything successfully pushed. I ended up getting an error messaage in fastboot (Failed image SOS 0x0002) so I decided to unlock the device by running fastboot oem unlock command. It completed successfully and got rid of the error message in fastboot. When I hit reboot it got past the Motorola logo and froze at that honeycomb animation (right in the beginning. I turned it off and turned it on again and now it won't go past the Motorola screen.
I went on a chat with Motorola and they will be sending me an email so I can send my Xoom for repair. I'm going to lock it again and send it back. I'm giving up unless anyone recommeds something I can try.

Phone appears dead after failed flash.

So I was running CM10 Alpha 4.4 and phone was running pretty well for the 24 Hours I had it installed, but unfortunately I couldnt do any nandroid backups or restores. Would always reboot near the end. Well I was told that I could flash the boot.img file from the alpha 4.3 version and that should solve the issue until the newer version is fixed. Anyway, i installed Heimdall on my mac, started it as root. Created the pic, then went to flash the new boot.img. The first come times i got handshake failures, but then i restarted the phone into download mode again for the second time and it finally started to move forward. I then got the following response:
ERROR: Failed to confirm end of file transfer sequence!
GANG upload failed!
Ending session...
ERROR: Failed to send end session packet!
Click to expand...
Click to collapse
So it appeared that Heidmall had given up basically gave me the option to try again (aka, the start button was available again). The phone was still in download mode and appeared like it was still trying to do a download, so i left it be for about 10 minutes and still no change and heimdall wasnt doing anythign with it anymore. So i turned off the phone and tried to turn it back on to get it back into download mode again so i could try again. Unfortunately now the phone wont even turn on. I mean no responses at all that its getting an type of power or anything (aka, no lights). I took the battery out for 10 mins and then put it back in and still no luck. Its back on the charger, but I am worried that its dead. What sucks is that i just got this replacement phone in June after someone physically broke my old E4GT. =/
Any suggestions?

MACscr said:
So I was running CM10 Alpha 4.4 and phone was running pretty well for the 24 Hours I had it installed, but unfortunately I couldnt do any nandroid backups or restores. Would always reboot near the end. Well I was told that I could flash the boot.img file from the alpha 4.3 version and that should solve the issue until the newer version is fixed. Anyway, i installed Heimdall on my mac, started it as root. Created the pic, then went to flash the new boot.img. The first come times i got handshake failures, but then i restarted the phone into download mode again for the second time and it finally started to move forward. I then got the following response:
So it appeared that Heidmall had given up basically gave me the option to try again (aka, the start button was available again). The phone was still in download mode and appeared like it was still trying to do a download, so i left it be for about 10 minutes and still no change and heimdall wasnt doing anythign with it anymore. So i turned off the phone and tried to turn it back on to get it back into download mode again so i could try again. Unfortunately now the phone wont even turn on. I mean no responses at all that its getting an type of power or anything (aka, no lights). I took the battery out for 10 mins and then put it back in and still no luck. Its back on the charger, but I am worried that its dead. What sucks is that i just got this replacement phone in June after someone physically broke my old E4GT. =/
Any suggestions?
Click to expand...
Click to collapse
If you cant get into download mode with the key combo ( VOL- / POWER / HOME) then a Jig may be your only hope beside JTAG.

Since it sounds like its hard bricked, a JIG probably wouldnt work, right? I just dont want to waste time/money trying to get it fixed with that method if i should be going straight to a service provider that can do JTAG.

hi mate just an option
it sounds bricked if you hold down the volume up button the bottom button and the power button fallow the same steps in there to install a rom just dont use any zips just rebootyou can use CWM to do a recovery from a back up if not as a last resort reinstall the rom you are using what rom is it that you use im trying to find a good one but you could try to do the update again or use a pc try back up the files you would need then reinstall but hope i helpped please click the tanks button if you feel i helped.

99ryan993 said:
you can use CWM to do a recovery from a back up if not as a last resort reinstall the rom you are using what rom is it that you use im trying to find a good one but you could try to do the update again or use a pc try back up the files you would need then reinstall but hope i helpped please click the tanks button if you feel i helped.
Click to expand...
Click to collapse
lol, you didnt help at all. You obviously didnt read my problem.

MACscr said:
Since it sounds like its hard bricked, a JIG probably wouldnt work, right? I just dont want to waste time/money trying to get it fixed with that method if i should be going straight to a service provider that can do JTAG.
Click to expand...
Click to collapse
Im not exactly sure if a jig will help you. There cheap to buy or make. I think its a long shot but who knows. How long have you had the phone and where did you buy it from? JTAG is $50 i believe. You could always try taking it to a verizon store.

Just got pointed out to me that I accidentally posted in the s3 forum when i have a e4gt. The local sprint store is replacing my phone though for only $35. Though their manager showed me her s3 and its pretty freakin sweet. With trade in and upgrade, I could get the s3 for about $140 after fees. Not sure if I am going to do it.

MACscr said:
Just got pointed out to me that I accidentally posted in the s3 forum when i have a e4gt. The local sprint store is replacing my phone though for only $35. Though their manager showed me her s3 and its pretty freakin sweet. With trade in and upgrade, I could get the s3 for about $140 after fees. Not sure if I am going to do it.
Click to expand...
Click to collapse
Nevermind, I am getting the s3 on Saturday when I am eligible and just selling the epic 4g touch on ebay.

lay off them bath salts and you would be suprised how much easier it is to navigate xda and post in the correct forum lol.

[Q] Nexus S - can't mount anything! - stuck on Google Logo

Hello!
Okay, so the weirdest thing has happened with me. My Nexus S (i9023) was working absolutely fine till last evening when it ran out of battery. After I came back home, I put it for charging and switched it on.
For the first few time, nothing would show except the USB connected/ disconnected screen which appears everytime you plug your phone in. I thought maybe it was just being weird, so I took out the battery and booted it up again. This time I am just stuck at the Google Logo! It is not going ahead.
I can enter CWM Recovery. However, I cannot mount sd card or usb storage or anything for that matter. If I try and install through .zip it says 'e can't mount sd card'. I can't format my sd card either, same problem of can't mount. I thought if I tried pushing a ROM in by ADB that might work.. It did transfer the file it showed that in the cmd window. However, CWM refuses to mount my sd card or my usb storage.
So basically, in essence, I'm locked out of my Nexus! Please please help. I'm really lost and confused now.
Thanks so much.
Alex

Similar problems below in this thread with solutions.
Let your phone sit for an hour with the battery out, Download Wug's Nexus Toolkit from the development section, download drivers from there and install stock boot img then re-root.
I have never seen it before but seems like this prob is coming up a lot lately. It can be fixed. Good luck.
Sent from my Galaxy Nexus using Tapatalk 2

Nexism said:
Similar problems below in this thread with solutions.
Let your phone sit for an hour with the battery out, Download Wug's Nexus Toolkit from the development section, download drivers from there and install stock boot img then re-root.
I have never seen it before but seems like this prob is coming up a lot lately. It can be fixed. Good luck.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks for your reply. I'm starting now. I have a doubt, how do I install stock? Since I can't seem to be able to mount anything..
"It can be fixed" - few words have given me this much hope in my life! Thanks a lot!
EDIT: I guess you mean flash through ADB right? Okay, let me try that. I really hope you are right. Some of those other problems lead to paying up! Ouch.

Hey! I just tried using WUGS.. for some reason it does not make the final boot and instead says: 'Fastboot Status - FAILWrite Fail' -- oh god.. I'm trying it again now..
Is there any other way out? :/

Okay, so now my recovery is also gone after using WUGS.. oh man. And the phone isn't starting up. Please please please help? I'm getting really desperate now.
EDIT: And it sucks that I can't post in the WUGS thread (http://forum.xda-developers.com/showthread.php?t=1766475) because I have less than 10 posts! fml.

can you boot into fastboot? If so then itnwasnthe same prob I had when I wiped my phone and SD in recovery. If you can boot into fastbootnthen makensurenyou leave the batt out format least an hour. If you installed Wug's drivers the bottom left corner ofnfastboot should give a message.
Sent from my Galaxy Nexus using Tapatalk 2

Nexism said:
can you boot into fastboot? If so then itnwasnthe same prob I had when I wiped my phone and SD in recovery. If you can boot into fastbootnthen makensurenyou leave the batt out format least an hour. If you installed Wug's drivers the bottom left corner ofnfastboot should give a message.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yes, I can get into fastboot - i'm leaving the battery out now - do you think i should try
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
and then flash everything again?
There is always a way to recover the nexus right? Even if it is hardbricked, right?
I really really appreciate your help.

I too have this problem but after a lot of battery pulls it does eventually start up. It just started happening all of a sudden. Ive heard that heating it up with a hair dryer or heatgun can help and also re-locking and un-locking the boot loader can help as it wipes the card. Could be worth a try.

Any luck Someone? I know it sux big time to feel like your phone is bricked. I am not a dev or expert but it sounds like the prob I had last week, when I posted no one replied so I ordered a GNex thinking all was lost. Before I activated my new phone I felt like I had to fix my nexus before getting started on my new phone and that's my situation. I don't want you to feel like the community has forgot you and thats why I'm trying to help. Were you able to get Wug's Toolkit to recognize your phone after leaving the batt out? I don't know why but I think that's the key. I had to leave mine overnight 'cause I don't have a PC and the next day at my friends house when I plugged the USB in I got that message at the bottom of fast boot "system normal" or something to that effect. Once recognized the stock boot IMG is what you need.
ANY ONE ELSE WHO HAS HAD THIS OR A SIMILAR ISSUE PLEASE GIVE SOME ADVICE. LET'S NOT LEAVE A COMMUNITY MEMBER WITH A LIFELESS PIECE IF PLASTIC. THANKS FORUM.
To set your mind at ease yes, I believe as long ad you have access to fastboot your nexus can be saved.
Sent from my Galaxy Nexus using Tapatalk 2

sounds to me like a hardware issue, since you haven't changed software and it seems like a brick. try flashing stock rom via fastboot, you should be able to google around how you can do that.

Blo0dyyy said:
sounds to me like a hardware issue, since you haven't changed software and it seems like a brick. try flashing stock rom via fastboot, you should be able to google around how you can do that.
Click to expand...
Click to collapse
Hi, if I'm not wrong essentially what WUG does automatically is what you do by fastboot (erase bootloader, cache, system.. and then flash all of them back) in both system fails to wipe and refuses to be flashed again (flashwrite error).
I don't want to lock it and then unlock it again because I read in other threads that it might lead to a permanent lock with an error for subsequent unlocking - that would leave me completely out.
Anyway, let's see - I've given it to someone to check it up. I'll keep you guys posted. He said he wanted to repartition the sd card.
My intuition says: hardware problem!

So I tried Odin today - and that also did not work it refused to flash the ROM. In the process I somehow managed to mess up the bootloader such that the phone would have some two lights on randomly when I switch on. It doesn't go into download mode either. I next plan to use JTAG to get the bootloader back and then reflash everything. Hopefully, that should sort things out. The Resurrection tool is amazing! I'll keep you guys posted.

Get it going someone?
Sent from my Galaxy Nexus using Tapatalk 2

I have the same problem as you, with the added difficulty of my phone not being recognized by anything other than fastboot. No ADB commands will function. It was charging, rebooted itself into a bootloop, and I have been struggling with it ever since. It is currently a worthless piece of plastic, my favorite phone ever, gone.
I can wipe and re-write recovery all that I want, but it seems as if the sdcard partition that /system and some other stuff writes too is either corrupted or physically damaged. Every time I flash it all via fastboot it all goes as stated, but gives me a fail message on the last two partitions and never allows me to actually write a new ROM or boot image. I wanted to try ODIN but can't seem to get it to recognize my phone in download mode...
Let me know if you have any success or progress!

someone. said:
So I tried Odin today - and that also did not work it refused to flash the ROM. In the process I somehow managed to mess up the bootloader such that the phone would have some two lights on randomly when I switch on. It doesn't go into download mode either. I next plan to use JTAG to get the bootloader back and then reflash everything. Hopefully, that should sort things out. The Resurrection tool is amazing! I'll keep you guys posted.
Click to expand...
Click to collapse
I myself am experiencing the same problem.... Did your cell got fixed.....?? Did JTAG worked kindly keep us posted em really concerned about it... coz your solution might get me some where or else i hav completely lost my phone ;(

Get it going someone?
Click to expand...
Click to collapse
Hey Nexism! Sorry for the late reply - things've been busy.
The JTAG is giving an internal voltage for some reason - so I've sent it for repair. It'll be repaired by tomorrow or so.. I'm then going to set it back up. It's all already soldered and all, just waiting for the JTAG. I think I've understood how this thing works now. So yeah, I'm hoping it's all sorted. Thanks a lot for your concern man.
I have the same problem as you, with the added difficulty of my phone not being recognized by anything other than fastboot.
Click to expand...
Click to collapse
Well my phone went blank - no fastboot mode - no download mode - no nothing - when i'd put the battery in randomly two of the four front lights would come on.. JTAG is going to solve the problem hopefully.

someone. said:
Hey Nexism! Sorry for the late reply - things've been busy.
The JTAG is giving an internal voltage for some reason - so I've sent it for repair. It'll be repaired by tomorrow or so.. I'm then going to set it back up. It's all already soldered and all, just waiting for the JTAG. I think I've understood how this thing works now. So yeah, I'm hoping it's all sorted. Thanks a lot for your concern man.
Well my phone went blank - no fastboot mode - no download mode - no nothing - when i'd put the battery in randomly two of the four front lights would come on.. JTAG is going to solve the problem hopefully.
Click to expand...
Click to collapse
So ladies and gentleman, JTAG also failed - apparently something was wrong with the sd card only. I got my motherboard replaced - luckily the guy I went to knew someone and Samsung and charged me Rs. 4,000 as opposed to the Rs. 8500 quoted by the Samsung Service Centre. Oh well.
Back on my Nexus now. XD

someone. said:
So ladies and gentleman, JTAG also failed - apparently something was wrong with the sd card only. I got my motherboard replaced - luckily the guy I went to knew someone and Samsung and charged me Rs. 4,000 as opposed to the Rs. 8500 quoted by the Samsung Service Centre. Oh well.
Back on my Nexus now. XD
Click to expand...
Click to collapse
I am with the same problem here... I cant turn off my phone or it get stuck in pre-boot phase. Acess recovery and cant mout sd card. Using last stable cm 10.
I think my sdcar is dead.

Same problem here. Around 8 out of 10 times I get stuck on the Google logo, 8 out of 10 times in recovery I can't mount SD card as well. And if I successfully boot, Media wakelocks and my battery drains in sleep as fast as if the screen were on. Please help.

For me I first noticed that my apps weren't using the SD partition. Tried to mount normally (fully loaded ROM) (ROM is SlimBean Beta2), but it would not mount. Went into CWM and tried to mount in there, but it would not work. tried to "Format /sdcard" but "Error mounting /sdcard". My phone still boots and runs fine, but I just don't have access to the SD partition. I don't want to do anything because I need my phone for business. Is there any PROVEN way to fix this yet?