Related
I have a r800i and when I try to boot it with DoomKernel ICS v0.3 it always boot into the recovery even though I have a room installed.
I installed xDark ICS by opening the zip. I also did a factory wipe, wiped the cache, the debian one, but it still only boots into recovery. When I used DoomKernal v14 with the NXT rom, it boots fine although I can't enter recovery (so I can't patch the wifi). Using the default ftf everything works normally.
Any help would be greatly appreciated. I've also search the forums for similar problems but I've only found similar problems with other phones using other kernals and roms.
I am having the same problem, except I cannot even get at recovery, it just sits at Kernel splash screen. Otherwise I'd have restored my nandroid backup already.
I flashed ics doomkernel, factory reset, wipe cache and dalvik then flashed rom in CWM and now my device is stuck.
Bootloader unlocked r800a
Can anyone help us two?
Sent from my backup x10 using xda premium
:highfive:Both cases sound like bad flashes. For the first post I'd say CWM restore it and try to reflash. For the second post, I'd say use flashtool on your pc and flash a stock rom again.
I tried installing a rom last week on my Galaxy Note II (Rogers), i followed orders (this isn't my first time flashing roms), and it has been stuck in a constant boot loop.
I've tried everything, wiping cache, factory reset, tried to flash different roms, etc....
I am a mac user (which means Odin isn't an option).
If you guys have any suggestions on how to fix this it would be greatly appreciated.
What rom were you on and what rom were you trying to flash originally? Also what recovery are you using? Need a little more info because usually wiping caches dies the trick. Provide a link to the rom you were trying to flash of your can.
jethro650 said:
What rom were you on and what rom were you trying to flash originally? Also what recovery are you using? Need a little more info because usually wiping caches dies the trick. Provide a link to the rom you were trying to flash of your can.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1986893
This is the rom, i was using CMW to flash it, then it made me switch to TWRP (think its called that)......hope that helps.
Sorry I can't be of more help aside of redoing the installation of your recovery and redownloading the rom ( bad downloads happen) and making sure you do all the wipes (cache, dalvik cache and factory reset). If none of that works I'm sure someone more knowledgable than myself will chime in.
I've never run into a bootloop problem myself, but this might help you out :
hxxp://galaxynote2root.com/galaxy-note-2-tutorials/how-to-unrootunbrick-galaxy-note-2-with-stock-firmware/
Good luck
Have you had any luck with this yet? I've been unable to get my phone back up.
QuantumPSI said:
Have you had any luck with this yet? I've been unable to get my phone back up.
Click to expand...
Click to collapse
No luck, but then again i am a Mac user, so its a little more difficult for me to solve this problem.
Anirchy said:
I tried installing a rom last week on my Galaxy Note II (Rogers), i followed orders (this isn't my first time flashing roms), and it has been stuck in a constant boot loop.
I've tried everything, wiping cache, factory reset, tried to flash different roms, etc....
I am a mac user (which means Odin isn't an option).
If you guys have any suggestions on how to fix this it would be greatly appreciated.
Click to expand...
Click to collapse
Put another ROM on an sdcard. Take your battery out then press the button combo for recovery mode before you slip your battery back in. Then it'll force download mode. Reflash the new ROM after full wiping and you should be good.
Sent from my SGH-I317 using xda premium
Definitely a bad ROM. Run a MD5 checker against it prior to copying to the SD card. Note: your SD card could be the culprit.
If you have a recovery installed, ensure you WIPE everything, Fix permissions (i'm on CWM) and reflash the modem and carrier files POST rom install.
I experienced my first boot loop yesterday but I was able to recover from it thanks to a little common sense and patience. :fingers-crossed:
Good luck!
first of all, don't freak out, a bootloop isn't the end of the world. Sounds like it was a bad flash.
ppl above have obviously told you to wipe caches, and all that stuff and if it hasn't worked then you are still down and out.
I would suggest you get yourself into recovery - not going to explain that here as you said you were able to flash other roms and it didn't work and try flashing your nand backup - hopefully you have a nice clean backup from before you flashed. if so, clear caches, etc and then try flashing it it should be back to at least working.
your nand backup will have all your stuff in it as you would have had to backup from recovery, which means you'll at least still be rooted. you can then go ahead and get another rom - check the md5 and flash it
Hello! I am new to the Xda community, and I have a Xperia S. I went throw a lot of Rom threads and read all, even video tutorial and because of that I got confused. Can anyone spare some time (aprox. 10 mins) to answer me some questions, by chatting or here. Please do not make a fool out of me like some other guys around here.
1. if i go into bootloop after flashing CM10, can i restart the phone and go into CWM without flashing again boot.img, and flash the rom again?
2. if i go into bootloop after flashing CM10, do i have to flash the stock rom using flashtool?
3. tell me a simple way to get out of bootloop.
4. flashing the CM10 on my SXS with built number *.2.55 will work?
If I have made anymistakes by posting this here, i would like someone to take it down. Thank you for your time.
chossen said:
Hello! I am new to the Xda community, and I have a Xperia S. I went throw a lot of Rom threads and read all, even video tutorial and because of that I got confused. Can anyone spare some time (aprox. 10 mins) to answer me some questions, by chatting or here. Please do not make a fool out of me like some other guys around here.
1. if i go into bootloop after flashing CM10, can i restart the phone and go into CWM without flashing again boot.img, and flash the rom again?
2. if i go into bootloop after flashing CM10, do i have to flash the stock rom using flashtool?
3. tell me a simple way to get out of bootloop.
If I have made anymistakes by posting this here, i would like someone to take it down. Thank you for your time.
Click to expand...
Click to collapse
I dont have an Xperia yet, but from reading and experience from other phone ...
1) did you wipe data, cache and dalvik cache? if not, try to do it and check again for bootloops. If not possible then reflash the firmware and try to wipe these things directly after flashing the firmware.
2) if you wiped, try to restart with flashing the firmware again and wiping everything.
3) if nothing working reflash stock, boot stock once to see if it is working without bootloops and then restart from scratch.
4) if also not working .... is it the correct firmware? did you forget something?
There are good instructions for the firmwares, if you do everything as explained, you shouldnt get bootloops. But ... no howto is perfekt.
Its mostly trying as much as possible, till you have the correct way to flash a firmware. Bootloop isnt that bad ...
If you have a way which works for you, keep the steps for later flashing and tell the community what you had to do differently or if you missunderstood some points, even then tell it, because that can make these instructions better.
---------- Post added at 04:36 PM ---------- Previous post was at 04:31 PM ----------
chossen said:
4. flashing the CM10 on my SXS with built number *.2.55 will work?
Click to expand...
Click to collapse
I would say that it doesnt matter which firmware is on the phone, as long as you unlock the bootloader and the fastboot or flashtool is working.
The custom firmwares use the same methods but might have added recovery for easier flashing later.
You should even be able to downgrade to older firmware with unlocked bootloader and flashing the ftf file.
Its only important to wipe the data, cache and dalvik cache that the firmware is working.
thank you very much but still to solve all of my problems:
You said "1) did you wipe data, cache and dalvik cache? if not, try to do it and check again for bootloops. If not possible then reflash the firmware and try to wipe these things directly after flashing the firmware."
what do you mean by that? which firmware to reflash CM10? how by restarting the phone? and will i be able to go into CWM without the boot.img?
chossen said:
thank you very much but still to solve all of my problems:
You said "1) did you wipe data, cache and dalvik cache? if not, try to do it and check again for bootloops. If not possible then reflash the firmware and try to wipe these things directly after flashing the firmware."
what do you mean by that? which firmware to reflash CM10? how by restarting the phone? and will i be able to go into CWM without the boot.img?
Click to expand...
Click to collapse
With different phone and different firmware i had some issues with recovery, specially if i didnt wipe directly after flashing the new firmware without reboot and without reboot into recovery ...
I hope i dont mix anything up. CWM is the recovery (?)
The recovery function is part of the kernel image which is exactly the boot.img.
You can see at the freexperia project page howto install CM10, i cant post links at the moment.
3rd point is flashing the CM kernel (boot.img)
4th point is booting into recovery
From that recovery you can flash the custom rom as described in point 5.
Point 6 is wiping the device, which is neccessary for first custom rom or if you change version (eg. CM9 to CM10) or if you change to a different ROM.
Most bootloops happen if you forget to wipe the device. I am not sure, but most important is dalvik cache, if that one is wiped the next boot takes longer, as it will be rebuilt during boot.
If you get into a bootloop after flashing kernel and custom rom, go into recovery and wipe the device, try rebooting.
If still in bootloop, try to reflash the custom ROM as in point 5 (starting at 4th point) and wipe device after flashing
If it didnt help, try reflashing the kernel and ROM, starting at point 3 and include the wiping the device.
If that didnt help, try to go back to full stock (kernel and rom) and repeat.
But check if you got the correkt ROM for your device.
Play a bit around with the steps, you can even reflash the kernel and leave the rom. I had once a bad situation with bootloops, but they are easy to fix. More important is the part with the kernel, i think there you can brick your device.
But when you follow the instructions you shouldnt have too many problems, just dont jump over a step at the first flashing. But as allways sayd, every custom rom, every kernel flashing can harm your device and you're responsible on your own.
But if you get into problems, write down what you did and you will get help here.
Edit:
"if not possible then reflash the firmware ..." There i had once a problem with a different device. I forgot to wipe after flashing a new version and got into a bootloop. In recovery i couldnt wipe the device fully, something got bugged, but reflashing helped. Reflashed wiped and i could reboot into system. As it was longer time ago i dont remember what exaclty happend, but i think the problem was about forgetting to wipe the device.
Wow Thank you soo much, you lost allot of time explaining this to me, I really appreciate it i understood everything I owe you really
ooh and what do you mean by wipping - all: factory reset, cache and dalvik or just cache?
Sent from my LT26i using xda premium
chossen said:
Wow Thank you soo much, you lost allot of time explaining this to me, I really appreciate it i understood everything I owe you really
ooh and what do you mean by wipping - all: factory reset, cache and dalvik or just cache?
Sent from my LT26i using xda premium
Click to expand...
Click to collapse
didnt take too much time
in case of first custom rom, changing custom rom version (e.g. CM9 -> CM10) or changing to a different custom rom: all: factory reset, cache and dalvik
in case of updating (e.g. CM10->CM10): dalvik should be enough, maybe cache and dalvik.
If something not working, do a complete wipe.
As I understand from what I read, you flashed cm10 and are now stuck at boot, did you fastboot the kernel? On my xperia s I always need to fastboot the kernel after flashing a ROM, especially when changing from an ICS to a jb ROM.
Sent from my Xperia S using xda app-developers app
daddyc00l said:
As I understand from what I read, you flashed cm10 and are now stuck at boot, did you fastboot the kernel? On my xperia s I always need to fastboot the kernel after flashing a ROM, especially when changing from an ICS to a jb ROM.
Sent from my Xperia S using xda app-developers app
Click to expand...
Click to collapse
No, he has no bootloops, from what i understood he is scared to get into bootloops and doesnt know what to do if it happens.
Hmm, kernel flashing after upgrading from ICS to JB? or all the time?
By kernel flashing you mean the boot.img flashing with fastboot, and its the same file as flashed before?
I've only ever fastboot'd my first kernel, advanced stock kernel. Any others have always been in recovery and never had any issues
Sent from my Android 4.2.2 Xperia S
It seems that you got the wrong Kernel. I'm not sure, of course.
But I had that issue some time ago, and a fix it flashing the right kernel that I found on xda forum. Ohh, dont forget to do the proper wipes.
I hope u solve this as soon as possible.
For some good info on recovering a phone read through the recovery thread in my signature.
Even if you don't have any issues now, you can see what others have done wrong & right.
From Jaramie's LT28at
2012Xperia SOFT-BRICK Recovery Thread
Help
I have had my phone rooted for 3 months now so i decided to go to the next level and install a custom rom. I installed cynagenmod on my device via clock work mod.
Just to let you know i have CLOCKWORKMOD ASWELL
As i did it it installed correctly until i booted it and realized i was in a boot loop.
the cynagen mod would freeze half way through the boot.
I have tried odin but i'm not sure if i'm doing it wrong, is there any other software or things u can do. Is it possible to do it with clockwork mod, i had tried the update thing but it aborts and i can seem to get a rom that i can use that would help or is there a will load as a zip. is there any thing that you guys have done that unbricked ur wonder that you could share ?
Thank you for your time
just suggest., reboot to CWM and wipe data, wipe cache, and wipe dalvik cache.
if it can't solve the problem you should to flash custom ROM again via CWM and if it can't solve your problem again, just back to Stock.
Go to cwm
Wipe data
Wipe cache
Flash download zip custom rom
Flash gapps
And enjoy it
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.