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.
Related
So here's the story
I installed CM11 about a month ago but then decided to revert back to stock, but then again due to short battery life decided to go back to cyanogenmod.
However when I try to install cyanogenmod (even the exact same version as before) on various recoveries (including CMW and Philz) I get the status 7 error. I've already tried to change the code in the updater-script and updating the recovery image, but nothing seems to work. Though I have succeeded in installing a SlimKat rom this rom doesn't support my provider or something.
Any idea on what I should do next?
Please help me out people, I'm kinda desperate right now :/
ogradish said:
So here's the story
I installed CM11 about a month ago but then decided to revert back to stock, but then again due to short battery life decided to go back to cyanogenmod.
However when I try to install cyanogenmod (even the exact same version as before) on various recoveries (including CMW and Philz) I get the status 7 error. I've already tried to change the code in the updater-script and updating the recovery image, but nothing seems to work. Though I have succeeded in installing a SlimKat rom this rom doesn't support my provider or something.
Any idea on what I should do next?
Please help me out people, I'm kinda desperate right now :/
Click to expand...
Click to collapse
A sidenote
when I use the latest version of CWM and install cm11 it installs perfectly fine, but when booted up the boot animation just goes on for hours and it won't let me get into the rom
ogradish said:
A sidenote
when I use the latest version of CWM and install cm11 it installs perfectly fine, but when booted up the boot animation just goes on for hours and it won't let me get into the rom
Click to expand...
Click to collapse
First you must know to use the latest CWM from CM11 thread or latest TWRP or Philz, second aere you flash the boot.img form fastboot erase cache from fastboot and delete dalvik to
hey guys,
short story: I'm running CM12, nightly from 06/15/15, updated a while ago from CM11 to CM12 and lost recovery. I tried to regain it by flashing a customized kerbel with nuts kernel builder (nut.xperia-files.com). AS a basis, I used the kernel which was running on the device anyway (boot.img). After creating the kernel on nuts page, I flashed it using flashtool.
After this, reboot results in green light, two vibrations and then start of the system (successful). However, still no recovery.
I tried with various nightlies... doesnt help.
Can anyone help me out?
Thanks guys!
guys?
Anyone?
xzd recovery only works with its own busybox framework. Check if you have installed any other busybox. For me this was my problem.
I would recommend you do a clean install then flash the xzdual zip.
EDIT: So it turns out the latest version of Philz touch actually does work, at least after reflashing stock.
The short story: I tried to update from CM11 to CM12 snapshot on 9/1/2015, but every CM based ROM would get stuck at CM boot logo, and this is true with the latest TWRP and latest Philz, along with the snapshot CM recovery provided at the official download page. After downgrading to TWRP 2.6.3.0 at the suggestion of http://forum.xda-developers.com/note-2-sprint/orig-development/rom-cyanogenmod-12-0-t2972922/page32, I got it working.
The long story:
I tried to update to CM12 over the air from CM11. That didn't work, as my philz touch recovery just boot directly back to CM11. It's too quick for me to see the install logs, but there was some error message like "can't install" etc.
So I thought maybe I need a different recovery, since the update notice does say "compatible recovery required" and I saw there is such a recovery in the CM download site.
I flashed cm12.1 snapshot recovery using flashify but I got stuck in a boot loop.
I then flashed the recovery using heimdall and that worked.
I then flashed cm12.1 snapshot using the cm recovery, but that was stuck on the cm logo for at least 4 hours before I shut it down.
I then tried a couple more times and it's the same thing.
I installed other cm11 versions and they all get stuck on the logo (even though I came from cm11).
So I tried a different recovery, the latest version of twrp and long story short it's the same thing with cm roms.
Then I flashed back to philz touch (but I didn't realize that I flashed the latest version) and it's the same thing.
Even after I restored a previous backup, the cm11 rom wouldn't boot up.
At the end I was able to use odin to flash back to stock.
I can also flash rwilco's NE2 based ROM.
I have also tried cyanideL, which is CM12 based and it gets stuck too.
Finally I found the post mentioned above and downgrading to TWRP 2.6.3.0 worked.
Hopefully this post will help someone down the road.
sorcererofdm said:
The short story: I tried to update from CM11 to CM12 snapshot on 9/1/2015, but every CM based ROM would get stuck at CM boot logo, and this is true with the latest TWRP and latest Philz, along with the snapshot CM recovery provided at the official download page. After downgrading to TWRP 2.6.3.0 at the suggestion of http://forum.xda-developers.com/note-2-sprint/orig-development/rom-cyanogenmod-12-0-t2972922/page32, I got it working.
The long story:
I tried to update to CM12 over the air from CM11. That didn't work, as my philz touch recovery just boot directly back to CM11. It's too quick for me to see the install logs, but there was some error message like "can't install" etc.
So I thought maybe I need a different recovery, since the update notice does say "compatible recovery required" and I saw there is such a recovery in the CM download site.
I flashed cm12.1 snapshot recovery using flashify but I got stuck in a boot loop.
I then flashed the recovery using heimdall and that worked.
I then flashed cm12.1 snapshot using the cm recovery, but that was stuck on the cm logo for at least 4 hours before I shut it down.
I then tried a couple more times and it's the same thing.
I installed other cm11 versions and they all get stuck on the logo (even though I came from cm11).
So I tried a different recovery, the latest version of twrp and long story short it's the same thing with cm roms.
Then I flashed back to philz touch (but I didn't realize that I flashed the latest version) and it's the same thing.
Even after I restored a previous backup, the cm11 rom wouldn't boot up.
At the end I was able to use odin to flash back to stock.
I can also flash rwilco's NE2 based ROM.
I have also tried cyanideL, which is CM12 based and it gets stuck too.
Finally I found the post mentioned above and downgrading to TWRP 2.6.3.0 worked.
Hopefully this post will help someone down the road.
Click to expand...
Click to collapse
After flashing back to stock NE2 rom, the nandroid restore from philz_touch worked.
sorcererofdm said:
After flashing back to stock NE2 rom, the nandroid restore from philz_touch worked.
Click to expand...
Click to collapse
Actually, I got CM12 working after flashing CM12 on top of CM11 restored from philz touch after flashing stock. So this is probably more properly called an "upgrade" from CM11 to CM12
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