Stuck in TWRP recovery on a Moto G4 running Nougat - General Questions and Answers

Problem: I unblocked my Moto g4 running Nougat and installed the latest version of twrp; everything was going well. Then I rooted my phone and installed superSU using twrp --- That is when the problem began and I can no longer boot into my regular system. Everytime my phone boots it boots into twrp recovery mode -
I used these two guides to do this:
https://forum.xda-developers.com/moto-g4-plus/how-to/guide-newbie-resource-thread-t3386584
https://forum.xda-developers.com/moto-g4-plus/development/wip-modified-boot-img-root-t3387113
What can I do to simply boot up into my regular Nougat system?

*XAOS* said:
Problem: I unblocked my Moto g4 running Nougat and installed the latest version of twrp; everything was going well. Then I rooted my phone and installed superSU using twrp --- That is when the problem began and I can no longer boot into my regular system. Everytime my phone boots it boots into twrp recovery mode -
I used these two guides to do this:
https://forum.xda-developers.com/moto-g4-plus/how-to/guide-newbie-resource-thread-t3386584
https://forum.xda-developers.com/moto-g4-plus/development/wip-modified-boot-img-root-t3387113
What can I do to simply boot up into my regular Nougat system?
Click to expand...
Click to collapse
When you flashed SuperSU, did you wipe cache and dalvik/ART cache in TWRP?
Did you accidentally wipe your system partition? If so, you have no OS to boot into, on this case, you'll have to flash a custom ROM for your model number or a modified TWRP flashable zip of your stock firmware.
If these things don't work then you've corrupted something, are you certain that you unlocked your device correctly? Are you certain that you covered all the bases for rooting your device?
Sent from my SM-S903VL using Tapatalk

Droidriven said:
When you flashed SuperSU, did you wipe cache and dalvik/ART cache in TWRP?
Did you accidentally wipe your system partition? If so, you have no OS to boot into, on this case, you'll have to flash a custom ROM for your model number or a modified TWRP flashable zip of your stock firmware.
If these things don't work then you've corrupted something, are you certain that you unlocked your device correctly? Are you certain that you covered all the bases for rooting your device?
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I think I might have corrupted something- In the meantime I flashed the original stock ROM that I got with the device - which was Marshmallow 6.0 but now I can't update back to 7.0. I flashed 6.0 because I couldnt find any official 7.0 ROMS for my Moto g4. Thanks for your response! If you have any idea why I can't update please let me know!

*XAOS* said:
I think I might have corrupted something- In the meantime I flashed the original stock ROM that I got with the device - which was Marshmallow 6.0 but now I can't update back to 7.0. I flashed 6.0 because I couldnt find any official 7.0 ROMS for my Moto g4. Thanks for your response! If you have any idea why I can't update please let me know!
Click to expand...
Click to collapse
That question is better answered by asking in the G4 forum, I'm not familiar enough with your device hardware/software specifics.
Sent from my SM-S903VL using Tapatalk

Related

(help) how to install official 6.0 using twrp on moto g3

Im still on 5.1.1 official version and my device is bootloader unlocked and twrp installed help me how to install official 6.0 version
First just flash 6.0 image through fastboot process in this twrp will be replace with stock recovery, Second flash someone's 6.0 Nandroid backup through TWRP...
Sent from my Toilet using Moto G3....
I have also same query, having xt1550 with 5.1.1 and unlocked bootloader with root access.
Also receiving OTA notification but can't install the same.
Tried to install OTA manually but could not go into recovery mode stuck on "No Command" screen.
Please guide....
beworld16 said:
I have also same query, having xt1550 with 5.1.1 and unlocked bootloader with root access.
Also receiving OTA notification but can't install the same.
Tried to install OTA manually but could not go into recovery mode stuck on "No Command" screen.
Please guide....
Click to expand...
Click to collapse
You can't flash OTA with root. You can look at the other thread on factory firmware and flash a Marshmallow factory image if one is available for your model. That is safer than flashing an OTA anyway.
Tel864 said:
You can't flash OTA with root. You can look at the other thread on factory firmware and flash a Marshmallow factory image if one is available for your model. That is safer than flashing an OTA anyway.
Click to expand...
Click to collapse
That's very much true.. Don't flash ota with TWRP with having root access..
Sent from my Moto G(Osprey)
Thanks for the reply
I have downloaded Official Firmware of 6.0 for XT1550 from here.
So Now, can i process with this using fastboot command.
If yes, will it look the bootloader ?
Tel864 said:
You can't flash OTA with root. You can look at the other thread on factory firmware and flash a Marshmallow factory image if one is available for your model. That is safer than flashing an OTA anyway.
Click to expand...
Click to collapse
I thought OTA's worked fine with root installed, although you often lose root in the process, it was custom recovery they burped at?

