Hi. I have a Note 5 that was factory reset and now Google play services stops working. Successfully flashed new stock rom to no avail. Tried adb sideload current Gapps with fastboot CMD line, however I get a failure for the whole file signature. Cannot log in with Google because the service keeps stopping. Any help is appreciated.
My apologies,
SN920-V running Stock MM 6.0.1
Christafer said:
My apologies,
SN920-V running Stock MM 6.0.1
Click to expand...
Click to collapse
Download the latest firmware update and flash it the correct way using odin on a Windows computer or Linux if you know how to do it. You don't need to even be side loading anything not Gapps nothing! All you need is the correct firmware update and odin to flash it.
Latest firmware here
https://www.androidfilehost.com/?fid=529141701856462360
I have already installed latest firmware with Odin. The issue I keep running into is the FRP has locked the phone. When I get to the setup, it tells me Google play services has stopped and will not let me enter the information to unlock. It then redirects me to wifi setup and the whole process starts again.
Christafer said:
I have already installed latest firmware with Odin. The issue I keep running into is the FRP has locked the phone. When I get to the setup, it tells me Google play services has stopped and will not let me enter the information to unlock. It then redirects me to wifi setup and the whole process starts again.
Click to expand...
Click to collapse
Then you'll have to look up the solution for the FRP.. The reason it did that is because you didn't enable Developer Options and then inside Developer Options you should have enabled oem unlock before trying to side load or updating to MM 6.
Related
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
URGENT HELP
On installing the update of 16.1 mb. The droid shows a error while installing after the reboot.
Nothing happens after that and the phone reboots
Right now it it running on 5.1.1
Same problem, LMY48B
I have the same problem, OTA update comes in a few times a day and never works, i simply get the message "Error". My update is 10.1 Mb. I am on build nr LMY48B and have Android version 5.1.1. When restarting using the power and volume button, the error message says "Empty". I tried Nexus Root Toolkit to update, no result.
Has anyone an idee to eather update or kill the updates all together?
Solution found !!Huraay!!
I just found a solution to this problem. You ll have to flash your nexus to stock (it is formatting not rooting)
Here are simple steps to it:
1. Enable Bootlegger
2. Turn on developer mode, enable USB debugging
3. Use a flash factory image (download it from any source)
Now you ll get 3 back to back OTA updates in settings, just install them and finally you ll get Marshmallow update of 403mb.
DONE.....
Cheers.
Contact if you still have a problem.
Thanks for sharing this. I tried to follow your instructions, using NEXUS Root Toolkit. At first i tried factory image 5.1.1, but this did not work , it just stopped. After that i tried to flash Hammerhead 6.0.0. Wich actually looked very promissing during the proces. After finishing reboot started, and it won't get out of reboot. I tried several times, up to 15 minutes. I also tried a factory reset, but it still keeps running the marsmellow startup grafic. Since i can't get into unlock mode, i do not have the opportunity to reflash the phone. Any ideas how to get out of reboot?
Hi,
We need to know more, what's actually failing. We could try and flash the update with TWRP, we'll get some output from there. Might be your radio or bootloader versions, for example.
And you using a toolkit, it doesn't help.
So, go learn some fastboot and some adb while you're at it, because you're going to need it. Guides to both are stickied everywhere around here.
Also, don't see the point on flashing a 5.1.1 factory image at this point, if the goal is to update to 6.0 (looking at the other user posting on this thread): just flash 6.0 factory image.
Sent from my Nexus 5 using Tapatalk
I have hear a S7 wich hangs on white samsung boot logo.
The device is stock, no root and no custom rom.
The problems started on a failed update, it started to hang during use.
I made a backup and then tried to reset it, sadly i came no further then this boot logo after it crashed again.
I decided to enter recovery mode, when entering recovery each time i get a blue install screen of an update and each times it fails with an error.
Then i did a wipe cache and rebooted, same result, it stops at boot logo
Then i did a wipe/format factory reset (from recovery) and reboot, here also it hangs on samsung logo
Also it reports the following:
fail to open recovery cause no such file or directory
I even let the phone boot for 8 hours on the logo, it gets really hot but it does not go pass the samsung boot logo
When booting and the phone is connected by USB to my laptop i get messages that android rom is prepared and 1 later it is installed, but that is it, no booting etc.
I then entered download mode and used ODIN, downloaded the latest stock rom and try to flash it.
But here also i get each try a FAILED on the boot, even when i do no enter BL i get a FAILED, so only AP it fails also.
I tried now about 5 different stock rom versions and they all fail.
Have really no idea how to fix this, as mentioned the phone is fully stock, so stock bootloader, stock rom etc.
Anyone any idea how to get this phone up and running again?
B3rt said:
I have hear a S7 wich hangs on white samsung boot logo.
The device is stock, no root and no custom rom.
The problems started on a failed update, it started to hang during use.
I made a backup and then tried to reset it, sadly i came no further then this boot logo after it crashed again.
I decided to enter recovery mode, when entering recovery each time i get a blue install screen of an update and each times it fails with an error.
Then i did a wipe cache and rebooted, same result, it stops at boot logo
Then i did a wipe/format factory reset (from recovery) and reboot, here also it hangs on samsung logo
Also it reports the following:
fail to open recovery cause no such file or directory
I even let the phone boot for 8 hours on the logo, it gets really hot but it does not go pass the samsung boot logo
When booting and the phone is connected by USB to my laptop i get messages that android rom is prepared and 1 later it is installed, but that is it, no booting etc.
I then entered download mode and used ODIN, downloaded the latest stock rom and try to flash it.
But here also i get each try a FAILED on the boot, even when i do no enter BL i get a FAILED, so only AP it fails also.
I tried now about 5 different stock rom versions and they all fail.
Have really no idea how to fix this, as mentioned the phone is fully stock, so stock bootloader, stock rom etc.
Anyone any idea how to get this phone up and running again?
Click to expand...
Click to collapse
What country are you in?
What network were you using?
What firmware was on your phone nougat or Oreo?
What firmware are you trying to flash?
What version of Odin are you using?
cooltt said:
What country are you in?
What network were you using?
What firmware was on your phone nougat or Oreo?
What firmware are you trying to flash?
What version of Odin are you using?
Click to expand...
Click to collapse
Living in The Netherlands
The phone is free, not network limited but was last used on T-Mobile
I am not 100% sure, i believe Android 8
i tried: DNL-G930FXXU3ESA3-20190131134911 and EUR-G930FXXS4ESAE-20190218105256 and DNL-G930FXXU2DRC1-20180402094302 and BTU-G930FXXU1DPLT-20170117160813 and G930FXXU1DQAN_G930FFTM1DQAD_FTM
Tried Odin3_v3.12.3 and Odin3-v3.13.1
B3rt said:
Living in The Netherlands
The phone is free, not network limited but was last used on T-Mobile
I am not 100% sure, i believe Android 8
i tried: DNL-G930FXXU3ESA3-20190131134911 and EUR-G930FXXS4ESAE-20190218105256 and DNL-G930FXXU2DRC1-20180402094302 and BTU-G930FXXU1DPLT-20170117160813 and G930FXXU1DQAN_G930FFTM1DQAD_FTM
Tried Odin3_v3.12.3 and Odin3-v3.13.1
Click to expand...
Click to collapse
Your trying to flash old versions of the firmware, once the boot loader is updated you can't go back.
This is the latest version of T Mobile for the Netherlands (TNL), it's always best to try the firmware you were on first [url]https://www.sammobile.com/firmwares/galaxy-s7/SM-G930F/TNL/download/G930FXXU3ESA3/255865/[/URL]
If that doesn't work this is the latest version of Unbranded BTU [url]https://www.sammobile.com/firmwares/galaxy-s7/SM-G930F/BTU/download/G930FXXS4ESAE/257466/[/URL]
Also use Odin 13. Put all files in correct slots and use CSC not HOME_CSC
As far as i could see these are all android 8 and 1 android 7 firmwares, so they are not that old.
Believe the latest one is from January this year, i know the last time the phone was updated was last October, after that all updates failed to install OTA
The link you gave me is exactly the same version i used only without the branding, so i already used the latest one.
I tried to be sure the download from the link you given but with those download speeds (15kb) it is almost impossible to download these firmware's, i am not gonna take a subscription to for 1 time fast downloading and also i do not want to risk that i paid for a fast download it fails again....
So if someone has a download link which i can use and try an other firmware please feel free to share it.
BTW i used the last Odin3-v3.13.1 version, i cannot find a newer one.
B3rt said:
As far as i could see these are all android 8 and 1 android 7 firmwares, so they are not that old.
Believe the latest one is from January this year, i know the last time the phone was updated was last October, after that all updates failed to install OTA
The link you gave me is exactly the same version i used only without the branding, so i already used the latest one.
I tried to be sure the download from the link you given but with those download speeds (15kb) it is almost impossible to download these firmware's, i am not gonna take a subscription to for 1 time fast downloading and also i do not want to risk that i paid for a fast download it fails again....
So if someone has a download link which i can use and try an other firmware please feel free to share it.
BTW i used the last Odin3-v3.13.1 version, i cannot find a newer one.
Click to expand...
Click to collapse
Ok well you can listen to me or not.
None of the firmwares you are using are for your device, PHN is Netherlands and the BTU you are using BTU-G930FXXU1DPLT is on a U1 boot loader, BTU is now on S4 which is 3 versions above U1.
The reason you only download from Sammobile or updato.com is because the firmware is correct, reliable and not full of virus/spyware. You can also download direct from Samsung severs with SamFirm Tool.
THREAD UPDATED 4/22/19
So I started having pre-flash errors, boot looping, and bricked modem problems from just flashing the modems so I decided to upload the entire stock firmware for Nougat and Marshmallow. It's the same process but you have to flash the entire firmware then flash TWRP to use custom roms. Just click the FLASH-ALL.bat in the Nougat or Marshmallow folder and it will flash the firmware automatically and reboot. If you have any issues please report it here. I also included TWRP and the stock boot images all in one package just go into the folder and hit FLASH-ALL.bat. Everything is automated no more looking for firmware and flashing manually.
Link 1:
https://mega.nz/#!K1o0XIDS!taCkfjVbWunmkEOFVrqUaFeTLEQZ-JQACqO2EpebnAo
Queston - just got done replacing the LCD-Digitizer and battery (Moto X Pure XT1575) with the iFixit repair kit and got it up and running again (cracked the display in an auto accident and never had time to fix it until now)- while it was out of service I've been using a Moto G Play XT1607 as a backup for the last couple years... anyway now that it's working again I ran the factory reset and checked the Android version and it's at 6.0 (MarshMellow?) ... am a novice and wondering if it should upgrade at least to 7.0 (Nougat) eventually, in a day or so(?) when it synchronizes somehow - or if i should go ahead and do it manually myself ... and/or if manually updated go straight to whatever the current version is (Oreo 8 or Pie 9) ... If this is the right place, I may need some pointers getting started in the right direction ... In comparison the Moto G Play is at 7.1.1 ...any suggestions?
jabberjaw007 said:
Queston - just got done replacing the LCD-Digitizer and battery (Moto X Pure XT1575) with the iFixit repair kit and got it up and running again (cracked the display in an auto accident and never had time to fix it until now)- while it was out of service I've been using a Moto G Play XT1607 as a backup for the last couple years... anyway now that it's working again I ran the factory reset and checked the Android version and it's at 6.0 (MarshMellow?) ... am a novice and wondering if it should upgrade at least to 7.0 (Nougat) eventually, in a day or so(?) when it synchronizes somehow - or if i should go ahead and do it manually myself ... and/or if manually updated go straight to whatever the current version is (Oreo 8 or Pie 9) ... If this is the right place, I may need some pointers getting started in the right direction ... In comparison the Moto G Play is at 7.1.1 ...any suggestions?
Click to expand...
Click to collapse
If you want stock Nougat go ahead and update to it but I had battery drain issues on the Nougat modem from personal experience. If you decide to update you can use this thread and downgrade to stock 6.0.
Hi, I downloaded the Nougat and tried the command "Flash-all.bat" while in windows 10 ( I have the device booted up in bootloader mode. ) nothing happens. The screen flashes something too quick for me to see what it is. I must be doing something dumb. Do I need to go into command mode to do this "Flash-all.bat" or can I do it in the windows screen ?
AndroidMilos said:
Hi, I downloaded the Nougat and tried the command "Flash-all.bat" while in windows 10 ( I have the device booted up in bootloader mode. ) nothing happens. The screen flashes something too quick for me to see what it is. I must be doing something dumb. Do I need to go into command mode to do this "Flash-all.bat" or can I do it in the windows screen ?
Click to expand...
Click to collapse
Okay if the terminal window flashes really fast and you can't read it that usually means it can't write to the phone. Either your bootloader isn't unlocked or your usb cable doesn't support data transfer. If that isn't the issue make sure you install Motorola device manager and the adb fastboot sdk drivers which can be found on XDA. More than likely you're getting a remote failure error I have this problem myself a lot on Windows 10.
Thank you for your reply. I will follow through with the info you gave me.
I no longer own this device so I will no longer participate in any Moto X Pure threads. FYI if you flash the Nougat firmware in this thread you have to OTA to the final update for Nougat ROMs to work.
Hi,
My Xiaomi 12 still hasn't gotten an new update and is stuck on MIUI 13.0.27.0( SLCEUXM) with security patch of oktober 2022.
I would like to get to the latest miui 14 and would like to know what is the best way to manually update this safely with a original ROM?
Should I do this incrementally start at MIUI 13.2.6.0 and then go to the next till I get to the latest or can I just update to the latest MIUI 14 directly?
Tnx
Gradually is the safest method.
Skipped the Beta stables.
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Thank you for the quick response.
I downloaded the MIUI downloader app are those ROMS good to?
I need to choose for a recovery ROM and then I can install it with the updater app right? So starting with version MIUI 13.2.6.0 would be the safest?
Downloaded from the site I told you, if the downloaded choice 'incremental update in yellow'.
Then go to OTA, 3 points at the top right, install update (if this does not appear, tap the Miui logo several times).
If it works, try OTA first.
NOSS8 said:
Downloaded from the site I told you, if the downloaded choice 'incremental update in yellow'.
Then go to OTA, 3 points at the top right, install update (if this does not appear, tap the Miui logo several times).
If it works, try OTA first.
Click to expand...
Click to collapse
You mean this one right?
It says it's only around 80mb is that correct?
When it's for a update from Android 12 to Android 13.
Error on my part, take the full rom.
it's the first A13 before yours.
If that doesn't work, download the incremental update of the current rom and then check if an update is offered.
NOSS8 said:
Error on my part, take the full rom.
it's the first A13 before yours.
If that doesn't work, download the incremental update of the current rom and then check if an update is offered.
Click to expand...
Click to collapse
So I tried to install the stable recovery ROM MIUI 13.2.6.0.TLCEUXM but it didn't work I keep getting this message "can't verify update can't flash this stable rom"
Then I tried a newer version recovery ROM MIUI 14.0.5.0.TLCEUXM but same message.
Also tried your suggestion to use the incremental update of the current ROM V13.0.27.0 but then I got the message "can't verify update can't downgrade ROM version"
Do you have any other ideas on how to fix this problem?
Try to change region (Belgium/Usa/change continent/country) and restart afterwards.
Then turn on WiFi and check for updates.
====================================
or unlock the bootloader and you can install any stock or custom rom.
NOSS8 said:
Try to change region (Belgium/Usa/change continent/country) and restart afterwards.
Then turn on WiFi and check for updates.
====================================
or unlock the bootloader and you can install any stock or custom rom.
Click to expand...
Click to collapse
Tried changing the continent/country and turn wifi back on after restart but no updates were found.
I really didn't want to try messing with the bootloader because of the warranty. I also read somewhere Google play services and bank apps not working when its unlocked.
Anything more I could try without unlocking?
Jappie3 said:
Tried changing the continent/country and turn wifi back on after restart but no updates were found.
I really didn't want to try messing with the bootloader because of the warranty. I also read somewhere Google play services and bank apps not working when its unlocked.
Anything more I could try without unlocking?
Click to expand...
Click to collapse
Nope, you can re-lock the bootloader after installing the stock rom.
No need with a Xiaomi Eu rom (certified play store, everything works).
NOSS8 said:
Error on my part, take the full rom.
it's the first A13 before yours.
If that doesn't work, download the incremental update of the current rom and then check if an update is offered.
Click to expand...
Click to collapse
Only thing I haven't tried, is using the incremental update of that version V13.2.6.0 because it was only 80 mb. If I try this update and it works will it then download the ROM information on it's own or something?
Jappie3 said:
Only thing I haven't tried, is using the incremental update of that version V13.2.6.0 because it was only 80 mb. If I try this update and it works will it then download the ROM information on it's own or something?
Click to expand...
Click to collapse
Nope,only solution unlock the bootloader.
Just to be sure I downloaded the 2 latest versions that I hadn't tried yet.
The recovery ROM of version MIUI 14.0.7.0.TLCEUXM and 14.0.8.0.TLCEUXM.
And they both seem to work
Since I'm still on Android 12 now and missed so many updates in-between these 2 latest versions. Would it be safe to install one of these?
Doesn't matter, it will work or not.
Note that if you have a bootloop afterwards, with the bootloader locked you will have to pay to recover your phone (this sometimes happens).
NOSS8 said:
Doesn't matter, it will work or not.
Note that if you have a bootloop afterwards, with the bootloader locked you will have to pay to recover your phone (this sometimes happens).
Click to expand...
Click to collapse
So it's not safe to just install one of these recovery versions manually with the updater?
Jappie3 said:
So it's not safe to just install one of these recovery versions manually with the updater?
Click to expand...
Click to collapse
Never at 100% with forcing.
EDIT:moreover, even regular updates via OTA can lead to a bootloop.
NOSS8 said:
Never at 100% with forcing.
EDIT:moreover, even regular updates via OTA can lead to a bootloop.
Click to expand...
Click to collapse
So it's just a risk of updating no matter what version I use. I never had a boot loop before.
Jappie3 said:
So it's just a risk of updating no matter what version I use. I never had a boot loop before.
Click to expand...
Click to collapse
Zero risk does not exist and this risk increases when you force the update by skipping versions.
NOSS8 said:
Zero risk does not exist and this risk increases when you force the update by skipping versions.
Click to expand...
Click to collapse
Oke, yeah I wanted to do it step by step till I got to the latest miui 14 and still don't get why the older versions don't work.
The only older version I could find that also worked was version V13.0.33.0.SLCEUXM but can't find much about that update.
Logical sequence