Database Users

This package is for d801 devices; this is a g2.

I am trying to install Cyanogenmod 11 or 10.2 on my T-Mobile LG G2 (D801), because I do not like the stock ROM.
When I try flashing the Cyanogenmod package, it says "This package is for d801 devices; this is a g2."
A d801 is a g2. What is wrong here?

Hypersonic1 said:
I am trying to install Cyanogenmod 11 or 10.2 on my T-Mobile LG G2 (D801), because I do not like the stock ROM.
When I try flashing the Cyanogenmod package, it says "This package is for d801 devices; this is a g2."
A d801 is a g2. What is wrong here?
Click to expand...
Click to collapse
Hugh... That's weird lol...

Hypersonic1 said:
I am trying to install Cyanogenmod 11 or 10.2 on my T-Mobile LG G2 (D801), because I do not like the stock ROM.
When I try flashing the Cyanogenmod package, it says "This package is for d801 devices; this is a g2."
A d801 is a g2. What is wrong here?
Click to expand...
Click to collapse
Sounds like something is messed up with your build.prop. Assuming that you have adb set up, can you run "adb pull /system/build.prop *a folder on your hard drive*" and upload the file?

jellopuddingstick said:
Sounds like something is messed up with your build.prop. Assuming that you have adb set up, can you run "adb pull /system/build.prop *a folder on your hard drive*" and upload the file?
Click to expand...
Click to collapse
http://pastebin.com/YaE3mi9k

jellopuddingstick said:
Sounds like something is messed up with your build.prop. Assuming that you have adb set up, can you run "adb pull /system/build.prop *a folder on your hard drive*" and upload the file?
Click to expand...
Click to collapse
you have no idea what your talking about dude... he's flashing a different ROM Build.prop has nothing to do with it.
OP how are u flashing the rom?

G1_enthusiast said:
you have no idea what your talking about dude... he's flashing a different ROM Build.prop has nothing to do with it.
OP how are u flashing the rom?
Click to expand...
Click to collapse
Allow me to explain your error. The first step of CyanogenMod's updater-script checks the phone's build.prop to ensure device compatibility, specifically the line ro.product.device. This should be the model number, d800, d801, vs980, etc. For whatever reason his device's build.prop has the value set to "g2".
To OP: You can either edit that line in your build.prop to say "ro.product.device=d801" or you could remove the check from the updater-script. Any ideas why this value would have been changed, though?

jellopuddingstick said:
Allow me to explain your error. The first step of CyanogenMod's updater-script checks the phone's build.prop to ensure device compatibility, specifically the line ro.product.device. This should be the model number, d800, d801, vs980, etc. For whatever reason his device's build.prop has the value set to "g2".
To OP: You can either edit that line in your build.prop to say "ro.product.device=d801" or you could remove the check from the updater-script. Any ideas why this value would have been changed, though?
Click to expand...
Click to collapse
build.prop is for system UI only, if you are in recovery, none of that matter...I flashed D802 on my D801 all the time....matter of fact i'm using ATT rom on my Tmobile D801 right now.
OP you are doing something wrong how are u flashing the fliles?
P.S do not edit build.prop files until you figure out what you did wrong. or else your phone will soft brick and it will be a pain to recover it if you dont know what your doing and especially if you dont have TWRP installed.

G1_enthusiast said:
build.prop is for system UI only, if you are in recovery, none of that matter...I flashed D802 on my D801 all the time....matter of fact i'm using ATT rom on my Tmobile D801 right now.
OP you are doing something wrong how are u flashing the fliles?
Click to expand...
Click to collapse
As you can see in this line:
Code:
assert(getprop("ro.product.device") == "d801" || getprop("ro.build.product") == "d801" || abort("This package is for \"d801\" devices; this is a \"" + getprop("ro.product.device") + "\"."););
Flashing the CM zip first gets the build.prop file, and checks the values of ro.product.device and ro.build.product, and if those both fail, then it issues the exact error OP is describing.
EDIT: Did a little further investigation, it seems that the ATT's script allows ro.product.device to be either d800, g2, or galbi. Which would explain how G1_enthusiast has been able to flash the ATT ROM on his Tmobile. The Tmobile ROM, however, required it be equal to d801. Thus, OP's error. My advice is the same as before: either edit the updater-script or your build.prop

