Database Users

I think i Messed up

guys ii really need some help.
i downloaded BTU-N9005XXUENB7-20140310153913 and flashed it via odin while in download mode. the flash was successful but now all im seeing is "recovery booting" on the phone and its just staying there?
ii was on stock rom 4.3 rooted with custom recovery before flashing the 4.4.2 file in odin. have i f****d my phone?
i did the same thing as i did last time iand it worked but im not sure whats going on here?
please can someone help me please:crying::crying::crying::crying:

Same happened to me when i used mobile Odin. The bootloader wasn't updated.
Did you use Odin 1.85? And did you tick the option update new bootloader? If not do that.
If did that then wipe cache and data reset from recovery.

kenny1991 said:
Same happened to me when i used mobile Odin. The bootloader wasn't updated.
Did you use Odin 1.85? And did you tick the option update new bootloader? If not do that.
If did that then wipe cache and data reset from recovery.
Click to expand...
Click to collapse
yeah i used the wrong version of odin. i used 1.85 now its working, but i didnt select update bootloader, how do i know if it updated the bootloader?

You know if the phone is up and running. Kitkat can't boot without new bootloader. So if the phone is working there is no issues.

kenny1991 said:
You know if the phone is up and running. Kitkat can't boot without new bootloader. So if the phone is working there is no issues.
Click to expand...
Click to collapse
last thing. im trying to install TWRP . i have the tar file from their site. i used odin 1.85 and 3 and flashed pda. odin says its done but it wont boot into TWRP it just reboots.
edit: i used mobile odin and its all good thanks for all your help

You welcome

thedan55 said:
last thing. im trying to install TWRP . i have the tar file from their site. i used odin 1.85 and 3 and flashed pda. odin says its done but it wont boot into TWRP it just reboots.
edit: i used mobile odin and its all good thanks for all your help
Click to expand...
Click to collapse
just FYI,
if you want to flash TW custom ROM, the best you use is Chenglu CWM. So far I seldom see user complain got problem during flashing with this CWM.
TWRP, some users got problem, some are not.

[Q] have i lost root forever ? help !

all.
I have an i9505 on 3 UK that has been rooted for over 6 months. I've been running the excellent TW based Echo Rom but wanted to try an ASOP rom but quickly wanted to revert.
I tried to restore my Nandroid but this failed and screwed up the phone (dont ask)so back to ODIN and i flashed back to stock 4.4.2 firmware for the UK via Sammobile (NG8)
Now back to square 1 so attempted to reroot with CF Autoroot again via ODIN. all show pass and i get the black screen on the phone with the red android logo and line stating stock recovery restored. I then used ODIN to flash Philz recovery again shown as Pass, however when i try to get into recovery i get some small white text on the bkack background that is there too briefly to read before the phone reboots as normal.
The Su superuser app is there but states the Su binary is outdated and the phone has no root access.
Ive read a few methods to get round this but they all seem to follow the same process ive tried a few times now.
The Rom for Echoe is auto root so id have thought if i could get to recovery somehow i could just flash this ?
Any one any views or have i screwed up for good ? .

You will be fine.
If you want to flash a custom rom anyway the shortest way would be to just flash the custom recovery. You don't need root for that.
Uncheck auto-reboot before you flash the recovery and it should work.

Lennyz1988 said:
You will be fine.
If you want to flash a custom rom anyway the shortest way would be to just flash the custom recovery. You don't need root for that.
Uncheck auto-reboot before you flash the recovery and it should work.
Click to expand...
Click to collapse
so i reflashed Philz recovery and unchecked auto reboot. This then gives me PASS in ODIN. I guess then i unplug and try and activate recovery - but still nothing...it just boots up normally ?

robinta said:
so i reflashed Philz recovery and unchecked auto reboot. This then gives me PASS in ODIN. I guess then i unplug and try and activate recovery - but still nothing...it just boots up normally ?
Click to expand...
Click to collapse
What is the model descriped when you are in download mode?
What is the exact version of Philz you are trying to flash?

