Hello,
I unlocked bootloader on my SP and flashed it with DooMKernel. Then, i installed Cyanogenmod. But i flashed it with doom again. Now, i am stuck in boot loop. It just shows doomkernel loading, and then some graphical artifacts, and then restarts itself
What i should do ?
DoomKernel only works on Stock Based ROMS
So reflash CM
Thats the problem i wont get into recovery ! I just see Doomlord screen and then some mumbo jumbo with black lines and blue screen
Okay now i flashed stock kernel with CWM and TWRP but i can no more install Cyanogenmod, installation fails...
Reflash stock and start over.... That is all you can do now since the recovery seems to be gone?
(Or try advanced kernel with recovery in it)
Okay it worked ! I flashed it with this kernel
http://forum.xda-developers.com/showthread.php?t=2646193
And then just wiped data and installed android, worked like a charm...
Great
Enjoy your revived PHone
Related
Hey!
I tried flashing CM10.1 but something went wrong when I flashed the boot.img. Whenever I try to flash a new boot.img in fastboot the phone reboots before the install is complete. I then tried to install the Doomkernel v06 through recovery (both CWM and TWRP), it seems like it works and I tried to install another room I had (KA05), still stuck in bootloop.
There is no green led when entering flashboot, but the flashtool finds the phone before it restarts again.
So yeah.. I'm rather stuck with no possibility of flashing stock ftf and no way of flashing anything but the Doomkernel v06 through recovery.
[SOLVED!!]
I managed to solve this by trying to install different roms and kernels. Ended up with Cyanogenmod (the one I was trying in the first place).
Not sure I'll be able to change back to anything though, but yeah at least it's not dead
Oh, and the kernel and rom I tried with was on the internal SD from earlier (backup if something went wrong)
ok, I managed to get into Cyanogenmod 10.1 now!
However, I don't have service, and it doesn't appear to find my sim-card
Hello everybody!
I used to have a working stock firmware 2.67 Android 4.2.2, but I decided to unlock my bootloader.
I did the operation twice and then I encountered bootloop issue.
I downloaded a stock firmware and flashed it using Androxyde Flashtool.
Oh god! The firmware FTF file was corrupted.
I AM sure that it was corrupted.
Next up, I booted my device but it won't let me inside: Just the SONY screen and a black screen and afterwards and it goes off.
Then I flashed CWM Recovery as a boot.img file. After that I entered (luckily!) the CWM recovery, Cleaned Cache and performed Hard reset and installed the CyanogenMod 10.2 Yuga Nightly (or sth like that) as a zip. It said that it had been successful.
Despite that, when I rebooted device through CWM, I got the CyanogenMod boot screen( a blue orbit moving around) and it shows that forever!
What is wrong with my smartphone?
How can I fix this thing without a fresh installation of the stock firmware?
And if you flash cm again without wipe data?
Do you tryed to flash only an other kernel?
Tipp: always do Backups before flashing new CFWs.
This always happens to me, I installed cwm and it works fine, but I can't normally boot my phone it just boot loops once and again, I just can go into recovery mode, that's it.
Last time I flashed cwm it happened the same, but I can't remember what I did
Help please
Alepvn said:
This always happens to me, I installed cwm and it works fine, but I can't normally boot my phone it just boot loops once and again, I just can go into recovery mode, that's it.
Last time I flashed cwm it happened the same, but I can't remember what I did
Help please
Click to expand...
Click to collapse
Was there a kernel included with the CWM files?
If on a stock Sony ROM re-flash a stock ROMs kernel via flashtool
If your using a non Sony ROM try flashing a kernel that matches the ROM you're using
I rooted my xperia z1 yesterday and installed a cm11 custom rom and everything worked like a charm but then i installled doomkernel v22 through recovery mode zip file installer of my phone, and when i rebooted my phone it left it in a boot loop. I have tried pretty much every thing but can't get it out of boot loop.
i don't have usb debugging turned on, so when i try to flash a stock firmware from flash tool it doesn't goes through!
urgent help required on this!
thanks in advance.
Harry.Singh said:
I rooted my xperia z1 yesterday and installed a cm11 custom rom and everything worked like a charm but then i installled doomkernel v22 through recovery mode zip file installer of my phone, and when i rebooted my phone it left it in a boot loop. I have tried pretty much every thing but can't get it out of boot loop.
i don't have usb debugging turned on, so when i try to flash a stock firmware from flash tool it doesn't goes through!
urgent help required on this!
thanks in advance.
Click to expand...
Click to collapse
Thats because doomkernel is only for stock Sony based roms,it wont work for cm/aosp based roms!!!
Since doomkernel is already installed, you should be able to access the recovery like normal.just get into the recovery and flash the cyanogenmod zip again.that zip will flash the cm kernel back on your device and everything will work fine
Hello everyone,
I'd appreciate some help here.
I've been using my xperia tx on 4.3 JB for quite a while now but it consumed my battery like hell. So I flashed it back to 4.1.2 JB stock fw.
Now here's the problem, as i'd like to flash to carbon rom and to do so I need to boot into cwm recovery. I've downloaded CWM 9i_JB by davidmarco or something like that and it installed successfully. My phone is rooted and it has unlocked bootloader. I tried several times to boot into cwm with restarting my phone then when Sony logo appears I was consistently pressing volume down button and nothing happened, my phone booted normally. I've also downloaded Rom Manager to try and boot into cwm but that didn't work also. I don't really know where the problem is and i'd appreciate some help.
Thanks in advance,
Sandi
edit:
I've flashed another kernel with cwm integrated in it so everything works fine now.