[Q] [Xperia S] CM10 Installation problems - Sony Xperia S, Acro S, Ion

Hello.
I was running cm9 for a few months without problems. But since the update from Januari the 13th apps started crashing.. I then tried to completly reinstall (wipe everthing), but got stuck on bootloop. Then I thought lets try cm10, and also I get stock on the booting screen.
These are the steps I did.
Flashed LT26i_6.1.A.2.50_1257-5499_WORLD.ftf to go back to stock rom.
Went trough the wizard and all and let it settle down for a few minutes.
Shutdown.
Fastboot boot.img from FXP202-cm-10-20130110-UNOFFICIAL-nozomi.zip
Fastboot reboot
Enter recovery
Flash rom FXP202-cm-10-20130110-UNOFFICIAL-nozomi.zip
Flash gapps gapps-jb-20121011-signed.zip
Wipe cache
Wipe dalvik
Reboot system
But it never boots, I get stuck on bootscreen (same procedure I did with CM9, but also got stuck on bootscreen),
What am I doing wrong?

Try doing full wipe and reinstall CM 10 as you did previously
Sent from my Xperia S using xda app-developers app

I tried that too. Like this you mean
1. Fastboot boot.img
2. Fastboot reboot
3. Enter recovery
4. Factory reset
5. Wipe/format system, cache, data, dalvik
6. Install Rom zip
But then I get error and says installation aborted..
Sent from my LT26i using xda app-developers app

dumbl3 said:
I tried that too. Like this you mean
1. Fastboot boot.img
2. Fastboot reboot
3. Enter recovery
4. Factory reset
5. Wipe/format system, cache, data, dalvik
6. Install Rom zip
But then I get error and says installation aborted..
Sent from my LT26i using xda app-developers app
Click to expand...
Click to collapse
I have the same problem My phone not boot in just freexperia logo and cwm5.5.0.4. My /data partition can't mount and format I can't install any rom:crying: Heeeeeelp:crying:

All will be fixed
dumbl3 said:
Hello.
I was running cm9 for a few months without problems. But since the update from Januari the 13th apps started crashing.. I then tried to completly reinstall (wipe everthing), but got stuck on bootloop. Then I thought lets try cm10, and also I get stock on the booting screen.
These are the steps I did.
Flashed LT26i_6.1.A.2.50_1257-5499_WORLD.ftf to go back to stock rom.
Went trough the wizard and all and let it settle down for a few minutes.
Shutdown.
Fastboot boot.img from FXP202-cm-10-20130110-UNOFFICIAL-nozomi.zip
Fastboot reboot
Enter recovery
Flash rom FXP202-cm-10-20130110-UNOFFICIAL-nozomi.zip
Flash gapps gapps-jb-20121011-signed.zip
Wipe cache
Wipe dalvik
Reboot system
But it never boots, I get stuck on bootscreen (same procedure I did with CM9, but also got stuck on bootscreen),
What am I doing wrong?
Click to expand...
Click to collapse
Follow this thread for Kernel and Rom installation; http://forum.xda-developers.com/showthread.php?t=1879982
Follow this other to select your Rom; http://forum.xda-developers.com/showthread.php?t=1642480
And take that cm-10-20130110-UNOFFICIAL is CM 10.2 for such reason look for JB Gapps For Android version 4.1.2
I flashed the Rom very well, also the kernel. my problem were the Gapps. I see there that you do not have the correct gapp zip for cm-10-20130110-UNOFFICIAL;This is CM 10.2 after installation and you need a 4.1.2 JB Gapps. Try and repeat the process.
Regards,

apsanchezs said:
I see there that you do not have the correct gapp zip for cm-10-20130110-UNOFFICIAL;This is CM 10.2 after installation and you need a 4.1.2 JB Gapps. Try and repeat the process.
Click to expand...
Click to collapse
I do have the correct gapps. This CM is android version 4.1.2. Here I downloaded the latest for CyanogenMod 10.0.x which is for android versions 4.1.x.
Anyway after a whole evening/night of flashing I finally managed to get it working via hei1125 cm10 version:
http://goo.im/devs/hei1125/nozomi
I dont know what I did to make it working again, but it does.. CM10 does look a lot nicer then CM9. Although I heard it has some bugs, which yet I still have to encounter..

