Hello !
I'm actually on PureNexus (primary rom) and i installed multirom.
I tried to add DP4 rom (as secondary rom) 2 times:
- first time with the all-in-one zip file -> the phone is stuck on Google logo
- second time with a backup of DP4 that i've made earlier -> the phone is also stuck on Google logo
maybe i've missed something... Can someone help me ?
Raiden350 said:
Hello !
I'm actually on PureNexus (primary rom) and i installed multirom.
I tried to add DP4 rom (as secondary rom) 2 times:
- first time with the all-in-one zip file -> the phone is stuck on Google logo
- second time with a backup of DP4 that i've made earlier -> the phone is also stuck on Google logo
maybe i've missed something... Can someone help me ?
Click to expand...
Click to collapse
I learned through casual reading of the Multirom thread that developer previews must be flashed to primary then moved to secondary
Sent from my Nexus 5X using Tapatalk
Ok, i did it, i reflash Android N factory image, then Multirom and i add PureNexus as secondary rom.
Now Android N rom is booting fine, but it's PureNexus which is stuck at Google logo... Also tried with Uberstock rom, same result.
I don't understand why the secondary rom never boot...
Raiden350 said:
Ok, i did it, i reflash Android N factory image, then Multirom and i add PureNexus as secondary rom.
Now Android N rom is booting fine, but it's PureNexus which is stuck at Google logo... Also tried with Uberstock rom, same result.
I don't understand why the secondary rom never boot...
Click to expand...
Click to collapse
You must flash the Marshmallow Vendor that matches your Marshmallow roms before booting them. Have you been doing so? You must also flash the Android N vendor before booting into developer previews.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
You must flash the Marshmallow Vendor that matches your Marshmallow roms before booting them. Have you been doing so? You must also flash the Android N vendor before booting into developer previews.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
No i don't... Okay, so if I flash marshmallow vendor, it will be fine ? Or i have to flash MM vendor each time i want to boot in this rom ??
Raiden350 said:
No i don't... Okay, so if I flash marshmallow vendor, it will be fine ? Or i have to flash MM vendor each time i want to boot in this rom ??
Click to expand...
Click to collapse
Yes it should. Each time you switch between MM and N, you must flash the Vendor that matches that MM or N rom. You don't have to do this between MM roms
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Yes it should. Each time you switch between MM and N, you must flash the Vendor that matches that MM or N rom. You don't have to do this between MM roms
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Oh really ? So annoying But thanks a lot for your help !
Raiden350 said:
Oh really ? So annoying But thanks a lot for your help !
Click to expand...
Click to collapse
Lol yes it is but it's only a slight annoyance since you can flash the vendor.img while in TWRP or MR-TWRP as well before booting up. I do encourage you to follow the MultiRom thread just to be aware of subtleties like this
http://forum.xda-developers.com/showthread.php?t=3313291
Sent from my Nexus 5X using Tapatalk
Related
Cyanogen OS 13.0.1 (6.0.1) cm-13.1-ZNH2KAS254-bacon-signed-fastboot-d194f46bee.zip 373e43912bf45a2dccdb37db78377b12
Cyanogen OS 13.0.1 (6.0.1) cm-13.1-ZNH2KAS254-bacon-signed-9fbe6186fd.zip d90c5f3258eeef9cf440ab50983ca943
Cyanogen OS 13.0.1 (6.0.1) cm-13.1-ZNH2KAS254-bacon-boot-debuggable-b988e25b87.img 8a478404685f3304ab831eb077c6806b
See also link - https://cyngn.com/support
Thanks. Anyone know if there's a new modem included with this update? Or still the same old one from a long time ago?
arh2o said:
Thanks. Anyone know if there's a new modem included with this update? Or still the same old one from a long time ago?
Click to expand...
Click to collapse
No, there's no new modem, hence many of the Bluetooth issues (such as interfering the 2.5Ghz wif band) are still present.
works like a charm ! thank you (dirty flashed over previous rooted build)
Can I flash it with TWPR? And if yes, which zip?
klubipiff said:
Can I flash it with TWPR? And if yes, which zip?
Click to expand...
Click to collapse
Yes. Signed zip i.e. second one.
cm-13.1-ZNH2KAS254-bacon-signed-9fbe6186fd.zip
I I'm having difficulty flashing with TWPR. I keep getting code 7.
Sent from my A0001 using XDA-Developers mobile app
bmttinman said:
I I'm having difficulty flashing with TWPR. I keep getting code 7.
Sent from my A0001 using XDA-Developers mobile app
Click to expand...
Click to collapse
You need to use official Cyanogen recovery to flash stock images, you can flash back TWRP later if you want. But it will break automatic updating of OTAs in the future.
[QUESTION] [HELP]Hey guys im A nOob here tried to install cm13 on my asus ze550kl but im stuck on boot logo
I faced unable to mount data and storage on twrp but i solved it by myself doing formatting
But i cant startup my phone now please solve
Thanks
Were you on stock marshmallow before flashing cm13? If not, go back to stock, update to marshmallow and try to install twrp and cm13 again. There was an easy way to fix this but I cant find the link here in xda. Make sure you have unlocked bootloader.
Hey guys...I've already unbricked my phone by reverting to 6.0.1
I had unlocked bootloader but i think it didnt work or may b some problem there
Finally i flashed 1877 recovery + boot + firmware
N saved my phone
Vickysoni3 said:
[QUESTION] [HELP]Hey guys im A nOob here tried to install cm13 on my asus ze550kl but im stuck on boot logo
I faced unable to mount data and storage on twrp but i solved it by myself doing formatting
But i cant startup my phone now please solve
Thanks
Click to expand...
Click to collapse
This problem arises due to the fact that, you have enabled device protection on stock Marshmallow.
To remove this, just remove the Google account and secure lockscreen(pattern/password/pin) on your device and try again.
It works.
Thanks dude
I will surely remember this next time
?
Sent from my ASUS_Z00LD using Tapatalk
Vickysoni3 said:
Thanks dude
I will surely remember this next time
Sent from my ASUS_Z00LD using Tapatalk
Click to expand...
Click to collapse
Glad. Enjoy your new ROM
Guyz zip for zen pixel camera?
Vickysoni3 said:
Guyz zip for zen pixel camera?
Click to expand...
Click to collapse
Just download the Asus Pixelmaster Camera app from PlayStore.
Okay dude.. I tried a zip but failed to install
Hello XDA
Since @Blueblob stopped his work with the vendor-images I thought I could pick it up
I have unpacked and uploaded the vendor image from google images, I havent touched anything on it.
Download and flash image in twrp/recovery of pref.
Updated 02.05.17
Bootloader
Radio
Vendor
Flash at your own risk.
Thanks Google
@LoverBoy2415 is this something for your index post?
Also I hope this is ok for the mods to stay up.
Stopped because TWRP can flash .img
Thanks for mirror ?
Envoyé de mon Nexus 5X en utilisant Tapatalk
[BUMP] Updated 02.05.17
Updated with vendor, bootloader and radio for May
[BUMP] Updated 06.06.17
New vendor image uploaded, radio and bootloader is same as last month
[BUMP] Updated 08.07.17
Updated the vendor image, radio and bootloader is same as before
[BUMP] Updated 08.08.17
Uploaded with latest, still same radio and boot as before
[BUMP] Updated 14.09.17
Updated with Android 8 (Oreo) images
Nothing for Android 7.x
bjorn96 said:
Updated with Android 8 (Oreo) images
Nothing for Android 7.x
Click to expand...
Click to collapse
So the sep vendor image won't work on 7.1.2?
Sent from my LG Nexus 5X using XDA Labs
Skittles9823 said:
So the sep vendor image won't work on 7.1.2?
Click to expand...
Click to collapse
Nope.
bjorn96 said:
Nope.
Click to expand...
Click to collapse
Okay. Thanks for the speedy response.
Sent from my LG Nexus 5X using XDA Labs
hey everyone,
I recently purchased a used Nexus 5x that is running fine so far. my only problem is i get the message "internal problem, contact manufacturer" after every boot.
the phone is running android 7.0 (NDR90S) and the seller told me he trie to root and flash custom firmware but somehow the boot loader always locked itself. Now its not possible to perform an OTA update to 8.0 (get it offered all the time).
According to the developer setting the Bootloader is unlocked. I read that it should be fine to flash the vendor.image. Is this correct so far?
laspecas said:
hey everyone,
I recently purchased a used Nexus 5x that is running fine so far. my only problem is i get the message "internal problem, contact manufacturer" after every boot.
the phone is running android 7.0 (NDR90S) and the seller told me he trie to root and flash custom firmware but somehow the boot loader always locked itself. Now its not possible to perform an OTA update to 8.0 (get it offered all the time).
According to the developer setting the Bootloader is unlocked. I read that it should be fine to flash the vendor.image. Is this correct so far?
Click to expand...
Click to collapse
You may want to do a full firmware flash. Simply get the latest firmware image from googles website for this device and run the installer script that comes with it. You'll be wiped clean and hopefully any issues are fixed. (You'll need to unlock the bootloader again if you plan to root or flash custom roms).
Sent from my Nexus 5X using XDA Labs
First i unlocked the bootloader
Second i flashed twrp.
Thirdly i flashed ElementalX-G4-2.01 and thn supersu
Now the phone is not booting atall only black screen is there any resolution or did i make any wrong flash please let me know but still i can access twrp.
Btw My phone is running on Android 7.0 and twrp 3.2.1.0
I tried google and all still no resolution.
Now i tried custom roms as well still same not booting up atall.
Akshaykoppula said:
First i unlocked the bootloader
Second i flashed twrp.
Thirdly i flashed ElementalX-G4-2.01 and thn supersu
Now the phone is not booting atall only black screen is there any resolution or did i make any wrong flash please let me know but still i can access twrp.
Btw My phone is running on Android 7.0 and twrp 3.2.1.0
I tried google and all still no resolution.
Now i tried custom roms as well still same not booting up atall.
Click to expand...
Click to collapse
Have you tried to wipe caches too? I guess your referring to https://forum.xda-developers.com/mo...g4-plus-supersu-android-t3587918/post71817560 right?
strongst said:
Have you tried to wipe caches too? I guess your referring to https://forum.xda-developers.com/mo...g4-plus-supersu-android-t3587918/post71817560 right?
Click to expand...
Click to collapse
i have tried now it seems working thanks. But custom rom having too many issues with diffrent kernel
can u suggest the official moto or any stable rom with kernel.
Akshaykoppula said:
i have tried now it seems working thanks. But custom rom having too many issues with diffrent kernel
can u suggest the official moto or any stable rom with kernel.
Click to expand...
Click to collapse
Official ressurection remix is very good, or stock rom.
I went thru every single thread, i have the latest TWRP 3.2.1, so no Error 7.
The ROM's install (i've tried Unofficial/RR/PixelExperience/BootLeggers/Cosmic/AOSIP) and the install goes smooth, but all stuck on Bootloop!
What on earth am I doing wrong? I can't find anyone mentioning specific Kernel or where to get an OREO specific Kernel.
Is there a Boot.img ? do i need to flash it as well? (no one says so in instructions)
The last rom i've got is the Official 7.1.2 which boots without a problem.
Note: But only the 20171025 build, nothing after that even of 7.1.2 doesn't boot (just has bootloop)
Device Specs as Appear on the back: YU4711, H/W ver V2.0, S/W ver: V0.0.9_171215, (2+8) GB
Have you updated the modem from cyanogen 14.0 then try again.
BTW you should made in discussion.
Flash your Phone with stock ROM
YU_YU4711_SW_V0.0.9_HW_V1.0_171215_2016012715.zip .
This can resolve your problem.
The AndroidGuy said:
Have you updated the modem from cyanogen 14.0 then try again.
BTW you should made in discussion.
Click to expand...
Click to collapse
I didn't know there is a new Modem from CM14, do you have a link or a name?
RoHiTkUmArShArMa said:
Flash your Phone with stock ROM
YU_YU4711_SW_V0.0.9_HW_V1.0_171215_2016012715.zip .
This can resolve your problem.
Click to expand...
Click to collapse
I'm sorry, but why on earth would I want to put my phone back on v5.1.1 ?
Sefy said:
I'm sorry, but why on earth would I want to put my phone back on v5.1.1 ?
Click to expand...
Click to collapse
It have some other files also including android 5... So flash this
And then flash twrp
Reflash the entire stock firmware *except system, userdata, recovery, cache* through fastboot, then you should be good to go.
ask in Q/A thread
RoHiTkUmArShArMa said:
It have some other files also including android 5... So flash this
And then flash twrp
Click to expand...
Click to collapse
I honestly don't see the logic in putting the phone back into Stock ROM of Android 5.1.1, when I can use it with 7.1.2 without a problem and only flashing of new ROM's is an issue.
But I have found something that may give more information, this is HW_V2 , so i'm assuming this device is the YU YUNIQUE 2 which is basically identical but with 2GB ram instead of 1GB ram.
Sefy said:
I honestly don't see the logic in putting the phone back into Stock ROM of Android 5.1.1, when I can use it with 7.1.2 without a problem and only flashing of new ROM's is an issue.
But I have found something that may give more information, this is HW_V2 , so i'm assuming this device is the YU YUNIQUE 2 which is basically identical but with 2GB ram instead of 1GB ram.
Click to expand...
Click to collapse
Can you able to boot into official LineageOS without editing updater-script?
The AndroidGuy said:
Can you able to boot into official LineageOS without editing updater-script?
Click to expand...
Click to collapse
As I mentioned, I can boot into 7.1.2 (that's LineageOS), but the latest i'm able to boot is 25/10/2017 and any build after, goes into bootloop.
Sefy said:
As I mentioned, I can boot into 7.1.2 (that's LineageOS), but the latest i'm able to boot is 25/10/2017 and any build after, goes into bootloop.
Click to expand...
Click to collapse
Maybe it is time to change device.
The AndroidGuy said:
Maybe it is time to change device.
Click to expand...
Click to collapse
Right....
I resolved the issue after way too much digging around, the issue was flashing the specific NON-HLOS.bin and now I can flash v8.x and v9.x roms
The one that resolved my issue came from this link: https://androidfilehost.com/?fid=817550096634760193
Help me
Can you tell me how to use this file plzz and thnx for solving this prb @Sefy
wise7709 said:
Can you tell me how to use this file plzz and thnx for solving this prb @Sefy
Click to expand...
Click to collapse
You need to flash it using: fastboot flash modem non-hls.bin
Then reboot and flashing of the ROM should go correctly and for me atleast, it booted up.