I have the batman rom installed on my g95ff now since my stock rom got boot looped when i tried to flash a boot logo that was a size too big.When that happened i flashed the stock firmware with odin aswell as stock recovery and it let me clear my cache/factory reset my phone to fix it.Sadly i lost my bootlogo and boot animation collection i had stored but i had most of my important apps backed up with titanium,so to make up for the lost data i rerooted with twrp,installed the batman rom and restored my apps back.The rom is really neat since i can customize more ui things such as the status bar aswell as my nav bar color which couldnt be done on the stock rom.So now that im familiar with installing roms,would i be able to try other ones simply by reflashing the stock firmware over the batman rom and reinstalling twrp?
So you're asking how you can try other custom ROMs?
You don't need to flash the stock ROM and flash TWRP every time you want to try a new custom ROM. It's MUCH easier than that.
You just need to backup your apps as normal with Titanium Backup, then boot into TWRP. From the Wipe menu, wipe system, data, cache, and dalvik-cache.
Then just flash the new ROM zip file as normal in TWRP, and you're done.
the_scotsman said:
So you're asking how you can try other custom ROMs?
You don't need to flash the stock ROM and flash TWRP every time you want to try a new custom ROM. It's MUCH easier than that.
You just need to backup your apps as normal with Titanium Backup, then boot into TWRP. From the Wipe menu, wipe system, data, cache, and dalvik-cache.
Then just flash the new ROM zip file as normal in TWRP, and you're done.
Click to expand...
Click to collapse
So as long as you wipe your phone you can install custom roms over anough anoughter custom rom.Sounds simple enough then.
iostoandroidconvert said:
So as long as you wipe your phone you can install custom roms over anough anoughter custom rom.Sounds simple enough then.
Click to expand...
Click to collapse
Yep, the "System" partition is where the ROM is installed. When you wipe that, you're essentially wiping the ROM from your phone.
Related
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
Just as title states, I always spend a lot of time after restoring apps and data from flashing a new ROM getting my screen and layout and folders and widgets as they were prior to flashing a new ROM.
Is there a way to restore all this quickly?
NO
The problem you're having is when you install a different ROM you usually "Wipe" everything. If you don't wipe /data then everything you have is still there. However you will have problems going from one custom ROM to another, as each developer has made some tweaks to the system packages.
Generally speaking, if you are running a "Stock Odexed" ROM you could possibly dirty flash a "Custom Odexed" ROM.
Same goes for Deodexed to Deodexed. You will have problems if you try to cross dirty flash a ROM.
So the simple answer to your question is NO there is no easy way, even if you backed up your Applications using a tool like Titanium Back Up.
If you are just updating the same ROM, the developer will say to either Clean Flash (wipe everything) or Dirty Flash (IMO still wipe cache and dalvik). If you can dirty flash everything will still be just as you set it up.
Got everything restored already, I'll have to just suck it up then I guess.
Just makes me wonder how flashaholics do it.
I am having a problem installing a custom ROM... I root the device using CF-Autoroot and Philz Recovery. TIBU confirms the phone is rooted.
I boot into recovery, then try to install a ROM which is on the ext-SD card. I do a full wipe using Philz Recovery.
When I try to restart the phone, I get a bootloop, NO MATTER WHICH ROM I am trying to install. Then I have to go through the hassle of downloading the original firmware using KIES
and start all over again.
Any help or thoughts will be greatly appreciated.
Wipe before flashing
You must do the full wipe before flashing a new ROM, not after (Because if you are wiping /system after flash, you are leaving your device without OS)
And remember, flash gapps after first boot, not after flashing The rom
P.S you can do a full Nandroid Baclup before flashing a new ROM, because if you get stuck in bootloop again, you can simply enter to recovery and restore backup
Thanks for your input, but that's exactly what I did.. except for the backup part.
I cant seem to find my way to FULLY wipe when I want to flash or try a new ROM. I just installed an RRO that resulted in SystemUI crash, I then went to reflash the ROM, same results. Decided to WIPE in TWRP and reflash the rom, the SystemUI FC is still there ! Wipe, Flash ROM, then Wipe, same result...Any help ? What's wrong with my TWRP ? Im on the latest.
I just restored an old backup, and I have the same FC of system UI !
Ensifolk said:
I cant seem to find my way to FULLY wipe when I want to flash or try a new ROM. I just installed an RRO that resulted in SystemUI crash, I then went to reflash the ROM, same results. Decided to WIPE in TWRP and reflash the rom, the SystemUI FC is still there ! Wipe, Flash ROM, then Wipe, same result...Any help ? What's wrong with my TWRP ? Im on the latest.
I just restored an old backup, and I have the same FC of system UI !
Click to expand...
Click to collapse
TWRP doesn't wipe the vendor partition where the layer is kept. You have to manually mount the vendor partition in TWRP then use TWRPs inbuilt file browser to go into the overlay folder and delete the layer files, this will stop the System UI FCs
There are also flashable stock vendor partition files available in some of the threads in the Android development section (can't remember where exactly) flashing them will restore it to stock.
Finally, you can fastboot flash the whole stock ROM from a pc and this will also remove them.
Deleting them using TWRP is probably the easiest.
Ensifolk said:
I cant seem to find my way to FULLY wipe when I want to flash or try a new ROM. I just installed an RRO that resulted in SystemUI crash, I then went to reflash the ROM, same results. Decided to WIPE in TWRP and reflash the rom, the SystemUI FC is still there ! Wipe, Flash ROM, then Wipe, same result...Any help ? What's wrong with my TWRP ? Im on the latest.
I just restored an old backup, and I have the same FC of system UI !
Click to expand...
Click to collapse
Batfink33 said:
TWRP doesn't wipe the vendor partition where the layer is kept. You have to manually mount the vendor partition in TWRP then use TWRPs inbuilt file browser to go into the overlay folder and delete the layer files, this will stop the System UI FCs
There are also flashable stock vendor partition files available in some of the threads in the Android development section (can't remember where exactly) flashing them will restore it to stock.
Finally, you can fastboot flash the whole stock ROM from a pc and this will also remove them.
Deleting them using TWRP is probably the easiest.
Click to expand...
Click to collapse
My index thread has links to the flashable vendor zips:
http://forum.xda-developers.com/nexus-6p/general/index-huawei-nexus-6p-t3213583
It's the easiest solution.
Ok, so I am not new to flashing rom but for some reason I am having huge issues trying to install clean stock OOS 5.1.4 rom. Just want to double check I am not doing anything stupid since I mainly been flashing custom roms (xXx rom mainly).
So I simply wipe dalvik/ART cache, cache, system and data (want to start off completely clan) then flashed the OnePlus5Oxygen_23_OTA_037_all_1807181258_7b4b6.zip file in TWRP.
I am currently on the latest blue TWRP and after flashing, it will try to boot but reboots back into TWRP. I have tried the zip file from a number of sources and they all do the same. Am I missing something here?
UPDATE: I did do something stupid after all. I forgot that my Oneplus was decrypted. So all I had to do was go into TWRP and go to Wipe and format data to re-encrypt it.
Z-Blade said:
Ok, so I am not new to flashing rom but for some reason I am having huge issues trying to install clean stock OOS 5.1.4 rom. Just want to double check I am not doing anything stupid since I mainly been flashing custom roms (xXx rom mainly).
So I simply wipe dalvik/ART cache, cache, system and data (want to start off completely clan) then flashed the OnePlus5Oxygen_23_OTA_037_all_1807181258_7b4b6.zip file in TWRP.
I am currently on the latest blue TWRP and after flashing, it will try to boot but reboots back into TWRP. I have tried the zip file from a number of sources and they all do the same. Am I missing something here?
Click to expand...
Click to collapse
When starting fresh, wiping of internal storage should be considered. I recommended 2 guides here https://forum.xda-developers.com/on...nos-beta-1-android-oreo-t3710003/post77205633