Develop Bugs

[HOWTO]Endless Bootloop FIX (no wipe)

Hi I got a solution to endless bootloops (at least working for me ) every time I flash new ROM I got stuck with bootloops so I experimented little bit and this solution seems to be working ...
I am using CM10 with Semaphore JB
You will need fixrecovery.tar and Odin (I used v1.83) you can download them in attachments.
For those who don't have flashable kernel on Internal SDCard can skip step 5 and second half of step 3.
1. So first of all you have to remove SIM and SDCard.
2. Flash fixrecovery.tar with Odin and uncheck Auto Reboot
3. Get into recovery and wipe only cache and flash kernel you want
4. Flash normal kernel with Odin and again uncheck Auto Reboot
5. Get into recovery and again flash kernel of your choice
6. Now you should be ready to switch your phone on
Maybe this excessive flashing of kernel is not necessary but I did it this way

Did you make this fix by yourself? There is already a fix for bootloop from stratosk!

Yes I did... can you post stratosk's fix please ?

Syntaxer said:
Yes I did... can you post stratosk's fix please ?
Click to expand...
Click to collapse
sorry, my mistake, it's probably made by someone else. Search the thread.
Anyway, thanks for the fix...

No problem I hope someone will find this fix useful

Syntaxer said:
Yes I did... can you post stratosk's fix please ?
Click to expand...
Click to collapse
sure you did ... [Q] Cannot boot or enter recovery (CM9 20120425)

Didn't see that post earlier, but it's not working for me anyway ... I had to clear cache additionally

Thats big development time... Clear cache ftw!
Sent from my XT910 using xda premium

Hello there,
Thanks for the guide. This hasn't worked for me?
I was upgrading versions of aways ROM (from ICS to Jellybean) and once I had flashed the ROM and GAPPS the phone rebooted. The link for the GAPPS was broken on the ROM website but it found me a replacement that I used. The phone does boot but FC on setup and no longer boots into recovery and is stuck in bootloop.
I thought this would fix the issue as I could still enter download mode but I still have the same problem? Phone won't boot into recovery and just loops...
Any thoughts?
Thanks in advance : )

I have a device that is experiencing bootloop just stop at the logo, I think this is the kind of Mtk, rooted, Kitkat. I do not know exactly what causes it bootloop, Before bootloop I edit files and install Tweaks build.prop through the application My pimp and when I restart the device bootloop ensued, do you think this is file damage build.prop or else. So that my device bootloop

[Q] Build.prop file always revert back to older version after reboot

Hi everyone,
I'm using rooted One M8 official Android 5. I changed build.prop file with root explorer as r/w mode successfully but when I reboot my phone then when I check the build.prop file, it is unchanged. Build.prop file always back to older version after the reboot. How can I solve this issue?
Also I tried several times with ES file manager, root browser, buildprop editor but it always revert back to older version after the reboot. I want to change " ro.ril.enable.r8fd=0 ro.ril.enable.pre_r8fd=0" for breaking of data connection.
Like this post; http://forum.xda-developers.com/showpost.php?p=56243481&postcount=7
Thanks a lot.

You can't because the stock kernel has write protection enabled. You need a custom kernel with write protection disabled like ElementalX.. check the original Android development section.
If you want to keep your stock kernel, what you can do :
Make a nandroid backup of your current ROM with your custom recovery
Install custom kernel
Reboot, make changes to build.prop
Reboot and see whether the modified build.prop still there
Reboot to recovery, restore boot only
Done.

ckpv5 said:
You can't because the stock kernel has write protection enabled. You need a custom kernel with write protection disabled like ElementalX.. check the original Android development section.
If you want to keep your stock kernel, what you can do :
Make a nandroid backup of your current ROM with your custom recovery
Install custom kernel
Reboot, make changes to build.prop
Reboot and see whether the modified build.prop still there
Reboot to recovery, restore boot only
Done.
Click to expand...
Click to collapse
Thank you so much. But I don't know how to install custom kernel. Also my device is s-off.

Have you ever install a custom ROM before ? It's the same, put the kernel zip on your sdcard. Reboot to recovery, select install - select kernel zip and install
Even your device is S-Off, you still need insecure kernel to do that modification

ckpv5 said:
You can't because the stock kernel has write protection enabled. You need a custom kernel with write protection disabled like ElementalX.. check the original Android development section.
If you want to keep your stock kernel, what you can do :
Make a nandroid backup of your current ROM with your custom recovery
Install custom kernel
Reboot, make changes to build.prop
Reboot and see whether the modified build.prop still there
Reboot to recovery, restore boot only
Done.
Click to expand...
Click to collapse
ckpv5 said:
Have you ever install a custom ROM before ? It's the same, put the kernel zip on your sdcard. Reboot to recovery, select install - select kernel zip and install
Even your device is S-Off, you still need insecure kernel to do that modification
Click to expand...
Click to collapse
Yes I installed once before. But I didn't find custom kernel for my device. If I install any custom rom, is the problem solved without the need custom kernel or etc ?

