Hello all!
First off I would just like to say thank you, thank you, thank you. I have been a long time lurker on these forums (since the evo) and have gotten a lot of useful information from here. Now to my issue. I have had no phone for two weeks now, and have been doing search after search. I upgraded my phone to 4.3 (it was mk2) and rooted it via motochopper. So my dumbass tried to flash a custom rom with kn0x0ut and it failed. The phone rebooted and now will boot up to the samsung custom screen. You can hear the att boot up sound but no image. I can get into odin mode and stock recovery. When I am in odin it says:
ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMC BURST MODE enabled
I have tried sideloading the stock MJ9 and MK2 files to no avail. I really hope somebody can help me, I don't know how much longer i can go without a phone. Thanks guys and Merry Christmas!!!
yea sounds like bricked you cant flash roms on 4.3 yet take it to best buy that has a samsung center and just tell them samsung sent you here because my phone all of a sudden was acting up and they will flash it back to factory for you thats what i had to do
gtj0 said:
OK, If you're stuck with an incomplete flash, here are some steps you can try to get to MJ9...
These instructions assume you started with MJ6.
First, make sure you can boot into recovery. If not, download and apply the MJ6 recovery.
recovery-mj6.tar.md5
It should apply without error. If not, report the failure.
Download and extract the following files...
mf3-emergency-part-1.tar.md5.7z
mf3-emergency-part-2.tar.md5.7z
If you don't already have it, download the mf3-mj9 update file...
update-mf3-mj9.zip
Start Odin, connect your phone and boot into Download mode.
Flash mf3-emergency-part-1.tar.md5 which contains modem.bin, NON-HLOS.bin and system.img.ext4.
The flash of system.img.ext4 WILL FAIL at the end. That's OK.
Reboot the phone back into Download mode and restart Odin.
Flash mf3-emergency-part-2.tar.md5 which contains cache.img.ext4.
The flash WILL FAIL at the end. That's OK.
The phone should now reboot to recovery by itself and apply a small update. If it fails, stop and report.
The phone should now reboot to a black screen with the pulsing notification LED.
Reboot into recovery mode and flash update-mf3-mj9.zip. I recommend sideloading instead of flashing from sdcard because the sdcard method reboots the phone whether the update was successful or not and you lose the error messages.
Reboot the phone and let it initialize.
You should now have MJ9.
Click to expand...
Click to collapse
download the above files except update-mf3-mj9.zip and replace with MF3>MK2 from this thread
http://forum.xda-developers.com/showthread.php?t=2573080
Hashcode has a Beta safesatrap for MK2 Safestrap-JFLTEATT-3.70-B01 if you want to flash anything to a rom slot or stock slot and make a backup (does not work with EXFAT formatted sd yet)
http://forum.xda-developers.com/showthread.php?t=2448925
dolph8886 said:
download the above files except update-mf3-mj9.zip and replace with MF3>MK2 from this thread
http://forum.xda-developers.com/showthread.php?t=2573080
Hashcode has a Beta safesatrap for MK2 Safestrap-JFLTEATT-3.70-B01 if you want to flash anything to a rom slot or stock slot and make a backup (does not work with EXFAT formatted sd yet)
http://forum.xda-developers.com/showthread.php?t=2448925
Click to expand...
Click to collapse
I was on MK2 using the 3.7 beta of SS when I couldn't get it to boot anymore. Tried the modified method outlined above, everything worked except after step 7, it never rebooted to recovery on it's own and installed a small update. Decided to try Kies, says it can do emergency firmware recovery but it hasn't worked yet. Any help would be appreciated as I'm not sure I can get the handset replaced since I got it at Walmart.
It may not automatically reboot into recovery, just make it.
if you do not already know this (i am not saying you don't)
holding the power button for 10? seconds will reboot phone or using the file in post below
http://forum.xda-developers.com/showpost.php?p=48621760&postcount=18
hold volume up and power the phone on to boot into stock recovery
have android sdk and files above ready
choose option to sideload update from adb
open terminal on computer and
adb sideload "update.zip"
without quotes
here are basically the same instructions just a bit different
sl1200md3 said:
Back on AT&T STOCK MK2 from a bricked TWRP'd install. I had to do the following:
1) Phone into download mode
2) Flash mf3-emergency-part-1.tar.md5 via Odin v1.85
3) Force Reboot
4) Flash mf3-emergency-part-2.tar.md5
5) Unplug phone / Reset Odin / plug phone back in
6) Flash recovery-mj6.tar.md5
7) Force Reboot in Odin using this file http://forum.xda-developers.com/showthread.php?t=1766399 Thanks kevinpc :good:
8) Manually enter recovery
9) ADB Sideload the file: update-mf3-mj9.zip found here: http://forum.xda-developers.com/showpost.php?p=47604388&postcount=152
10) ADB Sideload the file: update-MJ9-MK2.zip found here: https://docs.google.com/file/d/0B2iXrnZBB-MVYkYwNkYzU2FJaFk/edit
11) Reboot
Won't be flashing TWRP via Goo Manager again any time soon.
:good::good::good:
Click to expand...
Click to collapse
dolph8886 said:
It may not automatically reboot into recovery, just make it.
if you do not already know this (i am not saying you don't)
holding the power button for 10? seconds will reboot phone or using the file in post below
http://forum.xda-developers.com/showpost.php?p=48621760&postcount=18
hold volume up and power the phone on to boot into stock recovery
have android sdk and files above ready
choose option to sideload update from adb
open terminal on computer and
adb sideload "update.zip"
without quotes
here are basically the same instructions just a bit different
Click to expand...
Click to collapse
You sir, are amazing. What you posted was just different enough from what I had previously tried to work. I'm now booting and on MK2, thanks a million man!
FINALLY
dolph8886 said:
download the above files except update-mf3-mj9.zip and replace with MF3>MK2 from this thread
http://forum.xda-developers.com/showthread.php?t=2573080
Hashcode has a Beta safesatrap for MK2 Safestrap-JFLTEATT-3.70-B01 if you want to flash anything to a rom slot or stock slot and make a backup (does not work with EXFAT formatted sd yet)
http://forum.xda-developers.com/showthread.php?t=2448925
Click to expand...
Click to collapse
FINALLY LONG SEARCH OVER FOR THIS FIX JUST ONE QUESTION WILL THE RECOVERY FAIL AS WELL?
tonyc0642 said:
You sir, are amazing. What you posted was just different enough from what I had previously tried to work. I'm now booting and on MK2, thanks a million man!
Click to expand...
Click to collapse
hi i have the exact same problem....i dont know how to start adb on windows 7...arrgh...
Thanks to the everyone for this
It saved my ass..I put the zips on a sd and installed.Back on mk2 and rooted.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
I tried the above mentioned but after I flash the second file and reboot, it goes into kies , no recovery mode. Odin is still available. Also thanks for all the quick responses fellas yall are the best.
***UPDATE*** flashed the recovery but the sideload failed. Tried to turn it on and the Samsung lolgo came on, then went black. After a a few minutes the phone pops up on the computer and I can access the internal phone memory and the sd card.
I am really not sure, I believe that it will work if you do this process again.
No Idea if this makes any difference but, pay close attention to the process at least until the sideloading of the update.
Do not let the device attempt to boot with this firmware mismatch as this may cause issues. (This is the only conclusion I can come to as this process does work)
If the device automatically reboots then press and hold volume up to enter recovery or volume down to enter download mode.
If manual reboot or powering on then press and hold volume up or down respectively then press power until the device starts and release power button to avoid a reset.
SOLVED!!!
Thank you so much @dolph8886!!!1 You are the BEST!!! :good: :victory: :highfive:
This helped me, fixed my softbrick, hope this helps! Remember to thank the author if it works
http://forum.xda-developers.com/showthread.php?t=2621279
ok here it goes i tried to flash twrp using goo but now i have no stock recovery can someone help me please im on mk2 running 4.3 and rooted
Related
IMPORTANT: This guide is for the i9300 variant of the S3. Those with other variants - Please use this guide ONLY if you know for sure it will work for you.
For those with the Verizion S3, it was reported that you can use this guide: http://forum.xda-developers.com/showthread.php?t=1762709
The problem is that many of you may have unlocked your bootloaders, and this guide DOES NOT apply if you need to re-lock.
Right - I hope this is the correct section. I only just completely restored my S3 to factory state and I had to use so many articles over the web, half of them not even bringing me back to the original state. If you follow this, you will bring it back to a condition that will in effect recover your warranty and you'll be able to send it off. I'm also a new member(just signed up today) and I actually signed up because I wanted to post this haha.
==========================================
What this will leave you with in the end
==========================================
1. Official Firmware
2. Official Recovery
3. Binary Counter set to 0
4. Device status to "Normal"
5. Factory Settings as if you just took it out of the box.
=========================================
This will help you if
=========================================
You've soft bricked your phone but can still access recovery and want to reset
You've installed a custom recovery and want stock
You want to unroot and remove the modifications made (including a custom recovery such as CWM)
You want to reset the binary counter
THIS IS A DANGEROUS OPERATION AND COULD POTENTIALLY BRICK YOUR DEVICE. PROCEED AT YOUR OWN RISK. I AM NOT RESPONSIBLE FOR ANYTHING ON THIS THREAD AND FOR ANYTHING THAT WILL HAPPEN TO YOUR DEVICE AS A RESULT OF FOLLOWING MY GUIDE. BY FOLLOWING IT YOU ACCEPT THIS.
Process Overview
1. Reset Binary Counter
2. Flash Stock Recovery
3. Device Wipe
4. Flash Stock ROM
5. Done!
Instructions
1. Reset Binary Counter
Right so the S3 has a feature known as the binary counter - this counter is incremented everytime you flash any unnoficial software. This includes any custom ROMs, Kernels, and Recoveries. Chances are, during your rooting process you installed a custom recovery such as ClockWork Mod. This means your counter is not at 0, and your system status will be that you're running unnoficial software - WE NEED TO GET RID OF THIS.
=====================
Steps:
=====================
1.1 Turn off your phone.
1.2 Press the Home, Volume Down and Power buttons together.
1.3 Press Volume Up to continue when prompted
1.4 You will now see the binary counter will have an integer other than 0. Note this value down.
1.5 Download: TriangleAway. You can do this by going to this thread: http://forum.xda-developers.com/showthread.php?t=1494114
1.6 Copy it to your phone's memory or SD card.
1.7 Use any file browsing software to install the apk you downloaded.
1.8 Open the application and follow the notifications shown.
1.9 Find "Reset Flash Counter". The details shown should match your binary counter that you noted down earlier.
1.10 It may also say "this information cannot be retrieved" or something of the sort - in that case you can go ahead (I had to do this) and press reset flash counter. It will now boot into it's own mode. Follow the instructions to reset.
rootSU said:
Can I add that between steps 10 and 11, if you have a custom kernel or recovery, and a JellyBean bootloader - when the phone boots, the flash counter goes back up to to 1.
To remedy this, you can either:
1) After pressing the volume key in Triangle away, interrupt the boot up by pulling the battery. Check in download mode. If 0, move on to next step - otherwise, repeat
2) Flash an ICS Bootloader via ODIN first. ICS bootloaders are reset permanently once reset via Triangle away
3) Flash a stock recovery and kernel via ODIN so the flash counter doesn't increase once reset via Triangle away
4) Flip the entire process around. Flash a stock ROM first, root with CF Auto root. Run triangle way then use the superuser app itself to unroot.
Hope this helps.
Click to expand...
Click to collapse
1.11 Your counter is now reset! You can check it by repeating the first 4 steps.
2. Flash Stock Recovery
(Skip this step if you have stock recovery already)
We need to do a full wipe of the system. To do this we need to go to our recovery but OH **** we've got a custom recovery. If we go into this recovery then we'll set the binary counter back to 1 again and it'll defeat the purpose of the first step. If we, however, use a stock recovery then the counter will still stay at 0.
=====================
Steps:
=====================
Credits: http://galaxys3root.com/galaxy-s3-t...l-stock-recovery-and-update-ota-on-galaxy-s3/
2.1 We need to go back to ODIN mode (where you observed your binary counter).
2.2 Turn off your phone.
2.3 Press the Home, Volume Down and Power buttons together.
2.4 Press Volume Up to continue when prompted
2.5 Download ODIN: http://stockroms.net/file/Tools/ODIN/Odin3v185.zip (this is the version I used)
2.6 Download your StockRecovery:
Stock Recovery for International Galaxy S3 GT-i9300 (This is the one I used because I'm from the UK)
Download Stock Recovery for Galaxy S3 SGH-I717/I717M (AT&T,Canadian)
Download Stock Recovery for Galaxy S3 SCH-I535 (Verizon)
Download Stock Recovery for Galaxy S3 SGH-T999 (T-Mobile)
Download Stock Recovery for Galaxy S3 SPH-L710 (Sprint)
2.7 Run ODIN. Do not touch any of the options. Only Auto Reboot should be checked.
2.8 Plug in your phone. The first COM rectangle should be yellow (like: http://gyazo.com/ad7dcd2af17a7ff6745ded7ea91eefaf ) and ODIN should recognize the phone. If this is not the case and it's not recognizing it then you need to get drivers for your phone.
2.9 Click "PDA" and select the stock recovery file you just downloaded.
2.10 Click Start.
2.11 When complete the top left will be green.
2.12 Now you have a stock recovery!!
2.13 Unplug your phone
3. Device Wipe
3.1 Go into stock recovery by holding down Home, Volume up and Power buttons together.
3.2 When you see the samsung logo, let go and you'll see it go into custom recovery.
3.3 Scroll to device wipe using the volume keys.
3.4 Press the home key to select the option, and then select yes. Once the device is wiped it will let you know.
4. Flash Official ROM
4.1 Download your official ROM here: http://samsung-updates.com/device/?id=GT-I9300
4.2 Choose the correct ROM corresponding to your country, I chose BTU since my phone was unlocked and I'm from the UK.
Please note: it is IMPORTANT that you download the correct ROM. Dial *#1234# to find your CSC (country code) and CP number which you can match up to the ROM.
4.3 It's around 800MB so it will take a while to download.
4.4 Go to ODIN mode again by
4.5 Press the Home, Volume Down and Power buttons together.
4.6 Press Volume Up to continue when prompted.
4.7 Run ODIN on your computer and connect your phone.
4.8 When it recognizes it, check "Auto Reboot" and "F.Reset Time".
4.9 Everything else should be left unchecked.
4.10 On your computer, unzip the ROM file you downloaded. It should give you something with the extension of .tar.md5
4.11 Press "PDA" on ODIN and select this file.
4.12 Everything should be as shown here: http://gyazo.com/fea7a1c8b7a7b5bb287fb0a0c70056dc
4.13 Click Start and wait for it to do it's thing. It'll take quite a few minutes.
4.14 When it's finished, you're DONE!!!!
IMPORTANT: If when rebooting, it hangs at the samsung logo for a while then perform STEP 3 (Wipe Device) and then reboot it. Should work. If not then post here and someone may help you OR you can attempt reflashing your stock ROM again.
And that's it folks I'm not very experienced with android so I won't be able to answer questions if you have any problems, this is just the steps I devised and it worked.
Credits:
Makers of ODIN(?)
TriangleAway: http://forum.xda-developers.com/showthread.php?t=1494114
This Site: http://galaxys3root.com/galaxy-s3-t...l-stock-recovery-and-update-ota-on-galaxy-s3/
This Site: http://reviews.cnet.co.uk/mobile-phones/how-to-recover-a-bricked-samsung-galaxy-s3-50009490/
Thanks for reading, hope I helped ya out!
Tops! Should be sticky!:good:
joooe said:
Tops! Should be sticky!:good:
Click to expand...
Click to collapse
Perhaps that is a good idea, I could not find a complete guide elsewhere showing this
doovd said:
Perhaps that is a good idea, I could not find a complete guide elsewhere showing this
Click to expand...
Click to collapse
[Tut] Unroot the Galaxy SIII (for stock updates/warranty) 14 June 2012.
http://forum.xda-developers.com/showthread.php?t=1710613
Thanks for unlocking - hope you guys can make use of this. Feel free to ask any questions.
Can I add that between steps 10 and 11, if you have a custom kernel or recovery, and a JellyBean bootloader - when the phone boots, the flash counter goes back up to to 1.
To remedy this, you can either:
1) After pressing the volume key in Triangle away, interrupt the boot up by pulling the battery. Check in download mode. If 0, move on to next step - otherwise, repeat
2) Flash an ICS Bootloader via ODIN first. ICS bootloaders are reset permanently once reset via Triangle away
3) Flash a stock recovery and kernel via ODIN so the flash counter doesn't increase once reset via Triangle away
4) Flip the entire process around. Flash a stock ROM first, root with CF Auto root. Run triangle way then use the superuser app itself to unroot.
Hope this helps.
rootSU said:
Can I add that between steps 10 and 11, if you have a custom kernel or recovery, and a JellyBean bootloader - when the phone boots, the flash counter goes back up to to 1.
To remedy this, you can either:
1) After pressing the volume key in Triangle away, interrupt the boot up by pulling the battery. Check in download mode. If 0, move on to next step - otherwise, repeat
2) Flash an ICS Bootloader via ODIN first. ICS bootloaders are reset permanently once reset via Triangle away
3) Flash a stock recovery and kernel via ODIN so the flash counter doesn't increase once reset via Triangle away
4) Flip the entire process around. Flash a stock ROM first, root with CF Auto root. Run triangle way then use the superuser app itself to unroot.
Hope this helps.
Click to expand...
Click to collapse
Thanks a lot mate, will add it to the original post!
Can you confirm this procedure?
1)flash stock firmware with odin (for example MC2 4.1.2)
2) root + recovery
3)downgrade to XXALE8 bootloader
4) triangle away
5)another flash of stock firmware to uninstall recovery e root
It is the correct procedure?
I read about some issue in the 5) point (fail of odin in sboot.bin).....can I flash another time the stock firmware over the old bootloader?
Stuck
Thanks for the guide!
I'm having issues with step
2.10 Click Start.
When i get to this point, the Message window just hangs at " <ID:0/004> Get PIT for mapping.."
any clue whats going on, and/or how to fix?
EDIT: I'm using Verizon-SCH-I535 Stock Recovery.tar
Mogrix said:
Thanks for the guide!
I'm having issues with step
2.10 Click Start.
When i get to this point, the Message window just hangs at " <ID:0/004> Get PIT for mapping.."
any clue whats going on, and/or how to fix?
EDIT: I'm using Verizon-SCH-I535 Stock Recovery.tar
Click to expand...
Click to collapse
WRONG forum this is I9300 forum or you are trying to flash wrong phone to a I9300 .
jje
kenzolo said:
Can you confirm this procedure?
1)flash stock firmware with odin (for example MC2 4.1.2)
2) root + recovery
3)downgrade to XXALE8 bootloader
4) triangle away
5)another flash of stock firmware to uninstall recovery e root
It is the correct procedure?
I read about some issue in the 5) point (fail of odin in sboot.bin).....can I flash another time the stock firmware over the old bootloader?
Click to expand...
Click to collapse
no one
kenzolo said:
no one
Click to expand...
Click to collapse
Probably to stay on the safe side bring it back to the stock bootloader first?
OP if the original post is to be of use then it needs to be locked .
Alternative is it will just turn into a question thread that has nothing to with the original guide .
jje
i figured out a way to restore full stock
i figured it by my self, thinking, what if i boot into fastboot, will it increase binary counter? it does not! so...
1. Reset binary counter using Triangle Away.
2. Hard restart your phone ( "-" and power for 8 seconds) and instantly when it happens hold key combination for download mode ( "-" and home and power).
3. Flash stock firmware (after that counter = 0 will not be increased).
4. Factory default (required to clear "modified" status in system settings).
5. Done! Full and clean stock
Download mode *
Sent from my GT-I9300 using Tapatalk 2
JJEgan said:
WRONG forum this is I9300 forum or you are trying to flash wrong phone to a I9300 .
jje
Click to expand...
Click to collapse
This guide has Verizon instructions as well for the I535
Mogrix said:
This guide has Verizon instructions as well for the I535
Click to expand...
Click to collapse
Yes it does but that's a bad idea. We're all i9300 users so our advice could lead to danger.
OP, please repost separately in each device forum so when we give advice, we know we're giving right advice.
Sent from my GT-I9300 using Tapatalk 2
Yep that's what i see non I9300 users find somehow this thread follow the instructions then from this forum decide to flash a rom that is not for their phone .
Foolish though maybe but enough Verizon owners have already done just that .
jje
JJEgan said:
Yep that's what i see non I9300 users find somehow this thread follow the instructions then from this forum decide to flash a rom that is not for their phone .
Foolish though maybe but enough Verizon owners have already done just that .
jje
Click to expand...
Click to collapse
I'll post an explicit message at the top regarding this, thank you for your advice, and you too rootSU.
Added to http://forum.xda-developers.com/showthread.php?t=2148708
Hi,
I've tried several times flashing Clockworkmod 6.0.3.3 and other versions of Clockworkmod for S4 I9505, but after flashing it using Odin 1.85, Odin says ok, and reboot my phone, but after I turn the phone off, and try to start phone into recovery mode using power, volume up and home button at the same time, my phone doesn't find anything to use, so it starts in regular recovery mode (Default as from Samsung).
Anyone have an idea why Clockworkmod won't work on the phone, even when Odin says ok on flashing?
I've made sure that I downloaded the correct file for my phone.
My phone is a euro version, that shouldn't matter?
King Canute said:
Hi,
I've tried several times flashing Clockworkmod 6.0.3.3 and other versions of Clockworkmod for S4 I9505, but after flashing it using Odin 1.85, Odin says ok, and reboot my phone, but after I turn the phone off, and try to start phone into recovery mode using power, volume up and home button at the same time, my phone doesn't find anything to use, so it starts in regular recovery mode (Default as from Samsung).
Anyone have an idea why Clockworkmod won't work on the phone, even when Odin says ok on flashing?
I've made sure that I downloaded the correct file for my phone.
My phone is a euro version, that shouldn't matter?
Click to expand...
Click to collapse
Download the attached link. You find a folder of s4 root. Odin 1.85 and Cwm file and a rooting file(only if you need root)
An odin 1.85 specialy for gti 9505. Big thanks to chainfire.
Turn your phone in downloadmode. Connect your Phone to your pc. Open odin and select pda and select the file i9505-cwm-recovery -6.0.3.2-4
Start.
After the phone is rebooting, turn your phone off.
Then volume up,home button and powerbutton at the same time. When you see on top a blue text" recovery booting" let go of the 3 buttons and it boots in cwm. This should do the trick.
http://db.tt/BmvKeopK
Regards
Verstuurd van mijn GT-I9505 met Tapatalk
astraopcuser said:
Download the attached link. You find a folder of s4 root. Odin 1.85 and Cwm file and a rooting file(only if you need root)
An odin 1.85 specialy for gti 9505. Big thanks to chainfire.
Turn your phone in downloadmode. Connect your Phone to your pc. Open odin and select pda and select the file i9505-cwm-recovery -6.0.3.2-4
Start.
After the phone is rebooting, turn your phone off.
Then volume up,home button and powerbutton at the same time. When you see on top a blue text" recovery booting" let go of the 3 buttons and it boots in cwm. This should do the trick.
http://db.tt/BmvKeopK
Regards
Verstuurd van mijn GT-I9505 met Tapatalk
Click to expand...
Click to collapse
Thanks for trying to help me out, but still I got no luck with this,
After the flashing, when I try to go into recovery mode I can see that the phone tries to install or update something, but a sec after I get some sort of fail message and I'm back to default recovery mode.
I can't understand what seems to be the problem.
Could it be that my phone might be locked to a carrier?
King Canute said:
Thanks for trying to help me out, but still I got no luck with this,
After the flashing, when I try to go into recovery mode I can see that the phone tries to install or update something, but a sec after I get some sort of fail message and I'm back to default recovery mode.
I can't understand what seems to be the problem.
Could it be that my phone might be locked to a carrier?
Click to expand...
Click to collapse
Is your device rooted yet?
I first rooted my phone and then i flashed cwm recovery via odin 1.85. All in the file you've downloaded.
astraopcuser said:
Is your device rooted yet?
I first rooted my phone and then i flashed cwm recovery via odin 1.85. All in the file you've downloaded.
Click to expand...
Click to collapse
Do I have to root the phone to make the clockworkmod work?
King Canute said:
Do I have to root the phone to make the clockworkmod work?
Click to expand...
Click to collapse
you must first root your phone.:good:
---------- Post added at 10:54 PM ---------- Previous post was at 10:36 PM ----------
astraopcuser said:
you must first root your phone.:good:
Click to expand...
Click to collapse
for the gti 9505 lte is a little bit diverent at this time.
first flash the cf autorootjflte.... via odin. phone in downloadmode, select pda,select cf autoroot jfte... hit start. phone reboots, you see an red/orange android droid then its rebooting
after that turn off your phone . phone in downloadmode, open odin, select pda, select cwm 6.0.3.2-4, hit start
Your phone is rooted with cwm.
What rubbish!
You DO NOT need to root your phone to install a custom recovery. Are you sure you have i9505??
Download the latest Philz CWM recovery in .tar format and flash this in Odin 1.85.
I've done this on 6 different S4s and NEVER had an issue.
Seems strange that your having problems dude.
Obagleyfreer said:
What rubbish!
You DO NOT need to root your phone to install a custom recovery. Are you sure you have i9505??
Download the latest Philz CWM recovery in .tar format and flash this in Odin 1.85.
I've done this on 6 different S4s and NEVER had an issue.
Seems strange that your having problems dude.
Click to expand...
Click to collapse
How rubbish..... its goes that way to get a custom cwm on the gti9505.
He ask cwm, not philz recovery.
You can say next time ....theres another way to get it work.
I only trying to help
Verstuurd van mijn GT-I9505 met Tapatalk
This version of CWM work perfect and supports exFat (64GB SD Cards).
You don't need root.
Flash as PDA using Odin PC.
http://forum.xda-developers.com/showthread.php?t=2279579
Obagleyfreer said:
What rubbish!
You DO NOT need to root your phone to install a custom recovery. Are you sure you have i9505??
Download the latest Philz CWM recovery in .tar format and flash this in Odin 1.85.
I've done this on 6 different S4s and NEVER had an issue.
Seems strange that your having problems dude.
Click to expand...
Click to collapse
I'm 100% sure that my phone is a 9505, it's the only version sold in Norway.
Mittaa said:
This version of CWM work perfect and supports exFat (64GB SD Cards).
You don't need root.
Flash as PDA using Odin PC.
http://forum.xda-developers.com/showthread.php?t=2279579
Click to expand...
Click to collapse
It's this version I'm trying to flash with no luck, and I can't understand why it's not working.
Maybe I have to do a factory reset, or flash a complete new stock ROM?
King Canute said:
It's this version I'm trying to flash with no luck, and I can't understand why it's not working.
Maybe I have to do a factory reset, or flash a complete new stock ROM?
Click to expand...
Click to collapse
Do you have a proper USB connection between Odin PC and your phone?
Try another USB cable or/and another USB port ...
Did you remember to kill all KIES processes running in background?
CTRL, ALT, DELETE running processes ...
King Canute said:
Hi,
I've tried several times flashing Clockworkmod 6.0.3.3 and other versions of Clockworkmod for S4 I9505, but after flashing it using Odin 1.85, Odin says ok, and reboot my phone, but after I turn the phone off, and try to start phone into recovery mode using power, volume up and home button at the same time, my phone doesn't find anything to use, so it starts in regular recovery mode (Default as from Samsung).
Anyone have an idea why Clockworkmod won't work on the phone, even when Odin says ok on flashing?
I've made sure that I downloaded the correct file for my phone.
My phone is a euro version, that shouldn't matter?
Click to expand...
Click to collapse
in some stock firmwares, when you boot the phone, the stock recovery is re-writing over the flashed custom one:
root your phone, and with a root explorer go to system, delete "recovery-from-boot.p" or rename it to "recovery-from-boot.p.bak"
then go to system/etc, delete this file: "install-recovery.sh" or rename it to "install-recovery.sh.bak.
now you can flash your custom recovery.
Mittaa said:
Do you have a proper USB connection between Odin PC and your phone?
Try another USB cable or/and another USB port ...
Did you remember to kill all KIES processes running in background?
CTRL, ALT, DELETE running processes ...
Click to expand...
Click to collapse
I'm using an Samsung retail cable from the S2, but I did try with the S4 retail cable aswell, but still no luck. The flashing goes ok in Odin, so I doubt the cable is the problem. And Kies isn't running in the background at all. Even changed USB port just to be sure testing all the options.
samersh72 said:
in some stock firmwares, when you boot the phone, the stock recovery is re-writing over the flashed custom one:
root your phone, and with a root explorer go to system, delete "recovery-from-boot.p" or rename it to "recovery-from-boot.p.bak"
then go to system/etc, delete this file: "install-recovery.sh" or rename it to "install-recovery.sh.bak.
now you can flash your custom recovery.
Click to expand...
Click to collapse
Ok, so I might have to root my phone and try this out then.. I was hoping to avoid rooting for now.
And the way to root is done using Odin as described in an earlier post?
Will it be possible to reset the counter later on if I need to go back to stock ROM if the phone should need to sendt to service etc? I know it is possible to reset the counter on S3.
King Canute said:
Ok, so I might have to root my phone and try this out then.. I was hoping to avoid rooting for now.
And the way to root is done using Odin as described in an earlier post?
Will it be possible to reset the counter later on if I need to go back to stock ROM if the phone should need to sendt to service etc? I know it is possible to reset the counter on S3.
Click to expand...
Click to collapse
if you want to be sure, flash custom recovery, do not check "auto-reboot" or when it says "pass" unplug and take off the battery, then reinsert it, boot straight to recovery so you should see the custom recovery. but once you reboot the phone the stock recovery will be back .
any way, you can root in any method you want.
why you want to flash custom recovery without rooting??
once you flashed anything unofficial with odin, the counter is triggered.
yes you can reset it with triangle away.
samersh72 said:
if you want to be sure, flash custom recovery, do not check "auto-reboot" or when it says "pass" unplug and take off the battery, then reinsert it, boot straight to recovery so you should see the custom recovery. but once you reboot the phone the stock recovery will be back .
any way, you can root in any method you want.
why you want to flash custom recovery without rooting??
once you flashed anything unofficial with odin, the counter is triggered.
yes you can reset it with triangle away.
Click to expand...
Click to collapse
Ok I tried to flash the clockworkmod without checking the auto-reboot and it worked like you said.
The reason I don't want to root the phone is, because I actually don't need it, never had any use of it on other phones.
Ok then I have to root it like you said to make i work properly.
King Canute said:
Ok I tried to flash the clockworkmod without checking the auto-reboot and it worked like you said.
The reason I don't want to root the phone is, because I actually don't need it, never had any use of it on other phones.
Ok then I have to root it like you said to make i work properly.
Click to expand...
Click to collapse
hmmm, so why you need cwm?
EDIT: usually these 2 files (that reflash stock recovery) come with some OTA update. So if you dont want to root, you can flash a stock firmware with odin (those 2 files are not included) in order to flash custom recovery without rooting.
any way, when you flashed custom recovery, your binary counter is triggered. so you need triangle away to reset it for warranty ====> you need root access!
samersh72 said:
hmmm, so why you need cwm?
EDIT: usually these 2 files (that reflash stock recovery) come with some OTA update. So if you dont want to root, you can flash a stock firmware with odin (those 2 files are not included) in order to flash custom recovery without rooting.
any way, when you flashed custom recovery, your binary counter is triggered. so you need triangle away to reset it for warranty ====> you need root access!
Click to expand...
Click to collapse
I was thinking about installing Cyanogenmod ROM or maybe later Google Android 4.3.
So now I need to root the phone.
samersh72 said:
hmmm, so why you need cwm?
EDIT: usually these 2 files (that reflash stock recovery) come with some OTA update. So if you dont want to root, you can flash a stock firmware with odin (those 2 files are not included) in order to flash custom recovery without rooting.
any way, when you flashed custom recovery, your binary counter is triggered. so you need triangle away to reset it for warranty ====> you need root access!
Click to expand...
Click to collapse
Triangle Away wan't work if you have custom kernel OR recovery !
Mittaa said:
Triangle Away wan't work if you have custom kernel OR recovery !
Click to expand...
Click to collapse
yes i know and he supposed to read or already red TA thread to know that
So I've been running a rooted Note 3 for a while. When the Note 3 Kitkat update came out, I updated it via Odin as OTA update was not available since I was rooted.
All the posts I read had mentioned that updating to 4.4.2 from 4.3 would erase all my data but after updating via odin all my data was in place. I had only lost root which I rooted again though CF Auto Root.
The problem now is that when I try to install CWM (via Odin) or TWRP (via Goo or Odin), it goes through the installation but then the phone goes into a boot loop of sorts..It's NOT the normal boot loop which gets stuck on the Samsung logo.
What happens is that the phone vibrates twice (with a 1 sec interval in between), then the Samsung Note 3 N-9005 screen appears with "Booting Recovery..." on the top left and within a sec it goes blank and then back to 2 vibrates and the screen come on to show Samsung Note 3 N-9005.
The only way I found to fix this was a battery pull and then turning on the device holding the power, home and down vol key to boot into recovery and then flashing CF Auto Root again.
I don't know why am I not able to install any of these recoveries. I've made sure I try to install the latest versions of them which are Kitkat compatible.
Anyone else with this problem or a solution?
Can a Cache and data wipe fix this? But the problem again being I won't be able to backup my ROM since i can't get these recoveries to install!
There is a script in official firmware that checks for official recovery and if it finds a custom one it tries to overwrite with official one. If i remember correct it's called install-recovery. sh
PhilZ recovery handles it automatically.
It's impossibe to flash anything other than the leaked 4.4.2 stock because you flashed your bootloader to kitkat, no you MUST stay on sammy 4.4.2 till the devs found a solution for this. Thats why you have to read carefully be4 you flash.
silentvisitor said:
There is a script in official firmware that checks for official recovery and if it finds a custom one it tries to overwrite with official one. If i remember correct it's called install-recovery. sh
PhilZ recovery handles it automatically.
Click to expand...
Click to collapse
No luck!
I tried PhilZ recovery from the below link.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/hltexx
What are my other options?
sid8907 said:
No luck!
I tried PhilZ recovery from the below link.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/hltexx
What are my other options?
Click to expand...
Click to collapse
This one seems to be the only one working with 4.4.2 right now.
Possible solution
The way I can suggest is to create a little update.zip file with little updater-script to remove install-recovery.sh file from device (just one line needed).
Ok, I found a zip which I am attaching below. You(or anyone) may review the script before flashing.
Place this on your external (or internal) sdcard.
In ODIN don't check Auto reboot
Flash Recovery. Remove phone when it says PASS.
Remove battery. Start in Recovery mode by pressing buttons.
You should now be in new Recovery.
Flash that zip file.
Reboot.
You should be good.
The Auto Reboot for some reason is faded out. Tried different versions of Odin and also tried to open it with the phone connected/disconnected.
I am out of ideas.
I would suggest you to wait for someone to come up with working solution. Being too adventurous with ODIN could brick your device.
sid8907 said:
The Auto Reboot for some reason is faded out. Tried different versions of Odin and also tried to open it with the phone connected/disconnected.
Click to expand...
Click to collapse
Clear out all your ODIN caches etc, delete all files and keep 1.85.
Flash this (only working recovery on 4.4.2) via PDA in ODIN, If it doesn't reboot auto after saying PASS or RESET.. just turn phone off, reboot into recovery and it'll be fine.
EDIT: Just re-read, Re flash your Stock 4.4.2 (Use XEO not the leaked one!) and then start again
Thanks!
Maybe a little off topic, but is there a way to install CM11 on Stock 4.4.2 on the Note 3?
I've been reading Samsung is out with a new bootloader so there is no way round this?
radicalisto said:
Clear out all your ODIN caches etc, delete all files and keep 1.85.
Flash this (only working recovery on 4.4.2) via PDA in ODIN, If it doesn't reboot auto after saying PASS or RESET.. just turn phone off, reboot into recovery and it'll be fine.
EDIT: Just re-read, Re flash your Stock 4.4.2 (Use XEO not the leaked one!) and then start again
Click to expand...
Click to collapse
Thanks!!
sid8907 said:
Thanks!
Maybe a little off topic, but is there a way to install CM11 on Stock 4.4.2 on the Note 3?
I've been reading Samsung is out with a new bootloader so there is no way round this?
Click to expand...
Click to collapse
You may have to do a little reading but I believe CM11 is now working on the KK bootloader...
sid8907 said:
So I've been running a rooted Note 3 for a while. When the Note 3 Kitkat update came out, I updated it via Odin as OTA update was not available since I was rooted.
All the posts I read had mentioned that updating to 4.4.2 from 4.3 would erase all my data but after updating via odin all my data was in place. I had only lost root which I rooted again though CF Auto Root.
The problem now is that when I try to install CWM (via Odin) or TWRP (via Goo or Odin), it goes through the installation but then the phone goes into a boot loop of sorts..It's NOT the normal boot loop which gets stuck on the Samsung logo.
What happens is that the phone vibrates twice (with a 1 sec interval in between), then the Samsung Note 3 N-9005 screen appears with "Booting Recovery..." on the top left and within a sec it goes blank and then back to 2 vibrates and the screen come on to show Samsung Note 3 N-9005.
The only way I found to fix this was a battery pull and then turning on the device holding the power, home and down vol key to boot into recovery and then flashing CF Auto Root again.
I don't know why am I not able to install any of these recoveries. I've made sure I try to install the latest versions of them which are Kitkat compatible.
Anyone else with this problem or a solution?
Can a Cache and data wipe fix this? But the problem again being I won't be able to backup my ROM since i can't get these recoveries to install!
Click to expand...
Click to collapse
here's the link for twrp for ya'll http://forum.xda-developers.com/showpost.php?p=50333147&postcount=398
sid8907 said:
So I've been running a rooted Note 3 for a while. When the Note 3 Kitkat update came out, I updated it via Odin as OTA update was not available since I was rooted.
All the posts I read had mentioned that updating to 4.4.2 from 4.3 would erase all my data but after updating via odin all my data was in place. I had only lost root which I rooted again though CF Auto Root.
The problem now is that when I try to install CWM (via Odin) or TWRP (via Goo or Odin), it goes through the installation but then the phone goes into a boot loop of sorts..It's NOT the normal boot loop which gets stuck on the Samsung logo.
What happens is that the phone vibrates twice (with a 1 sec interval in between), then the Samsung Note 3 N-9005 screen appears with "Booting Recovery..." on the top left and within a sec it goes blank and then back to 2 vibrates and the screen come on to show Samsung Note 3 N-9005.
The only way I found to fix this was a battery pull and then turning on the device holding the power, home and down vol key to boot into recovery and then flashing CF Auto Root again.
I don't know why am I not able to install any of these recoveries. I've made sure I try to install the latest versions of them which are Kitkat compatible.
Anyone else with this problem or a solution?
Can a Cache and data wipe fix this? But the problem again being I won't be able to backup my ROM since i can't get these recoveries to install!
Click to expand...
Click to collapse
jp.26 said:
here's the link for twrp for ya'll http://forum.xda-developers.com/showpost.php?p=50333147&postcount=398
Click to expand...
Click to collapse
so.... yeah i just updated my bootloader to 4.4.2 and this drove me literally insane. ive been working on it for 4 hours now. i encountered so many problems with installing the bootloader. exact same problem as SID8907. i gotta tell you tho.... you worked some magic my friend. i tried almost everything. then i came across your link. i was like why not? so i flashed the img in odin..... anddddd :drumroll pleaseeeeee:: IT WORKED. ahhh....... so much frustration and the problem is solved!!! thank you so much JP.26 :good::laugh:
is there any word on how to fix this been looking for hours tmobile note beast dont want to put any roots down on my phone before i find a way to flash cm or a non bloated note rom would be nice.
I'll that I've managed is to root and flash twrp I found a way to turn cwm recovery into a tar file and flash through odin. But i just get into a boot loop with cwm due to the boot loader I presume but tarp works fine I just can't flash cm11. I get boot loop every time
Sent from my SM-N900T using XDA Premium 4 mobile app
im sorry but im confused here... does this all simply mean that there is not yet a working cwm for 4.4.2 yet? and that while we can root, there is no working recovery for this version?
I'm not sure myself tarp works but I can't flash cm11
Sent from my SM-N900T using Tapatalk
Phillz cwm Dev edition I think that's the name works its a themed touch cwm. This works great but still can't flash cm so gayyyy
Sent from my SM-N900T using Tapatalk
I was wondering what happened to the cmw too.
The modded cmw by Chenglu is the only one working that I know of.
Link to thread: http://forum.xda-developers.com/showthread.php?t=2454079
after I had succesfully rooted my phone, I wanted to install a custom rom.
I am sure I did something wrong ofcource otherwise I wouldn't be here.
#1 Battery in
#2 power on
#3 vibrate
#4 screen on RECOVERY BOOTING
Recovery is NOT SEANDROID ENFORCING
Set Warrenty Bit : recovery
Samsung
GALAXY Note3
SM-N9005
#5 screen off--> reboot -->goto #3
how to brake in the loop so I can use odin ( or whatever ) to install (at least) a normal boot again?
Which custom recovery did you flashed Twrp or Cwm?
Sent from my SM-N900W8 using xda app-developers ap
fwberg said:
after I had succesfully rooted my phone, I wanted to install a custom rom.
I am sure I did something wrong ofcource otherwise I wouldn't be here.
#1 Battery in
#2 power on
#3 vibrate
#4 screen on RECOVERY BOOTING
Recovery is NOT SEANDROID ENFORCING
Set Warrenty Bit : recovery
Samsung
GALAXY Note3
SM-N9005
#5 screen off--> reboot -->goto #3
how to brake in the loop so I can use odin ( or whatever ) to install (at least) a normal boot again?
Click to expand...
Click to collapse
You installed a 4.3 recovery on a 4.4 phone.
Most likely you downloaded the TWRP on the main page and did not download the latest 4.4 compatible one.
Please flash this in Download Mode: http://techerrata.com/bigbiff/hlte-recovery.img.tar
To get into Download Mode, remove the battery, wait a few minutes then put it back, Hold the Download Mode Combination then it would boot directly into Download Mode.
hey nicho, thank you very much
so that was the trick. REMOVE THE BATTERY --> PRESS THE DOWNLOAD KEYS AND HOLD THEM --> THEN ENTER THE BATTERY BACK.
it costed me the whole day yesterday searching for a solution.
at least now I can continue to install a new rom
Thanks man
TWRP
during twrp it told me, there was a newer one. 2.x.x.9
so stupid me, if I had sticked to the plan, nothing would happend.
I used twrp b4 some days ago, for my samsung note 10.1 (2014) without trubbles,
I guess, I overread something
but I'm happy it is all fixed now.
thx for show ur interest
greetz, fred
thank you
nicholaschum said:
You installed a 4.3 recovery on a 4.4 phone.
Most likely you downloaded the TWRP on the main page and did not download the latest 4.4 compatible one.
Please flash this in Download Mode: techerrata.com/bigbiff/hlte-recovery.img.tar
To get into Download Mode, remove the battery, wait a few minutes then put it back, Hold the Download Mode Combination then it would boot directly into Download Mode.
Click to expand...
Click to collapse
this solved my recovery problem, i clicked thank you!!!
nicholaschum said:
You installed a 4.3 recovery on a 4.4 phone.
Most likely you downloaded the TWRP on the main page and did not download the latest 4.4 compatible one.
Please flash this in Download Mode: http://techerrata.com/bigbiff/hlte-recovery.img.tar
To get into Download Mode, remove the battery, wait a few minutes then put it back, Hold the Download Mode Combination then it would boot directly into Download Mode.
Click to expand...
Click to collapse
You just saved my phone i readed so much almost one week 12hours without stop before i try custom recovery,rom and so on.
But well since i decided that im ready to, and first thing i tried to do was custom recovery wich leaded to this problam Now im afraid to enter revovery mode xD
Idiots
You're really the dumbest person I've ever seen in my life. See if this is solution to some kind of problem your beast
Worked for me
Thank you.
remove the battery then press download buttons keep them pressed and put the battery back. choose volume down to continue....
Solution To Loop SM-N900P
I am new to XDA and have only been with android for 6 months but i figure this will help new comers to this issue. Power+Volume Down+Home at the same time to enter download mode. Flash CWM via ODIN. This should work to fix the loop. I found out the hard way but it only took me an hour. I am not sure if this will work if you have not already rooted your phone but it should (since this is the major step in rooting). I believe i deleted my CWM file (accidentally) when i was trying to clear space for my recovery with ROM Manager. Be sure to download the Samsung drivers if you had not already done so during the rooting process.
Hope this helps.
Gives me same error message
But after that it boots into recovery.
Should I proceed installing custom rom or is there anything else to be taken care of
Thanks!
Thank you very much,you save me a lot of trouble.
hey_joe said:
Which custom recovery did you flashed Twrp or Cwm?
Sent from my SM-N900W8 using xda app-developers ap
Click to expand...
Click to collapse
hey joe im getting the same problem but im using the note 3 SM-N900W8 and I flash the CWM straight from the app and not using odin. My phone is already rooted using towelroot
billygun118 said:
hey joe im getting the same problem but im using the note 3 SM-N900W8 and I flash the CWM straight from the app and not using odin. My phone is already rooted using towelroot
Click to expand...
Click to collapse
Which android os do you have on your phone and which cwm version did you flashed?
hey_joe said:
Which android os do you have on your phone and which cwm version did you flashed?
Click to expand...
Click to collapse
im using version 4.4.2 jellybean. The rom manager is v5. 5.3.7/ current recovery 6.0.4.6
billygun118 said:
im using version 4.4.2 jellybean. The rom manager is v5. 5.3.7/ current recovery 6.0.4.6
Click to expand...
Click to collapse
Based on my experience, using rom manager to flash recovery always results in a problem. I suggest you use odin to flash this in download mode.
Btw, 4.4.2 is Kitkat
hey_joe said:
Based on my experience, using rom manager to flash recovery always results in a problem. I suggest you use odin to flash this in download mode.
Btw, 4.4.2 is Kitkat
Click to expand...
Click to collapse
should I root my phone first using cf-root. Then flash the cwm recovery. What happens if I get stuck in a bootloop after flashing the recovery
billygun118 said:
should I root my phone first using cf-root. Then flash the cwm recovery. What happens if I get stuck in a bootloop after flashing the recovery
Click to expand...
Click to collapse
The way I did this is, first install the cwm recovery then flash cf-root after. You can always use odin to flash back the original firmware.
hey_joe said:
The way I did this is, first install the cwm recovery then flash cf-root after. You can always use odin to flash back the original firmware.
Click to expand...
Click to collapse
so there is nothing else I have to do before flashing the recovery?
what boxes should be checkmarked in odin
billygun118 said:
so there is nothing else I have to do before flashing the recovery?
what boxes should be checkmarked in odin
Click to expand...
Click to collapse
Just make sure reactivation lock is off.
When you first start odin, F.Reset Time and Auto Reboot are ticked off so let them be and make sure only those are checked and nothing else.
You probably know this but just to make sure, load the recovery on the AP slot before hitting start.
hello guys,
i bought a used galaxy s5 from someone running Poland Android lollipop 5.0 and it shows the model as SM-G900F When i try to root it with CF-Auto-Root-klte-kltedx-smg900f It gets stuck on the boot screen saying
"1. RECOVERY BOOTING (in blue),
2. RECOVERY IS NOT SEANDROID ENFORCING (red)
3. Set Warranty Bit: recovery (yellow)"
i googled alot and flashed Phillz recovery which removed the error above but when i go to recovery its the stock recovery? .... I cant install twrp-2.8.7.0-klte.img.tar Either because after flashing it when i go to recovery its stock recovery again. Activation lock is off, SE for Android status is "enforing" does this mean this phone has a locked bootloader? Maybe this phone was on At&T, Sprint or Verizon and the last owner flashed 900f firmware on it to make it look carrier free but it maybe a carrier phoone? Please help me i am very very frustrated right now. i dont even know what recovery is seandroid enforcing means.....:crying::crying::crying:
dork997 said:
hello guys,
i bought a used galaxy s5 from someone running Poland Android lollipop 5.0 and it shows the model as SM-G900F When i try to root it with CF-Auto-Root-klte-kltedx-smg900f It gets stuck on the boot screen saying
"1. RECOVERY BOOTING (in blue),
2. RECOVERY IS NOT SEANDROID ENFORCING (red)
3. Set Warranty Bit: recovery (yellow)"
i googled alot and flashed Phillz recovery which removed the error above but when i go to recovery its the stock recovery? .... I cant install twrp-2.8.7.0-klte.img.tar Either because after flashing it when i go to recovery its stock recovery again. Activation lock is off, SE for Android status is "enforing" does this mean this phone has a locked bootloader? Maybe this phone was on At&T, Sprint or Verizon and the last owner flashed 900f firmware on it to make it look carrier free but it maybe a carrier phoone? Please help me i am very very frustrated right now. i dont even know what recovery is seandroid enforcing means.....:crying::crying::crying:
Click to expand...
Click to collapse
Akalsemann said:
Ok guys, try this.
1. Download philz kernel that matches your modem number. I think philz_touch_6.26.6-klte.tar.md5 works good.
2. Put it in ODIN on PDA/AP
3. Uncheck "Auto Reboot" and make sure Re-Partition is NOT CHECKED (keep F. Reset time)
4. Flash
5. It will say RESET on Odin and nothing further when it is done so just wait 2-3 minutes when RESET appears to be entirely sure that the procedure is done.
6. Pull out phones battery.
7. Put it back in and now go into Recovery directly (Vol up+home+power)
8. ???
9. Profit
Hopefully this might work, i think i did the same
Click to expand...
Click to collapse
Try that
Akalsemann said:
Try that
Click to expand...
Click to collapse
Kindly note that i am able to boot fine now, but the recovery wont stick and whenever i try to root this seandroid error happens
Did u do the following steps correctly
it should work bro
Been there
done the same process
thanx again Akalsemann
vinura kithmal said:
Did u do the following steps correctly
it should work bro
Been there
done the same process
thanx again Akalsemann
Click to expand...
Click to collapse
yes i entered philz recovery > selected format to install new rom > now stuck on samsung logo maybe it removed rom files. Now downloading flash roms from sammobile. Dont know if it will let me root it or not. can u please explain what this error is and why is it caused?
dork997 said:
Kindly note that i am able to boot fine now, but the recovery wont stick and whenever i try to root this seandroid error happens
Click to expand...
Click to collapse
You need to just boot into download mode (voldown+home+power) then push volup to enter download mode
Use Odin to flash trwp 2.8.6.0 tar file in AP spot
Download a pre rooted rom of your choice for g900f
Place on sd card
Reboot to twrp by holding volup+home+power immediately during start of boot
Flash the rom you just downloaded
Now you'll be rooted
(That's what I did in order to get my phone rooted after installing the newest stock lollipop ota)
Sent from my SM-G900F using Tapatalk
dork997 said:
yes i entered philz recovery > selected format to install new rom > now stuck on samsung logo maybe it removed rom files. Now downloading flash roms from sammobile. Dont know if it will let me root it or not. can u please explain what this error is and why is it caused?
Click to expand...
Click to collapse
Common bro
u haven't rooted your device,
u have to flash the supersu zip to get the root access
http://download.chainfire.eu/supersu
first download this file and place it in your device storage,once u pull the battry off and put it back in go straightly to the recovery
select install zip and flash the supersu.zip
then reboot it,after the first boot then go to the recovery and
install your custom rom
Swimguy14 said:
You need to just boot into download mode (voldown+home+power) then push volup to enter download mode
Use Odin to flash trwp 2.8.6.0 tar file in AP spot
Download a pre rooted rom of your choice for g900f
Place on sd card
Reboot to twrp by holding volup+home+power immediately during start of boot
Flash the rom you just downloaded
Now you'll be rooted
(That's what I did in order to get my phone rooted after installing the newest stock lollipop ota)
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
vinura kithmal said:
Common bro
u haven't rooted your device,
u have to flash the supersu zip to get the root access
http://download.chainfire.eu/supersu
first download this file and place it in your device storage,once u pull the battry off and put it back in go straightly to the recovery
select install zip and flash the supersu.zip
then reboot it,after the first boot then go to the recovery and
install your custom rom
Click to expand...
Click to collapse
I followed instructions given earlier to install philz recovery, i opened it by booting into it immediately i selected format for new rom install. after that i am stuck on samsung logo i think the old rom is now deleted. Now i am downloading fresh 5.0.2 UK from sammobile i will download it and try to root it normally with flashing CF ROOT via odin. if it does not work then i will do what u guys said. I dont know if TWRP will work by the same method (booting immediately into recovery) but philz recovery did. And i will also try flashing a prerooted Rom. What i dont understand is that why is this happening in the first place? i had an alpha before i could enter into TWRP normally i rooted it with CF AUTO root normally...no errors or anything why is this happening on my S5? the last owner must have done something weird with it ...i am trying to figure out why is this happening in the first place. Appreciate ur feedback.
I also dont know why this is happening
and yeah
i had all the galaxy S series upto S5 and this the only device that is not rooting with CF-auto root
the latest updates from samsung may have done something i dnt knw
and eralier mentioned method worked 100% for me and i did root my device like that
And last owner may b or may not done anything with it because my device is a brand new and still i had that issue