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.
Related
Hello everyone,
first off, I'm new to all this. Here's my situation,
I was trying to install a new ROM on my G1 and I found instructions on how to gain root access to my phone. I felt like I had followed the instructions but I can't seem to get the ROM installed on my phone. I downloaded Recovery Flasher and installed it. I chose "Backup recovery image" and then "Flash Cyanogen Recovery 1.4" and it all seemed fine, but then when I rebooted my phone and tried to install the new ROM it wouldn't let me. But I think I know what the problem was, I missed the step where I had to rename the folder of the ROM to "update." I went back to factory settings and tried to re-do the steps but this time, Recovery Flasher gives me the options to:
Download Recovery Image
Restore Backup Image
this confuses me because it's not the same as it was the first time I tried it. Does this mean my phone is already rooted? I tried to uninstall and install it again and same 2 options come up.
I know i was doing it right at first because I got all the correct screens that I saw on the instructions, but now I don't. I've been searching here and all over google to see if I can find an answer but I couldn't so I decided to make a thread to see if someone can help.
Thanks!
AFAIK the one-click method doesn't survive a full reboot, because when you reboot the OS it overflashes the recovery partition again with the original (unless you've flashed a new ROM)
Now your problem seems to be the "folder" bit. You do not unzip the ROM, you put, eg, "update-cm-4.0.4-signed.zip" on your SD card as-is. You also no longer need to rename it to use from this recovery partition.
I see,
well, when I tried it with update-cm-4.0.4 (that's what I was trying to install) it said that the file could not be found, and then I read that I'm supposed to change the file name to "update" and when I did that, it found it right away but it gave me the error "No Signature" (something along those lines) even though according to the place where I download it from, it is signed.
Should I just try to boot into recovery mode again and try it out again? I remember the very first time I tried it loaded the screen with a bunch of options, but now it just has 3, Boot Into Home, Wipe, and Apply SDcard zip, I might be wrong on the exact wording of those options but that's all I get...
and recommendations? Thanks for your response
nevermind, I got it to work! Thanks
Hi,
I'm researching flashing via CWR, ROM over ROM without flashing to Stock via ODIN. Specifically, I'm at Cog 3.02 with "base" Cognition Kernel/Modem thinking about going to Andromeda...both employ Voodoo/EXT4, so shouldn't need to disable lagfix (I think?)...
I read at this link (apologies for spaces, but I'm new so can't post actual links): h t t p : / / forum.xda-developers.com/showthread.php?t=900463
a spirited debate starting about page 4 that flashing to ODIN is effectively doubling your chances for a bad flash, and that recovering a bad flash via CWM is far easier (just try re-flash again...and again(?) until fail back to trying ODIN) than recovering a bad ODIN flash.
If that's true, what prep should I do first via CWR?
1. Andromeda says requires wipe, does ROM install do this or do I do it via CWR first (wipe data/factory reset in recovery)? How 'deep' is a wipe...what do I need to save prior to this?
2. Wipe Dalvik Cache and/or wipe cache partition?
3. Save /efs folder?
4. Aside from TiBu backup to PC, am I missing anything else to save? I forgot to save my Android ID on my first flash, so it's my understanding I can only get that back via flash to Stock...I'd prefer to only go to ODIN if I have to.
Another question I had was regarding nandroid. I made a nandroid backup right after flashing to Cog. Do I really even need this? Since I haven't changed kernel/modem, wouldn't I be better off just flashing my initial Cog zip file?
Finally thanks to all who make this site kick_ss. Connexion2005's videos are indispensable for a newbie like me. People actually answer questions here, and the Devs suceed in delivering onto us a wolf in (out of the box) sheep's clothing...something AT&T and Samsung have failed to do.
Cognition 3.02 is my first and only custom ROM and DG, you have literally saved me from making my phone a brick the old fashioned way: throwing it against a wall. Running flawlessly since Jan 17th...at the same time, I am eager to see what else is out there, ***safely*** as possible.
Thanks in advance.
Since they are both ext 4 you should be ok.
The rom wipes, I clear davlik cache before flash and after, but there our no good reason as to why
Efs files, do you use kies? If so you may want to back them up, if not don't worry, I have never backed then up
Odin flash is not needed but my opinion is you should know how to use odin prior to flashing. Why panic to figure it out if something goes wrong,?
NANDROID only needed if youare going back to cog and after you have flushed the rom you want to restore settings
I think I got everything you asked
Thank you.
So really just the Dalvik cache wipe in CWR prior to.
Kies...soooo failed ever getting that working, and don't seem to need it.
Yeah I actually flashed ODIN1 unnecessarily prior to my flash to Cog. I was at stock and somehow thought ADW would mess it up...rook. I have build 1006 so good to know ODIN's there if I need it.
Re: Nandroid, but if I kept the initial zip for my flash to Cog wouldn't I just use that? Or does Nandroid do better job of ensuring good flash back to what I have right now?
Not familiar with flushing...Would I be able to restore Nandroid directly on top of ROM I'm switching off of?
Thanks again.
OP,
You'd double the chance of failure if all else were equal. I don't have statistics, but I have no doubt that failures happen far more often with odin flashes, though.
1. Andromeda says requires wipe, does ROM install do this or do I do it via CWR first (wipe data/factory reset in recovery)? How 'deep' is a wipe...what do I need to save prior to this?
2. Wipe Dalvik Cache and/or wipe cache partition?
3. Save /efs folder?
4. Aside from TiBu backup to PC, am I missing anything else to save? I forgot to save my Android ID on my first flash, so it's my understanding I can only get that back via flash to Stock...I'd prefer to only go to ODIN if I have to.
Click to expand...
Click to collapse
The ROM install script does the wipe. This simply means all your apps and data will be erased (your pictures and anything on the internal and any external sdcard will not be deleted).
I never wipe the dalvik cache or cache partition before flashing. I only do that if I'm having issues like FCs (sometimes happens after a bad theme install, for example).
You probably should have backed up /efs before flashing anything, but that's not to say a backup now isn't a good idea. You only need to do this once.
If I recall, you do need to flash 2.1 to get the ID back. I'm not 100% sure there isn't another way.
WRT the nadroid backup, you don't really need it. What I do is keep 2 or 3 good CWM flashable ROMs and the CWM update.zip on my sdcard in case of problems. I also keep TiBU backup of my stuff there (which I also occasionally backup to my PC just in case my sdcard gets wiped for some reason).
One thing I would suggest is to be sure you have working button combos in case you ever need download mode (hopefully you never will, but it's always possible). If you don't have that, there is a clockwork flashable fix or you could just flash cognition or perception once and then flash whatever you want over them (you can do both flashes all without ever leaving recovery). That should fix the button combos since DG's ROMs include a good sbl.bin (I'm not a fan of that inclusion, but it is useful in this case). Since you are running Cog, I assume your download mode is already working.
Thanks opcow.
Yeah I made sure I could get into d/l and recovery mode with button combos before I even rooted.
So would you ever use a Nandroid backup if you added a different kernel/modem to a ROM? Or would you just go back to the initial zip and SGS Kernel to flash kernel/modem? I haven't done kernel flash...yet...
Madtowndave said:
Thanks opcow.
Yeah I made sure I could get into d/l and recovery mode with button combos before I even rooted.
So would you ever use a Nandroid backup if you added a different kernel/modem to a ROM? Or would you just go back to the initial zip and SGS Kernel to flash kernel/modem? I haven't done kernel flash...yet...
Click to expand...
Click to collapse
If the ROM you were running when you backed up is compatible with the new kernel then I don't see why there would be a problem. I don't do it, myself, but I'm not sure why. Maybe it's because I have the paid TiBU and I just use that.
Thanks again...
Yeah I bought full TiBu, so obviously that should work for the apps/data.
Did some more digging tonight and apparently Nandroid backup is ROM only, not Kernel...So seemingly would need to be on same Kernel at least to do proper Nandroid restore.
...that being the case, I guess I don't understand why people stress importance of running a Nandroid prior to and/or post ROM flash...am I missing something?
If you like a rom and set everything up but want to try another doing a nandroid allows you to restore once you flash the rom again.
Also good to run nandroid on new flash, so if you play with themes and something goes wrong you can restore
That makes sense.
Showing me newbie-ness since I haven't played around with themes yet...
...Figured I'd at least get 2nd ROM flash out the shoot before playing with kernels, modems or themes...
This thread is helpful for me. I appreciate your time.
This is along the lines of the question that I was going to post so figured would ask here. I too am considering trying out the new Andromeda. I am currently using Cog 3.04 and want to test out the new Andromeda. The TiBu I have right now is from when i was on stock as I just recently purchased this and Cog was my first flash.. Would i want to continue to use that backup when i flash to andromeda, or would it be better to run a full backup with tibu while cog is on there and then flash to andromeda and use the cog backup??
also,, from above, i could possibly just skip the step with odin and go straight to andromeda? or do I need to run odin and put it back to stock before going over to andromeda?
thanks
zug
Hey Zug,
Just flashed andromeda last night via method outlined above...did not revert to stock at all (no odin). Only issue thus far is market only showing very few installed apps under 'My Apps', but I think this is a common issue. Will research solution tonight (I did have some issues getting back all apps from TiBu, but after I restored missing apps twice and rebooted a few times they all appear to be back). Also my simi clock widget comes and goes, not sure why...might clear dalvik cache to see if that helps.
Regarding TiBu, it saves apps and data. It is not ROM specific...you just back it up, then after you flash new ROM you restore missing apps with data (do NOT restore system data).
EDIT: Resolved the My Apps Market issue (only a few were showing after flash) by going to Settings, Applications, Manage, go to Market, Clear Data, reboot. Search is my friend.
i897 running Andromeda 2.0
Thanks Madtowndave.. i might give that a try.. so, since my phone is rooted and what not, i can just go to the guide and start at the portion about puting the new rom on the sd card, rebooting it and what not in recovery and select that zip and flash it right ? (well condensed version of course) and it should all be good?? guessing if this fails can always use the odin and wipe it and go back?
since i added a few new apps, guessing then that i should use tibu and go ahead and reback up everything since this rom does the master clear and then reload them right?? and hate to ask.. but how do I do the nandroid? newbie still to android and i know that just backs up the rom, but is it a app to dl from market? was fishing around in phone and didnt quite see it yet. .but figured i would do a nandroid in case i want to go back to cog.. this smart?
thnx again
zug
I think most of your questions are answered by others in this thread...
One thing I noticed last night is that I only got red (voodoo) cwm recovery menu via 3 button or long press power and reboot to recovery...when I rebooted to recovery via ROM Manager, I got the green cwm recovery menu. Not sure if this matters, but in another forum (on Vibrant phone, our sgs cousin), they said to flash ROM via the red voodoo cwm menu (since cog and andromeda both employ voodoo you can leave it enabled).
Nandroid backup you can do either from ROM manager or in cwm recovery...
Also andromeda wipes the system data, not a master clear...your data on 16 gig internal memory should not be affected, but is very good idea to backup everything to pc per the flash custom ROM guide.
i897 running Andromeda 2.0
Thanks again madtown.. going to give it a try now.. as andromeda just finished DL'ing
Good luck, hope it goes smooth for you as it seemingly has for me...Feel like a bit of a heretic for not flashing to odin first...maybe I'm just lucky.
i897 running Andromeda 2.0
hmm. ok. .so did the reboot to recovery and installed andromeda.. did it take a tad bit for yours to boot into the phone portion after it got to the andromeda screen?? mine seemed like it was hanging and was about to worry.. but finally booted in.. so figured would see if yours did too? .. gonna test stuff out now and restore tibu
Yeah, did for me too...and yes I was worried. Pretty sure this is very normal on first boot into new ROM in general. Like I said, TiBu was a bit cranky for me and required 2 restores and reboots...
Really enjoying this ROM, btw.
i897 running Andromeda 2.0
yeh.. im still doing the install from tibu (getting paid version after tomorrow since payday since im hating have to select install for every app ) .. and then will reboot and test .. though one thing ive noticed that is diff from the video is the lock screen.. in his review it was the lock button and he swiped it up.. mine is set to a puzzle piece by default?? any idea??
edit.. k mine was a 1st time go for apps restored with tibu .this is pretty nice.. it does appear to be a lot faster/smoother than cog so far.. though the Keep the lights on app should keep my bottom buttons on all the time right? least thats what i thought i was from the video and mine seem to still fade out.. even though i hit the app and it said it was enabled..
changing unlock is in settings, display...
Dunno about lights, mine just worked. Make sure service started and reboot I guess.
i897 running Andromeda 2.0
ok.. that was what it was for the lock part.. thnx .. didnt know that was there for those 4 choices.. thought only could do the none, pattern, pw etc..
everything went fine until i decided to load my contacts/sms etc from tibu.. now when i rebooted to add them, i keep getting the message "Sorry, The application Swype (processcom.swype.android.inputmethod) has stopped unexpectedly.. please try again" constantly getting things like that about swype.. any idea what happened or what i need to do?
edit.. sucked it up and re-flashed ;( will just sync contacts and deal with the ones missing for now ;(
I read as much as I can about installation of a custom ROM. I think I'm confident enough to do it now, but I just want someone to review these steps before I start.
I have a Rogers I896 currently running the stock froyo that I upgraded via Kies with a build 10.10.
Because this is on a build 10.10 I can't follow the steps vertabim with the guide in the android development forum.
1. Root with SuperOneClick
2. Titanium Backup
3. Use Odin3 v1.7 or later to restore to stock with this http://forum.xda-developers.com/showthread.php?t=905042 and the 512 pit file. (I understand this is unnecessary as I'm already stock, but in case I need to revert back to stock from a custom ROM, this is what I'll do)
4. Reroot with SuperOneClick
5. Get the ROM and put it in the root of the phone
6. Download ROM Manager and install Clockwork Recovery
7. Boot into recovery and install zip from SD card and choose the zip file that I downloaded.
8. Titanium Backup to restore
Please let me know if I'm missing something. I think I read something about Nandroid backup somewhere in the forums. I'm not exactly sure what that is and it didn't really say that in the guide. Should I do that and how do I perform that?
I'm thinking about installing either Paragon, Serendipity, or di11i. Perhaps someone can also maybe list some differences, issues, pros and cons about these ROMs.
Thanks in advance!
your steps are good enough for you to flash to a new rom.
You may have trouble with installing Clockwork. If you do, follow this link.
Also, once you reboot into clockwork, remember to do a backup of your current ROM and move it and your TiBu backups to your HD. Clearing your cache before you install your new ROM isn't a bad idea either
Goodluck!
Is clearing cache done in the clockwork recovery? I notice an option for "clear download cache" from Rom manager. Is that the same thing?
integrasaurus said:
You may have trouble with installing Clockwork. If you do, follow this link.
Also, once you reboot into clockwork, remember to do a backup of your current ROM and move it and your TiBu backups to your HD. Clearing your cache before you install your new ROM isn't a bad idea either
Goodluck!
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I896 using XDA App
likiud said:
Is clearing cache done in the clockwork recovery? I notice an option for "clear download cache" from Rom manager. Is that the same thing?
I do not think "clear cache" is necessary when you install a new rom, since most of rom will format the related partitions first. You can clear the dalvik cache in the cwm.
A master clear is recommended since it will reset your phone to factory default and delete all the data in your built-in sdcard.
Click to expand...
Click to collapse
mengbo said:
likiud said:
Is clearing cache done in the clockwork recovery? I notice an option for "clear download cache" from Rom manager. Is that the same thing?
I do not think "clear cache" is necessary when you install a new rom, since most of rom will format the related partitions first. You can clear the dalvik cache in the cwm.
A master clear is recommended since it will reset your phone to factory default and delete all the data in your built-in sdcard.
Click to expand...
Click to collapse
It doesn't hurt AFAIK. I do notice after restoring apps with TiBu some apps require you to clear their cache in order to work properly, so I do it as a preventative measure.
Another tip: do NOT restore all system data with TiBu after you flash!
Click to expand...
Click to collapse
I started on Rogers stock 2.2.
Used superoneclick to root. Installed rom manager. Used a script to modify my recovery 3e file. Rebooted into recovery. Flashed cwm. Installed my custom rom.
Pretty awesome.
Sent from my SGH-i896
Hey I don’t mean to hijack/bump the thread but I’ve got an I896 which I’m attempting to flash a custom ROM onto, but I’m a complete phone newbie and could use some assistance when it comes to clarifying some instructions. This thread seemed to be the most “laid out” instruction guide for the I896 which I could find.
Currently my phone is running 2.2 Froyo / I896UXJL1 / Kernel 2.6.32.9 which I got via Kies early January when the update was released by Rogers.
I downloaded SuperOneClick 1.7 and rooted it without problems, but that’s as far as I’m clear/comfortable.
1. Do I need to use Odin (http://forum.xda-developers.com/showthread.php?t=905042) to restore to stock? Since I’m on the default Rogers technically that is already stock, no? Can I simply continue on from where I am?
a. If I don’t need to use Odin, do I need to make a backup with titanium?
2. Does step 6 of the OP’s list simply involve hitting the “Flash ClockworkMod Recovery” option in ROM Manager v3.0.1.0?
3. After that is it simply a matter of downloading my ROM of choice (Serendipity 5.12) and putting the .zip into my root folder, booting into recovery via the “Reboot into Recovery” option in ROM Manager, and then selecting to install the ROM .zip file?
4. Is my above three points everything I need to know or is there anything else I should know/be considered?
Also, when rooting I simply turned USB debugging on, ran the two .exe’s in order and then hit root after plugging in my phone. Was I supposed to go into download mode or anything or is that only for other modes of rooting (I have superuser installed and titanium backup was able to get root access so I assume my phone rooted properly).
That being said, I’ve read a ton of threads and a ton of stickies but things tend to seem either old/outdated or focusing on the AT&T i897, with there being limited information on a newbie friendly “explain all” way from A to B for the i896, unless I missed it. Some mention rooting with X, and using path ABC to root/flash a custom rom, and others mention rooting with Z and using patch DEF to do the same; all of which have left me feeling uneasy about flashing. ><
I'd be more then happy to provide any information in which I may have left out, and would appreciate any help I can get as I'm more then enthusiastic about flashing my first custom ROM but would like have the knowledge to do it right instead of being left with a brick. Yes, I know it seems almost all "bricked" captivates are unbrickable, though I would prefer to avoid that road at all costs either way haha.
mengbo said:
Another tip: do NOT restore all system data with TiBu after you flash!
Click to expand...
Click to collapse
I'm curious to know why not to restore system data?
Is "missing apps with data" ok to restore?
Restoring system data messes things up. Restore "missing apps with data" only. no system data.
If you restore system+data your home screen will fill up with force closes faster than you can clear them out, I know this Because I did it...twice, this is where my aww.W.T.F? sig came from. Don't panic if this noobish brain fart happens to you, just re-flash the rom and only restore missing apps+data as studacris said and enjoy.
I apologize if this has been covered already, but the search feature finds more noise than signal and I just don't see it.
I have safestrap on my xt860 with cm9 on the safe side of things, and I have a messed up and broken "stock" on the unsafe side. I'm pretty happy with cm9 in general, however there are still some known limitations, so I'm thinking of putting something else on the non safe side. Obviously I'd rather not break cm9 in the process.
Is doing this as simple as switching back to non safe and flashing the zip for what I want to try? Or is it more complicated than that?
You got to put back bootstrap. I think though that safe mode backs up to your internal storage so you should be good.
Sent from my XT862 using XDA
I believe that, when you have switched into non-safe mode, safestrap will not allow you to select the "install zip from sdcard" menu option. I am running safestrap 1.08d tweaked and just tried to do it. It says ".zip install is only available while safe System is enabled."
I don't think rick has gotten non safe flashing functional on any version.
To the op, make a backup of just safe rom, then switch to you non safe, uninstall safestrap recovery, install bootstrap, flash, uninstall bootstrap(you can't do the recovery part, but safestrap install script should clean that out), then reinstall safestrap recovery, and when you switch back to safe you can restore your backup
That's how I do it anyways
Sent from my XT860 using xda premium
Endoroid said:
To the op, make a backup of just safe rom, then switch to you non safe, uninstall safestrap recovery, install bootstrap, flash, uninstall bootstrap(you can't do the recovery part, but safestrap install script should clean that out), then reinstall safestrap recovery, and when you switch back to safe you can restore your backup
Click to expand...
Click to collapse
Not sure what happened there... I backed up my safe rom, then switched to non-safe, uninstalled safestrap, booted in to "stock" installed bootstrap, rebooted recovery, installed my new rom (cm9) and bootlooped... (I had CM9 working beautifully in my safe for ages, wanted it in my non-safe so I could play with other roms in safe)
So much for that plan...
I guess plan B is to figure out how to unbrick an XT860 (I don't think there are any Bell SBFs up, so I guess I go with one from somewhere else...)
I believe a Bell XT860 SBF is here (got it from another thread):
http://sbf.droid-developers.org/umt...M-111109-release-keys-BellMobility-CA.xml.zip
LaZiODROID said:
I believe a Bell XT860 SBF is here (got it from another thread):
http://sbf.droid-developers.org/umt...M-111109-release-keys-BellMobility-CA.xml.zip
Click to expand...
Click to collapse
Yeah, got the SBF loaded. Still have no idea why i couldn't get CM9 in to my non-safe. right now though I seem to have a bigger issue, for some reason my recovery can no longer mount my SD card (though the OS can) I've tried bootstrap, and safestrap, neither can read from my external SD... it's rather odd!
I found with safestrap 1.08f (ricks version) it wouldnt mount mine either.
I started from scratch and installed 1.08d and it works just fine.
As for flashing your non-safe .... i didnt know that was even possible.
Stick with your safe... its the .... safest. Lol
Sent from my XT860
thanks for the tip about 1.08f... maybe that's it, I'll investigate...
LaZiODROID said:
As for flashing your non-safe .... i didnt know that was even possible.
Stick with your safe... its the .... safest. Lol
Click to expand...
Click to collapse
I know sticking to safe is safer, but sometimes I don't want "safe" I want functional. seems a waste to me to have stock loaded on non-safe when I don't plan to ever, under any circumstances, use stock.
I like CM9, I'm quite happy with it as my every day rom. I'd like to put it in non-safe so that I can play with new ones in safe. unfortunately I'm not having much luck with that right now...
I'd like to do that as well (run something fun as my non-safe and try out others in my safe)... let me know if you get that going ;D
ve6rah said:
Not sure what happened there... I backed up my safe rom, then switched to non-safe, uninstalled safestrap, booted in to "stock" installed bootstrap, rebooted recovery, installed my new rom (cm9) and bootlooped... (I had CM9 working beautifully in my safe for ages, wanted it in my non-safe so I could play with other roms in safe)
So much for that plan...
I guess plan B is to figure out how to unbrick an XT860 (I don't think there are any Bell SBFs up, so I guess I go with one from somewhere else...)
Click to expand...
Click to collapse
There is indeed a sbf. Theyre called fastboot now. There's a thread for it
Sent from my XT860 using xda premium
LaZiODROID said:
I'd like to do that as well (run something fun as my non-safe and try out others in my safe)... let me know if you get that going ;D
Click to expand...
Click to collapse
well, others have reported success, but none of them seem to be using CM9 in the non-safe, so maybe it's something specific about that one rom?
I think I'll give it one more try today before giving up and going back to root/cm9 so that I don't end up without a phone for the next 2 weeks until I have time to play again!
seems to me that the trick is to find a bootstrap/recovery that is NOT safestrap, install it, install whatever you want, uninstall it, install safestrap, and go on with life as usual.
Unfortunately I can only find one non-safestrap recovery, and it doesn't seem to work too well. most are dead links now as everyone moved to safestrap.
Anyone have a link to a non-safestrap recovery I can try?
I have uploaded 2 bootstrap versions to DepositFiles. Sometimes when you root, a complete version of BusyBox isn't included, so:
1) Root
2) Install Busybox Installer from the market (it's free)
3) Run BusyBox Installer and install whatever highest version installs successfully. (I found that after using the Bell SBF, the highest version wouldnt install properly, so I just chose the next one in the list)
4) Install whatever bootstrap app, and click its button to do the recovery install.
Droid3 Bootstrap:
Link: http://depositfiles.com/files/5qcaay2e7
(This one's for the Droid3 - I believe that if you're using an XT860, the only way this will boot is if you have USB plugged in!)
Milestone3 Bootstrap
Link: http://depositfiles.com/files/o248gldkm
(For the XT860, this should just boot normally, without USB cable)
Well, the solution continues to elude me.
With Milestone3 Bootstrap I simply can't get cm9 to boot. it flashes ok, but then it just freezes on the motorola logo and won't go any further.
With Droid3 Bootstrap (and USB plugged in) I can boot in to cm9, but USB has to be plugged in EVERY time you boot up (not much of an option for an every day phone)
After getting cm9 working under Droid3 bootstrap though I decided to try to change to safeboot. Unfortunately that way it boots up to "android is upgrading... optimizing applications" followed by "starting applications" and it never gets past there.
I think part of the problem is that I have no way to uninstall the droid3 bootstrap before installing safestrap. anyone have any ideas how to do that properly?
So are you saying you had cm9 running, then installed safestrap, but after doing that, your CM9 wouldnt start up (freeze?). Do you get the safestrap splashscreen at least? I wonder if a wipe would fix up your CM9 (but is that even possible.. and would that wipe out the safestrap install... hmmmm)
LaZiODROID said:
So are you saying you had cm9 running, then installed safestrap, but after doing that, your CM9 wouldnt start up (freeze?). Do you get the safestrap splashscreen at least? I wonder if a wipe would fix up your CM9 (but is that even possible.. and would that wipe out the safestrap install... hmmmm)
Click to expand...
Click to collapse
yes CM9 worked on Droid3 Bootstrap. but not once I installed safestrap (without tweaking anything in safestrap.)
it doesn't so much "freeze" as it decides to "optimize applications" and then just can't seem to get past there. (only solution is a battery pull at that point) I do get the safestrap flashscreen, and can get in to safestrap.
After wiping cache, dalvik cache, and data (factory reset) I reboot, go through the safestrap boot screen, and get to... nothing. blank screen, refuses to boot further.
So something obviously went wrong between when I had Droid3 Bootstrap loaded, and when I installed safestrap. I'm just not sure what other option I have at that stage to make things go more smoothly. theoretically if it works under the Droid3 bootstrap, then it should work as the non-safe for safestrap, but it just doesn't, and I have no idea why.
well, still didn't figure out CM9 in the non-safe... so I've gone a different route.
I now have mavrom in the non-safe, and I'm in the process of installing steeldroid in safe...
Nice. So there was nothing special you had to do after your fresh MavROM install to get safestrap going?
Sent from my XT860
No, went smoothly.
- SBF to stock
- root
- install milestone3 bootloader
- flash mavrom
- remove miletone3 bootloader
- install safestrap
- switch to safe
- install steeldroid
I can't imagine what I'm doing wrong here. Steps I'm taking (rather circuitously I might add):
1) Odin back to stock 4.4.2
2) Root
3) Install SuperSU, Busybox, & SS 3.75
4) Reboot to recovery
5) Backup stock software
6) Reboot to recovery
7) Flash rom according to instructions
What happens is that it writes the data section, but not the system. So I'm left w/ no OS on the phone and have to Odin again to get it back up. After the initial backup (or even if I skip the backup), I get an error in SS "unable to mount /system"
I've searched high an low through the SS thread and so far have not been able to glean anything close to the problem I'm having. Is there something I'm doing wrong?
Could iy be your sd card?
janderfu said:
I can't imagine what I'm doing wrong here. Steps I'm taking (rather circuitously I might add):
1) Odin back to stock 4.4.2
2) Root
3) Install SuperSU, Busybox, & SS 3.75
4) Reboot to recovery
5) Backup stock software
6) Reboot to recovery
7) Flash rom according to instructions
What happens is that it writes the data section, but not the system. So I'm left w/ no OS on the phone and have to Odin again to get it back up. After the initial backup (or even if I skip the backup), I get an error in SS "unable to mount /system"
I've searched high an low through the SS thread and so far have not been able to glean anything close to the problem I'm having. Is there something I'm doing wrong?
Click to expand...
Click to collapse
I don't know if this would help but have you tried the process with a different SD card? I was having problems and thought it was something I did wrong but found out my scan disk 64gb micro SD card was the problem. Hope you get it working, good luck Janderfu
I tried that last night. Same result. For some reason I can read from the system partition, but not write to it.
some have reported issues where if you wipe system, it messes up the sd... if you are able to odin just fine, then when in SS, just do the factory data reset option to wipe and dont do the advance and wipe system.. then see if you are able to flash this way.. just make sure to do the factory reset like 3x to be safe and then flash..
see if that works.. also what version of SSare you using and what version are you on as in JB or KK... i see you say 3.75 up top, but to be sure you are on NC2/KK?
From my Fired-up Note Pro 12.2!
I'll give that a shot.
When I go back and Odin, it's going to NC2/KK. And yeah, the SS is 3.75.
janderfu said:
I tried that last night. Same result. For some reason I can read from the system partition, but not write to it.
Click to expand...
Click to collapse
I get a similar issue in trying to run init.d scripts. Several times a "can't mount root as read/write" error is shown. I'm interested to know if this is similar and how to approach as well. Thanks.
~Sent from my AT&T Samsung Galaxy Note 3 Badass~
janderfu said:
I'll give that a shot.
When I go back and Odin, it's going to NC2/KK. And yeah, the SS is 3.75.
Click to expand...
Click to collapse
Did it work with the factory rest without wiping the system in advanced wipe? If not than just to make sure that you are flashing the custom rom in one of the rom slots and not on the stock rom partition (just making sure because sometimes we make small mistakes as a noob).