Related
Hi
I tried to flash my phone to GENERIC x10a R2 firmware using PC companion today and after everything is finished I tried to turn my phone on with SIM card inserted but the damn phone is stuck a activating phone screen! but when i use the phone without a the SIM card it works phone and desktop is displayed
I tried to flash the phone again with different rogers firmware and same issue happnes
Did I brick my phone?!?
No, you didn't brick it. Brick is when the phone doesn't boot correctly if at all. How exactly does it freeze? Does the OS still work while it fails to connect to the network? Or does the phone become unresponsive completely?
I would try testing a different phone with your SIM, and a different SIM onto your phone.
Just curious, did you root your phone prior to flashing??
Here is what happened exactly
I had Rogers firmware R2A020 and I found a Gerneric X10a R2A020 so I decided to flash it. I didnt try to root or anything just used simple PC companion method.
Flashing went successful, when I booted up my phone it took me to the initial setup screen and the phone fucntioned normally that is of course without using a SIM card!
I turned off the phone and inserted the SIM card booted it up I was welcomed by the infamous lock screen it said at the top "no SIM card is inserted" I swapped my finder to unlock the screen and a black screen came up with a message that says "Activating phone" with a circular logo that spins next to it.
The message was setting there for almost 20 min I cant go past through that screen. I tired using my brother's SIM card but it still doing the same thing.
The phone works without SIM card but when I put any SIM in it same problem happens!!
I tried to repair and even flashed back to Rogers firmware but same issue.
I read that two people had the same problem on other forums, one possible cause is could my IMEI been blocked by AT&T?
Thanks Guys
It is not a problem with your Provider. I had the same problem as you 2 days ago.
Unfortunately I could not find an easy fix for it.
I tried to do the flash the same as you did and came across that error, but I had already rooted my phone.
I have a friend who works for SE, who I took the phone to. Even he had problems updating the phone. In the end he had to connect it to EMMA and do a "Phone Activation", this was the only way he could reflash the phone. After that, it worked ok.
I can only suggest you take it a service centre and ask them to reflash it. Sorry that I dont have a solution for you.
you could try unsetting DEVICE_PROVISIONED in build.prop
zephyrix said:
you could try unsetting DEVICE_PROVISIONED in build.prop
Click to expand...
Click to collapse
how can I access that?
I had the same issue. I rooted an Xperia X10i, everything worked fine. I then tried the MarketEnabler application on it and at reboot I got that "Activating Phone" message and it hangs there.
First, if you go to flight mode, that unblocks the phone. Going back to normal mode works but not the SIM card.
Then I changed DEVICE_PROVISIONED to 0 in build.prop and everything works fine now. Thanks to zephyrix for your help.
I'm new to Android so I don't know if this is the proper way of changing this but here's what I did:
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb pull /sdcard/build.prop
Then edit build.prop in a text editor to set DEVICE_PROVISIONED to 0
adb push build.prop /sdcard/build.prop
adb shell dd if=/sdcard/build.prop of=/system/build.prop
adb shell rm /sdcard/build.prop
adb shell reboot
That should do it.
jaguarondi said:
I had the same issue. I rooted an Xperia X10i, everything worked fine. I then tried the MarketEnabler application on it and at reboot I got that "Activating Phone" message and it hangs there.
First, if you go to flight mode, that unblocks the phone. Going back to normal mode works but not the SIM card.
Then I changed DEVICE_PROVISIONED to 0 in build.prop and everything works fine now. Thanks to zephyrix for your help.
I'm new to Android so I don't know if this is the proper way of changing this but here's what I did:
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb pull /sdcard/build.prop
Then edit build.prop in a text editor to set DEVICE_PROVISIONED to 0
adb push build.prop /sdcard/build.prop
adb shell dd if=/sdcard/build.prop of=/system/build.prop
adb shell rm /sdcard/build.prop
adb shell reboot
That should do it.
Click to expand...
Click to collapse
I'm going to root my phone tonight, thanks for the tip I hope it works
well, i got the dreaded "can't mount /dev/block/mmcblk0p1" error, and decided to try some stuff i learned since i had some important photos/videos from a recent trip on there. turns out it worked, and figured i'd share with anyone (although it seems this error is fixed with the latest software). i recovered everything off my phone, totalling to approximate 1.7gig.
flash a adb recovery ROM with SU (can't remember if the SU is necessary, but there are pre-rooted roms out there, i just used one). also make sure all the drivers for the phone are installed on your computer
adb shell
su
echo /dev/block/mmcblk0 > /sys/devices/platform/s3c-usbgadget/gadget/lun1/file
with winhex, open drive. a directory browser will show your file structure, and right click-->recover/copy whichever files you want. i went a step further created an full image so i can send in the phone. now i have a complete backup i can go back too at any time in case i forgot something i needed.
i tried re-flashing this phone with jg8/jh2/jk3/jl2 with different PITS trying to bring it back and nothing. tried force mounting it and some other commands, but in the end, this worked.
somebody should give this a try.
great work
i could've really used this had it been a month ago, before i sent it in and lost everything
hey Ziostilon, when you had your phone fixed last month, did they mail you a new phone, or did you bring it in for repair? these Bell guys are breaking my balls and saying samsun can recover all my data, and i have to send it in for repair for a month
edit: it looks like this worked because the data on the partition is still intact, just the partition table is messed up. i wonder if a program like partition magic can repair the partition in it's current state? it might be something to look into for people without a warranty.
Hello everybody! please help me wtih next situation. I've bought Galaxy tab 7.7 in Tailand about a week ago. It is working fine, but one thing im worrying about - it is the impossibility to make my device wroking on local sim cards ( I live in Russia -operatos are Megafon and Beeline). I tried to switch my ROM to a stock Russian with changing region, and i tried to unlock my device by editing nv_data.bin but i did not succeed - i could not find 0x181469 and 0x18150e bytes in order to edit nv_data.bin manually via HexEditor. So i tried script method and i ran this in adb shell, having my device in debug mode ofc:
su
cd /sdcard
echo "this takes about 45 seconds"
if [ ! -f /sdcard/nv_data.bin.orig ]; then
echo "copying file to /sdcard"
cp /efs/nv_data.bin /sdcard/nv_data.bin.orig
fi
echo -en \\x00 > out0
dd if=nv_data.bin.orig of=out1 bs=1 count=1578089
dd if=nv_data.bin.orig of=out2 bs=1 skip=1578090 count=163
dd if=nv_data.bin.orig of=out3 bs=1 skip=1578254
cat out1 out0 out2 out0 out3 > nv_data.bin.unlocked
rm out0 out1 out2 out3
rm /efs/nv_data.bin
cp nv_data.bin.unlocked /efs/nv_data.bin
rm /efs/nv_data.bin.md5
reboot
Click to expand...
Click to collapse
my device rebooted normally - i found new nv_data.bin.UNLOCKED file on sd-card. I replaced old nv_data with a new one (ofc i removed UNLOCKED tag) and rebooted. After both reboots (reboot via adb shell and manual reboot) - still no effect - it keeps telling me that i need to put my sim into a tab.
I am really desperate solving this problem - i cant find solution though i tried surfing internet more carefully. Please help!
Fuda163 said:
Hello everybody! please help me wtih next situation. I've bought Galaxy tab 7.7 in Tailand about a week ago. It is working fine, but one thing im worrying about - it is the impossibility to make my device wroking on local sim cards ( I live in Russia -operatos are Megafon and Beeline). I tried to switch my ROM to a stock Russian with changing region, and i tried to unlock my device by editing nv_data.bin but i did not succeed - i could not find 0x181469 and 0x18150e bytes in order to edit nv_data.bin manually via HexEditor. So i tried script method and i ran this in adb shell, having my device in debug mode ofc:
my device rebooted normally - i found new nv_data.bin.UNLOCKED file on sd-card. I replaced old nv_data with a new one (ofc i removed UNLOCKED tag) and rebooted. After both reboots (reboot via adb shell and manual reboot) - still no effect - it keeps telling me that i need to put my sim into a tab.
I am really desperate solving this problem - i cant find solution though i tried surfing internet more carefully. Please help!
Click to expand...
Click to collapse
Refer back to your operator & change your sim card with a new one, had the same issue with my Vodafone sim card & a replacement with a new one solved this issue.
lsherif said:
Refer back to your operator & change your sim card with a new one, had the same issue with my Vodafone sim card & a replacement with a new one solved this issue.
Click to expand...
Click to collapse
I already did! I tried with 4 different sim cards from 3 operators and i bought a new sim card just for an experiment like 2 days ago - still no result. Maybe i should try mini sim wtih adapter... but what confuses me most is absence of above mentioned bytes in my nv_data.bin...how can i check whether my device unlocked or not?
Maybe you have a broken Sim slot. Check the. Forums and you'll find lots of ppl with broken sim slots
Sent from my HTC Vision using Tapatalk 2
regius said:
Maybe you have a broken Sim slot. Check the. Forums and you'll find lots of ppl with broken sim slots
Sent from my HTC Vision using Tapatalk 2
Click to expand...
Click to collapse
Turned out my sim slot was rly broken.
But guys from tech support with replacing my slot also chagned IMEI number. They said imei should be chagned in order to use your device in your country... now its functioning normally.
Anyone know where to get a replacement sim slot? Mine is broken and no-one locally in Sydney can source it from anywhere.
the SIM Slot seriously has issues!
the last few days, my 3g connection keeps dropping randomly and the device alerts "please enter sim card". I've only used a solid old style sim card, nothing else
i had the same problem "No Sim", and i just flashed PIT file from here and it worked perfectly
http://forum.xda-developers.com/showthread.php?t=1749854&page=6
Yeah!
dotvoid said:
the SIM Slot seriously has issues!
the last few days, my 3g connection keeps dropping randomly and the device alerts "please enter sim card". I've only used a solid old style sim card, nothing else
Click to expand...
Click to collapse
glad to see i was not the only one with this problem :laugh:
After a month of purchasing my 7.7 tab i experienced this on HC but after a few weeks of just letting it happen, because i was thinking i have a defective sim card, the problem just went away and never occured again. But here comes ICS first 3 days are problem free but after that the sim card problem again is now reoccurring :crying:
mcbooth said:
Anyone know where to get a replacement sim slot? Mine is broken and no-one locally in Sydney can source it from anywhere.
Click to expand...
Click to collapse
+1
I would also like to know this. Thanks
JoJo2211 said:
+1
I would also like to know this. Thanks
Click to expand...
Click to collapse
sorry guys but i ve a question ...is it obligatory when i replace mine sim card slot as it brroken ..change my IMEI no. or it is optional...thank u in advance
----------- FIXED ----------
Hey guys,
I'm encountering a terrible problem with my P6810 tab. Here is the story :
At first, I just did format /system/ (and /data/, cache and dalvik) in CWM before flashing a new Rom.
After reboot, the tab just got stuck on the "Galaxy Tab 7.7" logo. no bootloop, just stuck on static logo.
At this stage i could go to download mode and recovery, which I did.
I tried to reflash the rom, no success so then i tried to flash stock ICS firmware through Odin 1.85 : Stuck on flashing Factoryfs.img for several hours, so i had no choice but to reboot the tab. (i had no kies-related software running, neither my antivirus)
There, the tab got stuck on the "Firmware upgrade encountered an issue. please select recovery in Kies" screen, no way to go to either recovery or download mode (not even worth saying Kies didn't recognize the tab).
I've been struggling a few hours with that brick and finally managed to get acces to download and recovery modes again by flashing CWM with Odin alongside a PIT file with "repartition" ticked in Odin.
So there I could access recovery, I flashed CM9, everything went smooth. The tab rebooted and got passed the Galaxy tab 7.7 logo and went to the cm9 bootscreen but got stuck there (big desillusion right there).
So now in recovery, i can mount every partition but those two : /data/ and /sdcard/
I figured out by reading similar threads that the solution to my issue might be e2fsck through adb. I'm a complete noob to adb.
I can acces the adb shell but here are what the commands i've been reading about return me : (mmcblk0p9 is /data/ partition on P6810)
# e2fsck -fDC0 /dev/block/mmcblk0p9 :
e2fsck : Superblock invalid, trying backup blocks...
The superblock could not be read or does not describe as a correct ext2 filesystem.
If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else),
then the superblock is corrupt and you might try running e2fsck with an alternate superblock : e2fsck -b 8193 <device>
also had this once with this command :
bad magic number in superblock while trying to open /dev/block/mmcblk0p9
# e2fsck -b 8193 /dev/block/mmcblk0p9 :
Attempt to read block from filesystem resulted in short read while trying to open /dev/block/mmcblk0p9
Could this be a zero-length partition ?
# e2fsck -c /dev/block/mmcblk0p9 :
same as above
can you guide me with e2fsck or give me a link to a specific tutorial related to android e2fsck?
is there not a way in adb to like replace the corrupt partitions with freshly created ones ? or any other workaround ?
Any help will be appreciated a lot, i'm willing to donate to whoever provides me with a solution to get my tab running again.
Thanks for reading.
check this thread, very informative, helped me before
http://forum.xda-developers.com/showthread.php?t=1625675&highlight=bootscreen
Thanks a lot, already checked that one though.
Everything that worked for the guys in that thread doesn't work for me, or I'm too ignorant to find out the right e2fsck command...
Still no one able to provide some help please ?
It's weird that so many people are having the same issue on 7.7 these days, could it be related to the EU ban of this tab ?^^
Anyway, last day before i send it to Samsung
check this thread here it may help you solve your issue. All problems are coming from a brick bug in the ICS Kernel thats trigerred by wiping.
Thanks a lot, trying this right now
Can someone please post a (parted) print of a safe and working Galaxy Tab 7.7 (either of the two models) ?
I need the exact size of the /data partition
ISSUE FIXED Thanks to Zorbakun's last post. A million thanks dude.
However, the actual internal storage of my tab is now 50mb :silly: anyway i'll find a way to fix that too.
the actual internal storage of my tab is now 50mb
Hello Androguide.fr.
Did you manage to find a way to fix your shrink of internal storage? If so, would you mind to share the method. Thanks
Regards
Budi
cakrabayu said:
Hello Androguide.fr.
Did you manage to find a way to fix your shrink of internal storage? If so, would you mind to share the method. Thanks
Regards
Budi
Click to expand...
Click to collapse
Well yeah, didn't recover the 16gb but you can try to earn yourself some extra gigs by doing this once you created a fresh /data partiton :
this is an example for p6810, replace resize 9 with resize 10 if on a p6800
Code:
adb shell
parted /dev/block/mmcblk0
print
resize 9
It will ask you for start/end values, keep the same start value otherwise it will give you an error. A good idea is to resize the partition like + 500mb at a time, to avoid i/o errors you might get when creating/resizing large file systems.
Hope it helps, good luck.
I am about to have to do this myself, and i'm not a developer. i have accessed and navigated around my device through adb, but this level of complexity *almost* over my head. i just want to make sure i'm not going to permanently mess this up. also, someone in another thread tried flashing ICS with an older version of ODIN and now his tab won't even power on. which i'm trying to avoid... so after reading around these forums for a few days (it happened saturday morning--and i KNEW to avoid flashing from stock ICS recovery--i think i wiped /data-cache-dalvik with CWM 5.0.1) i'm pretty sure that failure to mount /data seems to be the super brick bug everybody's talking about. i bought the p6800 as an import in the US so i am without warranty... if anyone can help with a step by step guide for the masses or something... i'm intelligent, and quite computer literate/net saavy, but i'm not a mentat ("dune" reference)...
like, i'm having trouble figuring out how to install adb on windows. and how do i use parted when it's linux software? i've repartitioned HD's before, and i'm familiar with some command-line basics, but....
--going to bed now...my head hurts--
aletheus said:
I am about to have to do this myself, and i'm not a developer. i have accessed and navigated around my device through adb, but this level of complexity *almost* over my head. i just want to make sure i'm not going to permanently mess this up. also, someone in another thread tried flashing ICS with an older version of ODIN and now his tab won't even power on. which i'm trying to avoid... so after reading around these forums for a few days (it happened saturday morning--and i KNEW to avoid flashing from stock ICS recovery--i think i wiped /data-cache-dalvik with CWM 5.0.1) i'm pretty sure that failure to mount /data seems to be the super brick bug everybody's talking about. i bought the p6800 as an import in the US so i am without warranty... if anyone can help with a step by step guide for the masses or something... i'm intelligent, and quite computer literate/net saavy, but i'm not a mentat ("dune" reference)...
like, i'm having trouble figuring out how to install adb on windows. and how do i use parted when it's linux software? i've repartitioned HD's before, and i'm familiar with some command-line basics, but....
--going to bed now...my head hurts--
Click to expand...
Click to collapse
Try the .PIT file for the P6800 located here. You will lose all data, and part of your internal SD space. Looks like the brick happens consistently at the same point of the memory chip, so the same .PIT works for most people. If that doesn't help, you will need parted.
How can you use parted? It's a Linux program that runs in your tablet. You will adb shell to it, then you will have a Linux shell. Everything you put down there will run in your tablet, as if you were typing on it (think ssh, or remote desktop). I can't help you much more, because (knocks on wood) my tablet is still very much alive, and I don't use ADB that much.
Now, I don't know how it works in your country, but here in Brazil the Samsung service accepts warranties issued anywhere. It may be worth a shot.
aletheus said:
I am about to have to do this myself, and i'm not a developer. i have accessed and navigated around my device through adb, but this level of complexity *almost* over my head. i just want to make sure i'm not going to permanently mess this up. also, someone in another thread tried flashing ICS with an older version of ODIN and now his tab won't even power on. which i'm trying to avoid... so after reading around these forums for a few days (it happened saturday morning--and i KNEW to avoid flashing from stock ICS recovery--i think i wiped /data-cache-dalvik with CWM 5.0.1) i'm pretty sure that failure to mount /data seems to be the super brick bug everybody's talking about. i bought the p6800 as an import in the US so i am without warranty... if anyone can help with a step by step guide for the masses or something... i'm intelligent, and quite computer literate/net saavy, but i'm not a mentat ("dune" reference)...
like, i'm having trouble figuring out how to install adb on windows. and how do i use parted when it's linux software? i've repartitioned HD's before, and i'm familiar with some command-line basics, but....
--going to bed now...my head hurts--
Click to expand...
Click to collapse
I am working on writing a specific 7.7 guide to teach people the parted/e2fsck technique I use to revive my bricked p6810 everytime I want to flash a new rom or test my builds.
First, as pointed out, try to Odin the PIT file for your particular model (eg : P6800 16gb).
You got to know that the parted technique is a pain in the ass, that you'll have to do it quite often if you like flashing roms, and that your tab will have a much smaller internal storage.
I think the guide will be ready in a couple days but you can pm be if you need help before that, no problem.
Good luck with this superbrick curse
thanks guys for your help, i'm going to try to figure this out this afternoon. i'm in the US, so they don't even offer warranties on imports. i was told by a samsung rep in the US that they don't grant warranties to imported models. i will first try the modified PIT file, then i will try the more complex method. @Androguide.fr i will PM you if i have trouble with the more complicated method later. thanks!!!!
aletheus said:
thanks guys for your help, i'm going to try to figure this out this afternoon. i'm in the US, so they don't even offer warranties on imports. i was told by a samsung rep in the US that they don't grant warranties to imported models. i will first try the modified PIT file, then i will try the more complex method. @Androguide.fr i will PM you if i have trouble with the more complicated method later. thanks!!!!
Click to expand...
Click to collapse
I just finished writing the guide, it's here : forum.xda-developers.com/showthread.php?t=1862294
Hi everyone.
First, I'm a noob on all this flashing Roms thing, so I'm a bit overwhelmed here. So please feel free to correct me if I'm saying the biggest mistake of all times.
I was setting up a Samsung Galaxy Tab 4 10.1 (SM-T530) for one of my colleagues, and was using Samsung's Device Configuration Tool (DCT) to set up most preferences.
I've played around some settings, and removed access to the "Settings" area, but I mistakenly thought that I still could adjust the profile afterwards, via DCT!
Unfortunately, it seems I've removed access to the Network "stack", so my device is isolated from the world.
When you remove access to "Settings", Samsung's tools immediately disables access to USB, Wifi, Bluetooth, SD card and other ways of connecting.
The device works, but cannot access anything, not even the machine that inserted the Security Policy.
I've tried to wipe data / factory reset on boot, but it says: MDM does not allow factoryReset
So my questions are:
- what should I do next?
- are there ways of bypassing security, to restore access and inject a new profile?
- should I flash a new ROM? (couldn't find a Stock version of it so far).
Thanks in advance to any kind soul that may spend his precious time helping this stupid f*ckup.
Also found this other guy that had the same problem as me, but the thread doesn't reflect the solution.
http://forum.xda-developers.com/galaxy-tab-3/help/reset-t2880721#post61484468
urbgimtam said:
Also found this other guy that had the same problem as me, but the thread doesn't reflect the solution.
http://forum.xda-developers.com/galaxy-tab-3/help/reset-t2880721#post61484468
Click to expand...
Click to collapse
U,
hi, after some attempts at starting settings or anything else from a terminal command line, for example
am start -a android.intent.action.MAIN -n com.android.settings/com.android.settings
Note- the above command still fails when;
am start --user 0 -a android.intent.action.MAIN -n com.android.settings/com.android.settings
not the correct "program", com.android.settings does not exist, but i just wanted to see about the permission issue , so when;
am start --user -2 -a android.intent.action.MAIN -n com.android.settings/com.android.settings
still denied.
i am learning you cannot do so as user, at least this way. You need to be rooted.
You are likely going to need to reflash firmware completely.
Alternately, flash a custom recovery so you can get adb access as root from terminal and try a surgical strike by that route
to undo what you did, after some research of course to figure out what changes you need to undo.
if you get that "fixed" then likely you can overwrite the custom recovery with a stock recovery from an sm-t530 device
If you know anyone who can get the above command corrected and working then that might be the way?
moonbutt74 said:
U,
hi, after some attempts at starting settings or anything else from a terminal command line, for example
am start -a android.intent.action.MAIN -n com.android.settings/com.android.settings
Note- the above command still fails when;
am start --user 0 -a android.intent.action.MAIN -n com.android.settings/com.android.settings
not the correct "program", com.android.settings does not exist, but i just wanted to see about the permission issue , so when;
am start --user -2 -a android.intent.action.MAIN -n com.android.settings/com.android.settings
still denied.
i am learning you cannot do so as user, at least this way. You need to be rooted.
You are likely going to need to reflash firmware completely.
Alternately, flash a custom recovery so you can get adb access as root from terminal and try a surgical strike by that route
to undo what you did, after some research of course to figure out what changes you need to undo.
if you get that "fixed" then likely you can overwrite the custom recovery with a stock recovery from an sm-t530 device
If you know anyone who can get the above command corrected and working then that might be the way?
Click to expand...
Click to collapse
Hi moonbutt74, and thanks for helping.
Just finished trying to flash an official ROM, which downloaded and installed successfully, but the problem still maintains...
I'm learning as I go, here, so I may be saying something wrong.
Shouldn't I just need to wipe the data? After all, this may just be a permissions problem, right?
When I flashed the ROM (using ODIN 3.09), it has options to "re-partition" and "Nand Erase All". Should I try one of these?
Also, when choosing the "apply update from adb", it says: "Now send the package you want to apply to the device with 'adb sideload <filename>'.
I've done the following:
"adb devices" to start adb-server and list the device (successful)
"adb sideload [pathtofile]" (successfull) - file is uploaded.
Device then says "E: footer is wrong" and "E: signature verification failed".
So no go.
Also, I just realized I don't have access to adb, as it says "error: closed" if you do any operation except "adb sideload".
So now, to root, what must I do? Flash a rooted ROM?
I do have other identical devices - is there a way to take an image from one of them and upload to the "bad" one?
Kind regards again, thanks for helping out.
Hi,
DO NOT play with Odin, no repartition or anything similar,
At this point you need to flash a custom recovery and root the tab, and/or find out what this samsung tool did and where,
Rule Number 1- never take on a job like that for someone else
So if the tab owner gives the go ahead, flash a custom recovery and root
Then;
first while in regular operation, plug tab into pc and try this in terminal ON TAB,
you must su first, su -c does not do it
su
echo 1 > /data/property/persist.service.adb.enable
now if you get the device pickup notification on pc, get terminal on pc open and run
adb shell
if that goes through run
mount
if all partitions are mounted then you should be good to go as far as access.
From there you will need to find out where this configuration software set and wrote what it did and undo it or correct it.
Try one of these recoveries https://www.androidfilehost.com/?w=files&flid=23537
for sm-t530nu recovery build rename from
sm-t530nu-Philz-6_58_9-final-recovery.tar.md5
to
sm-t530nu-Philz-6_58_9-final-recovery.tar
When you flash the recovery UNCHECK auto restart function in Odin, when flash is complete [res-ok]
unplug tab and manually reboot to RECOVERY --- Home Vol+ Power
if you don't the rom wil rewrite stock recovery and you will have to do it again
m