Hi All, I'm in desperate need of some help. For the past few days I've been going down the road of getting the latest Phoenix ROM working properly and I've been taking a step backwards with everything I've attempted, now I'm stuck at a soft-brick stage on my i9505
My current issue:
I can get into download mode. Not recovery, definitely not boot, only download mode.
Odin correctly identifies the phone but attempts to flash to the phone fail. It spits out the following:
Code:
<ID:0/005> NAND Write Start!!
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The phone then shows the progress bar completely stalled either at what looks like 99% for small writes (Like my attempt to flash TWRP), or at what looks like 1% (when I flash a full firmware). When I get home tonight I'll list the codes on the screen when it does it but I see a "START", and a "BBA" (I think), but I never get to the "END" command.
Has anyone experienced something similar?
What got me to this stage:
1. Flashed new Phoenix rom v10 upgrading from v9.4.
2. On sleep the cell dropped out constantly and so did WiFi so someone suggested I install a WiFi fix.
3. Installed the modem for XXUGNJ8 (I think). Combined package for LTE and GSM.
4. Every time the modem activated the phone had problems. Locked up when I open the phone app, reboot if someone called me, no sound when calls did "work", and the phone never sleeps and chews the battery after a simple text message.
5. Attempted to revert modem to XXUEMK4 (the other Galaxy S4 still on stock Android 4.3 had this modem). FAILED!
At this point my phone said the last firmware update failed and I was effectively in a softbrick scenario. I can still get into download mode.
6. Attempted to flash Optus carrier firmware 4.4.2 XXUGNH6. This failed, but the download screen changed now and says Samsung Official Firmware on it.
All other attempts to write to the phone have failed.
I've tried a different USB cable.
I've tried a different version of Odin.
I've tried flashing TWRP.
I tried installing Heimidall but have yet to get it working. (Visual studio runtime issues).
I installed Keis just to waste a bit of time.
I tried reinstalling drivers.
I just can't seem to write to the phone. Has anyone experienced anything similar and figured out a fix? When I get home tonight I'll post some pictures / screenshots of the errors I'm getting.
Cheers.
Are you trying to flash an older version of 4.4.2 that you had downloaded earlier?
Flash the LATEST 4.4.2 version for your phone.
"If someone helps, never forget to hit thanks ?"
Latest for my carrier? Or the latest version of stock there is?
By the way for the record here's some more info. Attached is a screenshot of my Odin after it fails. This was after attempting to install Philz recovery.
My phone has the following on the screen:
Code:
Odin MODE
Product Name: GT-i9505
Current Binary: Custom *note this said Samsung Official yesterday
System Status: Custom
Knox Kernel Lock: 0xfffffffc
Knox Warranty Void: 0xfffffffc
CSB-Config-LSB: 0x30
Write Protection: Enable
eMMC Burst Mode: Enable
and then the bits from the actual download attempt:
Code:
START [224, 1448]
BAR [240,1440]
That's it. The progress bar is sitting at what looks like the 99% mark.
No sure if this will help but I solved my issues by running odin as admin and make sure usb debugging is ticked.
I don't see you tried a different usb port/different pc.
For using heimdall your don't need the frontend interface. You only need to make sure you use the correct drivers for heimdall and then use the terminal to flash the recovery.
"heimdall flash --recovery recovery.img --no-reboot" (it's case sensitive.)
Ok success.
I used the i9505 pit file and re-parition and with that I can successfully flash twrp or philz recovery. Which brought up an error saying non-official firmware detected.
I tried flashing XXUGNJ8 downloaded straight from Samfirmware but it failed. I tried it both with and without repartitioning.
So I tried twrp again and failed.
Then I tried XXUGNJ8 again and it failed but got all the way to the image stage.
I read about swapping cables, drivers, USB ports, well I did all of that to no avail.
Finally I took the entire mess to work and used a new computer there, fresh drivers, fresh everything, and everything worked just fine. I have no idea what's wrong with my computer, but it was not happy.
Thank god these phones are hard to brick. I'm willing to bet my USB connection dropped out while flashing which caused the issue to begin with.
Dear fellows kindly help my problem here.
days ago due to "intune" app by microsoft office 365, my j530y need to unroot, and somehow the intune app reads my stock rom as custom rom.
so i download and flash this "SM-J530Y - J530YDXU3BRH6 XID" from Ymobile site.
everything working just fine (in my opinion), until i tried to flash twrp and try to root. NOTHING WORKED, i tried several twrp tar and cf autoroot also fail.
the notifications are :
1. "Only official released binaries are allowed to be flashed(RECOVERY)"
ID:0/010> Odin engine v(ID:3.1301)..
<ID:0/010> File analysis..
<ID:0/010> Total Binary size: 22 M
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> NAND Write Start!!
<ID:0/010> SingleDownload.
<ID:0/010> recovery.img
<ID:0/010> RQT_CLOSE !!
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Code:
Click to expand...
Click to collapse
2. i tried to downgrade to marshmllow/nougat and this error appear: "SW REV. CHECK FAIL (BOOTLOADER) DEVICE:3 BINARY:2"
3. last resource was just trying to flash custom rom (breeze+) which packed in zip file. the problem is when i want to flash it in the stock recovery, the process failure "can't mount /sdcard"
so please guys help me, i already browse several threads and days for downgrading this, but nothing cant pass this error message "SW REV. CHECK FAIL (BOOTLOADER) DEVICE:3 BINARY:2
please help,
im not a rich guy, but i will share a bit of my money to anybody give me the proper solution
Thank you in advance:crying:
hacker812c said:
[RMM] RMM State Fix Oreo 8.1 OEM Unlock Fix Dez 2018
This for users with RMM State or OEM Unlock Fix
And for users install custom ROM after Oreo 8.xx
[IMPORTANT]
With this tutorial you can reactivate de OEM unlock Option
TO install twrp or Downgrade to 7.0 nougat
Or install Custom ROM Oreo
[FILES]
#Samsung drivers
#Latest Stock firmware 8.x from Sammobile
#Odin any release after 3.x
#Miracle box 2.85
[NOTE:]
Back up your IMPORTANT files in your phone.
[STEPS]
1. install samsung drivers
2. Disable antivirus and Charge your Battery J7
3. Extract miracle all zip files
4. Run miracle box loader (run as admin)
5. Set your time to 2 years past.
6. Then close miracle box.
7. Open miracle box loader again (you will see miracle box is working now)
8. Connect the phone.
(Always check the phone. if there something pops up, tick "always allow" then "allow") i start Miracle Box_Cracked 2.58 and select Try to 3 options
9. Click "Connect" button on the top left side on miracle box
10. Click "Samsung tab" on the miracle box
11. Click Scan on the top right corner
12. Set the mode selection into : Download then hit "Go" button you will notice that your phone is on download mode and its blank. Just let it be on that state its on the process right now.
13. Click on "Reset Reactivation/EE Locks
14. Hit " Start button" and now its on the process.
15. Reboot the phone in download just hold synchronously press vol - , home button , and power then wait until you get again in the selection and then select "Continue". As you can see there's no more RMM State: prenormal in info. It means you're almost there..
16. Flash Stock 8.1 via Odin.
17. Enter in Stock Recovery and Factory Reset
18. Install TWRP and install Custom ROM
[CHECK ON STOCK]
After reboot Oreo
Steps on Check REMOVING RMM
Setup your phone
You're done.. Check Dev Options and you see "OEM Toggle".
[NOTICE]
After flash Fix is normal
You will see error on the miracle.
That's okay you're almost there to get rid of it.
[LINKS]
Miracle Box:
https://www.techeligible.com/2018/04/03/download-miracle-2-58-with-loader/
https://drive.google.com/file/d/1n_UGxEEmvJFGym0li05GH5tw087_7GjW/view
Hacker812c
The secret of my success is Jesus
Dedicated To Sabrina Mello (2015)
Click to expand...
Click to collapse
Hi all,
My J530Y oem unlock didnt show, rmm state prenormal, cant do anything to root or do more than stock users do basically.
ive been aimlessly crying for help and waiting if there's any update..ive been searching for this answer from July 2018.
So here's why i can work it out:
1. i read this thread just today, and realized there's some miracle called miracle box
2. i used miracle box to "RESURFACE" the OEM Unlock toggle in developer mode (3 times i fail, realized i have to use the newest stock rom of 8.1, indonesian region you can find it here) using odin until i make the oem unlock re-appear (this stock firmware is just temporary so at the end i replaced it with custom rom Breeze+)
3. im using twrp from here, countless time failure until i realized i should really read the guide to flash the twrp in odin, notice no7 that you have to untick auto reboot. read through and it should work!
4. last problem in twrp was it cant mount data partition, the solution is here, notice the faq part
5. so TWRP done, the next thing i do was installing these files in TWRP from OTG >RMM State Lock fix, and no-verity-opt-encrypt-6.0.zip
6. Last, im installing Breeze+ Also in TWRP and still using OTG. (i prefer using this because its prerooted with magisk, which is nice because i need the Intune Hider4magisk so i still can work freely with rooted device
7. I never "REBOOT SYSYEM" from step 4 to 6, since i tried and just realized need to install the custom rom at no6.
Might this help for my fellow J530Y users whose had the same problem as me.
Thank you all.
em. said:
Dear fellows kindly help my problem here.
days ago due to "intune" app by microsoft office 365, my j530y need to unroot, and somehow the intune app reads my stock rom as custom rom.
so i download and flash this "SM-J530Y - J530YDXU3BRH6 XID" from Ymobile site.
everything working just fine (in my opinion), until i tried to flash twrp and try to root. NOTHING WORKED, i tried several twrp tar and cf autoroot also fail.
the notifications are :
1. "Only official released binaries are allowed to be flashed(RECOVERY)"
2. i tried to downgrade to marshmllow/nougat and this error appear: "SW REV. CHECK FAIL (BOOTLOADER) DEVICE:3 BINARY:2"
3. last resource was just trying to flash custom rom (breeze+) which packed in zip file. the problem is when i want to flash it in the stock recovery, the process failure "can't mount /sdcard"
so please guys help me, i already browse several threads and days for downgrading this, but nothing cant pass this error message "SW REV. CHECK FAIL (BOOTLOADER) DEVICE:3 BINARY:2
please help,
im not a rich guy, but i will share a bit of my money to anybody give me the proper solution
Thank you in advance:crying:
Click to expand...
Click to collapse
You have to wait for a week to flash twrp. Its a part of the Oreo update that the bootloader remains locked for 7 days
garylawwd said:
You have to wait for a week to flash twrp. Its a part of the Oreo update that the bootloader remains locked for 7 days
Click to expand...
Click to collapse
hi,
i kept my phone awake for 3 weeks and no UEM unlock on devlpr option, do u know why ?
i keep searching for some threads that actually got the uem unlock option in just one week, but not mine.
help.......
Same problem here on G570M.
Does anybody know if Oreo bootloader lock with olders Security patch can be bypassed changing date and making manual updates? I'm stucked right here.
em. said:
Dear fellows kindly help my problem here.
days ago due to "intune" app by microsoft office 365, my j530y need to unroot, and somehow the intune app reads my stock rom as custom rom.
so i download and flash this "SM-J530Y - J530YDXU3BRH6 XID" from Ymobile site.
everything working just fine (in my opinion), until i tried to flash twrp and try to root. NOTHING WORKED, i tried several twrp tar and cf autoroot also fail.
the notifications are :
1. "Only official released binaries are allowed to be flashed(RECOVERY)"
2. i tried to downgrade to marshmllow/nougat and this error appear: "SW REV. CHECK FAIL (BOOTLOADER) DEVICE:3 BINARY:2"
3. last resource was just trying to flash custom rom (breeze+) which packed in zip file. the problem is when i want to flash it in the stock recovery, the process failure "can't mount /sdcard"
so please guys help me, i already browse several threads and days for downgrading this, but nothing cant pass this error message "SW REV. CHECK FAIL (BOOTLOADER) DEVICE:3 BINARY:2
please help,
im not a rich guy, but i will share a bit of my money to anybody give me the proper solution
Thank you in advance:crying:
Click to expand...
Click to collapse
same problem on SM-J530G
renguer0 said:
Same problem here on G570M.
Does anybody know if Oreo bootloader lock with olders Security patch can be bypassed changing date and making manual updates? I'm stucked right here.
Click to expand...
Click to collapse
WandresJersey said:
same problem on SM-J530G
Click to expand...
Click to collapse
Have you guys had any solution to this?
em. said:
Have you guys had any solution to this?
Click to expand...
Click to collapse
Just seven days waiting. There is a patch when unlocking bootloader that able to unlock without this trouble.
em. said:
Dear fellows kindly help my problem here.
days ago due to "intune" app by microsoft office 365, my j530y need to unroot, and somehow the intune app reads my stock rom as custom rom.
so i download and flash this "SM-J530Y - J530YDXU3BRH6 XID" from Ymobile site.
everything working just fine (in my opinion), until i tried to flash twrp and try to root. NOTHING WORKED, i tried several twrp tar and cf autoroot also fail.
the notifications are :
1. "Only official released binaries are allowed to be flashed(RECOVERY)"
2. i tried to downgrade to marshmllow/nougat and this error appear: "SW REV. CHECK FAIL (BOOTLOADER) DEVICE:3 BINARY:2"
3. last resource was just trying to flash custom rom (breeze+) which packed in zip file. the problem is when i want to flash it in the stock recovery, the process failure "can't mount /sdcard"
so please guys help me, i already browse several threads and days for downgrading this, but nothing cant pass this error message "SW REV. CHECK FAIL (BOOTLOADER) DEVICE:3 BINARY:2
please help,
im not a rich guy, but i will share a bit of my money to anybody give me the proper solution
Thank you in advance:crying:
Hi all,
My J530Y oem unlock didnt show
Thank you all.
Click to expand...
Click to collapse
Thank for reply
If twrp correctly installed and internal memory not encrypt is possible flash any rom
Two problems
1 sd encrypt
2 OEM unlock and RMM state
I searching solution for You
Hacker friend
---------- Post added at 10:33 AM ---------- Previous post was at 10:22 AM ----------
renguer0 said:
Just seven days waiting. There is a patch when unlocking bootloader that able to unlock without this trouble.
Click to expand...
Click to collapse
So i will not go back to official rom
Samsung stupid software
Hacker
hacker812c said:
Thank for reply
If twrp correctly installed and internal memory not encrypt is possible flash any rom
Two problems
1 sd encrypt
2 OEM unlock and RMM state
I searching solution for You
Hacker friend
---------- Post added at 10:33 AM ---------- Previous post was at 10:22 AM ----------
So i will not go back to official rom
Samsung stupid software
Hacker
Click to expand...
Click to collapse
See last post mine on TWRP thread. I've posted a solution to this.
If you have your phone briked you can upload stock rom from odin. Take care about the version, you can't downgrade.
renguer0 said:
See last post mine on TWRP thread. I've posted a solution to this.
If you have your phone briked you can upload stock rom from odin. Take care about the version, you can't downgrade.
Click to expand...
Click to collapse
Very important this information
Thank You
Report below => text form post @Renquer0 (thanks)
About TWRP => Error on twrp installing any zip rom, magisk or kernel
When ENCRYPTION message is showed when booting DON'T CLICK IN RESET.
You need to enable data partition (guide quoted) and then install Magisk,
RMM State Bypass and no-verity-opt-encrypt-6.0 files in that order.
This is the entire quoted post:
renguer0 said:
For everyone that can't mount or format data (this f**k up the entire rooting process) you can follow this:
sharneil said:
While formatting device using TWRP re., device failed and showed me something like "unable to mount /data or system"
This happens because your recovery is unable to read internal storage. You need to do some small steps.
Steps
1) Reboot into TWRP recovery
2) go to " Wipe "
3) then " Advanced Wipe "
4) Choose " data " and tap on " Repair or Change File System "
5) Then tap " Change File System "
You will see text as ext4 infront of ' file system '
6) Change it to "EXT2" by tapping and swiping.
7) Once its done, change it to "EXT4" again.
(if some detail doesn't match after step 5, don't worry... Change file system path to something else then and to default again.)
DONE !
Then go back and try formatting ( or any other work ). It should succeed.
This method worked for me where I was using Redmi Note 4 with custom(Lineage) os and TWRP 3.2.3.0
If this doesn't work, then try once again or I will suggest you to install TWRP recovery again.
Thank you.
Click to expand...
Click to collapse
Maybe the OP can add it to the first post. This allowed to me to install TWRP and Magisk in my J5 Prime.
When ENCRYPTION message is showed when booting DON'T CLICK IN RESET. You need to enable data partition (guide quoted) and then install Magisk, RMM State Bypass and no-verity-opt-encrypt-6.0 files in that order.
Click to expand...
Click to collapse
Hope it helps. In my case I couldn't format data partition in TWRP until I changed filesystem to EXT2 and EXT4.
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