Hello guys,
In trying to install the latest Android M nightly (20160222) in my Nexus 5 D820 (hammerhead) and it is getting stuck on the boot animation after clean install.
I'm using TWRP version 2.8.7.1.
Latest works fine here.
Using omni-6.0.1-20160311-hammerhead-NIGHTLY without a hitch.
Related
For the Nexus 4 rom: [ROM][AOSP-4.2.1][SR1] OFFICIAL codefireX 4.2 Builds
I used the following Gaaps addon: gapps-jb-20121212-signed.zip for the android 4.2.1 version.
After flashing the rom, it was very smooth, fast, and responsive touch screen. However, after flashing the above Gaaps, via TWRP recovery and booted the phone, the touch screen responsiveness was not that great. Should I have flashed: gapps-4.2-JOP40C-121116.zip the one codefire X provides?? Does that make any difference?
Thanks!
Hi all,
My specs are as follows:
1. Got a Nexus 4 with Android 4.3
2. Did a Sideload update to 4.4 and did not like what I saw )
3. Installed CyanogenMod 10.2 -20131114-SNAPSHOT-InstallerWPPQ46R-Mako via CyanogenMod Installer (screenshot attached)
4. Flashed the 4.3 radio via WUG's Nexus Root Toolkit because I did not have wifi.
I have CWM 6.0.4.3 that came preinstalled with the CM 10.2
I tried to do an update so I flashed the cm-11-20131205-SNAPSHOT-M1-mako.zip and the kitkat gapps via this process:
1. Booted to recovery
2. Wipe Cache
3. Wipe davlik
4. Installed Rom
5. Insalled Gapps
6. Wipe Cache
7. Wipe Davlik
The result was a "beautiful" bootloop. I like the new CM logo BTW )
Reading through some similar threads I came across several pieces of advice:
1. Update the recovery as the verion of recovery that comes with CM 10.2 is unable to flash CM 11.
Is the recovery from here an option?
2. One was to install a fresh version of kitkat and then install CM 11 which I don't fancy
3. Wipe data from device.
Could I get your input on how exactly can I proceed in order to get a fully working version of CM11 on my Nexus4?
Thanks a million
Andrei
Nobody with this problem?
no one has had this issue?
Updated to CM 10.2 Stable
In the meantime I updated to CM 10.2 stable version and also updated recovery to CWM Touch 6.0.4.5 from the link in the first post of this thread. Strangely enough now I am receiving information about update builds, even to the CM11 Snapshot.
As fellow Nexus 4 Users, which do you recommend: TWRP or CWM?
Thanks!
help
andreitudose said:
In the meantime I updated to CM 10.2 stable version and also updated recovery to CWM Touch 6.0.4.5 from the link in the first post of this thread. Strangely enough now I am receiving information about update builds, even to the CM11 Snapshot.
As fellow Nexus 4 Users, which do you recommend: TWRP or CWM?
Thanks!
Click to expand...
Click to collapse
Do you already did it upgrade to "cm11"? if so how did you do?
dan_flo10 said:
Do you already did it upgrade to "cm11"? if so how did you do?
Click to expand...
Click to collapse
Nope, just upgraded today to 10.2.1, the last stable version of cm10, released on the 3rd of Feb. I didn't upgrade to CM11, but when I get bored I will I was on kitkat before and it did not impress...
I think you need to update the baseband
To flash a 4.4 based rom you gonna need :
1-latest selinux compatible recovery.
2-latest bootloader, ver makoz30d .
3-.97 or .98 radio.
Radio and bootloader you can find in googles stock img for mako, extract them and flash via fastboot or find them on xda in a form of flashable zip file.
After all 3 stages you will be able to flash cm11 without a problem, note that a full wipe is highly recommended when coming from 4.3 roms.
Good luck buddy.
Hi all,
I just found my old Nexus 7 (2012 model) in a dresser drawer and decided to bring it up to speed. Currently it is running what appears to be a stock (maybe debloated) 4.4.2 with root and multirom. Recovery is TWRP for multirom. I was using multirom to run Ubuntu just for kicks, but have lost interest in that project, plus it now appears to no longer be supported. Now what I want to do is just flash one of the nougat based roms and call it good. When I try to add nougat as a second rom I get errors relating to E: not existing, it then deletes everything that just started to install. Posts I've seen in other hardware forums point to maybe the install script being wrong for multiboot. Is there any weight to this idea?
I want to run one of the new roms as a secondary first to see how well it works before flashing it for good. Am I missing something stupid here? I haven't messed with any of this stuff since I switched to Verizon and could really use some help.
I don't really need the multiboot option, but since I've gained it I'm a little slow to want to give it back up. Would it be easier for me to just reload the bootloader, recovery, etc, take it back to stock and start over?
Atari-San said:
Is the support of Multiroms dead or do they plan a patch for nougat later when it get more mainstream? I am currently running dirty unicorn 7.0 since I just got my screen and would like to have older build for compatibility issue.
Click to expand...
Click to collapse
If you wan Android 7 on your Nexus 7 2010 you can't use MultiROM: https://forum.xda-developers.com/showthread.php?t=2011403&page=316
Without MultiROM you can use this Android 7 ROM: https://forum.xda-developers.com/nexus-7/development/rom-lineageos-14-1-nexus-7-2012-t3530261
I cannot install madOS_7.1.2_s3_h560_20170605.zip from recovery
https://forum.xda-developers.com/devdb/project/?id=16842#downloads
My phone is a jiayu s3 (3GB version) and I have a twrp 3.1.0 recovery which I later upgraded to 3.1.1-0 because I thought MadOS nougart might require a newer twrp
The installation fails through recovery and I get the message
"updator process ended with signal: 11"
I beleive its a rom issue because I have installed a ressurection remix rom lineage_s3_h560-ota-63473cf184.zip which is the rom running now.
https://forum.xda-developers.com/devdb/project/?id=19675#downloads
I downloaded madOS_7.1.2_s3_h560_20170605.zip many times on both windows and linux but the problem remains
Can the coders look into the issue please ..
Thank you in advance ...
pfavayi said:
I cannot install madOS_7.1.2_s3_h560_20170605.zip from recovery
https://forum.xda-developers.com/devdb/project/?id=16842#downloads
My phone is a jiayu s3 (3GB version) and I have a twrp 3.1.0 recovery which I later upgraded to 3.1.1-0 because I thought MadOS nougart might require a newer twrp
The installation fails through recovery and I get the message
"updator process ended with signal: 11"
I beleive its a rom issue because I have installed a ressurection remix rom lineage_s3_h560-ota-63473cf184.zip which is the rom running now.
https://forum.xda-developers.com/devdb/project/?id=19675#downloads
I downloaded madOS_7.1.2_s3_h560_20170605.zip many times on both windows and linux but the problem remains
Can the coders look into the issue please ..
Thank you in advance ...
Click to expand...
Click to collapse
I had the same issue until I used the correct TWRP mentioned in FAQ of the madOS thread for MTK6572
Sent from my Jiayu S3 using XDA Labs
Hello guys, anyway to boot it on out device? April build booted successfully, buy May builds not working, im stucked on bootlogo... Someone tried?