Develop Bugs

Phone seems jacked, need help please..

I cannot get past the bootanimation screen. This just happened this morning out of the blue. It's been rooted since Dec, and been running fine since. I can get to recovery, but it just reboots and hangs from there on it's own. I'm using AOKP MS2, and FrancoKernel, which probably doesn't matter, but I just need to get this at least back to stock. What do you guys suggest? I have done a battery pull, entered recovery through fastboot, but it just won't boot up.

Since you can access recovery, just restore a nandroid backup. That will get your phone up and running again.

lonnyrs said:
I cannot get past the bootanimation screen. This just happened this morning out of the blue. It's been rooted since Dec, and been running fine since. I can get to recovery, but it just reboots and hangs from there on it's own. I'm using AOKP MS2, and FrancoKernel, which probably doesn't matter, but I just need to get this at least back to stock. What do you guys suggest? I have done a battery pull, entered recovery through fastboot, but it just won't boot up.
Click to expand...
Click to collapse
If you have a nandroid then flash that, if not you will have to wipe cache, system,dalvik and data and flash the rom again.
That should solve your problems.
Maybe try just wiping cache, dalvik and system and leave data alone and flash the rom again. That way all your apps etc will still be there.
If you get bootloops after that then full wipe and flash.

Can aokp m4 be flashed via fastboot? Not sure this is possible , anyone ever fastboot a custom rom? Or push it with fastboot and then flash it in cwm?
¢ £®0π π€XU$ |||

Stock Nandroid backup Bootloop - help

Hey guys, this post is not for me but for a friend.
As the title already mentions, he's trying to get to stock
so the step he follows are:
Move boot.img from his stock rom nandroid backup to his fastboot folder
so lets begin
first step-> boot into bootloader
fastboot erase cache
fastboot flash boot boot.img
fastboot erase cache
--> boot into recovery
wipe data/factory reset
wipe cache
wipe delvik cache
-> back up and restore
--> restore
--- nandroid backup gets installed ---
... so far i can't see where he is doing anything wrong
so he proceeds to reboot his phone.. and now i asked him multiple times about the taken procedure and he claims his phone boots normally to the point where the wallpaper shows up and then he talks about the phone falling into a constant bootloop
What went wrong? Why is he experiencing this?
I've taken into consideration that he might be doing something wrong, but then i even wrote the steps above and he says he did it exactly that way.
i'm clueless to say the least and i hope someone here could help me help him
thank you

