Database Users

Flashing a new rom

Hi guys i have an international samsung galaxy s2. i have villian rom installed but i accidentally deleted my stock rom but, i did not calibrate the battery properly. i woul like to install litening rom but the method of flashing is different from the villian flashing(clockmod recovery). is it okay to install the new rom or will it wipe out my entire data? is it possible to recover my old apps after flashing? i need you help...

primeup said:
Hi guys i have an international samsung galaxy s2. i have villian rom installed but i accidentally deleted my stock rom but, i did not calibrate the battery properly. i woul like to install litening rom but the method of flashing is different from the villian flashing(clockmod recovery). is it okay to install the new rom or will it wipe out my entire data? is it possible to recover my old apps after flashing? i need you help...
Click to expand...
Click to collapse
Litening uses the ODIN method to flash!
Coming from another custom ROM, you have to do a factory reset, cache and dalvik cache wipe from CWM!
Recovering your old apps, leave the job to Titanium Backup!

[Q] Can I restore to rooted backup after flashing rom?

I am using clockwork mod touch edition, and I have a full system backup using it. If I decide to flash cm9 to the device and then decide I want to switch back, can I then restore to this backup using cwm? Or do I have to flash to a stock Rom first?
Brent

u can restore using the backup u created earlier

Ok so the restore also includes the Rom backup then?

yea, that is the main purpose of recovery

Cool, thanks. Just trying to understand more about what is happening when I do these things. Cheers!

don't forget to wipe cache/dalvik cache. u should be fine

[Q] Trouble With Flashing CM10.2 and Wrong Kernel

So I was running CM10.1 nightlies with Franco Kernel and decided to make the jump to CM10.2. The ROM and gApps flash went just fine, but like a dummy, I flashed the version of Franco kernel that I'd been using before, which I guess is not compatible with 4.3. The phone seemed to be softbricked and would just hang at the Cyanogen boot animation. I can get into recovery and I've tried to reflash both CM10.1 and CM10.2 - both hang at the boot animation. I can go back to my stock backup just fine, but then when I try to flash CM again (either version), I have the same hanging problem. Does CM store like a memory of the kernel that you have flashed and try to revert to that? Why can't I flash CM again once I've gone back to stock (and the stock kernel)? Would reflashing the stock image fresh (rather than using a TWRP backup) change anything? I'm pretty inexperienced with this and would appreciated any help. Thanks in advance!

alphamini said:
So I was running CM10.1 nightlies with Franco Kernel and decided to make the jump to CM10.2. The ROM and gApps flash went just fine, but like a dummy, I flashed the version of Franco kernel that I'd been using before, which I guess is not compatible with 4.3. The phone seemed to be softbricked and would just hang at the Cyanogen boot animation. I can get into recovery and I've tried to reflash both CM10.1 and CM10.2 - both hang at the boot animation. I can go back to my stock backup just fine, but then when I try to flash CM again (either version), I have the same hanging problem. Does CM store like a memory of the kernel that you have flashed and try to revert to that? Why can't I flash CM again once I've gone back to stock (and the stock kernel)? Would reflashing the stock image fresh (rather than using a TWRP backup) change anything? I'm pretty inexperienced with this and would appreciated any help. Thanks in advance!
Click to expand...
Click to collapse
Just to be sure how much juice was left while you were flashing CM rom?? Reading your problem I would suggest you to do a fresh Stock image installation and then try flashing CM 10.2.
Have you tried restoring your NANDROID backup, if you made one??

Rohit02 said:
Just to be sure how much juice was left while you were flashing CM rom?? Reading your problem I would suggest you to do a fresh Stock image installation and then try flashing CM 10.2.
Have you tried restoring your NANDROID backup, if you made one??
Click to expand...
Click to collapse
I have restored the NANDROID backup successfully, but unfortunately I was lazy and only have the backup from when I first got the phone.
I backed everything up with Titanium Backup right before I tried to flash CM10.2. If I do a complete stock reflash, do I lose all the data I backed up with TB? I do have some app data that I would really like to keep if possible.
One other resort I thought of was flashing a different custom ROM (Paranoid Android maybe?) and then restoring my TB backup. Would there be any reason that I shouldn't be able to reflash CM after I've restored the stock NANDROID?

