Related
My Fried gave this phone to me (SM-N915G) which is stuck at Powered by Android, and told me to fix it.
He said that when he update to MM from LP without KIES or Odin, the phone suddenly restarted and stuck there getting HOT
He had no experiece to repair it so he asked me to fix it.
So for 3 days lately, i have tried many ways to fix it but wihout any progress, as follow :
1. Flashing Official MM wby using Odin -> still stuck
2. Downgrading Flash Official LP using Odin -> still stuck
3. Installed TWRP, and flasing CFW Micky387_MM_V3.0 for 915F/FY/G (flashing Bootloader and modem as required) -> still stuck with set warranty bit : kernel
4. After Flashing Micky CFW and Failde, i try to flash Emotion Kernel -> still stuck with Kernel is Seandroid Enforcing
5. Redoing Flash Micky CFW with other CSC -> Still Stuck (even i tried with 915F and 915FY as in the aroma installer)
6. Never failed during flash procedure with Odin or TWRP, everything is smooth
7. When stuck, the device is getting Hot slowly but and when left as long as 15 minutes, the HH is getting HOT (TWRP read 72 degree at most)
**Update
8. Tried using Official SmartSwitch sucessfully but the result is still the same -> Still Stuck and getting hot as usual T.T
Last Download Mode status is :
Odin Mode (High Speed)
Product name: SM-N915G
Current Binary: Samsung Official
System Status: Official
Reactivation Lock: Off
Knox warranty void: 0x1 (2)
Quallcomm secureboot : Enable (CSB)
RP SWREV: S1, T1, R1, A1, P1
Secure Download: Enable
UDC START
I am now thinking, should i flash another Kernel or PIT or Bootloader? but i still cant decide what to do next to revive this Phone
Please help, any suggestion is greatly appreciated, thank you.
Please give some help, thank you.
Help Please anyone?
This is Hard Brick or Soft Brick?
Any suggestion or Opinion please
Thank you
wingz17 said:
Help Please anyone?
This is Hard Brick or Soft Brick?
Any suggestion or Opinion please
Thank you
Click to expand...
Click to collapse
Have you tried a reinstall using KIES?
The Radius Kid said:
Have you tried a reinstall using KIES?
Click to expand...
Click to collapse
Yes i have try to recover but not using KIES, but using smartswitch...
Is it diffrent by using KIES or SmartSwitch?
Thank you.
wingz17 said:
Yes i have try to recover but not using KIES, but using smartswitch...
Is it diffrent by using KIES or SmartSwitch?
Thank you.
Click to expand...
Click to collapse
I can tell you that Kies and NOT Kies 3 was what worked for me when I downloaded/installed Marshmallow from Samsung's website.
Figure that one out.
That was also using a 64 bit version of Windows 7 Pro.
The Radius Kid said:
I can tell you that Kies and NOT Kies 3 was what worked for me when I downloaded/installed Marshmallow from Samsung's website.
Figure that one out.
That was also using a 64 bit version of Windows 7 Pro.
Click to expand...
Click to collapse
Thank you for the suggestion,
I will try that one out and let you know.
wingz17 said:
Thank you for the suggestion,
I will try that one out and let you know.
Click to expand...
Click to collapse
The Radius Kid said:
I can tell you that Kies and NOT Kies 3 was what worked for me when I downloaded/installed Marshmallow from Samsung's website.
Figure that one out.
That was also using a 64 bit version of Windows 7 Pro.
Click to expand...
Click to collapse
Sorry For the long response, i have tried flasing using KIES but still stuck on the android, and no progress.
Right now i am run out of option, please help, thank you.
wingz17 said:
Sorry For the long response, i have tried flasing using KIES but still stuck on the android, and no progress.
Right now i am run out of option, please help, thank you.
Click to expand...
Click to collapse
I'm going to guess that you've tried installing MM using Kies directly from Sammobile?
If so,have you tried turning off your computer's antivirus when you download/install?
It sounds like the bootloader is looking for something and can't find it.....kind of like what happened to me when I totally ripped KNOX out of my phone.
Restore time!
Good thing I did CWM backups.
In your case,your computer's anti virus could be seeing something in the download and ripping it out.
I've seen my browsers do that when I download stuff....pain in the....
Have you tried a different battery?
Maybe a search of the forums to see if anyone else has had this problem and solved it?
I kind of remember seeing something like this a while back.
The Radius Kid said:
I'm going to guess that you've tried installing MM using Kies directly from Sammobile?
If so,have you tried turning off your computer's antivirus when you download/install?
It sounds like the bootloader is looking for something and can't find it.....kind of like what happened to me when I totally ripped KNOX out of my phone.
Restore time!
Good thing I did CWM backups.
In your case,your computer's anti virus could be seeing something in the download and ripping it out.
I've seen my browsers do that when I download stuff....pain in the....
Have you tried a different battery?
Maybe a search of the forums to see if anyone else has had this problem and solved it?
I kind of remember seeing something like this a while back.
Click to expand...
Click to collapse
Thank you for the response,
I was using KIES 2.64 that downloaded from Samsung website to fix the phone as your suggestion (tools->firmware upgrade and initialisation) but still fail to fix it.
Nope, the antivirus still active when KIES download the FW and Flash it into the phone, but it is new to me that antivirus will intercept ongoing dowloaded files, if so i think the antivirus will give some notification or warning about the content of the file that being downloaded and in my case, my antivirus is still cool and no notification whatsoever.
The bad thing is i do not have any cwm backup and since this is my friend phone and not mine, well... we dont have any backup for this phone.
Regarding the battery, i admit that i havent try other battery, since i dont see any connecton between it, in my opinion, the phone works well, the charging animation working, and no sign of weak battery... but i will try to do it if i can get some other battery
I have surfed many forums and websites, but almost 90% can be fixed with simple flashing from odin or just by clearing up cache and data from recovery.
Other that that, wither, no one respond to the problem, or just some discussion without conclusion, really frustrating.
I even go further to read about android booting sequence to identify whats wrong with the boot sequence, but still confused...
But i have some question if you would to answer :
1 . Stuck at Android logo, bootloader or kernel problem?
2 . Is it possible that one of the mainboard chip that have some part in booting process is malfunctioning? But if so, the phone will be dead bricked right?
3. How about the booting process is halted due some hardware failure? ex : some chip (other than chip that have part in booting process) is bad and so the bootloader init is halted
4. The Worst guess, is it possible that the phone is fake? (the serial number behind the baterry is accepted by kies though)
Thank you very much, you are the only one who still response to my problem. :good:
As it seems you use the wrong Bootlaoder. Is his phone N915P or N915G? When you flash N915G Bootloader to N915P, it will not boot but the bootloader will work correctly. Try to flash the N915P bootloader.
I have N915FY phone but did not know first if I had N915F or FY. I flashed the N915F bootloader version, which flashed successfully, but was not booting. Bootloader said that my phones model is N915F. After flashing the FY Bootloader version, it successfully booted to system.
Bordo_Bereli51 said:
As it seems you use the wrong Bootlaoder. Is his phone N915P or N915G? When you flash N915G Bootloader to N915P, it will not boot but the bootloader will work correctly. Try to flash the N915P bootloader.
I have N915FY phone but did not know first if I had N915F or FY. I flashed the N915F bootloader version, which flashed successfully, but was not booting. Bootloader said that my phones model is N915F. After flashing the FY Bootloader version, it successfully booted to system.
Click to expand...
Click to collapse
Thank you for the Response,
First, his phone is N915G (according to the box and the information in the battery compartment)
(Really sorry for the mistake i made at the thread title)
And regarding bootloader, that is also my concern at first, i think maybe i was flasing wrong region and bootloader, and so i search the way to find out the real version of the phone, but after trying many ways described on the net (by imei or serial number) , i still cannot found out the way.
But one instance when i try using KIES, and KIES asked for the version and serial number when device upgrade and initialisation, i entered the exact version and serial number that is found behind the phone in battery compartment. KIES immediately confirms that the version and serial number is valid, (i still wonder though, is KIES check it online at Samsung server or there are some serial number database embedded in the KIES) and continue to run trough the official fw download and installation by KIES but at the end still no success.
Is it possible that the version and serial number is wrong ? if so, how to determine the correct one?
and is it safe to try flasing another bootloader?
Thank you very much
Hello, there is no bootloader related to serial number or something. There are different bootloaders for different models and android version. When you flash MM-Version, you need to be sure that you use the right bootloader and baseband files for MM. If you flash different region-locked firmware/bootloader, it will not affect btw. not solve the boot-stuck problem.
http://samsung-updates.com/device/?id=SM-N915G Try to flash 6.0.1 firmware that is related to your region if you still want to try to flash different region-firmware.
Maybe download the XSA 6.0.1 Firmware with the pit file XSA http://gsm-firmware.com/index.php?a=browse&b=file-info&id=15892.
Then flash XSA 6.0.1 and TBLTE_SEA_XSA.pit together in odin. Under Odin 3 V3.12 ticke the re-partition at option-tab and select TBLTE_SEA_XSA.pit under pit-tab.
Bordo_Bereli51 said:
Hello, there is no bootloader related to serial number or something. There are different bootloaders for different models and android version. When you flash MM-Version, you need to be sure that you use the right bootloader and baseband files for MM. If you flash different region-locked firmware/bootloader, it will not affect btw. not solve the boot-stuck problem.
http://samsung-updates.com/device/?id=SM-N915G Try to flash 6.0.1 firmware that is related to your region if you still want to try to flash different region-firmware.
Maybe download the XSA 6.0.1 Firmware with the pit file XSA http://gsm-firmware.com/index.php?a=browse&b=file-info&id=15892.
Then flash XSA 6.0.1 and TBLTE_SEA_XSA.pit together in odin. Under Odin 3 V3.12 ticke the re-partition at option-tab and select TBLTE_SEA_XSA.pit under pit-tab.
Click to expand...
Click to collapse
Thanks for the reply!
Although there is no bootloader related to serial number, but if we put the serial number in KIES, it will identify what CSC and region, which can be use as a guide to choose the correct FW or let KIES do the Flashing according to the inputted serial number, and as long as the serial number is correct one, that is my opinion but please CMIIW.
When flashing MM, if i use the MM that has been downloaded, the bootloader and baseband is included in the MM image right? or shouuld i flash it separately?
i have tried your suggestion but with no sucess, i have dowloaded the PIT and the FW, flash it trough odin which was sucess, but still stuck.
I do not tick auto restart at Odin, so i manually restart the phone, but i encounter an event which at 20% installing system update (below the greed droid guy) the progress bar is vanished and replaced with erasing, and after that the phone stuck again at the same spot.
Do you have any idea why?
Thank you very much.
Just thinking, should i erase the NAND in ODIN?
If so, how to restore it?
I think that if i backup the NAND using custom recovery and restore it later, it just bring back the same problem, if the NAND causing all this.
Do anyone have some NAND backup that i could use? or any other suggestion?
Thank you
Can you boot to recovery? if yes, try to wipe data and cache.
If it still not working, try to backup your efs with a custom recovery (ex. TWRP), or better the entire System like data, system, boot, efs, modem and save it to your computer.
After saving the backup, try to flash the firmware with pit file while checked NAND erase all.
When its finished and your device boots up, you can flash back your custom recovery and recover only the efs-partition.
If its not working, then there is maybe problems with your eMMC. But be aware using nand erase all. It is the last riskfully option left after trying several things.
I have a backup of my resurrection rom. If you want it I can upload it.
Still says 2017-08-01 security patch, but now with Blueborne and Krack patched as well.
https://www.verizonwireless.com/support/galaxy-s5-update/
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQL1_G900VVZW2DQL1_G900VVRU2DQL1_HOME.tar .md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQL1_G900VVZW2DQL1_G900VVRU2DQL1_HOME_No_ Aboot.tar.md5.zip
I also received the software update notification. Now hoping someone will be able to make the bootloader friendly/no aboot version to flash...
stormified said:
I also received the software update notification. Now hoping someone will be able to make the bootloader friendly/no aboot version to flash...
Click to expand...
Click to collapse
Been a while since I've been to this section of the forums but I'm already uploading a Dev Friendly version and the untouched one right now.
EDIT:
@Silent Patriot
Feel free to add this to the OP.
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQL1_G900VVZW2DQL1_G900VVRU2DQL1_HOME.tar.md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQL1_G900VVZW2DQL1_G900VVRU2DQL1_HOME_No_Aboot.tar.md5.zip
Dudash said:
Been a while since I've been to this section of the forums but I'm already uploading a Dev Friendly version and the untouched one right now.
EDIT:
@Silent Patriot
Feel free to add this to the OP.
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQL1_G900VVZW2DQL1_G900VVRU2DQL1_HOME.tar.md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQL1_G900VVZW2DQL1_G900VVRU2DQL1_HOME_No_Aboot.tar.md5.zip
Click to expand...
Click to collapse
Hi, I am running the Resurrection Remix Final N ROM on my g900v and I have this bootloader (g900vvrs2dqb2). I looked it up and saw that it was from February 2017.
I would like to update my modem and boot so I am ready for Oreo but I'm not sure best way to go about it,(Odin)?
I know this information is available on XDA and probably in this forum, but I am paranoid because I had a hell of a time unlocking the bootloader because I was fallowing old directions.
I would be very grateful to anyone willing to point me towards simple, but accurate directions.
Thanks in advance, and apologize for my ignorance!
Sent from my kltevzw using XDA Labs
Awesome! Thanks very much. I'm gonna give this a shot like the previous install/upgrade some time Friday afternoon PDT.
Jeebus I need sleep....
Can I flash this over LOS in TWRP to return to stock or do I have to use Odin?
Once flashed will the bootloader remain unlocked to allow me to reinstall LOS?
I got a new screen installed and it appears there may be an issue with how the digitizer interfaces with the software/kernal and going back to stock should update the software to allow the screen to function normally then allowing me to reflash LOS.
Hey Everyone,
Thanks for all your great work on the Galaxy S5. This thing is still kicking! I know I'm way behind on what's been going on. I'm still back on the TowelRoot days. The time has come to finally update my phone because some of the apps won't work anymore. I'm not into ROMs and stuff, I just want the latest firmware without all the bloatware. I had originally gone the TowelRoot method because people were having such a hard time with battery life (me included) with Lollipop. I was fortunate enough to get TowelRoot before updating to the newer version of Lollipop and went back to KitKat and I've been there ever since.
I'm currently on G900VVZW1ANCG (Kitkat 4.4.2) with root access and superuser. I have a CID 15 emmc which is a good thing from all the research I've been doing on XDA.
That's where I get stuck and confused with the newer stuff that's going on. Do I even need to unlock the bootloader?
In the end, I don't mind wiping the entire phone, I just want to get to the latest Marshmallow (which this thread seems to have) without all the bloatware or the ability to delete all the bloatware.
nickbike1 said:
Hey Everyone, Thanks for all your great work on the Galaxy S5. This thing is still kicking! I know I'm way behind on what's been going on. I'm still back on the TowelRoot days...
Click to expand...
Click to collapse
Welcome back!
You had asked some questions that is actually 2 separate ones upon themselves and I'll, hopefully, try to answer them...
Question 1: Should you unlock the bootloader?
Answer 1: The only need for anyone to require this is if they want to perform something outside the scope of just Rooting a device.
What I mean is... for example, if an individual would like to install a Custom Recovery and/or Firmware then you will need to unlock the bootloader.
Question 2: You would, ultimately, like to just debloat the Firmware?
Answer 2: Debloating Stock Firmware only requires root and not an unlocked bootloader.
The proper rooting of a device just means that you will be able to modify areas of the root directory that's restricted for devices without root and Debloating falls into this category.
Just an FYI regarding the following 2:
1) The 2 differences between the CID11 & CID15...
GS5 with CID11 = Toshiba EMMC
GS5 with CID15 = Samsung EMMC
2) There are a handful of Custom Firmwares that are based upon the stock Firmware that is already Debloated. Some of them only requires a Rooted device and Some requires an unlocked bootloader and recommends a Custom Recovery like TWRP.
This is just a brief summary to help you further but, I would recommend that you take note of/highlight the following 2threads that would be a bit more helpful depending on what your looking to do.
https://forum.xda-developers.com/showthread.php?t=2700073
https://forum.xda-developers.com/showthread.php?t=3561529
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
From this post here, I think the way to get this done for an unlocked bootloader is:
- flash the HOME_No version using Odin 3.12 AP option
- flash TWRP via Odin AP
- reinstall Magisk from TWRP and Magisk Manager.
1) Will that work?
2) What’s the most reliable tool for creating a backup—a) in case I screw up, AND b) in case everything goes well, so I can restore my apps and data into the new clean phone, preferably without screwing up the new clean phone?
I have a G900V.05 on QB2, rooted and unlocked bootloader and custom recovery, that I got to using this method by jrkruse and a false start via another method. So I’ve got Titanium Backup, TWRP, and FlashFire all in play. I'll probably shoot out backups from all of them, not sure which one restores best or if FlashFire survives the update.
Full System Backup method needed!
BigBird9906 said:
From this post here, I think the way to get this done for an unlocked bootloader is:
- flash the HOME_No version using Odin 3.12 AP option
- flash TWRP via Odin AP
- reinstall Magisk from TWRP and Magisk Manager.
1) Will that work?
2) What’s the most reliable tool for creating a backup—a) in case I screw up, AND b) in case everything goes well, so I can restore my apps and data into the new clean phone, preferably without screwing up the new clean phone?
I have a G900V.05 on QB2, rooted and unlocked bootloader and custom recovery, that I got to using this method by jrkruse and a false start via another method. So I’ve got Titanium Backup, TWRP, and FlashFire all in play. I'll probably shoot out backups from all of them, not sure which one restores best or if FlashFire survives the update.
Click to expand...
Click to collapse
1) -Yes, I just tried it, and it works perfectly! The only correction - you have to unzip
G900VVRU2DQL1_G900VVZW2DQL1_G900VVRU2DQL1_HOME_No_Aboot.tar.md5.zip file and flash md5 file with Odin (Odin won't work with that zip file).
2) -I have exactly the same question to fellow members - what is the current most simple and reliable method of full system backup (like ghost image for PC)? I want to try Lineage, but I already spent many hours on system customization (applications, app settings, accounts with login names/passwords, etc.). I really need some fast method to revert phone back to QL1 with all my current setup. I will flash again System and TWRP from Odin, and Magisk from TWRP. How can I then restore my full setup with one click? I used to use 'Titanium Backup' in the past, but that is not an option anymore. It freezes every time when I try to restore 'All apps with system data'
Thank you for reading that and for any possible advices.
So, if I have an unlocked bootloader, will it stay unlocked if I flash the boot from the "Developer Bootloader Friendly/No Aboot No-Wipe Firmware" version? Will it upgrade the baseband to the latest version as well?
Nerva said:
So, if I have an unlocked bootloader, will it stay unlocked if I flash the boot from the "Developer Bootloader Friendly/No Aboot No-Wipe Firmware" version? Will it upgrade the baseband to the latest version as well?
Click to expand...
Click to collapse
If your looking for the Baseband Modem Firmware, the following link has them all for the G900V and won't affect what you have (i use them on my Unlocked G900V to update the Modem Baseband Firmware and I've got TWRP and LineageOS).
[BASEBAND-FIRMWARE-MODEMS]Verizon Samsung Galaxy S5 {SM-G900V/KLTEVZW}[ODIN] by Ibuprophen
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Thanks. Are the baseband modem firmware also included in the QL1 "Developer Bootloader Friendly/No Aboot No-Wipe Firmware"? I've been told I should upgrade both my modem and bootloader, but I don't want to re-lock my unlocked bootloader.
WTF?? I was running TWRP 3.2.1.0 and crDroid 7.1.2, and I used Odin to flash the "Developer Bootloader Friendly/No Aboot No-Wipe Firmware" and checked the BL and CP options, which I thought should update just the bootloader and modem, and now it boots up with the Samsung logo and then the Verizon logo, and then just sits there. I tried to go to recovery so I could restore a backup, but it looks like the stock recovery. What did I do wrong and how do I fix it??
Since crDroid 7.1.2 is older than the bootloader, I'm wondering if that's the issue. I do have crDroid 8.1 on the microSD card. I also have TWRP 3.2.1.0 on the microSD card. So I'm wondering if I can use the stock recovery to flash TWRP. I haven't played around with custom ROM's in four years, but prior to that I did it all the time, so apparently I now remember just enough to be dangerous...
@Nerva, I apologize for the delay but, I'm curious to know where, why and what gave you the impression that you were/was required, on your your working device, to update your devices bootloader???
I'm just perplexed about this...
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
I went back and tried to find where I read it, and at the very least it was in this post:
godofsalt said:
Yep all true. .... But....
Once he sends you the info (model numbers and such) might want to also double check that he is on the latest firmware, for his devise. Important!
All reads good. If it's rather, "New" then, I would keep it as well.
Click to expand...
Click to collapse
I think I saw it someplace else as well, but I haven't stumbled across it -- I was posting a lot of questions in a lot of threads as well as PMing people.
Nerva said:
I went back and tried to find where I read it, and at the very least it was in this...
Click to expand...
Click to collapse
Your situation prompted me to confirm what I knew and others that you can see on the recent posts on the following thread...
https://forum.xda-developers.com/showthread.php?t=2259645
... I just wanted to state that if your devices bootloader was already unlocked and the device wasn't bricked (or similar) then you should not need to update the bootloader or it'll lock it up again and, potentially, can even cause FRP issues as well. Luckily your FRP didn't trip and the device was able to be unlocked again.
I have the same device that was unlocked a long time ago and never ever needed its bootloader updated.
Your question regarding the Baseband Modem Updates...
Those are the Modem files extracted from the stock Firmware and only updates the devices Modem. That controls the WiFi, Carrier Data, etc...
This is similar to updating the Drivers for something specific on a PC (like the PC LAN, WiFi, Video Card, etc... ).
When you had flashed what you did on your device, you basically flashed an optimized version of the Stock Firmware. This is why you saw the Samsung Boot Screen.
I hope that I had explained this okay via text...
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
I'm curious, if the bootloader version has so little importance for us custom-ROM users, why does Samsung/Verizon update their bootloader versions -- to what purpose?
It looks like this website will generate a cf-auto-root package for QL1:
https://desktop.firmware.mobi/device:840/firmware:14884
I'm wondering if I flash that with Odin, would it upgrade my current unlocked QB2 to an unlocked QL1?
Nerva said:
I'm curious, if the bootloader version has so little importance for us custom-ROM users, why does Samsung/Verizon update their bootloader versions -- to what purpose?...
Click to expand...
Click to collapse
I'm not stating that Bootloaders doesn't get updated upon themselves but, they specifically seldom require it.
One way to look at it is that the function of the bootloader is allot like the BIOS of a PC. They both handle the boot process and seldomly require to be updated specifically.
When a new Stock Firmware version is released, the bootloader is only updated accordingly to reflect the updates of the firmware. This reflection is to protect the device from being updated to an incompatible firmware version.
In short, when the bootloader is unlocked, the bootloader still protects the device from an incompatible firmware from being installed but, it being unlocked just bypasses the "Samsung Stock firmware only" restriction.
TWRP is just the conduit between the Firmware and the bootloader that just handles the communication between the bootloader and the Firmware.
.
I'm wondering if I flash that with Odin, would it upgrade my current unlocked QB2 to an unlocked QL1?
Click to expand...
Click to collapse
If you flash the firmware, your just going to relock your bootloader and be back to stock.
To get the QL1, just flash the Baseband Modem Update from the following link and you'll be good to go and you'll see this in your device info.
[BASEBAND-FIRMWARE-MODEMS]Verizon Samsung Galaxy S5 {SM-G900V/KLTEVZW}[ODIN] by Ibuprophen
Have I clarified this okay?
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
How to downgrade a non-rooted S7 Edge from Android Oreo 8.0 to 7.0 and keeping your Knox 0x0!
So if some of you are looking for a 'how-to' guide, look no further! (I believe it works on your S7 too, but make sure you have downloaded the correct firmware)
*IMPORTANT*
-I don't take ANY responsibility if you bricked your device during the flash!
-Follow the guide below before flashing your official firmware using Odin!
On the phone
-Sign-out any accounts on settings
-Have OEM-unlock & USB Debugging ON (developer options)
-*optional task, just in case* Screenshot your device information on the settings tab (IMEI, Baseband, Software Info, Model number)
-*optional task, just in case* Backup your device using Samsung SmartSwitch software
Things to download
-For this guide I used Odin v3.13.1 https://dl.sammobile.com/Odin3-v3.13.1.zip
-You can install the Samsung driver using SmartSwitch if your Win PC can't detect your Samsung phone (it should show on Device Manager > Modem > something like Samsung Modem)
-*READ* You can't flash back to version 6.0 now because of (Android Oreo 8.0 is using different version of boot-loader) but there are some late Android 7.0 with updated boot-loader, those are using boot-loader binary v2, so binary v1 it will be conflicted and won't work upon flash.
-*NOTE* Download the correct firmware of your phone model by following the baseband, that's why I recommended to take screenshots of your phone, you can search it on here https://www.sammobile.com/firmwares/, for mine, I've searched SM-G935F and BTU is my choice, the filtered results should be your correct firmware. But in my case I used (v7.0 in March 2018) because it has the binary boot-loader v2 with it (whatever it called, it's important otherwise it will not work which I've tried)
-*optional*, if you find sammobile download speed is way too slow* You can use https://updato.com/firmware-archive-select-model?q=SM-G935F&exact=1&r=&v=Nougat%28Android+7.0%29%2COreo%28Android+8.0.0%29&rpp=100, and basically look for the correct firmware which I have mentioned above.
-Extract your firmware onto a single folder, don't mess them up! (you should see something like AP_G935blahblahblah.md5, and you will need AP_, BL_, CP_, CSC_ for downgrading)
Follow the steps:
1. Now you have the correct firmware and Odin running on Admin right
2. On Odin you can add AP_, BL_, CP_ & CSC_ onto the correct selection, for example: https://i.imgur.com/DIB2d1S.png
3. Have your phone on Download mode, google it if you don't know how (make sure you followed the On the phone step first, it's very important)
4. Find a data USB cable and plug into USB2.0 port, make sure your phone appeared on Odin (you will see something like 0:[COM5])
5. On Odin (only Auto Reboot, F. Reset Time) is needed, it should be ticked by default.
6. Now you can safely click 'Start' on Odin.
7. DO NOT TOUCH YOUR PHONE in case your USB is loose which I had experience before.
8. Wait until it shows a green PASS! like this: https://i.imgur.com/FYosmx2.png
9. When see a blue screen with Erasing text on it, please wait until it reboot and hold (Volume UP + Home Button + Power Button) boot to recovery mode
10. Wipe cache partition, and data/factory reset then reboot system now
11. Wait for it to boot into your sweet sweet Android Nougat 7.0 (Late version)
12. Disable auto-update if you wish, mine was on auto-update so I had to pause it half-way
Hope you find this guide helpful, I tried to remember the steps on my head as I typed, (*sorry for the grammar if you find it hard to understand) and if you think I've missed something here, let me know! I would update the guide if any step is missing, just in case
Thanks
I'm guessing Knox counter wouldn't have incremented?
ZionMainframe said:
Thanks
I'm guessing Knox counter wouldn't have incremented?
Click to expand...
Click to collapse
No, not at all, if you are using the official firmware! Just follow the guide closely
Please help me downgrade from G935FXXS3ERHD to G935FXXU2DRAG.
I tried nand TWRP BL restore, BL and stock firmware flash in Odin. Nothing works.
Edit:
I found a solution, see: Original post
but there are some late Android 7.0 with updated boot-loader, those are using boot-loader binary v2
can you upload the bootloader?
How to know each android 7.0 bootloader is V2?
Now with the lattest update the binary changed to 3 then i cant downgrade to Nougat
(Im spanish)
Oreo to nougat
I have a s7 edge with the Data firmware Version 2018/09/18 8.0.0
PDA: G935FXXS3ERHD
CSC: G935FITV3ERG2
is it possible to downgrade from oreo to nougat? I have the battery that you always download
I tried but doesn't work
Hello dear!
I have a S7 edge SM-G935T and I tried to flash the last version of Nougat 7, but doesn't work. Odin don't let me finish the process. Maybe you wrote this thread before my cellphone received the last update of Oreo.
Do you have any solution in this case. I really appreciate it.
King regards, _/\_
Unfortunately the bootloader was updated in last updates, now the bootloader is version 3 as the phone said to me when i tried to flash the last version of Nougat.
i have stupid question but, i have R16NW.SM-G930FXXS3ERKE (oreo) but i think im not supposed download this(G930FXXS3ERKE) if i want downgrade to nougat but rather (G930FXXS2DRC3) because the first firmware i mentioned get me oreo again.... am I right??? i don t wont screw things up....
TheLoller221 said:
Unfortunately the bootloader was updated in last updates, now the bootloader is version 3 as the phone said to me when i tried to flash the last version of Nougat.
Click to expand...
Click to collapse
YES, the Guide is NOT working ANYMORE...
Does this work still
Help with G930A
Hello um I have a Samsung Galaxy S7 on AT&T (G939A) and it's on 8.0 (G930AUCS9CSB1). I've tried to root it but after some research I've come to find out I have to downgrade it to nougat to root it. But the problem is everytime I load a firmware it fails and I did more research I think it said something about the bootloader blocking it and the only way to downgrade the bootloader is downgrading the firmware which I can't do because of that cycle. Can someone please help me all I want to do is root install a custom recovery and a custom rom I love playing around with android tweaks but I can't get it because of this. I hope someone can help me please and thank you.
freshair4552 said:
I have a Samsung Galaxy S7 on AT&T (G939A) and it's on 8.0 (G930AUCS9CSB1)...
Can someone please help me all I want to do is root install a custom recovery and a custom rom...
Click to expand...
Click to collapse
Your bootloader cannot be unlocked due to it being Snapdragon, so unfortunately there is nothing you can do. Only Exynos variants can be modified.
Hello guys,I have a problem with my galaxy s7 sm-g935f(Exynos version).Few months ago I flashed my phone from android Nougat SEE CSC(South East Europe) to UK's Oreo BTU CSC.I'm curious is there any other way to downgrade it from oreo to nougat,otherwise than Odin.I tried flashing it a few times with the latest Odin version (3.13.3) and nougat SEE CSC(South East Europe) because that's my original CSC.Odin recognizes the device normally,but when i click start,it comes to setup connection and then FAIL.The reason I'm trying to downgrade is very poor battery life and heating,and the phone is very laggy.I even tried through Samsung Smart Switch Emergency software recovery but it seems that Samsung has restricted that option...please help if anyone has/had similar problem.Thank you!
Mine is Sprint g935pvpsbcta1
Am I screwed also?
Hi, I have
SM-G935Fand I can't find any nougat firmware with baseband of: G935FXXS8ETCA.. Can I flash any country / baseband 7.0 firmware? And will it improve the SOT? I'm currently getting upto 5 hours SOT.
lovetv said:
How to downgrade a non-rooted S7 Edge from Android Oreo 8.0 to 7.0 and keeping your Knox 0x0!
So if some of you are looking for a 'how-to' guide, look no further!
(I believe it works on your S7 too, but make sure you have downloaded the correct firmware)
*IMPORTANT*
-I don't take ANY responsibility if you bricked your device during the flash!
-Follow the guide below before flashing your official firmware using Odin!
On the phone
-Sign-out any accounts on settings
-Have OEM-unlock & USB Debugging ON (developer options)
-*optional task, just in case* Screenshot your device information on the settings tab (IMEI, Baseband, Software Info, Model number)
-*optional task, just in case* Backup your device using Samsung SmartSwitch software
Things to download
-For this guide I used Odin v3.13.1 https://dl.sammobile.com/Odin3-v3.13.1.zip
-You can install the Samsung driver using SmartSwitch if your Win PC can't detect your Samsung phone (it should show on Device Manager > Modem > something like Samsung Modem)
-*READ* You can't flash back to version 6.0 now because of (Android Oreo 8.0 is using different version of boot-loader) but there are some late Android 7.0 with updated boot-loader, those are using boot-loader binary v2, so binary v1 it will be conflicted and won't work upon flash.
-*NOTE* Download the correct firmware of your phone model by following the baseband, that's why I recommended to take screenshots of your phone, you can search it on here https://www.sammobile.com/firmwares/, for mine, I've searched SM-G935F and BTU is my choice, the filtered results should be your correct firmware. But in my case I used (v7.0 in March 2018) because it has the binary boot-loader v2 with it (whatever it called, it's important otherwise it will not work which I've tried)
-*optional*, if you find sammobile download speed is way too slow* You can use https://updato.com/firmware-archive-select-model?q=SM-G935F&exact=1&r=&v=Nougat%28Android+7.0%29%2COreo%28Android+8.0.0%29&rpp=100, and basically look for the correct firmware which I have mentioned above.
-Extract your firmware onto a single folder, don't mess them up! (you should see something like AP_G935blahblahblah.md5, and you will need AP_, BL_, CP_, CSC_ for downgrading)
Follow the steps:
1. Now you have the correct firmware and Odin running on Admin right
2. On Odin you can add AP_, BL_, CP_ & CSC_ onto the correct selection, for example:
https://imgur.com/DIB2d1S
3. Have your phone on Download mode, google it if you don't know how (make sure you followed the On the phone step first, it's very important)
4. Find a data USB cable and plug into USB2.0 port, make sure your phone appeared on Odin (you will see something like 0:[COM5])
5. On Odin (only Auto Reboot, F. Reset Time) is needed, it should be ticked by default.
6. Now you can safely click 'Start' on Odin.
7. DO NOT TOUCH YOUR PHONE in case your USB is loose which I had experience before.
8. Wait until it shows a green PASS! like this:
https://imgur.com/FYosmx2
9. When see a blue screen with Erasing text on it, please wait until it reboot and hold (Volume UP + Home Button + Power Button) boot to recovery mode
10. Wipe cache partition, and data/factory reset then reboot system now
11. Wait for it to boot into your sweet sweet Android Nougat 7.0 (Late version)
12. Disable auto-update if you wish, mine was on auto-update so I had to pause it half-way
Hope you find this guide helpful, I tried to remember the steps on my head as I typed, (*sorry for the grammar if you find it hard to understand) and if you think I've missed something here, let me know! I would update the guide if any step is missing, just in case
Click to expand...
Click to collapse
I just wonder this solution will be work as well? my phone is s6 edge plus G928C.
And i want to downgrade to 5.1.1 or 6.0 because 7.0 was really terrible.
Hello there
I bought a Samsung J7 Neo (SM -J701M) on another country than mine (Im from Argentina, device bought on Paraguay). Anyway, I started to look another way to get some space on the internal storage and I remember that android had an option to expand it, using a SD Card. Unfortunately, i realize this option is not allowed on samsungs device, but it works (i read it, because can't do it) if you get root user.
So I looked how to do it and i found a group of files
ODIN v3.12
Magisk v.14.5
twrp v.3.1.1 -j7 neo
Im not sure if I downloaded the right files, but im start the process anyway.
I followed point by point
First I installed TWRP Recovery v3.1.1 (which is supposed to be correct to my model) and then already on twrp rom I installed magisk 14.5 from sd card and did wipe data.
Turned on the phone and I restored all apps from a google backups, and I realized I cant find app "Magisk" on the device, so I decided to reboot the phone and it starts to do a bootloop with this error "kernel rev. check fail, device:2 binary:1"
At this point, I failed every attempt to fix this error
I tried installing the last official firmware that i found (and Im not sure if its the correct one)
J701MUBU3ARC2_J701MUWT3ARC1_UFN
And I got this error
"SW REV. CHECK Fail (BOOTLOADER) Device :5 Binary 3:
I searched on google this kind of error, and I found that I have to downgrade the bootloader. And this is why im here beacause I dont know how to do this, and if its works, i don´t know how to continue the process to root and expand my internal storage. So I really appreciate if someone one could help me with this. I can learn fast and I love to do this things by myself.
Thanks for your time!
Fernando
If you have to downgrade the boot loader, it means the firmware you are flashing is older than the one on your fon.
Go to www.updato.com and look for the he latest J701M firmware.
You can sort the list by date and by region.
And the site is download manager friendly ?
Good luck!
Sent from my SM-J700F using Tapatalk
Thanks for your answer! One more question about the region. Should I download firmware from the country that I bought the phone or firmware from the country that I am?
Look for your country specific firmware first.
Otherwise Samsung usually has regional software - i.e for several countries in a region e.g. Argentina, Paraguay.
Sent from my SM-J700F using Tapatalk
MikeEinziger said:
Hello there
I bought a Samsung J7 Neo (SM -J701M) on another country than mine (Im from Argentina, device bought on Paraguay). Anyway, I started to look another way to get some space on the internal storage and I remember that android had an option to expand it, using a SD Card. Unfortunately, i realize this option is not allowed on samsungs device, but it works (i read it, because can't do it) if you get root user.
So I looked how to do it and i found a group of files
ODIN v3.12
Magisk v.14.5
twrp v.3.1.1 -j7 neo
Im not sure if I downloaded the right files, but im start the process anyway.
I followed point by point
First I installed TWRP Recovery v3.1.1 (which is supposed to be correct to my model) and then already on twrp rom I installed magisk 14.5 from sd card and did wipe data.
Turned on the phone and I restored all apps from a google backups, and I realized I cant find app "Magisk" on the device, so I decided to reboot the phone and it starts to do a bootloop with this error "kernel rev. check fail, device:2 binary:1"
At this point, I failed every attempt to fix this error
I tried installing the last official firmware that i found (and Im not sure if its the correct one)
J701MUBU3ARC2_J701MUWT3ARC1_UFN
And I got this error
"SW REV. CHECK Fail (BOOTLOADER) Device :5 Binary 3:
I searched on google this kind of error, and I found that I have to downgrade the bootloader. And this is why im here beacause I dont know how to do this, and if its works, i don´t know how to continue the process to root and expand my internal storage. So I really appreciate if someone one could help me with this. I can learn fast and I love to do this things by myself.
Thanks for your time!
Fernando
Click to expand...
Click to collapse
@MikeEinziger
Hi There,
Did you have any luck with your Phone? I have the same exact model but I have Android Version 8.1.0, Samsung Experience version 9.5; Android security patch level -Feb 1, 2019; Baseband version: J701MUBS6BSB3 and like you, I love doing things myself, and I can't seem to abide a smartphone that's not rooted.
I'm not exactly a newbie, I've been assisting devs with testing and such on AT&T SGS3 for quite some time. But I can't seem to find a stable method for rooting for this phone, no one seems to be doing any development on it.
I would love to hear your story thus far.
im needing help myself, i have the SM-J701M (J7 NEO), with android pie 9 official, but the binary is 7 (because Argentina Geniuses of course) and of all the things i tried nothing works, and the only thing they did was brick the phone, so i flash and stock firmnware to be usable again
Ezeka93 said:
im needing help myself, i have the SM-J701M (J7 NEO), with android pie 9 official, but the binary is 7 (because Argentina Geniuses of course) and of all the things i tried nothing works, and the only thing they did was brick the phone, so i flash and stock firmnware to be usable again
Click to expand...
Click to collapse
What have you done? I saw your messages on TG but everyone ignores usually, I had another problem and footbed the solution myself as I got ignored for days.
So, what have you done? Maybe we can figure it out a way to root it, but to avoid telling you things that you may have already done it is better if you let us know your already followed steps.
Jemec26 said:
What have you done? I saw your messages on TG but everyone ignores usually, I had another problem and footbed the solution myself as I got ignored for days.
So, what have you done? Maybe we can figure it out a way to root it, but to avoid telling you things that you may have already done it is better if you let us know your already followed steps.
Click to expand...
Click to collapse
i tried flashing TWRP like a guide said (Latest version) but then got stuck with a boot loop in the Samsung Galaxy Logo, then when i enter to flash the latest global firmware it didn't work because it was binary 6, so i searched for the version in Argentina that has binary 7, after that i didn't try anything else in fears of getting fully bricked, i was thinking of the magisk canary way of rooting (patching the AP) but i don't know what happen if it fails the flash
Hi, i have the same device, SM-J701M, but when i try to flash the stock, it says that the device binary is 9 and the rom is 8, but i cant find the binary 9 rom in any place, only 8. I have the trwp installed, so I was thinking if I format all data (system and files) and try to flash again, it will work ?
Also im from Brazil (SM-J701MT), and the device was buyed in Paraguay (SM-J701M) too. Should i install the SM-J701MT ROM right ?
Some success.
iKmaster01 said:
Hi, i have the same device, SM-J701M, but when i try to flash the stock, it says that the device binary is 9 and the rom is 8, but i cant find the binary 9 rom in any place, only 8. I have the trwp installed, so I was thinking if I format all data (system and files) and try to flash again, it will work ?
Also I'm from Brazil (SM-J701MT), and the device was buyed in Paraguay (SM-J701M) too. Should i install the SM-J701MT ROM right ?
Click to expand...
Click to collapse
Ok, guys, I've had a bit of progress with my device Samsung Galaxy J 7 Neo (SM-J701M- Android version 8.01)
On this phone, the option to unlock the bootloader was missing in Dev Opt and I knew that in order to achieve anything I was going to have to unlock the bootloader.
I searched and found that, via adb/fastboot (Google's Platform Tools) rebooting the phone to the bootloader you could enter the code: 'fastboot oem unlock' or 'fastboot flashing unlock' and voila! everything would be fixed...But...my device wasn't even being recognized by "fastboot" ! adb yes but no fastboot! Always the message: "Waiting on any device". Trying to find and install the drivers to do this was next to impossible.
It actually caused me soft brick my device. However, it was a blessing in disguise; I knew what had to be done, I was going to have to reinstall the firmware via Odin. I searched the site (Sammobile - you'll have to create an account.) and found the Oreo and the Pie Firmware, I downloaded both but played it safe and restored my device with the Oreo first.
And lo and behold the option to unlock bootloader was there! No hesitation, clicked that sucker fast!!
Now, I'm running PIE (No one has done a Custom ROM for this baby just yet) and with the unofficial TWRP in the first link below, it's a bit buggy but until they make an official one for us ... I guess we'll have to wait.
Oh! And don't forget to make a backup with Smart Switch!
And pay attention to the advice here:
Code:
1. Extract the firmware file you just downloaded. You should get 5 files:
AP (System &Recovery)
BL (Bootloader)
CP (Modem / Radio)
CSC_*** (Country / Region / Operator)
HOME_CSC_*** (Country / Region / Operator)
2. Add each file to its respective field in Odin v3.14.4. Use CSC_*** if you want to do a clean flash or HOME_CSC_*** if you want to keep your apps and data.
3. Reboot your phone in Download / Odin mode (make sure your device is off) with the following button combo: POWER + VOLUME DOWN + BIXBY
Other options in case first option did not work or isn't possible.
Option 2 VOLUME DOWN + VOLUME UP then USB cable
Option 3 POWER + VOLUME DOWN + VOLUME UP
Option 4 POWER + VOLUME DOWN + HOME BUTTON
Option 5 (Note9) USB cable + VOLUME DOWN + BIXBY
Option 6 (Note10) POWER + VOLUME UP
4. Once in download mode, connect your phone to the PC, preferably using the original USB cable you got with your phone. Odin should detect your device and a BLUE box will show up with the COM port number. (Be sure, the SAMSUNG-drivers are installed on your PC!)
Do NOT tick any extra boxes. The only options to be ticked are F.Reset Time and Auto-Reboot.
5. Click the start button, wait for Odin to say 'PASS' in a GREEN box. Once the flash is complete, your phone will reboot, and you can disconnect your phone from the PC
These are some of the links I found helpful:
https://unofficialtwrp.com/root-twrp-galaxy-j7-neo-sm-j701m/
https://www.androidexplained.com/galaxy-note-9-restore-firmware/
https://forum.xda-developers.com/galaxy-j7/samsung-galaxy-j7-prime--j7-on-nxt-exynos7870/recovery-twrp-3-2-0-galaxy-j7-prime-t3716355
---------- Post added at 01:39 PM ---------- Previous post was at 01:30 PM ----------
iKmaster01 said:
Hi, i have the same device, SM-J701M, but when i try to flash the stock, it says that the device binary is 9 and the rom is 8, but i cant find the binary 9 rom in any place, only 8. I have the trwp installed, so I was thinking if I format all data (system and files) and try to flash again, it will work ?
Also im from Brazil (SM-J701MT), and the device was buyed in Paraguay (SM-J701M) too. Should i install the SM-J701MT ROM right ?
Click to expand...
Click to collapse
I think that's because you have to be specific with the carrier; Orange; Nextel; Movistar...that makes a lot of difference in with the firmware. If you can, check to see what you had before and try that first.
CoperaN said:
Ok, guys, I've had a bit of progress with my device Samsung Galaxy J 7 Neo (SM-J701M- Android version 8.01)
On this phone, the option to unlock the bootloader was missing in Dev Opt and I knew that in order to achieve anything I was going to have to unlock the bootloader.
I searched and found that, via adb/fastboot (Google's Platform Tools) rebooting the phone to the bootloader you could enter the code: 'fastboot oem unlock' or 'fastboot flashing unlock' and voila! everything would be fixed...But...my device wasn't even being recognized by "fastboot" ! adb yes but no fastboot! Always the message: "Waiting on any device". Trying to find and install the drivers to do this was next to impossible.
It actually caused me soft brick my device. However, it was a blessing in disguise; I knew what had to be done, I was going to have to reinstall the firmware via Odin. I searched the site (Sammobile - you'll have to create an account.) and found the Oreo and the Pie Firmware, I downloaded both but played it safe and restored my device with the Oreo first.
And lo and behold the option to unlock bootloader was there! No hesitation, clicked that sucker fast!!
Now, I'm running PIE (No one has done a Custom ROM for this baby just yet) and with the unofficial TWRP in the first link below, it's a bit buggy but until they make an official one for us ... I guess we'll have to wait.
Oh! And don't forget to make a backup with Smart Switch!
And pay attention to the advice here:
Code:
1. Extract the firmware file you just downloaded. You should get 5 files:
AP (System &Recovery)
BL (Bootloader)
CP (Modem / Radio)
CSC_*** (Country / Region / Operator)
HOME_CSC_*** (Country / Region / Operator)
2. Add each file to its respective field in Odin v3.14.4. Use CSC_*** if you want to do a clean flash or HOME_CSC_*** if you want to keep your apps and data.
3. Reboot your phone in Download / Odin mode (make sure your device is off) with the following button combo: POWER + VOLUME DOWN + BIXBY
Other options in case first option did not work or isn't possible.
Option 2 VOLUME DOWN + VOLUME UP then USB cable
Option 3 POWER + VOLUME DOWN + VOLUME UP
Option 4 POWER + VOLUME DOWN + HOME BUTTON
Option 5 (Note9) USB cable + VOLUME DOWN + BIXBY
Option 6 (Note10) POWER + VOLUME UP
4. Once in download mode, connect your phone to the PC, preferably using the original USB cable you got with your phone. Odin should detect your device and a BLUE box will show up with the COM port number. (Be sure, the SAMSUNG-drivers are installed on your PC!)
Do NOT tick any extra boxes. The only options to be ticked are F.Reset Time and Auto-Reboot.
5. Click the start button, wait for Odin to say 'PASS' in a GREEN box. Once the flash is complete, your phone will reboot, and you can disconnect your phone from the PC
These are some of the links I found helpful:
https://unofficialtwrp.com/root-twrp-galaxy-j7-neo-sm-j701m/
https://www.androidexplained.com/galaxy-note-9-restore-firmware/
https://forum.xda-developers.com/galaxy-j7/samsung-galaxy-j7-prime--j7-on-nxt-exynos7870/recovery-twrp-3-2-0-galaxy-j7-prime-t3716355
---------- Post added at 01:39 PM ---------- Previous post was at 01:30 PM ----------
I think that's because you have to be specific with the carrier; Orange; Nextel; Movistar...that makes a lot of difference in with the firmware. If you can, check to see what you had before and try that first.
Click to expand...
Click to collapse
Hey, I noticed we have the same android version and and phone model, I wanted to know which version of Twrp you used . I am guessing version 3.1.1?
It's an Un-official version of TWRP, so the version #( 3.2.1-0) may not count, you can check the links out to get more information.
hola tengo un problema, tengo un sm-j701m binario 11 android 9 y quiero intalarle un twrp pero no se cual descargar y que funcione
Don't know if anyone's still following this thread or even still has this phone but there's been quite some progress with this device. (i.e: SM-J701M) The posts below will certainly help to bring your device up to date re: rooting; flashing etc.
https://forum.xda-developers.com/t/...or-galaxy-j7-nxt-neo-core-10-08-2021.4222703/
https://forum.xda-developers.com/t/...laxy-j7-nxt-neo-core-j701-02-02-2021.4227921/
These posts contain links to ROMS and recoveries which have been sucessful, I can personally attest to this, my device was rooted and a custom ROM installed. I hope you will find them helpful.
Good Luck
Greetings, everyone! Usually I have good knowledge regarding rooting, custom recovery and flashing a new system. But this time I tried to downgrade the Samsung Xcover 3 of my friend and flashed the Android 4.4.4 sboot.bin with Heimdall - unfortunately I forgot to tick the "no reboot" option. The moment it rebootet, I know do not have any access to the phone anymore.
When trying to bring it into download mode, it vibrates, but nothing else. Neither Linux nor Windows recognizes the phone. Is it dead? How to gain access so that I can flash the correct sboot.bin? Any tricks you recommend?
back2nature said:
Greetings, everyone! Usually I have good knowledge regarding rooting, custom recovery and flashing a new system. But this time I tried to downgrade the Samsung Xcover 3 of my friend and flashed the Android 4.4.4 sboot.bin with Heimdall - unfortunately I forgot to tick the "no reboot" option. The moment it rebootet, I know do not have any access to the phone anymore.
When trying to bring it into download mode, it vibrates, but nothing else. Neither Linux nor Windows recognizes the phone. Is it dead? How to gain access so that I can flash the correct sboot.bin? Any tricks you recommend?
Click to expand...
Click to collapse
If you can find a "debrick.img" or "debrick.bin" for your specific model number, there is a method that uses your external sdcard to boot the phone then repair it while it is booted.
But, first, you need to find a debrick.img or debrick.bin for your specific model number. If you can't find a copy for your model number, you can try finding another member here that has a rooted Xcover 3 with the exact same firmware as your device had and have them pull a copy of debrick.img or debrick.bin from their device then upload it for you to download.
If you can't find that, the only other options are to send the device to a repair shop for JTAG service or replace the motherboard.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
If you can find a "debrick.img" or "debrick.bin" for your specific model number, there is a method that uses your external sdcard to boot the phone then repair it while it is booted.
But, first, you need to find a debrick.img or debrick.bin for your specific model number. If you can't find a copy for your model number, you can try finding another member here that has a rooted Xcover 3 with the exact same firmware as your device had and have them pull a copy of debrick.img or debrick.bin from their device then upload it for you to download.
If you can't find that, the only other options are to send the device to a repair shop for JTAG service or replace the motherboard.
Click to expand...
Click to collapse
I did not even expect that someone would answer here. THANK YOU SO MUCH, @Droidriven! That gives me hope to rescue the phone instead of having o buy a new one for my friend. Here is what I actually did wrong: In my attempt to "downgrade" from 5.1.1 Lollipop to Android 4.4.4 Kitkat (downgrade needed to be able to root the phone) I flashed the sboot.bin of Android 4.4.4 Kitkat with Heimdall and forgot to tick the NO REBOOT option.
That being said, the phone now only vibrates when using my JTAG (yes, I actually have one and the phone vibrates, but does not boot into download mode and is not recognized by neither Windows nor Linux). So, how to build this unbrick image? Could you help me with that? Both firmwares are to be found here:
Code:
https://samsungfirmware.net/samsung-galaxy-xcover-3-sm-g388f-stock-firmware
Another thread with sadly no file uploaded was to be found here:
Code:
https://forum.xda-developers.com/general/help/search-g388f-xcover3-debrick-img-sdc-t3399231
As for the creation of the unbrick image, do you recommend this tool? I currently have no Windows at hand but can provide you with the original PIT file if you can run this tool to create it:
Code:
http://forum.gsmhosting.com/vbb/f609/atf-v12-70-update-31-mar-2017-a-937102/index5.html#post10127092
DOWNLOAD LINK ATF_v12.70_Full_Installer:
Code:
http://www.mediafire.com/file/l1c9o7ibv2jypfv/ATF_v12.70_Full_Installer_%2528xdarom.com%2529.rar/file
Furthermore, I actually wanted to install LineageOS on that phone. Not sure if you have a Google-foo so strong that you are able to find a working one for me?
Thanks a lot for your help. May god return your efforts in helping me!
back2nature said:
I did not even expect that someone would answer here. THANK YOU SO MUCH, @Droidriven! That gives me hope to rescue the phone instead of having o buy a new one for my friend. Here is what I actually did wrong: In my attempt to "downgrade" from 5.1.1 Lollipop to Android 4.4.4 Kitkat (downgrade needed to be able to root the phone) I flashed the sboot.bin of Android 4.4.4 Kitkat with Heimdall and forgot to tick the NO REBOOT option.
That being said, the phone now only vibrates when using my JTAG (yes, I actually have one and the phone vibrates, but does not boot into download mode and is not recognized by neither Windows nor Linux). So, how to build this unbrick image? Could you help me with that? Both firmwares are to be found here:
Code:
https://samsungfirmware.net/samsung-galaxy-xcover-3-sm-g388f-stock-firmware
Another thread with sadly no file uploaded was to be found here:
Code:
https://forum.xda-developers.com/general/help/search-g388f-xcover3-debrick-img-sdc-t3399231
As for the creation of the unbrick image, do you recommend this tool? I currently have no Windows at hand but can provide you with the original PIT file if you can run this tool to create it:
Code:
http://forum.gsmhosting.com/vbb/f609/atf-v12-70-update-31-mar-2017-a-937102/index5.html#post10127092
DOWNLOAD LINK ATF_v12.70_Full_Installer:
Code:
http://www.mediafire.com/file/l1c9o7ibv2jypfv/ATF_v12.70_Full_Installer_%2528xdarom.com%2529.rar/file
Furthermore, I actually wanted to install LineageOS on that phone. Not sure if you have a Google-foo so strong that you are able to find a working one for me?
Thanks a lot for your help. May god return your efforts in helping me!
Click to expand...
Click to collapse
Sorry, I'm just now seeing this. Did you ever make any progress? Yes, I think there are some reliable methods to create debrick.img/debrick.bin files, there is one such method posted here at XDA in a random post in a thread here but I can't remember exactly what thread it is.