No idea about custom ROM, don't really use one. But I believe all have them have the write protection disabled, so you can do the modification.
Already mentioned you can install ElementalX kernel ? Try that first - http://forum.xda-developers.com/showthread.php?t=2705613
Choose ElementalX-m8-4.03-Sense if you're on Sense (I believe so)

ckpv5 said:
No idea about custom ROM, don't really use one. But I believe all have them have the write protection disabled, so you can do the modification.
Already mentioned you can install ElementalX kernel ? Try that first - http://forum.xda-developers.com/showthread.php?t=2705613
Choose ElementalX-m8-4.03-Sense if you're on Sense (I believe so)
Click to expand...
Click to collapse
@ckpv5 my friend,
I can't thank you enough. That worked like a magic. I really appreciate you taking the time for this issue.
Thanks a lot.

DISCUSSION: YU Yureka CM 12(S) Lollipop Update

Current firmware: Android 5.0.2, Build LRX22G, Cyanogen OS version 12.0-YNG1TAS0W0
OTA: http://builds.cyngn.com/cyanogen-os...deeca328/cm-12.0-YNG1TAS0W0-tomato-signed.zip
Fastboot flashable image: http://builds.cyngn.com/cyanogen-os...cm-12.0-YNG1TAS0W0-tomato-signed-fastboot.zip
Boot Debuggable image: http://builds.cyngn.com/cyanogen-os...cm-12.0-YNG1TAS0W0-tomato-boot-debuggable.img
Use OTA for manually update from any official KitKat build; don't use fastboot flashable images on existing devices with KitKat bootloader - it will brick the device!
How to unbrick: http://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040 (Credit goes to @tirta.agung)

OTA downloaded.... Now going with flashboot...

Need Some Help
Deleted

anyone flashed it yet???
Sent from my AO5510 using Tapatalk

Flashed it..initial boot will take a long time

blackyz said:
OTA downloaded.... Now going with flashboot...
Click to expand...
Click to collapse
I tried fastboot method now my phone is not booting

anyone done it successfully? my DL is halfway so I need procedural help.

Phone not booting
sharan.nyn said:
I tried fastboot method now my phone is not booting
Click to expand...
Click to collapse
I flashed with fastboot process successful but my phone not booting, nothing happening. i don't know what to do now no logo just dead.

I flashed it with TWRP.
Awsm CM12S.
Super smooth !

mralam92 said:
I flashed with fastboot process successful but my phone not booting, nothing happening. i don't know what to do now no logo just dead.
Click to expand...
Click to collapse
Same here bro!
now following this
http://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040

sharan.nyn said:
Same here bro!
now following this
http://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040
Click to expand...
Click to collapse
service centre help or not?

Posted cm12
Just installed the zip version of cm12 on yu. Could not wait for the official ota update. Updated zip using cwm recovery which I had installed while the phone was running on the cm11 kitkat 4.4.4 version.
I understand that since this is just a system update there is no need to change or revert back to the original recovery.
(just a doubt- is it necessary to revert back to original 4.4.4 system stock recovery in case we get the OTA or the OTA will take care of any Custom recovery and will install iteslf?)
Initial boot will take a long time due to the Android Runtime (ART) virtual machine which is the improvisation over the Dalvik Cache. So please be patient for all the 122 apps to get registered in by ART. I had tried the ART while on cm11 4.4.4 (despite of system warning that it might lead to crashes etc... ), even then it took a very long time......
Working absolutely fine. Initial experience is awesome. Will be observing it now for some time. Most other features are similar to the cm11. no more 3g detection errors. Got to explore more....
My first posting in XDA.
I owe a lot to this community from which I have taken a lot. I hope I will be able to give back even little that I have got to help others. :good::good:
By zip version i mean the version that can be installed using the phone recovery with out the need of a computer to push the system (i.e. the flashable version). I am not aware what the debuggable version means.

mralam92 said:
service centre help or not?
Click to expand...
Click to collapse
Service center said they will pickup the device in 7-8 days

please tell me difference between OTA,Fastboot flashable image and Boot Debuggable image.And which one should I download to install.?