What did TWRP do to my tablet?

I installed TWRP. It was supposed to be TWRP 2.8.6.0, but it is 2.8.5.0. Today, I just backed up my tablet with it. After using TWRP, my tablet boots up 6 times faster and the UI functions twice as fast as it did before. Overall, my tablet got better after running TWRP. So, what did it do? Also, I want to flash Lollipop. Can I do that with this version?
I don't know what twrp did to your tablet. If you want to flash a lollipop or a marshmallow rom however you should use this version of twrp : http://forum.xda-developers.com/gal...overy-team-win-recovery-project-twrp-t3464050
And use one of theses rom :
lollipop : http://forum.xda-developers.com/galaxy-tab-2/galaxy-tab-2-unified/rom-cyanogenmod-12-cm12-t2997934
Marshmallow (recommended) : http://forum.xda-developers.com/galaxy-tab-2/galaxy-tab-2-unified/rom-cyanogenmod-13-cm13-0-t3303798
Ka-B00M said:
I installed TWRP. It was supposed to be TWRP 2.8.6.0, but it is 2.8.5.0. Today, I just backed up my tablet with it. After using TWRP, my tablet boots up 6 times faster and the UI functions twice as fast as it did before. Overall, my tablet got better after running TWRP. So, what did it do? Also, I want to flash Lollipop. Can I do that with this version?
Click to expand...
Click to collapse
twrp manage all general functions before the android system completely started. you can compare twrp with the bios system on your pc.
if you want install the latest roms, you should upgrade your twrp to the latest unofficial common version (3.0.2-6). you can find it here: http://andi34.github.io/recoveries_tab2.html
smart-t78 said:
twrp manage all general functions before the android system completely started. you can compare twrp with the bios system on your pc.
if you want install the latest roms, you should upgrade your twrp to the latest unofficial common version (3.0.2-6). you can find it here: http://andi34.github.io/recoveries_tab2.html
Click to expand...
Click to collapse
Can I flash the linked recovery using the recovery I already have? If not, how can i do it? I do not have a PC, BTW.
Ka-B00M said:
Can I flash the linked recovery using the recovery I already have? If not, how can i do it? I do not have a PC, BTW.
Click to expand...
Click to collapse
yes, you can install the new version with your current twrp.
smart-t78 said:
yes, you can install the new version with your current twrp.
Click to expand...
Click to collapse
Awesome.
It's official, my device will be upgraded. May the force be with us all!

Moto G4 Plus US XT1644 Stock Unmodified 6.0.1 TWRP Backup & Recovery/Logo Images

