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....
Related
Hi, I need help in installing Recovery.
I unlocked the bootloader, installed TWRP and then CyanogenMod 13 ROM.
After this, Oxygen Os 3 got released. I downloaded the zip file and flashed through TWRP.
Oxygen OS got installed but after this, I couldn't go back in TWRP recovery.
I tried everything. I use "fastboot flash recovery twrp.img"
everything works
but when I boot in recovery, phone gets stuck on the LOGO and nothing happens.
Is there any way to solve this issue.
Almost the same for me.
When I flash oOS 3.0.2, unable to reboot using Grarak'sTWRP or TWRP-3.0.2-1.
Always stuck on boot logo without animation.
I reverted to old TWRP and oOS 2.2.1
piyushmodi01 said:
Hi, I need help in installing Recovery.
I unlocked the bootloader, installed TWRP and then CyanogenMod 13 ROM.
After this, Oxygen Os 3 got released. I downloaded the zip file and flashed through TWRP.
Oxygen OS got installed but after this, I couldn't go back in TWRP recovery.
I tried everything. I use "fastboot flash recovery twrp.img"
everything works
but when I boot in recovery, phone gets stuck on the LOGO and nothing happens.
Is there any way to solve this issue.
Click to expand...
Click to collapse
Try to install OOS recovery or Hybrid recovery.
Nobody ever learns or reads nowadays....
Read up on bootloader versions on Oneplus 2 and you will find the explanation perfectly understandable.
Thank You So much for your help. Finally it worked but I lost my data! Anyways, no issues.
Can you give us the way you fixed your problem .
Thanks
update:
i tried what you suggested, reflashing stock rom now. encountered same problem even in twrp, the phone reboots itself.
god help me i am trying to fix this for 2 days now.
=======
Here is the problem that i am encountering right now.
i am not sure what i am doing wrong, and this time whenever i flash something from recovery the phone reboots.
here are the things i did, using philz touch, i chose the install new rom (i do this everytime when flashing a new rom) then flash RR, was able to finish it but stuck in boot loop. so followed the same steps and flashed 2 other roms, infernus and halcycon (used these roms before) however before finishing the installation the phone reboots.
next step i flashed twrp via odin (success) and flashed the latest version via twrp recovery. guess what same problem, with RR it is stuck in boot loop while with other roms, it does not complete the installation. this thing never happened to me.
next step i used this adb thing and i believe it is successful, however same problem persists.
the only thing i can think of is to flash the original i9500 firmware which i am downloading right now and will flash it via odin. - did not work
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 Installed the unofficial cynogenmod 14 with gapps , and i was enjoying the new rom. After using the rom for 8-10 hours , the mobile froze , so i had to restart the phone . After the phone started , it started to lag , and while it was lagging it restarted on its own, and was stuck on boot logo.
I waited for a long time for it to boot up , but it was stuck there , so i tried flashing the unofficial cm14 again as it was in the internal storage , but the result was same no matter how many times i try , and in between numerous OS flash attempts , i accidentally wiped the INTERNAL STORAGE
Getting the PC to recognize the phone , and also for the ADB and FASTBOOT to work properly was way too much of a pain , but i was able to get everything correct so ADB and FASTBOOT were working .
AND THAT'S HOW MY JOURNEY BEGAN.
I HAVE FLASHED ALL THE OTA ROMS , flashed the official cynogenmods , flashed the unofficial cm14 and cm 14.1 , tried flashing thru MSM8994DownloadTool , all of the Roms i FLASHED were successful even the MSM8994DownloadTool was SUCCESFULLY FLASHED
BUT MY PHONE STILL DOESN'T BOOTS UP IN SYSTEM , IT'S STILL STUCK AT THE ONEPLUS BOOT LOGO
I LIVE IN BANGLADESH (ASIA) , after i failed so many times and given up all hope , i went to the mobile shops for repairing the HALF DEAD SOUL , and its really sad that even they were not able to make it LIVE AGAIN
ANY HELP TOWARDS MY SITUATION WILL BE REALLY REALLY APPRECIATED
It maybe cause of old modem. try restoring to stock(i.e oos 3.x) or flash latest modem then latest recovery and Rom.
ThePresence said:
It maybe cause of old modem. try restoring to stock(i.e oos 3.x) or flash latest modem then latest recovery and Rom.
Click to expand...
Click to collapse
Tried the op2 mm modem , the phone automatically restarted to recovery with a new recovery , but its still stuck
talhaisdead said:
Tried the op2 mm modem , the phone automatically restarted to recovery with a new recovery , but its still stuck
Click to expand...
Click to collapse
Are you following the right steps to flash rom? if you don't rom won't boot. also try resetting your phone to stock, it might help you.
ThePresence said:
Are you following the right steps to flash rom? if you don't rom won't boot. also try resetting your phone to stock, it might help you.
Click to expand...
Click to collapse
Yes , but it still doesn't work . No errors are given while flashing
Hey!
I installed LineageOs on my Xiaomi Mi A1, everything went okay but when I installed the Gapps, it got stuck on the LineageOs logo. The volume button wasn't working right, yet somehow, I manage to enter TWRP and wipe that OS and restore the backup with the original Android One. But when I boot it, it got stuck on Android logo, unable to enter fastboot, TWRP or hard reset because of the volume button not working.
I don't know what else to do, to be honest...
p.d.: I'm new here, sorry if this is not the right section to ask.
Are you 100% sure that you have chosen right version of GApps? because i never had any issues with GApps causing boot loop. BTW what lineage os version 16 or 17 ?
I never had any luck restoring stock rom backup via TWRP either i have no idea why whenever i restore it will stuck on androidone logo.
royalasif said:
Are you 100% sure that you have chosen right version of GApps? because i never had any issues with GApps causing boot loop. BTW what lineage os version 16 or 17 ?
I never had any luck restoring stock rom backup via TWRP either i have no idea why whenever i restore it will stuck on androidone logo.
Click to expand...
Click to collapse
I chose Android 10 GApps since I installed LineageOS 17. I thought it was the right version.
So TWRP can't be used for stock rom? I didn't know, maybe that's what got me stuck on Android One logo.
Any idea on how to get out from that loop? ?
Dont worry bootloop is not a problem download pixel experience it include gapps boot ur phone to twrp copy rom into internal or sd card Wipe system , data , cache and install the rom ..
TWRP should backup and restore stock image but i think there is something with this phone which wont let twrp to apply system restore i have done it 10 times and i failed everytime.
Edit: do let me know how it goes:good:
royalasif said:
Dont worry bootloop is not a problem download pixel experience it include gapps boot ur phone to twrp copy rom into internal or sd card Wipe system , data , cache and install the rom ..
TWRP should backup and restore stock image but i think there is something with this phone which wont let twrp to apply system restore i have done it 10 times and i failed everytime.
Edit: do let me know how it goes:good:
Click to expand...
Click to collapse
Definitely I'll try Pixel Experience! Seems like a good choice. I still need to figure out how to enter Fastboot or TWRP without the volume button.
try adb cmd if it works if not then u have to boot your device to EDL mode by test point method and then flash stock rom
ranjodhricky said:
try adb cmd if it works if not then u have to boot your device to EDL mode by test point method and then flash stock rom
Click to expand...
Click to collapse
Adb cmd won't recognize the device, so I'll have to boot it to EDL mode. Is there any guide here? I don't know how to do it.