Database Users

Nexus 4 kitkat update error

So I just got my OTA for 4.4 and downloaded the update. So I hit the restart and install button. The installing process ran like it supposed to be until the end part of it. The screen showed the word "error" with the android logo laying down. Then the phone just stayed like that and the screen not changing. So I decided to turn off the phone. Then I booted up the phone again, the google screen shows normally, but after that it shows the screen showing "no command" and I am stuck with that screen now and cannot go in. So I researched about it and find out I need to go to recovery mode. Then I hit the vol up and power button, then hit the recovery mode. But still, it shows the no command screen again.
Please help me... Thanks

Same issue here. Nexus 4 (rooted) OTA update from 4.3 to 4.4 failed. "No command" error. Please help

It's not pressing then together, have you tried this: http://forum.xda-developers.com/showpost.php?p=44388152&postcount=13

eksasol said:
It's not pressing then together, have you tried this: http://forum.xda-developers.com/showpost.php?p=44388152&postcount=13
Click to expand...
Click to collapse
It worked, now what do I do? I don't want to wipe all my data ._.
Is there a way to get the update and install it ?

GIANTLIZARDMAN said:
It worked, now what do I do? I don't want to wipe all my data ._.
Is there a way to get the update and install it ?
Click to expand...
Click to collapse
Check in the general section, there are a ton of info on this. i'll give you the links this time.
Follow the Scenario #1 instruction from here:http://forum.xda-developers.com/showthread.php?t=2145848
Or qbking77 video: http://forum.xda-developers.com/showthread.php?t=2537410

eksasol said:
Check in the general section, there are a ton of info on this. i'll give you the links this time.
Follow the Scenario #1 instruction from here:http://forum.xda-developers.com/showthread.php?t=2145848
Or qbking77 video: http://forum.xda-developers.com/showthread.php?t=2537410
Click to expand...
Click to collapse
I really don't know what to do, since I can't turn on my phone and get into the settings to check the USB Debugging I can't do anything with my phone plugged into my computer.... so.... what should I do? ((((

GIANTLIZARDMAN said:
I really don't know what to do, since I can't turn on my phone and get into the settings to check the USB Debugging I can't do anything with my phone plugged into my computer.... so.... what should I do? ((((
Click to expand...
Click to collapse
Just watch the video and follow its instruction, you enabled the adb sideload command in the stock recovery. It has nothing to do with USB Debugging whatsoever.

eksasol said:
Just watch the video and follow its instruction, you enabled the adb sideload command in the stock recovery. It has nothing to do with USB Debugging whatsoever.
Click to expand...
Click to collapse
Followed the instructions shown in the video, but when I try to install the 4.4 update it gives me an error:
set_metadata_recursive: some changes failed
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
Once again.... please help me.

