Phone doesn't recognize old Model Number after installing ROM - Samsung Galaxy S7 Edge Questions and Answers

So first off, l would like to say that i'm probably one of the biggest idiots alive right now.
So I flashed this Oreo Rom onto my phone not READING and realizing that it was for the SM-G935F models when i currently have the SM-G935W8 model. Being very new to flashing, I made a back up for all my data, but not for my old OS/firmware and after backing up, i completely wiped the old OS from my phone. Recently I have been trying to flash stock firmware for my phone but i hasn't been working. When i connect my phone to Samsung Switch, it recognizes itself as a G935F model and not a G935W8 model. Is there any way to fix this, I've spent the last few days trying to return it to stock but nothing is working.
My phone works okay, but the wifi reception sucks now. My phone is rooted with Magisk 14
Is there anything I can do to fix this?
This is the Oreo Rom i used.
https://forum.xda-developers.com/s7-edge/development/8-0-0-samsung-experience-9-0-s7-edge-t3748078

Related

Galaxy s5 reboots just after galaxy s5 logo is shown, cant get into recovery mode.

Hi,
To make everything clear i will start from the very begining. I bought my Galaxy S5 2 years ago. It was on android KitKat back then. Everything was stable and it was working like a charm. When android 5.0 Lollipop was available in OTA i let it update. Still everything was ok. And now, about 1 month ago when android 6.0 Marshmallow came out in OTA for my device i also didnt hesitate. Now i regret it as hell. On 6.0 my phone went from stable as a rock to restarting every 5 minutes. I thought maybe its battery fault so i changed it but unfortunately it didnt change much. I blamed 6.0 for all this thing so i decided to downgrade it to 5.0 Lollipop. I did it thanks to youtube tutorial by android doctor - Samsung Galaxy S5 Downgrade Android 6.0 G900F Marshmallow To 5.0 Lollipop ( i was using ODIN and i flashed XEO rom for my SM-G900F from sammobile website).
For like 3 weeks everything went back to normal but one day i couldnt turn WiFi on my phone (when i pressed the WiFi symbol nothing was changing, when in settings i tried to slide it to ON position it went back to OFF. I thought ok lets reboot the phone then. I did it but from that moment my phone is as useless as a brick. It turns on, shows Samsung Galaxy s5 logo and immediately restarts. I cant even enter recovery mode. I can enter download mode so i tied to flash another rom (6.0) but it didnt work. Phone was still restarting in the same moment. I even tried to install TWRP but cant enter it also.
I had my own small company but it went bankrupt and i have huge debts which i will be paying for next 10 years so i really dont have any money to spend. I live without the phone right now. My life is a misery. Can you guys please help me to unbrick my phone? I will be very grateful and you propably cant imagine how much it will cheer me up to have it working again.
Sorry for such a long post and useless informations about my life but i had to let it all out.
I'd try going back to stock kitkat with odin (install the firmware from sammobile)
im not sure if you can go back to kitkat via odin once youve gone to lollipop, nor am i sure why anyone would. Just get the OK4 tar.md5 from either sammobile.com (very slow servers) or from here (much faster) and flash it in odin. should be god to go. then you can root, flash twrp and youre ready to ROM

Bricked AT&T GALAXY S6 EDGE PLUS

I was trying to root my at&t s6 edge+ using Odin. As soon as the process completed, my phone froze on Samsung screen. Then I tried wiping cache and data but nothing worked. I downloaded few stock ROM for Odin but flashing keeps on failing. I read in some thread that new Samsung devices do not support downgrading. I went and checked my current build number and found that to be G928AUCS4CPK1. However, the firmware I was trying to flash were older version.
Has anyone experienced similar issue before? The main problem here is I cannot find the exact build number anywhere. I spent a lot of time searching and finally decided to post here.
Your valuable suggestions will be greatly appreciated.
Thanks.
hey man, you flashed an older version of the firmware? even if it wasnt bricked, your phone is essentially useless now. the efs is gone, meaning you cant make phonecalls or connect to wifi at all. sorry; your phone is bricked. perm.
download mode dosen`t work ?if so the only thing you can try is to use samsung kies to restore your phone but don`t know if that works
I done something similar to my standard S6 Edge the only difference was i was able to start it up ok and i thought everything was ok until i realised i had no reception. I so happened to notice my imei number was gone. I had no back ups of the partition that saved this info so i totally bricked my phone.
I did however find a website that would be able to do a work around ( for a fee of course) for it however it does question your morals as its essentially illegal in alot of countries. I dont want to post anything on here so if you want any info send me a PM.
Exact same thing happened to me... went to AT&T repair center but they didn't have the 'K1' firmware..
anyhow managed to find the latest firmware (gsm-firmware.com)... cost me $4, but the phone is up and running... I only flashed the AP file.. also used Odin 3.12.5..

Tracfone SM-S902L: Bad ROM flashes, need to recover stock ROM

Hello all,
I recently discovered that my S5 was only running KitKat despite Marshmallow having been released for it. I checked for OTA updates and it found nothing, so I decided to flash a custom 6.0 ROM onto it (and for some reason I ended up deciding not to make a backup of the phone beforehand, the ultimate mistake).
The problem became that it didn't recognize Tracfone for my service provider and wouldn't connect to the mobile network. I then downgraded it to a 5.0 ROM, and it no longer even recognized the SIM card, saying there was none.
So I tried to flash the original stock ROM a few times, but every time either got errors from ODIN, the phone itself, or the TWRP bootloader.
Long story short, I seem to have screwed up multiple times trying to install a ROM to get around KitKat and now my phone appears to be softbricked. I can get into the TWRP menu and the "download" mode, but when trying to start the phone, it sits on the "Samsung Galaxy S5" screen with the "Set Warrenty Bit : kernel" text at the top left.
I'm just wondering if there's a way to fix it at this point, or if I've completely trashed the phone.
If anybody has suggestions or experience with this, all help is welcome!
Thanks!
MevNav said:
Hello all,
I recently discovered that my S5 was only running KitKat despite Marshmallow having been released for it. I checked for OTA updates and it found nothing, so I decided to flash a custom 6.0 ROM onto it (and for some reason I ended up deciding not to make a backup of the phone beforehand, the ultimate mistake).
The problem became that it didn't recognize Tracfone for my service provider and wouldn't connect to the mobile network. I then downgraded it to a 5.0 ROM, and it no longer even recognized the SIM card, saying there was none.
So I tried to flash the original stock ROM a few times, but every time either got errors from ODIN, the phone itself, or the TWRP bootloader.
Long story short, I seem to have screwed up multiple times trying to install a ROM to get around KitKat and now my phone appears to be softbricked. I can get into the TWRP menu and the "download" mode, but when trying to start the phone, it sits on the "Samsung Galaxy S5" screen with the "Set Warrenty Bit : kernel" text at the top left.
I'm just wondering if there's a way to fix it at this point, or if I've completely trashed the phone.
If anybody has suggestions or experience with this, all help is welcome!
Thanks!
Click to expand...
Click to collapse
Are you sure you have the stock firmware for the 902l and not the 903vl? The reason you didn't get the update for 6.0 is you have the 902l model. If you had the 903vl model you'd have 6.0. Straight talk never released it for the 902l model. No idea why being both models are very similar. Im not sure but if you make it back to stock on kitkat. I think you can use safestrap from the Verizon s5 to use some custom roms that run kitkat. If your bootloader is in fact unlocked and you can install a custom recovery other then safestrap. I believe you can install pretty much anything but I'm pretty sure straight talk ships the phones with the Toshiba chip so the bootloader isn't unlockable

unbricking hard brick - moto x style

hey guys
i just brick my phone (no idea how, flashed android 7 firmware) after flash my phone was working for like 2 hours, then i let himself update a security options. After update my phone went brick
As far i found :
- installed Qualcoom QDLOADER 9008 driver
- found QFIL programmer
i need to have programmer path (something related to JTAG) and build xmp path
Where i can find them? Or is it a other way to resscue my phone?
I feel your pain. My timeline:
- The phone was unlocked but still in Stock Nougat (7.0?). Got that from OTA in Brazil.
- I tried to update to LineageOS 7 via TWRP. After a full wipe (everything, system, data, card, cache etc) I installed the new ROM. Turned on, bootlooped forever.
- Searching around I found out that there was no modem in the Nougat roms and for some reason I needed to flash a Marshmallow modem for my region to make that work (I think there is no Nougat modems around or something).
- I found a LA_DS modem for 6.0, flashed that using TWRP, still bootloop. Tried other roms using TWRP, still bootloop.
- I then downloaded a full stock old 6.0 firmware to go back to stock but the phone wouldn't accept some files ("preflash validation failed").
- Searched around and found out that you can't downgrade a bootloader from Moto.
- Using fastboot, I flashed the files the phone was willing to accept and it finally booted the 6.0 Marshmallow stock rom, but with no networking (radio/modem/baseband/IMEI missing).
- Flashed the 6.0 modem for my region again and everything worked. Connected on WiFi, dual sim cards detected etc.
- I started to install every update the phone showed to try to update it back to latest MM version.
- The three first updates went ok, the fourth turned off the phone to never turn on again.
Looks like there is no way out of this. My phone is pretty old and MotoCare in Brazil will charge a lung and a half for repair.
dsnunes said:
I feel your pain. My timeline:
- The phone was unlocked but still in Stock Nougat (7.0?). Got that from OTA in Brazil.
- I tried to update to LineageOS 7 via TWRP. After a full wipe (everything, system, data, card, cache etc) I installed the new ROM. Turned on, bootlooped forever.
- Searching around I found out that there was no modem in the Nougat roms and for some reason I needed to flash a Marshmallow modem for my region to make that work (I think there is no Nougat modems around or something).
- I found a LA_DS modem for 6.0, flashed that using TWRP, still bootloop. Tried other roms using TWRP, still bootloop.
- I then downloaded a full stock old 6.0 firmware to go back to stock but the phone wouldn't accept some files ("preflash validation failed").
- Searched around and found out that you can't downgrade a bootloader from Moto.
- Using fastboot, I flashed the files the phone was willing to accept and it finally booted the 6.0 Marshmallow stock rom, but with no networking (radio/modem/baseband/IMEI missing).
- Flashed the 6.0 modem for my region again and everything worked. Connected on WiFi, dual sim cards detected etc.
- I started to install every update the phone showed to try to update it back to latest MM version.
- The three first updates went ok, the fourth turned off the phone to never turn on again.
Looks like there is no way out of this. My phone is pretty old and MotoCare in Brazil will charge a lung and a half for repair.
Click to expand...
Click to collapse
Pretty similar situation on my part. I downgraded back to 6.0 and when it tried to take the December update I ended up with the same thing as you. I ended up getting a replacement from Moto for under 100 dollars which was worth it rather than trying to find a solution that doesn't exist.

Galaxy s7 edge exynos wont flash stock files HALP

Im using a Galaxy s7 edge exynos and I have been trying ALL day to return to stock firmware. (was aiming for 6.0, but when that didnt work I started trying 7.0 with slightly more success...) I was previously rooted via magisk using TWRP. I am not able to flash all 4 files at once via odin, (BL, AP, CP, CSC) I quickly get an error on both the device and odin (decive says binary 2 device something... Odin stops at either Param.bin or cm.bin depending on which CSC I use) the BL file seems to be the one that refuses to flash (from any of the 4 versions of odin i have and using different firmware versions that previously worked on the phone)
I am able to flash just the AP, CP, and CSC but when android loads up my mobile data doesnt work and many other things dont work correctly as well ...
I am so confused as to what I can even possibly do now. Im sitting here with a phone that wont correctly software update that I cant correctly root and has no mobile data. No full 4 files will correctly flash without odin error. TWRP gives me crap now too. I have wiped and formatted all the data many times hoping id missed something.
Send help
also
I try to manually update and it says "registering device" for a sec and then "Process failed" Like android 7.0 is running but not how it was before. I did update to newest update via the phone before i decided to try to revert to android 6.0 again because I was having issues connecting my pokemon go+
Hmmmm I still have problems with 5ghz and mobile data but i got magisk to install... luckily im not using this for phone purposes. this is the best i can do without help
What is yohr phone model ?
G935f
G935f
Currently running g935fd
Did you flash and Oreo rom by anychance?
"Maybe", i say maybe if you did thats why you cant go back to a < 8.0 version
riseofsand said:
Did you flash and Oreo rom by anychance?
"Maybe", i say maybe if you did thats why you cant go back to a < 8.0 version
Click to expand...
Click to collapse
I didn't try anything with oreo until like 10 hours of failing everything and reading everything I could find. It was unofficial and apps wouldn't install or update correctly. So actually what I got to semi work was 7.0 again. Build G935FXXU1DPLT. It doesn't show cell tower signal or work with 5ghz anymore but I got magisk installed and I can run apps off of wifi. (Same as before 8.0 but got magisk working this time)
I'd still like to try to get my 5ghz and cell signal (just in case something happens to my main phone) but I'm scared to soft brick my phone for the 1000th time in 2 days when I managed to get it semi working.
CactuarKing said:
I didn't try anything with oreo until like 10 hours of failing everything and reading everything I could find. It was unofficial and apps wouldn't install or update correctly. So actually what I got to semi work was 7.0 again. Build G935FXXU1DPLT. It doesn't show cell tower signal or work with 5ghz anymore but I got magisk installed and I can run apps off of wifi. (Same as before 8.0 but got magisk working this time)
Click to expand...
Click to collapse
Last time something like that happend to me, is because i was flashing the wrong stock rom (same model but wrong original carrier) sometimes it does matter, sometimes not
I was worried I might have messed it up for good as well luckily I'm not completely stuck but I still dont understand why I couldnt just 100% flash my OS via odin like I always do. Although I got cocky and started without following instructions up on the computer this time. Just my luck
double check mod #it can change with different roms my s5 tmobile g900t originally now its grown into g935f S7 edge

Categories

Resources