Database Info

[Q] Note 10.1 4G N8020 messed up

Hi all. Tried my first root + custom rom installation and i messed up the device..
i had the newest KIES firmware update (phone XXBMA5) and (XXBMA6) and i rooted the device with odin (3.07). That went OK.
Then i installed the CWM recovery with odin and that was OK too.
Then i downloaded the latest Omega Rom (i missread that it supports N8020) and followed the installation instructions to the point where it started installing Omega V2.0 from SDCARD and then it asked me to select device from a list that included only (N8000,N8010,N8013)..
So the situation now is that i have working odin, working CWM and backup of the EFS (img+tar) but no working recovery. i live in Finland and the device is Sonera locked i think, so the stock roms (international) do not work i guess.
KIES has a backup of my Note but i can't even get to a point where KIES discovers the device.
So basically i think i need a working ROM for my model (Note 10.1 4G N8020), or can i recover the original samsung software somehow ?
Any advices ?

Removed

Just a thought, but can't you reflash CWM or the stock recovery?
If you didn't install the rom why do you need to re-install anything. Just powering down and powering up should have left you as was....

Alajarvi84 said:
working CWM .......... but no working recovery.
Click to expand...
Click to collapse
Maybe i'm missing something but isn't CWM your custom recovery?
It doesn't sound like you've actually installed any rom yet.The Omega installer doesn't actually install anything until a few steps after the one you mentioned about the model type.
I'm with ultramag69 on this one. You should still be on a stock rom unless you already wiped your original rom.

Hi again. Problem solved, just had to do emergency thing from KIES. Like i said this was the first time trying root + custom ro install and to be honest it went to ****. Somehow i managed to delete the stock firmware so that is why the recovery gave me (no files). I did make some backup but when tried to restore it said MD5 mismatch or something. At first the KIES emergency recovery could not find the device, but after i switched from CWMcto stock recovery it worked.
So what did i learn from all this ? Nothing, because i am getting too old (tired+lazy ) to do proper investigation. So one could say my strategy is to bang my head to the wall as long as it takes to go trough. Even if i could just go around it
So basically i am now at the point where i started, with stock 4.1.2 rooted. Used the triangle away to wipe the (6) custom installs or something away, but it still says custom in the settings> information. Does this mean that OTA won't work ? Any way around it ? Because i would like to check now and then that is my version of android the newest one..
Could someone recommend a custom ROM for my Note 10.1 4G (LTE) N8020 4.1.2 because the only one i was able to find was the CyanogenMod (or something) and it basically makes the S-Pen (almost) useless. What i would like is the Omega ROM, but like stated before the installation only supported N8000, N8010 & N8013...
Added screenshot from info.
Thanks anyway

What is truly amazing is that i did not brick the device tough..

switch from cwm to stock
Alajarvi84 said:
Hi again. Problem solved, just had to do emergency thing from KIES. Like i said this was the first time trying root + custom ro install and to be honest it went to ****. Somehow i managed to delete the stock firmware so that is why the recovery gave me (no files). I did make some backup but when tried to restore it said MD5 mismatch or something. At first the KIES emergency recovery could not find the device, but after i switched from CWMcto stock recovery it worked.
So what did i learn from all this ? Nothing, because i am getting too old (tired+lazy ) to do proper investigation. So one could say my strategy is to bang my head to the wall as long as it takes to go trough. Even if i could just go around it
So basically i am now at the point where i started, with stock 4.1.2 rooted. Used the triangle away to wipe the (6) custom installs or something away, but it still says custom in the settings> information. Does this mean that OTA won't work ? Any way around it ? Because i would like to check now and then that is my version of android the newest one..
Could someone recommend a custom ROM for my Note 10.1 4G (LTE) N8020 4.1.2 because the only one i was able to find was the CyanogenMod (or something) and it basically makes the S-Pen (almost) useless. What i would like is the Omega ROM, but like stated before the installation only supported N8000, N8010 & N8013...
Added screenshot from info.
Thanks anyway
Click to expand...
Click to collapse
How did you switch from CWM to stock? I have having a problem syncing with kies also using omega rom on n8013.

jjndimp said:
How did you switch from CWM to stock? I have having a problem syncing with kies also using omega rom on n8013.
Click to expand...
Click to collapse
I was not easy, i just tried the download mode over and over again with KIES open in windows and somehow it finally did find my device and offered a emergency restore. That is it, and the device was restored to default "original state".

OMG.... one would think after nearly having bricked your device you would either A) stop messing around with it or, B) read and learn more about what you're wanting to achieve and THEN maybe trying something with the ABSOLUTE certainty that a backup to restore is available to you in case of any mishap!
Moral of story :
Don't do anything until you are absolutely sure you have read EVERYTHING about what you are going to do.
For others wanting to mess with their devices, take heed! You may not be as lucky as OP (or troller) whichever is applicable.

There comes a certain point, that when crossed one does not care what happens to the device at hand. After fighting with my n8020 for several days in a row i couldn't care less, and like said before i dont have the level of enhusiasm like i had when i was younger. Of course i know now what went wrong.. But seriously, these are just overpriced toys, so it's not a matter of life and death.
Sent from my GT-N8020 using XDA Premium HD app

[Q] JellyBam Installation Problem!

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.

[Q] 7.0Tab2 "status 7" errors. Help?

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.

[Q] Samsung Galaxy S3 L710 Flashing Cyanogenmod Failure

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.

[Completed] Is My Phone "Bricked?"

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!