How to go back stock rom from custom rom - Xperia Z5 Q&A, Help & Troubleshooting

Hi guys.I'm using resurrection 5.8.5 rom right now.I don't know how to go back stock rom. Can someone teach me with details.Thanks..

hemre2 said:
Hi guys.I'm using resurrection 5.8.5 rom right now.I don't know how to go back stock rom. Can someone teach me with details.Thanks..
Click to expand...
Click to collapse
If you made a backup with TWRP you can format /system, /data , /cache, wipe dalvik cache
and restore /data , /boot and /system
If you don't - not sure if there's a flashable 32.4.A.1.54 firmware available,
you must likely need to start anew with XperiFirm & FlashTool.
Before that make sure you backup your data on internal storage (and microSD just in case)

Related

Internal Memory full?

Hi all, I just flashed CM7 using the newest clockwork mod recovery. Now it says my internal memory is full. I havnt deleted anything internally since I got the phone. What is the best way to format that memory and reinstall a fresh copy of CM7?
Kaczman said:
Hi all, I just flashed CM7 using the newest clockwork mod recovery. Now it says my internal memory is full. I havnt deleted anything internally since I got the phone. What is the best way to format that memory and reinstall a fresh copy of CM7?
Click to expand...
Click to collapse
Go to recovery......in recovery go wipe cache, factory reset/data, go to mounts/storage and format system, data, cache....go to advance and delete dalvik cache..... then just install zip from sd, choose zip, flash taht **** and reboot your phone
Awesome!! thanks bud!
I don't mess with CWM wiping partitions anymore, I wrote a flashable script for that - a long time ago there was an issue with that on CWM 4.0.0.8
A member has confirmed that A01 wipe will be okay if you turn off and have no ROM installed, you will still be able to get to CWM and flash whatever you want.
A01 wipe will format /cache, /data and /system
B01 wipe will format /cache and /data
Use as needed.
I keep a backup memory card with my phone at all times that has A01 wipe, B01 wipe, and my original CWM backup of my stock system on it, in case I ever need to go back to stock if something goes wrong.
Attached are the scripts, just throw these on your sdcard and flash like normal in CWM if you need to, before installing a ROM or patch if needed.
Blue6IX said:
I don't mess with CWM wiping partitions anymore, I wrote a flashable script for that - a long time ago there was an issue with that on CWM 4.0.0.8
A member has confirmed that A01 wipe will be okay if you turn off and have no ROM installed, you will still be able to get to CWM and flash whatever you want.
A01 wipe will format /cache, /data and /system
B01 wipe will format /cache and /data
Use as needed.
I keep a backup memory card with my phone at all times that has A01 wipe, B01 wipe, and my original CWM backup of my stock system on it, in case I ever need to go back to stock if something goes wrong.
Attached are the scripts, just throw these on your sdcard and flash like normal in CWM if you need to, before installing a ROM or patch if needed.
Click to expand...
Click to collapse
hey Blue just outta curiosity has anyone confirmed having issues with wiping through CWM with the new recovery or has the issue carried over from the 4.0.0.8/9?
I'm pretty sure I don't remember anyone having issues directly with cwm 4.0.0.9, and it was only a problem with 4.0.0.8 - even then not everyone experienced it.
I haven't tried the new recovery available yet, I meant to get to it this weekend, but it doesn't look like i'll get a chance to fit it in my schedule. I haven't seen my lady in just over a week, so spending the weekend with her.
Hopefully over the next week i'll get a chance to bring myself up to speed with it, I don't expect to go back to 4.0.0.9 once I move up to the new CWM recovery.

[Q] Ext4 partition

