Lolipop downgrade to custom kitkat - Xperia Z Q&A, Help & Troubleshooting

Hi guys i have a simple question. I really would like to flash this rom http://forum.xda-developers.com/xperia-z/development/rom-existenz-ultimate-1-0-0-light-dark-t2779949. It is looking very well. Right now i have lolipop on my xperia. Can I flash this rom straight away from my lolipop or should i downgrade it first to stock kitkat rom? http://forum.xda-developers.com/xperia-z/general/stock-rom-xperia-z-c6603-10-5-1-0-283-t2912254 (stock rom i'm talkin about).
Sorry for such a stupid question I just want to make sure cause i'm doing it for the very first time. I have rooted device without a recovery yet so should i begin with recovery and proceed to flash custom rom or to flash stock rom first. Thank you in advance for answer.

if your bootloader is locked.. yes, you can
note that you need to install recovery, wipe all (cache, dalvik cache, system, data) before flashing..
that means clean flash
but it's always nice to revert to stock before flashing custom or stock-based custom rom to make sure everything is in good shape

Related

Phone restarting after flashing to Stock GB ROM

Apologies, but since I am a new user, I was not allowed to post in the thread in developer section.
I had bought a pre owned phone, on Rocket ROM (GB based), however as S-Pen apps were not working I decided to go on the stock ICS rooted way.
I followed the instructions here:
http://forum.xda-developers.com/showthread.php?t=1424997
I had downloaded the stock INdian ROM
N7000XXKK3 ------ 2.3.5 2011 November------ N7000ODDKK1 ------------------------India -------------------------Download
Click to expand...
Click to collapse
I followed the steps, downloaded Odin, and put the TAR file in PDA section, and flashed. All goes fine without error, on the phone it says everything is installed successfully. However after the process the phone just keeps restarting after the Samsung logo.
Have I done anything wrong here? How do I rectify the mistake and get my phone working
Did you clear cache/dalvik or do a wipe in recovery menu ? Looks like it's stuck because of leftover data from previous rom
Akiainavas said:
Did you clear cache/dalvik or do a wipe in recovery menu ? Looks like it's stuck because of leftover data from previous rom
Click to expand...
Click to collapse
Umm, pardon my ignorance as I am migrating from an ancient Nokia device.
No, I had done no such thing, no backups too as I just had it for a few days and no data so to speak of.
Should I be doing a wipe in recovery menu? And doesn't flashing the device, formats the memory too?
I think it should, but for some reasons it does not. To get rid of boot loop, go into recovery and clear cache. Should boot properly then
Also, avoid doing a factory reset on stock ics. If clearing cache wont help, i'd suggest flashing gb stock rom, doing a wipe and then upgrading to ics as wiping under ics has caused people a lot of troubles.
Yes you should do a wipe of cache memory and dalvik cache. That is availible from recovery menu. And no they arent allways formatted when flashing a new rom.
To go into recovery, do this.
Device off > vol-up+home+power. And now you are in recovery mode.
Also, avoid doing a factory reset on stock ics. If clearing cache wont help, i'd suggest flashing gb stock rom, doing a wipe and then upgrading to ics as wiping under ics has caused people a lot of troubles.
Click to expand...
Click to collapse
Thanks, I had read up how much ever I could, and am pretty wary of the emmc bug. Thats the reason I am flashing to a GB based stock rom, and then the ICS stock rom.
The error I got earlier is by flashing to a Indian GB Stock ROM, should I yet clear cache memory in the recovery mode?
A little bit of googling tells me I should be flashing to a ROM with multiple files (different ones for PDA, Modem, CSC etc) hence I am also downloading the stock Europe based ROM. Now the query is would the stock Europe GB ROM, cause any issues to a Note bought in India?
Edit: I wiped the cache partition in recovery mode, but the bootloop persists. I will try flashing to the Europe GB ROM and update.
Thanks, folks was able to install the Europe stock GB ROM, which I later flashed to an Indian stock ICS ROM. I have rooted the phone by a very helpful guide by Dr Ketan, however I miss some of the functions available to me on the rocket GB based ROM. Especially an option to have a data on/off option in quick notifications.
What is the purpose of rooting the stock ROM? Can I delete the bloatware that comes pre-installed on the stock ROM, once the phone is rooted? If yes how?
Any safe custom ICS ROM's you guys recommend? If I am right the correct way right now seems to be to flash a safe GB based ROM everytime before you flash an ICS ROM? Correct?
Last but not the least, thanks to the folks who replied and guided me in the thread, XDA is a very resourceful place, if you search it thoroughly.
About notification toggles - they are available in some roms, in others - not.
As far as rooting is concerned - yes, you can delete almost all the bloatware. There is a thread with APKs that are safe to remove - check it out and feel free to delete everything you won't be using. How ? Simple file explorer with root capabilities will do. Here's the list, thanks to pulser_g2:
https://spreadsheets.google.com/spr...1gdDJRekl4QmkyNmIzUmRvX2h3UDVkQXc&output=html
Safe custom ICS ROMs - I'd say go for CM9. For me, AOSP is the only way to go with Android. If you want TouchWiz based roms, however, can't really help cause i've never used them - there are plenty in development section though.
Nope, you don't need to flash GB ROM everytime. The problem with wipe affects only stock ICS roms ( so with stock-kernel based roms from Samsung, yeah, that's recommended ). But if you're going to flash/change/update roms like CM9, Criskelo etc. there is no need to go back to GB everytime.
Hi i was on ICS stunner and flash via PC Odin Stock GB rom.
everything goes ok but now i'm stuck on Samsung logo (bootloop)
i have to do cache/dalvik wip but i have only stock recovery.
Is there any way to do that on stock recovery or i have to flash a CWM instead ?
And if i have to so how to do that ?
help guys
arturutrata91 said:
Hi i was on ICS stunner and flash via PC Odin Stock GB rom.
everything goes ok but now i'm stuck on Samsung logo (bootloop)
i have to do cache/dalvik wip but i have only stock recovery.
Is there any way to do that on stock recovery or i have to flash a CWM instead ?
And if i have to so how to do that ?
help guys
Click to expand...
Click to collapse
Download abyss from the following site:
http://downloadandroidrom.com/file/...rnel/AbyssNotekernel42CWTouchOriginalLogo.tar
Flash the file with PC odin then reboot into abyss recovery. You can then do the wipe.
If you need more information, go to this website:
http://rootgalaxynote.com/galaxy-note-root/how-to-root-galaxy-note-gt-n7000-method-2odinheimdall/

