My Tab has been collecting dust for most of the year, so I figured I'd dust it off and update it to a shiny 4.3 rom. I wiped everything (no nandroid, stupid I know) and tried to flash, but I got a "status 7" error. It wasn't tied to the device, but to symlinks (I did try to remove the assert lines in the updater script first, just to make sure). According to some of the error lines in TWRP, it was the permissions (set_perm some changes failed). This result was the same from CWM, to TWRP, and finally to Philz recoveries.
I just couldn't flash anything. I tried a few 4.3 roms, and then assumed that perhaps something changed with 4.3 firmware-wise that I didn't have, tried something 4.2 like what was on before. Nothing. Same status 7 errors. I've been doing some research and can't find anything that will work for me. I've noticed, however, that I can't unmount the data partition. I'm wondering if this is my problem, and I can't find the solution for this either. Help the noob?
EDIT: I managed to flash a stock ICS image via Odin, then attempted to install TWRP and try again. Same errors. Not sure what could be going on.
Anybody? I'm not sure how often the second page gets glanced at around here. Even an inkling of an idea might put things in motion.
I believe Status 7 usually indicates the wrong update file.
You might try...
androidforums.com/nexus-s/588179-jelly-bean-update-status-7-error.html
highonandroid.com/android-roms/how-to-fix-status-7-error-with-cwm-recovery-on-rooted-android
ibtimes.co.uk/articles/499093/20130814/galaxytab2-p3100-p3110-p3113-android43-jellybean-cyanogenmod102. htm
Best of luck.
Bennyboy371 said:
My Tab has been collecting dust for most of the year, so I figured I'd dust it off and update it to a shiny 4.3 rom. I wiped everything (no nandroid, stupid I know) and tried to flash, but I got a "status 7" error. It wasn't tied to the device, but to symlinks (I did try to remove the assert lines in the updater script first, just to make sure). According to some of the error lines in TWRP, it was the permissions (set_perm some changes failed). This result was the same from CWM, to TWRP, and finally to Philz recoveries.
I just couldn't flash anything. I tried a few 4.3 roms, and then assumed that perhaps something changed with 4.3 firmware-wise that I didn't have, tried something 4.2 like what was on before. Nothing. Same status 7 errors. I've been doing some research and can't find anything that will work for me. I've noticed, however, that I can't unmount the data partition. I'm wondering if this is my problem, and I can't find the solution for this either. Help the noob?
EDIT: I managed to flash a stock ICS image via Odin, then attempted to install TWRP and try again. Same errors. Not sure what could be going on.
Click to expand...
Click to collapse
True, this is usually the case, but not this time. I tried all these, but the root of this issue is with the symbolic links and setting permissions. I am starting to really think it's all about getting data to unmount, but I haven't been able to get this to happen.
back to the stock rom
---------- Post added at 04:20 PM ---------- Previous post was at 04:17 PM ----------
[/COLOR]
Bennyboy371 said:
My Tab has been collecting dust for most of the year, so I figured I'd dust it off and update it to a shiny 4.3 rom. I wiped everything (no nandroid, stupid I know) and tried to flash, but I got a "status 7" error. It wasn't tied to the device, but to symlinks (I did try to remove the assert lines in the updater script first, just to make sure). According to some of the error lines in TWRP, it was the permissions (set_perm some changes failed). This result was the same from CWM, to TWRP, and finally to Philz recoveries.
I just couldn't flash anything. I tried a few 4.3 roms, and then assumed that perhaps something changed with 4.3 firmware-wise that I didn't have, tried something 4.2 like what was on before. Nothing. Same status 7 errors. I've been doing some research and can't find anything that will work for me. I've noticed, however, that I can't unmount the data partition. I'm wondering if this is my problem, and I can't find the solution for this either. Help the noob?
EDIT: I managed to flash a stock ICS image via Odin, then attempted to install TWRP and try again. Same errors. Not sure what could be going on.
Click to expand...
Click to collapse
try to get back to the stock rom firmware, I have the same
problem few days ago, cant flash any rom
n I think the problem b'cause wrog flash when rooting or
flashing the image cwm/bootloader
that's all I know,
Well it's good to know that I'm not the only person who has had this problem. I managed to get back to stock. I'm not sure what I can do from here, though. I don't want to try anything because I don't want to break it.
Related
Alright, so here goes. I've searched the thread for the issue I'm having, but have come up empty handed. I'm not Droid noob, especially not when it comes to flashing roms. But, here are the details I have.
I had been following dragonzkiller's development on his ICS rom. I hadn't really put forth any effort looking lately until yesterday, and saw that he had the wifi and camera fixed, which were really my two biggest issues, so when I saw that, I was excited. I began working on getting it all running. I've had the x2 for about 5 months or so, and usually, the first thing I do, as soon as I get a new phone, is root it. Back in April, I rooted with GingerBreak. Worked good, no issues there. Back in June, apparently I still received the OTA update taking it to 2.3.5-418, which I found out last night had kinda broken my root. So, I went back to find a way to re-root. I did that, with a desktop .exe that went in, and was supposed to flash BSR to my phone also. After I ran that, all my root permissions started asking for options again, so I was relieved. Now, for the issues I'm having.
I downloaded an app in the play store called Online Nandroid Backup. For some reason, and I think this may be a dev issue with the app, it won't run a backup, and tells me that it wasn't able to be granted superuser permissions, even though it is prompting and I'm allowing. Issue number two is this. I've tried 3 different ways to get this working. I used ROM Toolbox Lite, selected the rom I wanted to flash, and wipe data and cache, no delvik. I've selected to run a backup of my current rom. When it boots into recovery, I only have 4 options. Reboot your phone, something about installing the rom from sdcard, wipe data, and wipe cache. I'm not given the backup option on the recovery. Furthermore, when I kinda just decided that since I hadn't had any trouble flashing a rom to any of my other phones I've had, I would just try to flash the rom, it gives me a prompt about 25% through the rom package saying E: signature could not be verified, or something to that extent.
Even though it has said not to use Rom Manager, I did download that and try that, and got pretty much the same outcome of no rom, just a bit different scenario going through. Rom Manager won't reboot into recovery, and when I select to do a backup, it reboots the phone straight up. I also used the manual entrance into recovery, volume up, but it tells me something about starting RSD protocol, and sticks at that forever.
My real questions are this... I've always ever used CWM. All of my previous phones have been supported by Rom Manager nicely, so when it came to downloading and flashing a rom on them, no problems at all. I have never used BSR, to my knowledge, so I'm not sure if the recovery screen I'm seeing is the actual BSR recovery, or if it's some other recovery. If it's not BSR, do I just flash it like I would a rom, then re-run into that? And does the signature issue that I'm running into mean that I have to wait for a signed version of the rom in order to work it? Is there any way to fix this issue, or am I basically SOL right this moment? Any information on how I can fix all of this would be greatly appreciated. Thank you.
Just a quick heads up to everyone, I was able to fix my issue by SWITCHING TO A NEW SDCARD, I had been using a 64GB SDCARD and I switched to a 2GB SDCARD and I guess that my recovery or my phone couldn't handle such a large card.
It took me about two days to come to this conclusion but after lots of ODIN and reflashing just about everything possible I've decided this was the issue. Also I ran up my flash count a hell of a lot. I hope this helps someone out who may have issues like mine!
Hey all,
Today I decided I would try out a new ROM on my SGS3 so I decided to install the MIUIv5 ROM here: http://forum.xda-developers.com/showthread.php?t=2232800
Normally ROM installations go quite smooth for me so I opened up TWRP v2.5.0.0 and I did as I usually do by making a backup and wiping my system and then going to install my ROM. Instead today I got tons of errors saying:
Code:
Finding update package...
Opening update package...
E: Can't open /external_sd/MIUI5_d2vzw_3.4.12.420-signed (1).zip
(bad)
Installation aborted
So, I downloaded the ROM again, but this time from the mirror just in case I had a bad .zip or it didn't transfer to my SDCARD correctly, but then I started getting more and more errors.
Instead of getting a bad zip error I got the following:
Code:
E:Mount: Unable to find partition for path '/'
I guess this means it can't find my root partition?
Now all of a sudden I can't find my backups and I am just stuck without a ROM and I only have a recovery... quite inconvenient, also I can't flash any ROMS as I tried flashing some others but they didn't work at all no matter what I did and I am just running in circles... any help is GREAT APPRECIATED as I would love to have a functional phone by tomorrow.
I am fairly fluent with android and linux systems as well as computers in general so I should be able to provide any helpers with almost all information needed relative to my device, but sadly this whole issue has really stumped me.
Thanks so much!
ljbaumer
Click to expand...
Click to collapse
Have you tried flashing with Odin?
I know a lot of people swear by twrp but for me I always seemed to have issues. I had a similar issue you are having when I finally flashed cwm again. I was able to fix my issue by odin.
Sent from my GT-P5113 using xda premium
Thanks for both of your replies, I decided just to revert back to stock and I am in the process of re-obtaining root and such and then I am going to try to flash again just using recovery... by flashing by odin do you mean flashing a ROM or flashing back to stock?
FIXED! Read OP
I am stuck. My phone won't accept any ROMs I try to install. It keeps giving me the "Status 7" Error and I can't figure out why!
the backup recovery failed.
I am using TWRP as my recovery, but it is an old version (V2.2.1.1). I have tried multiple releases for CM, but none of them work, not even the stable ones.
The phone has already been wiped so i cant get back into stock android to fix much.
I have tried going into the "updater-script" file and deleting the code for checking the device matches the rom, but no luck. i have also tried installing a rom that wasn't cyanogenmod but i ran into the same problems.
CAN ANYONE HELP ME?!?!?
I really dont want to have to throw away a good phone because i missed something.
For the last year or so, I was using this rom, and I loved it, but I was curious to try the new KitKat version so I tried updating, and kept getting getting a recursive error when trying to flash the d2lte(supposedly all the S3 roms are unified now?) KitKat version. So after doing this, after /system was cleared, but I couldn't flash back to the backup I had made before hand because I was getting an md5 mismatch.
In response, I used Odin to flash Root66. Phone works, but its seriously lacking in terms of bells and whistles of a custom ROM. It says its rooted, but a lot of root apps would fail the permission test. No prompt was given. I used towelroot and started getting root access, but I still can't update CWM or Superuser binaries. Trying to flash any other ROM leads me to an infinite boot screen, forcing me to flash Root66 again.
I tried this as well, but it seemed to yield the same results.
So, I really would like get off Root66, but I'm at a loss as to how. Anyone have any ideas? I'm sure the answer is staring me in the face in one of those threads I linked, but I'd really appreciate it if someone could (at least try to) point me in the right direction. Apologizing in advance if this question has been asked before.
Thanks.
Some say "Bricking" is when the phone doesn't turn on at all, or does and displays and does nothing; some say there are different states of bricking. In any case... I'm only an intermediate, and I did not have any booting problems before this. So, with the least-common denominator in mind, please read on.
I have a Samsung Galaxy S3, SGH-i747 ATT. It was out of warranty anyway and I've flashed custom ROMs on it many times before without issue. I dropped it about a week ago and the LCD broke. Upon having it fixed, I noticed it no longer booted properly. I am able to get into ODIN's download mode, and I am able to flash stock recovery, but neither have proven helpful.
I was originally running Slimkat 4.4, but decided to flash back to the stock Android ROM since it would no longer boot properly anyway. This is where it gets strange.
First I attempted to flash CWM and TWRP as my recoveries. ODIN said both were successful in flashing on their respective attempts, but each one was simply a black screen after the Samsung logo disappeared. The blue text in the top-left letting me know it was booting into recovery was present with the logo, but after it disappeared, nothing.
So I tried to install stock recovery, and to my surprise, it worked, though it's really not useful for anything. Chainfire's CF-autoroot was also flashable and functional, but when I tried using adb to push files to the device, I would get several errors:
From the ADB command line, when trying to push something, I'd get "Error: closed".
From the recovery's log, sometimes when I'd successfully send a ROM to be installed, I'd get various notifications, such as: "Failed to verify whole-file signature" and "Incorrect footer", "Installation aborted".
When I attempt to flash any ROMs via ODIN, I get a few different errors, including (Not verbatim, these are from memory):
REV CHECK FAIL
DEV UNSUPPORTED
FUSED 2 > BINARY 0 [This one is especially confusing to me]
SECURE CHECK FAIL
and one from the ODIN side that said something along the lines of "HLOS-BIN" or something when it failed to flash.
So I can turn the device on, get to download mode, and even flash the stock ROM and CF-autoroot... but after 20 hours of reading other people's similar problems and varying degrees of success in their solving them, I'm stumped. I hope someone here might be able to share their superior knowledge vis-a-vis Android!
-Krust
Update
I've tried many things.
Right now I'm trying to re-flash Slimkat 4.4 (Which I was already using), and I know anything JB 4.3 or above will restrict the bootloader from downgrading, so maybe that was the problem. But if this doesn't work... I'm not sure what to do. Will post error updates if any.
-Krust
Same Status
I still get REV CHECK FAIL Fused 2 > Binary 0 error.
I believe this is from attempting to flash to a version lower than what I had (4.4).
I am unable to find stock firmware for the ATT SGH-i747 for 4.4 or above.
Please help! This is my only phone, and I know it can be restored because I can still get into download mode, but something's blocking ODIN from performing the flash, even on packages that seem to be the correct version.
Update
From what I have been able to find, I will need to update to an Android variant 4.4.2 or above due to the restricted bootloader.
My only problem... I haven't been able to FIND any stock ROMs for 4.4.2.
Everything I try returns a variety of errors, the most common being FUSED 2 > BINARY 0 (Which I now understand means I am attempting to downgrade) because I have not been able to find anything like Slimkat 4.4.2 that is in .tar format to flash.
I am very stuck and confused, and this is my only phone. Lesson learned: Keep up with the nuances of updates. But for now, I really need to get this fixed. Does anyone have experience with this particular problem?
Update
I was able to flash a modded TWRP recovery and was able to boot into it.
However, when I try to install ROMs via zip, I get the error E: Cannot execute binary update file.
One ROM, a Slimkat for i747M (Which isn't even my phone), appeared to flash successfully, but wouldn't boot.
GApps for Slimkat 4.4.4 was also able to flash successfully on its own, but the corresponding Slimkat could not.
I am quite stuck. Please help.
Hi,
Try posting your question here:
AT&T Galaxy S III Q&A, Help & Troubleshooting
The experts there may be able to help.
Good luck!