Database Info

Not able to update Verizon HTC ONE M8 to Android 4.4.3

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:

LG G3 Lollipop (D85010f)

Hello Respected Members,
I've searched a lot about my issue of g3 but can't find the solution or right answer. So I've an AT&T LG G3 which is great no doubt but I saw on the official site of AT&T that they've released the lollipop update for LG G3 on February but when I checked update through mobile it say's I've latest version of software which is 4.4.2. Software information is below
Android version : 4.4.2
Baseband version : MPSS.DI.2.0.1.c1.13.00009-M8974AAAAANPZM-1
Kernel version : 3.4.0
Build number : KVT49L.D85010f
Software version : D85010f
One Thing More, I've zero info about rom, cutrom rom, bootloader,etc
so I really appreciate if any one help me with this that is my phone have any root access or lollipop hasn't arrived for my phone yet?? I saw there is no SU here in my phone not in hidden applications also.
Please help me with this as all people around the world has solved their queries about their phones here....>
THank You!!

Where'd you get your phone? And do you have an AT&T SIM in your AT&T LG G3? Are you in the U.S.?

mudassar_ali said:
Hello Respected Members,
I've searched a lot about my issue of g3 but can't find the solution or right answer. So I've an AT&T LG G3 which is great no doubt but I saw on the official site of AT&T that they've released the lollipop update for LG G3 on February but when I checked update through mobile it say's I've latest version of software which is 4.4.2. Software information is below
Android version : 4.4.2
Baseband version : MPSS.DI.2.0.1.c1.13.00009-M8974AAAAANPZM-1
Kernel version : 3.4.0
Build number : KVT49L.D85010f
Software version : D85010f
One Thing More, I've zero info about rom, cutrom rom, bootloader,etc
so I really appreciate if any one help me with this that is my phone have any root access or lollipop hasn't arrived for my phone yet?? I saw there is no SU here in my phone not in hidden applications also.
Please help me with this as all people around the world has solved their queries about their phones here....>
THank You!!
Click to expand...
Click to collapse
Before you muck about with your phone, go here and read up. You do need some basic info so you have less chance of surprising yourself if something goes wrong. It has excellent info.
http://forum.xda-developers.com/att-lg-g3/help/frequently-questions-att-lg-g3-d850-t2958216
Following that, fundamentally, I'd do a clean install. You will lose your phones data, unless you save via Titanium, or the like. You can get the LP files, et al, from here:
http://forum.xda-developers.com/att-lg-g3/development/rom-20f-stock-rom-debloated-t3059610
1. unlock the phone via PC/ADB, then adb flash TWRP.
2. reboot phone, copy following files to phones external SD card (hope you have one)
modem
ROM
SuperSu
TWRP (already done but I do it anyway)
3. reboot to recovery and select the 4 files above from the install menu. I use the order above and works perfectly. Slide to install. Reboot into your system after the install. The initial install is very quick, after you reboot your phone to system, it will take some time to fully finish the install, 10 minutes or so.
4. Done. You will not have a direct menu to enter recovery after that, but get "Quick Boot" from PS, and that solves that.
This is how I've been doing LP, and no issues. I tried a dirty install, and had the same functionality as a clean install, except the dirty install had an Antutu of 23K. Previous I had an Antutu of 35-36K on KK. With a clean install on LP I have an about 40K.
.

HI, Did you upgrade to android 5.0 at the end as I'm stuck in the same situation?

Confused while trying to update my phone

Hello everyone,
I have bought a used Samsung Galaxy S8+ from China. I have been using it for a few days and i havent noticed anything odd. I don't know the phones origin or for how long has it been used before I got it.
It is running on Android 7.0 (Nougat). Since this is an older version of android I've been thinking to update it to Android 8.0 (Oreo). But I know that the phone doesn't have the originl ROM installed on it since I am not able to update it from the settings app and I also noticed that Knox was tripped in Odin mode.
This is the part which confuses me: if i enter Odin download mode there is a section which tells you your model number, and for me it says SM-G955N but if I look at the back of the phone or in the settings app it says SM-G955FD.
I was planning to download custom ROM and just simply install it via Odin app on my pc.
I'm just worried that I don't mess up something on my phone since the model numbers don't match up. How do I install any software update from this point and does the missmatching model number influence it?
I would very much appreciate anyones help, thanks.

Any way to downgrade from Nougat to MM without losing FP Sensor,Haptic Feedack&Camera

Any way to downgrade from Nougat to MM without losing FP Sensor,Haptic Feedack&Camera
I recently purchased a new S7 not realizing that it was equipped with a Nougat OS. I would like to restore my current phone to the new one, but my current phone runs on MarshMallow. After restoring the backup, my new phone has no haptic feedback, no fingerprint sensor with "an error has occurred with the fingerprint sensor. if this message appears repeatedly, restart your phone" message and the Camera doesn't work.
I'm sure it has something to do with bootloader N using MM. Even restoring Stock Marshmallow firmware (Including BL) on the new phone removes these functions. Does anyone have any ideas on how I can get these to operate?
My current phone has
Bootloader Version: G930W8OYA2APK3 (MM)
Baseband and PDA Version: G930W8OYA2API1 (MM)
When I restore my old phone to the new one, it ends up with
Bootloader Version: G930W8OYA2BQK4 (N)
Baseband and PDA Version: G930W8OYA2API1 (MM)
EDIT: Just tried the Nougat firmware with MM Bootloader. All of the functionality is present.
Bootloader Version: G930W8OYA2API1 (MM)
PDA Version: G930W8OYA2BQK4 (N)
Just restored old backup with MM bootloader (Boot, Data, System only).
No Fingerprint Sensor or Camera.
BTW, ignore the HAPTIC FEEDBACK portion of this post. I believe it is working.
Any help with this matter would be greatly appreciated.