FXP202-cm-10-20130110-UNOFFICIAL-nozomi.zip fails
dumbl3 said:
Hello.
I was running cm9 for a few months without problems. But since the update from Januari the 13th apps started crashing.. I then tried to completly reinstall (wipe everthing), but got stuck on bootloop. Then I thought lets try cm10, and also I get stock on the booting screen.
These are the steps I did.
Flashed LT26i_6.1.A.2.50_1257-5499_WORLD.ftf to go back to stock rom.
Went trough the wizard and all and let it settle down for a few minutes.
Shutdown.
Fastboot boot.img from FXP202-cm-10-20130110-UNOFFICIAL-nozomi.zip
Fastboot reboot
Enter recovery
Flash rom FXP202-cm-10-20130110-UNOFFICIAL-nozomi.zip
Flash gapps gapps-jb-20121011-signed.zip
Wipe cache
Wipe dalvik
Reboot system
But it never boots, I get stuck on bootscreen (same procedure I did with CM9, but also got stuck on bootscreen),
What am I doing wrong?
Click to expand...
Click to collapse
I'm on the same problem. Use FXP201 instead or wait until 203... The cm10-fxp202 doesn't work on my device too. Same procedure as Yours or update from 201 to 202 - all will fail on (my) nozomi.

Hello!
Hello! orange fix for this rom?if so, I would like to link to it? thank you very much :fingers-crossed:

Had same problem with fxp202 ans SSpeed rom.
Just try to install another kernel.
I had same problems with rom's above, I installed nova kernel nozimi and I have no problems anymore.
Sent from my Xperia S using Tapatalk 2

funky0308 said:
Had same problem with fxp202 ans SSpeed rom.
Just try to install another kernel.
I had same problems with rom's above, I installed nova kernel hikari and I have no problems anymore.
Sent from my Xperia S using Tapatalk 2
Click to expand...
Click to collapse
i got same plobrem with You.

Hello,
I have a problem updating my nozomi (xperia s) to the newest cm version. I always get error 7 - some symlinks failed and i cant install an update without factory reset / wipe user data. After this step i can install the zip, but without wipeing, always the same error.
When i'm installing updates on my girlfriend's urushi (xperia ray), everything works fine.
Any ideas?
Thanks

Enable signaturecheck in recovery before install. It worked for me.
Gesendet von meinem Xperia S mit Tapatalk 2

Make sure you flash the good .img before flashing the ROM !

alexdan2302 said:
Hello,
I have a problem updating my nozomi (xperia s) to the newest cm version. I always get error 7 - some symlinks failed and i cant install an update without factory reset / wipe user data. After this step i can install the zip, but without wipeing, always the same error.
When i'm installing updates on my girlfriend's urushi (xperia ray), everything works fine.
Any ideas?
Thanks
Click to expand...
Click to collapse
It's always recommend to wipe all (cache, davlink even system) then flash.
Be sure to mount system and then try.
And of course, check is you zip file o.k (maybe download again)
Even if you updating cm to new version it's best if you wipe.
I know that's lot of work, but only then you'll have good battery life, smooth and fast ROM and stability.
Sent from my LT26i using Tapatalk 2

Reinstalled apps and Data from googleserver after a datawiped update shoudn't be a Problem, or?
Gesendet von meinem Xperia S mit Tapatalk 2

I had just the same problem today. I installed cm10 from recovery and did everything you did!!!!
What i did to solve this prblem is:
- Went into recovery.
- wiped cache and dalvik.
- flashed the latest CM10 (FXP215 to be precise) again!!
- flashed gapps again!!
- after flashing both zips I wiped dalvik and cache again.
- Than reboot.
If you keep getting into bootloops, keep doing these steps. Beliefe me man I had the exect same problam today and this solved it . Just dont panic or do something stupid and have alot of patients! :good:

But this is not a so called clean install. I use factory reset to have a clean install or just wipe data partition. After 1st boot I restore only some of my saved data with titanium backup.
Gesendet von meinem Xperia S mit Tapatalk 2

Related

Cyanogen boot loop

