Develop Bugs

[Q] Reflash problem after flashing Cyanogen

Hi all !
Yesterday I wanted to try Cyanogen on my Desire, an I did so with a nightly build.
I just wanted to test it : I'm actually so much Sense-addicted ^^"
But, when I tried to flash my regular RCMixS v06, it didn't work, I was stuck on HTC Logo. Then, I tried to flash Modaco's update.zip file wich I used to root my phone, but, again, it didn't work. Now I'm stuck with a "onlyCM" Desire, which is pretty inconvenient :s
I'm asking you this question : what can I do?

alex83fr said:
Hi all !
Yesterday I wanted to try Cyanogen on my Desire, an I did so with a nightly build.
I just wanted to test it : I'm actually so much Sense-addicted ^^"
But, when I tried to flash my regular RCMixS v06, it didn't work, I was stuck on HTC Logo. Then, I tried to flash Modaco's update.zip file wich I used to root my phone, but, again, it didn't work. Now I'm stuck with a "onlyCM" Desire, which is pretty inconvenient :s
I'm asking you this question : what can I do?
Click to expand...
Click to collapse
Hi,
Did you check to make sure you had a compatible radio version?
Also, I would suggest clear Dalvik Cache and Wipe.
let me know how it goes

Do a full wipe:
Go into recovery - mounts and storage - format boot - format system - format data - format cache - then format sd-ext if you have it then exit that menu and goto advance and do a wipe on Dalvik cache
this is old style full wipe, works for me every time.
Hope you come right.
EDIT: After full wipe install ROm of choice..

Thanks Grobiedeb, it has worked

stuck at google for 2nd time niw!

Hello, this issue has happened to me before , I was on a 4.2.2 ROM , I flashed unofficial cm10.2 4.3 rom by carlos, the ROM was acting buggy, so I rebooted, and then I'm stucked at Google , rebooted into recovery , wiped everything , flashed another ROM , still stuck at Google, I had to wip everything including my SD data ;( , flashed Google factory image , rebooted fine, my question is , why I cannot roll back or install another ROM after flashing a 4.3 ROM? I always has to wipe all my data , I thought twrp was the problem, but this time I was using cwm, I'm so confused right now , I'm scared if I flashed a 4.2.2 ROM , then come back to 4.3 I will get stucked at Google again! What could be the solution to problem?

razi914 said:
Hello, this issue has happened to me before , I was on a 4.2.2 ROM , I flashed unofficial cm10.2 4.3 rom by carlos, the ROM was acting buggy, so I rebooted, and then I'm stucked at Google , rebooted into recovery , wiped everything , flashed another ROM , still stuck at Google, I had to wip everything including my SD data ;( , flashed Google factory image , rebooted fine, my question is , why I cannot roll back or install another ROM after flashing a 4.3 ROM? I always has to wipe all my data , I thought twrp was the problem, but this time I was using cwm, I'm so confused right now , I'm scared if I flashed a 4.2.2 ROM , then come back to 4.3 I will get stucked at Google again! What could be the solution to problem?
Click to expand...
Click to collapse
Ok... so you wrote to my ROM thread about it and I try to help you!
1. Use CWM, I ahve no experience of TWRP and I can't help Nexus users who uses TWRP
2. Flash factory images by wiping everything
3. If you flash a ROM then in CWM wipe data factory reset <-- it keeps files in the internal storage
4. Then flash a ROM
5. If it happens again them maybe something is broken on your Nexus, then I recommend the phone service...
Sorry I'm busy ad I read that quick if I missed some lines or didn't understand something, then I apologize

Carlos_Manuel said:
Ok... so you wrote to my ROM thread about it and I try to help you!
1. Use CWM, I ahve no experience of TWRP and I can't help Nexus users who uses TWRP
2. Flash factory images by wiping everything
3. If you flash a ROM then in CWM wipe data factory reset <-- it keeps files in the internal storage
4. Then flash a ROM
5. If it happens again them maybe something is broken on your Nexus, then I recommend the phone service...
Sorry I'm busy ad I read that quick if I missed some lines or didn't understand something, then I apologize
Click to expand...
Click to collapse
You better get some rest bro, u didn't read anything,! This issue also happened to you also, you said a 10-15 pages back that ur stuck on google too after rebooting, ! P.s i will install dreams 4.1.x , and wait for a 110% stable cm10.2 by you!

if you're reverting back from 4.3 to 4.2, you should do the Factory/Data Reset and you should boot into OS just fine, i had that problem too and that is how i sorted it out.

lastforone said:
if you're reverting back from 4.3 to 4.2, you should do the Factory/Data Reset and you should boot into OS just fine, i had that problem too and that is how i sorted it out.
Click to expand...
Click to collapse
no didnt worked for me,, had to flash factrory image

[Q] No Audio at All on Custom KitKat ROMs, Ideas?

I have now tried both CM11 and Slimkat 4.4, both ROMs, after flashing leave the device with no audio output at all. No ringtone, music, headphone output, call audio, nothing. Device is ATT S3 i747. Flashed back to stock JB 4.3 and audio issue is fixed every time. I really would like to run a custom ROM on my phone, but this issue makes it impossible. Does anyone know what could be causing the issue. Does it sound like a kernel or bootloader issue?

