My brother and I both own D950s from ATT My phone was updated to 4.4.2 through OTA, He started downloading the OTA update but it never actually installed, so under software information his phone is still 4.2.2, I ended up dropping his and broke the little bezzel a little, I felt bad, switched sim cards I now have his old 4.2.2, I thought i'd update it OTA, ATT doens't want to push the OTA cause it says his old phone with my sim card is not registerd, whatever that means. I figured since I can't get it to update OTA i'll just try to root it via ioroot25r1, The batch process hangs up at mounting SU binary etc etc and the phone never reboots into ADB or recovery after toggling usb modes and all that, any insight?
Related
I have an untouched HTC One M7 Google Play Edition phone that is stuck on Android 4.4.4. I am not sure what I should do at this point to get lollipop. I tried manually updating the phone by booting into recovery mode and selecting "Apply from phone storage". (I previously manually downloaded the update on the phone). This just quickly flashes "invalid operation" on the screen and the phone reboots. I see that there are many directions I can go from here, but I am not sure which one is best for my phone. I have concluded that Google has forgotten about me and I am not going to automatically get Lollipop. Incidentally, I bought my phone unlocked from Expansys and not from a Carrier. I am currently with Telus.
MZimbaro said:
I have an untouched HTC One M7 Google Play Edition phone that is stuck on Android 4.4.4. I am not sure what I should do at this point to get lollipop. I tried manually updating the phone by booting into recovery mode and selecting "Apply from phone storage". (I previously manually downloaded the update on the phone). This just quickly flashes "invalid operation" on the screen and the phone reboots. I see that there are many directions I can go from here, but I am not sure which one is best for my phone. I have concluded that Google has forgotten about me and I am not going to automatically get Lollipop. Incidentally, I bought my phone unlocked from Expansys and not from a Carrier. I am currently with Telus.
Click to expand...
Click to collapse
Anybody?
HELP - "dm-verity verification failed..." recovery message and no cell service
Background Info:
Was rooted on OE2 via pingpongroot and supersu and froze some bloatware with Titanium Backup, nothing else done to the phone. Flashfire was on there but never used. Phone has worked fine this way for about 7 months.
This past Friday I suddenly lost all network connectivity and was very sporadic in connecting to the LTE network. Also lost ability to send text messages.
These are the steps I did:
1. Went to the ATT store, verified IMEI was ok, and got a new SIM card - nothing
2. Tried *#*#4636#*#* dialer code to see the network settings - nothing
3. *#0011# diagnostics dialer code - nothing
4. Tried different APN settings as well as APN reset - nothing
5. Factory reset - nothing (could not factory reset from UI, had to do it from recovery - "dm-verity verification failed..." message seen in recovery)
6. Removed pingpongroot app and uninstalled root via supersu, verified with rootchecker - nothing
7. Did another factory reset without root - nothing (could not factory reset from UI, had to do it from recovery - "dm-verity verification failed..." message seen in recovery)
8. Somehow the texting message center digit code was changed, so I did some googling and changed it back to +13123149810 from 313133127 - FIXED TEXT MESSAGING
9. Spent an hour with tech support verifying there were no network restrictions or limitations with my device - nothing
10. Attempted an OTA update on the phone - update failed (dm-verity verification failed.... message in recovery)
I didnt find too much on the dm-verity verification failed... message in recovery. It seems it has something to do with system files being modified, or something with the EFS. I cannot figure out what is going on with no network service, so an option is to either replace the phone under warranty from a service center, or to try and flash stock firmware via ODIN. Phone doesnt have knox tripped and says official under status, so I dont think I would have a problem replacing with them.
Questions:
1. Will "dm-verity verification failed..." cause issues with Odin and going back to stock recovery? Last thing I want is a brick when I could return it.
2. Can anyone think of anything else I could try in terms of trying to get my cell signal back? It connects to LTE in high populated places, but in places where it used to have fine reception (work, home) it gets nothings. This combined with the fact that my message center code was changed makes me think something deep in the network settings was also changed, but I have no idea where to look.
Thanks.
Do you still have frozen bloatware? You might want to try un freezing everything, and seeing if that helps. Perhaps you locked something up that's in need of an update / conflicting now.
AoN
anneoneamouse said:
Do you still have frozen bloatware? You might want to try un freezing everything, and seeing if that helps. Perhaps you locked something up that's in need of an update / conflicting now.
AoN
Click to expand...
Click to collapse
Everything should be unfrozen after I did the factory reset, as I saw all of the ATT bloatware pop up again.
I am receiving reception again!
1. Odin back to stock. In this case it was OE2
2. Factory reset - this removed the "dm-verity verification failed..." message in recovery
3. Took the OTA update to OI2 ROM version
4. Factory Reset
5. Took the OTA update to OJ7 ROM version
6. Now have reception again in areas where it suddenly dropped off.
I do notice that my IMEISV number changed between OTA updates, and there are some extra network options in the secret dialer code menu. Not sure if that had anything to do with it, or the fact that I did not take any OTA updates since receiving the phone 7 months ago.
Anyway, hope this helps some people who may have suddenly lost reception in places they used to have it.
orlandoxpolice said:
I am receiving reception again!
1. Odin back to stock. In this case it was OE2
2. Factory reset - this removed the "dm-verity verification failed..." message in recovery
3. Took the OTA update to OI2 ROM version
4. Factory Reset
5. Took the OTA update to OJ7 ROM version
6. Now have reception again in areas where it suddenly dropped off.
I do notice that my IMEISV number changed between OTA updates, and there are some extra network options in the secret dialer code menu. Not sure if that had anything to do with it, or the fact that I did not take any OTA updates since receiving the phone 7 months ago.
Anyway, hope this helps some people who may have suddenly lost reception in places they used to have it.
Click to expand...
Click to collapse
Sorry bro, as you installed the old program?
I believe it's because you are on Of4 firmware, but restored the oe2 files? To get back you need the flash the files in Odin from the muniz of4 update thread.
Nevermind, I see you updated already.
Today I received a notification from supersu pro that I needed an update. After it installed it requested a restart. After restart, there was no connection to cell service nor could I turn the radio on in network settings nor were there any settings registered. I was however able to connect using WiFi from my home computer. I was running stock rom with twrp-recovery and OS h81120o for t-mobile. I tried restoring backups by twrp with no radio/network function. I installed
twrp-3.0.2-0-h811.img
android_device_lge_h811-android-5.1.zip
G4-H811-MM-20i-Stock-Debloated-Rooted.zip
G4-H811-MM-20o-Stock-Debloated-Rooted.zip
G4-H811-MM-20o-Stock-Rooted in this order with nothing different working in network connection and radio off. I finally installed LG-H81120i-Flashable.COMPLETE.zip and it said installed successful yet when restarted the phone bricked. No power on, nothing. I received than same notice for my rooted Samsung galaxy tab 4 8.1 and declined it and am still running fine there. Any thoughts?
Hey,
I was in the exact same boat and almost gave up!
Got my LG back from repair and I rooted it then made a back up, everything was working fine. Flashed a new ROM and updated SuperSU, was not able to get a signal or mobile connection after that. IMEI Number was now NULL. I tried factory reset but still nothing can get the network signal back. Even restoring back to my back up did not work.
I read that if you flashed the LG-H81120i-Flashable.COMPLETE.zip you will brick so I avoided that. I finally found the solution and maybe this will work for you.
Download LG UP and your kdz file (H81120o_00_0613.kdz was mine) on your pc.
Set phone into Download mode by pressing volume up and connect to PC.
Open LG UP and load the KDZ path file and run. Phone should reboot and come back. My signal came back after this.
I hope this method works for you.
Best of luck!
Hello XDA, I'm having a problem with my grandmother's phone, and I'm in a hurry to get this fixed because she needs it for business. Her phone is an AT&T Galaxy Note 3 SM-N900A unlocked to T-Mobile. It was running Android 4.4.2 KitKat, and I tried to update the phone as I did with my grandpa's, who has the same exact phone before we switched to T-Mobile. Because it was unlocked, the phone couldn't receive the OTA Lollipop update due to the SIM card not being AT&T.
After spending 4 hours searching and trying solutions, I came down to one thread on XDA Forums here. I saw it and I ended up using Odin 3.09 to flash the All-In-one/Non-Wipe Tar file onto it, now my phone is stuck in a boot-loop. Strangely, the Lollipop update seems to be installed as when I plug her phone into my PC/charge it, the battery screen is different than the old one which looked shiny and not flat and material like the Lollipop one. Knox has not been tripped, system status is OFFICIAL, and every time I turn on the phone, it proceeds to boot until the AT&T logo screen, where it freezes mid-way vibrates 2 times and boots the same way over and over again.
Is there anything I can do aside from doing a wipe or factory reset, as I mentioned before she has to use the phone for a business she works for and she had somewhat important work on the phone. The worst part of it all is I was stupid and ignored the warning to back my data up first in the firmware thread. Please help, I'm in a very big hurry to solve this and finish the updating/problem.
P.S If it's not a boot loop and it's called something else, whatever. xD
Did you try using Smartswitch to see if it can see and repair and/or reflash? A factory reset may be the only way to fix it because I believe the file layout for KK and LP and different.
I recently rooted my H811 G4 (T-mobile) and then installed the latest Imperium ROM on it. Everything worked fine for three days. The only thing that kept popping up was an alert from Lookout, saying that the Imperium Settings app had riskware and wanted me to delete it. I just ignored the warning as I figured that it was being fussy over an app from a custom ROM. I also kept getting notifications to upgrade my version of Android but I ignored those too as I learned that with a rooted phone, it either won't work, or will unroot the phone. After 3 days, I suddenly lost connectivity to the T-Mobile network. Could still make calls and text over wifi, but nothing when the wifi was off. After going into the settings, it would say that the network was disconnected. I took the phone to T-mobile and they tested the sim card in another phone, to which it worked just fine. So that told me that something was obviously wrong with my handset. I restored the phone back to factory default and was able to make calls again. Imperium was still installed on it. So I went back into recovery and wiped the phone clean. After selecting to restart the phone in TWRP, I got stuck on the bootloader screen. So I downloaded LG Bridge and got it working again. I was going to wait till I got a notification to upgrade Android before rooting it again, but after 2 days, I never got it. Has anyone else had this happen? I thought Imperium was cool but I'm not thinking of just going with another custom ROM.
Musicman82121 said:
I recently rooted my H811 G4 (T-mobile) and then installed the latest Imperium ROM on it. Everything worked fine for three days. The only thing that kept popping up was an alert from Lookout, saying that the Imperium Settings app had riskware and wanted me to delete it. I just ignored the warning as I figured that it was being fussy over an app from a custom ROM. I also kept getting notifications to upgrade my version of Android but I ignored those too as I learned that with a rooted phone, it either won't work, or will unroot the phone. After 3 days, I suddenly lost connectivity to the T-Mobile network. Could still make calls and text over wifi, but nothing when the wifi was off. After going into the settings, it would say that the network was disconnected. I took the phone to T-mobile and they tested the sim card in another phone, to which it worked just fine. So that told me that something was obviously wrong with my handset. I restored the phone back to factory default and was able to make calls again. Imperium was still installed on it. So I went back into recovery and wiped the phone clean. After selecting to restart the phone in TWRP, I got stuck on the bootloader screen. So I downloaded LG Bridge and got it working again. I was going to wait till I got a notification to upgrade Android before rooting it again, but after 2 days, I never got it. Has anyone else had this happen? I thought Imperium was cool but I'm not thinking of just going with another custom ROM.
Click to expand...
Click to collapse
Modem problem. Don't waste your time. Oreo is the latest build for TM-LGG4:
https://forum.xda-developers.com/g4/development/rom-lineageos-15-1-t3806629
Need TWRP to flash.