jellopuddingstick said:
As you can see in this line:
Code:
assert(getprop("ro.product.device") == "d801" || getprop("ro.build.product") == "d801" || abort("This package is for \"d801\" devices; this is a \"" + getprop("ro.product.device") + "\"."););
Flashing the CM zip first gets the build.prop file, and checks the values of ro.product.device and ro.build.product, and if those both fail, then it issues the exact error OP is describing.
Click to expand...
Click to collapse
I'm standing by what I said, I never seen a flash failed because of the wrong input in build.prop, if thats the case then there would be no such thing as Hard brick on android phones.
I'm willing to say this guy has not even install TWRP or CWM and he flashing it via Flashify or some other weird ways. if thats the case then you might be right.

G1_enthusiast said:
build.prop is for system UI only, if you are in recovery, none of that matter...I flashed D802 on my D801 all the time....matter of fact i'm using ATT rom on my Tmobile D801 right now.
OP you are doing something wrong how are u flashing the fliles?
P.S do not edit build.prop files until you figure out what you did wrong. or else your phone will soft brick and it will be a pain to recover it if you dont know what your doing and especially if you dont have TWRP installed.
Click to expand...
Click to collapse
I have TWRP installed. I am using the Install button.

Hypersonic1 said:
I have TWRP installed. I am using the Install button.
Click to expand...
Click to collapse
have you flash other roms before or this is the first time you doing it?

