Related
I am a new member to XDA, though I have been to this site countless times before, and finally thought it was about time to join. I am not a noob to rooting or flashing or any of that-though I am still learning.
I have come across a problem and need help. I have a T-Mobile SGS III SGH-T999 and was running 4.1.2 Axis M rom, but I decided try something else. I've been searching for a good debloated stock touchwiz rom with the latest update, but until I find one I wanted to try something I found called JellyBam. Right now I'm back to 4.1.1 stock-I made a rooky mistake and had to reroot, just fyi.
I downloaded the latest JellyBam from get.jellybam.com and flashed it but all I got was, "status (7) error, Installation Aborted". I found out that "status (7)" happens when the phone checks to make sure the rom is compatible and the way to fix it is delete the line of coding above "show progress" in the "updater-script" file that causes the phone to check for compatibility and rezip the package and flash it. When I flash it now, it doesn't check for it to be compatible, which is good, so it goes straight to install. This time I don't get the "status (7) error" but it still aborts installation and I can't find out what's wrong.
I stopped trying to figure out how to get it to work. I just couldn't figure out what's wrong, I kept getting "status 7" and then "status 6"-and I have no clue what that one is-so I went with a rom my father used and I love it. I went with the inFAMOUS rom.
I would still appreciate some help with that whole "status 6/7" problem if anyone knows. Also, if anyone knows of a good debloated touchwiz rom that has the latest 4.2.2 or 4.2.1 tell me cause I've been searching for one and can't find one I like. I would like one that gets the latest updates.
Thanks.
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.
Hello, Not sure if this is a nooby question. But, I've been playing around with roms for a while. Right now, im using the SlimKat rom on my Galaxy nexus ( version 4.4.2. Slim version: slim-4.4.2.build.5-official-4076). I was trying to change roms today. I went through the usual stuff. Factory reseting the phone and deleting the cache. When i went to transfer the files for the new rom to my phone from my PC i get an error that says " Cannot copy item The device has either stopped responding or has been disconnected". I can delete things on my phone from my computer and take files off the phone, but it wont let me put files on. After thinking it was the rom, i went to the toolkit to try to install the stock rom. This also didnt work. Any tips?
Hey Everybody
I'm new to the whole rooting process, which I did fine on Saturday the 4th of October 2014. Today (October 8th 2014) I tried to install Cyanogen using the installer, it said it worked, but when my phone rebooted it was in the original version of touchwhiz that came with my Galaxy S3 SGH-I747 Rogers version. I wanted to get my files back, so I went into CWM and tried to recover, which didn't work. I tried again and again and it finally loaded my apps, but I had no service and I was spammed with "failure to load .gapps.google" or something like that. I went into CWM and wiped cache, tried again, same issue. I then wiped everything, went back into it and it still was NOT working. What do I do? I have no service at all! I've tried pulling the SIM and putting it back, but no success. Please HELP!
EDIT: I flashed stock ROM using ODIN, which worked. I would still like to know why CWM didn't work though, and if it is still possible to try to get it to work
lasttimelord12 said:
Hey Everybody
I'm new to the whole rooting process, which I did fine on Saturday the 4th of October 2014. Today (October 8th 2014) I tried to install Cyanogen using the installer, it said it worked, but when my phone rebooted it was in the original version of touchwhiz that came with my Galaxy S3 SGH-I747 Rogers version. I wanted to get my files back, so I went into CWM and tried to recover, which didn't work. I tried again and again and it finally loaded my apps, but I had no service and I was spammed with "failure to load .gapps.google" or something like that. I went into CWM and wiped cache, tried again, same issue. I then wiped everything, went back into it and it still was NOT working. What do I do? I have no service at all! I've tried pulling the SIM and putting it back, but no success. Please HELP!
Click to expand...
Click to collapse
Anybody?
I'm a beginner myself, and i do not know much about installing custom roms on samsung phones, but maybe you did not flash a compatible custom kernel to support the custom rom? it seems like you did not flash gapps either, but that should not stop you from getting network service. my last guess would be that you need to also install a baseband perhaps. all this information should be there in the galaxy s3 section of the forums.
ishaang said:
did not flash a compatible custom kernel to support the custom rom? it seems like you did not flash gapps either, but that should not stop you from getting network service. .
Click to expand...
Click to collapse
Hey there, first off, thank you for replying.
I didn't manually use odin or other flashing software to flash the ROM. Unlike the rooting method (which went smoothly) I used the cyanogen mod installer. The installer itself said that cyanogen was installed successfully, but it was not. After it said this, my screen (on the phone) turned off, and I was brought to a fresh install of touchwhiz. I've actually fixed the networking issue by flashing touchwhiz stock,but that still doesn't explain why my CWM backup wasn't working.
I see...I haven't used the cyanogen mod installer myself so cannot say...
What I suggest is that, if you're up for trying again, to manually flash a rom - either Cyanogenmod or any other. There seem to be a lot of good roms available for your phone, and whichever rom you choose will come with instructions for how to install. The usual method will involve the following steps as far as I know:
- Root
- Unlock Bootloader
- Flash Custom Kernel with recovery
- Flash ROM
- Flash GAPPS
These steps are not difficult at all as long as you follow the instructions for your specific phone. I have a Sony Xperia SL and thats how I installed a custom rom on it many times. Sorry I could not help much not knowing Samsung procedures but good luck!
lasttimelord12 said:
Hey Everybody
I'm new to the whole rooting process, which I did fine on Saturday the 4th of October 2014. Today (October 8th 2014) I tried to install Cyanogen using the installer, it said it worked, but when my phone rebooted it was in the original version of touchwhiz that came with my Galaxy S3 SGH-I747 Rogers version. I wanted to get my files back, so I went into CWM and tried to recover, which didn't work. I tried again and again and it finally loaded my apps, but I had no service and I was spammed with "failure to load .gapps.google" or something like that. I went into CWM and wiped cache, tried again, same issue. I then wiped everything, went back into it and it still was NOT working. What do I do? I have no service at all! I've tried pulling the SIM and putting it back, but no success. Please HELP!
EDIT: I flashed stock ROM using ODIN, which worked. I would still like to know why CWM didn't work though, and if it is still possible to try to get it to work
Click to expand...
Click to collapse
OK,
Download stock ROM for your device from Samsung-updates.com according to device model and region.
Then flash it with Odin.
Good luck
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!