lineage-14.1-20170116-tilak-n7100.zip boot loop issue - Galaxy Note II Q&A, Help & Troubleshooting

I hope everyone is fine. I am facing an issue. I installed lineage-14.1-20170116-tilak-n7100.zip this rom in my samsung galaxy note 2 and it ran into boot loop....i wiped data, factory reset, cache etc and it worked fine...after sometime i restarted the phone again and it ran into boot loop again and i wiped everything again but this time it did not work and the boot loop is still there....... I used Phillz recovery for flashing.

Related

[Q] [HELP] Borked up phone!

Ouch. Been running various ROMs and various kernels. Had a ROM installed with imosyons exp2 kernel and touch recovery. Was trying out 1.42GHz. All of a sudden phone spontaneously rebooted. Hung repeatedly on Google screen. OK, no problem. Will wipe cache and dalvik cache and reinstall kernel. Hung on the dalvik cache wipe. OK, will skip the wipe and just load kernel. Opps, hung looking for .zip files. Opps, will reload recovery. Still hanging everywhere.
Used Galaxy Toolkit to reload stock images. It did do 1 bootloop, but then acted normally.
Reloaded everything. Left 1.42 alone! Worked all day and then I installed ROM Manager to make a nandroid backup. It wanted to install CWR so I let it. Upon a reboot it went into bootloops. Now I cannot do a factory restore (all my data is there upon a reboot). Tried the ODIN solution but it's still not clearing data. Apparently no PIT available to reparition? Shoot, what do I do!

PROBLEM: can't get past boot animation with ANY rom

I flashed the latest Axiom and everything was fine. Did a reboot and it just sat on the boot animation for a while. Like, 15 minutes. So I did a battery pull and tried to boot again. No go. Pulled the battery and went into CWM, wiped data/cache/dalvik and formatted /system then re-flashed the ROM. Stuck again. Went BACK into CWM, wiped/formatted, and installed Liquid (which worked before). STILL can't get past the boot animation. Tried to restore a Nandroid and got an error.
I'm in a bit of a panic mode here because I have no idea what to do.
Relax bootloops aint a major problem really, i suggest you go to cwm and wipe all, or try and testore a backup, if all else fails just go back to stock using a toolkit, re root and flash a rom
Sent from my Galaxy Nexus using xda premium
SomeGuyDude said:
I flashed the latest Axiom and everything was fine. Did a reboot and it just sat on the boot animation for a while. Like, 15 minutes. So I did a battery pull and tried to boot again. No go. Pulled the battery and went into CWM, wiped data/cache/dalvik and formatted /system then re-flashed the ROM. Stuck again. Went BACK into CWM, wiped/formatted, and installed Liquid (which worked before). STILL can't get past the boot animation. Tried to restore a Nandroid and got an error.
I'm in a bit of a panic mode here because I have no idea what to do.
Click to expand...
Click to collapse
Do this.

[Q] Stuck in recovery mode bootloop!

