Database Users

[Q] factory-reset S4 - keeps going into recovery

Hi, all
I have an S4, the I9505. I wanted to install a new KitKat-rom, the I9505_-_Official_Google_Edition_4.4.2_by_Jamal2367_Final-R1.2.
Then I wiped the device (I'm using CWM philz_touch_6.09.6-jfltexx.tar) but when installing the ROM, I get a weird '7'-error,
I forgot the real error.
Anyways: I thought: forget it and let's go back to stock.
So I rebooted in recovery, wiped/factory reset my s4 and rebooted. But it just comes back in Recovery?
What's wrong?
So then I thought: let's ODIN a factory-ROM, which I can download from SAMFIRMWARE.COM but since the file is
bigger than 1Gb I need to pay. Well, I don't care about the 5 euro's but I don't want to leave my creditcard stuff behind.
Any other options??
Thanks!

rommelrommel said:
Hi, all
I have an S4, the I9505. I wanted to install a new KitKat-rom, the I9505_-_Official_Google_Edition_4.4.2_by_Jamal2367_Final-R1.2.
Then I wiped the device (I'm using CWM philz_touch_6.09.6-jfltexx.tar) but when installing the ROM, I get a weird '7'-error,
I forgot the real error.
Anyways: I thought: forget it and let's go back to stock.
So I rebooted in recovery, wiped/factory reset my s4 and rebooted. But it just comes back in Recovery?
What's wrong?
So then I thought: let's ODIN a factory-ROM, which I can download from SAMFIRMWARE.COM but since the file is
bigger than 1Gb I need to pay. Well, I don't care about the 5 euro's but I don't want to leave my creditcard stuff behind.
Any other options??
Thanks!
Click to expand...
Click to collapse
Download and Flash Philz Recovery 6.09.2 via recovery then reboot recovery and then do a fullwipe and flash the Custom rom you want and you wont get that Error 7 anymore

Repulsa said:
Download and Flash Philz Recovery 6.09.2 via recovery then reboot recovery and then do a fullwipe and flash the Custom rom you want and you wont get that Error 7 anymore
Click to expand...
Click to collapse
Thanks, but ... your link wad dead. Did some searching, saw a newer version (6.13.1 from Feb 6).
Installed that without issues.
Booted in recovery, factory reset + davlik , installed the ZIP.
Same error: Status 7.
Or should I have used only the version you mentioned?

rommelrommel said:
Thanks, but ... your link wad dead. Did some searching, saw a newer version (6.13.1 from Feb 6).
Installed that without issues.
Booted in recovery, factory reset + davlik , installed the ZIP.
Same error: Status 7.
Or should I have used only the version you mentioned?
Click to expand...
Click to collapse
When i was clickin the file i gave you, it works tho but Yea feel free to download that version 6.09.2 and you should be fine flashing any custom rom.

Because of this error, yes, it won't boot to system. Been there. You should've made a backup. I just restored it and voila.
That error "status 7" seems to be the problem with Philz recovery, when I switched to TWRP I was able to flash any rom no problems.

Repulsa said:
When i was clickin the file i gave you, it works tho but Yea feel free to download that version 6.09.2 and you should be fine flashing any custom rom.
Click to expand...
Click to collapse
Hm, thanks again, I think there's much more going on.
I downloaded a 4.3 STOCK-rom, and in download-mode I was able to get a working phone again.
That is: apparently everything works BUT I cannot enable WIFI.
I saw another thread on that for a different phone.
But ... this is a phone from my employer ... I now have the KNOX Waranty VoId set to 0x1
I guess this is the reason for not being able to switch on WIFI ...
If I try to switch on wifi I get a security notice:
'your device's security has blocked an action that is not permitted. No further action is required'
If I pres on App-info, it comes out of KNOX ...
I guess this is also the reason for the Status-7 error ....

SOLVED!
When i was looking for the factory-ROM I ended at SamMobile. According to that page I 'landed' on, the latest factory-ROM for the I9505
was for 'Montenegro'.
I then downloaded the one specific for the Netherlands (where I live) and used ODON directly on top of the Montenegro-version,
no factory-reset.
After booting, WiFi was back aain, message about KNOX is gone. It's even rooted again, so it all works.
Yes, I still have the KNOX warranty Void 0x1 but I can access corporate e-mails so good to go.
Pfew ...

[Q] [HELP] i9505 Recovery Booting Stuck

Hello guys,
I need your help again!
I recently changed my i9100g with this other device, GT-I9505 Italian version, no brand.
The history of this device was quite this: stock FW until 4.3 (just my suppose) --> CM11 --> try to flash 4.2.2 stock --> brick @[email protected]
Now I tried to put the original 4.4.2 firmware by flashing with Odin v3.09, because I don't want custom rom for the moment, just make it work.
The problem is that the phone stucks at Samsung logo, and when I tried to go in recovery mode, it stays on the same logo but there's a blue write in the top left corner "Recovery Booting".
Do you have any suggestion?
TY in advance

Drake9090 said:
Hello guys,
I need your help again!
I recently changed my i9100g with this other device, GT-I9505 Italian version, no brand.
The history of this device was quite this: stock FW until 4.3 (just my suppose) --> CM11 --> try to flash 4.2.2 stock --> brick @[email protected]
Now I tried to put the original 4.4.2 firmware by flashing with Odin v3.09, because I don't want custom rom for the moment, just make it work.
The problem is that the phone stucks at Samsung logo, and when I tried to go in recovery mode, it stays on the same logo but there's a blue write in the top left corner "Recovery Booting".
Do you have any suggestion?
TY in advance
Click to expand...
Click to collapse
Flash the stock rom again..and do NOT check autoreboot in odin.
The straight away boot into recovery, factory reset it..and you'll boot
"If someone helps, never forget to hit thanks ? "

DeepankarS said:
Flash the stock rom again..and do NOT check autoreboot in odin.
The straight away boot into recovery, factory reset it..and you'll boot
"If someone helps, never forget to hit thanks ? "
Click to expand...
Click to collapse
Thank you very much for your reply!
It doesn't work, maybe I'm just doing something wrong, what should I have to do after flash?

Drake9090 said:
Thank you very much for your reply!
It doesn't work, maybe I'm just doing something wrong, what should I have to do after flash?
Click to expand...
Click to collapse
-Open odin
-Uncheck autoreboot
-Add your firmware file to the AP/PDA section
-Start the process
When this will end, your ohone wont boot automatically (obviously)
After 2-3 minutes start it, if it turns on properly congo..
If it doesnt..just boot into recovery (volume up+home button+power button) and perform a data wipe.
If this does not helo at all, download the LATEST KITKAT 4.4.2 UNBRANDED again for your phone as it can be a bad download issue too.
"If someone helps, never forget to hit thanks ? "

DeepankarS said:
-Open odin
-Uncheck autoreboot
-Add your firmware file to the AP/PDA section
-Start the process
When this will end, your ohone wont boot automatically (obviously)
After 2-3 minutes start it, if it turns on properly congo..
If it doesnt..just boot into recovery (volume up+home button+power button) and perform a data wipe.
If this does not helo at all, download the LATEST KITKAT 4.4.2 UNBRANDED again for your phone as it can be a bad download issue too.
"If someone helps, never forget to hit thanks ? "
Click to expand...
Click to collapse
I would try another firmware less recent, just to see what happens...
But I have great news: Philz touch works, so now I have a working custom recovery!
the problem is that I can't just flash a custom ROM to repair
I think I need the pit file, but I can't find one on the internet @[email protected]

Drake9090 said:
I would try another firmware less recent, just to see what happens...
But I have great news: Philz touch works, so now I have a working custom recovery!
the problem is that I can't just flash a custom ROM to repair
I think I need the pit file, but I can't find one on the internet @[email protected]
Click to expand...
Click to collapse
Y do you need a pit? Pit files are not to be played with and can possibly brick if not flashed with utmost care.
Try a stock firmware first. Dont try any stock firmware till you have a working phone..
"If someone helps, never forget to hit thanks ? "

DeepankarS said:
Y do you need a pit? Pit files are not to be played with and can possibly brick if not flashed with utmost care.
Try a stock firmware first. Dont try any stock firmware till you have a working phone..
"If someone helps, never forget to hit thanks ? "
Click to expand...
Click to collapse
I'm flashing this firmware: I9505XXUGNG8_I9505ITVGNG1_ITV
I was thinking about pit because the philz says strange errors:
failed to mount /data to setup /data/media, or something like this... and also other problems related to /sdcard
Have you an idea on what to do?
I'm just following this guide: http://forum.xda-developers.com/showthread.php?t=2265477

Drake9090 said:
I'm flashing this firmware: I9505XXUGNG8_I9505ITVGNG1_ITV
I was thinking about pit because the philz says strange errors:
failed to mount /data to setup /data/media, or something like this... and also other problems related to /sdcard
Have you an idea on what to do?
I'm just following this guide: http://forum.xda-developers.com/showthread.php?t=2265477
Click to expand...
Click to collapse
The pit file is right there in @samersh72s thread
In the attachments.
Flash properly after reading the OP very carefully and DO NOT SKIP ANY STEP OR MODIFY any
Still IMHO a data wipe after reflashing can fix your bootloop.
"If someone helps, never forget to hit thanks ? "

DeepankarS said:
The pit file is right there in @samersh72s thread
In the attachments.
Flash properly after reading the OP very carefully and DO NOT SKIP ANY STEP OR MODIFY any
Still IMHO a data wipe after reflashing can fix your bootloop.
"If someone helps, never forget to hit thanks ? "
Click to expand...
Click to collapse
I thought the same way too, but didn't work...
The attachment doesn't work, but some posts later there is one working
I'll try and let you know the results!

Stll locked here...
Used yhe pit file, but nothing changed
in Philz Touch 6 with CWM 6.0.4.7 I have this error:
E: could not mount /data to setup /data/media path!
Have you ever faced it?

Drake9090 said:
Used yhe pit file, but nothing changed
in Philz Touch 6 with CWM 6.0.4.7 I have this error:
E: could not mount /data to setup /data/media path!
Have you ever faced it?
Click to expand...
Click to collapse
Ermm no...
@Lennyz1988 @MAX 404
Help?
Sent from my GT-I9500 using XDA Free mobile app

I was thinking about a possible cause: could it be that I'm using a wrong firmware?
this device is used, so I supposed that it was ITV the correct firmware, but not 100% sure...
I'm just sure that it is no-brand.

Drake9090 said:
I was thinking about a possible cause: could it be that I'm using a wrong firmware?
this device is used, so I supposed that it was ITV the correct firmware, but not 100% sure...
I'm just sure that it is no-brand.
Click to expand...
Click to collapse
Screenshots of "phone info samsung" app please.
"If someone helps, never forget to hit thanks ?"

When you flash the Odin firmware it's succesfull?

DeepankarS said:
Screenshots of "phone info samsung" app please.
"If someone helps, never forget to hit thanks ?"
Click to expand...
Click to collapse
The only info that I'm able to see are the ones in download mode...
If the phone don't boot any firmware, how can I use that app?

Lennyz1988 said:
When you flash the Odin firmware it's succesfull?
Click to expand...
Click to collapse
Yes, or better to say, Odin says PASS, but when I reboot (even with or without Auto-Reboot flag) the phone stucks on Samsung Logo saying Recovery Booting.

DeepankarS said:
The pit file is right there in @samersh72s thread
In the attachments.
Flash properly after reading the OP very carefully and DO NOT SKIP ANY STEP OR MODIFY any
Still IMHO a data wipe after reflashing can fix your bootloop.
"If someone helps, never forget to hit thanks ? "
Click to expand...
Click to collapse
Drake9090 said:
Yes, or better to say, Odin says PASS, but when I reboot (even with or without Auto-Reboot flag) the phone stucks on Samsung Logo saying Recovery Booting.
Click to expand...
Click to collapse
On top of all advice given here...
Can you boot at all? what is the status at the moment , rom recovery?
I would try to flash a recovery first ( twrp , philz) see if it works , do a factory reset ( backup first) and try flashing a stock rom,,see if it helps

MAX 404 said:
On top of all advice given here...
Can you boot at all? what is the status at the moment , rom recovery?
I would try to flash a recovery first ( twrp , philz) see if it works , do a factory reset ( backup first) and try flashing a stock rom,,see if it helps
Click to expand...
Click to collapse
The situation is still the same, so in order:
I cannot boot a complete system, I just stuck on samsung i9505 logo with blue "Recovery Booting" written in top-left on the screen;
At the moment I'm reflashing ossessively the stock rom, and philz touch; I can go in DL mode and not in the stock recovery, but when I flash philz touch I can enter by double clicking vol up when I see the blue, red and yellow writes.
I cannot do a factory reset, that is the real problem I suppose, 'cause when I enter in philz recovery, it says: "error mount /data etc etc..." as you can see in previous posts.
In DL mode this is the situation:
PN: GT-I9505
Current binary: Samsung Official
System Status: Custom
Knox Kernel Lock: 0x0
Knox Warranty Void: 0x1
csb-config-lsb: 0x30
write prot: enabled
eMMC Burst mode enabled

Drake9090 said:
The situation is still the same, so in order:
I cannot boot a complete system, I just stuck on samsung i9505 logo with blue "Recovery Booting" written in top-left on the screen;
At the moment I'm reflashing ossessively the stock rom, and philz touch; I can go in DL mode and not in the stock recovery, but when I flash philz touch I can enter by double clicking vol up when I see the blue, red and yellow writes.
I cannot do a factory reset, that is the real problem I suppose, 'cause when I enter in philz recovery, it says: "error mount /data etc etc..." as you can see in previous posts.
In DL mode this is the situation:
PN: GT-I9505
Current binary: Samsung Official
System Status: Custom
Knox Kernel Lock: 0x0
Knox Warranty Void: 0x1
csb-config-lsb: 0x30
write prot: enabled
eMMC Burst mode enabled
Click to expand...
Click to collapse
Lets go one step at the time.........forget about recovery for now
Flashing with Odin a stock rom ( use same rom you had before or newer) , what happen? did you followed the guide
http://forum.xda-developers.com/show....php?t=2265477 that @DeepankarS suggested ? did you flash the PIT file?

MAX 404 said:
Lets go one step at the time.........forget about recovery for now
Flashing with Odin a stock rom ( use same rom you had before or newer) , what happen? did you followed the guide
http://forum.xda-developers.com/show....php?t=2265477 that @DeepankarS suggested ? did you flash the PIT file?
Click to expand...
Click to collapse
Followed that guide many times, but the result is stuck in Samsung Logo.
Even tried flashing PIT file, but nothing changed.
maybe flash just a stock recovery after the firmware could solve the problem?

[Q] SM-G900I

Hi There
Im trying to fix another persons SM-N900I which is stuck in a bootloop.
WHAT HAPPENED TO THE PHONE
What I've been told is that the phone was receiving an OTA upgrade to Lollipop in which it crashed somewhere in the process, which caused the phone to become all glitchy (that's what she said). In addition this caused the KNOX flag to be tripped which meant that the carrier staff refused to honour the warranty saying it was caused by a custom flash.
So attempting to remedy this she tried to use odin to flash a stock rom which sent the phone into an indefinite bootloop. (Sorry no idea what rom she tried to flash or if she clicked something wrong).
WHAT I'VE TRIED
Using Kies to "Firmware Upgrade and Intialisation" with the model number and S/N. This completed successfully with no errors, however after a restart I still get a bootloop.
As in 1 but with factory reset and clearing cache in recovery before flash.
Using odin to flash stock rom from sammobile. Still bootlooped after flash.
Trying stock KITKAT rom from sammobile with odin. Still bootloops after flash.
Installing a custom recovery and installing a couple of custom roms (factory resetting and clearing dalvik cache before install). Still bootloops...
Flashing stock bootloader, and stock rom. Still bootloops...
I wanted to try and flash a PIT file however I get the "secure check fail : PIT" message with and without flashing it with stock rom. Im assuming this is because reactivation lock wasn't disabled.
Not really sure where to go from here?
Thank You

makeez said:
Hi There
Im trying to fix another persons SM-N900I which is stuck in a bootloop.
WHAT HAPPENED TO THE PHONE
What I've been told is that the phone was receiving an OTA upgrade to Lollipop in which it crashed somewhere in the process, which caused the phone to become all glitchy (that's what she said). In addition this caused the KNOX flag to be tripped which meant that the carrier staff refused to honour the warranty saying it was caused by a custom flash.
So attempting to remedy this she tried to use odin to flash a stock rom which sent the phone into an indefinite bootloop. (Sorry no idea what rom she tried to flash or if she clicked something wrong).
WHAT I'VE TRIED
Using Kies to "Firmware Upgrade and Intialisation" with the model number and S/N. This completed successfully with no errors, however after a restart I still get a bootloop.
As in 1 but with factory reset and clearing cache in recovery before flash.
Using odin to flash stock rom from sammobile. Still bootlooped after flash.
Trying stock KITKAT rom from sammobile with odin. Still bootloops after flash.
Installing a custom recovery and installing a couple of custom roms (factory resetting and clearing dalvik cache before install). Still bootloops...
Flashing stock bootloader, and stock rom. Still bootloops...
I wanted to try and flash a PIT file however I get the "secure check fail : PIT" message with and without flashing it with stock rom. Im assuming this is because reactivation lock wasn't disabled.
Not really sure where to go from here?
Thank You
Click to expand...
Click to collapse
If you are using Windows operating system, have you tried running Odin "As Administrator" ( using right click on the mouse when you open Odin ), then try partitioning with the PIT file.

