Hit the thanks button and Enjoy. Any problems let me and others here know. Dirty flash the updates NOT the initial flash of this rom but the updates to it. As of 9-3-18 i will be switching to Ubuntu 18.04 Bionic Beaver, that being said i do not know if i will have to change anything or do anything different to keep pushing these updates out but i will most definitely try to keep them coming.
Data and SIM fixed
Rom Zip = flash this https://www.androidfilehost.com/?fid=673956719939835046, Gapps, and SuperSU
after the rom has booted up install root browser and navigate to the the ROM zip, extract build.prop in system folder and replace the one in your new root/system folder with it and reboot your phone.
Update
4-17-18
https://www.androidfilehost.com/?fid=746010030569969556 replace build.prop in root/system with the one in the ROM zips system/build.prop after boot then reboot
4-24-18
https://www.androidfilehost.com/?fid=673956719939836755
its got root built in but, If you are updating and already had supersu then you will have to flash the supersu zip anyways or it will say the binary is occupied. If you are not updating all you need is to install the supersu.apk . Data and SIM is working. After the rom boots up and you have root and a root browser replace the phones system/build.prop with the one in this zips system/build.prop and reboot. follow this process if there are any future updates.
5-2-2018
https://www.androidfilehost.com/?fid=818222786056028458
No special directions root is not built in
5-13-18
https://www.androidfilehost.com/?fid=890278863836285207
No special directions root is not built in
5-20-18
https://www.androidfilehost.com/?fid=746163614322265526
5-31-18
https://www.androidfilehost.com/?fid=890278863836288847
7-28-18
https://www.androidfilehost.com/?fid=5862345805528060531
9-3-18
https://www.androidfilehost.com/?fid=1322778262903997130
10-07-18
https://www.androidfilehost.com/?fid=1322778262904022217
10-10-18
https://www.androidfilehost.com/?fid=1322778262904024839
12-7-18
https://www.androidfilehost.com/?fid=11410963190603868410
12-15-18
https://www.androidfilehost.com/?fid=11410963190603875897
2-24-19
https://www.androidfilehost.com/?fid=1395089523397901058
3-24-19
https://www.androidfilehost.com/?fid=1395089523397924748
5-6-19
http://download1486.mediafire.com/5...73/lineage-14.1-20190507-UNOFFICIAL-d2att.zip
Temporary link due to problems with AFH
I Have Added the OTA-Updater App (More details in the last pages of this thread)
8-7-19
https://www.androidfilehost.com/?fid=6006931924117931911
ditched ota updater
10-11-19
https://www.androidfilehost.com/?fid=1899786940962606099
recommend clean flash (built with different computer and proprietary blobs pulled directly from stock nj2 device plus some from an early build of this rom),
not built with su or ota updater (I experienced issues with ota updater because of download link problems) ,
also I do not have anything to do with the security patches, they are released to the source when they are ready. The patch level to this build is Sept. 5.
My apologies for the lapse in updates, and responses.
setprop persist.lineage.nofool true in terminal emulator with root privs (type su first grant permission then setprop persist.lineage.nofool true) gets rid of persistant notification
Bluetooth dialtone when playing music fix
Settings > Battery > tap in 3-dot menu at top right tap on Battery optimisation. To show all apps and services here, select the ‘All apps’ options under the dropdown. Tap on both of the Bluetooth services and change them to Don't optimise.
First of all, thank you for taking on this task as this is a nice device to this day.
Installed to test with the following results in regards to sim card / mobile data.
Upon setup, no sim card detected and no baseband or imei. Restarting with same results and certain obvious settings greyed out. I think your endeveor is most positive. Again, thank you...
N/A
Joker1716 said:
You have a ROM where the sim works try this https://forum.xda-developers.com/galaxy-note-3/help/solution-lineage-os-sim-t3640689 page 1 of the thread if you want I do not have a sim at all or I would
Click to expand...
Click to collapse
Sim still not working after doing this.
DerPuGNa said:
Sim still not working after doing this.
Click to expand...
Click to collapse
Did you mess with any settings under cellular networks? And there is a sim status option in the about phone/status? I don't have a sim or service so I can't help in that area
DerPuGNa said:
Sim still not working after doing this.
Click to expand...
Click to collapse
Samsung phone info and test apk in play store
DerPuGNa said:
Sim still not working after doing this.
Click to expand...
Click to collapse
I noticed the I was on nj1 and the rom is for nj2 so I flashed this it may fix it it may not but it's the modem and bootloader for nj2
https://androidfilehost.com/?fid=24052804347797347
Chuckles5150 said:
First of all, thank you for taking on this task as this is a nice device to this day.
Installed to test with the following results in regards to sim card / mobile data.
Upon setup, no sim card detected and no baseband or imei. Restarting with same results and certain obvious settings greyed out. I think your endeveor is most positive. Again, thank you...
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=24052804347797347 bootloader and modem for nj2 flashable zip the rom is made around nj2 so you may need to flash this to get data just a suggestion
I needed nj2 for my sim to work with carbon, so that makes sense. I'll flash this later.
Joker1716 said:
https://androidfilehost.com/?fid=24052804347797347 bootloader and modem for nj2 flashable zip the rom is made around nj2 so you may need to flash this to get data just a suggestion
Click to expand...
Click to collapse
Yeah thanks, been running NJ2 for a long time. I'll look into some things soon.
Has anyone tried the settings/system profiles/default/settings I noticed that the default configuration is not setup so either turning system profiles off or configuring them accordingly may help. You may have to configure them then reboot. I wish I could help more but I can not being as I don't have a sim. I only use wifi on this phone.
Joker1716 said:
Did you mess with any settings under cellular networks? And there is a sim status option in the about phone/status? I don't have a sim or service so I can't help in that area
Click to expand...
Click to collapse
I didn't mess anything about sim or related to sim.
Joker1716 said:
I noticed the I was on nj1 and the rom is for nj2 so I flashed this it may fix it it may not but it's the modem and bootloader for nj2
https://androidfilehost.com/?fid=24052804347797347
Click to expand...
Click to collapse
I've flash this and still nothing. If you look closely into the settings, I've manage to have a signal because I revert back to OCT N OS. Because I need to copy the lib-sec.ro from the working ROM and paste it to the Linage OS.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Joker1716 said:
Has anyone tried the settings/system profiles/default/settings I noticed that the default configuration is not setup so either turning system profiles off or configuring them accordingly may help. You may have to configure them then reboot. I wish I could help more but I can not being as I don't have a sim. I only use wifi on this phone.
Click to expand...
Click to collapse
Disabled this setting and still nothing. Tried everything you've said. Replace the Lib-sec.ro, flash the NJ2 modem. still nothing. I've notice that baseband and IMEI is unknown at the Linage OS.
*#*#4636#*#* is a testing menu.
I have contacted lineage about the sim and data problem to see if they know what the deal is now its a waiting game. The other variants I have built for (d2spr,d2tmo) have no issues as of yet hopefully there will be a solution soon.
Joker1716 said:
*#*#4636#*#* is a testing menu.
Click to expand...
Click to collapse
Unknown IMEI as i said.
DerPuGNa said:
Unknown IMEI as i said.
Click to expand...
Click to collapse
Got it to recognise the baseband and imei its a small process I will get the file uploaded and directions posted shortly
DerPuGNa said:
Unknown IMEI as i said.
Click to expand...
Click to collapse
I have been up for days trying to figure out this problem. I believe I have found the solution, as i do not have a SIM i cant fully test but i did get the Rom to recognize the efs information. This is the process:
Rom Zip = flash this https://www.androidfilehost.com/?fid=673956719939835046, Gapps, and SuperSU
after the rom has booted up install root browser and navigate to the the ROM zip, extract build.prop in system folder and replace the one in your new root/system folder with it and reboot your phone.
I did all that and included a screenshot in the previous post
please let me know how it worked for you you may still need to disable system profiles and work with the settings after the sim is recognized
Joker1716 said:
I have been up for days trying to figure out this problem. I believe I have found the solution, as i do not have a SIM i cant fully test but i did get the Rom to recognize the efs information. This is the process:
First install the Rom from the first post in the thread 4-13-18
Second install the GAPPS and SuperSU
Third install root browser navigate to root/system/build.prop and copy it onto your sdcard
Fourth dirty flash this Rom Zip = https://www.androidfilehost.com/?fid=962187416754475323 or this if sim still isnt recognized https://www.androidfilehost.com/?fid=673956719939835046 and SuperSU
Fifth after the rom has booted up open root browser navigate to the place where you copied the build.prop to and replace the one in your new root/system with it and reboot your phone. If sim still is not recognized flash the second links ROM zip and continue with the instructions.
I did all that and included a screenshot in the previous post
please let me know how it worked for you you may still need to disable system profiles and work with the settings after the sim is recognized
Click to expand...
Click to collapse
"Rom from the first post in the thread 4-13-18" where is it?
instead of installing the rom and copy the build.prop, can I just copy and past the build.prop from the zip? i think that will save a lot of time?
DerPuGNa said:
"Rom from the first post in the thread 4-13-18" where is it?
instead of installing the rom and copy the build.prop, can I just copy and past the build.prop from the zip? i think that will save a lot of time?
Click to expand...
Click to collapse
The first post in this thread the ROM link dated 4-12-18 my bad and yes you can
Joker1716 said:
The first post in this thread the ROM link dated 4-12-18 my bad and yes you can
Click to expand...
Click to collapse
You could just install one of the ROMs in the solution post and extract the build.prop from the zip and paste it in the root/system folder it would save a lot of time but I wanted to be thorough
Related
This is only what has worked for me i take no responsibility for anyones phone catching fire after following my guide/advice. Tested myself on a UK D802 16GB on Three Network! Confirmed working on 32GB devices now too!!
This needs formatting to make it easier to read. I will get around to it but here is the basic info needed!
Please READ this entire first post before asking questions that are already answered.
Today i have managed to flash the European Open Kitkat rom and root it and keep TWRP recovery. It worked for me but can't guarantee the same results for you.
Prerequisites. (Skip this if you already have rooted JB rom with custom recovery)
First i downgraded to Jellybean using this guide. I downgraded to "UK Open 16GB D80210B_00.kdz" i'm not sure if that's required though.
Then I rooted it using IORoot.
Then i installed TWRP using Freegee from the Play Store.
From here you are ready to flash or you can start from here if you already have root and recovery on Jellybean.
You need these three files.
1. My modded Stock rom zip.
Mirror 1 | Mirror 2
2. Savoca Modded Boot.img.
3. SuperSU ZIP.
Now to flash! (Take out your simcard first.)
1. Boot into TWRP and flash the modded stock rom DOWNLOAD 1. It will take a while and the screen may turn off during this, just press power button. Ignore the failed error!
2. Now go to main TWRP screen and select Reboot Recovery. (Wouldn't mount system otherwise!)
3. Now go to Mount and make sure System is ticked. (Not sure if required but do it anyway!)
4. Now flash Savoca's modified boot.img DOWNLOAD 2.
5. Again go to Mount and make sure System is selected.
6. Now flash SuperSU ZIP DOWNLOAD 3.
7. Now i wiped data here not sure if it's required as the rom wipes system but do it anyway!
8. Replace sim and reboot and all should be well!
If you have NO MOBILE NETWORK i got this error and that's why i recommended removing sim card. I had to repeatedly toggle wifi on and off, and airplane mode and restarted a few times. Not sure what fixed it but don't panic it DOES work.
Bugs and Fixes!
Audio Hissing/Crackling on Headphones.
This is present on all Kitkat roms currently. Some users don't get it most do. Type of headphones seems to be a factor. The following fix is temporary and will revert after a reboot. So needs to be repeated if your phones reboots for any reason.
Type in phone dial pad 3845#*802# and it will show Hidden Service Menu.
Click on "ELT Test", select "Manual Mode" and select "Test Start".
With headphones plugged in select "Audio Loopback" and than select "Test Start".
Blow gently into the microphone and keep on this test 20 seconds or more.
Once done back out and play music. Enjoy!
No LTE/4G anymore?
It seems to require a change of bands for some to get LTE working. There is a value to edit in build.prop. You can do this manually with a root explorer and setting correct permissions after changing, I've found the easiest way is to download JRummy Build.prop editor from market.
Open the Build Prop Editor app.
Find the value "ro.telephony.default_network" and select it.
Notice the property value will be set to "9". Change this to "11" and let the app reboot phone.
If you still don't have LTE try again but change the value to "13" and let the app reboot phone.
Bluetooth Battery Drain
This is NOT real battery drain so please don't worry about it. It is a falsely reported statistic. I get battery life on a par with 4.2.2. Around 8 hours screen on time which is fantastic! If you have battery drain please try a full wipe, don't restore apps from another rom do it manually. Take a look at your apps.
How is it done?!
The modded zip is stripped down to include only the System, Modem and Cust partitions. These are all that is required for Kitkat to play nice with Savocas modified boot.img. I edited the updater-script to remove the entries for all partitions except those listed above and repacked it up nicely to flash. So it is possible to do this with any future updates too. The Cust partition is necessary in case your partition has old carrier stuff still on there, this flashes a clean Cust partition.
Thanks to:
LenAsh for the flashable zip i modded.
Savoca for the modded Boot.img and modules.
Chainfire for SuperSU.
Jesus for blessing all the little children.
it would be great if you also make one for the 32gb version
anyways, great work, dude!
I'm flashing it right now and looking up your address at the same time in case it won't work ;]
How long should it take to boot ?
superbonto said:
it would be great if you also make one for the 32gb version
anyways, great work, dude!
Click to expand...
Click to collapse
As i've said it seems like there isn't a difference between md5's of 32gb and 16gb versions of Kitkat i just wouldn't want to say test it... But in theory it should work just fine.
paniczklos said:
I'm flashing it right now and looking up your address at the same time in case it won't work ;]
How long should it take to boot ?
Click to expand...
Click to collapse
Let me know how it goes...you know just to give me a running start I assume you're 16GB user? It doesn't take long to boot but if it loops make sure you have wiped data in recovery. It is safe to do factory reset in standard recovery too as i tried it when trying to get my network back on!
ephumuris said:
As i've said it seems like there isn't a difference between md5's of 32gb and 16gb versions of Kitkat i just wouldn't want to say test it... But in theory it should work just fine.
Let me know how it goes...you know just to give me a running start I assume you're 16GB user? It doesn't take long to boot but if it loops make sure you have wiped data in recovery. It is safe to do factory reset in standard recovery too as i tried it when trying to get my network back on!
Click to expand...
Click to collapse
I'm preparing a dead fish to throw it on your doormat ;p
I'm on 12th minute of booting - LG logo and led flashing green-to-blue.
And yes I'm 16GB
How to use the standard recovery ?
Is it repeatedly making the boot sound? Hold power button and volume down until LG logo flashes up, then release power button and press again whilst keeping hold of volume. You should get a white screen. Just press power twice i think that should reset it.
I'm pretty sure it didn't take me 12 minutes to boot
Can you please tell us how to mod the original EUR kdz? I can't download 2 gigabytes now and I already have the kdz file. Is there any guide?
Thanks ephumuris
Hey TC i have a lg g2 16gb that i bought from amazon. I am also on the three network in the uk. I do not get 4g option on my phone. Sorry for OT but i havent met anyone else on here using three and g2. Any help would be appreciated.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my LG-D802 using Tapatalk
SPBoss said:
Hey TC i have a lg g2 16gb that i bought from amazon. I am also on the three network in the uk. I do not get 4g option on my phone. Sorry for OT but i havent met anyone else on here using three and g2. Any help would be appreciated. View attachment 2630159
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
What rom are you running? I get the option for gsm/wcdma/lte auto. Although no 4g for me on Three in Hull yet.
badchip said:
Can you please tell us how to mod the original EUR kdz? I can't download 2 gigabytes now and I already have the kdz file. Is there any guide?
Thanks ephumuris
Click to expand...
Click to collapse
I'm guessing there is some sort of tool to extract the KDZ files and then all you need out of that is system.img and modem.bin and cust.bin... Easy to make an update script or i can upload one for you. I've never needed to extract a KDZ though...
ephumuris said:
Is it repeatedly making the boot sound? Hold power button and volume down until LG logo flashes up, then release power button and press again whilst keeping hold of volume. You should get a white screen. Just press power twice i think that should reset it.
I'm pretty sure it didn't take me 12 minutes to boot
Click to expand...
Click to collapse
Doing that boots the TWRP. i've wiped the data like a satan, in every possible way. There's no boot loop - it's just booting and booting and booting. I think I'll have to go back to stock and repeat. Or is there any way to upload files to the phone through recovery (I remeber there was this option in clokcwork recovery ) ?
paniczklos said:
Doing that boots the TWRP. i've wiped the data like a satan, in every possible way. There's no boot loop - it's just booting and booting and booting. I think I'll have to go back to stock and repeat. Or is there any way to upload files to the phone through recovery (I remeber there was this option in clokcwork recovery ) ?
Click to expand...
Click to collapse
I'm not sure if there is an option in TWRP i've certainly not seen it. I find it strange that you are getting stuck at boot screen... Maybe it matter which JB rom you come from?
My original one was 80210B Euro open rom.
"UK Open 16GB D80210B_00.kdz"
ephumuris said:
I'm not sure if there is an option in TWRP i've certainly not seen it. I find it strange that you are getting stuck at boot screen... Maybe it matter which JB rom you come from?
My original one was 80210B Euro open rom.
"UK Open 16GB D80210B_00.kdz"
Click to expand...
Click to collapse
D80210A_00.kdz - it's EUR open + OTA update to E version.
I'm trying do sideload the files through ADB ;/
ephumuris said:
I'm guessing there is some sort of tool to extract the KDZ files and then all you need out of that is system.img and modem.bin and cust.bin... Easy to make an update script or i can upload one for you. I've never needed to extract a KDZ though...
Click to expand...
Click to collapse
Thanks, I found this guide but it doesn't mention the download from Savoca. Should I just follow it (and use the KKROM_template.zip)? Or what do you recommend? I really can't to flash KK with root on my device
paniczklos said:
D80210A_00.kdz - it's EUR open + OTA update to E version.
I'm trying do sideload the files through ADB ;/
Click to expand...
Click to collapse
The starting rom is the only thing i can think of that could make a difference if you followed instructions exactly all the factors are the same besides that!
It would help if anyone else has downloaded it and flashed successfully or unsuccessfully to let us know!
badchip said:
Thanks, I found this guide but it doesn't mention the download from Savoca. Should I just follow it (and use the KKROM_template.zip)? Or what do you recommend? I really can't to flash KK with root on my device
Click to expand...
Click to collapse
That guide will give you a rooted Kitkat rom but no custom recovery. Which is a risky position to be in
Although the tool would be useful in that thread it would allow you to get the system.img, modem.bin and cust.bin you need. I could then provide a blank update zip with just the correct updater-script for you?
ephumuris said:
The starting rom is the only thing i can think of that could make a difference if you followed instructions exactly all the factors are the same besides that!
It would help if anyone else has downloaded it and flashed successfully or unsuccessfully to let us know!
Click to expand...
Click to collapse
I'm downloading the UK open EUR and I'll start over.
ephumuris said:
That guide will give you a rooted Kitkat rom but no custom recovery. Which is a risky position to be in
Although the tool would be useful in that thread it would allow you to get the system.img, modem.bin and cust.bin you need. I could then provide a blank update zip with just the correct updater-script for you?
Click to expand...
Click to collapse
I would very much appreciate that. I have used the tool to extract the kdz and dz. I have the files in screenshot now.
Whats the proper next step?
Thanks for your help
edit: The meta-inf folder is from the KK template provided in that thread, I suppose I don't need that.
Hi!
Firstly thanks for this!
and secondly i have to say that i already flashed to my LG G2 32gb and works like a charm... btw i also did it with another way:
1-Downgrade to 4.2.2.
2-when your in v.4.2.2 root and recovery.
3-i used lastest CWM version from Philz.
4-FLash your Rom.zip
5-reboot to recovery. (Dunno if this is really necessary but just in case i did it too)
6-Flash Savoca Patched
7-Flash Root
8-Reboot
9-ENjoy EUR 20b =)
Thanks!
Great to confirm working on 32gb too. Badchip you might have to wait til later unless you can use that existing meta inf folder. I've just left for work so not at laptop.
Try deleting every file but only keep.
Meta inf folder.
System.IMG
Modem.bin
Custom.bin
Zip those up and flash them. Should work if the update script is right in meta inf folder.
@iall5tar What base jellybean rom did you downgrade to?
And regarding custom recovery it should work with any cwm philz or twrp. I just referenced twrp as that's what I use.
Sent from my LG-D802 using Tapatalk
What you mean about folder meta-inf? im not a expert i just want to give a try and it worked xD
I flashed 4.4.4 and i cant get the voicemail button on the dialer to work. Everytime i press it it shows a menu to add the voicemail number then i go into the settings and its disabled.
I am enclosing screenshots to better describe the problem. I cant post links because of post count. So please copy and paste into your browser to view the images.
puu.sh/cQp2F/3c1b377c2e.png
puu.sh/cQoAV/13f823059b.png
jobrien2001 said:
I flashed 4.4.4 and i cant get the voicemail button on the dialer to work. Everytime i press it it shows a menu to add the voicemail number then i go into the settings and its disabled.
I am enclosing screenshots to better describe the problem. I cant post links because of post count. So please copy and paste into your browser to view the images.
puu.sh/cQp2F/3c1b377c2e.png
puu.sh/cQoAV/13f823059b.png
Click to expand...
Click to collapse
I can't see the images.
You didn't say how or which 4.4.4 you flashed.
Was it the stock firmware, or a custom ROM? How did you flash: OTA, TWRP, CWM or ODIN?
What were you running before?
Did you do a wipe before you flashed?
Have you tried flashing the full stock firmware twice, without rebooting which is recommended with 4.4.4
Rob
rlichtefeld said:
I can't see the images.
You didn't say how or which 4.4.4 you flashed.
Was it the stock firmware, or a custom ROM? How did you flash: OTA, TWRP, CWM or ODIN?
What were you running before?
Did you do a wipe before you flashed?
Have you tried flashing the full stock firmware twice, without rebooting which is recommended with 4.4.4
Rob
Click to expand...
Click to collapse
Hello,
I uploaded the images to imgur if you have any trouble viewing them. I would place full links but the forum wont let me. Copy and paste please.
i.imgur.com/GfLr6KI.png
i.imgur.com/8JGxMV3.png
I was on 4.4.2 before
Also I add another screenshot which shows my software versions
i.imgur.com/u9z8pLt.png
I did a full wipe. Actually not sure, i used CWM and used the option on the menu to do a "clean wipe for a new rom".
I flashed stock 4.4.4 firmware using ODIN.
Then i odin CF auto root, then i odin CWN.
No, i havent flashed twice without rebooting. how do i accomplish that? everytime i flash it reboots. Also how can i perform a full wipe?
jobrien2001 said:
Hello,
I uploaded the images to imgur if you have any trouble viewing them. I would place full links but the forum wont let me. Copy and paste please.
i.imgur.com/GfLr6KI.png
i.imgur.com/8JGxMV3.png
I was on 4.4.2 before
Also I add another screenshot which shows my software versions
i.imgur.com/u9z8pLt.png
I did a full wipe. Actually not sure, i used CWM and used the option on the menu to do a "clean wipe for a new rom".
I flashed stock 4.4.4 firmware using ODIN.
Then i odin CF auto root, then i odin CWN.
No, i havent flashed twice without rebooting. how do i accomplish that? everytime i flash it reboots. Also how can i perform a full wipe?
Click to expand...
Click to collapse
I've attached what my Call Settings says, not the same as yours, and I'm running stock 4.4.4. Mine say "Voice Mail", yours says "My Carrier"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My Phone Info shows the same info as yours.
If you did a Wipe for ROM from CWM that should do it.
As to how to flash twice:
Flash the first time, make sure that the ODIN check box for reboot is off. When flash is complete, remove the battery by pulling it, don't press any buttons. Then, wait minute or two, and replace the battery. Go directly to Download Mode and flash a 2nd time. Then, you can let the phone boot into the system.
At that point, before you flash anything else - try the Voicemail.
One, more thing where did you download your 4.4.4 firmware? These are the two that should work:
http://forum.xda-developers.com/galaxy-s4-tmobile/general/firmwares-official-mdl-mk2-nb4-t2816508
http://www.sammobile.com/firmwares/download/34779/M919UVUFNH7_M919TMBFNH7_TMB.zip/
Rob
Hi again,
I think i got the file from the first link the mega one. I just run check on it i got:
M919UVUFNH7_M919TMBFNH7_M919UVUFNH7_HOME.tar.md5
md5 8c0e22bc2acccb82418a7cd97121968f
sha1 4fd6bb73fed26f5adc73edb9e168ad119f7dc0a1 d2636786
I am going to flash twice and report back.
well i flashed twice with odin, all stock, same problem.
Is there an alternate dialer i can use that replaces the built in one?
jobrien2001 said:
well i flashed twice with odin, all stock, same problem.
Is there an alternate dialer i can use that replaces the built in one?
Click to expand...
Click to collapse
Does Visual Voicemail work?
Could it be your SIM? How old/new is your SIM.
Another thought is that since you are on a stock ROM, the T-Mobile store may be able to help or calling 611. You could tell them you took the OTA update, and this is what happened.
Rob
lordena and
rlichtefeld said:
Does Visual Voicemail work?
Could it be your SIM? How old/new is your SIM.
Another thought is that since you are on a stock ROM, the T-Mobile store may be able to help or calling 611. You could tell them you took the OTA update, and this is what happened.
Rob
Click to expand...
Click to collapse
Its unlocked and from another carrier. And yes the SIM card is new 2 weeks maybe. Think that could be it? i dont recall the voicemail working on the new sim.
jobrien2001 said:
Its unlocked and from another carrier. And yes the SIM card is new 2 weeks maybe. Think that could be it? i dont recall the voicemail working on the new sim.
Click to expand...
Click to collapse
I would guess that non-TMO carrier has more to do with it than the version. You didn't say which other company's network you were using, but you may want to ask on this thread about the issue:
http://forum.xda-developers.com/galaxy-s4-tmobile/help/using-t-mobile-m919-att-network-t2880349
Rob
jobrien2001 said:
Its unlocked and from another carrier.
Click to expand...
Click to collapse
Wait a minute..... Um that's your problem most likely. Regardless what carrier you're on you need to flash the firmware for your model. What model or what carrier is your phone originally from.
ShinySide said:
Wait a minute..... Um that's your problem most likely. Regardless what carrier you're on you need to flash the firmware for your model. What model or what carrier is your phone originally from.
Click to expand...
Click to collapse
The phone is originally t mobile SGH-M919. I bought an unlock code and my current carrier is movistar (telefonica) peru.
Here is the stock 14.5.A.0.270 (5.0.2) customized AU odexed, pre-rooted, highly debloated and bundled up with PRFCreator
BEFORE and AFTER:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ZIP ARCHIVE INCLUDES:
a) the rom itself (removed bunch of crapware)
b) SuperSU-2.49-BETA
c) Nuts Dual Recovery 2.8.15
d) DRM Function Restoration for UB
STEPS:
1) backup
2) wipe /system, /cache, /dalvik-cache
3) flash the main rom
4) flash google services removal.zip (optional)
5) boot up phone and go through setup
6) flash further debloat (optional)
DOWNLOADS:
Main
Google Services Removal
Further Debloat
Maybe a noob question: Flashing your ROM means I will have my DRM functions restored?
Papanik said:
Maybe a noob question: Flashing your ROM means I will have my DRM functions restored?
Click to expand...
Click to collapse
I'm interested in this as well. Does flashing your rom restore BIONZ processing, making all the steps in the linked thread un-necesarry?
Also, anyway to check if BIONZ is working or not?
Papanik said:
Maybe a noob question: Flashing your ROM means I will have my DRM functions restored?
Click to expand...
Click to collapse
zgomot said:
I'm interested in this as well. Does flashing your rom restore BIONZ processing, making all the steps in the linked thread un-necesarry?
Also, anyway to check if BIONZ is working or not?
Click to expand...
Click to collapse
I'm currently on a locked bootloader so I can't verify if it'll work without having to flash an ftf with TA beforehand. Best thing to do is try it yourself.
If x-reality is working, bionz is working.
I flashed this ROM and my Z1 does not boot at all. When i press the power button, it vibrates once and that's all.
I flashed a stock rom, re-installed recovery and created a pre-rooted zip based on the SG customized firmware. The result was the same. Black screen, no sign of activity.
Does anyone have any idea what could be wrong here?
My device is a C6903 and worked just fine with the pre-rooted .242
Thanks!
facing problems...
After i do google and further debloat... dun even have app store to install my apps. I also unable to add my google account at Settings > Accounts...
Its great to have a RAM free rom... but what the point of having so much ram when there's nothing else u can do with the phone. I did try installing Google Play Store apk but it just simply crashes...
Please dun be offended as I still feel this ROM is a well done rom, I might just missed out something.
kedirakevo said:
After i do google and further debloat... dun even have app store to install my apps. I also unable to add my google account at Settings > Accounts...
Click to expand...
Click to collapse
The google debloat is only optional. If you don't flash it, you'll get to keep the play store.
I personally don't use the play store and download my apps from apkmirror or evozi
Okay, can share more what does further debloat do? I can do that without google debloat right?
kedirakevo said:
Okay, can share more what does further debloat do?
Click to expand...
Click to collapse
Further debloat removes some of the bloat that I forgot to remove from the main rom itself and also the setup wizards. So make sure to use it only after booting your device and going through the setup.
I can do that without google debloat right?
Click to expand...
Click to collapse
Yes.
I've tried flashing this twice and have ended up softbricking twice. I think the issue may be because of the wiping of system, which I have honestly never had to do before, so I'll try once again, and if it doesn't work I guess I'll just find something else.
EDIT: Yep, nothing I do seems to really be working, probably just getting bad downloads on my end though.
compatible with c6902?
Is this compatible with xperia z1 ,c6902?
Zerousen said:
I've tried flashing this twice and have ended up softbricking twice.
Click to expand...
Click to collapse
Do you have a c6903 and on latest kitkat(.108) or .242?
ravishmahur said:
Is this compatible with xperia z1 ,c6902?
Click to expand...
Click to collapse
Nope.
How to flash Xposed in this rom please? Thanks
Ahki767 said:
Here is the stock 14.5.A.0.270 (5.0.2) customized AU odexed, pre-rooted, highly debloated and bundled up with PRFCreator
edited
Click to expand...
Click to collapse
Flashed without issues coming from CM12.1 (the terrible, terrible photo-quality and some in-call sound issues recently always make me return to stock). I just took care to follow instructions and flash a pre-rooted .2.4.2 rom prior to flashing this.
The rom feels really really smooth, it's lovely so far.
edit: One issue thus far is some incompatibility on the Play Store, for instance Galaxy On Fire - Alliances. I can download it on any rom (CM/stock) except this one. Anyway to fix this?
edit2: Are dpi values changed for the launcher? I've tried a couple of xposed modules but I can't seem to get rid of that empty edge. The grid size is weird... it's like 4x4 but really crowded, with nasty-looking empty margins.
I tried a couple of apps to change dpi values to default, but they wouldn't read current dpi and no new values could be applied. Maybe this is linked to the Play Store incompatibilities.
How must I install it? Always I installed it (from official .242 and .270 too with RockZ1 Kernel) I had many bugs on this ROM, please help me
HELP
dyonissos said:
I flashed this ROM and my Z1 does not boot at all. When i press the power button, it vibrates once and that's all.
I flashed a stock rom, re-installed recovery and created a pre-rooted zip based on the SG customized firmware. The result was the same. Black screen, no sign of activity.
Does anyone have any idea what could be wrong here?
My device is a C6903 and worked just fine with the pre-rooted .242
Thanks!
Click to expand...
Click to collapse
Please help, I'v also got the same problems. I follow everything, but now my phone can not turn on anymore, can not charge. Everytime I press power button, it only vibrate once, but still off. Please help me.
I do the steps from Kitkat and using latest DUAL RECOVERY TWRP.
Thank you in advance
busukusu said:
Please help, I'v also got the same problems. I follow everything, but now my phone can not turn on anymore, can not charge. Everytime I press power button, it only vibrate once, but still off. Please help me.
I do the steps from Kitkat and using latest DUAL RECOVERY TWRP.
Thank you in advance
Click to expand...
Click to collapse
I fond the solutions for my problems. I test Fastboot at It work. When Power Off, press Volume Up and connect the USB Cable, then I can detect my phone with command: fastboot devices
After that, using Flashtools and install any FTF source with Kitkat 108, then flash it using Flashtools at computer PC. Prepare downloaded FTF files about 1 GB size at the same computer drive, then run Flashtools and then connect Press Volume Down and connect with USB cable, after that Flashtools display will show that my phone detected / connected, and continue with flashing FTF files, the process about 10 minutes less, and after finish flashing, disconnect USB cable, press Power button and YES it work again.
After that I have to install again with TWRP and install any Stock preroot firmware.
dyonissos said:
I flashed this ROM and my Z1 does not boot at all. When i press the power button, it vibrates once and that's all.
I flashed a stock rom, re-installed recovery and created a pre-rooted zip based on the SG customized firmware. The result was the same. Black screen, no sign of activity.
Does anyone have any idea what could be wrong here?
My device is a C6903 and worked just fine with the pre-rooted .242
Thanks!
Click to expand...
Click to collapse
I had the exact same problem. Ended up going back to my nandroid backup.
I am on locked bootloader. Not sure if that is the problem.
@Ahki767 could you please post md5 of the package? I am trying to make sure my download is not corrupt.
zgomot said:
edit: One issue thus far is some incompatibility on the Play Store, for instance Galaxy On Fire - Alliances. I can download it on any rom (CM/stock) except this one. Anyway to fix this?
edit2: Are dpi values changed for the launcher? I've tried a couple of xposed modules but I can't seem to get rid of that empty edge. The grid size is weird... it's like 4x4 but really crowded, with nasty-looking empty margins.
Click to expand...
Click to collapse
if you're still on this rom, you can change the dpi in /system/build.prop look for lcd_density and change it to 480 (original value). only thing i can think of for incompatibility is maybe an out of date play services
squashbuff said:
@Ahki767 could you please post md5 of the package? I am trying to make sure my download is not corrupt.
Click to expand...
Click to collapse
md5 check: 0406a4743310ee19209cfedcf0c728c9
make sure you're flashing at least from latest kit kat or lollipop
By request this is now the Unofficial Build Thread
This thread has been created to help clear up the confusion in the official threads.
That's right, everything here is just built. I am not the author of this code, I simply build current commits and provide them after having tested them myself on the most current Google provided factory images. I do not test these on betas. I will update this OP with more detailed instructions as deemed necessary.
Ok, so no more :good: Magisk is fixed :good: tomfoolery because I don't believe it anymore... From now on I am just going to provide solutions and assume that official is going to be broken again. What I am referring to is the dtbo image being patched and displaying the nasty "operating system on your device has been modified" message on every boot.
I have been told by typically competent developers that removing dtbo patching is stupid and makes no sense. I have been told that we cant run low level audio mods etc without it being patched. BlaBlaBla... Well, I can run everything I want without it being patched. Viper works, and anything else I have tried has worked. So, enough with that. More information on dtbo here...
I personally hate the message, and if you are here then you probably hate it too. So, if you like the message and want to keep it... Leave.
Unless something changes (oh and I am sure it will again) we only need a Magisk Manager app that does not patch dtbo without our permission. That is what I compile and provide. In the future if the actual root zip starts patching again, I will compile that too. But for now, it is just the app...
Here we go again...
1.) Uninstall official manager app
2.) Install this one. ...Unofficial Magisk Manager...
3.) If dtbo was patched and you are seeing the message then reboot to bootloader and 'fastboot flash dtbo dtbo.img' (factory dtbo)
4.) You are done.
Currently 15.2 root does not patch dtbo, Magisk Manager does.
I will release new modified Magisk Manager apps here as new commits are made. It is not necessary to update right away as there are rarely earth shattering changes released and most of the time the commits do not even apply to our device. I will compile new builds in as timely of a manner as I can. If something major does drop, it will be quick.
Happy New Year!!!
Join the Telegram Group!
https://t.me/Pixel2XLXDA
Reserved
...Because everyone else does it....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
...Look HERE for stuff...
*until google tells me otherwise*
(I don't care if you share/take credit for/mirror bla bla bla)
Suggestions
1.) Be current but not to current... (Run current non-beta factory images)
2.) Make sure you are running current adb/fastboot binaries. (Provided)
3.) Make sure your usb/usb-c cable is not from Toys R Us (They don't carry one : See Amazon)....
4.) You are not on a PS/1 (My first system )
5.) Don't exhibit behavior similar to mine...
..WIP..
Right on man. Thanks.
thedude420 said:
...Because everyone else does it....
...Look HERE for stuff...
*until google tells me otherwise*
(I don't care if you share/take credit for/mirror bla bla bla)
Suggestions
1.) Be current but not to current... (Run current non-beta factory images)
2.) Make sure you are running current adb/fastboot binaries. (Provided)
3.) Make sure your usb/usb-c cable is not from Toys R Us (They don't carry one : See Amazon)....
4.) You are not on a PS/1 (My first system )
5.) Don't exhibit behavior similar to mine...
..WIP..
Click to expand...
Click to collapse
#3 made me chuckle. :laugh::laugh::laugh::laugh::laugh:
On a serious note though, I tried flashing this last night and my phone would not stop rebooting on its own. It would restart and would just reboot. I tried grabbing some logs but the app (MatLog) would just load and not show any output.
Will probably see if I can try again and see if anything changes. Will also try the APK method you mentioned in the Magisk 2XL thread.
nexus_man12 said:
#3 made me chuckle. :laugh::laugh::laugh::laugh::laugh:
On a serious note though, I tried flashing this last night and my phone would not stop rebooting on its own. It would restart and would just reboot. I tried grabbing some logs but the app (MatLog) would just load and not show any output.
Will probably see if I can try again and see if anything changes. Will also try the APK method you mentioned in the Magisk 2XL thread.
Click to expand...
Click to collapse
Flash factory Nov images without -w to save your data then start over with twrp beta 2 and this magisk...
thedude420 said:
Flash factory Nov images without -w to save your data then start over with twrp beta 2 and this magisk...
Click to expand...
Click to collapse
Thanks dude for the prompt response. I'll give it a shot later today.
nexus_man12 said:
Thanks dude for the prompt response. I'll give it a shot later today.
Click to expand...
Click to collapse
Rite on! Here it is flash-all.bat. Not trying to be a douche but I once made changes to this file, flashed then realized that I did not save them prior... Ended up with a brand new device, it was great... Obviously this would only work with Nov factory images for Google "taimen" 8.0.0 ((OPD1.170816.025, Nov 2017) (not tested with the verizon ones..))
Code:
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-taimen-tmz10n.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-taimen-g8998-00122-1708311414.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot update image-taimen-opd1.170816.025.zip
echo Press any key to exit...
pause >nul
exit
Any word on ROMs being built for xl2? I'm waiting with bootloader til there are some ROMs
Sent from my Pixel 2 XL using Tapatalk
What do you mean? Waiting with bootloader?
Sent from my Pixel 2 XL
patt2k said:
Any word on ROMs being built for xl2? I'm waiting with bootloader til there are some ROMs
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I don't get it either. Unlock your bootloader now and get it over with. Going to have to wipe your data at some point. Also note that unlocking critical is NOT necessary. Just do a 'fastboot flashing unlock' and your good to go.
As far as ROMS go, I am not really sure. Syncing googles source tree today then I am going to do some test builds. Then go from there. They are coming :good:
thedude420 said:
I don't get it either. Unlock your bootloader now and get it over with. Going to have to wipe your data at some point. Also note that unlocking critical is NOT necessary. Just do a 'fastboot flashing unlock' and your good to go.
As far as ROMS go, I am not really sure. Syncing googles source tree today then I am going to do some test builds. Then go from there. They are coming :good:
Click to expand...
Click to collapse
Critical isn't required for a factory image flash? I wonder why they put the instructions on the site
Sent from my Pixel 2 XL
abuttino said:
Critical isn't required for a factory image flash? I wonder why they put the instructions on the site
Click to expand...
Click to collapse
The dev site says "may be necessary"... I have never unlocked critical and have not had one problem. Only thing I can tell it does is allow modifications to the actual bootloader which we do not need to do.
abuttino said:
Critical isn't required for a factory image flash? I wonder why they put the instructions on the site
Sent from my Pixel 2 XL
Click to expand...
Click to collapse
it's needed if there's an updated bootloader in the factory image.
8.1 DP1 has an updated bootloader so Unlock Critical is needed to fastboot flash that.
drewski_1 said:
it's needed if there's an updated bootloader in the factory image.
8.1 DP1 has an updated bootloader so Unlock Critical is needed to fastboot flash that.
Click to expand...
Click to collapse
Really? Google bootloader's will not flash without critical unlocked???
thedude420 said:
Really? Google bootloader's will not flash without critical unlocked???
Click to expand...
Click to collapse
It seems that way.
Sent from my Pixel 2 XL
Latest Unofficial Magisk Build
Magisk-14.5
Or attached to OP
So it appears Magisk Manager 5.4.2 is crashing. I would suggest sticking with 5.4.1 and disabling update notifications in settings for now.
So it appears Substratum theme was causing Magisk Manager crashing issues. I recommend not theming Magisk Manager!
Thanks for the effort and time put into this thread! Looking forward to having the time to sit down and play
Seriously though, the hard work is very much appreciated!
thedude420 said:
Latest Unofficial Magisk Build
Magisk-14.5
Or attached to OP
So it appears Magisk Manager 5.4.2 is crashing. I would suggest sticking with 5.4.1 and disabling update notifications in settings for now.
Click to expand...
Click to collapse
What are the circumstances? I'm running out with nothing happening yet. Can you help me reproduce it? Maybe we can figure something out.
CyberpodS2 said:
What are the circumstances? I'm running out with nothing happening yet. Can you help me reproduce it? Maybe we can figure something out.
Click to expand...
Click to collapse
Yeah, I have some stuff I need to do for the wife but then I will get some time and collect logs etc...
thedude420 said:
Latest Unofficial Magisk Build
Magisk-14.5
Or attached to OP
So it appears Magisk Manager 5.4.2 is crashing. I would suggest sticking with 5.4.1 and disabling update notifications in settings for now.
Click to expand...
Click to collapse
No crashing here. Did you try wiping data?
Sent from my Pixel 2 XL
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LG-VS996 20D ROMHello everyone
Users have requested that i can make a flashable Zip for the VS996. Hope it will be supported as with my other roms.
Rom ist Untested. Use it at your own risk! When somebody Tell me it Works then I will edit it
This Rom is 100% Stock. TWRP 3.2.1-0 must first be installed as with Nougat Roms. Then you can install this Rom and have Oreo with working TWRP.
This zip is created from the original KDZ. I changed the Boot.img, so you do not have to reinstall TWRP. . .
I had made this for users who can not get ota's because they have Custom Recovery / Root installed
Sorry for my bad english i'm out of practice
Features *Stock build made from official KDZ
*Stock Build.prop
*Unrooted
*Boot.img modified to keep TWRP
*Remove dm-verity
*Remove forceencryptInstallation What you need *Unlocked Bootloader [How to do]
*Working TWRP installed [Link to unofficial TWRP]
*When you need Root, Latest Magisk [Download]
*VS99620D(TWRP).zip [Download]
How to install When you are on Nougat: Reboot to recovery using button combo or reboot app (need root)
flash this TWRP.img Download reboot and Backup Dalvik,ART, Cache, System & Data (include not your internal memory) and Boot
in to your external sd or copy the backup from internal sd to your PC!
From Oreo: Install TWRP with this guide but with this img
For clean install: Wipe Dalvik/ART, Cache, System and Data (Recommend)
You can also keep your data by dirty flashing the zip. *Not tested!!!*
Flash VS99620D(TWRP).zip
then Magisk zip when you need root
Reboot System
At the first time you boot to system, it can be TWRP says No OS installed. You can ignore it.
If TWRP asks if you want to install SU, hit no
Here you can find my other [Downloads.] There are IMG´s, KDZ´z and more!
Rom Version
Android Version: 8.0
Android security patch level: 2018-05-01
Build date: 2018-06-14
MD5 SUMS:
Code:
[SIZE="4"][B][COLOR="Black"]boot.img 83cb7cabbd00f350c1a45b98d3f18313
modem.img 7c1d10c66f4a78ab583b0475537e33d0
persist.img 72aef7ed23519596ffc383c293f44474
rct.img 15bc82584049ec3a7c62d921c2897267
system.img 1a7ff1e9a2a664688a3c02b4857d3936
abl.img dcfe3827b4cb01b5016cd3751d6d78b3
apdp.img 60c2f929d5448404903c8a5f6c6599af
cmnlib.img 29acea73f83c2f4ec26d5d2898cd8b28
cmnlib64.img 1ca80dd965ba9cfdfaf0605fdc21ba6c
devcfg.img 6249eb8903db67633873845caf05c438
factory.img 15bc82584049ec3a7c62d921c2897267
hyp.img 20cbbea9743d6aa98ac2ecce4de28b5f
keymaster.img 8c27f3fdc8e1ffddecd2648d2e971658
laf.img 977a4de4b9cb6627a439eb53efb734a0
logfs.img c040a889d66a4f120f502f89b551f42b
msadp.img db354ccaabab3047db144fe04170560a
pmic.img dce34045db2954afbbbe6a5c81bb5634
raw_resources.img 8158fdcbf5f694db7dfcc032cc5d3b54
rpm.img 31e00d62598147a46f312c540cd0c5d4
sec.img 51963cce13001dc4d34baef78b1f9c3a
storsec.img 388d0392f31278d6b0f2a651ad3ef1da
tz.img f7daaa57bfa6ab5a71dfff4901b5d27e
xbl.img 74d1de6992b67e6a808616c8904585cd[/COLOR][/B][/SIZE]
Credits:
@autoprime
@SGCMarkus
@Chainfire
@topjohnwu
@Me :laugh:
Don´t forget to hit the thanks-button if you like my work! :good:
You want to help me with a [donation?] Feel free to make it.
Thanks so much OP!!! Will DL and test!, Will report back.
EDIT>>>>IT WORKS! Thanks OP!
Thanx! donation sent :good:
Visual Voicemail! Visual Voicemail! Visual Voicemail!
OMG!
OMG!
OMG!
Seriously, thanks Westwood24!
Downloaded and installed. Got a Verizon update notification and switched back to DotOS. I flashed everything that needed to be flashed and still got the Verizon update notification.
Can I flash this in TWRP to a "US998" (frankensteined from LS998 hardware), or do i need to frankenstein to VS996 first? I'm on Verizon and want working WiFi calling. All of the links i've read for WiFi calling have been dead ends.
d3structive_pyr0 said:
Can I flash this in TWRP to a "US998" (frankensteined from LS998 hardware), or do i need to frankenstein to VS996 first? I'm on Verizon and want working WiFi calling. All of the links i've read for WiFi calling have been dead ends.
Click to expand...
Click to collapse
Yes.
---------- Post added at 07:54 AM ---------- Previous post was at 07:52 AM ----------
WebDev28 said:
Downloaded and installed. Got a Verizon update notification and switched back to DotOS. I flashed everything that needed to be flashed and still got the Verizon update notification.
Click to expand...
Click to collapse
Because there is a newer update. You dont have to install it. You could also just freeze the OTA app with titanium, and no more notification.
Just dirty flashed everything is working fine. Noticed Verizon must have removed OEM bootloader unlock in developer options. Root and TWRP are fully functional. I get an app closure called quality data log service but that must be a Verizon thing also no big deal.:good:
4stringenator said:
Just dirty flashed everything is working fine. Noticed Verizon must have removed OEM bootloader unlock in developer options. Root and TWRP are fully functional. I get an app closure called quality data log service but that must be a Verizon thing also no big deal.:good:
Click to expand...
Click to collapse
It is a Verizon thing. You can freeze it using titanium, or just delete the app. Problem solved.
WebDev28 said:
Downloaded and installed. Got a Verizon update notification and switched back to DotOS. I flashed everything that needed to be flashed and still got the Verizon update notification.
Click to expand...
Click to collapse
You don't have to install the update. Just freeze in Titanium. It's "stock" Verizon except for custom recovery, so there will be some customization you have to do yourself.
---------- Post added at 12:27 PM ---------- Previous post was at 12:26 PM ----------
4stringenator said:
Just dirty flashed everything is working fine. Noticed Verizon must have removed OEM bootloader unlock in developer options. Root and TWRP are fully functional. I get an app closure called quality data log service but that must be a Verizon thing also no big deal.:good:
Click to expand...
Click to collapse
Yes, and you also do not get the bootloader unlock warning --even though the bootloader is still unlocked.
UPDATE!!! got it to work. i had to format date before flashing in twrp. setting up phone now. may add this into the how to install as a "if you get this error do this" for others that may run into this and panic like i did lol thanks again for making this!!!!
i get this image after flashing (not my picture just found on google but its the same thing but with white background)
wiped everything in twrp then installed. installed fine. after verizon boot animation i get this ill click reset phone and i just get taken into twrp. i will do a factory reset. doesn't help. i did the hold power and volume down to get into the reset phone menu chose to reset. just takes me back to twrp.
I set aside time today to port my converted LS998 from US998 to VS996. Everything went smoothly. Since I had the time, I dirty flashed first to see how/if it would work. I figured if it didn't go well, I would just do a clean install, but so far (4 hrs), I haven't yet seen had any noticeable problems. I froze the FOTA app, which I'm hoping is the correct one to prevent future Verizon updates.
From what I can tell, the VS996 ROM added the following apps:
Android Wear
Caller Name ID
Cloud
Hellp
Hum
Mobile Hotspot
NFL Mobile
Security and Privacy
Slacker Radio
ThinkFree Viewer
Email
Messaging
Voicemail
The items that went missing:
lg mobile (Switch?) ... don't know what the full app name is
Smart Clean(ing?) ... again, missing the full name
Smart World
Quick Help
Tasks
Safety Net reports invalid response in Magisk for a US998 flashing this rom
BHB78 said:
Safety Net reports invalid response in Magisk for a US998 flashing this rom
Click to expand...
Click to collapse
Just a Magisk Manager issue that appeared recently. SafetyNet Helper reported everything as fine.
my.ads0 said:
I set aside time today to port my converted LS998 from US998 to VS996. Everything went smoothly. Since I had the time, I dirty flashed first to see how/if it would work. I figured if it didn't go well, I would just do a clean install, but so far (4 hrs), I haven't yet seen had any noticeable problems. I froze the FOTA app, which I'm hoping is the correct one to prevent future Verizon updates.
From what I can tell, the VS996 ROM added the following apps:
Android Wear
Caller Name ID
Cloud
Hellp
Hum
Mobile Hotspot
NFL Mobile
Security and Privacy
Slacker Radio
ThinkFree Viewer
Email
Messaging
Voicemail
The items that went missing:
lg mobile (Switch?) ... don't know what the full app name is
Smart Clean(ing?) ... again, missing the full name
Smart World
Quick Help
Tasks
Click to expand...
Click to collapse
Wifi Calling. does that work??
johnp357 said:
Wifi Calling. does that work??
Click to expand...
Click to collapse
Confirmed WiFi Calling works.
my.ads0 said:
I set aside time today to port my converted LS998 from US998 to VS996. Everything went smoothly. Since I had the time, I dirty flashed first to see how/if it would work. I figured if it didn't go well, I would just do a clean install, but so far (4 hrs), I haven't yet seen had any noticeable problems. I froze the FOTA app, which I'm hoping is the correct one to prevent future Verizon updates.
From what I can tell, the VS996 ROM added the following apps:
Android Wear
Caller Name ID
Cloud
Hellp
Hum
Mobile Hotspot
NFL Mobile
Security and Privacy
Slacker Radio
ThinkFree Viewer
Email
Messaging
Voicemail
The items that went missing:
lg mobile (Switch?) ... don't know what the full app name is
Smart Clean(ing?) ... again, missing the full name
Smart World
Quick Help
Tasks
Click to expand...
Click to collapse
BHB78 said:
Confirmed WiFi Calling works.
Click to expand...
Click to collapse
outstanding... I will give this a spin. any other warnings or cautions?
johnp357 said:
Wifi Calling. does that work??
Click to expand...
Click to collapse
BHB78 said:
Confirmed WiFi Calling works.
Click to expand...
Click to collapse
What he said!
Had to go into Settings-->Advanced Calling to turn it on, but I can confirm that WiFi Calling shows up when making a call while connected to my home router. Visual voicemail is working too. Those are the 2 main reasons for me wanting to switch from US to VS.
Additionally, as has been mentioned in other threads, my phone now finds and gets the Verizon signal more quickly on this rom than the US998 one. Whereas I used to have to wait for the phone to fully boot to desktop and (seemingly having to wait for most) background processes to finish, I now get full signal immediately upon hitting the desktop.
johnp357 said:
outstanding... I will give this a spin. any other warnings or cautions?
Click to expand...
Click to collapse
Yes, lost of service and wifi w/ Magisk Beta install. Seemed to work fine otherwise, until beta install. Then reboots to have loss of service and disabled wifi. Restored state previous to Magisk beta install corrected this.
johnp357 said:
outstanding... I will give this a spin. any other warnings or cautions?
Click to expand...
Click to collapse
I have no warnings to offer.
Nandroid just in case.
I wiped dalvik cache before flashing.
I flashed VS996 zip.
I wiped dalvik cache again.
I forgot to flash magisk, so I had to adb reboot, wiped dalvik, flashed magisk, wiped dalvik and that was it. I could just be lucky, but everything's went smoothly for me.
---------- Post added at 08:41 PM ---------- Previous post was at 08:39 PM ----------
BHB78 said:
Yes, lost of service and wifi w/ Magisk Beta install. Seemed to work fine otherwise, until beta install. Then reboots to have loss of service and disabled wifi. Restored state previous to Magisk beta install corrected this.
Click to expand...
Click to collapse
I installed latest stable 16 as stated in OP and everything seems fine on my end.