Titokhan said:
OTA: http://builds.cyngn.com/cyanogen-os...deeca328/cm-12.0-YNG1TAS0W0-tomato-signed.zip
Fastboot flashable image: http://builds.cyngn.com/cyanogen-os...cm-12.0-YNG1TAS0W0-tomato-signed-fastboot.zip
Boot Debuggable image: http://builds.cyngn.com/cyanogen-os...cm-12.0-YNG1TAS0W0-tomato-boot-debuggable.img
Click to expand...
Click to collapse
Is the Android version 5.0.x or 5.1?
Has anyone encountered any bugs at all?
To flash through recovery, do I need the OTA version?

CM 12 update
guys plzzz help me as lollipop is out for yu...can i install ?? i have rooted my yu but i m still on stock rom i.e cm 11 and i have cwm ,can i flash the cm12 zip file using cwm ..

dont flash thru fastboot all who flashed it thru are having hard bricked devices

weshall said:
guys plzzz help me as lollipop is out for yu...can i install ?? i have rooted my yu but i m still on stock rom i.e cm 11 and i have cwm ,can i flash the cm12 zip file using cwm ..
Click to expand...
Click to collapse
YES YOU CAN JUST FOLLOW THIS STEPS
1. Download official CM12s Ota(1st zip in the link).
2. Place the downloaded zip file in the ‘download’ folder on phone’s internal storage.
3. Boot Yureka into Stock Cyanogen recovery - To do so, power off the phone. Then press Volume Up + Volume Down and Power button simultaneously,Onec you boot into recovery do data/ factory reset.
4. Select ‘Apply Update’ > ‘choose from internal storage’ > /0 > Download > and select “cm-12.0-YNG1TAS0W0-tomato-signed.zip” file. The ROM will be flashed and you should be seeing the Android Bot
5. Once installation is over, go to main page and ‘wipe cache partition’
6. Then select Reboot system now
That’s it! Wait for a while as the device boots for the first time with all new and fresh Cyanogen OS 12.
IF you dont get anyhting just revert me back ,or pm will help you.:laugh:

Titokhan said:
Current firmware: Android 5.0.2, Build LRX22G, Cyanogen OS version 12.0-YNG1TAS0W0
OTA: http://builds.cyngn.com/cyanogen-os...deeca328/cm-12.0-YNG1TAS0W0-tomato-signed.zip
Fastboot flashable image: http://builds.cyngn.com/cyanogen-os...cm-12.0-YNG1TAS0W0-tomato-signed-fastboot.zip
Boot Debuggable image: http://builds.cyngn.com/cyanogen-os...cm-12.0-YNG1TAS0W0-tomato-boot-debuggable.img
Use OTA for manually update from any KitKat build; don't use fastboot flashable images on existing devices with KitKat bootloader - it'll brick the device!
Click to expand...
Click to collapse
It just got updated if you flash it on kitkat bootloader, the device will get bricked
Many users have got their device bricked, the warning was too late I flashed it today at 1:50 AM

weshall said:
guys plzzz help me as lollipop is out for yu...can i install ?? i have rooted my yu but i m still on stock rom i.e cm 11 and i have cwm ,can i flash the cm12 zip file using cwm ..
Click to expand...
Click to collapse
Hi, You can very well install the .....signed.zip using the CWM recovery as I did.
1. Install the .....signed.zip file and not the ....flashable.zip or the ....bootable.zip files. Only the .....SIGNED.ZIP file either on your phone memory or sdcard
2. Reboot into the recovery mode either by using the advanced reboot option or by pressing the volumeup+down button and power buttons simultaneously and releasing them once you see the Yu logo and phone vibrates.
2. Use the Factory reset command first and then wipe the Cache
3. Navigate to the Install zip and chose the .....SIGNED.zip from either your phone memory or the SD Card as CWM has the option to chose the zip file. and swipe to install it.
4. After successful installation navigate to reboot and swipe to allow the system to restart.
5. Intial boot takes a very long time saying Android is updating. This is because Lollipop uses Android Runtime (ART) by default and not Dalvik Cache as a virtual machine for all apps. So please be patient till all the 122 or so apks are updated by ART. Takes around 10-15minutes.
6. The usual fist time boot stuff.... and then...
7. Enjoy. CM12 it is sweet.
---------- Post added at 09:58 AM ---------- Previous post was at 09:43 AM ----------
id74em8 said:
Is the Android version 5.0.x or 5.1?
Has anyone encountered any bugs at all?
To flash through recovery, do I need the OTA version?
Click to expand...
Click to collapse
It is android version 5.0.2
To flash through recovery (either CWM or TWRP) use the .....SIGNED.ZIP i.e. the first file in the list and NOT the .flashable.zip or the last one. Only the first one.
I installed the zip through CWM
The only bug I noticed was when you add the Powersaver option tile in the Notification drawer, when in the power saving mode, a notification showing the power save mode got invoked. When I used the same option after rebooting I am not getting it now..
Also all of a sudden a red boundary started to appear at the edges of the screen. So I though I had opted for the screen refresh notification in the Developer options but I had not. Still i could see the red rectangle when the screen refreshed. I had to reboot the system. Now fine.

