Hi, few month ago, I have unlocked the bootloader, rooted my phone, and installed CWM and CM 11.
It was quite buggy, and OTA updates didn't work, and I needed something more stable.
Yesterday, I wanted to reboot into recovery, and try flashing SlimKat or a newer CM if I don't like the Slimkat.
The combination of keys for Recovery didn't work and there wasn't any reasonable way to get around it.
On adb, the phone got detected, but offline, so I wasn't able to reboot into recovery this way.
Fast forward couple of hours, I have tried flashing about everything, but didn't manage anything besides being able to pass adb commands.
Now,
- when I turn on the phone the phone hangs on the Sony logo and I have to force turn it off
- I get the phone on ADB even when it keeps hanging on the Sony logo
- I can get into Fastboot by holding the up button on conneting to computer
- I have flashed the boot.img from CM11 for XPeria P to bring CWM back, but didn't happen, or did happen, but I can't get into recovery
- "adb reboot recovery" brings me to the same old hanging SONY logo.
- pushing whatever on boot doesn't help > SONY logo
Please help!
Why not just flash stock with flashtool?
[SOLVED] Partially...
I have downloaded FTF file for the device, and manage to flash it using Flashtool (worked only if I flashed incl. Kernel) and got the device up and running. I tried reflashing CM and Slim again, but none worked as I still wasn't able to get into recovery, so I reflashed once more. Finally, the device is working - with the stock firmware, at least...
davidszedely said:
worked only if I flashed incl. Kernel
Click to expand...
Click to collapse
This is a solution. When you flashing CM you need to flash CM kernel too. In some cases kernel needs to be flashed several times(for example before flashing CM and after flashing it).
Sorry for my bad English.
Thanks a lot for explanation. I'm happy to have the stock now, and will probably stick with it for the time being.
Hi guys,
I'm always experimenting with my U, but this time it happened something strange.
After one of my many tests i reflashed transcendence kernel and when i was about to leave recovery it asked me if i would like to make sure that other recovery didn't reflashed after reboot automatically and i said yes.
The problem is that now i can't get rid of this kernel!!
I enter recovery and flash another kernel, everything ok, but after i reboot i still have the old transcendece kernel.
Already relocked bootloader and flashed stock fw with sony pc suite and unlocked again and nothing, the damn kernel is still there!!!
What can i do? Anyone knows what this is?
:crying:
Mods can close this thread.
Problem solved.
Answer: Recovery got retained, hence the bootlogo is always the same. Flash new recovery to solve it.
Sent from Hacker's U
After trying a few custom ROMS, I decided to revert to full stock. CM12 did mess up with my recovery : it installed Cyanogen Recovery, even if I didn't want to and even if the option to install it was disabled in the dev settings ! Since then, I can't flash another ROM or if I can, it will be buggy for no reason (apps not working, etc.).
So I decided to revert to stock with a proper FTF file using Flashtool in flashmode...however, it won't work !
It won't flash the rom properly : the flash last 3 seconds. It says it went fine but as you can imagine, in 3 seconds, it didn't flash anything really. As a mater of fact, if I'm booting the tablet, I'm still under CM12.
Is there a way to revert to stock in another way ? I tried using Fastboot, after extracting the .ftf file but same issue : it looks like it's flashing but it's way too short to flash the system.
Any idea ?
Screw CM12 anyway, forcing their crappy recovery is a **** move.
Why can't this phone have some sort of permanent recovery for all ROMS, like Desire HD had it in it's time???
So a little insight, I've lost my whole day due to updating/changing ROM on my Xperia Z2.
The problem started after i decided to finally unlock a BL to see what does my phone actually get with that.
After it i tried updating to a ROM from original development section, the recovery i had was a TWRP 3.0.2-0,
with when i connected a phone to my PC it was recognized as Z3 and due to that i couldn't install any other ROM
because it wasnt a "sirius" device.
Well then I installed Mx ROM which came with it's recovery, i used that recovery to install Paranoid from original
section. It wasn't long after that ROM started sort of glitching and i wanted to go back to my previous ROM which
was working and to see if i lost anything with removed DRM keys. I couldn't enter recovery like it wasn't even there,
I've tried flashing recovery from adb, fastboot, which resulted with a boot loop.
All of this was fixed after i flashed a fresh .ftf and rooted it from the beginning and installed everything back. The phone
works OK now i can't notice what's gone with removed DRM keys, everything seems to be working as it was before.
After a long read, my point is.....what is unlocking a BL for??? Why can't Z2 have a sort of permanent recovery like DHD???
Why do we (me) lose a recovery with every new ROM flash, i'm actually afraid installing CM what might result in same
problem as above???
And i read it somewhere that installing a recovery to TA? partition could make it permanent? i'm not sure where I've seen that...
Twrp loop sony xperia z2
Hi,
i have installed TWRP image on my xperia z2 but my phone is not comming to normal mode . its in Twrp mode .please help what have to install .
It seems a bit trendy to mess with the recovery, resulting in a brick or bootloop.
Just making a new thread cause my case is a bit different.
I was on Existenz 4.7.0 when I decided to flash 5.0.
Wasn't a clean install, resulted in some app fc'ing and restarting, so i went back to trwp and used my backup, keeping in mind to come back and make a clean install when I can take the time it needs.
Made a few backups today and wanted to start the trwp backup when I realised that I wasn't able to enter recovery.
Installed the trwp app, which wasn't able to reflash the recovery.
So I read another posting and I decided to delete the chargemon and rename the chargemon.stock, but that wasn't that smart, I decided later.
So back home I downloaded the dual recovery software from NUT's website to totally reinstall the recovery. After some ADB trouble I managed to get everything running, the batch file installed the recovery, everything looked pretty, at the end of the process the Z2 rebootet and e voila, I'm stuck in bootloop, clueless.
When I power the phone you can feel the first small vibration, then the Sony logo appears, stays, and it reboots.
Reset Button, powering on and holding Volume up isn't doing anything, so is Volume down.
What can I Do?
I know I made a few mistakes, but help is still needed!
Bro, Please read carefully before installing recoveries.
Nut's Recovery is NOT for Marshmallow. and it will cause bootloop and same problem you encounter here.
Only Solution is to flash via flashtool and re-root.(personally i would flash a kitkat .ftf then root it with any of the available methods. you can try kingroot it is the easiest) after that install Nut's recovery and flash your MM rom which will come with its own working recovery.
Oh, ok, so thats the cause. Didn't know that, shame on me.
So Existenz 5 messed up my recovery and maybe the silly try of reflashing killed it totally or just the bootloader.
So I will try to setup a Win7 PC and setup flash tool properly (didn't seem to work on win10)
Thanks for that finger point I the right direction
Flashtool works on windows 10 no problem for me.
Just install the right drivers and install 0.9.18.6 version of flashtool and try different drivers it shall work
Will do, thanks a lot. Seems to me that I had a 4.7 Existenz Rom with bootloader/recovery from MM, which I destroyed.
Is it possible to reflash the old bootloader? Or will flash tool spare my datas on internal SD card?
why to flash a boot loader?? is your device unlocked bootloader??
It's locked.
So it can't be a broken bootloader?
So it's just because the recovery is messed up?
JackDCalloway said:
It's locked.
So it can't be a broken bootloader?
So it's just because the recovery is messed up?
Click to expand...
Click to collapse
yes bro don't worry.
It seems that you are new to sony or you re coming from samsung or any other device with recovery partition.
By default, Sony doesn't have a recovery partition like in samsung. that is why developers made the recovery a part of the system (your ROM) the chargemon files are the one responsible for the recovery. so when you install a recovery it is like you are installing a system application which can be messed up if it is not compatible with your rom version.
PS:Be carefull never wipe the system partition from recovery and restart your phone before installing a new rom because if you restart without having installed your rom your phone won't have a recovery(part of the rom) neither a system----> Bootloop and need to reflash.
you can unlock your bootloader and make a recovery partition and install aosp roms. but on sony once you unlock your bootloader you will loose a lots of features and camera enhancements. so better keep it Locked and use stock based roms like existenz and MIUI roms which are stock based.
I hope i have been able to clarify all
OK, makes sense.
Seems like I'm still pretty new to Sony. Came from Samsung last December, just got enough knowledge to flash and improvise, quick and dirty.
So if I could get hands on my old chargemon file, (from when I didn't tried to install Existenz 5) I may get the Z2 running again?
Of course a pretty clean install afterwards.
Just asking, cause of backup reasons
Edit: I knew that unlocking the BL has a few disadvantages. I'm happy with Existenz but now I know a few things more, thanks michel090428
it is very difficult now even if you have the chargemon file. i don't know what could be messed up with the system. go for a clean flash it is the most safe way to do it.
Read this guide if you want a help with flashing it is very easy and detailed. and remember it is better to flash kitkat .ftf as it is easily rootable.
http://www.gizmobolt.com/2015/04/09...z3-23-1-a-0-690-ftf-using-flashtool-manually/
Hey folks, I'm back again!
Managed to setup a Win7 PC, installed the correct drivers, setup Flashtool, found correct ftf file and so on.
Problem is that I'm only able to get into fastboot mode with my Z2, for me it seems like Flashtool won't work when the device is only in fastboot mode.
What can I do?
why you can't start your device with flashmode?
You need to shutdown the device then when flashtool ask you to start in flash mode you press volume down(keep pressed then you plug in USB cable and it should start in flash mode directly.
have you tried to follow the guide i posted in the first page? where are you stuck? which step?
michel090428 said:
why you can't start your device with flashmode?
You need to shutdown the device then when flashtool ask you to start in flash mode you press volume down(keep pressed then you plug in USB cable and it should start in flash mode directly.
have you tried to follow the guide i posted in the first page? where are you stuck? which step?
Click to expand...
Click to collapse
Was a bit tricky, did the 'vol down + plug in' thing several times and it worked suddenly, flashtool flashed the ftf. Now it's FCing several tasks while it would do the android setup. Trying to flash a 4.4.2 ROM now, thanks for patience and help, appreciated this!
WIPE DATA
JackDCalloway said:
Was a bit tricky, did the 'vol down + plug in' thing several times and it worked suddenly, flashtool flashed the ftf. Now it's FCing several tasks while it would do the android setup. Trying to flash a 4.4.2 ROM now, thanks for patience and help, appreciated this!
Click to expand...
Click to collapse
You re Welcome Bro,
Concerning the FC You need to check the WIPE DATA option in flashtool i think it will solve the FC's
I'm with 23.1.A.1.28 now and it's fine. Just need to get root, there should be an exploit but it's not working for me, reasons unknown. Going to have a look at it later. Want to flash Existenz, that's the goal.
Bro , Use KINGROOT it is able to root .28 firmware.
there is a thread here for kingroot.