G1_enthusiast said:
I'm standing by what I said, I never seen a flash failed because of the wrong input in build.prop, if thats the case then there would be no such thing as Hard brick on android phones.
I'm willing to say this guy has not even install TWRP or CWM and he flashing it via Flashify or some other weird ways. if thats the case then you might be right.
Click to expand...
Click to collapse
Not sure if you saw my above edit, but I went ahead and downloaded and checked the updater-scipt for the other variants as well. They all check ro.product.device, but the other variants allow the value to be either the model number (d800, d801, etc.) or g2 or galbi, while the Tmobile one doesn't check for g2 or galbi. Looks like this is an issue with the Tmobile build, not an issue's on OP part (OP's build.prop has ro.product.device set to "g2")

G1_enthusiast said:
have you flash other roms before or this is the first time you doing it?
Click to expand...
Click to collapse
This is the first time flashing with this phone.

jellopuddingstick said:
Not sure if you saw my above edit, but I went ahead and downloaded and checked the updater-scipt for the other variants as well. They all check ro.product.device, but the other variants allow the value to be either the model number (d800, d801, etc.) or g2 or galbi, while the Tmobile one doesn't check for g2 or galbi. Looks like this is an issue with the Tmobile build, not an issue's on OP part (OP's build.prop has ro.product.device set to "g2")
Click to expand...
Click to collapse
I'm out of ideas then...
to OP: You can try jello method but honestly thats a gamble to me. do let us know how u fix it.

Now my phone will not boot. It is stuck on the LG logo. I don't know if it was because of that line I changed, or gapps 4.4 was installed to Android 4.2.2, since CM11 failed. Should have just installed one image at a time.

Hypersonic1 said:
Now my phone will not boot. It is stuck on the LG logo. I don't know if it was because of that line I changed, or gapps 4.4 was installed to Android 4.2.2, since CM11 failed. Should have just installed one image at a time.
Click to expand...
Click to collapse
Can you get into recovery? Otherwise, http://forum.xda-developers.com/showthread.php?t=2432476.

jellopuddingstick said:
Can you get into recovery? Otherwise, http://forum.xda-developers.com/showthread.php?t=2432476.
Click to expand...
Click to collapse
I can enter into download mode by holding down the volume up button, but I do not know how to enter recovery mode with this phone.

Hypersonic1 said:
I can enter into download mode by holding down the volume up button, but I do not know how to enter recovery mode with this phone.
Click to expand...
Click to collapse
"Volume down & Power, when the LG logo appears release and press them again, then press the Power button three times" (from the cyanogenmod wiki)
Assuming you can get into recovery, flash either cm-11-20131206-NIGHTLY-d801.zip or cm-10.2.0-d801.zip and let me know what happens. Don't even worry about gapps right now.
EDIT: here's a video showing how to boot into recovery

jellopuddingstick said:
"Volume down & Power, when the LG logo appears release and press them again, then press the Power button three times" (from the cyanogenmod wiki)
Assuming you can get into recovery, flash either cm-11-20131206-NIGHTLY-d801.zip or cm-10.2.0-d801.zip and let me know what happens. Don't even worry about gapps right now.
Click to expand...
Click to collapse
Thanks. I got into recovery. I will just stick with cm-11, since they both fail anyway.
I am still getting this is a g2 error.

Hypersonic1 said:
Thanks. I got into recovery. I will just stick with cm-11, since they both fail anyway.
I am still getting this is a g2 error.
Click to expand...
Click to collapse
If you'll give me a minute, I can patch the updater-script to have the correct checks (as per the other variants) and upload it for you. You should be able to adb push it to your phone while it's in recovery, flash, and be good to go.

XNPH33R OTA with modified Updater-Script

https://www.mediafire.com/?922rx2xn53yt72r
Here it is. Enjoy. And yes it works on mine :fingers-crossed:
It's a new Official Update
Changelog taken from Android Police
-A new radio image.
-Touchscreen fixes (addresses BACON-55, which was originally reported and subsequently brought to our attention by Ausdroid). There's also an extensive thread on OnePlus' forums about it, among many other places (forum account needed).
Update: The fix is not complete, as reports of jumpiness are surfacing once again. It did fix the deadzone / random touches issue which prevented me from unlocking my phone for 10-15s at a time as I simply couldn't trace my pattern due to all the jumping around.
Unfortunately, the grounding issue which results in multitouch going nuts remains unfixed and must be resolved via another driver update. Another excruciating wait begins.
-Decreased power consumption in idle state (fixes BACON-599 which we wrote about here).
-Unspecified audio fixes.
-CVE-2014-4943 and another unspecified security update.
MD5 : 7538A068384C52FF6CA06C4B128B5ED1
P/S : I didn't have that jumpiness of sort, mine is working fine.

Flashing this worked perfectly for me. Thanks.

Glad to see it worked

Good job, works great

ravearamashi said:
https://www.mediafire.com/?922rx2xn53yt72r
Here it is. Enjoy. And yes it works on mine :fingers-crossed:
MD5 : 7538A068384C52FF6CA06C4B128B5ED1
Click to expand...
Click to collapse
Awesome!!!! Thanks so much

what is modified updater-script, is this the ota which is pushed by oneplus?

Is there a change log anywhere?

Fist and foremost,THANKS !
Could you perhaps elaborate on the update a bit ? e.g. this the official NEW update ?

boomam said:
Is there a change log anywhere?
Click to expand...
Click to collapse
You can check it out here. http://www.androidpolice.com/2014/0...ed-fixes-here-is-the-zip-for-manual-flashing/

Seems to work fine, thanks

Thanks m8, works perfectly.

What does it mean by modified updater script?

nice
Thank you

surronix said:
What does it mean by modified updater script?
Click to expand...
Click to collapse
I'm wondering the same thing. Can I flash this if I am on CM nightlies?

GETCASHMONEY said:
I'm wondering the same thing. Can I flash this if I am on CM nightlies?
Click to expand...
Click to collapse
No, it's strictly for CM11S
See, back when XNPH30O came out, lot of people couldn't update using OTA method when they are rooted/running Xposed/custom kernel and so forth because the OTA update would check the files before updating begins which of course the update would fail on devices running the aforementioned stuff. And a guy named Ludester modified the updater-script to bypass that file check and of course the update worked on these modified devices. So fast forward to this update, I just did the same thing.

Sorry Guys, but with TWRP i go into recovery and simply flash this file?

joeee89 said:
Sorry Guys, but with TWRP i go into recovery and simply flash this file?
Click to expand...
Click to collapse
Yes, and wipe cache after flashing then reboot.

joeee89 said:
Sorry Guys, but with TWRP i go into recovery and simply flash this file?
Click to expand...
Click to collapse
Yes you can

wipe
there is no need to wipe
i just installed it an no problems
i didt no wipe

Nope.
Phone is stuck at the OnePlus Logo after flashing via TWRP. Wiping caches and re-flashing didn´t help.

[GUIDE] How to install Emotion AOSP on T-Mobile N910T/N910T3

[GUIDE] How to install Emotion AOSP on T-Mobile N910T/N910T3
I know a lot of you wanted to try Emotion AOSP on our T-Mobile Note 4, but it is not supported currently.
I have been able to flash it successfully to my N910T3 and having no issues what so ever, all works.
Here are the instructions:
1) Download the ROM from here:
http://forum.xda-developers.com/note-4/snapdragon-dev/rom-aokp-emotroid-team-t3317486
2) Download the gaps from OpenGaps, I prefer pico version.
3) Now you need to open the zip file using 7-Zip and extract following file:
META-INF\com\google\android\update-script
4) Edit the file in any Text Editor and remove the 1st line starting with keyword "assert", if you don't remove this line then you won't be able to flash it your N910T/N910T3.
5) Put the modified update-script back in the zip file using 7-zip.
6) To get the Data/Wifi working you need to download the data fix for N910T from below link:
http://forum.xda-developers.com/note-4/snapdragon-dev/marshmallow-6-0-1-ports-data-fixes-t3379978
7) Now this ROM will be ready to flash via recovery as usual like any other ROM.
8) Copy all 3 files to your phone internal/external memory.
9) Flash in below order:
Emotion-trltexx-MM.r21.Official-20160916-200804.zip
open_gapps-arm-6.0-pico-*.zip
LouForgiveNo_N910T_MM_Data_Fix.zip
ROM will take about 10-15 minutes to boot. Then you should be able to setup the phone as per your requirements.
Don't forget to thank @Pafcholini and @louforgiveno for their work.

