Related
Is this at all possible? When attempting to downgrade with LGUP, it interrupts the flashing process (usually) around 9% with this error:
{
"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"
}
Is there a way to force-flash it regardless of this error? Or am I stuck without root forever?
Any answers are greatly appreciated.
At this moment in time the answer is NO. This is why you want to not do an upgrade until root is confirmed for the newer OS. Once recovery is available maybe you might be able to get root back.
I should correct myself you can't use the kdz files and go back to lolipop
details here :
http://forum.xda-developers.com/lg-v10/general/guide-lg-v10-stock-firmware-to-stock-t3224170
I was thinking about the TWRP method before, my bad.
LBJM said:
I should correct myself you can't use the kdz files and go back to lolipop
details here :
http://forum.xda-developers.com/lg-v10/general/guide-lg-v10-stock-firmware-to-stock-t3224170
I was thinking about the TWRP method before, my bad.
Click to expand...
Click to collapse
Thank you for the snappy reply! I have been very closely watching these forums on updates to either downgrade to lollipop, or root marshmallow. I sure hope we can get this resolved for people who's phone came with marshmallow
jingTongy said:
Thank you for the snappy reply! I have been very closely watching these forums on updates to either downgrade to lollipop, or root marshmallow. I sure hope we can get this resolved for people who's phone came with marshmallow
Click to expand...
Click to collapse
I had to downgrade using that same software when I purchased my Lg G3 and that alone sold me on the V10. With Samsung phones you are stuck if you have a newer OS.
The main reason you cannot downgrade is that the software won't flash an old version (as it checks your version stub), at all, on Verizon.
mcbeat257 said:
The main reason you cannot downgrade is that the software won't flash an old version (as it checks your version stub), at all, on Verizon.
Click to expand...
Click to collapse
So, with the way you termed it, it sounds like it's a software problem with LGUP?? If so, do you think it can be patched to ignore the version?
jingTongy said:
So, with the way you termed it, it sounds like it's a software problem with LGUP?? If so, do you think it can be patched to ignore the version?
Click to expand...
Click to collapse
The software itself makes it do this, and it is irrevocable and not able to do so in the builds, it reminds me of when I had my galaxy s4 and this happened as well.
According to this thread , you can:
http://forum.xda-developers.com/lg-v10/general/guide-lg-v10-stock-firmware-to-stock-t3224170
I normally do not root my phones, but I am having battery drain problems and I see no advantage to Marshmallow. I may downgrade if I cannot resolve my current problem.
mikekoz said:
According to this thread , you can:
http://forum.xda-developers.com/lg-v10/general/guide-lg-v10-stock-firmware-to-stock-t3224170
I normally do not root my phones, but I am having battery drain problems and I see no advantage to Marshmallow. I may downgrade if I cannot resolve my current problem.
Click to expand...
Click to collapse
Could you quote the part on that post where it talks about downgrading the firmware? As far as I can tell from the link you provided, that post only talks about returning the phone back to stock. And just to be clear, once you install the OTA update to the MM build, your stock is now the MM firmware. Please correct me if I am wrong.
zatanas33 said:
Could you quote the part on that post where it talks about downgrading the firmware? As far as I can tell from the link you provided, that post only talks about returning the phone back to stock. And just to be clear, once you install the OTA update to the MM build, your stock is now the MM firmware. Please correct me if I am wrong.
Click to expand...
Click to collapse
You may be correct, and hopefully somebody more knowledgeable than myself will chime in, but this text is part of the instructions from that thread:
TO GO BACK TO LP FROM MM - Open LGUP on your computer, click on FILE PATH and point it towards your LP KDZ. Close LGUP and re-open LGUP. Make sure you select REFURBISH this will do a FULL wipe, tick BIN file. Press Start. Make cup of tea and be patient
This does not work on the Verizon variant
Sent from my VS990 using XDA-Developers mobile app
mikekoz said:
According to this thread , you can:
http://forum.xda-developers.com/lg-v10/general/guide-lg-v10-stock-firmware-to-stock-t3224170
I normally do not root my phones, but I am having battery drain problems and I see no advantage to Marshmallow. I may downgrade if I cannot resolve my current problem.
Click to expand...
Click to collapse
I was having the same battery drain problem after the Marshmallow update on my V10. I let it go for a couple days to see if things would improve. Unfortunately, things weren't getting any better. While I've rooted a lot of Android phones in the past, I didn't really want to void the warranty on this phone yet.
I went ahead and did a factory reset and the battery is working better than ever. I usually use Titanium Root to backup, but had to rely on LG Backup this time. It worked well enough even though it took a long time to copy everything to the SD Card (about 3 hours for 4 GB). Only things that didn't come through after restoring were my home screen settings and the history for one game. No big deal, about an hour to get everything configured back to original (grab screenshots of your homescreen first).
Pretty thrilled to see the battery performing better than ever. Just got 16 hours out of it yesterday and had 35% left on somewhat light use.
burnsky05 said:
This does not work on the Verizon variant
Sent from my VS990 using XDA-Developers mobile app
Click to expand...
Click to collapse
The instructions say otherwise. There is even links to Verizon drivers. Where do you see that this method does not work for Verizon V10's?
http://forum.xda-developers.com/showthread.php?t=3344828
Sent from my VS990 using XDA-Developers mobile app
The thread also states its for certain models of LG V10 but the LGUP has a anti rollback built into it that will not allow you to go from marshmallow to lollipop on certain models...
burnsky05 said:
http://forum.xda-developers.com/showthread.php?t=3344828
Sent from my VS990 using XDA-Developers mobile app
The thread also states its for certain models of LG V10 but the LGUP has a anti rollback built into it that will not allow you to go from marshmallow to lollipop on certain models...
Click to expand...
Click to collapse
Thanks. :good:
So, maybe someone could come up with a anti rollback work around? Hopefully, or some other alternative.
hann1balk1ng said:
So, maybe someone could come up with a anti rollback work around? Hopefully, or some other alternative.
Click to expand...
Click to collapse
Possible if someone could reverse-engineer LGUP to allow downgrading. I have the lollipop KDZ file, now all I need is a way to flash it to my vs990.
In an attempt to downgrade an error was not seen in LGUP. As far as anyone could tell the phone and LGUP were in sync up until 85% or so and the reboot was initiated. The phone never came back on. LGUP made it to 100% but the phone stayed black. Maybe not,enough time was allowed to pass but the battery was then removed. The phone became a brick and wouldnt start in any mode. When plugged into a computer the computer sees something tries to install a driver then fails. Do not try and downgrade from Marshmallow with LGUP. It will not work.
AMCJUNGLE said:
In an attempt to downgrade an error was not seen in LGUP. As far as anyone could tell the phone and LGUP were in sync up until 85% or so and the reboot was initiated. The phone never came back on. LGUP made it to 100% but the phone stayed black. Maybe not,enough time was allowed to pass but the battery was then removed. The phone became a brick and wouldnt start in any mode. When plugged into a computer the computer sees something tries to install a driver then fails. Do not try and downgrade from Marshmallow with LGUP. It will not work.
Click to expand...
Click to collapse
Oh man that sucks.
Sent from my Nexus 7 using XDA-Developers mobile app
It's not on the net anywhere either, google is not working for the OT Elevate. There are no custom ROMs for the OT Elevate either.
I know that someone has one of these OT Elevate 5017B phones lying around somewhere. Post a stock ROM for download. People are suffering from bricks and soft-bricks. HELP more, we need to start a project making an attempt to catalog stock ROMs for every android device on earth.
There needs to be a larger archive of these ROMS. iOS developers are killing you. They have a database of all of the iOS firmwares, and there is a database of custom firmwares even for the iPhone 6S.
I know that the iPhone's situation is different, that one company designs the hardware and the software, and that everything is proprietary. I also feel there are too many companies making android phones. competition is one thing, but security of an OS is another. different phones from the same year with older versions of the OS on them, not good.
Marshmellow has been released and there are still 2016 phone releases with 4.5 OS on them. That's not secure. Why can't we make Android more secure by building better custom ROMs for more devices? I know there is a big shortage of developers, but you can recruit. Maybe even get funded by an organization, research grant?
Everyone needs more ROMs. Especially for Alcatel OT Elevate. Let's do something about this.
On 3. 1-2-3, Go Team!!!! :highfive: Let's Get It!
I have one of those Alcatel OneTouch phones right now, and I agree completely upon the notion for a catalog of all android devices that can be flashed.
@mU$!c @tyrex420
These Alcatel devices can only get attention if developers have them in their hands to work with. These devices are running a MediaTek SoC and not many developers like to work with those phones because of a lack of source code to work with or incomplete source in some cases. Yes you are correct in saying that Apple is different as it's one software, one hardware but you have to understand Google only set the stage and the companies do the rest. Not every company is Samsung or Sony. Alcatel has a tool which is really good called Mobile Upgrade Tool which has the factory ROM for their devices (which imho they need work on getting those newer devices supported). It works well if you haven't done much modification to your phone. Now the thing is that when those companies take the phones and modify them in some way like in locking the bootloader or hiding fastboot mode (Tracfone,MetroPCS), there's not much that a developer can do about that. Also those companies do not have that same support tool that Alcatel has which re-downloads the factory ROM because they are modified in some way.
Here's the good part about the phone running a MTK SoC. There are third-party tools such as MTK Droid Tools or SmartPhoneFlashTool (SPFT) which enables the users to make factory backups of their ROMs in the event that their devices suffers from a bootloop. What you can now do is become that developer that you are asking for to work on your phone and make something out of it. Be the first to upload a flashable factory ROM for your phone. Create a thread where users can come and post their issues and assist each other positively. It's nothing hard to do unless as I said before the company locks some part of the phone and makes these tools useless. By the way, MTK Droid Tools developer dropped support at Jelly Bean so KitKat and up won't work with the tool as it should.
Again, yes I agree with you in saying it would be nice for a users to find a compilation of ROMs that they can just follow instructions and flash but the thing is source code and users themselves not knowing how to use the tools mentioned above. If you want you can ask me for help in guiding you on how to use the tools. I've been doing this for 3 years now working with MTK and I'm learning something new everyday.
Sorry for my long reply, I hope to see a reply from you concerning getting a factory ROM for this device maybe a thread similar to mine .
@kirito9
Thank you. I learned more in 2 minutes from your reply than in two hours searching the internet. XDA needs more people like you!
-Cheers
bg260 said:
@kirito9
Thank you. I learned more in 2 minutes from your reply than in two hours searching the internet. XDA needs more people like you!
-Cheers
Click to expand...
Click to collapse
You're welcome .
kirito9 said:
You're welcome .
Click to expand...
Click to collapse
I had one of these fall in my lap. Charging port is shot. At least I can remove the battery and charge. I'm trying to see if it's worth fixing. All signs are pointing to no, unfortunately. OEM Bootloader unlock is available but without Fastboot.......
bg260 said:
I had one of these fall in my lap. Charging port is shot. At least I can remove the battery and charge. I'm trying to see if it's worth fixing. All signs are pointing to no, unfortunately. OEM Bootloader unlock is available but without Fastboot.......
Click to expand...
Click to collapse
Hmm so you don't have a working charging/usb port. I doubt you'll be able to do much with this phone in terms of development. Not sure if there is a way to unlock the bootloader from the device itself, doubt it.
kirito9 said:
Hmm so you don't have a working charging/usb port. I doubt you'll be able to do much with this phone in terms of development. Not sure if there is a way to unlock the bootloader from the device itself, doubt it.
Click to expand...
Click to collapse
I'll see if I can get something useful out of it. Maybe a recovery.img, boot.img, system.img. I'll have to use one of those dreadful one-click apps though.
As for the OP I think this is as close as it gets.
http://forum.xda-developers.com/wiki/
Being a public wiki everyone is welcome to add to or amend it.
bg260 said:
I'll see if I can get something useful out of it. Maybe a recovery.img, boot.img, system.img. I'll have to use one of those dreadful one-click apps though.
As for the OP I think this is as close as it gets.
http://forum.xda-developers.com/wiki/
Being a public wiki everyone is welcome to add to or amend it.
Click to expand...
Click to collapse
Yeah although the information is quite old still useful.
Root with Kingroot and backup with flashify haha. But won't you need the unlocked bootloader to root?
Got side tracked. Device currently disassembled, trying to replace usb but it is hard soldered to the Motherboard. Cheap phones....
bg260 said:
Got side tracked. Device currently disassembled, trying to replace usb but it is hard soldered to the Motherboard. Cheap phones....
Click to expand...
Click to collapse
Ahh cheap phone problems. Let me know if you get through.
Successfully rooted with Kingroot v4.92 . I have included others JIC.
I used The paid SuperSUme Pro to eradicate Kinguser from the device. Here are some other options.
http://forum.xda-developers.com/gal...ve-kinguser-replace-supersu-sch-i545-t3334533
After updating SuperSu via the playstore I installed Busybox Pro, but the unpaid version is fine. At which point I updated the SU binaries the "Normal Way" without a hitch.
{
"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"
}
@kirito9
I'll start with a system.img What else do you need?
Thanks
-Bg260
bg260 said:
Successfully rooted with Kingroot v4.92 . I have included others JIC.
I used The paid SuperSUme Pro to eradicate Kinguser from the device. Here are some other options.
http://forum.xda-developers.com/gal...ve-kinguser-replace-supersu-sch-i545-t3334533
After updating SuperSu via the playstore I installed Busybox Pro, but the unpaid version is fine. At which point I updated the SU binaries the "Normal Way" without a hitch.
View attachment 3906591
@kirito9
I'll start with a system.img What else do you need?
Thanks
-Bg260
Click to expand...
Click to collapse
Did you get the the USB removed? Hmm what are we trying to achieve? A full backup or a ROM?
kirito9 said:
Did you get the the USB removed? Hmm what are we trying to achieve? A full backup or a ROM?
Click to expand...
Click to collapse
I wasn't able to replace the USB. Without an unlocked bootloader there is not much I can do. Thought maybe I would help the cause is all. I personally will probably screw with it till it bricks. IDK. Thought someone could at least get a recovery going. I'm not a developer in that sense. I usually just crack open the system.img and add/remove a few thing to my liking. I'll go ahead and dump a system/boot/recovery.img package on AFH if anyone has interest.
bg260 said:
I wasn't able to replace the USB. Without an unlocked bootloader there is not much I can do. Thought maybe I would help the cause is all. I personally will probably screw with it till it bricks. IDK. Thought someone could at least get a recovery going. I'm not a developer in that sense. I usually just crack open the system.img and add/remove a few thing to my liking. I'll go ahead and dump a system/boot/recovery.img package on AFH if anyone has interest.
Click to expand...
Click to collapse
Ahh, that'd be nice. Someone might mess up their stock recovery/boot/system. Please upload and maybe I can try to get a custom recovery for this device. Then make a full backup using the custom recovery.
kirito9 said:
Ahh, that'd be nice. Someone might mess up their stock recovery/boot/system. Please upload and maybe I can try to get a custom recovery for this device. Then make a full backup using the custom recovery.
Click to expand...
Click to collapse
Found something different, the system partition on mmcblk0p33 is 800mb 535 used.
There is also something called custpack on mmcblk0p32 at 1gb total 663mb used. I made an img of both. I'll upload it in a little bit.
Quick question, I have been using furiusisomount with Linux mint cinnamon to rummage around system images. Lately it throws an error and won't mount. Is this familiar to you? I'm not as proficient with the CLI as I'd like to be so I often rely on GUI.
bg260 said:
Found something different, the system partition on mmcblk0p33 is 800mb 535 used.
There is also something called custpack on mmcblk0p32 at 1gb total 663mb used. I made an img of both. I'll upload it in a little bit.
Quick question, I have been using furiusisomount with Linux mint cinnamon to rummage around system images. Lately it throws an error and won't mount. Is this familiar to you? I'm not as proficient with the CLI as I'd like to be so I often rely on GUI.
Click to expand...
Click to collapse
Ok, both images are critical for Alcatel devices running MTK SoC to get it booting. The furiusisomount I'm not familiar with but maybe I can help. What error are you getting?
kirito9 said:
Ok, both images are critical for Alcatel devices running MTK SoC to get it booting. The furiusisomount I'm not familiar with but maybe I can help. What error are you getting?
Click to expand...
Click to collapse
Ok, Here you go. It has boot, aboot, recovery, system and custpack. Are you going to need patitioning info? Be easy if I had adb. But I don't
I'll get back to you on that error. I'm having some other issues and I think it might be systemic. I may have to do a fresh install of Mint.
Let me know what else you need. Happy to help.
https://www.androidfilehost.com/?fid=385035244224385460
bg260 said:
Ok, Here you go. It has boot, aboot, recovery, system and custpack. Are you going to need patitioning info? Be easy if I had adb. But I don't
I'll get back to you on that error. I'm having some other issues and I think it might be systemic. I may have to do a fresh install of Mint.
Let me know what else you need. Happy to help.
https://www.androidfilehost.com/?fid=385035244224385460
Click to expand...
Click to collapse
I think there may be another way to get the partitioning info but let me look into it. Thanks for the files and will let you know if I need anything else .
kirito9 said:
I think there may be another way to get the partitioning info but let me look into it. Thanks for the files and will let you know if I need anything else .
Click to expand...
Click to collapse
See if this is what you need. Created it with DiskInfo Pro. I used a different machine and mounted the system image fine. I thought it was a bad copy because the Build.prop displayed as broken. Then I realized it was just a symlink to the actual build.prop in custpack. At any rate, there's a copy of the build.prop in there as well.
View attachment build.prop-partitions-5017b.zip
UPDATE: Axon 7 A2017U Build 29 (MR3)
New OTA update is arriving and looking forward for what bring to the table.
aerospaceman Employee Oct 30, 2016 6:01 PM
Over the next 24 to 72 hours, you can expect our 3rd software update (MR3) to the Axon 7 (A2017U). This update will bring your device to the latest build, B29. This update comes less than one and a half months from the previous one, but the more exciting news is that we're in parallel paths to deploy Nougat as quickly as possible.
Here are the latest updates you will see on B29 (coming from the previous build, B27):
Notification bell is now optional (hooray!)
New application management policy to enhance battery life
Optimized video camera focus on moving objects
Resolved .FLAC file playback issue
Visual Voicemail optimized for dual SIM
Updated fix for Mute Call issue
Other general enhancements
Note: This is an over-the-air (OTA) update. To check availability of an update, click on "Settings -> Updates."
Aside from this update, you can bet on our R&D team being hard at work on Android N. Early tests from your Mod Squad have been very positive and we trust that many of you will also not sleep for the first several days after upgrading. Setting Nougat aside, we remain heads down prioritizing fixes and enhancements for our community. Your constant feedback, both positive and negative, continue to motivate our R&D team. So please don't let up on your interactions with us and each other about the Axon 7. Until the next update, please drop a comment below to add further motivation for your R&D team!
Click to expand...
Click to collapse
-------------------------------------------------------------------------
UPDATE: Axon 7 A2017U Build 29 (MR3) Announcement Link
-------------------------------------------------------------------------
TWRP Flashable Files can be found here : TWRP_A2017U.B29_Bootstack_StockSystem_Files
What's does the " Parallel paths" mean....
S8ntsHaz3 said:
What's does the " Parallel paths" mean....
Click to expand...
Click to collapse
Ha! I was thinking the same thing. It sounds like more vague crap from ZTE like normal.
jonathan3579 said:
Ha! I was thinking the same thing. It sounds like more vague crap from ZTE like normal.
Click to expand...
Click to collapse
I'm wondering if it means that it's at a parallel in development as far as time between updates... Like b27>b29 was 1 and 1/2 months and that's what they're lookin at for a time frame?
S8ntsHaz3 said:
What's does the " Parallel paths" mean....
Click to expand...
Click to collapse
jonathan3579 said:
Ha! I was thinking the same thing. It sounds like more vague crap from ZTE like normal.
Click to expand...
Click to collapse
S8ntsHaz3 said:
I'm wondering if it means that it's at a parallel in development as far as time between updates... Like b27>b29 was 1 and 1/2 months and that's what they're lookin at for a time frame?
Click to expand...
Click to collapse
my guess is " performing of multiple operations simultaneously " meaning getting MR's OTA and working Naugat (Android 7) at the same time???
well i'm just assuming so , and i assume next Update will be N release., you know B3x
DrakenFX said:
my guess is " performing of multiple operations simultaneously " meaning getting MR's OTA and working Naugat (Android 7) at the same time???
well i'm just assuming so , and i assume next Update will be N release., you know B3x
Click to expand...
Click to collapse
Oh how I hope your right!!!!
Now to wait for the download link
xtermmin said:
Now to wait for the download link
Click to expand...
Click to collapse
It's here!
{
"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 ZTE A2017U using Tapatalk
toyanucci said:
It's here!
Click to expand...
Click to collapse
How'd you get the embedded battery percentage?! I sorely miss that from my Nexus 6P.
jonathan3579 said:
How'd you get the embedded battery percentage?! I sorely miss that from my Nexus 6P.
Click to expand...
Click to collapse
There's an app in play store to enable it in any device!
Sent from my ZTE A2017U using Tapatalk
toyanucci said:
There's an app in play store to enable it in any device!
Click to expand...
Click to collapse
Oh sweet, thanks. I think I tried it before but it didn't stick after rebooting. Has it changed since then? If so, I'm definitely gonna have to search for it again.
I have the option for the update as well. Waiting as I'm rooted.
Here is the download link if anyone wants to play with it.
update_P996A01_B27_to_B29.up
I'll be looking into it and try to create a flashable zip for us TWRP users
DrakenFX said:
Here is the download link if anyone wants to play with it.
update_P996A01_B27_to_B29.up
I'll be looking into it and try to create a flashable zip for us TWRP users
Click to expand...
Click to collapse
Thanks for looking into a twrp version!
Sent from my ZTE A2017U using Tapatalk
Parallel paths does indeed mean they are simultaneously working on updates and the long awaited Nougaaaattttt update. ZTE has done a good job updating and listening to their customers in the z-forum. Lets hope this plus Official CM and unlock bootloader without breaking warranty will help ZTE be known as a developer friendly Own.
How do we install if we are unlocked bootloader and rooted??
Do we have any idea if flashing U roms on G device works? Would love to get rid of the bell
Here over in europe, i just received for my A2017G an 703mb big B05 Update.(previous B03)
Strange that ours is 703mb big (hope they fix the youtube freeze Problem) and also supports optional notification bell (no info for that in the change log)
Take a look:
DrakenFX said:
Here is the download link if anyone wants to play with it.
update_P996A01_B27_to_B29.up
I'll be looking into it and try to create a flashable zip for us TWRP users
Click to expand...
Click to collapse
Here is an Mega Mirror for the B29 update. Just in case.
I have simply copied it from its location "data/data/com.zte.zdm/files" where the updater places its OTA files.
https://mega.nz/#!K050XAqT!6EBTgtX13VTdAOiUjiYqeE6jemeOJ2mN8smrrreai6o
MD5: 9a7f45caf459a21a905de0c543748309
If you place the file into that directory. You should be good to go using the inbuild updater.
Dewaynelives said:
How do we install if we are unlocked bootloader and rooted??
Click to expand...
Click to collapse
I was on B27, unlocked bootloader, TWRP recovery, rooted, with changes to /system, and have successfully upgraded to B29 (w/ same modifications). Since I made changes to /system (AdAway, Titanium Backup, AFWall) and wanted a clean slate for everything, I wiped my A7.
If you don't want to factory reset your device and didn't make any changes to /system, you might only have to unroot, restore stock boot.img and stock recovery.img via TWRP (from rczrider's topic linked below), install B29.zip in stock recovery, flash TWRP, then flash root, but I didn't do it personally, so no guarantees.
Anyway, this is what I did. Some of these steps might not have been needed, and probably could have been done differently, but it's what worked for me, and yes I like rebooting:
1. Download the B29 update, DrakenFX's B27 StockSystem zip for TWRP (which also flashes stock boot.img), stock B27 recovery.img from rczrider, and SuperSU 2.65. Put all on microSD.
2. Booted into TWRP and did a factory reset, rebooted back into TWRP and flashed DrakenFX's B27 StockSystem ZIP, rebooted back into TWRP and flashed stock B27 recovery.img, rebooted device.
3. Powered on the device and made sure it booted into OS fine and was still reporting the correct amount of internal storage space. Rebooted into stock recovery and flashed the B29 update.zip from my microSD card. Installed fine, rebooted into OS to made sure it still worked.
4. Rebooted into fastboot, connected to my computer and flashed Unjustified Dev's TWRP via Minimal ADB & Fastboot, booted into TWRP and flashed SuperSU 2.65 from my microSD, let the device reboot itself a couple of times.
I now have B29 with unlocked bootloader, TWRP, and root.
NOTE: Something I noticed when I was going through and disabling system apps: WeShare can't be disabled from the Settings > Apps menu, but can be disabled by opening the app drawer, pressing and holding on it, and dragging it up to "Disable" at the top of the screen.
However, it would probably be easier to just wait for DrakenFX to create custom TWRP install zips for B29.
US998 original, TWRP 3.2.3-7-DataImg, bootloader unlocked
Have tried installing both Lineage and LiquidRemix, with no success. Upon reboot, phone bootloops. Easily put it in download mode and start all over again, using factory image (data seems to be getting corrupted).
When in recovery: factory reset, then wipe data, dalvik, cache, and system. Only installing ROM at this time, trying to weed out potential problems.
Tried flashing just no-verity earlier and phone was stuck on splash screen, then.
Any suggestions on this would be appreciated. Not sure where to pull a logcat, even if available, as I am not 100% sure where the problem is originating from.
mpicasso said:
snip.
Click to expand...
Click to collapse
Did you ever update stock firmware to newest update before trying to flash a custom ROM?
Sent from my LG-H932 using XDA Labs
BROKEN1981 said:
Did you ever update stock firmware to newest update before trying to flash a custom ROM?
Click to expand...
Click to collapse
Was rooted, with Magisk, on US99820H, when i did it the 1st time.
Thought there was a chance maybe i had not removed encryption but it seems to be something causing data corruption.
mpicasso said:
Was rooted, with Magisk, on US99820H, when i did it the 1st time.
Thought there was a chance maybe i had not removed encryption but it seems to be something causing data corruption.
Click to expand...
Click to collapse
I've no idea if this will or won't help, but have an ls998 converted to us998 which has successfully booted numerous of the custom roms, even from us99820H.
I always remove any accounts on phone, any finger prints unlock, pins, everything. Then do a factory reset. It should be bone stock at that point (for 20H), except of course bl unlocked and twrp installed.
Then, install the rom as you have been. If it doesn't boot, in the various after market rom threads people have discussed fixes they've found. But from what I've read it seems a pretty common problem is the device itself. You say it was an original us998? Was that US Cellular us998? I had one of those, it wouldn't boot an aftermarket rom either.
good luck, Cheers
Did you try flashing the TWRP ready firmware for your phone?
This is what ChazzMatt said: "If you are installing/updating latest US998 firmware for the first time after bootloader unlock/root, you should flash 20e zip (below), then 20f zip, 20g zip, 20h zip back-to-back in TWRP, then flash Magisk. If you go straight to 20h via TWRP-flashable zip from very early Oreo, you will most likely have problems. There were massive changes starting with US998 20f and you need the prior 20e as foundation before going on to 20h. You should also do this if coming from a custom ROM."
So, I am guessing you can flash a custom ROM by just flashing 20e first then the custom ROM after. Instead of flashing a custom ROM from 20h, which is known to cause issues.
AsItLies said:
You say it was an original us998? Was that US Cellular us998? I had one of those, it wouldn't boot an aftermarket rom either.
Click to expand...
Click to collapse
Thought US998U was US Cellular but went on to their website to verify IMEI...device not compatible with their network.
mpicasso said:
Thought US998U was US Cellular but went on to their website to verify IMEI...device not compatible with their network.
Click to expand...
Click to collapse
IF it's been converted from LS998 you'll get a false result like that. You're sure you have original US998?
US998U just means US998 V30+. U.S. CELLULAR sold them as well as B&H Photo, Best Buy, Amazon...
I know nothing about U.S. Cellular. It's possible they only allow phones they sold, whose IMEI are on their database. I don't know.
skittles-1999 said:
This is what ChazzMatt said: "If you are installing/updating latest US998 firmware for the first time after bootloader unlock/root, you should flash 20e zip (below), then 20f zip, 20g zip, 20h zip back-to-back in TWRP, then flash Magisk. If you go straight to 20h via TWRP-flashable zip from very early Oreo, you will most likely have problems. There were massive changes starting with US998 20f and you need the prior 20e as foundation before going on to 20h. Instead of flashing a custom ROM from 20h, which is known to cause issues.
Click to expand...
Click to collapse
TWRP: TWRP-3.2.3-7-default.img
Haha - had just noticed this comment before coming on here to respond! Yes, I went from B to H, without the tweeners. Honestly thought I had read everything...
Did not see the note where flashing from 20H causes problems. Do you have a link for that?
Will go back and install E and F, at minimum, as he said massive changes happened with 20F. Really want this phone to work with AOSP rom's, especially since I paid around $250 for it, but willing to still use it stock and rooted. Phone before this was a Nexus 6, which I hung on to for as long as I could (over 3 years...) but after this, going to OnePlus or Pixel.
Thanks for your help!
mpicasso said:
Thought US998U was US Cellular but went on to their website to verify IMEI...device not compatible with their network.
Click to expand...
Click to collapse
Did LG developers website give u the unlock bin for this device? That would be the definitive indication of what device it is as there is only that one and the 930 you can get unlock codes for.
*If* that's the case, that LG identifies it for unlock purposes, then I can only say be sure to have done what's mentioned above in removing accounts etc. After doing that, and an aftermarket rom won't boot? I'd be at a loss. It really wouldn't make any sense at all.
Cheers
mpicasso said:
Thought US998U was US Cellular but went on to their website to verify IMEI...device not compatible with their network.
Click to expand...
Click to collapse
AsItLies said:
Did LG developers website give u the unlock bin for this device? That would be the definitive indication of what device it is as there is only that one and the 930 you can get unlock codes for.
*If* that's the case, that LG identifies it for unlock purposes, then I can only say be sure to have done what's mentioned above in removing accounts etc. After doing that, and an aftermarket rom won't boot? I'd be at a loss. It really wouldn't make any sense at all.
Cheers
Click to expand...
Click to collapse
LG NEVER gave bootloader unlock code for any US998U aka US998 V30+ (128GB). I have Open Market US998U (V30+) bought from B&H Photo and had to use WTF bootloader unlock.
Only my US998 V30 (64GB) bought from B&H Photo was eligible for LG bootloader unlock code, and even then you have to hack the LG Developer drop down menu to get a code. No US998 is listed on the LG Developer website.. LG never officially put the US998 on the approved list. Yes, for original B&H Photo 64GB US998, you can still get LG bootloader unlock code -- but you have to know how to do it. However, we have no need with WTF exploit.
ChazzMatt said:
Only my US998 V30 bought from B&H Photo was eligible for bootloader unlock code, and even then you have to hack the LG Developer drop down menu to get a code.
Click to expand...
Click to collapse
^ this...
Bought new SD card today and doing as ChazzMatt originally suggested, which is start at B, then do E and up. Stopping at G, and trying from there.
Thank you...but no thanks to the drama.
I appreciate the help but sadly, skittles-1999 offered the best response, which I must have overlooked when reading everything I did.
Phone was bought off of Swappa and assured by seller it was a US998U. Box stated as such, model number shows as LG-US998. KDZ downloaded/installed, from LG, was a US998. Cannot think of any other way to verify that it truly is a US998, original.
Things I have changed - new microSD card, 1, and 2, have gone from B, to E, F, to G.
Have to step out but will try installing lineage later.
Tried installing Lineage, Magisk, and Gapps all together. Will try to go back and reinstall just Lineage, to see if that fixes the problem.
Thanks for everything.
Erm calm down?
Thread cleaned. No flaming please. Read Rules.
{
"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"
}
-XDA Staff
Giving up...almost
Have tried flashing this:
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Running US99820H, Magisk 19.3 with root. Even tried installing Lineage 15.0 (8.1) but again with no success.
System wipe
Advanced wipe: Data, Internal Storage, System, Cache, and Dalvik Cache
Format data
Reboot recovery
Install ROM
Install DM-verity
Install Magisk
Reboot
Can flash 20H zip, along with any other Magisk module, with no problem. Guessing it has something to do with boot.img?
mpicasso said:
Have tried flashing this:
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Running US99820H, Magisk 19.3 with root. Even tried installing Lineage 15.0 (8.1) but again with no success...
Click to expand...
Click to collapse
I thought 19.3 was not working properly for us.
Try 18.1 which definitely does work
gazzacbr said:
I thought 19.3 was not working properly for us.
Try 18.1 which definitely does work
Click to expand...
Click to collapse
Sorry, I install 18.1, them updates. Suggesting to not update before installing?
mpicasso said:
Sorry, I install 18.1, them updates. Suggesting to not update before installing?
Click to expand...
Click to collapse
Yes.
Sent via open market LG US998 V30/V30+
ChazzMatt said:
Yes.
Click to expand...
Click to collapse
Have downgraded to US998E. Is there a possibility partitions on the US998U have the same problem as others, such as the H931/H933? Would I brick my phone if I partitioned, using an H933 rom?
Tried installing bootlegger, with permissive kernel, but bootlooping as we speak. Have been at this, off and on, for days, with no success installing an AOSP rom but will try the suggestion offered. At the point I am ready to keep this as a backup and buy either an H930 or a US998, no plus.
mpicasso said:
Have downgraded to US998E. Is there a possibility partitions on the US998U have the same problem as others, such as the H931/H933? Would I brick my phone if I partitioned, using an H933 rom?
Click to expand...
Click to collapse
No, plenty of US998U (V30+) are running AOSP/Lineage custom ROMs. US998, US998U, US998R are all identical internally -- except for storage amount or RAM.
If you wish to try H933 workaround, no you won't brick the phone.
Ok using Lgup put my foot in it with complete wipe and flashing a kdz and now lost the imei number and whatnot can someone help.......please
You didn't lose your IMEI just by flashing a KDZ using the recommended Upgrade, Partition DL or Refurbish methods. You must have flashed using some mode NOT recommended in any of the Instructions. We specifically say to NOT mess with any modes not mentioned.
In all my Dev Patched LGUP instructions, I include this:
ChazzMatt said:
{
"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"
}
WARNING: In LGUP do NOT go messing with modes not mentioned in these instructions. Especially do NOT use Chip Erase.
https://9to5lg.com/lgup-1-15-manual-how-to-unbrick-restore-your-lg-devices-with-lgup/
Click to expand...
Click to collapse
ChazzMatt said:
You didn't lose your IMEI just by flashing a KDZ using the recommended Upgrade, Partition DL or Refurbish methods. You must have flashed using some mode NOT recommended in any of the Instructions. We specifically say to NOT mess with any modes not mentioned.
In all my Dev Patched LGUP instructions, I include this:
Click to expand...
Click to collapse
If I didn't do it the way I did wouldn't get update......
stinka318 said:
If I didn't do it the way I did wouldn't get update......
Click to expand...
Click to collapse
Why do you claim that?
You simply flash KDZ via Refurbish or Partition DL with Dev Patched LGUP and your phone is updated.
Most times you can even flash KDZ via Upgrade mode and keep data.
In ALL the KDZ threads we have, where users update their phones all the time, we only use Upgrade, Refurbish, or Partition DL modes.
What variant do you have?
ChazzMatt said:
Why do you claim that?
You simply flash KDZ via Refurbish or Partition DL with Dev Patched LGUP and your phone is updated.
Most times you can even flash KDZ via Upgrade mode and keep data.
In ALL the KDZ threads we have, where users update their phones all the time, we only use Upgrade, Refurbish, or Partition DL modes.
What variant do you have?
Click to expand...
Click to collapse
The fact the update is out there and tried LG bridge and tried a few other ways to push the update to no success........it is a v30 us998 being used in Australia is probably the reason.
I'm using the device right now so it is only a cosmetic thing at the moment.
stinka318 said:
The fact the update is out there and tried LG bridge and tried a few other ways to push the update to no success........it is a v30 us998 being used in Australia is probably the reason.
Click to expand...
Click to collapse
Follow the instructions in the US998 KDZ thread. We post all the KDZ images there, with several mirrors for each KDZ release.
You simply download the KDZ, flash via Upgrade mode with the Dev Patched LGUP -- which is also provided in the first post. At the most use Refurbish mode.
There's plenty of Instructions in the KDZ thread and how to use Dev Patched LGUP.
See Post#1.
https://forum.xda-developers.com/lg-v30/development/us998-lg-v30-us998-us99820a040330-kdz-t3786337
ChazzMatt said:
Follow the instructions in the US998 KDZ thread. We post all the KDZ images there, with several mirrors for each KDZ release.
You simply download the KDZ, flash via Upgrade mode with the Dev Patched LGUP -- which is also provided in the first post. At the most use Refurbish mode.
There's plenty of Instructions in the KDZ thread and how to use Dev Patched LGUP.
See Post#1.
https://forum.xda-developers.com/lg-v30/development/us998-lg-v30-us998-us99820a040330-kdz-t3786337
Click to expand...
Click to collapse
Download was not the problem it was the fact that it didn't want to update with refurbish or upgrade parts
Despite it being recognized by LGup.........
stinka318 said:
Download was not the problem it was the fact that it didn't want to update with refurbish or upgrade parts
Despite it being recognized by LGup.........
Click to expand...
Click to collapse
What LGUP were you using?
ChazzMatt said:
What LGUP were you using?
Click to expand...
Click to collapse
Tried a few different ones until i tried store version 1.14 it was a China man that i got it off so it may have been unlocked by a third-party in china.....
stinka318 said:
Tried a few different ones until i tried store version 1.14 it was a China man that i got it off so it may have been unlocked by a third-party in china.....
Click to expand...
Click to collapse
The Dev Patched LGUP in that US998 KDZ thread works for everyone around the world -- unless the seller did something to that USS98 with Octoplus box which Matt may prevent that Dev Patched LGUP from working right.
I saw that one time before with AS998, where Dev Patched LGUP couldn't do anything because dealer had messed it up with Octopus/Octoplus box when converting it from LS998.
ChazzMatt said:
The Dev Patched LGUP in that US998 KDZ thread works for everyone around the world -- unless the seller did something to that USS98 with Octoplus box which Matt may prevent that Dev Patched LGUP from working right.
I saw that one time before with AS998, where Dev Patched LGUP couldn't do anything because dealer had messed it up with Octopus/Octoplus box when converting it from LS998.
Click to expand...
Click to collapse
I have the box with the imei number on it......it is i reckon it is because someone didn't want to pay to get it unlocked by us cellular so they paid a third party to do it it has happened b4 to me......
Using dual mode LG UP in OP of US998 kdz thread and directions from post #6 on "how to get past stuck v30 logo", go back to freshly kdz 20h, H933 Nougat to get imei and partitions back, then 20e, then 20h, and lastly pie 30b
stinka318 said:
I have the box with the imei number on it......it is i reckon it is because someone didn't want to pay to get it unlocked by us cellular so they paid a third party to do it it has happened b4 to me......
Click to expand...
Click to collapse
All US998 are already carrier unlocked. Even U.S. Cellular.
If you're trying to update to Pie it's a different KDZ thread. I assumed you were trying to update to latest US998 Oreo since to you said it wouldn't update...
[US998][STOCK][PIE]LG V30 US998 US99830b_00_0902.KDZ
https://forum.xda-developers.com/lg-v30/development/us998-lg-v30-us998-us99830a000704-kdz-t3952256
ChazzMatt said:
All US998 are already carrier unlocked. Even U.S. Cellular.
Click to expand...
Click to collapse
Well that thows out that theory out the window.....
I just want to know if there is a fix for this problem.
ChazzMatt said:
All US998 are already carrier unlocked. Even U.S. Cellular.
If you're trying to update to Pie it's a different KDZ thread. I assumed you were trying to update to latest US998 Oreo since to you said it wouldn't update...
Click to expand...
Click to collapse
It was running oreo when i got the phone i was trying to get pie that was a success but it cost the imei number and being somewhat dyslexic and parsuly color blind didn't see the warning about the fact I'd lose imei number if i knew I'd probably stick with oreo.
stinka318 said:
It was running oreo when i got the phone i was trying to get pie that was a success but it cost the imei number and being somewhat dyslexic and parsuly color blind didn't see the warning about the fact I'd lose imei number if i knew I'd probably stick with oreo.
Click to expand...
Click to collapse
Luckily you still have box with IMEI, etc.
You'll have to Google for tools to repair your IMEI. You know what it is, you will just need to type it in.
It's a touchy subject on XDA we can't really discuss in depth because some people for nefarious reason want to CHANGE their IMEI and XDA frowns on that.
ChazzMatt said:
Luckily you still have box with IMEI, etc.
You'll have to Google for tools to repair your IMEI. You know what it is, you will just need to type it in.
It's a touchy subject on XDA we can't really discuss in depth because some people for nefarious reason want to CHANGE their IMEI and XDA frowns on that.
Click to expand...
Click to collapse
Yep so i think I'll will leave it alone got what i need now hopefully i can figure it out......thanks anyway.
ChazzMatt said:
Luckily you still have box with IMEI, etc.
You'll have to Google for tools to repair your IMEI. You know what it is, you will just need to type it in.
It's a touchy subject on XDA we can't really discuss in depth because some people for nefarious reason want to CHANGE their IMEI and XDA frowns on that.
Click to expand...
Click to collapse
Just got it fixed now have it back fully it has something to do with hidden menu.......lol