Update: Fixed (see edit 2)!
Original post:
I rooted many phones (especially Samsung ones) so I won't consider myself to be something of a "beginner".
However, I just got my Z Flip 3 today and (of course) straight went on to root it, using this thread and the guide that was linked there:
Rooting the SM-F711B (on Version F711BXXU2AUI4) working
First of all: I'm no Dev...just someone who likes to play lego. From this point of view everything I post here is taken from somewhere else in the Internet and used by your own risk. I've read a good startup here. Hopefully this makes this...
forum.xda-developers.com
However, no matter if I flash the patched (by Magisk) bootfile with Odin to AP (like in the linked guide) or to AP and BL (like the OP in the thread hinted), I can't get Wifi to work.
Of course it worked before rooting so it's not a hardware issue.
Should I flash more parts of the firmware that I downloaded with Frija?
Because according to the guide I just downloaded a stock firmware (probably the newest one) but only used the boot.img.lz4 from within the AP*.tar.md5, let Magisk on the phone patch it and then flashed the patched tar to AP (and BT) with Odin.
Everything else seems to work just fine, even the camera that is reportedly broken after rooting on some devices:
Samsung kills the cameras on the Galaxy Z Fold 3 if you unlock the bootloader
Unlocking the bootloader of the Samsung Galaxy Z Fold 3 reportedly breaks all the camera-related functionalities. Read on to know more!
www.xda-developers.com
Nevermind, the camera issue is on the Fold, not the Flip.
Edit:
It's probably because Frija got the newest FW while I have an older one and now there's a mismatch in the modem module. Oh man. Why won't the guide mention this?
I'm downloading the exact firmware that I already have on the phone right now, patch the boot from it again and repeat the process to hopefully end up fixing it this way. Wish me luck!
Edit 2:
Just did that and I have Wifi now. So everything's fine!
TarikVaineTree said:
Update: Fixed (see edit 2)!
Original post:
I rooted many phones (especially Samsung ones) so I won't consider myself to be something of a "beginner".
However, I just got my Z Flip 3 today and (of course) straight went on to root it, using this thread and the guide that was linked there:
Rooting the SM-F711B (on Version F711BXXU2AUI4) working
First of all: I'm no Dev...just someone who likes to play lego. From this point of view everything I post here is taken from somewhere else in the Internet and used by your own risk. I've read a good startup here. Hopefully this makes this...
forum.xda-developers.com
However, no matter if I flash the patched (by Magisk) bootfile with Odin to AP (like in the linked guide) or to AP and BL (like the OP in the thread hinted), I can't get Wifi to work.
Of course it worked before rooting so it's not a hardware issue.
Should I flash more parts of the firmware that I downloaded with Frija?
Because according to the guide I just downloaded a stock firmware (probably the newest one) but only used the boot.img.lz4 from within the AP*.tar.md5, let Magisk on the phone patch it and then flashed the patched tar to AP (and BT) with Odin.
Everything else seems to work just fine, even the camera that is reportedly broken after rooting on some devices:
Samsung kills the cameras on the Galaxy Z Fold 3 if you unlock the bootloader
Unlocking the bootloader of the Samsung Galaxy Z Fold 3 reportedly breaks all the camera-related functionalities. Read on to know more!
www.xda-developers.com
Nevermind, the camera issue is on the Fold, not the Flip.
Edit:
It's probably because Frija got the newest FW while I have an older one and now there's a mismatch in the modem module. Oh man. Why won't the guide mention this?
I'm downloading the exact firmware that I already have on the phone right now, patch the boot from it again and repeat the process to hopefully end up fixing it this way. Wish me luck!
Edit 2:
Just did that and I have Wifi now. So everything's fine!
Click to expand...
Click to collapse
Good news! so you've manged to root Android 12? if so, what steps did you take?
beanbean50 said:
Good news! so you've manged to root Android 12? if so, what steps did you take?
Click to expand...
Click to collapse
Android 12? No, I'm on 11.
TarikVaineTree said:
Android 12? No, I'm on 11.
Click to expand...
Click to collapse
Oh I see 11...
good luck when trying to upgrade & rooting to 12 as something has changed and none of the guides work anymore
TarikVaineTree said:
Update: Fixed (see edit 2)!
Original post:
I rooted many phones (especially Samsung ones) so I won't consider myself to be something of a "beginner".
However, I just got my Z Flip 3 today and (of course) straight went on to root it, using this thread and the guide that was linked there:
Rooting the SM-F711B (on Version F711BXXU2AUI4) working
First of all: I'm no Dev...just someone who likes to play lego. From this point of view everything I post here is taken from somewhere else in the Internet and used by your own risk. I've read a good startup here. Hopefully this makes this...
forum.xda-developers.com
However, no matter if I flash the patched (by Magisk) bootfile with Odin to AP (like in the linked guide) or to AP and BL (like the OP in the thread hinted), I can't get Wifi to work.
Of course it worked before rooting so it's not a hardware issue.
Should I flash more parts of the firmware that I downloaded with Frija?
Because according to the guide I just downloaded a stock firmware (probably the newest one) but only used the boot.img.lz4 from within the AP*.tar.md5, let Magisk on the phone patch it and then flashed the patched tar to AP (and BT) with Odin.
Everything else seems to work just fine, even the camera that is reportedly broken after rooting on some devices:
Samsung kills the cameras on the Galaxy Z Fold 3 if you unlock the bootloader
Unlocking the bootloader of the Samsung Galaxy Z Fold 3 reportedly breaks all the camera-related functionalities. Read on to know more!
www.xda-developers.com
Nevermind, the camera issue is on the Fold, not the Flip.
Edit:
It's probably because Frija got the newest FW while I have an older one and now there's a mismatch in the modem module. Oh man. Why won't the guide mention this?
I'm downloading the exact firmware that I already have on the phone right now, patch the boot from it again and repeat the process to hopefully end up fixing it this way. Wish me luck!
Edit 2:
Just did that and I have Wifi now. So everything's fine!
Click to expand...
Click to collapse
Hai. I got a Z Flip 3 a week ago and I am having the same issue here. Ive followed the same steps as you and ended up with wifi not working. Also my screen seems to go a weird magenta (for a few seconds) when I turn on the screen.
I am in Australia so my phone could be one of two CSC options: VAU or XSA. I tried VAU boot.img first and this caused the problem. I flashed with the XSA boot.img and the same problem.
I tried to follow this guide (https://www.droidwin.com/fix-no-wifi-calls-network-after-root-custom-rom/) but at the step 5 (boot to fastboot mode) my phone will only adb command into recovery mode when I use the command "adb reboot fastboot" and with the command "adb reboot bootloader" it will just boot loop the phone once and boot back into android.
In Odin, I tried to flash CP with the CP.tar file and this didnt change anything.
VerdandiAmine said:
Hai. I got a Z Flip 3 a week ago and I am having the same issue here. Ive followed the same steps as you and ended up with wifi not working. Also my screen seems to go a weird magenta (for a few seconds) when I turn on the screen.
I am in Australia so my phone could be one of two CSC options: VAU or XSA. I tried VAU boot.img first and this caused the problem. I flashed with the XSA boot.img and the same problem.
I tried to follow this guide (https://www.droidwin.com/fix-no-wifi-calls-network-after-root-custom-rom/) but at the step 5 (boot to fastboot mode) my phone will only adb command into recovery mode when I use the command "adb reboot fastboot" and with the command "adb reboot bootloader" it will just boot loop the phone once and boot back into android.
In Odin, I tried to flash CP with the CP.tar file and this didnt change anything.
Click to expand...
Click to collapse
You have to use the phone info app (don't remember the correct name) of the guide to get your correct CSC. That's very important. Also use the very same app to check your current (!) firmware and get exactly that one from the internet.
From there do the steps to alter the boot file according to the guide, then flash it with Odin while also at the same time clicking on BL and choose the (untouched) BL file from the complete firmware you just downloaded that fits your currently installed firmware. That's the most important step to make sure your modem stuff is working according to your current firmware.
beanbean50 said:
Oh I see 11...
good luck when trying to upgrade & rooting to 12 as something has changed and none of the guides work anymore
Click to expand...
Click to collapse
I don't mind staying here for a while honestly and I'm pretty sure someone will find out soon how to root Android 12 on the Flip. Thanks for the warning though.
TarikVaineTree said:
I don't mind staying here for a while honestly and I'm pretty sure someone will find out soon how to root Android 12 on the Flip. Thanks for the warning though.
Click to expand...
Click to collapse
I've finally managed to root Android 12 after weeks of trying.. Yippee..!
TarikVaineTree said:
You have to use the phone info app (don't remember the correct name) of the guide to get your correct CSC. That's very important. Also use the very same app to check your current (!) firmware and get exactly that one from the internet.
From there do the steps to alter the boot file according to the guide, then flash it with Odin while also at the same time clicking on BL and choose the (untouched) BL file from the complete firmware you just downloaded that fits your currently installed firmware. That's the most important step to make sure your modem stuff is working according to your current firmware.
Click to expand...
Click to collapse
Using phone info my correct CSC is VAU. The software I used to get firmware is Frija and I deployed it with Odin.
So flash the magisk patched boot.img file to AP via Odin as well as flash the firmware BL file to BL? Okay I will try this with VAU firmware and report back with what happens.
Related
Hello dev's !
So I am surfing alot of threads here lately and I finally have this chance to post my problem & hopefully get some help regarding my problem.
Device Info - MHA-L29C185... (Middle East Version - Dual SIM). Don't remember which stock rom I was on but it was oreo so maybe somewhere close to 374 or earlier version.
Problem :
Firstly, I rooted following one of the threads from here and it was successful. However, I messed up when I downloaded an app which modifies framework or something and it bricked me and pushed me out.
But luckily I had some help and I used Chimera Tool to flash the International Version which brought my phone back to life but a lot of features like WiFi, Fingerprint Scanner didn't work.
So I decided to re-flash my firmware ie; C185B374 (Middle East Version) hoping it would solve the problem. It did solve the Fingerprint and WiFi problem but gave new problems like Gallery App (System APP) not working and Bluetooth not working.
:crying:
Note : I tried downloading firmware files from Firmware Finder & and flashing all 3 files using twrp and it fails as there is some mess in the Partition which isn't resolving. :crying:
I tried flashing using firmware finder app in the phone. It downloads the firmware and everything but doesn't flash. :crying:
Now, when I try to rebrand also which seemed a possible solution, I get stuck on the step where oeminfo files has to be replaced from the twrp backups. The script just doesn't respond.
Well, I am still living with the phone but alot of features don't work.
Help Required is :
1. Need solution to get stock firmware working properly as I am currently running my regions version but features don't work.
2. Lock back bootloader if possible. ( ADB Method & Team MT Multi Tool have been tried with no success)
3. Possibly get everything back to orignal. That's all I want !
Can anybody provide a possible solution to this ?
Nobody ?
My thought:
Download the firmware images you want to install.
Follow the instructions for using HuRupdater (search, I don't have the link handy for it); basically: put hurupdater and your update zips in the same folder on microsd, flash hurupdater with TWRP.
For relocking, you should be able to use "fastboot oem relock", though the phone will show that status. If that's fine, go for it.
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.
i got the latest security update via OTA and an now running the G930UUEU9CSA3 firmware, ive tried flashing the eng boot img i originally used to root from here "https://forum.xda-developers.com/verizon-s7-edge/how-to/root-s7-s7edge-oreo-nougat-t3819616" but odin fails every time, i'm pretty sure its because the new security update updated the bootloader also... to version 9. now i guess my question is are there any eng boot files for the v9 bootloader available yet? or any other usable root methods available?
snaksalot said:
i got the latest security update via OTA and an now running the G930UUEU9CSA3 firmware, ive tried flashing the eng boot img i originally used to root from here "https://forum.xda-developers.com/verizon-s7-edge/how-to/root-s7-s7edge-oreo-nougat-t3819616" but odin fails every time, i'm pretty sure its because the new security update updated the bootloader also... to version 9. now i guess my question is are there any eng boot files for the v9 bootloader available yet? or any other usable root methods available?
Click to expand...
Click to collapse
That wasn't very clever was it.
Should never update branded unless it's to fix a major bug. Any loophole which allows root or flash is closed on an update until someone figures out how to root on the new boot loader.
I think the best advice to anyone on US networks is to flash unbranded and go from there.
snaksalot said:
i got the latest security update via OTA and an now running the G930UUEU9CSA3 firmware, ive tried flashing the eng boot img i originally used to root from here "https://forum.xda-developers.com/verizon-s7-edge/how-to/root-s7-s7edge-oreo-nougat-t3819616" but odin fails every time, i'm pretty sure its because the new security update updated the bootloader also... to version 9. now i guess my question is are there any eng boot files for the v9 bootloader available yet? or any other usable root methods available?
Click to expand...
Click to collapse
Get magisk.zip from internet , move to a sdcard insert sdcart to s7, Flash twrp for s7 then format data then click install magisk.zip reboot after finish and done.
kpwnApps said:
Get magisk.zip from internet , move to a sdcard insert sdcart to s7, Flash twrp for s7 then format data then click install magisk.zip reboot after finish and done.
Click to expand...
Click to collapse
I'm fairly certain that the only twrp for the s7 is a temporary one because there is no unlock for the bootloader, and even still the temp twrp is only compatible with the v4 bootloader and I am currently on v9.... that is unless I'm mistaken if I am then please someone correct me and point me in the right direction because I'd love to be running magisk on my s7 : )
cooltt said:
That wasn't very clever was it.
Should never update branded unless it's to fix a major bug. Any loophole which allows root or flash is closed on an update until someone figures out how to root on the new boot loader.
I think the best advice to anyone on US networks is to flash unbranded and go from there.
Click to expand...
Click to collapse
No it most definitely was not very clever at all and unfortunately I'm stuck : / Also is the G930UUEU9CSA3 firmware not unbranded?
snaksalot said:
No it most definitely was not very clever at all and unfortunately I'm stuck : / Also is the G930UUEU9CSA3 firmware not unbranded?
Click to expand...
Click to collapse
Yes it is I didn't read properly. Anyway what odin are you using to flash? The modified one?
We are talking about a qualcomm device yes?
cooltt said:
Yes it is I didn't read properly. Anyway what odin are you using to flash? The modified one?
We are talking about a qualcomm device yes?
Click to expand...
Click to collapse
Yes I'm using the modified Odin and all my previous attempts at flashing the eng boot files via Odin on the v8 bootloader have been successful, it wasn't until after the OTA that I started having issues.
And yes this is Qualcomm : )
snaksalot said:
Yes I'm using the modified Odin and all my previous attempts at flashing the eng boot files via Odin on the v8 bootloader have been successful, it wasn't until after the OTA that I started having issues.
And yes this is Qualcomm : )
Click to expand...
Click to collapse
Hmmm so it may be that loophole is now closed, what you need to think about is if you deffo need root? Or is it just nice to have. I'm sure a dev will get round it soon.
snaksalot said:
I'm fairly certain that the only twrp for the s7 is a temporary one because there is no unlock for the bootloader, and even still the temp twrp is only compatible with the v4 bootloader and I am currently on v9.... that is unless I'm mistaken if I am then please someone correct me and point me in the right direction because I'd love to be running magisk on my s7 : )
Click to expand...
Click to collapse
Twrp will work certainly, i did on my own s7 qualcomm variant with this https://www.google.com/amp/s/forum....de-how-to-root-android-8-0-oreo-t3840271/amp/
kpwnApps said:
Twrp will work certainly, i did on my own s7 qualcomm variant with this https://www.google.com/amp/s/forum....de-how-to-root-android-8-0-oreo-t3840271/amp/
Click to expand...
Click to collapse
Okay I was completely unaware of TWRP being an option or the possibility of Magisk with a locked bootloader, now to clarify I'm running the latest unbranded US Region firmware for the US T-Mobile version of the Qualcomm Galaxy S7 "(TMB) G930UUEU9CSA3" that being said I have a few questions about how to specifically to proceed if you don't mind helping me?
First is the version of Odin available from the post provided above inst the modified version I've been required to use for all my previous flashing "Odin3_v3.13.1_3B_PatcheD" should I use this one or the version provided in the post above "Odin3_v3.13.1"?
My next question is that all the different versions and variants of TWRP available for my device the Galaxy S7 and the S7 Edge are either for Exynos Canada/International or Korea or the Chinese Qualcomm variant of each. Should I download and use the TWRP for the Chinese Qualcomm S7?
The sammobile link in the original post for "Android 8.0 Oreo Stock Rom" provides me with a list of the latest and up to date international versions of firmware for the Galaxy S7 Edge "SM-G935FD" I'm assuming I should just use the stock firmware image for my device "SM-G930U" instead?
The link for the no-verity-opt-encrypt-6.0 is dead but I don't think its needed because of something someone said in the original post about this method failing after latest security update "the one I'm on" https://forum.xda-developers.com/showpost.php?p=78115895&postcount=18 he said he solved it easily with information and another flash able zip from this post https://forum.xda-developers.com/showpost.php?p=77000849&postcount=47 and the zip from here https://forum.xda-developers.com/showpost.php?p=76564735&postcount=37
All that being said I haven't attempted anything yet, I'll try the above method as I understand it later this evening and I'll post my results
snaksalot said:
All that being said I haven't attempted anything yet, I'll try the above method as I understand it later this evening and I'll post my results
Click to expand...
Click to collapse
Hello there, i deleted most of your post because i didn't want my post to be huge. So if i just give you some guidelines hopefully you can have a look around for the files you need.
1. For Qualcomm / snapdragon devices you must always use the patched version of Odin you already have. Now this version of Odin can be dangerous if you don't flash the correct firmware for your device because it ignores device mismatch and other safety measures the normal Odin checks for before flashing. Which brings me to.....
2. Anything for G935 will not work for G930 including TWRP, you must always use firmware, patches twrp which specifically says it for G930 Qualcomm/snapdragon devices.
3. The China/ Korea Qualcomm/snapdragon devices are exactly the same as the US devices, anything working on the China / Korea devices will work on the US device.
Now i know you want to root unbranded on V9 but as you are on the T Mobile network it may be easier to flash and root T Mobile Oreo for the time being until there is a workaround root for V9 unbranded.
All of the threads you linked to were for G935 devices and i've mentioned you can't use those patches BUT the process and step by step instructions you follow are the same for your device. So you can follow those guides as long as you are using the patches for your device.
There is a Snapdragon section on this forum so thats a good place to look.
I've had a quick look for this specific firmware and can't find anything about rooting the U9 version yet.....
I'm just checking this firmware G930UUEU9CSA3 your running did have either XAA or USC code next to it when you downloaded? I've noticed Verizon, AT&T and Sprint are using the same firmware VZN, ATT, XAS.
cooltt said:
Hello there, i deleted most of your post because i didn't want my post to be huge. So if i just give you some guidelines hopefully you can have a look around for the files you need.
1. For Qualcomm / snapdragon devices you must always use the patched version of Odin you already have. Now this version of Odin can be dangerous if you don't flash the correct firmware for your device because it ignores device mismatch and other safety measures the normal Odin checks for before flashing. Which brings me to.....
2. Anything for G935 will not work for G930 including TWRP, you must always use firmware, patches twrp which specifically says it for G930 Qualcomm/snapdragon devices.
3. The China/ Korea Qualcomm/snapdragon devices are exactly the same as the US devices, anything working on the China / Korea devices will work on the US device.
Now i know you want to root unbranded on V9 but as you are on the T Mobile network it may be easier to flash and root T Mobile Oreo for the time being until there is a workaround root for V9 unbranded.
All of the threads you linked to were for G935 devices and i've mentioned you can't use those patches BUT the process and step by step instructions you follow are the same for your device. So you can follow those guides as long as you are using the patches for your device.
There is a Snapdragon section on this forum so thats a good place to look.
I've had a quick look for this specific firmware and can't find anything about rooting the U9 version yet.....
I'm just checking this firmware G930UUEU9CSA3 your running did have either XAA or USC code next to it when you downloaded? I've noticed Verizon, AT&T and Sprint are using the same firmware VZN, ATT, XAS.
Click to expand...
Click to collapse
I'd be interested to know how this turned out if the device with V9 bootloader could be rooted with temp TWRP method.
Can i actually flash magisk on my 930u?
Is there any way to root my g930t ?
I'm on v9 bootloader, and i don't care about knox tripping.
Did developpers really failed to break the security of this little old device ? Or no one worked it ?
cooltt said:
Hello there, i deleted most of your post because i didn't want my post to be huge. So if i just give you some guidelines hopefully you can have a look around for the files you need.
1. For Qualcomm / snapdragon devices you must always use the patched version of Odin you already have. Now this version of Odin can be dangerous if you don't flash the correct firmware for your device because it ignores device mismatch and other safety measures the normal Odin checks for before flashing. Which brings me to.....
2. Anything for G935 will not work for G930 including TWRP, you must always use firmware, patches twrp which specifically says it for G930 Qualcomm/snapdragon devices.
3. The China/ Korea Qualcomm/snapdragon devices are exactly the same as the US devices, anything working on the China / Korea devices will work on the US device.
Now i know you want to root unbranded on V9 but as you are on the T Mobile network it may be easier to flash and root T Mobile Oreo for the time being until there is a workaround root for V9 unbranded.
All of the threads you linked to were for G935 devices and i've mentioned you can't use those patches BUT the process and step by step instructions you follow are the same for your device. So you can follow those guides as long as you are using the patches for your device.
There is a Snapdragon section on this forum so thats a good place to look.
I've had a quick look for this specific firmware and can't find anything about rooting the U9 version yet.....
I'm just checking this firmware G930UUEU9CSA3 your running did have either XAA or USC code next to it when you downloaded? I've noticed Verizon, AT&T and Sprint are using the same firmware VZN, ATT, XAS.
Click to expand...
Click to collapse
Would this info be applicable to edge models as well? Pretty sure our moderator has moved on as he is disgusted with samsungs persistance in blocking root with new bl versions. Im on an unlocked tmo s7 edge with the u firmware as well.
Toolmighty said:
Would this info be applicable to edge models as well? Pretty sure our moderator has moved on as he is disgusted with samsungs persistance in blocking root with new bl versions. Im on an unlocked tmo s7 edge with the u firmware as well.
Click to expand...
Click to collapse
Yes same hardware
cooltt said:
Yes same hardware
Click to expand...
Click to collapse
Can't get twrp to flash. Tried w rom as is, tried factory reset tried reinstall w/o auto reboot. All get same error
what about jruze root?
what about https://forum.xda-developers.com/verizon-s7-edge/how-to/root-s7-s7edge-oreo-nougat-t3819616 then flash from safestrap, format data, decript script?
nm it uses flashfire
Toolmighty said:
what about https://forum.xda-developers.com/verizon-s7-edge/how-to/root-s7-s7edge-oreo-nougat-t3819616 then flash from safestrap, format data, decript script?
Click to expand...
Click to collapse
Yes by using 1st and #1623 post number it can be rooted easily. I already have done that on both G930P and G930U.
Hey everyone hope you're all well. I have an s8 plus that's not booting. Here's the events that transpired....
My nephew wanted it wiped so I went into recovery and it immediately started to install an update for some reason and wouldn't boot, so I told his brother to flash a stock ROM which he did and booted fine, but with one issue, it showed as 16gb instead of 64gb. At this point I downloaded a pit file and flashed it. I then flashed the stock ROM and it won't get past the Samsung logo.
This is the stock ROM I flashed, AP_G955FXXSADTI1_CL18920278_QB34109287_REV00_user_low_ship_meta_OS9
I'm guessing I need to flash the correct pit file and then the stock ROM?
Any advice would be appreciated
Thanks!
thedan55 said:
Hey everyone hope you're all well. I have an s8 plus that's not booting. Here's the events that transpired....
My nephew wanted it wiped so I went into recovery and it immediately started to install an update for some reason and wouldn't boot, so I told his brother to flash a stock ROM which he did and booted fine, but with one issue, it showed as 16gb instead of 64gb. At this point I downloaded a pit file and flashed it. I then flashed the stock ROM and it won't get past the Samsung logo.
This is the stock ROM I flashed, AP_G955FXXSADTI1_CL18920278_QB34109287_REV00_user_low_ship_meta_OS9
I'm guessing I need to flash the correct pit file and then the stock ROM?
Any advice would be appreciated
Thanks!
Click to expand...
Click to collapse
Flash full firmware not just AP file. Flashing AP file only is more than likely the reason for difference in storage size.
No need for pit file. If it is needed it can be exacted from the firmware that you have downloaded.
I did flash all 4 files not just the ap. I only wanted to show the version etc
Now when I try to flash Odin says failed
What Odin version are you using
What errors in Odin
Can you post a copy of download mode and error in Odin
spawnlives said:
What Odin version are you using
What errors in Odin
Can you post a copy of download mode and error in Odin
Click to expand...
Click to collapse
Absolutely. Odin3 3.13
I've also attached a picture of the rom files. For some reason there's 2 CSC files. I tried using both but same issue.
thedan55 said:
Absolutely. Odin3 3.13
I've also attached a picture of the rom files. For some reason there's 2 CSC files. I tried using both but same issue.
Click to expand...
Click to collapse
1. CSC files
CSC file will wipe all apps and data ( same as out of the box )
HOME_CSC file will keep apps and data
2. The reason Odin is failing is you are trying to downgrade your firmware.
You are on bootloader version 11 the firmware you are flashing is on version 10. You can check in download mode to check bootloader version. There will be a line saying AP SWREV. The number after the letter B is your bootloader number.
Also in download mode down the bottom ( in red ) will tell the reason why it is failing.
You will have to find what firmware was flash before or wait for samsung to upgrade it's bootloader version.
spawnlives said:
1. CSC files
CSC file will wipe all apps and data ( same as out of the box )
HOME_CSC file will keep apps and data
2. The reason Odin is failing is you are trying to downgrade your firmware.
You are on bootloader version 11 the firmware you are flashing is on version 10. You can check in download mode to check bootloader version. There will be a line saying AP SWREV. The number after the letter B is your bootloader number.
Also in download mode down the bottom ( in red ) will tell the reason why it is failing.
You will have to find what firmware was flash before or wait for samsung to upgrade it's bootloader version.
Click to expand...
Click to collapse
I see. The strange thing is that this is the firmware that my nephew flashed after it initially failed and it flashed with no errors. The errors only occurred after I tried to flash the pit file, which I'm guessing was a big mistake.
Right so I need to find a stock ROM with bootloader 11. Is there an indicator in the filename that will tell me the bootloader version?
Why do I get this message every day? Throw the darn thing out already.
thedan55 said:
I see. The strange thing is that this is the firmware that my nephew flashed after it initially failed and it flashed with no errors. The errors only occurred after I tried to flash the pit file, which I'm guessing was a big mistake.
Right so I need to find a stock ROM with bootloader 11. Is there an indicator in the filename that will tell me the bootloader version?
Click to expand...
Click to collapse
Flashing the pit file should only fix the partition size and is generally not needed. Flashing the wrong pit file will cause issues. Doesn't effect the issue of trying to downgrading firmware.
As far I'm aware official samsung firmware is up to bootloader 10. Firmware should be downloaded from official site like sammobile or updato or pc apps like samfirm or frija
In regards to bootloader version ( official firmware ) it can be found in the firmware being downloaded.
Bootloader version will be the fifth number/letter from the right of firmware name.
eg:
G955FXXSADTI1 - A - bootloader version 10. I'm assuming the next bootloader version number will start with B
G955FXXU9DTF1 - 9 - bootloader version 9
The higher the number the higher the bootloader version.
Due to samsung anti róll back bootloader version cannot be downgraded.
Buy your nephew a damn phone
thedan55 said:
I see. The strange thing is that this is the firmware that my nephew flashed after it initially failed and it flashed with no errors. The errors only occurred after I tried to flash the pit file, which I'm guessing was a big mistake.
Right so I need to find a stock ROM with bootloader 11. Is there an indicator in the filename that will tell me the bootloader version?
Click to expand...
Click to collapse
pego99 said:
Buy your nephew a damn phone
Click to expand...
Click to collapse
I did buy him this phone. Just because it's a little messed up right now doesn't mean I should just thrown it out. This entire forum is dedicated to invigorating devices and keeping them going. XDA didn't accept the philosophy of throwing out devices when they can be repaired. I've been here long enough to know that.
Ffs people are still developing for the hp touchpad and m7 Windows devices!
Unsubscribe from this thread mate. Delete your replies so you don't notifications.
There's no need for your unhelpful comments when others are trying to be of assistance.
spawnlives said:
Flashing the pit file should only fix the partition size and is generally not needed. Flashing the wrong pit file will cause issues. Doesn't effect the issue of trying to downgrading firmware.
As far I'm aware official samsung firmware is up to bootloader 10. Firmware should be downloaded from official site like sammobile or updato or pc apps like samfirm or frija
In regards to bootloader version ( official firmware ) it can be found in the firmware being downloaded.
Bootloader version will be the fifth number/letter from the right of firmware name.
eg:
G955FXXSADTI1 - A - bootloader version 10. I'm assuming the next bootloader version number will start with B
G955FXXU9DTF1 - 9 - bootloader version 9
The higher the number the higher the bootloader version.
Due to samsung anti róll back bootloader version cannot be downgraded.
Click to expand...
Click to collapse
Thank you very much for your replies. It's very much appreciated mate.
I did flash the pit file and subsequently got errors in odin. I want aware that I was trying to downgrade. I've download from official site and will try flashing today.
Again thanks for the help. Been a while since I've had to do this lol I think the last device I was rooting and roming was my note 3! The support for it is still going strong though!
Cheers
I guess at some point its best to move on. My grandsons S8 had the digitizer go bad tried to fix unsuccessfully bought him a used on on fleabay for $150.
@spawnlives thank you very much. Phone is back up running perfectly. Appreciate it mate
@pego99 that's a judgment call. Fair enough buying an s8 screen is 100 and new is 150 it would be reasonable to buy a new device. However this was a software issue which costs nothing to fix. Your posts in this thread are redundant and useless.
thedan55 said:
@spawnlives thank you very much. Phone is back up running perfectly. Appreciate it mate
@pego99 that's a judgment call. Fair enough buying an s8 screen is 100 and new is 150 it would be reasonable to buy a new device. However this was a software issue which costs nothing to fix. Your posts in this thread are redundant and useless.
Click to expand...
Click to collapse
OK it costs nothing money wise but time but time is valuable. i.e. If you spend the next 6 months on this has it cost anything? Nope no out of pocket but a lot of time and nephew has no phone to use. BTW If you bought the phone in working condition how did it get screwed up anyway?
pego99 said:
OK it costs nothing money wise but time but time is valuable. i.e. If you spend the next 6 months on this has it cost anything? Nope no out of pocket but a lot of time and nephew has no phone to use. BTW If you bought the phone in working condition how did it get screwed up anyway?
Click to expand...
Click to collapse
It took less than an hour to fix this phone, that's a cost I can stomach.
if you had actually READ the post instead of commenting asinine remarks them you would know how the phone for corrupted in the first place.
Please stop replying to this now.
Hello
I've been reading forums and downloading files for days. Many of the links in the posts no longer work. Posts are 5 years and older. There are no new ones. At least not one that actually works. Downgrade I mean. That's why I wrote this question and I'm asking for help - how to really downgrade my Galaxy S6 G920F.
Thanks for the help.
PSA: Downgrading WILL void your warranty!
What have you already done (what method, software) have you already tried?
The 100% surefire way to downgrade your phone (or any android phone really), is to:
1. Backup your phone data.
2. Switch the phone into download mode, connect to PC, boot into TWRP recovery through fastboot
3. Wipe your 7.0 firmware and all data
4. Flash android 5.02 ROM
For a samsung phones ODIN + Freya is also an option. Odin is a samsung's firmware flashing tool, Freya is a 3rd party program that can download the stock firmware android for you. All of these tools are available online, and you can ask on a samsung subsection of XDA about how to use them - people can give you up to date links.
I'm laughing because you write quite a lot in three days. Of course, this method does not work.
Is there anyone willing to help?
Totesnochill said:
PSA: Downgrading WILL void your warranty!
What have you already done (what method, software) have you already tried?
The 100% surefire way to downgrade your phone (or any android phone really), is to:
1. Backup your phone data.
2. Switch the phone into download mode, connect to PC, boot into TWRP recovery through fastboot
3. Wipe your 7.0 firmware and all data
4. Flash android 5.02 ROM
For a samsung phones ODIN + Freya is also an option. Odin is a samsung's firmware flashing tool, Freya is a 3rd party program that can download the stock firmware android for you. All of these tools are available online, and you can ask on a samsung subsection of XDA about how to use them - people can give you up to date links.
Click to expand...
Click to collapse
That is assuming they have TWRP.
Also, the part you mention about "boot into download mode, connect to PC then boot to TWRP via fastboot" is not correct because Samsung is not compatible with fastboot, adb works but fastboot does not. Some Samsung devices technically have a "fastboot mode" but it isn't functional, it doesn't respond to fastboot commands, it's basically useless.
Also, you can't flash a firmware that has a lower binary than the currently installed firmware so if the binary of the downgraded firmware is lower than the binary of the currently installed firmware, the downgraded firmware can't be flashed.
Samsung is making it harder and harder to downgrade their devices.
OK. I'm afraid I'm missing the point of what's being said.
I know it is possible and there are also posts about it, but they are old, the links in them do not work. I'm asking for an expert who knows how to do this, philosophizing about what it would be like if it somehow doesn't really help me and I'm not interested either
I'm only interested in a positive thought, help and not brainstorming, if you understand me?
No offense