I couldn't get it to work. Got an error message in TWRP.

Aivo7192 said:
I couldn't get it to work. Got an error message in TWRP.
Click to expand...
Click to collapse
That means you missed Step 3-4, it won't work without modifying the update-script file.

pvsgh said:
That means you missed Step 3-4, it won't work without modifying the update-script file.
Click to expand...
Click to collapse
Steps 3-4 did confuse me a bit. I did it a few times still no luck.

Once you have the ROM zip file ready, verify the update-script file again, it should NOT contain below line:
assert(getprop("ro.product.device") == "trltexx" || getprop("ro.build.product") == "trltexx" || getprop("ro.product.device") == "trltedt" || getprop("ro.build.product") == "trltedt" || abort("This package is for device: trltexx,trltedt; this device is " + getprop("ro.product.device") + ".");
This line check if you have one of those Note 4 variant.

Or you can do what i did...
Or you can replace all references to other devices with the T-Mobile name. For some reason kept getting code 6 when I removed the line, but when I replaced all the references to other devices worked like a charm. This method still requires you to extract, edit and compress again through 7-Zip.

pvsgh said:
[GUIDE] How to install Emotion AOSP on T-Mobile N910T/N910T3
I know a lot of you wanted to try Emotion AOSP on our T-Mobile Note 4, but it is not supported currently.
I have been able to flash it successfully to my N910T3 and having no issues what so ever, all works.
Here are the instructions:
1) Download the ROM from here:
http://forum.xda-developers.com/note-4/snapdragon-dev/rom-aokp-emotroid-team-t3317486
2) Download the gaps from OpenGaps, I prefer pico version.
3) Now you need to open the zip file using 7-Zip and extract following file:
META-INF\com\google\android\update-script
4) Edit the file in any Text Editor and remove the 1st line starting with keyword "assert", if you don't remove this line then you won't be able to flash it your N910T/N910T3.
5) Put the modified update-script back in the zip file using 7-zip.
6) To get the Data/Wifi working you need to download the data fix for N910T from below link:
http://forum.xda-developers.com/note-4/snapdragon-dev/marshmallow-6-0-1-ports-data-fixes-t3379978
7) Now this ROM will be ready to flash via recovery as usual like any other ROM.
8) Copy all 3 files to your phone internal/external memory.
9) Flash in below order:
Emotion-trltexx-MM.r21.Official-20160916-200804.zip
open_gapps-arm-6.0-pico-*.zip
LouForgiveNo_N910T_MM_Data_Fix.zip
ROM will take about 10-15 minutes to boot. Then you should be able to setup the phone as per your requirements.
Don't forget to thank @Pafcholini and @louforgiveno for their work.
Click to expand...
Click to collapse
pvsgh, everything works except for phone, am unable to make or receive calls. Any idea what the problem could be? Had to go back to 5.1.1 to get phone to work, a shame as everything else worked perfectly.

