Related
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 own a rooted SM-G900P which is the Galaxy S5 Sprint. Trying to unroot or update my prl on this phone. Basically I only have internet service on my phone running Exodus or Cyanogen Mods. Currently running Exodus. Everytime I try to install a rooted stock rom from Clockworkmod/Phillz touch recovery it won't boot. I tried to use Odin to no avail had to rename the downloaded files to .tar just to run them then got "sw rev check fail: fused 3>binary 1" as the error on the phone. I need to unroot this phone to get my prl updated since I changed my number. Any ideas? Thank you!
Running Windows 7 64-bit, Odin 3.07, 3.09, SM-G900P, samsung usb cable. Is recovery flash locked?
same problem any idea
May be helpful, let us hope so...
Personally, I would get a new build of Odin (3.11, 3.13. or higher an Official , not off some weird far out website)
Odin does still work on the phones, (however, I do believe you need "Stock" firmware, at least installed to "update" could be wrong)
After you have a newer Odin, start that, then I would get the phone in Download mode. Then plug into PC. You see lights change color on Odin, also will have a not that you are hooked up. Now, I really have not updated the PRL ...yet. But, I think, if you, through Odin, Push the latest Platform (MM) , then, change the PRL, Then Add recovery (cause you don't have one now!
I think your done, especially if you put on a different ROM. (don't think Los or ASOP change any of those setting (PRL)
Hope this can be helpful. Plus, don't worry, been there done this!!!
Greetings.
I didn't post in very long time on this forum,since I could handle most of the problems on my own,now I need some andvanced tips and advices,so I'm reporting in.
I bough myself a Samsung Galaxy S4 Black Edition last year here in Bosnia and Hercegovina.Beautiful phone,never got a scratch on it,It had Android 4.2.2 Jelly Bean out of the box but all of the features from basic S4 except one,it couldn't update firmware to Lolipop 5.0.1.
That used to bother me,since I had much older devices that supported JB and this phone was just special,enough that I couldn't let it be my daily driver having unused potential,so i threw myself at work(which will later prove a very bad decision).
I checked for OTA updates in the settings and that option would litteraly do nothing,providing no info,or searching for new updates.
Smash that Build number,got into developer mode,toggle USB debugging,Install Kies on PC,run it as Admin,download latest drivers,connect the device,Firmware update asks for IMEI and s/n,type them in,says to check my s/n and IMEI,do that few times under different compatibility options,still the same.
I thought it must be something bad with data/catche so i reset to recovery mode and wipe them out,setup the phone,enter the OTA update for second time,it shows me "Your device have been modified, Software updates are not available", check device status and it states "Samsung",after several attempts it sometime said "Modified" sometimes "Samsung",Kies didn't recognise the device through all this process.
I was already lost here,but I thought,hell Kies isn't working,neather is OTA,i could flash using Odin,that might do the trick.
Went to Sammobile,downloaded latest drivers and Odin,found one Firmware that I though was compatible.,unbloked them in properties and set to rin as Admin.
Uninstalled Kies and checked for leftover drivers again,and it was all clear to go,ran odin,mounted firmware,set device in download mode and started flashing but Odin poped out "complete(write) operation fail" error.
Didn't want to try fixing it,went straight back to SM and downloaded two other firmwares,one said "complete(write) operation fail",and the other "Re-Partition operation failed",so I thought Odin was bad,since I checked on two PC's with several USB ports.
Download two more versions of Odin and find a stock s4 PIT file here somewhere for repartrition error.
Extracted everything,unblocked and ran with privilegies,same thing on both Odin versions,except that only Odin 3.07 could flash the pit file alone with no problems it passed.
Next time i ran download mode i tried to flash the firmware write fail came up again,extracted recovery and flashed it alone,worked like a charm,so I tried flashing once again,it proceedes a little further with same write error.
Reset the phone to wipe data and catche and it goes into "Firmware Upgrade Encountered An Issue Error",Install kies,it still doesn't recognise the phone.
Out of option right now I go for search of alternative recovery software,and I found the famous "Dr.Fone" (how stupid I was to not read all those,"if it wasn't for this software my phone would die" comments)
Installed it,ran recovery my phone shuts down and displays "set warranty bit: kernel message",from this point nothing works except recovery mode,so I install CWM recovery and flash a Custom ROM,now only this option that sets my phone in working order and I want to recover it's Firmware back,Anyone that could help me with this issue,or had it solved before?
Atleast give it a try.
this amount of pain can't be titled
Drow_Warlord said:
Greetings.
I didn't post in very long time on this forum,since I could handle most of the problems on my own,now I need some andvanced tips and advices,so I'm reporting in.
I bough myself a Samsung Galaxy S4 Black Edition last year here in Bosnia and Hercegovina.Beautiful phone,never got a scratch on it,It had Android 4.2.2 Jelly Bean out of the box but all of the features from basic S4 except one,it couldn't update firmware to Lolipop 5.0.1.
That used to bother me,since I had much older devices that supported JB and this phone was just special,enough that I couldn't let it be my daily driver having unused potential,so i threw myself at work(which will later prove a very bad decision).
I checked for OTA updates in the settings and that option would litteraly do nothing,providing no info,or searching for new updates.
Smash that Build number,got into developer mode,toggle USB debugging,Install Kies on PC,run it as Admin,download latest drivers,connect the device,Firmware update asks for IMEI and s/n,type them in,says to check my s/n and IMEI,do that few times under different compatibility options,still the same.
I thought it must be something bad with data/catche so i reset to recovery mode and wipe them out,setup the phone,enter the OTA update for second time,it shows me "Your device have been modified, Software updates are not available", check device status and it states "Samsung",after several attempts it sometime said "Modified" sometimes "Samsung",Kies didn't recognise the device through all this process.
I was already lost here,but I thought,hell Kies isn't working,neather is OTA,i could flash using Odin,that might do the trick.
Went to Sammobile,downloaded latest drivers and Odin,found one Firmware that I though was compatible.,unbloked them in properties and set to rin as Admin.
Uninstalled Kies and checked for leftover drivers again,and it was all clear to go,ran odin,mounted firmware,set device in download mode and started flashing but Odin poped out "complete(write) operation fail" error.
Didn't want to try fixing it,went straight back to SM and downloaded two other firmwares,one said "complete(write) operation fail",and the other "Re-Partition operation failed",so I thought Odin was bad,since I checked on two PC's with several USB ports.
Download two more versions of Odin and find a stock s4 PIT file here somewhere for repartrition error.
Extracted everything,unblocked and ran with privilegies,same thing on both Odin versions,except that only Odin 3.07 could flash the pit file alone with no problems it passed.
Next time i ran download mode i tried to flash the firmware write fail came up again,extracted recovery and flashed it alone,worked like a charm,so I tried flashing once again,it proceedes a little further with same write error.
Reset the phone to wipe data and catche and it goes into "Firmware Upgrade Encountered An Issue Error",Install kies,it still doesn't recognise the phone.
Out of option right now I go for search of alternative recovery software,and I found the famous "Dr.Fone" (how stupid I was to not read all those,"if it wasn't for this software my phone would die" comments)
Installed it,ran recovery my phone shuts down and displays "set warranty bit: kernel message",from this point nothing works except recovery mode,so I install CWM recovery and flash a Custom ROM,now only this option that sets my phone in working order and I want to recover it's Firmware back,Anyone that could help me with this issue,or had it solved before?
Atleast give it a try.
Click to expand...
Click to collapse
Day#4 Fail compilation
I see that this gets no response,but I'll continue this thread just in case I fix this and somebody else gets into same problem themselves.
I mentioned before that I somehow flashed custom ROM over CWM and that helped my phone boot into working state after bootloop error caused by greatest Android software there is on the internet,the legendary "Dr.Fone"
The Custom rom used was "[OFFICIAL][i9500][5.1.x] CyanogenMod 12.1 for Samsung Galaxy S4 [NIGHTLY]" From xda user: Alberto96 (thank you friend).
After several other failed attempts of implementing Stock firmware on this bricked device over the PC,I got to the point where I think that it's literally imposible to make it work since I tried so many ways and patterns of installation with no difference in the outcome results whatsoever.
I took a moment to rethink my strat over this and googled other ways of flashing that firmware without using PC.
Found 2 possible solutions that I'm trying to make use of,first is Odin Mobile and the Other is FlashFire.
Since both require rooted devices,finding way to root bricked S4 wasn't a very pleasant experiance,since flashing SuperSU through CWM recovery didn't work,Odin managed to flash me nice Autoroot from Chainfire over the custom ROM I installed before,I found a problem even there since the I9505 autoroot wouldn't work,the custom firware had changed the phone model to I9507 that I downloaded the Autoroot for,was a confusing issue,but I managed to root it anyways.
Page I used for this purpose was Chainfire Autoroot database(sorry if I'm violating forum rules but I think this could be left here without further discussion about it).
After rebooting the device I downloaded Rootcheck software along with SuperSU and FlashFire which confirmed that it's fully unlocked/rooted.
Now I'm recharging my phone so I can later tonight go ahead and transfer firmware to it's SD card and try to flash it once again with FlashFire,last option I'm thinking of as of now if this wouldn't have any progress is to download Odin mobile and try another flash,I'm running out of ideas on this one.
Sorry for the long posts,but these get no respose so who cares.
Hello everyone, looking for advice in how to return to factory firmware. First, a few bullets to condense the information, then an expanded explanation below. Any assistance would be appreciated.
TL : DR
-Xfinity Mobile GS8+, SM-G955U
-Phone boots and works fine
-When device was still on Nougat, the Oreo beta firmware update.zips were floating around
-Downloaded and installed via factory recovery said update.zips in succession
-Stuck on pre-release build, want to get back to official Verizon Firmware and receiving OTAs
-Current Build: R16NW.G955USQU2CRAD
-Desired Build: G955USQS5CRI4 (Verizon, 09.11.18)
-Tried flashing CRI4 package manually via Odin, Odin said no
-A few hours of Googling and reading through forums as etiquette demands I try first has led me to post this, never not been able to find a fix in the forums
-Plz help, will PayPal/GooglePay/whatever you a 12-pack of beer or whatever to whoever gets me back to factory
Things I've Tried:
-Factory reset
-Odin
-Smart Switch
-OTA
So I have a Galaxy S8+ purchased through Xfinity Mobile. I wasn't able to get into the Oreo beta officially offered through the Samsung Program, but there were update.zips floating around that allowed you to migrate to the pre-release builds. The samsung.firmware.science link above was relatively straightforward - pick your model, it had the latest official build, download an update.zip, and profit.
As the beta program progressed and various more final builds were released, these builds provided additional successive update.zips, until ultimately resting on what was the final version, build number R16NW.G955USQU2CRAD, which I am on currently. I use various forms of Package Disabler and had until recently kept a lot of Samsung's bloat disabled, including the OTA services. Note this only disables them and keeps them from running, not actually remove them from the phone.
Anyway, being an old ROM crackhead from back in the day when aftermarket ROMs actually provided significant software improvements over the garbage that OEMs ship on their phones, I don't like OTA updates that often because I prefer to factory reset after each update - the updates usually make the phone feel sluggish, which may be placebo, but here we are. In light of all the recent Android security vulnerabilities, despite not doing dumb stuff on my phone I figured it was time to go ahead and OTA to get the newest security patch. The issue is that my phone does not recognize any new OTAs despite being on a firmware build from January 2018.
I'm familiar with Odin, figure no big deal, grab the newest build for Verizon (Xfinity Mobile runs on Verizon towers, there's currently a Verizon sim in the device, and Xfinity Mobile builds seem to be entirely absent) and try to flash G955USQS5CRI4 dated 09.11.18. Verified through redundant sources this is, in fact, the latest Verizon build for the S8+.
Lo and behold, it doesn't work. Contacted Samsung regarding possible solutions, their chat agent wasn't very helpful, directed me to a local authorized repair store, who said they may or may not be able to flash it back with Samsung's software, and it requires what may be a two hour diagnostic that checks every possible thing it can on the device, and if it's not an official build, they will tell me to **** off, not withstanding the fact that the guy mentioned that the software from time to time glitches and crashes. My experience with flashing firmware makes me wary of what would happen during a system flash if the software crashes.
Anyway, for those of you who bothered to read past the TLR and embrace my dissertation, I've been out of the flashing game for a while, and because flashing factory firmware via Odin was my go to in the past, I'm not up to date on fixes for obscure issues. A few hours of Googling and reading through forums and I'm not anywhere closer than where I started, and I'd rather fix this myself rather than go to a store and potentially pay them for something that is "out of warranty."
Any ideas would be much appreciated, would gladly PayPal/Google Pay/Whatever someone a 12-pack of beer/$ to someone who can help me get this thing back to factory firmware.
Thanks in advance for any help.
From looking at your odin log almost looks like nothing was flashed, usually you will see abl.elf, modem, system.img, etc.... in the log while it's being flashed; After it checked the MD5 and started flashing it almost immediately closed it looks like but see no errors.
*After looking again I notice it says (success 0/fail 1) so it did not flash anything. Also make sure you are using the newest odin to flash
My suggestion, try flashing without USERDATA; When I flash I flash:
BL/AP/CP/CSC_OYM and not the HOME_CSC and never UserData
If that doesn't work try odin to G955USQU2CRC5 (Verizon 4/18) and then from there update to the latest update.
bmxmike said:
From looking at your odin log almost looks like nothing was flashed, usually you will see abl.elf, modem, system.img, etc.... in the log while it's being flashed; After it checked the MD5 and started flashing it almost immediately closed it looks like but see no errors.
*After looking again I notice it says (success 0/fail 1) so it did not flash anything. Also make sure you are using the newest odin to flash
My suggestion, try flashing without USERDATA; When I flash I flash:
BL/AP/CP/CSC_OYM and not the HOME_CSC and never UserData
If that doesn't work try odin to G955USQU2CRC5 (Verizon 4/18) and then from there update to the latest update.
Click to expand...
Click to collapse
Thanks for the response. I'm downloading the CRC5 file from Updato, and while the download speed is fluctuating, it's averaging around 50 KB/s with an ETA around 22~ hours. Is there a faster method to download this? I have a 300 Mb/s connection, so there's no bottleneck.
I'll try those steps in Odin, but can you expand on the reasoning so I understand the underlying mechanics? I was using the CSC_OYM and not the HOME_CSC, but why does this make a difference? Why never use USERDATA?
zerofighter1 said:
Thanks for the response. I'm downloading the CRC5 file from Updato, and while the download speed is fluctuating, it's averaging around 50 KB/s with an ETA around 22~ hours. Is there a faster method to download this? I have a 300 Mb/s connection, so there's no bottleneck.
I'll try those steps in Odin, but can you expand on the reasoning so I understand the underlying mechanics? I was using the CSC_OYM and not the HOME_CSC, but why does this make a difference? Why never use USERDATA?
Click to expand...
Click to collapse
I'm saying I have never flashed USERDATA as I've never seen it packed in most the roms I download, only other thing they have included is MAYBE a pit file for repartitioning. As for CSC:
Home_CSC: Flash the firmware without wiping the data (if you just want to update the ROM)
CSC: Flash the firmware along with a complete wipe including data (mostly used in cases like bricked phones or Go-Back-To-Stock situations)
I would try reflashing in download mode doing what I suggested and make sure that only reboot, nand erase, and f. reset are the only things checked.
As for downloads my suggestion is google try this:
site:androidfilehost.com G955USQU2CRC5
or
G955USQU2CRC5 filetype:zip (basing on the fact the roms I've downloaded all are zip format)
I think you can search from within the site, not sure. If you can find it always try download off filehost atleast I do because better speeds.
bmxmike said:
As for downloads my suggestion is google try this:
site:androidfilehost.com G955USQU2CRC5
or
G955USQU2CRC5 filetype:zip (basing on the fact the roms I've downloaded all are zip format)
I think you can search from within the site, not sure. If you can find it always try download off filehost atleast I do because better speeds.
Click to expand...
Click to collapse
https://forum.xda-developers.com/att-galaxy-s8+/how-to/g955u-stock-g955usqu2crc5-odin-files-t3773033
I managed to find this under AT&T SM-G955U thread, is this of any significance? Okay to flash?
zerofighter1 said:
https://forum.xda-developers.com/att-galaxy-s8+/how-to/g955u-stock-g955usqu2crc5-odin-files-t3773033
I managed to find this under AT&T SM-G955U thread, is this of any significance? Okay to flash?
Click to expand...
Click to collapse
Should have mentioned, the reason I'm asking is there is a discrepancy between the file size from Updato and this file - Updato file is 3.6~ GB and the one in this thread is 3.12~ GB.
No telling could be way it was compressed or files inside, like I said the rims I usually download don't include a USERDATA tar so maybe one has one and the other doesn't.
Have you tried again with what you have now?
There's been plenty of times I've tried to flash something to where I sometimes have to do it 3-5 times cause I over look something like under options (especially with resetting Odin cause when I do that it automatically enables partitioning for some reason). Also try a different USB cable, cause there should be something in Odin logs to lead you to problem; ex:
1 > 2 = This error usually means lower version Bootloader
Couldn't open file on XXXX: = Usually means partitioning was selected but no partition table given
Also if nothing else try flash in cosmey, I have yet to flash a v5 BL so I can't give you a this is what you need to do because my USB port is not working, but I've flashed from v1 to v3 in cosmey and have never had a issue with software only User Error (I'm trying to find a way to update from partycyborg to the same as you without Odin but cant because of my BL)
bmxmike said:
No telling could be way it was compressed or files inside, like I said the rims I usually download don't include a USERDATA tar so maybe one has one and the other doesn't.
Have you tried again with what you have now?
There's been plenty of times I've tried to flash something to where I sometimes have to do it 3-5 times cause I over look something like under options (especially with resetting Odin cause when I do that it automatically enables partitioning for some reason). Also try a different USB cable, cause there should be something in Odin logs to lead you to problem; ex:
1 > 2 = This error usually means lower version Bootloader
Couldn't open file on XXXX: = Usually means partitioning was selected but no partition table given
Also if nothing else try flash in cosmey, I have yet to flash a v5 BL so I can't give you a this is what you need to do because my USB port is not working, but I've flashed from v1 to v3 in cosmey and have never had a issue with software only User Error (I'm trying to find a way to update from partycyborg to the same as you without Odin but cant because of my BL)
Click to expand...
Click to collapse
Hey sorry, I've been busy working and haven't had the time to get back to this. I'm going to try this today and I'll get back to this post with an update.
So yesterday i tried odining to pie, was on the Nov security patch. Downloaded the correct file from Firmware Science, everything installed fine. Phone reboots but has sat on the Samsung Note 8 bott screen for over 12 hours now. And I cant seem to access recovery anymore. Download more works, but that's it. An I've tried to Odin Pie again, but now it fails every time. Any ideas to fix this? Att varient btw.
If you downloaded from Firmware Science you didnt download Odin files. Go HERE to Post #2, download Odin v3 listed there and the Stock Odin files for N950USQU5DSC1 .
Get into DL mode
Populate the BL, AP, CP, CSC (NOT the HOME_CSC) and the USERDATA and hit start. This will get you to the latest stock (Pie)
Trying it now
timark251 said:
Trying it now
Click to expand...
Click to collapse
And?
Got it to work perfectly, also used a new cable and USB port. Thanks for your help!