Related
Hi
I need a help. I was flashed by odin new KitKat rom from samsung website after passed phone restart and stuck on Recovery booting. I cant get any download mode or recovey still this same - only samsung Galaxy note 3 logo and blue info on top"Recovery Booting..." Please help me.
Think I have the same issue.
Followed the guide as quoted in this post; http://forum.xda-developers.com/showpost.php?p=49438067&postcount=402
Downloaded from post; http://forum.xda-developers.com/showpost.php?p=49448237&postcount=443
Can't boot into download mode and it doesn't connect to PC. Just stuck saying "Recovery Booting..."
Edit: I can boot into download mode. Trying the same guide again.
Edit 2: Second flash worked.
sylwek23111 said:
Hi
I need a help. I was flashed by odin new KitKat rom from samsung website after passed phone restart and stuck on Recovery booting. I cant get any download mode or recovey still this same - only samsung Galaxy note 3 logo and blue info on top"Recovery Booting..." Please help me.
Click to expand...
Click to collapse
Don t panick. I did that already... You need to disconnect the cable and take out the battery. Then you press on the 3 buttons for a while (to empty the note completely) and put the battery back in. When you press the 3 buttons again it should be in download mode again.
To me it happened i think due to the fact i didn't tick update boot loader in odin 1.85. After ticking it and flashing no problem any more. Good luck
Thank you both for help. I fixed. Now i have kitkat with root but is another problem about cwm recovery. I was flashed by odin 6.0.4.5 and was successful but not working on my phone i cant get in. Always when i pressing tree buttons is "RECOVERY BOOTING" and restarting phone and booting system normal. Any advice?
sylwek23111 said:
Thank you both for help. I fixed. Now i have kitkat with root but is another problem about cwm recovery. I was flashed by odin 6.0.4.5 and was successful but not working on my phone i cant get in. Always when i pressing tree buttons is "RECOVERY BOOTING" and restarting phone and booting system normal. Any advice?
Click to expand...
Click to collapse
I found problem. i was flashing cwm 6.0.4.5 but i should 6.0.4.6 now everything fine.:laugh:
sylwek23111 said:
I found problem. i was flashing cwm 6.0.4.5 but i should 6.0.4.6 now everything fine.:laugh:
Click to expand...
Click to collapse
Good news. :good:
orange_dutchman said:
Don t panick. I did that already... You need to disconnect the cable and take out the battery. Then you press on the 3 buttons for a while (to empty the note completely) and put the battery back in. When you press the 3 buttons again it should be in download mode again.
To me it happened i think due to the fact i didn't tick update boot loader in odin 1.85. After ticking it and flashing no problem any more. Good luck
Click to expand...
Click to collapse
thanks for your help, i thought that i will send my note 3 to claim warranty at tomorrow. My phone just stuck at the "recovery booting" after failed in flashing the rom with mobile odin pro.
Nightmare79 said:
Think I have the same issue.
Followed the guide as quoted in this post; http://forum.xda-developers.com/showpost.php?p=49438067&postcount=402
Downloaded from post; http://forum.xda-developers.com/showpost.php?p=49448237&postcount=443
Can't boot into download mode and it doesn't connect to PC. Just stuck saying "Recovery Booting..."
Edit: I can boot into download mode. Trying the same guide again.
Edit 2: Second flash worked.
Click to expand...
Click to collapse
im note able to boot into download mode any help
---------- Post added at 12:50 AM ---------- Previous post was at 12:28 AM ----------
orange_dutchman said:
Don t panick. I did that already... You need to disconnect the cable and take out the battery. Then you press on the 3 buttons for a while (to empty the note completely) and put the battery back in. When you press the 3 buttons again it should be in download mode again.
To me it happened i think due to the fact i didn't tick update boot loader in odin 1.85. After ticking it and flashing no problem any more. Good luck
Click to expand...
Click to collapse
thanks you saved me
HELP!!!!
I JUST TRIED TO JAILBREAK MY PHONE USING CF-Auto-Root-hltetmo-hltetmo-smn900t.zip AND NOW MY PHONE IS STUCK IN RECOVERY MODE. I TOOK THE BATTERY OUT AND TRIED TO BOOT IT UP NORMALLY AND IT WON'T ALLOW ME TO. :crying: WHAT DO I DO????
jmanciaz said:
I JUST TRIED TO JAILBREAK MY PHONE USING CF-Auto-Root-hltetmo-hltetmo-smn900t.zip AND NOW MY PHONE IS STUCK IN RECOVERY MODE. I TOOK THE BATTERY OUT AND TRIED TO BOOT IT UP NORMALLY AND IT WON'T ALLOW ME TO. :crying: WHAT DO I DO????
Click to expand...
Click to collapse
Reflash stock firmware with Odin and after that data reset, then find a custom recovery like this one http://goo.im/devs/philz_touch/CWM_Advanced_Edition/hltetmo and flash it with Odin and flash the latest superSU.zip in recovery and you`re rooted.
Guys, I have a problem
I was stuck on recovery rebooting and now i'm on download mode and have problem with uploading stock rom
Odin 1.85 Says "Write operation failed"
On the screen i have "WTITE PROTECTION: ENABLE
And - after "Start" of flashing
"UDC START
SW REV CHECK FAIL : [aboot]Fused 3 > Binary 2"
please help!
konradciok said:
Guys, I have a problem
I was stuck on recovery rebooting and now i'm on download mode and have problem with uploading stock rom
Odin 1.85 Says "Write operation failed"
On the screen i have "WTITE PROTECTION: ENABLE
And - after "Start" of flashing
"UDC START
SW REV CHECK FAIL : [aboot]Fused 3 > Binary 2"
please help!
Click to expand...
Click to collapse
What were you trying to do before you get this error?
hey_joe said:
What were you trying to do before you get this error?
Click to expand...
Click to collapse
I was trying to flash custom rom (alexandr) with mobile odin. But first i made CF Auto-Root
Now I have nothing but stock recovery N9005_Stock_Recovery_KK.tar.md5
Phone is rebooting on logo Samsung Galaxy Note 3.
I have access to downlowad mode and to this recovery. And now i don't now what to do...
konradciok said:
Guys, I have a problem
I was stuck on recovery rebooting and now i'm on download mode and have problem with uploading stock rom
Odin 1.85 Says "Write operation failed"
On the screen i have "WTITE PROTECTION: ENABLE
And - after "Start" of flashing
"UDC START
SW REV CHECK FAIL : [aboot]Fused 3 > Binary 2"
please help!
Click to expand...
Click to collapse
Write the stock 4.4 ROM for your phone in normal Odin.
konradciok said:
I was trying to flash custom rom (alexandr) with mobile odin. But first i made CF Auto-Root
Now I have nothing but stock recovery N9005_Stock_Recovery_KK.tar.md5
Phone is rebooting on logo Samsung Galaxy Note 3.
I have access to downlowad mode and to this recovery. And now i don't now what to do...
Click to expand...
Click to collapse
I suggest you do the following;
First boot into stock recovery and do a factory reset, reboot and see if it boots up to android.
If that doesn't work, you can either odin a custom recovery like TWRP or CWM. Make sure you flash the latest one for KK as I've seen lots of people flashing one for 4.3 when they have a 4.4 bootloader.
Lastly, you can odin the stock firmware for your phone which can be downloaded off sammobile.
orange_dutchman said:
Don t panick. I did that already... You need to disconnect the cable and take out the battery. Then you press on the 3 buttons for a while (to empty the note completely) and put the battery back in. When you press the 3 buttons again it should be in download mode again.
To me it happened i think due to the fact i didn't tick update boot loader in odin 1.85. After ticking it and flashing no problem any more. Good luck
Click to expand...
Click to collapse
Thank you for saving my life, I love you man :laugh:
Thanks!!! Although this tutorial is for a note3 I follow all your recommendations, applied to my note4, and now my phone is working again.
Need help
Hello need help here,
I'm being dumb and fail to root my phone
I try to root my galaxy note 3 by following the step on http://forum.xda-developers.com/galaxy-note-3#root
I downloaded CF-Auto-Root-hlte-hltexx-smn9005 and kies3
However after using odin with check on PDA which is linked to the file in the zip called CF-Auto-Root-hlte-hltexx-smn9005.tar.md5
and check on auto reboot
in odin, it says that my root has pass within 13s
BUT
my device keep looping afterward and
show
Recovery Rebooting....
Recovery is not SEANDROID ENFORCING
Set Warranty Bit : Recovery
and then turned off
and then show that again
and turn off and show that again and soo on
I tried : removing battery and put it back in, it autoboot even without me pressing the power button and it goes showing above message again.
i tried to press the volume down+home+power button, nothing changed
I desperately need help here
any help is appreciated.
orange_dutchman said:
Don t panick. I did that already... You need to disconnect the cable and take out the battery. Then you press on the 3 buttons for a while (to empty the note completely) and put the battery back in. When you press the 3 buttons again it should be in download mode again.
To me it happened i think due to the fact i didn't tick update boot loader in odin 1.85. After ticking it and flashing no problem any more. Good luck
Click to expand...
Click to collapse
i tried this process which you told but also my samsung galaxy mega lte I9205 stucks on recovery booting. is there any other idea to fix it.
i have samsung galaxy mega lte I9205. i updated it to the new version of kitkat by odin. it became passed but after flashing the rom whenever i open my phone it says recovery booting on the left at the top and frequently gets switch off and opens again and again. i ticked on bootoader update on odin also but it dint fixed the problem. is there any idea to fix it.
Hey guys,
I decided that I wanted to root my phone for a custom rom. I used towelroot and odin to root my phone. It rooted successfully.
Heres where the problem is:
I installed twrp, and scrolled through menu options so I could install a Recovery. However, whenever I tried to install the rom, it would always take me to the default boot menu, therefore i was unable to get a rom. Long story short, twrp has caused my download mode menu to enable write protection. I went onto supersu, and removed my root. I just want to go back to factory/ stock rom and remove root. I downloaded samsungs firmware from their site and tried using odin, but this gives me a fail and states that "complete (write) operation failed".
My phone displays:
SGH-I337
Samsung Official
Custom system status
Knox kernal lock: 0x0
Knox Warranty viod: 0x0
CSB-config-lsb 0x30
write protection: enable
eMMC burst mode enable
I have tried to flash it back to stock so many times. Now I am getting a msg that says "firmware upgrade encountered an issue" -kies does not help remove this.
-I am using the original cable
-I can only boot into recovery and download mode.
-My main goal is to go back to stock.
Akluu said:
Hey guys,
I decided that I wanted to root my phone for a custom rom. I used towelroot and odin to root my phone. It rooted successfully.
Heres where the problem is:
I installed twrp, and scrolled through menu options so I could install a Recovery. However, whenever I tried to install the rom, it would always take me to the default boot menu, therefore i was unable to get a rom. Long story short, twrp has caused my download mode menu to enable write protection. I went onto supersu, and removed my root. I just want to go back to factory/ stock rom and remove root. I downloaded samsungs firmware from their site and tried using odin, but this gives me a fail and states that "complete (write) operation failed".
My phone displays:
SGH-I337
Samsung Official
Custom system status
Knox kernal lock: 0x0
Knox Warranty viod: 0x0
CSB-config-lsb 0x30
write protection: enable
eMMC burst mode enable
I have tried to flash it back to stock so many times. Now I am getting a msg that says "firmware upgrade encountered an issue" -kies does not help remove this.
-I am using the original cable
-I can only boot into recovery and download mode.
-My main goal is to go back to stock.
Click to expand...
Click to collapse
What firmware version are you on? You're probably going to have to use odin to get your phone working correctly again.
Sent from my Nexus 5 using XDA Free mobile app
Akluu said:
Hey guys,
I decided that I wanted to root my phone for a custom rom. I used towelroot and odin to root my phone. It rooted successfully.
Heres where the problem is:
I installed twrp, and scrolled through menu options so I could install a Recovery. However, whenever I tried to install the rom, it would always take me to the default boot menu, therefore i was unable to get a rom. Long story short, twrp has caused my download mode menu to enable write protection. I went onto supersu, and removed my root. I just want to go back to factory/ stock rom and remove root. I downloaded samsungs firmware from their site and tried using odin, but this gives me a fail and states that "complete (write) operation failed".
My phone displays:
SGH-I337
Samsung Official
Custom system status
Knox kernal lock: 0x0
Knox Warranty viod: 0x0
CSB-config-lsb 0x30
write protection: enable
eMMC burst mode enable
I have tried to flash it back to stock so many times. Now I am getting a msg that says "firmware upgrade encountered an issue" -kies does not help remove this.
-I am using the original cable
-I can only boot into recovery and download mode.
-My main goal is to go back to stock.
Click to expand...
Click to collapse
What firmware are you on?
If you upgraded past 4.4.2 mdlish then you have to safestrap.
Sounds like a soft brick to me, you have to Odin back and try again.
Make sure you Odin back to what you have/had or your stuck forever with safestrap.
If you don't know how to Odin read the giant back to stock guide.
Haven't rooted a phone in a little but am generally pretty savvy. I can get into recovery, tried restoring factory settings and clearing cache, same result unfortunately. I tried running an Odin .exe I found in another thread but it just opens and closes.. :/
When in download mode, product name: SMN900V, System Status: Custom
Knox Kernel Lock: 0x0, Knox Warranty Void: 0x0, Qualcomm Secureboot: Enable (CSB), RP SWREV: S1, T1, A3, P1
Write Protection: Enable, UDC START
Any help anyone can offer or provide a working rom or flashable file to get me booted would be most appreciated! No idea what ROM or Android version he put on this thing (purchased from Swappa).
TIA!!
Re download Odin and tar file. Have you gotten Odin to flash anything or does it fail or do you mean Odin itself isn't working? It sounds like you didn't extract Odin files and just opened it.
Sent from my SM-N900V using XDA-Developers mobile app
I was able to flash a Verizon firmware (thru Odin) and get it booted but I don't have root (seller claimed he did beforehand). Sounds like I should start with unlocking bootloader or root first? Thanks for the response man, I appreciate all the help I can get!
Sent from my SM-N900V using XDA-Developers mobile app
Start with the root first. Can't unlock the bootloader without it.
Awesome is there a one click by chance or is it complicated?
Sent from my SM-N900V using XDA-Developers mobile app
DNak206 said:
Awesome is there a one click by chance or is it complicated?
Sent from my SM-N900V using XDA-Developers mobile app
Click to expand...
Click to collapse
I had installed jasmine rom and ended up having problems with certain apps not working due to the modified framework he was using. I used odin to flash the new OB6 & pit (returns to locked boot loader with stock lollipop rom). I took the OTA to OF1, then used the yemen 1 click root. At this point the only issue I have is trying to get a customer bootloader installed. The TWRP version 3.0.2-0 just leaves me stuck at boot loader and I had to reinstall the pit file to get phone to boot again. Hope that helps you. I like stock rom but am trying to get native tether to work, without customer bootloader I can't flash anything.
I just got note3 Verizon, I rooted it couple days ago. I am on tmobile, so far everything works with stock lollipop except hotspot. Contemplating on unlocking boot loader at the moment.
santas16 said:
I had installed jasmine rom and ended up having problems with certain apps not working due to the modified framework he was using. I used odin to flash the new OB6 & pit (returns to locked boot loader with stock lollipop rom). I took the OTA to OF1, then used the yemen 1 click root. At this point the only issue I have is trying to get a customer bootloader installed. The TWRP version 3.0.2-0 just leaves me stuck at boot loader and I had to reinstall the pit file to get phone to boot again. Hope that helps you. I like stock rom but am trying to get native tether to work, without customer bootloader I can't flash anything.
Click to expand...
Click to collapse
[threadjack]
I was fooling around with flashing custom recoveries from within a rooted ROM today, and found something useful - when I "got stuck at bootloader" because TWRP failed to boot. So long as the main ROM is still bootable and is rooted, you can clear the "always tries to boot the recovery" behavior the following way:
1) Pull the battery (and plug back in after a couple seconds)
2) Vol-Down+Home+Power (as if you are trying to enter Download mode)
3) When you get the Custom ROM Warning menu, choose Cancel (not Continue)
This clears the BCB (Boot Communication Block) in eMMC and the phone will thereafter attempt to boot normally, rather than continuing to try to boot the recovery again. The sequence #2-3 does not work if you don't start by pulling the battery - if you soft-boot by holding the Power button down (~ 15 seconds), the phone will always attempt to boot the (broken) recovery, whether you enter Odin mode or Cancel.
Well, that's the way my phone behaves at this moment. (I am using a older bootloader however - it is always possible that this is a bootloader behavior that changed in later versions). Anyway - if you get "stuck" again, this could save you some labor, rather than having to go back to Odin, flash everything, and re-root.
Having said that, I'm not sure what you would use as alternative custom recovery. You could do something like pull just the stock kernel from the OF1 and re-pack it into your own customization of TWRP to see if that changes anything. Thing is, I could have sworn I saw a report from someone who said they are using TWRP 3.0.2 with the OF1 bootloader successfully.
Are you using "twrp-3.0.2-0-hlte.img" ?
[/threadjack]
bftb0 said:
[threadjack]
I was fooling around with flashing custom recoveries from within a rooted ROM today, and found something useful - when I "got stuck at bootloader" because TWRP failed to boot. So long as the main ROM is still bootable and is rooted, you can clear the "always tries to boot the recovery" behavior the following way:
1) Pull the battery (and plug back in after a couple seconds)
2) Vol-Down+Home+Power (as if you are trying to enter Download mode)
3) When you get the Custom ROM Warning menu, choose Cancel (not Continue)
This clears the BCB (Boot Communication Block) in eMMC and the phone will thereafter attempt to boot normally, rather than continuing to try to boot the recovery again. The sequence #2-3 does not work if you don't start by pulling the battery - if you soft-boot by holding the Power button down (~ 15 seconds), the phone will always attempt to boot the (broken) recovery, whether you enter Odin mode or Cancel.
Well, that's the way my phone behaves at this moment. (I am using a older bootloader however - it is always possible that this is a bootloader behavior that changed in later versions). Anyway - if you get "stuck" again, this could save you some labor, rather than having to go back to Odin, flash everything, and re-root.
Having said that, I'm not sure what you would use as alternative custom recovery. You could do something like pull just the stock kernel from the OF1 and re-pack it into your own customization of TWRP to see if that changes anything. Thing is, I could have sworn I saw a report from someone who said they are using TWRP 3.0.2 with the OF1 bootloader successfully.
Are you using "twrp-3.0.2-0-hlte.img" ?
[/threadjack]
Click to expand...
Click to collapse
I get a different kind of stuck, I'm not going to try it again but it said the phone has detected software that is not authorized or something along those lines. I cannot just pull battery as it just repeats over and over. I actually do not ever get to enter any recoveries at all, it automatically detects that's it's not the original bootloader and tells me such. anyways, I had to reload the image and take the OF1 update again... all is working back to normal.
I had used "twrp-3.0.2-0-hltevzw-4.4.img" from the twrp manager app, flashed via app, restarted to end up having the error message immediately on bootup of device... no recoveries or anything could load. I would have to assume the 4.4 means kk version and that's why it didn't work?
santas16 said:
I had installed jasmine rom and ended up having problems with certain apps not working due to the modified framework he was using. I used odin to flash the new OB6 & pit (returns to locked boot loader with stock lollipop rom). I took the OTA to OF1, then used the yemen 1 click root. At this point the only issue I have is trying to get a customer bootloader installed. The TWRP version 3.0.2-0 just leaves me stuck at boot loader and I had to reinstall the pit file to get phone to boot again. Hope that helps you. I like stock rom but am trying to get native tether to work, without customer bootloader I can't flash anything.
Click to expand...
Click to collapse
Hmmm. Maybe I was reading something into your post that wasn't there. I assumed that you had also performed the retail-to-dev edition CID change "unlock" after you gained root on OF1. Is that wrong - did you simply flash a recovery after getting root?
In my case I flashed a non-bootable TWRP (dd of=/dev/block/mmcblk0p15...) onto the recovery; doing this tripped my Knox Warranty flag, but otherwise the bootloader didn't complain about unauthorized software. After figuring out how to clear the "always try to boot the recovery" near-disaster, I used a 2.8.x TWRP series custom recovery successfully (In addition to flashing the stock recovery back into place and verifying that it still worked) But this is on a truly ancient bootloader (MJ7), so maybe all bets are off about expecting later bootloaders to behave in this same fashion.
Still, the point of developer edition functionality is to allow for custom boot (& recovery) partitions, so it's surprising that you were getting warnings like that if your phone was in developer mode.
@santas16
Hey. For what it's worth, I was able to boot twrp-3.0.2-hltevzw-4.3.img from my SM-N900V ... with a MJ7 bootloader!
But not the hltevzw-4.4.img. (That could be due to the old bootloader however, I don't know for sure)
Note that my phone has the retail-to-deved CID change that puts it into developer mode. (I used @donc113 's executable with adb)
This allows unsigned boot or recovery partitions to proceed to load/execute, but it will burn your Knox Warranty flag (which is unimportant to me at this point). I think that is actually the expected behavior when the phone is in developer mode.
I've been flashing all sorts of recoveries without worrying whether they will boot or not (as I know I can get back into the rooted ROM to flash into place a working version)**
Probably the best advice about not getting stuck in the "continually tries to re-enter the recovery" mode is to NOT use "reboot to recovery" methods (in Safestrap, other recoveries, or root-privileged Apps (flashfire?)), but to always shut the phone down to a powered-off state, and just use the three-button startup method (Vol-Up+Home+Power) to enter the recovery. That way nothing is being written into the BCB that will make it want to loop back to a failed recovery.
cheers
** what was interesting is that I could successfully boot any of the MI9, MJ7, MJE stock recoveries on my MJ7 phone. Moreover, the bootloader would not pop up the yellow "Set Warranty Bit: recovery" message right before they loaded. The NC4 recovery would not boot to a menu, but it also did not present a "Set Warranty Bit: recovery" message. I presume this means that the boot layer is not looking for exact version matches, but rather just checking that the Samsung signing operation is correct. I could not boot OB6 or OF1 recoveries; somewhat curiously though, these attempts *would* throw the "Set Warranty Bit: recovery" error message even though they are validly signed Samsung recoveries. I don't know if it is a reasonable hypothesis, but I think that indicates that Samsung may have altered the details of their signing verification method someplace between NC4 and OB6 so that earlier bootloaders fail this check. Ugh. As if there weren't enough details already.
If your bootloader is still 0F1 then download flashify from Google and hit recovery and tap top twrp.. Your all set...sounds like a lot of craziness for nothing.
Sent from my SM-N900V using XDA-Developers mobile app
santas16 said:
I get a different kind of stuck, I'm not going to try it again but it said the phone has detected software that is not authorized or something along those lines. I cannot just pull battery as it just repeats over and over. I actually do not ever get to enter any recoveries at all, it automatically detects that's it's not the original bootloader and tells me such. anyways, I had to reload the image and take the OF1 update again... all is working back to normal.
I had used "twrp-3.0.2-0-hltevzw-4.4.img" from the twrp manager app, flashed via app, restarted to end up having the error message immediately on bootup of device... no recoveries or anything could load. I would have to assume the 4.4 means kk version and that's why it didn't work?
Click to expand...
Click to collapse
If you get the " not authorized or something along those lines" error, it means you're not unlocked.
Hi,
I'm from Singapore and I believe I have the international s5 (SM-G900F), at least that's what it says in download mode. My phone was running CM13 nightly and till last night it was working fine. Last night when I charged it, I woke up this morning and my battery was incredibly overheated. I changed my battery and tried booting, but now it gets stuck in a bootloop. I flashed stock 5.0 lollipop from sammobile via odin, but it still is stuck. I can boot perfectly into download mode with the android logo. Here are the details:
PRODUCT NAME: SM-G900F
CURRENT BINARY: Custom
System Status: Custom
Reactivation Lock (KK): OFF
KNOX WARRANTY LOCK: 0x1 (04)
QUALCOMM SECUREBOOT: ENABLE(CSB)
RP SWERV: S1, T1, R1, A1, P1
SECURE DOWNLOAD: ENABLE
UDC START
I would really appreciate any help. Thanks!
Boot into recovery and factory reset, then try booting again
Sounds like the DATA partition got corrupted, or something installed to it did, flashing with ODIN doesn't wipe anything, so you'll still be bootlooped unless you wipe DATA / Factory Reset
When you go from cyanogenmod back to stock samsung firmware, a wipe data / factory reset is required in recovery or else the phone will be stuck in a boot loop or not boot up.
Hi, the problem is I cant access the recovery any more. Every time I hold power, volume up and the home button, it says recovery booting, warranty bit:kernel, kernel is not se android enforcing (the usual) but doesn't actually enter recovery.
imbtrthanu said:
Hi, the problem is I cant access the recovery any more. Every time I hold power, volume up and the home button, it says recovery booting, warranty bit:kernel, kernel is not se android enforcing (the usual) but doesn't actually enter recovery.
Click to expand...
Click to collapse
Flash TWRP 3.0.0.0 with ODIN and wipe from there, then flash stock again
https://dl.twrp.me/klte/twrp-3.0.0-0-klte-klte.img.tar.html
Hi I tried flashing twrp but that didn't work. It doesnt enter recovery, it still just restarts.
Is there any other way I can do a wipe? Through adb or something? Or should I select a specific option in Odin (3.09) ? Like bootloader update, etc or something?
imbtrthanu said:
Hi I tried flashing twrp but that didn't work. It doesnt enter recovery, it still just restarts.
Click to expand...
Click to collapse
Uncheck "Auto Reboot" in ODIN, flash TWRP again, when it completes, disconnect USB and pull the battery to power off the phone
Replace the battery, and boot immediately into recovery with Vol Up & Home & Power
Hi that's not working as well. Should I reflash stock and then flash twrp in the way you suggested?
Try, but something seems wrong because you should be able to flash TWRP with ODIN
Have you got the drivers installed and does ODIN give you a COM port at the top when the phone is in download mode?
You are putting the phone in download mode to flash TWRP right?
Vol Down & Home & Power
Yes I'm using Odin 3.09. I'm flashing via the AP slot. I only have F Reset time checked. My S5 is definitely in downloading mode. Looks similar to this:
http://cdn.androidblog.gs/wp-content/uploads/2014/12/Samsung-Galaxy-S5-Stuck-In-Download-Mode.png
Also, I think the drivers may be the issue here. Could you advise me on how to check and how to fix it? Thanks so much! Also, yes, the COM port lights up
imbtrthanu said:
Yes I'm using Odin 3.09. I'm flashing via the AP slot. I only have F Reset time checked. My S5 is definitely in downloading mode. Looks similar to this:
http://cdn.androidblog.gs/wp-content/uploads/2014/12/Samsung-Galaxy-S5-Stuck-In-Download-Mode.png
Also, I think the drivers may be the issue here. Could you advise me on how to check and how to fix it? Thanks so much! Also, yes, the COM port lights up
Click to expand...
Click to collapse
If the COM port lights up, the drivers are installed and working
Try ODIN 3.10.7, that's the latest version
Code:
https://mega.nz/#!vcIGmBTQ!Yr00OrGvUslQouU9E-zPf4SmpyVwL7mwIjeSG-0EAZg
Hi, that also didn't work. Any other advice?
Use a different PC / USB lead, everything you have tried should have worked fine on a G900F
Hi, I tried using a different PC and USB cable. Still nothing. Could it be because I flashed a different PIT file previously? There was a thread where someone suggested flashing a pit file, so
imbtrthanu said:
Hi, I tried using a different PC and USB cable. Still nothing. Could it be because I flashed a different PIT file previously? There was a thread where someone suggested flashing a pit file, so
Click to expand...
Click to collapse
Didn't you flash the G900F PIT?
Flash this in the PIT section of ODIN along with the stock ROM
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Extract to .pit first
Hi, I tried flashing the stock rom with the PIT you gave me but it gave me the following response:
<ID:0/005> FAIL! (Size)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas what I should do now? Also, which stock rom should I be flashing? KK or Lollipop?
I don't know what you've done to your phone, and from your main post, it is definitely a G900F if that is what it says in download mode
Which PIT did you flash the first time? And did it flash successfully?
Any stock ROM should work, but might as well go for Lollipop, I know 100% this one works
Code:
https://mega.nz/#!fVhhzRBC!A79uC8Fgg1mGCZOaujQCzBxcUUN9z_ctVVkigD8ffVM
The only thing I can think of for now is to tell KIES3 to perform a firmware recovery
Code:
http://www.samsung.com/uk/support/usefulsoftware/KIES/
If you already have KIES installed, remove it and try ODIN again, people have reported it interferes with ODIN
If not, install KIES3, go to the firmware recovery setting and see if it can fix your phone
Other than that, it looks like it's going to need someone with knowledge of manual partitioning via adb shell or something, if the phone can enter a mode the PC can use that with
EDIT - You are using a native PC running Windows 7 or later right? Not a mac running Windows? Macs don't install the drivers properly and fail
Yup I'm running Windows 10. I'll try KIES and see if that works!
Which PIT did you originally flash? And did it actually flash?
Recently, I turned off developer options in my rooted S7 Edge (SM-G935FD). Idk if that is the cause, but after rebooting I got the error "Custom Binary Blocked by FRP Lock". I couldnt boot into my recovery (TWRP) either. I was running on Oreo btw. I watched some Youtube guides and apparently the solution was to flash stock rom. So... I flashed an Oreo Stock Rom on my phone via Odin. I thought that would solve my problem, but instead it made it worse. It didnt give me the Custom Binary Blocked by FRP lock error but my boot screen is stuck at the boot animation (not a bootloop). I could boot into the stock recovery tho. I tried a factory reset, that didnt make things better. I could also boot into download mode. I thought I made a mistake, so I flashed like 5-8 times with both CSC an Home_CSC. The result was the same, it would get stuck at the boot animation. I tried flashing TWRP via Odin too, but it said "Custom Binary (Recovery) blocked by FRP Lock". I tried sideloading that TWRP file to my device via ADB. It gave me an error too (I think "Cannot flash from external devices" or something like that) I thought flashing with Re-partition and Nand Erase On would solve my problem, so I tried that, but it didnt work. Im running on Binary 3 apparently. Is there anything I can do?
Rapidfayaround said:
Recently, I turned off developer options in my rooted S7 Edge (SM-G935FD). Idk if that is the cause, but after rebooting I got the error "Custom Binary Blocked by FRP Lock". I couldnt boot into my recovery (TWRP) either. I was running on Oreo btw. I watched some Youtube guides and apparently the solution was to flash stock rom. So... I flashed an Oreo Stock Rom on my phone via Odin. I thought that would solve my problem, but instead it made it worse. It didnt give me the Custom Binary Blocked by FRP lock error but my boot screen is stuck at the boot animation (not a bootloop). I could boot into the stock recovery tho. I tried a factory reset, that didnt make things better. I could also boot into download mode. I thought I made a mistake, so I flashed like 5-8 times with both CSC an Home_CSC. The result was the same, it would get stuck at the boot animation. I tried flashing TWRP via Odin too, but it said "Custom Binary (Recovery) blocked by FRP Lock". I tried sideloading that TWRP file to my device via ADB. It gave me an error too (I think "Cannot flash from external devices" or something like that) I thought flashing with Re-partition and Nand Erase On would solve my problem, so I tried that, but it didnt work. Im running on Binary 3 apparently. Is there anything I can do?
Click to expand...
Click to collapse
I still have the "FRP Lock: On" on download mode, so I tried bypassing FRP lock via binary 5 combination firmware and flashing a binary 7 stock firmware. This time, it doesnt get stuck at the boot animation, instead it redirects to a screen with an android face saying "Installing System updates". A few seconds later, it says "No command" with a dead android face. Then it reboots and the same thing happens. Basically a boot loop, but in a different way. I cant seem to boot to stock recovery either. The worst thing is that I cant even turn off the thing. I have to leave it loop for the entire day until its battery dies
Rapidfayaround said:
I still have the "FRP Lock: On" on download mode, so I tried bypassing FRP lock via binary 5 combination firmware and flashing a binary 7 stock firmware. This time, it doesnt get stuck at the boot animation, instead it redirects to a screen with an android face saying "Installing System updates". A few seconds later, it says "No command" with a dead android face. Then it reboots and the same thing happens. Basically a boot loop, but in a different way. I cant seem to boot to stock recovery either. The worst thing is that I cant even turn off the thing. I have to leave it loop for the entire day until its battery dies
Click to expand...
Click to collapse
after flashing the combination firmware, flash the stock firmware and go thru the boot process
Youdoofus said:
after flashing the combination firmware, flash the stock firmware and go thru the boot process
Click to expand...
Click to collapse
That is what I literally did. I flashed a combination firmware, factory rested my entire phone, turned on developer options as well as allow usb debugging, attempted to reset FRP via Z3X Samsung Tool Pro and finally flashed a stock rom. And, the result is this. A bootloop with an android face dying. I did manage to enter a different screen by pressing volume up once along with pressing volume down and power button. It said "could not open recovery_because_no file directory" and had some more errors. The thing is....I made it worse at the first place. I could have flashed a room with binary 6 or lower, cuz at least the combination firmware would have been available to flash, but my stupid brain did not think of that. I flashed a binary 7 stock rom and there is no combination firmware with a binary of 7 or more. Which means, I will most likely get the "SW check fail Device: 7 Binary: 6 " error while flashing.
Rapidfayaround said:
That is what I literally did. I flashed a combination firmware, factory rested my entire phone, turned on developer options as well as allow usb debugging, attempted to reset FRP via Z3X Samsung Tool Pro and finally flashed a stock rom. And, the result is this. A bootloop with an android face dying. I did manage to enter a different screen by pressing volume up once along with pressing volume down and power button. It said "could not open recovery_because_no file directory" and had some more errors. The thing is....I made it worse at the first place. I could have flashed a room with binary 6 or lower, cuz at least the combination firmware would have been available to flash, but my stupid brain did not think of that. I flashed a binary 7 stock rom and there is no combination firmware with a binary of 7 or more. Which means, I will most likely get the "SW check fail Device: 7 Binary: 6 " error while flashing.
Click to expand...
Click to collapse
If the device is still entering download mode, install the recent version of stock for your device. Maybe that will solve your problem.
Rapidfayaround said:
That is what I literally did. I flashed a combination firmware, factory rested my entire phone, turned on developer options as well as allow usb debugging, attempted to reset FRP via Z3X Samsung Tool Pro and finally flashed a stock rom. And, the result is this. A bootloop with an android face dying. I did manage to enter a different screen by pressing volume up once along with pressing volume down and power button. It said "could not open recovery_because_no file directory" and had some more errors. The thing is....I made it worse at the first place. I could have flashed a room with binary 6 or lower, cuz at least the combination firmware would have been available to flash, but my stupid brain did not think of that. I flashed a binary 7 stock rom and there is no combination firmware with a binary of 7 or more. Which means, I will most likely get the "SW check fail Device: 7 Binary: 6 " error while flashing.
Click to expand...
Click to collapse
the "no such file or directory" error is due to either having had removed stock recovery in flashing the firmwares or the factory recovery corrupted due to likely the same reason. Just flash a revision 7 firmware for your phone and it will at least boot
Dark Stranger said:
If the device is still entering download mode, install the recent version of stock for your device. Maybe that will solve your problem.
Click to expand...
Click to collapse
^^^ this ^^^
Dark Stranger said:
If the device is still entering download mode, install the recent version of stock for your device. Maybe that will solve your problem.
Click to expand...
Click to collapse
I have literally flashed the latest stock rom for my device and my country which is G935FXXS7ESK8.
I am a bit confused tho...I am not sure if my device is SM-G935FD or SM-G935F. The download mode says SM-G935F...but this phone used to work with a SM-G935FD rom back in the days. Is this causing the problem most likely? And btw the repair shop said they cant fix it too
Rapidfayaround said:
I have literally flashed the latest stock rom for my device and my country which is G935FXXS7ESK8.
I am a bit confused tho...I am not sure if my device is SM-G935FD or SM-G935F. The download mode says SM-G935F...but this phone used to work with a SM-G935FD rom back in the days. Is this causing the problem most likely? And btw the repair shop said they cant fix it too
Click to expand...
Click to collapse
I am somehow relieved to know that someone else on this planet is on the same (EXACT) boat as me....this is what we get for messing around too much with our phone hum?
1 - After booting up my phone I get the blue background with a dead Android and "No Command" message
2 - I tried accessing recovery by pressing Power+Home+VolumeUp, but all I get is a black screen with a wall of code lines with "fail to open recovery_cause(No such file or directory)" at the beggining of the text.
3 - "No problem! I'll just flash TWRP with ODIN and install a custom ROM and be done with it!".
..NOPE! FRP(factory reset protection) is ON!!! I cannot install TWRP
4- I've tried to find a combination file with binary version 7...but looks like the internet doesn't seem to care about the good ol' number 7...All I can find is binary version 6.
What Im trying to do now is creating my own combination file binary version 7 (if that's even a thing...) from a stock firmware. But I'm not getting any luckier down this path.
Looks like we need a hero...:crying:
PseudoNoob said:
I am somehow relieved to know that someone else on this planet is on the same (EXACT) boat as me....this is what we get for messing around too much with our phone hum?
1 - After booting up my phone I get the blue background with a dead Android and "No Command" message
2 - I tried accessing recovery by pressing Power+Home+VolumeUp, but all I get is a black screen with a wall of code lines with "fail to open recovery_cause(No such file or directory)" at the beggining of the text.
3 - "No problem! I'll just flash TWRP with ODIN and install a custom ROM and be done with it!".
..NOPE! FRP(factory reset protection) is ON!!! I cannot install TWRP
4- I've tried to find a combination file with binary version 7...but looks like the internet doesn't seem to care about the good ol' number 7...All I can find is binary version 6.
What Im trying to do now is creating my own combination file binary version 7 (if that's even a thing...) from a stock firmware. But I'm not getting any luckier down this path.
Looks like we need a hero...:crying:
Click to expand...
Click to collapse
OMGGGGGGGG....Looks like I am not the only one. DAMN. Bro...tell me if you find a solution ok? Hopefully there is a way to solve this problem...there has to be one. And share your combination firmware after you finish it. Thank you very much
Rapidfayaround said:
OMGGGGGGGG....Looks like I am not the only one. DAMN. Bro...tell me if you find a solution ok? Hopefully there is a way to solve this problem...there has to be one. And share your combination firmware after you finish it. Thank you very much
Click to expand...
Click to collapse
No luck over here friend...
Desperate times require desperate measures. Have you ever tried flashing combination files from different S7 Edge versions?
I can find files for the G935A with a revision 7 of the binary...Im thinking flashing it into my G935F and see what happens. I've read the risks associated with installing firmwares from other phone versions, but I'll have a paperweight either way.
I'll keep this thread updated.
Rapidfayaround said:
I have literally flashed the latest stock rom for my device and my country which is G935FXXS7ESK8.
I am a bit confused tho...I am not sure if my device is SM-G935FD or SM-G935F. The download mode says SM-G935F...but this phone used to work with a SM-G935FD rom back in the days. Is this causing the problem most likely? And btw the repair shop said they cant fix it too
Click to expand...
Click to collapse
Doesn't really matter if you have a F or FD. I'd say you flash the latest stock rom for G935F or FD(which ever is latest) for any country regardless. By this you should be able to boot and won't get any odin errors.
UsmaniMustafa said:
Doesn't really matter if you have a F or FD. I'd say you flash the latest stock rom for G935F or FD(which ever is latest) for any country regardless. By this you should be able to boot and won't get any odin errors.
Click to expand...
Click to collapse
Can you provide me the link plz.
Turns out, its a hardware problem with the storage. Replacing the motherboard might be the solution I think. :/
I had solved my phone last day
At first u can flash ur phone to leatest stock rom. Then u have to turn of frp lock. Then u will able to boot up your phone. If u cant fix u can knock me on facebook. (If u r a z3x user). Bcoz u need z3x for bypass frp with ufs cable.
Im also using s7 edge.
hazratboss said:
At first u can flash ur phone to leatest stock rom. Then u have to turn of frp lock. Then u will able to boot up your phone. If u cant fix u can knock me on facebook. (If u r a z3x user). Bcoz u need z3x for bypass frp with ufs cable.
Im also using s7 edge.
Click to expand...
Click to collapse
Oh ok I will contact you
hazratboss said:
At first u can flash ur phone to leatest stock rom. Then u have to turn of frp lock. Then u will able to boot up your phone. If u cant fix u can knock me on facebook. (If u r a z3x user). Bcoz u need z3x for bypass frp with ufs cable.
Im also using s7 edge.
Click to expand...
Click to collapse
Does it matter if I use the cracked version without box. And no, I dont have the ufs cable. Is there anything else I can do?
Hi guys, I have the exact same problem with my S7 edge from T-mobile (g935t). Odin will only accept for flash the latest rom and after flash it reboots but I get BSOD. I tried a pit file also from an old g935T rom which was android 6.0 and I managed to get into recovery for a moment and I did a factory reset/wipe cache but after reboot entered again in a black screen and the blue led was lit. I finally removed the battery to turn the phone off. I can still enter download mode but is there anything else I can do to resurrect the phone?
Samsung s7 edge (g935f)
Hi everyone , please am having issue of NO COMMAND and i cant boot into recovery. My oem is on so i cant install twpr neither. Am on binary u8. Please any solution to recover my phone?
Very very good new guys...yep you guessed it right. I was able to fix this problem.
How you may ask? Follow these steps
Note: Make sure you have enough battery. Lack of battery charge in my case caused alot of problems.
1. Download a U7 Rom for your SM-G935F or SM-G935FD
2. Extract the Rom as well as the AP
3. After you extract the AP, you will be greeted with boot.lz4.img , recovery.lz4.img , system.lz4.img & meta-data
4. Make a backup of recovery.lz4.img and meta-data just in case. Also, make a copy of boot.lz4.img and rename the copied one to recovery.lz4.img. Don't forget to delete the original recovery and meta-data
5. Now, you should be left with boot.lz4.img , (modified) recovery.lz4.img and system.lz4.img.
6. Now, download this https://www.mediafire.com/file/ah20ha869prdkkc/Autotar2.0_By_FixFirmwares.com.rar/file
7. Now, make a .md5 file that contains (modified) recovery.lz4.img and system.lz4.img
8. After you are done making that .md5, flash it along with CSC, CP and BL.
9. You should directly boot into your device, (if you do), charge your phone for a while if the battery is lower than 20%.
10. Then, go to the settings and enable OEM Unlock before doing ANYTHING
11. Then, reboot to download mode and flash TWRP
12. Download the no-verity-encryption.zip
https://zackptg5.com/android.php#disverfe
13. Allow system modifications and format data (NOT WIPE)
14. If that doesn't work, go to TWRP, connect it to your PC and copy the no-verity-encryption.zip file and install it
15. If that still doesn't work then, follow this tutorial
https://www.google.com/amp/s/forum....niversal-dm-verity-forceencrypt-t3817389/amp/
16. Then, you should boot and yea...enjoy ?
If this method doesn't work then, you need to try different combinations.
Try packing these files in AP
1. Boot.lz4.img, (Modified) Recovery.lz4.img & system.lz4.img
2. (Modified) Recovery.lz4.img & system.lz4.img
3. Meta-data, Boot.lz4.img, (Modified) Recovery.lz4.img & system.lz4.img
If that doesn't work, I'm sorry this is how I fixed it. ?*
For anyone wondering how I fixed it well, firstly a HUGE THANKS TO @shah22 & @Tapas27sTapas2. This would have been LITERALLY IMPOSSIBLE WITHOUT THEM. So, basically I tried an AP with renamed recovery.lz4.img and system.lz4.img only along with CP, CSC and BL. Due to my phone having literally 0%, this journey was very difficult.
Feel free to ask any question
Very very good new guys...yep you guessed it right. I was able to fix this problem.
How you may ask? Follow these steps
Note: Make sure you have enough battery. Lack of battery charge in my case caused alot of problems.
1. Download a U7 Rom for your SM-G935F or SM-G935FD
2. Extract the Rom as well as the AP
3. After you extract the AP, you will be greeted with boot.lz4.img , recovery.lz4.img , system.lz4.img & meta-data
4. Make a backup of recovery.lz4.img and meta-data just in case. Also, make a copy of boot.lz4.img and rename the copied one to recovery.lz4.img. Don't forget to delete the original recovery and meta-data
5. Now, you should be left with boot.lz4.img , (modified) recovery.lz4.img and system.lz4.img.
6. Now, download this https://www.mediafire.com/file/ah20ha869prdkkc/Autotar2.0_By_FixFirmwares.com.rar/file
7. Now, make a .md5 file that contains (modified) recovery.lz4.img and system.lz4.img
8. After you are done making that .md5, flash it along with CSC, CP and BL.
9. You should directly boot into your device, (if you do), charge your phone for a while if the battery is lower than 20%.
10. Then, go to the settings and enable OEM Unlock before doing ANYTHING
11. Then, reboot to download mode and flash TWRP
12. Download the no-verity-encryption.zip
https://zackptg5.com/android.php#disverfe
13. Allow system modifications and format data (NOT WIPE)
14. If that doesn't work, go to TWRP, connect it to your PC and copy the no-verity-encryption.zip file and install it
15. If that still doesn't work then, follow this tutorial
https://www.google.com/amp/s/forum....niversal-dm-verity-forceencrypt-t3817389/amp/
16. Then, you should boot and yea...enjoy ?
If this method doesn't work then, you need to try different combinations.
Try packing these files in AP
1. Boot.lz4.img, (Modified) Recovery.lz4.img & system.lz4.img
2. (Modified) Recovery.lz4.img & system.lz4.img
3. Meta-data, Boot.lz4.img, (Modified) Recovery.lz4.img & system.lz4.img
If that doesn't work, I'm sorry this is how I fixed it. ?*
For anyone wondering how I fixed it well, firstly a HUGE THANKS TO @shah22 & @Tapas27s. This would have been LITERALLY IMPOSSIBLE WITHOUT THEM. So, basically I tried an AP with renamed recovery.lz4.img and system.lz4.img only along with CP, CSC and BL. Due to my phone having literally 0%, this journey was very difficult.
Feel free to ask any question