If you tried to update to Mango beta and after the update got stuck at Samsung logo, you're one of the lucky few like me Here's a fix.
I've re-flashed it with Samsung i917 Focus firmware UCJK2 AT&T USA from here.
For flashing, comprehensive guide here, short version here and below is the minimalistic version.
Keep pressed camera, volume up and power, phone starts then release power button and you enter download mode.
Run Samsung i917 Focus firmware UCJK2 AT&T USA.exe and it will unpack the rom binaries and flasher.
Run WP7_Downloader_Ver_7.05_for_Retail_Device_(Product_Force_Select_MD5_X).exe and select the 4 binaries and click Start
Takes about 5 minutes, it will boot correctly after that.
Fire Zune, stop sync and go to Phone, Settings, Update.
Your restore is there (down), make use of it.
LE: If you're super "lucky", you might get the error 801812E0 when trying to restore. In that case, that's it. You'll have to start from scratch.
Anyway, here's a solution, so...
Panic mode off
just happened to me now restoring my phone. did you manage to get Mango?
fraincs said:
just happened to me now restoring my phone. did you manage to get Mango?
Click to expand...
Click to collapse
Yep, on both Rogers and AT&T.
I think I found out what the problem is. I stuffed my phone quite good, had 6 GB free (out of 22). Not gonna do that just to check, though
Related
Hi Gurus,
While everybody is trying 2.2, I am still stuck on FJ6 (or incomplete JH7).
Here's the history:
1. Got the phone on day 1 of release.. loved it and still love it. No GPS issues - first lock took 20 secs and subsequent locks took 6 seconds at most.
2. Rooted and unlocked the phone, deleted all AT&T crapware. Running Launcher Pro, Tiatinum backup etc.
3. Installed Lagfix - was happy with a high quadrant score
4. Saw that the JH7 OTA is out
5. Read up on the forums here and unlagged lagfix.
6. Initiated the OTA update, went all the way thru, and got the message "update failed - No updated available" after restart. GPS is messed up.
7. Settings --> About Phone shows this
- Firmware version: 2.1-update1
- Baseband Version: I897UCJH7
- Kernel Version: 2.6.29 [email protected] #2
- Build Number: ECLAIR
8. Went to plan B - Kies Mini, was able to connect but stuck at "Unregistered screen".
9. Got frustrated and called Samsung.
- They said that the OTA upgrade worked "half way thru". They were expecting something after the "ECLAIR" in build number and I should not see the "PC Internet" as an option under USB Settings.
So Samsung said that they will have to reflash the phone to JH7 and have asked me to send the phone in.
1. I will be without a phone for 4-5 days which sucks.
2. They may (an will?) see my shenanigans (root etc) on the phone even after a hard reset ??
What are the implications? Is there any way around this? Can I do something (or follow some instruction by myself) to fix this? I am ok going back to stock AT&T firmware - to need to mess around with removing crapware etc. I would just like to keep the phone "unlocked" (I travel overseas quite a bit).
I have read thru most of the form postings.. which confused me more. At this point of time, I have a "brain freeze" and would appreciated a "just do this and then this" type of instruction.
Ironically, ever since switching from Windows Mobile to android, I have been a big proponent of this phone and operating system. Now I am beginning to see the downside of being on the leading/bleeding edge..
Please help..
Nick
You can always use ODIN and flash it that way...
http://forum.xda-developers.com/showpost.php?p=8567598&postcount=6
defriend said:
Hi Gurus,
While everybody is trying 2.2, I am still stuck on FJ6 (or incomplete JH7).
Here's the history:
1. Got the phone on day 1 of release.. loved it and still love it. No GPS issues - first lock took 20 secs and subsequent locks took 6 seconds at most.
2. Rooted and unlocked the phone, deleted all AT&T crapware. Running Launcher Pro, Tiatinum backup etc.
3. Installed Lagfix - was happy with a high quadrant score
4. Saw that the JH7 OTA is out
5. Read up on the forums here and unlagged lagfix.
6. Initiated the OTA update, went all the way thru, and got the message "update failed - No updated available" after restart. GPS is messed up.
7. Settings --> About Phone shows this
- Firmware version: 2.1-update1
- Baseband Version: I897UCJH7
- Kernel Version: 2.6.29 [email protected] #2
- Build Number: ECLAIR
8. Went to plan B - Kies Mini, was able to connect but stuck at "Unregistered screen".
9. Got frustrated and called Samsung.
- They said that the OTA upgrade worked "half way thru". They were expecting something after the "ECLAIR" in build number and I should not see the "PC Internet" as an option under USB Settings.
So Samsung said that they will have to reflash the phone to JH7 and have asked me to send the phone in.
1. I will be without a phone for 4-5 days which sucks.
2. They may (an will?) see my shenanigans (root etc) on the phone even after a hard reset ??
What are the implications? Is there any way around this? Can I do something (or follow some instruction by myself) to fix this? I am ok going back to stock AT&T firmware - to need to mess around with removing crapware etc. I would just like to keep the phone "unlocked" (I travel overseas quite a bit).
I have read thru most of the form postings.. which confused me more. At this point of time, I have a "brain freeze" and would appreciated a "just do this and then this" type of instruction.
Ironically, ever since switching from Windows Mobile to android, I have been a big proponent of this phone and operating system. Now I am beginning to see the downside of being on the leading/bleeding edge..
Please help..
Nick
Click to expand...
Click to collapse
You hacked your phone, now it won't update and you think it is because android is on the bleeding edge.
If you had reverted to stock first (odin one click) you may have had success. Maybe it would kill your unlock -some it does, some it doesn't.
Some phones had trouble updating even from stock - but unless you put it back - you will have no baseline. You need to make it stock before you send it anyway - or they may just return it because you did root and modify it.
Use Odin to do a master clear, flash back to JH6 with Odin, then do the JH7 update via your phone or with Kies, then you can do the one-click root.
Or just skip JH7 and bump up to JI6.
Thanks for the link...
Some more questions:
1. Will this clear my unlock? I forgot to write down my unlock code. Is there a way to get it out again before the flash?
2. Will this completely eliminate all traces of modifications?
3. What about my apps? I have a appbrain account, will I use that to revert? What about paid apps?
Thanks in advance..
Regards
Nick
verysafety said:
You can always use ODIN and flash it that way...
http://forum.xda-developers.com/showpost.php?p=8567598&postcount=6
Click to expand...
Click to collapse
Thank you all for your help. I was able to upgrade to JH7.
1. Did the JF6 Odin 1-click update (did NOT do a Master Clear)
2. Once back to baseline, I uses Keis Mini to upgrade to JH7 - worked flawlessly
3. Rooted using Lagfix (did not install lagfix though)
4. Installed appbrain app - I see all the apps that I need to re-install. I installed some, but will wait to get home and do the "Once Button" install over wifi
5. Titanium Backup was not able to Restore Apps (no 3rd part app installation allowed). Will just wait for appbrain to do its thing and restore app data only from Titanium backup (hopefully this option exists).
6. Restored all screen from Launcher Pro backup - widgets are messed up, but not a big deal
This definitely worked out, especially comparing to the alternative of sending in the phone and what not..
As a bonus, GPS performance is fantastic - caught 7 satellites in 5 seconds 30' accuracy with my phone near my office window (did not even have to go outside). Will test more with maps on my way home..
Falling in love with Android all over again
Once again, a BIG thanks to those who helped.
I will wait for a few days before taking on 2.2 .. gulp..
Regards
Nick
defriend said:
Thanks for the link...
Some more questions:
1. Will this clear my unlock? I forgot to write down my unlock code. Is there a way to get it out again before the flash?
2. Will this completely eliminate all traces of modifications?
3. What about my apps? I have a appbrain account, will I use that to revert? What about paid apps?
Thanks in advance..
Regards
Nick
Click to expand...
Click to collapse
Just wanted to report back, GPS is awesome now. Takes max 10 seconds (first time) when fired from Google Maps. Subsequent locks are taking no more than 6 seconds.
Also, did not find a way to just restore app data from Titanium Backup. So had to recreate some stuff .. no biggie. Anybody know of an alternative backup app that will actually let me restore apps and stuff - which is the point of a backup app!!
Regards
Nick
defriend said:
Thank you all for your help. I was able to upgrade to JH7.
1. Did the JF6 Odin 1-click update (did NOT do a Master Clear)
2. Once back to baseline, I uses Keis Mini to upgrade to JH7 - worked flawlessly
3. Rooted using Lagfix (did not install lagfix though)
4. Installed appbrain app - I see all the apps that I need to re-install. I installed some, but will wait to get home and do the "Once Button" install over wifi
5. Titanium Backup was not able to Restore Apps (no 3rd part app installation allowed). Will just wait for appbrain to do its thing and restore app data only from Titanium backup (hopefully this option exists).
6. Restored all screen from Launcher Pro backup - widgets are messed up, but not a big deal
This definitely worked out, especially comparing to the alternative of sending in the phone and what not..
As a bonus, GPS performance is fantastic - caught 7 satellites in 5 seconds 30' accuracy with my phone near my office window (did not even have to go outside). Will test more with maps on my way home..
Falling in love with Android all over again
Once again, a BIG thanks to those who helped.
I will wait for a few days before taking on 2.2 .. gulp..
Regards
Nick
Click to expand...
Click to collapse
Hey guys, I just got my Note Pro a week ago and just started looking into rooting. I keep getting a notification about a 128mb stability update. I would assume it's gonna update to the latest build but I'm not sure what the latest build is or if it'll be rootable afterwords. my current build is KOT49H.P900UEU1ANAE. What is the latest build #? Is there a list of updates somewhere detailing what the improvements are? I just want to root, debloat, turn off OTA and remove KNOX.
Edit: sorry forgot to mention it's just the wife model SM-P900
So 48 views and not one person can tell me the latest build# ? I'll figure out the rest.
Sent from my SM-N900V using Tapatalk
Have you checked SamMobile?
http://www.sammobile.com/firmwares/database/SM-P900/XAR/
How i got there:
http://www.sammobile.com
1. Click Firmware on the top.
2. Click the greyed out firmware database link under the blue banner.
3. Under "Select your firmware" I picked Tablet-->Android-->SM-P900....-->Cellular South (which matches the US variants)
muzzy996 said:
Have you checked SamMobile?
http://www.sammobile.com/firmwares/database/SM-P900/XAR/
How i got there:
http://www.sammobile.com
1. Click Firmware on the top.
2. Click the greyed out firmware database link under the blue banner.
3. Under "Select your firmware" I picked Tablet-->Android-->SM-P900....-->Cellular South (which matches the US variants)
Click to expand...
Click to collapse
Thanks muzzy! I had already been to SamMobile but all it had was foreign countries listed. I didn't know about Cellular South being the US version. I'll look again.
Edit: oh look a list of the updates and release dates! My Wi - fi reception seems slow, do any of the update fix that?
I honestly can't say. I'm on NC5 which is dated back in April and have no major issues.
I'm rooted and debloated though, not that this would impact the wifi performance . .
48 views doesn't mean 48 users. About 44 of those are Google Content Crawler, which is Google search engine's bots crawling the net for content to display in google.com. It is an automated process.
Samsung doesn't release changelists, so we don't know what each update does beyond what we can see.
Thanks for the help guys! I just accepted the first update and it took me to ANC5. I guess I'll have to accept all updates until current and then try CF-Auto-Root. I'll report back then.
Actually I just got my tablet like a week ago as well. I m on the same build no as well....haven't updated yet. I also haven't installed Knox either. There is a download arrow on the Knox icon and if I click the icon it starts downloading so I just cancel it. I am thinking of rooting as well. Well what I m trying to say is...keep the thread updated and I will just follow your lead.....hehe.
It always helps to know your country as well as different countries are on slightly different versions. You can always go to sanmobile.com, click on firmware and search for p-900. That will give you the list of all the latest ROMs for different countries / carriers. US based ROMs are listed as "Cellular South".
Successful Root!
Okay guys sorry it's taken so long to respond, I had hernia surgery on Monday so I've been behind on getting this rooted.
My plan was to use CF-Auto-Root and then load TWRP recovery and then load "Debloat Stock Variant" by Gatsrom. I decided to do it in that order because I wasn't sure I could load a custom recovery without being rooted first.
I accepted all updates up to the current = P900UEU1BNK1. Using Win 7 and loaded Samsung drivers. Downloaded ODIN 3.09, Odin 3.07 came with CF-Auto-Root and downloaded TWRP. Booted into download mode and made sure ODIN recognized my P900. And this is when to fun began! Everything seem to be going okay but I did run into a snag. I used ODIN 3.07 because that's what came with Auto- Root and I'd read somewhere of people having trouble with 3.09??? Anyways I got a red "FAIL" message and my screen displayed multicolored lines. I tried running it in ODIN 3.09 and got the same result. (i didn't disconnect anything between the 3.07 or 3.09 attempts, maybe i should have?). I disconnected my P900 and it rebooted giving me a Firmware Error screen telling me to use Kies "Recovery Mode". I tried Kies Recovery but Kies3 wouldn't even recognize the P900. (I started freaking a little at this point!) Anyways, I decided to try and load TWRP because I thought I've got nothing to lose! I loaded TWRP into ODIN and it took, so I thought, because my P900 rebooted into an up and running normal state. (Big Sigh!) I tried booting into recovery but TWRP didn't take, it came up to stock recovery, trying to load TWRP just kicked the P900 out of the Firmware Error state it was in?? I decided to give Auto-Root another go after rebooting Win 7. Used ODIN 3.09 this time and everything went fine and I was rooted! Then I loaded TWRP and it loaded fine! I performed a TWRP backup at this point and things seem to be running smoothly. I still need to load the Debloat Variant, that's what's on my plate for today.
http://forum.xda-developers.com/showthread.php?t=2656551
http://forum.xda-developers.com/showthread.php?t=2706982
http://forum.xda-developers.com/gal...t/rom-original-stock-debloated-stock-t2860069
You are a much braver sole than I. Hope all goes smoothly.
I could be wrong but I would think that if one is going to a different ROM then rooting isn't necessary. Simply use Odin to flash TWRP but ensure that auto reboot is not enabled in Odin when you do it. If you allow the device to begin booting into stock system it's going to overwrite recovery again (with stock recovery) so what you want to do is flash TWRP, and once it's flashed FORCE a reboot directly into recovery again using the hardware keys on the device. At that point you can do an nandroid backup and then flash your ROM.
Sent from my SM-P900 using Tapatalk
treetopsranch said:
You are a much braver sole than I. Hope all goes smoothly.
Click to expand...
Click to collapse
I'm not that brave treetop! I just know my way around a computer and I've rooted a few of these things. Plus I know the guys here on XDA are good at helping out if you hit a snag. Luckily I figured this one out on my own! You've just gotta do your research before jumping in and search read, search read, search read! I provided some links to get you started....get to it!
muzzy99 said:
I could be wrong but I would think that if one is going to a different ROM then rooting isn't necessary. Simply use Odin to flash TWRP but ensure that auto reboot is not enabled in Odin when you do it. If you allow the device to begin booting into stock system it's going to overwrite recovery again (with stock recovery) so what you want to do is flash TWRP, and once it's flashed FORCE a reboot directly into recovery again using the hardware keys on the device. At that point you can do an nandroid backup and then flash your ROM.
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
Thanks for the info muzzy, I'll remember that for next time! :good:
I did get the Debloat Variant up and running and loaded Xposed framework with sdcard full access. Everything seems to be running smoothly!
Ok So I finally got to it and successfully rooted (in first try, if I may add ). Thanks to xblue's guide/heroic efforts I avoided certain things and everything went smoothly. So Basically I installed samsung drivers using Kies, rebooted pc (Win 8.1). Downloaded cf autoroot and downloaded odin 3.09 as autoroot comes with 3.07. Replaced ONLY 3.07 odin exe with 3.09. Started Odin in Admin mode, put the tablet in download mode. Attched to pc and Odin recognized it. Then Gave it a final thought......lol. Pressed Start, device booted couple times. Then PASS appeared on the Odin window after like 30 secs. Installed root checker...successfully rooted. Installed TWRP via odin and flashed that successfully. Made a full back up and installed a ROM of my choice. I am a happy camper.
Sweet Deal singhsta! I'm glad my efforts were a help!
i would update to the latest version.. i tried using the original one that you have however i got the screen flicker issue so had to update.. the first update isnt very good wifi keeps dropping but the most recent version doesn't tho you may have a bug where every time you unlock the screen the tablet is still asleep even though the icons are visible so you have to lock the screen again and unlock. however if you factory reset this bug goes away.
i find the latest version is the most stable and battery life is better if you disable all the unnecessary apps that you can i usually get rid of most of the samsung back up apps and all the google ones bar the ones it needs to run play store etc and maintaining the ones that sync for back up.
wifi was really slow when i first got it and would drop very annoying but now it seems better but have experienced slow wifi i think it's a hardware issue all note pro's have in built that should have been sorted by the latest build. i hope they finally give it an update in the coming months even to 4.4.4. or something.
I was able to install the first of the two updates earlier for the 5.1.1 update on my Verizon Galaxy Note Pro 12.2. The second downloads, prompts for install, reboots and begins installing but errors out and reboots back into the OS home screen. The Verizon software update manager shows Failed software update error code 402. I have factory reset my tablet a couple of times and still same issue. I do not have my tablet rooted and no apps disabled.
I downloaded the latest available Samsung firmware md5 file, version VZW-P905VVRUANK1-20141205133604 and tried flashing using Odin 3.07 while in download mode. It starts and after a few seconds, Odin fails and on the tablet screen, I get the error, SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1. I have re-downloaded the firmware along with older versions and still same issue.
I was reading somewhere that my tablet could be "soft bricked" and that is why it will not install the second part of the OTA. As for the Odin/download mode error, I had read that the firmware version I am trying to flash in Odin has an older version of bootloader than my current and Samsung does not let you downgrade the bootloader. I may be wrong on both accounts, which is why I am seeing if anyone else has had this same issue or have any advice on what I can try.
Thanks in advance!
Same here. I unforze all the apps unintstalled SU and factory reset still no dice. VZW repair assistant wont work or smart switch. RA says device firmware not supported and smart switch says im up to date. The first part of the update installed no problem.
dansto82 said:
Same here. I unforze all the apps unintstalled SU and factory reset still no dice. VZW repair assistant wont work or smart switch. RA says device firmware not supported and smart switch says im up to date. The first part of the update installed no problem.
Click to expand...
Click to collapse
I had the exact same issues. Here's what I did with my 4.4.2 Rooted NP. I wiped it completely from within the device, then connected it and to the VZW software and let it do a "Repair". After that, my tablet also said that it was up to date, still on 4.4.2. I let it sit overnight and tried downloading the software update the next morning from the tablet, and it took both of them. My NP is rocking 5.1.1. now, much faster. No root but that's alright for now. By running the repair assistant from VZW, it also got rid of the Unlocked Symbol, which may have prevented the upgrade in the first place.
tdetroit said:
I had the exact same issues. Here's what I did with my 4.4.2 Rooted NP. I wiped it completely from within the device, then connected it and to the VZW software and let it do a "Repair". After that, my tablet also said that it was up to date, still on 4.4.2. I let it sit overnight and tried downloading the software update the next morning from the tablet, and it took both of them. My NP is rocking 5.1.1. now, much faster. No root but that's alright for now. By running the repair assistant from VZW, it also got rid of the Unlocked Symbol, which may have prevented the upgrade in the first place.
Click to expand...
Click to collapse
I was able to get mine to update using ODIN and the firmware file from sammoble. Factory reset on the tablet, factory reset in recovery and finally ODIN worked.
I was having the same problems as the OP listed. Once I decided to live without root and I would be okay with wiping the tablet, I performed exactly what dansto82 said he did and I'm now on 5.1.1.
Now hoping someone comes up with a way to root.
Hey, I have the p905v and it is running 4.4.4, I rooted it with towelroot and it was completely fine. I then tried putting twrp recovery on it the wrong way through flashify and now I don't have a recovery mode and can't update it to 5.1.1. Other than that the tablet runs perfectly fine. Is there a way I can fix it?
Sent from my SM-P905V using XDA Free mobile app
Hey all, need some advice... I recently rooted my phone and found it wasn't for me (way too many apps stopped working). Because of this I tried to unroot the phone, but got stuck in a boot loop and had to recover from scratch.
Anyways, I'm running stock now and the system is back to being rooted. Problem is, I can't seem to update the phone. I'm not getting an error message either. Both Smart Switch and the phone simply say I'm up to date, but I'm on APB7 when I should be able to get APD3.
Is there anyway to fix this? Will I need to factory reset the phone? I'm not sure how to get the phone to recognize an update now.
Same here. I rooted my phone, installed TWRP but battery drain and apps not working properly made me go back to stock. Now I cant get any updates. I flashed APEQ fw yesterday dated June 8 but still dont get the June 17 updates.
I used Smart Switch to do an Emergency Reinstall of the firmware. Had to start over from scratch with my phone... It installed the lastest firmware though.
Been researching as much as I can online and it seems the consensus is simply unrooting the phone does nothing. You have to factory reboot. Tripping Knox won't stop you from getting updates but an unrooted phone that wasn't factory reset still won't get updates. Fun times. Last time I root my phone... Things aren't the same since I last rooted in Android 4.0. Now too many apps and updates etc. check for root and stop working if they detect it.
Luuthian said:
Hey all, need some advice... I recently rooted my phone and found it wasn't for me (way too many apps stopped working). Because of this I tried to unroot the phone, but got stuck in a boot loop and had to recover from scratch.
Anyways, I'm running stock now and the system is back to being rooted. Problem is, I can't seem to update the phone. I'm not getting an error message either. Both Smart Switch and the phone simply say I'm up to date, but I'm on APB7 when I should be able to get APD3.
Is there anyway to fix this? Will I need to factory reset the phone? I'm not sure how to get the phone to recognize an update now.
Click to expand...
Click to collapse
Did you use Odin to flash back to stock?
malek777 said:
Did you use Odin to flash back to stock?
Click to expand...
Click to collapse
I used the Emergency Recovery function of Smart Switch which, from my understanding, is basically the same thing. I know how to use ODIN but it seemed a better idea to go with the official solution. Guess I'll find out if it worked once the June update is available in Canada.
S8+ /S8 Global Unlocked Variants, (ie: G955FD, etc) Desperately need help w/issue After 8.0 Update...
Hi, I have a G955FD & have family members with this same model, as well as the Global unlocked regular S8-dual sim. We all have the same issue after the Samsung 8.0.0 update. The phone is no longer reliable. Randomly, these devices will not have any ring on incoming calls. If they don't leave a VM, then you have no indication of a missed phone call. In addition, random periods where text messages will also just not come thru. Difference on the texts is, when you reboot, they all populate in the message app and notifications. But the incoming calls are not known and lost forever w/o a VM left for you by caller.
I have been in contact with Samsung, although they indicate right off that I have no warranty because I didn't buy a carrier device from an authorized vendor for my local use, they were open & helpful to reveal that they are aware of '8.0 ringer issues' on the unlocked global devices. BTW, this must be a huge number of people across the world with this problem, but like my friends/family, originally think they have signal/carrier issues etc. Samsung says that it should be addressed in a patch or update..... but, WHEN? I have had a messed up phone for over 3months and counting.
The only thing that can be done to attempt having the phone work 'more often' is to do a restart every hour all day long and hope that your phone will ring when someone is calling.
I, personally, being the family tech guy, am the one working on the issue so I'm here to ask for help/input.
Been dealing with this issue for over 3 months now, here's some of what I have done and what I'd like help with please...
I have attempted 5x to install a custom ROM from XDA to alleviate this issue completely, but as of now, still unsuccessful. I've been rooting/hacking my android devices since my 1st but somehow can't get the process to work thru. At this point, using Odin, I have no issue to get my phone running TWRP and rooted. Somehow, after that point something isn't going right and my phone has to be re-odin flashed with OEM ROM and then wait 1 week for OEM unlock to re-appear to try again. So, If I could complete this process next time the OEM-unlock is back up, my problem would be over.
Now, since I am having issue with completing a custom ROM install... I thought, why not flash a previous OEM ROM (7.0 NOUGAT) and again, my problem should be over and I could wait until a 9.0 update to see how that goes. So far, any 7.0 stock ROMS I have been able to find/download, have 'failed' install in Odin. (I have standard Odin, patched and Prince Comsey) so I always try them all before I say it's a true fail.
Can anyone help me to understand why, with all the root/roms Ive done, cannot get custom ROM to complete install. I was trying for the CarHD or Batman. after rom flash, something goes wrong and the phone either goes bootloop or failed verify. (BTW, couple X I did flash the no-verify to alleviate that issue but still get bootloop or no new rom boot up)
The other thing I'd love to be able to do right now that 'should' be a piece of cake, (but hasn't been) until I figure out the custom rom install issue, is to ask for anyone that can post a link to a valid ODIN-flashable Stock 7.0 NOUGAT ROM for my S8+ G955F/FD. That would solve everything for now and I'd just disable updates for the interim. As previously mentioned, the couple I have found would only FAIL on Odin flash attempts. Seeing that this is a global, unlocked device, is it possible to flash a stock rom or flash a diff CSC that can get me North America Tmobile setup (my USA provider) I noticed that the global phone has no options to disable LTE or turn wifi calling on/off etc.
I apologize if I have jumped around in my post, not provided enough details or not written very eloquently, but I am happy to provide any other needed info to move forward if any of you have ideas here. I'm just at the end of my rope with this right now.
Any help, input here is much appreciated! TIA! mark~
Trying to be helpful here.
For some folks flashing with Odin the first run through errors/fails. That issue was a PITA. I found a post somewhere which said when you hook up the phone to flash with Odin, the first attempt will fail, but to leave the phone connected, go back into download mode, and flash again. Do not unplug the phone when you do this.
For some reason there's a kink in Odin with some folks.
That info, wish I could recall who by - they deserve the recognition, anyway it solved all my Odin errors.
JeffDC said:
Trying to be helpful here.
For some folks flashing with Odin the first run through errors/fails. That issue was a PITA. I found a post somewhere which said when you hook up the phone to flash with Odin, the first attempt will fail, but to leave the phone connected, go back into download mode, and flash again. Do not unplug the phone when you do this.
For some reason there's a kink in Odin with some folks.
That info, wish I could recall who by - they deserve the recognition, anyway it solved all my Odin errors.
Click to expand...
Click to collapse
hey jeff, thanks for checking in when the OEM unlock button returns again tomorrow, I'll keep this in mind on my next attempt. i did encounter that fail several times with some OEM firmware flashes (trying to go back to 7.0) and this should resolve that problem. overall though, my real issue seems to be when attempting a root/custom rom instead of a stock replacement... and 'after' i get TWRP completed. I'm doing something wrong with a button hold sequence or something else. maybe need flash 'do not verify' right off too. I'm gonna go extra slow/careful following each step from a great, detailed post for TWRP/ROOT/ROM procedure that i found here over weekend written by 'jesec' what i hate the most is, i only have 1 shot doing this with the oem unlock button, if messed up, have to re-flash a stock rom and wait another 7 days to try this all again.
i still cannot believe its been about 13wks and samsung says they are aware, yet still has not patched this problem. i love my samsungs but im so fed up, i almost ordered a oneplus 6 this weekend just because of this random no ring issue.
thanks much!