Related
Hello. First of all: I've tried for 6 hours to figure this one out, this is my last resort, and I hope you can help me.
I've got a major problem. What happened is that I was gonna flash CM 10.1. I wiped cache and all that, flashed the CM.zip, and it failed half way. This resulted in me getting stuck where I am now.
I've found numerous guides, but the problem is, when I download the files, I dont get a .tar or md5.tar(?) file, I only get the folders, like system etc. Ive tried every link Ive found, and the same happens. No file capable of being selected in Odin.
Could any of you, please direct me to where I can download the files needed to flash via Odin? I'm really desperate and tired.
Thibble said:
Hello. First of all: I've tried for 6 hours to figure this one out, this is my last resort, and I hope you can help me.
I've got a major problem. What happened is that I was gonna flash CM 10.1. I wiped cache and all that, flashed the CM.zip, and it failed half way. This resulted in me getting stuck where I am now.
I've found numerous guides, but the problem is, when I download the files, I dont get a .tar or md5.tar(?) file, I only get the folders, like system etc. Ive tried every link Ive found, and the same happens. No file capable of being selected in Odin.
Could any of you, please direct me to where I can download the files needed to flash via Odin? I'm really desperate and tired.
Click to expand...
Click to collapse
http://samsung-updates.com/
Use the link to download a firmware for ur variant
http://www.youtube.com/watch?v=91Z14voZ4Ms
U can try the above link to make a .tar should be possibe
else use my signature link for Q&A there many of my friends will help u
Thibble said:
Hello. First of all: I've tried for 6 hours to figure this one out, this is my last resort, and I hope you can help me.
I've got a major problem. What happened is that I was gonna flash CM 10.1. I wiped cache and all that, flashed the CM.zip, and it failed half way. This resulted in me getting stuck where I am now.
I've found numerous guides, but the problem is, when I download the files, I dont get a .tar or md5.tar(?) file, I only get the folders, like system etc. Ive tried every link Ive found, and the same happens. No file capable of being selected in Odin.
Could any of you, please direct me to where I can download the files needed to flash via Odin? I'm really desperate and tired.
Click to expand...
Click to collapse
That Could be a problem with Your computer then.. When U start downloading the Firmware File what is the name that it shows while it is getting downloaded. It coudl be that there is some Software In your system that automatically extracts the file once downloaded
download a stock firmware from the development forum and try a different computer with odin
I figured out what was wrong. Winrar automatically extracted all directories. Unfortunatly, I flashed again, but rendered the device unbootable. I have no idea what happened. Will get a new one on my insurance.
Thanks for your help guys. Much appreciated.
So I was trying to flash the latest system images off the Google website and I got this "Too Many Links" error when writing the system. I can't go back because it already erased the system files and i've tried using 3 different USB's to try to get it to flash to no avail. Can anyone help? haha first day with it and already broke it
http://imgur.com/jFJCL2U
Thanks
Kevin
EDIT: Just tried my desktop also, still same error
EDIT 2: Bam! Got it to work! Just had to update my android-sdk and all was good
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.
Anyone else having this issue? I tried a factory reset on my S8+. I got stuck in the Recovery screen with a dm-verity error. I downloaded the firmware, installed it through Odin3.12.7, rebooted, then got a DRK error. I'm not sure how to get past or fix that? Any experience out there with that?
gm0ney1 said:
Anyone else having this issue? I tried a factory reset on my S8+. I got stuck in the Recovery screen with a dm-verity error. I downloaded the firmware, installed it through Odin3.12.7, rebooted, then got a DRK error. I'm not sure how to get past or fix that? Any experience out there with that?
Click to expand...
Click to collapse
Drk error is usually a very bad sign. After an Odin flash? Sounds like you accidenty clicked efs clear.. j hope I'm wrong avout Tha and if not then pray you have a backup a to restore via Odin. If not it's not looking good.
gm0ney1 said:
Anyone else having this issue? I tried a factory reset on my S8+. I got stuck in the Recovery screen with a dm-verity error. I downloaded the firmware, installed it through Odin3.12.7, rebooted, then got a DRK error. I'm not sure how to get past or fix that? Any experience out there with that?
Click to expand...
Click to collapse
Give this thread a read
https://forum.xda-developers.com/galaxy-s8/how-to/how-to-fix-imei-drk-issues-t3622559
yep this is why you should always back up your efs partition as soon as you are done rooting. without a backup repairing this is going to be very hard.
partcyborg said:
Drk error is usually a very bad sign. After an Odin flash? Sounds like you accidenty clicked efs clear.. j hope I'm wrong avout Tha and if not then pray you have a backup a to restore via Odin. If not it's not looking good.
Click to expand...
Click to collapse
Thanks for the reply. I really don't know what happened. Woke up the other day and it wouldn't send texts. It would receive them, but not send. When I took it to Verizon, they suggested a factory restore, so I started that and that's when the errors began.
What do you mean by having a backup to restore?
moocman42 said:
Give this thread a read
https://forum.xda-developers.com/galaxy-s8/how-to/how-to-fix-imei-drk-issues-t3622559
Click to expand...
Click to collapse
Thank you. I did see that but not much for the S8. The form link he has just errors....similar to my phone haha
djisgod said:
yep this is why you should always back up your efs partition as soon as you are done rooting. without a backup repairing this is going to be very hard.
Click to expand...
Click to collapse
I'm not sure how to do that, but too late now anyways I guess. lol.
So is there even a way to repair this?
gm0ney1 said:
I'm not sure how to do that, but too late now anyways I guess. lol.
So is there even a way to repair this?
Click to expand...
Click to collapse
To be honest I don't know for sure but I don't have a good feeling.b efs contains your IMEI and all other per-phone information necessary to get a device on the network. If it's erased then all that info is gone so if you didn't back it up it's for good.
There are places (some less than reputable, others surely very reputable) that supposedly can repair these in certain cases, but I know nothing more.
Also fyi: if your initial thought is to clone someone else's efs, know that that is quite illegal in just about every country as it amounts to IMEI spoofing
partcyborg said:
To be honest I don't know for sure but I don't have a good feeling.b efs contains your IMEI and all other per-phone information necessary to get a device on the network. If it's erased then all that info is gone so if you didn't back it up it's for good.
There are places (some less than reputable, others surely very reputable) that supposedly can repair these in certain cases, but I know nothing more.
Also fyi: if your initial thought is to clone someone else's efs, know that that is quite illegal in just about every country as it amounts to IMEI spoofing
Click to expand...
Click to collapse
Alright....that's what I was worried about. Thank you for the information. Much appreciated
contact the author of this thread https://forum.xda-developers.com/galaxy-s8/how-to/how-to-fix-imei-drk-issues-t3622559 he has been helping people to try and recover from your situation. his thread is for the s7 but he has been helping s8 guys as well.
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?