i have googled this and tried multiple ways of installing it but i always get a boot loop. Whats going on?
Hey if you just want to get your phone back again, just flash another firmware from the one you used. Should start up just fine.
have done already but i actually want to install cyn mod. I managed to get as far as the main screen buit then immediately reboots. I cant find wifi modules for latest doom kernel either they arent in his thread.
FLASH KERNEL FIRST (from cyanogenMOD or doomkernel for CM7 etc)
Than flash cyanogenMOD
any other way will make your phone bootloop.
I think you have to unlock BL via SE in order to flash CM..
of course you would likely broke your warranty.
this based on my experience (I'm a newbie too in the android's world). this is what I've done :
1. unlock BL via SE (not all carriers allowed this!)..
2. flash .42 fw
3. follow the instructions given on CM thread by fxp.
it's worked for me.
goodluck.
I've had this problem before. Did you wipe the delvic cache, wipe data/factory reset and wipe cache partition in CWM before you flashed the update.zip?
It would seem it was a specific version of cm that was making it bootloop the one from dooms thread 7.2.0 works fine and also the one before the latest stable release also worked fine. I however found a problem with the spacebar on the keyboard when using the phone in landscape so am now going to try arconium and doom kernel its a shame really because cm from what i used of it looked really nice.
Try 7.1.0.1.
I got bootloop too with 7.1.0.2
Kuroyukii said:
Try 7.1.0.1.
I got bootloop too with 7.1.0.2
Click to expand...
Click to collapse
Aye thats the one i used but ended up having a problem with the spacebar not working in landscape so am on acronium now which is all good but superuser keeps crashing meh always something eh.
at first im also having the same problem,just follow the instruction by FXP : flash bb56,flash fw.42,flash FXP kernel via fastboot,flash update via recovery,wipe dalvik cache,reboot..
Sent from my LT18i using Tapatalk
I have this exact same problem
I've done everything I was supposed to, I think, and still doesn't work. It boots, shows me the little Android "Welcome!" screen, and before I have time to press anything or begin setting up my device, it reboots into the Cyanogenmod loading screen. I've tried different kernels, different basebands, every time wiping Dalvik cache, etc. and it REFUSES to work. I'm pretty desperate by now because I really wanted to use this ROM so any help is greatly appreciated.
I also followed precisely rashid.fairus' instructions and it still does the exact same thing.
You need to Wipe Data, Cache and Dalvik ----- BEFORE AND AFTER FLASH
I do this here, and positive feedback
Velcis Ribeiro said:
You need to Wipe Data, Cache and Dalvik ----- BEFORE AND AFTER FLASH
I do this here, and positive feedback
Click to expand...
Click to collapse
Sometimes you DON'T WIPE ANYTHING AT ALL. Just flash CM and Google.
Works for me on Xperia Acro S.
gabantarung said:
Sometimes you DON'T WIPE ANYTHING AT ALL. Just flash CM and Google.
Works for me on Xperia Acro S.
Click to expand...
Click to collapse
Only when you upgrade to a later version of the same ROM.
Sent from my Xperia Arc S using xda premium
Velcis Ribeiro said:
You need to Wipe Data, Cache and Dalvik ----- BEFORE AND AFTER FLASH
I do this here, and positive feedback
Click to expand...
Click to collapse
Wipe dalvik and cache when upgrading to later version, wiping data will reset phone to factory settings and you lose all personal data.
僕のLT18iから送られてきた

[Q] <URGENT> Phone Dead! :'(

