I recntly bought 16GB UK version that came with 5.1 and OTA updated it to the most recent MM (sorry didin't note its exact number). I then succesfully flashed TWRP 3.0.2-r1 and tried to factory reset it but it gave me a lot of errors, so I restarted TWRP and tried again - successfuly. I then tried to flash GtrCrafts ROM (here) and it flashed succesfuly but stuck on boot animation for nearly half an hour so I rebooted back to TWRP and tried again - with the same effect. I then tried Marshmallux - and exactly the same problem happened. Today I flashed Resurrection Remix and everything was perfectly fine - happy that my phone "resurrected" I tried flashing stock based ROMs (same as before) and they kept stucking on boot animation again. After all I downloaded stock firmware (XT1562_LUX_RETEU_6.0_MPD24.65-18.1_cid7_subsidy-DEFAULT_CFC.xml) and flashed it with fastboot - the only problem was I couldn't flash bootloader.img, but just skipped that and flashed the rest - after the long few minutes my phone booted into system, so I thought it's finally OK, but no - I first checked if TWRP is still there but rebooting into recovery just left me with black screen so I flashed TWRP again (same version) and after this... I couldn't reboot into system (from TWRP menu) - it just kept rebooting TWRP on and on, so I turned my phone off, booted into bootloader and from bootloader - into system, with success. Trying to flash stock-based ROMs brought all the same problems back so I just gave up for now and wondering what could be wrong and is it fixable. Why would CM based RR flash and boot fine but not Marshmallux and GtfCraft's one? Anyone had the same issues or knows what's wrong? Could it be TWRP problem, phones problem, or a jinx?
Thanks.
Try flashing stock rom with rsdlite
Sent from my XT1562 using XDA-Developers mobile app
pijes said:
Try flashing stock rom with rsdlite
Sent from my XT1562 using XDA-Developers mobile app
Click to expand...
Click to collapse
I just realised OP messed instructions in this thread - http://forum.xda-developers.com/moto-x-play/general/guide-how-to-flash-factory-image-return-t3261486
I'll try again with proper ones...
OK, flashing stock firmware fixed all issues.
Hi guys,
some weeks ago I upgraded my recovery from 3.0.1 to last version (3.0.2-0).
I made the upgrade by the official App (downloaded from Play store). No problem at the first look. But some day ago I tried to made an upgrade to my custom rom AryaMod 8.1 to 8.3) and during the flash the device has been rebooted and the upgrade of the rom has failed. The device is ok and all functional. I have thought at an error. Not important in this case.
But to day I have made a good backup of all my data and (after a full wipe of Dalvik, Cache, Data and System) I re tried an change of custom rom with a new one Rom (DarkWolf_FW Galaxy S7 Edge Port][V2]) on my device.
The some result as the previous upgrade. The device has been rebooted after some second during the flash of the rom. At the device restart no OS or Data (locked on "Note 3" startup logo) but this is normal after a full wipe.
Furtunaly I restored my backup (made by recovery) and everything is back to normal situation before the wipe.
My question is... Some guy have found a similar problem with the new release of the recovery TWRP 3.0.2-0?
My device is a Samsung Galaxy Note 3 (Qualcom international)
I have had the same issue with some roms.
Touchwiz roms often fail to update and the recovery boots into recovery again.
No errors, just random reboot at initiating the installation.
CM13 and latest AOSP roms seem to flash without any issue.
Try going back to 2.8.7.X it will work.
Too bad you will loose the theme and glossiness of TWRP3
***
Also please backup your data on your computer if your partitions are f2fs while downgrading.
You cannot use twrp 3 for aroma zip.
Sent from my SM-N920C
I am Using Custom Roms From Last 5 Months. I ve installed cwm recovery in My yu yureka. Recently changed my Custom ROM To CR droid. It was Going smooth and neat. I Got bored of CR droid. Tried To change my ROM to miui Through cwm Got bootloop
Then I have restored my old CR droid ROM through cwm. And then I flashed Twrp 3.0 . and again I tried to flash miui ROM again got bootloop. And then again restored to CR droid which I have backed first. And then downloaded the Resuccurtion remix ROM and flashed through Twrp it booted up. And again I tried flashing miui Through Twrp. Phone started restarting again and again continuously and then went to my recovery tried restoring my old ROM phone booted up and I was using the same ROM. Next morning when I wake up phone rebooting again and again. Went to recovery , tried cleared system / factory reset Phone still rebooting. Made clean wipe flashed new ROM phone still rebooting
Don't know what to do. Then I flashed stock ROM using fastboot mode , flashed successfully phone booted up after completing setup wizard the phone started rebooting Help me to get rid out of this thanx :good:
Sorry for long explanation
I have same problem here after miui 8
waiting for solution
hope someone will solve
I have a similar case my device is in bootloop untill charger is connected.
I had similar(all most same) trouble you mentioned before and my bad luck i still dont have a solution :crying:
i flashed nuclear 7.1 but i encurred in a bootloop that i could resolve only with qfil tool, so i putted cos 12.1 stock, unclocked bootloader and flashed twrp, now: when i flash ANY rom via twrp i go in a bootloop that i can only solve with qfil tool going back to cos and do everything from beginning.
i tried:
change recovery (i tried CWM but i have same problem)
wipe storage (anything changed)
i tried several roms but everyone gave me the same result: very fast bootloop in zuk logo and phone vibration
the only thing i can do is to restore a backup, but since im note able to flash mm firmware (bootloop) i cant use touch id and g-sensor
what can be the problem?
any solution?
thanks
Boot and recovery partitions
Sounds like you messed up boot and recovery sections. Since you can boot up successfully, you may try to flash back to ZUI which changes these two sections completely. If it's not a solution for you, I think the only way to repair is completely format including kernel, system and partitions. You can find the tutorial on Website.
...
you can fix it just use TOOL_ZUK_Z1_ENG_0.0.6
Try flashing COS 12.1 via fastboot.
crazyox said:
i flashed nuclear 7.1 but i encurred in a bootloop that i could resolve only with qfil tool, so i putted cos 12.1 stock, unclocked bootloader and flashed twrp, now: when i flash ANY rom via twrp i go in a bootloop that i can only solve with qfil tool going back to cos and do everything from beginning.
i tried:
change recovery (i tried CWM but i have same problem)
wipe storage (anything changed)
i tried several roms but everyone gave me the same result: very fast bootloop in zuk logo and phone vibration
the only thing i can do is to restore a backup, but since im note able to flash mm firmware (bootloop) i cant use touch id and g-sensor
what can be the problem?
any solution?
thanks
Click to expand...
Click to collapse
Hi!! I've flashed the NucleaRom too and for a couple of weeks it worked just fine. However one day, out of nowhere, the phone, while still on and working, restarted itself and entered a bootloop. After a few days it restarted normally and lasted a couple of hours but then it all started again. The BIG issue here is that when the phone enters in this bootloop where it remains on for about 15 seconds, it does it either in the system or the recovery/fastboot. I've managed to install two other ROMs via TWRP, when it miraculously remained turned on, but the problem persisted.
Is there a chance your problem was similar? How did you manage to flash via QFIL? I can't enter into that "emergency" or "download mode" in order to flash.
Many thanks in advance
i think that the problem is in the bootloader itself you should try flashing the latest os u have used and instal ordinary unofical lineage nightly (you can find everywhere) by this way your bootloader will be updated to 7.1 after that you can install any software i was having same problem when trying to migrate to lineage os
unable to install Custom ROM's
hi ,,
even i had the same problem like recovery was not accepting any ROMS... if we flash it ll go to recovery again and again,
and later i have flashed CM 13 with image file,, it worked and gone to recovery and updated the update to lineage OS 14.1 with Gapps..
hope it might help u...
crazyox said:
i flashed nuclear 7.1 but i encurred in a bootloop that i could resolve only with qfil tool, so i putted cos 12.1 stock, unclocked bootloader and flashed twrp, now: when i flash ANY rom via twrp i go in a bootloop that i can only solve with qfil tool going back to cos and do everything from beginning.
i tried:
change recovery (i tried CWM but i have same problem)
wipe storage (anything changed)
i tried several roms but everyone gave me the same result: very fast bootloop in zuk logo and phone vibration
the only thing i can do is to restore a backup, but since im note able to flash mm firmware (bootloop) i cant use touch id and g-sensor
what can be the problem?
any solution?
thanks
Click to expand...
Click to collapse
crazyox said:
i flashed nuclear 7.1 but i encurred in a bootloop that i could resolve only with qfil tool, so i putted cos 12.1 stock, unclocked bootloader and flashed twrp, now: when i flash ANY rom via twrp i go in a bootloop that i can only solve with qfil tool going back to cos and do everything from beginning.
i tried:
change recovery (i tried CWM but i have same problem)
wipe storage (anything changed)
i tried several roms but everyone gave me the same result: very fast bootloop in zuk logo and phone vibration
the only thing i can do is to restore a backup, but since im note able to flash mm firmware (bootloop) i cant use touch id and g-sensor
what can be the problem?
any solution?
thanks
Click to expand...
Click to collapse
i am continuously on the boot loop! how to get rid of it?
plz help its been 4 hrs, i think i am in trouble! any possible solutions!!!!
U can try one thing.... Install cm13 with flash file and then restart - - & go to recovery select install update and select lineage 14 and G apps... I did like this . And it worked....
Hello. My device reboot into TWRP only after reboot (TWRP or System). I tried to reset data into AICP ROM in settings. Install again ROM don't works. Also restore from backup dont works. Help me :/
seems like this one trouble;
https://forum.xda-developers.com/note-4/help/sdcard-empty-installing-rom-t3030736
will try flash the stock one after night. If anybody knows solution, please help me.
After 356 milions of flashing twrp and wiping my phone finally update.zip (stock OS) transfered into phone (earlier still bugs). Then transfered stock.img (image of stock recovery) into phone and flashed it and... My backup worked. I'm embarrased. Will charge my phone and try to update to the lastest version. Then I'll check that my phone have stock or twrp of recovery. Idk what happened last night!
I could install the stock ROM (i had stock recovery and custom ROM). After boot, device runs ~40 sec then rebooting. In recovery i did clean data, then the stock OS works fine.