Related
ive searched the forums but couldnt find anything helpful. so i have my captivate rooted and its on 2.2 fw. i load rom manager and it says the clockworkmod is loaded and i reboot to recovery but i get the android recovery 3e instead of the CWM. I try to apply the update.zip but of course the signature is not verified. i tried older versions but half of them are not loading. I also tried the 3e modified recovery installer but after it installs and runs rageagainstthecage it fails on stopping adb server. Any help would be great.
Thanks - MaDDaWg
EDIT: I foudn a way to manually redo the recover to run unsigned sigs. sorry for the post. feel free to delete!
I have sort of the opposite problem- I recently used CWM to upgrade a DX to the pre-rooted GB and all went swimingly except that just about everytime I reboot the phone, CWM turns on. From there, if I select reboot, it will reboot properly, but I can't get CWM to turn off. I had this same problem on another DX and I was able to go into Manage Apps, found the D2 Bootstrapper running, so I selected "Force Stop" and that resolved the problem, but on this particular phone, the D2 Bootstrapper is not listed in the running applications, so that resolution is a dead-end.
Thoughts greatly appreciated!
pstgh said:
I have sort of the opposite problem- I recently used CWM to upgrade a DX to the pre-rooted GB and all went swimingly except that just about everytime I reboot the phone, CWM turns on. From there, if I select reboot, it will reboot properly, but I can't get CWM to turn off. I had this same problem on another DX and I was able to go into Manage Apps, found the D2 Bootstrapper running, so I selected "Force Stop" and that resolved the problem, but on this particular phone, the D2 Bootstrapper is not listed in the running applications, so that resolution is a dead-end.
Thoughts greatly appreciated!
Click to expand...
Click to collapse
welcome to the captivate section. this isnt a DX section. we dont use bootstrappers here.
My situation is this: I went through all the instructions to flash Cyanogen to my NC and started out with the 7.1 stable build. Then later I flashed again, this time to 7.2. Everything is working fine. But I'm just finding that there are little quirks to the Nook Reader for Android that make me like the stock Nook Color better. So I decided to follow the instructions to flash back to stock.
However, when I booted into CWM from my sd card, I get the menu and can scroll around in it. But none of the menu options actually work. When I select an option all I get is the black hat with the circular orange arrow icon and nothing happens. I can't get to the menu where I'm supposed to wipe data etc. The backup function doesn't work either. the So I booted back into Cyanogen then used rom manager to tell it to reboot into recovery. Same result as booting from the SD card. I can get to the menu but nothing actually works. Back in CM7.2 again I used the option in ROM manager to back up the existing ROM. It rebooted into CWM and did the backup successfully, even though backup doesn't work if I try to do it directly from CWM.
Everything still works fine from CM7.2. It just seems to be CWM that's flaky whether I boot it from the device itself or from the SD card. Sending CWM a command from inside ROM manager does work. I've tried both backups and flashing a new CM7 version from there and it works.
Is it possible to get around this by using the install update from sd functionality in ROM manager to re-flash the B&N 1.4.1 ROM?
Are you using the “n” key to select the options in CWM? The black hat with the orange arrow comes up if you are pressing the power button to try to select an option
Yes, you can flash the 1.4.1 ROM from ROM Manager, just download the file from HERE so that it will keep CWM
GMPOWER said:
Are you using the “n” key to select the options in CWM? The black hat with the orange arrow comes up if you are pressing the power button to try to select an option
Yes, you can flash the 1.4.1 ROM from ROM Manager, just download the file from HERE so that it will keep CWM
Click to expand...
Click to collapse
D'oh.....ok, I didn't know that. But I could swear I used the power button when I was originally flashing CM7. But, if I can just do it from ROM manager, that's easier anyway.
Thanks!
Edit. Question: Is there anywhere else those files can be downloaded? Firefox was telling me the download time was predicted to be over 3 hours. Then it only got through 3.3 MB before crapping out. Trying it again now and its saying I'm downloading at 10 KB/sec. Uggg. Might be easier to just go with the SD card route afterall.
ratman6161 said:
D'oh.....ok, I didn't know that. But I could swear I used the power button when I was originally flashing CM7. But, if I can just do it from ROM manager, that's easier anyway.
Thanks!
Edit. Question: Is there anywhere else those files can be downloaded? Firefox was telling me the download time was predicted to be over 3 hours. Then it only got through 3.3 MB before crapping out. Trying it again now and its saying I'm downloading at 10 KB/sec. Uggg. Might be easier to just go with the SD card route afterall.
Click to expand...
Click to collapse
I put together my own version, give this a try, LINK
GMPOWER said:
I put together my own version, give this a try, LINK
Click to expand...
Click to collapse
I eventually got one of the other links to work. Flashed back to 1.4.1 from rom manager and it works like a charm. Thanks for the hel[p.
Ok, so, a few weeks ago I tried rooting my new Incredible S from Bell running 2.3.3
I was able to S-Off and then installed CM7. Problem was the phone app would make and receive calls, I just couldn't hear anything nor could the person on the other end. After trying to update my radio I gave up and I thought I went back to stock by installing RUU_Vivo_BellMobility_WWE_1.37.666.3_Radio_Radio_20.23.30.0802U_38.02.01.17_M_release_174461_signed.exe
Once I installed this everything seemed to work properly again although my signal seems crappy but being used to the iPhone I have no basis for comparison.
So last night I thought I'd try and root again and put CM7 back on. I turned off fastboot and rebooted. When the menu came up I was surprised to see I was still S-Off as I thought it would have reverted back to stock. Clearly I have no idea what I'm doing when it comes to Android.
Anyway, after I noticed I was s-off I copied su-3.0-efgh-signed.zip to the root of my SD and attempted to enter recovery mode but all I get is a small pic of my phone with an exclamation point through it.
What I'd like is to root this puppy and run CM7 (or if you have a better suggestion for a rom) and have my phone app work properly. Is there anyone that can point me in the right direction.
Thanks guys!!
christanya99 said:
Ok, so, a few weeks ago I tried rooting my new Incredible S from Bell running 2.3.3
I was able to S-Off and then installed CM7. Problem was the phone app would make and receive calls, I just couldn't hear anything nor could the person on the other end. After trying to update my radio I gave up and I thought I went back to stock by installing RUU_Vivo_BellMobility_WWE_1.37.666.3_Radio_Radio_20.23.30.0802U_38.02.01.17_M_release_174461_signed.exe
Once I installed this everything seemed to work properly again although my signal seems crappy but being used to the iPhone I have no basis for comparison.
So last night I thought I'd try and root again and put CM7 back on. I turned off fastboot and rebooted. When the menu came up I was surprised to see I was still S-Off as I thought it would have reverted back to stock. Clearly I have no idea what I'm doing when it comes to Android.
Anyway, after I noticed I was s-off I copied su-3.0-efgh-signed.zip to the root of my SD and attempted to enter recovery mode but all I get is a small pic of my phone with an exclamation point through it.
What I'd like is to root this puppy and run CM7 (or if you have a better suggestion for a rom) and have my phone app work properly. Is there anyone that can point me in the right direction.
Thanks guys!!
Click to expand...
Click to collapse
You need to reinstall ClockworkMod recovery. When you went back to stock, it overwrote ClockworkMod recovery with the stock HTC recovery.
Ok, will give it a shot. Thanks!
Once I do that, should I be able to flash CM7? The radio is what's really gonna confuse me though.
Just tried reinstalling clockwork recovery and I get the same thing, pic of phone with red exclamation. I have to remove the battery to reboot.
Could the problem be that I need to go back to stock completely and then start from scratch??
christanya99 said:
Just tried reinstalling clockwork recovery and I get the same thing, pic of phone with red exclamation. I have to remove the battery to reboot.
Could the problem be that I need to go back to stock completely and then start from scratch??
Click to expand...
Click to collapse
What method are you using to try and install CWM?
I stuck it on the root of my sd, I boot into the menu and select recovery. That's when I get the exclamation point.
christanya99 said:
I stuck it on the root of my sd, I boot into the menu and select recovery. That's when I get the exclamation point.
Click to expand...
Click to collapse
You will need to either install CWM using a PG32IMG.zip file method or flash the image in FASTBOOT USB mode. You cannot flash CWM using the standard HTC recovery.
Try following STEPS 4 through 9 from the following post:
http://forum.xda-developers.com/showthread.php?t=1337105
[SOLVED -- Read my last post]
Posting on forum was my last resource, but I've tried literately almost everything I can possible find.
I already bricked my phone and had to unbrick, do everything (update firmware etc) all over again.
I am at a point where I am afraid to do something new to my phone now without knowing what they are...
Please bare with me, I am not familiar with exactly what flashing is or whatnot, I just followed the instructions and got where I am....
K, recently I decided to wipe my phone CLEAN and update to new CyanogenMod 9 from factory mode.
So, I have Captivate, I897. It was ECLARE with 2.1 firmware.
I have updated to 2.3.5 (Gingerbread [I897UCKJ2]), Rooted.
I had to Flash BACK to KK4_stock_kernel.tar for me to use WIFI again because I had issue after Rooting my phone, I couldnt access the WIFI.
I installed Clockwork mod (Free version).
My goal is to install CyanogenMod 9, and part of the process requires me to enter the CMW Recovery Mod.
I dont even know what this looks like, but all I know is whenever I boot my phone, after the AT&T logo animation it seems to go into this "messed up" screen, where as if my phone is broken. Stays there for 3 seconds and then continues to boot back to its OS.
In ROM manager, it says Flash ClockworkMod Recovery (You must have the clockworkmod recovery installed to flash and restore ROMs!)
Another option within ROM manager is, Reboot into Recovery (Boot into Recovery mode for manual management.), which if I do access it, it takes me back to that AT&T logo animation and that "messed up" screen again, but this time it stays there. Where all kinds of colored pixels are on my screen as if my screen is broken. It will only continue to boot back to my OS if I press power button or some sort.
Im guessing that's my Recovery Mod, which my phone for some reason cannot see?
So I tried "Download ROM (Upgrade to ROM Manager (premium) to access the full list of ROMs!", hoping this may cure that messed up screen effect, which I think is the Recovery Mod for all I know... When I click to install, it gives me Confirm Phone Models. None are my phone model for me to install.. (It only gives me Google Nexus S / Google Nexus S 4G / Samsung Epic4G / Samsung GalaxyS i9000).
Earlier, I was looking at this, http://forum.xda-developers.com/showthread.php?t=1127578
which is a way to fix recovery mod(?) But I have NO idea how to even install those files... Maybe not the .tar file but the other one.
Please help? Am I the only one experiencing this kind of problem? Couldnt find anywhere else on youtube / google / forum..
Thank you VERY much in advance, really appreciate it..
-Dan.
danroh said:
I had to Flash BACK to KK4_stock_kernel.tar for me to use WIFI again because I had issue after Rooting my phone, I couldnt access the WIFI.
-Dan.
Click to expand...
Click to collapse
This is your likely problem right here. The Kernel that is installed during the rooting process and typically when you install custom roms is what is responsible for installing and therefor you being able to access the CWM recovery. Flashing back to the stock kernel likely messed things up for you.
http://forum.xda-developers.com/showthread.php?t=1300843
Now if you follow that link it will take you to several one click options for flashing your phone to stock gingerbread but with a kernel containing CWM. Also keep in mind that it is possible you could have wifi issues if you've had them in the past, but if your goal is to get to CM9 just ignore the wifi for the time it shouldn't be an isuse in the end.
Hey OP,
See this.... TRusselo's Flashing Guide
Sent from my SAMSUNG-SGH-I897 using xda premium
You need Gingerbread bootloaders.
Thanks guys! I figured out the problem and solved it!
Like you guys said, I didnt have the bootloader. The gingerbread I installed was the no bootloader version. After reinstalling to the one with bootloader, I was able to access the recovery mod and that "rainbow screen" glitch was no more.
Thank you!
A couple days ago I decided to load the new Safestrap Hashcode linked to. Everything went very well, and I have been running Maverick 4.5 in slot 2 as my daily driver. I was able to get back into Safestrap using the menu button. I also loaded Gummybear ICS into Slot 3, but went back to Maverick.
Yesterday I was going to go back into Safestrap and switch to the Gummybear/slot 3 rom to check it out.
I can't get back into Safestrap at all. I am stuck in the Maverick 4.5 rom.
One thing I did notice and do not understand: When I use Titanium Backup or the Reboot Widget to "Reboot into Recovery", I get a Yellow Triangle with an Exclamation Mark and the Android guy.
mhelm23 said:
One thing I did notice and do not understand: When I use Titanium Backup or the Reboot Widget to "Reboot into Recovery", I get a Yellow Triangle with an Exclamation Mark and the Android guy.
Click to expand...
Click to collapse
That's the stock Droid 3 recovery. Using a reboot recovery will lead to that, and will not allow Safestrap's bootloader to intercept the boot and activate Safestrap recovery.
I haven't tried running Safestrap 3.05 myself, since it's still not official, but I do know that you cannot reboot recovery as you describe to to get into Safestrap for any version of Safestrap.
mhelm23 said:
A couple days ago I decided to load the new Safestrap Hashcode linked to. Everything went very well, and I have been running Maverick 4.5 in slot 2 as my daily driver. I was able to get back into Safestrap using the menu button. I also loaded Gummybear ICS into Slot 3, but went back to Maverick.
Yesterday I was going to go back into Safestrap and switch to the Gummybear/slot 3 rom to check it out.
I can't get back into Safestrap at all. I am stuck in the Maverick 4.5 rom.
One thing I did notice and do not understand: When I use Titanium Backup or the Reboot Widget to "Reboot into Recovery", I get a Yellow Triangle with an Exclamation Mark and the Android guy.
Click to expand...
Click to collapse
thats the stock recovery
now. do you still get the boot menu splash page where it asks you to input the menu key or continue?
if so hit the menu many times or hit on the screen the hit menu for recovery image section, as it shoulod also work.
maybe my next question is silly or already tried, but have you tried to try it with the charger disconnected?
some times when my droid 3 is connected, the touch screen gets un responsive o registers more than input
hope this helps
I now have the same problem. I see the splash screen and it vibrates and reacts when I press the menu button, however it does not boot into safestrap v3.05.
From the JB topic it seems more people have this problem!
DoubleYouPee said:
I now have the same problem. I see the splash screen and it vibrates and reacts when I press the menu button, however it does not boot into safestrap v3.05.
From the JB topic it seems more people have this problem!
Click to expand...
Click to collapse
For those with trouble entering recovery with SS 3.05
The EASIEST and most DEPENDABLE way I've found to boot into the new SS 3.05 is;
Shutdown the phone
Slide open keyboard
Hold M and press the power button to boot the phone (still holding M, release when it boots the next step)
Immediately a menu pops up
Press Volume DOWN to highlight "BP Tools" (tap several times, be quick, if you wait too long, it'll automatically select what is highlighted)
Press Volume UP to select it.
Phone will reboot showing the M logo, then proceed into SS Recovery.
Skreelink said:
For those with trouble entering recovery with SS 3.05
The EASIEST and most DEPENDABLE way I've found to boot into the new SS 3.05 is;
Shutdown the phone
Slide open keyboard
Hold M and press the power button to boot the phone (still holding M, release when it boots the next step)
Immediately a menu pops up
Press Volume DOWN to highlight "BP Tools" (tap several times, be quick, if you wait too long, it'll automatically select what is highlighted)
Press Volume UP to select it.
Phone will reboot showing the M logo, then proceed into SS Recovery.
Click to expand...
Click to collapse
This did not work for me. It just hangs on the Motorola splash screen after choosing BP Tools. Just tried a few moments ago.
Also I haven't had my phone plugged in or charging.
Sent from my DROID3 using xda premium
mhelm23 said:
This did not work for me. It just hangs on the Motorola splash screen after choosing BP Tools. Just tried a few moments ago.
Also I haven't had my phone plugged in or charging.
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
Strange, I have tried it several times... worked each time... maybe try reinstalling safestrap 3.05? Back up what you can of course, stock should not be touched.
Skreelink said:
Strange, I have tried it several times... worked each time... maybe try reinstalling safestrap 3.05? Back up what you can of course, stock should not be touched.
Click to expand...
Click to collapse
Yea - I tried that too. I am really at a loss.
Sent from my DROID3 using xda premium
I am sittin in the same spot. Can't boot into recovery...
Sent from my DROID3 using xda app-developers app
Skreelink said:
For those with trouble entering recovery with SS 3.05
The EASIEST and most DEPENDABLE way I've found to boot into the new SS 3.05 is;
Shutdown the phone
Slide open keyboard
Hold M and press the power button to boot the phone (still holding M, release when it boots the next step)
Immediately a menu pops up
Press Volume DOWN to highlight "BP Tools" (tap several times, be quick, if you wait too long, it'll automatically select what is highlighted)
Press Volume UP to select it.
Phone will reboot showing the M logo, then proceed into SS Recovery.
Click to expand...
Click to collapse
Had this problem today after creating a rom slot and flashing a new rom, this worked for me however I had to try it a few times. Once I got into recovery I wiped the rom and rom slot and ss3 is working properly now. Not sure if this was a rom issue or ss3.
Sent from my DROID3 using XDA
i had the same problem. and a bootloop top...
i have complete install my droid everything is lost...
another question. my "new" droid has the build 860 and withe safetrap i installed 2 other system.
can i update the stock to 906 without loosing safetrap and the 2 new systems?
dabayer said:
i had the same problem. and a bootloop top...
i have complete install my droid everything is lost...
another question. my "new" droid has the build 860 and withe safetrap i installed 2 other system.
can i update the stock to 906 without loosing safetrap and the 2 new systems?
Click to expand...
Click to collapse
When you run the OTA update to 906, it will remove the Safestrap bootstrap and will unroot as well. However, you can reroot with Motofail, then run the Safestrap app again to install recovery, and you slots *should* still be there. Perhaps making a backup of each slot before running the OTA would be smart.
doogald said:
When you run the OTA update to 906, it will remove the Safestrap bootstrap and will unroot as well. However, you can reroot with Motofail, then run the Safestrap app again to install recovery, and you slots *should* still be there. Perhaps making a backup of each slot before running the OTA would be smart.
Click to expand...
Click to collapse
i dont like the word "should"
ok i try to save the files in safetrap and try an OTA. yesterday the ota didn't run but i think i have to wait longer thar it starts the installation than the 10 minutes...
The slots are all stored on the internal storage (the mount point /sdcard) on the phone, so as long as you don't format internal storage, they should stay there.
I should note that I have never tried installing the OTA with safestrap 3.05 installed - I did it with 1.08. Actually, you may want to activate the stock slot, go into the safestrap app and uninstall recovery, and then try running the OTA. It's possible that the OTA will balk with a custom recovery installed - I don't remember, and, like I said, I never tried with Safestrap 3.05 installed.
You can also download the OTA, copy it to an external SD card, and manually run the update from stock recovery. See this thread: http://forum.xda-developers.com/showthread.php?t=1643521
[edit] Sorry - that link is for an update from 890 to 906. I forgot that you were not on 890. Sorry about that...
I had almost the same problem with my phone, the diference is that mine got stuck on non safe system (Stock ROM). Initializing the phone with th Android Recovery (Turning on with the key "m" pressed down) and choosing BP Tools doesn't worked.
- Phone: Milestone 3 XT860 (Brazilian Droid 3)
- Carrier: Vivo
- Current ROM: Stock 2.3.5 - 5.2.440