Related
Ok, I have decided to go ahead and upgrade my device since I want to maintain root, and Acer has been unable to provide my ANY OTA updates or a copy of firmware and I don't want to ship my device to support just for a firmware upgrade.
My Device Current Pre-Upgrade info:
Flex Version: 05_COM_GEN2
Device info version: 1.0
Model ID: A100(it's an A100-07u-16u the 16GB)
EC Version: 2d010100
Android Version: 3.2
It IS rooted, with Busybox installed but still stock build.prop etc. The only mod I apply regularly is to enable hulu with my script.
Q: It seems to me they are ALL FULL Firmware installs, meaning Non-Incremental Updates. If so I'm guessing I can go directly to 4.0.3(0.12 build) from 3.2 Gen2, but I have read some mixed info about Gen1 vs Gen2. Im trying to verify I dont need to make and extra upgrade to gen1 first.
Q: Im wondering what the best upgrade path would be from my devices current state, to get it upgraded to ICS with CWM(or other recovery mod?)
Q: I am wondering if I am understanding the correct order of things, especially when it comes to the, temp-root to perm-root, /system rw, Busybox reinstall.
Do I just;
-Do a reset to factory defaults(maybe reroot after?)
-Enable "debug mode" in Settings
(still HC 3.2 Gen2)
-Copy 0.12 to SD card, rename and run update from stock recovery
(if it boot loops do a soft reset to wipe old data?)
-Start ICS
EITHER
-root ICS(mempodroid)
-mount -o remount /dev/block/mmcblk0p3 /system/
(Is this still necessary, to enable the installation of busybox to /system etc?)
-install/re-install Busybox, SuperUser from Market
OR
-root ICS(mempodroid)
-Install Busybox, SuperUser from Market
-mount -o remount /dev/block/mmcblk0p3 /system/
-Re-install Busybox to correct location(maintains root or re-root also?)
OR
-Some other method?
THEN
-ICS installed and rooted
-Unlock bootloader and install CWM(is this the RIGHT method HERE? for the unlock & CWM?
THEN(optional)
-Upgrade to custom ROM
Thanks
You should do a factory reset and reroot hc
Then download and install the .009 leak (.12 is an incremental update and does not perform the complete upgrade)
Then run the quick root method for ice found in these forums.
Unlock your boot loader
Flash cwm recovery and install rom manager following my thread on how to.
Then remove the boot.img from the .12 leak and flash through cwm
Hope this helps
Sent from my A500 using XDA App
NoSudo said:
Q: It seems to me they are ALL FULL Firmware installs, meaning Non-Incremental Updates. If so I'm guessing I can go directly to 4.0.3(0.12 build) from 3.2 Gen2, but I have read some mixed info about Gen1 vs Gen2. Im trying to verify I dont need to make and extra upgrade to gen1 first.
Click to expand...
Click to collapse
It is completely safe to go directly from 3.2 Gen2 to .12 ICS Gen1.
NoSudo said:
Q: Im wondering what the best upgrade path would be from my devices current state, to get it upgraded to ICS with CWM(or other recovery mod?)
Click to expand...
Click to collapse
Upgrade it as it is.
NoSudo said:
Q: I am wondering if I am understanding the correct order of things, especially when it comes to the, temp-root to perm-root, /system rw, Busybox reinstall.
Click to expand...
Click to collapse
Just root ICS using this method: http://forum.xda-developers.com/showthread.php?t=1531646, and that's it. Do not re-install busybox.
NoSudo said:
Do I just;
-Do a reset to factory defaults(maybe reroot after?)
-Enable "debug mode" in Settings
(still HC 3.2 Gen2)
-Copy 0.12 to SD card, rename and run update from stock recovery
(if it boot loops do a soft reset to wipe old data?)
-Start ICS
EITHER
-root ICS(mempodroid)
-mount -o remount /dev/block/mmcblk0p3 /system/
(Is this still necessary, to enable the installation of busybox to /system etc?)
-install/re-install Busybox, SuperUser from Market
OR
-root ICS(mempodroid)
-Install Busybox, SuperUser from Market
-mount -o remount /dev/block/mmcblk0p3 /system/
-Re-install Busybox to correct location(maintains root or re-root also?)
OR
-Some other method?
THEN
-ICS installed and rooted
-Unlock bootloader and install CWM(is this the RIGHT method HERE? for the unlock & CWM?
THEN(optional)
-Upgrade to custom ROM
Thanks
Click to expand...
Click to collapse
- Place the update.zip on your external sd card
- Boot into the stock recovery (and it will automatically flash the file)
- It will boot up
- Do a factory reset
- Root using the method linked
- Unlock the bootloader: http://forum.xda-developers.com/showthread.php?t=1557445
- Rename the install_recovery.sh in the "/etc/" or "/system/etc/" directory.
- Flash CWM: http://forum.xda-developers.com/showthread.php?t=1558595
Optional - Flash a custom rom.
Follow what Theonew has proposed. I have a Gen2 and everything went swell. The key is to perform a Factory reset after installing ICS. Then:
Root
Unlock
Install CWM
I followed Masterpker2's Instructions in THIS thread and it all went perfect.
I didn't realize that the file for leak version 12 was an incremental. I just checked and I'm running 09
This being said the steps would probably be:
Flash 09
Update to 12
Root
Unlock
Install CWM
Edit: Don't forget this additional step which was missing from the OP that I linked
Land Master said:
Flash 09
Update to 12
Root
Unlock
Install CWM
Click to expand...
Click to collapse
You do not need to flash .09 before .12.
From my inspection of the .zip files it seems .009 has boot loader.blob which is needed to update to the ics boot loader.
I did not see the blob in the .012 leak so it was a safe assumption to upgrade to the .009 leak first.
As with all flashing it is better to be safe than sorry. I have only done it the way I explained it above, but hey, if it works then that is one less step.
Sent from my A500 using XDA App
masterpker2 said:
From my inspection of the .zip files it seems .009 has boot loader.blob which is needed to update to the ics boot loader.
I did not see the blob in the .012 leak so it was a safe assumption to upgrade to the .009 leak first.
As with all flashing it is better to be safe than sorry. I have only done it the way I explained it above, but hey, if it works then that is one less step.
Sent from my A500 using XDA App
Click to expand...
Click to collapse
Yep. I agree with that statement. Just curious more than anything. I'm attempting to compile a consolidation thread and obviously if we can save some steps that's important. The more steps involved the more chances for something to go haywire.
Honestly all the different files that have been floating around can be confusing and I'm just attempting to clarify everything. Worst case is I will give various files a try and document my findings before posting results.
BTW... Thanks for your Thread on CWM. It was an unbelievably valuable resource!!
I just recently flashed my wife's new 3.2.1 gen2 straight to the .012 leak with no issues. I then unlocked boot loader, installed cwm, etc...
Gibson.Dubs said:
I just recently flashed my wife's new 3.2.1 gen2 straight to the .012 leak with no issues. I then unlocked boot loader, installed cwm, etc...
Click to expand...
Click to collapse
Thanks!
Can you check the MD5 of the file (.012) you used against this:
61db347f9137196b936b6a3aa6c5e5f8
The file I have is named: Acer_AV041_A100_1.012.00_WW_GEN1.zip
Land Master said:
Thanks!
Can you check the MD5 of the file (.012) you used against this:
61db347f9137196b936b6a3aa6c5e5f8
The file I have is named: Acer_AV041_A100_1.012.00_WW_GEN1.zip
Click to expand...
Click to collapse
That is the correct file name and the md5 matches.
61DB347F9137196B936B6A3AA6C5E5F8 *Acer_AV041_A100_1.012.00_WW_GEN1.zip
I could have sworn that there was a bootloader I deleted from the zip before flashing 012? Maybe that was 09 ha ha, if you have a look over at the A500 forums the recovery installer app now supports the a100, tested it yesterday, works well
Sent from my A500 using xda premium
toyface said:
I could have sworn that there was a bootloader I deleted from the zip before flashing 012? Maybe that was 09 ha ha, if you have a look over at the A500 forums the recovery installer app now supports the a100, tested it yesterday, works well
Sent from my A500 using xda premium
Click to expand...
Click to collapse
You probably did. As I said I upgraded from 3.2.1 gen2 straight to ICS .012. I do not even have any of the other leaks downloaded anymore so I am certain.
Hey Thanks all for the information. It will make me feel allot more comfortable about performing the upgrade. Im sure other folks will be in the same/similar situation and will probably also find the info useful.
I can confirm that the .012 copy I got from Vanche's site has a bootloader.blob in the root of the .zip file. I didn't yet have the .009, just the original .002 and the .012 anyway so I'm glad I don't need .009. I Also confirmed it passed an md5 check 61db347f9137196b936b6a3aa6c5e5f8 Acer_AV041_A100_1.012.00_WW_GEN1.zip.
I'm running all over tomorrow. I should have time in the next few days. I'll post the results after and try to document anything that seems unexpected/note worthy for the directions Land Master is working on.
NoSudo said:
Hey Thanks all for the information. It will make me feel allot more comfortable about performing the upgrade. Im sure other folks will be in the same/similar situation and will probably also find the info useful.
I can confirm that the .012 copy I got from Vanche's site has a bootloader.blob in the root of the .zip file. I didn't yet have the .009, just the original .002 and the .012 anyway so I'm glad I don't need .009. I Also confirmed it passed an md5 check 61db347f9137196b936b6a3aa6c5e5f8 Acer_AV041_A100_1.012.00_WW_GEN1.zip.
I'm running all over tomorrow. I should have time in the next few days. I'll post the results after and try to document anything that seems unexpected/note worthy for the directions Land Master is working on.
Click to expand...
Click to collapse
Good Luck NoSudo. FYI, I have posted a link to 009 in my thread. Not that you should need it but it is there now.
This information outlines what I did to upgrade stock HC 3.2 GEN2(rooted) to ICS 4.0.3 .012. Leak(for info on rooting HC look here
Update:
Well today after breakfast I decided to go ahead and upgrade.
1) I made a fresh backup with Titanium and copied it to an external device.
2) I placed the Acer_AV041_A100_1.012.00_WW_GEN1.zip inside a freshly formated(fat32) 4gb micro SD card.
3) Renamed the file to update.zip.
4) Did an MD5 check to ensure the file on the SD was a good file.
5) With the tablet shut down I placed the 4GB micro SD card into the A100
6) I twitched the screen lock to "on", held down the "volume down" button, then while still holding the "volume down" button, I pressed the "power button" for about 3 seconds.
7) Once the "booting into recovery" message in the upper left showed up, I released the still pressed down "volume down" button. As soon as the volume down button is released a graphic appeared with a robot with moving gears, and a progress bar.
Once the progress bar reached full, it poped up a message saying "Android is Updating" another progress bar, and a message saying "optomizing application x of 135" x being a changing number as it progressed.
After this process completed my login keypad appeared. I was able to login and all my old apps are still here and it all looks nice. So far so good. Im going to poke around a little then whipe the old data and stuff. Currently though it upgraded and kept all my apps, and settings, and seems to be working well.
I'll post another update later after I have messed with it a bit more.
NoSudo said:
After this process completed my login keypad appeared. I was able to login and all my old apps are still here and it all looks nice. So far so good. Im going to poke around a little then whipe the old data and stuff. Currently though it upgraded and kept all my apps, and settings, and seems to be working well.
I'll post another update later after I have messed with it a bit more.
Click to expand...
Click to collapse
When you're ready to root, etc. make sure you do a factory reset first.
Theonew said:
When you're ready to root, etc. make sure you do a factory reset first.
Click to expand...
Click to collapse
Yep, I'm planning on doing a factory reset and I guess format the internal storage also to be safe. I'm just curious how/what works without doing anything other then the update. So Im messing around with it a little. I also realized I forgot to backup a few documents I need LOL(oops that was close!) I didn't think about the fact that titanium just does my apps, and system. So I'm uploading some stuff to my dropbox at the moment.
NoSudo said:
Yep, I'm planning on doing a factory reset and I guess format the internal storage also to be safe. I'm just curious how/what works without doing anything other then the update. So Im messing around with it a little. I also realized I forgot to backup a few documents I need LOL(oops that was close!) I didn't think about the fact that titanium just does my apps, and system. So I'm uploading some stuff to my dropbox at the moment.
Click to expand...
Click to collapse
Only updating is fine. I upgraded to ICS within a few days of the first leak, and everything's been working great.
I found that my camera was not being recognized after upgrading from 3.2 to 4.03(.012). As in I load camera and it pops up a box saying it doesnt see a camera device. I just did a clear cache, clear data in settings, apps, and now it sees the camera and it is working fine. No funky greenness some talked about so far.
Q&A for [ROM][V500][5.0.x][CM12] Official CyanogenMod 12
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][V500][5.0.x][CM12] Official CyanogenMod 12. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
is there any way of getting MULTICAST enabled in the CM12 stock kernel?
axelander1 said:
is there any way of getting MULTICAST enabled in the CM12 stock kernel?
Click to expand...
Click to collapse
Yes, the first step is to submit a patch to gerrit. Is there a patch available?
Deltadroid said:
Yes, the first step is to submit a patch to gerrit. Is there a patch available?
Click to expand...
Click to collapse
I could probably create one.
Do you know which kernel config is used? is it one in https://github.com/CyanogenMod/android_kernel_lge_v500/tree/cm-12.0/arch/arm/configs ?
Is this even the kernel repo which is used for the cm12 nightlies?
axelander1 said:
I could probably create one.
Do you know which kernel config is used? is it one in https://github.com/CyanogenMod/android_kernel_lge_v500/tree/cm-12.0/arch/arm/configs ?
Is this even the kernel repo which is used for the cm12 nightlies?
Click to expand...
Click to collapse
This is the script that generates the config and moves it to arch/arm/configs/
https://github.com/CyanogenMod/android_kernel_lge_v500/blob/cm-12.0/make_defconfig.sh
Deltadroid said:
This is the script that generates the config and moves it to arch/arm/configs/
https://github.com/CyanogenMod/android_kernel_lge_v500/blob/cm-12.0/make_defconfig.sh
Click to expand...
Click to collapse
this file takes a parameter, I suppose awifi070u-perf_defconfig is used (see the other make script make_awifi070u_defconfig.sh).
However this has CONFIG_IP_MULTICAST=y.
I somehow doubt that this is the config which is actually used for the official builds. If I understand http://wiki.cyanogenmod.org/w/Build_for_v500 correctly, the command "breakfast v500" would pull the kernel repo and triggers make for the kernel's .config file?
Yes. You can also create a local manifest to pull a specific repo without having to pull everything.
Example:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="cmhub" fetch="git://github.com/CyanogenMod/" review="review.cyanogenmod.com" />
<project path="device/lge/v500" name="android_device_lge_v500" remote="cmhub" />
</manifest>
Example Procedure:
repo init -u git://github.com/CyanogenMod/android.git -b cm-12.0
repo sync device/lge/v500
repo start my_fixed_branch device/lge/v500
cd device/lge/v500
<edit files>
git commit -a
repo upload device/lge/v500
---------- Post added at 12:23 AM ---------- Previous post was at 12:11 AM ----------
Just substitute "device" for "kernel" in the project path and name.
How do I know if I'm using hardware or software decoding for Netflix? No idea if I need your patch.
Also, I installed cm-12-20150226-NIGHTLY-v500.zip yesterday. Updated to cm-12-20150227-NIGHTLY-v500.zip with CyanDelta today, works like a charm. Thank you!
If you make a backup of /system/etc/media_codecs_google_video.xml then you can revert the patch. It only removes one line in that xml file so that adaptive playback is not an option for h264 decoding. The only difference is that hardware decoding should save on the battery. This patch was taken from slimRom and I need it for other devices, so I thought it would be worth testing for this device also.
Hi everyone, I am on 28\02 nightly and Google Now doesn t work, showing "Network error. Check your network connections".
Does anyone knows how to solve it?
It's working here. Either the Google services is temporarily down in your area or you need to install the correct version of gapps. The "Delta" gapps that I have posted in the development section are up to date and working.
cm12 crashes after flashing
Everytime I flash cm12 it fails. I get into the setup process, login to wifi' cyanogenmod, and google. I never get passed this. During setup I get messages that say "unfortunately there is a problem with music", then the same for camera. Then the screen stars flashing and eventually goes dark. The back key shows at the bottom, but the other two do not show. The back key is nonresponsive. I have to power down and get back to recovery and restore my cm11 backup.
When I got the gpad, it came with 20D, andI had to use the lgflashtool to get back to 4.2.2. (20A0. Then I rooted with stump and installed twrp using flashify. Then I was able to flash cm11 (m10, 11 and 12). Cm11 ran like a champ.
A couple of weeks ago I decided to flash a cm12 nightly and had the problem described above.
I have tried multiple combinations of steps to solve this problem: going back to 4.2.2, rooting and flashing cm12 from 4.2.2, I have tried 4.4.2. I have tried multiple versions of twrp and philz. I have wiped with and without wiping system. I have tried different versions of gapps-lp. I have tried different versions of the nightlies.
Every time I get the same result (which I think is the definition of insanity).
What is most frustrating is that I have another gpad that went from cm11 to cm12 with no problems. Worked the first time using the 0217 nightly,
So what am I doing wrong? Why am I having problems with cm12 after I flash it?
Thanks in advance. Xda has been a life saver since I got my first tablet, a viewsonic, a few years ago.
John
It sounds like you know the procedure of installing CM because one of your devices works fine. There seems to be a difference between your two devices. Have you looked at the thread for "back cam fix" in the development section to find out how to check which camera module your device has? Maybe one of your devices has a different camera module than the other (which requires other camera drivers). Although, the device should still function with cm12 even if your camera module is unsupported.
Also, make sure you format the cache, Dalvik cache, and system partitions in addition to a factory reset before flashing from your internal sdcard.
Still can't set up CM12
Deltadroid said:
It sounds like you know the procedure of installing CM because one of your devices works fine. There seems to be a difference between your two devices. Have you looked at the thread for "back cam fix" in the development section to find out how to check which camera module your device has? Maybe one of your devices has a different camera module than the other (which requires other camera drivers). Although, the device should still function with cm12 even if your camera module is unsupported.
Also, make sure you format the cache, Dalvik cache, and system partitions in addition to a factory reset before flashing from your internal sdcard.
Click to expand...
Click to collapse
Thanks for the suggestions. I first checked the camera.
While in CM11 I turned on the camera and took a picture. I also opened a terminal window and grepped both the OV and the S5K cameras. Nothing came back for OV. I did get stuff from S5k. So I assume the camera is the right one.
Then I did went into recovery, carefully wiped and formatted, and flashed CM12 and Gapps.
I am still getting the camera and music errors. Then the screen flashes to black and the it locks.
The bad news is that I cannot get back to recovery. It looks like I'm back to the lgflashtool.
I will try again from stock. But right now I think it is miller time.
Yeah, if it was working on cm11 then your camera is supported.
Maybe going back to latest stock Rom with lg tool would help fix any unknowns. Instead of flashing the 10a firmware, stay on 20d stock and just replace aboot so you can install a custom recovery. Next, install cm12 with red kernel or mani kernel to support your stock 20d 4.4.2 firmware.
Are you sure you did wipe SYSTEM before flashing?
Still can't set up CM12
Deltadroid said:
Yeah, if it was working on cm11 then your camera is supported.
Maybe going back to latest stock Rom with lg tool would help fix any unknowns. Instead of flashing the 10a firmware, stay on 20d stock and just replace aboot so you can install a custom recovery. Next, install cm12 with red kernel or mani kernel to support your stock 20d 4.4.2 firmware.
Click to expand...
Click to collapse
No cigars yet! Same error with camera and music then screen locking.
I found an XDA tool called Original LG Firmware.exe. It allowed me to download V50020d_00.kdz.
I used LGFlashTool2014 to install.
I used Stump to get Root.
I downloaded SuperSU and Flashify to set up recovery.
Recovery failed. It didn't think I was rooted.
I used another tool, LGGPabRecoveryTWRP 2.8(BypassBootloader).apk to resolve this problem
I installed CM11-M12.
Then I went to recovery to install CM12, gapps, and red kernal.
The first attempt used the 0305 nightly. It hung on the flash.
I forced a power down and manual reboot into recovery.
Did all the wiping and tried the 0217 nightly. The flash was successful but as it initialized, CM12 crashed and burned again.
I'm beginning to believe I have a poltergeist in this gpad.
johnseidel said:
No cigars yet! Same error with camera and music then screen locking.
I found an XDA tool called Original LG Firmware.exe. It allowed me to download V50020d_00.kdz.
I used LGFlashTool2014 to install.
I used Stump to get Root.
I downloaded SuperSU and Flashify to set up recovery.
Recovery failed. It didn't think I was rooted.
I used another tool, LGGPabRecoveryTWRP 2.8(BypassBootloader).apk to resolve this problem
I installed CM11-M12.
Then I went to recovery to install CM12, gapps, and red kernal.
The first attempt used the 0305 nightly. It hung on the flash.
I forced a power down and manual reboot into recovery.
Did all the wiping and tried the 0217 nightly. The flash was successful but as it initialized, CM12 crashed and burned again.
I'm beginning to believe I have a poltergeist in this gpad.
Click to expand...
Click to collapse
The reason your recovery failed is because your 20D firmware has an aboot.img that is not loki exploitable. After rooting, you will need to replace your aboot.img with the aboot.img from 10A firmware. This means you are keeping the 20D bootloader but only downgrading the 10A aboot.img so that you can use the loki tool to install a custom recovery. Flashify also needs a loki exploitable aboot.img (10A) to be installed before it can work and install a lokified recovery. The trick is to keep your new bootloader from 20D but only downgrade the aboot.img. There is a batch file in the development section that does this with a script using the dd command.
Okay.
20D is flashed and rooted.
V50020_aboot_twrp_v2 has been executed.
Flashify flashed TWRP 8.0.0.0 and rebooted.
I am assuming the next step is to flash CM12, but wanted to make sure. I've shot myself in the foot so many times I'm running out of toes.
Next, factory reset, and format /system. You could also format your internal sdcard, but it's not often necessary.
Finally, install latest nightly build of cm12. You can install gapps later.
---------- Post added at 02:45 AM ---------- Previous post was at 02:36 AM ----------
Note, make sure you copy the files to your sdcard first if you plan on formatting the internal sdcard.
This was tough to get as LG locked down all known exploits with the ZVI release. It took some hardware hacking to pull a clean unmodified system and kernel. Here is a flashable zip:
http://jacobstoner.com/LS980ZVI.zip
This includes a bootstack with an older bootloader and TWRP 2.8.7.3. The ZVI kernel has been bumped to work with the older bootloader. Otherwise this is completely unmodified and unrooted so if you want root then flash SuperSU after flashing this.
http://download.chainfire.eu/supersu
Thanks for sharing, i am on cyanogenmod 11, can i install it with hybrid bootstack and blestagator's bumped twrp?
It will replace your bootstack and update twrp, but it will work fine.
Thanks, man! I wait for it so long! Because I'm still on ZVG because ZVI was unrootable. So all what I need is just clean flash room in recovery and install supersu app? Without any unlockers? Downloading now, making backups and give a try!
astherion said:
Thanks, man! I wait for it so long! Because I'm still on ZVG because ZVI was unrootable. So all what I need is just clean flash room in recovery and install supersu app? Without any unlockers? Downloading now, making backups and give a try!
Click to expand...
Click to collapse
Yes, just flash in recovery and flash the supersu zip from the link above. You can dirty flash over ZVG, it will overwrite the whole system partition anyway.
Confirmed! If works! Just made clean installation 20 minutes ago & flash supersu.zip through recovery. Superuser works fine. So now I've try restore zvg & flash over it. Because I use lots of exposed modules & dorimanx kernel, titanium backup, lucky patcher, freedom etc. For this sw root is critical... Thanks a lot for latest ZVI + root! Later I link to your thread for peoples from russian 4PDA LG G2 thread. Lots of people will be happy!
ROM working well for me too. Thanks!
Not ever try to flash on installed rom! You'll receive a lots of lags after! Make app backup & flash "clean" install through recovery. I found also 1 issue in recovery: then screen goes off after you turn it on you see only blue-grey-black-white stripes with tiny squares. It happens not always but sometimes.
P.S. Previously I also used bumped 2.8.7.3 TWRP and has no problems. Also I use xposed, so when I flash ZVI on ZVG & restore apps backup has lots of lags like force close systemUI, deleted unworking software etc. So - clean install! After that - restore backup, but only user apps, not system like xposed apps, home g4 launcher, dialer etc.!
Rom
Its working fine ... but i am facing network lock issue...Kindly help
To nomansabir: what means network lock? Simlock? Or you can't switch cdma/lte?
astherion said:
To nomansabir: what means network lock? Simlock? Or you can't switch cdma/lte?
Click to expand...
Click to collapse
Dear i am facing sim lock problem.... Its showing Invalid sim card message...
SIM-unlock
Nomansabir: you need made sim-unlock again.
Download Wirking+Hotspot.zip. You must be rooted 1st. Install adbdinsecure2.00.apk, open it, accept root privileges, use checkbox "enable insecure adb" - exit apk. Connect g2 to pc, open simunlock.exe with admin rights, phone must reboot itself after correct installation. Voila: you phone is now sim-free!!!
P.S. You can delete adbdinsecure.apk after
astherion said:
Nomansabir: you need made sim-unlock again.
Download Wirking+Hotspot.zip. You must be rooted 1st. Install adbdinsecure2.00.apk, open it, accept root privileges, use checkbox "enable insecure adb" - exit apk. Connect g2 to pc, open simunlock.exe with admin rights, phone must reboot itself after correct installation. Voila: you phone is now sim-free!!!
P.S. You can delete adbdinsecure.apk after
Click to expand...
Click to collapse
Thnx astherion .... its working fine now.....
jacob019 said:
This was tough to get as LG locked down all known exploits with the ZVI release. It took some hardware hacking to pull a clean unmodified system and kernel. Here is a flashable zip:
http://jacobstoner.com/LS980ZVI.zip
This includes a bootstack with an older bootloader and TWRP 2.8.7.3. The ZVI kernel has been bumped to work with the older bootloader. Otherwise this is completely unmodified and unrooted so if you want root then flash SuperSU after flashing this.
http://download.chainfire.eu/supersu
Click to expand...
Click to collapse
that's wonderful, @jacob019, thanks for sharing this highly waited zip of the ZVI, as far as i am on cloudy G2 3.3 with my LS980 for a long time and have not experienced the stock firmware after ZVG.
I have two questions in my mind if you could please clear them.
1. Is there any problem in the ZVI like most of the LG updates have not been without bugs or lagging ?
2. Can i flash this zip directly from my already installed TWRP without going back to stock ZVG or ZVE? (I have Cloudy G2 3.3 installed with blastgator's boot stack/baseband) {Cloudy G2 v3.3 is indeed a perfect ROM for my LS980 till now}
Thanks again for the great job you have done
talvigi said:
1. Is there any problem in the ZVI like most of the LG updates have not been without bugs or lagging ?
2. Can i flash this zip directly from my already installed TWRP without going back to stock ZVG or ZVE? (I have Cloudy G2 3.3 installed with blastgator's boot stack/baseband) {Cloudy G2 v3.3 is indeed a perfect ROM for my LS980 till now}
Click to expand...
Click to collapse
1. I've been using it for a couple weeks, seems quite stable but I'm a light user.
2. Yes, you can flash it directly from your already installed TWRP. No need for any other preparation.
jacob019 said:
1. I've been using it for a couple weeks, seems quite stable but I'm a light user.
2. Yes, you can flash it directly from your already installed TWRP. No need for any other preparation.
Click to expand...
Click to collapse
Thanks @jacob019 for your time and again for your great job.
I will try it as soon as the download of the zip file will be completed.
And i also must try the SIM unlock as you mentioned above because i live out of US and am using GSM network not CDMA, so i think to do that i need some preparations.
I hope there are thousands in this line to need ZVI and the SIM unlock. Hail Jacob.
What is the flashing procedure by the way? is it same as we flash custom ROM (wipe system, devlock, cache and data) or just wipe dev lock and cache and flash the zip file
Just reboot to tarp recovery, choose wipe - advanced - check all except "sdcard" - wipe and just flash zip. Also better to flash supersuper.zip if you need root. Reboot - profit!
For me it works flawlessly, slight more battery drain, but solved by dorimanx kernel, xposed & greenify app. I didn't see the even mentioned lags in this Rom. Working for me the same as ZVG & also rootable!
astherion said:
Nomansabir: you need made sim-unlock again.
Download Wirking+Hotspot.zip. You must be rooted 1st. Install adbdinsecure2.00.apk, open it, accept root privileges, use checkbox "enable insecure adb" - exit apk. Connect g2 to pc, open simunlock.exe with admin rights, phone must reboot itself after correct installation. Voila: you phone is now sim-free!!!
P.S. You can delete adbdinsecure.apk after
Click to expand...
Click to collapse
@astherion, Thanks for the SIM Unlock files, by the way rooted is OK but but what is "after correct installation" is it what the software in PC does with the mobile or something else? And developer options have to enabled or otherwise?
Edited: Thank you very much guys specially @jacob019 and @astherion, you guys rock the party. The stock Lollipop is flashed perfectly and SIM Unlock was the most simple step i have every seen in the LG world, But astherion you should have mentioned the USB debugging option as it needs to be enabled before running the simunlock.exe from the PC, and an other thing i can see Hands free activation disturbs after every reboot (i have just rebooted twice and it cameup both times) and battery level also going very fast don't know why but, this can be a major issue which may force some people like me to go back to Cloudy. My battery was at 75% and 4 hours 12 minutes remaining and after i rebooted to recovery and wiped devlock cache and data, still battery says 69 % 3 hours 3 minutes remaining. This is dangerous, the battery graph is showing like a forward slash is on the graph panel, I will attach pics.
Indeed this all made me a fan of you guys,
So I am on ZVH, rooted with TWRP installed. Can I just flash the zip files?
When doing a clean install, are you just totting back to an earlier release(ZVE or G), rooting and installing TWRP and then this zip files?
tekweezle said:
So I am on ZVH, rooted with TWRP installed. Can I just flash the zip files?
When doing a clean install, are you just totting back to an earlier release(ZVE or G), rooting and installing TWRP and then this zip files?
Click to expand...
Click to collapse
Yes, you can just flash the zip file; should be no need to wipe data if you're coming from ZVG. Also there is no need to tot back to an earlier release unless you are already on ZVI because wiping data and installing this zip will produce just as clean of an install.
@talvigi, battery is okay for me; but I'm used to stock. I'm not sure about disabling activation because I'm using it on Sprint. I'm sure you can find info on how to improve both of those issues, but there isn't anything to be done here since this is an unmodified stock rom.
Stock Oreo US998 20H flashable TWRP zip. Original zip created by westwood24.
COMPATIBILITY
This zip is compatible with ls998, us998, and should be compatible with vs996 but im not 100% sure about that. But if someone confirm vs996 compatibility that would be great :good: Its been tested and vs996 is compatible as well
This zip is created from the original KDZ. It contains almost the complete 20H firmware, but the partition table rewriting part and recovery image (beside five to eight other images) is removed. I changed the system.img, so you do not have to reinstall TWRP (recovery-from-boot.p deleted) when ROM once booted. I also changed the partition size of system.img, so the vendorized people can install this too without having problems because of a too small system partition.
FEATURES
Stock build made from official KDZ
Unrooted
System.img modified to keep TWRP
Resized system.img (for Treble users)
Removed dm-verity
Removed rctd (LG's root checker tool daemon)
Removed ForceEncryption
Added DTS prop to enable DTS
Added all weather lockscreen prop to enable other weather
INSTALLATION
Unlocked Bootloader [How to do]
Working TWRP installed (should be installed already, otherwise you wouldn't need this zip [Link to newest unofficial TWRP]
When you need Root, Latest Magisk [Download]
LATEST ZIP
john-fawkes.com US99820H.zip [Click to Download]
OLDER ZIPS
AFH ZIPS [Download]
HOW TO INSTALL
When you are still on Nougat
you should start fresh: Reboot to recovery using button combo or reboot app (needs root; btw, Magisk offers this possibility too: Modules Menu then click three dot menu top right - Reboot to recovery
Then flash [this latest TWRP.img] via image flashing function in TWRP, reboot to recovery again (for fully working new recovery) and do a backup, then copy this backup to your PC.
Then initiate a factory reset. Wipe your system partition too in TWRP advanced wiping menu, copy the 20H firmware zip to your SD and install it. Reboot and enjoy
From Oreo
For clean install: Factory reset and wipe system
You can also keep your data by simply dirty flashing the zip.
*Be aware that problems may occur, maybe you need to do a factory reset to start fresh*
Flash the 20H zip, then Magisk zip when you need root, then reboot to System = you're DONE
If the first time you boot to system, it could be TWRP says No OS installed. You can ignore it.
If TWRP asks if you want to install SU, hit no (in newest TWRP SU is disabled, and the option to install the TWRP app is disabled too.)
Rom Version: 8.0 Oreo
Android security patch level: 2019-3-1
Just give a thanks if you like the zip!
You want to help me with a [donation?] Not asking for it, I have fun doing this for you, but feel free...
RESERVED
I'm applying for dev status on afh. This will make it easier to download the zips in the future since gdrive adds it to the gdrive of the user downloading and then has to download it again from their drive. Makes no sense google
THE LINK IS ACTIVE NOW!!!!!!
sorry about that guys. forgot to allow access to everyone
This is actually enraging me. Can someone please tell me where the XDA app puts downloads?
mrsubway said:
This is actually enraging me. Can someone please tell me where the XDA app puts downloads?
Click to expand...
Click to collapse
should put it in internal storage /Downloads
JohnFawkes said:
should put it in internal storage /Downloads
Click to expand...
Click to collapse
Have no clue where it went. Downloaded via browser and it flashed fine! Great job man! Thank you!!
?
mrsubway said:
Have no clue where it went. Downloaded via browser and it flashed fine! Great job man! Thank you!!
Click to expand...
Click to collapse
no problem! enjoy! i will be taking over all us998 kdz2zip and vs996 kdz2zip releases. and @seadersn will take care of canada, india and EU. hopefully us998 20F will be here soon
JohnFawkes said:
no problem! enjoy! i will be taking over all us998 kdz2zip and vs996 kdz2zip releases. and @seadersn will take care of canada, india and EU. hopefully us998 20F will be here soon
Click to expand...
Click to collapse
Man I wish they'd push a stock 8.1.
MD5: 3FB2D258B37DBFC5195EBD207BBB9765
SHA-1: B72795AAEDAD661004030137F712E2FBEE65EC92
For reference to compare your download.
mrsubway said:
Man I wish they'd push a stock 8.1.
Click to expand...
Click to collapse
Would be nice. When i was on htc 10 it was the same way. We got Oreo 8.0 but never got 8.1. However the lg g7 one just got pie update so we may get stock pie soon hopefully
Im usuallynot the one to complain but my carrier is sprint and this rom seems like my reception got worse. Im only getting 1 bar in my house where i usually get 3 on average and sometimes 4. Maybe becuz its a us998 rom instead of the sprint rom?
MonstaSaleens said:
Im usuallynot the one to complain but my carrier is sprint and this rom seems like my reception got worse. Im only getting 1 bar in my house where i usually get 3 on average and sometimes 4. Maybe becuz its a us998 rom instead of the sprint rom?
Click to expand...
Click to collapse
Shouldn't matter. I'm on sprint as well with this same zip and no reception issues. Could just extract the modem from the sprint kdz and flash it in twrp if you want to use sprints modem
Deleted.
Thx?
Been some time since I've commented on xda but had to let you know thank you, this worked perfectly on my new v30+. Nice to have you doing this. Thanks again.
NPCMW said:
Been some time since I've commented on xda but had to let you know thank you, this worked perfectly on my new v30+. Nice to have you doing this. Thanks again.
Click to expand...
Click to collapse
No problem ?. We should be getting 20F soon and I'll be doing this one as well. Hopefully within days of it dropping. But being a single dad of 2 little kids and a full time 40 hour a week job plus my like 10 other android projects I maintain, I can't definitely say it will be within days of it dropping though
Just an FYI to those curios, I dirty flashed this zip on my frankensteined US998 that was running 20D and it worked great. I ran a nandroid just in case but after flashing the zip, doing a cache wipe and reflashing magisk, i was up and running where i left off.
bacon612 said:
Just an FYI to those curios, I dirty flashed this zip on my frankensteined US998 that was running 20D and it worked great. I ran a nandroid just in case but after flashing the zip, doing a cache wipe and reflashing magisk, i was up and running where i left off.
Click to expand...
Click to collapse
Ditto man! Flashed over D, flashed Magisk, flashed Xposed, cleared Art and Cache and rebooted, and all was well! Great job!
Just dirty flashed it, and of course works great.
A lot better than last weekend when I updated my wife's still-bootloader locked/unrooted (don't ask) V30 from US998 20A to US998 20E via dev patched LGUP -- and in a moment of carelessness (trying to do three things at once) FORGOT to choose "UPGRADE" instead of the default "REFURBISH". It finished quite quickly -- and quite completely WIPED her phone. Ouch. I was then busy the next 2 or 3 hours setting up her phone again...
Changing the subject, for those with US998 and want to try something different... This is a US998 V30/V30+/V30S great Magisk module by @TotallyAnxious that
* Enables dual speaker mode. That part is sort of based on @Whiskeyomega mod, but is TWRP flashable.
* HIM for all earphones
* Also has some kernel tweaks.
* Installs YouTube ad-free "Vanced"
* Google Dialer
* Other stuff
AnxiousV30 magisk mod (v106)
Try it out if you wish.
JohnFawkes said:
should put it in internal storage /Downloads
Click to expand...
Click to collapse
Mine automatically, I guess, went to Google drive. I had to go into drive and download it a second time. That's when it went to download.
When I clicked on the "zip" file in the OP, it took me to the OP's Google drive to download it. I guess it then automatically downloads to my Google drive.
---------- Post added at 02:27 AM ---------- Previous post was at 01:57 AM ----------
Just dl'd and installed this an hour or so ago. It seems to be running really well. ?.
I am a Verizon customer with an original vs996 phone.
LG V30 Sprint LS998-30A ROMHi!
This Rom is 99% Stock. Most recent TWRP should first be installed. Then you can install this Rom and have Oreo with working TWRP.
This zip is created from the original KDZ.. It is made by me flashing my back to factory zip to lose TWRP and root and taking the OTA and then using lgup to dump all the partitions and then making a flashable zip. It contains almost the complete 30A firmware, but the partition table rewriting part and recovery image is removed. I changed the system.img, so you do not have to reinstall TWRP (recovery-from-boot.p deleted) when ROM is booted. I also changed the partition size of system.img, so the vendorized people can install this too without having problems because of a too small system partition. This is a continuation of westwood24's idea and work, I've updated it to the newest fw version and edited / advanced it a bit. I followed his idea and made this for users who can not take OTA's because they have Custom Recovery / Root installed.
Features
[*]Stock build made from official KDZ
Made from me taking OTA and dumping Partitions
Stock Build.prop (only 2 extra lines added for DTS, full weather lockscreen)
[*]Unrooted
Latest Canary Magisk Pre-installed (19.4 -087b451e (19308))
system.img modified to keep TWRP
System image size shrunk for being able to flash this on a smaller system partition, mainly caused by vendorizing
Removed dm-verity
Removed rctd (LG's root checker tool daemon)
Enabled opt-encrypt, it's your choice now if you want to encrypt your phone, it's no more forced. TWRP now is capable of decryption (both AOSP and stock) since a few versions
Installation
What you need
Unlocked Bootloader [How to do]
Working TWRP installed (should be installed already, otherwise you wouldn't need this zip )[Link to newest unofficial TWRP]
[*]When you need Root, Latest Magisk [Download]
No Longer Needed on 30a
NOTES
Starting with 30a
Please make a full twrp backup in case anything goes wrong. if after installing you lose your texts or your launcher changes back to the default stock launcher or some other weird bug like that, restoring just your DATA backup will fix it. If after flashing 30a you experience random reboots immediately after booting, DO NOT worry. This same thing happened to me and i believe that its just finishing the update with sprint. When this happened to me, I could see the Finishing Update notification in the pull down. My device rebooted about 3 times and in some cases became extremely laggy and i had to force reboot by holding vol up and power button . After the 3rd boot everything settled down and became stable and no reboots since.
LATEST ZIP
john-fawkes.com LS99830a.zip [Click to Download]
OLDER ZIPS
AFH ZIPS [Download]
How to install
When you are still on Nougat,
you should start fresh: Reboot to recovery using button combo or reboot app (needs root; btw, Magisk offers this possibility too: Menu -> Modules -> three dot menu top right - Reboot to recovery)
Then flash this TWRP.img via image flashing function in TWRP, reboot to recovery again (for fully working new recovery) and do a backup, then copy this backup to your PC.
Then initiate a factory reset. Wipe your system partition too in TWRP advanced wiping menu, copy the 30A firmware zip to your SD and install it. Reboot and enjoy
From Oreo:
For clean install: Factory reset and wipe system
You can also keep your data by simply dirty flashing the zip. *Be aware that problems may occur, maybe you need to do a factory reset to start fresh*
Flash the 30A zip, then Magisk zip when you need root, then reboot to System = you're DONE
P.S.: could be, that you first need to boot up your fresh install and set it up before you can flash magisk.No Longer Needed on 30a. Just Flash 30a Zip.
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 (in newest TWRP SU is disabled, and the option to install the TWRP app is disabled too.)
Rom Version
Android Version: 8.0 Oreo
Android security patch level: 2019-08-1
Don´t forget to hit the thanks-button if you like this zip! :good:
You want to help me with a [donation?] Not asking for it, I have fun doing this for you, but feel free...
Now this is what I like to see right here.bout to leave havoc in start flashing this asap I miss stock anyways thanks @JohnFawkes
Deandre7452 said:
Now this is what I like to see right here.bout to leave havoc in start flashing this asap I miss stock anyways thanks @JohnFawkes
Click to expand...
Click to collapse
Your welcome lol. Took me forever to do this. Had to backup and then wipe data then flash factoryls998 zip from sprint thread, then take Ota, the use lgup to dump all partitions then kdz to us99820e to root again then create flashable zip. I've tested it and it boots just fine
I can add this to WTF instructions tonight -- to join the Verizon and AT&T stock firmware TWRP-FLASHABLE zips already listed.
Thanks for you, @seadersn and @david.542569 efforts in making the North America stock firmware TWRP-FLASHABLE zip ROMs.
JohnFawkes said:
Your welcome lol. Took me forever to do this. Had to backup and then wipe data then flash factoryls998 zip from sprint thread, then take Ota, the use lgup to dump all partitions then kdz to us99820e to root again then create flashable zip. I've tested it and it boots just fine
Click to expand...
Click to collapse
Damn my brother you went through the struggle ? do not remind me, because I went through some before flashing stocks and roms with converting.
---------- Post added at 07:21 PM ---------- Previous post was at 07:19 PM ----------
ChazzMatt said:
I can add this to WTF instructions tonight -- to join the Verizon and AT&T stock firmware TWRP-FLASHABLE zips already listed.
Thanks for you, @seadersn and @david.542569 efforts in making the North America stock firmware TWRP-FLASHABLE zip ROMs.
Click to expand...
Click to collapse
Chazz I see you have a lot of update to do
ChazzMatt said:
I can add this to WTF instructions tonight -- to join the Verizon and AT&T stock firmware TWRP-FLASHABLE zips already listed.
Thanks for you, @seadersn and @david.542569 efforts in making the North America stock firmware TWRP-FLASHABLE zip ROMs.
Click to expand...
Click to collapse
Sounds good :good: btw if anyone hears about us998 kdz updates please let me know. That's next on the list. While I'm waiting on that I'm going to finish the magisk module for @Whiskeyomega audio mod. Got permission from him to not only turn it into a Magisk module but im using xmlstarlet to do it. Xmlstarlet is a xml parser. It allows on the fly editing of xml files. This will allow the device to keep its original mixer_paths xml and my module just add the modifications in. This is extremely useful since whisky and myself both have seen LG deploy multiple mixer paths xmls. Why? No idea. Every regions mixer_paths is different. Not by much. But in my head patching is ALWAYS better than replacing :good::good:
@mattgyver please delete the 2 posts
JohnFawkes said:
@mattgyver please delete the 2 posts
Click to expand...
Click to collapse
:crying: This place is the Krypton to my Superman. I have no power here. I'm just a regular user in "this neck of the woods". You'll need to report the posts so the mods for the LG forums see them to delete them. Really, though, replacing content of the posts with "deleted" has the same effect.
Thanks man!
I have been having too many weird problems on my 21A and was about to do a wipe and clean flash of that one from back in May, and wasn't looking forward to it. I've been using the same system partition for probably 3 months without resetting anything.
I'm excited now that I can flash an updated version instead, now! Ill try it in the next 2-3 days and let you know if anything feels odd (I don't suspect that since you say it's about 100% stock).
Thanks again for your work, and taking the time to upload a TWTP flashable version :good:
.
Sent from my LG-LS998 using XDA Labs
Thanks! Looking forward to flashing this.. haven't flashed anything since 21A... You think dirty flash is ok??
Lurien said:
Thanks! Looking forward to flashing this.. haven't flashed anything since 21A... You think dirty flash is ok??
Click to expand...
Click to collapse
should be yes
Ive been running it over a full day now, debloated and tweaked a bit. RCS and VoLTE is working after ##72786# and a PRL and profile update.
I don't have any obvious issues, thanks again!
Sent from my LG-LS998 using XDA Labs
syndre said:
Ive been running it over a full day now, debloated and tweaked a bit. RCS and VoLTE is working after ##72786# and a PRL and profile update.
I don't have any obvious issues, thanks again!
Click to expand...
Click to collapse
Dirty flash?
Lurien said:
Dirty flash?
Click to expand...
Click to collapse
I did a clean flash and restored my apps from google (first boot up) and then used titanium backup to restore app data for the ones that needed it.
syndre said:
I did a clean flash and restored my apps from google (first boot up) and then used titanium backup to restore app data for the ones that needed it.
Click to expand...
Click to collapse
Thank for the reply. May I ask what rom you were running? Thanks..
Lurien said:
Thank for the reply. May I ask what rom you were running? Thanks..
Click to expand...
Click to collapse
Before this one I was using the stock Sprint 21A ROM that @JWnSC shared in his US998 to LS998 guide here.
I never could get an AOSP ROM to work the way I wanted on a LG V-series phone, even though I still try every 2-3 months, going back probably 4 years. Especially now that Sprint has RCS and VoLTE activated on their Network, I don't see an AOSP ROM on this device working with those two things functioning any time soon, if ever. That and the DAC not being perfect are the reasons I'm still on stock LG.
I wouldn't ever recommend an LG V-phone to anyone on Sprint who plans on using it as a daily driver with AOSP. Those LTE features will probably never be supported.
.
syndre said:
Before this one I was using the stock Sprint 21A ROM that @JWnSC shared in his US998 to LS998 guide here.
I never could get an AOSP ROM to work the way I wanted on a LG V-series phone, even though I still try every 2-3 months, going back probably 4 years. Especially now that Sprint has RCS and VoLTE activated on their Network, I don't see an AOSP ROM on this device working with those two things functioning any time soon, if ever. That and the DAC not being perfect are the reasons I'm still on stock LG.
I wouldn't ever recommend an LG V-phone to anyone on Sprint who plans on using it as a daily driver with AOSP. Those LTE features will probably never be supported.
.
Click to expand...
Click to collapse
Thanks for the reply. I'm also running that same 21A ROM.. I figured a dirty flash would be ok,.. according to the OP dirty flash should be fine.. will try in the next few days.. As far as AOSP ROMS I've stayed away from them after reading about all those issues.. I've never been a huge fan of AOSP ROMS but in the the past I've tried them out on other phones just to flash and try something new...
I have not seen any mention of this yet, but I would like to mention the fact that that most of the major LG stock apps have updates to them on apkmirror. Camera, QMemo, LGHealth, LGBackup, FMRadio, SmartWorld, Gallery3D v7.0 and a few others.
I install these apks then use LP to integrate them into /system . You must put magisk into core only mode when you integrate the updates into the ROM, otherwise you'll just get errors like "not enough space on target".
I actually made TWRP flashable zips for all these updated apps so that you can just flash them in recovery and not worry about having to "integrate" anything. If there's enough interest in these zips from others, I can upload them to a cloud somewhere and share them with everyone.
.
Sent from my LG-LS998 using XDA Labs
Compared to 21a, is this worth the risk? Does it have a new radio? Could someone post their baseband?
---------- Post added at 10:29 PM ---------- Previous post was at 09:50 PM ----------
I seem to have lost LTE on a dirty flash ... Is there something else I have to do with the Sprint modem? Baseband is Def different
Perhaps I am just getting bad LTE reception today, but I am only getting 3g...odd
islandfever said:
Compared to 21a, is this worth the risk? Does it have a new radio? Could someone post their baseband?
---------- Post added at 10:29 PM ---------- Previous post was at 09:50 PM ----------
I seem to have lost LTE on a dirty flash ... Is there something else I have to do with the Sprint modem? Baseband is Def different
Perhaps I am just getting bad LTE reception today, but I am only getting 3g...odd
Click to expand...
Click to collapse
I've been running this for a little over a week now and I dirty flashed between us998 20e ls998 21a and this 26a and I've had lte with all 3 the entire time. Haven't switched to 3g once