Purenexus ROM custom boot theme?

I'm trying to replace my boot animation using purenexus rom on 7.1.2 (april patch) with elemental x kernel rooted with magisk 12.0. I went into recovery and tried to flash this https://drive.google.com/file/d/0B-NX_VbtkT7POWROVVA1X2Fjbms/view but it didn't replace the boot animation. I tried to manually replace it and it wouldn't let me do this either. Help is appreciated

tryfont said:
I'm trying to replace my boot animation using purenexus rom on 7.1.2 (april patch) with elemental x kernel rooted with magisk 12.0. I went into recovery and tried to flash this https://drive.google.com/file/d/0B-NX_VbtkT7POWROVVA1X2Fjbms/view but it didn't replace the boot animation. I tried to manually replace it and it wouldn't let me do this either. Help is appreciated
Click to expand...
Click to collapse
Just so I'm clear as to what you've already tried, you flashed the aforementioned zip using twrp and it didn't replace it and you tried using a root browser to replace the file and fixed permissions?

tryfont said:
I'm trying to replace my boot animation using purenexus rom on 7.1.2 (april patch) with elemental x kernel rooted with magisk 12.0. I went into recovery and tried to flash this https://drive.google.com/file/d/0B-NX_VbtkT7POWROVVA1X2Fjbms/view but it didn't replace the boot animation. I tried to manually replace it and it wouldn't let me do this either. Help is appreciated
Click to expand...
Click to collapse
That's because magisk doesn't mount system properly. You have to use a specific file browser with magisk. I'm not sure which one it is as I don't use magisk. But I saw someone mention an issue like this in anther thread.

toknitup420 said:
That's because magisk doesn't mount system properly. You have to use a specific file browser with magisk. I'm not sure which one it is as I don't use magisk. But I saw someone mention an issue like this in anther thread.
Click to expand...
Click to collapse
It's root explorer and FX file manager, both.

Device turns off randomly after root

Hi guys, I rooted my redmi note 8 yesterday. Everything went well except two things: on boot the error message said that "there is an internal problem" and the phone reboots/shuts down itself.
Any thoughts?

cicish said:
Hi guys, I rooted my redmi note 8 yesterday. Everything went well except two things: on boot the error message said that "there is an internal problem" and the phone reboots/shuts down itself.
Any thoughts?
Click to expand...
Click to collapse
You should explain the problem obviously if you want a help, if your phone still working you should flash twerp.img to be able to root it and solve any existing problem by flashing new rom

niceman2007 said:
You should explain the problem obviously if you want a help, if your phone still working you should flash twerp.img to be able to root it and solve any existing problem by flashing new rom
Click to expand...
Click to collapse
Hey thanks for answer.
Actually i did everything correctly, flashed latest twrp, tried several roms, oficial, unoficial etc., But still no result. After all these, ive flashed the stock rom which solved the problem but phone is no more rooted. So..

cicish said:
Hey thanks for answer.
Actually i did everything correctly, flashed latest twrp, tried several roms, oficial, unoficial etc., But still no result. After all these, ive flashed the stock rom which solved the problem but phone is no more rooted. So..
Click to expand...
Click to collapse
If you still want to root it again,after flasing new rom go to twero and then go to wipe then format,you should format your phone after rom flashing,try this and inform me

Yes yes! I want to root phone once again. So the steps are these:
1) booting into twrp with adb from pc.
2) from the twrp menu wiping and formating the data
3) instaling new rom
Is this true?
Thanks!

If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.

Leeban Joseph said:
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Click to expand...
Click to collapse
You mean that its possible to have root access on stock rom?

Leeban Joseph said:
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Click to expand...
Click to collapse
Hey, I was able to flash magical using twrp but can't flash dm-verity. It gives me some error 1 with no description. I could flash magisk. What can the problem be? Thanks!

cicish said:
Hey, I was able to flash magical using twrp but can't flash dm-verity. It gives me some error 1 with no description. I could flash magisk. What can the problem be? Thanks!
Click to expand...
Click to collapse
From your stock rom extract the boot.img and place it on your SD card. Flash the boot image using twrp or you can also flash in fastboot, then reboot. Now boot to twrp recovery and flash dm-verity first and then magisk zip. Worked for me I'm having root permission with stock rom.

