Hello!
Previously I've had PA 3.99 but today I downloaded stock 4.4 from google site and flashed it via fastboot. System works perfectly, but always when I want to flash CWM or TWRP (newest) phone stuck on boot (but recovery works)
Anyone knows the reason?
Cheers!
Try...
Colourkey said:
Hello!
Previously I've had PA 3.99 but today I downloaded stock 4.4 from google site and flashed it via fastboot. System works perfectly, but always when I want to flash CWM or TWRP (newest) phone stuck on boot (but recovery works)
Anyone knows the reason?
Cheers!
Click to expand...
Click to collapse
Try wiping data/cache after flashing recovery in this recovery.
I'm stupid. Worked. Thanks!
But
Colourkey said:
w8
Click to expand...
Click to collapse
I mean after you stuck at boot logo and already installed TWRP enter TWRP and wipe those If it not work flash zip of an 4.4 thats already rooted.
msihp said:
I mean after you stuck at boot logo and already installed TWRP enter TWRP and wipe those If it not work flash zip of an 4.4 thats already rooted.
Click to expand...
Click to collapse
Sorry for misunderstood. I answered before fact that phone finally boot. Wipe helped, I'm stupid, because I forgot about that ;D
Dzięki!
Related
After rooting my N7 a few weeks back, I have tried flashing at least 3 different grouper custom roms through TWRP 2.4.2.
After flashing the rom, when I reboot from TWRP, the N7 gets stuck on bootscreen logo of the respective rom. I have to use Nexus Toolkit 1.6.3 to reboot into TWRP and restore from nanroid backup of stock rom, and everything works fine.
Why are Custom ROMs not being able to boot past the bootscreen logo?
I would appreciate help.
Thanks in advance.
You should give us more info... What's your device, which rom you want to try, what steps did you do to flash the rom in recovery?
Nico_60 said:
You should give us more info... What's your device, which rom you want to try, what steps did you do to flash the rom in recovery?
Click to expand...
Click to collapse
Nexus 7, I have tried flashing simbean 4.2.2, latest XenonHD and another which i have forgotten the name (all latest grouper versions).
I downloaded ROMs on my PC from XDA.
Copied zip file into nexus 7 via USB cable.
Rebooted into TWRP 2.4.2.0
Wipe System/ cache/ dalvic cache
flashed Rom (indicated flash was successful)
Rebooted from TWRP
bootloop (getting stuck at the bootanimation of the custom rom)
Used Nexus Toolkit 3.6.1 to reboot into TWRP
Restored my stock rom from backup.
Stock Rom working fine.
Ive tried flashing faux kernel and an aroma installer for boot animation change, which has worked fine both times.
When you are in recovery, first go in wipe menu and do a factory reset, wipe system (optional), install the ROM and reboot and all should be fine.
Maybe try flashing with a more recent version of TWRP, 2.4.4.0
http://forum.xda-developers.com/showthread.php?t=1779092
http://www.teamw.in/project/twrp2/103
--------
Fastboot flash the latest recovery image from here...
http://techerrata.com/browse/twrp2/grouper
...and then try again, flashing your preferred ROM in recovery.
--------
Don't know if it will work... but it's got to be worth a shot.
What is odd, is you seem to have no problem NANDROID restoring back to stock...
Anyway, hope you get it sorted.
Rgrds,
Ged.
Nico_60 said:
When you are in recovery, first go in wipe menu and do a factory reset, wipe system (optional), install the ROM and reboot and all should be fine.
Click to expand...
Click to collapse
thanks , problem solved
fslnwz101 said:
thanks , problem solved
Click to expand...
Click to collapse
hi all,
I flashed the 4.3 factory image today and intalled TWRP recovery using Goo Manager and then successfully booted into it and flashed the SuperSU zip...but now i cant boot into it again to flash other things
whatever the method i try, it returns the android lying on with a red exclamation mark
anybody know a solution??
IKnowIRock! said:
hi all,
I flashed the 4.3 factory image today and intalled TWRP recovery using Goo Manager and then successfully booted into it and flashed the SuperSU zip...but now i cant boot into it again to flash other things
whatever the method i try, it returns the android lying on with a red exclamation mark
anybody know a solution??
Click to expand...
Click to collapse
try clearing cache and dalvick cache..
have you taken any nandroid backup??
IKnowIRock! said:
hi all,
I flashed the 4.3 factory image today and intalled TWRP recovery using Goo Manager and then successfully booted into it and flashed the SuperSU zip...but now i cant boot into it again to flash other things
whatever the method i try, it returns the android lying on with a red exclamation mark
anybody know a solution??
Click to expand...
Click to collapse
Rohit02 said:
try clearing cache and dalvick cache..
have you taken any nandroid backup??
Click to expand...
Click to collapse
Lulz. The reason why this is happening is because stock nexus roms will ALWAYS try to flash back a normal recovery.
You need to try and find a way to flash back a custom recovery (ahem, fastboot flash recovery recovery.img)
and there should be a notification when you're about to reboot that says something like disable stock recovery?
Not sure if that was TWRP or CWM.
stock rom will replace your custom recovery with stock recovery.
Use Flashify app to flash img on phone
Sent from my Nexus 4 using Tapatalk 4
I decided today to try and root my phone and followed the steps on this tutorial: http://forum.xda-developers.com/nexus-4/general/nexus-4-guide-unlock-bootloader-root-t2266654
I had unlocked my phone and installed the latest version of TWRP. Now I can only boot into TWRP and bootloader. My phone is not being picked up by my PC. I tried a factory reset and format of data on TWRP but my phone still only boots into TWRP.
Is my phone permanently bricked?
Any help will be greatly appreciated
I actually have just made some progress now. I've managed to get the phone connected to the computer by going into ADB sideload and installing the ADB drivers again on my computer.
Typing ADB devices in CMD now shows my device as connected.
Any advice on what I should do now?
What happens when you try to boot it normally? Is it stuck at the boot animation or does it go directly to the bootloader or recovery? Since you already had to wipe everything you could try flashing a factory image via fastboot.
theminikiller said:
What happens when you try to boot it normally? Is it stuck at the boot animation or does it go directly to the bootloader or recovery? Since you already had to wipe everything you could try flashing a factory image via fastboot.
Click to expand...
Click to collapse
Booting the phone normally loads it into TWRP. Booting the phone with the volume key pressed down loads the bootloader. I think I may have just wiped the OS present on the Phone.
I want my phone to be rooted running CyanogenMOD (phone is currently unrooted). Should I first install a stock rom then root by installing SuperSU and CyanogenMOD or can I just skip installing a stock rom and install SuperSU and CyanogenMOD?
Thanks for the help
You could try flashing a cyanogenmod zip from TWRP, and if that doesn't work I would suggest flashing I factory image.
theminikiller said:
You could try flashing a cyanogenmod zip from TWRP, and if that doesn't work I would suggest flashing I factory image.
Click to expand...
Click to collapse
But my phone is not rooted yet. Can I install SuperSU by copying onto my phone and installing it through TWRP?
umair_ said:
But my phone is not rooted yet. Can I install SuperSU by copying onto my phone and installing it through TWRP?
Click to expand...
Click to collapse
Yes, if it is a zip file. But I'm pretty sure installing cyanogenmod will automatically root it for you.
theminikiller said:
Yes, if it is a zip file. But I'm pretty sure installing cyanogenmod will automatically root it for you.
Click to expand...
Click to collapse
I installed SuperSU then CyanogenMOD and lastly GApps. It still only boots into TWRP and it doesn't look like there has been any files added to the phone's storage. Should I first flash a stock rom and then try to install CyanogenMOD?
umair_ said:
I installed SuperSU then CyanogenMOD and lastly GApps. It still only boots into TWRP and it doesn't look like there has been any files added to the phone's storage. Should I first flash a stock rom and then try to install CyanogenMOD?
Click to expand...
Click to collapse
Yes, try flashing a factory image. If it boots then you could try flashing cyanogenmod.
EDIT: here is a guide on how to flash a factory image: http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
theminikiller said:
Yes, try flashing a factory image. If it boots then you could try flashing cyanogenmod.
EDIT: here is a guide on how to flash a factory image: http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
Click to expand...
Click to collapse
I've managed to get it all working by first flashing the stock ROM and starting all over again.
Thanks for your help.
Is there a workaround to this other than flashing factory images...?
hwweiler said:
Is there a workaround to this other than flashing factory images...?
Click to expand...
Click to collapse
@hwweiler, No friend there is no other way.Please before do this as is one direction way take the pain to look on my post #180 on zaclmon's thread http://forum.xda-developers.com/nexus-4/orig-development/wip-aosp-7-0-nougat-t3448444/page18 and keep in mind that is impossible to return back on any nandroid backup u kept e.g to 5.1.1 or M furthermore its also impossible to flash any rom zip if u use this N (WIP) rom,the only way to have a workable phone again is to flash the stock rom from scratch.Exceperienced with and never again untill we have the appropriate solution..The twrp used and i still use on M is TWRP 3.0.2.0.The possibility to return on LP ffrom M and reverse still exists but not when u flash this rom.
Regards,Christos
i downloaded the kernel on my s3 neo (gt i9300i) running cm12.1 and i got a bootloop after i restarted in my recovery (cwm) after i flashed it. can anyone help me? D:
if you want to get from a bootloop, then REFLASH your CM12.1. just boot into your recovery.
wipe system, data, cache, dalvik. THEN REFLASH your ROM CM12.1 and GAPPS (optional)
if you want to install kernel successfully, i recommended to switch from TWRP recovery.
most kernel of cm12.1 based rom suggested that you use TWRP.
I'm using TWRP and flash kernel and didnt get any bootloop...
DerPuGNa said:
...
Click to expand...
Click to collapse
thanks bro im going to try and flash twrp now and see if it does the trick. thanks
DerPuGNa said:
...
Click to expand...
Click to collapse
I changed my recovery into twrp and tried to flash the kernel on my cm12.1 but still no luck. im stuck in the boot screen :crying:
Vanwald said:
I changed my recovery into twrp and tried to flash the kernel on my cm12.1 but still no luck. im stuck in the boot screen :crying:
Click to expand...
Click to collapse
what kernel u flashing?
DerPuGNa said:
what kernel u flashing?
Click to expand...
Click to collapse
nvm hahaha. i downloaded the latest cm12.1 for my phone, flashed gapps then i flashed the kernel using twrp and i got it to work. thanks m8
My N10 with stock 5.1 previously had root with TWRP 2.8.6, but for some reason it recently lost root. In addition, it seems that TWRP has been corrupted because whenever I try to boot into recovery I get a dead bootloader with a red exclamation mart. After I flashed the most recent version of TWRP 3.0.0-1 using "fastboot flash recovery twrp-3.0.0-1-manta.img" (bootloader still unlocked), I still get a dead bootloader when booting into recovery.
Then I flashed back to TWRP 2.8.6, but the problem remains!
How to fix the problem? Thanks!
I hope you can go to bootloader mode... Revert to stock by flashing the factory images and then start over again
nitin.chobhe said:
I hope you can go to bootloader mode... Revert to stock by flashing the factory images and then start over again
Click to expand...
Click to collapse
Thanks!
Just flashed an even older version (2.8.5) of TWRP, and now suddenly it can boot into recovery without any problem. I have also gained root now after flashing SuperSU.
I was planning to flash the most recent version of TWRP (3.0.0-1), and then try out CM13, but for some reason my N10 with stock 5.1 does not like those newer versions of TWRP. Do you know why?
mj56gt said:
Thanks!
Just flashed an even older version (2.8.5) of TWRP, and now suddenly it can boot into recovery without any problem. I have also gained root now after flashing SuperSU.
I was planning to flash the most recent version of TWRP (3.0.0-1), and then try out CM13, but for some reason my N10 with stock 5.1 does not like those newer versions of TWRP. Do you know why?
Click to expand...
Click to collapse
No, I do not konw that. Are you flashing correct version of TWRP made for manta?
nitin.chobhe said:
No, I do not konw that. Are you flashing correct version of TWRP made for manta?
Click to expand...
Click to collapse
I downloaded all the three versions (2.8.5, 2.8.6, and 3.0.0-1) of TWRP I've flashed so far from here:
https://dl.twrp.me/manta/
This is weird. Is it because I didn't have root during the time I flashed 2.8.6 or 3.0.0-1? I thought that flashing TWRP would not require root.
Can I flash CM13 with TWRP 2.8.5? I'll definitely make a Nandroid backup before proceeding.
mj56gt said:
I downloaded all the three versions (2.8.5, 2.8.6, and 3.0.0-1) of TWRP I've flashed so far from here:
https://dl.twrp.me/manta/
This is weird. Is it because I didn't have root during the time I flashed 2.8.6 or 3.0.0-1? I thought that flashing TWRP would not require root.
Can I flash CM13 with TWRP 2.8.5? I'll definitely make a Nandroid backup before proceeding.
Click to expand...
Click to collapse
With nandroid, you are good to go.
Should be possible :fingers-crossed:
nitin.chobhe said:
With nandroid, you are good to go.
Should be possible :fingers-crossed:
Click to expand...
Click to collapse
I did factory reset in TWRP 3.0.0-1 and then flashed CM 13.0-20160309 on my N10 with the dynamic Gapps. Now I get this error Unfortunately Google Play Services Has Stopped. Is it because the default factory reset is not good enough or something else? If it needs a full wipe, what exactly should I wipe, system and data? And after a full wipe, do I need to reflash CM13 or just Gapps?
Thanks!
mj56gt said:
I did factory reset in TWRP 3.0.0-1 and then flashed CM 13.0-20160309 on my N10 with the dynamic Gapps. Now I get this error Unfortunately Google Play Services Has Stopped. Is it because the default factory reset is not good enough or something else? If it needs a full wipe, what exactly should I wipe, system and data? And after a full wipe, do I need to reflash CM13 or just Gapps?
Thanks!
Click to expand...
Click to collapse
Problem solved: Just flashed the pico Gapps, and now everything works fine. For some reason the dynamic Gapps didn't work for me.
mj56gt said:
Problem solved: Just flashed the pico Gapps, and now everything works fine. For some reason the dynamic Gapps didn't work for me.
Click to expand...
Click to collapse
May be there isn't enough space to flash them.
Happy that is working now
Sent from my Nexus 4 using XDA Free mobile app