Try the cache clean up after the nandroid is restored.
Also try to install some other compatible kernel (if it's stock it should be also to find on the forums) after the restore with its modules if the cache clean up doesn't help.
Sent from my HTC One X using Tapatalk 2

Wipe the cache and dalvik cache again.

shadehh said:
Hey guys, this post is not for me but for a friend.
As the title already mentions, he's trying to get to stock
so the step he follows are:
Move boot.img from his stock rom nandroid backup to his fastboot folder
so lets begin
first step-> boot into bootloader
fastboot erase cache
fastboot flash boot boot.img
fastboot erase cache
--> boot into recovery
wipe data/factory reset
wipe cache
wipe delvik cache
-> back up and restore
--> restore
--- nandroid backup gets installed ---
... so far i can't see where he is doing anything wrong
so he proceeds to reboot his phone.. and now i asked him multiple times about the taken procedure and he claims his phone boots normally to the point where the wallpaper shows up and then he talks about the phone falling into a constant bootloop
What went wrong? Why is he experiencing this?
I've taken into consideration that he might be doing something wrong, but then i even wrote the steps above and he says he did it exactly that way.
i'm clueless to say the least and i hope someone here could help me help him
thank you
Click to expand...
Click to collapse
I restored my original 4.0.3 nandroid backup yesterday and got exactly the same problem coming from arhd 9.7.2 4.0.4. I want to get back to stock so I can get JB ota when its available. Mine also loaded the wallpaper and then rebooted. All I did to fix it was copy the boot.img from my nandroid backup and reflash that after I had restored again.
So the way I did it was
Boot into recovery
Full wipe
Restored rom
booted into bootloader
flash boot.img (from original nandroid)
rebooted and worked a treat

Thanks for the help guys. I mentioned all the suggestions on this thread to him and it he was able to get it running
Sent from my HTC One X using xda app-developers app

bradmax57 said:
I restored my original 4.0.3 nandroid backup yesterday and got exactly the same problem coming from arhd 9.7.2 4.0.4. I want to get back to stock so I can get JB ota when its available. Mine also loaded the wallpaper and then rebooted. All I did to fix it was copy the boot.img from my nandroid backup and reflash that after I had restored again.
So the way I did it was
Boot into recovery
Full wipe
Restored rom
booted into bootloader
flash boot.img (from original nandroid)
rebooted and worked a treat
Click to expand...
Click to collapse
OK I had the same issue and followed these steps, however when I try to flash boot.img I get an error in command prompt saying it cannot load boot.img (even though the file is copied to root of the 'sd card')
any idea what I'm doing wrong

squirrelbo1 said:
OK I had the same issue and followed these steps, however when I try to flash boot.img I get an error in command prompt saying it cannot load boot.img (even though the file is copied to root of the 'sd card')
any idea what I'm doing wrong
Click to expand...
Click to collapse
The file shouldn't be on the phone, but on the PC.
Place it in the folder in which you have your fastboot files.

oh of course. I'm being a moron again.
I cant believe I did that. so very very simple. sorry for being a numpty guys. wasn't thinking strait. Done a few custom rom installs but never flashed a backup. Didnt even think. You even have to type the directory into command prompt.sorry guys I can't believe I didn't think that. (was thinking along the lines of installing from zip way)
to be fair the only reason I'm doing all this is because my screen is playing up and I need to return it so getting everything as close to stock as possible so got other things on my mind
everything is working now. Thanks guys. My god stock rom on HTC one x from orange is ugly.

No worries mate. You're not a moron, just a beginner.

TToivanen said:
No worries mate. You're not a moron, just a beginner.
Click to expand...
Click to collapse
thanks heaps for the thread guys, this has been a great help as I'm doing a similar thing and had the same problem.

HTC One X stuck on home screen

Hello!
After some fiddling around I have finally succeeded into installing the MIUI custom rom. (had a heck of a work around to perform because I forgot to put the custom ROM on my SD card first.)
Right now, I've got Clockwork Recovery 5.8.4.0 installed with the latest miui. Fastboot is also installed and working, and my phone is unlocked. The correct boot.img has also been installed.
It even boots. BUT. After it has showed the MIUI logo and goes to my home screen, it starts loading for like 4-5 seconds where everything still works, and it then stops. Crash. The screen freezes and my phone reboots. It seemed like a SIM card problem to me, but even removing the SIM card and booting my phone wont solve this issue. Does anyone have any clue what I can do?
Summary of installed software:
Clockwork Recovery V5.8.4.0
HBOOT 1.12.0000
Latest MIUI for One X (downloaded this afternoon)
Latest ADB Development Kit. (Not used though)
Latest Flashboot.
Factory Reset performed (Whole phone is empty except for above mentioned programs.
Thanks in Advance!
P

Erase Cache
While in Fastboot Mode .Perform This command
Fastboot erase cache
Should do the job for u!
I would suggest flash the boot.img again and then erase cache again.Will work

Tried it, but..
I'm afraid it didn't do the trick.
Even flashing another custom ROM (Android Revolution HD16) with it's corresponding boot.img didn't do the job. The crashing times have also changed now. It sometimes works for like 5-6 seconds into booting the homescreen, and sometimes it doesn't even reach it.

Piedro92 said:
I'm afraid it didn't do the trick.
Even flashing another custom ROM (Android Revolution HD16) with it's corresponding boot.img didn't do the job. The crashing times have also changed now. It sometimes works for like 5-6 seconds into booting the homescreen, and sometimes it doesn't even reach it.
Click to expand...
Click to collapse
Clockwork Recovery V5.8.4.0
HBOOT 1.12.0000
^^ for ARHD 16 u need hboot 1.33 , 1.36 depending on your CID
for miui did you do full wipe?

Piedro92 said:
I'm afraid it didn't do the trick.
Even flashing another custom ROM (Android Revolution HD16) with it's corresponding boot.img didn't do the job. The crashing times have also changed now. It sometimes works for like 5-6 seconds into booting the homescreen, and sometimes it doesn't even reach it.
Click to expand...
Click to collapse
Did you wipe cache and dalvik cache? I think ARHD does that anyway, but might be worth doing the superwipe.
Oh, and if you're restoring system data or system apps with Titanium backup, stop it.

HBOOT!
I am afraid ur not on the right CID version for installing JB roms.
Please update ur Hboot

@ali3nfr3ak: Yes, I did a full wipe before MIUI. After every flash I do a Dalvik Cache Wipe, Factory Reset Wipe and Cache Wipe. Even the fastboot receive a cache wipe after every flash.
How do I update my HBOOT? The rest seemed pretty straight forward, but there are tons of versions out there, and I do not know which one I should be taking. And what is CID? I've also been having troubles porting a Super Wipe toward my mobile phone. Can a Super Wipe be performed within fastboot/recovery?
Haha and no, I'm not using Titanium Backup

Right, I've succesfully restored my phone to it's old state. Flashing MIUI again provided the same error. Could it be that my hBoot is out of date here? My One X still has the 4.0.4 android version, whilst MIUI is based on 4.1, right?

Change the rom, miui isn't good.

[Q] Stuck at "Google Logo" after Rom Flash?

I've got an AT&T M8 devices, and have installed the stock Kitkat version of Android on it. I found myself missing the (IMO superior) HTC camera app, and decided to flash either the stock Sense 6 rom or something based on it, like Android Revolution 5.
I booted into TWRP, backed everything up, and flashed the rom. When flashing was done, I cleared the Dalvik and Cache. The system then boots to a Google Logo with an unlocked lock at the bottom of the screen, and stays there until I do a hard reboot into TWRP. From there, I AM able to restore from backup, thankfully.
I thought I might not be waiting long enough for the ROM to do its magic, so I set a timer and let it stay on the Google Logo for a full 10 minutes. Still nothing.
I have tried this with the Stock Sense 6 AND the Android Revolution 5 ROMs with the same result.
Phone is S-Off. I'm coming from IOS for the last 3 years, so am probably missing something obvious, but can't seem to figure out what that is.
Does anyone have any ideas?
Thanks very Much.

ThePedigree said:
I've got an AT&T M8 devices, and have installed the stock Kitkat version of Android on it. I found myself missing the (IMO superior) HTC camera app, and decided to flash either the stock Sense 6 rom or something based on it, like Android Revolution 5.
I booted into TWRP, backed everything up, and flashed the rom. When flashing was done, I cleared the Dalvik and Cache. The system then boots to a Google Logo with an unlocked lock at the bottom of the screen, and stays there until I do a hard reboot into TWRP. From there, I AM able to restore from backup, thankfully.
I thought I might not be waiting long enough for the ROM to do its magic, so I set a timer and let it stay on the Google Logo for a full 10 minutes. Still nothing.
I have tried this with the Stock Sense 6 AND the Android Revolution 5 ROMs with the same result.
Phone is S-Off. I'm coming from IOS for the last 3 years, so am probably missing something obvious, but can't seem to figure out what that is.
Does anyone have any ideas?
Thanks very Much.
Click to expand...
Click to collapse
need to reformat /system as well.

dipole said:
need to reformat /system as well.
Click to expand...
Click to collapse
..,before or after I flash it?

ThePedigree said:
..,before or after I flash it?
Click to expand...
Click to collapse
Before, you need to clear out remnents of old rom, reformat cache, dalvik, data (not sd) and system then flash rom and gapps if needed. Reboot.

dipole said:
Before, you need to clear out remnents of old rom, reformat cache, dalvik, data (not sd) and system then flash rom and gapps if needed. Reboot.
Click to expand...
Click to collapse
Thank you for your advice. I wish I had better news...
I Wiped the parts you mentioned. Installed ROM. Cleared Cache and Dalvik using the TWRP button that shows after installation. Rebooted, and there was no different result.
Tried it with both ROMs. Same results both times, except the non-stock ROM gives up and reboots in recovery mode after about three minutes. The stock ROM just stays stuck at Google logo.
Restore from backup still works.
Any other ideas, folks?

ThePedigree said:
Thank you for your advice. I wish I had better news...
I Wiped the parts you mentioned. Installed ROM. Cleared Cache and Dalvik using the TWRP button that shows after installation. Rebooted, and there was no different result.
Tried it with both ROMs. Same results both times, except the non-stock ROM gives up and reboots in recovery mode after about three minutes. The stock ROM just stays stuck at Google logo.
Restore from backup still works.
Any other ideas, folks?
Click to expand...
Click to collapse
Did you convert to GPE? If so you can't flash back to sense just yet
Also, check md5 of your download, might be corrupted

ThePedigree said:
I've got an AT&T M8 devices, and have installed the stock Kitkat version of Android on it. I found myself missing the (IMO superior) HTC camera app, and decided to flash either the stock Sense 6 rom or something based on it, like Android Revolution 5.
I booted into TWRP, backed everything up, and flashed the rom. When flashing was done, I cleared the Dalvik and Cache. The system then boots to a Google Logo with an unlocked lock at the bottom of the screen, and stays there until I do a hard reboot into TWRP. From there, I AM able to restore from backup, thankfully.
I thought I might not be waiting long enough for the ROM to do its magic, so I set a timer and let it stay on the Google Logo for a full 10 minutes. Still nothing.
I have tried this with the Stock Sense 6 AND the Android Revolution 5 ROMs with the same result.
Phone is S-Off. I'm coming from IOS for the last 3 years, so am probably missing something obvious, but can't seem to figure out what that is.
Does anyone have any ideas?
Thanks very Much.
Click to expand...
Click to collapse
Did you flash a gpe rom or convert using ruu?

an0ther said:
Did you flash a gpe rom or convert using ruu?
Click to expand...
Click to collapse
Converted using ruu. Thanks for your interest!

ThePedigree said:
Converted using ruu. Thanks for your interest!
Click to expand...
Click to collapse
You have to convert back to sense. The gpe partitions are the incorrect size for a sense rom. Follow steps in post #2 in this link to get back. Next time just flash a gpe rom. The only advantage to converting is ota updates, which in a rom, they will update those too.
http://forum.xda-developers.com/showthread.php?t=2708589
if you get lost let me know, when it says flash firmware, you have to use the "fastboot oem rebootRUU" mode that you used in the conversion

ThePedigree said:
Converted using ruu. Thanks for your interest!
Click to expand...
Click to collapse
HOW TO RETURN TO SENSE:
-Flash 1.54 Image- http://forum.xda-developers.com/show...68&postcount=3
(fastboot oem rebootRUU, fastboot flash zip (whatever you name it).zip FLASH TWICE 1ST WILL FAIL )
-Boot Into OS
-Get Decrypt Error
-Boot back into Bootloader
-Flash TWRP- http://techerrata.com/file/twrp2/m8/...2.7.0.2-m8.img
(fastboot flash recovery recovery.img)
-Boot into Recovery
IMPORTANT!!!!!!
-Wipe Data, Factory Reset, Advanced Wipe-Wipe System, Data, Cache
-Reboot Recovery
-Restore or Flash a Sense Rom

charlieb620 said:
HOW TO RETURN TO SENSE:
-Flash 1.54 Image- http://forum.xda-developers.com/show...68&postcount=3
(fastboot oem rebootRUU, fastboot flash zip (whatever you name it).zip FLASH TWICE 1ST WILL FAIL )
-Boot Into OS
-Get Decrypt Error
-Boot back into Bootloader
-Flash TWRP- http://techerrata.com/file/twrp2/m8/...2.7.0.2-m8.img
(fastboot flash recovery recovery.img)
-Boot into Recovery
IMPORTANT!!!!!!
-Wipe Data, Factory Reset, Advanced Wipe-Wipe System, Data, Cache
-Reboot Recovery
-Restore or Flash a Sense Rom
Click to expand...
Click to collapse
Thanks for your continued attention and generous efforts.
By "Boot into OS" do you mean simply reboot after the flash? I've done that and it shows the animated Google logo with the four squares of moving color. It seems to stay there for as long as I let the phone sit.
When does the Decrypt Error come into play?
Thank you!

ThePedigree said:
Thanks for your continued attention and generous efforts.
By "Boot into OS" do you mean simply reboot after the flash? I've done that and it shows the animated Google logo with the four squares of moving color. It seems to stay there for as long as I let the phone sit.
When does the Decrypt Error come into play?
Thank you!
Click to expand...
Click to collapse
Fastboot reboot
Also if that doesn't work, try wiping everything with Philz recovery
Sent from my HTC One_M8 using Tapatalk

charlieb620 said:
Fastboot reboot
Also if that doesn't work, try wiping everything with Philz recovery
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Just to clarify.... after flashing ROM I simply "fastboot reboot". How long (approx) should I wait and watch the Google logo before I assume things didn't work? Is more than 10 minutes normal?
Thanks much!

Less than 3 mins. If nothing change recoveries and start the process over. Try Virtuous rom fresh flash
Sent from my HTC One_M8 using Tapatalk

charlieb620 said:
Less than 3 mins. If nothing change recoveries and start the process over. Try Virtuous rom fresh flash
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Charlie, just curious, I'm happy with GPE conversion, but with your instructions are you saying that you reset the partitions back to sense? Or are you simply forcing the sense ROMS to use the GPE partitioning scheme?

dipole said:
Charlie, just curious, I'm happy with GPE conversion, but with your instructions are you saying that you reset the partitions back to sense? Or are you simply forcing the sense ROMS to use the GPE partitioning scheme?
Click to expand...
Click to collapse
Putting the partitions back where they belong if you want to go back to sense.
Sent from my HTC One_M8 using Tapatalk

whew thanks for this thread

[Q] Boot loop after flashing TWRP recovery !

Hello everyone, I have a problem with my xperia S, any help would be greatly appreciated! Let's start from the beginning, I'll try to be brief :
So, I flashed TWRP recovery using the app "RASHR" (I was using the Pure AOSP Lollipop rom when doing this, if it can help), which caused my phone to always boot the recovery and nothing else. I managed to flash the rom again (I made sure to wipe using "factory reset" and "dalvik cache" before installing), and it seemd to work perfectly, but then I rebooted the phone, and got stuck at the sony logo, no recovery available.
I flashed TWRP recovery (stock-6.1.A.0.452-twrp-2.4.0.0.elf) using flashtool, then tried to install another rom (Paranoid Android, found on this thread : http://forum.xda-developers.com/showthread.php?t=2573345). The first boot was successful, but as soon as I reboot the phone, I'm stuck in a bootloop again, with a little difference : when the sony logo appears, the led becomes pink for a few seconds. No access to recovery. Then the led lights off, the logo disappears, and the phone reboots. Again and again. I just reinstalled the same recovery and tried to wipe and fix permissions, but it does not solve the bootloop, and I don't know what to do...
Could it be possible that "rashr" did a bad install of TWRP and corrupted my recovery/bootloader partition or something ?
EDIT : I reinstalled Pure AOSP Lollipop, and now for some reason, no boot loop anymore... I don't understand why, but as long as it works... problem solved !

LegatoExia said:
Hello everyone, I have a problem with my xperia S, any help would be greatly appreciated! Let's start from the beginning, I'll try to be brief :
So, I flashed TWRP recovery using the app "RASHR" (I was using the Pure AOSP Lollipop rom when doing this, if it can help), which caused my phone to always boot the recovery and nothing else. I managed to flash the rom again (I made sure to wipe using "factory reset" and "dalvik cache" before installing), and it seemd to work perfectly, but then I rebooted the phone, and got stuck at the sony logo, no recovery available.
I flashed TWRP recovery (stock-6.1.A.0.452-twrp-2.4.0.0.elf) using flashtool, then tried to install another rom (Paranoid Android, found on this thread : http://forum.xda-developers.com/showthread.php?t=2573345). The first boot was successful, but as soon as I reboot the phone, I'm stuck in a bootloop again, with a little difference : when the sony logo appears, the led becomes pink for a few seconds. No access to recovery. Then the led lights off, the logo disappears, and the phone reboots. Again and again. I just reinstalled the same recovery and tried to wipe and fix permissions, but it does not solve the bootloop, and I don't know what to do...
Could it be possible that "rashr" did a bad install of TWRP and corrupted my recovery/bootloader partition or something ?
EDIT : I reinstalled Pure AOSP Lollipop, and now for some reason, no boot loop anymore... I don't understand why, but as long as it works... problem solved !
Click to expand...
Click to collapse
You flashed the TWRP in wrong way. You need to flash it by this method.

Mirhawk said:
You flashed the TWRP in wrong way. You need to flash it by this method.
Click to expand...
Click to collapse
Hello, and thanks for the answer ! After a few days using the Pure AOSP rom and rebooting several times without any problem, I just got a bootloop again yesterday, forcing me to reflash my rom to be able to use the phone again... will your method (including your tutorial in your signature, which I'm trying as I write this) solve the problem once and for all ? It's a real pain to redownload all my apps again and again and again because of those bootloops =(
Edit : finished following your tutorials, everything seems to work for the moment, hope it will stay stable this time... thanks for your help )

LegatoExia said:
Hello, and thanks for the answer ! After a few days using the Pure AOSP rom and rebooting several times without any problem, I just got a bootloop again yesterday, forcing me to reflash my rom to be able to use the phone again... will your method solve the problem once and for all ? It's a real pain to redownload all my apps again and again and again because of those bootloops =(
Click to expand...
Click to collapse
What did You do before the bootloop was caused? Did You try to flash the TWRP again?

Mirhawk said:
What did You do before the bootloop was caused? Did You try to flash the TWRP again?
Click to expand...
Click to collapse
No, I didn't, I was too afraid of creating another problem xD I just used the phone normally, installed apps from the play store, the last one being nova launcher (but I rebooted a few times after that without any issue)., things like that.
But after applying your tutorials to flash the Lollipop Pure AOSP rom, I think the problems were caused by :
1) a wrong recovery and/or flashing method : previously I used "stock-6.1.A.0.452-twrp-2.4.0.0.elf" which I flashed directly via flashtools with the phone in fastboot mode with the command "fastboot flash boot xxxxxx.elf". And although I didn't reinstall it after flashing the ROM, I suppose it left something in the recovery partition that caused the bootloop... ?
2) the fact that I didn't flash any "boot.img" at all before installing the ROM... inf fact, I didn't even knew it was necessary !
3) a bad ROM installation procedure : wipe, flash rom, gapps and SuperSU and THEN wiping cache and dalvik, restart
4) all of the above (!)
Anyways, after doing it "the right way", everything seems to work correctly for the moment. After installing the ROM, I followed your recovery tutorial using "openrecovery-twrp-2.8.5.0-LT26i.img", hope I did the right thing this time, hahah. Thank you again for your help !

LegatoExia said:
No, I didn't, I was too afraid of creating another problem xD I just used the phone normally, installed apps from the play store, the last one being nova launcher (but I rebooted a few times after that without any issue)., things like that.
But after applying your tutorials to flash the rom AND the recovery, I think the problems were caused by :
1) a wrong recovery and/or flashing method : previously I used "stock-6.1.A.0.452-twrp-2.4.0.0.elf" which I flashed directly via flashtools with the phone in fastboot mode with the command "fastboot flash boot xxxxxx.elf". And although I didn't reinstall it after flashing the ROM, I suppose it left something in the recovery partition that caused the bootloop... ?
2) the fact that I didn't flash any "boot.img" at all before installing the ROM... inf fact, I didn't even knew it was necessary !
3) a bad ROM installation procedure : wipe, flash rom, gapps and SuperSU and THEN wiping cache and dalvik, restart
4) all of the above (!)
Anyways, after doing it "the right way", everything seems to work correctly for the moment. Thank you again for your help !
Click to expand...
Click to collapse
Glad that it is worked for You. Yes, You did somethings wrong, which caused You bootloop, better explained as below:
1) The "stock-6.1.A.0.452-twrp-2.4.0.0.elf" is the stock kernel of ICS version of Xperia S. So if You flash it with a ROM, Your ROM won't boot.
See, each ROM consist of two main parts, one the kernel and other the is the remaining of ROM(apaps, data etc.) A ROM is compatible only with certain kernels, and if wrong kernel is used with a ROM, the ROM won't boot. This is what You were doing, using a stock kernel on non stock based ROM.
2) This essentially doesn't lead to boot loop. This step needs to be done sometimes if You occur a error while flashing ROM via TWRP sometimes.
3) Yes, this sometimes does cause issue, the procedure is always for a clean flash, -Wipe system, wipe data, wipe cache and wipe dalvik cache. Flash ROM and immediately wipe cache and dalvik cache.

