Hi,
I am trying to install any custom rom however no matter which one I try I get an error ranging from either status 0 or status 7.
These are roms files that worked previously but no seem to give that message.
so far my S4 has no rom and it and will not boot into recovery.
I have looked into the status 7 error and it turns out that some text needed to be deleted from a file within the rom, upon closer inspection this text has already been deleted by who ever cooked the rom.
can anyone help me please as I have been spending the last 3 hours on this..
Thanks
Wrong section buddy!
Reported for moving
Please read the rules Scott....
Sent from my GT-I9505 using xda premium
Related
I am trying to upgrade or just simply change roms. I have tried and downloaded lokis and I have tried that method at least 10 times..I also tried farias method to a tee and no hope...I also went to the wiki and did that method. I get the three bars of death and an error message on the screen. I have never had problems with this I have unlockd the c and u method and I have also hard reset before and I have turned the power button off after the enablRapi...can someine please help I have read tried so many times and I am not dumb or rude I just need help
I know I am whining
I Just need some help from I fresh 8125 I have had no luck updating th rom
First the "three bars of death" is the bootloader. That is required mode for ROM Flashing.
Second, what error message do you get? Have you searched the forum for that error message?
Details, boy, the devil is in the details...
Thank You
I know its the bootloader...I am usually the one people rely on for this information...The error message is standard because when I go for the readme the .doc cant be found. I go through the process but the expected time elapsed never shows up and then I have to recovery...also I have search for various errors here and I have no luck...thank you again
error[260]
i tried it again for you and this is the error thank you
Re: error[260]
Bnetts said:
i tried it again for you and this is the error thank you
Click to expand...
Click to collapse
Two issues attributed to this "260" update Error:
First try a different cable. One user resolved their problem that way.
Others report that unsuccessful CID unlock has caused this error.
What Rom is currently on your phone?
Thank You
You are appreciated I switched position right after the last quote but you would have saved me with that post...Thank you for coming forward and know that I think you're cool :wink:
Hi,
I wanted to try the Roto JME firmware, and I flashed it using the instructions at the dev forum. It seemed to work nice. Now I want to get back to stock firmware, and I am having a lot of trouble doing it.
I tried downloading the stock ROM at the sticky thread in the dev forum and decrypt it. It is not possible for me, I have tried four different computers with both Win XP and Win 7. All I get is "System.Runtime.InteropServices.COMException (0x80040154)".
Anyhow, I downloaded the file already decrypted at the first post in this thread: http://forum.xda-developers.com/showthread.php?t=881952&highlight=Official+ROMs.
I extracted the zip-file and in Odin v.1.70, I selected PDA = JME.tar which I got from the zip-file. I did not select re-partition. Odin says PASS! but the galaxy tab goes to a screen with a triangle with a exclamation mark in it, and it says "E:Can't mount /dev/block/stl10
(invalid argument)
E:copy_dbdata_media:Can't mount DBDATA:
your storage is not prepared yet, please use UI menu for format and reboot actions.
copy default media content failed. "
I tried the reboot option. The screen says "SAMSUNG" and nothing happens. I don't dare try the other options.
Please help, I don't know what to do!
Sounds like the internal sd is corrupted. Try a factory reset in recovery
Sent from my GT-P1000 using XDA App
That did not work. It still just shows the Samsung logo, it waits some time and then it vibrates, and it seems it does some kind of new boot atempt.
Please help!
No one can help me?
Please.
I think you need to get a copy of dbdata.rfs.tar and flash it using odin.
You can find a link to download it in the second post in this thred.
http://forum.xda-developers.com/showthread.php?t=875557
Thanks man, it worked!
Still not back to stock FW though. I wonder why no-one has written a howto on that.
No problem
I have been using jk5 firmware which allowed my at&t tab to make calls. However, I noticed after a while, that 90% of my use of the tab was wifi and certain apps would not download because the vendor thought my app was from a different country. None the less, I thought it was best for me to just return to the stock firmware. i called Samsung, told them I wanted stock firmware back on my tab, they gave me a prepaid ups label and I just shipped it off today for a 7 day turnaround.
What?! So you're saying there is no known procedure for getting back to stock, without calling samsung? This is ridiculous... So I have a tab wich is more or less ruined in regards to future official updates, i.e. Honeycomb and such?
I feel sad and fooled..
If you know what the original firmare was, you can download it at samfirmware.com
I think the rom you downloaded has the protected bootloader :-(
Doesn't restoring your rotobackup get back to stock?
Just have have to remove the root , unlock and any other changes after restore?
Can't you point me to a description on how to do that? I would be very grateful.
If you have a signed bootloader you cant go back to stock until the new fix is ready. Read all about it here
http://forum.xda-developers.com/showthread.php?t=888071
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.
im wondering if anyone can shed some light on this problem. it boots onto the normal samasung galaxt NOTE3 sm-n9005 screen but in the top left it says set warranty bit : recovery. when i hold home power and vlume up it comes up with recovery booting and then that message after. ive re installed stock rom onto this and it was all sucessfull but still hasnt fixed the issue. any help will be appriciated!
Also to add upon battery removal ond switch on i get set warranty bit kernel
Yes search its well posted set w bit kernel.Even a whole thread on it .
Sent from my SM-N930F using XDA-Developers Legacy app
And what exactly is the issue ? And next time use search. The phone is not from yesterday !
Remove the battery, attempt to boot into download mode, select cancel, boot into android and flash a different recovery
Thanks for the replies. The issue came after a update it's an old phone but just messing about trying to sort it. I've re installed a rom and still comes up with the same issue tried 5 different rooms and 4 of them failed is there any way to find out all the model info so I can get the right one? Plus spam mobile won't let me get the stock 4 rom because you have to be a premium member?
try updato.com
same problem
i got the same problem
maged251 said:
i got the same problem
Click to expand...
Click to collapse
Answered already search and read .
help asap...
Updater process ended with ERROR: 7
when flashing this build
what should I do ??
Hmmm.... don't you think that you should have mentioned the file you were trying to flash and your TWRP version?
I too get error 7 many times and some devs have advised that it should be ignored (in most cases, NOT necessary for your one).
stark1296 said:
Hmmm.... don't you think that you should have mentioned the file you were trying to flash and your TWRP version?
I too get error 7 many times and some devs have advised that it should be ignored (in most cases, NOT necessary for your one).
Click to expand...
Click to collapse
my mistake,
happened that I downloaded Pixel Experience ROM zip, but somehow the file was corrupted in my PC ( I realized when tried to unzip it)
that caused error 7 while flashing
I just re-downloaded it, and all flashed fine ...
thnx !
Glad you got it working.
From what I have read over the years on XDA, error 7 is always a bad download, regardless of the ROM you are downloading, it's the download itself so just redo it and you should be good to go.