[Q] back to the beginning: how do you wipe N7 and flash a custom ROM?

Hey guys,
I've been running running a custom ROM on my N7 since December and even though I flash the updates (dirty flash) without any problem I want to make a clean flash one of these days..
Then I though, while I'm at it, why don't I completely wipe the whole thing and THEN flash the ROM? My N7 would be as clean as ever then..
So my question is, two fold: 1) is it really possible to completely wipe the memory space and 2) can I flash the desired ROM directly or do I have to first flash a factory ROM and then flash what want?
Thanks for the help!
EDIT: I just noticed I didn't post this on the QnA forum.. Could a MOD move this thread there please? Sorry for the trouble
Run the fast boot flash of the stock image. It will wipe everything and put it back to stock. Then load up new recovery, Adb push your ROM and flash it
Sent from my Galaxy Nexus
Post in the correct section and read the stickies in that section.

[Q] Few questions about Roms, flashing and Kernels

Hi guys. I just decided to use custom Roms because stock is slow. I checked some Roms and 2 interested me: CM 11 and Zaiben.
1. Could you tell me about differences between them? At the moment I have got orginal Android 4.1.2 V20B. Is it possible to flash Zaiben from V20B, I am asking because in Zaiben's thread there isn't any information about flash from v20b. There is only about flash from v20a. And I can't post in that thread yet.
2. Also what should I do before flash new Rom. Will wipe data/factory reset and wipe cache partition be enough?
3. And could you tell me if I want to flash new Kernel I just use install zip option? And which Kernels do you recommend guys?
Thanks in advance.
speeduser said:
Hi guys. I just decided to use custom Roms because stock is slow. I checked some Roms and 2 interested me: CM 11 and Zaiben.
1. Could you tell me about differences between them? At the moment I have got orginal Android 4.1.2 V20B. Is it possible to flash Zaiben from V20B, I am asking because in Zaiben's thread there isn't any information about flash from v20b. There is only about flash from v20a. And I can't post in that thread yet.
2. Also what should I do before flash new Rom. Will wipe data/factory reset and wipe cache partition be enough?
3. And could you tell me if I want to flash new Kernel I just use install zip option? And which Kernels do you recommend guys?
Thanks in advance.
Click to expand...
Click to collapse
1) Zaiben is a modified stock rom, cm is a completely independent rom based on open source project.
All you need to do is have the most updated recovery and you can simply flash right away.
2) If moving to zaiben you can probably dirty flash and don't need to wipe data since it's basically the same basis
If moving to cm you will most likely need a full wipe (system, data cache and dalvik
3) Yes - you canno't ask that question
Before you do any of the above you must unlock your bootloader to install cwm or twrp recovery!
Thank you for the help And last question: If I change Kernel what do I need to wipe after this?
speeduser said:
If I change Kernel what do I need to wipe after this?
Click to expand...
Click to collapse
Flashing kernel doesn't require wiping anything.
Each kernel has it's advantages and disadvantages. You need to read through their topics and find out which one will be more suitable for your needs.
Then I will try some. Thank you for help