I have a question about ext4 convert here.. Let's say I've flashed to a custom rom that converts my phone's partitions to ext4, once I flash a stock firmware on top of it, do the partitions stay in ext4 or back to rfs?
No it converted to rfs
Sent from my GT-I9003 using XDA App
Ok... What about I wipe date from cwm? Does that revert the partitions back to rfs as well?
I don't think by wiping your data cache u can revert back to rfs. you have to reflash for rfs.
e398rokr said:
I have a question about ext4 convert here.. Let's say I've flashed to a custom rom that converts my phone's partitions to ext4, once I flash a stock firmware on top of it, do the partitions stay in ext4 or back to rfs?
Click to expand...
Click to collapse
Wiping doesnot changes the partition format. When you flash a new firmware the partitions will be converted to rfs.
send from gt-i9003 using android keyboard
I have a big Q!
Once i flashed KPH and i tried to convert to ext4 via CWM, but i had a problem, after doing a backup i flashed the ext4 zip, when i tried to restore the nandroid i stuck on bootloop!
Any idea of what could have caused this?
Lucasred said:
I have a big Q!
Once i flashed KPH and i tried to convert to ext4 via CWM, but i had a problem, after doing a backup i flashed the ext4 zip, when i tried to restore the nandroid i stuck on bootloop!
Any idea of what could have caused this?
Click to expand...
Click to collapse
I think it is not compatible with xxkph. Try wiping cache and dalvik cach
send from gt-i9003 using android keyboard
sirilpta said:
I think it is not compatible with xxkph. Try wiping cache and dalvik cach
send from gt-i9003 using android keyboard
Click to expand...
Click to collapse
Could be the reason, but many guys at another forum did it and it worked perfect for them, i think the error could be in the flash of kph, so the whole process went bad
Lucasred, i had the same problem twice. But i had tried it with XXKPQ.
can i converted file system too ext4 on KPU
google translate
user_i9003 said:
can i converted file system too ext4 on KPU
google translate
Click to expand...
Click to collapse
Yes, I'm using it.
For the others: the restore of the nandroid backup after the conversion failed whenever I tried to convert the phone before deodexing it. Try to deodex first, and then convert.
What I found weird was that the error was "not enough space", but when I tried to restore the backup on rfs it worked, doing the same after the ext4 conversion gave the error. I don't know how you could convert the partitions in ext4 with an odexed rom, I didn't look for any solution, maybe if you don't want to deodex your rom you could try to remove some system apps or something like that before the nandroid backup, in order to get more space.

[Q] Can i flash this rom over my previous?

http://forum.xda-developers.com/showthread.php?t=1678485
sorry guys, i am using cm7.1.0 kernel version [email protected]#1
can i put this in my folder and just flash it and gapps using cwm? or do i need to flash a different kernel?
sorry this is my 2nd time switching through between rom, just experimented switching to miui using cwm and now wanna try those in xda.
Thanks for commenting.
Go to Recovery.
Perform a nandroid backup of your current ROM.
Wipe All partitions - system, boot, data ,cache, dalvik cache {except your SD card}.
Install Zip from SD card & navigate to your ROM from your SD card.
Flash G Apps attached in the OP of the ROM.
Reboot

[Q] Encryption unsuccessful on every custom rom

