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.
Related
Hi everyone,
Google messed up ! I received the OTA for the 7.1.2 uptdate last thursday. After it my phone was unable to detect my SIM card, my IMEI number disappeared, neither base band.
The first thing i've tried is to get a new SIM card, with no result, then I tried a soft reset, an hard reset (factory reset+wipe data), and wiping the cache without any positive result either. I've contacted Google, the phone was from Google Store and my 1 year warranty expired on 25/03/17 (the update was installed on 05/04/17, exactly two week later), they refused to take it back, nor RMA, a shame! I think it will be the last Google phone I buy!
I've tried to flash the full factory image of 7.1.1. but nothing positive from it. I think the OTA corrupted my EFS data files but no idea on how to fix it. The thing is when i'm going to the bootloader, under barcodes menu i still find an IMEI number.
I don't know what to do now, I'm little bit desperate, if anyone have an advice here.:crying::crying:
Thank you in advance.
Nexus 6P
7.1.2 build N2G47H
kernel 3 .10.73-g0a21e4c
Bootloader locked
Unrooted
blckhwkone said:
Hi everyone,
Google messed up ! I received the OTA for the 7.1.2 uptdate last thursday. After it my phone was unable to detect my SIM card, my IMEI number disappeared, neither base band.
The first thing i've tried is to get a new SIM card, with no result, then I tried a soft reset, an hard reset (factory reset+wipe data), and wiping the cache without any positive result either. I've contacted Google, the phone was from Google Store and my 1 year warranty expired on 25/03/17 (the update was installed on 05/04/17, exactly two week later), they refused to take it back, nor RMA, a shame! I think it will be the last Google phone I buy!
I've tried to flash the full factory image of 7.1.1. but nothing positive from it. I think the OTA corrupted my EFS data files but no idea on how to fix it. The thing is when i'm going to the bootloader, under barcodes menu i still find an IMEI number.
I don't know what to do now, I'm little bit desperate, if anyone have an advice here.:crying::crying:
Thank you in advance.
Nexus 6P
7.1.2 build N2G47H
kernel 3 .10.73-g0a21e4c
Bootloader locked
Unrooted
Click to expand...
Click to collapse
Hello...
Unless you have a TWRP EFS backup, there's not much you can do...
I already saw some people saying that a restore from someone else EFS backup solved the problem and their proper IMEI, etc were back. I never had the issue, so I can't confirm it really works.
Now you need to find someone who can give it to you.
Otherwise you can RMA...
Good luck...
Is there any personal info in the efs backup? I would be happy to help but am not going to jeopardize privacy...
Sent from my Nexus 6 using XDA-Developers Legacy app
CyberpodS2 said:
Is there any personal info in the efs backup? I would be happy to help but am not going to jeopardize privacy...
Click to expand...
Click to collapse
Hello...
Since his IMEI disappeared, there must be infos about it somewhere in the EFS. I don't know what else...
Cheers...
CyberpodS2 said:
Is there any personal info in the efs backup? I would be happy to help but am not going to jeopardize privacy...
Click to expand...
Click to collapse
I think giving someone a copy of your efs partition essentially gives them the information needed to clone your phone, so it's not something you would want to do for a stranger.
blckhwkone said:
Hi everyone,
Google messed up ! I received the OTA for the 7.1.2 uptdate last thursday. After it my phone was unable to detect my SIM card, my IMEI number disappeared, neither base band.
The first thing i've tried is to get a new SIM card, with no result, then I tried a soft reset, an hard reset (factory reset+wipe data), and wiping the cache without any positive result either. I've contacted Google, the phone was from Google Store and my 1 year warranty expired on 25/03/17 (the update was installed on 05/04/17, exactly two week later), they refused to take it back, nor RMA, a shame! I think it will be the last Google phone I buy!
I've tried to flash the full factory image of 7.1.1. but nothing positive from it. I think the OTA corrupted my EFS data files but no idea on how to fix it. The thing is when i'm going to the bootloader, under barcodes menu i still find an IMEI number.
I don't know what to do now, I'm little bit desperate, if anyone have an advice here.:crying::crying:
Thank you in advance.
Nexus 6P
7.1.2 build N2G47H
kernel 3 .10.73-g0a21e4c
Bootloader locked
Unrooted
Click to expand...
Click to collapse
Google's been messing up along recently
blckhwkone said:
Google messed up !
Click to expand...
Click to collapse
Several people have been able to recover from this by wiping both the EFS partitions, but because your bootloader is locked (and USB debugging probably not enabled), I don't believe there is any way forward. See the link for the method used: http://www.theandroidsoul.com/fix-e...d-wifibluetooth-issues-restoring-twrp-backup/
Hi
I have Axon 7 A2017G. Bought from AliExpess in Feb of this year. It has been a very good phone so far with no issues. Well, at least until yesterday.
I was on Android 6 until yesterday when I found out that I can upgrade to Android 7.1.1. So, I stupidly upgraded to 7.1.1 (getting the upgrade from from ZTE) and now I have *lost my connectivity* (I am using three.co.uk sim). It doesn't recognise my sim card at all.
I have tried deleting and wiping the cache - no joy. Not sure what else to do.
I tried to use other upgrade from ZTE (Nougat to Marshmallow) and Marshmallow. Both fail with 'e footer is wrong e signature verification failed installation aborted'.
Everything else seems to be fine and I have had no issues with Axon 7 (had it since Feb) before the upgrade.
Hope someone can either help to get the connectivity back or somehow degrade my Android back to 6 (when it was all working fine).
Thanks Robie
SlickRobie said:
Hi
I have Axon 7 A2017G. Bought from AliExpess in Feb of this year. It has been a very good phone so far with no issues. Well, at least until yesterday.
I was on Android 6 until yesterday when I found out that I can upgrade to Android 7.1.1. So, I stupidly upgraded to 7.1.1 (getting the upgrade from from ZTE) and now I have *lost my connectivity* (I am using three.co.uk sim). It doesn't recognise my sim card at all.
I have tried deleting and wiping the cache - no joy. Not sure what else to do.
I tried to use other upgrade from ZTE (Nougat to Marshmallow) and Marshmallow. Both fail with 'e footer is wrong e signature verification failed installation aborted'.
Everything else seems to be fine and I have had no issues with Axon 7 (had it since Feb) before the upgrade.
Hope someone can either help to get the connectivity back or somehow degrade my Android back to 6 (when it was all working fine).
Thanks Robie
Click to expand...
Click to collapse
The problem is probably that you do not have an A2017G. Turn your phone around and tell me what the model erched into the back of the phone is. I suspect that you have an A2017, you didn't read the little paper that came with the phone that explained what they (the aliexpress seller) did with it, and you flashed an A2017G ROM on your A2017, effectively messing up the modem file.
I don't know if flashing through EDL fixes the issue, but it might be worth trying. It involves downloading a FULL_EDL package (the full system for your device model), then flashing it entirely through EDL.
The failproof method is to unlock the bootloader, flash TWRP, then flash the modem file corresponding to your device.
Choose an username... said:
The problem is probably that you do not have an A2017G. Turn your phone around and tell me what the model erched into the back of the phone is. I suspect that you have an A2017, you didn't read the little paper that came with the phone that explained what they (the aliexpress seller) did with it, and you flashed an A2017G ROM on your A2017, effectively messing up the modem file.
I don't know if flashing through EDL fixes the issue, but it might be worth trying. It involves downloading a FULL_EDL package (the full system for your device model), then flashing it entirely through EDL.
The failproof method is to unlock the bootloader, flash TWRP, then flash the modem file corresponding to your device.
Click to expand...
Click to collapse
Doh! Doh! Doh! :crying:
You are ABSOLUTELY correct. I didn't read that little paper that came with it because it was all Chinese - not English. Damn - why didn't I check. :crying:
When I bought it, the website said it was a 2017G model and therefore I assumed it was 2017G model.
Anyway, I don't understand some of the things you wrote (I am okay with upgrade and such like but not so much programming lark). What is this FULL_EDL package and how straight forward would it be for me to use it? Where do I get hold of it?
Everything is fine except phone call, sms and data of course. Internet connection is fine and all the apps works too.
Another question, would it help if I did a full factory reset and then applied the correct upgrade? I have backup of all my apps, contacts, pictures, music, etc.
Thanks
Robie
SlickRobie said:
Doh! Doh! Doh! :crying:
You are ABSOLUTELY correct. I didn't read that little paper that came with it because it was all Chinese - not English. Damn - why didn't I check. :crying:
When I bought it, the website said it was a 2017G model and therefore I assumed it was 2017G model.
Anyway, I don't understand some of the things you wrote (I am okay with upgrade and such like but not so much programming lark). What is this FULL_EDL package and how straight forward would it be for me to use it? Where do I get hold of it?
Everything is fine except phone call, sms and data of course. Internet connection is fine and all the apps works too.
Another question, would it help if I did a full factory reset and then applied the correct upgrade? I have backup of all my apps, contacts, pictures, music, etc.
Thanks
Robie
Click to expand...
Click to collapse
Not at all, this is much more messed up. A factory reset only wipes data, you need to fix a part of the system. If you are okay with unlocking your phone (i think you don't have warranty anyways) then you should do that, there are guides but be sure that they are FOR THE A2017!
After unlocking you need to install TWRP, those guides usually also explain you how to do this. Then you download this file and flash it through TWRP (put it in the phone, go to TWRP, Install - select the zip - swipe to start)
It may help understanding to know that there are 3 models.
A2017 is the Chinese one, A2017U is the American one and A2017G is multinational/European. There are different telephony frequency bands in use around the world and the Chinese one also has different storage and memory. A bit bummed they held that back from the rest of the world.....
Choose an username... said:
Not at all, this is much more messed up. A factory reset only wipes data, you need to fix a part of the system. If you are okay with unlocking your phone (i think you don't have warranty anyways) then you should do that, there are guides but be sure that they are FOR THE A2017!
After unlocking you need to install TWRP, those guides usually also explain you how to do this. Then you download [https:// androidfilehost.com/?fid=457095661767137840]this file and flash it through TWRP (put it in the phone, go to TWRP, Install - select the zip - swipe to start)
Click to expand...
Click to collapse
Thank you for quick response.
Yes, you are correct, warranty is non-issue anyway and I will make sure it is for A2017 (not A2017G/U). Wish I had just checked the back of the phone then I would not have ended up here but it is nice to learn new things, however painful..
Thanks for the heads up on the process as well. There goes my weekend but the boss (wife) is away so it is okay.
I will report if I manage to get it working next week. Wish me luck.
Robie
Update.
I spent the weekend on this and sadly didn't get anywhere. I followed the instructions and download from here:
http://https://forum.xda-developers.com/axon-7/how-to/guide-b13-chinese-a2017-root-unlock-t3549873.
Unfortunately, no joy. I can get my phone in EDL mode (drivers downloaded & suetup successfully, COM port is correct, etc) but the following commands just sit forever. They don't respond at all.
axon7backup.exe -p COM# -d
axon7root.exe -p COM# -r
Not sure where to go from here. If anyone has any ideas then please let me know.
Thanks.
Robie
1. Thanks to @FP_XDA and GSMZambia for the great directions found here
2. The other stuff and ideas:
The above method does put the U firmware on your phone. I had trouble getting it to connect to the network. I did try different combinations of files in the AP tar; CP; and CSC, but it would either not connect after a factory data reset or loop with the message about my SIM has changed, please restart.
I tried just flashing the following combinations through flashfire, but maybe this is a Sprint SIM issue and it works on other SIM cards; however, I have Sprint.
The U firmware seemed to work fine on the software. Including boot.img in flashfire would take away the eng_boot and root. I just had trouble connecting to the Sprint network.
Do you need to use the v5 combo file and flash a certain CP/CSC before going through the rooting steps? The U firmware CSC file is different in size, so is it a partition (PIT) issue since that will write the cache.img.ext4 file and those vary in size from stock to the U? Is there a certain order to flash in flashfire to get it to work properly?
Anyway, I downloaded several U CSC firmwares (XAA, XAS, SPR (last two are sprint)), but ran into some network issue every time. The operating system seemed stable, but the lack of connection and some random entries under settings make it so close, but yet so far.
I don't mind the Sprint firmware, but can you unlock additional LTE bands if you use the stock sprint firmware on another carrier?
Thanks for any help!
Here is more info about the Settings submenu options:
Here is some more detailed info:
The submenus under settings give me options like K twophoneservice; T roaming; Giga LTE. I think it is CSC related as those carriers are Korean based. I think this may be my issue along with a few others I've seen on reddit. Just wondering why it says that though. I used the G930U version, so not sure why this would appear.
Any help or suggestions?
Thanks
Bootloop
Did you get Oreo working while running on v5? Have followed steps in that video but the phone always gets stuck in a boot loop. I extracted the latest Oreo files from the AP file and every seems to flash right but gets stuck in a boot loop after flashfire reboots. Have tried multiple times with same result. Would rather not upgrade to v6 but was trying to get Oreo working.
Aggiedude said:
Did you get Oreo working while running on v5? Have followed steps in that video but the phone always gets stuck in a boot loop. I extracted the latest Oreo files from the AP file and every seems to flash right but gets stuck in a boot loop after flashfire reboots. Have tried multiple times with same result. Would rather not upgrade to v6 but was trying to get Oreo working.
Click to expand...
Click to collapse
I didn't try Oreo, but I didn't have any success getting Nougat to work. It would install and run fine, but I never got it to connect to a network. I tried flashing different imgs and making zip files with additional files to add to the system and same result. I do have additional LTE bands unlocked (12,13,17), but since I still have sprint, I have no way to test it.
I assume that everything would work normal except for VoLTE, but I think you could add that with root.
lvpre said:
I didn't try Oreo, but I didn't have any success getting Nougat to work. It would install and run fine, but I never got it to connect to a network. I tried flashing different imgs and making zip files with additional files to add to the system and same result. I do have additional LTE bands unlocked (12,13,17), but since I still have sprint, I have no way to test it.
I assume that everything would work normal except for VoLTE, but I think you could add that with root.
Click to expand...
Click to collapse
You have to follow the other guide on here about disabling packages. The only problem: you can't disable packages anymore with the apps from the play store. Samsung stopped that. There are system level applications that are blocking you from connecting to sprints network after flashing eng_boot. My guess is you flashed eng_boot, phone booted, then shutdown and reboot, now no network connection? This happens with the binary 4 version as well. I have been on nougat rooted using U firmware for a good while. I once had to re-install everything and when I went to disable the apps, I couldn't. There is a way to disable them via ADB but its not easy and requires patience. But once those packages are disabled, you will have a perfectly running phone with root.
Here are the packages:
XMayhem2099 said:
7. Disable the following packages via bk or adhell
Chameleon
Sprint OMADM
Sprint OMADM Phone Interface
MDMApp
SecurityLogAgent
Security Policy Updates
Security Storage
Click to expand...
Click to collapse
I came here looking to see if the same eng_boot works on Oreo. Guess I will just have to go ahead and try it myself
elesbb said:
You have to follow the other guide on here about disabling packages. The only problem: you can't disable packages anymore with the apps from the play store. Samsung stopped that. There are system level applications that are blocking you from connecting to sprints network after flashing eng_boot. My guess is you flashed eng_boot, phone booted, then shutdown and reboot, now no network connection? This happens with the binary 4 version as well. I have been on nougat rooted using U firmware for a good while. I once had to re-install everything and when I went to disable the apps, I couldn't. There is a way to disable them via ADB but its not easy and requires patience. But once those packages are disabled, you will have a perfectly running phone with root.
Here are the packages:
I came here looking to see if the same eng_boot works on Oreo. Guess I will just have to go ahead and try it myself
Click to expand...
Click to collapse
The version used by GSMZambia includes a boot.img file, which removes the eng_boot and root after a factory reset. It sounds like you are actually still b4 for everything. This version is for people on b5/6 and want to install the U firmware. However, you are correct about disabling those packages when rooting on the U firmware. You lose root and eng_boot by flashing the stock boot.img in flashfire. The point is to have the U firmware without root on a b5/6 Sprint S7/Edge.
Maybe it would work if you flash the eng_boot again and disable, but then you are stuck on the eng_boot. Plus it messes with Knox, so I'm not sure if something like SABS or Adhell would even work.
lvpre said:
The version used by GSMZambia includes a boot.img file, which removes the eng_boot and root after a factory reset. It sounds like you are actually still b4 for everything. This version is for people on b5/6 and want to install the U firmware. However, you are correct about disabling those packages when rooting on the U firmware. You lose root and eng_boot by flashing the stock boot.img in flashfire. The point is to have the U firmware without root on a b5/6 Sprint S7/Edge.
Maybe it would work if you flash the eng_boot again and disable, but then you are stuck on the eng_boot. Plus it messes with Knox, so I'm not sure if something like SABS or Adhell would even work.
Click to expand...
Click to collapse
But from what I read in the original post is that BEFORE using flashfire to flash the original boot.img, you are running the eng_boot.img. Is this correct? Btw, flashfire NEEDS root. So you ARE rooted at some point. Therefore, this is why you are being kicked from the network. Thus, disabling those packages will prevent that. But SABS and Adhell no longer work, at least I couldn't get them to. I even paid for the one and used it once. So I'm a bit annoyed with that. But yes, I am still on binary 4 for the BL. It was a requirement when purchasing my phone on Craigslist xD
But, what you are after may not be feasible. This is what you want: 100% U firmware on Sprint Binary > 4 WITHOUT eng_boot?
I always thought the whole point of being on U firmware was for root access though. But anyhow, once you get the U firmware flashed, which BL version is on the device? Is this an exploit that allows for older Binary to be flashed?
I'm intrigued by this method for other reasons. I would really REALLY love for a custom boot.img to be allowed but you can't. If this method is a way to block checking of BL, AP, etc hash checks, then the similar method should be possible for a custom recovery and custom kernel. I miss my kernel.
elesbb said:
But from what I read in the original post is that BEFORE using flashfire to flash the original boot.img, you are running the eng_boot.img. Is this correct? Btw, flashfire NEEDS root. So you ARE rooted at some point. Therefore, this is why you are being kicked from the network. Thus, disabling those packages will prevent that. But SABS and Adhell no longer work, at least I couldn't get them to. I even paid for the one and used it once. So I'm a bit annoyed with that. But yes, I am still on binary 4 for the BL. It was a requirement when purchasing my phone on Craigslist xD.
Click to expand...
Click to collapse
AdHell 3 still works on Nougat at least. You have to get the newer version because Samsung changed their SDK keys program. I'm not on Oreo, so I'm not sure if it will work. But if you are rooted, you have better options. If you need the new version of AdHell3, I'll post a link.
But, what you are after may not be feasible. This is what you want: 100% U firmware on Sprint Binary > 4 WITHOUT eng_boot?
Click to expand...
Click to collapse
Basically, when you finish. You'll have the U firmware on the phone, but the BL with still be 5/6. So some things like Knox, System Updates, etc..won't work because of the conflict and will say the phone has been compromised. Also, the phone doesn't bootloop because of those items you need to disable, because you did it before using flashfire.
It works fine after applying the changes after rooting, but it is after the flashfire flash and factory reset that doesn't. Modem you can flash, but the CSC files mostly get erased because parts of them are install to the system with the rom. When you check, the phone has no CSC setup available. Which is why it probably displays Korean carrier settings since that is the default with CSC files present.
I always thought the whole point of being on U firmware was for root access though. But anyhow, once you get the U firmware flashed, which BL version is on the device? Is this an exploit that allows for older Binary to be flashed? .
Click to expand...
Click to collapse
The original point of U firmware was to get rid of carrier bloatware and the ability to use most carriers easily with most addons (VoLTE) available.
I'm intrigued by this method for other reasons. I would really REALLY love for a custom boot.img to be allowed but you can't. If this method is a way to block checking of BL, AP, etc hash checks, then the similar method should be possible for a custom recovery and custom kernel. I miss my kernel.
Click to expand...
Click to collapse
So in conclusion, you have the U4 firmware running on a Sprint S7 with b5/6 installed without root. Since the phone runs fine with the U firmware, something is causing connection issues to Sprint. I assume he is in Africa (Zambia) and by using a GSM only sim card, it will work.
Unless you want to upgrade to b5/6 and try it, that's probably the only true way to test it. Plus, who wants to be on b4 anyway?
lvpre said:
AdHell 3 still works on Nougat at least. You have to get the newer version because Samsung changed their SDK keys program. I'm not on Oreo, so I'm not sure if it will work. But if you are rooted, you have better options. If you need the new version of AdHell3, I'll post a link.
Click to expand...
Click to collapse
Yeah I am currently rooted with the U firmware BL4. I want to upgrade to Oreo, hoping for performance improvements, better battery, etc. But I guess since the Oreo U firmware is still BL4, I can just downgrade if I can't get root back.
Basically, when you finish. You'll have the U firmware on the phone, but the BL with still be 5/6. So some things like Knox, System Updates, etc..won't work because of the conflict and will say the phone has been compromised. Also, the phone doesn't bootloop because of those items you need to disable, because you did it before using flashfire.
Click to expand...
Click to collapse
I never mentioned a bootloop? Is this about something else? The point I am trying to address is the loss of Sprint connectivity after flashing eng boot. This is because of the packages that need to be disabled.
It works fine after applying the changes after rooting, but it is after the flashfire flash and factory reset that doesn't. Modem you can flash, but the CSC files mostly get erased because parts of them are install to the system with the rom. When you check, the phone has no CSC setup available. Which is why it probably displays Korean carrier settings since that is the default with CSC files present.
Click to expand...
Click to collapse
So you flash everything, eng boot, and are currently rooted. You then flash the provided file via flash fire, factory reset, and now you no longer are able to connect to Sprint network? When you say "can't connect to Sprint network", are you referring to data or to Sprint network entirely? If you go under your "about phone" section, what does your IMEI and phone number display? Don't actually type it here, but it should be something comprehensible. It shouldn't say "unknown" or a bunch of zeros, etc. [/quote]
The original point of U firmware was to get rid of carrier bloatware and the ability to use most carriers easily with most addons (VoLTE) available.
Click to expand...
Click to collapse
True..
So in conclusion, you have the U4 firmware running on a Sprint S7 with b5/6 installed without root. Since the phone runs fine with the U firmware, something is causing connection issues to Sprint. I assume he is in Africa (Zambia) and by using a GSM only sim card, it will work.
Unless you want to upgrade to b5/6 and try it, that's probably the only true way to test it. Plus, who wants to be on b4 anyway?
Click to expand...
Click to collapse
I do. A lot of people want to be back to BL4. There is NO difference in the newer bootloaders EXCEPT a special "key" type of thing that prevents downgrading. That is the only thing different. This is why the U firmware is still on BL4 despite having an Oreo update. Sprint changes the BL version just so people like us have extra hurdles to overcome when we want something different. Its very stupid tbh.
But, I would like to help you guys out, however, I AM NOT upgrading to the BL5/6. Noway nohow.
It actually shows a crossed out circle for the signal strength in the status bar. I'm pretty sure I tried it by flashing just the system and system with boot, which removes the root. Even entering apn info had slight issues.
I was hoping someone with more knowledge and a b5\6 phone would give this a whirl. If you get bored, maybe it would be like you flashing the U firmware with b2.
My wife's phone is still b4, so at least one of us didn't get the Sprint screw.
lvpre said:
It actually shows a crossed out circle for the signal strength in the status bar. I'm pretty sure I tried it by flashing just the system and system with boot, which removes the root. Even entering apn info had slight issues.
I was hoping someone with more knowledge and a b5\6 phone would give this a whirl. If you get bored, maybe it would be like you flashing the U firmware with b2.
My wife's phone is still b4, so at least one of us didn't get the Sprint screw.
Click to expand...
Click to collapse
Hmm. That's weird. What does your about phone section say for IMEI and phone number? Everything good? I wonder if something is affecting the PRL. Try updating that via settings menu before you flash the firmware and factory reset. The CSC shouldn't really affect that part. I have changed mine multiple times to just eff around and see what/if anything changed. Its more for the phone to know what menu options are available and such. For instance, call recording shows up when its not a US branded carrier.
Sadly I will never flash the newer BL. But I will definitely keep trying via the thread and if you would like to discord or something similar I would be down. School starts in about 2 weeks so I'm basically free till then
sim boot loop
I have the same issue. I can install the g930u Nougat firmware on my BLv5 Sprint phone (you seem to need BLv6 for Oreo), however, the phone will not connect to the sprint network. I flashed the cache.img file and it does the same thing. It forces you to reboot to finish setup then errors out on the blue sim card screen in recovery. I removed the AutoPreconfig app through adb shell to bypass the forced reboot and tried to just select Sprint as the network under connection settings where you can search for available carriers. That too failed...it just sat there for a while then said that it couldn't connect and shows the emergency calls only as the network up top and low signal bars.
Aggiedude said:
I have the same issue. I can install the g930u Nougat firmware on my BLv5 Sprint phone (you seem to need BLv6 for Oreo), however, the phone will not connect to the sprint network. I flashed the cache.img file and it does the same thing. It forces you to reboot to finish setup then errors out on the blue sim card screen in recovery. I removed the AutoPreconfig app through adb shell to bypass the forced reboot and tried to just select Sprint as the network under connection settings where you can search for available carriers. That too failed...it just sat there for a while then said that it couldn't connect and shows the emergency calls only as the network up top and low signal bars.
Click to expand...
Click to collapse
Thanks for posting this!!! I'm glad that I wasn't the only having this issue. I tried it again using a different method and still got the SIM boot loop. This method probably works great if you have anything other than Sprint or Sprint MVNO, but something is conflicting like it does during a typical root of the G930P. Anyway, hopefully, someone else will be able to figure this out.
Hello yall!
So I am at a complete loss on how to fix the issues with my Essential device.
So I decided to post here in as much detail as I can and hopefully receive some answers.
I purchased my phone used from eBay about a month ago.
According to the listing it was factory unlocked.
I have AT&T prepaid.
Everything was running smoothly for about a week until I receive the notification for the Android Pie OTA.
(At this time my bootloader was not yet unlocked nor was I rooted).
Again everything was fine UNTIL I installed the security patch update.
As soon as I installed and rebooted my sim read as invalid.
I rebooted, tried to mess with network settings, factory reset, etc.
Turning to Google, I realize this is a common issue with the Sprint variant of this device (of course my luck would be for me to unknowingly purchase the Sprint variant not knowing there was any issues) and the pie update.
The main fix for this issue would be of course to downgrade back to Android 8.
Here's my issues...
I unlock my bootloader.
Install the Android 8 firmware from the official Essential site. (made sure to install the one for Sprint variant).
Flash.
The touch screen is not functional. At all.
Flash back to Android Pie and install TWRP
Flash Android 8 custom ROM.
Touch screen still not functional.
So I'm back on Android Pie and touch screen is working, but sim is still invalid.
How are other essential users successful in downgrading the software?
HELP.
stephxo said:
Hello yall!
So I am at a complete loss on how to fix the issues with my Essential device.
So I decided to post here in as much detail as I can and hopefully receive some answers.
I purchased my phone used from eBay about a month ago.
According to the listing it was factory unlocked.
I have AT&T prepaid.
Everything was running smoothly for about a week until I receive the notification for the Android Pie OTA.
(At this time my bootloader was not yet unlocked nor was I rooted).
Again everything was fine UNTIL I installed the security patch update.
As soon as I installed and rebooted my sim read as invalid.
I rebooted, tried to mess with network settings, factory reset, etc.
Turning to Google, I realize this is a common issue with the Sprint variant of this device (of course my luck would be for me to unknowingly purchase the Sprint variant not knowing there was any issues) and the pie update.
The main fix for this issue would be of course to downgrade back to Android 8.
Here's my issues...
I unlock my bootloader.
Install the Android 8 firmware from the official Essential site. (made sure to install the one for Sprint variant).
Flash.
The touch screen is not functional. At all.
Flash back to Android Pie and install TWRP
Flash Android 8 custom ROM.
Touch screen still not functional.
So I'm back on Android Pie and touch screen is working, but sim is still invalid.
How are other essential users successful in downgrading the software?
HELP.
Click to expand...
Click to collapse
Go to the guide section and read the post that says uicc unlock there is a solution outlined.just follow it and your phone will be back in service
stephxo said:
Hello yall!
So I am at a complete loss on how to fix the issues with my Essential device.
So I decided to post here in as much detail as I can and hopefully receive some answers.
I purchased my phone used from eBay about a month ago.
According to the listing it was factory unlocked.
I have AT&T prepaid.
Everything was running smoothly for about a week until I receive the notification for the Android Pie OTA.
(At this time my bootloader was not yet unlocked nor was I rooted).
Again everything was fine UNTIL I installed the security patch update.
As soon as I installed and rebooted my sim read as invalid.
I rebooted, tried to mess with network settings, factory reset, etc.
Turning to Google, I realize this is a common issue with the Sprint variant of this device (of course my luck would be for me to unknowingly purchase the Sprint variant not knowing there was any issues) and the pie update.
The main fix for this issue would be of course to downgrade back to Android 8.
Here's my issues...
I unlock my bootloader.
Install the Android 8 firmware from the official Essential site. (made sure to install the one for Sprint variant).
Flash.
The touch screen is not functional. At all.
Flash back to Android Pie and install TWRP
Flash Android 8 custom ROM.
Touch screen still not functional.
So I'm back on Android Pie and touch screen is working, but sim is still invalid.
How are other essential users successful in downgrading the software?
HELP.
Click to expand...
Click to collapse
Did you unlock your critical partitions along with the bootloader?
arjunv said:
Go to the guide section and read the post that says uicc unlock there is a solution outlined.just follow it and your phone will be back in service
Click to expand...
Click to collapse
Do you think you could link that post for me? I can't seem to find it.
I also don't see any uicc option on my debice. (Not sure or that matters though)
If it's Sprint you need to wait 50 days before you can unlock it. CDMA phones are a pain in the ass to unlock, always buy International if possible!
This thread has some information that might be useful:
https://forum.xda-developers.com/essential-phone/help/unlock-sprint-version-t3720727
Sent from my PH-1 using XDA Labs
SuperBrolySSJ said:
Did you unlock your critical partitions along with the bootloader?
Click to expand...
Click to collapse
This is required for the touch screen firmware to be flashed and OP needs to see this.
Hi, I have to say I didn't expect that this would be such a ride when I got into this. I am now simply trying to have a working phone again.
I will briefly sum up what I've done so far :
So I got a brand new V20 a few weeks ago with the intention to root it and install a custom rom. It came as a H91010l with a security patch from dec 2016.
I got everything ready it took a while but then went ahead and followed this guide [LS997|VS995|H910|F800L] DirtySanta Bootloader unlock and Root guide by me2151
A few minor hicups on the way but I got the bootloader unlocked, twrp installed and then LOS 18.1. I thought everything would be fine and I didn't make a backup... It worked well except that I had no mobile data (French carrier SFR), only sms worked and also some notification issues.
After a break and looking for solutions I tried another OS tonight (/e/) and the same issues were present. No mobile network.
It's not to do with the APN (which I made sure was configured properly) but likely some incompatibility after tweaking the system with the root procedure. Maybe something to do with US996 files being used.
So I decide that I needed to go back to stock since I wouldn't find a solution from there and I did a wipe before flashing a stock US996 firmware in TWRP taken in this thread, the US99610f - SPL 2016-12-01
Result : I lost the fast boot and TWRP, the phone is stuck on the LG logo.
Only one thing works at this point, firmware update download mode, so I did a full partition dl flash of the following H91510e_00_VTR_CA_OP_1205 kdz which according to many posts should be fine. Nope, it doesn't boot it's stuck on the LG logo.
I have tried a second one that is old, US99610f_00_1205 kdz which should work too. It boots and I get into setup but it reboots within a minute/30s on top of being really slow.
So what I'm looking for right now is a solution to go back to stock. I have no backup and no root. I can only use LGUP. And it seems that my model is pretty non cooperative. What can I do ?
Thank you.
I was going to follow the instructions in this post and install the F800K10e.kdz but the lg-firmwares.com website is limiting me to 2 files per 24h so I decided to give the H91510e_00_VTR_CA_OP_1205.kdz another go. It wouldn't boot again until I formatted the data, it seems to be working so far.
I'm sure this is some noobie knowledge but most posts/guides didn't say to do that and I am indeed a beginner. I will update this thread with information on what I do next if relevant and if I can get my mobile data working somehow.
Edit : SMS work, 4G works but the sim card crashes when I call or get called.
Unfortunately I didn't even try my sim card when I got the phone so maybe it was the same onthe H91010l. Looks like I'll have to redo the unlocking procedure and continue fixing this mess.
Edit 2 : Notifications don't work properly either like on the custom roms... For example skype messages.
Xanvast said:
Hi, I have to say I didn't expect that this would be such a ride when I got into this. I am now simply trying to have a working phone again.
I will briefly sum up what I've done so far :
So I got a brand new V20 a few weeks ago with the intention to root it and install a custom rom. It came as a H91010l with a security patch from dec 2016.
I got everything ready it took a while but then went ahead and followed this guide [LS997|VS995|H910|F800L] DirtySanta Bootloader unlock and Root guide by me2151
A few minor hicups on the way but I got the bootloader unlocked, twrp installed and then LOS 18.1. I thought everything would be fine and I didn't make a backup... It worked well except that I had no mobile data (French carrier SFR), only sms worked and also some notification issues.
After a break and looking for solutions I tried another OS tonight (/e/) and the same issues were present. No mobile network.
It's not to do with the APN (which I made sure was configured properly) but likely some incompatibility after tweaking the system with the root procedure. Maybe something to do with US996 files being used.
So I decide that I needed to go back to stock since I wouldn't find a solution from there and I did a wipe before flashing a stock US996 firmware in TWRP taken in this thread, the US99610f - SPL 2016-12-01
Result : I lost the fast boot and TWRP, the phone is stuck on the LG logo.
Only one thing works at this point, firmware update download mode, so I did a full partition dl flash of the following H91510e_00_VTR_CA_OP_1205 kdz which according to many posts should be fine. Nope, it doesn't boot it's stuck on the LG logo.
I have tried a second one that is old, US99610f_00_1205 kdz which should work too. It boots and I get into setup but it reboots within a minute/30s on top of being really slow.
So what I'm looking for right now is a solution to go back to stock. I have no backup and no root. I can only use LGUP. And it seems that my model is pretty non cooperative. What can I do ?
Thank you.
Click to expand...
Click to collapse
If you did not make a dump backup there is not much you can do that I know of. You can try and delete the modemst1 and modemst2 and see if that fixes your no signal issue.
hold vol down plug phone into computer USB cable.
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
restart phone into os see if that fixes the issue.
If so make a backup of you EFS in twrp and save it.
Your EFS got corrupted when you flashed the stock KDZ to root the H910 happen to me also. This would explain why your phone is crashing and no signal.
Darnrain1 said:
If you did not make a dump backup there is not much you can do that I know of. You can try and delete the modemst1 and modemst2 and see if that fixes your no signal issue.
hold vol down plug phone into computer USB cable.
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
restart phone into os see if that fixes the issue.
If so make a backup of you EFS in twrp and save it.
Your EFS got corrupted when you flashed the stock KDZ to root the H910 happen to me also. This would explain why your phone is crashing and no signal.
Click to expand...
Click to collapse
I didn't flash any kdz to root initially. I just started flashing stuff once I lost my bootloader and TWRP. I managed to have the H91510e working that's where I'm at currently as per the second post. I will try and root it again following this procedure soon. I have to look into why I can't call or get called first. We'll see what happens, but according to this thread I will lose mobile network when I root the H915 version. I'll see when I get there.
Xanvast said:
Hi, I have to say I didn't expect that this would be such a ride when I got into this. I am now simply trying to have a working phone again.
I will briefly sum up what I've done so far :
So I got a brand new V20 a few weeks ago with the intention to root it and install a custom rom. It came as a H91010l with a security patch from dec 2016.
I got everything ready it took a while but then went ahead and followed this guide [LS997|VS995|H910|F800L] DirtySanta Bootloader unlock and Root guide by me2151
A few minor hicups on the way but I got the bootloader unlocked, twrp installed and then LOS 18.1. I thought everything would be fine and I didn't make a backup... It worked well except that I had no mobile data (French carrier SFR), only sms worked and also some notification issues.
After a break and looking for solutions I tried another OS tonight (/e/) and the same issues were present. No mobile network.
It's not to do with the APN (which I made sure was configured properly) but likely some incompatibility after tweaking the system with the root procedure. Maybe something to do with US996 files being used.
So I decide that I needed to go back to stock since I wouldn't find a solution from there and I did a wipe before flashing a stock US996 firmware in TWRP taken in this thread, the US99610f - SPL 2016-12-01
Result : I lost the fast boot and TWRP, the phone is stuck on the LG logo.
Only one thing works at this point, firmware update download mode, so I did a full partition dl flash of the following H91510e_00_VTR_CA_OP_1205 kdz which according to many posts should be fine. Nope, it doesn't boot it's stuck on the LG logo.
I have tried a second one that is old, US99610f_00_1205 kdz which should work too. It boots and I get into setup but it reboots within a minute/30s on top of being really slow.
So what I'm looking for right now is a solution to go back to stock. I have no backup and no root. I can only use LGUP. And it seems that my model is pretty non cooperative. What can I do ?
Thank you.
Click to expand...
Click to collapse
I know what's wrong. You cant use lineageos to make calls on AT&T network. You can get internet but no VoLTE. So your going to have to use a deblaoted Stock Oreo rom if you want a rooted phone with phone calls.
Custom Stock Oreo Rom Debloated & DeGoogled for the H910 & Most Lgv20 phones. VoLTE and WiFi-Calling working.
Darnrain1 said:
I know what's wrong. You cant use lineageos to make calls on AT&T network. You can get internet but no VoLTE. So your going to have to use a deblaoted Stock Oreo rom if you want a rooted phone with phone calls.
Custom Stock Oreo Rom Debloated & DeGoogled for the H910 & Most Lgv20 phones. VoLTE and WiFi-Calling working.
Click to expand...
Click to collapse
Thanks for your reply. I am using SFR, a French carrier. Is it the same issue ?
There has been developments since my last post. I started from the H91510e like I said and followed the [ROOT] HOWTO: AT&T H910 up to v20g (FULLY TESTED) guide by runningnak3d supported by a video from NewTechBegins. It went well until the flashing from TWRP.
I think it was my mistake to do like the video and flash h910-10r.rar followed by Magisk-v19.0. This resulted in not being able to boot, I kept getting the secure boot with password even after formatting. And after a couple of times it turned into a green screen crash. I couldn't get to recovery either for some reason even though I'm sure it was still there. The corruption warning message would appear almost instantly at boot and not allow me to do the volume down + power shortcut, and fastboot reboot recovery would not work either.
Reflashing the H91510e with LGUP worked but the system was particularly slow at first, it seemed to do better after a few minutes. Going over everything again, the part where we boot into recovery for the first time ended up the same with a green screen crash.
What seems to have solved it is to flash boot1.img from the root package in this [LS997|VS995|H910|F800L] DirtySanta Bootloader unlock and Root guide by me2151, which is different from the boot without extension of the other guide. I also reflashed the recovery several times, it didn't change anything until this.
I will continue updating this thread with the results of what follows next. I just have to install the h91010r now and manage to get to setup.
Edit : I just installed the h91010r with having wiped + formatted before and formatted after, it still goes into secure boot...
Xanvast said:
Thanks for your reply. I am using SFR, a French carrier. Is it the same issue ?
There has been developments since my last post. I started from the H91510e like I said and followed the [ROOT] HOWTO: AT&T H910 up to v20g (FULLY TESTED) guide by runningnak3d supported by a video from NewTechBegins. It went well until the flashing from TWRP.
I think it was my mistake to do like the video and flash h910-10r.rar followed by Magisk-v19.0. This resulted in not being able to boot, I kept getting the secure boot with password even after formatting. And after a couple of times it turned into a green screen crash. I couldn't get to recovery either for some reason even though I'm sure it was still there. The corruption warning message would appear almost instantly at boot and not allow me to do the volume down + power shortcut, and fastboot reboot recovery would not work either.
Reflashing the H91510e with LGUP worked but the system was particularly slow at first, it seemed to do better after a few minutes. Going over everything again, the part where we boot into recovery for the first time ended up the same with a green screen crash.
What seems to have solved it is to flash boot1.img from the root package in this [LS997|VS995|H910|F800L] DirtySanta Bootloader unlock and Root guide by me2151, which is different from the boot without extension of the other guide. I also reflashed the recovery several times, it didn't change anything until this.
I will continue updating this thread with the results of what follows next. I just have to install the h91010r now and manage to get to setup.
Click to expand...
Click to collapse
I would flash Auto_Debloat you get Oreo Debloat rom.
Custom Stock Oreo Rom Debloated & DeGoogled for the H910 & Most Lgv20 phones. VoLTE and WiFi-Calling working.
But to answer your question a lot of cell carriers are going to VoLTE only and LOS does not have that on the H910.
I made Auto_Debloat so if you need help just let me know.
Darnrain1 said:
I would flash Auto_Debloat you get Oreo Debloat rom.
Custom Stock Oreo Rom Debloated & DeGoogled for the H910 & Most Lgv20 phones. VoLTE and WiFi-Calling working.
But to answer your question a lot of cell carriers are going to VoLTE only and LOS does not have that on the H910.
I made Auto_Debloat so if you need help just let me know.
Click to expand...
Click to collapse
I added an edit at the bottom of my post, it displays the warning really quick and goes into secure boot everytime. Could it be that the h910-10r.rar package you shared at the end of the thread is not identical to the original post ? It simply won't boot into setup for me. Any ideas ?
I will try installing something quick tonight to have a working system with recovery I'm done messing around for the day. I will look into your custom rom in the coming days thanks for your help !
Xanvast said:
I added an edit at the bottom of my post, it displays the warning really quick and goes into secure boot everytime. Could it be that the h910-10r.rar package you shared at the end of the thread is not identical to the original post ? It simply won't boot into setup for me. Any ideas ?
I will try installing something quick tonight to have a working system with recovery I'm done messing around for the day. I will look into your custom rom in the coming days thanks for your help !
Click to expand...
Click to collapse
Yes your data partition is encrypted still. You need to format it in twrp.
Darnrain1 said:
Yes your data partition is encrypted still. You need to format it in twrp.
Click to expand...
Click to collapse
That's the thing, it still goes into secure boot after formatting it.
So I flashed the boot1 again and twrp to be safe, it now doesn't display the warning anymore but goes into the green screen crash after a minute or so.
I'm now back to twrp, I'll just wipe everything and install LOS to try. If at least it has mobile data that would be more than before.
Xanvast said:
That's the thing, it still goes into secure boot after formatting it.
So I flashed the boot1 again and twrp to be safe, it now doesn't display the warning anymore but goes into the green screen crash after a minute or so.
I'm now back to twrp, I'll just wipe everything and install LOS to try. If at least it has mobile data that would be more than before.
Click to expand...
Click to collapse
Yes you need a kernel. Your still running stock kernel that's why your getting the green screen.
Darnrain1 said:
Yes you need a kernel. Your still running stock kernel that's why your getting the green screen.
Click to expand...
Click to collapse
Oh I see now, so it's indeed not the same package. That is why you had to flash H910_BTTF-mk2000.zip
Thanks for your time and patience.
I installed LOS 18.1 and it works fine with 4G this time (before reading your reply). Unsurprisingly calls in and out make the phone kernel crash with a black screen. I really like LOS and android 11, is there something I can do to make calls work ? Like flashing another kernel ? Does /e/OS have the same issue ?
If not I can absolutely live without calls for the moment, no problem.
Edit : I'm not getting notified of messages for Discord/Skype and not getting the call if the app is not open actively. Seems like it's not running the services in the background.
Xanvast said:
That's the thing, it still goes into secure boot after formatting it.
So I flashed the boot1 again and twrp to be safe, it now doesn't display the warning anymore but goes into the green screen crash after a minute or so.
I'm now back to twrp, I'll just wipe everything and install LOS to try. If at least it has mobile data that would be more than before.
Click to expand...
Click to collapse
It's complicated,
Xanvast said:
Oh I see now, so it's indeed not the same package. That is why you had to flash H910_BTTF-mk2000.zip
Thanks for your time and patience.
I installed LOS 18.1 and it works fine with 4G this time (before reading your reply). Unsurprisingly calls in and out make the phone kernel crash with a black screen. I really like LOS and android 11, is there something I can do to make calls work ? Like flashing another kernel ? Does /e/OS have the same issue ?
If not I can absolutely live without calls for the moment, no problem.
Click to expand...
Click to collapse
Yep your welcome, no problem. You may just need to setup LOS with your network provider. Do a google search for APN carrier settings for your cell provider. Take care.
Darnrain1 said:
It's complicated,
Yep your welcome, no problem. You may just need to setup LOS with your network provider. Do a google search for APN carrier settings for your cell provider. Take care.
Click to expand...
Click to collapse
That's the first thing I've done, I entered the APN settings from this page (3), and the results reported are from after. So do you know about other OS like /e/, any that would not behave the same ? Or anything I can flash on top to fix it ?
Have a good evening.
Xanvast said:
That's the first thing I've done, I entered the APN settings from this page (3), and the results reported are from after. So do you know about other OS like /e/, any that would not behave the same ? Or anything I can flash on top to fix it ?
Have a good evening.
Click to expand...
Click to collapse
I am in the USA so it's in the afternoon for me.
You may want to try and flash you EFS from fastboot mode.
Manually reinstall your EFS on the Lgv20.
You need to find your Original DUMP of the rom your Lgv20 phone was on, before you downgraded your firmware for rooting.
Note: COM21 is what ever com port you were using at the time.
Reboot into fastboot mode
With the phone powered off hold the down vol and plug in usb to computer.
Info on what the files are
/fsg
A backup of your modemst1 and modemst2 files. So if you erase modemst1 and modemst2 /fsg should restore the partitions automatically. But if /fsg is corrupted then it will not restore them.
/misc
This partition contains miscellaneous system settings.
/modemst1 /modemst2
Modemst1 and modemst2 store information like IMEI.
fastboot flash fsg fsg_COM21
fastboot flash misc misc_COM21
fastboot flash modemst1 modemst1_COM21
fastboot flash modemst2 modemst2_COM21
fastboot reboot
Darnrain1 said:
I am in the USA so it's in the afternoon for me.
You may want to try and flash you EFS from fastboot mode.
Manually reinstall your EFS on the Lgv20.
You need to find your Original DUMP of the rom your Lgv20 phone was on, before you downgraded your firmware for rooting.
Note: COM21 is what ever com port you were using at the time.
Reboot into fastboot mode
With the phone powered off hold the down vol and plug in usb to computer.
Info on what the files are
/fsg
A backup of your modemst1 and modemst2 files. So if you erase modemst1 and modemst2 /fsg should restore the partitions automatically. But if /fsg is corrupted then it will not restore them.
/misc
This partition contains miscellaneous system settings.
/modemst1 /modemst2
Modemst1 and modemst2 store information like IMEI.
fastboot flash fsg fsg_COM21
fastboot flash misc misc_COM21
fastboot flash modemst1 modemst1_COM21
fastboot flash modemst2 modemst2_COM21
fastboot reboot
Click to expand...
Click to collapse
Unfortunately as stated in my first post, I have no backup of the state of the phone when I got it as a H91010l. I didn't do one either while on the H91510e because I didn't see the point, it was already modified and calling didn't work.
Thank you for the explanation.
Something I'd like to mention for other readers is that there is one main visible difference between the first root (from H91010l with the old guide) and second one (H91510e with newer guide). The first time the warning message with the red triangle during boot was very distorted and duplicated. It was unreadable. Now it is clear. I don't know enough to say what was causing it or point at what made 4G work in the second case but this was something worth noting.
Alright, going into this de-Googling trip I did not know that many apps relied on Google Play Services to work and the Google cloud services, Firebase cloud etc... to send their notifications. I had no idea that Google was managing the notifications for most of the world and so much more. That only reinforces my desire to get away from it.
So these apps like Discord, Skype and others that don't send notifications it's directly because of the lack of Google Play Services. I noticed today that MicroG has a Cloud Messaging option but I will not enable it.
Signal works fine without any of it. I also found Skype Lite to send notifications so that's what I'll use from now on. Discord is going into the trash. I've read that Telegram is supposed to work too. So another problem solved. I have no issues making concessions on my convenience to be freer.
A website I came across which references how apps behave without Google : https://plexus.techlore.tech/
Darnrain1 said:
It's complicated,
Xanvast said:
Oh I see now, so it's indeed not the same package. That is why you had to flash H910_BTTF-mk2000.zip
Thanks for your time and patience.
I installed LOS 18.1 and it works fine with 4G this time (before reading your reply). Unsurprisingly calls in and out make the phone kernel crash with a black screen. I really like LOS and android 11, is there something I can do to make calls work ? Like flashing another kernel ? Does /e/OS have the same issue ?
If not I can absolutely live without calls for the moment, no problem.
Edit : I'm not getting notified of messages for Discord/Skype and not getting the call if the app is not open actively. Seems like it's not running the services in the background.
Click to expand...
Click to collapse
Yep your welcome, no problem. You may just need to setup LOS with your network provider. Do a google search for APN carrier settings for your cell provider. Take care.
Click to expand...
Click to collapse
I took photos of my Kernel crashes, now it doesn't just happen with calls, which I could live with but also while using Skype Lite and looking out of the app for example, when I'm doing something taxing for the device or sometimes the phone would just reboot. Several times a day.
It seems to be very similar to what is mentioned in this post. Do you or anybody think that I should do the same and flash h915freedommobilemodem.img ? How do I go about it if so ? Is that something you do in fastboot ?
Also what are the risks if it goes bad ? I'm tired of dealing with repairing the mess and I'd like to avoid more problems.
Thanks.
Xanvast said:
I took photos of my Kernel crashes, now it doesn't just happen with calls, which I could live with but also while using Skype Lite and looking out of the app for example, when I'm doing something taxing for the device or sometimes the phone would just reboot. Several times a day.
It seems to be very similar to what is mentioned in this post. Do you or anybody think that I should do the same and flash h915freedommobilemodem.img ? How do I go about it if so ? Is that something you do in fastboot ?
Also what are the risks if it goes bad ? I'm tired of dealing with repairing the mess and I'd like to avoid more problems.
Thanks.
Click to expand...
Click to collapse
If I am not mistaken your running LineageOS. I would ask in that post for help. I run Stock Oreo on my H910 because everything works.
[OFFICIAL] LineageOS 18.1 for the LG V20
Darnrain1 said:
If I am not mistaken your running LineageOS. I would ask in that post for help. I run Stock Oreo on my H910 because everything works.
[OFFICIAL] LineageOS 18.1 for the LG V20
Click to expand...
Click to collapse
Yes the post is in that thread. I didn't have this problem the first time I used LOS 3 weeks ago so I assume it has to do with the green screen crash caused by the kernel I didn't flash after the h910-10r.rar. So it's still unaddressed in my opinion. Should I go ahead and flash that missing kernel or the H915 modem ? I don't know what's the difference and both seem plausible.
It's fine if you aren't sure and I will end up asking there.