Purchased a Note3, stuck on Custom ROM boot screen - Verizon Galaxy Note 3 Q&A, Help & Troubleshooting

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.

Related

[SOLVED] Flashed wrong recovery, now stuck in Odin mode: "Could not do normal boot"

[SOLVED] Flashed wrong recovery, now stuck in Odin mode: "Could not do normal boot"
First time venturing into rootin' 'n bootin' Android devices. Hopefully will have a long pleasant journey ahead, but due to a silly oversight, I flashed the wrong recovery file to my device (hangs head in shame). I'm an seasoned coder, but am somewhat new to Android.
Some info:
Model: SM-N910G (SnapDragon)
Device does not want to boot normally, stuck in downloading mode. The screen shows the following:
"Could not do normal boot. ODIN MODE (HIGH SPEED)" Reactivation lock is "OFF".
[x] device is rooted and was running stock TouchWizard (based on Lollipop 5.0.1)
[x] can't get the phone to enter recovery mode (by pressing PWR+Menu+Volume Up)
[x] device is not recognised in ADB (using "adb devices")
[x] Samsung Kies3 does recognise that there is a device but says it's unsupported
[x] device is recognised in Odin/Windows (blue comes up)
[x] device is recognised in Heimdall on OSX (however, I have not used Heimdall for flashing at all yet)
[x] I now have to pull the battery to turn device off
[x] my main computer is a fast MacBook Pro, but have access to older/slower Windows 7 laptops (with only 2GB RAM).
I had the device rooted and working fine except for the fact that I was getting "dm-verity verification failed" errors when trying to make a Nandroid backup. So I tried to reinstall TWRP recovery -- this time rather than going through Odin, I tried it with TWRP Manager (installed on device). I managed to select the wrong recovery file (SM-N910F instead of SM-N910G -- in TWRP Manager this was somewhat unlclear, as I selected the "Galaxy Note 4 INTERNATIONAL version"; my device could be considered "INTERNATIONAL version", I should have been MUCH more careful however).
What is the best course of action to take from here on? I have read a serious number of posts on XDA, but am somewhat unclear about best action to take from here on.
All help will be much appreciated: amazing Karma coming your way to all who can help get this device booting normally!
Have you tried to flash via ODIN the right version of TWRP?
_mone said:
Have you tried to flash via ODIN the right version of TWRP?
Click to expand...
Click to collapse
First of all, thank you for responding. Much appreciated.
One of the problems I keep running into is that Odin (various versions) gets stuck and is "Not Responding" when attempting to verify the MD5 hash of the recovery file. Mind you, this happens when the device is NOT plugged in.
Surely, verifying a 15mb recovery file should only take a few seconds (even on an older machine) ? I have tried re-downloading the same file. For now: I'll keep looking for good sources of the correct N910G TWRP recovery file.
Zef Vegas said:
First of all, thank you for responding. Much appreciated.
One of the problems I keep running into is that Odin (various versions) gets stuck and is "Not Responding" when attempting to verify the MD5 hash of the recovery file. Mind you, this happens when the device is NOT plugged in.
Surely, verifying a 15mb recovery file should only take a few seconds (even on an older machine) ? I have tried re-downloading the same file. For now: I'll keep looking for good sources of the correct N910G TWRP recovery file.
Click to expand...
Click to collapse
Correct me if I'm wrong.
Is the N910G called trltedt?
If it is like that you should download twrp-2.8.7.0-trltedt.img.tar from this official TWRP page and flash it via ODIN
I believe you are correct (and thanks for that link). I'm currently verifying whether the N910G is indeed called trltedt. There seems to be a bit of confusion out there over that specific model. Will report back shortly.
Zef Vegas said:
I believe you are correct (and thanks for that link). I'm currently verifying whether the N910G is indeed called trltedt. There seems to be a bit of confusion out there over that specific model. Will report back shortly.
Click to expand...
Click to collapse
N910G is indeed trltedt.
Battlehero said:
N910G is indeed trltedt.
Click to expand...
Click to collapse
Thanks for confirming that. I had just come to the same conclusion. Am now looking for best source for Odin that works with my N910G device. As soon as I have found that, I'll flash the recovery file (from source suggested by _mone) on a PC w/ official Samsung USB drivers & w/ Kies uninstalled.
With ODIN 3.10.x you should be ok.
_mone said:
With ODIN 3.10.x you should be ok.
Click to expand...
Click to collapse
I am VERY happy to report that the flash worked: device booted up nicely. Thanks guys! As promised: seriously good Karma coming your way.
Now, what has made this all a fair bit trickier up to this point: each time I tried to let Odin read the MD5 hash associated with its TAR recovery file, Odin borked and became unresponsive. The recovery file suggested by _mone was processed by Odin just fine and the whole thing was done in seconds. Yay!
Think I'll have a beer now, take a breather, and toast to you guys (wish I could drink it with you two).
[EDIT] I was initially using a different recovery file to the one suggested by _mone. The recovery file I was using at first included a MD5 hash and caused Odin to become unresponsive.
Happy if you managed to solve the problems with your phone!
I'll have a beer too now! lol :cheers:

