This is pretty bizarre.
I have been running CM7 nightly 180 with Trinity for about a month now. I woke up to my phone vibrating a bit - my K9 mail app got reset so it was redownloading old emails. I tried to open my Twitter app and that was reset as well. After that a bunch of force close dialogues popped up, so I rebooted my phone thinking it glitched up. Once I did that, it would show the Google logo, then the first Trinity logo, and just hang there. It did not get to the Trinity animation.
I can get into recovery, and from there I tried to restore to a backup, and it says E:Can't mount /sdcard. Do I have to Odin to fix this or is there another option? I remember the same error happening to my Vibrant, and that was the only solution.
Does anyone have any explanation as to why this happened? I didn't do anything unusual with the phone or install anything new/different at all. I plugged it in, went to bed, and woke up to this.
Strange :S. Did you try to mount SD card from recovery while you have your phone conected to PC? I hope it's not faulty storage memory problem...
Sent from my Nexus S using XDA App
I just tried, CWM says "Error mounting /sdcard!" This all happened with my Vibrant. It said all of the same things and I had to use Odin, and it worked, but my /sdcard was completely wiped. It just doesn't make sense since this time I didn't do anything differently; I think on my Vibrant I had installed a new ROM and then it messed up. This time it's like a phantom f**k up.
That doesn't sound so good . Seen few people with same problem, and most of them sent their devices for repairs. It was some hardware error where Odin couldn't help.
Can't be sure if that is the same problem, but it easily could be. I'm not expert, I'm just sharing what I've seen before. Let's hope I'm wrong about this one...
Ugh I really hope not. I bought this phone on eBay in August, I still owe money to Bill Me Later -_-
Off to Samsung it goes
Sent from my Nexus S 4G using xda premium
Get into recovery mode by turning phone off then hold volume up button then press the power button. It should go to recovery. In recovery go to advanced the mount SD card and mount data. Then try doing a restore
Sent from my Nexus S 4G using xda premium
bille3939 said:
Get into recovery mode by turning phone off then hold volume up button then press the power button. It should go to recovery. In recovery go to advanced the mount SD card and mount data. Then try doing a restore
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Try to read again what OP wrote in his/her posts...
Have you tried flashing another recovery? Or even, lock and unlock the bootloader? It should format your sd card and that might fix it.
Sent from my Google Nexus S using XDA App
I recall having a similar problem in recovery, I just can't remember what I did to fix it!
Sent from my Google Nexus S using XDA App
You could also try this.
http://forum.xda-developers.com/showpost.php?p=18316565&postcount=29
Try use other version of recovery. It is a bug from I dunno which version of recovery.
Accidentally sent from my Google Nexus S using XDA Premium
I'm on version 5.0.0.0 of CWM, is that the buggy one by chance?
I can't get the USB driver to install here at work (Windows), I am going to have to wait til I get home to flash an updated version of CWM from my Mac.
Flashing a new recovery didn't help. My /sdcard still says error for everything. I wish Odin worked on Macs.
Just used someone's PC to use Odin and my phone hangs at "verify image (ipbl)... success." I think I'm going to throw in the towel and cut my losses at this point. I don't really have any other options.
Amazing but working solution for the same problem!
There is a post in Google mobile support were many people had the same problem and one guy exposes the solution, because I am new user, I can't link outside xda so I tell you the fix:
It's said to be a common hardware problem in this device, for me it just works when I power on after heating up with a hot air gun (other people say a hair dryer is enough)
I hope that you find this information useful
any news?? i have the same problem :'(
Heating Works
Thanks I have the same problem. I was not able to mount any of the system or sdcard partitions. Heated the phone with a heat gun and it starts up.
palpablo said:
There is a post in Google mobile support were many people had the same problem and one guy exposes the solution, because I am new user, I can't link outside xda so I tell you the fix:
It's said to be a common hardware problem in this device, for me it just works when I power on after heating up with a hot air gun (other people say a hair dryer is enough)
I hope that you find this information useful
Click to expand...
Click to collapse
Related
Hello people,
I recently installed GalaxySense Rom (Search "oozeroo" on Google) for my Samsung Captivate AT&T, and it was working fine, until I changed a few settings, then it said it was going to Hot Boot, so the hot boot worked fine. Then, I turned off my phone and turned it back on, and it does not boot. I tried some stuff (check the Situations). My phone is stuck at "Galaxy S Cyanogen(Mod)" (Picture Included!!!)
Situation:
-No Download Mode
-No recovery mode
-Flashed this rom with rom manager (wiped dalvik cache only)
-TRIED installing Clockworkmod recovery, but wont work (not booting into recovery)
-Only an internal SD inside phone, 14 Gigs.
(Ask me for more info if needed please)
Thank you so much, and please help.
--DV
It looks like a possible brick dude
Sent from my ADR6300 using XDA App
Alright, well, thanks, at least, for the response.
I still have the 30 day warranty, although not sure if it is a good idea if I should because it is rooted! Aye caramba...
Wrong freaking forum. That being said, take out battery, hold both volume buttons, plug in USB, then put in battery, all with both volume buttons held the whole time. May take a few tries but will get u in download mode for Odin.
If this doesn't resolve your problem (it will if done correctly), visit the Captivate forums.
Sent from my SGH-T959 using XDA Premium App
aigh, did not work for me, and tried returning it, but they did'nt accept it, NOT because it had cyanogenmod on it, but because it was bot booting!
Thanks guys
Buy or make a jig to force download mode... its not bricked because its loading, probably something was messed up being that its a port and 1 change can send things into disarray seeing as the kernel has been reoriented and is very beta
Sent from my I897 using XDA App
can I cut off an old charger that fits the captivate, and use that?
There is an article somewhere on xda that shows you how to make it business 3 100k resistors and there must be other ways, you can if you want to waste a charger but look it up thoroughly before making any rash decisions
Sent from my I897 using XDA App
Like this I believe
http://wn.com/Force_Galaxy_S_into_download_mode_by_homemade_Jig
Sent from my I897 using XDA App
Hi, completely lost with what to do so hoping you guys can help me out. I am relatively clueless (but hopefully able to follow direction).
Heres the story:
Bought a Nexus S second hand for Rogers here in Canada. Been working great for 3 months or so.
The phone, to my knowledge, has never been rooted in anyway, hacked, etc.
So I have had Go Launcher and its associated widgets installed for some time. No issues. About a week ago I got an update notification for 2.3.6 (I was previously on 2.3.4, and even though I checked it never did find 2.3.5)
Now I heard about issues with tethering, and since I never had the search pop up issue I kept ignoring this.
Well today, the Go Launcher got 'stuck' while I was switching orientation( horizontal to verticle) and once it got unstuck recevied a ton of force close notices. I decided to power it off. It got stuck in the power off animation. I pulled the battery.
Since then, it gets stuck in the boot animation (rainbow x?). I have pulled battery numerous times, one time it sat in the animation for 20 min or so, only to restart itself and do it again.
I went to fastboot, and rebooting that way does nothing. Also, I can't go to recovery, when I do it restarts, and then the Android pops up, but eventually I get an Exclamation mark and Android and need to pull battery.
I don't think I can hook it up to the pc because I don't think I enabled usb debugging.
What are my options, any help would be greatly appreciated!
You need to flash the clock work recovery to put a new rom, first install the usb drivers for the nexus and the using dos flash the clock work recovery
Sent from my Nexus S using XDA App
Sent from my Nexus S using XDA App
Is that possible even though I'm pretty sure usb debugging is not enabled?
Any idea what caused this?
Surely there is a way to reset?
OK so did the rooting procedure but stopped before actually hitting the rooting stage.
Any ideas what happened?
Could it have been Go Launcher? Or maybe enabling orientation switching caused it to freak out...
Sent from my Nexus S using XDA App
Follow up to step 7 in the nexusshacks how to root guide and goto recovery mode now, select mounts and thrmen mount usb storage and copy a downloaded rom like cyanogen mode and goto install from zip and fromsd sdcard to install and then advance>clear delvik cache and clear cache partition before installing the rom
Sent from my Nexus S using XDA App
brad2332 said:
OK so did the rooting procedure but stopped before actually hitting the rooting stage.
Any ideas what happened?
Could it have been Go Launcher? Or maybe enabling orientation switching caused it to freak out...
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
If you don't tick the prevent force close, a month ago mine were stuck on home screen and keep forceclosing, all i do is just install another launcher press home screen and voila
The android ! Is the recovery. Stock recovery.
You can try a factory reset from in there.
Or do the entire unlock bootloader and root thing. Unlocking will wipe the phone anyways so just try a factory reset from recovery.
At the ! There is a button press that brings you to the options. I can't recall for sure what it is though. I think it is volume up and press power but I am not certain. If you can't figure it out on your own just look it up.
You probably corrupted your sdcard partition while pulling the battery while it was trying to unmount. If that's the case your sdcard is now bad and the only way to fix is to send it in to service.
Sent from my Nexus S 4G using xda premium
So just went ahead and rooted and now running cm7.
Unfortunately lost everything on the phone but had no choice. It was not possible to get into fastboot and use recovery. It hung at the exclamation mark.
Oh well. First time using CM7.... pretty good... mostly just seems to be stock android?
Sent from my Nexus S using XDA App
Again the exclamation mark IS the stock recovery.
i have a nexus s 4g i havent used in awhile because it is stuck on a cm7 bootloop. any think i can do? i havent been on here in awhile since i told myself i wouldnt root another phone. now i want one i can play with so im going to reuse my old one. i dont care if it gets reset considering it hasnt been used.
i4g3t143 said:
i have a nexus s 4g i havent used in awhile because it is stuck on a cm7 bootloop. any think i can do? i havent been on here in awhile since i told myself i wouldnt root another phone. now i want one i can play with so im going to reuse my old one. i dont care if it gets reset considering it hasnt been used.
Click to expand...
Click to collapse
First this is the wrong section for this. Second just restore the phone back to stock.
Click HERE !!!!!
Before you do this turn off your device, press volume up and power at the same time !! That should take you to Bootloader Menu !!
I recommend you to stay stock, if you have no experience rooting, flashing or unrooting don't try again BEFORE educating yourself more.
Try going into clockwork mod mount USB in advanced menu download a new rom put it on your SD card and flash it. Just so u know this belongs in q/a not development.
Sent from my Nexus S 4G using xda premium
it doesnt allow me to do anything. and isnt recognized by the computer. and i realized its in the wrong section but its kind of late now.. i just plugged it to let it charge. its doing something it hasnt done before.. its stuck on bootloop but when i unplug it it flashes the lockscreen with status bar searching for media then turns off
i4g3t143 said:
it doesnt allow me to do anything. and isnt recognized by the computer. and i realized its in the wrong section but its kind of late now.. i just plugged it to let it charge. its doing something it hasnt done before.. its stuck on bootloop but when i unplug it it flashes the lockscreen with status bar searching for media then turns off
Click to expand...
Click to collapse
Install the drivers on your computer. U cand find them here somewhere and hold volume up + power and try to use fast boot to flash cwm
Sent from my Nexus S 4G using xda premium
Can you access recovery by holding volume + and power? If so, just wipe everything and reflash the rom on your sd.
Thread moved to Q&A.
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?
I realize there are multiple threads like this but throughout all of them I have not found any that relate to my issue or a combination of them. If I have missed one I apologize in advance and please direct me to that thread then. I was running steel droid what I thought was 5.5 ICS but it looks like it is 5.1 according to the forums. I was previously running steel droid 4.5 GB. I was switching back to 4.5 because I could not get wifi hotspotting to work. I forgot to wipe my cache and went to install 4.5 and I am stuck in bootloop. X+Power gives me the android error screen, M+Power allows me into the main menu but I cannot use AP fastboot, SBF motorola will not pick up my phone and the screen will show a connection to the USB cable. I've never had a problem before but also have never forgotten to wipe the cache so any thoughts would help.
m3schz8! said:
I realize there are multiple threads like this but throughout all of them I have not found any that relate to my issue or a combination of them. If I have missed one I apologize in advance and please direct me to that thread then. I was running steel droid what I thought was 5.5 ICS but it looks like it is 5.1 according to the forums. I was previously running steel droid 4.5 GB. I was switching back to 4.5 because I could not get wifi hotspotting to work. I forgot to wipe my cache and went to install 4.5 and I am stuck in bootloop. X+Power gives me the android error screen, M+Power allows me into the main menu but I cannot use AP fastboot, SBF motorola will not pick up my phone and the screen will show a connection to the USB cable. I've never had a problem before but also have never forgotten to wipe the cache so any thoughts would help.
Click to expand...
Click to collapse
Not wiping cache won't give you boot loop lol just go back into recovery wipe everything and flash a working ROM solved :thumbup:
Sent from my SCH-I500 using Tapatalk 2
bbrad said:
Not wiping cache won't give you boot loop lol just go back into recovery wipe everything and flash a working ROM solved :thumbup:
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
I would but I get android error screen with exclamation mark each time regardless of how I access recovery X+Power or vol +,- and Power then going to recovery, I wouldn't have thought that not wiping the cache would have been the cause but it was the one step I didn't do that I normally always do so I was just adding it in for information but thanks for the know how that it wasn't the cause. Any other thoughts since I cant even get into my backup ROM or recovery, I have another SD card not sure if my SD card has become fried for some reason, I will be trying that to see if maybe that is all it is.
m3schz8! said:
I would but I get android error screen with exclamation mark each time regardless of how I access recovery X+Power or vol +,- and Power then going to recovery, I wouldn't have thought that not wiping the cache would have been the cause but it was the one step I didn't do that I normally always do so I was just adding it in for information but thanks for the know how that it wasn't the cause. Any other thoughts since I cant even get into my backup ROM or recovery, I have another SD card not sure if my SD card has become fried for some reason, I will be trying that to see if maybe that is all it is.
Click to expand...
Click to collapse
Well I'm on a Samsung device but we have a program you load files in and you can flash your device back to stock do you have something like that?
Sent from my SCH-I500 using Tapatalk 2
Droid 3 stuck in bootloop'
bbrad said:
Well I'm on a Samsung device but we have a program you load files in and you can flash your device back to stock do you have something like that?
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
Yep but phone isn't picking up my data cable and how ever many issues that have come about here, I think I am SOL but gonna try an SD card hoping that it is just a bad SD card or something like that. May end up having to use part of that great tax return also, thanks for the help, I'm going samsung next, that whole fore sight wasn't there two years ago.
In it's current state, is it in any way possible to tell that it is rooted? Is the boy animation stock or a different one? Motorola might repair it for you if you can't tell that it's been rooted
Sent from my HTC6435LVW using xda app-developers app
Droid 3 stuck in bootloop
dj2muchxx said:
In it's current state, is it in any way possible to tell that it is rooted? Is the boy animation stock or a different one? Motorola might repair it for you if you can't tell that it's been rooted
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Unfortunately you can easily tell that it is not stock ROM by bootloop
Well your computer should recognize your droid that's a common problem with Odin and Samsung one of these steps always work so try then and seen if we can't get your droid recognized NUMBER 4 WILL WORK 99% OF THE TIME BUT TRY THE OTHER METHODS FIRST 1. Use the stock cable or try a difrent port 2. If its possible on your program take out the battery and SD card as leaving them in course problems 3. Run the program as aminstrative 4. Plug the phone in and have it in download mode or whatever you call it WHILE THE COMPUTER IS BOOTING Up This will force the computer to recognize it not the best method but it always works
Sent from my SCH-I500 using Tapatalk 2
Droid 3 stuck in bootloop
bbrad said:
Well your computer should recognize your droid that's a common problem with Odin and Samsung one of these steps always work so try then and seen if we can't get your droid recognized NUMBER 4 WILL WORK 99% OF THE TIME BUT TRY THE OTHER METHODS FIRST 1. Use the stock cable or try a difrent port 2. If its possible on your program take out the battery and SD card as leaving them in course problems 3. Run the program as aminstrative 4. Plug the phone in and have it in download mode or whatever you call it WHILE THE COMPUTER IS BOOTING Up This will force the computer to recognize it not the best method but it always works
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
Thanks step 4 ended up being the working method, happened again when loading gingerbread back on, so I walked through it again, removed ICS from memory card wiped phone completely and then loaded gingerbread back on and finally had success. Thanks for all the help
m3schz8! said:
Thanks step 4 ended up being the working method, happened again when loading gingerbread back on, so I walked through it again, removed ICS from memory card wiped phone completely and then loaded gingerbread back on and finally had success. Thanks for all the help
Click to expand...
Click to collapse
NP if you ever need anything just ask
Sent from my SCH-I500 using Tapatalk 2