pvsgh said:
That means you missed Step 3-4, it won't work without modifying the update-script file.
Click to expand...
Click to collapse
After changing assert line ...I can flash but the ROM never goes beyond boot animation. Waited more than 20 minutes .I dint flash datafix...was planning to do that If rom boots

Manan79 said:
After changing assert line ...I can flash but the ROM never goes beyond boot animation. Waited more than 20 minutes .I dint flash datafix...was planning to do that If rom boots
Click to expand...
Click to collapse
vanemburghj said:
pvsgh, everything works except for phone, am unable to make or receive calls. Any idea what the problem could be? Had to go back to 5.1.1 to get phone to work, a shame as everything else worked perfectly.
Click to expand...
Click to collapse
What model you guys are using? and what is the version of your bootloader? I have the latest EPG2.

pvsgh said:
What model you guys are using? and what is the version of your bootloader? I have the latest EPG2.
Click to expand...
Click to collapse
Same... 910t on epg2...

Manan79 said:
Same... 910t on epg2...
Click to expand...
Click to collapse
Did you install at least the gapps package? That is a required install. I would suggest you to install all 3 files mentioned in OP.

pvsgh said:
Did you install at least the gapps package? That is a required install. I would suggest you to install all 3 files mentioned in OP.
Click to expand...
Click to collapse
Will do...and update you

vanemburghj said:
pvsgh, everything works except for phone, am unable to make or receive calls. Any idea what the problem could be? Had to go back to 5.1.1 to get phone to work, a shame as everything else worked perfectly.
Click to expand...
Click to collapse
I tested the phone call immediately after install and it worked for me without issues. So in your case only phone call is not working, what about data and wifi?

pvsgh said:
I tested the phone call immediately after install and it worked for me without issues. So in your case only phone call is not working, what about data and wifi?
Click to expand...
Click to collapse
ok , so for me , it did boot after following the exact 3 steps...i m testing the rom now , will report if any issues.. thanks for the OP
1. only H+ instead of LTE i get
2. camera does not work , just shows blank screen
I am gonna go back to norma note 7 port... however, very nice that i can load the rom and test it. thx again

pvsgh said:
I tested the phone call immediately after install and it worked for me without issues. So in your case only phone call is not working, what about data and wifi?
Click to expand...
Click to collapse
phone calling not working for me. It shows dialing but nothing happen.

pvsgh said:
What model you guys are using? and what is the version of your bootloader? I have the latest EPG2.
Click to expand...
Click to collapse
SM-N910T and bootloader is EPE3.
---------- Post added at 05:44 PM ---------- Previous post was at 05:40 PM ----------
pvsgh said:
I tested the phone call immediately after install and it worked for me without issues. So in your case only phone call is not working, what about data and wifi?
Click to expand...
Click to collapse
Data and wifi work, which is why I did not realize I had problems with the phone. Started receiving voice mails, thought I had the volume down and that wasn't it. Tried calling the house and it just said dialing for 5 minutes. Again, a shame as I liked the ROM, but need the phone to work.

I didn't have to do anything but flash in TWRP. I'm on epg2

Does anyone have the nougat update file

Hey guys i couldn't get in the beta so i was wondering if anyone has the Nougat update file that i can flash with odin.
Thanks

Join the club. No one has the VZW one for the flat s7 either....

Illogi.xbone said:
Join the club. No one has the VZW one for the flat s7 either....
Click to expand...
Click to collapse
Someone said they are going to try. I offered help if need be