SM-G900S bootloop after trying to root

Good afternoon guys,
i have a big issue with my galaxy s5 SM-G900S (korean version). I bought it as a refurbished device. Knox was on 0x1 so something may have been modified.
It came with the stock (?!) android 4.4.2 from march14. I tried to update but it returned a registration error. Probably because knox is 0x1
In any case, I activated usb debugging and tried to root the phone using cfautoroot and the corresponding root file: CF-Auto-Root-klteskt-klteskt-smg900s.zip which I still assume to be the correct one.
I used odin for flashing. The device was properly connected (blue).
Everything seemed to go smooth until the phone restart when it said "recovery is not seandroid enforcing". I tried several times with both odin 3.07 and 3.09 but i cannot pass this step. I also tried the method to untick auto reboot, shut the phone down manually and boot into recovery mode but it failed.
This means I am now stuck in the bootloop. I can access download mode, but i cannot reach recovery mode. Also the phone is not recognized by the computer if i try to connect it to adb, kies etc. Odin seems to connect properly still.
Alright how should i proceed now?? My actual target is to flash a custom rom. I will need to go for a dirty flash now correct? Should I flash a stock rom with odin? If yes, which one?
Please support me a bit, I am very frustrated on this topic, especially cause I still dont realize my mistake......
Merry Christmas and greets from Bavaria, Germany.
cheeet

