[Q] Help with rooting/romming - Captivate Q&A, Help & Troubleshooting

Hi, everyone.
I am trying to install a rom on a Samsung Captivate and having some, but not total, success.
I used the super one-click method to root, but I may have messed it up; I unplugged it too soon, when it appeared to hang pushing busybox.
However, when I rebooted the phone, it had superuser. I installed both ROM manager, one-click lag fix, and titanium backup from the market, and opened the applications. In all instances, I had no problem granting superuser permissions. In Titanium, it showed I needed to have usb debugging checked (which I had), and third-party applications (which I can't find in the menu).
However, when I ran ROM manager, I flashed Clockwork, and everything seemed to go all right, with no errors or warnings, but it won't actually boot into the Clockwork recovery. I can only get into the stock (blue) recovery, with a handful of options.
Fearful that I messed up the rooting by unplugging, I unrooted and then re-rooted. This time I didn't unplug anything, and it said it had success. The phone has a superuser app icon. It looks like superuser stuck around even after I wiped cache/data. I verified root via root checker, and it seems to be working correctly, and busy box is correctly installed. I installed ROM manager again and reran it and reflashed it, and it requested superuser, which I granted.
But then I reboot into recovery from ROM manager, and I'm pretty sure it's not clockwork. It's five options, all in blue.
I must be doing something wrong. Help, anyone?

Reinstall packages in normal recovery ... If you get an error saying signature verification failed, its because you're on froyo that has 3e recovery, search got 3e signature verification...
Also one click lag fix is pretty outdated and useless...

willentrekin said:
Hi, everyone.
I am trying to install a rom on a Samsung Captivate and having some, but not total, success.
I used the super one-click method to root, but I may have messed it up; I unplugged it too soon, when it appeared to hang pushing busybox.
However, when I rebooted the phone, it had superuser. I installed both ROM manager, one-click lag fix, and titanium backup from the market, and opened the applications. In all instances, I had no problem granting superuser permissions. In Titanium, it showed I needed to have usb debugging checked (which I had), and third-party applications (which I can't find in the menu).
However, when I ran ROM manager, I flashed Clockwork, and everything seemed to go all right, with no errors or warnings, but it won't actually boot into the Clockwork recovery. I can only get into the stock (blue) recovery, with a handful of options.
Fearful that I messed up the rooting by unplugging, I unrooted and then re-rooted. This time I didn't unplug anything, and it said it had success. The phone has a superuser app icon. It looks like superuser stuck around even after I wiped cache/data. I verified root via root checker, and it seems to be working correctly, and busy box is correctly installed. I installed ROM manager again and reran it and reflashed it, and it requested superuser, which I granted.
But then I reboot into recovery from ROM manager, and I'm pretty sure it's not clockwork. It's five options, all in blue.
I must be doing something wrong. Help, anyone?
Click to expand...
Click to collapse
Have you reinstalled package??
If you get signature failed after doing so - means u're on froyo 2.2 and you need 3e recovery fix. If not, u're on eclair 2.1 and flashing will be as easy as stealing from a baby

studacris said:
Reinstall packages in normal recovery ... If you get an error saying signature verification failed, its because you're on froyo that has 3e recovery, search got 3e signature verification...
Also one click lag fix is pretty outdated and useless...
Click to expand...
Click to collapse
OMG really?? you replied the same thing as I did I call JYNX!!

Beat ya! ;p

studacris said:
Reinstall packages in normal recovery ... If you get an error saying signature verification failed, its because you're on froyo that has 3e recovery, search got 3e signature verification...
Click to expand...
Click to collapse
That's exactly the error I'm getting. Searched it and working on it now. Will report back.
Also one click lag fix is pretty outdated and useless...
Click to expand...
Click to collapse
I figured so, but I was attempting to check root against all the sources I could, and I remembered there having been an 'unroot' option. But thanks for the confirmation. I figured it wasn't much use on a Captivate anyway.

Okay.
So I found two threads concerning the 3e recovery.
I tried the one here:
http://forum.xda-developers.com/showthread.php?t=833423
And it started okay but then failed to refind a temporary root and aborted. This was the second temporary root, though; the first time it checked, it was fine.
So I went here:
http://forum.xda-developers.com/showthread.php?t=909213
And extracted the file and downloaded Root Explorer, but my explorer only goes dev/block/delv. There's no other folder besides delv under block, so far as I can see. No st19.
Further help? Thanks so much in advance.

No, that instuction is to how to mount the system to r/w if using a terminal ... With root explorer that is a button on the top right so press that and move on to the next step and put the file in /system/bin. Reboot ... Bam!

studacris said:
No, that instuction is to how to mount the system to r/w if using a terminal ... With root explorer that is a button on the top right so press that and move on to the next step and put the file in /system/bin. Reboot ... Bam!
Click to expand...
Click to collapse
Okay. So, I moved the recovery file to my sdcard from my desktop, so it was on the phone. I ran root explorer, then first went into the sdcard to copy the file. After that, into system, then bin, which I mounted as r/w, and then pasted the recovery file there.
I got so excited I tried to do clockwork before rebooting. Now it gets to the update bit and seems about to work but sticks.
Do I need to wipe everything and retry? Just reboot?

reboot, you might want to paste the file in and reboot just for peace of mind ... also that downloaded update.zip with CWM could be bad, redownload it with rom mananger ... or take this one.

studacris said:
reboot, you might want to paste the file in and reboot just for peace of mind ... also that downloaded update.zip with CWM could be bad, redownload it with rom mananger ... or take this one.
Click to expand...
Click to collapse
Ha! Got it! It looked like it might bootloop for a second, and then it came up as stock recovery, and then I reinstalled packages and it came up with the green!
Wooo!
Thanks so much. Hopefully that'll be the last of the problems. Installing purplicious now. It looks like it's working.

Related

[Q] ROM Manager Signature Verification Failure

A few weeks ago I flashed the Cognition V2.2 ROM and everything was fine until it started getting twitchy a few days ago. I tried to use the ROM Manager to restore the backup that was created during the flash but I keep getting the same error message and the phone does not seem to go into the Clockwork Mod Recovery but stays in the Android system recovery. The message says that the whole-file signature has failed to verify and that the installation was aborted. Does anyone have any idea how I can get my phone back to normal?
gtcochran said:
A few weeks ago I flashed the Cognition V2.2 ROM and everything was fine until it started getting twitchy a few days ago. I tried to use the ROM Manager to restore the backup that was created during the flash but I keep getting the same error message and the phone does not seem to go into the Clockwork Mod Recovery but stays in the Android system recovery. The message says that the whole-file signature has failed to verify and that the installation was aborted. Does anyone have any idea how I can get my phone back to normal?
Click to expand...
Click to collapse
Common knowledge that the version of Cognition you are running is not supported by ROM Manager, it is 3e recovery and Clockwork needs 2e. You can update to the newer Cognition which has 2e recovery. I recommend you read the facts sheet befor flashing, the method you should use is Odin one click back to stock http://forum.xda-developers.com/showthread.php?t=731989, then master clear so that nothing is lingering from your previous setup, backup everything from your internal storage to your pc first, this will wipe everything from your internal, replace it after you finish Master clear. you should only replace the update.zip, ClockworkMod and your music, photo's and that stuff. Backup your apps using Titanium Backup.
Here's the link for the new Cognition http://forum.xda-developers.com/showthread.php?t=786532
So I tried what you recommended and got my phone back to the stock condition but I'm still not able to use ROM manager or flash another ROM. After I root the phone I install ROM Manager, flash it to the current edition and then try to reboot into recovery but when it gets to recovery it gives the following error message...
--Installing from package...
Finding update package...
Opening update package...
E:Can't open /cache/update.zip
(bad)
Installation aborted
Also the header of the screen states that I am in Android system recovery <2e>. If I am not mistaken, shouldn't I be in recovery <3e>? If so how do I get there? I've tried flashing the stock Kernel but that didn't work and I even installed the internal betas correctly but no cigar.
gtcochran said:
Also the header of the screen states that I am in Android system recovery <2e>. If I am not mistaken, shouldn't I be in recovery <3e>? If so how do I get there? I've tried flashing the stock Kernel but that didn't work and I even installed the internal betas correctly but no cigar.
Click to expand...
Click to collapse
did you really read Rhi's post?
in order to use rom manager (clockwork mod) you must be using 2e!
my brain hurts from all the lack of searching people in this forum seem to have a problem with
Pirateghost said:
did you really read Rhi's post?
in order to use rom manager (clockwork mod) you must be using 2e!
my brain hurts from all the lack of searching people in this forum seem to have a problem with
Click to expand...
Click to collapse
LOL, +1
Touche, but the error still remains. Does anyone have any positive ideas? Like I stated before, I still cannot put my phone into clockwork mod recovery.
gtcochran said:
Touche, but the error still remains. Does anyone have any positive ideas? Like I stated before, I still cannot put my phone into clockwork mod recovery.
Click to expand...
Click to collapse
so put it in download mode, and use ODIN one click back to stock...then leave it the hell alone....
Like I said, I've already used Odin. Everything is back to stock except for the Kernel and a stock kernel install with Odin doesn't seem to work. Odin says that the install passed but nothing changes on the phone itself. All things considered, the phone is stock but not capable of going into Clockwork Mod recovery.
gtcochran said:
Like I said, I've already used Odin. Everything is back to stock except for the Kernel and a stock kernel install with Odin doesn't seem to work. Odin says that the install passed but nothing changes on the phone itself. All things considered, the phone is stock but not capable of going into Clockwork Mod recovery.
Click to expand...
Click to collapse
When you go into stock recovery now is it version 2e or 3e?
gtcochran said:
Like I said, I've already used Odin. Everything is back to stock except for the Kernel and a stock kernel install with Odin doesn't seem to work. Odin says that the install passed but nothing changes on the phone itself. All things considered, the phone is stock but not capable of going into Clockwork Mod recovery.
Click to expand...
Click to collapse
if you used the one click back to stock then you are on the stock kernel.....what makes you think you are not on the stock kernel?
The recovery is 2e
I believe that the kernel is not stock because when I look at the phone information it says that the kernel is
2.6.29
[email protected] #2
I'm not sure that it is stock or not but my gut tells me that it isn't.
gtcochran said:
The recovery is 2e
I believe that the kernel is not stock because when I look at the phone information it says that the kernel is
2.6.29
[email protected] #2
I'm not sure that it is stock or not but my gut tells me that it isn't.
Click to expand...
Click to collapse
Rom manager will work just fine with 2e recovery. Just delete any update.zip files you have in your home directory - then open rom manager and reflash clockworkmod the cappy - then you should be good to go.
As for whether or not that is the stock kernel I am not sure, but how can you tell just by looking at it if you don't know which kernel is the stock one?
I've mounted my internal and external sd cards and removed any updates but it still gives the same error. After I used the odin one-click to flash the stock rom I used the master clear as recommended. Now, if I am not mistaken, shouldn't that erase all of my user data? I reinstalled my espn app so I could follow my football team and the app still remembered my preferences and favorites. This makes me think that the master clear did not finish the job. Thoughts?
gtcochran said:
I've mounted my internal and external sd cards and removed any updates but it still gives the same error. After I used the odin one-click to flash the stock rom I used the master clear as recommended. Now, if I am not mistaken, shouldn't that erase all of my user data? I reinstalled my espn app so I could follow my football team and the app still remembered my preferences and favorites. This makes me think that the master clear did not finish the job. Thoughts?
Click to expand...
Click to collapse
Master clear should've done that. If you are restoring your apps and settings using Titanium Backup then you are restoring user data which you should not do.
When you Master Clear is your device on and on the home screen, it needs to be. Don't Master Clear in Recovery mode or Download mode or it does nothing. Also you need to have debugging on.
2.6.29
[email protected] #2
That is the stock kernel. Just so you know if you are running stock with root you can simply place the update.zip from the Clockwork folder, you should have backed up before flashing and Master clear, back into your internal. ClockworkMod does fail on first attempt to flash sometimes, it happenned to me the first time I flashed it, the second time worked like a charm. Are you rooted? You need root to use ROM Manager and debugging should be on.
gtcochran said:
I've mounted my internal and external sd cards and removed any updates but it still gives the same error. After I used the odin one-click to flash the stock rom I used the master clear as recommended. Now, if I am not mistaken, shouldn't that erase all of my user data? I reinstalled my espn app so I could follow my football team and the app still remembered my preferences and favorites. This makes me think that the master clear did not finish the job. Thoughts?
Click to expand...
Click to collapse
After you deleted the update.zip then opened rom manager and flashed clockworkmod it should of put a new update.zip on your phone in your home directory - can you confirm that this is the case?
Also you may not have had a successful master clear - you may want to do it again then redo odin3 one click. Also if I am remembering correctly I believe you have the option to clear cache or user data or both in stock recovery you may want to try that as well.
It all works now. The issue was with the master clear. I guess that I did try to run it in the download mode. Thanks a million guys, i really appreciate it.
Maybe I was a bit premature on that. ROM Manager works beautifully but I cannot install updates or flash a custom ROM. The Manager was able to backup the system correctly and enter clockwork mod recovery but it cannot install the update. If the update is on the internal SD it says that...
E:Can't open /sdcard/update.zip
(bad)
and if the update is on the external SD it says that there is no such file or directory. Am I doing it wrong or is there still an underlying issue?
gtcochran said:
Maybe I was a bit premature on that. ROM Manager works beautifully but I cannot install updates or flash a custom ROM. The Manager was able to backup the system correctly and enter clockwork mod recovery but it cannot install the update. If the update is on the internal SD it says that...
E:Can't open /sdcard/update.zip
(bad)
and if the update is on the external SD it says that there is no such file or directory. Am I doing it wrong or is there still an underlying issue?
Click to expand...
Click to collapse
/sdcard/update.zip should only boot into clockwork recovery from stock recovery or boot to stock recovery from clockwork recovery if you flashed clockworkmod correctly from rom manager - and so long as you are not renaming any other files as update.zip after you flash clockworkmod recovery.
Which custom rom are you attempting to install?
I got it. The zip file was corrupted. Now, should I be able to boot into normal clockwork mod recovery with the Cognition 2.2 Beta 7 cuz when I try clockwork recovery it boots into normal recovery? I'm still a little hazy about all this.
gtcochran said:
I got it. The zip file was corrupted. Now, should I be able to boot into normal clockwork mod recovery with the Cognition 2.2 Beta 7 cuz when I try clockwork recovery it boots into normal recovery? I'm still a little hazy about all this.
Click to expand...
Click to collapse
When you first boot into recovery it should be stock recovery. While in stock recovery when you select reinstall packages it will reboot into clockwork recovery - if you flashed clockworkmod recovery correctly from rom manager and it put the appropriate update.zip into your home directory.
And just to note: don't be renaming any files as update.zip if you are using clockwork recovery to flash something.

"Install Failed" when booting into CWM?

So I had alot of issues rooting but im finally in, all rooted. Downloaded ROM Manager from the market and installed CWM. Says its successful, but when I manually reboot into CWM i get a error, so I cant install the 1.1 fix
Any ideas?
Really no one knows? This sucks!
This normally happens when recovery is not flashed properly. Did you try flashing again via Rom Manager? Also when you flash, does the screen show something like "Rom Manager has been granted super user permissions"?
ya, it flashes successfully through rom manager....
I think the problem is when I was trying to go back to 1.0.1 I flashed a restore through CWM. Then I whiped the /system and /data folders. The directions said to do this but I didnt realize I was supposed to do this BEFORE flashing not after. Basically I had no restore partition left so when I went and let it fail to boot 8x i got a error, and i had no OS. I ended up doing the N/Pwr, it restored, then i got a bootable CWM, booted into it and flashed the 1.0.1. But not everything seems, odd.
I can go into Rom Manager and install CWM fine, it says installation successful. But if I reboot into recovery, I get the error. I really need this fixed but im thinking it may be easier to just use a bootable CWM. Any ideas? I need to get 1.1 on here before I lose root
DroidHam said:
I think the problem is when I was trying to go back to 1.0.1 I flashed a restore through CWM. Then I whiped the /system and /data folders. The directions said to do this but I didnt realize I was supposed to do this BEFORE flashing not after. Basically I had no restore partition left so when I went and let it fail to boot 8x i got a error, and i had no OS. I ended up doing the N/Pwr, it restored, then i got a bootable CWM, booted into it and flashed the 1.0.1. But not everything seems, odd.
I can go into Rom Manager and install CWM fine, it says installation successful. But if I reboot into recovery, I get the error. I really need this fixed but im thinking it may be easier to just use a bootable CWM. Any ideas? I need to get 1.1 on here before I lose root
Click to expand...
Click to collapse
I fixed this by downloading the latest busybox from the market, installed it, then ran the "fix permissions" from Rom Manager. I then reinstalled the latest CWM, and it would allow me to reboot into recovery.

[Q] ClockworkMod: An error occurred while attempting to run privileged commands.

ClockworkMod: An error occurred while attempting to run privileged commands.
i've tried everything...that i know of or have read of so far...
i just cant get cwm to install
d1 rooted and unrooted thru super one click and z4root, rom manager uninstalled and redownloaded and reinstalled, wifi connected or 3g
su is current and shows list of other apps, tried permisions fix in rom manager too, just stuck w/ that same lousy error and cant install any roms...
some one please help me!!
-n
nutiket95 said:
ClockworkMod: An error occurred while attempting to run privileged commands.
i've tried everything...that i know of or have read of so far...
i just cant get cwm to install
d1 rooted and unrooted thru super one click and z4root, rom manager uninstalled and redownloaded and reinstalled, wifi connected or 3g
su is current and shows list of other apps, tried permisions fix in rom manager too, just stuck w/ that same lousy error and cant install any roms...
some one please help me!!
-n
Click to expand...
Click to collapse
You prolly fixed this already but in case someone else has this issue. Try installing Busybox from the market.
Same issue and won't boot into clockworkmod recovery
nutiket95 said:
ClockworkMod: An error occurred while attempting to run privileged commands.
i've tried everything...that i know of or have read of so far...
i just cant get cwm to install
d1 rooted and unrooted thru super one click and z4root, rom manager uninstalled and redownloaded and reinstalled, wifi connected or 3g
su is current and shows list of other apps, tried permisions fix in rom manager too, just stuck w/ that same lousy error and cant install any roms...
some one please help me!!
-n
Click to expand...
Click to collapse
I rooted my phone with eclair installed and used clockworkmod recovery with no issues until I one day wanted to go back to stock and attempted a restore of the backup I made right before flashing the OverStock ROM. The phone wouldn't boot, so finally got the Overstock to go back. Phone worked fine for the most part, but from then on to get into recovery mode, required shutting down and using button presses (Up/down vol/PWR button) and it would go in fine. Could never get Clockworkmod to go into recovery mode with a click. Saw that (finally) Samsung has published a Froyo update, so took back to stock eclair using ODIN3 so I could use Kies mini to update. Did a factory reset to remove all old info directories and data. Update went perfect, but want the option to use the rooted apps (Titanium backup and ClockworkMod--purchased apps) to play with my phone as I see fit. Used SuperOneClick to root phone and verified I can get superuser with using terminal emulator, successfully executing "su" command. Problem is I can't get into CWM recovery. Only get "Android system recovery <3e>". Tried uninstalling CWM and reinstalling. Re-Flashed CWM recovery and it lists version 2.5.1.2 as current and latest.
I obviously need CWM recovery to flash different ROMS, but wanted a current backup before starting. Can't get any further until I figure this out. Any help would be appreciated. I was a noob, just a month ago, but was feeling pretty confident until this happened. Guess I'm still a noob, but just a little more dangerous now. Thanks in advance.
Just noticed that I wasn't in a phone specific thread, so here's my phone details... Samsung Vibrant (T-Mobile).
CWM issues with Milestone
In the last update of the RomManager was added support for version ClockWorkMod 3.x for Milestone - but still unable to use the CWM as standard recovery.
Using another recovery as OR1.4 you can start CMW from the SD card - but that does not solve the problem of RomManager stay with completely limited functions.
The Rom Manager is having updates constantly and I think we have a working version for Milestone soon - but in part I'm upset to see that the Milestone is listed as a supported device - when in fact it is not.
I bought the full version of Rom Manager because I believe it is a great tool and I hope someday I can use all its functions.
I have the same problem. I use OpenRecovery for Sholes to do those things. I hope we can use those tools like a normal user even a day.

[Q] Rom Manager/ClockworkMod recovery - need help

I have installed Rom Manager (paid version), and clicked the "Install ClockworkMod Recovery" button.
It asks for the device - selected Samsung S Captivate (which is what my phone is).
It asks for (and gets) root, pops up a message saying that it has downloaded ClockWorkMod Recovery, then seems to do nothing else.
If I then click on Backup Current ROM, it presents a name for the backup (date and time), then re-boots the phone into recovery.
No backup happens, and the recovery is the Samsung one.
So the installation of ClockworkMod Recovery seems to have failed.
Tried several more times - same result. Tried installing recovery a few times too.
Looked at the filestore -- the clockworkmod recovery download is there.
Deleted Rom Manager, re-installed - tried again - same results.
Any suggestions???
PhilipPeake said:
I have installed Rom Manager (paid version), and clicked the "Install ClockworkMod Recovery" button.
It asks for the device - selected Samsung S Captivate (which is what my phone is).
It asks for (and gets) root, pops up a message saying that it has downloaded ClockWorkMod Recovery, then seems to do nothing else.
If I then click on Backup Current ROM, it presents a name for the backup (date and time), then re-boots the phone into recovery.
No backup happens, and the recovery is the Samsung one.
So the installation of ClockworkMod Recovery seems to have failed.
Tried several more times - same result. Tried installing recovery a few times too.
Looked at the filestore -- the clockworkmod recovery download is there.
Deleted Rom Manager, re-installed - tried again - same results.
Any suggestions???
Click to expand...
Click to collapse
First, you need to be rooted. If you are rooted already, when you get to the Samsung recovery, is it the 3e recovery? if so, you need to get around that first be reading here: http://forum.xda-developers.com/showthread.php?t=909213
Once you get around 3e recovery you can flash whatever you want. Report back, let us konw how it goes.
edit: oops, just noticed that you did say you have root when you mentioned you allowed root access for Rom Manager.
Reboot to Recovery and select "reinstall packages". --- u may have to do it twice, but then u should be in CWM Recovery... Unless u have the stock 3e recovery as stated above.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Ok - loaded the modified 3e recovery binary.
Seems to be working, because now when I boot into recovery I see:
-- Movi_check Start..||
checksum confirmation need_checksum[0]
Not need checksum confirmation
...
But still can't get clockworkmod recovery to load.
Tried loading an old version, followed by re-loading the current version.
Backup Current ROM ... and still see the Samsung recovery utils message,
and of course, no backup.
Ok -- lets try reinstall packages twice ...
Ok - that did it.
Thanks!!
As said in the post above your last one, you do have to select Reinstall packages twice to get into CWM. Are you selecting it twice?
edit: just saw your post above. glad you got it working.
Ok - now some random questions (for my education):
First, any idea why it might take TWO re-installs of packages for things to work?
It always makes me a bit nervous when repeating an operation has different effects. Software is supposed to be deterministic!
Next, I assume that installing clockworkmod recovery just replaces the "recovery" binary in /system/bin (?).
If so, why didn't (couldn't?) I just get hold of a single binary and drop it into /system/bin in place of the standard recovery binary?
PhilipPeake said:
Ok - now some random questions (for my education):
First, any idea why it might take TWO re-installs of packages for things to work?
It always makes me a bit nervous when repeating an operation has different effects. Software is supposed to be deterministic!
Next, I assume that installing clockworkmod recovery just replaces the "recovery" binary in /system/bin (?).
If so, why didn't (couldn't?) I just get hold of a single binary and drop it into /system/bin in place of the standard recovery binary?
Click to expand...
Click to collapse
As far as the re-installing packages twice, you should only have to do that once. now when you reboot to recovery, or 3-button boot to recovery it should go right to CWM.
And I have no idea about the single binary thing. I just followed instructions as you did to get it working. Hahaha!
Honesty on a forum -- I like that!
Just did a bit of poking around ... it doesn't replace the restore binary, looks like it uses that to load CWM -- if you issue a "reboot recovery" you end up in the standard recovery. If you run reboot into recovery from Rom Manager, you can see it loads the original recovery first, then jumps into CWM.
I suppose this is actually a good thing, because you always have the old recovery to fall back to.
Thanks a lot ... I would probably never have found the 3e restore replacement without that pointer.
Philip

