Related
Guys, I need some advice.
If I'm rooted and I solely depend on Xposed for tweaks (that means I don't modify system files), will my moto g be fit for OTA updates? like I read here somewhere that if you're rooted and no system files were tweaked, OTA updates won't be a problem.
Thank you so much. New XT1033 Moto G owner here running Stock 4.4.2 rom. Still on the fence when it comes to rooting tbh. Also, I haven't been able to find changelogs for the 4.4.4 update. Thank you!
@OldYellowBricks
The short answer
If you have stock recovery and have not modified any system files, you will be able to OTA without a problem. Did it myself from 4.4.2 to 4.4.3.
The long answer
Here is how updating works:
The updater has a list of files that are going to be modified by the update. It first calculates the checksum of every file that is going to be modified and compares it to the cheksum it has on a list. If there is a checksum mismatch, the update process is aborted. If all the checksums agree, the updater starts patching the files.
Now, since the updater doesn´t expect you to have xposed and supersu on your system partition, it doesn´t look for them and it does not care about them - it just patches the files on the list. That´s all.
knizmi said:
@OldYellowBricks
The short answer
If you have stock recovery and have not modified any system files, you will be able to OTA without a problem. Did it myself from 4.4.2 to 4.4.3.
The long answer
Here is how updating works:
The updater has a list of files that are going to be modified by the update. It first calculates the checksum of every file that is going to be modified and compares it to the cheksum it has on a list. If there is a checksum mismatch, the update process is aborted. If all the checksums agree, the updater starts patching the files.
Now, since the updater doesn´t expect you to have xposed and supersu on your system partition, it doesn´t look for them and it does not care about them - it just patches the files on the list. That´s all.
Click to expand...
Click to collapse
Okay now I get! Thank you so much. I would like to keep to stock ROM andbrun some xposed modules for stability and to be honest, I'm pretty reluctantbto flash ROMs on this dual sim phone cause support is pretty wonky from what I've read (no disrespect to the developers!)
Hello,
I'm fairly inexperienced with this since this is my first Android device I've rooted manually (I have a Nexus 7 2012 I rooted via Nexus Root Toolkit). I have TWRP recovery v2.8.5.0 installed as well as SU and Busybox. Now I'm trying to install some Custom ROMS.
I've tried installing crDroid and Cyanogenmod 12.1, both of which have something along the lines of this error: (I copied and pasted part of the log, if you need the full log, just let me know) (this was when I tried installing crdroid, but Cyanogenmod had the exact same error minus the fact that the zip filename was different)
script aborted: This package is for device: xt1505,xt1506,otus_umts,otus_umtsds,otus,otus_ds; this device is surnia.
This package is for device: xt1505,xt1506,otus_umts,otus_umtsds,otus,otus_ds; this device is surnia.
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/external_sd/crdroid-5.1.1-20150912-otus.zip'
Error flashing zip '/external_sd/crdroid-5.1.1-20150912-otus.zip'
So far many google searches have brought nothing. My phone's model number is XT1526 and the code name is "otus", yet it appears that it is being identified as "surnia". Am I doing anything wrong? I'm wiping Data, System, Cache, and Dalvik Cache, and I've already created an update.zip in Titanium Backup as well as a Nandroid backup in TWRP recovery. As far as I know, this is the latest TWRP I can find, as the manager wants me to downgrade to 2.7.x.x, which I tried, only to have to reflash 2.8.5.0. And I'm getting the CM ROM download from CM's official website and I got the crDroid download from this website's Moto E 2015 ROMS forum. Can I?
A. Change the ID of my device to match the ID the ROM wants?
B. If the ROMS are the issue (I'm aware crDroid is based off of Cyanogenmod, so if CM doesnt work, maybe crDroid acts the same way), could I be pointed towards a few other ROMS that are close to Cyanogenmod or are just very useful to use?
C. Replace TWRP with CWM and try installing it that way?
Thank you so much in advance, I've tried every Google search possible and it seems hopeless. Hopefully these forums can help!
Fallonite said:
Hello,
I'm fairly inexperienced with this since this is my first Android device I've rooted manually (I have a Nexus 7 2012 I rooted via Nexus Root Toolkit). I have TWRP recovery v2.8.5.0 installed as well as SU and Busybox. Now I'm trying to install some Custom ROMS.
I've tried installing crDroid and Cyanogenmod 12.1, both of which have something along the lines of this error: (I copied and pasted part of the log, if you need the full log, just let me know) (this was when I tried installing crdroid, but Cyanogenmod had the exact same error minus the fact that the zip filename was different)
script aborted: This package is for device: xt1505,xt1506,otus_umts,otus_umtsds,otus,otus_ds; this device is surnia.
This package is for device: xt1505,xt1506,otus_umts,otus_umtsds,otus,otus_ds; this device is surnia.
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/external_sd/crdroid-5.1.1-20150912-otus.zip'
Error flashing zip '/external_sd/crdroid-5.1.1-20150912-otus.zip'
So far many google searches have brought nothing. My phone's model number is XT1526 and the code name is "otus", yet it appears that it is being identified as "surnia". Am I doing anything wrong? I'm wiping Data, System, Cache, and Dalvik Cache, and I've already created an update.zip in Titanium Backup as well as a Nandroid backup in TWRP recovery. As far as I know, this is the latest TWRP I can find, as the manager wants me to downgrade to 2.7.x.x, which I tried, only to have to reflash 2.8.5.0. And I'm getting the CM ROM download from CM's official website and I got the crDroid download from this website's Moto E 2015 ROMS forum. Can I?
A. Change the ID of my device to match the ID the ROM wants?
B. If the ROMS are the issue (I'm aware crDroid is based off of Cyanogenmod, so if CM doesnt work, maybe crDroid acts the same way), could I be pointed towards a few other ROMS that are close to Cyanogenmod or are just very useful to use?
C. Replace TWRP with CWM and try installing it that way?
Thank you so much in advance, I've tried every Google search possible and it seems hopeless. Hopefully these forums can help!
Click to expand...
Click to collapse
Hi and thank you for using XDA Assist
You need to be very careful with the variants because there are some variants of the new Moto E and maybe you downloaded the ROMs for a different variant of Moto E. For example this ROM instead is for real for your specified device
Regards
nilac said:
Hi and thank you for using XDA Assist
You need to be very careful with the variants because there are some variants of the new Moto E and maybe you downloaded the ROMs for a different variant of Moto E. For example this ROM instead is for real for your specified device
Regards
Click to expand...
Click to collapse
Hi nilac,
I downloaded the exact rom from the link you gave me, and I had the same error appear. Do you need the whole log? Or is there another solution?
Fallonite said:
Hi nilac,
I downloaded the exact rom from the link you gave me, and I had the same error appear. Do you need the whole log? Or is there another solution?
Click to expand...
Click to collapse
Hi again, well if it's still not working i suggest you then to write it over the Q&A forum of your device, right here:
E 2015 Q&A, Help & Troubleshooting
Good luck!
Hey there, I own a Mi5S Plus with MIUI Stable 9.2.1 (based on Android 7.0).
For a bug that gives me a terrible battery drain (3 hours of screen usage tops) I decided to install Lineage OS 15.1.
I've got last version of TWRP (3.2.1-1), Unlocked bootloader, the phone has ben rooted.
As explained on the official guide:
- Factory reset with TWRP;
- Install *.zip file with last LOS update, positioned in /sdcard/
- Returns ERROR 7, I do exactly as suggested online
so:
- I delete “assert” strings from “updater-script” file and I zip it back up;
Here I have 2 different outcomes:
1) Invalid zip file format (I used both OSX and Win, using both native apps and third party ones);
2) Missing file “updater-binary” even if it is right in the zip.
What if, being the string after “assert” referring to a specific MIUI version, the problem is due to my installed MIUI version? It makes no sense, I know.
Here's what I'm talking about:
ui_print("Target: Xiaomi/natrium/natrium:6.0.1/MXB48T/V8.2.4.0.MBGCNDL:user/release-keys");
What should I do? I've tried them all!!!
I had the same problem installing the AospExtended 5.3 and I solved flashing the 8.1.4 modem.
[OBSOLETE] @yshalsager As of 8.8.16 flashable TWRP non ARB Firmware now available see thread.
[GUIDE] Updating Modem, Bluetooth and DSP! ~~~ Without triggering ARP on WHYRED!
For anyone on customs rom and need to updated the above partitions?
The commands to flash them in fastboot are: -
Code:
fastboot flash modem NON-HLOS.bin
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
pause
I just created a bat file (windows) with the above content.
All I need do in future is download a firmware from here, extract the three files and place the bat file in the same folder, and run it.
^^^ Note I have adb/fastboot setup with a global path in windows.
Haven't tested in operation yet but in theory should work. I'm on 8.7.5 Beta firmware at present and see no need to update until the custom rom in use requires update files.
Above 3 files have been reported safe to flash here (Thanks @aank) , without effecting the bootloader, so not to trigger ARP.
First two files are self explained.
DSP (Digital Signal Processor)
[INFO] ANDROID DEVICE PARTITIONS and FILESYSTEMS
Attached is a sample bat file, just remove the .txt from the end of the file name.
I posted this before in the Everything About Anti Roll-back [Whyred] by @AL_IRAQI , but would probably get lost there.
Edit: - Edited the batch file to include a "pause", in case you double click instead of running in CMD/POWERSHELL window.
Cool, hope it works if i ever need it. Thanks
thx tested it, it works, i am still on anti 3 after updating these 3
does this improve signal reception? when I'm using any custom rom, my signal is really bad, but in MIUI it isn't, it's really great and it's full.
rizdar said:
does this improve signal reception? when I'm using any custom rom, my signal is really bad, but in MIUI it isn't, it's really great and it's full.
Click to expand...
Click to collapse
It may depend on the custom rom your on?
What was your last MIUI firmware?
Updating/downgrading the modem to the working version may help/improve things.
@corkiejp Do you recommend flashing the firmware files from 9.5.19 or the ones from 8.7.26 when moving to a custom rom?
corkiejp said:
It may depend on the custom rom your on?
What was your last MIUI firmware?
Updating/downgrading the modem to the working version may help/improve things.
Click to expand...
Click to collapse
I'm on Arrow OS right now.
But after I do the steps above, it seems like nothings changed.
The signal is still the same.
It's happening on all custom ROMs, is it because my providers?
Edit: I was on 8.7.26 (Masik U 2.2)
@eyebiz
I would stick with whatever firmware your device has at present. It is probably more recent than firmware recommend by custom roms.
There is really no reason to update firmware, if your device is working well with what you have!
If the rom recommends a specific firmware, then you may need to upgrade, but don't downgrade firmware to match.
If I'm flashing firmware, I usually use the version from beta roms, as that is often the more recent firmware.
I only update roms, once a month when security patches included. And patch the firmware at the same time.
@rizdar Your network provider maybe the problem, check your APN settings with the recommend settings of your provider.
The three files mentioned in this thread, may not be alter from one firmware to the next. It is usually the bootloader (which we need to avoid for ARP) that regularly changes.
You could compare files and hashes from different firmware to see if there is changes.
Hi @corkiejp
I've created TWRP flashable .zip with latest stable modem, dsp and bluetooth here :
https://drive.google.com/file/d/1eYys31FFgdxz4GyMFgMiuvoTWwwgER1Y/view?usp=drivesdk
The ARB should be fine as well,
I've tried myself, flashed it on top of 9.6.3 fw less ROM.
@otonieru Saw your post in the firmwareless rom thread. Are you same person that was creating these zips on xiaomi.eu?
Had a look at the script again, looks safe.
It would help if you labeled the zip with the date/version of firmware. i.e. Global 8.8.16.
Also I thought you where going to remove unneeded files. Don't know what update binary script does?
Edit: - Waiting on a RR rom update before flashing new partial firmware.
corkiejp said:
@otonieru Saw your post in the firmwareless rom thread. Are you same person that was creating these zips on xiaomi.eu?
Had a look at the script again, looks safe.
It would help if you labeled the zip with the date/version of firmware. i.e. Global 8.8.16.
Also I thought you where going to remove unneeded files. Don't know what update binary script does?
Edit: - Waiting on a RR rom update before flashing new partial firmware.
Click to expand...
Click to collapse
Oh, no, am not on xiaomi.eu. Just happen to look around the fw less thread, and it seems there's a need for a TWRP flashable zip for radio only update,
I use firmware file from git, and merged it with TWRP flashable zip. Only, i edit the updater script to make it only flash modem, bluetooth and DSP.
I didnt delete too much files from firmware update folder, only one i think is really safe to delete.
Alright, i will modify the file name.
It contain 8.8.16 Global files.
otonieru said:
I use firmware file from git, and merged it with TWRP flashable zip. Only, i edit the updater script to make it only flash modem, bluetooth and DSP.
Click to expand...
Click to collapse
Have you a link to git, it would be easier to just download the three files for me, than extracting them from Firmware zips.
Apparently those firmware files are safe. I flashed them with a .zip file I put together. For anyone that wants to try you can download it from here.
Looks like @yshalsager is also going to provide update zips with just the three files as well.
@otonieru @Ookami999 He must of edited his automatic script to create the zips.
corkiejp said:
Looks like @yshalsager is also going to provide update zips with just the three files as well.
@otonieru @Ookami999 He must of edited his automatic script to create the zips.
Click to expand...
Click to collapse
lol. you spoiled the surprise, it was a test. I'll release it soon
corkiejp said:
Looks like @yshalsager is also going to provide update zips with just the three files as well.
@otonieru @Ookami999 He must of edited his automatic script to create the zips.
Click to expand...
Click to collapse
I edited the original one and signed the .zip, it seems to be working. Although the cell power consumption is still quite high so far.
deleted
I have this problem
Jio-volte network goes away after reboot in all pie custom roms. Network signals are on after changing preferred nertwork type.
and data on jio-volte is not working.
I was told i should upgrade firmware,but same problem.
will upgrading these 3 files from here help me?
ahsnali said:
I have this problem
Jio-volte network goes away after reboot in all pie custom roms. Network signals are on after changing preferred nertwork type.
and data on jio-volte is not working.
I was told i should upgrade firmware,but same problem.
will upgrading these 3 files from here help me?
Click to expand...
Click to collapse
It may or may not help your situation. If your worried about your anti version, there is non arb firmware zips available with just them files.
VoLTE is broken on most PIE roms (I believe based on discussions in TE) , check your rom thread and see if anyone else has it working. Or if there is Patch to enable it.
Magisk cannot parse the boot image from the latest Android 13 image.
Apparently the developer only wants bug reports from official debug releases, but there are *no* official debug releases on the releases view on github.
So of course the bot closed my github issue. Linking it anyway because it's the fastest way to get the boot image file. https://github.com/topjohnwu/Magisk/issues/6283
It feels like a "what did you expect me to do?" kind of thing. It's a brand new phone; there's a bug in the android 12 firmware causing bootloader unlock to not work at all; can't downgrade from 13 to 12; magisk can't parse boot.img; my old phone is dead before its time.
On the main page of the Magisk Github, there's a "Downloads" section; the far-right, red "Debug" button is a link to the debug version 25203 the bot wants you to use to file a report.
That said, I'm not sure why it'd be failing to patch, it worked fine for me without needing any special build of Magisk - though I think I was already running 13 when patching the 13 boot image, not sure if that's a factor.
And when you say "there's a bug in the android 12 firmware", are you getting an error or something? You don't have a carrier model (Verizon and AT&T, I think?) that restricts/prohibits unlocking the bootloader? Nevermind on this point, just realized you're referring to the 6a and I just researched the issue, apologies.
By the way, if you do want to downgrade to 12 after upgrading to 13, some good news, I believe the Developer Support image of Android 12 should be useful; from my understanding it's just 12 with the updated bootloader so you won't run into the anti-rollback.
And be careful and tread lightly, the anti-rollback WILL hard brick your phone if triggered! I found out the hard way...
So I did finally figure it out. The nested zip files were confusing me; and it didn't help that one of the two images I got was incomplete.
As the other guy said elsewhere; bootloader is not boot. The actual boot.img is inside a nested zip file. I'm actually kind of suprised that updating a zip file that is fed to fastboot is the way its done, but that's what it is.
joshudson said:
So I did finally figure it out. The nested zip files were confusing me; and it didn't help that one of the two images I got was incomplete.
As the other guy said elsewhere; bootloader is not boot. The actual boot.img is inside a nested zip file. I'm actually kind of suprised that updating a zip file that is fed to fastboot is the way its done, but that's what it is.
Click to expand...
Click to collapse
The images in the internal zip can be written separately as well.
fastboot flash boot boot.img