Installing Custom Rom

Hi there, i am on stock rom 4.3 and i am considering to flash a custom rom. It is going to be my First flash of a custom rom and i am wondering if something is not working as it should, will i be able to return to stock with no problems? If i install a custom Kernel as well will kies install stock firm as usual (to return to stock)? Or the only method is a full backup and restore? Restoring method restores kernel too? Thank you for your help.
U must rooting your device, next install custom recovery and backup your rom, thats all, and next try the first install omni rom
I am already rooted. Omni is one of my thoughts. Should i flash a custom kernel after omni or it is not mandatory?

Flashing other roms than Andro X doesn't work

I just updated my bootloader and whenever i try to flash a rom, the booting process takes forever until i wipe my phone myself. But when i flash Andro X rom than it takes max. 3min to boot and then it works.
But i want another rom, how do i fix this?
Do you mean that when u flash lollipop based rom it gets bootloop? if yes then first flash stock lollipop firmware and then try flashing other rom. I mostly wipe my internal storage when going from Kitkat to lollipop it works for me.
Well Firstly Explain your problem clearly (I didnt quite understand it)
OK so here's my solution from what I understood..
1. Restore your stock rom Backup from recovery. Boot it once.
2. Now clean flash (Wipe System, Data , Cache, Dalvik cache) a lollipop based Rom (preferably try to clean flash cm 12.1 build)
3. Dont flash Gapps. First see if your phone boots up properly.
4. Configure data and reboot to recovery and flash Gapps.
If you dont have a Stock backup, Then download Stock Firmware images from gregor's thread and install via fastboot. Then follow from step2.
Hope this helps you.
Haroun16 said:
I just updated my bootloader and whenever i try to flash a rom, the booting process takes forever until i wipe my phone myself. But when i flash Andro X rom than it takes max. 3min to boot and then it works.
But i want another rom, how do i fix this?
Click to expand...
Click to collapse
Use easy installer first and get stock lollipop then u can simply root and install recovery then try roms?
sagar846 said:
Well Firstly Explain your problem clearly (I didnt quite understand it)
OK so here's my solution from what I understood..
1. Restore your stock rom Backup from recovery. Boot it once.
2. Now clean flash (Wipe System, Data , Cache, Dalvik cache) a lollipop based Rom (preferably try to clean flash cm 12.1 build)
3. Dont flash Gapps. First see if your phone boots up properly.
4. Configure data and reboot to recovery and flash Gapps.
If you dont have a Stock backup, Then download Stock Firmware images from gregor's thread and install via fastboot. Then follow from step2.
Hope this helps you.
Click to expand...
Click to collapse
My problem is that when i try to flash roms like CM12, Blisspop it doesn't stop booting, it was taking more than an hour so i shutdown my phone and when i flashed Andro X the booting took around 3mins.
So can anyone explain in easy steps how to fix this?
OK now I understand what your problem is. Give me your full specs (like which Model and and stuff). But if you follow what I said above it might fix your problem.
sagar846 said:
OK now I understand what your problem is. Give me your full specs (like which Model and and stuff). But if you follow what I said above it might fix your problem.
Click to expand...
Click to collapse
I got the XT1068
Haroun16 said:
I got the XT1068
Click to expand...
Click to collapse
are you fully wiping cache and userdata (factory reset) because this is most common problem moving between Roms that causes bootloops and why I include factory reset in my easy installer.
you can only dirty flash when going up (upgrading) the same rom - changing roms or downgrading nearly always causes bootloop / hang.

Categories

Resources