Hey guyz!
Well, Here's my story
I unlocked the bootloader of my Arc..... Flashed the 0.42 rooted .ftf file and well I had my arc.
I took backup of all my stuff and thought of installing CM7.
So well, I downloaded the latest CM7 Mod from the website stable one and fastboot'd (or whatever the language is) the boot.img into my arc.
And den I booted my phone into recovery mode, wiped my cache, system and data and flashed the update_cm7.1.zip file into it.
Not my phone after booting up dosent work. It shows the lock screen and within a second boots again :'(
I searched and found that I did not install the CWM Recovery and guessed that it was crucial for it.
Now I have a dead phone.
Can you Pleaaaaaaaase Help Me out!
My mobile is my life and my parents will kill me
Thanks Alot!
Install doom kernel via fastboot
Enviado desde mi LT18i usando Tapatalk
Done Doom Kerenal
Still going into Infinite BootLoop!!
you usually wipe everything(user data, cache, dalvik cache) after flashing the ROM
or try repeating the whole process
- flash .42 ftf file using flashtool 0.6.7 then disconnect device
- fastboot flash boot boot.img(from the CM7 package) then disconnect device
- power-on and go to recovery then flash the CM7 ROM then GAPPS
- wipe user data, cache and dalvik cache
- reboot
I suggest you also try FXP105 package here in XDA, I think it's more updated than the one from official CM7 site
terranox said:
Install doom kernel via fastboot
Enviado desde mi LT18i usando Tapatalk
Click to expand...
Click to collapse
What are you talking about?
DooMKernel is for stock based ROMs, not for CM.
I'd recommend to you to check out FXP's CM7, it's way better and stable, imo.
Rycon33 said:
you usually wipe everything(user data, cache, dalvik cache) after flashing the ROM
or try repeating the whole process
- flash .42 ftf file using flashtool 0.6.7 then disconnect device
- fastboot flash boot boot.img(from the CM7 package) then disconnect device
- power-on and go to recovery then flash the CM7 ROM then GAPPS
- wipe user data, cache and dalvik cache
- reboot
I suggest you also try FXP105 package here in XDA, I think it's more updated than the one from official CM7 site
Click to expand...
Click to collapse
Ill Try!
Thanks Alot!
Whats GAPPS?
And Dalvik cache? How can I clear it
SS4Serebii said:
Ill Try
Whats GAPPS?
And Dalvik cache?
Click to expand...
Click to collapse
Go here.
And dalvik cache is under advanced options in CWM.
Ok, Followed your steps but going into infinite boot loop :'(
Will try for CM7.2.0 - FXP10
SS4Serebii said:
Ok, Followed your steps but going into infinite boot loop :'(
Will try for CM7.2.0 - FXP10
Click to expand...
Click to collapse
Do that and follow these steps:
dp94 said:
Connect your device with your current ROM to a PC.
Put the ROM (*.zip file) on your sdcard.
Shutdown device.
Connect your device with fastboot mode (pressing menu button) to a PC.
Go to your fastboot folder.
Press shift key, right click and select "Open command window here".
Install kernel by using the command "fastboot flash boot boot.img".
After installing disconnect your device from PC.
Enter CWM recovery by pressing volume down button several times while booting.
Do a full wipe/factory reset, wipe cache, wipe dalvik cache.
Select install zip from sdcard.
Navigate to the folder you've saved the ROM and select it.
After installing select reboot system now.
Click to expand...
Click to collapse
Now I got the same problem as Serebii. I've done all you've said, but I just get a black screen flashing the kernel. The fxp-Logo doesn't appear and I can't get into recovery mode.
Have you guys flashed .42 firmware before?
Or are you using a different?
You'd have to flash .42 firmware (look into CM7 thread) and then do the above steps again.
guys, when flashing kernel, look closely on your fasboot command window if there's something like "1 bad blocks encountered" message
should be "0 bad blocks encountered" for the kernel to work fine from what I know
Did That
Still Nothing...
Although Unlike macmeir, I'm able to go into recovery adn first see SE, and den CM7 boot logo
And also 1 second of the CM7 Welcome screen.
Thats It
Yea, It isnt showing any bad blocks
Now I got my phone back to life. I flashed the .42 firmware with flashtool. But then I had to install the fxp103-stuff. I cleared all caches, etc. It's strange; I did it before but it didn't work. I don't know if I've done something different.
But I'm still not able to run fxp104 or 105. I won't try again soon, because I spend five hours to get my device working.
Thanx for your help and good luck to you, Serebii.
good for you.
btw, you can also try Doomkernel on stock ROM, it's a great combo, I always go back to that setup
OK,
I flashed the latest CM7.2 And My Phone's alive Again!
A Biiiiiiiiig Thanks to Everybody!!

RobotoMOD - Xena v1.0.1 Installation Problem

