Related
Hi Guys,
today I wanted to flash the latest Stock ROM for my device via ODIN. I've done this many times before and (thought) I knew what I was doing. It is my third Phone frome the same carrier and none of them were branded/ locked devices before. Unfortunatly I wasn't aware that this particular device was locked.
After downloading the international firmware I tried to install it and ODIN got stuck while writing the system.img. After that my phone did not boot up (of course). After that I downloaded and tried to isntall the firmware of the carrier, but I had the exact same issue. When I turn my device on I get to an error screen which tells me to execute an "emergency recovery" via the Samsung smart switch software. But it too gets stuck on some point and only gets me to an error screen.
FRP hinders me to install a custom recovery and the stock one does not allow any isntallations via ADB or SD card.
My qustion is: Does anyone know how I can install a rom from here?
I know that I had to have made some changes prior to the flashing, but as I said I was not aware and an Idiot for not double checking.
Since it is not bricked yet I suppose there must be an answer but I can't find anything.
Thanks in advance
Edit:
After only installing the stock bootloader, I am autmaticly entering it when I boot my devive. On the bottom of the screen is an error message: "dm-verity verification failed...
E:failed to mount /system (invalid argument)"
Fix
For anyone in the same situation: I fixed it.
In the end all you have to do is flash the firmware with the fitting PIT file. If you firmware consists of multiple files and there is a "HOME"-file, flash it with this one first on the AP slot in ODIN. After that the same again just use the AP file this time.
My phone is up and running again now.
fabivons said:
hi guys,
today i wanted to flash the latest stock rom for my device via odin. I've done this many times before and (thought) i knew what i was doing. It is my third phone frome the same carrier and none of them were branded/ locked devices before. Unfortunatly i wasn't aware that this particular device was locked.
After downloading the international firmware i tried to install it and odin got stuck while writing the system.img. After that my phone did not boot up (of course). After that i downloaded and tried to isntall the firmware of the carrier, but i had the exact same issue. When i turn my device on i get to an error screen which tells me to execute an "emergency recovery" via the samsung smart switch software. But it too gets stuck on some point and only gets me to an error screen.
Frp hinders me to install a custom recovery and the stock one does not allow any isntallations via adb or sd card.
My qustion is: Does anyone know how i can install a rom from here?
I know that i had to have made some changes prior to the flashing, but as i said i was not aware and an idiot for not double checking.
Since it is not bricked yet i suppose there must be an answer but i can't find anything.
Thanks in advance
edit:
After only installing the stock bootloader, i am autmaticly entering it when i boot my devive. On the bottom of the screen is an error message: "dm-verity verification failed...
E:failed to mount /system (invalid argument)"
Click to expand...
Click to collapse
have u solved your problem ? This problem i am facing on the s7edge nougat ? Plz help ?
Hey,
look at the second post I made in this thread. There is described how I got my S7 up and running again. I'm not sure if it is a valid solution since it felt like trial and error to me, but I'm writing this text from my S7 so it might be worth a try!
Good luck!
Fabivons said:
Hey,
look at the second post I made in this thread. There is described how I got my S7 up and running again. I'm not sure if it is a valid solution since it felt like trial and error to me, but I'm writing this text from my S7 so it might me worth a try!
Good luck!
Click to expand...
Click to collapse
y i have done that and the device boots up but some applications force close and when i insert the memory card , the phone gets restarted everytime
Fabivons said:
For anyone in the same situation: I fixed it.
In the end all you have to do is flash the firmware with the fitting PIT file. If you firmware consists of multiple files and there is a "HOME"-file, flash it with this one first on the AP slot in ODIN. After that the same again just use the AP file this time.
My phone is up and running again now.
Click to expand...
Click to collapse
Tell us in detail now.
SjDU said:
Tell us in detail now.
Click to expand...
Click to collapse
"please"
I described everything I did in the posts before.
As soon as you can enter the system again all you need to do is deactivate the locks I was talking about in my first post and perform a full wipe.
After that you can install any ROM you want via ODIN just like you are used to.
If that doesn't work for you, I don't have any answers either.
But again:
Prep work:
1. Download most recent ODIN
2. Download the correct firmware for your carrier (from www.sammobile.com)
3. Download the correct PIT file for your device
4. Put your device in download mode
Process:
1. Extract your firmware if it is a zip
2. Start up ODIN
3. Connect your device and check if it's detected by ODIN
3. Put the PIT file in ODIN
4. Put the "HOME" file of your firmware in the PDA slot of ODIN
5. Press start
6. When finished unplug your device and restart phone and ODIN
7. Reconnect your phone and check if it's detected by ODIN
8. Put all the other files of your firmware + the PIT in the correct slot in ODIN
9. Press start
After that my device booted up but still was, as you described too, a little buggy. So I deactivated FRP, activated USB debugging in the dev options, installed TWRP, performed a full wipe and installed another firmware of my choosing via ODIN (without a PIT file this time).
I am running 7.0 on my device now and it works flawlessly.
Fabivons said:
"please"
I described everything I did in the posts before.
As soon as you can enter the system again all you need to do is deactivate the locks I was talking about in my first post and perform a full wipe.
After that you can install any ROM you want via ODIN just like you are used to.
If that doesn't work for you, I don't have any answers either.
But again:
Prep work:
1. Download most recent ODIN
2. Download the correct firmware for your carrier (from www.sammobile.com)
3. Download the correct PIT file for your device
4. Put your device in download mode
Process:
1. Extract your firmware if it is a zip
2. Start up ODIN
3. Connect your device and check if it's detected by ODIN
3. Put the PIT file in ODIN
4. Put the "HOME" file of your firmware in the PDA slot of ODIN
5. Press start
6. When finished unplug your device and restart phone and ODIN
7. Reconnect your phone and check if it's detected by ODIN
8. Put all the other files of your firmware + the PIT in the correct slot in ODIN
9. Press start
After that my device booted up but still was, as you described too, a little buggy. So I deactivated FRP, activated USB debugging in the dev options, installed TWRP, performed a full wipe and installed another firmware of my choosing via ODIN (without a PIT file this time).
I am running 7.0 on my device now and it works flawlessly.
Click to expand...
Click to collapse
the time when u were fixing your device , you were on marshmallow or nougat ? beacuse i am on nougat and whenever i flash twrp , it stucks there and not booting into it even i have ticked the oem unlock and usb debugging in developer mode ?
suhaibahmad said:
the time when u were fixing your device , you were on marshmallow or nougat ? beacuse i am on nougat and whenever i flash twrp , it stucks there and not booting into it even i have ticked the oem unlock and usb debugging in developer mode ?
Click to expand...
Click to collapse
Does the TWRP flash complete? Can you boot up the OS after you flashed TWRP? (And did you download the correct version of TWRP for your device?)
As a last resort, you could try and flash marshmallow on your device and see if it works there.
Fabivons said:
Does the TWRP flash complete? Can you boot up the OS after you flashed TWRP? (And did you download the correct version of TWRP for your device?)
As a last resort, you could try and flash marshmallow on your device and see if it works there.
Click to expand...
Click to collapse
if i flash marshmallow it doesnt even boot up and in the odin mode showing binary and everything as custom , if i flash nougat and then flash twrp and try to manually boot into twrp it stucks on the s7edge screen which comes before recovery , and if i boot the mobile normally without the button combination then it stucks on the second logo SAMSUNG . if i flash again the stock recovery then boots normally
suhaibahmad said:
if i flash marshmallow it doesnt even boot up and in the odin mode showing binary and everything as custom , if i flash nougat and then flash twrp and try to manually boot into twrp it stucks on the s7edge screen which comes before recovery , and if i boot the mobile normally without the button combination then it stucks on the second logo SAMSUNG . if i flash again the stock recovery then boots normally
Click to expand...
Click to collapse
Have you tried to perform a regular factory reset via the OS on nougat? Sometimes that does the job, too.
But as I said. I can only give you my best guess here - my phone worked after my procedure, so I didn't investigate further.
And don't forget: Google is your friend.
Fabivons said:
Have you tried to perform a regular factory reset via the OS on nougat? Sometimes that does the job, too.
But as I said. I can only give you my best guess here - my phone worked after my procedure, so I didn't investigate further.
And don't forget: Google is your friend.
Click to expand...
Click to collapse
thats your kindness , yes i have performed the factory reset several times from recovery , but when i trying to reset it from settings , it goes after restart to recovery with dm-verity error , then i wipe and factory reset from there
Fabivons said:
For anyone in the same situation: I fixed it.
In the end all you have to do is flash the firmware with the fitting PIT file. If you firmware consists of multiple files and there is a "HOME"-file, flash it with this one first on the AP slot in ODIN. After that the same again just use the AP file this time.
My phone is up and running again now.
Click to expand...
Click to collapse
Fabivons said:
"please"
I described everything I did in the posts before.
As soon as you can enter the system again all you need to do is deactivate the locks I was talking about in my first post and perform a full wipe.
After that you can install any ROM you want via ODIN just like you are used to.
If that doesn't work for you, I don't have any answers either.
But again:
Prep work:
1. Download most recent ODIN
2. Download the correct firmware for your carrier (from www.sammobile.com)
3. Download the correct PIT file for your device
4. Put your device in download mode
Process:
1. Extract your firmware if it is a zip
2. Start up ODIN
3. Connect your device and check if it's detected by ODIN
3. Put the PIT file in ODIN
4. Put the "HOME" file of your firmware in the PDA slot of ODIN
5. Press start
6. When finished unplug your device and restart phone and ODIN
7. Reconnect your phone and check if it's detected by ODIN
8. Put all the other files of your firmware + the PIT in the correct slot in ODIN
9. Press start
After that my device booted up but still was, as you described too, a little buggy. So I deactivated FRP, activated USB debugging in the dev options, installed TWRP, performed a full wipe and installed another firmware of my choosing via ODIN (without a PIT file this time).
I am running 7.0 on my device now and it works flawlessly.
Click to expand...
Click to collapse
Well I had the same issue but Odin method didn't work for me on Nougat. And also FRP lock was On. every time I flashed the files it give me FRP on error. so I had to use Smartswitch. Even though I used original csc and ap files with latest Odin. BTW I have SM-G935FD model
SjDU said:
Well I had the same issue but Odin method didn't work for me on Nougat. And also FRP lock was On. every time I flashed the files it give me FRP on error. so I had to use Smartswitch. Even though I used original csc and ap files with latest Odin. BTW I have SM-G935FD model
Click to expand...
Click to collapse
Well FRP has to be turned off (the button in the menu is called "OEM unlock, the button has to be set to on which deactivates FRP). You don't mention using a PIT file - did you use one?
●BRIEF INTRODUCTION :-
•Here Is All In One Guide For Various Flashing Processes For Samsung Galaxy Devices Using Windows PC
•Official Stock Firmware flashing Including Upgrading And Downgrading Firmwares Using Samsung Odin
Note :-
*Downgrading Of Stock Firmware Is Neither Officially Supported By Samsung Nor By Xda Community.
*Do It At Your Own Risk.
•Emergency Software Recovery Using Samsung SmartSwtich
•TWRP-Custom Recovery Flashing Using Samsung Odin
•CF-Autoroot-Root Tool Flashing Using Samsung Odin
●WHO SHOULD USE THE GUIDES :-
•Users Who Want To Manually Upgrade Their firmware to Higher Android Version OR Users Who want to Manually Downgrade Their firmware to Lower Android Version
•Users Who are facing Various DM-Verity/SW-Check Fail/Custom Binary Blocked by FRP/Bootloops Due to Flashing Wrong Custom Roms Or Mods Or Fixes etc. Hence Unfortunately Have to Flash Stock Official Firmware
•Users Who want to Install TWRP-Custom-Recovery
•Users Who want to Root their devices using CF-Autoroot-Root Tool
●REQUIREMENTS :-
•Samsung Device with OEM Unlocking And USB
Debugging Options Enabled from Developers Options
Note :-
To enable Developers Option Follow The Steps Below
*Go to Settings/About Device
*Press On Build Number For 6-7 Times until you see Developers Options Enabled Popup
*You will be able see Developers Options In Settings
*Go To Settings/ Find Developers Options Mostly At The End
•Device Should Be Charged upto 60-70% as Flashing Process May Sometimes Lengthens according to various Devices/Firmware Sizes As Well As Internet Connection Speed in case of SmartSwitch As It Uses Data For Downloading/Updating Firmwares Online
•Original Samsung OEM Usb Cable As Other Cables Would sometimes Give Device Not Recognized or Flashing Interrupted or Flashing Stuck At Certain Points like Errors
•Windows PC With Samsung Usb Drivers Installed According To your Device Model Number
LINK For Samsung Usb Drivers Download:-
https://androidmtk.com/download-samsung-usb-drivers
•Latest Samsung's Odin Tool For Windows PC
Note :-
*Extract Odin.rar Or Odin.zip to Specific Folder to get Odin.exe File
LINK For Samsung Odin Download:-
http://www.droidviews.com/download-odin-tool-for-samsung-galaxy-devices-all-versions/
• Samsung's Official SmartSwitch Tool For Windows PC
LINK For Samsung SmartSwitch Download:-
http://samsungsmartswitch.org/
Note :-
*If You want to use Odin Then install Odin Only on PC Or If You want to use SmartSwitch then install SmartSwitch Only On PC
*Simultaneous Appearance of Both Tools On PC will Sometimes May probably give Error while Flashing Firmwares through Odin
•Samsung Stock Official Firmware for Your Device Model Number/Country/CSC
LINKS For Samsung Official Stock Firmware Download:-
1)https://www.sammobile.com/firmwares/
2)http://samsung-updates.com/device/
3)http://updato.com/firmware-archive-select-model
4)https://androidmtk.com/download-samsung-stock-rom
Note :-
*The Downloaded Firmware should be Latest According to availability for Your Country
Since Some Courtiers Got Official 7.0 Nougat While Some Are Still Stucked At 6.0.1 Marshmallow Yet
*As well As Firmware should be accurate for Your Device Model Number/Country/CSC to avoid Further Flashing Errors Through Odin
•Trick of booting your Samsung Device into Download Mode using Hardware Key Configuration
Note :-
Follow Below Steps To Boot Your Device Into Download Mode
*Power Off your device
*Press Volume Down+Home+Power Buttons Simultaneously Untill You See Download Mode Window
*Press Volume Up Key To Continue To Download Mode
●CAUTION :-
No One Here Within XDA Community Including Me Will Ever Be Responsible For Bricked Devices
So Kindly Try Any Of Following Guide At Your Own Risk
●SAMSUNG ODIN FLASHING GUIDE TO FLASH STOCK OFFICIAL FIRMWARES ON SAMSUNG DEVICES FOR COMPLETE STOCK/UNROOTED EXPERIENCE
●IMPORTANT NOTE :-
This Guide Can Be Used For Both Upgrading And Downgrading Of Stock Official Firmwares
Only Precaution Should Be Taken Is That In Case Of Upgrading Firmware Kindly Choose Latest Dated Higher Version Of Android OS While In Case Of Downgrading Firmware Kindly Choose Latest Dated Lower Version Android OS Available For Your Device/Country/CSC
●INSTRUCTIONS :-
•As Per Requirements I assume You have
*Enabled OEM Unlocking And USB Debugging Options From Developers Options
*Downloaded/Installed Latest Samsung Usb Drivers For Your Device on PC
*Downloaded/Extracted/Installed Samsung Odin On Your PC
*Downloaded/Extracted Latest Official Stock Firmware For Your Model Number/Country/CSC
•Run Odin.exe as Administrator
•You Will See Odin Window with Various TABS like BL/AP/CP/CSC/UMS As Well As Certain Odin Options like Auto Reboot/F-Reset Time/Re-Partion/PIT File Add etc.
•Extract the Downloaded Stock Official Firmware in Specific Folder And You will get ***.tar.md5 like file of Stock Firmware in Specific Extracted Folder
•Add the Extracted ***.tar.md5 Firmware File in AP TAB of Odin
Note :-
*It will take Some Time to Add Firmware file into Odin According To Firmware Size
*So Keep Some Patience And Let Odin Ready For Flashing Process
•Be sure in Odin Options Only Auto-Reboot/F-Reset Time options are Ticked
•DON'T SELECT Re-Partion Or PIT File Add Options Unless Your Facing Null/Generic IMEI Or Baseband Unknown Related issues only
Note :-
*You Will Need to Download PIT files for Your Specific Device Model Numbers For Re-Partion of Partion Table In Case Of Null/Generic IMEI Or Baseband Unknown Issues
•Boot Your device into Download Mode Connect To PC using Original OEM Samsung Usb Cable Into Main Usb Port Of PC
Note :-
*Secondary Usb Hubs Sometimes May Produces error Of Device Not Recognized etc.
•Allow PC to install Samsung Usb Drivers for your Device
•You can see Your Device is added in Odin as its Highlighted in ID:COM Section on Left corner of Odin Windows
•Now your ready to flash Stock Firmware
Note :-
*ID:COM Will Look Like for eg. IDORT21 Etc.
•Press on Start Button in Odin, It will automatically start flashing process And You can see flashing log in Odin Side Window
•It will take some time to flash Stock firmware according to Device/Odin version/Firmware Size So Keep Some Patience And Stay Relax
•After flashing process gets complete, You will see "Pass" Message at the top of Odin Window
•Your Device will Reboot automatically
•Disconnect Your Device from PC
•Wait untill Software Updating/Installing Process Gets Completes on Device
•Afterwards Your device will Booup normally to Initial Setup Wizzard
•If In Case Your Device gets Stuck at Samsung Galaxy Logo For Long Time More than 10-20 minutes
Don't Worry Your Device Is in Soft BootLoop And There Is A Solution to fix it
Note :-
To Get Out Of Bootloop Follow The Steps Below
*Press Volume Down+Power Button Untill Screen gets Turned Off to Power Off Your Device
*Quickly Press Volume Up+Power+Home Buttons Simultaneously untill You See Samsung Galaxy Logo
*Release Keys Now
*You will Get Into Stock Recovery
*Select Wipe Data/Factory Reset Option There
*Wait Until Wiping Process get Completes
*After Wiping Process Get Completes Reboot your Device
*This time Your Device should BootUp normally without any issues
●SAMSUNG SMARTSWITCH GUIDE FOR EMERGENCY SOFTWARE RECOVERY ON SAMSUNG DEVICES
●INSTRUCTIONS :-
•Open Samsung SmartSwitch You have installed On Your PC
•You will see SmartSwitch Window
•Click On the More Option at the top Right Corner in SmartSwitch Window
•Select Emergency Software Recovery And Initialization Option From Menu
•You will See Emergency Software Recovery And Initialization Window
•Select Device Initialization Option
•You will be Asked to Enter Your Device Model Number
Note :-
*Device Model Number Should Be Like For Eg. SM-N920C/I/G/F
•In Next Step It will ask You to Enter Device Serial Number Which You Can Find Printed On OEM Original Box Or On the Back Panel Of Device Or In Settings> About Device> Status> Serial Number
Note :-
*Device Serial Number Should Like For Eg. RZ8G*****
•Click Ok For Approval Whenever It Will Be Asked Until You See Some Instructions Window in SmartSwitch
Note :-
*Instructions Should Look Like "Make Sure Your Device Is Turned Off/Put Your Device Into Recovery Mode i.e.Download Mode" Etc.
•Put Your Device into Download Mode As per Instructed Into 'REQUIREMENTS' Section Using Hardware Keys Configuration
•Connect Your Device to PC using Original OEM Samsung Usb Cable To PC
•Click On "OK" Button In Instructions Windows
•SmartSwitch Will Automatically Detect/Download/Install Latest Available Stock Official Firmware for Your Device
•Wait And Keep Patience Untill Whole Process is Being Completed
•Your Device will Reboot Automatically After Installation Process Completes Successfully
•If In Case Your Device Stuck at Samsung Galaxy Logo For Long Time More than 10-20 minutes Then Don't Worry Your Device Is in Soft Bootloop AND There is A Way to fix it
Note :-
To Get Out Of Bootloop Follow The Steps Below
*Press Volume Down+Power Button Untill Screen gets Turned Off to Turn Off Your Device
*Quickly Press Volume Up+Power+Home Buttons Simultaneously Untill You See Samsung Galaxy Logo
*Release Keys Now
*You will Get Into Stock Recovery
*Select Wipe Data/Factory Reset Option There
*Wait Until Wiping Process Get Completes
*After Wiping Process Get Completes Reboot Your Device
*This Time Your Device Should Bootup Normally Without Any Issues
●TWRP-CUSTOM-RECOVERY FLASHING GUIDE USING ODIN ON SAMSUNG DEVICES
●INSTRUCTIONS :-
•First Step is to Download Latest TWRP-Custom-Recovery For Your Specific Device Model Number
•You Can Grab Latest Version Of TWRP-Custom-Recovery From Official TWRP Website Below Posted
Note :-
*Select And Download Latest twrp***.img.tar File for Your Device Model Number Correctly
Official Website For TWRP-Custom Recovery Download:-
https://twrp.me/Devices/
•Open Odin On PC As Administrator And Add twrp***.img.tar into AP TAB of Odin
Note :-
*In case If You have downloaded twrp***.zip Then
Extract it to Specific Folder to get twrp***.img.tar file
•In Odin Options Be Sure To Un-Tick Auto-Reboot Option Also Don't Select Re-Partion Option
So Make Sure You Have Only Ticked F-Reset Time Option In Odin Options
Note :-
*If You Tick Auto-Reboot Option Then You will Get into Stock Recovery Again Even After flashing TWRP Using Odin
*So Better to Un-Tick Auto-Reboot Option And Manually Boot Into TWRP-Custom Recovery After Flashing Successfully By Hardware Keys Configuration
•Boot Your Device Into Download Mode And Connect To PC Using Original OEM Samsung Usb Cable
•You will See Your Device Is Added And Highlighted In ID:COM Port
•Click On "Start" Button In Odin And Wait Untill Odin will Flash TWRP-Custom-Recovery
After Flashing Completes Successfully You will See "Pass" Message In Odin
•Disconnect Your Device From PC Even if Its in Download Mode
•You Have To Boot Your Device Into TWRP-Custom-Recovery Manually By Using Hardware Keys Configuration
Note :-
To Get Into TWRP-Custom-Recovery Manually Follow The Steps Below
*Press Volume Down+Power Button To Turn Off Device
*Immediately Press Volume Up+Power+Home Buttons simultaneously After Device Screen Gets Turned Off
*You Will See Samsung Galaxy Logo
*Release Keys Now
•Your now in TWRP Recovery And Ready To Flash
*Custom Roms/Mods/Fixes
*Systemless SuperSU/Magisk Root Zips
Note :-
*If Your Planning To Flash Any Custom Roms/Mods/Fixes Or Systemless SuperSu/Magisk Root Zips Files Using TWRP
*Then Make Sure You Have Downloaded Those Files And Saved Them Already Into Your Internal Storage/External SD-Card Before Flashing TWRP-Custom-Recovery
●CF-AUTOROOT- ROOT TOOL FLASHING GUIDE USING ODIN ON SAMSUNG DEVICES
●INSTRUCTIONS :-
•First Step Is To Download Official CF-Autoroot-Root Tool For Your Device Model Number According To Android Version And Build Number
•You Can Download Official CF-Autoroot-Root Tool for Your Device Model Number And Android Version From Official Website Listed Below
Official Website For CF-Autoroot-Root Tool Download:-
https://autoroot.chainfire.eu/
•Extract CF-Autoroot.Zip in Specific Folder to get CF-Autoroot.tar file to be Flashed Using Odin
•Open Odin On PC As Administrator And Add CF-Autoroot.tar into AP TAB of Odin
•Make Sure To Tick Only Auto-Reboot And F-Reset Time Options In Odin Options
Dont Tick Re-Partion Option In Odin Options
•Put Your Device Into Download Mode And Connect To PC Using Original OEM Samsung Usb Cable
•You Will Eee Your Device Is Added And Highlighted In
ID:COM Port
•Click On "Start" Button In Odin
Wait Untill Odin will flash CF-Autoroot
You See "Pass" Message In Odin After Successful Flashing
•Your Device Will Reboot Automatically After Flashing Completes
Disconnect It From PC
You Wipl See On Device Screen That CF-Autoroot is Rooting Your Device
Note :-
*You Will See Some Red Command And Process Logs On Your Device Screen While CF-Autoroot Is Rooting Your Device
•Keep Patience untill Rooting process completes
Don't Turn Off Device while Process is going on Even if it will lead to some BootLoops
Your device will Reboot Automatically after Rooting Process completes.
•You Will See SuperSU Wpp In Default App-Drawer After Your Device Bootup
Could you tell me even though i took ota update to naugat, if i could downgrade back to marshmallow by flashing throught odin?, and if i do what could happen if anything?
desmond462 said:
Could you tell me even though i took ota update to naugat, if i could downgrade back to marshmallow by flashing throught odin?, and if i do what could happen if anything?
Click to expand...
Click to collapse
1)To be say honestly downgrading is not officially supported by Samsung also But yes you can successfully downgrade to 6.0.1 from 7.0 (I personally downgraded to 6.0.1 once successfully due to issues on stock 7.0)
2)You only need to follow the guide as instructed carefully Also the version of 6.0.1 MM you will choose to downgrade to should be latest dated (I mean the latest 6.0.1 firmware for your device and country available on Sammobile.com casually)
3)Hence you can find some instructions within my own Post in which i mentioned step by step installations instructions (Go To Page No 65 And Find My Post In Reply To Okiera29 There Regarding Downgrading To MM From Nougat)
https://forum.xda-developers.com/note5/help/help-thread-question-noob-friendly-t3220229/page65
DayDreamer said:
1)To be say honestly downgrading is not officially supported by Samsung also But yes you can successfully downgrade to 6.0.1 from 7.0 (I personally downgraded to 6.0.1 once successfully due to issues on stock 7.0)
2)You only need to follow the guide as instructed carefully Also the version of 6.0.1 MM you will choose to downgrade to should be latest dated (I mean the latest 6.0.1 firmware for your device and country available on Sammobile.com casually)
3)Hence you can find some instructions within my own Post in which i mentioned step by step installations instructions (Go To Page No 65 And Find My Post In Reply To Okiera29 There Regarding Downgrading To MM From Nougat)
https://forum.xda-developers.com/note5/help/help-thread-question-noob-friendly-t3220229/page65
Click to expand...
Click to collapse
Ok thank you for your reply, I understand. I also had some trouble with drk verity fail issue when I factory reset because I run into issue with my efs, it was failing to boot ,but after searching the internet I found out how to fix the efs issue and then I flash stock over and then run into trouble with drk verity fail issue, but found a script to bypass this error ,but I read that whenever I flash or factory reset I will run into this drk verity fail issue again, so I must flash this script to bypass this error.
So my question after all i have explain is, will it be a problem to downgade to 6.0 because of those previous issues ?
desmond462 said:
Ok thank you for your reply, I understand. I also had some trouble with drk verity fail issue when I factory reset because I run into issue with my efs, it was failing to boot ,but after searching the internet I found out how to fix the efs issue and then I flash stock over and then run into trouble with drk verity fail issue, but found a script to bypass this error ,but I read that whenever I flash or factory reset I will run into this drk verity fail issue again, so I must flash this script to bypass this error.
So my question after all i have explain is, will it be a problem to downgade to 6.0 because of those previous issues ?
Click to expand...
Click to collapse
1)Can't say exactly without trying or downgrading firmware as i said already neither samsung nor any community will officially support downgrading of firmware as it may cause various baseband and imei related issues due to downgrading of bootloader
2)But for safety you can take full Nandroid backup of your current stable rom using TWRP and Try to downgrade firmware at your own risk
Regards
DayDreamer said:
1)Can't say exactly without trying or downgrading firmware as i said already neither samsung nor any community will officially support downgrading of firmware as it may cause various baseband and imei related issues due to downgrading of bootloader
2)But for safety you can take full Nandroid backup of your current stable rom using TWRP and Try to downgrade firmware at your own risk
Regards
Click to expand...
Click to collapse
ok thank you. So i end up downgrading back to marshmallow and i did run into the issue with drk and i flash the script to bypass that error and boot up successfully, but at the moment am searching for a fix to the drk failing on the internet, i found that alot of persons have run into this problem, but i see wat i can find.
desmond462 said:
ok thank you. So i end up downgrading back to marshmallow and i did run into the issue with drk and i flash the script to bypass that error and boot up successfully, but at the moment am searching for a fix to the drk failing on the internet, i found that alot of persons have run into this problem, but i see wat i can find.
Click to expand...
Click to collapse
You can find more information in below listed thread about DM-verity with DRK check
https://forum.xda-developers.com/note5/help/how-to-solve-dm-verity-verification-t3293306
Gr3atGeek said:
•You will See Emergency Software Recovery And Initialization Window
•Select Device Initialization Option
Click to expand...
Click to collapse
What version of Smart Switch offers initialization for SM-N920C Note 5's? The latest version doesn't include initialization anymore at all, and an older version I tried stated that initialization was not supported for Note 5's.
All right, I'll see what i do.
Thank you very much.
Here's another rooting guide for SM-J530F/DS (Dual Sim) stock ROM. Even with Lineage OS my hardware model (ordered March 2018, EU SIM card only) tends to mute the main speaker after rooting. This rooting method works for me and is based on the work of others, especially ananjaser1211 and Abdullah_a86.
Make a backup of everything and make sure that the backup is usable. You are responsible if following this description and flashing bricks your phone. It did work for me which does not mean that it also works for you.
Enable Developer options. (Settings, About phone, Software information, tap a few times on Build number)
OEM unlock the phone. (Settings, Developer options, OEM UNLOCK: enable - otherwise you will bootloop)
Reboot into download mode.
Flash J530F_TWRP_3.2.1.0.tar (in AP) with Odin.
Now TWRP is installed and you should be able to use your phone as usual or to boot into TWRP recovery.
Rooting will erase everything, verify your backup again unless this is a new phone.
Reset the phone. (Open Settings, About Phone, (Looking for something else?) RESET, Factory data reset, Reset, DELETE ALL)
Reboot into recovery, a cleanup script will run and reboot after a few seconds.
Reboot into recovery again, install SuperSu and reboot (wipe nothing).
Starting takes a little time, after running the initial setup SuperSU is installed and the speaker works as expected.
I started here a few times after no-sound, no-root and/or bootloop experiences with LineageOS, CF-Autoroot and Magisk. If you upgrade to this firmware version you can no longer downgrade to a previous firmware version. Follow this only if you break something, want to un-root, update your firmware and/or start from scratch:
Force a reboot if necessary and then boot into download mode. All data on the phone will be lost.
Flash the J530FDBT2ARB3 firmware with Odin (AP*, BL*, CP* and CSC*. Do not use HOME_CSC*).
Now you have again a phone with stock firmware without root.
Links:
Odin (3.12.3): https://samsungodin.com/download/
TWRP (3.2.1-0): https://forum.xda-developers.com/ga...twrp-samsung-j5-pro-twrp-3-1-10-v2-0-t3728233
SuperSU (2.82): https://forum.xda-developers.com/ga.../guide-root-samsung-galaxy-j5-pro-sm-t3720446
Optional (also older firmware or a firmware backup may be used):
Firmware (Android7 J530FDBT2ARB3 2018-02-08): https://www.sammobile.com/firmwares/galaxy-j5/SM-J530F/DBT/download/J530FXXU2ARB3/210251/
Hints:
Power+Home+VolumeUp = Recovery
Power+Home+VolumeDown = Download Mode
Power+VolumeUp+VolumeDown = Force Reboot
PS: If a mod wants to move the thread to https://forum.xda-developers.com/ga...17-roms-kernels-recoveries--other-development please just do it and remove this comment. My reputation is too low to post there.
Hello, could you help me ? Odin doesn't recognize it, pc shows drivers being installed, but nothing shows up on odin, tried different version of odin.
aofthe said:
Hello, could you help me ? Odin doesn't recognize it, pc shows drivers being installed, but nothing shows up on odin, tried different version of odin.
Click to expand...
Click to collapse
Enable OEM unlock and USB debugging in developer options
garylawwd said:
Enable OEM unlock and USB debugging in developer options
Click to expand...
Click to collapse
Yeah, they were already enabled.
Hello again, i managed to fix Odin problem, it installed Twrp and said pass, with green, but when i tried to enter recovery mode, it went downloading, and the no command, phone boots normally, but i got no recovery, any suggestions ?
Download Mode Fix
aofthe said:
Hello again, i managed to fix Odin problem, it installed Twrp and said pass, with green, but when i tried to enter recovery mode, it went downloading, and the no command, phone boots normally, but i got no recovery, any suggestions ?
Click to expand...
Click to collapse
I think this might fix you booting into download mode problem try this post. Read "how to fix" near the bottom. Please Thank us if it does. This same thing happened to me and I wish I stumbled across this earlier because I figured this out on my own by just messing around going from recovery to download mode and it eventually fixed itself.
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
hi all my grandson cannot remember his login info for his tablet, so i went and followed the instructions below I got to step 5 and could not get it to download recovery or turn it on.
After flashing the combo file there was a screen said factory binary but it would not load past that so i followed the steps and did a factory recover. the samsung logo came on but again it just went on to the factory binary screen. so i turn it off but would not turn back on. What can I do I have been out of the scene for a bit, I remember with the note 3 and 4 you could use a download jig to force it to download mode. I tried that but nothing happens. Any help would be greatly appriciated.
I have successfully Unlocked my SM-T377W from Rogers Canada on 7.1.1
I have been Struggling for a while to Unlock the FRP from this device and finally done it
Now its unlocked and I can use whatever sim card i want also
Successfully Unlocked FRP of my SM-T377W from Rogers Canada on 7.1.1
I have successfully Unlocked my SM-T377W from Rogers Canada on 7.1.1 I have been Struggling for a while to Unlock the FRP from this device and finally done it Now its unlocked and I can use whatever sim card i want also So I have used these 2...
forum.xda-developers.com
So I have used these 2 files [IT IS IMPORTANT TO USE THE CORRECT COMBINATION AND CORRESPONDING STOCK], maybe you can use the same ones I have used if you do not have a choice
1- Combination "COMBINATION_OYA_FA60_T377WVLU3ARG1"
2- Stock ROM "Firmware SM-T377W T377WVLU3BRG4 [7.1.1]"
So what I have basically done,
1- Turn the device off and put the device in DOWNLOAD MODE
2- Flash the Combination Firmware to your device with Odin
3- When the device restarts and it runs the Combination firmware, turn it off again and put it in "RECOVERY MODE" not download, and in "RECOVERY MODE" do factory reset wipe and click yes then It will restart or maybe shut off
4- Turn it on again normally and it will run the Combination firmware
5- Now Turn it off again and put in "DOWNLOAD MODE" this time
6- From the Stock ROM extract the 3 files (boot, sboot and system) from inside the files of the stock ROM, you will find them inside "AP" and "BL" (cause we have BL, AP, CP, CSC), you need to use 7-zip so you can extract whats inside them
7- Create new file/archive (it will be .tar) using 7-zip with these 3 files (boot, sboot and system)
9- Flash the new file you made .tar (that has the 3 files) in the AP section in Odin.
10- Your done