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.
Related
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!
Software version is WW_21.40.0.1692. Download the update now.
BTW, it's only for model no. ZD551KL.
-- Source and download link
See the changelog too before updating, so that you can decide on creating necessary backups if one of the apps you use are getting the axe in the update.
From Official Website
Description
ASUS ZenFone Selfie software Image: V21.40.0.1692 for WW SKU only*
Improvement Item:
1) Update OS to Andorid M
2) APP2SD won’t be supported in Android 6.0 (Marshmallow). Please move apps to the internal storage before system upgrade.
3) The apps listed below will no longer be pre-loaded once your device has been upgraded to Android 6.0 (Marshmallow).
Thanks for your support.
1.ASUS Backup
2.Mirror
3.Remote Link
4.Party Link
5.PC Link
6.Photo Frame
7.What's Next
8.ASUS MyFrame
9.ASUS MyWater
10.Omlet
11.Data Transfer
12. Snap View
13.EZ 訂
14.Dr. Eye
15.Yahoo 購物中心
4) Add new features and new apps:
- Google Calendar
- Google Messenger
- Motion Gesture
- Camera: Pano Sphere Mode
5)Remove Asus Email, Asus Calendar, Asus Messaging after Factory Reset. You could use Gmail, Google Calendar, Google Messenger for relevant services.
For more information please refer to:
TW：http://www.asus.com/zentalk/tw/ReleaseNotes
WW：http://www.asus.com/zentalk/ReleaseNotes
File Size 1.63 GBytesupdate 2016/06/30
Download from Global
Click to expand...
Click to collapse
I'm currently downloading firmware, will install soon when i downloaded. Now just waiting for easy root method.
Getting some problem during update to Android , also other version too.
E: Error in /sdcard/UL-ZOOT-WW-1.15.40.1582-user.zip (Status 1)
E: fota_return_code 408
amanjumon said:
Getting some problem during update to Android , also other version too.
E: Error in /sdcard/UL-ZOOT-WW-1.15.40.1582-user.zip (Status 1)
E: fota_return_code 408
Click to expand...
Click to collapse
Are you on the latest version without modifications?
Sent from my ASUS_Z00A using XDA Labs
krasCGQ said:
Are you on the latest version without modifications?
Sent from my ASUS_Z00A using XDA Labs
Click to expand...
Click to collapse
Bought new phone 2 days ago before Boot Loop, and it was completely new. Version was 1.13, I didn't unlock bootloader ever.
amanjumon said:
Bought new phone 2 days ago before Boot Loop, and it was completely new. Version was 1.13, I didn't unlock bootloader ever.
Click to expand...
Click to collapse
Try to flash back Lollipop stock firmware...
Sent from my ASUS_Z00A using XDA Labs
Enable Adoptable Storage ?
Like the Zenfone 2 Laser (ZE500KL), Adoptable Storage is disabled by looking at the changelog.
I'm about to buy this phone but I do really need it, I know it's possible to enable it back (with adb, etc) but I want to be sure before.
Can someone who switched to Android Marshmallow try to get it back and tell if they've succeeded on the Zenfone Selfie ?
krasCGQ said:
Try to flash back Lollipop stock firmware...
Sent from my ASUS_Z00A using XDA Labs
Click to expand...
Click to collapse
I tried almost 3 page in Google Search to fix. First of All I didn't unlock bootloader and downloaded 3 firmware which is M, 1.13(Stock), 1.15. And try to flash them all. Every time I failed. Also try to flash with flashboot mode also same problem as like as Install From SD.
E: Error in /sdcard/UL-ZOOT-WW-1.15.40.1582-user.zip (Status 1)
E: fota_return_code 408
Click to expand...
Click to collapse
or sometime
E: Error in /sdcard/UL-ZOOT-WW-1.15.40.1582-user.zip (Status 7
E: fota_return_code 408
Click to expand...
Click to collapse
One more thing that there was no OTA update option in my phone. If you belive that you can fix it or can help me.
Add Me in Skype: amanullahjumon
Click to expand...
Click to collapse
Now my phone is Dead
solution
amanjumon said:
I tried almost 3 page in Google Search to fix. First of All I didn't unlock bootloader and downloaded 3 firmware which is M, 1.13(Stock), 1.15. And try to flash them all. Every time I failed. Also try to flash with flashboot mode also same problem as like as Install From SD.
or sometime
One more thing that there was no OTA update option in my phone. If you belive that you can fix it or can help me.
Now my phone is Dead
Click to expand...
Click to collapse
I had the same problem bro, just flash the cn recovery and flash, your're good to go.
I have a rooted zenfone selfie, how can I update?
mashruk said:
I had the same problem bro, just flash the cn recovery and flash, your're good to go.
Click to expand...
Click to collapse
Already fixed after posting that comment. Now working with CM but no more ASUS stock rom.
Can't flash the ROM on my phone
I already tried to flash this ROM with my phone (Build LRX22G.CN_user_1.13.40.661_20151103044030520_2015052101030030000500001) several times via "apply update via sd card" and as well via adb sideload. Both of them don't work. I also tried to flash different Lollipop stock firmwares (WW_1.12.40.382 and WW_1.15.40.1582), doesn't work either. I always get the errors: "E: failed to verify whole-file signature" and "E: signature verification failed". Can somebody help me?
Edit: I ordered the phone from China, maybe that's why I have this "strange" build number? Is there any possibility to flash Marshmallow on a Chinese phone? In my options menu I don't have any updates option unfortunately
I have bootloader unlocked, I downloaded nougat 7.0 firmware and tried to update manually, everything installs normally, but at the time of calling it says that the system is corrupted.
I already tried to put the boot and recovery of the version 7.0, already tried to put of the old, but always of the same thing, only version that works is previousor, someone knows how to do?
luizflb said:
I have bootloader unlocked, I downloaded nougat 7.0 firmware and tried to update manually, everything installs normally, but at the time of calling it says that the system is corrupted.
I already tried to put the boot and recovery of the version 7.0, already tried to put of the old, but always of the same thing, only version that works is previousor, someone knows how to do?
Click to expand...
Click to collapse
Whats the link for the manual download, ill experiment with it when i can update
Sm0k3r83 said:
Whats the link for the manual download, ill experiment with it when i can update
Click to expand...
Click to collapse
i used this link: http://dlcdnet.asus.com/pub/ASUS/Ze...ser.zip?_ga=1.245707268.1656347377.1488140054
Finished the update, all went well. Was a little laggy at first, so i cleaned the cache. Then rooted. Everything seems to be fine for me
same issue here. I can't update both with trwp and stock recovery. Originally my zenfone 3 was TIM SKU. Should be that the reason?
Hai.... someone could help me, I need recovery.image for asus ze520kl
zulfikarbugis said:
Hai.... someone could help me, I need recovery.image for asus ze520kl
Click to expand...
Click to collapse
mega.nz/#F!ok0V0RIA!5WKtHe98opzjVI3NPbM7Ww
Nobody knows a solution? I have tried to change the reocvery and the boot to the nougat version, and install the firmware manually, everything installs normally without errors, but when it connects it appears the following message "your device software can not be checked for corruption, Please lock the bootloader".
The cell phone is just that and I have to go back to the previous version!
I already took root, xposed and everything, and it always gives the same thing!
luizflb said:
Nobody knows a solution? I have tried to change the reocvery and the boot to the nougat version, and install the firmware manually, everything installs normally without errors, but when it connects it appears the following message "your device software can not be checked for corruption, Please lock the bootloader".
The cell phone is just that and I have to go back to the previous version!
I already took root, xposed and everything, and it always gives the same thing!
Click to expand...
Click to collapse
Same issue here =(
luizflb said:
Nobody knows a solution? I have tried to change the reocvery and the boot to the nougat version, and install the firmware manually, everything installs normally without errors, but when it connects it appears the following message "your device software can not be checked for corruption, Please lock the bootloader".
The cell phone is just that and I have to go back to the previous version!
I already took root, xposed and everything, and it always gives the same thing!
Click to expand...
Click to collapse
Updating thru TWRP results in an Error 7.
mxdxl said:
Updating thru TWRP results in an Error 7.
Click to expand...
Click to collapse
You did not understand, I installed the original recovery, both the last version of 6.0 and the version of 7.0, all install the update without error, but when it goes online does not work and I have to go back to the previous version
Raw firmware
I have the same issue. My phone was branded "tim italy". When i bought it, I flashed the WW version via asus flash tool, and I'm currently able to update till the last M version, which is the ......152.
If i try to update to Android N, my phone will not boot, giving me the corruption message and shutting down after 10 seconds. I also tried to perform the dm restore procedure; the dm error disappeared but the system is stuck on the Asus boot screen
I believe that the only solution is to flash a Nougat RAW firmware via asus Flash tool. Does Anyone have a download link for the N version ?
I have the same problem .. is there who can help?
`same problem can't update to nougat but my error is signature verification
hope someone can help us both
---------- Post added at 11:00 AM ---------- Previous post was at 10:48 AM ----------
Sm0k3r83 said:
Finished the update, all went well. Was a little laggy at first, so i cleaned the cache. Then rooted. Everything seems to be fine for me
Click to expand...
Click to collapse
Did you unlocked before updating?
same problem here....i downloaded the update and put it in internal storage...it automatically detected system update but when i try to update it it failed during installation....anyone help pls
mxdxl said:
Updating thru TWRP results in an Error 7.
Click to expand...
Click to collapse
if you want to update with twrp you must modify the update-script file placed in
UL-ASUS_Z012D-WW-14.2015.1701.8-user/META-INF/com/google/android
i have uploaded my one, if you can't modify the file you can download it and replace it in zip file
ExperienceTesla said:
if you want to update with twrp you must modify the update-script file placed in
UL-ASUS_Z012D-WW-14.2015.1701.8-user/META-INF/com/google/android
i have uploaded my one, if you can't modify the file you can download it and replace it in zip file
Click to expand...
Click to collapse
This works well? I have unlocked the bootloader and root my device. if this works for it?
zulfikarbugis said:
This works well? I have unlocked the bootloader and root my device. if this works for it?
Click to expand...
Click to collapse
The solution to the picture is Flash through the course
JadeKubPom said:
The solution to the picture is Flash through the course
Click to expand...
Click to collapse
I've done this but still fails. My phone will not boot, giving me the corruption message and shutting down after 10 seconds.
zulfikarbugis said:
I've done this but still fails. My phone will not boot, giving me the corruption message and shutting down after 10 seconds.
Click to expand...
Click to collapse
mine does the same even with the right update-script.
When i try to update using stock recovery i get failed signature message
[TA-1053] Official OTA 8.1 - Stuck at Recovery with "No command" warning after update
Hey guys,
I received the official update for Android 8.1 on my Nokia 5 TA-1053. I had no root, no Custom Recovery and bootloader locked.
During the update, as usual, the phone rebooted, and I got a error waring "No command". The waring is in recovery mode and I can access recovery options like "updtade from ADB, SD Card. Tried uptading with Android 8.0, but after reboot, still get the same error.
Does anyone have any clue?
Erkyem said:
Hey guys,
I received the official update for Android 8.1 on my Nokia 5 TA-1053. I had no root, no Custom Recovery and bootloader locked.
During the update, as usual, the phone rebooted, and I got a error waring "No command". The waring is in recovery mode and I can access recovery options like "updtade from ADB, SD Card. Tried uptading with Android 8.0, but after reboot, still get the same error.
Does anyone have any clue?
Click to expand...
Click to collapse
That happened to me too, I had to rollback to 7.1 flashing December update and flashing OST before I was able to use my phone again.
If you haven't yet recovered your phone, I uploaded April and May OTAs here:
https://forum.xda-developers.com/showpost.php?p=76513215&postcount=61
If that doesn't work, you will have to do what I did to get my phone up and running
Hi, and thanks.
I spent the night, without any success, trying to downgrade, using this https://forum.xda-developers.com/nokia-5/how-to/guide-how-to-downgrade-official-oreo-to-t3746007.
The OST flashing the nb0 but always fails with error "BATTERY_VOLTAGE_TOO_LOW_FAIL (0xA24B)". I Tried many, many times. If I sideload the OTA through adb (OTA is around 1.7 GB) it will fail at around 47%. Error message on ADB: "adb: failed to read command: No error". Error on phone: "Warning: no" and cannot read anymore. Then it goes to the little android screen with the no command warning, again.
Tried unlock bootloader now, without success. Maybe I need the full OTA for 8.1, but I'm not able to find it.
Erkyem said:
Hi, and thanks.
I spent the night, without any success, trying to downgrade, using this https://forum.xda-developers.com/nokia-5/how-to/guide-how-to-downgrade-official-oreo-to-t3746007.
The OST flashing the nb0 but always fails with error "BATTERY_VOLTAGE_TOO_LOW_FAIL (0xA24B)". I Tried many, many times. If I sideload the OTA through adb (OTA is around 1.7 GB) it will fail at around 47%. Error message on ADB: "adb: failed to read command: No error". Error on phone: "Warning: no" and cannot read anymore. Then it goes to the little android screen with the no command warning, again.
Tried unlock bootloader now, without success. Maybe I need the full OTA for 8.1, but I'm not able to find it.
Click to expand...
Click to collapse
Did you try the OTAs I listed?
If they didn't work, try to flash one of the OTAs here:
https://forum.xda-developers.com/nokia-5/development/ota-nokia-5-ta-1053-monthly-ota-zip-t3655123
They are much smaller. Then you can try flashing OST
BTW I hope you didn't try flashing any of the nb0 files from the mega link in the post you mentioned. None of them are Nokia5 nb0s
If you don't have one, you can try the one in this link:
https://drive.google.com/file/d/0B60NFIDB93wudDNXaG5vMkEyWVE/view
redweaver said:
That happened to me too, I had to rollback to 7.1 flashing December update and flashing OST before I was able to use my phone again.
If you haven't yet recovered your phone, I uploaded April and May OTAs here:
https://forum.xda-developers.com/showpost.php?p=76513215&postcount=61
If that doesn't work, you will have to do what I did to get my phone up and running
Click to expand...
Click to collapse
Please, what did you do? Flashing Dec Update then using an nb0 file with OST, it got stuck at "Connection Failed, 0xc6da" Error; do you have any idea of what I should do?
K1r1k4z3 said:
Please, what did you do? Flashing Dec Update then using an nb0 file with OST, it got stuck at "Connection Failed, 0xc6da" Error; do you have any idea of what I should do?
Click to expand...
Click to collapse
You got this error when flashing the nb0?
redweaver said:
You got this error when flashing the nb0?
Click to expand...
Click to collapse
Yes, I did. I have no idea what it means.
K1r1k4z3 said:
Yes, I did. I have no idea what it means.
Click to expand...
Click to collapse
How many times did you try again?
redweaver said:
How many times did you try again?
Click to expand...
Click to collapse
Severally.
Meanwhile, the OST tool won't run on my Windows 10 PC. I get this error. Is there something I'm missing if you've run this tool on Windows 10 before. Meanwhile I'm at PH.
K1r1k4z3 said:
Severally.
Meanwhile, the OST tool won't run on my Windows 10 PC. I get this error. Is there something I'm missing if you've run this tool on Windows 10 before. Meanwhile I'm at PH.
Click to expand...
Click to collapse
I don't like Windows 10. My lappy comes with Win 8.1. I had to dual boot win 7 just to run OST
redweaver said:
I don't like Windows 10. My lappy comes with Win 8.1. I had to dual boot win 7 just to run OST
Click to expand...
Click to collapse
Could you help me with the specific nb0 file you used in flashing yours.
K1r1k4z3 said:
Could you help me with the specific nb0 file you used in flashing yours.
Click to expand...
Click to collapse
I got it from one of those links
https://mega.nz/#!HoNX1CBT!AORGMLndzcbc5iOBrJlLlLKyncZ5hImJirnPApRGj_s
redweaver said:
I got it from one of those links
https://mega.nz/#!HoNX1CBT!AORGMLndzcbc5iOBrJlLlLKyncZ5hImJirnPApRGj_s
Click to expand...
Click to collapse
I'm kinda confused; what's the difference between "ND1-3320-0-00WW-A02.nb0" and "ND1-3700-0-00WW-B03.nb0"
Cos I'm flashing this "ND1-3320-0-00WW-A02.nb0 with the OST right now and it's still stuck at "Reflash Service Bootloader" for over 20mins now. Is this normal?
K1r1k4z3 said:
I'm kinda confused; what's the difference between "ND1-3320-0-00WW-A02.nb0" and "ND1-3700-0-00WW-B03.nb0"
Cos I'm flashing this "ND1-3320-0-00WW-A02.nb0 with the OST right now and it's still stuck at "Reflash Service Bootloader" for over 20mins now. Is this normal?
Click to expand...
Click to collapse
I honestly have no idea. Wait for it to finish or give an error, otherwise you risk bricking your phone for good. Did you "downgrade" to nougat before flashing?
FINALLY! I got my Nokia 5 working like new.
Thanks @redbeaver! You've got no idea, but you helped alot!
redweaver said:
I honestly have no idea. Wait for it to finish or give an error, otherwise you risk bricking your phone for good. Did you "downgrade" to nougat before flashing?
Click to expand...
Click to collapse
I sent you a PM sir, please attend to it.
I've probably messed this thing up just about as badly as I can.
Here's what I can tell you:
Update: I just figured out that you are supposed to put dload onto a separate sd card, So i'll be trying that when the phone comes out of it's coma XD anything else you can suggest is very welcome.
- The phone currently isn't turning on after messing around in twrp(tried to restart into bootloader)
- While trying to get it working, it is now showing up as CAN-L11(likely from trying some backups of others)
- I was unable to use ANY roms I tried. full update files didn't work. always error 7
- It seems in twrp that I'd often get this error: mountencrypt failed to mount /data, despite wiping /data many times
- I've tried using iso files extracted from some update.app, and using that to get system and data on there, as well as recovery too
- I was switching between twrp and default recovery to transfer files and then use dload to try to recover the system, never let me do it though. got to 5% then told me something like: "Getting package info failed". it would do this in the download and recover mode as well when I would hook up to the internet and it would also give me that error.
You are free to ask me any questions about the device.
I think I just need to drain the battery then I should be able to at least get something out of it, but until then, if anyone has any recommendations after it's functional again let me know. Any help is appreciated.
TheProgrammerEX said:
I've probably messed this thing up just about as badly as I can.
Here's what I can tell you:
- The phone currently isn't turning on after messing around in twrp(tried to restart into bootloader)
Click to expand...
Click to collapse
It isn't even charging?
- While trying to get it working, it is now showing up as CAN-L11(likely from trying some backups of others)
Click to expand...
Click to collapse
Yeah, that's why. The model name can be changed in build.prop, but you're still using a CAN-L11 ROM though.
- I was unable to use ANY roms I tried. full update files didn't work. always error 7
Click to expand...
Click to collapse
You haven't flashed the TWRP mentioned in the first post of their thread, hence you've got that error which is basically telling you that you're trying to flash the ROM on an unsupported device (the phone's codename / model is mentioned in TWRP and ROM checks for it), but actually it's working on all models.
- It seems in twrp that I'd often get this error: mountencrypt failed to mount /data, despite wiping /data many times
Click to expand...
Click to collapse
That occurs because TWRP doesn't support decryption. You have to format data, not wipe. You can format it from TWRP > Wipe > Format data.
- I've tried using iso files extracted from some update.app, and using that to get system and data on there, as well as recovery too
Click to expand...
Click to collapse
What happened after you've tried that?
- I was switching between twrp and default recovery to transfer files and then use dload to try to recover the system, never let me do it though. got to 5% then told me something like: "Getting package info failed". it would do this in the download and recover mode as well when I would hook up to the internet and it would also give me that error.
Click to expand...
Click to collapse
Try to unplug the cable from PC. Also, note that I've read in past somewhere that the firmwares from Firmware Finder has to be approved by Huawei and if it isn't, then the stock recovery will fail to flash it. Other Huawei phones has modified / patched stock recovery which allows to flash unapproved firmwares though.
You are free to ask me any questions about the device.
Click to expand...
Click to collapse
How do you guys end up like this? xD
Update: I just figured out that you are supposed to put dload onto a separate sd card, So i'll be trying that when the phone comes out of it's coma XD anything else you can suggest is very welcome.
Click to expand...
Click to collapse
Hah, here's the answer to the above question: not reading xD. Try to slap the phone to wake it from the coma ahahahah xD. When did it get into coma though?