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.
Related
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.
Hey guys,
I have a problem with my Z1C.
I used CM 12.1 quite a while now and I wanted to know how much difference is to Android 6.
So I downloaded the Remix Resurrection rom and flashed the boot.img in fastboot mode to replace the CM-recovery with TWRP. That was a bit tricky, because CM deleted TWRP again and again and booted in the CM-recovery.
So, finally I got TWRP working, after booting directly into the recovery after flashing the boot.img via fastboot.
TWRP now told me, that no OS is installed. I tried to wipe the phone and to install the RR-rom, but the recovery always said that it has the wrong version (?).
So I flashed the boot.img from the Cyanogenmod-zip and was able to boot into CM again. But now there seems to be no recovery on the phone. Whenever I try to boot to the recovery, the Sony logo appears and the notification light turns into orange, but then it starts again to do so.
At the moment I try to boot into CM again, but I think it has stucked in a bootloop...
What can I do here? The only thing what works is to boot into fastboot mode, but without the system.img I cant flash any roms there. How can I fix this?
Thanks!
Reapy
Reapy1804 said:
Hey guys,
I have a problem with my Z1C.
I used CM 12.1 quite a while now and I wanted to know how much difference is to Android 6.
So I downloaded the Remix Resurrection rom and flashed the boot.img in fastboot mode to replace the CM-recovery with TWRP. That was a bit tricky, because CM deleted TWRP again and again and booted in the CM-recovery.
So, finally I got TWRP working, after booting directly into the recovery after flashing the boot.img via fastboot.
TWRP now told me, that no OS is installed. I tried to wipe the phone and to install the RR-rom, but the recovery always said that it has the wrong version (?).
So I flashed the boot.img from the Cyanogenmod-zip and was able to boot into CM again. But now there seems to be no recovery on the phone. Whenever I try to boot to the recovery, the Sony logo appears and the notification light turns into orange, but then it starts again to do so.
At the moment I try to boot into CM again, but I think it has stucked in a bootloop...
What can I do here? The only thing what works is to boot into fastboot mode, but without the system.img I cant flash any roms there. How can I fix this?
Thanks!
Reapy
Click to expand...
Click to collapse
Shut down your device and press volume up button while connecting it to your computer. Then it will boot into fastboot mode and you should be able to flash stock firmware in flashtool, and then you can start from scratch.
---------- Post added at 06:27 PM ---------- Previous post was at 06:12 PM ----------
Another option is to follow this guide to install Recovery and When done you can boot into Recovery and flash a custom rom. http://forum.xda-developers.com/sony-xperia-z1-compact/general/fota-twrp-recovery-amami-t2909719
Reapy1804 said:
Hey guys,
I have a problem with my Z1C.
I used CM 12.1 quite a while now and I wanted to know how much difference is to Android 6.
So I downloaded the Remix Resurrection rom and flashed the boot.img in fastboot mode to replace the CM-recovery with TWRP. That was a bit tricky, because CM deleted TWRP again and again and booted in the CM-recovery.
So, finally I got TWRP working, after booting directly into the recovery after flashing the boot.img via fastboot.
TWRP now told me, that no OS is installed. I tried to wipe the phone and to install the RR-rom, but the recovery always said that it has the wrong version (?).
So I flashed the boot.img from the Cyanogenmod-zip and was able to boot into CM again. But now there seems to be no recovery on the phone. Whenever I try to boot to the recovery, the Sony logo appears and the notification light turns into orange, but then it starts again to do so.
At the moment I try to boot into CM again, but I think it has stucked in a bootloop...
What can I do here? The only thing what works is to boot into fastboot mode, but without the system.img I cant flash any roms there. How can I fix this?
Thanks!
Reapy
Click to expand...
Click to collapse
Try Rashr app from play store. It sounds to me like incompatible kernel/recovery combo. Download a recovery IMG, (latest TWRP, for example), then use Rashr to flash it. You can also use it for flashing a boot IMG. Its probably the same reason you had trouble flashing ROM.
Besides that, you can install real recovery, which works the same regardless of the kernel-
http://forum.xda-developers.com/xperia-e3/general/bootloader-devices-real-recovery-t3096837
Okay, after flashing it with flashtool it starts again. I now put the RR rom with Android 5.1 on.
I have again the CM recovery, but at least it starts how it should.
I will try to flash the real recovery, thanks!
Update:
Currently running RR with Android 5.1.
I would now like to use RR with Android 6, but again, I can only boot into the Cyanogen recovery, which cant make a backup of the currently running OS. I have tried to flash the boot.img from RR 5.1 with fastboot, Rashr, but nothing seems to work, as it puts me back to the Cyanogen recovery every time. How can I replace the Cyanogen recovery?
And one more question: When the phone starts, the notification light turns into red before the Sonmy logo appears and then turns into pink. What does the red light mean?
Reapy1804 said:
Update:
Currently running RR with Android 5.1.
I would now like to use RR with Android 6, but again, I can only boot into the Cyanogen recovery, which cant make a backup of the currently running OS. I have tried to flash the boot.img from RR 5.1 with fastboot, Rashr, but nothing seems to work, as it puts me back to the Cyanogen recovery every time. How can I replace the Cyanogen recovery?
And one more question: When the phone starts, the notification light turns into red before the Sonmy logo appears and then turns into pink. What does the red light mean?
Click to expand...
Click to collapse
You need a recovery img, not boot img. Try this one - http://forum.xda-developers.com/showpost.php?p=65361797&postcount=78 or this one - http://forum.xda-developers.com/sony-xperia-z1-compact/general/fota-twrp-recovery-amami-t2909719 Open Rashr, choose ' recovery from storage'.
Okay, i flashed the 2.8.6.0 version via Rashr and now Im stuck on the Sony logo...the notification light is orange all the time, but I cant restart the phone anymore...any suggestions?
Edit: Worked! Used the combination between power and Vol+ to reset, and now it starts!
You should disable CM Recovery Protection – On your phone go to Settings > Developer options. Then disable the ‘Update recovery with system updates’ option. Otherwise it will keep installing cm recovery itself.
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.
May want to check out http://forum.xda-developers.com/oneplus-3/help/boot-recovery-cm14-1-nightly-official-t3497425 thread.
thanks i will try this
i checked it out and will try it as soon as i can
Same question over and over again
Dude on same page you got answer just USE EYS
Hello, I flashed CM14 Nougat 7.1.1 and everything worked fine until I tried to boot into recovery to get access to TWRP. If I try and boot into recovery I get the 1+ logo and then just a black screen and i have to hard reboot the phone to use it again. After the hard reboot it just goes back to nougat. I downloaded the TWRP APK to try and restore my previous save but it just does the same thing.
Can anyone help?
Thank you.
I get the same problem. This is WHY we should BACKUP it first. but I didd't, and so are you. I was having lots of works and did not check much news about CM for a long time. but yes, I get the rumors about CM getting shut down. and I check the news. Today I found out CM is shutting down, and my phone is not working.
But, hey, who am I. OnePlus 3 User with lots of experience.
So I tried CM recovery, the newest version works, but there is no backup option, I tried old CM13 recovery. it also black screen. This confirm my theory, this is due to Android 7.1 or CM14.1 upgrade
How to solve this problem?
I found this
https://forum.xda-developers.com/oneplus-3/development/rom-hydrogenos-h2os-beta-edition-oct-t3482259
go to this thread, and download modified TWRP.
BACKUP.
Install your new ROM via any XDA rom. not the CM14.1 build on Dec 25.
Note: If you want Android 7.xx, you could flash the Official Beta ROM(above), or download modem from
https://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628
Happy New Year.
YungKremer said:
Hello, I flashed CM14 Nougat 7.1.1 and everything worked fine until I tried to boot into recovery to get access to TWRP. If I try and boot into recovery I get the 1+ logo and then just a black screen and i have to hard reboot the phone to use it again. After the hard reboot it just goes back to nougat. I downloaded the TWRP APK to try and restore my previous save but it just does the same thing.
Can anyone help?
Thank you.
Click to expand...
Click to collapse
boot into fastboot mode and give following commands
fastboot erase recovery
fastboot flash recovery twrp-xxxx.img
now reboot to recovery...
Please confirm if this works
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