billydroid said:
Someone said they are going to try. I offered help if need be
Click to expand...
Click to collapse
I cannot post outside links so please PM me if you would like to test the file. I will also upload it to Android File Host when I am approved.

jakemastaflash said:
I cannot post outside links so please PM me if you would like to test the file. I will also upload it to Android File Host when I am approved.
Click to expand...
Click to collapse
Hey, send me the link. Other than the files, the proccess should be the very basic odin proccess right?

diego97yey said:
Hey, send me the link. Other than the files, the proccess should be the very basic odin proccess right?
Click to expand...
Click to collapse
I believe it can be flashed from Recovery. It's being tested now, I will be checking for updates\consistency tomorrow with a clean flash and update.

jakemastaflash said:
I believe it can be flashed from Recovery. It's being tested now, I will be checking for updates\consistency tomorrow with a clean flash and update.
Click to expand...
Click to collapse
Keep us posted man

Footer and verification error so far

Same here
Sent from my SM-G930P using XDA-Developers mobile app

dgr581 said:
Same here
Sent from my SM-G930P using XDA-Developers mobile app
Click to expand...
Click to collapse
Sounds like it is throwing errors for everyone . I will be trying to grab a fresh copy today, or tomorrow. Link removed until we have a working update.

jakemastaflash said:
Sounds like it is throwing errors for everyone . I will be trying to grab a fresh copy today, or tomorrow. Link removed until we have a working update.
Click to expand...
Click to collapse
I tried using winrar to repair it but still got error code my recovery has been acting strange tho. It says install system update when i boot to it then gives me a dead droid with yellow triangle but then enters recovery like normal.

vegoja said:
I tried using winrar to repair it but still got error code my recovery has been acting strange tho. It says install system update when i boot to it then gives me a dead droid with yellow triangle but then enters recovery like normal.
Click to expand...
Click to collapse
I believe I have a solution. I am working on it now. Additionally, I'm getting close 10 posts!

jakemastaflash said:
I believe I have a solution. I am working on it now. Additionally, I'm getting close 10 posts!
Click to expand...
Click to collapse
Another update pull failed verification and resulted in another footer error. If installed without any modification it works, but after rooting and pulling the update.zip, trying to install it results in an error. It could be a security measure introduced to the update.zip to prevent installing on a phone without the matching signature assigned during the initial download.

Whenever i tried to follow the link it asked me for a security key ????

footer error
I read on another nougat beta thread that if you get a footer error then you should decrypt your SD and try agian

N3ksta said:
I read on another nougat beta thread that if you get a footer error then you should decrypt your SD and try agian
Click to expand...
Click to collapse
I did not have my SD Card encrypted. I have also noticed some discrepancies between the update.zip I am extracting and the working VZW update.zip. Things like: the boot.img is 0kb, and there are missing CERT.RSA, CERT.SF, or MANIFEST.MF files under META-INF folder.
I have tried extracting it in several different ways\environments and get problems with every pull.
Other variants are working on the same thing with the same issues. I have the last pull I made, but I can't continue working on this as heavily since I'm using my daily driver. I'll try again as new info\solutions come up.

Seems like getting root (with current methods) may be disturbing the file structure. There may be something else at play here since all the pulls still come with a boot.img that is 0kb, and are missing CERT.RSA, CERT.SF, or MANIFEST.MF files under META-INF folder.
Here is the link to the WIP update.zip. I'm going to stop working on this until someone can suggest a better way to root or pull the file without it coming out corrupt\incomplete. Good luck!
Link to the update.zip.
Here is the flashing method used by the VZW folks:
Originally Posted by zimgir124
A method has been found to install the beta without being accepted!
Thanks @jrkruse for finding this method!
1. reboot to download mode (power + volume up +home) and make sure phone says Official under system and binary.
2. If it does not then you must odin the PH1 firmware, use the pit file and the full csc not the home csc file
3. go through setup
4. enable developer options
5. turn OEM unlock off
6. enable USB debugging
7. place Update.zip on Ext sd card in folder named fota
8. power off phone
9. reboot to download mode make sure both system and binary are official.
10. reboot to recovery (Power + volume down + home)
11. choose apply Update.zip from SD card
12. find Update.zip in the fota folder you created on your Ext sdcard
13. click yes to apply
After this it should update to the Android 7.0 beta and hopefully will be able to download future beta OTAs.
You will not lose anything as this is an OTA
You do not want to be rooted. You must be stock for this to work!
There is no gear VR available on the beta.
Troubleshooting:
"E: footer is wrong" followed by "E: signature verification failed" : Decrypt SD Card and try again.
Click to expand...
Click to collapse