Flash the stock firmware to get out of boot loop. After flashing the stock firmware, everything should be working fine and booting again. Instead of using CF auto root, flash a custom recovery like TWRP and then use it to flash the SuperSU zip.

toxious651 said:
Flash the stock firmware to get out of boot loop. After flashing the stock firmware, everything should be working fine and booting again. Instead of using CF auto root, flash a custom recovery like TWRP and then use it to flash the SuperSU zip.
Click to expand...
Click to collapse
Alright, Im back to stock android 4.4.2 now. Works perfect, aside from registration. If I click on "update now" it shows: SKT-USIM required.
Can someone link a detailed guide for flashing cm13? I checked the web but i still dont entirely understand.
In any case I do not want to risk going into a tricky situation once more.....
Thanks in advance.
Greets, cheet

bricked s5 g901f "could not do normal boot"

hello everyone, after rooting and flashing lots of phones, i have probably managed to brick one
since i am using linux, i tried heimdall wich detected but couldnt flash , not even read pit
i tried to root it, with kingroot, failed
then i tried kingoroot desktop app, it seemed to work then after flashing philzcwm using rashr, it went into download mode
at some time i may have flashed a recovery img onto BL, wich i NOW know is the bootloader
i knew that i shouldnt mess with the bootloader, but didnt think BL was bootloader
now using odin 3.10.6 in win xp it doesent seem to do nothing
it automatically goes into download mode with first line saying
"could not do normal boot"
i am now downloading an original firmware 4.4.6 from sam mobile
can anyone help me or is it bricked?