Lennyz1988 said:
What is the model descriped when you are in download mode?
What is the exact version of Philz you are trying to flash?
Click to expand...
Click to collapse
GTI9505...(Bootloader i9505xxegng8)
Originally I tried philz_touch_5.15.8-i9505.tar.md5
and then updated to philz_touch_6.23.9-i9505.tar.md5 with no avail.

Try redownloading it. If you say that if passes, then it should just work.
If it still fails then try TWRP. Uncheck auto-reboot before flashing.

Could it be connected to me flashing a generic unlocked UK firmware on a 3 UK handset ?

That's sorted it ! Flashed CWM recovery and am now running Echoes v28.
Thanks for the help. I was really panicking for a while.
I wont be changing roms for a while but I guess if I did I won't lose root ?

[SOLVED] How do I wipe data/cache in download mode?

Hello!
I've flashed a stock ROM on my Samsung Galaxy S5 (SM-G900F) using ODIN 3.07 and now the phone is bootlooping. I guess It's because I need to wipe data and cache partitions and here's the problem.
My home button is not working, so I can't boot in recovery mode. Adb does NOT recognize my device. I'm only able to access download mode using a JIG.
So, is there any way to wipe those partitions or to be able to access recovery using ODIN?
Thanks in advance for your help!

That is a challenging situation! I'd try flashing the stock ROM once more, just on top of the one you already did using Odin and see if it boots this time.
If it didn't, see if Samsung kies would recognize your phone on download mode and get kies to flash the proper stock rom because I know kies does a full wipe before flashing automatically every time.

Yea, you shouldn't need to wipe anything if you use the correct tar in Odin, it should do it automatically. I would try again as stated above. Are you sure you have the correct tar file?

