Hello folks,
Those who are using latest TWRP or 4Ext recovery,Please comment below.Also i want to know which custom rom your on? I do flash roms in every 2-3 days and problem took place i guess somewhere from CM11 nightly 06/12 onwards.
So my question is: Anybody has encountered a problem where flashing latest nightly or any latest build beyond 4.4.3 causes reboot into recovery automatically soon after flashed boot.img and reboot system.
I always prefer Clean wipe, Install rom, Appropriate GApps, Inspiremod Patch, flash boot.img via fastboot.
Also i would like to add,that when i use Musta's CM11 nightly after successfully flashing it and rebooting the device. But nothing comes after typical htc logo and complete blank screen for few seconds and redirects me into TWRP recovery again. Where as If i use any rom made chinese devs like for ex. Mokee Open Source's latest weekly(randomly) it flashes correctly but it stuck at bootanimation.
Yesterday i've tried one more modified version of Musta's 20140622 nightly made by chinese dev, It flashed correctly but hangs up in bootanimation, i couldn't able to see anything beyond that.
Any sort of help will be appreciated.
Thanks.
Hello, a friend of mine installed a custom rom at my lg g3 android phone. The rom is ressurrection remix. I accidently dirty flashed an older version of the same rom, I had 5.1.1 r6 and I flashed 5.0.3, and now neither adb works nor download mode due to killswitch. The only thing it does is show the old rr boot image. It's on a bootloop and since it doesn't open I don't know how to fix it. Can someone tell me what should I do?
Can you use the button combo to boot into TWRP? If you can get into TWRP then just flash the ROM you want and be sure to follow the rom threads instructions before flashing of course.
so far ive had a problem with gapps, the the cm12 rom works fine but every gapps package i flash when i boot the phone up it pops a million notification com.google.... has stopped i have tried gapps from about most websites for lollipop 5.0.2 for cm 12 non worked from basketbuild i have tried no succes if you know how to help me then do i havent found any solution so far system info: htc one x endeavoru,cm 12 rom unofficial
cwm recovery 5.8.4.0
kuba6532 said:
so far ive had a problem with gapps, the the cm12 rom works fine but every gapps package i flash when i boot the phone up it pops a million notification com.google.... has stopped i have tried gapps from about most websites for lollipop 5.0.2 for cm 12 non worked from basketbuild i have tried no succes if you know how to help me then do i havent found any solution so far system info: htc one x endeavoru,cm 12 rom unofficial
cwm recovery 5.8.4.0
Click to expand...
Click to collapse
how you flash the phone with CM12 and this old recovery this is inpossible and this is the reason why the gapps not working go and read how to flash cm12 new layout and wich gapps to use
is there a non touch recovery i could use? since touch recoveries dont work for me if there is a solution could you link me to a thread with the solution?
solved just had to use twrp big picture and format my card
So recently i flashed the new cyanogen 14.1 nightly rom but it said their was an update but after i installed it it tried to go into recovery and wouldnt start. I shut it down and it would only go into fastboot mode and show the boot image. after this i downloaded fastboot and adb files and a tool kit and it now boots into the actual rom but still not recovery. so how can i get the recovery to pop up? iv already tried to flash twrp again but it still didnt load. and i even flashed the stock recovery and still wouldnt boot up. if anyone knows a way i can fix my recovery it would help alot. :good:
I have exactly same problem as you k hope it's a problem with the new cyanogenmod 14.1 nightly if not may try to change the kernel? I'm looking around too
Same problem here.... I installed TWRP and Dirty Unicorns on my One Plus 3, but immediately had a host of problems (including home key not working). I then flashed the most recently nightly (cm-14.1-20161119-NIGHTLY-oneplus3.zip). It booted fine, but now I cannot get into recovery. Any attempt to boot into recovery will put me back at the unlock warning screen... The phone is functionally useless at this point, because it doesn't even have gapps on it.
How can I restore this phone to a usable state (i.e., enter recovery to allow flashing of gapps)?
official twrp doesnt work with community builds and cm 14.1. You have to use modified twrp 3.0.2-22. the link can be found easily in official cm 14.1 forum on xda.
I'm having issues with LineageOS based roms. Basically, ever since 4.1.0 was released, I haven't been able to boot anything other than OxygenOS.
The first time I flashed the 4.1.0 firmware, my OnePlus 3 bricked. I then used the unbrick tool to fix it. I then tried again, by flashing the 4.1.0 firmware, then flashing the latest LineageOS "lineage-14.1-20170316-nightly-oneplus3-signed.zip". Upon reboot, the phone stays stuck at the lineageos boot animation. I can't get any logcats (adb logcat doesn't seem to work).
Things I've tried so far:
- Using TWRP 3.0.4-1
- Using TWRP 3.1.0-0
- Dirty flash
- Clean flash
- Data as both f2fs and ext4, neither works
- Tried using TWRP's "Fix Contents"
- Tried using TWRP's filesystem repair, no problems with the filesystem
I'm at a loss, no idea what to do. I really want to get back to LineageOS, but ever since that original brick, the phone hasn't been able to boot anything other than the stock ROM.
do you try download again that rom?
i had some problems with AICP, flashing last firmware+modem was solved
you can try using other base, like 4.02, or freedomOS OB12
just ideas, I don't know what's the problem :/
bro i flashed the 316 build on oos 4.1 firmware and modem no issue here all works fine still using it with blue spark kernal you must have done something wrong
vasu1312 said:
bro i flashed the 316 build on oos 4.1 firmware and modem no issue here all works fine still using it with blue spark kernal you must have done something wrong
Click to expand...
Click to collapse
I don't think I screwed up anything. I had flashed multiple roms before. (LineageOS, ResurrectionRemix, AICP, FreedomOS...)
All of them worked, up until recently. When the 4.1.0 update came out, LineageOS Roms stopped booting. OxygenOS ROMS still work fine though. Flashing the OB12 firmware doesn't help.
This is the first time this has happened, I have no idea why its happening.
Do you flash SuperSU, without SuperSU mine boots fine. Without i m stuck in boot
Tried flashing SuperSU, but nothing has changed. Android still won't boot up if it is a LineageOS based ROM
go to stock recovery (oxygen os stock one)
then flash 4.1.0 with that recovery
then boot
now replace the recovery with twrp 3.1.0
once done dont boot the rom n go to recovery and flash su
now boot rom
now again go to twrp n wipe system, data, cache, dalvik
and then flash lineage lastest build.. it will work
if not lemme know i will help you further
indroider said:
go to stock recovery (oxygen os stock one)
then flash 4.1.0 with that recovery
then boot
now replace the recovery with twrp 3.1.0
once done dont boot the rom n go to recovery and flash su
now boot rom
now again go to twrp n wipe system, data, cache, dalvik
and then flash lineage lastest build.. it will work
if not lemme know i will help you further
Click to expand...
Click to collapse
Just did it. It didn't work, the phone gets stuck in the LineageOS Boot screen
Now, not even Android 6.0 ROMS will boot. I think some partitions are corrupted, but I'm unable to wipe them in fastboot mode.
Edit: So, finally, after 3 days, I was able to get in contact with OnePlus. OnePlus fixed the problem with the Qualcomm Tools, not entirely sure what they did, but it fixed the problem. I'm finally able to boot LineageOS!!!!
AquaBytez said:
Just did it. It didn't work, the phone gets stuck in the LineageOS Boot screen
Click to expand...
Click to collapse
how much time do you wait because first boot does take 5 or more minutes
indroider said:
how much time do you wait because first boot does take 5 or more minutes
Click to expand...
Click to collapse
OnePlus said that the persist partition had been corrupted. So they re-flashed it and the phone started booting custom ROMS again. I guess the ROMS weren't booting because they got stuck waiting on the sensors. (To be completely honest, I never noticed that the sensors were broken. Since the only one I frequently use is the Gyroscope and that one was working fine)
AquaBytez said:
OnePlus said that the persist partition had been corrupted. So they re-flashed it and the phone started booting custom ROMS again. I guess the ROMS weren't booting because they got stuck waiting on the sensors. (To be completely honest, I never noticed that the sensors were broken. Since the only one I frequently use is the Gyroscope and that one was working fine)
Click to expand...
Click to collapse
perfect... that is what i was trying ro instruct you reflasing the stock but somehow ,,, it was not able to be done throught stock oxygen recovery... from ur end
nevertheless happy ur device is working fine now