Lost count of how many things you did wrong there
Get a Native Windows 7+ PC running, boot the phone into download mode, flash stock ROM with ODIN 3.10.7
If it fixes it - spend a long time reading threads here on XDA before trying anything else

i dont think i flashed the bootloader, i remembered, odin was crashing before i ever hit start cause i was selecting the md5 and it didnt have the tar
now after flashing twrp 2.8 it boots fine, but if i try to boot in recovery, it goes to download mode "cant do normal boot"
flashed cf autoroot it also goes to download mode
i remember on galaxy s3 if you didnt restart straight to recovery just after flashing it would overwrite with stock recovery
but now if i try to restart to recovery after flashing it doesent do anything, i have to unplug it and take out the battery
edit
if i press vol[-] home power it goes to normal download mode
if i press vol[+] home power it supposed to go to recovery but goes to download mode with "could not do normal boot" message
if i press power alone it boots normally
in download mode it says
product name: sm-g901f
current binary:custom
system status:custom
reactivation lock: off
knox warranty void 0x1(4)
qualcomm secureboot: enable (csb)
RP SWREV: S1 T1 R1 A1 P1
secure download : enable
UDC start
i dont mind learning but android is pretty ugly with all the lack of documentation and standards
i learned a lot of stuff reading this forum, and will always respect people who know more than me
i just dont understand what the hell just happened, didnt encountered this before

