https://adduono.com/twrp-test/twrp-3.1.1-0-h930.img
go ham
NOT FOR T-MOBILE LG V30/V30+ H932 OR ANYTHING OTHER THAN H930/H930G!
however, if you find an exploit to flash this to an unlocked bootloader H932 then have at it!
don't forget to unlock your bootloader first: http://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryId=CTULRS0702
if LG's bootloader unlock page says your device isn't eligible, then you are officially screwed!
you must use fastboot to flash it to your recovery partition, from there, do the factory reset button dance
i have no idea how to do that so tell a friend
warning: if you boot the OS after flashing recovery, it will just replace it with stock recovery!
solution: swipe to enable modifications in TWRP after accepting factory reset screen (it won't actually wipe your device, twrp will ignore the request)
if you are having trouble with that, you can flash twrp to boot partition instead, and probably get away with flashing your boot image to recovery.
using it backwards like this, you will default boot into twrp, then you can select reboot -> recovery to get into your rom. it's just like having a GRUB menu, ha!
you should have an extra copy of boot.img for your current rom if you want to go this route!
tested working:
OTG storage
MTP
ADB
Mass Storage mode (legacy sdcard as flash drive mode!)
Brightness
no-verity-opt-encrypt-6.0.zip (download here)
please test:
Backup/Restore
f2fs (requires a custom kernel to boot, LG does not have it enabled in stock)
exFAT sdcards
NTFS (via OTG storage)
time/date? (be sure to set your timezone correctly)
STABILITY - LG really sucks at kernel modifications and any small thing could cause a NULL pointer exception and crash
Magisk stable (root that puppy, MAKE BACKUPS FIRST!)
SuperSU (don't flash it with Magisk lol)
Backing up EFS and emailing it to me so I can sell to the highest chinese bidder
will probably never work:
Encryption - LG's proprietary encryption is beyond my capabilities - it is possible to support encryption on custom ROMs however.
you can flash no-verity-opt-encrypt then format your data partition to disable encryption (i think?)
LG might just encrypt it regardless, who knows
you can disable LG's root checker daemon/service by flashing this cool zip https://build.nethunter.com/android-tools/lg-rctd-disabler/
crashes can be diagnosed by entering back into recovery immediately after the crash and doing adb pull /sys/fs/pstore then uploading pstore folder for me to stare at in confusion
when all is tested and happy, I will close this thread, submit it to twrp.me, and open an official TWRP thread.
thanks for your participation
special thanks to @wolfgart for providing factory images to work off, and doing all the dangerous pre-alpha testing for me, and allowing me to use SSH to talk to his device.
SOURCES (never trust a man without them)
kernel: https://github.com/jcadduono/android_kernel_lge_msm8998/commits/twrp-7.1
device tree: https://github.com/jcadduono/android_device_lge_h930
UNDECIDED IDEAS
should it be called h930? officially it is called joan/joan_global_com
should I make it a unified device and have it automatically populate with correct model by reading serial number (H930 vs H930G) or just have it H930 for simplicity
should I update the f2fs driver to f2fs-stable upstream
should I include crypto libs and qseecomd for custom ROMs to use HW encryption (may cause delayed startup/longer boot in TWRP for everyone else)
should I just hand this off to someone who actually owns the device to maintain themselves
should I log out of XDA and go back to playing World of Warcraft for another few years
It would be nice to get feedback from the community on these as I know sometimes my choices may be different than yours if I don't know what you want
And so it starts , thank you
jcadduono said:
https://adduono.com/twrp-test/twrp-3.1.1-0-h930.img
go ham
don't forget to unlock your bootloader first: http://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryId=CTULRS0702
you must use fastboot to flash it to your recovery partition, from there, do the factory reset button dance
i have no idea how to do that so tell a friend
warning: if you boot the OS after flashing recovery, it will just replace it with stock recovery!
solution: swipe to enable modifications in TWRP after accepting factory reset screen (it won't actually wipe your device, twrp will ignore the request)
if you are having trouble with that, you can flash twrp to boot partition instead, and probably get away with flashing your boot image to recovery.
using it backwards like this, you will default boot into twrp, then you can select reboot -> recovery to get into your rom. it's just like having a GRUB menu, ha!
you should have an extra copy of boot.img for your current rom if you want to go this route!
tested working:
OTG storage
MTP
ADB
Mass Storage mode (legacy sdcard as flash drive mode!)
Brightness
no-verity-opt-encrypt-6.0.zip (download here)
please test:
Backup/Restore
f2fs (requires a custom kernel to boot, LG does not have it enabled in stock)
exFAT sdcards
NTFS (via OTG storage)
time/date? (be sure to set your timezone correctly)
STABILITY - LG really sucks at kernel modifications and any small thing could cause a NULL pointer exception and crash
Magisk stable (root that puppy, MAKE BACKUPS FIRST!)
SuperSU (don't flash it with Magisk lol)
Backing up EFS and emailing it to me so I can sell to the highest chinese bidder
will probably never work:
Encryption - LG's proprietary encryption is beyond my capabilities - it is possible to support encryption on custom ROMs however.
you can flash no-verity-opt-encrypt then format your data partition to disable encryption (i think?)
LG might just encrypt it regardless, who knows
crashes can be diagnosed by entering back into recovery immediately after the crash and doing adb pull /sys/fs/pstore then uploading pstore folder for me to stare at in confusion
when all is tested and happy, I will close this thread, submit it to twrp.me, and open an official TWRP thread.
thanks for your participation
special thanks to @wolfgart for providing factory images to work off, and doing all the dangerous pre-alpha testing for me, and allowing me to use SSH to talk to his device.
SOURCES (never trust a man without them)
kernel: https://github.com/jcadduono/android_kernel_lge_msm8998/commits/twrp-7.1
device tree: https://github.com/jcadduono/android_device_lge_h930
UNDECIDED IDEAS
should it be called h930? officially it is called joan/joan_global_com
should I make it a unified device and have it automatically populate with correct model by reading serial number (H930 vs H930G) or just have it H930 for simplicity
should I update the f2fs driver to f2fs-stable upstream
should I include crypto libs and qseecomd for custom ROMs to use HW encryption (may cause delayed startup/longer boot in TWRP for everyone else)
should I just hand this off to someone who actually owns the device to maintain themselves
should I log out of XDA and go back to playing World of Warcraft for another few years
It would be nice to get feedback from the community on these as I know sometimes my choices may be different than yours if I don't know what you want
Click to expand...
Click to collapse
I think h930 and us998 would be the best options when it comes out ofc cause they both would get super long names but I do like the naming scheme of joan because it would set the precedent for the entire rom scene @ChazzMatt might have an opinion too as I know he is wanting to Dev the device and I'm getting mine here soon
jcadduono said:
UNDECIDED IDEAS
should it be called h930? officially it is called joan/joan_global_com
should I make it a unified device and have it automatically populate with correct model by reading serial number (H930 vs H930G) or just have it H930 for simplicity
should I just hand this off to someone who actually owns the device to maintain themselves
It would be nice to get feedback from the community on these as I know sometimes my choices may be different than yours if I don't know what you want
Click to expand...
Click to collapse
Unified. Over in the Moto Quark forums (Droid Turbo XT1254, U.S Moto Maxx XT1250, Moto Turbo XT1225, "international" Moto Maxx XT1225) the TWRP dev got us official TWRP (although he also makes his own modded versions) but made the wise decision to go unified. That way no matter what Quark you have, there's ONE TWRP thread, and one official TWRP. It really reduces confusion. (And the Droid Turbo bootloader was unlocked a full year after release by Sunshine. Didn't matter, the Quark TWRP dev included them in the party.)
To reiterate, there's actually TWO XDA Quark forums to cover ALL the variants, but ONE unified TWRP.
Yes, for the V30 right now there's the H930, and surprisingly the H930G -- but in a month there will also be the North America US998. Just because it's not there yet, don't forget to mentally prepare for it. You're the TWRP guy right now and you can include ALL these models. Over in the LG G6 forum, they didn't do that and there's two TWRP versions, two TWRP threads. We can do it better.
The open market US998 will be released December 5 (next week), and even though probably won't be bootloader unlocked until about 3 weeks later, upon release you can immediately update the TWRP to include the serial numbers, yes? So, it will be "shovel ready" when LG does list it on the bootloader unlock page.
I know I wouldn't want to flash this TWRP over my US998 and have it be called an H930, same with someone with an H930 not wanting it to be a US998. And someone with an H930G would also want their device specifically recognized.
Same with ROMs, for any other devs reading this. Again, using Moto Quark as good example -- with only with one Verizon stock-based ROM exception -- ALL the Quarks from all over the world can run ALL the custom ROMs. Should be the same with the V30. (And yes, even Quark had different (32GB/64GB) internal size configurations like the V30/V30+. That doesn't matter. It can be done. When you boot up, the About Settings for all the ROMs show even show specifically what device you have, whether Droid Turbo, Moto Maxx, Moto Turbo.
Please don't make ROMs for JUST the H930 or JUST the US998. Make the ROM so people can flash the radio they need, but the ROM works for all V30 variants.
jcadduono said:
should I just hand this off to someone who actually owns the device to maintain themselves
Click to expand...
Click to collapse
That's your decision. It is harder to test if you don't own the device yourself. The Quark dev @bhb27 even makes modded versions of TWRP, which we actually trust more than the "official" TWRP -- because he's also the dev of two different ROMs and a custom kernel. He throws his custom kernel into the TWRP build (if I understand correctly) so it runs better. TWRP website won't accept his modded TWRP builds, but then no one installs the official TWRP anymore because his modded TWRP has so many extra features. Point is, he owns the device and knows what works and what doesn't.
If you decide not to buy a V30 for personal reasons, and decide to hand it off, you can at least get a good foundation going with a unified build.
ChazzMatt said:
Unified. Over in the Moto Quark forums (Droid Turbo XT1254, U.S Moto Maxx XT1250, Moto Turbo XT1225, "international" Moto Maxx XT1225) the TWRP dev got us official TWRP (although he also makes his own modded versions) but made the wise decision to go unified. That way no matter what Quark you have, there's ONE TWRP thread, and one official TWRP. It really reduces confusion. (And the Droid Turbo bootloader was unlocked a full year after release by Sunshine. Didn't matter, the Quark TWRP dev included them in the party.)
To reiterate, there's actually TWO XDA Quark forums to cover ALL the variants, but ONE unified TWRP.
Yes, for the V30 right now there's the H930, and surprisingly the H930G -- but in a month there will also be the North America US998. Just because it's not there yet, don't forget to mentally prepare for it. You're the TWRP guy right now and you can include ALL these models. Over in the LG G6 forum, they didn't do that and there's two TWRP versions, two TWRP threads. We can do it better.
The open market US998 will be released December 5 (next week), and even though probably won't be bootloader unlocked until about 3 weeks later, upon release you can immediately update the TWRP to include the serial numbers, yes? So, it will be "shovel ready" when LG does list it on the bootloader unlock page.
I know I wouldn't want to flash this TWRP over my US998 and have it be called an H930, same with someone with an H930 not wanting it to be a US998. And someone with an H930G would also want their device specifically recognized.
Same with ROMs, for any other devs reading this. Again, using Moto Quark as good example -- with only with one Verizon stock-based ROM exception -- ALL the Quarks from all over the world can run ALL the custom ROMs. Should be the same with the V30. (And yes, even Quark had different (32GB/64GB) internal size configurations like the V30/V30+. That doesn't matter. It can be done. When you boot up, the About Settings for all the ROMs show even show specifically what device you have, whether Droid Turbo, Moto Maxx, Moto Turbo.
Please don't make ROMs for JUST the H930 or JUST the US998. Make the ROM so people can flash the radio they need, but the ROM works for all V30 variants.
That's your decision. It is harder to test if you don't own the device yourself. The Quark dev @bhb27 even makes modded versions of TWRP, which we actually trust more than the "official" TWRP -- because he's also the dev of two different ROMs and a custom kernel. He throws his custom kernel into the TWRP build (if I understand correctly) so it runs better. TWRP website won't accept his modded TWRP builds, but then no one installs the official TWRP anymore because his modded TWRP has so many extra features. Point is, he owns the device and knows what works and what doesn't.
If you decide not to buy a V30 for personal reasons, and decide to hand it off, you can at least get a good foundation going with a unified build.
Click to expand...
Click to collapse
The H930/H930G are practically the same device so all the work is done for unifying them. For US998 to be included in the same TWRP build will require a lot of hacks or just good luck with dtb mismatches. The US998 might have hardware located on different pins than H930/H930G so I will have to check the dtb files and see what doesn't match up and create a unified dtb OR find a way to detect the real device model within the kernel (can be done by reading serial number from command line passed by bootloader) and then select the correct dtb to load. This might require modifying dtb format to add device variant descriptors. It would be a lot easier if different models didn't have the same dtb subtype codes conflicting with each other and it would load the correct dtb automatically.
I would be leaning towards the method of modifying dtb/dtsi to include a model ID and insert some code in dtb selector to pick the right one based on serial number from BL cmdline.
None of this will be necessary if this build boots with no noticeable issues running TWRP on US998 when it releases, and if so all I need to do is add init code to change version props. Easy.
jcadduono said:
The H930/H930G are practically the same device so all the work is done for unifying them. For US998 to be included in the same TWRP build will require a lot of hacks or just good luck with dtb mismatches. The US998 might have hardware located on different pins than H930/H930G so I will have to check the dtb files and see what doesn't match up and create a unified dtb OR find a way to detect the real device model within the kernel (can be done by reading serial number from command line passed by bootloader) and then select the correct dtb to load. This might require modifying dtb format to add device variant descriptors. It would be a lot easier if different models didn't have the same dtb subtype codes conflicting with each other and it would load the correct dtb automatically.
I would be leaning towards the method of modifying dtb/dtsi to include a model ID and insert some code in dtb selector to pick the right one based on serial number from BL cmdline.
None of this will be necessary if this build boots with no noticeable issues running TWRP on US998 when it releases, and if so all I need to do is add init code to change version props. Easy.
Click to expand...
Click to collapse
This may be what you are saying, but how about this? If it's NOT an H930/H930G, THEN it HAS to be a US998. True/false decision.
We know only the H930/H930G/US998 will be on the LG bootloader unlock list.
Later, if some devs have luck with T-mobile H932 (using something like this) or other carrier branded models, you can cross that bridge when it comes.
________
jcadduono said:
The H930/H930G are practically the same device so all the work is done for unifying them. For US998 to be included in the same TWRP build will require a lot of hacks or just good luck with dtb mismatches. The US998 might have hardware located on different pins than H930/H930G so I will have to check the dtb files and see what doesn't match up and create a unified dtb OR find a way to detect the real device model within the kernel (can be done by reading serial number from command line passed by bootloader) and then select the correct dtb to load. This might require modifying dtb format to add device variant descriptors. It would be a lot easier if different models didn't have the same dtb subtype codes conflicting with each other and it would load the correct dtb automatically.
I would be leaning towards the method of modifying dtb/dtsi to include a model ID and insert some code in dtb selector to pick the right one based on serial number from BL cmdline.
None of this will be necessary if this build boots with no noticeable issues running TWRP on US998 when it releases, and if so all I need to do is add init code to change version props. Easy.
Click to expand...
Click to collapse
I know I hit thanks on post #1, but I also want to say it in writing. Thanks for your work on this.
Not sure why LG separates the European and North America bootloader unlock dates, but probably so the North American carriers have more time to fleece their customers before LG releases the GOOD stuff. They give the carriers some sort of exclusive selling time. We saw it on the LG G6 and it's happening again with the LG V30. But the "open market" US998 is coming.
I'm hoping LG will surprise us and also release a V30+ version of the US998.
U.S. Cellular sells such a version (V30+) with the same model number (US998). It won't be eligible for bootloader unlock, but LG could make that same variant available to authorized retailers for their "open market" model. Much like the H930 (V30) and H930G (V30+). LG including the H930G gives me hope they will do something similar for North America.
LG has said nothing publicly about the North American "open market" US998. The only information (including alleged December 5 release date) we have is from the B&H Photo pre-order page -- and I've already ordered one from there. But there will be other authorized retailers, and none of those have put up pre-order pages. Everyone except for B&H Photo seems to be waiting for LG to speak first.
jcadduono said:
The H930/H930G are practically the same device so all the work is done for unifying them. For US998 to be included in the same TWRP build will require a lot of hacks or just good luck with dtb mismatches. The US998 might have hardware located on different pins than H930/H930G so I will have to check the dtb files and see what doesn't match up and create a unified dtb OR find a way to detect the real device model within the kernel (can be done by reading serial number from command line passed by bootloader) and then select the correct dtb to load. This might require modifying dtb format to add device variant descriptors. It would be a lot easier if different models didn't have the same dtb subtype codes conflicting with each other and it would load the correct dtb automatically.
I would be leaning towards the method of modifying dtb/dtsi to include a model ID and insert some code in dtb selector to pick the right one based on serial number from BL cmdline.
None of this will be necessary if this build boots with no noticeable issues running TWRP on US998 when it releases, and if so all I need to do is add init code to change version props. Easy.
Click to expand...
Click to collapse
i prefer to have different TWRP's images . One for H930 / G and another one for US variant.
Make Official for H930
wolfgart said:
i prefer to have different TWRP's images . One for H930 / G and another one for US variant.
Make Official for H930
Click to expand...
Click to collapse
No, no need for that. Can be one official TWRP for all LG V30. You didn't even read what I posted.
As a great example, Moto Quark (XT1254, XT1250, XT1225) has several different variants but still has one OFFICIAL TWRP which works on all, recognizes all. They even have two different XDA forums to cover all the variants, but still ONE TWRP, one TWRP thread -- which makes dev discussion much simpler.
No need for two or three TWRP threads in the LG V30 development section, when this is a forum for all.
It doesn't "hurt" in any way to have a unified build, but does HELP development in so many ways.
ChazzMatt said:
This may be what you are saying, but how about this? If it's NOT an H930/H930G, THEN it HAS to be a US998. True/false decision.
We know only the H930/H930G/US998 will be on the LG bootloader unlock list.
Later, if some devs have luck with T-mobile H932 or other carrier branded models, you can cross that bridge when it comes.
________
I know I hit thanks on post #1, but I also want to say it in writing. Thanks for your work on this.
Not sure why LG separates out the European and North America bootloader unlock dates, but probably so the North American carriers have more time to fleece their customers before LG releases the GOOD stuff. They give the carriers some sort of exclusive selling time. We saw it on the LG G6 and it's happening again with the LG V30. But the "open market" US998 is coming.
I'm hoping LG will surprise us and also release a V30+ version of the US998.
U.S. Cellular sells such a version (V30+) with the same model number (US998). It won't be eligible for bootloader unlock, but LG could make that same variant available to authorized retailers for their "open market" model. Much like the H930 (V30) and H930G (V30+). LG including the H930G gives me hope they will do something similar for North America.
LG has said nothing publicly about the North American "open market" US998. The only information (including alleged December 5 release date) we have is from the B&H Photo pre-order page -- and I've already ordered one from there. But there will be other authorized retailers, and none of those have put up pre-order pages. Everyone except for B&H Photo seems to be waiting for LG to speak first.
Click to expand...
Click to collapse
Yeah I agree Chazz with unified especially when it came to G6 people only developed for the country they own and even though @Rashed97 owned and maintained the us997 the only official lineage thread was for the h870 along with numerous other official h870 with no mention of us997 other than me and one other Dev building unofficial roms for personal builds and sharing.
All things seem to work so far, (the ones I normaly use in twrp that means), including backup, restore, magisk stable, magisk beta and supersu. Only thing i can't get to work is flashing zips which would install apps. I have a suspicion but before I talk bullcrap I would like to ask why that may be, if there's a workaround or if I have to wait for the first custom ROMs
Edit : got it, I'm stupid
Is this for the tmobile variant? Sorry for the noobish question
lightninbug said:
Is this for the tmobile variant? Sorry for the noobish question
Click to expand...
Click to collapse
Nope T-Mobile is H932
Sent from my LG-H932 using Tapatalk
lightninbug said:
Is this for the tmobile variant? Sorry for the noobish question
Click to expand...
Click to collapse
It's for the carrier unlocked variants, which we waited patiently to be released. Those are placed on the LG bootloader unlock list and have full ADB flash commands. The thread title says which V30 variants this TWRP is for.
@jcadduono, I know you will hate to do this, but there's going to be a flood of questions from T-mobile people HOPING this will work for T-mobile. You may need to add a statement near the top of the OP in big red letters, "NOT FOR T-MOBILE LG V30/V30+ H932!" -- until at some point some dev magic happens and the H932 can join the party.
Hi all, apologies if this is a seemingly a daft question. When trying to flash to the recovery partition, I receive the following error;
C:\adb>adb reboot bootloader
C:\adb>fastboot flash recovery C:\adb\twrp-3.1.1-0-h930.img
sending 'recovery' (22588 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.109s
C:\adb>fastboot flash recovery C:\adb\twrp-3.1.1-0-h930.img
sending 'recovery' (22588 KB)...
FAILED (remote: unknown command)
finished. total time: 0.016s
C:\adb>fastboot flash recovery C:\adb\twrp-3.1.1-0-h930.img
sending 'recovery' (22588 KB)...
FAILED (remote: Requested download size is more than max allowed
Click to expand...
Click to collapse
Can anyone point me in the right direction? It's the H930 variant with unlocked bootloader.
Thank you
--------------------------------------------------------------
All sorted, it w a driver issue at my end. It works great!
I don't understand why US carriers are such assholes.
Why the need to create different models, steal accessories from the box, use different bands, lock down the phones, unlike what the manufacturer decided etc?
It's just stupid. Why don't the people complain about some of those issues? Sorry for the offtopic, just didn't find a more appropriate thread to say that.
mustaine8661 said:
Hi all, apologies if this is a seemingly a daft question. When trying to flash to the recovery partition, I receive the following error;
Can anyone point me in the right direction? It's the H930 variant with unlocked bootloader.
Thank you
Click to expand...
Click to collapse
you have to open CMD inside working folder where you have twrp image too
wolfgart said:
you have to open CMD inside working folder where you have twrp image too
Click to expand...
Click to collapse
Thank you for the quick reply. Already doing that from the get-go.
I've not come across something like this before. Will keep poking and see if I can find a way around this
FAILED (remote: Cannot flash this partition in unlocked state)
TWRP SuperSU LG V30+ H930DS
@jcadduono
Hello from Italy.
I'm waiting for you to get me LG V30 + H930DS unlocked purchased here:
https://www.bravobuy.co.it/it_IT/product/lg-v30-h930ds-dual-sim-libero-128gb-4g-argento.html
I wanted to ask you a courtesy.
I do not know English to read all the post # 1.
With which adb command you installed the TWRP and which SuperSU did you use for the Root ... ???
Thank you.
Google translator
Pisolo said:
@jcadduono
Hello from Italy.
I'm waiting for you to get me LG V30 + H930DS unlocked purchased here:
https://www.bravobuy.co.it/it_IT/product/lg-v30-h930ds-dual-sim-libero-128gb-4g-argento.html
I wanted to ask you a courtesy.
I do not know English to read all the post # 1.
With which adb command you installed the TWRP and which SuperSU did you use for the Root ... ???
Thank you.
Google translator
Click to expand...
Click to collapse
Good question about SuperSU. I'm curious to know also, for when the US998 gets added to the LG Developer Bootloader Unlock list.
On some phones like the Moto Quark, you have to actually FIRST flash a specific older version of SuperSu, THEN you can update to the latest SuperSu.
So, which SuperSu can you flash on the LG V30 for current Nougat 7.1.2?
The answer may change for when it's upgraded to Oreo...
Related
I am certain my G4 is TWN, from the box and the software version. But what are the actual differences to the European H815? Specifically, can I flash European KDZs or use the EU command for flashing a rooted /system image?
Code:
dd if=/data/media/0/system.rooted.H81510c-EU.img bs=8192 seek=55296 count=529920 of=/dev/block/mmcblk0
Thanks
I have a the TWN version too damn it. - that's what happens when you buy from a global vendor over the internet .
Good news is that you can flash the EU rooted system image. I did and it worked fine.
Bad news is that you can't unlock the boot loader (yet), which means no TWRP or custom roms and flashing a stock Marshmallow leaves you without root and no way to downgrade.
Cheers
BTW I don't know of any differences between the EU and TWN devices other than the version coding - to me it just seems to be a way for LG to control their different markets.
Thank you for this. I do not want to unlock it just yet, since I bought it from a local vendor and I have a 2 year warranty with them. I see there is already a rooted image for v10d TWN, so I will flash that soon (are you sure the parameters for the dd command are the same?).
Sidenote, it would be nice if we could compile our own KDZs and make rooted ones.
metalboy94 said:
Thank you for this. I do not want to unlock it just yet, since I bought it from a local vendor and I have a 2 year warranty with them. I see there is already a rooted image for v10d TWN, so I will flash that soon (are you sure the parameters for the dd command are the same?).
Sidenote, it would be nice if we could compile our own KDZs and make rooted ones.
Click to expand...
Click to collapse
I can't really comment on the all the parameters in that command string except to say that it's one I used and it worked well. Whether those numbers would need to be modified for the 10D image or not I can't say - I would suggest you ask the author of that original rooting thread.
BTW you can't unlock the bootloader on the TWN version just now in any case. I tried the official method over the weekend and was told the TWN version was not supported. There's unofficial unlock method available for any G4 variant yet either but people are working on it.
wadken1 said:
I can't really comment on the all the parameters in that command string except to say that it's one I used and it worked well. Whether those numbers would need to be modified for the 10D image or not I can't say - I would suggest you ask the author of that original rooting thread.
BTW you can't unlock the bootloader on the TWN version just now in any case. I tried the official method over the weekend and was told the TWN version was not supported. There's unofficial unlock method available for any G4 variant yet either but people are working on it.
Click to expand...
Click to collapse
Probably the parameters aren't different between firmware images, because they depend on the partition table of the device.
Now waiting for a version of Xposed that is confirmed not to drain battery. Thanks again!
I'm running xposed now with about 10 modules. I don't see any great battery drain.
wadken1 said:
I have a the TWN version too damn it. - that's what happens when you buy from a global vendor over the internet .
Good news is that you can flash the EU rooted system image. I did and it worked fine.
Bad news is that you can't unlock the boot loader (yet), which means no TWRP or custom roms and flashing a stock Marshmallow leaves you without root and no way to downgrade.
Cheers
BTW I don't know of any differences between the EU and TWN devices other than the version coding - to me it just seems to be a way for LG to control their different markets.
Click to expand...
Click to collapse
Hang on, I can flash MM into my TWN? I missed that, how does that work? Is there a thread?
wadken1 said:
I have a the TWN version too damn it. - that's what happens when you buy from a global vendor over the internet .
Good news is that you can flash the EU rooted system image. I did and it worked fine.
Bad news is that you can't unlock the boot loader (yet), which means no TWRP or custom roms and flashing a stock Marshmallow leaves you without root and no way to downgrade.
Cheers
BTW I don't know of any differences between the EU and TWN devices other than the version coding - to me it just seems to be a way for LG to control their different markets.
Click to expand...
Click to collapse
I did the same thing, buying online and getting stuck with TWN. I came from a GS6 and was thinking "I'll wack an AOSP ROM on the G4 and I'll have the perfect phone". Now I'll probably never buy another LG even though I actually like the G4 but when we pay close to $1k for a phone we should be able to do what we like with it!
There is a thread for stock marshmallow which you can install with flash fire but there's no root available with that option just now.
wadken1 said:
There is a thread for stock marshmallow which you can install with flash fire but there's no root available with that option just now.
Click to expand...
Click to collapse
I've tried to find the correct thread but could you point me in the right direction?
Thanks
gz5ztg said:
I've tried to find the correct thread but could you point me in the right direction?
Thanks
Click to expand...
Click to collapse
Sorry. Missed this while I was away.
The thread I'm talking about is http://forum.xda-developers.com/g4/development/stock-h815-20a-stock-rom-t3233049
BUT be warned you will lose root !!. So far as I know just now there is no way to get root on stock MM without an unlocked bootloader. This may have changed inthe last couple of days - you'll need to read around the forum.
ALSO there is no sure way back to L is you decide you can't live without root (I certainly couldn't so I'm waiting for further developments). I think I read that someone here more-or-less accidentally managed to recover back to L but I didn't really have time to take in all the details so futher reading needed if you want to take the risk.
wadken1 said:
Sorry. Missed this while I was away.
The thread I'm talking about is http://forum.xda-developers.com/g4/development/stock-h815-20a-stock-rom-t3233049
BUT be warned you will lose root !!. So far as I know just now there is no way to get root on stock MM without an unlocked bootloader. This may have changed inthe last couple of days - you'll need to read around the forum.
ALSO there is no sure way back to L is you decide you can't live without root (I certainly couldn't so I'm waiting for further developments). I think I read that someone here more-or-less accidentally managed to recover back to L but I didn't really have time to take in all the details so futher reading needed if you want to take the risk.
Click to expand...
Click to collapse
Okay thanks, maybe I will wait. This is going to sound like a completely noob type question but what is it that you are doing that you couldn't live without that requires root?
gz5ztg said:
Okay thanks, maybe I will wait. This is going to sound like a completely noob type question but what is it that you are doing that you couldn't live without that requires root?
Click to expand...
Click to collapse
Here's a few of the things I use which need root:
TI Backup
LMT Launcher
Bubble UpnP
FX Explorer (with root)
Gravity Box (xposed) to give expanded desktop
Llama + Secure settings (allows for automated control of airplane mode, gps and others which have been denied by google for default seetings)
Buidprop editor - allows altering a number of settings but especially DPI
Greenify advanced functions
Amplify
Better Battery Stats
Flashfire
Busybox
Viper4Android
SE Linux Mode Changer (needed to allow Viper to work)
Hi,
Everybody is looking for official stock roms for Moto G4/G4 Plus *AWAY* from Motorola support, which looked to me like kind of weird but I now know why: people are looking for stock roms that will allow them over the air upgrades. If you have a developer edition or a moto with unlocked bootloader, Moto's own roms are flashable and *COMPLETELY WORKING*
motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
Go to above URL, quick login using G+, follow instructions to get to the download list. The listed download for XT1625 will also work just fine for XT1642.
Or, you can just use this direct link: motorola-global-portal.custhelp.com/cc/ajaxCustom/getBootFile/fileName/ib65qpz53y
may also require login.
******** VERY IMPORTANT ************
Everybody lists fastboot utility commands with which you restore a Moto stock rom. They do not tell these severe warnings:
- Never flash a gpt.bin file unless you really absolutely ultimately intentionally and knowingly NEED TO. Why? in 99.9% of the cases it is useless to your phone and your needs and all it will do is deprive you the ability to downgrade to an earlier version or flash an older boot file, system file, ...etc. You get the picture. BTW, gpt.bin is only a partition image containing Moto's partition table scheme, with versioning for downgrade prevention. Keep away from it. It is pure EVIL.
IF YOU SEE gpt.bin FILE, DELETE IT WITHOUT HESITATION.
- Our second vanity: bootloader.img or bootloader.bin or anything that spells BOOTLOADER. EVIL. DELETE IT. It will 99.9% only mess up your cellular capability and render your phone without voice calls, with out SMS and without 2G/3G/4G; no data whatsoever. It will convert your phone into a 5.5 inch SIM-less tablet. It will KILL YOUR SIM SLOTS.
Instruction are on the first link, but anyway, here we go:
To flash, put the phone in fastboot mode:
1. Power OFF your device
2. Then Power ON + Volume Down Alternatively, you can reboot into fastboot mode if you have adb...
adb reboot bootloader.
Next flash the images using fastboot:
Code:
"DELETED COMMAND HERE WAS SUPPOSED TO FLASH THE GPT.BIN. NEVER DO IT"
"DELETED COMMAND HERE WAS SUPPOSED TO FLASH THE BOOTLOADER. NEVER DO IT"
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase userdata
fastboot erase cache
fastboot reboot
enjoy
****removed****
MK+2017 said:
****removed****
Click to expand...
Click to collapse
I would like back to MM from Nougat on XT1642. This firmware comes from a trusted source, but have you tried this firmware, no problems after flashing? Do I have to have an unlocked bootloader ?
kkamelot said:
I would like back to MM from Nougat on XT1642. This firmware comes from a trusted source, but have you tried this firmware, no problems after flashing? Do I have to have an unlocked bootloader ?
Click to expand...
Click to collapse
if you have not unlocked boot-loader you are covered by warranty and I advise you keep it that way. Motorola is a BI***.
if you really can't live without older stock, go to moto service and ask them to do it for you. should not cost you much, if any.
if what you hate is stock firmware, you can unlock bootloader, get warranty off, and flash LinageOS. Stable enough although still in nightly builds (successor of CyanogenMod)
hope that helps.
PS1: what you would fear the most is lose your SIM slot, happens a lot. Be safe!
PS2: asking if I tried it yes, I did. it worked. but I was on 6.0.1 at the time. do not take risk.
PS3: Motorola is a *****. DON'T MESS WITH IT.
MK+2017 said:
if you have not unlocked boot-loader you are covered by warranty and I advise you keep it that way. Motorola is a BI***.
if you really can't live without older stock, go to moto service and ask them to do it for you. should not cost you much, if any.
if what you hate is stock firmware, you can unlock bootloader, get warranty off, and flash LinageOS. Stable enough although still in nightly builds (successor of CyanogenMod)
hope that helps.
PS1: what you would fear the most is lose your SIM slot, happens a lot. Be safe!
PS2: asking if I tried it yes, I did. it worked. but I was on 6.0.1 at the time. do not take risk.
PS3: Motorola is a *****. DON'T MESS WITH IT.
Click to expand...
Click to collapse
Thank you for your answer !
I have one more question, is there way (like in nexus) to back to original software (Nougat can be) after changing OS or make a modifications?
kkamelot said:
Thank you for your answer !
I have one more question, is there way (like in nexus) to back to original software (Nougat can be) after changing OS or make a modifications?
Click to expand...
Click to collapse
There is, but if you are not good with command line, think twice. Check here: https://forum.xda-developers.com/moto-g4-plus/help/complete-partition-backup-script-xt1644-t3608408
you would typically use that alongside full TWRP backup.
I can assure you nothing will go wrong if you jump straight to LineageOS, it might only go wrong if you take the bad decision of going back to stock. The dd images would give you solid backup, though.
In case you lose your sim slot, you can use help from here: https://forum.xda-developers.com/showpost.php?p=72343095&postcount=101
I intuitively contributed to that solution Giving is taking!
Thank you @m.sawastik and @givitago
MK+2017 said:
There is, but if you are not good with command line, think twice. Check here: https://forum.xda-developers.com/moto-g4-plus/help/complete-partition-backup-script-xt1644-t3608408
you would typically use that alongside full TWRP backup.
I can assure you nothing will go wrong if you jump straight to LineageOS, it might only go wrong if you take the bad decision of going back to stock. The dd images would give you solid backup, though.
In case you lose your sim slot, you can use help from here: https://forum.xda-developers.com/showpost.php?p=72343095&postcount=101
I intuitively contributed to that solution 😊Giving is taking!
Thank you @m.sawastik and @givitago
Click to expand...
Click to collapse
I would also be happy to assist you if you want to jump to LineageOS. I won't assist you with dd backup, just because you need to take that responsibility on your own
My XT1625 is already on Lineage OS Andriod N. However, I feel like the cellular reception and thus battery life has been worse versus stock.
I wanted to flash only the latest baseband from the latest stock Andriod N but your Moto link only has 6.0.1 for XT1625.
What gives- I thought Motorola already updated the G4 to 7.0?
Will OTAs work with this?
Will OTAs work with these?
If I just want to upgrade my modem/baseband and then go back to LOS, do I just need to type "fastboot flash modem NON-HLOS.bin" or do I need to make a full install?
it works for moto g4 t1625 amazon version?? compilation number npj25.93-14.5 ?????? i answer this because in the web site motorola its appear the moto g4 rom xt1625 build MPJ24.139-64
Works!
I just want to say that I had a Moto G4 Plus (XT1642) that had no SIM recognition, no IMEI, no Wifi, and thanks to the instructions at the top of this thread, I now have it all.
I spent the whole day trying all sorts of things. Now it finally works!
Thanks!
How do I flash?
Hi friend, sorry but my English is not good.
My phone will receive nougat via OTA?
Something has broken my sound notifications
When I try this procedure I get a lot of these errors against some of the commands
(bootloader) Image aboot failed validation
(bootloader) Preflash validation failed
(bootloader) will fail: flash:aboot
FAILED (remote failure)
And now sounds that accompany any notifications from any applications fail to make any sound. Vibrate does initiate.
I am trying to find a way to enable hotspot on my ATT Moto G4 plus, if I flash this rom can anyone confirm it will unlock this feature? Torn between flashing or just going in to kernel and make change for this feature, any advice appreciated..
how to restore the sim slot after flash( i have no service)
i had frp, and after remove it with 3rd party tool i flash new rom.
now i have no service(but it detect the sim), there is any way to restore the sim slot?
i flashed the original rom from motorola site and it didnt help.
i flash the lineage OS and it didnt helped.
thanks
ggc201 said:
there is any way to restore the sim slot?
Click to expand...
Click to collapse
I've been searching for a fix for a few months now, whenever I get free time. Most threads about the subject die and aren't revisited. Someone will inevitably come to this page on a Google search wondering like us. I haven't found anything that will help and so I'm calling it quits. This phone is so outdated it would be better suited to find a deal somewhere else.
Thanks... can't find the button.
I have the xt1625 amz channel version and the: XT1625-XT1644_ATHENE-RETUS_6.0.1_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml.zip > provided enhanced LTE whereas the official OS did not support. I can actually do sh** on my phone without hanging up.
I want you and yours to be blessed forever and great post.
Bootloader is unlocked but somehow it is stuck between root and no root. Will figure it out....
Again... thanks... this is a big deal for me. :good:
non-developer edition?
If you have a developer edition or a moto with unlocked bootloader, Moto's own roms are flashable and *COMPLETELY WORKING*
Click to expand...
Click to collapse
Can anyone attest to having successfully flashed an unlocked non-developer edition G4 with this ROM? Motorola clearly warns against doing this:
IMPORTANT! Do not use these images/packages on non-developer edition devices or on devices with a locked bootloader.
Click to expand...
Click to collapse
(sorry, I'm a new member so I'm not allowed to include a link)
Hello, I'm new
I'm not sure if this is the right place, I felt a discussion area was an okay place to share and discuss my findings
I'm working with the Boost Mobile Motorola E4, the contents to this thread will relate solely to the Boost E4
Bootloader Unlocking
Unlocking the E4's bootloader was very simple through Motorola's website, it is for certain unlocked
After unlocking the bootloader I got the bad key screen but in my experience that's normal
You can verify that your bootloader is unlocked by using fastboot or checking the Developer Options
Rooting
Other people claim to have success with it, I have not yet had that success Just flash Magisk 13.1 after flashing the verity zip, don't bother with anything else, root will work first try. If you tried another root method, you will have to restore with the method in post #2 before it will work without giving the error.
After flashing the superuser zip and the verity zip, I wasn't led to a successful root I instead downloaded SuperSU-v2.82-201705271822 and flashed that after the verity zip and i was able to reach home menu
I tried flashing Chainfire's SuperSU zip but the device stuck at the boost mobile logo, I will try again after I can get back to stock and do the processes over again and find a way to have 100% success each time Downloaded a new version SuperSU-v2.82-201705271822 as noted above and i was able to fully boot
The issue now is that SuperSU app isnt detecting root but Terminal is gaining root, I'm going to try reinstalling app from the market. I got the SU Binary Occupied error, going to try to downgrade it to 2.79 and see how that goes. It didn't work for me, now it says improperly installed.. Going to try something else. It's 1:55AM August second, taking a small break from the root, at least I got other things figured out for now.
verity zip link (flash first): https://www.androidfilehost.com/?fid=24459283995297893
Stock Resources
Sprint 7.1.1 stock RSD file: https://androidfilehost.com/?fid=673368273298975628
-update- I added the stock RSD file to the list, going to be doing some pulls of stock files for us to work with when I can.
I'm going to try to collect as much information as I can about this device and provide as much detail as possible
NOTE: The below IS NOT Boost Mobile stock, it's sprint will update when I figure out Boost Stock
The sprint stock does fully work with the Boost Mobile device, LTE/data services seems to not work until you do a Factory Reset (in settings). ##72786# didn't work. It is now working for me fully after the factory reset from settings. The boost apps automatically install after the factory reset and after the celluar setup on first boot.. My Boost, etc.
After a few times of flashing and re-setup I've ended up with HFA error 701 which asks me to contact service provider to configure the device for service. Fixed by turning phone off for 20 minutes to an hour and the activation processed correctly.
If your experience differs, let us know!
Restoring to Stock
Install Motorola Drivers
Download RSDlite v6.2.4: http://rootjunkysdl.com/files/Android Programs/RSDLite6.2.4.zip
Download the Sprint firmware file: https://androidfilehost.com/?fid=673368273298975628
Rename the zip to sperry.zip, the reason for this is to avoid the long file name error in RSD in some locations
Let the flashing process complete
Some people reported RSD not working in Windows 10, this is not fully true, install all moto and android drivers and it will show up fine as seen in below image
http://imgur.com/a/vdQxG
Thanks!,
rootjunky for RSD mirror
moto firmware team for the e4 stock 7.1.1
Have you check if this phone have gsm bands?
USA or International Variant?
zoofie666 said:
Hello, I'm new
I'm not sure if this is the right place, I felt a discussion area was an okay place to share and discuss my findings
I'm working with the Boost Mobile Motorola E4, the contents to this thread will relate solely to the Boost E4
Bootloader Unlocking
Unlocking the E4's bootloader was very simple through Motorola's website, it is for certain unlocked
After unlocking the bootloader I got the bad key screen but in my experience that's normal
You can verify that your bootloader is unlocked by using fastboot or checking the Developer Options
Rooting
Other people claim to have success with it, I have not yet had that success Just flash Magisk 13.1 after flashing the verity zip, don't bother with anything else, root will work first try. If you tried another root method, you will have to restore with the method in post #2 before it will work without giving the error.
After flashing the superuser zip and the verity zip, I wasn't led to a successful root I instead downloaded SuperSU-v2.82-201705271822 and flashed that after the verity zip and i was able to reach home menu
I tried flashing Chainfire's SuperSU zip but the device stuck at the boost mobile logo, I will try again after I can get back to stock and do the processes over again and find a way to have 100% success each time Downloaded a new version SuperSU-v2.82-201705271822 as noted above and i was able to fully boot
The issue now is that SuperSU app isnt detecting root but Terminal is gaining root, I'm going to try reinstalling app from the market. I got the SU Binary Occupied error, going to try to downgrade it to 2.79 and see how that goes. It didn't work for me, now it says improperly installed.. Going to try something else. It's 1:55AM August second, taking a small break from the root, at least I got other things figured out for now.
verity zip link (flash first): https://www.androidfilehost.com/?fid=24459283995297893
Stock Resources
Sprint 7.1.1 stock RSD file: https://androidfilehost.com/?fid=673368273298975628
-update- I added the stock RSD file to the list, going to be doing some pulls of stock files for us to work with when I can.
I'm going to try to collect as much information as I can about this device and provide as much detail as possible
If you would like me to test anything you can hit me up on Discord: Zoofie#6780 and we can brainstorm
Click to expand...
Click to collapse
Do you have the USA or international variant of the phone? The only bootloader unlocking guide I've found was for the international variant.
Mensarius said:
Do you have the USA or international variant of the phone? The only bootloader unlocking guide I've found was for the international variant.
Click to expand...
Click to collapse
Read the root thread
@zoofie666 were you able to actually flash the moto g5 twrp or did you just boot it? I can get it to boot with fastboot but I get a not signed or corrupt error when trying to flash it.
amarc78 said:
@zoofie666 were you able to actually flash the moto g5 twrp or did you just boot it? I can get it to boot with fastboot but I get a not signed or corrupt error when trying to flash it.
Click to expand...
Click to collapse
You can only boot it
mendelgordon said:
You can only boot it
Click to expand...
Click to collapse
Yeah, I came to that conclusion. Just read it elsewhere also. I'm going to see what I can do about building twrp.
is it possible to take backup of Moto E4 stock rom with RSD lite ?
kartik verma said:
is it possible to take backup of Moto E4 stock rom with RSD lite ?
Click to expand...
Click to collapse
Not sure, but you can do so by booting the Moto G 5 twrp with fastboot. Restoring works also.
amarc78 said:
Not sure, but you can do so by booting the Moto G 5 twrp with fastboot. Restoring works also.
Click to expand...
Click to collapse
For the international variant?
mendelgordon said:
For the international variant?
Click to expand...
Click to collapse
I have the Boost Mobile variant.
Is there anyone with the Boost Mobile variant that made a working system and boot backup? If so, could you please upload it for me? Mine got corrupted somehow and won't restore.
@amarc78 You should be able to use the Sprint firmware posted by zoofie666 - Boost is Sprint's prepaid brand.
The weirdness with the activation on Sprint/Boost seems to be normal, because I had trouble with two phones recently. The first was a retail unlocked e4 (to be used on Sprint), done before rooting, and activated at a Sprint corporate store last week by a rep who had trouble. The second phone was a retail unlocked Moto g4 Play (also to be used on Sprint), that I rooted first, got the SIM and back-end computer part taken care of by a rep at the same store yesterday, and did the rest myself.
hitokage004 said:
@amarc78 You should be able to use the Sprint firmware posted by zoofie666 - Boost is Sprint's prepaid brand.
Click to expand...
Click to collapse
Yeah, I know all about that. I've already made a stock rom zip with sprint firmware but I want Boost so I can make a zip for that.
Sent from my LGLS755 using XDA Labs
I can provide a backup of system but already rooted / disabled dm verity before I took the backup so /boot you'd have to snag the stock kernel, let me know if you want the nandroid tho.
CodyF86 said:
I can provide a backup of system but already rooted / disabled dm verity before I took the backup so /boot you'd have to snag the stock kernel, let me know if you want the nandroid tho.
Click to expand...
Click to collapse
Dang bro, you pop up everywhere I go around here, lol. Remember me from the moto g helping getting data on cm? Your the one who posted the nasa gif when we got it right? Anyway, I would gladly take what you have rooted or not, and any other imgs you would be so kind to provide me with. I was about to buy another now that they're $20 cheaper than when I got my first. I knew that would happen. I wanted to get my wife one anyway. I was a dumb ass and ran a flash all script for sprint stock firmware and forgot to remove everything but the system sparse chunks. So now I really need full stock firmware. Thanks a lot for responding man!
amarc78 said:
Dang bro, you pop up everywhere I go around here, lol. Remember me from the moto g helping getting data on cm? Your the one who posted the nasa gif when we got it right? Anyway, I would gladly take what you have rooted or not, and any other imgs you would be so kind to provide me with. I was about to buy another now that they're $20 cheaper than when I got my first. I knew that would happen. I wanted to get my wife one anyway. I was a dumb ass and ran a flash all script for sprint stock firmware and forgot to remove everything but the system sparse chunks. So now I really need full stock firmware. Thanks a lot for responding man!
Click to expand...
Click to collapse
I member..... 5.1 for falcon was a trial.... imma be getting this device next month. Love seeing the future happening before my eyes
SykkNyzz said:
I member..... 5.1 for falcon was a trial.... imma be getting this device next month. Love seeing the future happening before my eyes
Click to expand...
Click to collapse
Hey, don't you have a LG volt?
Hello guys, i have two questions:
a) after you unlock bootloader on this device, is it possible to flash the non boost (international e4) rom on it? if so, have you done it?
b) i used to have a moto e2 from boost mobile (xt1526) and did this with the unlocked international e2 rom (xt1527) and i was able to use my gsm networks with it as i dont live in the U.S and CDMA bands dont work in my country, would it be possible with this device too? Because GSM bands are embeded in snapdragon chipsets, so flashing a stock unlocked firmware should make it work, but i want to know if you have tried it
Hello Verizon V30 Users,
I am providing the full KDZ file for the Verizon V30 software version 10C, the latest available for the VS996.
You can download it from HERE!
Coming from the V10, I've noticed the KDZ for the Verizon V30 is almost 3.5 GB, compared to just over 2 GB with the V10.
>> NEW DLL FILE REQUIRED TO FLASH!! <<
You must use LGUP to flash this. If you haven't upgraded your DLL file for LGUP, inside this same archive, you'll find a dll file named LGUP_Common.dll. Place that DLL file in C:\Program Files (x86)\LG Electronics\LGUP\model\common. Just as a precaution, change the extension of the existing LGUP_Common.dll to .bak or something in case this doesn't work for you. After you put the new DLL file in that folder, open LGUP and in the very lower left hand corner of the window, you should see DLL Version 1.0.31.9.
Enjoy! If anyone has any questions, feel free to hit me up!
Reserved
And again.
Perfect! I was thinking about buying the V30 but was worried I couldn't dev on it as there was nothing to go back to. Thank You.
je2854 said:
Perfect! I was thinking about buying the V30 but was worried I couldn't dev on it as there was nothing to go back to. Thank You.
Click to expand...
Click to collapse
What kind of Dev work do you plan on doing?
abine45 said:
What kind of Dev work do you plan on doing?
Click to expand...
Click to collapse
As of right now just internals.
Sounds, Bloatware, Boot Animations... right now until I can get my computer back up and running...
Once I get my machine back up and running I will be doing audio mods and deeper customizations...
We also need to get root!
I'm going to experiment on it now that we can revert back!
je2854 said:
As of right now just internals.
Sounds, Bloatware, Boot Animations... right now until I can get my computer back up and running...
Once I get my machine back up and running I will be doing audio mods and deeper customizations...
We also need to get root!
I'm going to experiment on it now that we can revert back!
Click to expand...
Click to collapse
So you are going to work on root? May I be of any service to you? I am pretty knowledgeable and may be able to help.
abine45 said:
So you are going to work on root? May I be of any service to you? I am pretty knowledgeable and may be able to help.
Click to expand...
Click to collapse
Once I get operational I will attempt it.
I see no reason why we cannottry together.
je2854 said:
Once I get operational I will attempt it.
I see no reason why we cannottry together.
Click to expand...
Click to collapse
Awesome, DM me when you are able to get going Thank you
There are rumors someone cracked the bootloader and rooted a Verizon LG G6, but for their own reason chose not to publish the method. Knowing the person who told me, I have no reason to doubt it. But, no, I don't know how they did it, as I am not a dev.
This of course leads to a bunch of questions. Is it possible some of the 2017 LG flagship (G6, V30) carrier models have ADB flash commands if you can get past the bootloader? We know the T-mobile LG G6 and LG V30 do not, because the bootloader is easily unlocked and they are ADB crippled. We just assumed all the other carrier modes were the same way, because no one has cracked the bootloader and published the results.
Or this person cracked the bootloader and found some other way to root. They didn't go any further than that, but they did unlock the bootloader and root a Verizon LG G6.
ChazzMatt said:
There are rumors someone cracked the bootloader and rooted a Verizon LG G6, but for their own reason chose not to publish the method. Knowing the person who told me, I have no reason to doubt it. But, no, I don't know how they did it, as I am not a dev.
This of course leads to a bunch of questions. Is it possible some of the 2017 LG flagship (G6, V30) carrier models have ADB flash commands if you can get past the bootloader? We know the T-mobile LG G6 and LG V30 do not, because the bootloader is easily unlocked and they are ADB crippled. We just assumed all the other carrier modes were the same way, because no one has cracked the bootloader and published the results.
Or this person cracked the bootloader and found some other way to root. They didn't go any further than that, but they did unlock the bootloader and root a Verizon LG G6.
Click to expand...
Click to collapse
Do they know who possibly did this? Where are the rumors coming from?
abine45 said:
Do they know who possibly did this? Where are the rumors coming from?
Click to expand...
Click to collapse
Yes, I know.
https://forum.xda-developers.com/showpost.php?p=74470375&postcount=333
That link above discusses it more, but other than that I'm not interested in "proving" anything. I'm not the dev, and he can release what he wants to release. I encourage everyone to buy the "open market" version of the LG V30. That will have guaranteed root, TWRP, ROMs, kernels, etc.
If you want to read where I got it from, read back through my posts. It was discussed in open thread about three weeks ago.
The only reason I'm mentioning it here is it might be relevant to the LG V30, to let people know a carrier branded LG G6 was bootloader unlocked and rooted. If one person can do it, others can.
je2854 said:
Once I get operational I will attempt it.
I see no reason why we cannottry together.
Click to expand...
Click to collapse
The bootloader for the LG V30 has to be cracked correct?
abine45 said:
The bootloader for the LG V30 has to be cracked correct?
Click to expand...
Click to collapse
Technically no. The V20 doesn't have a cracked BL and it still has full root.
je2854 said:
Technically no. The V20 doesn't have a cracked BL and it still has full root.
Click to expand...
Click to collapse
How did it allow TWRP and roms to be installed especially if the bootloader still does it's checks?
abine45 said:
How did it allow TWRP and roms to be installed especially if the bootloader still does it's checks?
Click to expand...
Click to collapse
If I remember correctly, engineering boatloaders don't have such a rigorous check...
je2854 said:
Technically no. The V20 doesn't have a cracked BL and it still has full root.
Click to expand...
Click to collapse
Dirty Santa exploit cracked the bootloader of the V20 (December 2016). And here (June 2017).
DirtySanta Exploit Unlocks the Bootloader of the LG V20 H990 -- XDA article, June 2017
And the 2016 V20 still had all the ADB flash commands. So, once past the bootloader, you had free reign. That has changed with the 2017 LG flagships, where LG has removed most of the ADB flash commands.
Even this LG V20 method, in a thread started END of August 2017 has as a first step -- RUN Dirty Santa! Even though Dirty Santa/Dirty Cow exploit was now patched, you can swap out modules in the phone, so it will then still run. So, I do not know of any LG V20 that were rooted where the bootloader was not first unlocked -- even if you are replacing out modules with "Engineering" modules or whatever to allow Dirty Santa to still run. If you have other information to the contrary, I would be interested in hearing it.
Now back during the LG G2 and LG G3 era you could root and install TWRP without unlocking the bootloader, but that was back when signed packages were not required.
ChazzMatt said:
Dirty Santa exploit cracked the bootloader of the V20 (December 2016). And here (June 2017).
DirtySanta Exploit Unlocks the Bootloader of the LG V20 H990 -- XDA article, June 2017
And the 2016 V20 still had all the ADB flash commands. So, once past the bootloader, you had free reign. That has changed with the 2017 LG flagships, where LG has removed most of the ADB flash commands.
Even this LG V20 method, in a thread started END of August 2017 has as a first step -- RUN Dirty Santa! Even though Dirty Santa/Dirty Cow exploit was now patched, you can swap out modules in the phone, so it will then still run. So, I do not know of any LG V20 that were rooted where the bootloader was not first unlocked -- even if you are replacing out modules with "Engineering" modules or whatever to allow Dirty Santa to still run. If you have other information to the contrary, I would be interested in hearing it.
Now back during the LG G2 and LG G3 era you could root and install TWRP without unlocking the bootloader, but that was back when signed packages were not required.
Click to expand...
Click to collapse
You seem pretty smart with this stuff? do you do developing or hacking of your own?
abine45 said:
You seem pretty smart with this stuff? do you do developing or hacking of your own?
Click to expand...
Click to collapse
I'm not a developer, but I research a lot and I have knowledgeable people tell me stuff.
I keep up with LG phones, and I know V20 bootloader was unlocked by Dirty Santa exploit. Which was why I corrected the misinformation that the V20 was rooted without unlocking the bootloader.
Maybe there's another method of rooting V20 of which I'm unaware, but in V20 forum all I see are the links I posted above - which all involve unlocking the bootloader.
But the v30 is too new to have a dirty santa version anyway. And no adb commands.
Unless this makes it on to the lg list for unlocking I dont think it will happen.
Sent from my HTC One_M8 dual sim using XDA Labs
Hello all,
-I bought a 'refurbished' LG G4 online (claimed to be H815), but when I got it & checked the motherboard inside, it's VS986 instead.
Currently it's on H815 v10h (Lollipop), with ARB v2, and Baseband is MPSS.BO.2.5.c3-00070-M8992FAAAANAZM-1.19025.1
-What's is the best option I have (which ROM to flash)? I'm from Malaysia & I need GSM for 2G/3G capability (AFAIK Verizon's VS986 uses CDMA)*.
Please advise, thank you.
*EDIT: I entered Service Menu & found that several GSM & WCDMA modes are supported, but none of LTE modes is available.
Musafir_86 said:
Hello all,
-I bought a 'refurbished' LG G4 online (claimed to be H815), but when I got it & checked the motherboard inside, it's VS986 instead.
Currently it's on H815 v10h (Lollipop), with ARB v2, and Baseband is MPSS.BO.2.5.c3-00070-M8992FAAAANAZM-1.19025.1
-What's is the best option I have (which ROM to flash)? I'm from Malaysia & I need GSM for 2G/3G capability (AFAIK Verizon's VS986 uses CDMA)*.
Please advise, thank you.
*EDIT: I entered Service Menu & found that several GSM & WCDMA modes are supported, but none of LTE modes is available.
Click to expand...
Click to collapse
The problem with Frankensteins like this is nobody knows what EXACTLY they did to make it look like a h815.
First thing to try is checking the ARB (Antirollback, see my sig) and if you are one of the 1% of lucky users then you may see "nonfusing device" instead of an ARB level.
Assuming that you did that already (as u mentioned ARB2) u are screwed.
There is no valid way to get to a good result here.
Your main issue is that the modem partition must be a vs986 one - or at least a vs986 compatible one as the ARB also takes place in that partition.
Second, if you cannot change the modem partition u might not be able to get 2G/3G as you already found out.
unlocking the device won't help either as the main issue you have relies on the the modem (partition) and even when flashing a vs986 ROM or any other it might never work.
Last - but not least - whatever you do or plan to do: kee my first sentence in mind. Each step you do can easily hard brick your device.
Ofc you can use QFIL to likely bring it back to life (the G4's are really hard to brick until an unusable state) but for this you need the extra tools, knowledge and time to learn.
sorry but there is nothing much you can do other then request your money back as you were tricked.
if you can't I may would try getting another modem partition to work with but doing that requires also a lot of time to learn how to use SALT to extract KDZs, identify the ARB of the modem partition properly (so you do not increase the ARB level by flashing a wrong modem partition) and so on..
gl
.-
steadfasterX said:
The problem with Frankensteins like this is nobody knows what EXACTLY they did to make it look like a h815.
First thing to try is checking the ARB (Antirollback, see my sig) and if you are one of the 1% of lucky users then you may see "nonfusing device" instead of an ARB level.
Assuming that you did that already (as u mentioned ARB2) u are screwed.
There is no valid way to get to a good result here.
Your main issue is that the modem partition must be a vs986 one - or at least a vs986 compatible one as the ARB also takes place in that partition.
Second, if you cannot change the modem partition u might not be able to get 2G/3G as you already found out.
unlocking the device won't help either as the main issue you have relies on the the modem (partition) and even when flashing a vs986 ROM or any other it might never work.
Last - but not least - whatever you do or plan to do: kee my first sentence in mind. Each step you do can easily hard brick your device.
Ofc you can use QFIL to likely bring it back to life (the G4's are really hard to brick until an unusable state) but for this you need the extra tools, knowledge and time to learn.
sorry but there is nothing much you can do other then request your money back as you were tricked.
if you can't I may would try getting another modem partition to work with but doing that requires also a lot of time to learn how to use SALT to extract KDZs, identify the ARB of the modem partition properly (so you do not increase the ARB level by flashing a wrong modem partition) and so on..
gl
.-
Click to expand...
Click to collapse
-Thanks for your reply.
-About returning & requesting a refund, I think it'll be hard as I already damaged the warranty sticker over one of the screws while trying to check the board.
-If we ignore the modem issue for now (maybe use it as WiFi-only device), then what's the best ROM I could flash? I hope at least Marshmallow so it'll last longer as more & more apps are targetting higher Android API levels.
-BTW, I just tried flashing VS9862BA_00_0525_ARB02.kdz but LG UP says "KDZ file is invalid". On another note, while in download mode, I just noticed it says:
Code:
USER S0.0 AS0.0 B91 UHS
S U LG-H810 05.1 Hrev_10
H81010o
-So, now it also has AT&T's H810 pieces inside too?
-BTW, sorry for PM'ing you earlier; I didn't notice your signature (even though you put it in big, red fonts!).
Musafir_86 said:
-Thanks for your reply.
-About returning & requesting a refund, I think it'll be hard as I already damaged the warranty sticker over one of the screws while trying to check the board.
-If we ignore the modem issue for now (maybe use it as WiFi-only device), then what's the best ROM I could flash? I hope at least Marshmallow so it'll last longer as more & more apps are targetting higher Android API levels.
-BTW, I just tried flashing VS9862BA_00_0525_ARB02.kdz but LG UP says "KDZ file is invalid". On another note, while in download mode, I just noticed it says:
Code:
USER S0.0 AS0.0 B91 UHS
S U LG-H810 05.1 Hrev_10
H81010o
-So, now it also has AT&T's H810 pieces inside too?
-BTW, sorry for PM'ing you earlier; I didn't notice your signature (even though you put it in big, red fonts!).
Click to expand...
Click to collapse
-Okay, now I have successfully flashed VS9862BA_00_0525_ARB02.kdz by extracting the DZ file & flashing it directly! :good:
However, it seems Android FRP (Firmware Reset Protection) has been triggered; need to figure on how to bypass this while on 2BA firmware.....
Musafir_86 said:
-Thanks for your reply.
-About returning & requesting a refund, I think it'll be hard as I already damaged the warranty sticker over one of the screws while trying to check the board.
-If we ignore the modem issue for now (maybe use it as WiFi-only device), then what's the best ROM I could flash? I hope at least Marshmallow so it'll last longer as more & more apps are targetting higher Android API levels.
-BTW, I just tried flashing VS9862BA_00_0525_ARB02.kdz but LG UP says "KDZ file is invalid". On another note, while in download mode, I just noticed it says:
-Okay, now I have successfully flashed VS9862BA_00_0525_ARB02.kdz by extracting the DZ file & flashing it directly! :good:
However, it seems Android FRP (Firmware Reset Protection) has been triggered; need to figure on how to bypass this while on 2BA firmware.....
Click to expand...
Click to collapse
Warranty or not i would return it as its not what you had paid for. But up to you and ofc as you flashed a kdz on it you would need to get it back to the state jt was before..
You could unlock and flash nougat, oreo, pie but as with flashing the vs986 kdz/dz nothing comes without a risk ofc. Especially on Frankensteins!
The good is that you likely can revert UsU if you ever want to as you have a fusing device.
Sent from my OnePlus 7T Pro using XDA Labs