alphamini said:
I have restored the NANDROID backup successfully, but unfortunately I was lazy and only have the backup from when I first got the phone.
I backed everything up with Titanium Backup right before I tried to flash CM10.2. If I do a complete stock reflash, do I lose all the data I backed up with TB? I do have some app data that I would really like to keep if possible.
One other resort I thought of was flashing a different custom ROM (Paranoid Android maybe?) and then restoring my TB backup. Would there be any reason that I shouldn't be able to reflash CM after I've restored the stock NANDROID?
Click to expand...
Click to collapse
Try this.
As you are able to go in recovery,
Wipe cache , dalvik cache, system, data install PA 3.97 flash pa_gapps then supersu v1.51(for root,also enable app+adb from developer option)
wipe cache and dalvck again and reboot..
P.S : Charge your battery first to 80% minimum and flash the rom.
If the above doesn't help,
Backup all you valuable data into pc, backup app+data through TB move it to pc and flash the factory image through fastboot.

Rohit02 said:
Try this.
As you are able to go in recovery,
Wipe cache , dalvik cache, system, data install PA 3.97 flash pa_gapps then supersu v1.51(for root,also enable app+adb from developer option)
wipe cache and dalvck again and reboot..
P.S : Charge your battery first to 80% minimum and flash the rom.
If the above doesn't help,
Backup all you valuable data into pc, backup app+data through TB move it to pc and flash the factory image through fastboot.
Click to expand...
Click to collapse
I ended up flashing the stock image and completely wiping all data. I then tried to install CM10.2 again and it still hung at the CM boot animation for about 15 minutes. It shouldn't take that long to flash, right?

alphamini said:
I ended up flashing the stock image and completely wiping all data. I then tried to install CM10.2 again and it still hung at the CM boot animation for about 15 minutes. It shouldn't take that long to flash, right?
Click to expand...
Click to collapse
Did you use the Franco.Kernel for the JSS build?
Sent from my Nexus 4 using Tapatalk 4

is it safe to restore nandroid backup twrp?

i installed a custom rom which i think changed the kernel and a few other stuff and now i want to go to the cloudypro 2 but im not sure how to get stock kernel lg g2 d802 back but anyway i have a nandroid backup of stock os if i were to restore it would my phone brick???/

Abu7500 said:
i installed a custom rom which i think changed the kernel and a few other stuff and now i want to go to the cloudypro 2 but im not sure how to get stock kernel lg g2 d802 back but anyway i have a nandroid backup of stock os if i were to restore it would my phone brick???/
Click to expand...
Click to collapse
If I understand correctly, you're currently on a ROM and wish to flash a different because the kernel changed?
If so, you can reflash the ROM your currently on and restore the original kernel. Make sure to wipe cache/dalvik/system (you don't have to wipe data) then relfash your ROM. You don't have to wipe data if flashing the same ROM you're currently on. If switching to another ROM, make sure to wipe everything except internal SD card (data/cache/dalvik/system).

simon_lefisch said:
If I understand correctly, you're currently on a ROM and wish to flash a different because the kernel changed?
If so, you can reflash the ROM your currently on and restore the original kernel. Make sure to wipe cache/dalvik/system (you don't have to wipe data) then relfash your ROM. You don't have to wipe data if flashing the same ROM you're currently on. If switching to another ROM, make sure to wipe everything except internal SD card (data/cache/dalvik/system).
Click to expand...
Click to collapse
If i flash the cloudypro rom what steps would i have to take-----would i have to change the kernel???? or baseband ???? im a noob

Abu7500 said:
If i flash the cloudypro rom what steps would i have to take-----would i have to change the kernel???? or baseband ???? im a noob
Click to expand...
Click to collapse
What ROM/baseband/android version are you on right now?

[Q] ROM Downgrading nexus 4

Hello everyone, I am a newbie in flashing ROM's rooting etc.
I am currently running on CM11 on my nexus 4 with android version 4.4.4 . I want to flash a CM11 based rom for my nexus 4 which is 4.4.2. Do I need to wipe data before flashing it?
ROM LINK THAT I AM GOING TO FLASH http://forum.xda-developers.com/nexus-4/development/rom-xl-z1-rom-v2-0-xperia-z1-style-t2630043
Thanks in advance!!

Make a nandroid backup of your current ROM and flash the new ROM after wiping cache, Dalvik, and system. If the phone bootloops, wipe the data in recovery. If the phone then boots, you know that some of the apps may not be compatible.

Thanks

balarishinoob said:
Thanks
Click to expand...
Click to collapse
Another option would be to use titanium back-up user apps, wipe data and then flash new rom. (definently shoul do an nandroid regardless)