Yea.. So follow my instructions

i am following your instructions precisely , will spend the day installing crap win7 wich i am running away from, to use with 3.10.7
in the meantime can you explain to me what happened?
i read somewhere something about odin bad usb on xp, would that pe hardware, driver, odin or usb protocol error

fixed, was flashing klte recovery, damn dozen versions of every phone
only clean rom i found was cm12 and dokdo7, both 5.1 based
waiting for network unlock, and case and im good to go
would have loved more after-market roms omni,aokp,pac, maybe 4.4
5.1 has the crap pie (position independent executable) so i cant play with perl 5.20, im stuck with 5.7
if anyone knows where to find more clean roms for g901f / kccat6xx i would be greatful
a more recent version of perl to work on 5.1 would also be nice

did you ever get this fixed?
having the same trouble with my Note4...just happened out of nowhere.

broad_st_bully said:
did you ever get this fixed?
having the same trouble with my Note4...just happened out of nowhere.
Click to expand...
Click to collapse
His last post says he fixed it...

*Detection* said:
His last post says he fixed it...
Click to expand...
Click to collapse
this phone is making me think I'm crazy...after pure hell all day yesterday and last night I wake up (after accepting the fact the phone was R.I.P.) and it turns right on and lets me set up after a factory reset.
This happened yesterday too though so I'm not gonna get all happy yet...