Thank you so much!!
The problem is that I was trying to flash an older firmware to use Towelroot. I've flashed the same firmware and now it's working again!
Now, I really need to root because I need virtual keys (hardware ones don't work) and i have to edit build.prop file.
What's the easiest way to root on a Lollipop firmware? I don't care about Knox and warranty void.
Also, I already tried CF-Auto Root but when the phone rebooted It gave me this message: "RECOVERY IS NOT SEANDROID ENFORCING" and it didn't start anymore, that's why I needed to flash the stock firmware again.
EDIT: Nevermind. I flashed TWRP using Odin and then I flashed SuperSU in the recovery. I've booted in the recovery using "adb reboot recovery". Thanks again!

Glad you got it working!

S4 GTI9505 flashed recovery without root help

So I accidentally flashed the recovery package through Odin to a friend's s4 gt i9505 and i get a no access error in the recovery with an android and a red triangle. Since it has a custom recovery odin doesnt detect it. My question is what should i do ? . There is literally noone that has experienced the same (noob) mistake so there is no real fix. The phone is running 4.4.2 with an official upgrade to lollipop but KNOX was tripped so I would like to fix for him without having to pay for official service.
Thanks in advance.

Odd. I have a custom recovery on my S4 and Odin detects my S4 without a problem, meaning something else is causing your connection woes. Obviously, make sure you're in download mode first (hold down the volume down, home, power keys), which wouldn't be affected by a custom recovery, and change USB ports until Odin does recognize the device. Then flash the stock ROM again to restore the S4 to working order.

Strephon Alkhalikoi said:
Odd. I have a custom recovery on my S4 and Odin detects my S4 without a problem, meaning something else is causing your connection woes. Obviously, make sure you're in download mode first (hold down the volume down, home, power keys), which wouldn't be affected by a custom recovery, and change USB ports until Odin does recognize the device. Then flash the stock ROM again to restore the S4 to working order.
Click to expand...
Click to collapse
the thing is it bypassed download mode straight into the recovery so it didnt recognize it at all. Maybe it was because it had a non rooted recovery? Anyway i rooted the phone with kingoroot which on the one hand it worked on the other hand the phone laggs like hell but it wiped the custom recovery somehow so i got samsung's download mode back flashed cf auto root but it doesnt update su binary so thats my problem now . The phone is a 4.4.2 firmware so should i Flash first lollipop and then root it or flash a recovery to install the su binary from there?

CostasV23 said:
the thing is it bypassed download mode straight into the recovery so it didnt recognize it at all. Maybe it was because it had a non rooted recovery? Anyway i rooted the phone with kingoroot which on the one hand it worked on the other hand the phone laggs like hell but it wiped the custom recovery somehow so i got samsung's download mode back flashed cf auto root but it doesnt update su binary so thats my problem now . The phone is a 4.4.2 firmware so should i Flash first lollipop and then root it or flash a recovery to install the su binary from there?
Click to expand...
Click to collapse
Based on your first post and this post I have come to the conclusion that you have absolutely no idea what you are doing. You are mixing everything up. And I mean everything.
- A non rooted recovery? What is that? It doesn't excist. A recovery has nothing to do with root.
- Because you had a custom recovery Odin doesn't detect it? Completely impossible. A custom recovery has nothing to do with Odin detecting or not detecting.
- Wiping the recovery and getting download mode back? Dude that's impossible. Download mode and recovery are two completely different things.
1. Flash Lollipop if you want Lollipop. With .pit and re-partition.
2. Perform a factory reset.
3. Flash cf-auto root.
That's all there is to it.

Lennyz1988 said:
Based on your first post and this post I have come to the conclusion that you have absolutely no idea what you are doing. You are mixing everything up. And I mean everything.
- A non rooted recovery? What is that? It doesn't excist. A recovery has nothing to do with root.
- Because you had a custom recovery Odin doesn't detect it? Completely impossible. A custom recovery has nothing to do with Odin detecting or not detecting.
- Wiping the recovery and getting download mode back? Dude that's impossible. Download mode and recovery are two completely different things.
1. Flash Lollipop if you want Lollipop. With .pit and re-partition.
2. Perform a factory reset.
3. Flash cf-auto root.
That's all there is to it.
Click to expand...
Click to collapse
What I meant was that I accidentally flashed the recovery tar.md5 file before cf-auto-root and it wasn't working . aside that I get an su binary update error is there a fix for that?

CostasV23 said:
What I meant was that I accidentally flashed the recovery tar.md5 file before cf-auto-root and it wasn't working . aside that I get an su binary update error is there a fix for that?
Click to expand...
Click to collapse
Root and recovery are two unrelated things. You don't need root for a custom recovery and you don't need a custom recovery to root.
I would start with a clean install since you used Kingoroot and cf auto-root.
Flash a stock rom with re-partition and .pit. Then only use cf auto-root.

Lennyz1988 said:
I would start with a clean install since you used Kingoroot and cf auto-root.
Flash a stock rom with re-partition and .pit. Then only use cf auto-root.
Click to expand...
Click to collapse
If I flash the official lollipop firmware via odin will it work you mean ? (Sorry for noob question ) also about that .pit I haven't found anywhere a .pit file is it necessary ?

CostasV23 said:
If I flash the official lollipop firmware via odin will it work you mean ? (Sorry for noob question ) also about that .pit I haven't found anywhere a .pit file is it necessary ?
Click to expand...
Click to collapse
You can also wipe /system and /data in TWRP and then flash Lollipop firmware.

Lennyz1988 said:
You can also wipe /system and /data in TWRP and then flash Lollipop firmware.
Click to expand...
Click to collapse
Is it obligatory i wipe the system partition because odin flash rewrites it anyway or am i wrong on this one?
Also after kingroot the recovery was wiped clean for some reason

Bro my s4 GT I9505 have stock rom v5 .0.1 UHOE3.now I need rooted and install philz touch recovery so pls proper guide and file.thanks in advance.

Philz is outdated, and certain ROMs will not install with it. Use TWRP instead. For installing, it's just like installing a stock ROM through Odin. We have guides on this in the General section.

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