Related
So i just updated to V20 Europe Open following this tutorial and the update seemed to go through fine, rebooted, and new firmware installed. After finally setting up the phone as i like, i let it sit to synchronize all my contacts and what not. When i pushed the power button to wake up the phone, there were these random lines over the entire screen, look like blinds.
When i do a battery pull or reboot its back to normal, but everyime i let the phone sit for a couple of minutes and then wake it up, i get the same screen..
Ive attached two screen shots
Any ideas on how to fix this? Thanks.
I had the exact same problem, I didn't find any solution so I had to revert back to v10.
Which v20 did you install? The Portuguese one?
Mottz said:
I had the exact same problem, I didn't find any solution so I had to revert back to v10.
Which v20 did you install? The Portuguese one?
Click to expand...
Click to collapse
Use the same method that you use to roll back (LGFlash Tool) and install Euro_open V20A.
There is no difference between the euro and PT.
All needed files you can find them here:
http://forum.xda-developers.com/showpost.php?p=38838927&postcount=7
RuedasLocas said:
Use the same method that you use to roll back (LGFlash Tool) and install Euro_open V20A.
There is no difference between the euro and PT.
All needed files you can find them here:
http://forum.xda-developers.com/showpost.php?p=38838927&postcount=7
Click to expand...
Click to collapse
I tried the HK version as well, still having the issue. Do i just need to roll back to V10? Is it a software issue? How come very few people have it if all the versions are the same..?
faraband said:
I tried the HK version as well, still having the issue. Do i just need to roll back to V10? Is it a software issue? How come very few people have it if all the versions are the same..?
Click to expand...
Click to collapse
Might just be a bad flash.
By flashing with LGFlash Tool you don't need to roll back.
Just make sure that you have official firmware, don't use leaked.
To be a hardware problem, you should have it in ICS too...
RuedasLocas said:
Might just be a bad flash.
By flashing with LGFlash Tool you don't need to roll back.
Just make sure that you have official firmware, don't use leaked.
To be a hardware problem, you should have it in ICS too...
Click to expand...
Click to collapse
I tried 3 different routes to get V20A Euro installed, all the installs were successful but the screen issue is still there:
1. LG Flash Tool
2. KDZ_FW_UPD
3. Using LGKDZ hack and LG PC Suite
All of these successfully got V20A installed, but none solved the lines on the screen. I made sure to wipe before and after each install..
Any other ideas?
Perhaps screen is faulty ?
leolipop said:
Perhaps screen is faulty ?
Click to expand...
Click to collapse
I had no issues when on V10H, and nothing happened to the phone during the upgrade, just remained on my desk. When i revert back to V10H i have no issues also. I tried LGFlashTool to roll back to V10H and now have LG PC Suite find and upgrade the phone on its own, will see if that makes a difference...
Thanks
I see...I ll inform a member in another forum whereas he had the same issue.
faraband said:
I had no issues when on V10H, and nothing happened to the phone during the upgrade, just remained on my desk. When i revert back to V10H i have no issues also. I tried LGFlashTool to roll back to V10H and now have LG PC Suite find and upgrade the phone on its own, will see if that makes a difference...
Thanks
Click to expand...
Click to collapse
If after official upgrade doesn't work, I recommend you to take it to LG Service.
RuedasLocas said:
If after official upgrade doesn't work, I recommend you to take it to LG Service.
Click to expand...
Click to collapse
So i am currently in the US, bought the phone brand new unlocked from ebay. I called LG Support, and the rep said that since the phone is international, they cant do anything.. I would have to contact international LG Support to get help..? wtf
faraband said:
So i am currently in the US, bought the phone brand new unlocked from ebay. I called LG Support, and the rep said that since the phone is international, they cant do anything.. I would have to contact international LG Support to get help..? wtf
Click to expand...
Click to collapse
Same problem here. Not in such scale but I think it is the same. I had just bought the phone and when I did the update from the official site of LG te problem occured. I have sent the phone to service and I am waiting for it. Does anybody know if that phone has an international DOA??
Went to service, came back with the same problem. They had to replace it with a new one. I want risk to update again. Will stick with 4.0.
I just got a similar problem but much worse seen in the photo below attached my phone was working for a few weeks before this problem came as i was sat reading it, it just appeared while the screen was on. it also appears at boot and in cwm does this happen for you guys coz i think it's more a hardware problem for me.
Not sure what is causing it, but i went to 4 different repair stores, and none of them could figure it out. I sent it in for warranty, will report back what happens..
I had the same problem on my screen all the time , It's gone now for some reason, only thing i did is relocked the bootloader and unlocked it again since then it been running without any problems for almost a month now.
I remember i used the old method to unlock the bootloader , relocked it and i ran stock v20a(with locked bootloader) for like a month without any problems so i decided to try again , i used the official lg unlock method and now even on other roms it seems fine.
This bug is really annoying though hope ya'll get to fix it .
Try download an other v20 firmware, if that doesnt work, i can recommend superxe rom, its realy fast and stable.
Sent from my LG-P880 using xda app-developers app
I also think that it is a software problem because mine with the original Poland Rom 4.0 worked just fine.After one day of use I decided to upgrade to 4.1 from the original site of LG in Greece.this caused the problem.I believe that the flash caused some malfunction to the gpu.My cousin has the same exact phone for a year now but has never that problem.Maybe LG should give it a look because it seems pretty serious.
Sent from my LG-P880 using xda app-developers app
I had the same problem with V20A! but now I installed the CM10.1 nightly and also with the cyanogenmod appeared the same problem!! is a hardware problem? :crying: how can I fix?? Help me!! :crying:
this is the screenshot of CM10.1! I cut a little the picture!
Sent from my LG-P880 using xda app-developers app
is anyone elses permanently there. since it came on on mine it has never gone off including when booting up, in cwm and whilst in software recovery from flashing original bootloader. the other thing is screenshots look fine when on my pc.
My phone started doing the 4.3 OTA update last night, when the download got to about 43% the phone powered off and now wont turn on again.
The phone is completely stock. S-ON, no root.
When I connect it to the PC it tries to install drivers for QHUSB_DLOAD.
I take it the phone is bricked and has to go back for repair?
mikemod said:
My phone started doing the 4.3 OTA update last night, when the download got to about 43% the phone powered off and now wont turn on again.
The phone is completely stock. S-ON, no root.
When I connect it to the PC it tries to install drivers for QHUSB_DLOAD.
I take it the phone is bricked and has to go back for repair?
Click to expand...
Click to collapse
QHUSB_DLOAD -> yep, i would say hard-brick, needs a motherboard replacement.
OK, thanks, just organising to send it back, hopefully the new one will already have the update.
I take it no-one else has had any problems with the OTA update and this was just a one off?
This was in the UK on Vodafone.
mikemod said:
OK, thanks, just organising to send it back, hopefully the new one will already have the update.
I take it no-one else has had any problems with the OTA update and this was just a one off?
This was in the UK on Vodafone.
Click to expand...
Click to collapse
Not that I can recall, saw a few posts where it sometimes got stuck and had to force a reboot (manually), but not a hard brick. I guess the OTA got stuck updating hboot, and failed which would cause a brick I think.
mikemod said:
My phone started doing the 4.3 OTA update last night, when the download got to about 43% the phone powered off and now wont turn on again.
The phone is completely stock. S-ON, no root.
When I connect it to the PC it tries to install drivers for QHUSB_DLOAD.
I take it the phone is bricked and has to go back for repair?
Click to expand...
Click to collapse
By download, you mean downloading the OTA or installing it?
It was just in the middle of downloading it from HTC, got to about 43% and then powered down.
My htc one m7 phone is stuck too. How do you 'send it off' for a motherboard replacement and how much will it cost? Is it under warranty?
Can I go to the sprint store?
I'm on Vodafone UK and before I got the upgrade to 4.3, I got a small update just first, then the main 4.3 it installed ok and have had no problems as yet. Just wondering if the users that have had problems, got this small update first.
Sent from my HTC One using xda app-developers app
mikemod said:
It was just in the middle of downloading it from HTC, got to about 43% and then powered down.
Click to expand...
Click to collapse
Actually this seems to me more like a hardware issue. The phone can't just power down in the middle of the download, and it can't flash anything from inside the OS, it has to be in recovery. It's just a coincidence that you were doing the update.
Sent from my HTCONE using Tapatalk
Phone was irreparable so has been replaced with a nice shiny new one
Hi there eveyone, thank you for reading this.
a friend of mine has an HTC Desire OPM1100 D626ph (says on the back of the phone)
when he tries to update to the newer version (the official way) He faces an error, the phone restarts and its stuck now on an endless loop. the options he had was htc recovery menu. he has tried all the options there in hope of fixing the problem.(he doesn't know english) and he probably ruined everything. now the phone doesn't have a back up, nothing works. ADB wasn't turned on in the begining. no fast boot. the only options i think i have is to download a rom via sdcard.(not even sure if it's external)
these are the options on the menu:
reboot system now:
apply update from adb
apply update from sdcard
apply update from cache
wipe /data/factory reset
wipe cache partition
backup user data
restore user data
any help on this would be appreciated, any ideas what should be my next step? i have history of using fastboot/adb. i don't know which rom i should download and from where? htc website confused me and the onlyy thread i found on the internet was this one and there are several links on there. not sure which one should i use?
thanks again guys.
Which carrier is he on? Also, we would need to know if it's a 626, 626s, 626x, 626g, etc... Not sure which model it is from the info posted above. If it's a 626s, the only way to recover is if it's a T-Mobile 626s (no other versions have an RUU to restore it to stock).
Sent from my HP SlateBook 10 x2 PC using Tapatalk
jtrosky said:
Which carrier is he on? Also, we would need to know if it's a 626, 626s, 626x, 626g, etc... Not sure which model it is from the info posted above. If it's a 626s, the only way to recover is if it's a T-Mobile 626s (no other versions have an RUU to restore it to stock).
Sent from my HP SlateBook 10 x2 PC using Tapatalk
Click to expand...
Click to collapse
thank you for your response
it's an HTC Desire 626G+ (dual sim) and the carrier is "Telecommunication Company of Iran"
Hmm - I would have him contact his carrier and see if they have an "RUU" available for that phone. An "RUU" is Windows application that will reset the phone back to the way it came from the factory - and can typically restore any phone - unless it has a hardware issue.
Otherwise, let's see if anyone else has any input (I'm not familiar with the 626g myself).
Sorry that I couldn't be more helpful!
Sent from my HP SlateBook 10 x2 PC using Tapatalk
jtrosky said:
Hmm - I would have him contact his carrier and see if they have an "RUU" available for that phone. An "RUU" is Windows application that will reset the phone back to the way it came from the factory - and can typically restore any phone - unless it has a hardware issue.
Otherwise, let's see if anyone else has any input (I'm not familiar with the 626g myself).
Sorry that I couldn't be more helpful!
Sent from my HP SlateBook 10 x2 PC using Tapatalk
Click to expand...
Click to collapse
i don't think the carrier would help out with this. though it made me think he didn't do anything wrong so do you think that warranty will accept the phone?
The carrier are the ones that need to supply the RUU (either directly or via HTC), which I why I mentioned that he should contact the carrier.
I would agree that it's a warranty issue if he we just trying to install an OTA update and it caused all of this...
Sent from my HP SlateBook 10 x2 PC using Tapatalk
i have same problem with D626ph. I was rooted phone with kingroot after this try to update with ota and result was error and phone boot only to recovery menu
Ahhh - yeah, if you are rooted (and unlocked bootloader), you cannot apply OTA updates. Although, usually, they fail right away and you can just boot right back into the phone normally (without the update, obviously). It's kinda strange that the OTA is bricking the phone like that.
Sent from my HP SlateBook 10 x2 PC using Tapatalk
i wasnt unlock bootloader. phone was trying updating itsef, but failed. cant revive anymore.
i was repair my phone after many hours by flashing with SP FLASH TOOL and with
this file:
https://mega.nz/#!qFgAUQTI
regards!
Cant download the file, post full link.
bossko said:
i wasnt unlock bootloader. phone was trying updating itsef, but failed. cant revive anymore.
i was repair my phone after many hours by flashing with SP FLASH TOOL and with
this file:
https ://mega .nz/#!qFgAUQTI
regards!
Click to expand...
Click to collapse
Your link requires an decryption key.
pl provide key. facing the same problem with htc 626g+. Updated via official OTA. Sad that they rolled it without thoroughly testing it.
Have you guys contacted HTC and/or the carrier? They should resolve this issue for you (via an RUU or some other means)!
Sent from my HP SlateBook 10 x2 PC using Tapatalk
diml0rd said:
Hi there eveyone, thank you for reading this.
a friend of mine has an HTC Desire OPM1100 D626ph (says on the back of the phone)
when he tries to update to the newer version (the official way) He faces an error, the phone restarts and its stuck now on an endless loop. the options he had was htc recovery menu. he has tried all the options there in hope of fixing the problem.(he doesn't know english) and he probably ruined everything. now the phone doesn't have a back up, nothing works. ADB wasn't turned on in the begining. no fast boot. the only options i think i have is to download a rom via sdcard.(not even sure if it's external)
these are the options on the menu:
reboot system now:
apply update from adb
apply update from sdcard
apply update from cache
wipe /data/factory reset
wipe cache partition
backup user data
restore user data
any help on this would be appreciated, any ideas what should be my next step? i have history of using fastboot/adb. i don't know which rom i should download and from where? htc website confused me and the onlyy thread i found on the internet was this one and there are several links on there. not sure which one should i use?
thanks again guys.
Click to expand...
Click to collapse
Check this out, hope it helps: http://forum.xda-developers.com/desire-626/help/fix-htc-desire-626g-update-command-t3243510
Guys thank you for your replies. I'm kinda new to xda forum. Should i reply one by one and quote people's names or just reply in one comment? Are there any rules?
About the post, it's weird that many people are experiencing the same problem! And where i live phone carriers don't care about phone problems and it's the first time I'm hearing that i should contact my carrier for my bricked device. But things are differently in different countries ?? to @tpr0 i might try your solution when i get my hands on the device againand if no one provides a better suggestion. Because i gave it back to my friend and told him to try the warranty. After a day turned out he has bought the device without a warranty! They sell phones without warranty in iran for a cheaper price. I think it's worth paying 50 more dollars for a 1-2 years warranty. Anyway I'll let you guys know as soon my friend returns his phone (which will be pretty soon I'm guessing. Meanwhile ill wait if anyone has a link for the ROM or a solution.
try this:
https://drive.google.com/file/d/0B-19rlZr42VQVzNzdEV2MkpQQzA/view?usp=sharing
can u tell me the procedure for working with this file ??
diml0rd said:
Hi there eveyone, thank you for reading this.
a friend of mine has an HTC Desire OPM1100 D626ph (says on the back of the phone)
when he tries to update to the newer version (the official way) He faces an error, the phone restarts and its stuck now on an endless loop. the options he had was htc recovery menu. he has tried all the options there in hope of fixing the problem.(he doesn't know english) and he probably ruined everything. now the phone doesn't have a back up, nothing works. ADB wasn't turned on in the begining. no fast boot. the only options i think i have is to download a rom via sdcard.(not even sure if it's external)
these are the options on the menu:
reboot system now:
apply update from adb
apply update from sdcard
apply update from cache
wipe /data/factory reset
wipe cache partition
backup user data
restore user data
any help on this would be appreciated, any ideas what should be my next step? i have history of using fastboot/adb. i don't know which rom i should download and from where? htc website confused me and the onlyy thread i found on the internet was this one and there are several links on there. not sure which one should i use?
thanks again guys.
Click to expand...
Click to collapse
Im facing the same problem with desire 626 dual sim,after update phone back me to the recovery menu and giving me message update fail.After phone reboot stuck me on recovery menu and thats is. With 2 hours reading forums,the only way was to flash stock rom via Spflash tool..Afterall banned update from phone ! I dont know why is that issues if someone knows tha answer please let tell us ?
If you're using a phone from Iran I think you have bigger things to worry about.
Hi guys, as a lot of people now confirmed to me that it solved their problems complete when they switched to the GPE Firmware i think it is a good thing to write all that in a little own thread so not every user has to spam for the same bugs in all Android N Rom Threads.
First of all, YOU NEED TO HAVE S-OFF to flash Firmware files!!!
Using the GPE Firmware can solve the following bugs (thats no guarantee there can still be bugs in the Rom+Kernel):
-In Call Sound problems
-Camera Problems
-Mobile data problems
-wifi problems
-battery problems
Those bugs where already existing when the first Android 6 (M) Roms came to our M7 and with Android 7 (N) its still the same. But, those bugs are mostly present while using a Custom Rom on a Sense Firmware and they are nearly complete gone when you use the GPE Firmware.
Thanks to the Slim Jim Guy we have everything we need already here in the Forum. And please be that nice just give him a thanks for his thread as it helps us all a lot. Here is his Post and here is the direct download of his complete prepared Firmware without recovery and boot img GPE Firmware Download. It will delete nothing from your device, just changes the Firmware.
This Firmware is complete different to the one from HTC and is newer because Google provided much longer official updates for the m7 GPE than HTC did for the usual version.
Changed OP for complete Firmware file from Slim Jim Guy (thanks to maciclazar for this information)
just a little bump as a reminder haha
So if I understood right, it's better to have gpe firmware if I have a nougat ROM even if my phone is not GPE?
JustElisha said:
So if I understood right, it's better to have gpe firmware if I have a nougat ROM even if my phone is not GPE?
Click to expand...
Click to collapse
You can flash the GPE Firmware on any device thats not from a provider with CDMA radio like Verizon devices.
saturday_night said:
You can flash the GPE Firmware on any device thats not from a provider with CDMA radio like Verizon devices.
Click to expand...
Click to collapse
I just have to flash it in twrp or S-OFF is required?
JustElisha said:
I just have to flash it in twrp or S-OFF is required?
Click to expand...
Click to collapse
Like written in OP "First of all, YOU NEED TO HAVE S-OFF to flash Firmware files!!!"
@saturday_night I was using that firmware from Santod040's thread for months until I realised it was not full firmware.
The full GPE firmware is located in this post by Slim Jim Guy. It is full firmware containing hboot, radio and everything else and will turn you phone in full GPE device and the best thing is it fixes random reboots on nougat and marshmallow roms.
Edit: Never mind. Found the answer I was looking for.
maciclazar said:
@saturday_night I was using that firmware from Santod040's thread for months until I realised it was not full firmware.
The full GPE firmware is located in this post by Slim Jim Guy. It is full firmware containing hboot, radio and everything else and will turn you phone in full GPE device and the best thing is it fixes random reboots on nougat and marshmallow roms.
Click to expand...
Click to collapse
Exactly, link of post #1 is the black hboot 1.54 only
Would this work for Android N ROMs with the international variant? Running Xenon 7.1 ATM.
Not sure what's wrong. I've flashed GPE firmware, got a new battery, still phone does this awful thing Could be mainboard problem? How can I test motherboard?
Thanks
umbyka said:
Not sure what's wrong. I've flashed GPE firmware, got a new battery, still phone does this awful thing Could be mainboard problem? How can I test motherboard?
Thanks
Click to expand...
Click to collapse
What ROM are you using right now, how did you get S-OFF?
Yesterday I've turned back to stock GPE 5.1, hoping that it's a ROM problem, but still my phone shuts down by itself, even at 90%. S-OFF I gained a few years ago, in 2014 I think. Rumrunner if I remember right.
@umbyka are you able to completely drain the battery to zero, then, without powering the phone back on, connect it to a charger and let it charge to 100%?
93zx7 said:
@umbyka are you able to completely drain the battery to zero, then, without powering the phone back on, connect it to a charger and let it charge to 100%?
Click to expand...
Click to collapse
Yes, I'm able. So..I did turn back to 5.1 GPE, full stock, seems that, with this ROM, everything is normal. Didn't mention, that with all N ROMs the phone went so hot, that it was almost burning, but with 5.1 GPE it doesn't. I did this HTC said battery calibration, with both volume buttons + power button for 2 minutes also. Hopefully it's not a mainboard issue after all...
umbyka said:
Yes, I'm able. So..I did turn back to 5.1 GPE, full stock, seems that, with this ROM, everything is normal. Didn't mention, that with all N ROMs the phone went so hot, that it was almost burning, but with 5.1 GPE it doesn't. I did this HTC said battery calibration, with both volume buttons + power button for 2 minutes also. Hopefully it's not a mainboard issue after all...
Click to expand...
Click to collapse
How's the camera performance? How often does the purple hue come?
zeeBomb said:
How's the camera performance? How often does the purple hue come?
Click to expand...
Click to collapse
This is a hardware problem and not software related. When HTC made the first OTA Updates the device became too hot during the update process so that some camera modules got a little damage which caused this purple pictures. If it wasnt repaired under guarantee the only way for you to get this fixed is replace the camera module.
saturday_night said:
This is a hardware problem and not software related. When HTC made the first OTA Updates the device became too hot during the update process so that some camera modules got a little damage which caused this purple pictures. If it wasnt repaired under guarantee the only way for you to get this fixed is replace the camera module.
Click to expand...
Click to collapse
right...but what exactly would the camera fix be if i flash gpe?
So, I haven't been around for a while now, but I'll share with you the problems I have :
Even with GPE ROM phone shuts itself down sometimes even at 70% battery, sometimes it lasts till 20%. When it shuts down itself, turning it back on seems to get a problem. Normally it should get back on with all my settings saved, I mean background, ringtones, etc., but it starts with a message : Android is optimising apps..., and when it boots up finally, everything is gone. I mean background, ringtones, passwords. So, anybody has a clue what's going on?
umbyka said:
So, I haven't been around for a while now, but I'll share with you the problems I have :
Even with GPE ROM phone shuts itself down sometimes even at 70% battery, sometimes it lasts till 20%. When it shuts down itself, turning it back on seems to get a problem. Normally it should get back on with all my settings saved, I mean background, ringtones, etc., but it starts with a message : Android is optimising apps..., and when it boots up finally, everything is gone. I mean background, ringtones, passwords. So, anybody has a clue what's going on?
Click to expand...
Click to collapse
Did you clean flash everything including firmware? If yes, that sounds like a hardware damage
Here is the link and source.
https://m.gsmarena.com/samsung_gala...sing_battery_life_and_security-news-32580.php
Nice. Thanks for the heads up
Typical
I've only just gone n rooted and twrp'd arrrggghhhhh
Yes, I confirm. Bought a used Note 4 for the wife and was surprised to see it getting an update...
I didn't received the update
I have problem to install it,i have downloaded file couple of time and every time when i try to update says update faild tmobile...something like that. .
jjoeshua said:
I have problem to install it,i have downloaded file couple of time and every time when i try to update says update faild tmobile...something like that. .
Click to expand...
Click to collapse
what is youre curent version? drf1?
The problem is when I go to stock recovery I get message like this:
Dm - verify verification failed
Check your DRK first..
I must solve this to be eneble to install update..
I dont know how..
Greetings, I'm new to this forum but I've followed it for a long time in the great HTC days of installing windows on their phones. I live in France (nobody is perfect )
On from the introduction, my girlfriend and one of her friend have batteries problem with their note4 since a couple of weeks now: the phone "dies" at 34% or so reported remaining battery power. It refuses to start again unless plugged, the first days the charging animation even reported 34 remaining power but now it starts at 0%. And though I've ordered a new battery, her friend did the replacement before us and it didn't fix her problem, so I guess battery replacement won't fix mine.
So if it's not the battery, it may be the software (it may be a hardware problem on the board but I don't think it suddenly stroke two note 4) So my question is, how do we know if this upgrade is currently installed ? Is it the "build number" N910FXXU1DRF1 and/or baseband version N910FXXS1DQA1 or something else ?
Thanks in advance for your help.
jjoeshua said:
The problem is when I go to stock recovery I get message like this:
Dm - verify verification failed
Check your DRK first..
I must solve this to be eneble to install update..
I dont know how..
Click to expand...
Click to collapse
This means you've disabled encryption on the boot partition.
You'll have to flash the stock firmware via Odin.
Totally stock, no bells and whistles.
---------- Post added at 05:06 PM ---------- Previous post was at 05:03 PM ----------
jtmasse said:
Greetings, I'm new to this forum but I've followed it for a long time in the great HTC days of installing windows on their phones. I live in France (nobody is perfect )
On from the introduction, my girlfriend and one of her friend have batteries problem with their note4 since a couple of weeks now: the phone "dies" at 34% or so reported remaining battery power. It refuses to start again unless plugged, the first days the charging animation even reported 34 remaining power but now it starts at 0%. And though I've ordered a new battery, her friend did the replacement before us and it didn't fix her problem, so I guess battery replacement won't fix mine.
So if it's not the battery, it may be the software (it may be a hardware problem on the board but I don't think it suddenly stroke two note 4) So my question is, how do we know if this upgrade is currently installed ? Is it the "build number" N910FXXU1DRF1 and/or baseband version N910FXXS1DQA1 or something else ?
Thanks in advance for your help.
Click to expand...
Click to collapse
My note 4 was going through this exact issue.
You'll need either a brand new battery, or you'll have to do a full format and reinstall whatever software you had prior.
ninjasinabag said:
This means you've disabled encryption on the boot partition.
You'll have to flash the stock firmware via Odin.
Totally stock, no bells and whistles.
Click to expand...
Click to collapse
Can you explain me a little more about that encryption on the boot partition.
First I was download official stock firmware for my model sm-n910t T-Mobile, than flash it try Odin and the problem is still stay Odin didn't change nothing. I was havin an OTA update that i couldn't install because of this DM- verify verifications failed.
So I download Smart Switch and through that program install the latest update that was realised this year with security patch from August I think it's Baseband version with N910TUVU2EQI2, but still problem is stay.
Do I need something more to do in Odin or what?
jjoeshua said:
Can you explain me a little more about that encryption on the boot partition.
First I was download official stock firmware for my model sm-n910t T-Mobile, than flash it try Odin and the problem is still stay Odin didn't change nothing. I was havin an OTA update that i couldn't install because of this DM- verify verifications failed.
So I download Smart Switch and through that program install the latest update that was realised this year with security patch from August I think it's Baseband version with N910TUVU2EQI2, but still problem is stay.
Do I need something more to do in Odin or what?
Click to expand...
Click to collapse
Honestly, I can't tell you more than I already have.
DM-verity (encryption) has to be active for you to be able accept an update.
I don't know why it's failing for you, can't fix it either.