Hello all,
Just found a neat little work around for getting into recovery when you have a radio on your SDcard. You don't need a card reader or anything for this one. Tonight I accidentally flashed a Sense kernel while trying to get CM7 up and running. I got stuck at the HTC screen and it refused to boot any farther. So I had the choice of going to walmart and buying an SDCARD reader, but I thought that I could find a way around it, and I did. Sorry if this has already been posted.
Steps:
1. Connect to a charger and remove the SDCARD from the phone, replace the battery and then boot into Hboot screen. Normally this would ask to update the radio if an SDCARD with a PG05img.zip file was inserted, and regardless of whether you accepted or declined, you were forced to reboot, with no way to get into recovery.
2. Remove the battery from the phone. Hboot will stay powered up while connected to your charger.
3. Reinsert the SDCARD and replace battery.
4. Select recovery and your phone will boot into recovery for you, and you can restore a backup, or reflash your rom, or whatever you were trying to accomplish before you got into a bootloop or bad rom install or whatever.
Again, I don't know if this has been posted before, but I thought it was a cool little workaround for those times you need to get to recovery but can't due to the PG05img.zip file still being on your SDcard.
Hey nice find!
Neat, I didn't realize HBoot would stay up without a battery.
This is a nice find. We should have a tips and tricks sticky for the bolt.
Sent from my thunderbolt
or you can use ADB and type "adb reboot recovery", or if you have the 4 in 1 reboot mod on your rom selecting to reboot to recovery bypasses hboot also
And don't forget rom manager, that has a feature that will boot directly into recovery also
wow nice! I had this same problem and I had to grab my friend's fascinate to delete the radio in order to get into recovery. I was trying the method as you by taking out the battery but I didn't try it at the hboot screen so the phone kept powering off.
Deltaechoe said:
or you can use ADB and type "adb reboot recovery", or if you have the 4 in 1 reboot mod on your rom selecting to reboot to recovery bypasses hboot also
And don't forget rom manager, that has a feature that will boot directly into recovery also
Click to expand...
Click to collapse
This method is there for the times you are stuck in a bootloop, but due to the fact that you have a radio (PG05img.zip) on your sdcard, you can't get into recovery to restore a backup. Like if you flash a sense kernel and are trying to run CM7 like I did. This avoids the need to have to use a card reader to remove the file from the root of the sdcard, or using a buddies phone.
Sent from my ThunderBolt using XDA Premium App
Awesome trick. Still a good idea to rename it or delete it, but this is great for people who inevitably ignore it lol.
Sent from my ThunderBolt using XDA App
Yeah, I forgot to remove the file from my sdcard before flashing the new rom, and that's what got me in trouble. I usually do delete the file after flashing a radio, but I forgot, then when the kernel didn't agree with the rom, I was stuck.
Or if you have rom manager u can boot up then reboot to recovery ....
Nvm I see what u did lol
Sent from my ThunderBolt using XDA App
Hmmm, that's pretty cool.
This saved my ass last night. Thanks for the tip!
Thank you, this is helpful.
Sent from my ADR6400L using Tapatalk
whb_3 said:
This saved my ass last night. Thanks for the tip!
Click to expand...
Click to collapse
Glad it helped someone :]
Sent from my ThunderBolt using XDA Premium App
great find! coulda saved me some headaches before, but im sure it will save future ones!
This does not seem to work for me. When I am in HBoot and pull the battery while its plugged into the charger it just shuts off.
I might actually give this a try tonight despite not having this problem yet. Been running das BAMF GB and now with the bricking scare that's been going on, might as well make sure I can recover if need be.
espnaholik said:
This does not seem to work for me. When I am in HBoot and pull the battery while its plugged into the charger it just shuts off.
Click to expand...
Click to collapse
Make sure you're using a wall charger and not using an extension cable or any sort of power splitter. I ran into the same issue when using a USB cable and when using a wall charger on an extension power splitter. I plugged straight into the wall and it worked like a champ.
Pretty cool ... hopefully I'll never need it
Seriously though, I had this happen while at work and was freaking out. Lucky for me the IT guy had a micro SD card reader on hand (I do have one at home). But it's good to see this little trick so that if this were to happen to me again while at work I can save myself the embarrassment of having to ask the IT guy for his card reader again lol
I was using a wall charger but I had it plugged into the lamp power outlet in the hotel I'm staying in, guess it wasn't enough power. Ended up getting a micro sd card reader at wally world, phone was stuck at HTC screen after flashing latest gingervitis.
Related
I know I saw this before somewhere here in the forums but I can't find it. I am following http://forum.xda-developers.com/showpost.php?p=14692818&postcount=1 this guy on how to root. I'm at the part: Installing kernel through CWM.
So my problem is when I'm in the recovery mode it says something on the lines of apply update sd card or something like that instead of "install zip from sdcard". How do I get it to say that?
Thanks in advance!
Edit: Another question, do I leave odin3 open the whole time?
I'm thinking you are in stock recovery, not cwm. Did you boot straight into cwm after using odin?
Sent from my Droid Charge!!
no **** i forgot that i had to put the kernal and ROM on the sd card. I'll try that now
I'm stuck at the blue banana? Any ideas on what to do?
Nevermind, got it, had to hit the power button
K, pull battery then boot back into cwm. From main menu use volume key to scroll down. Keep scrolling till a message says back button enabled. After that you should be good.
Sent from my Droid Charge!!
hockeybpr25 said:
I'm stuck at the blue banana? Any ideas on what to do?
Click to expand...
Click to collapse
Scroll through the menu 3 times till it says go back enabled. Then it should work fine.
Sent from my SCH-I510 using Tapatalk
So I was about to install my ROM and I did wipe data and it does it and then it reset the phone and that female voice started to say whatever it says and then says 2 minutes remaining so it never allowed me to install the ROM. what should I do now?
Just let it do it's thing. After it boots just boot into recovery then flash the rom like you had planned.
Sent from my Droid Charge!!
it just booted up normally and had me set up my phone, i just skipped through everything though because i know it's all messed up atm and i need to flash the ROM
another thing, i forgot to do the sd card fix and i'm trying to put it on the sd card but now it says:
"The disk is write-protected.
Remove the write-protection or use another disk."
How do I fix that?
Ok, from what I've read you can't with the phone. You would have to take the sd card out and put it into your computer if you have a card reader.
Sent from my Droid Charge!!
Crap, I don't think I do. Do I need the SD card fix?
I believe thats the only way to fix it. Not completely sure though. There may be more info in the thread you got the fix from.
Sent from my Droid Charge!!
I just put GummyCHARGED on it and after that it allowed me to add it, so I'm just glad I can still put stuff on it.
Awesome! Glad you got it figured out.
Sent from my Droid Charge!!
Thanks bunches
Sure thing!
Sent from my Droid Charge!!
Hi All
Hoping someone can tell me if I've completely killed my phone. It was working absolutely fine with no problems whatsoever until earlier today when it froze. Without looking around at what to do I just held down Vol + & Vol - & power. This restarted the phone and it went through the T-Mobile logo and then just sat there. I then took out the battery, put it back in and held vol - and hit power, got into the clockworkmod menu and used the recovery option to wipe then restore an earlier backup, this all seemed to go fine and I used the power off option to restart the phone.
Nowwww though it just vibrates 7 times and stops, if I then pull the battery and replace it and hit power it vibrates 7 times again and then nothing unless I pull the battery again.
Am I screwed?
The phone is S-Off and had clockworkmod installed. Has the clockworkmod boot loader thingy some how been damaged? Anything I can do?
Appreciate any advice. Thanks
can you get into recovery? if so try wiping everything and then doing a fresh install of something
Sent from my Desire HD using XDA App
dont keep pulling the battery if you dont already have emmc failure you will soon if you continue to pull the battery!
Yea I didn't realise pulling the battery was that bad. I haven't done it since reading this forum. But no I can't get in to recovery any more since that time I wiped everything and restored a backup. Since then it just vibrates 7 times when I push the power button and that's all.
can it connext to adb? if so, id try flashing an ruu via fastboot. that will set everything back to stock. then you can reroot and flash a rom, and id get rid of that backup
Sent from my Desire HD using XDA App
Is there a guide for adb anywhere? I haven't used it before, but I've tried plugging the phone in by USB and Windows doesn't say new hardware found so I assume that's a bad sign?
rlzzzz said:
Is there a guide for adb anywhere? I haven't used it before, but I've tried plugging the phone in by USB and Windows doesn't say new hardware found so I assume that's a bad sign?
Click to expand...
Click to collapse
theres tons of guides but if you give me a few minutes ill upload a auto installer for you, so then you just have to add the path in
Sent from my Desire HD using XDA App
I looked for adb guides and they all seem to show how to install the drivers etc but my phone doesn't even get detected as a new device in Windows so I assume it's not going to show up?
I mean it looks completely dead right now, won't turn on or even vibrate. Unless I was to pull the battery again I think it would probably then vibrate 7 times when I push the power button for the first time and that would be it again.
Do you think the clockworkmod boot loader got overwritten some how when I did the restore?
rlzzzz said:
I looked for adb guides and they all seem to show how to install the drivers etc but my phone doesn't even get detected as a new device in Windows so I assume it's not going to show up?
I mean it looks completely dead right now, won't turn on or even vibrate. Unless I was to pull the battery again I think it would probably then vibrate 7 times when I push the power button for the first time and that would be it again.
Do you think the clockworkmod boot loader got overwritten some how when I did the restore?
Click to expand...
Click to collapse
it could of, and its worth a shot, it might be recognized. just get adb working, and install the drivers. plug the phone into your computer, and wait a minute or 2 and the screen should turn on but be black. then just boot into the bootloader and flash the ruu via fastboot
Sent from my Desire HD using XDA App
So I installed Java JDK, then Android SDK, then downloaded the HTC adb drivers but it says to install the drivers plug in your phone and wait for Windows to detect it... which is as far as I can go because Windows doesn't detect the phone.
I don't even seem to be able to reset the phone by holding Vol + & Vol - & power at the same time. It's not looking good.
In fact you say about the phone going to a black screen, it did do this after I initially restored the image. But it was just after that that I pulled the battery and now it doesn't do that anymore.
I assume basically what has happened then is first some thing froze and corrupted my normal install, so to fix this I tried the restore and the restore image somehow overwrote clockworkmod but at this point the phone was still recoverable via adb? but then I pulled the battery and now it's definately dead?
Seems like an unfortunate string of events but at least I know now to avoid pulling the battery next time! Thanks for all your help stumpyz9 and djisgod, I don't suppose you know why pulling the battery can so easily kill the phone?
Btw if anyone would like to jump in and make my day by saying nooo everything is fine here is a quick fix please feel free
my only guess of why pulling the battery killed it is when you where restoring it and then pulled the battery, it was restoring something very essential to even turning the phone on. i dont know why windows wouldnt detect your phone, it has derected my DHD even in the worst scenarios. and were you saying the drivers wanted you to hook the phone to the computer? if so dont and try to continue installation, because if you can get it hooked up to your computer and have adb recognize it, then tyere is a very good chance you can recover it. if not, then im sorry to say you have yourself a very pretty paper weight. if it is a paper weight, id say maybe check to see if a dev could use it or basically part it out on ebay and sell the lcd, digitizer, housing, camera and you can probably make some of your money back.
Sent from my Desire HD using XDA App
The ADB HTC drivers I downloaded are not an installer file, you need to plug in the phone so Windows will recognise a new device and ask you to select the location of the drivers but I can't because it doesn't detect the phone being plugged in at all.
I've also been reading around a bit more and found a thread about a fried eMMC chip. I was actually getting the same errors they mention in that thread when I did the restore from clockworkmod.
"E:Can't open /cache/recovery/log" etc etc
dont use that, install htc sync, then plug the phone in and tell me if that works
Sent from my Desire HD using XDA App
Yea I just gave that a go after reading someones adb guide and even with HTC sync installed when I run "adb devices" it lists nothing.
It's strange I thought once I had clockworkmod installed nothing could go wrong because I would always be able to restore from an old backup. I always assumed that clockworkmod would be sat on the boot partition and never touched even when restoring a backup. I can't understand how it went so wrong lol.
Although right now the phone seems so far gone maybe I could get away with a warranty repair as they won't be able to tell it was S-OFF.
yah if all of the chip has been fried and it wont power on, i think that would be your best bet, seeing as they probably wouldnt be able to tell.
Sent from my Desire HD using XDA App
Ok well thanks for your patience I appreciate your help.
rlzzzz said:
Ok well thanks for your patience I appreciate your help.
Click to expand...
Click to collapse
no prob, alwsys like to help out when i can
Sent from my Desire HD using XDA App
​Atrix 2 will not charge it is stuck in recovery (Blue CWM) it has atrix 2 bootsrap installed and RAZR-CWMOnBoot-Global-J.Y.Daddy.zip file installed need help asap tried cmd line prompt to reboot phone but cpu wont recognize device also i left it on charger overnight and still nothing i will probably get another battery soon but i still need to know how to fix this if i run another battery to 0% thanks in advance dev team :crying:
Did you try to take the battery out of the phone? When you do it will boot into CWM Recovery.
thats the only thing it will boot into it wont go past CWM no matter what i do
dscott973 said:
thats the only thing it will boot into it wont go past CWM no matter what i do
Click to expand...
Click to collapse
When you try "reboot now", what happens?
Charge phone for awhile and FXZ back to stock. The phone will charge if you turn it off and plug into wall charger.
Sent from my SAMSUNG-SGH-I997 using xda premium
And if you have CWM on boot installed you need to either delete the bootstrap apk, or deny it su rights in super user. It's either one or the other, not both.
Sent from my MB865 using xda premium
pull the battery, then put it back after a few seconds and hold both volume buttons while turning it on. choose normal powerup and see if that will boot it. you can also try bp tools.
TheZeroDay said:
When you try "reboot now", what happens?
Click to expand...
Click to collapse
You have CWM on boot installed so this is what it's going to do every time you reboot.
You have to select "reboot now" to get it to boot up normally after getting to CWM.
Have you selected " reboot now" and what were the results?
I have seen people even having this type of trouble on other phones as well, If you are unable to charge your battery Get a battery only charger from ebay using which you will be able to charge your battery then use FXZ you will be fine
link for charger
http://www.ebay.com/itm/Battery-Cha...259246?pt=PDA_Accessories&hash=item4cff64042e
Maybe you should but a ROM in your SD card, get the SD card out put in another phone or MicroSD card adaptor, put a ROM in it and flash it, it should fix the issue. It's not the best idea but it should work.
JRW 28 said:
You have CWM on boot installed so this is what it's going to do every time you reboot.
You have to select "reboot now" to get it to boot up normally after getting to CWM.
Have you selected " reboot now" and what were the results?
Click to expand...
Click to collapse
Sounds as though he's just not familiar with CWM and its functions. I don't see how CWM can just hang there unless the user isn't selecting any of its functions to run...
Apex_Strider said:
Sounds as though he's just not familiar with CWM and its functions. I don't see how CWM can just hang there unless the user isn't selecting any of its functions to run...
Click to expand...
Click to collapse
Actually, if there is an issue with the boot image, it may NOT go past CWM, becuase it can't even check the boot partition if it is corrupted, so it will not even attempt it. I think there was link a few posts up that explained something similar.
I saw this a WHOLE lot with my inspire 4g, where the boot partition became corrupted on reboot, and CWM would not even attempt to boot.
I think tmease1 was right an fxz restore is the best fix at this point, just hope that the boot partition is not so borked that even that does not fail.
jimbridgman said:
Actually, if there is an issue with the boot image, it may NOT go past CWM, becuase it can't even check the boot partition if it is corrupted, so it will not even attempt it. I think there was link a few posts up that explained something similar.
I saw this a WHOLE lot with my inspire 4g, where the boot partition became corrupted on reboot, and CWM would not even attempt to boot.
I think tmease1 was right an fxz restore is the best fix at this point, just hope that the boot partition is not so borked that even that does not fail.
Click to expand...
Click to collapse
Ah, yes... indeed, if his boot image or system image is borked it WOULD NOT boot passed CWM in that case. Hard to diagnose the issue if we don't know what else has been done. Won't RSDlite flash the boot image in the unfortunate chance that his boot image is fudged?
Apex_Strider said:
Ah, yes... indeed, if his boot image or system image is borked it WOULD NOT boot passed CWM in that case. Hard to diagnose the issue if we don't know what else has been done. Won't RSDlite flash the boot image in the unfortunate chance that his boot image is fudged?
Click to expand...
Click to collapse
Yeah, but if I remember correctly, I think I saw a few users who still had issues restoring with RSDlite and even with the moto-fastboot commands, if the boot partition was deleted or so corrupted that it could not overwrite it. Now I have not done a search but just going off of what I remember, so I could be incorrect here though.
I fixed it I saw a post on another forum (forgot which one to anxious to try it) but it would only charge while connected to a computer led was white while charging unlike when connected to a wall charger (no led) it decided to reboot itself as I'd I selected reboot now from CWM I am thankful for all of you guys input. And I'm still gonna get a extended battery so this doesn't happen when I'm away for long periods of times...by the way the standard battery last about two days of moderate usage but can I use an extended battery designed for the Droid Bionic I figured I could but I'm not sure could it hurt?
Sent from my MB865 using xda premium
dscott973 said:
I fixed it I saw a post on another forum (forgot which one to anxious to try it) but it would only charge while connected to a computer led was white while charging unlike when connected to a wall charger (no led) it decided to reboot itself as I'd I selected reboot now from CWM I am thankful for all of you guys input. And I'm still gonna get a extended battery so this doesn't happen when I'm away for long periods of times...by the way the standard battery last about two days of moderate usage but can I use an extended battery designed for the Droid Bionic I figured I could but I'm not sure could it hurt?
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
if it fits and i the same voltage, it should be fine from a hardware standpoint, not sure what the phone will think of it though, I don't know if it does any kind of check.
Oh and every time I was turning it off and connecting to wall charger it would auto boot back to CWM then I would try to "reboot now" and it would fail and I did that continuously for a few hours sorta a manual boot loop lol glad I fixed it though even though it wasn't too broke
Sent from my MB865 using xda premium
dscott973 said:
Oh and every time I was turning it off and connecting to wall charger it would auto boot back to CWM then I would try to "reboot now" and it would fail and I did that continuously for a few hours sorta a manual boot loop lol glad I fixed it though even though it wasn't too broke
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Yeah, Moto is finicky about having the battery somewhat charged, and will not usually let you fully boot without it in, I think I read in some document on the Motorola forum that it had to do with the bootloader, and it was a "safeguard".
Good to see you're back up and running
I flashed a Jellybean touchwiz rom for Verizon GS3, and went to reboot and now nothing, zero zip nada. No charging led light, no way to get into recovery and no response.
Anything I can do?
what happens when you do vol up + home+power button?
Absolutely nothing. I tried to get back into the recovery to see if I could restore my backup and nope.
did you try leave it pluged in for 30mins ?
does it vibrate once when you try to turn it on?
No vibrating and no sign of life at all. Even when plugged into my computer, I was going to try the unbrick guide but it listed that I should be able to get into the recovery still.
NickTheMajin said:
No vibrating and no sign of life at all. Even when plugged into my computer, I was going to try the unbrick guide but it listed that I should be able to get into the recovery still.
Click to expand...
Click to collapse
leave it plugged in for a while to make sure its not drained battery
do you have a usb jig?
I don't have a USB jig but this is possibly good news. I removed the battery and SD card and plugged it into my computer and it tried to install drivers (failed but tried) and the led light comes on red.
if your gettin led now you more then likely need to let it charge
It doesn't give me the led with the battery in
Plug it into a wall charger for at least 30 or even better if you can get a battery from someone.
Sent from my sexy white Eclipsed galaxy S3
I think its gone still nothing.
red led means qualcomm download mode. sounds dead to me
Yeah, haha. I saw it and mentally prepared myself for it. Literally just got the phone today so Verizon had no qualms with just sending me a new phone. Guess I'm reactivating my Rezound in the meantime. Thanks for the help guys.
you know
I am surprised. That also happened to me the first time i flashed that very same rom (touchwiz) with twrp . I have done this so many times , i literarily can flash a rom on the way to work .
I was in shock , i still dont know how the heck can i flash a rom and brick .
I plugged mine into windows and i got the device manager driver error from hell . and my phone never came back up again
I stayed away form twrp and touchwiz and i still cant possibly comprehend how a simple rom flash can brick my phone .
Which ROM did you flash?
Sent from my SCH-I535 using xda premium
you could probably send it to get Jtag'ed for around $60 if your warranty is invalid (ie used device)
You just hard bricked it. I did the same thing. Check here - post 5 shows the same symptoms :http://forum.xda-developers.com/showthread.php?t=1770341
And here: http://forum.xda-developers.com/showthread.php?t=1791721
I was pushing a copy of root66 that I hadn't md5'd. Took a JTAG to bring me back (twice) .
Sent from my SCH-I535 using xda app-developers app
So, in the future, md5 checksum absolutely everything since I'm assuming now that that is why this happened? (Since I made doubly sure I was flashing a rom for my phone).
If you still have the file you downloaded, you can check it. That would answer that question. If it checks out fine, then we have to look elsewhere for the problem.
BTW, MobileTechVideos.com can bring you back - based on my experience with them, I highly recommend.
Sent from my SCH-I535 using xda app-developers app
Please share exactly what you did so others can benefit from your unfortunate experience.
What ROM did you flash?
Did you use ODIN or a recovery?
If recovery, which one - CWM or TWRP?
Was there any unusual condition you can think of ... low battery, USB connected to computer or to charger, etc?
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