Moto G4 Plus US Variant XT1644
Build# MPJ24.139-64 Android 6.0.1
Stock Unmodified TWRP Backup
Stock Recovery.img & Logo.bin​
Description:
I could not find ANY stock images for the US XT1644 variant so I made my own for others that have modified their system partition and wish to restore to a factory state and take the 7.0 update. Backup created on a factory reset unmodified stock build (not previously rooted/xposed/modified in any way) via fastboot booting TWRP w/system write disabled. Stock recovery and logo extracted via DD from stock rooted rom after TWRP backup was made. I pulled the recovery and logo images as these are the most commonly modified partitions (other than the system). This backup will work if you stayed on 6.0.1 and rooted/exposed/changed boot logo/etc. If you played with the 7.0 updates made for other variants, I honestly don't know if this will work for you to take the OTA as the bootloader/modem were likely modified - Test and let us know.
Directions:
-Have ADB working on your PC (google it, not getting into that here)
-Download TWRP backup here: https://mega.nz/#F!vBgU3QJB!R5J5RgZkvUiWHwmIfN6BkA
-Move backup to your proper TWRP backup location on your sd or external sd
-Restore backup via TWRP and reboot
-Download stock recovery & logo images here: https://mega.nz/#F!eBpB3Z5C!J6hoLKdfcObSLavWCsLnyw
-Power off device/plug into pc/hold volume down for 5 seconds/press and hold power & volume down until fastboot appears
-Move files to adb location (Windows) or open terminal where you downloaded the files (Linux) on your pc
-Verify connection
Code:
fastboot devices
-Restore stock recovery:
Code:
fastboot flash recovery recovery.img
-Restore stock logo (if you changed it previously to get rid of warning):
Code:
fastboot flash logo logo.bin
-Reboot and enjoy stock 6.0.1 and be able to take OTA
You are the mvp here!
I have the exact model, and it worked out great
When I was setting up as a new device, it showed some errors like SystemUI stopped working, and File Manager, theres a way to fix that?
Will it show any problems in the future? Of those same ones?
My Compilation Number is "MPJ24.139-48", should be ...64
In stock recovery says i'm at MPJ24.139-64/65
Edit* I had to flash a XT1625-XT1644 MPJ24.139-64 Firmware, then I wiped the OS with TWRP, then I restored your backup and worked like a charm, now running 6.0.1 MPJ24.139-64 with no problems :laugh::good:
panchoarcia said:
You are the mvp here!
I have the exact model, and it worked out great
When I was setting up as a new device, it showed some errors like SystemUI stopped working, and File Manager, theres a way to fix that?
Will it show any problems in the future? Of those same ones?
My Compilation Number is "MPJ24.139-48", should be ...64
In stock recovery says i'm at MPJ24.139-64/65
Click to expand...
Click to collapse
You must have been on the release prior to the one I was on when I got the phone this December. Something is not matching up. You likely have a different bootloader, and modem. When I get a chance I'll extract as many partitions that I can get access too for fastboot flashing. I'll try to do it later on this evening. It really sucks Moto won't give us full firmware for this phone.
Sent from my XT1575 using Tapatalk
annoyingduck said:
You must have been on the release prior to the one I was on when I got the phone this December. Something is not matching up. You likely have a different bootloader, and modem. When I get a chance I'll extract as many partitions that I can get access too for fastboot flashing. I'll try to do it later on this evening. It really sucks Moto won't give us full firmware for this phone.
Click to expand...
Click to collapse
I Will flash stock xt1644 firmware 64, then i restore your backup
Does XT1644 have an OTA available now? I didn't think it was pushed yet.
pupamonkey said:
Does XT1644 have an OTA available now? I didn't think it was pushed yet.
Click to expand...
Click to collapse
It's not available, we're still waiting for it, that's why we flashing stock firmware again
Thanks for doing this! It's essentially what I did to get the marshmallow update (restore stock system & boot via TWRP, then recovery & logo via fastboot).
Please let us know when you see moto/Lenovo push out the nougat update via OTA!
Sent from my Moto G4 Plus using Tapatalk
you are the champ!! i have exact same model but i am yet to update to 64 release as i just got the phone today. Just doing some research before i grease my hands! thanks man!
Sigh... Sitting here in California with an XT1644. I restored the last official stock firmware (Marshmallow Build #: MPJ24.139-64), and the OTA update simply check says my "Software is up to date!". With India variants having received Nougat back in December, I'm wondering WTF is taking so long?
I'm mostly interested in getting the updated baseband, as I'm now running @Silesh.Nair's unofficial LinageOS Nougat with few issues. I guess I'll keep waiting for the official modem update for this device in this country.
Hmmph.
bmeek said:
Sigh... Sitting here in California with an XT1644. I restored the last official stock firmware (Marshmallow Build #: MPJ24.139-64), and the OTA update simply check says my "Software is up to date!". With India variants having received Nougat back in December, I'm wondering WTF is taking so long?
I'm mostly interested in getting the updated baseband, as I'm now running @Silesh.Nair's unofficial LinageOS Nougat with few issues. I guess I'll keep waiting for the official modem update for this device in this country.
Hmmph.
Click to expand...
Click to collapse
Yeah, the US variant xt1644 still has not gotten the 7.0 update. So friggen annoying!! That's basically what I'm doing too, waiting for is the official OTA just for the radio. I'd rather have the 7.0 baseband/firmware before I start flashing any custom roms.
where to check?
i have the us variant from best buy as well , but i twicked it a lot .
How can i know when a nougat release is available? where can i check .
panchoarcia said:
You are the mvp here!
I have the exact model, and it worked out great
When I was setting up as a new device, it showed some errors like SystemUI stopped working, and File Manager, theres a way to fix that?
Will it show any problems in the future? Of those same ones?
My Compilation Number is "MPJ24.139-48", should be ...64
In stock recovery says i'm at MPJ24.139-64/65
Edit* I had to flash a XT1625-XT1644 MPJ24.139-64 Firmware, then I wiped the OS with TWRP, then I restored your backup and worked like a charm, now running 6.0.1 MPJ24.139-64 with no problems :laugh::good:
Click to expand...
Click to collapse
Where did you find file XT1625-XT1644 MPJ24.139-64 Firmware?
Did you flash it in TWRP as a zip file or fastboot?
Did you still have to fastboot stock recovery & logo images?
I'm on a unlocked bootloader/TWRP installed/rooted on MPJ24.139-48. Trying to get back to STOCK.
Hymizzle said:
Where did you find file XT1625-XT1644 MPJ24.139-64 Firmware?
Did you flash it in TWRP as a zip file or fastboot?
Did you still have to fastboot stock recovery & logo images?
I'm on a unlocked bootloader/TWRP installed/rooted on MPJ24.139-48. Trying to get back to STOCK.
Click to expand...
Click to collapse
If you flash a XT1625-XT1644 firmware and you use it "normally" on a XT1644, at some point you will have ghost touch even with low brightness, but...
For upgrading, I'll recommend flashing XT1625-XT1644, (cause there's no
...139-64 XT1644 firmware, just a firmware for both)
Flash it via fastboot, boot it up, flash TWRP recovery, wipe the full system with it, download the TWRP backup that was posted here, restore it, then via fastboot flash the stock recovery (for removing TWRP) and stock logo, then you will have MPJ24.139-64 with no problems, just waiting for nougat OTA for retus version.
Here's the link for retus firmwares: https://mirrors.lolinet.com/firmware/moto/athene/official/RETUS/
didn't work from be coming back from flashing nougat firmware, didnt expect it to just pointing it out
TheDude1998 said:
didn't work from be coming back from flashing nougat firmware, didnt expect it to just pointing it out
Click to expand...
Click to collapse
Yeah I wouldn't think so, but thanks for letting us know.
Sent from my XT1575 using Tapatalk
getting the Nougat OTA
annoyingduck said:
Yeah, the US variant xt1644 still has not gotten the 7.0 update. So friggen annoying!! That's basically what I'm doing too, waiting for is the official OTA just for the radio. I'd rather have the 7.0 baseband/firmware before I start flashing any custom roms.
Click to expand...
Click to collapse
So now that an update to Nougat is getting pushed to xt1644 devices in the 'States, I'm having some challenges successfully applying the update with my unlocked bootloader.
I believe I've got the correct system, boot, logo & recovery images; I'm able to boot up, download the OTA, and initiate the update. Unfortunately, the update process eventually displays the green android character on its back with the red error symbol.
I was hoping to get the update, with the proper local and updated baseband, without going all the way back to stock with the locked bootloader, etc.
I know i had taken the October Marshmallow security update OTA with an unlocked bootloader... Can anyone share the minimum requirements for the current Nougat OTA?
Edit: I went ahead and returned my US xt1644 to the latest stock Marshmallow firmware (MPJ24.139-64) via fastboot and the script commands listed in this post by @yeshwanthvshenoy. Though I left the bootloader unlocked, the phone booted up and went through the OTA Nougat update process without any issue.
I stayed on the new/updated stock Nougat ROM just long enough to confirm that it's working well I'm on my network (Verizon LTE/CDMA), then I flashed @Shreps' build of TWRP 3.1 and backed up every partition before restoring @Silesh.Nair's LineageOS-based InvictaOS. At last I have an up-to-date baseband (M8952_70030.25.03.62R) and appear to have no issues on custom Nougat ROMs - fingerprint registration works fine, for example.
Sent from my Moto G4 Plus using Tapatalk
bmeek said:
So now that an update to Nougat is getting pushed to xt1644 devices in the 'States, I'm having some challenges successfully applying the update with my unlocked bootloader.
I believe I've got the correct system, boot, logo & recovery images; I'm able to boot up, download the OTA, and initiate the update. Unfortunately, the update process eventually displays the green android character on its back with the red error symbol.
I was hoping to get the update, with the proper local and updated baseband, without going all the way back to stock with the locked bootloader, etc.
I know i had taken the October Marshmallow security update OTA with an unlocked bootloader... Can anyone share the minimum requirements for the current Nougat OTA?
Edit: I went ahead and returned my US xt1644 to the latest stock Marshmallow firmware (MPJ24.139-64) via fastboot and the script commands listed in this post by @yeshwanthvshenoy. Though I left the bootloader unlocked, the phone booted up and went through the OTA Nougat update process without any issue.
I stayed on the new/updated stock Nougat ROM just long enough to confirm that it's working well I'm on my network (Verizon LTE/CDMA), then I flashed @Shreps' build of TWRP 3.1 and backed up every partition before restoring @Silesh.Nair's LineageOS-based InvictaOS. At last I have an up-to-date baseband (M8952_70030.25.03.62R) and appear to have no issues on custom Nougat ROMs - fingerprint registration works fine, for example.
Click to expand...
Click to collapse
If i fash stock mm via adb will my bootloader still unlock? and if upgrade via ota, bootloader still unlock too?
dedik46 said:
If i fash stock mm via adb will my bootloader still unlock? and if upgrade via ota, bootloader still unlock too?
Click to expand...
Click to collapse
Yes your bootloader will still be unlocked unless you specifically enter the oem lock command. Read the tutorials, they all explain how to keep your bootloader unlocked.
Sent from my XT1575 using Tapatalk
bmeek said:
So now that an update to Nougat is getting pushed to xt1644 devices in the 'States, I'm having some challenges successfully applying the update with my unlocked bootloader.
I believe I've got the correct system, boot, logo & recovery images; I'm able to boot up, download the OTA, and initiate the update. Unfortunately, the update process eventually displays the green android character on its back with the red error symbol.
I was hoping to get the update, with the proper local and updated baseband, without going all the way back to stock with the locked bootloader, etc.
I know i had taken the October Marshmallow security update OTA with an unlocked bootloader... Can anyone share the minimum requirements for the current Nougat OTA?
Edit: I went ahead and returned my US xt1644 to the latest stock Marshmallow firmware (MPJ24.139-64) via fastboot and the script commands listed in this post by @yeshwanthvshenoy. Though I left the bootloader unlocked, the phone booted up and went through the OTA Nougat update process without any issue.
I stayed on the new/updated stock Nougat ROM just long enough to confirm that it's working well I'm on my network (Verizon LTE/CDMA), then I flashed @Shreps' build of TWRP 3.1 and backed up every partition before restoring @Silesh.Nair's LineageOS-based InvictaOS. At last I have an up-to-date baseband (M8952_70030.25.03.62R) and appear to have no issues on custom Nougat ROMs - fingerprint registration works fine, for example.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
I had the exact same issue, and your solution worked perfectly. It's unfortunate how difficult Motorola has made it to find the stock firmware for the XT1644.
vishnureddy17 said:
I had the exact same issue, and your solution worked perfectly. It's unfortunate how difficult Motorola has made it to find the stock firmware for the XT1644.
Click to expand...
Click to collapse
Which of these 5 download? .

XT926 from 4.1.1 to LineageOS 14.1

I do not understand how to do what I want to do. I want to install the custom ROM LineageOS 14.1. Here's where I am stuck.
In trying to install the xt926/spyder 14.1 nightly build from 6.30.17 using ROM Manager, I get the following error message E3004: This package is for device: cdma_spyder; this device is xt926. It seems the error message states I am trying to install it on the wrong phone, so the install is aborted. But I do have an xt926 that I'm trying to install to. I posted on the Lineage site. I was told "don't use rom manager or clockworkmod they haven't been supported in years; also make sure you're using the latest TWRP for the correct device. The "this is device xxxx" is based on what the recovery says it is." I do not know which old TWRP I can use. In ROM Manager it states my current recovery is ClockworkMod 6.0.4.4. What's wrong with my recovery? The installer says I have an xt926, so why did it really fail? I'm wondering if I need the KKBL (KitKat bootloader), and the lack of that is why it really failed. If so, I do not understand from reading the posts how to get the KKBL. I read where I felt some were stating there was a small window to be able to get it and still root. I read about just flashing the BL, but then some said to never do that. Can someone please help me? TIA
Current -
OS: android 4.1.1 / 9.1.41xt926.verizon.en.us
Bootloader unlocked
Rooted
Baseband version: vanquish_bp_100700.210.64.05p
Kernel version: 3.0.31-g59a8475
System modifications: android 4.1.1 / 9.1.41xt926.verizon.en.us
Goal -
LineageOS 14.1 (Nougat)
Bootloader unlocked
Rooted
retalger said:
I do not understand how to do what I want to do. I want to install the custom ROM LineageOS 14.1. Here's where I am stuck.
In trying to install the xt926/spyder 14.1 nightly build from 6.30.17 using ROM Manager, I get the following error message E3004: This package is for device: cdma_spyder; this device is xt926. It seems the error message states I am trying to install it on the wrong phone, so the install is aborted. But I do have an xt926 that I'm trying to install to. I posted on the Lineage site. I was told "don't use rom manager or clockworkmod they haven't been supported in years; also make sure you're using the latest TWRP for the correct device. The "this is device xxxx" is based on what the recovery says it is." I do not know which old TWRP I can use. In ROM Manager it states my current recovery is ClockworkMod 6.0.4.4. What's wrong with my recovery? The installer says I have an xt926, so why did it really fail? I'm wondering if I need the KKBL (KitKat bootloader), and the lack of that is why it really failed. If so, I do not understand from reading the posts how to get the KKBL. I read where I felt some were stating there was a small window to be able to get it and still root. I read about just flashing the BL, but then some said to never do that. Can someone please help me? TIA
Current -
OS: android 4.1.1 / 9.1.41xt926.verizon.en.us
Bootloader unlocked
Rooted
Baseband version: vanquish_bp_100700.210.64.05p
Kernel version: 3.0.31-g59a8475
System modifications: android 4.1.1 / 9.1.41xt926.verizon.en.us
Goal -
LineageOS 14.1 (Nougat)
Bootloader unlocked
Rooted
Click to expand...
Click to collapse
The spyer is the old razor xt912 not the razor hd xt926 the xt926 is the vanquish. your flashing xt912 firmware on an xt926 device.
SOLVED
OGdroidster said:
The spyer is the old razor xt912 not the razor hd xt926 the xt926 is the vanquish. your flashing xt912 firmware on an xt926 device.
Click to expand...
Click to collapse
Oh! Thank you so much for the help.
retalger said:
Oh! Thank you so much for the help.
Click to expand...
Click to collapse
Sure your welcome
Has anyone managed to get Lineage OS 14.1 working on the xt926? I was able to flash it through TWRP along with opengapps 7.1 and it boots but either System UI or Setup is constantly crashing meaning i'm unable to proceed past setup.
drkdeath5000 said:
Has anyone managed to get Lineage OS 14.1 working on the xt926? I was able to flash it through TWRP along with opengapps 7.1 and it boots but either System UI or Setup is constantly crashing meaning i'm unable to proceed past setup.
Click to expand...
Click to collapse
To get 14.1 working you need to use RSDLite to flash back to 4.1.2 Jelly Bean (https://www.androidfilehost.com/?fid=24269982087011677), then install TWRP for the Photon Q (https://twrp.me/devices/motorolaphotonq.html) then use the official nightly builds for the Photon Q posted on the Lineage website. Open Gapps ARM 7.1 nano works best for me.
That said, you won't be able to use your main mic for phone calls, only speakerphone. I have yet to find a rom/recovery/firmware combination that will allow fully functional phone calls with anything above 4.4. This isn't a problem for me as this is a toy without a sim card in it, what some people call a toilet phone. It sits in my bathroom vanity and comes out when I forget one of my main devices. Other than that I play with it once every few months to see how far the development community has pushed it.
thunder2132 said:
To get 14.1 working you need to use RSDLite to flash back to 4.1.2 Jelly Bean (https://www.androidfilehost.com/?fid=24269982087011677), then install TWRP for the Photon Q (https://twrp.me/devices/motorolaphotonq.html) then use the official nightly builds for the Photon Q posted on the Lineage website. Open Gapps ARM 7.1 nano works best for me.
That said, you won't be able to use your main mic for phone calls, only speakerphone. I have yet to find a rom/recovery/firmware combination that will allow fully functional phone calls with anything above 4.4. This isn't a problem for me as this is a toy without a sim card in it, what some people call a toilet phone. It sits in my bathroom vanity and comes out when I forget one of my main devices. Other than that I play with it once every few months to see how far the development community has pushed it.
Click to expand...
Click to collapse
I tried this last weekend but was getting constant force closes from System UI so i gave up and went back to the MokeeOS build.
Thanks @thunder2132. After fumbling about, I finally got this working:
- In TWRP, wiped cache, data & system
- Reflashed 4.1.2 factory image
- I used fastboot manually and followed the recipe in the XML file. The gpt and tz images can't be downgraded, and I did not wipe userdata [not wiping this was probably a mistake])
- Rebooted to system with sim card
- Powered off
- Booted into bootloader/fastboot and flashed TWRP
- `fastboot reboot-bootloader` (in an attempt to keep the phone from trying to boot into system again)
- Booted into TWRP, flashed LOS & OpenGApps Nano
- Tried to reboot into system and failed
- Booted into TWRP, "Format Data"
- Rebooted into system, waited, profited
Now I'd like to figure out why I can only use ADB over the network. >:| It doesn't show up at all over USB, neither in LOS nor TWRP.
PS: Later I wiped system, reflashed LOS, and flashed OpenGApps *Pico*. No issues yet.
polyzen said:
Thanks @thunder2132. After fumbling about, I finally got this working:
- In TWRP, wiped cache, data & system
- Reflashed 4.1.2 factory image
- I used fastboot manually and followed the recipe in the XML file. The gpt and tz images can't be downgraded, and I did not wipe userdata [not wiping this was probably a mistake])
- Rebooted to system with sim card
- Powered off
- Booted into bootloader/fastboot and flashed TWRP
- `fastboot reboot-bootloader` (in an attempt to keep the phone from trying to boot into system again)
- Booted into TWRP, flashed LOS & OpenGApps Nano
- Tried to reboot into system and failed
- Booted into TWRP, "Format Data"
- Rebooted into system, waited, profited
Now I'd like to figure out why I can only use ADB over the network. >:| It doesn't show up at all over USB, neither in LOS nor TWRP.
PS: Later I wiped system, reflashed LOS, and flashed OpenGApps *Pico*. No issues yet.
Click to expand...
Click to collapse
Nice! I'm glad you got it working.
what do you mean with reflashed factory image 4.1.2?
I was on Resurrection Remix for the Razr M and now flashed LOS from this thread because of connectivity problems and I hoped it is a problem of RR. But unfortunately I still just have Edge connection, no 3G or 4G. Does anyone know how to fix that? There were no problems under 4.1.
Edit: I went back to 4.1.2 and wanted to start from zero but now on 4.1.2 there's only Edge connection as well :/

[STOCK][O] H850 30a OPEN EU ROM Flashable ZIPs + KDZ (Android 8.0 "Oreo")

Stock Firmware H850 V30a "Oreo" OPEN EU ROM
KDZ-File: H85030a_00_OPEN_EU_OP_0910.kdz (MD5)
Flashable ZIP Complete: LG-H85030a-Flashable.COMPLETE.zip (MD5)
Flashable ZIP Boot: LG-H85030a-Flashable.Boot.zip (MD5)
Flashable ZIP Bootloader: LG-H85030a-Flashable.Bootloader.zip (MD5)
Flashable ZIP Modem: LG-H85030a-Flashable.Modem.zip (MD5)
Android 8.0.0
Patch level: 1 September 2018
Baseband: MPSS.TH.2.0.c1.4-00070-M8996FAAAANAZM-1.163432.2a.168009.1
Kernel: 3.18.71
Build: OPR1.170623.032
Software version: V30a-EUR-XX
Changes:
- Android Oreo
Instructions:
Upgrade from Android 7 and root using TWRP and Magisk
Do backups! Expect to lose your apps and settings!
Get the required imgages:
H85030a_00_OPEN_EU_OP_0910.kdz from above --> store it on your HDD.
twrp-3.2.3-2-h850.img --> HDD
Magisk 17.1 ZIP file. Copy it to your G5's SD card.
the LG-H85030a-Flashable.COMPLETE.zip from above --> SD-Card.
Optional: You can additionally download the MD5 file which is being used by TWRP to verify the ZIP file (simply place it in the same folder like the ZIP).
As a safety measure, I'd clean upgrade with the stock KDZ first using LG UP. This will replace also recovery to stock. If successful, you can continue.
Unlock the bootloader (if not already unlocked) as described here with the official bootloader unlock and flash TWRP. TWRP 3.2.3-2 worked for me. Boot into TWRP as described.
Optional: Do a backup in TWRP.
Format Data: "Wipe" > "Format Data" > type "yes". Wipe slider wipe is not enough!
Go back until you see the TWRP main screen. Then Reboot into Recovery. Don't start into System!
Flash / Install the LG-H85030a-Flashable.COMPLETE.zip and Magisk-v17.1.zip without reboot inbetween.
Reboot to System
enjoy!
To build the ZIPs I used parts of autoprime's previous files. Thx again!
Disclaimer: This is not an official post by LG to update the firmware! Don't blame me if you destroy your phone. If you use these files and instructions you do it at your own risk!
Is the Oreo firmware backward compatible with Nougat?
Sent from my LG-H850 using Tapatalk
Why does it come with the Vodafone app?
Flashable ZIP Bootloader: LG-H85020v-Flashable.Bootloader.zip (MD5)
Flashable ZIP Modem: LG-H85020v-Flashable.Modem.zip (MD5)
Click to expand...
Click to collapse
Just curious if above should be in the OP as they are Nougat files unless I'm mistaken.
I've had it with these stock firmware files and images, I'm waiting until a debloated stable custom rom hits. The KDZ hung on boot even after factory resetting and this stock rom wipes twrp every time I reboot causing me to endlessly reflash twrp.
ezzony said:
Just curious if above should be in the OP as they are Nougat files unless I'm mistaken.
Click to expand...
Click to collapse
Thank you! My bad, the links were correct but the texts were wrong. Corrected.
VortexHD said:
Why does it come with the Vodafone app?
Click to expand...
Click to collapse
Shouldn't. I tested it and there is no Vodafone app on my device. Where did you see this? Are you Vodafone customer?
Ok, just for information (and it may be useful to others with the same scenario):
I'm on lineage Oreo, with magisk and twrp 3.2.3.2, can I flash the COMPLETE zip => then twrp => then magisk and get the rom installed keeping twrp and root? I can't access any Windows machine (only Mac) to flash the kdz file, would it work as well if i flash all that stuff in twrp?
Thanks!
xlxcrossing said:
Is the Oreo firmware backward compatible with Nougat?
Click to expand...
Click to collapse
What do you mean? Downgrading back to Nougat? Honestly I never tried this.
xlxcrossing said:
I've had it with these stock firmware files and images, I'm waiting until a debloated stable custom rom hits. The KDZ hung on boot even after factory resetting and this stock rom wipes twrp every time I reboot causing me to endlessly reflash twrp.
Click to expand...
Click to collapse
The first boot after KDZ installation took 5-10 minutes on my device while showing the LG symbol and flashing LED... But it continued. The firmware appears stable on my device. TWRP runs persistent.
karma0321 said:
I'm on lineage Oreo, with magisk and twrp 3.2.3.2, can I flash the COMPLETE zip => then twrp => then magisk and get the rom installed keeping twrp and root? I can't access any Windows machine (only Mac) to flash the kdz file, would it work as well if i flash all that stuff in twrp?
Thanks!
Click to expand...
Click to collapse
I'd give a try but don't blame me if it is not working. Flashing the KDZ was a safety measure to me as I was not entirely sure if flashing COMPLETE alone is enough. But you are already running an Oreo OS, so I'd try it. As long as you have access to TWRP or Bootloader you can flash your working Lineage image and TWRP. However, flashing TWRP after COMPLETE makes no sense in my eyes as COMPLETE does not contain stock recovery.
DavidFlint said:
Shouldn't. I tested it and there is no Vodafone app on my device. Where did you see this? Are you Vodafone customer?
Click to expand...
Click to collapse
i also see 2 vodafone apps and some french thing "jeau" or something similar that keeps asking for permissions.
im on EE, but the previous firmware was non branded.
everything seems to be working smoothly
Anyone got any other link than Mediafire? Takes 4 hours to download and would like it faster?
DavidFlint said:
...However, flashing TWRP after COMPLETE makes no sense in my eyes as COMPLETE does not contain stock recovery.
Click to expand...
Click to collapse
Thank you so much, I didn't know COMPLETE has no recovery inside. So (sorry for bothering) what does COMPLETE contain? My guess is Rom+boot+modem+bootloader but now I'm not sure anymore
Hi
So is good rom to install from TWRP recovery. Any one fund any issue?
DavidFlint said:
Shouldn't. I tested it and there is no Vodafone app on my device. Where did you see this? Are you Vodafone customer?
Click to expand...
Click to collapse
The Vodafone app is called "Start" and the phone is unlocked and I'm not a Vodafone customer.
Rom is from Vodafone or only app?
Flashed today, have been running it for about 5 hours...
Gotta say I'm in love, and btw, no bloatware apps nothing. Just clean stock LG Oreo. Beautiful.
bmwtomas said:
Flashed today, have been running it for about 5 hours...
Gotta say I'm in love, and btw, no bloatware apps nothing. Just clean stock LG Oreo. Beautiful.
Click to expand...
Click to collapse
I flashed yesterday coming from Lineage OS 15, wiped System, Data and Caches, installed Rom and Magisk. It works.
But I do have the bloatware from LG like Facebook App and a lot of others, that I can not entirely uninstall.
And my phone keeps presenting me a software update, that I would only see, when I agree in using my personal data for...
Btw. no Vodafone App. Why do we have these different experiences? What's going on?
Oevi said:
I flashed yesterday coming from Lineage OS 15, wiped System, Data and Caches, installed Rom and Magisk. It works.
But I do have the bloatware from LG like Facebook App and a lot of others, that I can not entirely uninstall.
And my phone keeps presenting me a software update, that I would only see, when I agree in using my personal data for...
Btw. no Vodafone App. Why do we have these different experiences? What's going on?
Click to expand...
Click to collapse
Use system app remover
Flashed Oreo on two LG G5
One got no bloatware and one came with Vodafone and Orange app
The one without bloatware has the Software Version: V30a-EUR-XX
and the one with bloatware has the Software Version: V30a-214-07
I used the same files for flashing
But the bad thing is on both phones the light doesn't work?!
Someone with the same issue?
---------- Post added at 01:27 AM ---------- Previous post was at 01:21 AM ----------
VortexHD said:
Why does it come with the Vodafone app?
Click to expand...
Click to collapse
You don't have software version: V30a-EUR-XX right?
Works the light for you?

Categories

Resources