Issue: Whenever i try to install a custom rom for the first time the device is starting normally and it booting, But when i try to install the same rom again, the device goes to bootloop. This happened to all roms i tried. So help me to avoid this issue.
(Note: After the bootloop i manually flashed stock firmware to boot the device)
@Vasanth476
What's the TWRP recovery version you're using currently?
How you flash ROMs, dirty or clean flash?
saurav007 said:
@Vasanth476
What's the TWRP recovery version you're using currently?
How you flash ROMs, dirty or clean flash?
Click to expand...
Click to collapse
I am using TWRP 3.0.2
I did clean flash
Vasanth476 said:
I am using TWRP 3.0.2
I did clean flash
Click to expand...
Click to collapse
When you flash the same ROM second time, that is clean or dirty flash?
But this is weird. One can dirty flash same ROM, there shouldn't be any bootloops.
saurav007 said:
When you flash the same ROM second time, that is clean or dirty flash?
But this is weird. One can dirty flash same ROM, there shouldn't be any bootloops.
Click to expand...
Click to collapse
I did clean flash only. I did everything in order. I dont know where the problem is?
Related
On flashing a Custom Rom, my phone gets stucked with continous FC ("Unfortunately Phone Crashed","Press OK") just after the phone boots.
I had faced the same problem earlier so someone on XDA suggested to use twrp recovery. Then i flashed the purity rom and it worked fine, but then as you may know now, as PA is out, so flashed it and again i'm getting continuous fc error....
currently i'm using purity rom, stock kernel and twrp recovery (2.6.3.3)
I would flash back to a stock 4.2.2 and start over. I find that this is the only way I can install certain roms.
audit13 said:
I would flash back to a stock 4.2.2 and start over. I find that this is the only way I can install certain roms.
Click to expand...
Click to collapse
I already did this and again i'm facing the same problem
htrapy said:
I already did this and again i'm facing the same problem
Click to expand...
Click to collapse
Strange. Are you updating the bootloader and radio before flashing a 4.4 rom?
Are you doing a factory reset???? And flashing a proper gapps after ROM? You should always do this when going from one ROM to another. Sometimes a manual format of /system is necessary also.
no i am not updating my bootloader and radio before flashing (rather didn't know if i had to update them,fyi i bought my nexus 4 this september)....and yes i'm doing a factory reset (using the wipe option in twrp recovery which warns clearing of data, cache and dalvik memory)
My battery life has took a serious turn for the worse every since experimenting with a few different kernels, I'd really like to go back to stock 4.3 n9005 kernel. I did factory reset, but as suspected that didn't return the kernel.
Please help.
http://forum.xda-developers.com/showthread.php?t=2461929
flash rom with stock kernal as above.
davelangmaid said:
http://forum.xda-developers.com/showthread.php?t=2461929
flash rom with stock kernal as above.
Click to expand...
Click to collapse
Installed the pre-rooted rom in that thread and now stuck in a boot loop :/
Cant get out of this boot loop, still have access to TWRP but cannot do anything from there
Have you tried booting into recovery and clearing data. Do you have a backup? I don't no Twrp verywell as use cwm but I think its under wipe.
I have TWRP recovery but no backup, clearing data not fixing it unfortunately oh god
jarrodstrachan;501roms4 said:
I have TWRP recovery but no backup, clearing data not fixing it unfortunately oh god
Click to expand...
Click to collapse
Will have to download another rom on pc. Not sure why has happend.
Were you on custom rom?
davelangmaid said:
Will have to download another rom on pc. Not sure why has happend.
Were you on custom rom?
Click to expand...
Click to collapse
If boot loop happen after u flash the kernel than u flashed the wrong 1. Need to match with the firmware u're using. Try other custom kernel for 4.3. If u really planning to flash the whole rom then there is no need for custom kernel
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
My TWRP is 3.0.3 and whenever I flash the latest PureNexus Rom, only thing that appears on my screen is Android is starting after I complete the setup.
SHINee2 said:
My TWRP is 3.0.3 and whenever I flash the latest PureNexus Rom, only thing that appears on my screen is Android is starting after I complete the setup.
Click to expand...
Click to collapse
Even i had faced this issue on 6.0.1 build, Dont remember exactly how i got it resolved .
But you may try this
flash vendor image
wipe
flash rom
wipe
reboot
just try it out :good:
ramrock007 said:
Even i had faced this issue on 6.0.1 build, Dont remember exactly how i got it resolved .
But you may try this
flash vendor image
wipe
flash rom
wipe
reboot
just try it out :good:
Click to expand...
Click to collapse
Thank you I will try it out.
SHINee2 said:
My TWRP is 3.0.3 and whenever I flash the latest PureNexus Rom, only thing that appears on my screen is Android is starting after I complete the setup.
Click to expand...
Click to collapse
Did you flash a GApps package? I believe Pure Nexus recommends Dynamic GApps... Check the PN thread for the download link.
Wipe
Flash ROM
Flash GApps
Flash vendor (although you shouldn't need to do this again)
Reboot system
SHINee2 said:
My TWRP is 3.0.3 and whenever I flash the latest PureNexus Rom, only thing that appears on my screen is Android is starting after I complete the setup.
Click to expand...
Click to collapse
You should search the Pure nexus thread. This is a known issue with the latest build and there are workarounds for it.
Okay so I've tried Pixel experience, lineage os , omni rom treskmod and couple of other custom android 10 roms, all stable and official and also updated ones, the wifi just simply doesn't work, wifi hotspot won't turn on either. I've tried every solution on the internet. I've even factory reset my phone using msm download tool and no luck(did this countless times).
I'm back in OOS 10.3.2 and there's no issue apparently.
At one point , i flashed a custom rom and the wifi didn't work, so I flashed OOS in the two slots and checked , the wifi works in OOS apparently, and never in custom roms.
Has anyone got this issue before and knows a solution?
How is your installation procedure?
onliner said:
How is your installation procedure?
Click to expand...
Click to collapse
I flash OOS and twrp on both slots, reboot recovery,
And then flash the rom and twrp, reboot recovery,then format data and factory reset, reboot recovery, if needed for some gapps, then reboot system
ivanthomas said:
I flash OOS and twrp on both slots, reboot recovery,
And then flash the rom and twrp, reboot recovery,then format data and factory reset, reboot recovery, if needed for some gapps, then reboot system
Click to expand...
Click to collapse
That's a lot of unnecessary steps. OOS on both slots, reboot to bootloader, boot twrp, format data and flash the custom rom, reboot bootloader, boot twrp and flash gapps, don't install twrp permanently if you are not going to install Magisk.
onliner said:
That's a lot of unnecessary steps. OOS on both slots, reboot to bootloader, boot twrp, format data and flash the custom rom, reboot bootloader, boot twrp and flash gapps, don't install twrp permanently if you are not going to install Magisk.
Click to expand...
Click to collapse
I need magisk too, I usually permanently install twrp
Also you think it's the way I'm installing at fault here? Or the rom? Or is it something wrong with my device?
ivanthomas said:
it's the way I'm installing at fault here?
Click to expand...
Click to collapse
This.
I always install roms with the procedure i said above and have never had any problems.
onliner said:
This.
I always install roms with the procedure i said above and have never had any problems.
Click to expand...
Click to collapse
Alright so got one doubt, I used OOS 10.3.2 to flash, should it be oos 10.0 only?
Thought that didn't make a difference.
I am also facing the same issue. Were you able to find any solution ?
So I found out treskmod omni rom and Paranoid android quartz 2 work perfectly , try those out, it still doesn't solve the problem in the other roms though. So not exactly a solution.