jakemastaflash said:
Seems like getting root (with current methods) may be disturbing the file structure. There may be something else at play here since all the pulls still come with a boot.img that is 0kb, and are missing CERT.RSA, CERT.SF, or MANIFEST.MF files under META-INF folder.
Here is the link to the WIP update.zip. I'm going to stop working on this until someone can suggest a better way to root or pull the file without it coming out corrupt\incomplete. Good luck!
Link to the update.zip.
Here is the flashing method used by the VZW folks:
Click to expand...
Click to collapse
So should this method work for us?

jakemastaflash said:
Seems like getting root (with current methods) may be disturbing the file structure. There may be something else at play here since all the pulls still come with a boot.img that is 0kb, and are missing CERT.RSA, CERT.SF, or MANIFEST.MF files under META-INF folder.
Here is the link to the WIP update.zip. I'm going to stop working on this until someone can suggest a better way to root or pull the file without it coming out
Here is the flashing method used by the VZW folks:
Click to expand...
Click to collapse
Is it for the flat or edge? also have you tried using adb to pull the file (you probably have, but just asking)

15jpenni said:
So should this method work for us?
Click to expand...
Click to collapse
Ideally it should. However, I have not been able to successfully reproduce the same results as installing the update file without modification.
---------- Post added at 09:04 PM ---------- Previous post was at 09:00 PM ----------
N3ksta said:
Is it for the flat or edge? also have you tried using adb to pull the file (you probably have, but just asking)
Click to expand...
Click to collapse
This is for the SM-G930P regular S7 (not edge). I have pulled it via filemanager app after full root, and via adb on linux and windows after eng kernel root and full root. All of them yielded an apropriately sized update.zip, but it seems to get corrupted during the rooting or extraction process.
Also, there may be a reason behind our update.zip not having a boot.img. We may not need a new boot.img after updating to PJ2, so it isnt packaged in our update. If someone can repackage the update.zip so it passes verification we may have more luck.

Nokia 6 T-1000 official rom desperately needed

Hi, I bought a Nokia 6 T-1000 and it wound up having an unofficial rom installed. I am desperately trying to get the official firmware installed and I can't find it. Sadly, now my brand new phone just boots straight into recovery mode. Can anyone backup their firmware and provide it to me or point me to where I could get it?

aNorthernSoul said:
Hi, I bought a Nokia 6 T-1000 and it wound up having an unofficial rom installed. I am desperately trying to get the official firmware installed and I can't find it. Sadly, now my brand new phone just boots straight into recovery mode. Can anyone backup their firmware and provide it to me or point me to where I could get it?
Click to expand...
Click to collapse
Try download the file from below. Follow the steps.
http://www.stechguide.com/install-android-7-1-1-nougat-on-nokia-6/

kanakarkku said:
Try download the file from below. Follow the steps.
Click to expand...
Click to collapse
I had tried that. I can only do method 1 though as it won't go out of recovery mode to turn on USB debugging. When doing method 1, it attempts installing, I see it installing three times with a couple reboots then returns to recovery mode and says the following:
Failed to parse build number in post-build-incremental=00CN_3_170
Failed to parse build number in pre-build-incremental=00CN_1_310
E1004: System partition fails to recover
E:Error in <downloaded filename>
(Status 7)
Installation aborted.

aNorthernSoul said:
I had tried that. I can only do method 1 though as it won't go out of recovery mode to turn on USB debugging. When doing method 1, it attempts installing, I see it installing three times with a couple reboots then returns to recovery mode and says the following:
Failed to parse build number in post-build-incremental=00CN_3_170
Failed to parse build number in pre-build-incremental=00CN_1_310
E1004: System partition fails to recover
E:Error in <downloaded filename>
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
It seems it's not the right file. When I check the built number it is 00CN_3_31A_SP. It would be good to know what built be you have as it is failing to increment the 170 .. I will check later what I can do