Help with rooting G906S Marshmallow 6.0.1 (tried CFire, TWRP and kingroot)

Hi, I've just recently switched over from iphone to android so I'm still new to the whole system. Anyway I've been trying to root my phone for the past 2 days to no avail so I'm at my wits end here. Before I start my phone is from korea which I don't know if whether or not impacts its ability to be rooted, I've done all the basics like enable USB debugging from dev mode, install samsung usb drivers, open ODIN in admin mode and allow MTP to computer. My Device details are below:
>Baseband version : G906SKSU1CPF1
>KERNEL : 3.10.40-8533426
>BUILD NUMBER : MMB29M.G906SKSU1CPF3
So anyway I first tried flashing using CF autoroot for sm-G906S with odin which while it said it was passed and was successful on pc it would be stuck on the samsung logo with a message at the top left that said :
>Recovery booting
>Recovery is not seandroid enforcing
>set warranty bit recovery
So then I tried flashing TWRP custom recovery and putting Super user zip in the internal storage which although got my phone back to working order still wouldnt let me root as the process required me to go to recovery mode from the fastboot mode after it was done flashing (I tried both with and without autoreboot), however once the flashing was done on fastboot I couldn't get to recovery mode no matter how long I held the Vol up/power/home button combination and when i tried it after rebooting it would show normal recovery mode hence there was no way to install the Super User. (Also attempted this with phils recovery)
I then tried to do the TWRP method using adb with command prompt however it would get stuck saying waiting for device when i tried to flash and needless to say kingroot also failed.
At this point as far I've gone through all the methods I could find for my particular device. Would greatly appreciate any insight or advice regarding this problem.
Thanks
start reading from here http://forum.xda-developers.com/gal...ner-thread-t2807639/post68725608#post68725608

unlock bootloader SM-G901F DTM

