Related
I have a Sprint variant of the S4 and I want to unroot it. But I used Triangle Away and it's not resetting the binary count. TA is says that "Status cannot be determined..."
Why do all the tutorials say that this will work on the Sprint S4 when TA reboots the device, it says "Could not find triangle and counter date..."
What the heck is going on????
heyjoojoo said:
I have a Sprint variant of the S4 and I want to unroot it. But I used Triangle Away and it's not resetting the binary count. TA is says that "Status cannot be determined..."
Why do all the tutorials say that this will work on the Sprint S4 when TA reboots the device, it says "Could not find triangle and counter date..."
What the heck is going on????
Click to expand...
Click to collapse
You're probably on MF9. I believe Triangle Away only works for MDL and earlier.
Sent from my SPH-L720 using XDA Premium 4 mobile app
heyjoojoo said:
I have a Sprint variant of the S4 and I want to unroot it. But I used Triangle Away and it's not resetting the binary count. TA is says that "Status cannot be determined..."
Why do all the tutorials say that this will work on the Sprint S4 when TA reboots the device, it says "Could not find triangle and counter date..."
What the heck is going on????
Click to expand...
Click to collapse
You have to be on MDL or MDC for triangle away to work. You also need the stock kernel and recovery installed to reset everything.
This message brought to you in part by Sprint and the letters GS and the number 4
So am I stuck? or is there a way to reset my binary count?
I keep trying to flash the current kernel (MF9) with a MDL but after rebooting, the device still shows MF9.
GiantJay said:
You have to be on MDL or MDC for triangle away to work. You also need the stock kernel and recovery installed to reset everything.
This message brought to you in part by Sprint and the letters GS and the number 4
Click to expand...
Click to collapse
I keep trying to flash the rom with MDL roms but they're not sticking. I've tried several MDL ROMs. I also tried flashing just the kernel via Odin and no change in the MF9.
heyjoojoo said:
I keep trying to flash the rom with MDL roms but they're not sticking. I've tried several MDL ROMs. I also tried flashing just the kernel via Odin and no change in the MF9.
Click to expand...
Click to collapse
I have a thread on this in q and a. Good luck is all I can say. Last time I tried to get rid of mf9 I couldn't figure it out.
This message brought to you in part by Sprint and the letters GS and the number 4
GiantJay said:
I have a thread on this in q and a. Good luck is all I can say. Last time I tried to get rid of mf9 I couldn't figure it out.
This message brought to you in part by Sprint and the letters GS and the number 4
Click to expand...
Click to collapse
The problem is that I'm trying to reset the binary counter. All these youtube videos and tutorials indicate that it can be done. But I have had no success thus far. And it seems that the MF9 update is the culprit.
heyjoojoo said:
The problem is that I'm trying to reset the binary counter. All these youtube videos and tutorials indicate that it can be done. But I have had no success thus far. And it seems that the MF9 update is the culprit.
Click to expand...
Click to collapse
Here's how I did it the other day. I was going from rooted MDL (stock rom with some tweaks) to MF9. So I had to get back to unrooted MDL first. I followed the "Reverting to Unmodified Stock MDL to update to Stock MF9" section of this thread to do it:
http://forum.xda-developers.com/showthread.php?t=2277480
I did a factory reset first. ODIN'd the MDL tar in that section. That did not set me all the way back to official on the download screen, though. I ran Triangle Away at that point, but it made no difference. So I did another factory reset and that did the trick. I was all back to official and unrooted.
I then installed MF9 using the very next section of the above thread. It was also showing official in the download screen.
jejb said:
Here's how I did it the other day. I was going from rooted MDL (stock rom with some tweaks) to MF9. So I had to get back to unrooted MDL first. I followed the "Reverting to Unmodified Stock MDL to update to Stock MF9" section of this thread to do it:
http://forum.xda-developers.com/showthread.php?t=2277480
I did a factory reset first. ODIN'd the MDL tar in that section. That did not set me all the way back to official on the download screen, though. I ran Triangle Away at that point, but it made no difference. So I did another factory reset and that did the trick. I was all back to official and unrooted.
I then installed MF9 using the very next section of the above thread. It was also showing official in the download screen.
Click to expand...
Click to collapse
So, I should unroot back to MDL stock (but not the MF9 stock). Then root with a MDL or MDC based ROM. Run Triangle Away but do a Factory reset?
heyjoojoo said:
So, I should unroot back to MDL stock (but not the MF9 stock). Then root with a MDL or MDC based ROM. Run Triangle Away but do a Factory reset?
Click to expand...
Click to collapse
No, follow the directions to get back to MDL unrooted, stock rom. Do not root it once there. You may have to do a couple of factory resets for the binaries to get reset so that it's all "official" on the Download screen. Once you get to that point - all official - then take the OTA to go to MF9. That will give you stock rom, unrooted, all official MF9.
From there you can root or not, up to you. I did. But my download screen says custom again of course, now that I've rooted my MF9.
The issue that I had was getting rid of the mf9 software and baseband. Whenever I flashed mdl the mf9 software and baseband would still be there. I gave up but I need to unroot still and get back to all stock with no custom binary too. I think I might try today again.
This message brought to you in part by Sprint and the letters GS and the number 4
---------- Post added at 12:57 PM ---------- Previous post was at 12:35 PM ----------
Here's the thread I created a while ago. http://forum.xda-developers.com/showthread.php?t=2382188
This message brought to you in part by Sprint and the letters GS and the number 4
jejb said:
No, follow the directions to get back to MDL unrooted, stock rom. Do not root it once there. You may have to do a couple of factory resets for the binaries to get reset so that it's all "official" on the Download screen. Once you get to that point - all official - then take the OTA to go to MF9. That will give you stock rom, unrooted, all official MF9.
From there you can root or not, up to you. I did. But my download screen says custom again of course, now that I've rooted my MF9.
Click to expand...
Click to collapse
Success!!!! Thank you so much for your help!!!!
Product Name: SPH-L720
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
Glad it worked for you. Remember to hit the "Thanks" button, if you would be so kind.
jejb said:
Glad it worked for you. Remember to hit the "Thanks" button, if you would be so kind.
Click to expand...
Click to collapse
Lol. I don't think 99% of the people on this website even know that there is a thanks button, or don't know how to use it. Gave up a long time ago on that one.
This message brought to you in part by Sprint and the letters GS and the number 4
I think MF9 locks the baseband in odin when you trip the counter. I found the easiest way to downgrade was to odin MDL or MDC and then let it boot up. It will show as baseband of MF9 still. Go back into odin one more time and load the same version as the first time. The second time will change the baseband because the bootloader is using the MDL or MDC version and not the MF9 version so the second time everything will change and when you re-boot you won't see MF9 anymore. At least this works for me. Hope it helps someone else.
So I upgraded from 4.4.2 kitkat to 5.0 lollipop. However, I soft bricked my phone by installing the wrong xposed SDK. Now I'm trying to flash 4.4.2 kitkat back onto my bricked phone and then update back to lollipop. Problem is ODIN is not wanting to flash the g900a stock rom back. It gives me an error saying 'SW REV CHECK FAIL : [ABOOT]FUSED 2 > BINARY 1' does anyone know how to fix this as I'd like to fix my phone soon!
900A? That's the AT&T model isn't it? That being the case, the locked bootloader on your device is only ever going to let you flash 5.0 if you had 5.0 on your device before you bricked....
http://i.imgur.com/rVnFwJM.jpg
help
keithross39 said:
900A? That's the AT&T model isn't it? That being the case, the locked bootloader on your device is only ever going to let you flash 5.0 if you had 5.0 on your device before you bricked....
Click to expand...
Click to collapse
That's good an all but where can I find a 5.0 in a tar format! My phone is literally bricked so I can't access it to flash the .zip files to it. I can't find a .tar of lollipop 5.0 anywhere no matter where I look all the links for ones have been taken down! You wouldn't happen to have one would you?
Not sure fella.....checked every hosting/firmware website I can think of, and all I'm seeing are KitKat firmwares.....
Have you tried Kies to see if it'll perform an 'emergency recovery/restore'?
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
Not sure fella.....checked every hosting/firmware website I can think of, and all I'm seeing are KitKat firmwares.....
Have you tried Kies to see if it'll perform an 'emergency recovery/restore'?
Click to expand...
Click to collapse
Kies won't recognize my device! It just says it's not supported! ;-; this is really unfortunate I've been looking everywhere with what little time I have (I work and I'm in college and it's around finals season for the semester so that doesn't help with time to fix this). I've been scouring everywhere but can't find anything. This is really unfortunate and I don't have the money to afford to have my phone fixed ;-; I'm really hoping I can find a solution soon! Everytime I try to install a kitkat 4.4.2 rom it just says FUSED 2 > BINARY 1 or something along those lines. From what I've heard that means I can't downgrade. Like I said what happened was I installed the wrong xposed sdk and it soft bricked. Every lollipop 5.0 rom I've found is in zip format. Now this wouldn't be a problem if I had a custom recovery that could flash zips and the means to put the zip on the phone. The problem is I don't (yes I've tried using ADB it refuses to put the zip on the phone it only lets me put .tar.md5's on there with the sideload and everything else just returns an error). If you find a solution or anyone else does please let me know! I'm In very dire need of help!! Also, my phone it makes it to the samsung galaxy s5 powered by android screen and then after that I just hear the AT&T noise but the screen doesn't change it just hangs there. I've also tried a full cache wipe and system restore in the recovery menu!
First of all.....The obvious....lol
These zips you mention, have you extracted them to see what's inside them.....
I know that sammobile and Samsung-updates provide their firmware .tars inside zips.....
Secondly, until someone makes an AT&T Lollipop firmware available, it looks like you're going to have to play the waiting game......at this point, I believe that with the correct firmware package, you WILL be able to recover your device....that may not be true further down the line if you continue to try 'potential' fixes.....
My advice is to leave it 'as-is' (unsatisfactory...I know) and wait for the firmware to become available......
Do you have an older device you can use in the mean time?
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
First of all.....The obvious....lol
These zips you mention, have you extracted them to see what's inside them.....
I know that sammobile and Samsung-updates provide their firmware .tars inside zips.....
Secondly, until someone makes an AT&T Lollipop firmware available, it looks like you're going to have to play the waiting game......at this point, I believe that with the correct firmware package, you WILL be able to recover your device....that may not be true further down the line if you continue to try 'potential' fixes.....
My advice is to leave it 'as-is' (unsatisfactory...I know) and wait for the firmware to become available......
Do you have an older device you can use in the mean time?
Click to expand...
Click to collapse
Yes I unzipped the zip. It was just files inside. I might just take it by an AT&T I'm pretty sure with all I've done to it the warranty is void but it's a worth a shot maybe they will take it in. I don't have an older device right now and I need to have some my phone soon as I have important usage of it with work. It seems I guess I don't have a choice left ;-; thank you though for all your help I'm very thankful for it
hey
Could someone please please help me get my tablet (sm-t337a) Back on. My tablet has been off for the last 12 hours try to figure out how to restore back to stock. i am literrally pulling my hair out! I rooted it with Kingroot and when I restarted, I was locked out. Now, I have Odin up with the stock firmware version downloaded but I keep getting this error.
I keep getting this error message when restoring through odin SW REV CHECK FAIL: [ABOOT]FUSED 2 > BINARY 1
Please could someone tell me a fix for this i would really really really appreciate it. FYI I am a noobie with it comes to this stuff. Ive successfully rooted phones in the past using walkthroughs
Thank you
"You are trying to load old firmware on a phone that has already been updated at some point in its life. You can not go backwards in firmware except 5.0 can be back reved to 4.4.4"
Credits to @donc113
Oh okay.. So does anyone know what to do then? Is it possible to reverse the root or something? I read somewhere about how a pit file could help?
Thanks
mr_p_man said:
Oh okay.. So does anyone know what to do then? Is it possible to reverse the root or something? I read somewhere about how a pit file could help?
Thanks
Click to expand...
Click to collapse
I was just in your position myself. Just flash the lp fix boot tar with Odin from the bottom of first post of thread below:
http://forum.xda-developers.com/tab-4/general/rooted-nk2-att-t377a-t2992639
You may need to factory reset in recovery afterwards, I borked mine so bad I had to take to best buy to have them reflash 5.1.1 firmware since we do not have access to that file.
Hope this helps!
Did they do that free of charge? I have the tablet 4 8.0 sm-t337a and I rooted it, was working fine then got message about att found dead software blah blah blah..but now when it boots up, I can't get the samsumg setup menu...been like this for days now...I tried LP boot loop fix...and no luck.
Wrong battery info with lollipop?
Best Buy wanted to charge me forty bucks to upgrade from a rooted KK to L. Others have been more successful.
Can someone with a t337a running lollipop check their battery capacity in settings_general_about device. Mine is showing only 2400mah @ 5v. Odd.
I haven't changed the battery, so it should be 4450mah @ 3.7v. Right?
My s4 was rooted about a year ago with the logo SAMSUNG and Unlocked with an open lock below it when it boots up. I gave this phone to my girlfriends daughter and forgot to tell her not to try and update it. I don't remember the way i rooted it or what software it had on it at the time.
So when I go to recovery after it loads into an AT&T logo and tries to install it and it gets to 24%. After this it bootloops. Any help would be appreciated. My phone model is SGH-I337 , also not sure of what the original firmware is.
StephenTiz said:
My s4 was rooted about a year ago with the logo SAMSUNG and Unlocked with an open lock below it when it boots up. I gave this phone to my girlfriends daughter and forgot to tell her not to try and update it. I don't remember the way i rooted it or what software it had on it at the time.
So when I go to recovery after it loads into an AT&T logo and tries to install it and it gets to 24%. After this it bootloops. Any help would be appreciated. My phone model is SGH-I337 , also not sure of what the original firmware is.
Click to expand...
Click to collapse
Open lock symbol means your phone is rooted not unlocked.
If you could go to the recovery mode (voloume-up+home+power) it would tell you your firmware version. You could try clear cache, factory reset in recovery mode. If it still gives you the bootloop, you might need to flash the firmware via odin.
You can find instructions and necessary files in here and here.
No recovery options
Sorry I left that part out. When it goes to recovery i get the blue text that say recovery then it goes straight to the AT&T installing. So no recovery options. I can still get to the Odin dowloading screen though and it says im running Samsung Original software
No recovery options
sway8966 said:
Open lock symbol means your phone is rooted not unlocked.
If you could go to the recovery mode (voloume-up+home+power) it would tell you your firmware version. You could try clear cache, factory reset in recovery mode. If it still gives you the bootloop, you might need to flash the firmware via odin.
You can find instructions and necessary files in here and here.
Click to expand...
Click to collapse
Sorry I left that part out. When it goes to recovery i get the blue text that say recovery then it goes straight to the AT&T installing. So no recovery options. I can still get to the Odin dowloading screen though and it says im running Samsung Original software
StephenTiz said:
Sorry I left that part out. When it goes to recovery i get the blue text that say recovery then it goes straight to the AT&T installing. So no recovery options. I can still get to the Odin dowloading screen though and it says im running Samsung Original software
Click to expand...
Click to collapse
One reason I asked you to go to the recovery option was to know what version of firmware you were on before .
Do you remember you were on jelly bean or kick-kat or lollipop? If you do you can find the firmware for jelly bean and kit-kat on the links I mentioned in the previous message.
If you could not recall your firmware, the latest odin flashable firmware we have is kit-kat NB1.
You can flash that one to revive your phone. Then use twoel root to root the phone. After that you can go to lollipop if you want. All the instructions are there.
Woop Woop!
sway8966 said:
One reason I asked you to go to the recovery option was to know what version of firmware you were on before .
Do you remember you were on jelly bean or kick-kat or lollipop? If you do you can find the firmware for jelly bean and kit-kat on the links I mentioned in the previous message.
If you could not recall your firmware, the latest odin flashable firmware we have is kit-kat NB1.
You can flash that one to revive your phone. Then use twoel root to root the phone. After that you can go to lollipop if you want. All the instructions are there.
Click to expand...
Click to collapse
It worked. I have tried so many different firmware and kit-kat NB1 worked perfectly. Thank you so much, my girlfriends daughter will be so happy. I think i will leave it unrooted for now. I hope this post helps someone else in the future.
StephenTiz said:
It worked. I have tried so many different firmware and kit-kat NB1 worked perfectly. Thank you so much, my girlfriends daughter will be so happy. I think i will leave it unrooted for now. I hope this post helps someone else in the future.
Click to expand...
Click to collapse
I am glad that it works out for you.
Rooting is so easy from that point. Just get towel root and root it. The link also included in my previous post. After the root you might need to disable the AT&T OTA update too. The instructions are also in that post too.
I flashed the firmware from here https://forum.xda-developers.com/tmobile-s7-edge/how-to/6-8-t-mobile-935u-firmware-qe2-t3619151 along with the Tmobile radio via Odin 3.13.1, it failed in Odin and now the phone is stuck on the samsung logo. I used the BL and the AP from the zip, the CP I used from the separate tmobile download link. For the CSC I first tried the CSC that is in the package and when that failed I tried the HOME CSC even that failed. the User data I kept blank both times.. Then I tried it a third time same as above except in the CSC I put the CSC file from the zip and in Userdata I put the Home CSC file, it failed again. Am i doing something wrong ?
Update: I have been trying to flash the stock firmware from samobile, but I am unable to do even that. It keeps failing. I downloaded the firmware from here https://www.sammobile.com/firmwares/...S5BRA1/206887/, extracted it, added just the AP and as per instructions went in to download mode, clicked on start and it keeps failing. In Options only auto reboot and f reset is clicked.
I would really appreciate any help to unbrick this device, it is stuck on an exclamation mark saying " An error has occurred while updating the device software. Use the emergency recovery function in the smart switch PC software". Smartswitch is not recognizing this device saying it's an unsupported device so emergency restore software wont work from there. I can get it into download mode but as I said flashing the firmware via Odin is not working. I can also get it into recovery mode but it keeps endlessly trying to update, fail and loop back to trying to update.
Thanks in advance.
Firstly I would check your use cable, I have a bunch and not all of them work. Secondly, make sure that your phone is being recognized on PC, hence the cable check. and third, make sure you are flashing the correct firmware. You said TMB, but I see you are flashing 3 different company files. Hi back to full G935P firmware , you front need to flash TMB on t, it should be fine cause I have a g935p with TMB sim in it
Anything else I'll be glad to help
bothambhai said:
I flashed the firmware from here https://forum.xda-developers.com/tmobile-s7-edge/how-to/6-8-t-mobile-935u-firmware-qe2-t3619151 along with the Tmobile radio via Odin 3.13.1, it failed in Odin and now the phone is stuck on the samsung logo. I used the BL and the AP from the zip, the CP I used from the separate tmobile download link. For the CSC I first tried the CSC that is in the package and when that failed I tried the HOME CSC even that failed. the User data I kept blank both times.. Then I tried it a third time same as above except in the CSC I put the CSC file from the zip and in Userdata I put the Home CSC file, it failed again. Am i doing something wrong ?
Update: I have been trying to flash the stock firmware from samobile, but I am unable to do even that. It keeps failing. I downloaded the firmware from here https://www.sammobile.com/firmwares/...S5BRA1/206887/, extracted it, added just the AP and as per instructions went in to download mode, clicked on start and it keeps failing. In Options only auto reboot and f reset is clicked.
I would really appreciate any help to unbrick this device, it is stuck on an exclamation mark saying " An error has occurred while updating the device software. Use the emergency recovery function in the smart switch PC software". Smartswitch is not recognizing this device saying it's an unsupported device so emergency restore software wont work from there. I can get it into download mode but as I said flashing the firmware via Odin is not working. I can also get it into recovery mode but it keeps endlessly trying to update, fail and loop back to trying to update.
Thanks in advance.
Click to expand...
Click to collapse
just checking... are you using the edited princecomsy odin? http://d-h.st/gsDA or use the link here https://forum.xda-developers.com/att-s7-edge/help/princes-odin-t3545104
find the correct rom here https://forum.xda-developers.com/sprint-s7-edge/how-to/odin-stock-nougat-firmware-s7-edge-t3569834
just use files from one rom at a time. get good at that first. maybe you are careful but it really looks like you were guessing what goes where at the end of your post.
i just have tips on what helped me. passing along the info and the link.
epikroms said:
Firstly I would check your use cable, I have a bunch and not all of them work. Secondly, make sure that your phone is being recognized on PC, hence the cable check. and third, make sure you are flashing the correct firmware. You said TMB, but I see you are flashing 3 different company files. Hi back to full G935P firmware , you front need to flash TMB on t, it should be fine cause I have a g935p with TMB sim in it
Anything else I'll be glad to help
Click to expand...
Click to collapse
What is your APN settings ? With the sprint firmware I could either get LTE data or calls and text not both at the same time.
Thanks.
bothambhai said:
What is your APN settings ? With the sprint firmware I could either get LTE data or calls and text not both at the same time.
Thanks.
Click to expand...
Click to collapse
Im actually on the G935U rom from jrkruse. If you are on the latest firmware just skip the flashing of the stock U firmware. Just flash eng boot, root it, and follow his process in his t-mobile thread for flashing in flashfire. When aroma starts it asks you what kernel to flash just choose tmobile and it works instantly. But fo APN settings whatbi had was this:
Name
T-Mobile US LTE
Apn
fast.t-mobile.com
Mmsc
http://mms.msg.eng.t-mobile.com/mms/wapenc
Apn Type
default,supl,mms or Internet+MMS
epikroms said:
Im actually on the G935U rom from jrkruse. If you are on the latest firmware just skip the flashing of the stock U firmware. Just flash eng boot, root it, and follow his process in his t-mobile thread for flashing in flashfire. When aroma starts it asks you what kernel to flash just choose tmobile and it works instantly. But fo APN settings whatbi had was this:
Name
T-Mobile US LTE
Apn
fast.t-mobile.com
Mmsc
http://mms.msg.eng.t-mobile.com/mms/wapenc
Apn Type
default,supl,mms or Internet+MMS
Click to expand...
Click to collapse
I managed to flash back the Sprint firmware. I feel the problem is Sprint is probably the only one with an upgraded baseband due to their last update. Both the TMO and U firmwares are based on the 4 baseband G930TUVS4BRA1 and the last Sprint update put it on a 5 baseband G935PVPS5BRA1. That is what is causing for it to fail, I feel. Do you think if I follow the eng.boot method I should be able to overcome the problem ?
bothambhai said:
I managed to flash back the Sprint firmware. I feel the problem is Sprint is probably the only one with an upgraded baseband due to their last update. Both the TMO and U firmwares are based on the 4 baseband G930TUVS4BRA1 and the last Sprint update put it on a 5 baseband G935PVPS5BRA1. That is what is causing for it to fail, I feel. Do you think if I follow the eng.boot method I should be able to overcome the problem ?
Click to expand...
Click to collapse
Okay the problem you are having is that you are actually on bootloader 5 not baseband 5. So that number represents the bootloader and there is no way of downgrading as of yet. Samsung does this thing with fuses on the phone being blown as the bootloader upgrades, well as far as i know from the s8&s8+. So your problem you are having is that you are trying to flash a previous bootloader which isn't going to happen. Flashing the QK5 or the BRA1 firmware will work. Cause it's on bootloader 5. I'd you do what I said a couple posts ago you'll be fine I'm still running the U series tom with tmo kernel installed and I have actually had 0 issues so far. It's been completely solid and everything works, data, sms, Wi-Fi calling, etc...... it works after flashing and boot. With the Sprint tom I got headache after headache and the activating thing is annoying. Just do what I said and you'll see a that what jrkruse then did is probably going to be the only best thing the Sprint variant gets. Try it
epikroms said:
Okay the problem you are having is that you are actually on bootloader 5 not baseband 5. So that number represents the bootloader and there is no way of downgrading as of yet. Samsung does this thing with fuses on the phone being blown as the bootloader upgrades, well as far as i know from the s8&s8+. So your problem you are having is that you are trying to flash a previous bootloader which isn't going to happen. Flashing the QK5 or the BRA1 firmware will work. Cause it's on bootloader 5. I'd you do what I said a couple posts ago you'll be fine I'm still running the U series tom with tmo kernel installed and I have actually had 0 issues so far. It's been completely solid and everything works, data, sms, Wi-Fi calling, etc...... it works after flashing and boot. With the Sprint tom I got headache after headache and the activating thing is annoying. Just do what I said and you'll see a that what jrkruse then did is probably going to be the only best thing the Sprint variant gets. Try it
Click to expand...
Click to collapse
Thanks for your reply. If it is not too much can you please break down the steps a bit more because I don't want to guess and mess it up again and also if you could please kindly point me to the other thread as well so I can download the appropriate stuff from there and read a bit more about it. I am right now unable to use the phone with the sprint firmware on it on TMo, it's super annoying.
Thanks in advance.
https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3572739
Don't mind all the instructions there .
1. Download the flashfire zip file and place it in your phone.
2. Download the Ufirm_multi_carrier.zip and unzip it and place the AP or TaR on your phone(the file that's inside the zip)
3. Make sure to use the eng boot and the root provided in this thread and root your phone.(root is a pain but it's worth doing for this room.)
(Note, if you have flashfire stuck on enumerating partitions you can try rebooting or Google flashfire latest app or flashfire 0.73 app and download and install it)
4. In flashfire allow root permissions and select zip and choose flashfire flashable.zip and select mount system read/write,
5. In flashfire select firmware and select the AP or TaR that you downloaded and it should have all partitions checked. Leave it and press the check mark.
6. Make sure that SuperSU is not injected. MNow click on wipe and select dalvik/cache format cache .
7. The order should be firmware then zip then wipe in flashfire.
8. Click the flash tab at bottom in flashfire.
9. In aroma, select the wipe SuperSU image, I think it's selection 2, and the rest of it is entirely up to you for what carrier you are on and so forth.
There is no need to download the Ufirmware stock for Odin because it won't stick because if the new software you have on your phone. Please make sure you know what you are doing to apply these things. These instructions worked for me and if you choose to do otherwise that's on you. I claim no responsibility for bricked devices or what you create . Flashing is a risk that we all take and it's entirely up to you.
Any more questions I'll be glad to answer. Trying to get the oreo working but having issues.
---------- Post added at 10:49 AM ---------- Previous post was at 09:58 AM ----------
May have been the wrong link sorry here is the correct one:
https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3637375
Did you get it sorted out? Hopefully you are on the rom and haven't bricked your device. I attached a picture so you could see that I am on what I say I am on.
epikroms said:
https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3572739
Don't mind all the instructions there .
1. Download the flashfire zip file and place it in your phone.
2. Download the Ufirm_multi_carrier.zip and unzip it and place the AP or TaR on your phone(the file that's inside the zip)
3. Make sure to use the eng boot and the root provided in this thread and root your phone.(root is a pain but it's worth doing for this room.)
(Note, if you have flashfire stuck on enumerating partitions you can try rebooting or Google flashfire latest app or flashfire 0.73 app and download and install it)
4. In flashfire allow root permissions and select zip and choose flashfire flashable.zip and select mount system read/write,
5. In flashfire select firmware and select the AP or TaR that you downloaded and it should have all partitions checked. Leave it and press the check mark.
6. Make sure that SuperSU is not injected. MNow click on wipe and select dalvik/cache format cache .
7. The order should be firmware then zip then wipe in flashfire.
8. Click the flash tab at bottom in flashfire.
9. In aroma, select the wipe SuperSU image, I think it's selection 2, and the rest of it is entirely up to you for what carrier you are on and so forth.
There is no need to download the Ufirmware stock for Odin because it won't stick because if the new software you have on your phone. Please make sure you know what you are doing to apply these things. These instructions worked for me and if you choose to do otherwise that's on you. I claim no responsibility for bricked devices or what you create . Flashing is a risk that we all take and it's entirely up to you.
Any more questions I'll be glad to answer. Trying to get the oreo working but having issues.
---------- Post added at 10:49 AM ---------- Previous post was at 09:58 AM ----------
May have been the wrong link sorry here is the correct one:
https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3637375
Click to expand...
Click to collapse
First up, thanks a lot for your help. After a lot of tries I managed to root the phone or so I thought and that's what the phone said after I ran the root.bat file on the computer and the phone rebooted. I downloaded the flashfire app but when I turned it on it says "root access could not be acquired, are you rooted ?".
After I ran the root.bat file and the phone rebooted the phone clearly said it was rooted. How do I go ahead now ?
bothambhai said:
First up, thanks a lot for your help. After a lot of tries I managed to root the phone or so I thought and that's what the phone said after I ran the root.bat file on the computer and the phone rebooted. I downloaded the flashfire app but when I turned it on it says "root access could not be acquired, are you rooted ?".
After I ran the root.bat file and the phone rebooted the phone clearly said it was rooted. How do I go ahead now ?
Click to expand...
Click to collapse
Get the root from the thread in the link I provided .
In the file there should be something OS something flash the bat file in there it kills all Sprint stuff. Then do the root.batch file and don't worry when it removes all the SuperSU, flashfire, and so on, it's normal okay do on to the painful part......
In the command screen or terminal, it'll say to press a button when your phone has registered on the PC., this is probably where you are messing up. Watch your computer screen until the s7 pips up and watch your phone when it says Allow, MAKE SURE YOU TAP ALLOW! wait for your phone to click off on the PC and then click back on( it takes a while) then press whatever button you like and watch the terminal, if it has errors then it's not rooted if it is rooted then the terminal will close and your phone will reboot. Then proceed to flashfire and do it's thing. For good measure when your phone is booted open SuperSU app first and you'll know if your rooted. Let me know if you need more help
thats pretty interesting being on the binary 5 baseband and binary 4 rom. to clarify, you were on the binary 5 rom and reverted? or were you on the baseband 4 and upgraded just the baseband? thanks for the info.
epikroms said:
Get the root from the thread in the link I provided .
In the file there should be something OS something flash the bat file in there it kills all Sprint stuff. Then do the root.batch file and don't worry when it removes all the SuperSU, flashfire, and so on, it's normal okay do on to the painful part......
In the command screen or terminal, it'll say to press a button when your phone has registered on the PC., this is probably where you are messing up. Watch your computer screen until the s7 pips up and watch your phone when it says Allow, MAKE SURE YOU TAP ALLOW! wait for your phone to click off on the PC and then click back on( it takes a while) then press whatever button you like and watch the terminal, if it has errors then it's not rooted if it is rooted then the terminal will close and your phone will reboot. Then proceed to flashfire and do it's thing. For good measure when your phone is booted open SuperSU app first and you'll know if your rooted. Let me know if you need more help
Click to expand...
Click to collapse
I odined the AP_Nougat_S7_Edge_EngBoot.tar.md5 then ran the root.bat file from Nougat_S7_Root_2_82_All_Carriers_V2 , I chose the options to install the fingerprint fix and install the root without any gpu tweaks. I watched the whole process complete and the cmd prompt close, my phone never asked my permission to ALLOW anything, everything was on the computer. I ran the root.bat from cmd as an administrator and the program ran evidently because it asked me about the fingerprint fix and root with or without tweaks etc. I noticed the phone reboot and there was a notification, the phone was rooted but no SU and flashwire says no root access. I tried it back from square one a couple of tries more right back from flashing stock sprint firmware and trying the whole rooting process again, same results except the next two times the phone doesn't reboot after running the root.bat file. I notice now when the phone boots up there is a sign saying "CUSTOM" beneath the samsung logo on the screen. I don't know where I am going wrong in the process though. I don't know if it is because I am on the binary 5 however I also read somewhere that people have been successful in rooting their binary 5 sprint S7 edges. I have rooted many devices before and installed roms etc, this has been, by far, the most perplexing phone in every which way.
Fownt know what to say,but, you are saying that you are on binary 5 and have successfully downgraded bootloader's by flashing stock vzw firmware which is on binary 4? I don't think downgrading is possible yet?? The way I explained it to you is exactly how I did mine numerous times. I can no longer assist you though because, I kinda bricked my s7edge,
Here's something for everyone to note on a DONT DO!!!!
Do not flash the latest ENG_BOOT AND COMBO FIRMWARE.
I think it was the binary 5 QK1 eng boot and combo I forget, but after flashing back to stock firmware you will get a SBL ERROR in upload mode and let me tell you....... It is not fun at all. I had all the files necessary for unbricking, the complete restore files, I tried the z3x box, I tried octoplus, and I tried the uni-android tools and nothing flashes it over. It's insane. But I ended up sort of destroying the body of the phone but not the internal, so I now have a skeleton phone and no screen or mid frame.
So I wish you luck and probably a final goodbye to Samsung and their insaniy with phones.
epikroms said:
Fownt know what to say,but, you are saying that you are on binary 5 and have successfully downgraded bootloader's by flashing stock vzw firmware which is on binary 4? I don't think downgrading is possible yet?? The way I explained it to you is exactly how I did mine numerous times. I can no longer assist you though because, I kinda bricked my s7edge,
Here's something for everyone to note on a DONT DO!!!!
Do not flash the latest ENG_BOOT AND COMBO FIRMWARE.
I think it was the binary 5 QK1 eng boot and combo I forget, but after flashing back to stock firmware you will get a SBL ERROR in upload mode and let me tell you....... It is not fun at all. I had all the files necessary for unbricking, the complete restore files, I tried the z3x box, I tried octoplus, and I tried the uni-android tools and nothing flashes it over. It's insane. But I ended up sort of destroying the body of the phone but not the internal, so I now have a skeleton phone and no screen or mid frame.
So I wish you luck and probably a final goodbye to Samsung and their insaniy with phones.
Click to expand...
Click to collapse
Bummer about your phone. On a glad note I managed to root and flash my phone and everything works great now. I was taking the hard nerdy way to do it by running cmd as an administrator and having that run the root.bat file. I read somewhere else you could just double click the file and it worked for me . From there on the aroma part was pretty straightforward. I am grateful to you for pointing me in this direction and breaking it down for me, I seriously doubted me being able to achieve this on my binary 5 phone but it turned out to be smooth.
I do wish you the best and thanks once again.