GIANTLIZARDMAN said:
Followed the instructions shown in the video, but when I try to install the 4.4 update it gives me an error:
set_metadata_recursive: some changes failed
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
Once again.... please help me.
Click to expand...
Click to collapse
Status 7 usually means something wrong with the package (or your recovery version isn't compatible, which is not the case in this scenario). So either your file is corrupt or you downloaded the wrong package to update. What package you use depends on what version you come from. You can either use:
4.4-KRT16S-from-JWR66Y
4.4-KRT16S-from-KRT16O
If you are unsure, try the first one, then the other. It's most likely the first though or your package is corrupt, so redownload it: http://forum.xda-developers.com/showthread.php?t=2145848
Also try using wipe cache' option in the recovery to see if it help. (The factory reset option will wipe all your data.)

eksasol said:
Status 7 usually means something wrong with the package (or your recovery version isn't compatible, which is not the case in this scenario). So either your file is corrupt or you downloaded the wrong package to update. What package you use depends on what version you come from. You can either use:
4.4-KRT16S-from-JWR66Y
4.4-KRT16S-from-KRT16O
If you are unsure, try the first one, then the other. It's most likely the first though or your package is corrupt, so redownload it: http://forum.xda-developers.com/showthread.php?t=2145848
Also try using wipe cache' option in the recovery to see if it help. (The factory reset option will wipe all your data.)
Click to expand...
Click to collapse
Hi, I have tried both packages twice and re-downloaded them, and also wipe cache. I'm still getting the error status 7 installation aborted. I dont know what to do now. Please help im stuck.

I got it with the method in your sig. Flash factory image without wiping data (a different method) (short, if bootloader already unlocked). Thanks!

eksasol said:
Status 7 usually means something wrong with the package (or your recovery version isn't compatible, which is not the case in this scenario). So either your file is corrupt or you downloaded the wrong package to update. What package you use depends on what version you come from. You can either use:
4.4-KRT16S-from-JWR66Y
4.4-KRT16S-from-KRT16O
If you are unsure, try the first one, then the other. It's most likely the first though or your package is corrupt, so redownload it: http://forum.xda-developers.com/showthread.php?t=2145848
Also try using wipe cache' option in the recovery to see if it help. (The factory reset option will wipe all your data.)
Click to expand...
Click to collapse
tippingvan said:
Hi, I have tried both packages twice and re-downloaded them, and also wipe cache. I'm still getting the error status 7 installation aborted. I dont know what to do now. Please help im stuck.
Click to expand...
Click to collapse
GIANTLIZARDMAN said:
I really don't know what to do, since I can't turn on my phone and get into the settings to check the USB Debugging I can't do anything with my phone plugged into my computer.... so.... what should I do? ((((
Click to expand...
Click to collapse
I'm having the same problem.
I had 4.2 stock (JOP40C).
I used NRT to unlock and root.
I then got an OTA update for 4.3 (JWR66Y, I believe) and lost root.
I was going to re-root, but received another OTA for 4.4, so I figured I'd install it before re-rooting.
Unfortuntately, I didn't re-enable USB debugging, which may be my current issue.
The install encountered an error (Android on his back and little red triangle).
Now I can't get past Recovery.
I tried installing 4.4 from JWR66Ymanually via adb using methods described here and get the status 7 message shown above.
If I try installing 4.4 from KRT160 I get an error indicating my device has the wrong keys (seems to imply not the right starting version for the upgrade).
I've also tried flashing the factory JWR66Y ROM from the Google site using adb. When I do that, I get a "signature verification failed" message.
It looks like there may be a way around this if a flash a different recovery. Can I do that with adb?
I can't connect with NRT anymore. I ahve some backups I made with NRT, but am not sure how to load them without using NRT.
I can sideload with adb, but can't do much else. "fastboot devices" doesn't return anything.
Help!
Thanks!

[FIX] Cannot make calls or receive them and no sound on I9505

Hi all,
If you change ROM quite often and baseband too, most of the time everything goes smoothly, however, if you choose the wrong combination, you might encounter a very annoying issue: lost of the system sound, no ability of calling nor receiving phone calls.
I finally found a way to make my mobile sound working again (as it should) and I am able to call and receive phone calls as well. No reboots either.
When I started my investigation I had the following on my mobile:
ROM: [AOSP] Official 4.4.2 - S4 Google Edition - Final-R1.1 by jamal2367
Baseband: baseband XXUFNA1
Recovery: TWRP
Let me make the point. It is not because of the above settings that I had problems, but because of a combination of changing ROMs and baseband, probably only baseband.
When I was receiving a phone call only the vibration was working, no sounds, I couldn't slide the screen to answer properly, which means that I was able to slide, but the round icon of the slide could not catch the phone green icon. I could play no sound at all on videos, spotify, alarm, etc.; at the beginning I thought it was the current ROM, then
- I add to install Kies to try to restore the original firmware
- I changed it to another one
- I changed to CyanogenMod (and changed recovery to the default that comes with it: CWM)
- I rolled back to Samsung Stock edition (thank God I made a backup with TWRP months ago, before rooting)
Same damn issue and since I was there, I kept changing baseband with what I thought was the best for that particular (current) ROM. It is easy, you ask Mr. Google and he will tell you or you can try with http://www.sammobile.com/firmwares/2/
How can you fix it?
a. Download I9505XXUEMKF_I9505OXXEMK3_I9505XXUEMKF_HOME.tar.md5 and I9505XXUEMK8_I9505OXAEMK8_I9505XXUEMK8_HOME.tar.md5
b. Untar them in different directories
c. Use Heimdall - http://glassechidna.com.au/heimdall/ to flash all files in I9505XXUEMKF_I9505OXXEMK3_I9505XXUEMKF_HOME
c1. On Heimdal, click on the second tab _flash_, then browse your pit file, click on the button _add_ and choose the right partition. Do this for all the files inside the directory. Inside the _partitions (files)_ window you will have as many items as you have in the directory, in the example I put only 3, but you should have 12 of them in total (see image below)
- Under the partition ID, there is also a label/text that suggest you what file to choose.
- A note, MDM is for the modem, do not use MODEMST1 or MODEMST2
- If you do not have a pit, you can google it or as I did, use the forth tab _Utilities_, detect your device, and save as...under Download PIT.
c2. Then click on start to flash.
d. reboot in recovery and let CWM install unrecognized packages if asked. You might also find some red lines on the top left of the screen, but do not worry too much.
You might also find other red text _unable to unmount this or that_, after pressing start, but do not worry.
I tried to restart my mobile, but I was not able to restart it; in case you can, your stock Samsung ROM still has no sound. So
e. reboot in download and flash NON-HLOS.bin from the other folder I9505XXUEMK8_I9505OXAEMK8_I9505XXUEMK8_HOME. Use Partition Name _APNHLOS_ from partition Details in Heimdall.
f. the sounds is back
g. re-install your favourite recovery back
h. re-install your favourite ROM
I put back TWRP and [AOSP] Official 4.4.2 - S4 Google Edition - Final-R1.1 by jamal2367
Current baseband XXUEMKF. I will leave it as it is for a while, without changing it.
You can use Heimdall on windows too, but in case of driver problems use this to resolve the issue http://zadig.akeo.ie/
LTE and WiFi will work too.
You can get the two folders from this zip file: https://mega.co.nz/#!GARWHLDY!d2hrbCaVMKMLOXdNG6VfgkFMcjZclXJHTxe6amz0TNM
Note:
- When you flashed NON-HLOS.bin it might get the message stuck on _Rebooting device..._ and it does not give the impression that it finished. If you manual reboot and sometimes it means _remove the battery_, it will work.
- At the reboots note how the text on the top left changes during and after flashing.
At the booting now I get a warning text on the top-left (small text), it is something I can cope with or fix it later.
You can read in some posts that if _my phone number_ in unknown, under _status_ then you have problems with phone calls. I always had that one and still have it and it is working, so I wouldn't pay too much attention.
- if you have problems with heimdall, remove Kies (actually you can just remove it directly) and on mac, to remove some dependencies, run
sudo sh -
kextunload -b com.devguru.driver.SamsungComposite
kextunload -b com.devguru.driver.SamsungACMData
kextunload -b com.devguru.driver.SamsungACMControl
the uninstaller seems like it is working ok, so you might not need the above lines.

Or just flash the right non-hlos/wifi fix and that should fix your problem ...if you have a newbootloader just flash any latest non-hlos, but if you are still in oldbootloader feel free to flash a BMH1 non-hlos/wifi fix.. have a nice day.
Sent feom Hell ?

haven't really understood Step c1 Please @racoonlab

I cant find The pit File

Hi m_beek,
m_beek said:
I cant find The pit File
Click to expand...
Click to collapse
Have you tried the 4th tab of heimdall, utilities?
a. detect
b. save as
c. download
If you do not detect it, use the Zadig drivers first.
You can also try to have a look at http://forum.xda-developers.com/showthread.php?t=999097

What about getting "ERROR: Claiming interface failed!" after Clicking Start ?

m_beek said:
What about getting "ERROR: Claiming interface failed!" after Clicking Start ?
Click to expand...
Click to collapse
Do you have the Kies software installed? If yes, uninstall it and see also the last few lines of my post, to remove potential dependencies.
EDIT
Restart your machine too after the uninstall
R

Since I'm on W8 , I have never Installed Kies

m_beek said:
Since I'm on W8 , I have never Installed Kies
Click to expand...
Click to collapse
i. did you manage to get the pit?
ii when did you get that message, when flashing?
R

I couldn't get my Pit from _Utilities_ because of that, So I Googled "GT I9505 Pit" and download a Pit file, The After Managing Pit and Start flashing That What it's sayed
"This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
ERROR: Claiming interface failed!"

m_beek said:
I couldn't get my Pit from _Utilities_ because of that, So I Googled "GT I9505 Pit" and download a Pit file, The After Managing Pit and Start flashing That What it's sayed
"This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
ERROR: Claiming interface failed!"
Click to expand...
Click to collapse
Have you tried the Zadig drivers? To me it helped to:
- start the program
- see the list of the usb in used
- while the program was showing me the list, I unplugged the cable from one usb and attached to another one.
- run the program.
R

racoonlab said:
i. did you manage to get the pit?
ii when did you get that message, when flashing?
R
Click to expand...
Click to collapse
Ps. Odin Works, Can I Flash it with Odin ?

m_beek said:
Ps. Odin Works, Can I Flash it with Odin ?
Click to expand...
Click to collapse
probably with the latest yes.
http://www.xda-developers.com/android/mobile-odin-updated-to-version-4-new-features-and-devices/

racoonlab said:
probably with the latest yes.
http://www.xda-developers.com/android/mobile-odin-updated-to-version-4-new-features-and-devices/
Click to expand...
Click to collapse
Finally works
Ps. Its normal to get "Invalid Percent of Drawing progress Bar1"

Repulsa said:
Or just flash the right non-hlos/wifi fix and that should fix your problem ...if you have a newbootloader just flash any latest non-hlos, but if you are still in oldbootloader feel free to flash a BMH1 non-hlos/wifi fix.. have a nice day.
Sent feom Hell
Click to expand...
Click to collapse
Currently I have this one instaled I9505VJUHOK1. It was working fine with the stock ROM from SamMobile (http://www.sammobile.com/firmwares/download/61139/I9505VJUHOK1_I9505ZTOHOK1_ZTO/).
There is no sound at all on calls when using CM13.
What would you recommend?

[Q] Stuck in TWRP recovery project in G2

Hi out there looking for help with my G2 (D803) . I am new to all this rooting and TWRP stuff but been trying to learn and figure this out. I accepted some update after which the phone only boots into TWRP recovery project v2.6.3.2 now. Looks like I lost everything else (at least that is what I think has happened).
So I have been reading on the forums and learned about using ADB devices and getting the right rom from xda-developers (I am with Telus in Canada) - used http://forum.xda-developers.com/showthread.php?t=2432476 - downloaded LG support tool and flash tool and drivers for phone and installed them all on the computer.
I first had trouble pushing the rom on to my phone (using ADB devices and ADB push commands) because the phone would just turn off while transferring and I could only regain access when the battery is fully drained (happens really fast now?) and I recharge (which seems to take forever now?).
I took the phone to a store and they did some tweaking (says SIMULATING ACTIONS on the title now below TWRP and version number) after which I could push the ROM (I did rename it on the computer) successfully on to the phone using "ADB push" in command prompt.
I proceeded to install the rom and it says successful but clearly it did not work. What I see is:
Finished running boot script.
E:storage partition '//TWRP/BACKUPS/018bf7ce0f4c6fa0' not found
simulation actions ...
updating partition details ...
but then I reboot and it goes back into TWRP.
I tried going through flashtool as well and followed the steps to install the kdz file but it seems like the computer is not connecting to the phone. But if i go to device manager the device shows and says working properly (i installed the drivers already) and you also hear the beep when plugging in the USB cable into the phone. again it also seems to connect through command prompt because i can push a file successfully.
I am getting worried that I am out of luck with this phone . Can anyone help or provide suggestions as to what I am doing wrong? Would really appreciate it. Thanks.

brownbullet said:
Hi out there looking for help with my G2 (D803) . I am new to all this rooting and TWRP stuff but been trying to learn and figure this out. I accepted some update after which the phone only boots into TWRP recovery project v2.6.3.2 now. Looks like I lost everything else (at least that is what I think has happened).
So I have been reading on the forums and learned about using ADB devices and getting the right rom from xda-developers (I am with Telus in Canada) - used http://forum.xda-developers.com/showthread.php?t=2432476 - downloaded LG support tool and flash tool and drivers for phone and installed them all on the computer.
I first had trouble pushing the rom on to my phone (using ADB devices and ADB push commands) because the phone would just turn off while transferring and I could only regain access when the battery is fully drained (happens really fast now?) and I recharge (which seems to take forever now?).
I took the phone to a store and they did some tweaking (says SIMULATING ACTIONS on the title now below TWRP and version number) after which I could push the ROM (I did rename it on the computer) successfully on to the phone using "ADB push" in command prompt.
I proceeded to install the rom and it says successful but clearly it did not work. What I see is:
Finished running boot script.
E:storage partition '//TWRP/BACKUPS/018bf7ce0f4c6fa0' not found
simulation actions ...
updating partition details ...
but then I reboot and it goes back into TWRP.
I tried going through flashtool as well and followed the steps to install the kdz file but it seems like the computer is not connecting to the phone. But if i go to device manager the device shows and says working properly (i installed the drivers already) and you also hear the beep when plugging in the USB cable into the phone. again it also seems to connect through command prompt because i can push a file successfully.
I am getting worried that I am out of luck with this phone . Can anyone help or provide suggestions as to what I am doing wrong? Would really appreciate it. Thanks.
Click to expand...
Click to collapse
I'm not entirely sure, but it sounds like everything in TWRP is being simulated, which would mean that no files are actually written. Try going into Settings in TWRP, uncheck the "Simulate actions" checkbox, and run the rom installation again.

flutterguy317 said:
I'm not entirely sure, but it sounds like everything in TWRP is being simulated, which would mean that no files are actually written. Try going into Settings in TWRP, uncheck the "Simulate actions" checkbox, and run the rom installation again.
Click to expand...
Click to collapse
Thanks for the reply. It definitely did something because the installation process moves forward now. Now I get:
Zip signature verification failed: 1
Error flashing zip '/sdcard/telus.zip
also when i unclick zip file verification in setting i also see:
checking for MD5 file...
skipping MD5 check: no MD5 file found
So problem with the zip file? I downloaded it off xda-developers but I renamed the file to Telus.zip and pushed it on to the phone in the sdcard directory.

Download the whole Rom and flash it
Sent from my LG-D802 using XDA Premium 4 mobile app

brownbullet said:
Thanks for the reply. It definitely did something because the installation process moves forward now. Now I get:
Zip signature verification failed: 1
Error flashing zip '/sdcard/telus.zip
also when i unclick zip file verification in setting i also see:
checking for MD5 file...
skipping MD5 check: no MD5 file found
So problem with the zip file? I downloaded it off xda-developers but I renamed the file to Telus.zip and pushed it on to the phone in the sdcard directory.
Click to expand...
Click to collapse
you are a fxxxing genius thnx you so much

im going through the same thing
bigpappapuff said:
you are a fxxxing genius thnx you so much
Click to expand...
Click to collapse
Can you help me out? The same thing with my G2 and i have no idea how to fix it.

Chris2312 said:
Can you help me out? The same thing with my G2 and i have no idea how to fix it.
Click to expand...
Click to collapse
More info please.

bender_007 said:
More info please.
Click to expand...
Click to collapse
my g2 was was rooted and got an over the air update so now its just stuck in twrp and all of the memory got wiped so i dont know if its possible to fix it or if i have to get a new phone.

There are a lot of threads for your issue. Will search for one when I'm on lap.
Sent from my LG-D802 using Tapatalk
EDIT: There you go

bender_007 said:
There are a lot of threads for your issue. Will search for one when I'm on lap.
Sent from my LG-D802 using Tapatalk
EDIT: There you go
Click to expand...
Click to collapse
Thank you

flutterguy317 said:
I'm not entirely sure, but it sounds like everything in TWRP is being simulated, which would mean that no files are actually written. Try going into Settings in TWRP, uncheck the "Simulate actions" checkbox, and run the rom installation again.
Click to expand...
Click to collapse
Hi,
Was stuck with my HTC Butterfly x920d with the same. Thanks for your guidance, was able to recover.
Foolishly, I had SIMULATE option checked in the recovery settings. Though was able to boot into system but no account, no google & reset stuck into recovery.
Thanks a ton
(I was trying to reset this device for my father)

flutterguy317 said:
I'm not entirely sure, but it sounds like everything in TWRP is being simulated, which would mean that no files are actually written. Try going into Settings in TWRP, uncheck the "Simulate actions" checkbox, and run the rom installation again.
Click to expand...
Click to collapse
How do you get into settings when it goes straight to simulating actions?

[Q] bootloader kitkat gt-i9500

So i upgraded to 4.4.2 and somehow the os got into salad status.
I was wondering if there is a bootloader file that will allow be to regain hold of the that area and be able to reload a kitkat rom
i believe i downloaded prior versions of the bootloader file and it didn't work giving the error of the magic string. i presume that's for a prior to 4.4.2
But is there a bootloader file that will breath new breath into it -
If I as a 10 thumbs expert is inept, can anyone guide me to someone able to repair it, I AM WILLING TO PAY THE ASKING RATE TO ANYONE THAT FEELS UP TO THE JOB.
I will be immensely grateful to anyone that can assist this 70 y.old in need of his phone. at my age fixed income is hardship
MUCH APPRECIATED

I read your story 3 times but I have absolutely no idea what you are talking about.
- What is "salad status"?
- Do you want to downgrade your rom or do you want to reflash the rom?
- Breath new breath into it? What does that mean?

to be or not to be
before the disaster i had loaded the revosoft 4.4.2 rom at a point the phone rebooted and in middle of boot it stopped.
right now when started it stopped 3 or 4 notes before the end of the samsung tune. and it dies there.
i tried - download mode - via odin several roms although the odin message says pass, the phone still stops at the logo
recovery mode - i get an efs error and it does not load the rom, it aborts during and reboots, and it stops at the logo
i tried to load a bootloader hoping to help erase the existing failed bootloader with a fresh one. the bootloader i got failed via odin (the message on the phone was - missing magic string - and fail on odin)
that's why i asked if anyone had the new 4.4.2 bootloader to help me restart propely the phone OTHERWISE
i was willing to pay for a capable technician to do the job
better and thanks if you are able to assist
Lennyz1988 said:
I read your story 3 times but I have absolutely no idea what you are talking about.
- What is "salad status"?
- Do you want to downgrade your rom or do you want to reflash the rom?
- Breath new breath into it? What does that mean?
Click to expand...
Click to collapse

First of all:
Did you make a backup of your rom before you flashed the revosoft rom?
Can you give us the exact error you are getting in the recovery. The EFS error.

fingers crossed
1) yes i have a backup of the previous setup - and i do have full backups - so i am not worried about wiping everything
2) when i go into recovery - i get this error - without doing anything - just by entering recovery mode
e:failed to mount /efs(invalid argument) = twice
# MANUAL MODE #
--Appling Multi-CSC ...
Applied the CSC-cod : unknown
Successfully applied multi-CSC
top of the screen reads
Android system recovery <3e>
KOT49H i950xxufne4
i stop here in case you want to proceed with other instructions -
btw i tried to reload the previous backup and IT also died at the logo
thank you for your patience - always bare in mind i am willing to ship this anywhere in case it needs a good surgeon - money is no object as long as it does not cost the price of a new smartphone
sincerely
Lennyz1988 said:
First of all:
Did you make a backup of your rom before you flashed the revosoft rom?
Can you give us the exact error you are getting in the recovery. The EFS error.
Click to expand...
Click to collapse

exactly same problem , but i was running hassan rom when this happened

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.