Hello everyone,
This is what is happening to me. I was trying to flash Miroslav's Cyanogenmod 11 RC2 with Philz Touch 6.07.9, but none of the recomended methods worked for me, I just got stuck on lg logo bootloop - I really want this rom but it is hard as f**k to flash -. So I tried to go back to CM 10.2.1 and got the "Status 7" error. Very frustrated, I finally used my stock recovery image and it worked fine.
From this point, i was recovering my apps and data using titanium back up and when it finished, a notification asked if I wanted the official system update. I refused it and proceded to reboot. Now the phone boots instantly to recovery mode and show the purple screen of Philz touch. First I wiped cache and dalvik and got the same bootloop. Then I wiped cache, dalvik and factory reset and got the same bootloop. Finally, I formated system, factory reset, wiped cache, wiped dalvik and flashed again my recovery image, and got again the recovery mode bootloop.
Any Ideas? Thank you for your help.
Best regards.
EDIT: I must clarify that when I flash my recovery image, it ALWAYS get suck on a part that says something like "installing android security". I have to press power button 10 seconds to restart but it boots normaly in the stock rom.
chortiman said:
Hello everyone,
This is what is happening to me. I was trying to flash Miroslav's Cyanogenmod 11 RC2 with Philz Touch 6.07.9, but none of the recomended methods worked for me, I just got stuck on lg logo bootloop - I really want this rom but it is hard as f**k to flash -. So I tried to go back to CM 10.2.1 and got the "Status 7" error. Very frustrated, I finally used my stock recovery image and it worked fine.
From this point, i was recovering my apps and data using titanium back up and when it finished, a notification asked if I wanted the official system update. I refused it and proceded to reboot. Now the phone boots instantly to recovery mode and show the purple screen of Philz touch. First I wiped cache and dalvik and got the same bootloop. Then I wiped cache, dalvik and factory reset and got the same bootloop. Finally, I formated system, factory reset, wiped cache, wiped dalvik and flashed again my recovery image, and got again the recovery mode bootloop.
Any Ideas? Thank you for your help.
Best regards.
EDIT: I must clarify that when I flash my recovery image, it ALWAYS get suck on a part that says something like "installing android security". I have to press power button 10 seconds to restart but it boots normaly in the stock rom.
Click to expand...
Click to collapse
When in vain , unbrick your phone again using unbricking guide and use CWM , not all guide is working for the same type of phone . No need to wipe system clean cache watevr **** you were told unless recommended by developer and just factory reset then flash the rom
Mr.201 said:
When in vain , unbrick your phone again using unbricking guide and use CWM , not all guide is working for the same type of phone . No need to wipe system clean cache watevr **** you were told unless recommended by developer and just factory reset then flash the rom
Click to expand...
Click to collapse
Thanks for the answer and the advice about factory reset. Yes, I had to unbrick my phone and by the way, still could not install miroslav's cm11 RC3 using Philz touch 6.19.3.
But I have another issue: I successfully got back to CM 10.2.1 but after I restored my apps using Titanium Backup, I rebooted the phone and got stuck on CM logo for half hour. I wiped dalvik and got the same result. Then wiped cache and dalvik and still stuck. What should I do? Flash again the rom? The restored data is from CM 10.2.1 so I don't see any problem....
chortiman said:
Thanks for the answer and the advice about factory reset. Yes, I had to unbrick my phone and by the way, still could not install miroslav's cm11 RC3 using Philz touch 6.19.3.
But I have another issue: I successfully got back to CM 10.2.1 but after I restored my apps using Titanium Backup, I rebooted the phone and got stuck on CM logo for half hour. I wiped dalvik and got the same result. Then wiped cache and dalvik and still stuck. What should I do? Flash again the rom? The restored data is from CM 10.2.1 so I don't see any problem....
Click to expand...
Click to collapse
check again what you restore, user apps will have no problem to restore but system apps will cause incompatibility to the rom and crash it
Mr.201 said:
check again what you restore, user apps will have no problem to restore but system apps will cause incompatibility to the rom and crash it
Click to expand...
Click to collapse
The phone is good now, I restored the stock rom and from there I flashed CM 10.2.1 just making a factory reset. Plus I flashed adreno drivers and gapps. Once it booted, I restored my apps without sistem data and now the phone works properly.
Thank you Mr.201
chortiman said:
The phone is good now, I restored the stock rom and from there I flashed CM 10.2.1 just making a factory reset. Plus I flashed adreno drivers and gapps. Once it booted, I restored my apps without sistem data and now the phone works properly.
Thank you Mr.201
Click to expand...
Click to collapse
Glad it worked, make sure you untick 'system' in filter in titanium backup so that you can only see your user apps .

Note 4 stuck at AT&T logo after factory reset

Every few months I usually wipe my phone to give it that fresh running feeling. I wiped my AT&T note 4 from recovery and wiped cache today and the phone boots and gets stuck at the AT&T logo. I thought it was strange and so I booted into recovery again and again tried to factory reset and wipe cache.
If it matters my phone is currently on version U2EPK1 and I've never encountered anything like this before on this phone.
Any tips for progression?
HobsonA said:
Every few months I usually wipe my phone to give it that fresh running feeling. I wiped my AT&T note 4 from recovery and wiped cache today and the phone boots and gets stuck at the AT&T logo. I thought it was strange and so I booted into recovery again and again tried to factory reset and wipe cache.
If it matters my phone is currently on version U2EPK1 and I've never encountered anything like this before on this phone.
Any tips for progression?
Click to expand...
Click to collapse
Try installing a firmware via odin

Stuck on boot animation, wipe succesfull but nothing is wiped

Hey guys,
Okay so long story short, i went through a lot of reinstalling magisk modules and battery twrp mods, one time the reboot took longer than usual, so i wiped caches and rebooted and its fixed. Later on, i decided to uninstall a magisk module, so i rebooted, and now im stuck.
Thats not the problem tho, the huge problem is that twrp is failing to wipe partitions, it says that partitions are successfully wiped, but theyre not. Because of this issue i cant reflash my rom and fix the problem.
I tried rebooting from twrp and it booted, but then it immediately reboots again and its back to bootlooping.
I tried changing to a different twrp, the twrp install is successfull, but still not able to wipe partitions.
I alr tried reflashing my rom, but no luck, i need to wipe my partitions but my phone just cant do it,
Pls help
Update
Now it says error creating f stab everytime i wipe or install roms

Categories

Resources