Related
Hi All, recently I went back to stock ICS from Omega v27, and then rooted with CF 6.4 and installed Siyah 1.53.
On v27 custom bootanimation enabling zip file was there on my exSD card. Today by curiosity I flashed that Zip file using CWM and since then when the phone boots I just hear the sound but cannot see the boot animation. What should I do now to make it visible ?
Regards,
Flash Omega V27.1 which uses a custom boot animation by default.
Sent from my GT-I9300
thekoRngear said:
Hi All, recently I went back to stock ICS from Omega v27, and then rooted with CF 6.4 and installed Siyah 1.53.
On v27 custom bootanimation enabling zip file was there on my exSD card. Today by curiosity I flashed that Zip file using CWM and since then when the phone boots I just hear the sound but cannot see the boot animation. What should I do now to make it visible ?
Regards,
Click to expand...
Click to collapse
Did you enable Custom Bootanimation Zip or did you just flash the bootanimation directly, because if so that will end up with infinite bootloop.V27.1 Bootanimation enabled by default and implemented inside the ROM.
nhariamine said:
Did you enable Custom Bootanimation Zip or did you just flash the bootanimation directly, because if so that will end up with infinite bootloop.V27.1 Bootanimation enabled by default and implemented inside the ROM.
Click to expand...
Click to collapse
Dear, I rebooted into Cockworkmod recovery. Then chosen the custom bootanimation enabling zip file That Came with the Omega Rom Files Menu that I installed previously. That zip file was left on the ext SD card and then by enough stupid curiosity I flashed that Zip file using CWM which resulted in no infinite loop but a blanc screen with default Samsung Animation sound and the phone gets into the home screen. This is uncomfy. I can hear the sound but see no animation. I really like to get back the stock animation working. I even factory reset the phone, but of no vail.
thekoRngear said:
Dear, I rebooted into Cockworkmod recovery. Then chosen the custom bootanimation enabling zip file That Came with the Omega Rom Files Menu that I installed previously. That zip file was left on the ext SD card and then by enough stupid curiosity I flashed that Zip file using CWM which resulted in no infinite loop but a blanc screen with default Samsung Animation sound and the phone gets into the home screen. This is uncomfy. I can hear the sound but see no animation. I really like to get back the stock animation working. I even factory reset the phone, but of no vail.
Click to expand...
Click to collapse
hi mate,
its your animation that need some modification..
inside the bootanimation.zip there is a file named "desc.txt", just open that with notepad++, and edit the last line that probably says something like this:
p 0 0 Part1
Click to expand...
Click to collapse
and change the 0 (zero) after "p", to 1 or more (depends on how many times you want it to loop)
so it looks something like this:
p 1 0 Part1
Click to expand...
Click to collapse
ICS dosent support looped animations, and therefore youll end up having the animation showing forever.. its only JB that supports looped animations.
you could read this thread for further information:
Custom Bootanimations Collection + How To Install + Enable/Disable
and especially check post #5
EDIT:
btw, you need both CF-root with CWM and Busybox for it to work on stock roms.
hi anbech, the prob is fixed. Thank you for the extensive help and others too. Yes, I've read your thread. Infact we should (not could) read your thread when it comes about first time custmizing the bootanimations.
Hi,
I have a rooted galaxy S2 on stock with the SuperSU application. I updated the SuperSU application today and when I opened it, it advised me to update the binary. I selected the option to update the binary via CWM (as that's my recovery tool). My phone then tried to reboot but is now stuck on the splash screen, I have access to ODIN mode which currently says CUSTOM BINARY DOWNLOAD: Yes (1 counts) but no access to CWM.
Please could anyone help? I have a feeling I would need to flash the kernel but am not really sure what the best way to fix this is. If possible I would like to keep all my data intact.
Any help is appreciated
Also apologies if I have posted this to the wrong section.
Thanks
peshmann said:
Hi,
I have a rooted galaxy S2 on stock with the SuperSU application. I updated the SuperSU application today and when I opened it, it advised me to update the binary. I selected the option to update the binary via CWM (as that's my recovery tool). My phone then tried to reboot but is now stuck on the splash screen, I have access to ODIN mode which currently says CUSTOM BINARY DOWNLOAD: Yes (1 counts) but no access to CWM.
Please could anyone help? I have a feeling I would need to flash the kernel but am not really sure what the best way to fix this is. If possible I would like to keep all my data intact.
Any help is appreciated
Also apologies if I have posted this to the wrong section.
Thanks
Click to expand...
Click to collapse
Sorry to persist, but has anyone got any suggestions on how to fix this? I'm on Jeboo kernel v1.2, stock JB firmware.
Thanks
Same problem for me, I updated the last version of SU and try to update binary choossing cmw/trwp. Now I have a bootlopp. onece it started few seconds after the phone reboot again and again.
peshmann said:
Sorry to persist, but has anyone got any suggestions on how to fix this? I'm on Jeboo kernel v1.2, stock JB firmware.
Thanks
Click to expand...
Click to collapse
Same problem for me. In download mode I flashed a stock jb rom, siyah kernel, then I restored the backup from cwm.
Sent from my GT-I9100 using xda app-developers app
chrisXL said:
Same problem for me. In download mode I flashed a stock jb rom, siyah kernel, then I restored the backup from cwm.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
After a few hours of struggling, I managed to get my phone back up and running.
All I did was flash the kernel with a Stock one eg. Philz (as I have stock JB firmware). Once flashed my phone booted up.
However I do have a issue with the SD card now, apps which were installed on my SD card were all greyed out even though I can access the data such as music and films off the card. Slightly strange. I did try mounting and unmounting, as well as reboot and that didn't help.
Considering downloading the apps again and simply moving to SD card and see if that works rather than an uninstall and reinstall.
SuperSU 1.86 binary update
Hi, i using HTC ONE with ARHD31.6 stock kernel. Also i have encountered bootloop issue after i did a update for superSU from v1.8 to v1.86. Tried both options and it stills resulted to bootloop. So far havent been able to find a solution for this so other then restored back to my previous backup.
Hi,
I have a rooted galaxy S2 on stock with the SuperSU application. I updated the SuperSU application today and when I opened it, it advised me to update the binary. I selected the option to update the binary via CWM (as that's my recovery tool). My phone then tried to reboot but is now stuck on the splash screen, I have access to ODIN mode which currently says CUSTOM BINARY DOWNLOAD: Yes (1 counts) but no access to CWM.
Please could anyone help? I have a feeling I would need to flash the kernel but am not really sure what the best way to fix this is. If possible I would like to keep all my data intact.
Any help is appreciated
Also apologies if I have posted this to the wrong section.
Thanks
Click to expand...
Click to collapse
I had the same problem (bootloop issue) on my Samsung win I8552 and I solved that reinstalling CWM trought ODIN :
1. First be sure USB Debugging is checked in ur device ( Settings>Developer Options>USB Debugging )
2. Extract the Odin file from the zip.
3. Open Odin3 (Run As Administrator).
4. Put your device in download mode. To do so, press Volume Down And Home And Power Button all together and when it vibrates release
Power Button but keep pressing left ones. You should have a triangle with an android janitor while it's saying downloading ..
VOL UP TO CONTINUE...
5. Now connect USB to PC ,you should see a blue rectangle with COM:xx and saying Added. It means that your device is ready to be flashed!
6. Go into the PDA section and select your .tar file.(CWM Recovery)
7. Dont check any option (F.reset time and Auto reboot are checked by default) So just uncheck Auto Reboot.
8. Now click Start.
9. When it's finished, it should say that "Res OK" in Odin..
10. Now remove ur USB and remove ur battery and put it back and power on your phone.
It must work now!
:highfive:
SuperSU Binary Update Boot problem
I have a rooted galaxy S2 using jeboo kernel and SuperSU application. I updated the SuperSU application today and when I opened it, it advised me to update the binary. I selected the option to update the binary via CWM. My phone then tried to reboot but is now stuck on the splash screen, I have access to ODIN mode which currently says CUSTOM BINARY DOWNLOAD: Yes (1 counts) but no access to CWM.
Please could anyone help
Try to reinstall a kernel via odin then reboot.
Sent from my GT-I9100 using XDA Free mobile app
I know this is an old topic, but the recent supersu update caused my phone to get stuck during booting:
The new update came over the playstore, it asked me to update the app. After that it said that the Super User Binary needs to be updated. I chose the option that does the update process in the CWM recovery.
Then this happend:
System shuts down, boots, I see that some kind of black screen gets displayed(softkeys on and the display stays blank), then it reboots and stops the boot on the Galaxy S2 splash screen. Now that I didnt even get to the samsung splash screen I flashed the Apolo Kernel as an tar file through odin
after that I was able to get one step further and was able to get the Samsung splash Screen but the Splash screen keeps on repeating over and over but after that I also had my recovery back.
Now I tried to Install SuperSU 2.16 as zip in the recovery. but the endless samsung screen persited. After that I used the 2.15 Beta file. but this didnt work either.
I also fixed permissions wiped cache & dalvic cache
Why wouldnt my system boot after the first initial update and how can I finally fix the boot "loop"?
Thank you very much guys!
Heraku said:
I know this is an old topic, but the recent supersu update caused my phone to get stuck during booting:
The new update came over the playstore, it asked me to update the app. After that it said that the Super User Binary needs to be updated. I chose the option that does the update process in the CWM recovery.
Then this happend:
System shuts down, boots, I see that some kind of black screen gets displayed(softkeys on and the display stays blank), then it reboots and stops the boot on the Galaxy S2 splash screen. Now that I didnt even get to the samsung splash screen I flashed the Apolo Kernel as an tar file through odin
after that I was able to get one step further and was able to get the Samsung splash Screen but the Splash screen keeps on repeating over and over but after that I also had my recovery back.
Now I tried to Install SuperSU 2.16 as zip in the recovery. but the endless samsung screen persited. After that I used the 2.15 Beta file. but this didnt work either.
I also fixed permissions wiped cache & dalvic cache
Why wouldnt my system boot after the first initial update and how can I finally fix the boot "loop"?
Thank you very much guys!
Click to expand...
Click to collapse
Try to reinstall your rom without wipe data. Don't update supersu via cwm!
Sent from my GT-I9100 using XDA Free mobile app
chrisXL said:
Try to reinstall your rom without wipe data. Don't update supersu via cwm!
Sent from my GT-I9100 using XDA Free mobile app
Click to expand...
Click to collapse
I was able to pull a logcat:
Could someone look into it and perhaps tell me how to fix it?
Heraku said:
I was able to pull a logcat:
Could someone look into it and perhaps tell me how to fix it?
Click to expand...
Click to collapse
Sorry to repeat myself, reflash your rom (no wipe). You will not lose anything.
It's the easiest way.
Sent from my GT-I9100 using XDA Free mobile app
after using complete unroot s6 keep in boot loop how to fix it?
If you use TWRP like me and have a recent backup of your system just restore it and it'll fix the boot loop.
chrisXL said:
Sorry to repeat myself, reflash your rom (no wipe). You will not lose anything.
It's the easiest way.
Sent from my GT-I9100 using XDA Free mobile app
Click to expand...
Click to collapse
thank u very much, this saved me from freaking out. it absolutely worked.
supersu binary reboot problem
first of all, get into recovery mode and copy the rom and gapps files to your internal storage through pc via usb cable.
then wipe the data, and make a clean flash of rom and gapps and reboot system.
I know this method will surely lose our data. but I have not found a solution at that particular instant other than this.
It happened to me.
Hope someone will surely solve this problem.
Thank you chrisXL, came across this thread from a Google search regarding my OnePlus2 using LinageOS after the SuperSU binary update. I simply went to INSTALL in TWRP and didn't use any wipe options. Phone booted right up after that! Thanks!!
Hi Guys, please help me. I flashed my moto g peregrine with the latest lineage os version. After that, i enable the the root option via TWRP with the addonsu.
After that, i downloaded via google store the SuperSU app i it asks to update the binary. I choosed the option via "TWRP" since the other option didn't work. After that, my phone is on bootloop (the symbol of lineage os is moving) and i can't acess to recovery mode.
What i can do?
j_moreno91 said:
Hi Guys, please help me. I flashed my moto g peregrine with the latest lineage os version. After that, i enable the the root option via TWRP with the addonsu.
After that, i downloaded via google store the SuperSU app i it asks to update the binary. I choosed the option via "TWRP" since the other option didn't work. After that, my phone is on bootloop (the symbol of lineage os is moving) and i can't acess to recovery mode.
What i can do?
Click to expand...
Click to collapse
Same problem here I had my mokke Rom pre rooted but titanium used to ask for SuperSU so installed the app from Google play and tried to install it via cwm/twrp and now it's stuck on the mokkee boot logo and can't even access my recovery what did you do solve the problem?
Hi there
Well my phone is rooted and unlocked bootloader, im new to this so i want to install the new kit kat rom on it but i dont know if i installed clockwordmod well cause when i access it it says that it doesnt have recovery for my mobile phone , can someone post me a link to install a correct rom manager pro and recovery and explain how i enter the recovery mod later cause i tried volume up , volume down everything and it continued to the xperia logo dont know why maybe i dont have the recovery well installed,
Thanks guys im a newbie in this so be patient please
helderhalen said:
Hi there
Well my phone is rooted and unlocked bootloader, im new to this so i want to install the new kit kat rom on it but i dont know if i installed clockwordmod well cause when i access it it says that it doesnt have recovery for my mobile phone , can someone post me a link to install a correct rom manager pro and recovery and explain how i enter the recovery mod later cause i tried volume up , volume down everything and it continued to the xperia logo dont know why maybe i dont have the recovery well installed,
Thanks guys im a newbie in this so be patient please
Click to expand...
Click to collapse
Cwm isn't enough... You need custom kernel...and custom kernels come with cwm... So unlock boatloader... Flash kernel... Then Rom will work..
Sent from my Xperia Neo V using Tapatalk 2
Attitude.SSJ said:
Cwm isn't enough... You need custom kernel...and custom kernels come with cwm... So unlock boatloader... Flash kernel... Then Rom will work..
Sent from my Xperia Neo V using Tapatalk 2
Click to expand...
Click to collapse
Im trying to install this rom http://forum.xda-developers.com/showthread.php?t=2545367 , how do i get the custom kernel?
Thanks
the kernel is in the rom zip file, named boot.img
flash it via fastboot mode.
an0nym0us_ said:
the kernel is in the rom zip file, named boot.img
flash it via fastboot mode.
Click to expand...
Click to collapse
Ok but then i cant access the recovery on my phone to install the rom , i tried the volume up, down etc and nothing works... i think the cwm isnt working properly....
if u already flashed to boot.img, just repeatedly press volume down button when phone booting, on kernel logo while led lights up.
an0nym0us_ said:
if u already flashed to boot.img, just repeatedly press volume down button when phone booting, on kernel logo while led lights up.
Click to expand...
Click to collapse
Ok the only way i can get to boot is installing x parts and then i press the sony logo and the boot appears, but it tells me that i cant wipe system cause the CWM will delete too , with the normal rom manager pro i downloaded the last version on aptoide i cant get any recovery and i cant get to bootloader , i need help, post me a link to download a version of CWM that works with SK17i.
Thanks
did u even flash the boot.img from rom zip?
an0nym0us_ said:
did u even flash the boot.img from rom zip?
Click to expand...
Click to collapse
If i cant access the bootloader how the hell can i install the rom? i didnt flash the rom yet im trying to figure out yet how to access the CWM recovery thats what im having trouble right now
then stop trying to figure out thing u cant achieve.
aosp base rom such as cm11 u want to install require flashing custom kernel, the boot.img provided in the rom zip, which in the kernel itself contains cwm recovery.
if u manage to flash it then u will get cwm that came with the kernel.
an0nym0us_ said:
then stop trying to figure out thing u cant achieve.
aosp base rom such as cm11 u want to install require flashing custom kernel, the boot.img provided in the rom zip, which in the kernel itself contains cwm recovery.
if u manage to flash it then u will get cwm that came with the kernel.
Click to expand...
Click to collapse
oh sorry i wasnt understanding that, i thought it didnt have any recovery, ok but now i installed a recovery from some place maybe i have to uninstall it, so im using flashtool , i put my phone in fastboot mode, then i choose select system to flash? Can You explain the steps using flashtool? im new to this tool too. sorry im really new to this roms thing yet..
1- turn off phone
2- hold volume up button and while still holding the volum up, connect usb to phone and pc. led on phone will light ups blue indicating fastboot mode.
3- open flashtool, click on flash button, select fastboot mode, click ok, click select kernel to flash, on dropdown on lower left change to *.img, browse the boot.img, click ok.
4- flashtool main window will give output log of flashing the kernel.
5- remove usb
6- turn on phone
7- while kernel logo appear and led lights up, press volume down repeatedly.
8- phone will now boot into cwm
9- do wipe data/factory reset
10- flash rom
11- flash gapps
12- profit
anyway, why did u want to flash the buggy cm11?
try custom rom based on stock first, or miui, or cm9 or cm10. those roms are stable enough for everyday use.
an0nym0us_ said:
1- turn off phone
2- hold volume up button and while still holding the volum up, connect usb to phone and pc. led on phone will light ups blue indicating fastboot mode.
3- open flashtool, click on flash button, select fastboot mode, click ok, click select kernel to flash, on dropdown on lower left change to *.img, browse the boot.img, click ok.
4- flashtool main window will give output log of flashing the kernel.
5- remove usb
6- turn on phone
7- while kernel logo appear and led lights up, press volume down repeatedly.
8- phone will now boot into cwm
9- do wipe data/factory reset
10- flash rom
11- flash gapps
12- profit
Click to expand...
Click to collapse
I have to send the folder cm-11.0-20131225-NIGHTLY-LegacyXperia-mango.zip and the gapps folder to sd card before i flash kernel right?
yes, both the rom zip and gapps zip need to be in sdcard.
and if i'm not mistaken, cm11 need to repartition system partition due to not enough space in it for the big rom.
probably need to manually format system too before flash, i'm not really sure.
ask in the support thread instead
http://forum.xda-developers.com/showthread.php?t=2543426
an0nym0us_ said:
yes, both the rom zip and gapps zip need to be in sdcard.
and if i'm not mistaken, cm11 need to repartition system partition due to not enough space in it for the big rom.
probably need to manually format system too before flash, i'm not really sure.
ask in the support thread instead
http://forum.xda-developers.com/showthread.php?t=2543426
Click to expand...
Click to collapse
It Just says This:
WARNING: This ROM uses a modified internal memory layout.
Our /system partition is originally 400MB but this space is not enough for a fluid kitkat experience and a full installation with proper google apps.
Our /cache partition is also too small to fit art-cache when we enable the ART runtime. We originally had 100MB /cache but art-cache needs ~150mb of free space.
I have repartitioned the internal memory layout, giving:
450mb in /system
469,5mb in /data
8mb in /cache
Steps required for correct installation (order is important):
1: Flash boot.img in fastboot & reboot into recovery
1.1 (optional): If the device is not booting, reboot to bootloader again and run:
fastboot erase system
fastboot erase userdata
2: Enter recovery, go to mounts and storage
3: Format /system, then /data and then /cache (Important step!)
4: Flash update zip
5: Flash gapps (recommended package is the one provided in the link below)
Steps 1.1, 2 & 3 are not needed when you install new cm11 nightlies on top of older cm11 builds in the future
If you want to return to a ROM that doesn't use the new partition layout, you need to follow the above steps again (only replace boot.img & update zip with the ones you want to use).
Right, I have a set of issues which all seem vaguely connected but I can't figure out how to resolve.
I've unlocked my bootloader and I've been messing about with recoveries and CM11 etc.
The situation however is that I installed doomkernel, got into CWM and installed CM11, all good.. went to go back into the recovery and it's gone, it just hangs if I try, no worries I thought I'll just reflash doomkernel, then the ROM doesn't boot so I have to reflash boot.img from the CM11 zip.
That kills the recovery again... rinse and repeat basically, it looks like I can't have CM11 and CWM which is a PITA.
Plenty of people in the CM11 thread seem to be having no issues with either retaining the recovery or using cyandelta, neither of which work for me and whilst CM11 is still in nightly I really need to be able to upgrade frequently.
Also, using flashtool to unlock the bootloader was fine but I can't flash a recovery from there as the option is greyed out on both CM11 and the stock ROM..
I'm lost, I've tried several combinations but I've also gone dangerously close to bricking the phone so I've backed off..
Can anyone give me any pointers?
The only thing I haven't done is download the ROM from the frexperia site as I can't make sense of which ROM I need, I can't see Z2 or Sirius mentioned anywhere and I've learned the painful way in the past not to flash the wrong ROM.
So now I'm back to the stock rooted ROM but there's a bunch of issues with it such as it loving switching the wifi on and off, proximity sensors thinking my face is my fingers, the useless lock screen etc etc.
HALP! Thanks all
Try this:
1 - install recovery.
2 - reboot into recovery.
3 - flash CM11, don't reboot.
4 - flash gapps, don't reboot.
5 - flash recovery & reboot.
Does this leave you with a recovery? There is an option to upgrade recovery in CM11 settings -> developer options -> update CM recovery. Try this and see what happens.
Sent from my SGP311 using XDA Free mobile app
I haven't been flashing the recovery from within CWM, in fact I'm not even sure you can with it being a kernel image as thats how Sony's work? If I flash the doomkernel again I know CM11 won't boot and sort of vice versa..
EDIT - Sorry I didn't see you had a Z2.. have you managed to pull this off? Any tips on a recovery flashable kernel?
mrmatt100 said:
I haven't been flashing the recovery from within CWM, in fact I'm not even sure you can with it being a kernel image as thats how Sony's work? If I flash the doomkernel again I know CM11 won't boot and sort of vice versa..
EDIT - Sorry I didn't see you had a Z2.. have you managed to pull this off? Any tips on a recovery flashable kernel?
Click to expand...
Click to collapse
Reintall stock. Skip Doom Kernel, directly fastboot CM boot.img. Flash CM in your now working recovery.
Thats what worked for me
Sent from my Xperia Z2 using Tapatalk
Sorry what do you mean by skin the kernel? I'm not a n00b but I've never heard that before?
but thanks for the help!
Myself5 said:
Reintall stock. Skin Doom Kernel, directly fastboot CM boot.img. Flash CM in your now working recovery.
Thats what worked for me
Sent from my Xperia Z2 using Tapatalk
Click to expand...
Click to collapse
Still stuck on this, I do know I've got stock with doom kernel and I've fastboot flashed the CM boot.img from the CM11 nightly, that basically results in a phone that won't boot OR go into recovery.
Literally the only way I can get into CWM is by using doom kernel and the stock ROM (obviously rooted and using xposed etc if that makes a difference) and the moment I flash anything from within CWM it obviously overwrites the boot.img meaning I can boot normally but not with a working recovery.
I can't escape the feeling that I ought to be flashing a specific version perhaps from freexperia rather than the cyanogenmod website or I need a different kernel to kick the process off rather than doom kernel.
Very confusing and a real shame doom kernel only works with stock ROMs
Sorry the skin part was a spelling misstake. Should have been SKIP. I issued the same as you, my problem was somehow related to DoomKernel. So just Flash Stock now (using a ftf in flashtool) and then straight the boot.img from the CM zip. Now boot in the recovery (press vol down when the Amber led lights up at the boot process) and flash the CM zip in this recovery (wipe data/Factory reset and format /system before ofc (least that what I would recommend)). Flash Gapps if you whish. Reboot to your now working CM install.
Sent from my Xperia Z2 using Tapatalk
Myself5 said:
Sorry the skin part was a spelling misstake. Should have been SKIP. I issued the same as you, my problem was somehow related to DoomKernel. So just Flash Stock now (using a ftf in flashtool) and then straight the boot.img from the CM zip. Now boot in the recovery (press vol down when the Amber led lights up at the boot process) and flash the CM zip in this recovery (wipe data/Factory reset and format /system before ofc (least that what I would recommend)). Flash Gapps if you whish. Reboot to your now working CM install.
Sent from my Xperia Z2 using Tapatalk
Click to expand...
Click to collapse
Absolutely 100% spot on, I'm so happy! Thanks
mrmatt100 said:
Absolutely 100% spot on, I'm so happy! Thanks
Click to expand...
Click to collapse
hello i'm having this exact same issue and i will be trying this taday when home from work. the only thing i'm not sure about is the ftf in flashtool.
don't know what ftf stands for, but i presume flashtool is the official sony flash tool?
http://developer.sonymobile.com/services/flash-tool/
thanks for the answer.
skuko said:
hello i'm having this exact same issue and i will be trying this taday when home from work. the only thing i'm not sure about is the ftf in flashtool.
don't know what ftf stands for, but i presume flashtool is the official sony flash tool?
http://developer.sonymobile.com/services/flash-tool/
thanks for the answer.
Click to expand...
Click to collapse
I think there's the official and an unofficial tool, I used the one from here http://www.flashtool.net/index.php
And a .ftf file is an official sony ROM, bit like how you end up with .zip files for non official ROMs, HTCs have .RUUs and iPhones have .ISPW files.
There's a list of .ftf files on here somewhere, grab the latest from there.
For what it's worth, I went CM11, got fed up with the camera quality so went to xistenz and romaur, both slightly unstable so I went back and back again to a stock .ftf, rooted it and I'm just using a bunch of xposed tweaks now and it looks pretty much the same as AOSP now. You only see the difference when you're in settings.
skuko said:
hello i'm having this exact same issue and i will be trying this taday when home from work. the only thing i'm not sure about is the ftf in flashtool.
don't know what ftf stands for, but i presume flashtool is the official sony flash tool?
http://developer.sonymobile.com/services/flash-tool/
thanks for the answer.
Click to expand...
Click to collapse
I meanwhile found a even easier way to solve this problem. Just go into faatboot mode (turn off phone press Vol+ and attach USB) and do "fastboot erase recovery" this will boot the kernels default recovery (CWM) again. This all is caused by some missing tools in the kernel which is not loading TWRP. However even with the tool provided by @Dees_Troy it does not load TWRP, now instead of hanging at the black screen with no recovery it still loads CWM after flashing TWRP to the recovery partition.
Sent from my Xperia Z2 using Tapatalk
Myself5 said:
I meanwhile found a even easier way to solve this problem. Just go into faatboot mode (turn off phone press Vol+ and attach USB) and do "fastboot erase recovery" this will boot the kernels default recovery (CWM) again. This all is caused by some missing tools in the kernel which is not loading TWRP. However even with the tool provided by @Dees_Troy it does not load TWRP, now instead of hanging at the black screen with no recovery it still loads CWM after flashing TWRP to the recovery partition.
Sent from my Xperia Z2 using Tapatalk
Click to expand...
Click to collapse
so if i want to get rid of the doomkernel, i still need to reflash the stock ftf, correct?
skuko said:
so if i want to get rid of the doomkernel, i still need to reflash the stock ftf, correct?
Click to expand...
Click to collapse
In case you want back to stock, yes. In case you want from Doom to CM just erase the recovery partition and fastboot flash the CM boot.img
Sent from my Xperia Z2 using Tapatalk
seems to have worked, my kernel in "about phone" now says:
3.4.0cyanogenmod-g449fd42
[email protected] #1
Mon Aug 18 09:30:35 BST 2014
i used the boot.img from your carbon rom nightly.
Hi,
I have the reboot loop after flashing any of the .570 rom. I have tried the flashable zip from one thread and have also tried a couple of FTFs with APP Log and UserData wipe selected.
Does anyone know why this isn't working on my phone? I have a regular 4G Z2 with a locked BL.
Thanks,
linkazoid said:
Hi,
I have the reboot loop after flashing any of the .570 rom. I have tried the flashable zip from one thread and have also tried a couple of FTFs with APP Log and UserData wipe selected.
Does anyone know why this isn't working on my phone? I have a regular 4G Z2 with a locked BL.
Thanks,
Click to expand...
Click to collapse
Yes I also face this bootloop with "Marshmallow_Stock_570_ROM_Ultraslim (Full deodxed)" so try to install bootloop fix from other thread OP topic 5.5 http://forum.xda-developers.com/xperia-z2/development/rom-official-6-0-1-23-5-0-486-beta-t3336770 it work
Doesn't this put the old kernel back though?
linkazoid said:
Doesn't this put the old kernel back though?
Click to expand...
Click to collapse
I don't know BUT today he make the new one with the latest version 570 with this fix bootloop I can try and enjoy MM rom .
I saw this, I have now flashed the ultraslim rom and the .570 fix instead.
What is the bootloop like? I have bootloop after flash the 570 made from a tft. It shows the SONY logo and then black screen for seconds then auto reboot. I'll try that bootloop fix zip tomorrow. Hope that will work.
My bootloop consisted of the ROM booting but as soon as you touched the screen to check a box or unlock the screen it would restart. The fix by niaboc works as I've applied it on the ultraslim ROM, now using the latest kernel and latest ROM!
To fix the bootloop, have to flash via recovery.
Then how I enter the recovery while this handheld keep restart at welcome screen.thanks for ur respons
Touch the screen and hold volume down! If you've installed a ROM without recovery then you'll have to reflash a ftf and start again