Leeban Joseph said:
From your stock rom extract the boot.img and place it on your SD card. Flash the boot image using twrp or you can also flash in fastboot, then reboot. Now boot to twrp recovery and flash dm-verity first and then magisk zip. Worked for me I'm having root permission with stock rom.
Click to expand...
Click to collapse
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange

cicish said:
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
Click to expand...
Click to collapse
UPDATE: after another custom rom install failure, i got back to stock miui 11 with miflash tool. the problem is now that when i unlock the bootloader and try to flash magisk and disable-dm-verity, the system refuses to boot. the redmi note 8 logo is sticked on boot. i dont understand what i am doing incorrectly. if there are any suggestions im ready to try.

cicish said:
UPDATE: after another custom rom install failure, i got back to stock miui 11 with miflash tool. the problem is now that when i unlock the bootloader and try to flash magisk and disable-dm-verity, the system refuses to boot. the redmi note 8 logo is sticked on boot. i dont understand what i am doing incorrectly. if there are any suggestions im ready to try.
Click to expand...
Click to collapse
Is your bootloader unlocked right now or did you lock it while flashing using miflash tool.

Leeban Joseph said:
Is your bootloader unlocked right now or did you lock it while flashing using miflash tool.
Click to expand...
Click to collapse
the bootloader was unlocked. everything went kinda fine, until i flashed youtube vanced from magisk: when i did that, the system was unable to boot. i don't know what's happening. is there anything to do with kernel or something? really interesting what i am doing wrong.

cicish said:
the bootloader was unlocked. everything went kinda fine, until i flashed youtube vanced from magisk: when i did that, the system was unable to boot. i don't know what's happening. is there anything to do with kernel or something? really interesting what i am doing wrong.
Click to expand...
Click to collapse
I think it may be because of YouTube vanced module. If you remove the module you might be able to boot. In twrp in the advanced option select file manager and then select data/adb/magisk/ in that you will find the list of installed modules, select the one which is causing the problem and delete that folder and try to reboot.

Leeban Joseph said:
I think it may be because of YouTube vanced module. If you remove the module you might be able to boot. In twrp in the advanced option select file manager and then select data/adb/magisk/ in that you will find the list of installed modules, select the one which is causing the problem and delete that folder and try to reboot.
Click to expand...
Click to collapse
I've already flashed the stock rom but this will help me next time! Thanks!
I'll stop trying for some days cause I'm really tired with tweaking so thanks and will get back!

cicish said:
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
Click to expand...
Click to collapse
Your device reboots randomly on custom rom because probably it was made for tianma display and you have hauxing display

the_weird_aquarian said:
Your device reboots randomly on custom rom because probably it was made for tianma display and you have hauxing display
Click to expand...
Click to collapse
Hey, thanks for the answer. i've just googled about it and you are right. checked the TP version and it says that i have huaxing display. in the Lineage OS thread the moderator wrote that the next update will fix that bug. hopefully ill be able to install custom rom. also if you know, are there any custom roms for huaxing display? thank you man!

cicish said:
Hey, thanks for the answer. i've just googled about it and you are right. checked the TP version and it says that i have huaxing display. in the Lineage OS thread the moderator wrote that the next update will fix that bug. hopefully ill be able to install custom rom. also if you know, are there any custom roms for huaxing display? thank you man!
Click to expand...
Click to collapse
currently bootleggers rom,PE official and unofficial and drepfest all have reboot issues in huaxing display. Haven't tried any other rom yet..still on MIUI..waiting to get the issue fixed asap.

the_weird_aquarian said:
currently bootleggers rom,PE official and unofficial and drepfest all have reboot issues in huaxing display. Haven't tried any other rom yet..still on MIUI..waiting to get the issue fixed asap.
Click to expand...
Click to collapse
i've tried Lineage OS too and it also has reboot issue. i've checked a thread here https://forum.xda-developers.com/redmi-note-5-pro/development/derp-kernel-clang-4-4-138-t3804996 that flashing a different kernel when you have flashed a custom rom can fix the problem. idk if its safe to do

cicish said:
i've tried Lineage OS too and it also has reboot issue. i've checked a thread here https://forum.xda-developers.com/redmi-note-5-pro/development/derp-kernel-clang-4-4-138-t3804996 that flashing a different kernel when you have flashed a custom rom can fix the problem. idk if its safe to do
Click to expand...
Click to collapse
that thread is for redmi note 5 pro..and flashing different kernel probably won't solve it because I know few guys flashed genom kernel but still ended up with reboot in huaxing display. Maybe waiting for fix is better.