I am looking for a way to unlock the bootloader on my Samsung Galaxy S5 Plus (Sm-g901f, kccat6) with German t-Mobile branding (DTM) in order to flash Lineageos on it.
Is there a known way (executable for a newbie in Android flashing)?
Unfortunately my handset does not have a "OEM unlock" button in the developer options.
Is it possible to verify if the bootloader is locked apart from flashing a custom recovery and checking if it has been installed persistently?
i think you just have to flash twrp. if i remmeber correctly i had the same message that my bootloader was locked with my s4 i9506 back then
k2828 said:
i think you just have to flash twrp. if i remmeber correctly i had the same message that my bootloader was locked with my s4 i9506 back then
Click to expand...
Click to collapse
Even though my answer was posted a month ago, I want to present my solution:
As I said above, flashing TWRP did not worked on the way that all installation guides told me. But not because my bootloader was locked, the reason seems to be a bug (or is it a feature ) in TWRP.
The problem was, that the Stock OS is overwriting the bootloader on the first normal start.
What you have to do in order to prevent this mechanism:
1. Uncheck Auto-Reboot in Odin.
2. After Odin shows "PASS" shut your phone down and reboot it manually to the recovery.
3. In TWRP select Reboot and then System.
4. Done.
Now I am a lucky user of a LineageOS powered phone.
ooo yes thats a common odin bug for some phones..
dial25and said:
Even though my answer was posted a month ago, I want to present my solution:
As I said above, flashing TWRP did not worked on the way that all installation guides told me. But not because my bootloader was locked, the reason seems to be a bug (or is it a feature ) in TWRP.
The problem was, that the Stock OS is overwriting the bootloader on the first normal start.
What you have to do in order to prevent this mechanism:
1. Uncheck Auto-Reboot in Odin.
2. After Odin shows "PASS" shut your phone down and reboot it manually to the recovery.
3. In TWRP select Reboot and then System.
4. Done.
Now I am a lucky user of a LineageOS powered phone.
Click to expand...
Click to collapse
Why to shut down ?
When Odin passed !
Press download mode command keys
When screen goes black
Immediately press recovery commands !
And if u failed to reboot to recovery,flash firmware with nand erase all option !
As i experienced this issue!

Noob needs help flashing Android 6.0 or higher.

Noob here: I need help with my Note 3 (SM-N900V).
I bought a used phone to replace a stolen one; it came with Android 4.0. A few years ago I successfully used Odin to flash TWRP 3.1.0.0 and the stock OF1 Android 5.0 rom, followed by a root with ArabicTool.
Phone works fine for everyday use, including root-requiring apps, but several apps are now requiring a more recent version of Android. Also, I can no longer boot into recovery mode; instead I get a message saying "System software not authorized by Verizon Wireless has been found on your phone".
I thus decided to try to flash the phone from scratch.
First I tried to use ADB and Fastboot to make sure the bootloader is unlocked. Unfortunately, while ADB worked fine, I was never able to get Fastboot to see the phone, despite following the advice of several web pages addressing this issue, and trying several different drivers.
Pressing on, I decided to try to install TWRP again. Booted phone with VolDown, Home, Power. First I tried using Heimdall 1.4, both with drivers from Samsung, and then with the MSM8960 drivers that came with Heimdall, using this command:
heimdall flash --RECOVERY twrp-3.3.1-0-hlte.img --no-reboot
In both cases, all I got was "ERROR: Failed to access device. libusb error: -12"
Therefore, decided to try it with Odin. Booted phone with VolDown, Home, Power. Run Odin 3.12.4_4, which immediately shows "Added". Load TWRP 3.3.1.0 with AP button, click Start...and get a red Fail flag within a few seconds. Log shows "FAIL! (Auth). Phone shows "SYS REV CHECK FAIL: No Version" and "SECURE MAGICCODE CHECK FAIL: recovery".
I didn't even bother trying to flash the LineageOS ROM.
Can someone please tell me what I'm doing wrong? Please don't assume I know anything about what I'm doing.
--
*not an expert*
Verify that you are using the correct build of twrp-3.3.1.
I am using the hlte build of 3.3.1 on my phone (SCL22)... but my gut tells me that you and I wouldn't share the same build.
Nope basic problem is that OP is in the wrong forum for a Verizon phone .
Assuming that download mode still works (if it is, lucky you); I'd suggest reflashing the stock firmware for your Verizon device.
Flashing a stock firmware would *hopefully* fix your recovery and download issues.
Perhaps the errors you described may have been caused by installing the wrong ROM/firmware.
So, NEVER INSTALL/FLASH a custom or stock ROM that is not tested to work on your device. The main reason is because different variants of the same device (N9000, N900A, N900V) use different chipsets, software and drivers. Also, flashing a wrong ROM/kernel/firmware may cause application errors, boot loops, broken recovery/download mode, or a hard brick.

Bricked S7 Edge?

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

Categories

Resources