OTA zip (Qualcomm) retail 3.3.2018 "Blur_Version.26.11.27.owens.retail.en.US"
Hello everyone. I saw that there was an update pending on my Moto E4 Plus today so I DLed it and put it into OneDrive. I don't have much time available to do much with it for now but in case anyone else can do something with it, you can DL it HERE.
Chad The Pathfinder said:
Hello everyone. I saw that there was an update pending on my Moto E4 Plus today so I DLed it and put it into OneDrive. I don't have much time available to do much with it for now but in case anyone else can do something with it, you can DL it HERE.
Click to expand...
Click to collapse
Thanks, @Chad The Pathfinder. Good to see you here.
I'm on boost mobile e4 plus stock but rooted. Is this zip for twrp flashing to bring rooted stock versions up to date?
shezzy83 said:
I'm on boost mobile e4 plus stock but rooted. Is this zip for twrp flashing to bring rooted stock versions up to date?
Click to expand...
Click to collapse
It is for the retail XT1775 only. It's an official OTA update.
---------- Post added at 06:21 PM ---------- Previous post was at 05:40 PM ----------
Chad The Pathfinder said:
Hello everyone. I saw that there was an update pending on my Moto E4 Plus today so I DLed it and put it into OneDrive. I don't have much time available to do much with it for now but in case anyone else can do something with it, you can DL it HERE.
Click to expand...
Click to collapse
I can probably make this work to flash with TWRP, but you'll need to have your system, oem and boot.img original stock before flashing. If anyone is willing to test it for me, I will modify the ota zip when I have a chance. I have the Boost XT1766 so I can't test it myself. Let me know if anyone is willing to test it because if not, I won't waste my time modifying the ota.
Sent from my Moto E (4) Plus using XDA Labs
I'm willing to try it. I'm a little confused about the requirements you mentioned though. I'm on stock but with a few modifications I've made here and there. Would I need to uninstall Magisk?
Chad The Pathfinder said:
I'm willing to try it. I'm a little confused about the requirements you mentioned though. I'm on stock but with a few modifications I've made here and there. Would I need to uninstall Magisk?
Click to expand...
Click to collapse
If you look inside the ota zip, there are patches for the boot.img, system.img, oem.img, modem.img, etc. If you don't have the original stock versions of these it may fail to install properly and will likely cause problems. Hence the reason for the asserts in the OTA zip to check for the proper unmodified versions of these. If I had the XT1775 I would just flash stock firmware and update officially then pull the imgs, make an updated stock ROM with the system and boot, and make an make a twrp flashable ota zip with the other modem, fsg and oem.imgs. So, you basically have to do the same as if you were going to update officially minus reflashing stock recovery. You almost might as well just flash your latest stock firmware and take the ota update, then pull the modem, fsg and oem and make a system and boot backup with twrp which I can make an updated ROM and twrp flashable ota for others to update without that hassle. Your choice. I asked another user to provide me with a backup after they updated, but they had to go somewhere for a few days and said they would when they returned. I could give you a stock ROM flashable so you don't have to flash firmware with fastboot. I already have one made, I just haven't uploaded and posted it yet.
Sent from my Moto E (4) Plus using XDA Labs
Goose03 said:
If you look inside the ota zip, there are patches for the boot.img, system.img, oem.img, modem.img, etc. If you don't have the original stock versions of these it may fail to install properly and will likely cause problems. Hence the reason for the asserts in the OTA zip to check for the proper unmodified versions of these. If I had the XT1775 I would just flash stock firmware and update officially then pull the imgs, make an updated stock ROM with the system and boot, and make an make a twrp flashable ota zip with the other modem, fsg and oem.imgs. So, you basically have to do the same as if you were going to update officially minus reflashing stock recovery. You almost might as well just flash your latest stock firmware and take the ota update, then pull the modem, fsg and oem and make a system and boot backup with twrp which I can make an updated ROM and twrp flashable ota for others to update without that hassle. Your choice. I asked another user to provide me with a backup after they updated, but they had to go somewhere for a few days and said they would when they returned. I could give you a stock ROM flashable so you don't have to flash firmware with fastboot. I already have one made, I just haven't uploaded and posted it yet.
Sent from my Moto E (4) Plus using XDA Labs
Click to expand...
Click to collapse
Sure. If you want to send me the flashable you have I'll do that tonight and see what happens.
Chad The Pathfinder said:
Sure. If you want to send me the flashable you have I'll do that tonight and see what happens.
Click to expand...
Click to collapse
I'll have to modify the ota zip for you first so you can flash it after the stock ROM. As soon as I have a chance to, I'll upload that and the stock ROM zip for you. You didn't modify your oem partition at all did you? If so, I'll give you a flashable oem zip to restore that back the way it was also. Just make sure you have stock firmware ready to flash with fastboot in case something doesn't go right. Most of the ota is modem related, no bootloader patches, so it should work fine and hard bricking shouldn't be a concern.
Sent from my Moto E (4) Plus using XDA Labs
Goose03 said:
I'll have to modify the ota zip for you first so you can flash it after the stock ROM. As soon as I have a chance to, I'll upload that and the stock ROM zip for you. You didn't modify your oem partition at all did you? If so, I'll give you a flashable oem zip to restore that back the way it was also. Just make sure you have stock firmware ready to flash with fastboot in case something doesn't go right. Most of the ota is modem related, no bootloader patches, so it should work fine and hard bricking shouldn't be a concern.
Sent from my Moto E (4) Plus using XDA Labs
Click to expand...
Click to collapse
I did not modify the oem partition. I've just made small changes like changed the boot animation, splash screen and some other things like that. Nothing major. have attempted to make a deodex version with a couple of different kitchens to make some other changes but haven't had enough time to really get into anything.
Chad The Pathfinder said:
I did not modify the oem partition. I've just made small changes like changed the boot animation, splash screen and some other things like that. Nothing major. have attempted to make a deodex version with a couple of different kitchens to make some other changes but haven't had enough time to really get into anything.
Click to expand...
Click to collapse
I'm uploading the ROM now. I just got done modifying the ota zip and I'll give you links as soon as they're done uploading. I made a deodexed Sprint variant version. Was planning on deodexing the retail version also. I may as well wait for the newer version though. The trick is, you need to deodexed the oem apps and framework also or it won't boot.
Sent from my Moto E (4) Plus using XDA Labs
Thanks. I'm in town right now. I'll check when I get home and flash if its ready. If all goes well, you want me to send you a twrp backup of boot and system only right?
Chad The Pathfinder said:
Thanks. I'm in town right now. I'll check when I get home and flash if its ready. If all goes well, you want me to send you a twrp backup of boot and system only right?
Click to expand...
Click to collapse
Yes. It'll be a little while, uploads are going really slow and keep failing on AFH. I had it almost uploaded twice and it keeps failing.
Sent from my Moto E (4) Plus using XDA Labs
I couldn't even log into AFH earlier. That's why I used OneDrive in the op.
Chad The Pathfinder said:
I couldn't even log into AFH earlier. That's why I used OneDrive in the op.
Click to expand...
Click to collapse
I have been having issues uploading to AFH too. Man, I wish they would finally get this fixed.
Chad The Pathfinder said:
I couldn't even log into AFH earlier. That's why I used OneDrive in the op.
Click to expand...
Click to collapse
Finally got it
ROM: https://www.androidfilehost.com/?fid=746010030569959248
OTA:
So, here's what I want you to do.
1. Make a backup before you do anything.
2. Flash a Magisk uninstaller.
3. Flash the ROM. (if it should fail to flash, please get a recovery log so I can see exactly what failed.)
4. Flash the OTA zip. (again, if it should fail to flash, please get a recovery log so I can see exactly what failed.)
5. If everything flashes ok, reboot recovery to make sure you don't lose twrp.
6. Make a system backup.
7. Use fastboot to pull the boot.img, modem.img, fsg.mbn, and the oem.img.
Edit: actually, if you could pull everything you see in a stock firmware package and pull them so they have the same name and file extension, that would be great.
I'll be working until about 8 tonight. (3.5.18) I'll work on it tonight and let you know what happens.
Edit: I managed to get the "Blur_Version.26.11.27.owens.retail.en.US--XT1775_TWRP_flashable" down loaded but the other was taking too long and failed a couple of times. I will try again when I can.
so glad you guys are working on this My daughter and her moms xt1775 just popped the update message and im not "allowed" to work on them too often so i cant experiment with you. So a twrp flashable update would be great if i dont have to unroot reroot stock.img etc etc it will be a painless (for me) update.
A Sort-of Related Question
I installed the update by using RSD Lite to go back to stock, taking the update as an OTA, then reflashing TWRP and Magisk. All was fine, until I tried to restore a back up. Which failed, unable to mount System. Thereafter, all reboots take me to Bootloader. I can't use RSD Lite again, as I have updated to a later version. (Believe me, I have tried multiple times!) I tried flashing the two zips, but I fail at the OTA. I was able to load Lineage, which works, but still reboots to Bootloader, then to the ROm.
I have tried fastboot oem fb_mode_clear via both ADB and TWRP Terminal but that fails as well.
Any thoughts on clearing this?
NEVER MIND - Tried a different PC and the mode clear command worked! Whew! The good news is that is something that might be worth trying if you get stuck.
koop1955 said:
I installed the update by using RSD Lite to go back to stock, taking the update as an OTA, then reflashing TWRP and Magisk. All was fine, until I tried to restore a back up. Which failed, unable to mount System. Thereafter, all reboots take me to Bootloader. I can't use RSD Lite again, as I have updated to a later version. (Believe me, I have tried multiple times!) I tried flashing the two zips, but I fail at the OTA. I was able to load Lineage, which works, but still reboots to Bootloader, then to the ROm.
I have tried fastboot oem fb_mode_clear via both ADB and TWRP Terminal but that fails as well.
Any thoughts on clearing this?
NEVER MIND - Tried a different PC and the mode clear command worked! Whew! The good news is that is something that might be worth trying if you get stuck.
Click to expand...
Click to collapse
The modified ota zip I posted failed to flash? Did you happen to get a recovery log?
Sent from my Moto E (4) Plus using XDA Labs
Goose03 said:
The modified ota zip I posted failed to flash? Did you happen to get a recovery log?
Sent from my Moto E (4) Plus using XDA Labs
Click to expand...
Click to collapse
Of course, sent to you via PM.
I don't think that it is a quality of your zip, I think it is related to my earlier attempt at installing the OTA itself.
Related
Hi,
I'm using only stock rom, rooted and with xposed mods on my Nexus devices. Because of trying some things out, I want to have a stock rom update.zip from the latest Factory Image on my device to have the security to flash it back to stock without a computer.
So, I've managed with some help this update.zip. It's absolutely pure stock. Not rooted, not deodexed or anything else (to root, there is a link below)
I think, some of you are thinking the same and so I want to share this update zip. I hope you have fun with it.
It works with CWM and TWRP Recovery!
Romversion
KOT49H Hammerhead
Tweaks / Changes
Nothing
Download
Stock ROM KOT49H Hammerhead
MD5 Checksum: 864626c54510b0c0eb3dac8a23e66f45
Thanks to
vetzki
caho
for their kindly help!
Infos
- You want root, you only have to flash, this file here, too: SuperSU Download
- the install process is slow. Please wait, it really installs. It takes about 5 Minutes. If someone has the ability to show me how to make it faster: Please, please!!!
Have Fun!
So, do you recommend a full wipe and cache clear when installing this?
Let's say I want to go stock in anticipation of a new update to android. I would go to Recovery (I use twrp), wipe data/erase everything from my previous rom, and then flash update.zip (and supersu at the same time), and I'll be set with stock everything including kernel, etc?
You won't be able to get an update with a rooted rom. Google checks before sending the files that your rom matches the md5
Sent using reversed alien technology...
howard bamber said:
You won't be able to get an update with a rooted rom. Google checks before sending the files that your rom matches the md5
Sent using reversed alien technology...
Click to expand...
Click to collapse
Well, question still stands. I still want to ensure this thing catches kernels and everything else provided I do a full wipe, and I assumed a full wipe is recommended (as with most things on this site). I wanted to get clarification before hand.
xybur said:
Well, question still stands. I still want to ensure this thing catches kernels and everything else provided I do a full wipe, and I assumed a full wipe is recommended (as with most things on this site). I wanted to get clarification before hand.
Click to expand...
Click to collapse
Yes if you want to flash the ROM you should do a full wipe just in case there are any mods left over from the previous ROM/kernel.
What the previous poster was informing you of is that flashing this ROM won't give you the update directly from Google itself. You will need to flash the new update manually as the md5 sum gets checked when they send out updates.
It's nothing to worry about just flash the new update when it comes. Most of the time you can flash the new update before Google would send it out to your phone anyways.
Mo'HAWK said:
Yes if you want to flash the ROM you should do a full wipe just in case there are any mods left over from the previous ROM/kernel.
What the previous poster was informing you of is that flashing this ROM won't give you the update directly from Google itself. You will need to flash the new update manually as the md5 sum gets checked when they send out updates.
It's nothing to worry about just flash the new update when it comes. Most of the time you can flash the new update before Google would send it out to your phone anyways.
Click to expand...
Click to collapse
Gotcha, thanks for the help/clarification.
As far as I know, google send updates to rooted devices, too.
But I don't want to swear
A full wipe is indeed better if you come from another rom.
But with a nandroid backup, you can try.
Sent from my IPhone 7s
howard bamber said:
You won't be able to get an update with a rooted rom. Google checks before sending the files that your rom matches the md5
Click to expand...
Click to collapse
FormelLMS said:
As far as I know, google send updates to rooted devices, too.
But I don't want to swear
Click to expand...
Click to collapse
Hello,
All is here about OTA and root: [INFO] Nexus 5 OTA Help-Desk...
Thanks!
So it's right.
Flash this rom, don't delete or change a file. No new Kernel and you can receive the update.
Sent from my IPhone 7s
howard bamber said:
You won't be able to get an update with a rooted rom. Google checks before sending the files that your rom matches the md5
Sent using reversed alien technology...
Click to expand...
Click to collapse
very wrong. first off, Google does not check. secondly, you can get an update while having root, as long as you do not change system files. why do you think we get so many "i updated ota and lost root" threads?
I'm just curious, I thought that the recovery was supposed to be stock to receive ota updates? Tia
Sent from my Nexus 5 using JellyBombed Tapatalk 2
Would you care to share how did you make flashable stock room?
Sent from my Nexus 5 using Tapatalk
Hey,
this thread here shows the most:
http://forum.xda-developers.com/showthread.php?t=2285831
You have to know, that you need the extracted system.img as the system folder in your update.zip.
Then you need the boot.img unextracted.
This is a all easy. A bit complicated is the meta-inf folder.
I've used this folder from other aosp roms.
I have to learn that now, too.
Sent from my IPhone 7s
Download link not working????
Sent from my Nexus 5 using XDA Free mobile app
This CWM/TWRP flashable zip is 4.4.4 from my dump of 212.44.26.ghost_att.ATT.en.US (ATT xt1058).
The stock ATT 4.4.4 kernel is within the zip and must be flashed manually.
Safestrap and root are 'baked in', but the rom is otherwise stock.
I am using the modem from 4.4.2 without issue, and I plan to create a new zip when the official sbf is available.
The instructions below are mostly for rooted, locked ATT phones using safestrap.
This zip does not alter your bootloader.
I was able to upgrade from 4.4.2 without a wipe/factory reset.
This rom installs Safestrap. (I welcome exact instructions on removing this from the rom.)
WARNING: I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE.
Instructions for ATT locked phones:
If you can still get permanent root (pre 4.4.2 bootloader), then you can use safestrap to install this zip of ATT 4.4.4 and get root again.
Prerequisite:
Rootable Moto x (not temporary root)
Have fastboot (motorola version for this phone) and PC drivers installed and working
BACKUP ANYTHING YOU DON'T WANT TO LOSE.
Instructions:
root (thanks jcase)
install safestrap (thanks Hashcode and Team Win)
Make a nandroid and copy it off the phone!?
download zip to sdcard (motox-444-212.44.26.ghost_att-from-dump-ss.zip, link below)
extract boot.img to the fastboot directory of your PC
enter safestrap recovery (twrp) and activate the stock-slot
twrp: flash rom (motox-444-212.44.26.ghost_att-from-dump-ss.zip) to the stock-slot
twrp: reboot to bootloader (home -> reboot -> bootloader)
on pc: execute fastboot commands (below) then power on normally.
install supersu (thanks chainfire) from play store
Fastboot command to flash the kernel:
Code:
fastboot flash boot boot.img
Fastboot command for locked phones not using MotoWPNoMo with pre 4.4 bootloaders:
Code:
fastboot flash recovery boot.img
Thanks to touchpro247 for making the raw OTA available. Also thanks to iKrYpToNiTe for his safestrap selinux metadata code.
Download:
motox-444-212.44.26.ghost_att-from-dump-ss.zip: http://www.androidfilehost.com/?fid=23622183712458373
anyone try this one yet?
Installed this on my DE. Works perfectly. I actually have better reception. I'm on ATT btw.
Thanks a lot!
Sent from my XT1058 using XDA Free mobile app
bahhh now all I need is one from VZW
Thanks! This seems to work fine for my unlocked Brazil XT1058 using TWRP. The only thing is now that whenever I start the phone there's a 2-3 second screen saying Safestrap disabled (I've never installed Safestrap). Is there a logo flash that will remove this?
would this work on 1053 on att or nah
Sent from my XT1053 using XDA Free mobile app
goonigoogoo said:
Thanks! This seems to work fine for my unlocked Brazil XT1058 using TWRP. The only thing is now that whenever I start the phone there's a 2-3 second screen saying Safestrap disabled (I've never installed Safestrap). Is there a logo flash that will remove this?
Click to expand...
Click to collapse
Because this came from my /system dump, it has safestrap there. I'm not sure of the easiest way to perfectly remove it, and I welcome input on the issue.
I'll update the op.
hey guys i have a 1053 rooted i am a noob sorry how can i get this to work for me
g4ess said:
would this work on 1053 on att or nah
Sent from my XT1053 using XDA Free mobile app
Click to expand...
Click to collapse
Yep. Works well. I now have visual voicemail.
Sent from my XT1058 using XDA Free mobile app
can't get it to install how to u manually flash kernel
Sent from my XT1053 using XDA Free mobile app
Weapondrift said:
bahhh now all I need is one from VZW
Click to expand...
Click to collapse
This one doesn't work? http://forum.xda-developers.com/moto-x/development/rom-stock-rooted-vzw-212-55-26-t2829123
Has anyone seen if Faux's kernel will work? I'm waiting for my phone to charge before I flash. I'll report whether or not if no one else does.
Edit: So far, it's working great on my 1053 DE with Faux's latest kernel on AT&T.
nice
Thanks Ctrl-Freak for this. I appreciate you putting it together. I just upgraded from 4.4.2 to 4.4.4.
C:\>adb shell getprop ro.boot.write_protect
0
Click to expand...
Click to collapse
Sorry if this question is aggravating but if I flash this on my rooted XT1053 will it wipe my internal? Just trying to be sure, never flashed anything carrier specific. I flash and reboot right? Or do I also need the kernel? I read the OP but I'm wondering if I do all of that and or need safestrap.
Edit: I think I got it.
I did this update as instructed on my AT&T, locked bootloader XT1058 but I skipped the fastboot commands entirely. Installed under stock slot with root from 4.2 android and Safestrap. Went through like a charm. Still have root, had to reboot to write protect off mode and install Xposed again, but otherwise everything is as it was...except that I'm on 4.4.4 now! I didn't even lose my original bootloader (the globe one that looks so sexy) that I had to manually install after their damn PlayStore update replaced. Not sure if this will stick for others that haven't done that already.Thanks!!!
---------- Post added at 02:17 PM ---------- Previous post was at 02:14 PM ----------
Apollo_316 said:
I did this update as instructed on my AT&T, locked bootloader XT1058 but I skipped the fastboot commands entirely. Installed under stock slot with root from 4.2 android and Safestrap. Went through like a charm. Still have root, had to reboot to write protect off mode and install Xposed again, but otherwise everything is as it was...except that I'm on 4.4.4 now! I didn't even lose my original bootloader (the globe one that looks so sexy) that I had to manually install after their damn PlayStore update replaced. Not sure if this will stick for others that haven't done that already.Thanks!!!
Click to expand...
Click to collapse
I should clarify. I had the old root from 4.2 that was on the phone when I purchased it. Updating to 4.4.4 was coming from 4.4.2 previously.
Apollo_316 said:
I did this update as instructed on my AT&T, locked bootloader XT1058 but I skipped the fastboot commands entirely.
...
Click to expand...
Click to collapse
If possible, I recommend that you go ahead with the official att 4.4.4 kernel packaged within the zip (boot.img via fastboot). It is likely that this latest kernel includes important fixes. (For example, the Android OS battery issue seems fixed.)
(I skipped the modem because I don't know how to package the modem partition into a flashable image.)
Ctrl-Freak said:
If possible, I recommend that you go ahead with the official att 4.4.4 kernel packaged within the zip (boot.img via fastboot). It is likely that this latest kernel includes important fixes. (For example, the Android OS battery issue seems fixed.)
(I skipped the modem because I don't know how to package the modem partition into a flashable image.)
Click to expand...
Click to collapse
I'll have to agree with you on the 4.4.4 kernal and the android is bug. I was using Faux's 4.4.3 kernal with this ROM and still had the os bug. Now, it's all gone after I manually flashed the new kernel.
iSecks said:
This one doesn't work? http://forum.xda-developers.com/moto-x/development/rom-stock-rooted-vzw-212-55-26-t2829123
Click to expand...
Click to collapse
nope. That didn't do anything
Ctrl-Freak said:
If possible, I recommend that you go ahead with the official att 4.4.4 kernel packaged within the zip (boot.img via fastboot). It is likely that this latest kernel includes important fixes. (For example, the Android OS battery issue seems fixed.)
(I skipped the modem because I don't know how to package the modem partition into a flashable image.)
Click to expand...
Click to collapse
beefgoat said:
I'll have to agree with you on the 4.4.4 kernal and the android is bug. I was using Faux's 4.4.3 kernal with this ROM and still had the os bug. Now, it's all gone after I manually flashed the new kernel.
Click to expand...
Click to collapse
Ctrl-Freak said:
If possible, I recommend that you go ahead with the official att 4.4.4 kernel packaged within the zip (boot.img via fastboot). It is likely that this latest kernel includes important fixes. (For example, the Android OS battery issue seems fixed.)
(I skipped the modem because I don't know how to package the modem partition into a flashable image.)
Click to expand...
Click to collapse
You were quite right. I'm having battery issues (now) and my WiFi/Bluetooth won't turn on at all, even in safe mode. Was getting 52 hours consistently on battery, now I'm down to 36 hours tops! Phone started being 'awake' while the screen was off. I went back and flashed the boot, all good now. I'll report back on the battery issue. Thank you guys for setting me strait! :highfive:
Possible anyone knows how to disable the annoying OTA updates permanently? Remedied for now, being on 4.4.4, but I was trying to avoid 4.4.4 for now and the update notification that I couldn't kill, greenify, stop on boot, etc., is what drove me to this post. I'd love to turn these off and upgrade at my leisure in the future.
This is what I've been waiting for. Android OS is where it's supposed to be. Thank you Ctrl Freak for the upload.
OK, the pic didn't upload.
Hey! I am having problem flashing the OTA zip (LRX21L-->LRX21R). It simply wont let me sideload the .zip file because my device can't be found after i reboot to the bootloader. Can anyone please help me with this?
My device has an unlocked bootloader and is rooted using Chainfires first root for the nexus 9. Thanks in advance!
acceh said:
Hey! I am having problem flashing the OTA zip (LRX21L-->LRX21R). It simply wont let me sideload the .zip file because my device can't be found after i reboot to the bootloader. Can anyone please help me with this?
My device has an unlocked bootloader and is rooted using Chainfires first root for the nexus 9. Thanks in advance!
Click to expand...
Click to collapse
Flash the 21l boot.img in fastboot. Then try the ota. Chain fire modified the boot image and that's why it isn't working
Sent from my Nexus 9 using XDA Free mobile app
Where do i get that 21l img file? And how to flash if fastboot is not recognized? I have twrp installed, could someone provide a flashable zip? Thanks
GeneralSmart said:
Where do i get that 21l img file? And how to flash if fastboot is not recognized? I have twrp installed, could someone provide a flashable zip? Thanks
Click to expand...
Click to collapse
Yeah...., I could go with this too, actually. I had pretty much everything from the board loaded. Including @Chainfire 's recov. I then later attempted to update the *poluza rom parts. It was failing any which way I tried in or out of twrp. Unfortunately, I am not much of a fastboot user, nor twrp.
I thought that maybe it had something to do with this updated vendor img. By the time I was done I had reformatted several times and started from scratch not leaving out steps. As far as I know. With just these images and no device trees nor a proper updater script, there is no way to tell really.
Currently and for a few days, it's been down to bare metal, and only a fastboot to look at. lol
I can't even seem to make a new factory image flash.
Never since my first android have I been this lost frankly.....
Maybe they have them now, I will look but it would also be helpful if the guys used a bit of ......'if.....then......' in their 'OP's'
"If you are using the included recovery, then......"
"If you are using this recovery then do......."
"If you wanted to use @Chainfire s recovery, then simply paste it......."
etc.
Could anyone possibly help and provide a way to update??? I unlocked bootloader and I am rooted, but now I want to have a working way to update....ANY HELP??
I found a solution: check out the video and download his tool...he did a great job there and it worked like a charm for me!!!!!!!!!!!!!!!!!!!!!!!!!!
https://www.youtube.com/watch?v=bsU1r6wKMiA
its the tool on the second link under the video...around 750 MB sized
https://developers.google.com/android/nexus/images?hl=en
Wow nice !!!
Let's Rock!
Can't wait for pure nexus to update to N
Sent from my Nexus 6P using Tapatalk
YES!
Is it possible to flash the factory image using flashfire?
Im currently using this ROM (Stock+Nougat-NRD90M Debloated-Prerooted-Odex-Busybox-Fast & Stable).
Vegeta700 said:
Is it possible to flash the factory image using flashfire?
Im currently using this ROM (Stock+Nougat-NRD90M Debloated-Prerooted-Odex-Busybox-Fast & Stable).
Click to expand...
Click to collapse
I only flash via fastboot and when going between versions I'd personally want to do a fully clean flash. Mind you I reverted to MM after trying N for a couple days, but again, I'd never flash a full factory image via Flashfire.
Vegeta700 said:
Is it possible to flash the factory image using flashfire?
Im currently using this ROM (Stock+Nougat-NRD90M Debloated-Prerooted-Odex-Busybox-Fast & Stable).
Click to expand...
Click to collapse
Unless a lot of users have certified that flashing via dlash fire works, I would recommend a clean flash via fastboot. This way you are flashing the images the most direct way possible. Doing this will also reduce possible entry points for issues.
First person to find an .mbn file in the boot.img or bootloader.img gets SO much cred.
Oh my .. Time to flashing silently
Is there a list of apps that currently don't work (or do work) with 7.0? I'm trying to switch over but there's a couple core apps that I need to know will work fine.
kaslopis said:
Is there a list of apps that currently don't work (or do work) with 7.0? I'm trying to switch over but there's a couple core apps that I need to know will work fine.
Click to expand...
Click to collapse
There's a thread called "Android N: What doesnt work" here in general
david279 said:
There's a thread called "Android N: What doesnt work" here in general
Click to expand...
Click to collapse
Most of the apps on that list that I use did not have the stated issues... None of them did.. I'm not sure if that list is up to date.
You're welcome.
I just finished flashing back to 6.0.1 and getting everything set up.
Of course now it gets released...
E30Nova said:
You're welcome.
I just finished flashing back to 6.0.1 and getting everything set up.
Of course now it gets released...
Click to expand...
Click to collapse
You aren't alone. Went back a day ago myself.
Sent from my Nexus 6P using Tapatalk
From what I've seen, this version isn't all that superb. Being on 6 isn't so bad
I've honestly had zero issues with the factory image for N. I wiped everything and clean flashed the image flat. Once I restored all my apps (around 80), so far it seems very smooth. No issues with lag in either the system or the fingerprint scanner.
I keep getting an error about not being able to find systsem.img in its package.. In thought they fixed this in the flash all script in 5.0 for factory images?
Soured Lie said:
I keep getting an error about not being able to find systsem.img in its package.. In thought they fixed this in the flash all script in 5.0 for factory images?
Click to expand...
Click to collapse
Flash-all is still broken afaik, better flash the individual img`s in fastboot.
Hey y'all,
Sorry to bother here. I looked around but couldn't find anything. I'm running NRD90M on my phone. I install TWRP and I rooted my 6P + unlocked bootloader. However I just downloaded the full image on google NRD90U. I'd like to put back my phone to stock with this new image and be able to just keep it stock and receive OTA. Can someone help me out or giving me a link where there's a tutorial. I already downloaded Fastboot/ADB and installed my drivers.
PS: It's find if it wipes everything. I just want it clean.
Thanks!
StangATX
Alright, so long story short I'm running JW's sprint21a software version after following the guides on Frankensteining and rooting the V30. Ever since August 16th I've been getting update messages to update to the newest version from sprint. Sadly, this update isn't available as a zip anywhere to flash via TWRP like I did when I converted from US998 after rooting to LS998 to restore LTE and the sprint bands.
I've been reading a bit and asking question in a few other threads and it would seem the latest US998 version is 20d and coincided with the new LS update as well. I'm wondering if it'd be feasible to flash 20d via TWRP so I can have the newest security update, then flash the sprint modems by themselves from JW's 21a file or not. I'm just wondering how feasible this would be. I'm not entirely sure if flashing a modem from a different (and older) version of the software would work with the newer and different one or not.
If it is feasible, my next question is how I would go about flashing just the modem files. I cracked JW's zip file open and I can see theres a modem.bin file in there. I'm wondering if I could wipe everything else in the zip out and leave that, then flash 20d via TWRP, then the modified zip with only the modem, followed by root,no-verity, and rctd...
Will this idea work, or am I missing something vital either in the procedure or is the idea itself not possible? Any thoughts or feedback would be greatly appreciated!
Sure you can
Go here
https://forum.xda-developers.com/lg-v30/how-to/making-modem-bin-flashables-twrp-t3794435
Post #5 grab modem.bin rename to .img(from .bin) flash as image in TWRP
First flash rom,magisk or what ever else you like then boot once you set up go back to TWRP flash modem reboot and ad apns reboot and profit
See
ricohz said:
Go here
https://forum.xda-developers.com/lg-v30/how-to/making-modem-bin-flashables-twrp-t3794435
Post #5 grab modem.bin rename to .img(from .bin) flash as image in TWRP
First flash rom,magisk or what ever else you like then boot once you set up go back to TWRP flash modem reboot and ad apns reboot and profit
See
Click to expand...
Click to collapse
How do you have that nice black theme? WANT!
Sent from my LG-LS998 using Tapatalk
ricohz said:
Go here
https://forum.xda-developers.com/lg-v30/how-to/making-modem-bin-flashables-twrp-t3794435
Post #5 grab modem.bin rename to .img(from .bin) flash as image in TWRP
First flash rom,magisk or what ever else you like then boot once you set up go back to TWRP flash modem reboot and ad apns reboot and profit
See
Click to expand...
Click to collapse
ahh ricohz you're my hero!! I'm goign to download these and give it a shot in the next couple of days when I have some time off from work to really toy around with it. Thank you so much!
JesseAaronSafir said:
How do you have that nice black theme? WANT!
Link fixed
Sent from my LG-LS998 using Tapatalk
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=com.lge.theme.pixterial
One I have
https://play.google.com/store/apps/details?id=com.lge.wsdeveloper.g7black
Free one that's almost the same
@txag2011
No problem
ricohz said:
https://play.google.com/store/apps/details?id=com.lge.theme.pixteria
One I have
https://play.google.com/store/apps/details?id=com.lge.wsdeveloper.g7black
Free one that's almost the same
@txag2011
No problem
Click to expand...
Click to collapse
I don't find that "pixteria" one in the play store. The link seems broken. I do see the 2nd one, which is free and I installed it.
These don't have anything to do with substratum, right? I've played around with substratum some but have run into a situation where everything goes black and you can't navigate the screen anymore so I have to revert with TWRP. I think it has to do with themeing SystemUI but I'm not sure. I know that substratum has an addon that you can use if you don't have root but it requires hooking up to a computer. As I have root, I was thinking I should be able to use substratum without that addon and without hooking up to a computer. Anyway, I haven't had great luck with it so far.
It looks like this "G7 Black Theme for LG V30 & G6 Oreo" from WSTeams uses the native theming engine of LG V30 instead. I see that it themed the keyboard as well. NICE!! THANKS FOR THIS!!
ricohz said:
Go here
https://forum.xda-developers.com/lg-v30/how-to/making-modem-bin-flashables-twrp-t3794435
Post #5 grab modem.bin rename to .img(from .bin) flash as image in TWRP
First flash rom,magisk or what ever else you like then boot once you set up go back to TWRP flash modem reboot and ad apns reboot and profit
See
Click to expand...
Click to collapse
Hi, when I was trying to flash this modem.img it was asking me how I want to flash, recovery, boot, system and LAF/ DL, I chooses system and now it wont boot up, I didn't have option for Modem Im using this TWRP-3.2.3-6-IntSD.img so which is the best option for me to choose to install modem.img
zfk110 said:
Hi, when I was trying to flash this modem.img it was asking me how I want to flash, recovery, boot, system and LAF/ DL, I chooses system and now it wont boot up, I didn't have option for Modem Im using this TWRP-3.2.3-6-IntSD.img so which is the best option for me to choose to install modem.img
Click to expand...
Click to collapse
@seadersn, he can grab an older version of your TWRP and flash that, can't he?
ChazzMatt said:
@seadersn, he can grab an older version of your TWRP and flash that, can't he?
Click to expand...
Click to collapse
Yes that what I did I went to older TWRP and it had a option for Modem, now my phone's settings looks like attach zipped file
zfk110 said:
Yes that what I did I went to older TWRP and it had a option for Modem, now my phone's settings looks like attach zipped file
Click to expand...
Click to collapse
What modem image did you flash? For another LG V30/V30+ variant?
Strange your software version now says US998 21A with May 2018 security patch. That SHOULD BE 20A. There's no such thing as US998 21A...
You ONLY flashed modem image using the older TWRP?
@seadersn?
ChazzMatt said:
What modem image did you flash? For another LG V30/V30+ variant?
Strange your software version now says US998 21A with May 2018 security patch. That SHOULD BE 20A. There's no such thing as US998 21A...
You ONLY flashed modem image using the older TWRP?
@seadersn?
Click to expand...
Click to collapse
I Frankensteind my LS998 to US998 using your method then went back to LS998 using this
Sprint 21a(may security patch)
https://forum.xda-developers.com/lg-v30/how-to/us998-to-ls998-sprint-lte-root-t3802310
I haven't try to activated the phone with Sprint to see if its going to work, I thought let me try to get the correct modem flashed first
this is the modem.bin I used, I was told I have to change bin to img and then use twrp to flash it
https://forum.xda-developers.com/showpost.php?p=76603286&postcount=5
ChazzMatt said:
What modem image did you flash? For another LG V30/V30+ variant?
Strange your software version now says US998 21A with May 2018 security patch. That SHOULD BE 20A. There's no such thing as US998 21A...
You ONLY flashed modem image using the older TWRP?
@seadersn?
Click to expand...
Click to collapse
maybe main firmware differs from used system image. something got mixed up, jep. but to be honest, i can't fully imagine what happened there, really it's modem.image flashing to system. fw version is stored in modem image too, but.. i don't know
ChazzMatt said:
@seadersn, he can grab an older version of your TWRP and flash that, can't he?
Click to expand...
Click to collapse
newest 6a has correct modem partition handling added back, better use this one.
zfk110 said:
Hi, when I was trying to flash this modem.img it was asking me how I want to flash, recovery, boot, system and LAF/ DL, I chooses system and now it wont boot up, I didn't have option for Modem Im using this TWRP-3.2.3-6-IntSD.img so which is the best option for me to choose to install modem.img
Click to expand...
Click to collapse
first install new recovery 3.2.3-6a, then reboot to recovery and wipe cache. a system.img fitting your current main firmware should fix this. format system and flash the system image. the appropriate (or wished) modem can then be flashed via image flashing function to modem partition.
sry, was busy the last few days will not get really better because of christmas, bdays, broken car lol... but every two to three days i'm looking in xda there'll be a little update to twrp too, because some op partitions are available now. there's just an op image flashing function added (and some gatekeeper files for lockscreen settings tests), could be possible that this comes this weekend.