I've flashed a US retail version of Oreo operating system to the phone and re-locked bootloader, now upon restart I keep seeing:
"Your device has loaded a different operating system. "
It then boots up fine, barring the fact OTA's still fail and phone won't connect to any data/Carrier networks...the thing I was trying to fix.
How do I get rid of this message so it loads up as if out of the box? Thanks!
UPDATE: Word of advice, don't Flash third-party-Carrier ROM's onto this phone...keep like to like.
(NO ROOT) Get Verizon Working on Sprint Carrier Version Moto Z2 Force OREO ROM
Follow these steps!
https://forum.xda-developers.com/z2-force/how-to/free-sprint-moto-z2-force-carrier-t3843824
Related
I upgraded from a stock rooted 4.4.2 to the OTA 5.0 using the ROM that was rooted. Some apps for my smart watch don't work in 5.0 yet, so I went TWRP and restored my backup. After booting, the phone will not get any service at all. It shows it's searching for service then gives a red "x" then starts searching again. This is process that just keeps going. I flashed the stock .tot file using the LG flash tool to get the phone completely back to stock. After doing so, the radio still won't get service. I then applied the OTA push of 5.0. After 5.0 was installed, the radio gets service without any issues. I used the LG flash tool again to go back to 4.4.2 stock and same issue; no service. Updated again to 5.0, and I get service. Any ideas on what's happening here? Is it the firmware for the radio that's having issues?
I was able to fix this by playing with the APN settings and it was able to get service, but no data. I then went back to the default t-mobile APN setting and now it works.
Same Issue
After using lg update tool to go to new 5.0 update, I put twrp back on and flashed cm12 and bliss pop rom on mine and service 100% drops out and only came back after a battery pull or a reboot, e tried to re-install roms on both and after having the same issue with the roms i tried a custom kernel issue went away and then came back, so i haven't tried AOSP since the t mobile said they'd send me another brand new phone ....but once i put everything back to OEM using the lg tool it's been 100% working again with no issues... i will try AOSP when the new phone gets here,, im thinking its kernel related
You need the new modem, boot loader, and boot images. You can't simply just flash a ROM unless all 4 (system included) is packaged as so
Hello,
I'm having a weird issue with my Note 7 that I didn't have at all until tried to root for the first time....
It randomly restarts, sometimes is very often and sometimes it take a few hours to do it, but when it does it just restarts out of nothing and when Android loads again it asks me for a password that doesn't even exsits
"To start your device, enter your password" (Picture attached)
This started to happen after used the rootable kernel that was published before SuperSU 2.77 Beta but even reflashing the stock firmware, bootloader, modem, CSC it keeps doing it even when my Android is not yet configured (at the first Welcome screen before setting the phone up), so there is no password at all at this point. I've tried my Google account password, but it doesn't work.
This message is the same that comes up when you select "Secure Boot" so you need to enter a password or PIN to decrypt your data and be able to load it, but I don't have that option checked, and could not be checked when the phone is not even configured.
The way to work around this issue is flashing the no-verity-opt-encrypt mod that is not supposed to be needed anymore after SuperSU 2.77 has been released. So flashing this mod will get me into my Android home screen but it will eventually restart again and I need to flash this mod again.
This is what I've tried so far and it keeps happening:
- Flashed the rootable kernel when it was published and the no-verity mod. I formated data as indicated in the post. Then this problem appeared.
- Flashed stock firmware, bootloader, modem, csc thinking this would remove any trace of the mods I flashed, but kept happening.
- Factory reset from the Samsung recovery, had the "no verity" errors sometimes and sometimes not.
- Flashed other firmwares, bootloaders, modems, csc from other countries but for the same model N930F and kept happening.
- Flashed custom ROMs, formated system, data, everything.
- Flashed stock firmware again.
- Flashed custom ROMS again with the new SuperSU 2.77 and keeps happening.
I have done every single flash that actually exists for the Note 7 and formated everything with no luck....
Has anyone have this issue or had it at all at some moment? If so... How did you manage to get rid of this message?
I hope someone can help, If it was faulty phone I think it would restart at any point even in Recovery or Download mode, but only happens inside of Android.
Seems a common problem I think?
http://forum.xda-developers.com/showthread.php?t=3444510
Sent from my Nexus 6P using Tapatalk
Yep, saw that post... But never seen anyone complaining about the phone asking for a password when reboots (only when it crashes) its like it was asking for a password to decrypt the phone.
Hi guys,
I have been having issues with my Australian Moto Z PLay. I have been Romming for a while now and tried to first return the phone to stock using the adb method. Which didnt work (I cant remember why, I think I finished it all and it would only boot to bootloader or recovery). Then tried updating only the modem using this method https://forum.xda-developers.com/moto-z-play/how-to/update-bootloader-modem-to-flash-stock-t3818253 then I tried flashing a few ROM's
The issue now is that the phone turns itself off and on a few times a day. I have launcher crashed quite often and the battery seems to have less life in it.
In short I'm not too sure what I have done wrong. Maybe a few things. Can anyone help me get back to a point where I can install custom ROM's like before relatively safely and reliably? I have tried a few different rom's and had lots of similar issues with each.
ROM - AOSP Extended v5.8 Official
Android - 8.1.0
Baseband version - M8953_10238.63.04.83.01R
Kernel Ver - 3.18.71-OPN28.49-2-g04699f27af49
SELinux Permissive
Hardware - Moto Z Play purchase in Australia retail from Harvery Norman
Boot messages
"There's an internal problem with your device. Contact manufacturer for details" (appears twice, once before needing password, once after. Never needed pin code before)
Thakn you in advance!
....also lots of lag. I'm going someone can guide me to the modem etc settings that should be in my device
Hi team
I recently purchased an ex Demo HTC One M9 as a cheap replacement to my broken Galaxy S7 Edge, as soon as I received it I decided to flash TWRP and a new ROM on it. I was able to unlock the bootloader via HTCDEV.com easily enough and I was able to flash TWRP onto it without issue but when it came to the ROM's I ran into many problems.
Any version of Android that is Nougat or lower would not boot, the phone would go straight to the white bootloader screen every time. Oreo and Pie ROMs were able to boot but I ran into separate issues with them, I could not make or receive phone calls as the whole phone would freeze and there was no audio in from the speaker. I was also unable to play any videos in Facebook, YouTube, Snapchat etc.
I tried every single ROM available here on XDA and ran into these issues. I stupidly also did not make a TWRP backup of my system so it was quite hard to revert back to what it came from factory, I managed to get a stock Marshmellow running thanks to a User here posting a TWRP backup so thanks.
Is anyone able to help me with upgrading to Nougat? I would really like to get the Viper ROM working if possible, is it a known issue getting stuck in the bootloader menu every time?
I've tried just updating through the OTA process in the menu but it says there is no update file available.
Cheers
I am trying to revive my old z2 force t-mo edition. It basically crashed after an OTA and lost baseband and IMEI and i threw in in a drawer for months.
I tried flashing newest firmware-nothing, i tried unlocking bootloader and flashing second new firmware-nothing. The device does turn on--just no data, no wifi etc. I'm not too familiar with blankflashing, is this something i can even do with a device that turns on? Will that even work? Moto assistant says they are "unable to verify a match" when i pick repair device and select XT1789-04. Does anyone else have anything else to try? I have not rooted, have not installed pie firmware or anything. Long story short, im now in need of a working phone so i just want to get this working again!
Same boat as you! Have tried everything on here. What's a blank flash?
Have u tried this?https://forum.xda-developers.com/z2...m-tmo-z2-force-27-1-5-flashall-march-t3917070
I was in your situation and this fixed everything (in my case 27.1.5 didn't work, 27.1.7 worked)
Just remember to do a factory reset in stock recovery, after flashing. Without it, I had bootlops
Dany XP said:
Have u tried this?https://forum.xda-developers.com/z2...m-tmo-z2-force-27-1-5-flashall-march-t3917070
I was in your situation and this fixed everything (in my case 27.1.5 didn't work, 27.1.7 worked)
Just remember to do a factory reset in stock recovery, after flashing. Without it, I had bootlops
Click to expand...
Click to collapse
Had the same issue with baseband unknown/no wifi/no LTE, the 27.1.7 flashall fixed it for me