Soo I had a problem with my phone's charging where I would pull the plug to stop charging the phone, and the batteey would still indicate that it was charging. Also, randomly, my phone would think its connected to the computer and the "USB" notification would pop up and leave every 2 seconds over and over "again (that stopped eventually). Also, when i try to connect my SD card to my computer, it wont connect (even if the phones "USB" notification popped up). I used to use many different chargers to charge my phone and then stopped because I thought that was the problem. Now, my phone still acta a little weird when I charge it, USB is gone, abd I can't recover into CWM recovery. I have the full version of ROM manager, tried going into recovery that way, but when in normal recovery, it just keeps resetting onto that stock recoveey system. This problem started when I had DL30, now I'm using EB01. I wiped data and chache and its still giving me problems...oh and I forgot to mention, if my phone shuts off, I have to connect it to a charger to turn it back on...even if it has good battery. What can I do???
Sent from my SCH-I500 using XDA App
My friend is having this prob.. The 3 button recovery method still works for him.. I still have not fixed his phone.. But all I have tried so far is a franken kernel flash because he has an extended battery.. I will try more next week
Rocking dj05 and jt's voodoo 5
Are you using a different charger than the stock Samsung one? It sounds like your USB port is screwed over.
KitsuneKnight said:
Are you using a different charger than the stock Samsung one? It sounds like your USB port is screwed over.
Click to expand...
Click to collapse
ahhhhhhyep. Sure that is part of it, but the constant flux and what not I'm sure has messed with the phone. Try an odin back to Di01 or dl09 and see if it fixes things.
I had the same exact problem, odin'd back to stock, didnt fix it at all. Had to return the phone. Guy at best buy said he had seen a few others with the same problem. Must be common for the USB port to take a ****?
mikey6p said:
I had the same exact problem, odin'd back to stock, didnt fix it at all. Had to return the phone. Guy at best buy said he had seen a few others with the same problem. Must be common for the USB port to take a ****?
Click to expand...
Click to collapse
It's when incorrect chargers are used. Whether it be voltage or pin arrangement, it's not as uncommon as you think.
No its not uncommon at all...there are many different grades of chargers
Rom manager throws up a red flag for me to begin with. If your CWM is jacked up you should replace it with an odin flash. I've seen a lot of people having trouble with CWM from rom manager lately.
I agree with the probability of the USB port being messed up, but i'd make sure your software is square first.
As far as the usb issues, have you tried using a different usb cable? If you have, and you are still having issues, then I'm guessing your usb port has a short in it and will need to be repaired.
About your CWM problems, if you flash with something like SuperClean v2.4, you will have your kernel, CWM, and rom all replaced at the same time. This way, if you can get into CWM once, then you won't have issues getting back into recovery again, because CWM will be permanently installed.
Don't use the ROM manager's recovery unless you manually the swap the recovery-update.zip file on your SD card:
Daswolven said:
Take the fixed CWM update.zip from the above post. Drop a copy on your sd card. Copy it into the clockworkmod folder and rename the copy recovery-update.zip. Will work on both ends then.
Click to expand...
Click to collapse
Related
If You try to partition with Rom manager it partitions the internal sd and you will brick your phone. Your screen will be black with only the capacative buttons glowing. This brick is possibly the more annoying ones where you have to flash your phone twice. If you have this problem don't panic like i did.
*REMOVING EXTERNAL SD CARD MIGHT IMPROVE ODIN CHANCES OF WORKING*(Thanks Hoey2011 for mentioning this)
Step 1: Download all files from this thread
http://forum.xda-developers.com/showthread.php?t=734475
PUt them in a safe spot you will need them for later.
Step 2: Download files from this thread
http://forum.xda-developers.com/showthread.php?t=740558
Step 3: HAVE ODIN OPENED FIRST!!(This helped it detect my phone for some reason)Get phone into download mode. The easiest way to do this is pull out battery from phone. Then plug phone into usb connected to computer it will have the battery sign. Hold volume keys and power button when the screen goes black let go of power button. You will be in download mode if Odin doesn't detect it unplug usb and replug it.
Step 4: Once Odin has recognized your phone set the pit file and .tar file FROM EUGENE'S 2.2 THREAD. NOT THE FIRST LINK THE SECOND LINK. Then click start. And follow all the directions on his thread.
Step 5: Once you have flashed that rom you put your phone in download mode again and set up the pit and .tar file for Stock 2.1. After you finish flashing it your phone should be saved!
Thanks to Eugene373, justanothercrowd and anomalous3(for being patient and helping me out when I had this problem) And to anyone else that helped me solve this problem.
Thanx for being the guinea pig. Glad you got it back working.
Yea It was a ***** tho. Spent at least 4 hrs fixing it. But glad its working
Wow that sucks well thanks for the write up.
I was in the same boat as you and as I was downloading 2.2 to try I found your thread. Works like a charm! Thanks for the info on this. I guess I shouldn't read threads backwards from now on, huh?
ok so I've been following this method, and got eugene's 2.2 loaded up correctly, and rebooted back into download mode. The 2.2 files loaded just fine through odin, but now that I'm flashing 2.1, it seems hung on the cache.rfs.
I am gonna go smoke a blunt or two and come back and see how it's progressed, but this hang is the same issue I had before, on my windows 7 64bit machine. I figured it was a compatibility problem so I'm using my old busted vista machine. I've gotten further on the vista laptop than the W7 one, but I'm still hung.
How long should the 2nd loadup take??
I am almost at my wits end with this stupid mistake I made and hope is such a far stretch
ok, so i continued my use of the search tool here at xda and found my answer
I had my MicroSD card in my phone, hadn't even thought to remove it. I have moved past the cache.rfs file and am now waiting to see the results....
IT WORKED OMG OMG OMG
Xda forums almost ruined my phone, then brought it back from the dead
god i love equlibrium
Good info thanks for posting it, but one thing I would like to point out and I am not alone in feeling this way people are throwing the.word brick around and far to casually. You did not brick your phone by partitioning it the proof is that you fixed your phone. Bricking a phone is wheb youbrender the phone usless as a brick when it is totally broken and unfixable. I dont mean to nitpick i just hate seeing everyone that makes a mistake in anything crying wolf and claiming to have bricked. But my rant aside thanks for the very usefull info you mightvwanna pass it on to koush so he can fix it.
Sent from my SGH-T959 using XDA App
I did exactly this and I was so frustrated that I sent my phone back to tmobile and just purchased a new one. I don't know about yall but if there are two storage points (internal and external) there should be an option for both in default recovery because when I tried to partition the external sd card *in which i was able to execute on my nexus one* it was very easy but because I use clockwork recovery and did a rom backup, i guess the backup zip wasn't safe because I received the same results as you. There should be 2 options to choose from that says *internal storage, External SD Card* why make things difficult? lol
The manufacturers need to be a little more intuitive.
*this is my opinion*
zDisturbed1 said:
Good info thanks for posting it, but one thing I would like to point out and I am not alone in feeling this way people are throwing the.word brick around and far to casually. You did not brick your phone by partitioning it the proof is that you fixed your phone. Bricking a phone is wheb youbrender the phone usless as a brick when it is totally broken and unfixable. I dont mean to nitpick i just hate seeing everyone that makes a mistake in anything crying wolf and claiming to have bricked. But my rant aside thanks for the very usefull info you mightvwanna pass it on to koush so he can fix it.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Thanks for the clarification. I actually had no idea a brick was unfixable. I thought a brick was when your phone messed up and you'd reflash to get it working. Lol sorry again
Sent from my SGH-T959 using XDA App
Ah crap, that's right, /sdcard is mapped to the *internal* sd card on the phone, and that's what is partitioned. I'll disable partitioning on the phone (external SD card is not accessible in recovery).
Koush said:
Ah crap, that's right, /sdcard is mapped to the *internal* sd card on the phone, and that's what is partitioned. I'll disable partitioning on the phone (external SD card is not accessible in recovery).
Click to expand...
Click to collapse
I haven't tried partitioning, but the card's /dev/block/mmcblk1p* entries are there and I can mount them. That's how the dc2ext hack works. It mounts /sd-ext and /data to do the copies and it does it in recovery.
hoey2011 said:
ok so I've been following this method, and got eugene's 2.2 loaded up correctly, and rebooted back into download mode. The 2.2 files loaded just fine through odin, but now that I'm flashing 2.1, it seems hung on the cache.rfs.
I am gonna go smoke a blunt or two and come back and see how it's progressed, but this hang is the same issue I had before, on my windows 7 64bit machine. I figured it was a compatibility problem so I'm using my old busted vista machine. I've gotten further on the vista laptop than the W7 one, but I'm still hung.
How long should the 2nd loadup take??
I am almost at my wits end with this stupid mistake I made and hope is such a far stretch
Click to expand...
Click to collapse
I have had serious issues with Odin hanging on my WIn 7 32bit system. However, I think I was actually doing it wrong. I was booting my phone to download mode then plugging it in to my computer. However, I have had continued success (tried a bunch last night) by doing this:
Open Odin, take out the battery, plug in USB cord to phone and computer, hold vol up+down, put in battery. Whenever I booted into Download Mode this way, Odin worked perfect every time. Turns out after cursing my computer it was user error, whoops .
brandnewsimmy said:
I have had serious issues with Odin hanging on my WIn 7 32bit system. However, I think I was actually doing it wrong. I was booting my phone to download mode then plugging it in to my computer. However, I have had continued success (tried a bunch last night) by doing this:
Open Odin, take out the battery, plug in USB cord to phone and computer, hold vol up+down, put in battery. Whenever I booted into Download Mode this way, Odin worked perfect every time. Turns out after cursing my computer it was user error, whoops .
Click to expand...
Click to collapse
turns out, the system wasn't the finicky piece of equipment, it was the phone and the odin software. I inadvertently left the sd card in the phone, the external one, and that was causing my hangs. Two more tries after pulling the sd card, I had success and was back to my phone again
hoey2011 said:
turns out, the system wasn't the finicky piece of equipment, it was the phone and the odin software. I inadvertently left the sd card in the phone, the external one, and that was causing my hangs. Two more tries after pulling the sd card, I had success and was back to my phone again
Click to expand...
Click to collapse
I forgot to mention to do that. I did that with mine as well. Taking out the sd card increases success. Thanks for mentioning it.
Sent from my SGH-T959 using XDA App
farrisizdaman said:
Thanks for the clarification. I actually had no idea a brick was unfixable. I thought a brick was when your phone messed up and you'd reflash to get it working. Lol sorry again
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
YEa I guessed as much thats why I was trying not to "flame" and to be informative you are a victim of exactly what I am talking about. Because so many people throw around the word brick anytime anything goes wrong not only is it losing its meaning but people are also getting confused.
This does work, it took me about 7 hours last night to fix it.
I will say if it does not work then keep trying.
My flash kept freezing on the froyo rom and would not finish, so I actually had to try and flash the full captivate stock rom (search the captivate forum) it froze but afterwords it let me go throught the whole flash process with Eugenes 2.2 rom, then flashed right back to 2.1 no prob.
I will also say that if you are on a x64 system then go find a x86 (32 bit) system. I dont know why but it just works better.
So if it doesnt work then do this:
1. Make sure you are on a 32 bit system.
2. Flash a Full Rom from the Captivate forum. (It has a more to it I believe, changes the system maybe?)
3. If it freezes that is ok. Flash the 2.2 rom. (might need to do it a couple times)
4. After successful flash then go to stock.
This needs a sticky!!!!!!!!!
I just did this. Wish I would have seen this thread first!
I'm having a really hard time getting to download mode. Read all the threads I could find on it.
Any ideas? Download mode isn't removed when partitioning with rom manager is it?
I'm trying not to freak out...
tsnow247 said:
I'm having a really hard time getting to download mode. Read all the threads I could find on it.
Any ideas? Download mode isn't removed when partitioning with rom manager is it?
I'm trying not to freak out...
Click to expand...
Click to collapse
After fighting with it I found out this worked best for me:
Battery out
Plug in USB cord to the phone and PC
Hold Vol up and down
Put the battery in
Phone should boot right into download mode.
Also, I found you should have Odin open FIRST before you do this. If I didn't I would have constant issues with Odin hanging.
greetings...i've read far too many threads on not being able to boot into "recovery" and "download" and haven't found anything to fix me...
i can successfully get into "recovery" but when i try to reinstall the packages it starts to run a recovery with Clockworkmod etc...it stops and reboots into recovery...this will go on and on...
now when i try to boot into "download" i can't, i've tried many methods none work.
any help?
rooted/clockwork recovery/nandroid back up prior to trying the vibrant7
same problem here...
http://forum.xda-developers.com/showthread.php?p=7904808#post7904808
The K-Zoo Kid said:
same problem here...
http://forum.xda-developers.com/showthread.php?p=7904808#post7904808
Click to expand...
Click to collapse
sweet...well, not sweet...PM me if you find a fix: i'll do the same, i have a replacement on the way via t-mobile.
for the record, i've successfully gotten in to download mode and used Odin to get back to factory...twice, once for fun and once for resurrection...i don't know what went wrong, except while nandroiding maybe i backed up a bogus recovery rom before i flashed. i can't get past Vibrant, and i don't even see the battery recharge display either when i usb, i'm letting the battery run down to try and get to the green battery icon to try a "download" mode??? i've read of a move while you see the charging screen but i haven't been able to get there... oh well, live and learn. i am also searching for a way to boot from the removable sd card that has a system or recovery rom on it..nothing yet.
also, i've read people discussing newer models being blocked from download...well like i said i've done this with this phone before but i got a new SIM last week and this is the first attempt with the new SIM???? maybe a coincidence...
take battery out, plug in usb to pc, hold vol up n down, replace battery, boom download mode.
dsuycott said:
sweet...well, not sweet...PM me if you find a fix: i'll do the same, i have a replacement on the way via t-mobile.
for the record, i've successfully gotten in to download mode and used Odin to get back to factory...twice, once for fun and once for resurrection...i don't know what went wrong, except while nandroiding maybe i backed up a bogus recovery rom before i flashed. i can't get past Vibrant, and i don't even see the battery recharge display either when i usb, i'm letting the battery run down to try and get to the green battery icon to try a "download" mode??? i've read of a move while you see the charging screen but i haven't been able to get there... oh well, live and learn. i am also searching for a way to boot from the removable sd card that has a system or recovery rom on it..nothing yet.
also, i've read people discussing newer models being blocked from download...well like i said i've done this with this phone before but i got a new SIM last week and this is the first attempt with the new SIM???? maybe a coincidence...
Click to expand...
Click to collapse
Alright i will doo... and you restored from odin after the problem started...?
I flashed the stock kernel and everything is good... Its in the OP of Eugenes rom.
98classic said:
take battery out, plug in usb to pc, hold vol up n down, replace battery, boom download mode.
Click to expand...
Click to collapse
thanks for the reply...i've done that a bazillion times...won't go, i even went to the tmobile store in my hood and no go on their end...
The K-Zoo Kid said:
Alright i will doo... and you restored from odin after the problem started...?
Click to expand...
Click to collapse
not after, i had restored from odin about two weeks ago...
Did you read my post about The stock kernal in eugenes original post?
Sent from my SGH-T959 using XDA App
The K-Zoo Kid said:
Did you read my post about The stock kernal in eugenes original post?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
yes(but i'm over saturated right now, i might have missed something) ...i'm dead in the water, i can't get to the point of anything seeing my device...my computer won't see it except as unknown usb device, no partitions show up, adb doesn't recognize it in any way...maybe i'm a [email protected], but i don't see anyway to flash it without at least getting in to download mode, or somehow pushing a .zip at the sd for a recovery??? technically figuring out that stuff is beyond my remaining brain cells...this seems like a dicey way for the phone to rely on when restoring to factory.... it would be nice to have the device look at All available partitions, internal/removable, for a recovery system or have an altogether different sd in the phone for a -R dedicated recovery volume....don't know, i'm a noob at this android stuff sooo....
Hey guys, I just made the move from Blackberry to the Fascinate from Verizon, it is stock with the DI01. I am familiar with rooting using ADB etc and I have been doing it for a few friends. My issue is when I plug the Fascinate via usb I get a CD-Drive icon with a few software like Samsung_Mobile_USB_Driver and TooLauncher_Bootstrap and when I mount SD I get the same CD-Drive icon with error message windows can't access this disc. Also ADB shell also reports Device not found with USB Debugging and Allow mock locations enable.
The SD settings is set to Mass storage and I have the Samsung driver installed.
Can anybody point me how to get the SD mounted as a storage disk so I can have access to it?
Thanks allot guys
Can you post what OS you are using for clarification?
The issue I had with this was I didn't realize I had to authorize the mount from the pulldown up top when I plugged it in. You probably did that, but just in case.
Swyped w/ XDA App. When in doubt, mumble.
Im on Win 7 x64 with Samsung USB x64 driver install.
The funny thing I had another Fascinate in just last week and I was able to connect and mount the SD card as a disk drive just fine.
Any tought?
Try restarting your phone with the USB cable plugged into your computer and usb debugging turned on.
Here are some posts by people with the same issue:
rmtobler said:
Well I finally got the computer to recognize the sdcard, but I had to flash the d101 odin files a bunch of times and start over. But after awhile on DJ05 the same problem happens again. I tried to check to make sure the sd was recognized after each step I took, but it seemed it seemed to have stop working overnight and now is just not recognized at all or as my cd-rom (drivers show 'samsung cd-rom usb device', though the sdcard is still working on the phone
Click to expand...
Click to collapse
rmtobler said:
I got mine to work again. Although I'm not exactly sure why it worked. But I un-installed and re-installed the samsung usb drivers and then later when I restarted my phone with the usb plugged in (and usb debug on) the computer started loading up the drivers correctly while the phone booted and it has worked since then.
Click to expand...
Click to collapse
nike984 said:
This worked for me too.
Basically you have to restarted the phone with the usb plugged in.
After than that the problems was gone.
Thanks rmtobler!
Click to expand...
Click to collapse
cseeley said:
I am not totaly sure that the connection issue is related to DJ05, or full DIO1 package. After running into the problems with the debug connection, I was not able to root because of the connection issue.
Luckily, I saved off a rom manager backup od my DJ05 after rooting it the first go around, as it seems as though something of DJ05 stays around, and breaks all my DI01 roms.
What I ended up doing, to get back up and running is as follows;
I formatted the SD card just in case that had a problem. Put my rom manager backups back on their, and then I flashed back the DI01 package to get me back to the factory radio. Then I flashed clockwork, I then copied update.zip from the clockwork thread to the root of the sd card, and booted into recovery. Next I restored my DJ05 backup that already had root, and then back into recovery and flashed the DJ05 radio, and Kernel.
I am now back up and running. Not sure on the debug connection, I will have to some things.
Thanks,
Chris
Click to expand...
Click to collapse
rmtobler said:
Try restarting your phone with the USB cable plugged into your computer and usb debugging turned on.
Click to expand...
Click to collapse
Don't know if anybody ever told you this!
You're the man, it works, I have access the SD card via USB.
Thanks ALLOT bro.
none of the above methods work for me. All trouble began when i installed DJ05. I used the **87284 through dialer to confirm its on USB mode. Now i don't have debugging and sdcard mount failure.
Under windows 7 x64 device manager other devices got loads of question marks on Data Interface.
I was looking at other post for EVO4G
http://forum.xda-developers.com/showthread.php?t=695243
The fastboot option is only available on HTC models i guess.
I was wondering about a fix for fascinate through Odin.
I would just suggest trying the different odin files for dj01 modem, system, recovery until you get a combination that gets the usb working again. The first time I used odin it worked great, then the second time it didn't work and I just kept doing it until it did. Then once I went to dj05 and flashed anything using clockwork the USB would go back to not being recognized but a restart w/ the phone plugged in fixes it.
Downloaded latest files & instructions from irc samsung-fascinate channel. it used to mount as CDROM earlier. That is gone now. Still shows question marks under Data Interface win7 x64. Tried various combinations. Went back to stock now.
However the baseband modem is DI01 and build number is DH12. Similar issue reported by http://forum.xda-developers.com/showthread.php?t=854704.
In search of DH12 baseband modem now. Hoping this will fix the issue i'm having. I've got a nandroid backup but that does not restore the baseband modem to DH12.
I rooted my phone earlier today. Was looking into flashing a new rom.
Went with a dj05 rom, downloaded it, and the radio. All flashed fine. Went to reboot after and do the kernal and now it wont boot into recovery. (has a screen that comes up with a cell phone and computer with a triangle in between.
It will boot into download mode, but odin isn't recognizing my phone as being plugged in.
It was the superclean dj05 rom i flashed. any help would be greatly appreciated...
Are you sure that you have the correct phone drivers installed? Odin has never been the most well-written and bug free of programs, but it has been invaluable all things considered. Have you been able to use Odin in the past?
If you are absolutely sure it doesn't work, I suggest downloading and figuring out to use Heimdall, as it will use completely new USB drivers and do pretty much the same thing as Odin.
I also helped someone who had Odin not recognize the phone and nothing I suggested would help him. Eventually someone came up with the idea of buying a USB controller PCI card, and miraculously that worked. It shouldn't have to be that way, but sometimes computers like to fart in your face like that
Also, make sure you have the battery out when plugging in and going into download mode. Odin doesn't like batteries.
I've seen many people on this forum have luck with trying different USB ports on their PCs when this happens. For some reason ODIN is finicky with some USB ports, even when those same ports work fine for mounting the SD card and other things.
Kevin Gossett said:
Also, make sure you have the battery out when plugging in and going into download mode. Odin doesn't like batteries.
Click to expand...
Click to collapse
Have you had a bad experience? I am the type of person that doesn't use any specific arrangement for download and recovery mode... but I kept lousy notes. I can only confirm it never has hurt me to try with the battery in and remove it if there is a problem.
I mean no offense and admit it is good practice; I'm just curious how this detail sorts into rumor/prejudice/fact in the spirit of raised eyebrows.
Swyped w/ XDA App. When in doubt, mumble.
soba49 said:
Have you had a bad experience? I am the type of person that doesn't use any specific arrangement for download and recovery mode... but I kept lousy notes. I can only confirm it never has hurt me to try with the battery in and remove it if there is a problem.
I mean no offense and admit it is good practice; I'm just curious how this detail sorts into rumor/prejudice/fact in the spirit of raised eyebrows.
Swyped w/ XDA App. When in doubt, mumble.
Click to expand...
Click to collapse
I haven't heard it cause any kind of damage if that's what you mean but Odin just plain wont see my phone if the battery is in it sometimes. If I unplug the USB and remove the battery I can plug it back in and it works. Odin is just crazy like that.
I can't even get my phone to go into download mode when there's no battery in. Plugged in via USB and everything- no response. I got to the screen once, and used Odin to put CWM from the EB01 walkthrough thread on there, but Rom Manager won't recognize that, OR that I have the SD card in mount mode. Help please? Lol.
UPDATE: Fixed it. Figured out what I was doin' wrong to get into Manual Download and just redid everything, and it worked out.
Kevin Gossett said:
Also, make sure you have the battery out when plugging in and going into download mode. Odin doesn't like batteries.
Click to expand...
Click to collapse
The battery thing and odin is completely untrue. At least for me. Because whenever I need to flash something with odin my battery is in every time. So the whole odin not liking batteries seems like a myth to me.
Sent from my SCH-I500 using XDA App
times_infinity said:
The battery thing and odin is completely untrue. At least for me. Because whenever I need to flash something with odin my battery is in every time. So the whole odin not liking batteries seems like a myth to me.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Agree.... I have option to reboot into Download mode via the power button and I dont take my battery out, still works fine.
Take the battery out, hold down the volume down button, then plug the usb cable in (other end of the usb cable should be plugged into the computer.) This is the correct way to get to "download mode" and use Odin. Also, what someone said about drivers is also something to consider. But after flashing a rom, I figured you'd have done all this at least once!
Do you have the correct version of clockwordmod? What about the modem version? This should be sorted out before flashing...
disregard this
Okay, I've searched and searched and no one seems to have the specific problem that I'm having with my phone, so I'm taking to the forums myself. I've been rooting since the G1, I know how to adb push things, I have used google and multiple forums to try to fix this problem. So here goes, anyone that can help I thank you in advance.
1-My phone, like some other MT4G users, reboots itself each time it's plugged in. Initially I thought this was because I was using a Kindle cord to plug it into the pc, so I bought an MT4G usb cable from tmobile, and still it boot loops (just the first white screen for maybe 4 seconds, then black then again and again). The only way to charge it is to let it start boot looping, take the battery out, turn it on, and if I'm lucky enough that it begins to boot up correctly I plug it in mid boot. If I wait til it's fulled loaded it just starts rebooting again.
2-It will not at all from any angle go into Recovery mode. If I try to go to recovery from Rom Manager, or from the screen you get when holding power and lower volume key or by flashing a rom through Rom Manager, it just boot loops just like mentioned above, until I pull the battery for a while (it is currently sitting next to me with the battery out) and then put it back in.
3-If by chance it's on, and plugged into the computer, it is not at all recognized. Ever. While it's booting up my computer finds something, but doesn't know what it is, and doesn't allow me to view any folders on the SD card. Yes I've installed the HTC drivers file. I've adb'ed things to this phone before, now it says device not found. I don't know when it stopped being recognized...
4-I've even tried to fastboot something over to it, but to no avail, still not found.
If I try to do a factory reset, it boot loops. If I sneeze it boot loops.... I don't know what to do, and if I trade it in under warranty, I have to reset it to stock rom, or they're going to charge me for a new phone. Any ideas!?
I have Cyanogen mod 7 on here.
have you tried a fastboot wipe? or have you tried to reboot to recovery from adb?
First, I don't trust using the actual ROM Manager app to do the flashing/installing.
Since you've been flashing since the G1 days why not use Clockwork Recovery? Just go into recovery and do the necessary wipes.
So I suggest to do a complete full wipe in Clockwork, meaning wipe data, cache, and dalvik cache. Install the newest CM nightly (Which is working wonderfully BTW) and see if your problems still persists.
Edit: I didn't realize you tried to enter recovery, oops. But yeah try what the buy above me said. Try re-installing the latest CWM recovery, if that still fails then try heading into there via ADB.
mackster248 said:
First, I don't trust using the actual ROM Manager app to do the flashing/installing.
Since you've been flashing since the G1 days why not use Clockwork Recovery? Just go into recovery and do the necessary wipes.
So I suggest to do a complete full wipe in Clockwork, meaning wipe data, cache, and dalvik cache. Install the newest CM nightly (Which is working wonderfully BTW) and see if your problems still persists.
Click to expand...
Click to collapse
I second that, flashing ROMs from ROM Manager a terrible idea.
Well...if all else fails and if you are really thinking about returning it and still under warranty...few seconds in the microwave method should work just fine. They wont be able to see that its rooted if the phone wouldn't turn on, would they???
glimmer of hope...
So by the grace of god I did get it flashed back to unrooted, stock 2.2 by putting it as pd15img.zip on my sd card and going into bootloader. Once that was done I thought I would be out of the woods... I even plugged it in last night and no boot loop!! but this morning I unpllugged it (and I'm using a tmobile cable for the phone attached to my pc) and here it sits, next to me again with the battery out of it because everytime I try to turn it on (for over 40 minutes now) it boot loops to that stupid white screen (that is honestly driving me insane at this point). I know that it isn't rooted (because I dl'ed rom manager and it won't let me do anything without being rooted) so do we think that I'm safe to go to the store today to request a new one be sent? Thoughts? And thanks for the help thus far!
yeah I would send that back
Bad emmc chip? I'm sorry man, that's a terrible story.
Sent from my HTC Glacier using XDA App