Related
Original links:
http://m.muzisoft.com/soft/80706.html
-
http://rom.htc.shoujifans.com/2014/10/11.html
Mirrors:
https://drive.google.com/uc?id=0Bwq9Di4bqEXkQjhTMmpsN1ZmTXM&export=download
-
https://www.dropbox.com/s/ay5y8s8dg...S_0.57_003_release_385969_signed_2_4.zip?dl=0
Tested and works on STOCK AND LOCKED BOOTLOADERS ONLY!
Your device CANNOT have the *tampered* or unlocked status.
WHEN S-OFF IS ACHIEVED; your device will be able to flash this and downgrade as well if it has been unlocked or tampered with.
-Boot up your device and just drop on your SD card / Internal Storage with the name 0P9CDIAG.zip
-Boot back into bootloader and it AUTOMATICALLY begins.
-Flash twice if uncertain to ensure file has written properly.
Hopefully this will help Single SIM variant development!
P.S.
More mirrors are appreciated!
Drive link gives a 403
Also I have contacted HTC and Virgin Mobile about a RUU, and currently at http://www.htc.com/us/support/htc-desire-816-virgin-mobile/ and http://www.htcdev.com/devcenter/downloads/ there is nothing about a RUU. So wherre did you find it because I have been looking for a RUU for the longest time.
FoxyDrew said:
Drive link gives a 403
Also I have contacted HTC and Virgin Mobile about a RUU, and currently at http://www.htc.com/us/support/htc-desire-816-virgin-mobile/ and http://www.htcdev.com/devcenter/downloads/ there is nothing about a RUU. So wherre did you find it because I have been looking for a RUU for the longest time.
Click to expand...
Click to collapse
Oh snap. Guess I'll have to upload it on dropbox instead. Google drive links tend to be kinked lol. Actually the same way these RUU's posted here from those Japanese, Chinese, Korean websites had listed it. I checked HTC and they have the kernel source but no RUUs for any of these devices US or international.
Sent from my 710C using XDA Free mobile app
Thank you. Was hoping for an RUU. Will Download as soon as you have it up somewhere.
Getting signature fail every time I try to flash.
jaysoblitzed said:
Here it is.
https://drive.google.com/uc?id=0Bwq9Di4bqEXkQjhTMmpsN1ZmTXM&export=download
NEW LINK/MIRROR
https://www.dropbox.com/s/ay5y8s8dg...S_0.57_003_release_385969_signed_2_4.zip?dl=0
Tested and it does work.
Remove all mods/apps that require root first.
Then remove all root files from the settings in SuperSU.
Follow up with a reboot and if the SuperSU app is still there then try to delete it like a normal app.
Go into bootloader and flash the stock recovery.
Then boot back up and just drop on your SD card / Internal Storage with the name 0P9CDIAG.zip
Boot back into bootloader and it AUTOMATICALLY begins.
Received Setup Wizard not responding issue on first initial flash.
Booted into bootloader again did it once more and fixed issue.
Hopefully this will help Single SIM variant development!
P.S.
Mirrors for this file are appreciated!
Click to expand...
Click to collapse
The file you uploaded is corrupted. After trying to flash, now nothing works. I re-unlocked the bootloader, flashed a recovery, and after a fresh wipe no ROM's boot, and my only backup refuses to restore data.
FoxyDrew said:
The file you uploaded is corrupted. After trying to flash, now nothing works. I re-unlocked the bootloader, flashed a recovery, and after a fresh wipe no ROM's boot, and my only backup refuses to restore data.
Click to expand...
Click to collapse
Before you flashed you did remove root from SuperSU, then uninstalled it completely, then flashed the stock recovery and relocked the bootloader right?
I had no idea what would happen if I didn't do those as a safety measure and although, I did notice when I used the RUU and booted up the SuperSU app was still there.
Now what I suggest is using the RUU that you posted to fix the system errors after using this one. I will post the link for the 154MB RUU on HTCDEV. Although I don't recommend anyone to use just one of these IF their rooted and has removed system apps from the device.
Also, it isn't corrupted as I tested it on my device before uploading. Here is where I got it from:
http://m.muzisoft.com/soft/80706.html
And here has the same thing
http://rom.htc.shoujifans.com/2014/10/11.html
Sent from my 710C using XDA Free mobile app
jaysoblitzed said:
Before you flashed you did remove root from SuperSU, then uninstalled it completely, then flashed the stock recovery and relocked the bootloader right?
I had no idea what would happen if I didn't do those as a safety measure and although, I did notice when I used the RUU and booted up the SuperSU app was still there.
Now what I suggest is using the RUU that you posted to fix the system errors after using this one. I will post the link for the 154MB RUU on HTCDEV. Although I don't recommend anyone to use just one of these IF their rooted and has removed system apps from the device.
Also, it isn't corrupted as I tested it on my device before uploading. Here is where I got it from:
http://m.muzisoft.com/soft/80706.html
And here has the same thing
http://rom.htc.shoujifans.com/2014/10/11.html
Sent from my 710C using XDA Free mobile app
Click to expand...
Click to collapse
Yes I locked flashed stock recovery and relocked bootloader before flashing. I cant even flash the one you posted, it gives the verification error, and since it didn't flash, I tried to open it, and whenever I tried to open it or extract it it tells me the file is corrupt.
FoxyDrew said:
Yes I locked flashed stock recovery and relocked bootloader before flashing. I cant even flash the one you posted, it gives the verification error, and since it didn't flash, I tried to open it, and whenever I tried to open it or extract it it tells me the file is corrupt.
Click to expand...
Click to collapse
Should've flashed the recovery before locking...
And if your flashing in recovery mode there is a verification error. Flashing an RUU would not make this error appear. It wouldn't even load after extracting the files from the .zip and your saying it gave a signature error and verification error. Really?
Sent from my 710C using XDA Free mobile app
jaysoblitzed said:
Should've flashed the recovery before locking...
And if your flashing in recovery mode there is a verification error. Flashing an RUU would not make this error appear. It wouldn't even load after extracting the files from the .zip and your saying it gave a signature error and verification error. Really?
Sent from my 710C using XDA Free mobile app
Click to expand...
Click to collapse
I did flash the recovery before locking.
And I didn't flash the RUU in recovery, at first I tried how you said in the OP, and after "checking..." for about 5 minutes it said press power to reboot, and when I did it brought me strait back into Hboot no matter what I did. Then I tried flashing the RUU using "fastboot flash zip "nameofRUUfile".zip, thats when the cmd gave me the "signature verify fail" message. After receiving that message, I tried to open the actual RUU file on my PC using WinRar, thats when it said that the actual file was corrupted.
FoxyDrew said:
I did flash the recovery before locking.
And I didn't flash the RUU in recovery, at first I tried how you said in the OP, and after "checking..." for about 5 minutes it said press power to reboot, and when I did it brought me strait back into Hboot no matter what I did. Then I tried flashing the RUU using "fastboot flash zip "nameofRUUfile".zip, thats when the cmd gave me the "signature verify fail" message. After receiving that message, I tried to open the actual RUU file on my PC using WinRar, thats when it said that the actual file was corrupted.
Click to expand...
Click to collapse
Then its exactly as it says, corrupted. You should re download.
When I open the file with WinRAR I get the following:
android-info.txt
boot_signed.img
dzdata_8g.hdr
dzdata_8g.img
tp_HMX852XD.img
Sent from my 710C using XDA Free mobile app
jaysoblitzed said:
Then its exactly as it says, corrupted. You should re download.
When I open the file with WinRAR I get the following:
android-info.txt
boot_signed.img
dzdata_8g.hdr
dzdata_8g.img
tp_HMX852XD.img
Sent from my 710C using XDA Free mobile app
Click to expand...
Click to collapse
I re-downloaded 3 times, thats why I accused the file you uploaded as being the problem. And I get the same thing you do
android-info.txt
boot_signed.img
dzdata_8g.hdr
dzdata_8g.img
tp_HMX852XD.img
But when I try to open android-info.txt from withing the winrar window, or extracting the archive, thats when I get the corrupted message.
FoxyDrew said:
I re-downloaded 3 times, thats why I accused the file you uploaded as being the problem. And I get the same thing you do
android-info.txt
boot_signed.img
dzdata_8g.hdr
dzdata_8g.img
tp_HMX852XD.img
But when I try to open android-info.txt from withing the winrar window, or extracting the archive, thats when I get the corrupted message.
Click to expand...
Click to collapse
Are you sure it wasn't because you flashed the 154MB file you posted? What happened when you used that one before you posted it?
If my link doesn't work download it from the original source. I was just helping everyone out by uploading it to Dropbox seeing as the servers from those sites tend to move a little slow.
And yes the same uploaders from htcui posted this as well as all the other RUU's found on this devices forum.
Sent from my 710C using XDA Free mobile app
jaysoblitzed said:
Are you sure it wasn't because you flashed the 154MB file you posted? What happened when you used that one before you posted it?
If my link doesn't work download it from the original source. I was just helping everyone out by uploading it to Dropbox seeing as the servers from those sites tend to move a little slow.
And yes the same uploaders from htcui posted this as well as all the other RUU's found on this devices forum.
Sent from my 710C using XDA Free mobile app
Click to expand...
Click to collapse
Im sure I wasn't flashing the other one, and the other file I posted isn't even a flashable file.
And I've been downloading that since you gave me the link it's just going very slow. But what I don't get is why attempting to flash that RUU broke my /data partition. I can't mount it or restore it from backups.
FoxyDrew said:
Im sure I wasn't flashing the other one, and the other file I posted isn't even a flashable file.
And I've been downloading that since you gave me the link it's just going very slow. But what I don't get is why attempting to flash that RUU broke my /data partition. I can't mount it or restore it from backups.
Click to expand...
Click to collapse
You posted it without testing it but tested mine and ran into issues? If someone tried your file they might be in the same situation your in now.
I think you should flash the one you posted on top of the one I did the same way you did for this file.
But retry the RUU posted as I got the same thing in the bootloader when it says press power to reboot but when I did the phone booted up but I ran into a "setup wizard is not responding" error when it fully booted up. Flashed again and was fixed.
As I said flash the HTC file now available to fix any issues with startup as this RUU may contain the files/apps but the RUU you posted organizes the files/apps for the system in the correct manner I believe.
Sent from my 710C using XDA Free mobile app
jaysoblitzed said:
You posted it without testing it but tested mine and ran into issues? If someone tried your file they might be in the same situation your in now.
I think you should flash the one you posted on top of the one I did the same way you did for this file.
But retry the RUU posted as I got the same thing in the bootloader when it says press power to reboot but when I did the phone booted up but I ran into a "setup wizard is not responding" error when it fully booted up. Flashed again and was fixed.
As I said flash the HTC file now available to fix any issues with startup as this RUU may contain the files/apps but the RUU you posted organizes the files/apps for the system in the correct manner I believe.
Sent from my 710C using XDA Free mobile app
Click to expand...
Click to collapse
My file couldn't of hurt anyone's device, as I said, it wasn't even a flashable file. Your file is the one that has my phone not working. Your RUU WON'T flash, and as I stated the file I posted is not a RUU of any kind, I don't know why you insist on me flashing it.
FoxyDrew said:
My file couldn't of hurt anyone's device, as I said, it wasn't even a flashable file. Your file is the one that has my phone not working. Your RUU WON'T flash, and as I stated the file I posted is not a RUU of any kind, I don't know why you insist on me flashing it.
Click to expand...
Click to collapse
So you posted it and didn't even test it. You just assumed it would work for people?
Also, its not my file. It was put out there by a developer out in the world. I also used this to test on my device before uploading. I have no idea what you do/did with your device so I can't just try to recreate the issue your facing. I told you how I used it on mine and I was able to get it to work.
With any file you should be fully prepared and knowledgeable in what your using in the case an issue arrives. If CM bricked your device, you would be mad at the developer or yourself?
Your telling me its my files fault, yet your taking no responsibility for your actions. If you ran into an issue and me as the uploader stating explicitly that I have tested it and the methods I have used to get it to work what would you like me to do? I gave you the original source of the files so you could compare them to your leisure but its the exact same file.
The things your saying don't line up at all in short. I apologize if there was an issue with yours but mine works just as fine as day one after flashing the RUU. This RUU DOES flash just not in incapable hands it seems. Hopefully HTC will release an easier one to flash for anyone with difficulties.
Have you downloaded from the source as of yet?
Sent from my 710C using XDA Free mobile app
jaysoblitzed said:
So you posted it and didn't even test it. You just assumed it would work for people?
Also, its not my file. It was put out there by some developer out in the world. Which I also used to test on my device before uploading. I have no idea what you do/did with your device so I can't just try to recreate the issue your facing. I told you how I used it on mine and I was able to get it to work.
With any file you should be fully prepared and knowledgeable in what your using in the case an issue arrives. If CM bricked your device, you would be mad at the developer or yourself?
Your telling me its my files fault, yet your taking no responsibility for your actions. If you ran into an issue and me as the uploader stating explicitly that I have tested it and the methods I have used to get it to work what would you like me to do? I gave you the original source of the files so you could compare them to your leisure but its the exact same file.
The things your saying don't line up at all in short. I apologize if there was an issue with yours but mine works just as fine as day one after flashing the RUU.
This RUU DOES flash. Just not in incapable hands it seems. Hopefully HTC will release an easier one to flash for those with difficulties.
Have you downloaded from the source as of yet?
Sent from my 710C using XDA Free mobile app
Click to expand...
Click to collapse
I wasn't calling you out because I thought it was your fault. You said I had uploaded a file without testing, when in reality your file is the only one to harm somones device, (wether it be your fault for uploading it or mine for flashing it) ,when my file couldn't hurt anyone. That's like saying if I claim a .jpg file is a Lollipop ROM it will brick people's phone.
I think my issue is deeper, my /data partition is clearly corrupted, as I can't format in recovery or through fastboot commands.
FoxyDrew said:
I wasn't calling you out because I thought it was your fault. You said I had uploaded a file without testing, when in reality your file is the only one to harm somones device, (wether it be your fault for uploading it or mine for flashing it) ,when my file couldn't hurt anyone. That's like saying if I claim a .jpg file is a Lollipop ROM it will brick people's phone.
I think my issue is deeper, my /data partition is clearly corrupted, as I can't format in recovery or through fastboot commands.
Click to expand...
Click to collapse
[Edited] So in short do you believe I uploaded something that could potentially harm a device when the device has specific security measures that will not allow certain actions to be taken?
[Deleted]
[Edited] Also, that's like saying I made the RUU myself. A great accomplish that would be only; If its supposed to be signed code ONLY FROM HTC that's accepted by the bootloader. If you try to put an UK RUU on your phone and its US it won't flash because of these signed codes and bootloader security measures.
[Deleted]
Sent from my 710C using XDA Free mobile app
jaysoblitzed said:
So in short your trying to make people believe I uploaded something that could potentially harm their device when the device has specific security measures that will not allow certain actions to be taken?
Also, your the only one with a complaint, and funny enough your the only one who has had an issue with me since I posted in CM a while back directing a comment to the developer and someone who was having an issue.
Also, that's like saying I made the RUU myself. A great accomplish that would be only; If its supposed to be signed code ONLY FROM HTC that's accepted by the bootloader how would I make an RUU or a "bad file"?
Tell me this. If you try to put an UK RUU on your phone and its US it won't flash. Do you know why? Do you know why this RUU works on this device and it won't work on any other device?
I suggest you keep your comments to yourself as I know you were hoping someone else would've posted this but never expected me to come across it first.
The things you've said thus far are enough to commit you to fraudulent claims so stop before you hurt yourself.
Its a link with a file bro.
Jealously is not in my persona.
& don't skip past half the stuff I said and comment on the points that made you "mad" because that is annoying.
Sent from my 710C using XDA Free mobile app
Click to expand...
Click to collapse
This has nothing to do with any past issues between us get over yourself. My phone currently is 100% not working I could care less what you have to say I have not commited any fraudulent claims thus far but I'd love for you to try to prove I did somehow. I'd be perfectly fine with posting pictures/a video to show I am seriously having an issue with my device and your RUU is of no help. I skip things that you say that are childish and have no relation to the problem at hand.
As title says, all attempts to flash a custom ROM result in error 7, I have checked that my version of TWRP is up to date and the ROM is for TRLTEXX. I have also tried removing the 'assert' section in `updater-script`, which caused another error where the `update-binary` file cannot be found. Can anyone help me figure out why this is happening and how to fix it?
MinkShenanigans said:
As title says, all attempts to flash a custom ROM result in error 7, I have checked that my version of TWRP is up to date and the ROM is for TRLTEXX. I have also tried removing the 'assert' section in `updater-script`, which caused another error where the `update-binary` file cannot be found. Can anyone help me figure out why this is happening and how to fix it?
Click to expand...
Click to collapse
First, if you just bought this phone, what I would do is double check the phone is really 910f. What's it say behind battery? Also boot into download mode, what info does that tell you. When you plug into Odin what model does it say. Reason I say this, I've seen others buy what they thought were F but they were really 910p.
If all the info checks out, I would download twrp again just to make sure you got good file. Downloads can mess up rarely.
Let me know what this tells you.
Had the phone for about a year and a half now, battery cover, behind battery, about page, and download mode all say N910F, the same as the version of TWRP is supposedly for, I have flashed both 3.0.1.0 and 3.0.2.0 of TWRP using Odin with the same result, error 7 on all attempts of installing a ROM. The ROM I'm trying to install is the Resurrection Remix ROM for 6.0.1 TRLTEXX, but others have the same error.
MinkShenanigans said:
As title says, all attempts to flash a custom ROM result in error 7, I have checked that my version of TWRP is up to date and the ROM is for TRLTEXX. I have also tried removing the 'assert' section in `updater-script`, which caused another error where the `update-binary` file cannot be found. Can anyone help me figure out why this is happening and how to fix it?
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/note-4/general/efs-fix-invalid-argument-twrp-fix-t3489294
Trex888 said:
Try this
http://forum.xda-developers.com/note-4/general/efs-fix-invalid-argument-twrp-fix-t3489294
Click to expand...
Click to collapse
I'd rather not experiment considering it still boots into touchwiz fine.
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.
Good morning everyone,
I was finally able to get out of my previous situation (bricked phone) thanks to your help, i can now fully load my phone (Samsung Galaxy A5 SM-A500FU).
I wanted to go back to modding right again cause i really dislike the samsung software (i actually have stock 6.0.1 firmware).
I flashed TWRP 3.0.2 with odin, and then tried to flash Cyanogenmod 13 taken from the proper thread. Tried to flash it, got error 7. I try to get information on that error and discovered it should be about rom version not right for my model. I was already sure i was trying to flash the correct rom, but i downloaded it again to be 100% sure. same error. Followed a guide who told me to edit some script file and remove some text lines, did it. Still error 7. Tried to flash with that "signature option" unselected. Still error 7.
Also tried to flash Cyanogenmod 12. something for my device, still error 7.
Do you have any clue on how to get out from this situation? maybe trying a different recovery?
I never had this kind of error, and i flashed dozens of time on multiple devices
Thank you in advance as always for your patience
Dharmost said:
Good morning everyone,
I was finally able to get out of my previous situation (bricked phone) thanks to your help, i can now fully load my phone (Samsung Galaxy A5 SM-A500FU).
I wanted to go back to modding right again cause i really dislike the samsung software (i actually have stock 6.0.1 firmware).
I flashed TWRP 3.0.2 with odin, and then tried to flash Cyanogenmod 13 taken from the proper thread. Tried to flash it, got error 7. I try to get information on that error and discovered it should be about rom version not right for my model. I was already sure i was trying to flash the correct rom, but i downloaded it again to be 100% sure. same error. Followed a guide who told me to edit some script file and remove some text lines, did it. Still error 7. Tried to flash with that "signature option" unselected. Still error 7.
Also tried to flash Cyanogenmod 12. something for my device, still error 7.
Do you have any clue on how to get out from this situation? maybe trying a different recovery?
I never had this kind of error, and i flashed dozens of time on multiple devices
Thank you in advance as always for your patience
Click to expand...
Click to collapse
When u get the error, go to ADVANCED and "Copy log" to sdcard, upload here and maybe we can help :good:
TheAbraham696 said:
When u get the error, go to ADVANCED and "Copy log" to sdcard, upload here and maybe we can help :good:
Click to expand...
Click to collapse
Here you go, sir
Dharmost said:
Here you go, sir
Click to expand...
Click to collapse
If i'm right error it's caused by broked signature in zip cuz u edited for skip devicename assert. So u need to sign again the zip or delete all files in "rom.zip/META-INF", only files! No the "com" folder.
And r u doing a factory reset before install?
Enviado desde mi SM-J710F mediante Tapatalk
TheAbraham696 said:
If i'm right error it's caused by broked signature in zip cuz u edited for skip devicename assert. So u need to sign again the zip or delete all files in "rom.zip/META-INF", only files! No the "com" folder.
And r u doing a factory reset before install?
Enviado desde mi SM-J710F mediante Tapatalk
Click to expand...
Click to collapse
I'm sorry sir, i'm not sure i fully understood your message :
The attached lo was a result of flashing the regular custom rom (not the edited one), don't remember if i had the signature option ticked or not. What are You suggesting me To do? On this try i didn't resect factory (no dalvik or cache ) But i di reset those 3 in previous tries And always got error 7
Dharmost said:
I'm sorry sir, i'm not sure i fully understood your message :
The attached lo was a result of flashing the regular custom rom (not the edited one), don't remember if i had the signature option ticked or not. What are You suggesting me To do? On this try i didn't resect factory (no dalvik or cache ) But i di reset those 3 in previous tries And always got error 7
Click to expand...
Click to collapse
You need to put in phone/sdcard the rom without any edition, do a factory reset, then flash
TheAbraham696 said:
You need to put in phone/sdcard the rom without any edition, do a factory reset, then flash
Click to expand...
Click to collapse
This is what i did the first time i tried to flash, didn't worked. I tried again, and incredibly the thing worked itself out. I have no idea what happened honestly, but now i'm back on track!
Thank you so much for assistence
[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.