Try this:
1) wipe cache, Dalvik, data, and system before installing the ROM;
2) install ROM and, before rebooting, wipe cache and Dalvik again;
3) boot into the rom.

audit13 said:
Try this:
1) wipe cache, Dalvik, data, and system before installing the ROM;
2) install ROM and, before rebooting, wipe cache and Dalvik again;
3) boot into the rom.
Click to expand...
Click to collapse
Definitely followed that process to a T just now. Still no audio on anything. grrr.

MeatyFingers said:
Definitely followed that process to a T just now. Still no audio on anything. grrr.
Click to expand...
Click to collapse
Just to be certain, what is your recovery. I would recommend twrp 2.7.0.0. Maybe you have an old recovery that's messing with flashing ROMs. Idk just a guess.

UnXKnown0 said:
Just to be certain, what is your recovery. I would recommend twrp 2.7.0.0. Maybe you have an old recovery that's messing with flashing ROMs. Idk just a guess.
Click to expand...
Click to collapse
I am running Clockworkmod 6.0.4.7 touch version which I found on the clockworkmod website under ATT s3

MeatyFingers said:
I am running Clockworkmod 6.0.4.7 touch version which I found on the clockworkmod website under ATT s3
Click to expand...
Click to collapse
Try flashing Validus 13's ROM. I have that on my s3 and it works fine.

try this out !!
Personally i find philz touch recovry the best when it comes to flashing kitkar roms.. It might be wierd but basically i flashed the recovery from 'smart phone revolution-aroma bloat installer'
http://forum.xda-developers.com/galaxy-s3/development/rom-smart-phone-revolution-rom-v7-0-t2541054
I then use the option of "yes I'm flashing a new rom" in factory reset..
Try it out !!
Hope it helps..

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

[Q] [need help] every ROM get's stuck on boot animation

I tried:
different recoveries ( 2 versions of TWRP and 1 other ) , flashing different kernels, wiping cache/dalvik cache/factory reset like 100 times, 3 ROMS that used to work in the past
I didn't try flashing a rom with adb because I can't get it to work, but I don't know if it would help.
The only thing that works is stock ROM with stock kernel and stock recovery. ( ROM from EN MIUI forum )
Everything else just gets stuck on the boot animation ( the cyanogenmod/mokee/... logo )
btw: already tried googling, but all I found is how to fix the problem by installing stock everything but the problem is I hate the stock rom/recovery and If I flash a custom recovery and ROM after fixing it, it just gets stuck again.
Thanks in advance

As you already tried TWRP and not working, here is something u can try...
1)Flash Original miui for redmi 1s
2)then flash philz touch through stock recovery
3)then try to install CM 11 or other ROM
Not sure if it will work for you but you can try
BANG that THANKS button

lanadekat said:
I tried:
different recoveries ( 2 versions of TWRP and 1 other ) , flashing different kernels, wiping cache/dalvik cache/factory reset like 100 times, 3 ROMS that used to work in the past
I didn't try flashing a rom with adb because I can't get it to work, but I don't know if it would help.
The only thing that works is stock ROM with stock kernel and stock recovery. ( ROM from EN MIUI forum )
Everything else just gets stuck on the boot animation ( the cyanogenmod/mokee/... logo )
btw: already tried googling, but all I found is how to fix the problem by installing stock everything but the problem is I hate the stock rom/recovery and If I flash a custom recovery and ROM after fixing it, it just gets stuck again.
Thanks in advance
Click to expand...
Click to collapse
Had you tried to wipe cache, dalvik, data, and system before? I had my problem solved with custom rom
See here, focus what written at Edit section, ignore else. Just curios thou.. Need to be confirmed by others. Thanks

presetz said:
Had you tried to wipe cache, dalvik, data, and system before? I had my problem solved with custom rom
See here, focus what written at Edit section, ignore else. Just curios thou.. Need to be confirmed by others. Thanks
Click to expand...
Click to collapse
Could be the problem I asked the guy/girl who posted it how he fixed the problem. I'll also look for another non-CM based ROM and see if it works.

lanadekat said:
Could be the problem I asked the guy/girl who posted it how he fixed the problem. I'll also look for another non-CM based ROM and see if it works.
Click to expand...
Click to collapse
Just try what i said, wipe cache, dalvik, data, system,
As i recalled (i used twrp) reflash twrp. Leave it without OS
After reboot update twrp to 2.8.6.0 allow to install root, reboot.
And after you enter twrp recovery once again, do clean install as custom rom "how to install" instructed. Hope that help, might have to try other than cm, just for testing it.
Hit thanks if it work, else dont curse on me

presetz said:
Just try what i said, wipe cache, dalvik, data, system,
As i recalled (i used twrp) reflash twrp. Leave it without OS
After reboot update twrp to 2.8.6.0 allow to install root, reboot.
And after you enter twrp recovery once again, do clean install as custom rom "how to install" instructed. Hope that help, might have to try other than cm, just for testing it.
Hit thanks if it work, else dont curse on me
Click to expand...
Click to collapse
oh haha I didn't notice you were the same guyI thought you linked me to someone else's post xD I'll try it, I hope it works!
edit: thanks! reflashing the kernel, wiping everything, then fixing the permissions ( but not the SElinux permissions ) fixed the problem for me I'm back to android 12.1
I'll see if I can close the thread.