Today I had a software update and come to figure out it was 6.0!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
nice man.
are you using at&t sim and currently in america? because i am in asia and i unlocked my phone!
so i barely get any update thing. they say to use at&t sim if i have to update. alas! do tell please
---------- Post added at 09:02 PM ---------- Previous post was at 08:56 PM ----------
plus if some one has zip for MM for lg d850 i will thankful
issues after mm upgrade
Here's what I experienced after update...
Once you upgrade you can't flash back to stock. LG flash tool fails because it couldn't detect the model. After setting up McAfee it disables root and usb debugging. You have to go into McAfee and turn those options off. So it seems like once you go to mm you can't get back to lollipop. I'm also having proximity sensor issues also with the screen going black during a call. I guess once we can get root I'll be able to install another rom.
Hi, I got the notification and I was not in WiFi network so decided to cancel it and check it again once I got to wifi zone. But when I checked next time, I just get a message, your phone is uptodate. I tried rolling date forward to circumvent the 24 hour check, but no luck. Any ideas to get the update notification back ?
no luck updating
tried the update today, it just sends me to twrp recovery screen every time
You can't install a factory update while rooted. Come on guys you should know this.
Sent from my LG-D850 using XDA-Developers mobile app
Update
vishnugs said:
Hi, I got the notification and I was not in WiFi network so decided to cancel it and check it again once I got to wifi zone. But when I checked next time, I just get a message, your phone is uptodate. I tried rolling date forward to circumvent the 24 hour check, but no luck. Any ideas to get the update notification back ?
Click to expand...
Click to collapse
I had the same thing happen to me so what I did to make the phone think I haven't checked for an update and avoid the 24 hour wait I did a hard reset. I want to point out that I didn't care much about all my apps being deleted and you might want to back them up. Note: I was on stock lollipop
Anyone do an adb pull and extract the modem yet? Want to flash it on Fulmics 5.0.
Sent from my LG-D850 using Tapatalk
DARKCHYLDX101 said:
Anyone do an adb pull and extract the modem yet? Want to flash it on Fulmics 5.0.
Sent from my LG-D850 using Tapatalk
Click to expand...
Click to collapse
Please let us know if you get it accomplished.
louvass said:
Here's what I experienced after update...
Once you upgrade you can't flash back to stock. LG flash tool fails because it couldn't detect the model. After setting up McAfee it disables root and usb debugging. You have to go into McAfee and turn those options off. So it seems like once you go to mm you can't get back to lollipop. I'm also having proximity sensor issues also with the screen going black during a call. I guess once we can get root I'll be able to install another rom.
Click to expand...
Click to collapse
Not sure if there is an "anti roll back" But You cannot use flashtools once updating to Lollipop you must use LGUP.
hyelton said:
Not sure if there is an "anti roll back" But You cannot use flashtools once updating to Lollipop you must use LGUP.
Click to expand...
Click to collapse
Where do I get a KDS for the 850 along with the LGUP, seems everything points to the 855? thanks. I can't seem to root after the upgrade to 6.
louvass said:
Where do I get a KDS for the 850 along with the LGUP, seems everything points to the 855? thanks. I can't seem to root after the upgrade to 6.
Click to expand...
Click to collapse
Its KDZ. the D850 is TOT method only.
My Guide:
http://forum.xda-developers.com/showthread.php?t=2785089
But remember its your own risk, not sure if downgrading will brick or not yet from MM on the AT&T Model.
FWIW, if you're experiencing DND issues after the 6.0 update check settings > dnd > advanced > schedule. kept noticing on my moto360 it was switching to dnd for no reason. turns out some scheduling magically appeared. been running 6.0 without a hitch since last night. had to manually disable at&t video calling and a few other things but im happy with it thus far.
cjoeone said:
I had the same thing happen to me so what I did to make the phone think I haven't checked for an update and avoid the 24 hour wait I did a hard reset. I want to point out that I didn't care much about all my apps being deleted and you might want to back them up. Note: I was on stock lollipop
Click to expand...
Click to collapse
I tried doing a factory reset after spending a lot of time to back up data. But after fresh restore, I'm getting the message that your phone is uptodate. I m cursing myself why I dismissed the prompt yesterday. Any other solutions to force update ?
hyelton said:
Its KDZ. the D850 is TOT method only.
My Guide:
http://forum.xda-developers.com/showthread.php?t=2785089
But remember its your own risk, not sure if downgrading will brick or not yet from MM on the AT&T Model.
Click to expand...
Click to collapse
Thanks yes I know how to use the flash tool...my problem is it fails every timeI try going back to stock lollipop.
vishnugs said:
I tried doing a factory reset after spending a lot of time to back up data. But after fresh restore, I'm getting the message that your phone is uptodate. I m cursing myself why I dismissed the prompt yesterday. Any other solutions to force update ?
Click to expand...
Click to collapse
You have to do a hard reset through stock recovery. Don't do it if you are using a custom rom. If you are not experienced I recommend you wait to see if you get another update notification
louvass said:
Thanks yes I know how to use the flash tool...my problem is it fails every timeI try going back to stock lollipop.
Click to expand...
Click to collapse
That is because flashtool you cannot use if your on MM you use LGUP with the TOT file.
hyelton said:
That is because flashtool you cannot use if your on MM you use LGUP with the TOT file.
Click to expand...
Click to collapse
Can you send me a link for it thanks man..i got it thanks
louvass said:
Can you send me a link for it thanks man..i got it thanks
Click to expand...
Click to collapse
It's in the 2nd post of my guide in the link I posted earlier ^^ but just remember at your own risk as I haven't seen anyone try yet. Example like the G4 after a certain point people bricked there AT&T model from downgrading. But if you do risk it and everything went smoothly let us all know!
cjoeone said:
You have to do a hard reset through stock recovery. Don't do it if you are using a custom rom. If you are not experienced I recommend you wait to see if you get another update notification
Click to expand...
Click to collapse
No luck, tried hard reset through recovery twice and before that general reset several times. I'm not getting the notification for the second time
Any other ways to force update ?
Related
Hey guys,
Using a guide for the g3 by @topet2k12001 i was able to get permanent recovery working for our d801's running the new 30b Lollipop. I compiled the necessary files into a flashable zip for you all. The zip contains bump'd lollipop boot.img, kk aboot.img, and twrp 2.8.6.1 recovery.
as always... FLASH AT YOUR OWN RISK
Prerequisites:
- Running Stock D80130b
- Rooted
- Autorec installed
Getting Started:
- Copy TWRP-2.8.6.1_D80130b.zip to your phones storage
- Run Autorec and flash TWRP (2.7)
- Reboot to recovery
- Flash TWRP-2.8.6.1_D80130b.zip
- Enjoy!
You should now have a permanent recovery.
DOWNLOAD:
Twrp for d80130b:
https://mega.co.nz/#!qFUDWC4a!nHj3R-gPAEqvZ-yLcQMZxXvTN8eFJg99vWfopnCjR_w
Stock d80130b bootstack + recovery: (flashes stock recovery in case anything goes wrong)
https://mega.co.nz/#!KI9k1YxT!HDJEDSd0X1MEsdr5oiNdutg0aADuqB3A1XrNQUjsqrQ
Credits to @blastagator for the Recovery and @Cloudyfa for Autorec
Great work man...i had a feeling you would bring us a working fix
Was going to try this and got this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
nalanotae said:
Was going to try this and got thisView attachment 3241785
Click to expand...
Click to collapse
If i remember correctly, that means you are not currently rooted - or Autorec doesnt have root permissions
Done!..you're awesome man. By the way, my lollipop charges so slowly like in 4-5 hours. Any help you can offer me?
Thanks very much!! Works great
Sent from my LG-D801 using XDA Free mobile app
snowlin said:
If i remember correctly, that means you are not currently rooted - or Autorec doesnt have root permissions
Click to expand...
Click to collapse
I am rooted and autorec had been granted root permisions........... I may try a fresh install of everything and start over tonight after work...... Thanks for your response
Messip3 said:
Done!..you're awesome man. By the way, my lollipop charges so slowly like in 4-5 hours. Any help you can offer me?
Click to expand...
Click to collapse
Just let it cycle a few days. It will improve.
Same happened for me with 30a and 30b. Of anything i reccomend using "amplify" xposed module.
nalanotae said:
I am rooted and autorec had been granted root permisions........... I may try a fresh install of everything and start over tonight after work...... Thanks for your response
Click to expand...
Click to collapse
maybe you need busybox?
I had that problem once but it was in the middle of me re-flashing the kdz a bunch of times and it didn't happen again. Start fresh if you can
KDZ > Root > Recovery
Great work man!
I knew when I saw you working on it in the other thread that you'd find something!
May I ask what you did to fix this?
snowlin said:
Just let it cycle a few days. It will improve.
Same happened for me with 30a and 30b. Of anything i reccomend using "amplify" xposed module.
Click to expand...
Click to collapse
Alright man...thank you.
mjoecarroll said:
Great work man!
I knew when I saw you working on it in the other thread that you'd find something!
May I ask what you did to fix this?
Click to expand...
Click to collapse
I pulled the aboot.img and laf.img from 20e , bumped the stock lollipop boot.img using a guide i found in the g3 forums and packaged it with twrp 2.8.6.1.
I'm not super experienced or anything but this kind of stuff interests me so i learn as i go
That's pretty awesome. I was gonna try something similar, but I was afraid I was gonna brick my phone... I didn't think about bumping the boot.img at all, that was smart haha.
mjoecarroll said:
That's pretty awesome. I was gonna try something similar, but I was afraid I was gonna brick my phone... I didn't think about bumping the boot.img at all, that was smart haha.
Click to expand...
Click to collapse
It took me a ton of trial and error haha, luckily i had the stock recovery already zip'd so if anything went wrong i could usually just flash that in order to be able to boot again and start over.
snowlin said:
It took me a ton of trial and error haha, luckily i had the stock recovery already zip'd so if anything went wrong i could usually just flash that in order to be able to boot again and start over.
Click to expand...
Click to collapse
Worked just great, thanks a million.
snowlin said:
maybe you need busybox?
I had that problem once but it was in the middle of me re-flashing the kdz a bunch of times and it didn't happen again. Start fresh if you can
KDZ > Root > Recovery
Click to expand...
Click to collapse
That was my plan....... When i first flashed this rom i had no problem with installing autorec but then i got the security error.. So i just flashed kdz then rooted and set the phone up...... Can't wait to get all this going.... Really untested to see how sins if these custom roms run with new radio
Screen goes crazy when recovery tries to dim screen...looks like back when lgd jdi screen issues used to be a problem
jamesd1085 said:
Screen goes crazy when recovery tries to dim screen...looks like back when lgd jdi screen issues used to be a problem
Click to expand...
Click to collapse
hmmm i'm not experiencing this at all, i included the panelfix script from the twrp package too. perhaps its not running correctly.
anyone else having this problem?
snowlin said:
hmmm i'm not experiencing this at all, i included the panelfix script from the twrp package too. perhaps its not running correctly.
anyone else having this problem?
Click to expand...
Click to collapse
So far it happened twice while i was testing...while attemting to back up it did it but was fine as long as i kept screen active...also on restore same issue...if no one else has issue then idk
jamesd1085 said:
So far it happened twice while i was testing...while attemting to back up it did it but was fine as long as i kept screen active...also on restore same issue...if no one else has issue then idk
Click to expand...
Click to collapse
maybe try flashing blastagators twrp package for the 801 : http://blastagator.ddns.net/twrp/2-8-6-1.php
even though this is what i used in mine anyways, it's worth a shot. You will still be able to boot after flashing this since it is only recovery.
I am downloading an update that is 568.3 mb. GO GRAB IT!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Me too!
Manually went to update...
Update finally
AT LAST
Got it!!
5.1.1?
Pump your brakes
If this is the 5.1.1 update and you are rooted and enjoy a custom device. Please understand what this update means before flashing it.
http://forum.xda-developers.com/sprint-galaxy-s6-edge/help/dont-odin-5-1-1-t3136671
wildjeep said:
Pump your brakes
If this is the 5.1.1 update and you are rooted and enjoy a custom device. Please understand what this update means before flashing it.
http://forum.xda-developers.com/sprint-galaxy-s6-edge/help/dont-odin-5-1-1-t3136671
Click to expand...
Click to collapse
You are 100% correct my friend... I hate when people hurry up and jump on the update, then complain non stop they lost root and can't get it back....
Sent from my SM-G925V using Xparent Green Tapatalk 2
Soooperstar said:
5.1.1?
Click to expand...
Click to collapse
+1
If you upgrade to 5.1.1, you will not be able to root at this time
DO NOT ATTEMPT TO ROOT
I have been unsuccessful to go back to OE2 via odin, does someone have the recovery image for 5.1.1
If anyone has taken the update, please report back on whether TWRP and/or Cf autoroot works
Sent from my SM-G925P using Tapatalk
dhonzik said:
If you upgrade to 5.1.1, you will not be able to root at this time
DO NOT ATTEMPT TO ROOT
I have been unsuccessful to go back to OE2 via odin, does someone have the recovery image for 5.1.1
Click to expand...
Click to collapse
This is one of the compilations that has been warned for a few weeks now. It will take some time to achieve a stable Root/Recovery.
So if anyone is satisfied with stock. Unroot and flash away.
Or sit tight and wait for the custom development to catch up to the current stock software :highfive:
I will say, however, the device seems to run much smoother and early signs show battery improvement as well. Obviously it's early but it seems promising. Just wanted to share my stock experience as I chose to not root for the future payment platform
I updated but I am not root
no ram management .
If you take this update, you cannot root for the time being and certainly cannot Safe root (not tripping knox) with PingPoint root. In addition, you cant downgrade kernel, etc.
So the question becomes, what is the best course of action here. Can we PingPong root prior build, then update to OF7 kernel and rom once someone repacks them? Flash with FlashFire and maintain root? Then again, I guess we could accept the OTA and stay stock until CF-Auto Root is updated to work with it.
Either way, I'm holding for a bit here to see what shakes out...
UPDATE: thought about this a second. Sprint doesnt typically lock boot loader like AT&T, verizon. So this locked boot loader is whats preventing people from downgrading kernel once they update right? So this should not be an issue with Sprint if the boot loader is not locked?
Alpine- said:
If you take this update, you cannot root for the time being and certainly cannot Safe root (not tripping knox) with PingPoint root. In addition, you cant downgrade kernel, etc.
So the question becomes, what is the best course of action here. Can we PingPong root prior build, then update to OF7 kernel and rom once someone repacks them? Flash with FlashFire and maintain root? Then again, I guess we could accept the OTA and stay stock until CF-Auto Root is updated to work with it.
Either way, I'm holding for a bit here to see what shakes out...
UPDATE: thought about this a second. Sprint doesnt typically lock boot loader like AT&T, verizon. So this locked boot loader is whats preventing people from downgrading kernel once they update right? So this should not be an issue with Sprint if the boot loader is not locked?
Click to expand...
Click to collapse
Take a look at this thread: http://forum.xda-developers.com/sprint-galaxy-s6-edge/help/dont-odin-5-1-1-t3136671
It is not a looked boot loader that is the problem. T-Mobile solved it so I am sure it will be solved for us very soon.
wildjeep said:
This is one of the compilations that has been warned for a few weeks now. It will take some time to achieve a stable Root/Recovery.
So if anyone is satisfied with stock. Unroot and flash away.
Or sit tight and wait for the custom development to catch up to the current stock software :highfive:
Click to expand...
Click to collapse
Heads up the t-mobile TWRP recovery does get my bricked phone to the recovery, but the buttons do not work. If it did I had a backup I would have tried. Heading to the Sprint Store Tech Center to hopefully get a working phone or a replacement.
dhonzik said:
Heads up the t-mobile TWRP recovery does get my bricked phone to the recovery, but the buttons do not work. If it did I had a backup I would have tried. Heading to the Sprint Store Tech Center to hopefully get a working phone or a replacement.
Click to expand...
Click to collapse
So did the Sprint recovery not work?
How did you brick?
Sprint may not mess with it once the see the wrong recovery
Soooperstar said:
So did the Sprint recovery not work?
How did you brick?
Sprint may not mess with it once the see the wrong recovery
Click to expand...
Click to collapse
It was attempt to see if the CF Auto-Root would work after the update. I went back to other recovery that doesn't open up, if the tech center has the complete firmware maybe it will be to flash it back on. I opened a thread to see if someone can pull the stock recovery from the update. Trying to reflash back to OE2 fails.
dhonzik said:
It was attempt to see if the CF Auto-Root would work after the update. I went back to other recovery that doesn't open up, if the tech center has the complete firmware maybe it will be to flash it back on. I opened a thread to see if someone can pull the stock recovery from the update. Trying to reflash back to OE2 fails.
Click to expand...
Click to collapse
Did you try to Odin our twrp?
Soooperstar said:
Did you try to Odin our twrp?
Click to expand...
Click to collapse
Yes, it was a no go, $75 later I'll have a new phone in a week
I just got a prompt for a new OTA update, but being rooted and running a ROM I couldn't install it. It gave no new information about the update such as size or fixes. Anyone else get this? I'm on an OC3 based ROM by the way.
yea i got it
Seanbest said:
I just got a prompt for a new OTA update, but being rooted and running a ROM I couldn't install it. It gave no new information about the update such as size or fixes. Anyone else get this? I'm on an OC3 based ROM by the way.
Click to expand...
Click to collapse
It is the stage fright update
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
Will we be able to flash it some other way?
ClearD said:
Will we be able to flash it some other way?
Click to expand...
Click to collapse
I'm sure there will be soon
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
Well, on second thought, I just went ahead and let the update run. It completed. Everything appears normal.
I confirm, it is a fix for Stagefright. Baseband version went from I337UCUFNJ4 to I337UCUFNJ5
+ SuperSU is working properly.
Below: Before & After the update
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
New Update Came ..
https://www.att.com/esupport/softwareUpdateArticle.jsp?sid=KB419415&cv=820
ClearD said:
Well, on second thought, I just went ahead and let the update run. It completed. Everything appears normal.
Click to expand...
Click to collapse
Were you rooted with the Flashfire method?
Anytime AT&T or Samsung offer a "security" update FOTA, I cringe. I'm on rooted Lollipop and absolutely have to remain rooted to use Total Recall call recorder (you can't imagine how many times it's saved my ass with baseless promises from AT&T and other utility vendors), so I'm always hesitant to upgrade to any FOTA's that may make it more difficult to either flash a better ROM, or other utilities that it might block. Call me paranoid, but I'm going to hold off and try to find a better solution to threats to my OS. Belarc Security Advisor (Free) is highly respected, and a non-conventional system scan that identifies real threats. Running it yesterday and just now; show no threats. I realize that Stagefright is a threat, but I'm running antivirus software that I trust and keep my phone backed up locally on a regular basis.
billbillw said:
Were you rooted with the Flashfire method?
Click to expand...
Click to collapse
Well, I also let it run. Figured worst case, it would be rejected due to root. It ran, no errors, still on root (using Flashfire method). Stagefright detector now shows my device is safe.
---------- Post added at 09:39 AM ---------- Previous post was at 09:38 AM ----------
nukesnooper said:
Anytime AT&T or Samsung offer a "security" update FOTA, I cringe. I'm on rooted Lollipop and absolutely have to remain rooted to use Total Recall call recorder (you can't imagine how many times it's saved my ass with baseless promises from AT&T and other utility vendors), so I'm always hesitant to upgrade to any FOTA's that may make it more difficult to either flash a better ROM, or other utilities that it might block. Call me paranoid, but I'm going to hold off and try to find a better solution to threats to my OS. Belarc Security Advisor (Free) is highly respected, and a non-conventional system scan that identifies real threats. Running it yesterday and just now; show no threats. I realize that Stagefright is a threat, but I'm running antivirus software that I trust and keep my phone backed up locally on a regular basis.
Click to expand...
Click to collapse
If you're using the Stock AT&T Lolipop, and Flashfire method for rooting, you will be OK to let the update run. It ran with no issues for me and it kept root.
billbillw said:
Well, I also let it run. Figured worst case, it would be rejected due to root. It ran, no errors, still on root (using Flashfire method). Stagefright detector now shows my device is safe.
---------- Post added at 09:39 AM ---------- Previous post was at 09:38 AM ----------
If you're using the Stock AT&T Lolipop, and Flashfire method for rooting, you will be OK to let the update run. It ran with no issues for me and it kept root.
Click to expand...
Click to collapse
That's exactly how I did it. My only concern is that it may install patches that could further restrict future modifications.
I also just completed running Lookout and it found no threats or vulnerabilities. I'm staying where I am until I hear more feedback.
Thanks for your advice. I'll be keeping an eye on it.
It's coming in as a 280mb download, I'm going to see what happens with root (previously used Flashfire)
sim_pl said:
It's coming in as a 280mb download, I'm going to see what happens with root (previously used Flashfire)
Click to expand...
Click to collapse
Please Upload .cfg File For Update My Device .. That OTA File /cache .. Check It And Upload It Please And Check fota Folder
UPDATED POST:
I upgraded with the install stock but "keep root" method, using flashfire...
The update failed at 29%.
I did a factory reset, and it still failed at 29%...
What are my options now?
Update:
I used Flashfire to install the tethering addon... I wonder if that is the culprit.
Installing without thethering... will update with results.
And It's a pain to download that ATT update each time. --- Their servers are SLOW!
Same story here. Update stops and phone reboots about a third of the way through. Defrosted all Samsung/AT&T bloat and tried again. Same story. Bummer.
I rooted my wife's 0C3 with Kingroot and tried to take the update. It failed.
Maybe I should try again since I just used triangle away to get rid of the "custom" nag at boot.
Rockin' a l337 with Goldeneye v49.1 + Wanam Xposed and loving life on AT&T's 4G LTE network
billbillw said:
Were you rooted with the Flashfire method?
Click to expand...
Click to collapse
Yes. Rooted with flashfire, on oc3 bootloader. I ran the update through the normal OTA method, not trying to install it through flashfire. It worked fine and root stayed normal. Verified when titanium backup ran last night on its normal schedule.
Well, it updated fine, using just the straight rooted rom, no additional flashes. No more fails at 29%...
It appears that adding in anything extra, de-bloat, hotspot enable, etc. will cause the update to fail.
/sk
Reinstalled the rooted stock ROM and the update worked fine. Still have root. All is groovy.
I've got a Galaxy S5 that I purchased from someone earlier today and it worked well until I did some type of software update, it went well but then restarted and it's been messed up since. Now, whenever I boot up the phone it boots fine all the way too the Sprint Spark screen and it just hangs, and hangs and then restarts again, and goes through the same process. I've tried reflashing the device using Odin but I keep getting an error "SW REV CHECK FAIL" with some other stuff. I've tired to do so much, I tried resetting the device and the cache using the options. Please, can someone offer me some help. It's a 900P and it's a Sprint device. I just got back from a funeral a little bit ago so I'd love to get this thing working finally, I've been working on it all night.
Can you check the model number under the battery?
I think Sm-g900m is the South America version, and Sm-g900p should be the North America sprint version.
tys0n said:
Can you check the model number under the battery?
I think Sm-g900m is the South America version, and Sm-g900p should be the North America sprint version.
Click to expand...
Click to collapse
Yes, that's correct my bad. It's the 900P. I'll correct the thread.
nulledbyme said:
Yes, that's correct my bad. It's the 900P. I'll correct the thread.
Click to expand...
Click to collapse
Ok, good The "SW REV CHECK FAIL" is probably caused by secure bootloader which won't allow downgrade.
Have you tried to flash the latest firmware?
tys0n said:
Ok, good The "SW REV CHECK FAIL" is probably caused by secure bootloader which won't allow downgrade.
Have you tried to flash the latest firmware?
Click to expand...
Click to collapse
Could you link me a GOOD site that doesn't require me to pay to get fast downloads? Haha I'll try it in the morning if you send me a link.
nulledbyme said:
Could you link me a GOOD site that doesn't require me to pay to get fast downloads? Haha I'll try it in the morning if you send me a link.
Click to expand...
Click to collapse
Sure! This should be the latest firmware available. http://updato.com/firmware-archive-select-model?record=281516900A1911E7963AFA163EE8F90B
Hope it will work to get you up and running.
tys0n said:
Ok, good The "SW REV CHECK FAIL" is probably caused by secure bootloader which won't allow downgrade.
Have you tried to flash the latest firmware?
Click to expand...
Click to collapse
tys0n said:
Sure! This should be the latest firmware available. http://updato.com/firmware-archive-select-model?record=281516900A1911E7963AFA163EE8F90B
Hope it will work to get you up and running.
Click to expand...
Click to collapse
It goes fine all the way till the system.img.ext4 part and it just sits there. I tried letting it sit last night for 4+ hours on a different firmware and it just sat there. Any thoughts?
EDIT: So, I reflashed it, it was successful but my device still hangs at the Sprint screen..
nulledbyme said:
It goes fine all the way till the system.img.ext4 part and it just sits there. I tried letting it sit last night for 4+ hours on a different firmware and it just sat there. Any thoughts?
EDIT: So, I reflashed it, it was successful but my device still hangs at the Sprint screen..
Click to expand...
Click to collapse
Hmm, I have no idea why it won't boot properly. This "stuck on bootlogo" seems to be a common problem on todays samsung models.
Have you tried factory reset in recovery after flash?
Only other thing I can think of is if some other partition got messed up during the software update.
Maybe can be fixed with a 4-file "repair firmware" with BL/AP/CP/CSC-parts. I'll see if I can find one.
tys0n said:
Hmm, I have no idea why it won't boot properly. This "stuck on bootlogo" seems to be a common problem on todays samsung models.
Have you tried factory reset in recovery after flash?
Only other thing I can think of is if some other partition got messed up during the software update.
Maybe can be fixed with a 4-file "repair firmware" with BL/AP/CP/CSC-parts. I'll see if I can find one.
Click to expand...
Click to collapse
I've heard of that before but I've never really looked into it much. Do you by any chance have a Skype or a Discord link I could join so I could talk to you more direct?
nulledbyme said:
I've heard of that before but I've never really looked into it much. Do you by any chance have a Skype or a Discord link I could join so I could talk to you more direct?
Click to expand...
Click to collapse
Sorry, I don't. Maybe it's better if you ask for more help in S5 forum on how to go on with this, as I don't own this device myself. I will probably find that thread if you do, and be able to help futher if needed
Otherwise there's plenty of tutorials on how to flash 4-files with odin.
I did find one and uploaded it to mega in case you want to grab it. G900PVPS3CQB3_CSC_SPT_CL10090296_QB12576102_REV00_user_low_ship_MULTI_CERT.tar.zip
I've used those kind of firmwares on various devices for all kind of problems where official firmware wasn't enough to fix it, and it always worked without problems.
tys0n said:
Sorry, I don't. Maybe it's better if you ask for more help in S5 forum on how to go on with this, as I don't own this device myself. I will probably find that thread if you do, and be able to help futher if needed
Otherwise there's plenty of tutorials on how to flash 4-files with odin.
I did find one and uploaded it to mega in case you want to grab it. G900PVPS3CQB3_CSC_SPT_CL10090296_QB12576102_REV00_user_low_ship_MULTI_CERT.tar.zip
I've used those kind of firmwares on various devices for all kind of problems where official firmware wasn't enough to fix it, and it always worked without problems.
Click to expand...
Click to collapse
I'll try that so, with those files I just put them all into Odin?
nulledbyme said:
I'll try that so, with those files I just put them all into Odin?
Click to expand...
Click to collapse
Yes exactly. This is what you'll find once it's unzipped.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
First make sure your battery is well charged (we don't want it to die during flash)
Just put the files in their boxes in odin, connect your phone in download mode and flash.
Hopefully it will now boot past that bootlogo. If not...there must be some hardware problem.
tys0n said:
Yes exactly. This is what you'll find once it's unzipped.
View attachment 4098803
First make sure your battery is well charged (we don't want it to die during flash)
Just put the files in their boxes in odin, connect your phone in download mode and flash.
Hopefully it will now boot past that bootlogo. If not...there must be some hardware problem.
Click to expand...
Click to collapse
Well, it looks like Odin is just sitting at the "aboot.mbn" part of the flashing process :L thoughts?
nulledbyme said:
Well, it looks like Odin is just sitting at the "aboot.mbn" part of the flashing process :L thoughts?
Click to expand...
Click to collapse
It just sits there? No errors? Maybe you should try a different version of odin, like Odin 3.09
You could also try another usb port and/or different cable. Those are the most common problems when flash won't start.
tys0n said:
It just sits there? No errors? Maybe you should try a different version of odin, like Odin 3.09
You could also try another usb port and/or different cable. Those are the most common problems when flash won't start.
Click to expand...
Click to collapse
I'll give those tips a try I'm also trying Samsung Smart Switch to see if it'll do something.
nulledbyme said:
I'll give those tips a try I'm also trying Samsung Smart Switch to see if it'll do something.
Click to expand...
Click to collapse
Yeah you can do that too. Another thing you've reminded me of now when talking about smart switch...Go to your task manager on pc and make sure that no smart switch or kies is running in background before open odin. It may interfere with odin connection.
I remember it was a common problem with kies/odin.
tys0n said:
Yeah you can do that too. Another thing you've reminded me of now when talking about smart switch...Go to your task manager on pc and make sure that no smart switch or kies is running in background before open odin. It may interfere with odin connection.
I remember it was a common problem with kies/odin.
Click to expand...
Click to collapse
I'll try that, I'm still so confused by this. I flash it, and then ODIN says "RESET" in blue, it resets the device and it hangs at the Sprint logo..
nulledbyme said:
I'll try that, I'm still so confused by this. I flash it, and then ODIN says "RESET" in blue, it resets the device and it hangs at the Sprint logo..
Click to expand...
Click to collapse
Yeah, it's a mystery. If it flash and pass without errors it should work. Can't figure out why it doesn't
tys0n said:
Yeah, it's a mystery. If it flash and pass without errors it should work. Can't figure out why it doesn't
Click to expand...
Click to collapse
Well guess what, I ****in fixed it haha. I just reset after the flash and it's working now! Thanks for all your help man!
nulledbyme said:
Well guess what, I ****in fixed it haha. I just reset after the flash and it's working now! Thanks for all your help man!
Click to expand...
Click to collapse
That's awesome! Glad I could help.
Hi, i got samsung tab s7 and it auto downloaded the update to android 12 and now it says that I can postpone it 9nly 3 times. Is there a way to get rid of it? I wouldn't be able to use the color calibrator app once it will get the update, which makes the tablet pretty useless for me. Thanks
Clear the system cache... I never tried it but was told that would clear it.
blackhawk said:
Clear the system cache... I never tried it but was told that would clear it.
Click to expand...
Click to collapse
blackhawk said:
Clear the system cache... I never tried it but was told that would clear it.
Click to expand...
Click to collapse
Thanks, I'll give it a try. How do I do a system cache clean?
sltwtr said:
Thanks, I'll give it a try. How do I do a system cache clean?
Click to expand...
Click to collapse
It's on the boot menu. Not sure for that device.
It can be a little tricky if you don't get the timing and button sequence right.
It would have been better to force power off the phone before it completed the download. Perhaps using ADB editing you could kill it. Not sure if disabling OTA updates now would stop it but that be worth a shot.
If it updates you may be able to flash it back to 11 if it doesn't upgrade the boot loader too.
You may want to see if someone has a better, more detailed plan. I always keep OTA updates package blocked. Package Disabler can be used to kill updates, that might be the easiest way.
OTA updates...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
blackhawk said:
It's on the boot menu. Not sure for that device.
It can be a little tricky if you don't get the timing and button sequence right.
It would have been better to force power off the phone before it completed the download. Perhaps using ADB editing you could kill it. Not sure if disabling OTA updates now would stop it but that be worth a shot.
If it updates you may be able to flash it back to 11 if it doesn't upgrade the boot loader too.
You may want to see if someone has a better, more detailed plan. I always keep OTA updates package blocked. Package Disabler can be used to kill updates, that might be the easiest way.
OTA updates...
View attachment 5567769
Click to expand...
Click to collapse
Thank you vm. Ckearing cache didnt work, theres still a scheduled update. I thought to try and reset the tablet (its still running android 11) and not to connect it to the wifi before ill disable the auto software updates in the settings. You think it might work or is it possible that after ill reset it, it will upgrade itself?
Btw, are there any drawbacks if ill flash it back to android 11? (security-wise, warranty-wise etc')
sltwtr said:
Thank you vm. Ckearing cache didnt work, theres still a scheduled update. I thought to try and reset the tablet (its still running android 11) and not to connect it to the wifi before ill disable the auto software updates in the settings. You think it might work or is it possible that after ill reset it, it will upgrade itself?
Btw, are there any drawbacks if ill flash it back to android 11? (security-wise, warranty-wise etc')
Click to expand...
Click to collapse
Sorry that didn't work.
Try disabling the update app itself.
You can roll back to 11 as long as it doesn't update the bootloader to a new version.
No warranty implications unless you root it.
Security isn't an issue. I'm running on Pie.
blackhawk said:
Sorry that didn't work.
Try disabling the update app itself.
You can roll back to 11 as long as it doesn't update the bootloader to a new version.
No warranty implications unless you root it.
Security isn't an issue. I'm running on Pie.
Click to expand...
Click to collapse
What do you mean by disabling the app itself? What app?
How can i tell if it uploaded the bootloader?
Will i still have all the samsung features and apps?
Can you refer me to a reliable guide for downgrading?
Sorry for all the questions, thank you
sltwtr said:
What do you mean by disabling the app itself? What app?
How can i tell if it uploaded the bootloader?
Will i still have all the samsung features and apps?
Can you refer me to a reliable guide for downgrading?
Sorry for all the questions, thank you
Click to expand...
Click to collapse
My previous post shows the app in it com.wys... whatever. Install package disabler and see if that can kill the install. It probably can.
If you end up on 12... deal with that then.
I recommend you do everything you can to keep it from installing... tick-tock Mr. Wick, no time to dilly dally.
blackhawk said:
My previous post shows the app in it com.wys... whatever. Install package disabler and see if that can kill the install. It probably can.
If you end up on 12... deal with that then.
I recommend you do everything you can to keep it from installing... tick-tock Mr. Wick, no time to dilly dally.
Click to expand...
Click to collapse
I ended up doing a factory reset. I didn't connect it to wifi at first and disabled auto update in the setting. So far it seems to work. Thank you
sltwtr said:
I ended up doing a factory reset. I didn't connect it to wifi at first and disabled auto update in the setting. So far it seems to work. Thank you
Click to expand...
Click to collapse
You're welcome.
Yay. Glad you were about to kill it.
Thank you for that information about the cache fix being invalid.