Mirhawk said:
Glad that it is worked for You. Yes, You did somethings wrong, which caused You bootloop, better explained as below:
1) The "stock-6.1.A.0.452-twrp-2.4.0.0.elf" is the stock kernel of ICS version of Xperia S. So if You flash it with a ROM, Your ROM won't boot.
See, each ROM consist of two main parts, one the kernel and other the is the remaining of ROM(apaps, data etc.) A ROM is compatible only with certain kernels, and if wrong kernel is used with a ROM, the ROM won't boot. This is what You were doing, using a stock kernel on non stock based ROM.
2) This essentially doesn't lead to boot loop. This step needs to be done sometimes if You occur a error while flashing ROM via TWRP sometimes.
3) Yes, this sometimes does cause issue, the procedure is always for a clean flash, -Wipe system, wipe data, wipe cache and wipe dalvik cache. Flash ROM and immediately wipe cache and dalvik cache.
Click to expand...
Click to collapse
Okay, now I understand ! There are so many roms, kernels and things like that on the internet, it was quite confusing...
Thanks again good sir, your help was a precious time saver =D

LegatoExia said:
Okay, now I understand ! There are so many roms, kernels and things like that on the internet, it was quite confusing...
Thanks again good sir, your help was a precious time saver =D
Click to expand...
Click to collapse
can you please tell me how did you get out of the boot loop to begin with? i can't do anything...

Frostymoon said:
can you please tell me how did you get out of the boot loop to begin with? i can't do anything...
Click to expand...
Click to collapse
I guess You are on stock firmware and flashed the "stock-6.1.A.0.452-twrp-2.4.0.0.elf" or the twrp.img file via fastboot directly. Flash the DoomKernel from here via flashtool as kernel and it will work with stock and have recovery too. Use the blue coloured "Download Now" button and the extension of file is .elf.