facing this weird error Coming From stock GPE Rom with Stock kernel XT1032 Model with unlock bootloader i am on TWRP 2.7 this one(http://forum.xda-developers.com/show....php?t=2759058). Before flashing the rom I wiped the cache system partition except the internal data partition (Internal storage)
i have Flashed the rom then slim gapps when i boot the rom i am faced with this error
Encryption unsuccessful
Encrypton was interuupted and cant complete the data on your phone is no longer accesible
and RESET button at the bottom when i pressed that button it goes in recovery and formats something and again I am faced with that Encryption unsuccessful screen. I Tried Omni Rom too but still Facing with this error
i have never encrypeted my phone!!! pls help really wanna try this rom
Make full wipe including internal memory
everything will be wiped including the existing rom
adb push any rom of yourchoice and install it asusual
commad
adb push yorromname.zip /sdcard/
Click to expand...
Click to collapse
all will be fine.
this error is due to the mismatch partition of ext4 and f2fs
Thanks for the help really appriciated also do I have to do everytime when flashing the rom or only for rom utilizing f2fs partition coz I really don't wanna wipe internal data every time, Also are all the custom rom based on f2fs partition? Really confused
Tried wiping internal storage still Facing same error :crying:
i believe Stock GPE uses Ext4 and all custom rom uses F2fs
So what to do really help needed??
So how do i convert to F2fs to flash custom roms

F2FS for amami

This is a simple .zip file you can flash on any amami, which uses a ramdisk like the combinedrootfs from Cyanogenmod 11. Your device needs to have a f2fs-compatible kernel, for example this one.
This zip is only modifying your current ramdisk. It will delete the normal fstab and add a binary, which detects if your system, data and cache partition are formatted with f2fs and create a new fstab every boot. It will also flash a twrp recovery, which is modified to work with f2fs.
Ok but... what is f2fs?
It is a new file system, which is especially designed for flash-based storages, like our phones. It will give you much better reading and writing speed.
Installation:
1. Be sure, that you have a f2fs-compatible kernel and your ramdisk's structure is similar to Cyanogenmod's one. If you are on any aosp-based rom, the ramdisk will be compatible anyway.
2. Flash the .zip file from a custom recovery
3. Reboot recovery
4. Now go to advanced wipe and you can change the file systems of system, data and cache to f2fs.
Some more information:
If you convert cache to f2fs:
->No data will be lost
If you convert data to f2fs:
->Your whole internal storage will be wiped. backup your data before you decide to do that!
If you convert system to f2fs
->You need to flash your rom again. You need to modify the updater script of your rom before that like this
OK. I formatted data with f2fs, but want to flash a new rom. What to do?
You need to flash a kernel with f2fs and this zip, no need for any wipes
Download:
http://www.androidfilehost.com/?fid=23578570567713678
For Developers:
You can include this in your rom like this: https://gist.github.com/CoolDevelopment/54ede52a1e075da48151
XDA:DevDB Information
F2FS for amami, Tool/Utility for the Sony Xperia Z1 Compact
Contributors
CoolDevelopment, NovaFusion
Version Information
Status: Testing
Current Beta Version: 2.0
Beta Release Date: 2014-07-16
Created 2014-07-16
Last Updated 2014-07-16
@CoolDevelopment
So, if I corectly understand this zip will erase all data including internal storage? Am I right? But about if I use nightlies? Will I neen to flash it every time after update?
da900 said:
this zip will erase all data including internal storage?
Click to expand...
Click to collapse
It won´t erase your internal storage , I flashed and everthing is there !
pvillasuso said:
It won´t erase your internal storage , I flashed and everthing is there !
Click to expand...
Click to collapse
OK. Thanx. But will erase all data, so I need to install all apps again?
da900 said:
OK. Thanx. But will erase all data, so I need to install all apps again?
Click to expand...
Click to collapse
Nope , it won´t erase any data, files, apps, etc from your internal o external storage
from the OP :
This zip is only modifying your current ramdisk. It will delete the normal fstab and add a binary, which detects if your data and cache partition are formatted with f2fs and create a new fstab every boot. It will also flash a twrp recovery, which is modified to work with f2fs.
It does not erase anything. It makes your current ramdisk compatible with f2fs. If you just flash this notjing changes. But you can convert you cache and data partition to f2fs after flashing the zip with the recovery. If you do that, all your data is lost.
If you have converted your partitions to f2fs and flash a new rom, you need to flash a f2fs-compatible kernel and this again.
CoolDevelopment said:
It does not erase anything. It makes your current ramdisk compatible with f2fs. If you just flash this notjing changes. But you can convert you cache and data partition to f2fs after flashing the zip with the recovery. If you do that, all your data is lost.
If you have converted your partitions to f2fs and flash a new rom, you need to flash a f2fs-compatible kernel and this again.
Click to expand...
Click to collapse
OK. Thanx. I will try. But if I will update the ROM (for example, when using CM nighlies), when there is no need to wipe all data, will I still need to perform all these steps to convert data partion to f2fs? I mean will I need every time restore all data again?
da900 said:
OK. Thanx. I will try. But if I will update the ROM (for example, when using CM nighlies), when there is no need to wipe all data, will I still need to perform all these steps to convert data partion to f2fs? I mean will I need every time restore all data again?
Click to expand...
Click to collapse
You need to flash a f2fs compatiblr kernel and this zip, no wipes
But if you don't do that your rom will bootloop
Sent from my Xperia Z1 Compact using XDA Premium 4 mobile app
New version!
I uploaded a new version with /system support and a few fixes.
I also updated the op.
Have fun!
I would guess that if you have f2fs you should flash the appropriate kernel only if switch ROMs or if the nightly build brings kernel changes.
If you install kernel with f2fs support and your partition is f2fs formatted, I think your data should be safe even between ROM changes.
Somebody please confirm my assumptions.
I hope oshmoun will have the time to build PAC ROM with oms kernel, built in [emoji12]
idimitro said:
I would guess that if you have f2fs you should flash the appropriate kernel only if switch ROMs or if the nightly build brings kernel changes.
If you install kernel with f2fs support and your partition is f2fs formatted, I think your data should be safe even between ROM changes.
Somebody please confirm my assumptions.
I hope oshmoun will have the time to build PAC ROM with oms kernel, built in [emoji12]
Click to expand...
Click to collapse
Every rom flashes a boot.img. This boot.img contains a zImage and a ramdisk(on sony devices it is a bit more complicated but that's enough for now).
Using f2fs needs:
1. A zImage(kernel) with f2fs support
2. A ramdisk with f2fs support
This zip modifies the ramdisk for compatibility with f2fs.
You need to flash a f2fs kernel manually.(for example my moshkernel)
And everytime you flash a new rom, you have to modify the contents of the boot.img again
And why don't I just let you flash a modified boot.img? It is only one file.
It would only be compatible with one rom. This is compatible with any rom and boot.img, which uses the ramdisk architecture like cyanogenmod(combinedrootfs).
I hope I could explain it well
If i want to format my system to f2fs, i just need to do step 6 as in your link and then zip back the rom?
So when ever i decide to do full wipe everything, will my system, data, cache format still in f2fs format?
Sent from my Candy Amami using Tapatalk
najar360 said:
If i want to format my system to f2fs, i just need to do step 6 as in your link and then zip back the rom?
So when ever i decide to do full wipe everything, will my system, data, cache format still in f2fs format?
Sent from my Candy Amami using Tapatalk
Click to expand...
Click to collapse
If you use TWRP yes
But if you want to revert back go to advanced wipe->change or repair filesystem/change filesystem-> ext4
CoolDevelopment said:
If you use TWRP yes
But if you want to revert back go to advanced wipe->change or repair filesystem/change filesystem-> ext4
Click to expand...
Click to collapse
i try to change data to f2fs format then flash new rom, mosh kernel, and this patch and then reboot system. i got bootloop. i didnt do step 6 yet.
najar360 said:
i try to change data to f2fs format then flash new rom, mosh kernel, and this patch and then reboot system. i got bootloop. i didnt do step 6 yet.
Click to expand...
Click to collapse
Can you tell me which rom?
I tried it with slimkat and it worked well
And what kind of bootloop? Do you see the sony or rom bootlogo?
And please use MoshKernel 0.1.2
CoolDevelopment said:
Can you tell me which rom?
I tried it with slimkat and it worked well
And what kind of bootloop? Do you see the sony or rom bootlogo?
And please use MoshKernel 0.1.2
Click to expand...
Click to collapse
i'm using candykat
my step, flash f2fs patcher, reboot recovery, change cache and data to f2fs format. reboot recovery again, wipe everything. checking cache and data still in f2fs. flash candykat, mosh kernel, f2fs patcher. reboot system. sony bootlogo appear, rom bootanimation appear. stuck for 10 minutes.
anything wrong with my step?
najar360 said:
i'm using candykat
my step, flash f2fs patcher, reboot recovery, change cache and data to f2fs format. reboot recovery again, wipe everything. checking cache and data still in f2fs. flash candykat, mosh kernel, f2fs patcher. reboot system. sony bootlogo appear, rom bootanimation appear. stuck for 10 minutes.
anything wrong with my step?
Click to expand...
Click to collapse
Did you use the latest MoshKernel?(0.1.2)
The new f2fs-patcher zip is not compatible with the old MoshKernel
CoolDevelopment said:
Did you use the latest MoshKernel?(0.1.2)
The new f2fs-patcher zip is not compatible with the old MoshKernel
Click to expand...
Click to collapse
yeaps. i'm using 0.1.2 version.
najar360 said:
yeaps. i'm using 0.1.2 version.
Click to expand...
Click to collapse
That's strange. I tried it with slimrom, which is the base for candycat as far as i know, and it worked perfectly.
CoolDevelopment said:
That's strange. I tried it with slimrom, which is the base for candycat as far as i know, and it worked perfectly.
Click to expand...
Click to collapse
is my step correct?
edit : try slimkat and it work.

Categories

Resources