Related
Hey,
I recently installed Omega Rom v19 (Android 4.3) on my Samsung Galaxy S4 i9505 Intl.
All of a sudden it loses cellular connection instantly whenever I lock the phone with the power key. It will take a couple of minutes before it will come back and this is REALLY annoying.
Any help on this would be great, could it be a modem issue? My baseband is I9505DVUAMD8
I installed a 4.4.2 Google Edition Rom prior to this one and it did the same thing, I have no idea how to fix it!?
Thanks!
thefury91 said:
Hey,
I recently installed Omega Rom v19 (Android 4.3) on my Samsung Galaxy S4 i9505 Intl.
All of a sudden it loses cellular connection instantly whenever I lock the phone with the power key. It will take a couple of minutes before it will come back and this is REALLY annoying.
Any help on this would be great, could it be a modem issue? My baseband is I9505DVUAMD8
I installed a 4.4.2 Google Edition Rom prior to this one and it did the same thing, I have no idea how to fix it!?
Thanks!
Click to expand...
Click to collapse
Flashed a new modem which did not work, could it be a kernel issue perhaps? What is a recommended kernel for use with Omega v19?
Cheers
thefury91 said:
Flashed a new modem which did not work, could it be a kernel issue perhaps? What is a recommended kernel for use with Omega v19?
Cheers
Click to expand...
Click to collapse
I doubt you flash it right follow this instruction. and check your baseband version if it changes that should fix your dropping issue. Remember to turn off your phone Manually before flashing anything via odin.
Use Odin
Untick Autoreboot
Flash modem
Reboot once again into Download Mode using (Vol Down plus Home button combi)
Flash Modem once more
Once done,unplug then reboot device manually.
If this doesn't work, try repeating the flash process again while rebooting manually and with auto-reboot option turned off.
Repulsa said:
I doubt you flash it right follow this instruction. and check your baseband version if it changes that should fix your dropping issue. Remember to turn off your phone Manually before flashing anything via odin.
Use Odin
Untick Autoreboot
Flash modem
Reboot once again into Download Mode using (Vol Down plus Home button combi)
Flash Modem once more
Once done,unplug then reboot device manually.
If this doesn't work, try repeating the flash process again while rebooting manually and with auto-reboot option turned off.
Click to expand...
Click to collapse
Thanks for the reply,
After flashing the modem I checked and the baseband had changed to the new modem, I am trying a different modem soon, once it has downloaded. I will see how I go with this new one.
Cheers
Hey Guys,
Today I updated my i9505 from Cynogen Mod 10.3.1 to the new "[AOSP] Official 4.4.2 - S4 Google Edition - Final-R1.1" by Jamal, but I read that you needed to update to the leaked 4.4.2 before flashing so that the modem and bits are upto date before flashing any 4.4.2 ROMs or else you could end up with no wifi after flashing.
So I followed these instructions to flash the leaked 4.4.2:
INSTRUCTIONS
- Extract (unzip) the firmware file
- Download Odin3 v3.09 (From here or here)
- Extract Odin .ZIP file
- Open Odin3 v3.09
- Restart phone in download mode (Press and hold Home + Power + Volume down buttons)
- Connect phone and wait until you get a blue sign in Odin
- Add AP_I9505XXUFNA5_373648_REV06_user_low_ship_MULTI_CERT.tar.md5 to AP
- Add BL_I9505XXUFNA5_373648_REV06_user_low_ship_MULTI_CERT.tar.md5 to BL
- Add CP_I9505XXUFNA5_373648_REV06_user_low_ship_MULTI_CERT.tar.md5 to CP
- Add CSC_OXA_I9505OXAFNA5_373648_REV06_user_low_ship_MULTI_CERT.tar.md5 to CSC
- Make sure re-partition is NOT ticked
- Click start button, sit back and wait a few minutes.
Which all went well but I couldn't get Wifi after flashing, and (probably not important) but the default language it choose during the setup was Dutch??? Seeing as I couldnt get the wifi to enable I decided to flash Philz Touch Recovery v6 and then put Jamal's "S4 Google Edition - Final-R1.1" by putting it onto the SD card and flashing through Philz recovery.
Flashing went without a problem.... only thing is now I cant get Vodafone (UK) signal 80% of the time, the other 20% I do get signal and can make calls, just seems strange as previously 80% I WOULD get signal!
Did I do something wrong? I had a really bad feeling that flashing the CP, BL and CSC has somehow messed things up......please help!
Same problem, bump.
ColdIce23 said:
Same problem, bump.
Click to expand...
Click to collapse
I just fixed the problem, ColdIce23, check your Baseband Version under Settings > About Device, I bet yours is still set to the original baseband version like mine was...
1) Re-Download the Baseband for the leaked 4.4.2 rom (Here)
2) Open Odin 3.09 and do the following:
Ok it worked.
If anyone else is having issues with the baseband not changing, do this.
Use Odin v3.04
Untick Autoreboot
Flash modem
Reboot once again into Download Mode using (Vol Down plus Home button combi)
Flash Modem once more
Once done,unplug then reboot device manually.
If this doesn't work, try repeating the flash process again while rebooting manually and with auto-reboot option turned off.
Click to expand...
Click to collapse
Now I have FULL SIGNAL! .....so far..... will report back once I have left work but this is a good sign as I had no signal what-so-ever 5 minutes ago!
Flasing a 4.4.2 Modem works well with the Kit Kat based roms. Two to choose from NA1 or NA5, depending on what bootloader your on flash the appropriate modem files.
I've got NA5 on the 4.4.2 GE Rom with Three and no signal issues as of yet.
treesmoker said:
I just fixed the problem, ColdIce23, check your Baseband Version under Settings > About Device, I bet yours is still set to the original baseband version like mine was...
1) Re-Download the Baseband for the leaked 4.4.2 rom (Here)
2) Open Odin 3.09 and do the following:
Now I have FULL SIGNAL! .....so far..... will report back once I have left work but this is a good sign as I had no signal what-so-ever 5 minutes ago!
Click to expand...
Click to collapse
My I9505 baseband version is I9505XXUFNA5. Is not it the updated one?
kamrul.auntu said:
My I9505 baseband version is I9505XXUFNA5. Is not it the updated one?
Click to expand...
Click to collapse
Yes you the latest baseband available.
treesmoker said:
Hey Guys,
Today I updated my i9505 from Cynogen Mod 10.3.1 to the new "[AOSP] Official 4.4.2 - S4 Google Edition - Final-R1.1" by Jamal, but I read that you needed to update to the leaked 4.4.2 before flashing so that the modem and bits are upto date before flashing any 4.4.2 ROMs or else you could end up with no wifi after flashing.
/QUOTE]
I think u missunderstood something. For the Kitkat Google Edition u do not have to flash the leak before. Its only for the Samsung Touchwiz Version of Kitkat
tapatalked by an Echoenian
Click to expand...
Click to collapse
nikzDHD said:
Flasing a 4.4.2 Modem works well with the Kit Kat based roms. Two to choose from NA1 or NA5, depending on what bootloader your on flash the appropriate modem files.
I've got NA5 on the 4.4.2 GE Rom with Three and no signal issues as of yet.
Click to expand...
Click to collapse
I flashed the NA5 modem which seems to have failed the first time round, as it didnt actually change the baseband version in settings. Since flashing a second time (when it actual flashed properly) I now have full signal...... but I have another problem now:
When I click the dailer and select a person to call, the screen goes black and I dont see/hear any indication that a call has initiated. I tried with my wife and her phone rings and she can answer the call, but my screen is still black with no sound....
I have tried wiping data / davlik / cache and installing the rom from scratch, but I still get the same issue?
UPDATE:
Right so I just flashed CM11 as a test, and still can't make calls, so obviously not a ROM fault..... does the BL, CP or CSC have anything to do with the making calls procress?
I've got a similar issue.
I've got a M919V running Jamal's 4.3 GPE rom, but after flashing Jamal's 4.4.2 GPE i get no signal. After going into settings and selecting network the signal lasts, but after the screen goes off signal is once again lost.
Is there a procedure to follow that will fix this? This is found when when flashing many 4.4 roms.
-Thanks
Well, I get signal when I'm near a cell tower...
No changes tho. Still same problem.
Hi guys,
I'm wondering if you have resolved your modem problems?
I flashed to Jamal's 4.4.2 version 1.2 and I don't have a signal now.
I flashed the modem to NA5 but styill no signal. Also I can't even check my CSC using *#1234# as "Mobile network not available"
Any suggestions?
Thanks.
Hi Duskin,
For me, I think it's releated to the phone itself as I got a screen replacement. I haven't solved the problem yet because I got to get back to the store where I got my screen replaced.
Sent from my LG-P880 using Tapatalk
Hey guys quick question before I download and attempt it, I have an Australian i9506 (Cat 4 LTE) but we don't have an official 5.0.1 firmware yet.
Can I just download the Nordic version from http://www.sammobile.com/firmwares/database/GT-I9506/ and install it, or would it brick my phone/radios not work?
Thanks
juzza87 said:
Hey guys quick question before I download and attempt it, I have an Australian i9506 (Cat 4 LTE) but we don't have an official 5.0.1 firmware yet.
Can I just download the Nordic version from http://www.sammobile.com/firmwares/database/GT-I9506/ and install it, or would it brick my phone/radios not work?
Thanks
Click to expand...
Click to collapse
Hi mate,
Yes you can !! it will not brick it , you may have (or not) problems with the modem as maybe is not the best for your region but you can always flash another...
should not be a problem
BACKUP first , nandroid and your EFS Folder, just in case there is a problem
Just to add to the previous suggestion, use Wanam's EFS Backup Tool rather than Samsung Tool, as it not only backs up the EFS partition but the hidden partitions where the IMEI and the modem are stored.
Strephon Alkhalikoi said:
Just to add to the previous suggestion, use Wanam's EFS Backup Tool rather than Samsung Tool, as it not only backs up the EFS partition but the hidden partitions where the IMEI and the modem are stored.
Click to expand...
Click to collapse
+1 mate!!
It also depends if your phone is carrier locked.
Thanks for the advice guys I'm giving it a try now, will edit as I go. My phone is not carrier locked (Voda AU don't lock them fortunately but they provide the codes on their website for free to unlock anyway).
So I downloaded Odin3 3.09 and the firmware I9506XXUDOA6_I9506NEEDOA6_NEE (this is the link from sammobile).
I'm following the instructions I found on another site but it's basically put the phone into download mode (home, power and volume down), agree to enter download mode, in Odin for AP select the .tar.md5, make sure Auto Reboot and F. Time Reset are ticked but not Re-Partition or anything else and start.
EDIT 1: The phone rebooted into recovery and updated something, now the phone is booting with a new boot animation. (for those referring to this I was on the latest AU Voda FW, then updated to CM12 5.0.2).
EDIT 2: After the usual nerve-wracking amount of time of first boot the boot logo finally went away and the usual "optimizing apps" message has come up and it's started (235 apps whoa the bloat). Waiting for that but at least it's working to a point where I can recover it. I just realised it's 6:10AM now and I FORGOT TO MAKE A BACK UP. I hope this works but worse case scenario there's a 4.4.2 Vodafone firmware I could flash and try my luck with if this doesn't work out.
EDIT 3: I'm not sure if it's part of the setup process but the word "UP" then a short progress bar appeared on the screen, now I've got only a black screen with a status bar (4G icon is there but no clock). I have rebooted from the power menu, let's see what's going on here.
EDIT 4: Cache wipe from stock recovery didn't work, trying factory reset from stock recovery. I note that the first time I set up the phone it was plugged into the computer with ODIN still running, I don't think it could have interfered but I unplugged the phone this time just in case.
EDIT 5: I'm not sure if it was ODIN or needing to do a factory reset but it's working now, I'm running through the set up. WiFi is working 100%.
Final EDIT: Everything is working 100%, tested the camera, proximity sensor, screen rotation, voice calls, mobile data, wifi and it's all 100%.
juzza87 said:
Thanks for the advice guys I'm giving it a try now, will edit as I go. My phone is not carrier locked (Voda AU don't lock them fortunately but they provide the codes on their website for free to unlock anyway).
So I downloaded Odin3 3.09 and the firmware I9506XXUDOA6_I9506NEEDOA6_NEE (this is the link from sammobile).
I'm following the instructions I found on another site but it's basically put the phone into download mode (home, power and volume down), agree to enter download mode, in Odin for AP select the .tar.md5, make sure Auto Reboot and F. Time Reset are ticked but not Re-Partition or anything else and start.
EDIT 1: The phone rebooted into recovery and updated something, now the phone is booting with a new boot animation. (for those referring to this I was on the latest AU Voda FW, then updated to CM12 5.0.2).
EDIT 2: After the usual nerve-wracking amount of time of first boot the boot logo finally went away and the usual "optimizing apps" message has come up and it's started (235 apps whoa the bloat). Waiting for that but at least it's working to a point where I can recover it. I just realised it's 6:10AM now and I FORGOT TO MAKE A BACK UP. I hope this works but worse case scenario there's a 4.4.2 Vodafone firmware I could flash and try my luck with if this doesn't work out.
EDIT 3: I'm not sure if it's part of the setup process but the word "UP" then a short progress bar appeared on the screen, now I've got only a black screen with a status bar (4G icon is there but no clock). I have rebooted from the power menu, let's see what's going on here.
EDIT 4: Cache wipe from stock recovery didn't work, trying factory reset from stock recovery. I note that the first time I set up the phone it was plugged into the computer with ODIN still running, I don't think it could have interfered but I unplugged the phone this time just in case.
Click to expand...
Click to collapse
Hi mate
How is it going?
If trouble , do a factory reset and flash it again....
Thanks mate that did the trick!
juzza87 said:
Thanks mate that did the trick!
Click to expand...
Click to collapse
glad to hear it mate, you did it!!
Thanks for let in us know.
For any other Aussies out there trying this I'm on day two and everything is working perfectly, getting root is super easy too, just use Odin to flash a custom recovery (Solk's CWM from May 2014 works great), boot into the recovery and install UPDATE-SuperSU-v2.45.zip, exit and when it asks if you want to repair root say yes. Reboot, go to the play store, update to the latest SuperSU and all is well.
Hi everyone. I just flashed back to stock (Koodo official firmware) to sell my Note 3 and now my back hardware button isn't working. I have searched the web and to no avail. Could someone please give me an idea of what I can do to fix this? Thank you!!
Which note 3 is it?
SM n900W8
I have the same model. I haven't used it for a while. I powered it on a few days ago to take the update from doc4 to doh1. I just tried the back and menu buttons using the doh1 ROM and they seem to work fine.
A friend of mine has the same phone and he flashed the doh1 ROM from sammobile.com over a rooted doc4 RIM and he also has no problems.
Both of us were using custom ROMs with a 4.4.2 bootloader and we both flashed back to stock using sammobile.com's doc4 ROM before moving to doh1.
I ended up flashing a stock n9005 zip TW rom and it is fixed - but I had to install TWRP again etc. Thanks for the help though!
Glad you got it fixed but I'm not sure I was much help.
Partially solved..
Hi.
I have done everything trying to solve this and can confirm the next:
1st: If you go back to Kit Kat, the capacitive buttons start to work again. Then you are offered a couple of OTAs (one after the other to get you to DOH1). After the first OTA, the buttons stop working again.
So first solution: stay on Kit Kat (probably not what we want).
2nd: Flashing a custom Cyanogenmod based firmware works, I used latest temasek's build, I am testing it to see if I can keep it.
3rd: I tried erasing almost every single partition (system/cache/dalvik(art?) cache) and flashing from scratch DOH1... wont work.
According to what I have read all around there is a system file that controls the capacitive buttons, probably that file is getting weird with the upgrade, I still need to install a official rom, root it and try to edit such file.
It's strange that some phones have no problem while others do. My friend and I have no problems but we weren't running custom ROMs before the doc4 or doh1 updates.
audit13 said:
It's strange that some phones have no problem while others do. My friend and I have no problems but we weren't running custom ROMs before the doc4 or doh1 updates.
Click to expand...
Click to collapse
I wasn't running anything custom. I was on Official ROM (no root no anything, just Stock Samsung Software) as always with my Note 3. It was just that the DOH1 update make the damages.
Now I think I gotta stick to Cyanogenmod given this problem, unless Samsung says something and fix the thing.
Does this happen with TW-based custom ROMs too?
Dont know. As of now, I am trying to flash DOH1 again on top of KitKat 4.4.2
[/COLOR]http://www.askmefast.com/I_have_a_n...art_any_idea_what_can_be_done-qna1982335.html
They say clearing the Cache of the Samsung Keyboard fixes the thing. Wont be able to test by myself til tomorrow
Edited
I have N900W8 bell version, using it on Virgin network.
worked flawlessly with KitKat (either with Bell or Virgin version).
I've only experimented with Note-based custom roms (KitKat only), since I need the pen functionality.
First attempt:
I have experienced the same, not properly working menu button and not working back button.
I was on rooted stock KitKat 4.4.2 (N900W8VLUCNB7 Firmware Virgin mobile version), rooted with Chainfire CF-auto root (Build ID:KOT49H.N900W8VLUCNB7) using Odin. (all the buttons working properly)
Upgraded to Lollipop 5.0 (N900W8VLU2DOH1) with Odin, rooted same way with CF-auto root (Build ID:LRX21V.N900W8UBU2DOL1). (Buttons do not work)
Second Attempt (No rooting involved what-so-ever):
Reverted back to stock KitKat 4.4.2 (N900W8VLUCNB7 Firmware Virgin mobile version, clean flash), all the buttons working properly.
Did OTA update through Wifi to, assuming, N900W8VLU2DOC4. (Buttons do not work)
Another OTA update through Wifi to N900W8VLU2DOH1(confirmed). (Buttons do not work)
For both of above attempts, buttons are working properly with KitKat, whether it was rooted or not, and not with Lollipop, whether it was rooted or not. I'm thinking it's just the lollipop issue.
Third attempt (using N900W8VLUCNB7 Firmware Bell version):
Reverted back to stock KitKat 4.4.2 (N900W8VLUCNB7 Firmware Bell version, clean flash), all the buttons working properly.
Did OTA update through Wifi to N900W8VLU2DOC4. (Buttons do not work)
Another OTA update through Wifi to N900W8VLU2DOH1(confirmed). (Buttons do not work)
wy2sl0 said:
I ended up flashing a stock n9005 zip TW rom and it is fixed - but I had to install TWRP again etc. Thanks for the help though!
Click to expand...
Click to collapse
Do you have the link for the stock Tom zip?
Sent from my SM-N900W8 using XDA Free mobile app
Ok. Pretty much tried everything while staying on stock firmware.
However, everything else seems to work okay other than the touch button.
So now im gonna root the stock lollipop and use xposed and gravitybox to manually remap the 2 touch keys. Will update
Hell yeah(excuse my language, but I'm so happy), I got this working!
Before I start listing my steps, please thank wrench588 here for me to find a confirmed working solution, and
thank stew721 here for the original post!!
No root on a stock lollipop (N900W8VLU2DOH1) Virgin firmware on Bell phone
1. Clean flash with N900W8VLU2DOH1 Virgin firmware on odin. (I'm guessing you actually wouldn't even need to do this step, if you are already on lollipop (N900W8VLU2DOH1 or N900W8OYADOC4 firmware)4N900W8
- I got my stock firmware from here
2. Download idlekernel here
- For Odin flash: download idleKernel-hlte-can-6.6.5.tar.md5 (for Canadian galaxy note 3 SM-N900W8)
- For recovery flash (ie. twrp): download idleKernel-hlte-can-6.6.5.zip (for Canadian galaxy note 3 SM-N900W8)
3A. For Odin,
a. open Odin
b. load into download mode (by holding Power+Volume Down+Home key together when turning on the device)
c. Load the idleKernel-hlte-can-6.6.5.tar.md5 into the "AP" on Odin
d. "Start" on Odin
3B. For Recovery(TWRP or CWM),
a. Boot normally and copy idleKernel-hlte-can-6.6.5.zip into your phone
b. flash idleKernel-hlte-can-6.6.5.zip file in recovery
Done.
Thank you so much again, wrench588 and stew721. I could not be happier
Next step for me would be getting my stock rom to get deodexed so I can install "xposed". I need to replace the function of holding "menu" touch button to pop up google search instead of S finder.
rocked_out said:
Hell yeah(excuse my language, but I'm so happy), I got this working!
Before I start listing my steps, please thank wrench588 here for me to find a confirmed working solution, and
thank stew721 here for the original post!!
No root on a stock lollipop (N900W8VLU2DOH1) Virgin firmware on Bell phone
1. Clean flash with N900W8VLU2DOH1 Virgin firmware on odin. (I'm guessing you actually wouldn't even need to do this step, if you are already on lollipop (N900W8VLU2DOH1 or N900W8OYADOC4 firmware)4N900W8
- I got my stock firmware from here
2. Download idlekernel here
- For Odin flash: download idleKernel-hlte-can-6.6.5.tar.md5 (for Canadian galaxy note 3 SM-N900W8)
- For recovery flash (ie. twrp): download idleKernel-hlte-can-6.6.5.zip (for Canadian galaxy note 3 SM-N900W8)
3A. For Odin,
a. open Odin
b. load into download mode (by holding Power+Volume Down+Home key together when turning on the device)
c. Load the idleKernel-hlte-can-6.6.5.tar.md5 into the "AP" on Odin
d. "Start" on Odin
3B. For Recovery(TWRP or CWM),
a. Boot normally and copy idleKernel-hlte-can-6.6.5.zip into your phone
b. flash idleKernel-hlte-can-6.6.5.zip file in recovery
Done.
Thank you so much again, wrench588 and stew721. I could not be happier
Next step for me would be getting my stock rom to get deodexed so I can install "xposed". I need to replace the function of holding "menu" touch button to pop up google search instead of S finder.
Click to expand...
Click to collapse
THanks for this!!! note that some will get a "unfortunately knox has stopped working" upon bootup and nothing can be done about it to my knowledge.
SS604 said:
THanks for this!!! note that some will get a "unfortunately knox has stopped working" upon bootup and nothing can be done about it to my knowledge.
Click to expand...
Click to collapse
Hey , has anyone firgured out how to get rid of the "unfortunately Knox has stopped working" ? I had the same issue with the softkeys not working. This fix works but I get this message. I was also told to try flashing a PIT file with stock firmware to fix the softkey issue, but this did not work.
Maybe flashing supersu from TWRP will allow supersu to disable knox?
not to bring back a dead thread, but this is exactly what I needed. I needed to root to fix screen mirroring so I just used root uninstaller to delete knox.
Hello, my SM-G935A is rooted, and I have 2 issues with it. Firstly, I'm unable to receive texts or phone calls (I can send them), and I've tried a factory reset and I even got a new SIM, but nothing worked. I think if I flash stock firmware, it might fix the issue. Second problem, when I go into download mode and select my AP in Odin and press start, my phone gets an error and Odin freezes at Initialization.
Any help would be appreciated. I would prefer to fix the texting issue, as I don't want to return the phone to ATT. In either case, the Odin issue needs to be fixed
I'm having a similar issue. This afternoon, 2 apps threw errors and closed. I rebooted, which apparently was the wrong thing to do. The reboot stalled on the AT&T logo and stayed that way for 5 min - the unit became very hot & the power button did not respond, even while holding it down. I got into recovery, cleared the cache and factory reset, then rebooted. The unit came back up and started reinstalling everything. I took it back down into the download status and attempted to reload 935x via Odin, only to stall at "initialzation" [sic] as you did. I got out of that after waiting for some sort of response. SuperSU was still in my apps as was Root Checker. Root Checker indicates the system is rooted. SuperSU indicates it needs the binary updated. BusyBox and TiBu indicate they cannot find root. I deleted all the root apps and tried reinstalling root via adb which completed successfully, but the same outcome with all the root apps. So I'm not sure if I'm still really rooted as Root Checker claims, or not.
EDIT: I just saw that I have 2 "Knox Settings" apps. Clicking on either returns, "Unfortunately, Container Agent2 has stopped."
use the odin from the stock firmware thread to flash it again. if it fails you can flash the u firmware and then the stock again. then you have to use a different odin if you want to flash the root api file the one you flash the firmware with wont work. also there is help in one of the threads about fixing the volte problem so you dont have to turn it off to get calls. i didnt have to do it as using the odin i mentioned fixed it for me when i came from the u firmware.
NovaEDM™ said:
Hello, my SM-G935A is rooted, and I have 2 issues with it. Firstly, I'm unable to receive texts or phone calls (I can send them), and I've tried a factory reset and I even got a new SIM, but nothing worked. I think if I flash stock firmware, it might fix the issue. Second problem, when I go into download mode and select my AP in Odin and press start, my phone gets an error and Odin freezes at Initialization.
Any help would be appreciated. I would prefer to fix the texting issue, as I don't want to return the phone to ATT. In either case, the Odin issue needs to be fixed
Click to expand...
Click to collapse
I was having the exact same problem you had with Odin. It seemed I was able to flash stock firmware using this version of Odin: http://www.mediafire.com/download/2t2sjqxtogbkafk/odin_3.12.3.rar
rob219 said:
use the odin from the stock firmware thread to flash it again. if it fails you can flash the u firmware and then the stock again. then you have to use a different odin if you want to flash the root api file the one you flash the firmware with wont work. also there is help in one of the threads about fixing the volte problem so you dont have to turn it off to get calls. i didnt have to do it as using the odin i mentioned fixed it for me when i came from the u firmware.
Click to expand...
Click to collapse
did you have any problems with the u version of the s7 edge firmware, like the fingerprint scanner not responding? i am on that version and cant get any odin version or any version of s7 edge g935a firmware to flash, tried unrooting and was forced to use the U version of the s7 edge firmware, everything works except the fingerprint scanner, cant get back to full stock firmware, need help!
im having the exact same problem, when i put my phone into download mode and flash the stock at&t firmware, Odin get stuck in "initialization" and my phone screen displays and error message.
Same stuff was happening to me, I went back to stock and took the update. When your phone stops working as an actual phone, it's time to roll it back.
I played with it for a week and my phone was so freaking hot (with hot weather) equals a wait and see if this gets more stable in the near future. I did use the Odin 3.12.3 mentioned by King James III. Honestly, I did so many things to get it back to stock I forget what actually worked (it was the wee hours of the morning and I was spent). Don't give up guys, it will and can work.
edit: It may be as simple as not right clicking Odin and running it as Administrator.
nicetucu said:
Same stuff was happening to me, I went back to stock and took the update. When your phone stops working as an actual phone, it's time to roll it back.
I played with it for a week and my phone was so freaking hot (with hot weather) equals a wait and see if this gets more stable in the near future. I did use the Odin 3.12.3 mentioned by King James III. Honestly, I did so many things to get it back to stock I forget what actually worked (it was the wee hours of the morning and I was spent). Don't give up guys, it will and can work.
edit: It may be as simple as not right clicking Odin and running it as Administrator.
Click to expand...
Click to collapse
I used Odin_v3.12.3_Patched_SHA256 to flash the 935U Firmware then used Odin3_v3.11.2 to flash the June Firmware release.