for rooting that is. i rooted my inspire 4g couple days ago using bubby323's method. loved it. this method is what was recommended to me. now attnn1's method was recommended instead. i dl'ed it and looked at the effen manual, and it seems slightly confusing, maybe i'm missing something.
anyway, i was just wondering what everyone's preference was for rooting, and why. thank you all.
Hack kit was much easier for me.
Sent from my Desire HD using XDA Premium App
i used bubbys. but why are you rooting again?
i took my phone in and exchanged it, simply put b/c the volume button came loose and i wasn't comfortable with it like that. yes, i put everything back to stock and unrooted it first as well.
Hack it. Menu driven with no need to enter terminal commands. All I had to do was put the phone in usb debugging a couple of times and make menu selections. I found the effen manual to be consfusing at first, but once you open up and start running the program, it becomes more clear. The effen manual is telling you more what the process is going to do for you than what you need to do to run the process, which is making menu selections.
Sent from my Desire HD using Tapatalk
i see that now, thank you!
i seem to be having a problem with the ace hack kit...
What is it?
Sent from my Desire HD using XDA Premium App
on the 2nd step of downgrading. it doesn't seem like it's actually downgrading the phone. in the cmd it says it's clearing the cache, but when all that is said and done, it reboots back into the phone like normal, no setup to go through like the manual suggests. i hate to ask such a noob question, but does the fastboot need to be on or off or something? i feel like i'm missing something. during the 2nd step am i supposed to be doing anything manually or is it still doing everything for me?
You need to run as an administrator with a good gold card, good usb drivers, antivirus completely shut down, usb debugging turned on, and the usb connection in charge only mode. With all this, when you run menu 2, you should get the downgrade rom. If you don't, then there is an issue with one of the above.
Sent from my Desire HD using Tapatalk
when in the process of step 2, is there anything i need to be doing myself?
ok it went through step 2, rebooted, had to go through setup and change to usb debugging. did that. i'm supposed to hit the 3 on the cmd then right? i did that, and it turned off and now i have a red triangle with an exclamation point in it.
did you flash clockwork recovery?
Sent from my Desire HD using XDA Premium App
ahervey85 said:
when in the process of step 2, is there anything i need to be doing myself?
Click to expand...
Click to collapse
No. As long as you have all that I mention, you select menu 2 and have to do nothing until it reboots. If you are not rebooting into a downgraded rom, then something is wrong. It could be a bad gold card. I created my gold card with the gold card maker and then just picked up with the hack kit on menu two. The gold card creation process in the hack appears to be the same. Make sure all antivirus and malware detection is disabled, including anything Windows if you are using it. If you got the usb drivers from Sync, make sure Sync is disabled or uninstalled. I didn't use the sync drivers because I already had them installed from the sdk.
Sent from my Desire HD using Tapatalk
no, not yet. i was at the step of run through setup and turn on usb debugging. it says to temproot again? what was i supposed to do here? and how can i get rid of the triangle? i do apologize, i'm just a little bit confused at this point
fernandezhjr said:
No. As long as you have all that I mention, you select menu 2 and have to do nothing until it reboots. If you are not rebooting into a downgraded rom, then something is wrong. It could be a bad gold card. I created my gold card with the gold card maker and then just picked up with the hack kit on menu two. The gold card creation process in the hack appears to be the same. Make sure all antivirus and malware detection is disabled, including anything Windows if you are using it. If you got the usb drivers from Sync, make sure Sync is disabled or uninstalled. I didn't use the sync drivers because I already had them installed from the sdk.
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
yes, i finally got it to boot into the downgraded rom, but i'm stuck again. i swear i made it through the other method of rooting before, so i'm not sure where i'm messing up here. i'm in the downgraded rom now, just went through the setup and turned on usb debugging.
hate to bother, but can anyone point me in the correct direction once i've made it to the downgraded rom?
All I did was make sure debugging was turned on, made sure that the usb connection was still charge only, and started option 3 in the menu.
Sent from my Desire HD using Tapatalk
fernandezhjr said:
All I did was make sure debugging was turned on, made sure that the usb connection was still charge only, and started option 3 in the menu.
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
so if i understand correctly, once i turn usb debugging back on, very usb charge only, i go to cmd prompt and hit 3?
thanks for everyone's help. i finally got it through the final steps. now is there any recommendations for any radio's? or can i leave it as is?
Related
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.
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
My HTC Inspire is running CM7.1 but for some reason I can't get it into debugging mode. I want to unroot it so I can sell it. I've tried this: http://www.filefactory.com/file/b50...60.19_26.06.04.06_M_release_166557_signed.exe but it just force closes. I've tried other unroot methods but nothing seems to work!
What could the problem be?
Ferrari353 said:
My HTC Inspire is running CM7.1 but for some reason I can't get it into debugging mode. I want to unroot it so I can sell it. I've tried this: http://www.filefactory.com/file/b50...60.19_26.06.04.06_M_release_166557_signed.exe but it just force closes. I've tried other unroot methods but nothing seems to work!
What could the problem be?
Click to expand...
Click to collapse
Maybe a bad flash. You can try flashing the CM again. USB Debugging should activate automatically when you plug your cell to the PC. If that is not working, try flashing a different Rom and see what happens....
You can also try the Hack Kit to revert to stock and S-ON....hope it helps
I have tried reflashing, even different ROMs. When I plug it in, nothing happens and the notification bar thing doesn't show up even though it's supposed to.
And I'm pretty sure the hack kit needs debugging...
Sent from my Touchpad using Tapatalk
Ferrari353 said:
I have tried reflashing, even different ROMs. When I plug it in, nothing happens and the notification bar thing doesn't show up even though it's supposed to.
And I'm pretty sure the hack kit needs debugging...
Sent from my Touchpad using Tapatalk
Click to expand...
Click to collapse
bad usb cord?
also sometimes try rebooting your computer. if you have plugged and unplugged your phone a lot of times, it can screw up the usb drivers and a reboot helps.
I've tried different cords, different computers, nothing. and I can't get a warranty replacement because I can't return it to stock.
Sent from my Touchpad using Tapatalk
you can try gene pooles son tool, in the Dev section.
i recently got into rooting and setting up my phone for new roms but im still new at it. i ended up bricking my phone to the lg screen with the blue swipe across the screen. my computer will not register the driver to use recovery flasher. i need help. anyone wanna help out a noob?
Try using nvflash to revert back to 2.3.4 I can't give you a link but it's easy to find in the development section
jj_z1 said:
Try using nvflash to revert back to 2.3.4 I can't give you a link but it's easy to find in the development section
Click to expand...
Click to collapse
i tried to use nv flash but no matter what i do i cant seem to make my phone register in the usb driver. if i could make it register i would be able to flash it then.
Did you try using the kdz updater? it's a tricky method, but if you follow the guide properly you should be able to get it going
jj_z1 said:
Did you try using the kdz updater? it's a tricky method, but if you follow the guide properly you should be able to get it going
Click to expand...
Click to collapse
i dont know how to go about it.
laroacha said:
i dont know how to go about it.
Click to expand...
Click to collapse
Never mind my last post, you need to be able to boot into a rom to use kdz updater, it's been a while since I had to do this kind of thing.
I'm pretty sure you only soft bricked your phone (i.e. it still turns on) and the only way, that I know of, is to use nvflash. I've had the same problem before, there could be many things that are causing the phone to not be recognized by your computer. Follow this guide http://forum.xda-developers.com/showthread.php?p=17258229
when you plug the usb into your phone make sure the audio on you computer is loud enough for you to hear that "usb recognized" sound. If you don't hear it, or it does not get recognized, try using a different usb port on your computer, believe me that actually worked for me a couple of times. Also, make sure you follow the steps very carefully because if you use the wrong button combination, or release the buttons too early, it won't work.
I wish I could help you more, but that's all i've got.
Good luck, and if by any chance you get it fixed, don't try to root your phone using any root tools, simply nvflash cwm recovery and flash your choice of a custom rom, that will automatically give you root privileges.
jj_z1 said:
Never mind my last post, you need to be able to boot into a rom to use kdz updater, it's been a while since I had to do this kind of thing.
I'm pretty sure you only soft bricked your phone (i.e. it still turns on) and the only way, that I know of, is to use nvflash. I've had the same problem before, there could be many things that are causing the phone to not be recognized by your computer. Follow this guide http://forum.xda-developers.com/showthread.php?p=17258229
when you plug the usb into your phone make sure the audio on you computer is loud enough for you to hear that "usb recognized" sound. If you don't hear it, or it does not get recognized, try using a different usb port on your computer, believe me that actually worked for me a couple of times. Also, make sure you follow the steps very carefully because if you use the wrong button combination, or release the buttons too early, it won't work.
I wish I could help you more, but that's all i've got.
Good luck, and if by any chance you get it fixed, don't try to root your phone using any root tools, simply nvflash cwm recovery and flash your choice of a custom rom, that will automatically give you root privileges.
Click to expand...
Click to collapse
every time i look at my apx driver it always tells me to troubleshoot but it always says driver not installed. ive downloaded the same driver in different posts just to make sure but nothing helps. Wireless shops are useless. I live in vegas and there isnt a single store with a person smart enough to figure it out.lol. ive given my phone up for days at a time to shops who brag about "WE CAN FIX ANYTHING" they lied. well i guess im going to search for a few more hours on here to get some kind of lead. thanks for the help. if you kknow anything else or figure something out i would appreciate the help.
Have you tried this stuff?
http://forum.xda-developers.com/showthread.php?t=1619932
It sounds to me like your pc's jacked up the driver somehow. Try plugging in the phone with the battery out and holding all 3 buttons, go into your device manager and uninstall all the USB drivers. Then reboot and try following the apx driver installation procedure again.
Sorry if you tried all this stuff a million times already.
I would say the two things that I would focus on would be to first fix the drivers on your computer. I downloaded mine from the LG website. Next is to flash CWM Recovery so you can flash a rooted ROM to your phone. I would go back to the thread where you got the instructions to start flashing and ask the same questions but only after reading the whole thread. There the orig. developer might chime in and you'll have more specific answers focused on your specific issue.
It's true your phone isn't bricked and have patience and you'll get it fixed.
Sent from my LG-P999 using xda premium
superhero7 said:
I would say the two things that I would focus on would be to first fix the drivers on your computer. I downloaded mine from the LG website. Next is to flash CWM Recovery so you can flash a rooted ROM to your phone. I would go back to the thread where you got the instructions to start flashing and ask the same questions but only after reading the whole thread. There the orig. developer might chime in and you'll have more specific answers focused on your specific issue.
It's true your phone isn't bricked and have patience and you'll get it fixed.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
well i have all the drivers needed. and the computer is fine but the phone is not. i mean the pc doesnt quite read the phone right. with that being said i dont know how to flash cwm recovery to a phone my computer cant read. im running windows 7 64bit and all my usb drivers work fine.
CWM = Clockworkmod Recovery (everyone remember this is a newbie).
Important question: Did you do a backup before making any changes to your phone?
Also, try this: remove your phone's battery for 30 seconds. Put the battery back in. Press and hold the volume down button, then press and hold the power button. Hold both buttons. First you'll see the white LG screen, then wait, when you next see the blue LG screen wait ONE second (no longer) then release the buttons. Tell us what the phone does then and what the screen says.
Have you tried taking out your SIM card and micro SD card?
Usually right after I take them out and plug in my phone while holding volume up and volume down... it usually works after that.
Yup, that's my problem. No matter how many USB ports I tried it still wouldn't read it until I took out the SIM card and micro SD ;p.
Try this on for size...
laroacha said:
well i have all the drivers needed. and the computer is fine but the phone is not. i mean the pc doesnt quite read the phone right. with that being said i dont know how to flash cwm recovery to a phone my computer cant read. im running windows 7 64bit and all my usb drivers work fine.
Click to expand...
Click to collapse
Sounds like you are having the same the issues i was having with my phone why dont you try this..... First you have to flash a custom recovery image for your phone, follow all the procedures exactly then once you have flashed your CWM Recovery ( i. e. Clockworkmod recovery) Once you have installed that properly, you can now flash your new custom ROM and that should help to fully reboot your phone back to recovery for you to start using again....... hope that works for you.......just as it did for me have a good one!!... :fingers-crossed:
RVD1 said:
Sounds like you are having the same the issues i was having with my phone why dont you try this..... First you have to flash a custom recovery image for your phone, follow all the procedures exactly then once you have flashed your CWM Recovery ( i. e. Clockworkmod recovery) Once you have installed that properly, you can now flash your new custom ROM and that should help to fully reboot your phone back to recovery for you to start using again....... hope that works for you.......just as it did for me have a good one!!... :fingers-crossed:
Click to expand...
Click to collapse
He can't flash anything to his phone -__- that's the problem we are all trying to solve.
May sound stupid, but have you tried different cords? Maybe your USB cord is bad. Just a thought.
Sent from my LG-P999 using xda premium
@op can you give us screenshots of:
A: what your device manager looks like when you plug your phone in not in apx mode.
And
B: When it is in apx mode.
To do this: right click on my computer>properties>on left hand side, click on device manager. Hit print screen, open paint and tell it to paste. Save and upload here.
Sent from my LG-P999 using xda premium
EEngineer said:
CWM = Clockworkmod Recovery (everyone remember this is a newbie).
Important question: Did you do a backup before making any changes to your phone?
Also, try this: remove your phone's battery for 30 seconds. Put the battery back in. Press and hold the volume down button, then press and hold the power button. Hold both buttons. First you'll see the white LG screen, then wait, when you next see the blue LG screen wait ONE second (no longer) then release the buttons. Tell us what the phone does then and what the screen says.
Click to expand...
Click to collapse
well i brought it to two shops and were both unsuccessful. wireless toyz and smart fix. i have it back and it goes to the lg screen. and instead of the second it flashes from black to a very dim gray back and forth. when i hold the power button along with the volume down it does a master reset and i can press the home button then it takes me to a screen to delete cache partition and what not and you move up and down with the volume keys but i cannot select anything. i think i really messed my phone up.
Somehow you got stock recovery. Google for howbto do a master reset, on devices like the nexus tablet at my work there's a series of steps needed to do a full reset/restore. Just booting into stock recovery may not give you the option. As well, please post those screen shots as I said earlier, this way the issue with the USB can be troubleshot and maybe we can get you a fully working phone with CWM.
Sent from my LG-P999 using xda premium
Волк said:
Somehow you got stock recovery. Google for howbto do a master reset, on devices like the nexus tablet at my work there's a series of steps needed to do a full reset/restore. Just booting into stock recovery may not give you the option. As well, please post those screen shots as I said earlier, this way the issue with the USB can be troubleshot and maybe we can get you a fully working phone with CWM.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
idk how to post screenshots of my phone without a camera.lol. im about ready to give up. its been way too long with not having a phone.
You hit the print screen button, open paint, and tell it to paste/paste from clipboard.
Sent from my LG-P999 using xda premium
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