broad_st_bully said:
this phone is making me think I'm crazy...after pure hell all day yesterday and last night I wake up (after accepting the fact the phone was R.I.P.) and it turns right on and lets me set up after a factory reset.
This happened yesterday too though so I'm not gonna get all happy yet...
Click to expand...
Click to collapse
S5 or NOTE 4?

Could not do normal boot odin mode
I just rooted my phone so i can install a rom on my sm-n900s but i didnt realise that it was for an sm-n900.I flashed it on my phone with flashify and now all i can do is go to my custom recovery TWRP to wipe everything but still to no avail.I really do not know what to do.PLS HELP :crying::crying::crying::crying::crying:

zpimp said:
fixed, was flashing klte recovery, damn dozen versions of every phone
only clean rom i found was cm12 and dokdo7, both 5.1 based
waiting for network unlock, and case and im good to go
would have loved more after-market roms omni,aokp,pac, maybe 4.4
5.1 has the crap pie (position independent executable) so i cant play with perl 5.20, im stuck with 5.7
if anyone knows where to find more clean roms for g901f / kccat6xx i would be greatful
a more recent version of perl to work on 5.1 would also be nice
Click to expand...
Click to collapse
How did you fix it ??? if i flash a custom rom i get the same issue and my device is the same as yours. I flashed back stock rom, samsungs own recovery works well but as soon as i flash a custom recovery (twrp-3.0.0-0-klte-klte.img.tar or philz_touch_6.57.8-klte.tar.md5) i get your issue. How can i fix this and install a custom recovery ? When i install CF-Auto-Root-kccat6-kccat6xx-smg901f.tar.md5 the recovery is back but even when i flash within the os (terminal) the recovery is broken "again"
FIXED!!!! Installed CWM-based Recovery v6.0.5.1

MichelN said:
How did you fix it ??? if i flash a custom rom i get the same issue and my device is the same as yours. I flashed back stock rom, samsungs own recovery works well but as soon as i flash a custom recovery (twrp-3.0.0-0-klte-klte.img.tar or philz_touch_6.57.8-klte.tar.md5) i get your issue. How can i fix this and install a custom recovery ? When i install CF-Auto-Root-kccat6-kccat6xx-smg901f.tar.md5 the recovery is back but even when i flash within the os (terminal) the recovery is broken "again"
FIXED!!!! Installed CWM-based Recovery v6.0.5.1
Click to expand...
Click to collapse
Download stock rom and flash by odin.They are plenty of websites online.Just search for ur phone model followed by stock rom and u will find the exact rom for u to download and flash via odin.

The problem was the recovery, same as the user on page 1. See my last notes in prev. post