For the past week I've been trying to install the NE9 update. When trying it reboots the phone and starts installing. Half way through installation the android falls on its back and fails. Then when it boots back up again it tells me that the update wasn't applied due to failure.
Prior to the update before trying I've been rooted with towelroot if thats worth mentioning.
I also tired Verizon Software Upgrade Assistant on the PC and the software tells me its up to date, not acknowledging that there is a newer firmware available.
Is there another way to "update" without flashing. I'm not really up to reinstalling and reconfiguring everything. Although I have Titanium Backup Pro.
Also if no solutions how do I get rid of this screen which pops up everyday?
You already know the answer and are trying to avoid it. Odin is the most reliable way to apply an update. OTA updates fail for numerous reasons and we couldn't begin to guess why in your case because you provided almost zero information about your phone e.g.what was the exact, verbatim error or failure message you received, have you frozen any apps, syslog, current firmware version or anything else.
We don't have your phone in front of us, so when you don't describe those crucial details, the best we could possibly do is make stabs in the dark as to what is going on.
If you do a proper backup, restoring your programs afterward shouldn't be that hard. You could probably just restore your backed up /data partition over the updated system and have most of your apps and settings restored in one swoop. Alternately, you might be able to apply the new firmware image with mobile odin pro, while leaving your existing /data partition intact.
Or disable the OTA update manager to avoid the update. Verizon likes to rename or at least append vzw to system apps, so search the Verizon forum for the name of the Verizon OTA update manager app.
.
fffft said:
You already know the answer and are trying to avoid it. Odin is the most reliable way to apply an update. OTA updates fail for numerous reasons and we couldn't begin to guess why in your case because you provided almost zero information about your phone e.g.what was the exact, verbatim error or failure message you received, have you frozen any apps, syslog, current firmware version or anything else.
We don't have your phone in front of us, so when you don't describe those crucial details, the best we could possibly do is make stabs in the dark as to what is going on.
If you do a proper backup, restoring your programs afterward shouldn't be that hard. You could probably just restore your backed up /data partition over the updated system and have most of your apps and settings restored in one swoop. Alternately, you might be able to apply the new firmware image with mobile odin pro, while leaving your existing /data partition intact.
Or disable the OTA update manager to avoid the update. Verizon likes to rename or at least append vzw to system apps, so search the Verizon forum for the name of the Verizon OTA update manager app.
.
Click to expand...
Click to collapse
I got through it. Thanks for replying. The Verizon Software Upgrade Assistant started working. I was getting ready to go into odin after I plugged in my USB cable then I noticed to the bottom right something said downloading update. The software did everything. After I swapped kernels rooted and swapped the kernal back with odin. Sorry my mind is a bit foggy I've recently came back to Android. Last time I was around was way back with the Motorola Cliq and the HTC Sensation. I really wasn't up for flashing because I had the phone for about 2 weeks and if I hit a snag then it will require a bunch of research /rant.
All is well solved.
Hey all,
Having a small issue with my Verizon LG G2.
When I first got it on launch, I rooted it, installed loki (to bypass the locked boot loader) and have been running custom ROMs.
This is the way I ahve been running it since, on 12B, with loki and CM11.
Before I installed custom roms I did a image backup using Clockwork.
Yesterday I bought a Droid Turbo, so it was time to restore the G2 in preparation for sale.
I attempted to restore my original backup of the stock image, but it failed (stating something about an inability to restore/system, resulting in a soft bricked phone.
I fixed this by downloading the LG Flash tool, and the stock 24A .kdz image, putting the phone in download mode and flashing it.
The LG flash tool seemed a bit buggy, complaining about not finding servers, but eventually flashed the phone with the .kdz.
Everything seems to have worked well. Root is gone, clockwork is gone, (and I assume loki is gone as well, but I can't tell) but now I can not do the latest OTA updates, and am stuck on 24A.
It's not that it downloads the OTA, and then fails to install it, but rather it complains that it is unable to download the updates at all.
I was thinking this might have something to do with the fact that the CDMA radio is now unactivated (since I got a new phone) and it somehow needs to verify with the Verizon network prior to downloading, so I grabbed a working SIM and popped it it in. Even with 4G via the SIM, the OTA downloads don't succeed.
Does the CDMA radio need to be activated in order for a phone to receive OTA updates? If not, I ahve something else wrong going on, and would appreciate any suggestions regarding fixing it.
The plan was to sell the LG G2 to pay for my Droid Turbo upgrade, but I don't want to sell the phone to someone if I think it may be having issues.
I would appreciate any thoughts and suggestions from you guys!
I purchased 2 Essential phones from Sprint. In order to get them fully unlocked, they need to be active on Sprint for a minimum of 50 days.
This isn't a huge deal, since I am an active Sprint customer. I currently setup the first phone exactly as I like it, rooted, and restored all my apps with Titanium Backup. Currently running Android 7.1.1 NMJ32F, since I wasn't ready to flash the Oreo beta.
My plan is to use the first phone for 50 days, get it unlocked, wipe it, relock the bootloader, and give it to a relative to use on Verizon.
I will then start using the 2nd Essential phone on my Sprint line, unlock it after 50 days, and keep it for my personal use.
Question: Is there any possible issue that may arise if I use TWRP to make a full backup of Phone #1 and then restore that backup on Phone #2?
I am hoping TWRP would create phones that were identical in terms of apps, home screens, settings etc. Doing this would save me the time of having to setup two phones.
If this will work, does it even matter if the 2nd device is running the same software build version of Android, prior to me restoring the TWRP backup from the first device?
As long as you don't backup and restore EFS, you should be fine. I've done this in the past with no issues
Do US carrier lock unlocked phones??? I bought mine outright from Telus in Canada and popped my Bell Sim in and it was fine. I thought the Nexus, Pixel and now Essential lineups were unlocked out the box?
Turbojugend said:
Do US carrier lock unlocked phones??? I bought mine outright from Telus in Canada and popped my Bell Sim in and it was fine. I thought the Nexus, Pixel and now Essential lineups were unlocked out the box?
Click to expand...
Click to collapse
Pretty much every time, particularly if they're the 'exclusive' carrier for it :
Pixels with Verizon are locked
PH-1s from Sprint are locked
HTC U11 from Sprint are locked
It even used to be that you more or less got an unlocked GSM phone when you bought from T-Mobile, now you get them locked as well.
Seamonkey79 said:
Pretty much every time, particularly if they're the 'exclusive' carrier for it :
Pixels with Verizon are locked
PH-1s from Sprint are locked
HTC U11 from Sprint are locked
It even used to be that you more or less got an unlocked GSM phone when you bought from T-Mobile, now you get them locked as well.
Click to expand...
Click to collapse
That's really crappy. As of Dec 1st in Canada all devices will be unlocked and older locked ones will be unlocked free of charge.
Turbojugend said:
That's really crappy. As of Dec 1st in Canada all devices will be unlocked and older locked ones will be unlocked free of charge.
Click to expand...
Click to collapse
It is, but that's okay because so are the carriers. They're required to offer unlocks once the phone's contracted time is up and/or it's paid in full, but like Sprint with their 50 days, they just add other criteria so that you have to stick with them. They're all pretty predatory.
Seamonkey79 said:
Pretty much every time, particularly if they're the 'exclusive' carrier for it :
Pixels with Verizon are locked
PH-1s from Sprint are locked
HTC U11 from Sprint are locked
It even used to be that you more or less got an unlocked GSM phone when you bought from T-Mobile, now you get them locked as well.
Click to expand...
Click to collapse
Verizon pixels are not locked. Verizon does not carrier lock any lte phones.
Sent from my PH-1 using Tapatalk
bricky23 said:
Verizon pixels are not locked. Verizon does not carrier lock any lte phones.
Click to expand...
Click to collapse
Oh yes, that's right. Pixels just get the bootloader lock on Verizon.
Do they still disallow APN changes, though? My Droid Turbo wasn't carrier locked, but the Globe SIM I tried to use when I was in the Philippines wouldn't work because it needed APN adjustments to function.
diesteldorf said:
I purchased 2 Essential phones from Sprint. In order to get them fully unlocked, they need to be active on Sprint for a minimum of 50 days.
This isn't a huge deal, since I am an active Sprint customer. I currently setup the first phone exactly as I like it, rooted, and restored all my apps with Titanium Backup. Currently running Android 7.1.1 NMJ32F, since I wasn't ready to flash the Oreo beta.
My plan is to use the first phone for 50 days, get it unlocked, wipe it, relock the bootloader, and give it to a relative to use on Verizon.
I will then start using the 2nd Essential phone on my Sprint line, unlock it after 50 days, and keep it for my personal use.
Question: Is there any possible issue that may arise if I use TWRP to make a full backup of Phone #1 and then restore that backup on Phone #2?
I am hoping TWRP would create phones that were identical in terms of apps, home screens, settings etc. Doing this would save me the time of having to setup two phones.
If this will work, does it even matter if the 2nd device is running the same software build version of Android, prior to me restoring the TWRP backup from the first device?
Click to expand...
Click to collapse
Should be no issue.
I would do a data and app restore and leave the OS alone.
But even if you restore everything as long as it is not EFS you should be fine.
That is exactly what I did when I got replacement phones.
qbanlinxx said:
As long as you don't backup and restore EFS, you should be fine. I've done this in the past with no issues
Click to expand...
Click to collapse
Do you (or anyone) have a link to a guide on this? I'm getting a replacement PH-1 tomorrow and it would be nice to just dupe my current phone.
GospelNerd said:
Do you (or anyone) have a link to a guide on this? I'm getting a replacement PH-1 tomorrow and it would be nice to just dupe my current phone.
Click to expand...
Click to collapse
No guide, but do a backup throu twrp minus efs. Transfer the backup to the PC. Unlock bootloader on the new phone, install twrp. Transfer backup to phone and restore backup and you should be golden.
qbanlinxx said:
No guide, but do a backup throu twrp minus efs. Transfer the backup to the PC. Unlock bootloader on the new phone, install twrp. Transfer backup to phone and restore backup and you should be golden.
Click to expand...
Click to collapse
Do you mean using TWRP from boot, like we do when flashing magisk, etc? I don't recall offhand the options presented as I haven't done it in a while, but I assume it'll be pretty obvious how to exclude EFS? Do I flash the correct boot.img before doing the backup? Thanks!
GospelNerd said:
Do you mean using TWRP from boot, like we do when flashing magisk, etc? I don't recall offhand the options presented as I haven't done it in a while, but I assume it'll be pretty obvious how to exclude EFS? Do I flash the correct boot.img before doing the backup? Thanks!
Click to expand...
Click to collapse
I haven't had the essential in a while, but yes boot into twrp. Once there you should see an option for backup. Honestly not sure about flashing the boot image. If the phone is in the same build you were on previously, I don't think it would be needed. My apologies, I've been using an s8+ and haven't used twrp in a while
i can confirm that cloning via twrp is working. i moved from a black moon ph-1 to a halo gray one. both where unlocked and rooted on oreo beta 8.1.
i made a backup of data partition via twrp and copied the content of /data/media manually (whilst in twrp). you have to boot once after flashing oreo and wiping.
my push tan app noticed the new hardware and stopped working so i had to receive new login crdentials from my bank. also signal stopped working and needed a new setup. i have to confirm every existing bluetooth connection for one time. that's all.
M!tch said:
i can confirm that cloning via twrp is working. i moved from a black moon ph-1 to a halo gray one. both where unlocked and rooted on oreo beta 8.1.
i made a backup of data partition via twrp and copied the content of /data/media manually (whilst in twrp). you have to boot once after flashing oreo and wiping.
Click to expand...
Click to collapse
Did TWRP ask you for a password? Mine did, but I don't know why. I assumed it had something to do w/ 8.1, but you're on it. So...
Also, to clarify, you're saying that you didn't clone the system, you just did the data partition? But you flashed and rooted 8.1 separately?
yes, i flashed full stock to make sure erverything is updated. maybe backup and restore system partition has the same effect.
you have to deactivate fingerprint and pin/pattern security to make sure twrp is able to show data.
I tried to do this with a replacement and overall it worked but it broke the fingerprint reader had to wipe it it fix it. I don't remember what I ended up doing or if I just restored from Google.
M!tch said:
yes, i flashed full stock to make sure erverything is updated. maybe backup and restore system partition has the same effect.
you have to deactivate fingerprint and pin/pattern security to make sure twrp is able to show data.
Click to expand...
Click to collapse
Worked for me taking the same path.
-Flashing up to the same version (I'm on 8.1 beta 1 [rooted]) was necessary to get on the same firmware build.
-adb push/pull is real handy for manually copying /data/media/ (/sdcard; including the TWRP backup) up to PC, then down to new phone
gk1984 said:
I tried to do this with a replacement and overall it worked but it broke the fingerprint reader had to wipe it it fix it. I don't remember what I ended up doing or if I just restored from Google.
Click to expand...
Click to collapse
Once I got it all restored including /data/media, my fingerprint reader wasn't working either. But, the Googs pulled up this beautiful doc some fine folks here put together ( @bmg1001 ?): https://media.readthedocs.org/pdf/mata/latest/mata.pdf which states...
If you move data between devices or change encryption and after restoring data from a twrp backup, you end up without a working fingerprint reader, delete /data/system/users/0/fpdata and /data/system/
users/0/settings_fingerprint.xml then you should be able to re-enroll fingerprints
Click to expand...
Click to collapse
^ I booted back into TWRP to do this, and it worked for me. Now all is good. New cloned phone is just like the old one w/broken screen which is going in the mailbox back to Essential.
my finperprint reader also wasn't working.
i've found the following solution in another thread.
konzi said:
[..]
Solution for fingerprinter:
Boot into TWRP
Go to advanced>filemanager to acces the files in your phone.
Enter the folder /data/system/user/0
Delete following files: ./fpdata/user.db, settings_fingerprint.xml
Reboot to system and set up new fingerprints with the fingerprint wizard
Everything should work normal
Hope it helps
Click to expand...
Click to collapse
Hi all, I thought I'd shout into the void to see if anyone can answer:
I broke the screen on my non-Sprint, unlocked, Magisk-rooted Ph-1. I bought a Sprint unlocked Ph-1 and have tried to clone from one to the other, but I am failing. I know I can just replace the screen, but I'd prefer to have a backup phone w/broken screen since the cost of the used Ph-1 was little more than the cost for the screen.
I've tried a bunch of different things, but the procedure has basically been:
Boot to bootloader
Install TWRP img
Install TWRP .zip
Wipe
Install LineageOS+MicroG zip, TWRP zip
Successfully boot to LineageOS
Reboot to TWRP
Restore data partition, restore /sdcard/ data manually, flash Magisk zip
Fail to boot, it'll then boot to TWRP
It also fails if I take a full image backup of the broken-screen phone with TWRP and attempt to restore that. I'm wondering if there's some sort of ID codes I need to wipe out, or if the Sprint and non-Sprint versions are sufficiently different that this won't work...can anyone solve this problem? I really like the Ph-1, it's got great build quality (have a look inside!), it's pretty, specs are plenty good enough for me. I'd like to get a backup / restore system going so that I can seamlessly switch between these two.