I am unlocked and rooted on jelly beans custom ROM version 9.If I do the ota update to version1.0 will I lose the setup I currently have with my home screen widgets etc? I just really want to make sure it doesn't change anything. Thanks for the help in advanced.
Sent from my SCH-I605 using xda app-developers app
You may not if you don't wipe but you may run into problems. Dirty flashing is always a risk.
I did a "dirty" flash from Beans version 10 to version 11 yesterday (only wiped cache and dalvik cache). I did a full nandroid backup of 10 first as there can be some issues, but it worked flawlessly. All settings were saved and the total turnaround was less than 10 min. I wouldn't try that between different ROMs but upgrades to the same base seem ok.
Alright thanks guys I'm going to backup my ROM up then try dirty flashing.
Sent from my SCH-I605 using xda app-developers app
Related
Im currently running the first flight Rom and wanted to go back to alpha 2...i tried a reflash but my phone is still on the other Rom, i did another reset and reflash of alpha but it still hasn't change. I than tried to use my nandroid backup which ice used before but when i try to use it it tells me nothing on file...what do i do
Sent from my SAMSUNG-SGH-I717 using xda premium
After about 4 attempts i was able to flash alpha 2 and my back ups seem to be there as well...not just empty folders like before, weird
Sent from my SAMSUNG-SGH-I717 using xda premium
That is odd. Make sure you always factory reset multiple times as well as wipe cache multiple times when switching roms.
So you would:
- factory reset x3
- wipe cache x3
- wipe dalvik x1
- flash new rom
This should help with experiencing less if these type issues as well as other bugs.
Sent from my SAMSUNG-SGH-I717 using xda premium
Coffinfeeder said:
That is odd. Make sure you always factory reset multiple times as well as wipe cache multiple times when switching roms.
So you would:
- factory reset x3
- wipe cache x3
- wipe dalvik x1
- flash new rom
This should help with experiencing less if these type issues as well as other bugs.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
I actually do those steps. I flashed one of the other ics roms and I didn't really like it so I tried to flash alpha back, after reboot I was still on the other rom...I tried again with same result, finally I used my backup. This time the same thing happened but I was on a different rom, the only difference was I wasn't able to use my back up, backup folder said "no file" when trying to flash, so I was pretty much forced to keep trying to flash alpha, finally it worked and I checked my cwm folder and my backups are there and are not empty. Odd
Sent from my SAMSUNG-SGH-I717 using xda premium
nash2000 said:
I actually do those steps. I flashed one of the other ics roms and I didn't really like it so I tried to flash alpha back, after reboot I was still on the other rom...I tried again with same result, finally I used my backup. This time the same thing happened but I was on a different rom, the only difference was I wasn't able to use my back up, backup folder said "no file" when trying to flash, so I was pretty much forced to keep trying to flash alpha, finally it worked and I checked my cwm folder and my backups are there and are not empty. Odd
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
weird considering when you do a restore it erases boot partition before starting to restore so unless you used the wrong backup file it should've worked the first time.
roloracer said:
weird considering when you do a restore it erases boot partition before starting to restore so unless you used the wrong backup file it should've worked the first time.
Click to expand...
Click to collapse
I only used the restore one time a week or so ago because everytime I tried to flash back to alpha I was still on the collective rom. Thats when I used my backup and it worked but this time the same time happened....flashed alpha like 3 times and nothing happened, I than tried to use my backup but my phone told me the backup file was empty, I have 2 backups and my phone told me the same thing on both. I continued to flash alpha over and over again with wiping date etc each time and it finally worked, and my backups have data in them unlike before.
Sent from my SAMSUNG-SGH-I717 using xda premium
Hi hoping anyone can tell me if I did this correct. I use to mess with my og AE55 with clockwork recovery I think it was called?
Anyway im hoping I did this correct. I flashed to beans build 6. I had a back up of my stock rom rooted with twp.
After using beans rom I kind of missed the little features of stock. So to revert back I went to the twp recovery screen. I did factory reset and wiped davlik cache.
Then restored rom.
Was this the right process? The phone does seem a little bit slow? Maybe its just my mind messing with me since beans rom was f*ing fast.
Sorry for being a complete noob. I just came back from 2 years of being with the iphone 4. Damn do I miss android!
Sent from my SCH-I605 using xda premium
Why not try cleanrom? Its stock with some improvements.
Sent from my Note2 running cleanrom 4
That's fine. You actually don't even need to wipe because the restore will overwrite all that anyways. Having said that I factory reset everytime too just to be sure.
Sent from my SCH-I605 (AKA NOTE 2)
JasonGeiger said:
Why not try cleanrom? Its stock with some improvements.
Sent from my Note2 running cleanrom 4
Click to expand...
Click to collapse
I'll definitely check it out!
kintwofan said:
That's fine. You actually don't even need to wipe because the restore will overwrite all that anyways. Having said that I factory reset everytime too just to be sure.
Sent from my SCH-I605 (AKA NOTE 2)
Click to expand...
Click to collapse
Ok phew, I saw wipe rom and freaked out that now i have other files taking up space not being used since i thought i didnt use that then restore.
And the all have the same green leaf for a home screen, so are my ROMS not being written to the right place or what. this is getting confusing. the ROM form about shows the different versions but all are skipping the setup and I have no 3G/LTE connection, only wifi.
Whatever I am doing I seem to be consistent about it
Did you flash gapps?
Sent from my GT-P7500 using XDA Premium HD app
eushaun99 said:
Did you flash gapps?
Sent from my GT-P7500 using XDA Premium HD app
Click to expand...
Click to collapse
the AOPK had gapps folded in. what is odd is I have now tried AOPK and a CM10 and CM10.1 and they all seem to have the same start screen, come up after the boot like it is already installed, missing any 3G/4G connection. Now I have flashed back to EG01 and run up though iCS several times and it isn't taking the CWM now, says it installs ok but boots into stock recovery. Now I using the older CWM 5504 for the i-905 and it writes somewhere, but apparently not where it should be. I was going to try TWRP but that doens't appear to run on HC/ICS - is it JB only? I have shied away from the newer CWM for a long time because for a while they just seemed to boot-loop the tablet.
Any one have a suggested working version of CWM? This starting from scratch and rolling in all the updates is getting old - which is why I was wondering if there is a way to build my own ODIN set to just flash back to this point without having to go though reroot and install of the recovery (which apparently now I am not able to do - wts! )
Thanks!
Rob (lost) in Katy.
Twrp is compatible with ICS too, if im not mistaken. Go to www.droidbasement.com and download pershoots's version of cwm recovery. That should work just fine. BTW, you did make a full wipe (system, data, cache, dalvik) right? And what's EG01?
Sent from my GT-P7500 using XDA Premium HD app
eushaun99 said:
Twrp is compatible with ICS too, if im not mistaken. Go to www.droidbasement.com and download pershoots's version of cwm recovery. That should work just fine. BTW, you did make a full wipe (system, data, cache, dalvik) right? And what's EG01?
Sent from my GT-P7500 using XDA Premium HD app
Click to expand...
Click to collapse
I am now one cycle 15 and doing the last update to 4.04. every stinking rom I load goes back to the factory or the ROM starts off and ignores the setup. The really annoying thing is I have had all this setup and working before. Ahhhhhh!
rgranger said:
I am now one cycle 15 and doing the last update to 4.04. every stinking rom I load goes back to the factory or the ROM starts off and ignores the setup. The really annoying thing is I have had all this setup and working before. Ahhhhhh!
Click to expand...
Click to collapse
Ok, i found another recovery laying around that seems to be working. I also found that the bug where you need to delete the script that deletes the new recovery. Once I got that far things started making sense. I guess whatever mod I was on before didn't need it. The next trick will be trynig to decifer how to do an odin backup so that I don't haver to roll though 4/5 upgrades to get here. I know someone is doing it. thanks for the help and a place to bounce ideas. will update if i come up with anything.
Rob
So ive been having issues with dhacker29's roms making my phone reboot and hang on the bootloader. Well the latest one, the selinux build which he put more bugs into an already screwed up reboot cycle it worked good when I first installed it, than it did one of its forced reboots.
Phone hasnt booted since, restored to previous rom that worked fine. Stock, all kinds of things tried. It just hangs on the motorola logo now.
Anybody got any ideas for me?
When you go back to other ROMs are you restoring apps and data along with them via Titanium Backup or another backup app? If so, that might be the cause. It may be something in your apps, not the ROM. And as always wipe cache and dalvik cache after any flash.
Just restoring back to a TWRP backup. not using tibackup or anything like that,
Ive tried wiping dalvik, Tried a factory reset on these backups. Even tried fix permissions. Still nothing.
Probably a bad backup
If you wipe fully (yes I mean a full wipe) and then restore a back up from working phone and it just loops, chances are you had a bad backup
Just wipe clean and flash a new rom
Sent from my Nexus 4 using xda premium
demkantor said:
Probably a bad backup
If you wipe fully (yes I mean a full wipe) and then restore a back up from working phone and it just loops, chances are you had a bad backup
Just wipe clean and flash a new rom
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I did some posting in the thread for the rom. 2 others had the same issue where none of there backups worked after flashing that rom version and after it crashed and rebooted it never came back. So I doubt it was a bad backup just something weird with the rom
Sent from my XT926 using Tapatalk 2
Unless there is something very strange about this ROM (as in it corrupts other partitions but so highly doubtful), backups are 100% separate from another ROM, this means a full wipe will erase everything about you current ROM and then restoring a backup from a previous ROM will work, so long ad the backup is good and the wipe is clean.
Sent from my Nexus 4 using xda premium
I don't know. The rom does have a form or selinux in it so maybe that caused it. I don't know the specifics of what selinux does internally just what the goal is
Sent from my XT926 using Tapatalk 2
Doesn't sound like it should brake anything, if the ROM won't boot for you that's one thing, but completely wiping your phone then flashing a new ROM should fix your issue.
I am highly suspect that the ROM in question could have done anything at all to your recovery or your backups.
You said you are using twrp, have you tried wiping/formating all partitions and then flashing a known working ROM? Does your phone have fast boot mode? If so this may be an even cleaner wipe to do prior to the flash
Sent from my Nexus 7 using xda premium
I had to fastboot back to stock to get anything to work.. No rom I tried would boot
Sent from my XT926 using Tapatalk 2
Again, without knowing anything about your phone, the ROM would not affect your bootloader/radio/recovery no firmware should be changed just by flashing a rom,.
If it won't boot after a full wipe then there is some other issue, but if you were able to fix things by flashing back to stock then good.
Without knowing more specifics about your phone or the ROM you had issues with I guess I can't help you any further, so long as your are up and running now I would suggest just to stay away from any ROM you have had issues with, make new backups and test them (yes fully wipe before a restore and being your phone has fastboot wipe there) and best of luck to you
Happy flashing!
Sent from my Nexus 7 using xda premium
RAZR hd... Cm10.1 on the post started by epinter.. You can read how others had the same issue. I had 4 backups and non boot looped. It would hang at the bootloader and never even make it to the boot animation. Apparently it's something nobody's seen before but me and 2 others there have experienced it. So it's not a 1 time fluke.
Sent from my XT926 using Tapatalk 2
After running just about every ROM for this device, I recently flashed my first stock based ROM (cooked 1.8). However since this time I've been unable to flash back to any aosp ROM. I get boot looped on every one. I've tried everything. Yet, I can flash cooked again no problem. I know there's something I'm missing. Any help would be great.
Sent from my SAMSUNG-SGH-I777 using XDA Premium 4 mobile app
You have a nandroid backup right? Restore that then flash whatever you want.
Sent from my SGH-I777 using Tapatalk 2
Backup won't boot either. That was my first plan.
Sent from my SAMSUNG-SGH-I777 using XDA Premium 4 mobile app
Have you tried to format system under mounts and storage after your factory reset, and before you flash your rom and gapps? Just a suggestion. Not sure it will fix you problem or not. It seems as if I had a problem similar to what you are describing after running a Samsung based rom in the past. I believe that was the cure to my issue.
adrock74 said:
Backup won't boot either. That was my first plan.
Sent from my SAMSUNG-SGH-I777 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Search for Siyah kernel v4.3.3 in the forums and install, restart recovery and flash away. Should take care of it.
T
Sent from my SGH-I777 using Tapatalk 2
I always have kept that kernel on standby but that didn't work. I've tried every kernel. Can't believe backups won't even boot. I flashed cook's ROM wipe before his ROM the first time, wonder if that did something.
Sent from my SAMSUNG-SGH-I777 using XDA Premium 4 mobile app
Try Odin to stock and start from scratch. A lot of work but hey what do you have to lose. :beer:
Sent from my SGH-I777 using xda app-developers app
First find a compatible Kernel for the AOSP ROM your trying to flash. Flash that Kernel.
Second, after the flashing is done, reformat the device; cache, dalkiv cache and system and system settings.
Third, reboot into recovery mode from the recovery menu itself.
Fourth, flash the kernel one more time.
Fifth, flash the AOSP ROM of your choice.
Sixth, reboot back into recovery menu.
Seventh, reformat once more.
Eigth, reboot the device.
As you should know, the first boot up after flashing a ROM takes the longest. Give it like a minute or two.
If this doesn't work, you have to flash a kernel that was compatible with the "cooked" rom you were using. Then from there do a reformat from the recovery menu. Once reformat is done, flash the AOSP kernel, then flash the AOSP ROM right after. Then reformat once more and reboot as normal.
If that doesn't work, flash compatible kernel with the "cooked" ROM your using now and also relay the cooked ROM, and then use Odin to bring it back to stock un-rooted. From there, do as you wish.
Butchr said:
Have you tried to format system under mounts and storage after your factory reset, and before you flash your rom and gapps? Just a suggestion. Not sure it will fix you problem or not. It seems as if I had a problem similar to what you are describing after running a Samsung based rom in the past. I believe that was the cure to my issue.
Click to expand...
Click to collapse
That is exactly what needed to be done. Mr cook actually has another thread with cwm flashable wipe scripts that would have done that. Quite handy :thumbup: