<<Reposted from QA, couldn't move the post myself>>
I'm confused with FRF72, why is it only 2MB?! That is very small. Is this meant to patch the earlier FRF50 which I have running right now?
Even if it is/or isn't a patch, has anyone tried to run the ROM ZIP WITHOUT WIPING so to save from having to restore Titanium backup? I can't be bothered with the whole process until the weekend is over, unless I can upgrade without wiping. Please let me knwo if any of you have attempted to do that and have you succeeded? Thanks.
When I upgraded 2.1 to 2.2 and was curious, I didn't wipe and the 2.2 successfully booted, and everything all the settings and apps were intact, but it was force closing every single time I tried to run any app, so after that, I wiped, and then it was fine.
I don't want to go through that whole process again though, this time being its 2.2 older beta to newer beta, so it might work without a wipe right?
if u dont wipe u will be stuck in a boot loop. i did a nandroid and then flashed it only to land in the loop. then i wiped and flashed and all was well. thank goodness for nandroid
Related
It seems that I can't get a clean boot off anything other than the JF 1.5 or 1.51 US builds. I've tried cyanogen and even jf 1.51/1.5 ADP builds but it always boot loops. Any suggestions?
I've read through the questions threads, I've used search. I just can't seem to find anything relevant to my problem in specific. I've flashed to hardspl, I've updated the radio, tried various builds of the same developer to see what it could possibly be, but I'm pretty stumped.
Hmmmm... try re-flashing RC29, re-root, and try the update again... sounds like its not updating correctly
Tried that multiple times over the last few days. this time, I managed to get past a straight reboot loop, but I was stuck at the boot screen with sounds/alerts/sleepbutton as if I had changed my launcher.apk with a file from the wrong rom. Going to reflash to 29 again and try it again =P
As many times as I go through this long (well, not quite) and arduous (heh, sure) process, it's still fun
*edit* out of curiosity, how extensive are nandroid backups? I've tried some flashes using a nandroid restore from an rc29 with the OTA radio and cyanogen's restore img. Would that reflash me back to prior settings?
//Note not all of my installs are with nandroid restores. I have tried with pure fresh dreaimg.nbh/root/hardspl/radio installs.
hmmm, have you tried flashing the new recovery? Try Cyan's 1.3.1 Recovery Image, might work a little better.
just reboot looped again. order of operations for a freshie should be something like this;
1)dreaimg.nbh
2)root
3)cyan's recovery
4)ota radio
5)JF 1.51 ADP
correct?
*edit* in all honesty, I want to try cyan's newest build but if I can't even get past installing JF's ADP build... ya...
wahookasan said:
just reboot looped again. order of operations for a freshie should be something like this;
1)dreaimg.nbh
2)root
3)cyan's recovery
4)ota radio
5)JF 1.51 ADP
correct?
Click to expand...
Click to collapse
No... you're missing HardSPL between root and cyan's recovery.
lol, just did some more searching, and realized that I was misunderstanding what hardspl actually did for me. It was my understanding that Cyan's recovery img replaced hardspl (don't ask me how I got it mixed up, I just did, ok? xD). I just got into rooting my G1 recently, if you haven't noticed.
Thank you for your timely reply's and hopefully this helps me dive into what I was missing out on
Sorry for the double post but the issue isn't resolved.
the problem is persistant. even with hardspl in (could have sworn I had that in at some point anyway) I still can't use the ADP or cyan's latest
Did you perform a wipe before flashing ROMs? Not wiping may cause some boot loops with certain mods.
I've done a full wipe back to dreaimg.nbh (assuming that's what you mean). I've gone back to step 1 of the root process. Still no go
wahookasan said:
I've done a full wipe back to dreaimg.nbh (assuming that's what you mean). I've gone back to step 1 of the root process. Still no go
Click to expand...
Click to collapse
You should go ahead and wipe before all of the builds when your starting up. I believe DREAIMG.nbh is a US based rom, and the JF you are installing is ADP. You MUST wipe when switching from US based ROM to an ADP based ROM
im having the exact same problem i was able to get a rom other than the JF installed, i have tryed every damn way possible and mine will not work either. i use the Haykuro 1.5 Cupcake one, and it seems to work. My phone gets stuck whenever i try to load any hero, or Cynanogen roms. Its depressing, yeah fun at first but now i look at posts and cry hahahahha when these people have theres all bad ass! SOMEONE HELP USSS! email me at [email protected] if needed pleeeease i need HERO!
root, wipe, flash JF, wipe, update radio, wipe, update recovery image, wipe, flash whatever ROM you want.
Did you try that?
Updated my phone to the 2.2 JPM firmware successfully and then applied the root using the CF-Root v1.2 method. Everything working fine so far I applied the new Voodoo-5-pre6-Froyo fix and phone rebooted fine. Now I go to install Titanium backup and it requests root privileges which I confirm but it still says it cannot attain superuser privileges when attemping to run Titanium.
Anyone know what's up? I wouldn't mind getting my old apps back
Simply restart Titanium, happens to me all the time. Once restarted, it should work normally.
However, generally if you have come from a non-froyo ROM, it is recomended that you do not use Titanium to backup, due to the 2.1 system data causing a force closes.
I was looking for the button to thank you because I JUST had the exact same issue. Googled it and brought me here.
Thanks so much. I kept hesistating whether I wanted to try one of the froyo roms since it was taking FOREVER to get the official version and I was tired of waiting around.
@ coboltmarine
I want to flash my galaxy with Froyo (still have 2.1). Therefore I would like to backup my firmware first if something goes wrong so I can re-do everything. Since you said that backing up a non-froyo with titanium is not recommended, which one would you recommend? Do you know any posted thread which could help me in this?
Thanks a lot
After getting Clockwork Mod working and making a Nandroid backup, I decided to apply hardcore's Speedmod Lagfix. When it was done I ended up with most of my apps force closing, including Launcher Pro, which made it very difficult to do anything. I was able to switch to TW Launcher so I could do things. I tried to restore some apps and data with TI, but get a message saying my phone won't allow it for security reasons. I was able to previously as I installed Amazon Market app on my rooted Cappy with stock Froyo. I found out after lots of work that if I uninstalled and re-installed apps they worked fine. Hoping to avoid having to do that. I also tried the fix permissions options in recovery to no avail.
Did I do something wrong or have I left a step out in applying the lagfix? My thoughts are I may have to do a nandroid restore, but am hoping not to. My plans are to flash Fasty ROM eventually. Is it better to get this cleaned up first or restore back to stock, without lagfix possibly, and then flash?
Thanks for any assistance.
if you're going to flash a different rom why worry about problems your having on your current os? its kinda like asking this:"windows xp is giving problems should i resolve those before installing windows 7?"
the enabling of the lagfix makes a nandroid backup, wipes everything to format to ext4 and then restores everything. sounds like perhaps that data was corrupted. make a fresh tibu backup, disable lagfix, do a wipey wipe of data, cache, and dalvik from cwm and flash a new rom, and then only restore MISSING APPS + DATA. DO NOT RESTORE ANY SYSTEM DATA.
Thanks for the advice. I'll try it later when I get home. I guess I'm being a bit careful and want to be comfortable in taking the next step. Since this is my only phone for right now, I can't afford to be without it very long. I've been looking for a cheap, broken screen, yet working Cappy on eBay to let me toy around with.
Hello all,
I've been running Eclipse 2.2 on 902 for some time and I've stubbornly refused to switch away from using bootstrap for all my backup needs, however, after reading enough about it I decided to give safestrap a try. I've had a little trouble with the process however and was looking for a little clarity...
My understanding with safestrap was that in addition to giving me a safe (technically unsafe) 2nd partition/access to recovery in case I messed something up, that it would also pretty easily transfer data, apps, etc from one partition to the next, making flashing roms (and I thought updating) much easier and quicker without needing to backup individual portions of my system, Is this correct or am I mistaken?
Onward to what I did (my goal is to update to 905 and install eclipse 3.0) - Installed safestrap, backed up safe and unsafe side. I then went to unsafe and used bootstrap to restore to IMMEDIATELY after I applied the 902 update (had backed it up previously). This backup was literally a stock Bionic which I had updated from 886 all the way to 902, rooted, then installed bootstrap to backup. I then updated this to 905 with no issue, and of course backed it up... From here, my understanding was that I could simply swap over to safe side, then install the eclipse 3.0 through finding a zip in recovery - Recovery would not do this for me. It gave me an error similar to "cannot apply eclipse3.0.zip (bad)"
I tried to push the ROM both without making any changes (just switching from unsafe to safe and immediately trying to apply the zip) and when that didn't work I wiped data, formatted system, and wiped cache/dalvik and got the same error. (the net result through all of this was making my safe side non-responsive, and me ending up restoring safe side system to the initial backup I had made about 30 minutes prior).
Is this working as intended? Should I look at safestrap as purely an extra failsafe to keep me from bricking my phone and not an easier method to flash/update? If I have to expect that I need to go to safe, follow the same path to apply the update as I did on unsafe, then flash 3.0 and restore with titaniumbackup, sms/call log backup, etc, I will, but I just wanted to make sure I'm not misunderstanding something with safestrap that may allow me to make this whole process easier - I'd be much more interested in trying out a variety of ROMs if the restoring of my data wasn't such a hassle when I did it.
Sorry for the long post - I'm long winded and also wanted to get all of the information out there for anyone who may answer.
Thanks in advance!
-Jamie
Guess I was too wordy and nobody wants to read it (or posted in the wrong spot maybe) -
tldr:
Is there a way to use safestrap as having a way to easily transfer data etc from one rom/update to the next? or should I be using it solely to have an extra backup to prevent me from bricking my phone, and just do the longer more arduous methods of restoring data and settings after a rom swap/update?
I'm no expert but I have successfully used Safestrap, installed eclipse 3.0 as well as tried other roms and themes, and have other Android experience as well. Sounded like you may have used bootstrap and Safestrap at the same time. Am I wrong? If not, from my understanding that is a no no. Uninstall bootstrap completely and use Safestrap only. I also upgraded my "unsafe" system to .905 via OTA before attempting 3.0. My first experience with Safestrap, however, was not entirely positive either. I think my download was corrupt because it stopped working correctly. I downloaded again and haven't had any problems since. I followed this guide http://forum.xda-developers.com/showthread.php?t=1455888 and it worked. He's not really all that clear at times. It's also not necessary to factory reset after flashing a new rom. Always do it, but it can be done before too. I always do it before and have no problems. Also if you decide to apply a theme make sure you boot up the new ROM before flashing the theme. This guide was not entirely clear on that and it got stuck in a wicked boot loop that ended with me on stock and Safestrap gone. Keep trying. Hope some of this helped. I'm wordy too
Sent from my Galaxy Nexus using xda app-developers app
Btw, to answer your first question, the best way I've found to transfer user apps from ROM to ROM is with titanium backup. Other data will still be on your sd cards and accessible to the new ROM. I never use titanium to restore system settings and most system apps though. Things tend to get messed up if you try to do this from one rom to another. System apps can be converted to user apps with titanium which is cool then backed up and restored to new ROM. And never restore Google play app with titanium. Some go so far as to say don't restore apps with data but I haven't had any trouble except with core google apps like play, gmail, voice. Usually flash gapps if I have to and restore other core Google apps directly from play store. Sometimes titanium "hangs" on some apps. Not to much trouble with it lately maybe it's fixed used to be a PIA though.Sorry there's still plenty of setup involved any time you want to "dial in" a new ROM.
Sent from my Galaxy Nexus using xda app-developers app
Thanks G-diddy,
To clarify, I knew bootstrap and safestrap didn't play well together. That being said, I did NOT use safestrap to try and restore to a bootstrap backup. I installed safestrap, then swapped to my UNSAFE side, then restored to a previous bootstrap backup (using bootstrap), then OTAd to .905. I then backed up this fresh near stock but rooted .905 with safestrap (thus should never have to use bootstrap ever again). I then tried to swap over to safe and push eclipse 3.0 but had no success... At present my phone has near stock but rooted .905 on my unsafe side, and the same .902 with 2.2 eclipse on my safe side that I've been running for months...
I guess I have no choice but to restore my present safe side to the old bootstrap backup, then manually ota, then install the rom, I just thought that Safestrap would make all of this process easier - in as much as since my unsafe side is successfully updated, I was hoping my safe side would be too, making the process somewhat simpler. Sounds like I'm wrong in this assumption though, unless someone else can say otherwise?
Thanks for the tip on Titanium Backup too, although I've been using the premium version of that for months now, ever since I decided I was going to turn my phone into a toy
Hey all,
I installed CM10 Helly Bean (DerTeufel) port for Captivate V10 with full wipe.
It seemed to be working fine... fooled around a bit, tried out Google Now, etc.
Was restoring apps (not data) w/ Titanium Backup.. forget if it had finished or not...
Didn't try to run any of these programs or anything, just tried to unlock and the touchscreen was not responsive... Tried wiping cache+dalvik + fixing permissions... tried reinstalling ROM and GAPPS...
All are in a non-responsive bootloop.
I'm starting over now with another factory wipe... as of now it is stuck on "Welcome" Screen and touchscreen is not responding... AND.. it just restarted
Any ideas as to the problem... Was it Titanium Backup related? Should I resist running that again (assuming this ever works)?
I would post this on Development thread but I still don't have my 10 posts, heh, mostly a long-time lurker...
Thanks!
Worse than I thought!
So It's worse than I thought... I gave up and re-flashed slim (ICS)... and the same problem still exists... boots up, looks normal, can't touch anything.... eventually it reboots....
Suggestions?
Would ODIN flash do anything different? I9000 bootloaders?
ScruffMcG said:
Hey all,
I installed CM10 Helly Bean (DerTeufel) port for Captivate V10 with full wipe.
It seemed to be working fine... fooled around a bit, tried out Google Now, etc.
Was restoring apps (not data) w/ Titanium Backup.. forget if it had finished or not...
Didn't try to run any of these programs or anything, just tried to unlock and the touchscreen was not responsive... Tried wiping cache+dalvik + fixing permissions... tried reinstalling ROM and GAPPS...
All are in a non-responsive bootloop.
I'm starting over now with another factory wipe... as of now it is stuck on "Welcome" Screen and touchscreen is not responding... AND.. it just restarted
Any ideas as to the problem... Was it Titanium Backup related? Should I resist running that again (assuming this ever works)?
I would post this on Development thread but I still don't have my 10 posts, heh, mostly a long-time lurker...
Thanks!
Click to expand...
Click to collapse
sorry I'm just going to post twice so I can post to development...
yeah... 10char
What I can suggest is, go back to GB. Download a one click Odin w/ bootloaders, you can search that in the dev forum. After that flash it with a corn kernel so you can have a working CWM. And then Go to recovery, have a full wipe (data,cache,dalvik) TWICE and flash this--
Slimmed Down V10 by cbalt
Wipe Data/Factory Reset/Wipe Dalvik
Flash http://www.mediafire.com/?9p212pempybwnj3
Then Flash http://www.mediafire.com/download.php?bdjabcmobz6aw6k
Then Fix Permissions
Then Reboot
Click to expand...
Click to collapse
I can recommend you that one because it's the one the I'm currently using right now and I can say that it's working like a charm.
The method above is the one I'm using everytime I flash a ROM. I always do a full wipe so I won't be encountering any issues or whatsoever.
About TiBu, I am not sure if that's where the issue coming from because I've been using TiBu for a long time and haven't encountered that. Just always remember, if you are using backup using TiBu, just backup the User Apps+Data, DO NOT INCLUDE THE SYSTEM APP. Goodluck!
So you think w/bootloaders will help?
I have flashed every odin w/o bootloaders that I have access too and all get me stuck at ATT bootscreen....
Little hesitant to reflash my bootloaders since I was/am already on GB bootloaders, but if it might help I may have to do it...
I actually was on that JB version (but with the normal gapps b/c I wanted google now...)... now I'm on no version of anything hahah
takeoutttt said:
What I can suggest is, go back to GB. Download a one click Odin w/ bootloaders, you can search that in the dev forum. After that flash it with a corn kernel so you can have a working CWM. And then Go to recovery, have a full wipe (data,cache,dalvik) TWICE and flash this--
I can recommend you that one because it's the one the I'm currently using right now and I can say that it's working like a charm.
The method above is the one I'm using everytime I flash a ROM. I always do a full wipe so I won't be encountering any issues or whatsoever.
About TiBu, I am not sure if that's where the issue coming from because I've been using TiBu for a long time and haven't encountered that. Just always remember, if you are using backup using TiBu, just backup the User Apps+Data, DO NOT INCLUDE THE SYSTEM APP. Goodluck!
Click to expand...
Click to collapse
I met a problem. I do not know wether or not it is common. The phone will reboot by itself sometimes.
Do you have the same problem?
same here
seems as though many of the problems experienced by one are shared by the other
this is logical as they share many common points including the same partition and both jellybean derivations
I was having issues... accelerometer and audio issues.
All came out right as rain after flashing back to stock and reflashing
ScruffMcG said:
yeah... 10char
Click to expand...
Click to collapse