Hi,
Im trying to install this rom.
Currently using using modpunk's cm9 alpha6.
Got little problem then decided to re-flashing the rom.
Im using CWM5.0.2.8.
What i did was,
1. boot into CWM
2. factory reset
3. clear dalvik cache
4. install from zip
installation was successful. however, my phone keep booting into H-BOOT everytime.
anyting went wrong in the steps?
hellilyntax said:
Hi,
Im trying to install this rom.
Currently using using modpunk's cm9 alpha6.
Got little problem then decided to re-flashing the rom.
Im using CWM5.0.2.8.
What i did was,
1. boot into CWM
2. factory reset
3. clear dalvik cache
4. install from zip
installation was successful. however, my phone keep booting into H-BOOT everytime.
anyting went wrong in the steps?
Click to expand...
Click to collapse
cleared cache partition too?
try going into "mounts & Storage" and formatting everything (except SD Card) and try again.
elspanish88 said:
cleared cache partition too?
try going into "mounts & Storage" and formatting everything (except SD Card) and try again.
Click to expand...
Click to collapse
just re-flash rom using modpunk's alpha7.
i will try that another time.
thanks for your reply.
hellilyntax said:
Hi,
Im trying to install this rom.
Currently using using modpunk's cm9 alpha6.
Got little problem then decided to re-flashing the rom.
Im using CWM5.0.2.8.
What i did was,
1. boot into CWM
2. factory reset
3. clear dalvik cache
4. install from zip
installation was successful. however, my phone keep booting into H-BOOT everytime.
anyting went wrong in the steps?
Click to expand...
Click to collapse
I have 2 ideas.
1. When you boot the phone, just press the button instead of holding it down like most people do. It will still boot properly and should cut out any chance of it booting into H-BOOT.
2. If it still goes into H-BOOT even just pressing instead of holding the button then factory reset, clear dalvik cache and install the zip all over again.
If the problem still happens then go to the original RobotoMod thread and post the problem there so the developer can see it. He'll have the best idea out of anyone.
hellilyntax said:
Hi,
Im trying to install this rom.
Currently using using modpunk's cm9 alpha6.
Got little problem then decided to re-flashing the rom.
Im using CWM5.0.2.8.
What i did was,
1. boot into CWM
2. factory reset
3. clear dalvik cache
4. install from zip
installation was successful. however, my phone keep booting into H-BOOT everytime.
anyting went wrong in the steps?
Click to expand...
Click to collapse
I had the same problem...
i tried again except this time i did a custom installation and did not install gappsextra.what you do is when it asks you if you want to install google apps...select install but in the next screen uncheck all the apps(there are only 3)....that should do it.
---------- Post added at 01:10 AM ---------- Previous post was at 01:04 AM ----------
im getting some problems after installing the rom though and was hoping i could get some help on it.
first of all it does not recognise my ext partition through terminal or recovery...
and also my mobile network doesnt work smoothly after i installed this...i have to keep rebooting it for it to work.
I also have problem
I also face a problem while installing that rom. That is not boot. My phone is reboot to recovery when it had finished the installation. How can I fix it???
DuWun said:
I also face a problem while installing that rom. That is not boot. My phone is reboot to recovery when it had finished the installation. How can I fix it???
Click to expand...
Click to collapse
did you try the custom installation like iv mentioned?
I'm having a similar problem
When I first installed RobotoMod I used the recommended settings, but after the reboot the phone just stays on the white HTC screen it was, at first i thought it was just loading, so i gave it a little more time (about 7 hours) but still nothing happened, so I tried using the custom settings and through multiple attempts and combinations all on the CM9 alpha it booted up, but as soon as it was done loading it put me straight into the lockscreen and wont unlock no matter what I do, I've tried AOKP but that just gets the 1st problem, and ive seriously tried everything and I haven't found anyone with the same problem maybe its just me, i installed using CWMR 5.02.8
use
DuWun said:
I also face a problem while installing that rom. That is not boot. My phone is reboot to recovery when it had finished the installation. How can I fix it???
Click to expand...
Click to collapse
use gapps extra instead of rcommended ones on 2 pop up

[Q] Boot Loop, Need help!