Not possible to downgrade since the bootloader block you from flashing lower version of that. You may try to flash without BL, but your phone will be malfunction

Thank you for your reply. I don't think I'll be able to get the fingerprint wizard to work but having a functional camera would be a necessity. From the System/Priv-App folder I copied the SamsungCamera5 (from MM) and the SamsungCamera6 (from N) onto an SD Card. I guess I can try to play around with them to see if either will work, but I don't think they will since my restored backup should already have SamsungCamera5 and the SamsungCamera6 apk probably isn't compatible with MM. Kinda disappointing that I'll have to continue to use my old phone with a broken screen instead of the brand new one I purchased.

Sleaze0 said:
Thank you for your reply. I don't think I'll be able to get the fingerprint wizard to work but having a functional camera would be a necessity. From the System/Priv-App folder I copied the SamsungCamera5 (from MM) and the SamsungCamera6 (from N) onto an SD Card. I guess I can try to play around with them to see if either will work, but I don't think they will since my restored backup should already have SamsungCamera5 and the SamsungCamera6 apk probably isn't compatible with MM. Kinda disappointing that I'll have to continue to use my old phone with a broken screen instead of the brand new one I purchased.
Click to expand...
Click to collapse
do not flash AP from a firmware set made prior to the bootloader youre on, it will more than malfunction, itll probably brick
i went back and read all the tl : dr stuff and saw that you seem to have got it working, oddly enough. The camera issue is likely the kernel

Thanks for the info on the thanks button. I've just about given up trying to get Marshmallow to work properly on this phone. Looks like it'll take weeks to configure my new Nougat phone to be similar to the three years of tweaks I've made to my old MM one. Oh well, first world problems I guess.

As others have pointed out, you can't use Odin to successfully flash a ROM with a bootloader that is earlier (in version) than the bootloader you have installed. The "gatekeeper" is Odin, however, not the bootloader.
Though I haven't tried it, it is my understanding that there is a way around this. Install TWRP, and use it to install a custom ROM which uses the version of bootloader that you want/need. Once the bootloader has been rolled back, you can use Odin to reinstall Nougat (or whatever). I don't know whether this might require a particular build of Odin, but I doubt it

Droiderat said:
As others have pointed out, you can't use Odin to successfully flash a ROM with a bootloader that is earlier (in version) than the bootloader you have installed. The "gatekeeper" is Odin, however, not the bootloader.
Though I haven't tried it, it is my understanding that there is a way around this. Install TWRP, and use it to install a custom ROM which uses the version of bootloader that you want/need. Once the bootloader has been rolled back, you can use Odin to reinstall Nougat (or whatever). I don't know whether this might require a particular build of Odin, but I doubt it
Click to expand...
Click to collapse
i cant even begin to imagine how/why that would work. the bootloader doesnt really care what ROM you install, its the other way around. The ROM being installed has to be compatible with the bootloader. So, installing a ROM wouldnt really do anything to the bootloader and therefore wouldnt be able to bypass the lock in knox.

The procedure I outlined apparently works where the custom ROM includes a related bootloader. Thus, when it is installed via TWRP, it replaces both the existing ROM and the bootloader. I know that TWRP can be used to install a bootloader, as I have done it (on a SM-930F). And if the gatekeeper is Odin and not the bootloader itself, then this could work.
As I stated, I haven't tried this, nor have I extensively researched it. I've only read about it, and am passing it along as a possible solution.

This post can be closed since the phone was deemed Lost or Stolen by the carrier, therefore they couldn't unlock it for me to use my SIM card. I've since returned the phone. At least I learned a few lessons for my next one. Mainly, back up the phone when you first get it. Thanks again for all of the feedback.

Question Unroot device

So, I rooted my device couple of month ago.
Long story short I had a problem and don t have magisk on my phone anymore
I want to unroot my device. But what i have read is that i need the original firmware with the boot.img that came with my phone when I rooted it.
Ihave search my device and the magisk folder got deleted and so I don t have the backup of boot.img that magisk did for me.
If I download the firmware with frija (the baseband is that the version number) can I restore the phone to his original state ?
And is there a way to have the original bootloader back and enable knox again ?
Thanks

When i input the baseband in frija the software let me download the latest version of the software on android 12.
Is it possible to find the original version of the software that came it was android 11

Everything is included in the firmware for reverting back, although not necessarily needed, i would advise for a reset as well. You can do that in one go by flashing CSC instead of HOME_CSC.
About KNOX, forget it, you're done. I haven't rooted a Samsung phone since the 2019, and don't see any reason to anymore, but if you do, i don't see a reason to revert back either since KNOX is out of the question.