Related
Hello!
I have a Verizon HTC ONE M8 that no matter what it won't download the new update. I've bought 3 of them (identical) 1 month ago from Ebay. One of them was able to receive the update. On the other two i keep receiving the following message: "We were not able to download this update. To retry, go to Settings > Software update. "
My device is S-off (after a lot of effort). I've tried to get rid of all the bloatware and many more by flashing a new ROM. I have tried flashing ViperROM, ARHD, Clean ROM using TWRP Recovery, without any success. All of my attempts got stuck at the booting screen for more than 30 minutes without any success of booting into the OS. Clean ROM even refused to flash properly. Keep in mind that all the ROMs that I've flashed were based on 4.4.2 firmware, the one that my phone came with, not 4.4.3. I've searched on this forum for a flashable 4.4.3 OTA update, but no success either. What's to be done !?!? All my attempts of installing a new OS failed. Please HELP!
P.S: I'm a newbie when it comes to all of this stuff. First time doing S-off/ installing custom ROMs.
hgpt said:
Hello!
I have a Verizon HTC ONE M8 that no matter what it won't download the new update. I've bought 3 of them (identical) 1 month ago from Ebay. One of them was able to receive the update. On the other two i keep receiving the following message: "We were not able to download this update. To retry, go to Settings > Software update. "
My device is S-off (after a lot of effort). I've tried to get rid of all the bloatware and many more by flashing a new ROM. I have tried flashing ViperROM, ARHD, Clean ROM using TWRP Recovery, without any success. All of my attempts got stuck at the booting screen for more than 30 minutes without any success of booting into the OS. Clean ROM even refused to flash properly. Keep in mind that all the ROMs that I've flashed were based on 4.4.2 firmware, the one that my phone came with, not 4.4.3. I've searched on this forum for a flashable 4.4.3 OTA update, but no success either. What's to be done !?!? All my attempts of installing a new OS failed. Please HELP!
P.S: I'm a newbie when it comes to all of this stuff. First time doing S-off/ installing custom ROMs.
Click to expand...
Click to collapse
You probably won't be able to take the OTA with a custom recovery, it has to be stock. Best bet is to flash the 4.4.3 firmware from the development section since you're s-off, then flash an already rooted stock 4.4.3 rom. It's been a while since I've done this stuff so if I mentioned some incorrect info, my apologies.
dynofrk666 said:
You probably won't be able to take the OTA with a custom recovery, it has to be stock. Best bet is to flash the 4.4.3 firmware from the development section since you're s-off, then flash an already rooted stock 4.4.3 rom. It's been a while since I've done this stuff so if I mentioned some incorrect info, my apologies.
Click to expand...
Click to collapse
I flashed back again the stock ROM and i keep receiving the same message over and over again. No TWRP recovery this time, just the red triangle. I guess my best bet is to try and flash the CleanROM ODEX 4.4.3 as mentinoned here: @branmuffin17
I'll come back with the results.
hgpt said:
I flashed back again the stock ROM and i keep receiving the same message over and over again. No TWRP recovery this time, just the red triangle. I guess my best bet is to try and flash the CleanROM ODEX 4.4.3 as mentinoned here: @branmuffin17
I'll come back with the results.
Click to expand...
Click to collapse
If you are on the old firmware you need to update firmware separately.
And btw, if you freeze just one system app that can cause a Vzw ota to fail.
Question.....Is the phone active on your account? I also had one in the drawer and got the same error till I switched it to the active device on my account.
It honestly sounds like there is something preventing the ota to even download, if that's the case use dottat's ruu to return to a clean slate, if it still won't download the OTA then I would be willing to bet money that they are defective or not genuine Verizon M8s And if I were to guess it's more of the latter that would be the only valid reason every Rom you've tried fails no matter what.
sent from space
runandhide05 said:
It honestly sounds like there is something preventing the ota to even download, if that's the case use dottat's ruu to return to a clean slate, if it still won't download the OTA then I would be willing to bet money that they are defective or not genuine Verizon M8s And if I were to guess it's more of the latter that would be the only valid reason every Rom you've tried fails no matter what.
sent from space
Click to expand...
Click to collapse
Based on what you said i went on some websites to check the IMEI/ESN of the device it seems to be OK. After that i went to the Verizon Wireless website to try an activate my phone and when it comes to "Enter your Device ID to check eligibility", I type in the IMEI and the following message apears: "The phone associated with the Device ID you entered is not compatible with the Verizon Wireless network." To me is strange because on the back of the phone it says Verizon 4G LTE. When it comes to the identity of the phone it is a HTC6525LVW. The phone is GSM Unlocked (I use my phone in Europe so i needed it to be GSM unlocked). More strange it is to me that i don't receive the same message when i type in the IMEI of the others Verizon GSM unlocked HTC's ONE M8 that i bought along with this one.
I guess my only chance is to flash the new firmware @here[and after that flash the Deoxed 4.4.3 Stock Clean ROM @here. If it's not going to work i really don't know what's else it's to be done.
hgpt said:
Based on what you said i went on some websites to check the IMEI/ESN of the device it seems to be OK. After that i went to the Verizon Wireless website to try an activate my phone and when it comes to "Enter your Device ID to check eligibility", I type in the IMEI and the following message apears: "The phone associated with the Device ID you entered is not compatible with the Verizon Wireless network." To me is strange because on the back of the phone it says Verizon 4G LTE. When it comes to the identity of the phone it is a HTC6525LVW. The phone is GSM Unlocked (I use my phone in Europe so i needed it to be GSM unlocked). More strange it is to me that i don't receive the same message when i type in the IMEI of the others Verizon GSM unlocked HTC's ONE M8 that i bought along with this one.
I guess my only chance is to flash the new firmware @here[and after that flash the Deoxed 4.4.3 Stock Clean ROM @here. If it's not going to work i really don't know what's else it's to be done.
Click to expand...
Click to collapse
The message from the vzw site tells me something is not right.
Google goophone or knock off gs4, the goophone also has an m8 now too... Even with all the branding and everything. And I've seen some gs4s that run what appears to be TouchWiz cloned to a T.
I'd try calling vzw and talk to a rep and it's possible that they could give you more info other than just what the site said.
sent from space
So I did what I've said:
1. Installed firmware provided here @Tigerstown
2. Installed the Odex Stock Rooted ROM proivede here: @scrosler
I am pleased to announce you that everything is fully functional now
Phone is showing:
Android Version: 4.4.3
Software number: CleanROM 2.0.0 (after flashing it from @here)
Baseband version: 1.09.20.0702
Bulid number: 2.21.605.2 CL362279 release-keys
After managing to flash the 4.4.3 version of Android all went up without any problem. Tried to ARHD but it's still not booting. After that installed ViperROM which went up all, but to me it is not the pure HTC Sense 6 experience i was looking about and all that customization is to much for me, so i flashed CleanROM 2.0.0 and here I am. Everything is as it should be: no bloatware, pure HTC Sense 6, optimized performance... and above all the mobile hotspot is now fully functional, not to mention the EXT SAVER.
As a conclusion, to all that guys that are not able to update to the 4.4.3 version via the OTA updates provided by Verizon do what I did above (steps 1 and 2).
ATTENTION: Your device needs to be S-Off and bootloader unlocked + custom recovery!!!
Another thing worth to be mentioned: it would be great if the admins could flag this thread, cause I've seen so many users on different forums that are not able to update via the OTAs.
In the end i would like to thank to all the devs out there for their work and to the users for their support. Cheers!:highfive:
Hi all,
I'm having a nightmare of a time with my Galaxy S7... For some unknown reason I decided to root my phone about 2 months ago using CF Auto Root.. worked great.. This morning, was having bad lag issues, so I restarted the phone.. as soon as the Samsung logo came up, I got a red message at the top of the screen saying "Custom Binary locked by FRP".. kind of freaked out and booted the phone into Recovery mode.. wiped Cache and wiped phone (to go back to factory setting I guess).. restarted... since then, I had no boot.. it did loop for a while as I was trying to charge the phone.. but that's it.
Now, the only way the phone will power on is if I plug it into my computer in Download Mode. I am trying to flash the ROM, custom or stock, but Odin fails almost as soon as it starts the sboot.bin and the phone screen shows "SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 6, BINARY: 1".. Also, When I try to power on the phone, it HAS to be plugged in to my computer or charger cable and it just loops with a message at the top of the screen.
I can't do anything with this phone and cant find any solutions online... please help! :crying:
PM me for images of all screens please
I had the some problem while playing with my handset I switched off OEM unlock for some reason under developer option..
Next time i reset my handset it stuck on that warning
You need to download combination file, flash it with odin, then unlock developer mode, toggle OEM unlock, than flash back your current firmware, or if you have full twrp back up restore it
JayMor81 said:
Hi all,
I'm having a nightmare of a time with my Galaxy S7... For some unknown reason I decided to root my phone about 2 months ago using CF Auto Root.. worked great.. This morning, was having bad lag issues, so I restarted the phone.. as soon as the Samsung logo came up, I got a red message at the top of the screen saying "Custom Binary locked by FRP".. kind of freaked out and booted the phone into Recovery mode.. wiped Cache and wiped phone (to go back to factory setting I guess).. restarted... since then, I had no boot.. it did loop for a while as I was trying to charge the phone.. but that's it.
Now, the only way the phone will power on is if I plug it into my computer in Download Mode. I am trying to flash the ROM, custom or stock, but Odin fails almost as soon as it starts the sboot.bin and the phone screen shows "SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 6, BINARY: 1".. Also, When I try to power on the phone, it HAS to be plugged in to my computer or charger cable and it just loops with a message at the top of the screen.
I can't do anything with this phone and cant find any solutions online... please help! :crying:
PM me for images of all screens please
Click to expand...
Click to collapse
This problem appears on the forum over and over. Its a direct result of not understanding what type of S7 you have and what you need to do before modification.
The error you have in Odin means the firmware you are trying to flash is older than the bootloader file on your device. You can never downgrade a bootloader only upgrade.
In your case you need to flash a firmware version 6 or above for your device. So if you have a branded T Mobile for example you will need to download and flash T Mobile firmware version 6 or above. The firmware must also be for your region where you live.
The FRP lock is because you didn't sign out of, or remove the Google account on the device before modification. Its a security feature. It will still appear after you've flashed firmware but as long as you know the email and password the phone will start fine.
cooltt said:
This problem appears on the forum over and over. Its a direct result of not understanding what type of S7 you have and what you need to do before modification.
The error you have in Odin means the firmware you are trying to flash is older than the bootloader file on your device. You can never downgrade a bootloader only upgrade.
In your case you need to flash a firmware version 6 or above for your device. So if you have a branded T Mobile for example you will need to download and flash T Mobile firmware version 6 or above. The firmware must also be for your region where you live.
The FRP lock is because you didn't sign out of, or remove the Google account on the device before modification. Its a security feature. It will still appear after you've flashed firmware but as long as you know the email and password the phone will start fine.
Click to expand...
Click to collapse
Dammit.. I tried to put as much detail as possible in there lol.. obviously I forgot some.. My mistake the Galaxy s7 that I am using is a Rogers Mobile (Canada) SM-G930W8. As for not signing out before modification, omfg, that makes perfect sense.. didn't even think of doing that before rooting.. I appreciate the help!! I will give this a go and see what outcome I get.. Thanks!
[/COLOR]That was nice of you to respond so helpfully, despite you having seen the scenario posted over and over.
cooltt said:
This problem appears on the forum over and over. Its a direct result of not understanding what type of S7 you have and what you need to do before modification.
The error you have in Odin means the firmware you are trying to flash is older than the bootloader file on your device. You can never downgrade a bootloader only upgrade.
In your case you need to flash a firmware version 6 or above for your device. So if you have a branded T Mobile for example you will need to download and flash T Mobile firmware version 6 or above. The firmware must also be for your region where you live.
The FRP lock is because you didn't sign out of, or remove the Google account on the device before modification. Its a security feature. It will still appear after you've flashed firmware but as long as you know the email and password the phone will start fine.
Click to expand...
Click to collapse
Can't make or receive calls
Please I need help my I rooted my S7 (flat) flashed the original OS with odin Installed Twrp flashed Andriod 9 and since then I can't make or receive calls wifi seems fine. Someone please come to my rescue:crying:
Cesilina said:
Please I need help my I rooted my S7 (flat) flashed the original OS with odin Installed Twrp flashed Andriod 9 and since then I can't make or receive calls wifi seems fine. Someone please come to my rescue:crying:
Click to expand...
Click to collapse
The S7 didn't receive Android 9 so the ROM is a custom one. Any issues with custom ROM's should be asked on the ROM thread itself where you got the ROM from. It's quite normal for custom ROM'S to have bugs.
You can try flashing the ROM (Android 9 Pie) again to see if it works. If not there are several different A9 ROM's to choose from.
cooltt said:
The S7 didn't receive Android 9 so the ROM is a custom one. Any issues with custom ROM's should be asked on the ROM thread itself where you got the ROM from. It's quite normal for custom ROM'S to have bugs.
You can try flashing the ROM (Android 9 Pie) again to see if it works. If not there are several different A9 ROM's to choose from.
Click to expand...
Click to collapse
Thank you for reply. I have tried atleast 4 different custom ROMs but to avail
Cesilina said:
Thank you for reply. I have tried atleast 4 different custom ROMs but to avail
Click to expand...
Click to collapse
Do you still have an imei number listed in settings?
Can't make or receive calls
cooltt said:
Do you still have an imei number listed in settings?
Click to expand...
Click to collapse
Yes please I still have an IMEI number
Greetings. After trying Derpfest on my Redmi Note 7 Pro, I decided to switch back to MiUI. I wiped out the entire Custom ROM, then installed Indian version firmware, and then installed the latest MiUI ROM in recovery mode (I prefer Orange Fox). After that, I wanted to relock my bootloader so I got the latest MiUI 11 fastboot ROM and then used MiFlash and used the clean_all_and_lock option. My device relocked it's bootloader, however, it turned out that several things like sensors or Find Device service were not working correctly. It also showed a message "Find device storage corrupted, your device is now unsafe". Looking for solutions, I ended up unlocking the bootloader again, getting back OFox, and installing the persist.img file which I extracted from my fastboot ROM. This fixed the issue with the sensors. But now, I still can't get access to services like Find Device (both from Xiaomi and Google). If I have to avoid the 'Find Device Storage corrupted' error, I have to unlock bootloader. If I have to lock bootloader, I get the error message. What am I supposed to do?
I also have tried older Fastboot ROMs, although they were all MiUI 11. Should I try fastbooting into a MiUI 10 ROM and then get OTA to do everything else? If this is the case, which specific version of MiUI 10 ROM should I flash? I can't remember which version my phone came with. My model number M1901F7S. And also, I've never used Magisk. I didn't really care if I wanted to root or not. Derpfest passed Safetynet pretty nicely. But now I do not wish to root. I don't want Magisk or anything else, I want to secure the phone just as it was before.
EDIT : Turns out that Find Device (from both Google and Xiaomi) are actually working, just in a less effective scale than what I previously used to have (before getting the custom ROM). But yet, can I bring my phone back to the locked bootloader state? I want to secure it completely, just like how it was when it came out of the box. I also cannot install apps like Netflix. I would really like to know how to relock my bootloader.
EDIT 2: I've fixed it. Indeed, I had to flash a stock MiUI 10 ROM. Version 10.0.2 and whatever number ahead worked for me and gave me no problems, and then I simply updated to MiUI 11 using OTA Updates.
However, I do not recommend using MiFlash tool, and instead recommend pasting the ROM files into your platform_tools folder and then running flash_all_lock/flash_all. MiFlash may sometimes glitch and cause problems.
Hello Android-Wizzards,
i am stuck in a Bootloop to stock recovery mode since i tried to downgrade my mi note 10 pro from MIUI 12 V12.1.4.0.RFDEUXM to MIUI 12 V12.1.3.0.RFDEUXM via the update app .
After the OTA update to 12.1.4. i could not make any calls anymore so i searched for a way to downgrade to 12.1.3, where the problem was not present. I did it with the internal update app and followed this instruction: https://www.world-today-news.com/th...evert-your-xiaomi-a-buggy-update-xiaomi-news/
Sadly i didnt make a backup before anf after the rom finished installing it only boots to stock recovery anymore. If i try to connect the device via "Connect with MIAssistant" it does not work.
I searched the forums but i cant find a way to install MIUI 12 V12.1.4.0.RFDEUXM again.
The tutorials mention that if i want to recover my phone i have to use MIflash or fastboot flash which both need a unlocked bootloader according to the tutorials.
Sadly i did NOT unlock the bootloader when the phone was working normal and i dont see a method to umlock the bootloader an a bricked / bottloped mi note 10 pro.
Its bad enough that cause i didnt make a backup befor i tried to downgrad i must assume that all my pbhotos i took this year with my note 10 pro are lost forever, Mi cloud backup is full since last year and i didnt bother to pay for more space, another bad decicion in hindsight but is there a way i can restore my phone?
Please help, i dunno what else to do to get my phone booting up agian.
Had a simmilar problem with an older mi phone of mine a few years ago and then it wasnt a problem cause i could easyli flash it with MIflash, but dunno since when you have to unlock bootloader first and since i didnt know that my phone has a locked bootloader, never minded to unlock it.
Nautzzz said:
Hello Android-Wizzards,
i am stuck in a Bootloop to stock recovery mode since i tried to downgrade my mi note 10 pro from MIUI 12 V12.1.4.0.RFDEUXM to MIUI 12 V12.1.3.0.RFDEUXM via the update app .
After the OTA update to 12.1.4. i could not make any calls anymore so i searched for a way to downgrade to 12.1.3, where the problem was not present. I did it with the internal update app and followed this instruction: https://www.world-today-news.com/th...evert-your-xiaomi-a-buggy-update-xiaomi-news/
Sadly i didnt make a backup before anf after the rom finished installing it only boots to stock recovery anymore. If i try to connect the device via "Connect with MIAssistant" it does not work.
I searched the forums but i cant find a way to install MIUI 12 V12.1.4.0.RFDEUXM again.
The tutorials mention that if i want to recover my phone i have to use MIflash or fastboot flash which both need a unlocked bootloader according to the tutorials.
Sadly i did NOT unlock the bootloader when the phone was working normal and i dont see a method to umlock the bootloader an a bricked / bottloped mi note 10 pro.
Its bad enough that cause i didnt make a backup befor i tried to downgrad i must assume that all my pbhotos i took this year with my note 10 pro are lost forever, Mi cloud backup is full since last year and i didnt bother to pay for more space, another bad decicion in hindsight but is there a way i can restore my phone?
Please help, i dunno what else to do to get my phone booting up agian.
Had a simmilar problem with an older mi phone of mine a few years ago and then it wasnt a problem cause i could easyli flash it with MIflash, but dunno since when you have to unlock bootloader first and since i didnt know that my phone has a locked bootloader, never minded to unlock it.
Click to expand...
Click to collapse
Did you try wipe data with the recovery?
or try this old method.
Did you try to flash the rom in recovery again?
I have a Russian (thanks Amazon !!) Redmi 9a 32Gb/2gb. It is currently running latest 12.0.x ROM version, but i would like to upgrade it to 12.5.
I see on xiaomi ROM site there is currently a 12.5.x version for Russian version, but the OTA never arrived and if i download the recovery zip file and install it manually, it fails verification and stops.
Is there a way to install 12.5 without unlocking the bootloader ?
Is 12.5 supported on this specific redmi 9a ?
thanks !
mmm... spflashtool might work, but Ive only ever used it on a bircked device to unbrick it, never on a functional device to just change the ROM version, but if you really wanna do it without unlocking bootloader thats your best choice.
I will say anyway, its probably safer to unlock bootloader install recovery and install the rom from there, its your call tho.
Heres how I unbricked my device
[GUIDE] Unbrick hard-bricked device
Condition Phone does not turns on Phone not detected via USB Phone handshake/memory hash failed Requirements Unplug battery Download MIUI 12.5.4.0.RCDMIXM Fastboot ROM Download Scatter File for 12.5.4.0.RCDMIXM Download SP Flash Tool Download...
forum.xda-developers.com
here are some useful files
REDMI 9A - Google Drive
drive.google.com
Thanks
Right now I cannot unlock the bootloader, maybe in the next months I might try (I want to wait for the warranty to expire). My concern is that my version of Redmi 9A with just 2G of Ram is actually not compatible with MIUI 12.5. The 12.5 rom is actually available, but OTA will leave me in the 12.0 branch and verification fails if I try to install the ROM manually. I would not want to brick it by installing an unsupported ROM.
My phone model is M2006C3LG and the ROM I have right now says I have 1.8Gb of available RAM, I don't think you have a different device from mine.
Im a total n00b so I may be wrong about this next thing, but, I think the only difference is what version of MIUI they were sold with since the hardware doesn't allow downgrades further than the stock ROM that came with the device.
There is always antirollback after MIUI 10, but I think its even further locked for the original stock ROM that came to the device, but yeah, this is all my own speculation due to a bricking incident I faced.
The model number is the same, but the 9A was available with different sizes of RAM 2 or 3 or 4 Gb. Mine is the low end 32/2 which is the model still on sale today. If you still have 1.8 Gb of free RAM you very likely has the 3 or 4 GB model.
Maybe you are right, the OTA allows only for updates within the same MIUi version; I saw several guides on-line and i think i will try the miflash tool and switch to the global version. I have to find a way to unlock bootloader without Xiaomi account (no way in hell I'm signing up for that) and without sim card (this phone is used as a smaller wi-fi only tablet). There are some tools for an offline unlock, I will try those first.
It is incredible how Xiaomi is making it complex just to update to a stable official ROM; given also how much bloatware is shovelled with the stock ROM, I'm not sure I will ever consider Xiaomi again.
enryfox said:
The model number is the same, but the 9A was available with different sizes of RAM 2 or 3 or 4 Gb. Mine is the low end 32/2 which is the model still on sale today. If you still have 1.8 Gb of free RAM you very likely has the 3 or 4 GB model.
Maybe you are right, the OTA allows only for updates within the same MIUi version; I saw several guides on-line and i think i will try the miflash tool and switch to the global version. I have to find a way to unlock bootloader without Xiaomi account (no way in hell I'm signing up for that) and without sim card (this phone is used as a smaller wi-fi only tablet). There are some tools for an offline unlock, I will try those first.
It is incredible how Xiaomi is making it complex just to update to a stable official ROM; given also how much bloatware is shovelled with the stock ROM, I'm not sure I will ever consider Xiaomi again.
Click to expand...
Click to collapse
In my opinion, DON'T UPGRADE. I upgraded it with recovery and fastboot and my phone got an message everytime when I boot it : dm verity corrupted and I will need to press power button again to work. Maybe i didn't did that correctly ( I have Global 12.0.20 32/2gb)
Rares6567 said:
In my opinion, DON'T UPGRADE. I upgraded it with recovery and fastboot and my phone got an message everytime when I boot it : dm verity corrupted and I will need to press power button again to work. Maybe i didn't did that correctly ( I have Global 12.0.20 32/2gb)
Click to expand...
Click to collapse
Thanks for the info. So you upgraded to latest 12.0 without moving to 12.5, any reason for not trying 12.5 ? The phone is currently barely usable with Android 10, maybe Android 11 is even heavier, but why not give it a try ?
I saw several youtube videos and guides and by using MI Flash with a Fastboot image (scattered tgz) it should be a total reflash of the phone.
enryfox said:
Thanks for the info. So you upgraded to latest 12.0 without moving to 12.5, any reason for not trying 12.5 ? The phone is currently barely usable with Android 10, maybe Android 11 is even heavier, but why not give it a try ?
I saw several youtube videos and guides and by using MI Flash with a Fastboot image (scattered tgz) it should be a total reflash of the phone.
Click to expand...
Click to collapse
Idk, android 11 may will use more resources but give it a try , good luck
The updates come over time so we must have patience
the_arxyn said:
The updates come over time so we must have patience
Click to expand...
Click to collapse
True but sometimes u won't get the update
Rares6567 said:
True but sometimes u won't get the update
Click to expand...
Click to collapse
in this situation flash the wanted version via recovery or fastboot
the_arxyn said:
in this situation flash the wanted version via recovery or fastboot
Click to expand...
Click to collapse
Yea.