kanakarkku said:
It seems it's not the right file. When I check the built number it is 00CN_3_31A_SP. It would be good to know what built be you have as it is failing to increment the 170 .. I will check later what I can do
Click to expand...
Click to collapse
Thanks! Before the update, it was saying "00CN_3_170" under Build Number in Settings. I had spoke to Nokia though and they felt that the firmware had been tampered with.

nokia stuck in recovery mode
aNorthernSoul said:
Hi, I bought a Nokia 6 T-1000 and it wound up having an unofficial rom installed. I am desperately trying to get the official firmware installed and I can't find it. Sadly, now my brand new phone just boots straight into recovery mode. Can anyone backup their firmware and provide it to me or point me to where I could get it?
Click to expand...
Click to collapse
aNorthernSoul said:
Thanks! Before the update, it was saying "00CN_3_170" under Build Number in Settings. I had spoke to Nokia though and they felt that the firmware had been tampered with.
Click to expand...
Click to collapse
kindly tell me what to do my new nokia 6 is also stuck on recovery mode plz help me what to do

kafeel3186 said:
kindly tell me what to do my new nokia 6 is also stuck on recovery mode plz help me what to do
Click to expand...
Click to collapse
I am still trying to figure it out. Based on where you live, you might be able to contact Nokia via online chat and they could direct you to a service centre to flash the phone. They don't have any in Canada though.
I am trying to get the legit firmware but I am not sure if it is the one I have or the modified one my phone came with causing me to be able to unsuccessfully install it.
How did yours wind up in that state?

kanakarkku said:
It seems it's not the right file. When I check the built number it is 00CN_3_31A_SP. It would be good to know what built be you have as it is failing to increment the 170 .. I will check later what I can do
Click to expand...
Click to collapse
Just a side note, I am able to sideload the update via the PC. It quits at 54% (failed to read command * no error) after showing those same parse errors on the screen though. Weirdly, then it reboots with a differently styled logo screen and tried (and fails) to update. Then the logo screen is normal again.

Just in case anyone is wondering, I spoke to the seller I purchased from on Amazon. Whether advertised or not, most China suppliers are installing a custom ROM on all China variants of the Nokia 6. When buying from a more local third party, you have no access to this ROM. I just bought this phone last week and knew about the update from Nokia so had confirmed with them that it currently didn't support Google Services. I didn't want a custom rom.
I have asked for either the rom installed or the official firmware that should have came with the phone and a means to install it or I will take action with Amazon tomorrow. I don't really want to return the phone, I'd likely wait for someone to release an official rom but I could barely afford this phone as it was and it is currently useless.
I just wanted to warn anyone else thinking about buying the Chinese model.

kanakarkku said:
It seems it's not the right file. When I check the built number it is 00CN_3_31A_SP. It would be good to know what built be you have as it is failing to increment the 170 .. I will check later what I can do
Click to expand...
Click to collapse
aNorthernSoul said:
I had tried that. I can only do method 1 though as it won't go out of recovery mode to turn on USB debugging. When doing method 1, it attempts installing, I see it installing three times with a couple reboots then returns to recovery mode and says the following:
Failed to parse build number in post-build-incremental=00CN_3_170
Failed to parse build number in pre-build-incremental=00CN_1_310
E1004: System partition fails to recover
E:Error in <downloaded filename>
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
I had the same result after method 1 via sd

Quixote78 said:
I had the same result after method 1 via sd
Click to expand...
Click to collapse
And after method 2 via ADB)))
As result device stuck in bootloop mode.
I've managed to bring it back with MiFlash only.

kanakarkku said:
Try download the file from below. Follow the steps.
http://www.stechguide.com/install-android-7-1-1-nougat-on-nokia-6/
Click to expand...
Click to collapse
IMO the file that you download is to update the existing working ROM and the op has somehow ended up with one that doesn't work. So I think he would need the entire ROM the exact version that he last had to get back into the phone and then update.