hi,
i have installed recovery 1.7 and everything went well,but from the second i have tried to install the Cyanogen mod everytime i turn on the phone it get stuck on the logo screen i have tried to restore the nand but it didn't help
i can reach the recovery menu
please tell me it's not brick and that i can fix it...
thank you in advance
Dor Dali
No it's not bricked... it's an issue many ppl are facing with CM 5.0.5.1...
The temp fix: Enter recovery, wipe, flash CM 5.0.5, then flash CM 5.0.5.1, then flash GApps...
For another possible fix see:
http://forum.xda-developers.com/showpost.php?p=5954230&postcount=4
it worked thanks
but now i have another problem
how do i add keyboard(hebrew)?
Trying to install a Custom ROM for the first time on Nexus 7 (3G).
I've been using the WF Nexus Toolkit.
I've rooted, unlocked and flashed ParanoidAndroid but I'm only getting a bootscreen loop. I waited 15 min before rebooting the device and attempted to boot into PA again. Still not getting past the Bootscreen.
I booted into recovery; did a full wipe then flashed the PA ROM again... Still not getting past the Bootscreen (waited 30 min before powering off the device)
I've tried to obtain help via IRC before posting here; as well as reading through other post directly related to the problem (even a few that were slightly indirect) but nothing I find is helping... so I've turned to you guys!
I would very much like to get this ROM working, so if there is anyone that can help I would greatly appreciate it.
I just don't know what to do next; I've never had this issue with any device in the past.. I've usually been able to figure the problem out and get it working. But now I'm just stuck.
What is your recovery? What steps did you do in recovery to install the rom?
Try these step may help.
1.Boot into recovery
2.Full wipe
3.Wipe Cache
4.Wipe dalvik cache
5.Flash ROM, GAPP
then reboot your N7.
...
If above method still doesn't work. make sure you have the right version of bootloader and stock image on your device for PA 3.15 or newer it should be 4.18 for bootloader and 4.2.2 for stock image (optional).
And if you've found that you have other version of bootloader than 4.18 check this http://forum.xda-developers.com/showthread.php?t=1907796 thread for how to get it right.
...
Finally if you've done all the solutions above and still in bootloop problem just try to do a factory reset (full wipe) again after finish flashing ROM, GAPP.
That's all I can thinks of about this problem base on my personal experience facing bootloop problem few months ago.
If you are still stuck after trying the above posts. You can just try to get back to stock. Nexus Root Toolkit maybe the easiest way to do that..
____________________________________________
Please press the thanks button if you find this helpful
I have rooted my phone, then installed TWRP along with CM 12 unofficial. Next, I wiped everything and reflashed it down to CM 11, but I haven't been able to successfully reboot the phone at anytime. My phone will boot up to the Galaxy Screen, but won't doing anything unless it's a fresh install of the GAPPS and ROM. So it's hard to take pics when you have to restart and wipe your phone, and reflash it just to take a single pic! Is there anything that I could possibly do to fix this? Any help is greatly appreciated!
Hi. Writing from my Phone now. Im running cm 11. I installed or flashed philz touch...
Then installed cm11.
I want to do a nandroid backup..
But when i tried restarting to recovery, it skipped that part and went to cm11..
Normal reboot.
Before i flashed cm i had latest stock rom from samsung.
I flashed philz touch that time to..
But when i then installed cm, something went wrong, got some error on cm.
Uid's something. Forgot. I could not boot in recovery, so i used odin, flashed philz touch.
Factory reset and my Phone was fine!
Cm and recovery.
Now it seems i cant get into recovery again...
Anyone know whats the issue?
Locked bootloader? Have not read up on that yet...
Its wierd if recovery just fails or whats the issue.
Pardon the blurry explenation and my bad english/spelling. Im tired.
Thanks in advance.
It was the Quick boot app. Since i set developer options in cm to restart into recovery through CyanogenMod.
But the Buttons did not work last time i tried.
But its kinda solved. Flashed the latest recovery with rashr yesterday...
So i will just use cm to boot into recovery..
Thanks anyways.
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....