[Q] SafeStrap not flashing roms correctly

So I've followed all the tutorials I could find. I've rooted, installed busybox (to make sure it really existed), installed safestrap (the official one from the blog) and can get into recovery just fine. I made sure I have the right phone version and I've never done any kind of bootstrap stuff on this phone before this.
However, when I switch to safe mode to try out some roms, it simply will not work. I've tried all three versions of Eclipse and one CM9 version, but once supposedly done flashing and told to reboot, it gets a blackscreen for a few seconds and restarts back to the dual-core pre-recovery screen. I've wiped, wiped, super wiped everything just like the various instructions tell me to, but nothing ever changes the blackscreen.
Switching it back to non-safe and rebooting works just fine, but I cannot get any custom safe-mode roms to boot up. Is there something else I should be doing that I missed?
I occasionally have issues with Safestrap when you choose to reboot, so I just power off and then power on - that always works. Initial boots do take some time, though more than a few minutes without animation is probably too much.
And, just to clarify, this is the Safestrap that I use: http://blog.hash-of-codes.com/downloads/safestrap/
But it's not that it takes time, it reboots the phone itself. It's not locking up like I've seen others say and requiring a battery pull. It just refuses to go on, instead more like a boot loop? But nothing appears to be going wrong and I can easily switch back to the base no-problem.
And yeah, that's the same one I'm using. Droid 3 v1.08 exactly from that site.
It's making me sad that I can't get this going
Edit: I went ahead and tried just powering it off, leaving it for a moment, and turning it back on. Still did the reboot thing
are you installing the rom and then wiping data?
if so try wiping data first then install rom then reboot..
ovelayer said:
are you installing the rom and then wiping data?
if so try wiping data first then install rom then reboot..
Click to expand...
Click to collapse
Yeah, tried both ways. Wipe data/factory and cache numerous times, install, nothing. Install then wipe, nothing. Wipe, install, wipe, nothing.
Is there an easy way to know for sure if it is even installing anything at all, like navigating to it using a root explorer?
Are you sure that the zip files you are loading are complete downloads? Generally you would receive error messages when installing if so, but you can try unzipping on your computer to see if they have errors. I always download ROM zips on my computer and transfer over (usually using the Dropbox app, but only because I don't want to bother with attaching, choosing USB storage mode, copying the files, unmounting the drives, choosing charge only.) But, if you are downloading the zips with your phone, try doing so instead with your computer, check the files sizes, and then transfer them over to the phone.
(Also, most/all/many of the CM9 zips require flashing a Google apps zip after flashing the ROM. That shouldn't prevent the phone from starting if you skip this step, but it will prevent you from having the market. Just FYI.)
I'd also try Maverick ROM to see if it has the same problem.
I've been running the stock 906 based ROM from Q9Nap here (the one marked Safestrap system), debloated by Pete Souza's script: http://forum.xda-developers.com/showthread.php?t=1554916
doogald said:
Are you sure that the zip files you are loading are complete downloads? Generally you would receive error messages when installing if so, but you can try unzipping on your computer to see if they have errors. I always download ROM zips on my computer and transfer over (usually using the Dropbox app, but only because I don't want to bother with attaching, choosing USB storage mode, copying the files, unmounting the drives, choosing charge only.) But, if you are downloading the zips with your phone, try doing so instead with your computer, check the files sizes, and then transfer them over to the phone.
(Also, most/all/many of the CM9 zips require flashing a Google apps zip after flashing the ROM. That shouldn't prevent the phone from starting if you skip this step, but it will prevent you from having the market. Just FYI.)
I'd also try Maverick ROM to see if it has the same problem.
I've been running the stock 906 based ROM from Q9Nap here (the one marked Safestrap system), debloated by Pete Souza's script: "no linkies for me"
Click to expand...
Click to collapse
I did as you suggested and tried unzipping the files on my computer (which was where I original downloaded them). They all unzipped fine without any errors, unfortunately. The chances of 4 full files being that way were slim, but I sorta hoped...
I'll try Maverick and the Safestrap stock after I get done downloading them.
Thanks everyone for trying to help.
Edit: Alright, I tried Maverick and it showed a prettier flash log, symlinked, all that, still reset itself after passing the recovery splash. Same with the 906 stock based. This time I also tried installing from internal and external SD just to test that.
I'll ask again, is there a specific folder I can get to just for my peace of mind where I can see where it is supposed to have installed these? Or is it in a area where a normal root explorer can't get to?
shinseitom said:
I did as you suggested and tried unzipping the files on my computer (which was where I original downloaded them). They all unzipped fine without any errors, unfortunately. The chances of 4 full files being that way were slim, but I sorta hoped...
I'll try Maverick and the Safestrap stock after I get done downloading them.
Thanks everyone for trying to help.
Edit: Alright, I tried Maverick and it showed a prettier flash log, symlinked, all that, still reset itself after passing the recovery splash. Same with the 906 stock based. This time I also tried installing from internal and external SD just to test that.
I'll ask again, is there a specific folder I can get to just for my peace of mind where I can see where it is supposed to have installed these? Or is it in a area where a normal root explorer can't get to?
Click to expand...
Click to collapse
wait a sec..
you unzipped them?
the zip files are not ment to be unzipped..
download the zip to your phone
go into safestrap and choose install zip then choose the zip
oh wait...duh you were just checking to see if they worked lol
use root explorer and navigate to system folder open the build.prop and see if there is a mention of the rom your trying to install..ie..version=mavrick or eclipse
I'm not finding any references to other roms anywhere in it. I did a search by eye, then a search for "version", "cm", and "mav" and didn't come up with anything relevant. Is that bad?
There are two other things that you can try, though I am not sure that they will help:
1. From non-safe, stock, run Safestrap and uninstall recovery. Restart to see that it does not intercept before the boot screen, then go back in and reinstall recovery from safestrap. Restart the phone to see if it is working. Then restart to Safestrap and try toggling safe mode and see if your flashes work.
2. One other thing to try (not sure if this will help, but...) is to (prior to flashing a ROM) go into the Mounts menu and format /system. Maybe the old system isn't being cleared out by the ROMs you are trying to flash? Then go install the zip, do a wipe data/factory reset and see if that works.
Just wondering if there is a benefit to Safestrap or Bootstrap and why?
I went with Safestrap... Is it just a style thing or is one better?
Not trying to be a jerk, but I have been scanning this post.
Any chance you have overlooked the step of "Toggle Safe System" from the recovery menu?
At the top of the menu it should say "Safe System is: Enabled"
Droidlyen said:
Just wondering if there is a benefit to Safestrap or Bootstrap and why?
I went with Safestrap... Is it just a style thing or is one better?
Click to expand...
Click to collapse
Safestrap is supposed to allow you to install a rom onto a safe "partition" of sorts, though that's not really what's going on. Anyway, it doesn't touch your stock rom so if something fails (like my flashing attempts) you're not in trouble.
SteveHebe said:
Not trying to be a jerk, but I have been scanning this post.
Any chance you have overlooked the step of "Toggle Safe System" from the recovery menu?
At the top of the menu it should say "Safe System is: Enabled"
Click to expand...
Click to collapse
Nah, I switch it every time. I'm not quite messing up that bad
Anyway, I might have to resort to bootstrap to see if that works. If not, well, I guess I'll be stuck on stock. Nothing so far mentioned in the thread has worked for me. Kinda sucks, since I have an Infuse that loves being flashed with anything I want to put on it without problems, unlike a friend's Infuse. Maybe its phone karma.

Categories

Resources