Related
Can any one help me try to get cm11 on my verizon note 3. I have TWRP and Unlocked Bootloader with root running CM13 but I still want to run cm11 and when I tried to flash the rom, it gave me a updater 7 error. If you know a way to fix this please tell me.
lootrooter said:
Can any one help me try to get cm11 on my verizon note 3. I have TWRP and Unlocked Bootloader with root running CM13 but I still want to run cm11 and when I tried to flash the rom, it gave me a updater 7 error. If you know a way to fix this please tell me.
Click to expand...
Click to collapse
Error 7 is typically a mismatch condition between the fingerprint of the recovery in use and the model of the phone the ROM is intended for - the ROM author puts an "assert" statement in the installer script to prevent dummies from flashing a ROM from the wrong device to a phone.
Assuming you didn't make a mistake downloading the wrong cm rom for the SM-N900V Note 3 this could be a "hlte" vs "hltevzw" issue depending on which TWRP version you have installed.
You can work around this by unpacking the ROM .zip file, deleting the offending "assert" line in the installer script, and red zipping the ROM.
bftb0 said:
Error 7 is typically a mismatch condition between the fingerprint of the recovery in use and the model of the phone the ROM is intended for - the ROM author puts an "assert" statement in the installer script to prevent dummies from flashing a ROM from the wrong device to a phone.
Assuming you didn't make a mistake downloading the wrong cm rom for the SM-N900V Note 3 this could be a "hlte" vs "hltevzw" issue depending on which TWRP version you have installed.
You can work around this by unpacking the ROM .zip file, deleting the offending "assert" line in the installer script, and red zipping the ROM.
Click to expand...
Click to collapse
It was just a "hlte" vs "hltevzw" error, thanks
Did you get CM11 working?
Sent from my SM-N900V using Tapatalk
Old 4.4 rom on new vzw bootloader
bishop0114 said:
Did you get CM11 working?
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
I did and c-rom. Which i love. But with both of them lte data goes in and out. I've tried a bunch of things but can't figure it out. It's weird editing apns causes them to be deleted. Any ideas anyone?
how to install
themrgoats said:
I did and c-rom. Which i love. But with both of them lte data goes in and out. I've tried a bunch of things but can't figure it out. It's weird editing apns causes them to be deleted. Any ideas anyone?
Click to expand...
Click to collapse
can tell me how did u installed it? i am getting ERROR : 7 in TWRP , cm-11-20160612-NIGHTLY-hltevzw.zip (223.82 MB)
Rooted 0B6 then Unlocked Bootloader.
dat ka said:
can tell me how did u installed it? i am getting ERROR : 7 in TWRP , cm-11-20160612-NIGHTLY-hltevzw.zip (223.82 MB)
Rooted 0B6 then Unlocked Bootloader.
Click to expand...
Click to collapse
TWRP error 7 typically means you're trying to install the zip onto the wrong device.
Sent from my SM-N900V using Tapatalk
Yes if you are using the hltevzw twrp then just flash the hlte generic twrp and u can flash roms that don't require the hltevzw twrp to see the right rom is version is being flashed.
One more question , i am running JasmineRom its 5.0.x CM 11 is 4.x.x Will it work? if i install it?
dat ka said:
One more question , i am running JasmineRom its 5.0.x CM 11 is 4.x.x Will it work? if i install it?
Click to expand...
Click to collapse
I don't think so but was wondering since we have an unlocked bootloader, can we downgrade to a developer 4.4.2 rom and then install the cm11?
Sent from my SM-N900V using Tapatalk
Hello everyone,
I'm currently using this ROM : http://forum.xda-developers.com/zenfone-5/development/rom-resurrection-remix-mm-5-6-7-t3357331
Is there any method on how to return back to the stock ROM ?
If I just do a full wipe and flash the latest update, will it work ?
thanks
Angristan said:
Hello everyone,
I'm currently using this ROM : http://forum.xda-developers.com/zenfone-5/development/rom-resurrection-remix-mm-5-6-7-t3357331
Is there any method on how to return back to the stock ROM ?
If I just do a full wipe and flash the latest update, will it work ?
thanks
Click to expand...
Click to collapse
Flash stock .78 via twrp do not ask why then manually update to .87. Then flash stock recovery and relock bootloader. Done
Sent from my ASUS_T00J using Tapatalk
ZeeJcG said:
Flash stock .78 via twrp do not ask why then manually update to .87. Then flash stock recovery and relock bootloader. Done
Sent from my ASUS_T00J using Tapatalk
Click to expand...
Click to collapse
Thanks I'll try that.
I can't flash, it says "Only Android 4.4.3/Android 5.0 2015 [...] image version could upgrade with this package", and i'm on 6.0.1
Anyone knows how to go back to stock ROM ?
Angristan said:
Anyone knows how to go back to stock ROM ?
Click to expand...
Click to collapse
Flash this in twrp : UL-ASUS_T00F-WW-3.24.40.78-user.zip
after that manually update to .87
how to ?
download .87 firmware put to your Internal Storage
or directly flash .87 in TWRP here:
.87 flashable
milano88 said:
Flash this in twrp : UL-ASUS_T00F-WW-3.24.40.78-user.zip
after that manually update to .87
how to ?
download .87 firmware put to your Internal Storage
or directly flash .87 in TWRP here:
.87 flashable
Click to expand...
Click to collapse
Yeah basically that's what @ZeeJcG said before ^^'
So anyway that was pretty hard I downgraded with WW_5.2.2.2 (flashing fastboot/recovery) and WW_5.3.3.3, I was in 2.21, and then upgraded the classic way, yolo
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
when the LinageOS version on the Chinese model guys?((
If you manage to get for us the N files needed or someone who has the Nougat files , we can work something out. Otherwise till Chinese variant release the Full N Update.
DrakenFX said:
If you manage to get for us the N files needed or someone who has the Nougat files , we can work something out. Otherwise till Chinese variant release the Full N Update.
Click to expand...
Click to collapse
uhm, there are some builds based around the old tree, that should work.
https://forum.xda-developers.com/axon-7/development/rom-nello-t3495844
http://www.cyanogenmods.org/forums/topic/zte-axon-7-lineage-14-1-nougat-7-1-rom/
MaxRink said:
uhm, there are some builds based around the old tree, that should work.
https://forum.xda-developers.com/axon-7/development/rom-nello-t3495844
http://www.cyanogenmods.org/forums/topic/zte-axon-7-lineage-14-1-nougat-7-1-rom/
Click to expand...
Click to collapse
NOPE, all those trees are base in MM sources ... @Unjustified Dev lineage. Is base in FULL N
DrakenFX said:
NOPE, all those trees are base in MM sources ... @Unjustified Dev lineage. Is base in FULL N
Click to expand...
Click to collapse
Uhm, thats exactly what i wrote.
nevertheless they do work on the A2017 right now but are by far not as bugfree as UJDs N-tree-based build
hi,guys.This is my extract the files of N.
http://pan.baidu.com/s/1mhVJs9a
http://pan.baidu.com/s/1mhVJs9a
It's the complete N upgrade package, I hope to help you.
http://pan.baidu.com/s/1hrFC2hA
http://pan.baidu.com/s/1hrFC2hA
Perhaps download speed is slow, I hope you can have a way.
Thank you for your work.
DrakenFX said:
If you manage to get for us the N files needed or someone who has the Nougat files , we can work something out. Otherwise till Chinese variant release the Full N Update.
Click to expand...
Click to collapse
hi,guys.This is my extract the files of N.
http://pan.baidu.com/s/1mhVJs9a
http://pan.baidu.com/s/1mhVJs9a
It's the complete N upgrade package, I hope to help you.
http://pan.baidu.com/s/1hrFC2hA
http://pan.baidu.com/s/1hrFC2hA
Perhaps download speed is slow, I hope you can have a way.
Thank you for your work.
DrakenFX said:
If you manage to get for us the N files needed or someone who has the Nougat files , we can work something out. Otherwise till Chinese variant release the Full N Update.
Click to expand...
Click to collapse
I upload N updates to Google cloud disk.
https://drive.google.com/file/d/0B3DK6lUODGKeUHlhWGFocDRXcm8/view?usp=sharing
savior333 said:
I upload N updates to Google cloud disk.
https://drive.google.com/file/d/0B3DK6lUODGKeUHlhWGFocDRXcm8/view?usp=sharing
Click to expand...
Click to collapse
:good: Thank you, will look into it :good:
Out of curiosity, is this the official N update?
ultramag69 said:
Out of curiosity, is this the official N update?
Click to expand...
Click to collapse
from what i can see, this is probably the OTA use to update from MM to N in the chinese variant. so meaning you must be in the software require to be able to update from MM to N using this file.
still there is a few partitions i'll need to create a Stack for the Chinese variant, cuz here in this zip they are in a form of Patch and not full.
Can someone port this for TWRP for chinese version?
DrakenFX said:
from what i can see, this is probably the OTA use to update from MM to N in the chinese variant. so meaning you must be in the software require to be able to update from MM to N using this file.
still there is a few partitions i'll need to create a Stack for the Chinese variant, cuz here in this zip they are in a form of Patch and not full.
Click to expand...
Click to collapse
Yep, I'm on B13 (A2017) so thought I'd give it a shot...
I'll let you know if I was successfulor not....
Apparently not the upgrade from B13 (MM) as it isn't detected as an upgrade file by my Chinese A2017...
DrakenFX said:
from what i can see, this is probably the OTA use to update from MM to N in the chinese variant. so meaning you must be in the software require to be able to update from MM to N using this file.
still there is a few partitions i'll need to create a Stack for the Chinese variant, cuz here in this zip they are in a form of Patch and not full.
Click to expand...
Click to collapse
Hi,This would be useful.It is aosp N with base function from zte.
https://drive.google.com/file/d/0B3DK6lUODGKeREhEdDk0R2xTQTQ/view?usp=sharing
savior333 said:
Hi,This would be useful.It is aosp N with base function from zte.
...
Click to expand...
Click to collapse
Could I ask you some questions please?
I installed this package and this seemed to change something in the bootloader. I can boot up, use my device with no bugs. But I can't enter bootloader.
Trying to flash twrp recovery from EDL caused me a soft brick. After that I can't even enter recovery.
Then I managed to flash the recovery.img, extracted from your pakage.
Now I want to go back the stock Zte 6.0 rom. But the recovery cant flash the update.zip, which I got from zte china website. It said that my device had a blank "ro.product.device". Trying the DrakenFx system zip failed the verification.
Could you please guide me how to go back? This rom has root app but press Root button does nothing. And I cant enable OEM unlock under Developer Option.
Thank you in advance.
ultramag69 said:
Out of curiosity, is this the official N update?
Click to expand...
Click to collapse
probably a BETA I don't think official N is out yet
quanlop93 said:
Could I ask you some questions please?
I installed this package and this seemed to change something in the bootloader. I can boot up, use my device with no bugs. But I can't enter bootloader.
Trying to flash twrp recovery from EDL caused me a soft brick. After that I can't even enter recovery.
Then I managed to flash the recovery.img, extracted from your pakage.
Now I want to go back the stock Zte 6.0 rom. But the recovery cant flash the update.zip, which I got from zte china website. It said that my device had a blank "ro.product.device". Trying the DrakenFx system zip failed the verification.
Could you please guide me how to go back? This rom has root app but press Root button does nothing. And I cant enable OEM unlock under Developer Option.
Thank you in advance.
Click to expand...
Click to collapse
1. Why did you installed this package?
2. Did you have the device for this package?
3. Did someone told you was OK to flash this package?
4. Which variant to you use.
@savior333
Got the file, I'll check today and see if N stack can be done for LineageOS. Thanks again
DrakenFX said:
1. Why did you installed this package?
2. Did you have the device for this package?
3. Did someone told you was OK to flash this package?
4. Which variant to you use.
...
Click to expand...
Click to collapse
1. I just cant stand the Mifavor anymore so I take the risk and install it.
3. Nobody told me it was OK to flash it. But in the end my device boot up and run flawlessly.
2. and 4. I have the A2017 4G/64Gb Chinese variant.
Curiosity cant kill my device but it leaves me no way back.....
Ps: As I looked into the build.prop inside the official A2017 B11 package and this pakage, I saw the stock has "ro.product.name=P996A03" while the N pakage has "ro.product.name=P996A03_N"
quanlop93 said:
Could I ask you some questions please?
I installed this package and this seemed to change something in the bootloader. I can boot up, use my device with no bugs. But I can't enter bootloader.
Trying to flash twrp recovery from EDL caused me a soft brick. After that I can't even enter recovery.
Then I managed to flash the recovery.img, extracted from your pakage.
Now I want to go back the stock Zte 6.0 rom. But the recovery cant flash the update.zip, which I got from zte china website. It said that my device had a blank "ro.product.device". Trying the DrakenFx system zip failed the verification.
Could you please guide me how to go back? This rom has root app but press Root button does nothing. And I cant enable OEM unlock under Developer Option.
Thank you in advance.
Click to expand...
Click to collapse
sorry,you should not flash this rom.if you want back,need a special package.wait for me upload.
savior333 said:
sorry,you should not flash this rom.if you want back,need a special package.wait for me upload.
Click to expand...
Click to collapse
Thank you very much. I thought I have to live with this forever and you save me.
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