Happening OTA on my SNS as I type this - WHOO-HOO!
No! Mine won't work, i select restart and install, the phone reported with the little android and box with the update progress bar, half WA through the box changed to A warning triangle,what am i supposed to do, there is now nothing in system updates, please help.
Sorry to hear that SWFlyerUK, I can't help with any suggestions I'm afraid.
However, mine is good and I'm having a play with it now - haven't seen much difference thus far though.
Thanks.
I've tried renaming it to update.zip then restart phone holding down volume up, recovery, the Google screen shows then the box and little android then the warning triangle, I've never been able to get into recovery, always me lol
When on the triangle press up + power again and the recovery menu will appear.
Nope thats not doing anything, the only way for me to turn the phone off is to remove the battery - is my device then "update bricked" So I can't access recovery?
When I first turn on the device with the power + volume up I enter the bootloader no problem, when I scroll down to "recovery" the Google screen is shown with the little unlocked padlock, then the box and android, then that changes to the warning triangle and android then nothing happens, can't turn off or anything without removing the battery.
SWFlyerUK, you should try to press keys in different order, press power first and then volume up.
I stayed 5 minutes as you wondering why it didn't work !!!!
Congratulation JTHM, but can you post your start version and the link of the update please ?
Worked a charm - updating now, thanks mate!
Though I'm now getting an error on install;
asset failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "google/so ju/crespo:2.3.3/GRI40/102588:user/release-keys" || file_getprop("/system/build.prop", ro.build.fingerprint") == "google/so ju/crespo:2.3.4/GRJ22/121341:user/release-keys
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation Aborted.
I'm currently on 2.3.3, is it because i'm installing the wrong update?
My model is GRH78C I9020XXJK8 and installing an i9020T
GRI40, KB1 update?
My origional update that was download via OTA this morning is no longer on my device.
Correction, I do still have the origional called update.zip, but thats not working either.
SWFlyerUK said:
Though I'm now getting an error on install;
asset failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "google/so ju/crespo:2.3.3/GRI40/102588:user/release-keys" || file_getprop("/system/build.prop", ro.build.fingerprint") == "google/so ju/crespo:2.3.4/GRJ22/121341:user/release-keys
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation Aborted.
I'm currently on 2.3.3, is it because i'm installing the wrong update?
My model is GRH78C I9020XXJK8 and installing an i9020T
GRI40, KB1 update?
My origional update that was download via OTA this morning is no longer on my device.
Click to expand...
Click to collapse
GRH78C is 2.3.2 not 2.3.3 which is why you get that error. You need to upgrade to 2.3.3 (GRI40) first before you can use the upgrade. The script checks for GRI40 and it doesn't find it so it aborts.
Sent from my Nexus S
I got a nice little surprise this morning. The OTA update was waiting for me to install. I didn't have to wait long at all to get. It took a couple weeks for 2.3.3 to land on my phone, but 2.3.4 took a few of days since it was announced. Not too shabby.
Sent from my Nexus S using Tapatalk
Ok so I've got 2.3.3 download, gone to apply the update which got further but was yet again aborted,
I've got assert failed:apply_patch_check("MTD:boot:2949120:ddf4dec1310bc3213cbdee1f4915e86f045755b:2945024:75a5866e391831bdc85dc6a75f81c08f6c5427")
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation Aborted.
I'm sure its the correct file. 98f3836cef93.signed.soju-GRI40-fromGRH78C.98f3836c.zip
If I'm currently rooted on 2.3.3 will my device still receive updates if an OTA upgrade is available or I have to go manual?
Would a total reformt etc of my phone help?
lolopro said:
Congratulation JTHM, but can you post your start version and the link of the update please ?
Click to expand...
Click to collapse
2.3.1 (SIMfree) when I woke this morning -> automatic OTA update straight to 2.3.4.
As it was automatic OTA I don't have a download link. Nice surprise though.
Try flash 2.3.3 full ROM? That's what I did to remove CM7 and get back to stock in order to update to 2.3.4.
Si_NZ said:
Try flash 2.3.3 full ROM? That's what I did to remove CM7 and get back to stock in order to update to 2.3.4.
Click to expand...
Click to collapse
Where do I find a 2.3.3 full rom for my I9023, xxxkb3?
I need it to remove my current CM7 before I can manually flash 2.3.4 into my phone. Would really appreciate it alot if you could guide me.
What do I need to do to ensure I get the OTA update??? Thanks in advance
Sent from my Nexus S using XDA Premium App
Should I do a factory reset on my phone?
Related
http://community.sprint.com/baw/message/133820#133820
I'm guessing that if you install it, you would lose root. Is that correct?
Not likely. Expect that whenever they have a release for android 2.0, but this is only supposed to address the known bugs caused by HTC's software.
sweet!! thanks for the update
flipzmode said:
Not likely. Expect that whenever they have a release for android 2.0, but this is only supposed to address the known bugs caused by HTC's software.
Click to expand...
Click to collapse
This is supposedly the one that will fix the messaging app and a few other minor things. Not a full fix but not 2.0 either.
so we (rooted ones) can go ahead and install this when its ready and it wont affect our root access?
Honestly, we won't know if it actually fixes the root vulnerability or not until it's out.
i hope not as of last night the only internet acces i have now if from my hero wifi tether lol
Just an FYI from what I've read (in how HTC and Sprint have worded it) it seems that this will be an automatic update that will get pushed to your phone.
There is actually service that runs in the background at all times on our phone called Sprint Updater. Also /system/app/Sprint_App_Updater.apk.
So other than killing those I don't know that you will be able to prevent this update from even coming through. I still don't believe it will affect root status but truly we won't know.
FYI...update is now live (3748377 byte package).
c4sp14nx said:
FYI...update is now live (3748377 byte package).
Click to expand...
Click to collapse
It is? How do I check?
gqukyo said:
It is? How do I check?
Click to expand...
Click to collapse
mine still doesn't show there being any firmware updates
Firmware update is 3748377 bytes takes about 2-4 minutes to download depending coverage area. Update is version 1.56.651.2, and you will not be able to make or receive calls during installation and it'll reset and you'll see it an box with arrow to phone icon.. rooted does not update
Finding update package...
Opening update package...
Verifying update package...
Installing update...
E:Error in applypatch
(Status 256)
E:Failure at line 137:
run_program PACKAGE:applypatch -c /system/app/LearnMore.apk 60305252684acd750b923921dea244df29127aaf e3e88ad00025fda1b4b8e7d6633549c88cb437e3c
Installation aborted.
It maybe cause I took of LearnMore.apk from the phone someone else can try, phone works after testing.. even if rooted phone works
You will need to go back to stock rom, then do it.. download update. Once completed just root it back
FYI, My Gutted rom does not have the sprint_app_updater.apk app so you should be safe with my rom. Also, this means you can't update until someone dumps it and we make a new rom with it. But at least you wont lose root. I can't remember if version 1.0 has the updater but I know my soon to be released 1.1 does not have it.
GODZSON said:
Go to firmware update, and select update.. its 3748377 bytes takes about 2-4 minutes to download depending coverage area. Update is version 1.56.651.2, and you will not be able to make or receive calls during installation and it'll reset and you'll see it an box with arrow to phone icon..
Click to expand...
Click to collapse
Yup, I already tried that before I posted. States no update is available... maybe they're rolling it out slowly... I do have the MoDaCo rom installed though...
I too have the MoDaCo rom installed, no firmware update for me in DC area.
No luck updating on my rooted hero. The phone rebooted after downloading the update and it booted back up into the recovery mode where it said the update wasn't verified (or something along those lines). Looks like the recovery image might be getting in the way.
GODZSON said:
Go to firmware update, and select update.. its 3748377 bytes takes about 2-4 minutes to download depending coverage area. Update is version 1.56.651.2, and you will not be able to make or receive calls during installation and it'll reset and you'll see it an box with arrow to phone icon.. rooted does not update.
Click to expand...
Click to collapse
So can you confirm...does it break root?
when I check the firmware update it tell me that I have a update available, but when i try to download it, it keeps on failing
any ideas?
My phone is rooted.
tmidle8575 said:
I too have the MoDaCo rom installed, no firmware update for me in DC area.
Click to expand...
Click to collapse
Ditto. Also DC area.
GODZSON said:
Firmware update is 3748377 bytes takes about 2-4 minutes to download depending coverage area. Update is version 1.56.651.2, and you will not be able to make or receive calls during installation and it'll reset and you'll see it an box with arrow to phone icon.. rooted does not update
Finding update package...
Opening update package...
Verifying update package...
Installing update...
E:Error in applypatch
(Status 256)
E:Failure at line 137:
run_program PACKAGE:applypatch -c /system/app/LearnMore.apk 60305252684acd750b923921dea244df29127aaf e3e88ad00025fda1b4b8e7d6633549c88cb437e3c
Installation aborted.
It maybe cause I took of LearnMore.apk from the phone someone else can try, phone works after testing..
Click to expand...
Click to collapse
aeroterp said:
Ditto. Also DC area.
Click to expand...
Click to collapse
MoDaCo's ROM's usually do OTA updates only of itself I thought...
I am pretty confident that the GSM ROM does this but does the CDMA do this too? In which case you wouldn't see an update from Sprint.
EDIT: Update applied and root still works.
Universal FRF91 OTA Update:
http://android.clients.google.com/packages/passion/signed-passion-ota-43546.cc653ee4.zip
FRF85B to FRF91 Build:
http://android.clients.google.com/packages/passion/signed-passion-FRF91-from-FRF85B.db99fdf1.zip
(Alternatively, you may also do a *#*#CHECKIN#*#* in order to get to FRF91 once you are on FRF85B)
Also, for anyone looking to get to FRF85B from an older build (GSM or AWS):
http://www.megaupload.com/?d=WMCZIIIB
ERE27 to FRF91:
http://android.clients.google.com/packages/passion/signed-passion-FRF91-from-ERE27.e410116a.zip
ERE36B to FRF91:
http://android.clients.google.com/packages/passion/signed-passion-ota-43546.cc653ee4.zip
FRF50 to FRF91:
http://android.clients.google.com/packages/passion/signed-passion-FRF91-from-FRF50.836691a1.zip
EPF21B to FRF91
http://android.clients.google.com/p...R_FRF91-1.13.1700.1_EPF21B_release_signed.zip
Instructions:
1. Download the update from one of the links above.
2. Rename the file to update.zip. Note that if you're using Windows, just rename it to "update" (no quotes, of course) because it's already a zipped file.
3. Copy the update.zip file onto your microSD card.
4. With your Nexus One off, hold down the trackball and press the power button.
5. You'll be booted into a white screen with three Android robots on skateboards. Select "Bootloader."
6. On the next screen, select "Recovery."
7. Your phone will reboot, giving you a picture of the Android robot and an exclamation point inside a triangle.
8. Now press the power button and volume up button at the same time. It could take a couple of tries.
9. Now (using the trackball this time) choose "Apply sdcard:update.zip" and let things run their course.
(Note: Before doing step 9 you can also run the "Wipe Cache Partition" option. This has been known to help with the soft key accuracy on the nexus one (optional. This causes no data loss.)
*************************************
By Popular Demand (Credit to lox):
Update.zip to flash with custom recovery
This is the totally stock FRF91 repacked as update.zip. The radio hasn't changed since FRF50, so if you are using it, you can keep it and install the noradio version.
Download:
- without radio image: multiupload (md5sum: 041b1e21433e636340ca6b56f141a315)
Root
To root FRF91, just flash this update.zip (contains busybox, superuser.apk, su, unsecured boot.img) (md5sum: c6c27598c210576792d6d56738a2edde)
just saw this on the google forum and was going to post. Great job! Now excuse me while I update
texas-saluki said:
just saw this on the google forum and was going to post. Great job! Now excuse me while I update
Click to expand...
Click to collapse
Haha! Ya the news is spreading like wild fire
Lets see if we can crash google's servers lol.
are we going to see newer froyo updates after this one?
Just updated from Stock 2.1 on AT&T. Thank you!
Its for real this time. My phone is updating as I type. I cant wait...
So while waiting for my 5 minute between post restriction to expire ive seen the phone boot and noticed a few things. The power control widget takes a while to load. You have to re-authenticate to facebook and my Exchange calendar was automatically added.
Downloaded the file from Google's servers and shall be applying as soon as my classwork done.
Just signed up to say...
THANK YOU!!!
I have been patiently waiting for Froyo while seeing my friend who works for Google just happily loving Froyo alone.
Anyway, thank you thank you thank you!
i can definitely confirm that this works. thanks!
arcticreaver said:
are we going to see newer froyo updates after this one?
Click to expand...
Click to collapse
my understanding is that this is the final froyo build that is going out ota. People are receiving the update in waves so this should be official.
So I'm on ATT nexus and rooted and running the latest r19. Is this the final version that both t-mobile and ATT versions will get? Or is this a second version only for ATT phones?
Should I upgrade to this if I'm rooted already?
FINALLY. Thanks a bunch
My Nexus is updating right now
Glad I'm the first to have problems...
Stock N1 at&t bands, when I apply the update per the steps in the OP, I get
Finding update package...
Opening update package...
Verifying update package...
E:failed to open /sdcard/update.zip (no such file or directory)
E:signature verification failed
Installation aborted.
I've tried it 3 times, reformatted the sdcard so the update.zip was the only thing on it, down loaded the file twice...I'm lost.
Signed,
At the mercy of the XDA Gods!
Sorry for this question, but...
If I update my Nexus AT&T with this rom, will it avoid its warranty? Is it the official update provided by Google?
Thanks a lot.
davidusr said:
Glad I'm the first to have problems...
Stock N1 at&t bands, when I apply the update per the steps in the OP, I get
Finding update package...
Opening update package...
Verifying update package...
E:failed to open /sdcard/update.zip (no such file or directory)
E:signature verification failed
Installation aborted.
I've tried it 3 times, reformatted the sdcard so the update.zip was the only thing on it, down loaded the file twice...I'm lost.
Signed,
At the mercy of the XDA Gods!
Click to expand...
Click to collapse
I have the same issue.
make sure the file is not update.zip.zip
sifuhall said:
I have the same issue.
Click to expand...
Click to collapse
I had that problem as well. I tried twice.
http://www.engadget.com/2010/06/28/...85-hitting-atandt-nexus-one-owners-ota-right/
Go there. Notice how there's an "update", "update 2" and "update 3"? Try downloading the link from "update 3". Of course you wanna make sure you rename it "update.zip". Transfer it to your sdcard and then try again.
Also, for those who do not know how to update manually:
Rename the downloaed file to update.zip
Put it at the root of your SD-Card and then turn off the phone.
Hold down the volume button and then press the power on button, it should go into a boot screen. Wait for a few seconds for it to load up proper and then select "Recovery" with the volume down/up button and press the power button.
Once you see an android holding a sign with an exclamation mark push volume down+ volume up + power button _at the same time_.
Select "apply sdcard:update.zip"(or something similiar) with the trackball and press it.
After the update is finished select "reboot system now" with the trackball and press it.
Click to expand...
Click to collapse
luffyz said:
make sure the file is not update.zip.zip
Click to expand...
Click to collapse
Thats what it was. Came back to let the other guy know, but ya beat me to it.
Rename it to "update" with out the .zip. Worked for me.
Thanks!
Still not work for me. Already rename to update; but is still saying E:signature verification failed !!!
Worked for me!
Getting root without unlocking the bootloader worked after updating to FRF85B too!
Hello All, I'm receiving an error when trying to revert to stock from Overcome UX mod.
I'm receiving the following error...
assert failed: getprop("ro.bootloade") == "P7100BUKB7"
E:Error in /sdcard/hc-3.1_ota-full_sam_tab_10.1.zip
(Status 7)
Installation Aborted.
Any ideas?
More information, please. Which tab do you have? What are you doing to return to stock? What preceded the error message.
Really folks, if you have a problem, put some info into the OP so people can get a sense of what happened.
slack04 said:
More information, please. Which tab do you have? What are you doing to return to stock? What preceded the error message.
Really folks, if you have a problem, put some info into the OP so people can get a sense of what happened.
Click to expand...
Click to collapse
Sorry. Using a 16gb WiFi US Galaxy Tab 10.1. I figured it out though.
Had to flash recovery-cwm_4.0.0.4-sam-tab-10.1.tar.md5 via odin
Then installed the stock hc-3.1_ota-full_sam_tab_10.1.zip via cwm
Then odined stockretail.tar.md5... voila back to stock.
Thanks for replying.
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!
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.