i have been running the kiss kernel for a while now, last night i tried to flash the hellboy kernel and retern to my pacman rom. but it still boots, i have cleared all my caches formated everything but my sd card, have tried flashing all kiss kernels and multipul hellboy kernels, but never gets passed the boot screen.. any ideas?
i managed to get it to the android is upgrading.. starting apps thing, but it gets stuck there.
Did you wipe anything when you flashed the kernel? If the kernel was for jellybean it shouldn't hang like that... not sure?
lilrob1213 said:
Did you wipe anything when you flashed the kernel? If the kernel was for jellybean it shouldn't hang like that... not sure?
Click to expand...
Click to collapse
yeah i wiped the cache, devlink cache, data, system, and a factory reset, been trying to figure it out all day but have not made much improvement
JARR3DF15CH3R said:
yeah i wiped the cache, devlink cache, data, system, and a factory reset, been trying to figure it out all day but have not made much improvement
Click to expand...
Click to collapse
and you installed a rom after wiping those things right? I'm assuming... but just wondering. What rom did you flash and are you CDMA virgin mobile?
lilrob1213 said:
and you installed a rom after wiping those things right? I'm assuming... but just wondering. What rom did you flash and are you CDMA virgin mobile?
Click to expand...
Click to collapse
yeah i installed it after, pacman http://forum.xda-developers.com/showthread.php?t=1948770&page=12
im with telus gsm. the rom was working fine, but i went to change the kernel to hellboy cause i herd it was a bit better and now im in this bootloop
also not running the newest version of that rom, i am running v15a
Oh okay wellllll I'm on virgin mobile and I don't know much about the primou phones and rom and kernel compatibility so I'm afraid I'll have to leave this to someone who knows more... good luck to you though... maybe try booting into bootloader from the recovery and flash the boot.img you had before then flash the rom again?
lilrob1213 said:
Oh okay wellllll I'm on virgin mobile and I don't know much about the primou phones and rom and kernel compatibility so I'm afraid I'll have to leave this to someone who knows more... good luck to you though... maybe try booting into bootloader from the recovery and flash the boot.img you had before then flash the rom again?
Click to expand...
Click to collapse
thanks anyways, ill be sure to give that a try:silly:
Did u wait Little longer time while first boot???? Choose latest kernel n flash. .
Hit thanks if I helped u!!!
bahubali67 said:
Did u wait Little longer time while first boot???? Choose latest kernel n flash. .
Hit thanks if I helped u!!!
Click to expand...
Click to collapse
yeah i always wait a little while, i have chosen latest kernel, has not made a difference, i have gotten better results using an older one of the titanium kiss, hellboy doesnt seem to work with my phone for some reason
Did you use the command
fastboot flash boot boot.img or just
fastboot boot boot.img?
Also,after flashing it,does the terminal say something like this?
Okay.
Okay.
Finished.
Edit:also,see that you are flashing the kernel in the fastboot screen(where it says 'fastboot usb'),and not in the Hboot(bootloader) screen.
mihirengg19 said:
Did you use the command
fastboot flash boot boot.img or just
fastboot boot boot.img?
Also,after flashing it,does the terminal say something like this?
Okay.
Okay.
Finished.
Edit:also,see that you are flashing the kernel in the fastboot screen(where it says 'fastboot usb'),and not in the Hboot(bootloader) screen.
Click to expand...
Click to collapse
i am using the all in one tool kit to flash my kernel, yes i am in fastboot, a window pops up runs through code and my phone reboots, i have changed the kernel on it before, but for some reason this time it wont boot properly at all, the phone is currently at the " android is upgrading" screen, it was the starting apps box with the spinning circle
if you say that it is stuck at android is upgrading - that's because the dalvik works and it is deodexing your gapps.
so i suppose you flashed kernel, flashed rom and gapps and rebooted. well this works from time to time but you have to reboot between flashing rom and gapps.
1. download this kernel: hellboy
2. go to bootloader and flash the kernel.
3. go to recovery and: do a factory reset + wipe system - no need for wiping dalvik or cache cause factory reset does them both.
4. flash your rom
5. reboot.
6. if it boots properly, reboot to recovery and now flash GAPPS package.
1ceb0x said:
if you say that it is stuck at android is upgrading - that's because the dalvik works and it is deodexing your gapps.
so i suppose you flashed kernel, flashed rom and gapps and rebooted. well this works from time to time but you have to reboot between flashing rom and gapps.
1. download this kernel: hellboy
2. go to bootloader and flash the kernel.
3. go to recovery and: do a factory reset + wipe system - no need for wiping dalvik or cache cause factory reset does them both.
4. flash your rom
5. reboot.
6. if it boots properly, reboot to recovery and now flash GAPPS package.
Click to expand...
Click to collapse
thank you so much 1ceb0x! my phone has been in this bootloop for an entire 24 hours,
1ceb0x said:
if you say that it is stuck at android is upgrading - that's because the dalvik works and it is deodexing your gapps.
so i suppose you flashed kernel, flashed rom and gapps and rebooted. well this works from time to time but you have to reboot between flashing rom and gapps.
1. download this kernel:
2. go to bootloader and flash the kernel.
3. go to recovery and: do a factory reset + wipe system - no need for wiping dalvik or cache cause factory reset does them both.
4. flash your rom
5. reboot.
6. if it boots properly, reboot to recovery and now flash GAPPS package.
Click to expand...
Click to collapse
hey icebox, i have the same problem, stuck on pacman logo
can you tell me which hellboy kernel should i use?
i've flashed the 1st one on the mediafire list. thanks!
chikuera said:
hey icebox, i have the same problem, stuck on pacman logo
can you tell me which hellboy kernel should i use?
i've flashed the 1st one on the mediafire list. thanks!
Click to expand...
Click to collapse
Thats the old version.... See the changelog code and flash dat in future..... Right now.... Here u go....
http://www.mediafire.com/?waggdha1ir1lxz0

[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.

Categories

Resources