Hello all,
Firstly I would like to thank all the great people here, I've been struggling for hours with my dead Xperia Z and the amount of dedication and support I've found so far across all the members here is really impressing.
Let me first illustrate my case.
Firstly, I came here to root my phone and install a custom rom ships with Android N 7.1.2 (Resurrection Remix), I did went through all the newbies/how to threads and I did successfully ended up with Android N on my phone
Unfortunately, the device was not working probably in case of incoming or outgoing calls. No ringtone (already selected from Settings >Sound - played and heared), while in call it keeps ending the call unexpectedly, sometimes it feels very laggy that I couldn't even tap on anything. So I decided to give up until I found another rom that ships with Android N (XOSP), after successfully installing the rom, it starts out very smooth and I tested everything and it was ok, until yesterday the same issue still persists plus my device mic is not working no one can hear me while I'm talking neither from a headset mic nor the device mic. Finally I gave up and decided to rollback to the old lolipop stock rom.
Here's comes the current problem:-
1- I did flash 10.7.A.0.222 Customized MEA using flash tool and it's flashed successfully.
2- I'm now stuck with a dead black screen after sony logo.
I tried everything, changed the flashtool version, downloaded other ftf kernel file, used Xperia Companion and non of them worked for me. I did also tried what's listed in here https://forum.xda-developers.com/xperia-z/general/disaster-recovery-getting-z1-zu-z-zl-to-t2229250
I only can boot into fastboot or flashboot mode
I cannot copy files to my phone as it never appears as a storage media in my computer.
Any help will be much appreciated
Sorry for the long post
I never had this problem before, but have you try other ftf with lower android version like KK?
I see this problem on someone, everyone of them had this problem when they try to revert back to stock LP from N. Then someone suggest to flash KK ftf. You should try this if you haven't try this.
Sorry if my English is bad.
UPDATE:
when the first 7.0 nougat custom rom came, I'm on 5.1.1 rom with XZDual recovery. I made a backup for this rom and flash the 7.0 N rom only for trial then revert back to stock 5.1.1 that I backup before. Chippa's rom always came with latest built-in recovery so when I upgrade to nougat rom the XZDual recovery also lost (I don't have FOTA recovery, lol).
The step I made to revert back to stock is to do a FULL wipe of the phone (cache, davlik cache, data, system, AND internal storage), not a regular full wipe (without internal storage).
I put my backup stock rom file to my external sdcard (because the internal storage got wiped) and begin to flash, BUT NOT reboot into system, I reboot the phone to recovery instead (because I think the 5.1.1 rom works better with old TWRP so I reboot the phone to recovery first to get the old XZDual recovery).
After phone enter the old TWRP, I do a FULL wipe (cache, davlik, data, system, internal storage) once again to make sure everything OK, then flash the stock rom once again.
aand... it works. I did it 3-4 times to test new build of 7.0 n rom and never have any problem of reverting back.
But, I never test this method on newest 7.1.1 rom or 7.1.2 rom.
since you can't boot on LP rom, then try to flash KK rom.
Just install phone driver, flashtool, and download the KK ftf.
I'm sorry I can't provide you the full instruction because I never had this problem before, but you can search for this on N rom thread (the rom developed by Chippa). There is a guide made by someone on that thread.
Zerikwan said:
I never had this problem before, but have you try other ftf with lower android version like KK?
I see this problem on someone, everyone of them had this problem when they try to revert back to stock LP from N. Then someone suggest to flash KK ftf. You should try this if you haven't try this.
Sorry if my English is bad.
UPDATE:
when the first 7.0 nougat custom rom came, I'm on 5.1.1 rom with XZDual recovery. I made a backup for this rom and flash the 7.0 N rom only for trial then revert back to stock 5.1.1 that I backup before. Chippa's rom always came with latest built-in recovery so when I upgrade to nougat rom the XZDual recovery also lost (I don't have FOTA recovery, lol).
The step I made to revert back to stock is to do a FULL wipe of the phone (cache, davlik cache, data, system, AND internal storage), not a regular full wipe (without internal storage).
I put my backup stock rom file to my external sdcard (because the internal storage got wiped) and begin to flash, BUT NOT reboot into system, I reboot the phone to recovery instead (because I think the 5.1.1 rom works better with old TWRP so I reboot the phone to recovery first to get the old XZDual recovery).
After phone enter the old TWRP, I do a FULL wipe (cache, davlik, data, system, internal storage) once again to make sure everything OK, then flash the stock rom once again.
aand... it works. I did it 3-4 times to test new build of 7.0 n rom and never have any problem of reverting back.
But, I never test this method on newest 7.1.1 rom or 7.1.2 rom.
since you can't boot on LP rom, then try to flash KK rom.
Just install phone driver, flashtool, and download the KK ftf.
I'm sorry I can't provide you the full instruction because I never had this problem before, but you can search for this on N rom thread (the rom developed by Chippa). There is a guide made by someone on that thread.
Click to expand...
Click to collapse
Thank you so much for your reply. I will try it out. I really appreciate your contribution and I will keep you updated
Related
i recently flashed the eXistenZ Ultra 2, and im sure i did everything fine, after flashing the rom in recovery and flashing suprsu and wifi fix, i powered off the phone, and powered on but sony logo has apeared until now , and welcoming`s sounding 999..times. i cant turn it off, or i should say i cant do anything.
please help,
After flashing ROM and the fixes you should flash the 12.1.A.0.266 Firmware with FlashTool!
If problem still persists:
http://xda-university.com/as-a-user/how-to-recover-from-a-bootloop
Take a look at this site A recovery would be quite useful, but I think the kernel of eXistenZ ROM has one. If not, you'll find one in the development section. Otherwise, use the ADB as solution.
Good luck
Thanx for the post!
I used force shut down and then flash the 254 rom, and did all those things, and the problem occured again.
does the recovery software have to be the touch recovery? I use CWM v6 that enables with volume +.
and i use SuperSU fix.zip rather than superUser.zip and generally i flash rom, supersu fix.zip and wifi fix.zip. i flashed those three, before first booting, do i have to boot first before flashing wifi fix.zip?
eefathi said:
Thanx for the post!
I used force shut down and then flash the 254 rom, and did all those things, and the problem occured again.
does the recovery software have to be the touch recovery? I use CWM v6 that enables with volume +.
and i use SuperSU fix.zip rather than superUser.zip and generally i flash rom, supersu fix.zip and wifi fix.zip. i flashed those three, before first booting, do i have to boot first before flashing wifi fix.zip?
Click to expand...
Click to collapse
I think you need to flash 12.1.A.0.266 instead of 12.0.A.2.254 after flashing ROM. You could also wipe data, cache and dalvik cache, reflash eXistenZ ROM and SuperSU fix (or SuperUser but SuperSU should be ok), shut down the phone with the option in recovery and then flash the 12.1.A.0.266 with FlashTool.
It doesn't matter which recovery you take. Use the one you like best. I'm not quite sure, but to go sure, please flash the wifi fiz.zip after first boot up!
Schokonuss said:
I think you need to flash 12.1.A.0.266 instead of 12.0.A.2.254 after flashing ROM. You could also wipe data, cache and dalvik cache, reflash eXistenZ ROM and SuperSU fix (or SuperUser but SuperSU should be ok), shut down the phone with the option in recovery and then flash the 12.1.A.0.266 with FlashTool.
It doesn't matter which recovery you take. Use the one you like best. I'm not quite sure, but to go sure, please flash the wifi fiz.zip after first boot up!
Click to expand...
Click to collapse
thanx again,
i flashed the 266 kernel before the first boot, and the rom runs correctly,
but ive got some new problems:
1. performance, when i click on performance, it closes unexpectedly and says it has stopped.
2. i used go backup for backing up from data in 4.1, but in this rom i restored my apps,the apps installed correctly but goBackup says the data restoring successfully finished , but the data didnt restored, by the way at the time i backed up from my apps&data, i swapped memories with that linux code that this forum did.
eefathi said:
thanx again,
i flashed the 266 kernel before the first boot, and the rom runs correctly,
but ive got some new problems:
1. performance, when i click on performance, it closes unexpectedly and says it has stopped.
2. i used go backup for backing up from data in 4.1, but in this rom i restored my apps,the apps installed correctly but goBackup says the data restoring successfully finished , but the data didnt restored, by the way at the time i backed up from my apps&data, i swapped memories with that linux code that this forum did.
Click to expand...
Click to collapse
You're welcome
1. Do you have SuperSU installed? On AOKP ROM I'm running it asked for superuser permission for ROM Control (the control center implemented in the settings of the ROM). Maybe it'll ask you if SuperSU is installed. Otherwise, because it is after the first boot it needs to rebuild cache and so on.. If problem persists after reboot, just use an other clock speed controler (No-frills CPU, SetCPU..)
2. If you did that at the same time, maybe Go Backup didn't really backup your data. Try again, if it doesn't work and if you have a nandroid backup (backup from recovery) you can go into recovery, then to advanced restore and restore data. Otherwise your data is unfortunately gone I think :/
PS: I prefer Titanium Backup
Hello,
I flashed CM11 yesterday and everything went alright. This morning I noticed I had an update for it and proceed to do it.
After the instalation and optimizing all apps it asked me for my simcard PIN and after I unlocked the phone it just went back to the cyanogenmod logo over and over.
I tried to reboot phone but it didn't help.
I've tried to search for similar threads but since i'm a newbie (first time I ever flashed anything) to this I decided to create this thread.
What should I do?
Thank you!
try to use flashtool. google it on how to use flashtool or check other threads.
So I guess i have to flash a stock ROM with flashtool and do it all over again right?
And btw, any reason you guys might think It got stuck in bootloop after I updated CM11? I came from a fresh stock rom. I'm kinda scared it might happen again after the reinstall.
Can't you enter recovery to flash a nandroid backup? (If you have one)
If not, you have two options to choose from.
Fastboot or flash a kernel with CWM or TWRP.
ADB push a zip file of a ROM and flash that.
Flash an FTF file using flashtool and start all over again.
There are many reasons why you're stuck in bootloop at the moment.
With the info you provided, there's no way of telling what caused it for you.
Well, i flashed stock ROM with flashtool, installed CM11 and I had no problems.
Went to settings and OTA update was available. Downloaded it and installed it, stuck in loopboot again. I just can't figure out what's wrong. My phone has bootload unlocked.
Might just do it all over and not update, is that a problem?
Don't use OTA, just download and flash updates manually using recovery.
In the future, for your ease, if this happens again just wipe the phone very clean (cache, /system, /data etc except /boot) and then re-flash the CM zip that you have.
It is a good practise if you make a nandroid backup before flashing a newer version of zip, in case of breaks. Or, you can have Titanium Backup to backup your apps automatically (pro version) everyday, so that you can be ready if there will be something bad happen.
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.
Whichever flashing method I use (TWRP, fastboot) Whichever rom I use (I tried clean stock, pre rooted, MM, LP, backups), I can't get past the animation screen. Even restoring a backup through TWRP gets stuck at the same spot. The only ROM that works is LineageOS (based on Android 7.1). I tried wiping various combinations of dalvik cache, data, cache, system, internal storage - still always stuck on boot animation. I tried leaving it for a long time always, the longest was over 2 hours. I feel like I'm missing wiping something since it seems like the issue is going from a 7.1 rom down maybe?
More info: I was using SLiM ROM (MM 6.0.1) for a while but it got extremely slow and poor battery life after a while. I flashed LineageOS for Z3C and it worked fine, but wasn't my cup of tea, so I wanted to go back to stock-based. I figured I'd try eXistenZ (MM 6.0.1). The instructions said to be on 23.5.A.1.291 first, then root it, and then flash the existenz zip. I didn't downgrade to .291 the first time and it didn't work. Second time I flashed a stock D5803_23.5.A.1.291 (which booted up normally). Went through the rooting process (as seen here), and that worked fine. But the next step of flashing eXistenz didn't work. I tried again from the start, but this time I couldn't boot into after flashing 23.5.A.1.291 again. This is where the problem started. I tried Slim and various roms using fastboot, various versions of twrp, and even a 6.0.1 backup through twrp. Always regardless of ROM, it gets stuck on boot animation. Except for LineageOS.
Hi, I'm in the exact same situation, I have Lineage OS 7.1 installed and I can't go back to any custom ROM based on Android 6.0 stock, all I get is always a bootloop. The only other ROM I can install is Sony stock via Flashtool. I really don't know what the problem is, please let me know if you manage to solve this weird problem.
Install old twrp, wipe /apps_log.
Or use emma to get a clean device again.
I solved the issue installing stock Android 6.0 with Flashtool, twrp 3.0.2 and then flashing ROM. :good:
Hi everyone, I'm here because i have problems with my phone and i want to fully restore. To do this i would like to install a new ROM, but from what i've seen, to install a ROM is necessary to have the stock JB 4.1.2 on the device, while i have CyanogenMod 11 (4.4.4) running.
This wouldn't be a problem if i could use Odin, but apparently my USB port has something wrong, and i cant connect my phone to any PC, so i cant flash in that way. Luckly i can access to the custom recovery (CWM), so i 'd like to ask if there is a way to flash the stock firmware via CWM.
Instead, If I can install a ROM starting directly from CM11 without restoring stock JB, or if i'm missing something important, let me now, i would appreciate a lot
Thank you in advantage. (Excuse se for any misspelling, I'm not English)
What kind of problems do you have?
If you can access CWM recovery there's no need to install stock in order to flash a new ROM, just be sure to wipe caches and data before installing the new one to avoid related bugs; and you will probably need to update the recovery to TWRP if you want to flash one of the most recent ROMs
It's always recommended to create a backup before everything else.
Peace
Hi, thank you for then anwer Well, it would be a long list of problems ^^ The biggest one though is the fact that if I'm in AeroMode everything works as always, sometimes bugged but nothing exceptional, but in the moment i switch AeroMode off and digit the SIM pin, the phone turns off and then enters in a bootloop(vibrating every 1 minute like before entering the main window, but it remains stuck) that is solvable only pressing for 8/10 secs the POWER button and restarting it. I can't have a phone which is not able to make voice calls :/ Back to the problem, so if i'm not misunderstanding anything, I dont need to reverto to stock and then reflash the new ROM? Because, for example, in the main page of CM13 it's written:
ROM Firmware Required: Stock + CWM compatible with KitKat
and that's the origin of my post... But in case, which wipe should i do? Dalvik + wipe data/factory reset?
OK, the thing is that you need stock + CWM at minimum, it means you can't install it if you are on gingerbread; but if already installed something higher than 4.1 you can go from there.
First create a backup then wipe cache, wipe dalvik, factory reset and install your preferred ROM
Ohhh, that makes sense.... Ok, so i will wipe what you said and flash the new ROM! You saved me a lot of time, thank you so much!