Just as an FYI for anyone else. I was just able to take the NE5 OTA while being rooted with the towelroot method just fine.
If you have done the hotspot mod, you need to revert it back before you can get the OTA to take. Otherwise it will error out during the update file hash check and fail.
After the update is complete, just follow the steps like before and use towelroot to re-root. I had to reboot, then open supersu to install root binaries. A second reboot after install was done per instructions in the root install process.
Again, l did not uninstall xposed framework, unfreeze any apps that I had frozen, or uninstall wanam xposed. The only thing I had to do was revert the hotspot mod files to get the OTA past the file hash check.
Good luck!
What is the easiest way to remove the hotspot stuff so that I can take the OTA. That is the only thing I've done since rooting.
Thanks
SWhetsel said:
Just as an FYI for anyone else. I was just able to take the NE5 OTA while being rooted with the towelroot method just fine.
If you have done the hotspot mod, you need to revert it back before you can get the OTA to take. Otherwise it will error out during the update file hash check and fail.
After the update is complete, just follow the steps like before and use towelroot to re-root. I had to reboot, then open supersu to install root binaries. A second reboot after install was done per instructions in the root install process.
Again, l did not uninstall xposed framework, unfreeze any apps that I had frozen, or uninstall wanam xposed. The only thing I had to do was revert the hotspot mod files to get the OTA past the file hash check.
Good luck!
Click to expand...
Click to collapse
ksfireman82 said:
What is the easiest way to remove the hotspot stuff so that I can take the OTA. That is the only thing I've done since rooting.
Thanks
Click to expand...
Click to collapse
When you did the mod, if you just replaced the services.odex and services.jar files, hopefully you saved the original files. When you replace a system file you should make backups of the original files.
So for instance, I renamed both of those files to services.odex.old and services.jar.old before placing the new files into the folder. So to revert the files, I deleted the replacement edited files, and then renamed the originals back to the correct names.
However, if you didn't make a back up, I can attach my two original files to this post. I just can't promise it will work for you.
SWhetsel said:
When you did the mod, if you just replaced the services.odex and services.jar files, hopefully you saved the original files. When you replace a system file you should make backups of the original files.
So for instance, I renamed both of those files to services.odex.old and services.jar.old before placing the new files into the folder. So to revert the files, I deleted the replacement edited files, and then renamed the originals back to the correct names.
However, if you didn't make a back up, I can attach my two original files to this post. I just can't promise it will work for you.
Click to expand...
Click to collapse
Damn, didn't rename or save the original files. I had the OTA first then did the hot spot mod.
Original files.
I MAKE NO GUARANTEE THESE WILL WORK FOR YOU!
NOT A FLASHABLE ZIP.
Related
I am having issues with framework-res.apk.
I make some minor changes and add and replace these files into framework-res.apk using WinRar.
Then copy this into the update.zip file and
install from sdcard using clockworkmod.
But then my nookGL won't reboot, and I end up having to factory reset.
After the factory reset the changes I put in the framework-res are now showing up and working fine.
I then need to go through the process to root the nook etc.
This is a very long winded way for some minor changes.
Is there something I am doing wrong?
I am now very hesistant to try any more changes, even though I would love to, as I really don't want to have to go through the whole process again.
Any suggestions?
Framework.res has to be signed with the system signature.
You can copy over the original META-INF directory (most of the time) when you repack it.
Your problem could be one of three things:
1) You repacked it without the original signature.
2) You repacked it with a new (personal or debug) signature.
3) You repacked it with the original signature but you modified something important (like AndroidManifest.xml).
If you want to get heavily into mods you should resign your whole system with either the debug or your personal signature.
Yes! Thank You, Renata! That was it - problem solved!
In the jelly beans thread Beanstown106 posted a link to batter image mods to change the picture has anybody got these to work and if so could you explain how I've tried moving systemui.apk and tried flashing them via safe strap and I get nothing
Sent from my SM-N900V using Tapatalk
I am having the same problem, but I did find a workaround. Here's what I did:
1. Copied the SystemUI.apk to my extSDCard/download folder, then to my PC from there (I reversed the process for putting it back)
2. Changed the .apk to .zip
3. Extracted the downloaded battery zip file
4. Dragged dropped the images from the downloaded file into the SystemUI.zip. (Making sure to NOT change anything else)
5. Renamed SystemUI.zip back to SystemUI.apk
6. Using Root Explorer, made a copy of the original SystemUI.apk to SystemUI.apk.bak.
7. Copied my modified SystemUI.apk back into it's original location, overwriting the original one.
8. Reboot
I can't say for sure that this will work for you, but I was able to successfully make the change on mine.
I'm still trying to figure out why flashing it through SS didn't work. When I did the install, it gave no errors (that I could see) and showed successful. When I booted back up, I still had the default icon.
Hope this is helpful
So I rooted my device, hten followed a guide, that Instructed me to replace two files in the system/framework folder, services.jar and services.odex, i backed them up, but like a fool i backed them up in the same folder, which i can't access, I can restore from CWM and i was actually hoping someone had a system recovery that i could borrow, since i can't seem to figure out how to change the files back within my cwm backup.
callen2011 said:
So I rooted my device, hten followed a guide, that Instructed me to replace two files in the system/framework folder, services.jar and services.odex, i backed them up, but like a fool i backed them up in the same folder, which i can't access, I can restore from CWM and i was actually hoping someone had a system recovery that i could borrow, since i can't seem to figure out how to change the files back within my cwm backup.
Click to expand...
Click to collapse
Okay, slow down. You can fix this. There are only a few steps:
1. Download the stock odexed rom. You can find it here: https://www.androidfilehost.com/?fid=23622183712466565
2. Extract the stock rom.
3. Navigate to the system/framework folder
4. Copy services.jar and services.odex to your phone (download folder or anywhere on your sdcard is fine)
5. Since you are rooted, you can use a root file explorer to copy those files to your system/framework folder on your phone. Locate the two files you copied from the stock odex rom on your computer. Paste these into system framework, and overwrite the two existing files (you can use ES file manager or other root browser to accomplish this)
That's it! There are many other ways to do this, but this is probably the simplest.
I'd just flash a custom rom with hotspot though
Kinda makes this noob sick. I just got a new Moto G4 X1625 (not Amazon). Next came the steps to unlock the bootloader with Motorola and to install TWRP. Everything had gone so easily by following some how-to steps I jumped to the next step of installing SuperSU without doing a backup – thinking it was simply adding an app. Big mistake! Reboot and now always stuck on the logo boot animation.
Okay, so I found and tried use TWRP to install ATHENE_6.0.1_MPJ24.139-13.1_cid50_subsidy-DEFAULT_CFC.xml.zip in an attempt to get back to stock. No luck there since install always aborts with a "Could not find 'META-INF/com/google/android/update-binary' in the zip file."
I checked a couple of other ROMs and that META-INF directory doesn't seem to be included in them either.
What do I need to do just to get back to normal eliminating the effects of that SuperSU install? Help greatly appreciated.
That file you downloaded is not a flashable file.
Instead, read this linky
Thanks for the helpful clue @t0mm13b. I followed the approach at <http://www.stechguide.com/download-stock-firmware-of-moto-g4-and-g4-plus/> and executed the listed commands from my MacOS Terminal. They did the job resulting in a fresh install after bootup.
2-1/2 questions…
1. Are flashable ROM files readily available? The ones I found all seemed missing the META-INF directory. Will they be .img files and not .zip?
2. Is TWRP not useful for these stock ROMs?
The ones I found all seemed missing the META-INF directory. Will they be .img files and not .zip?
Click to expand...
Click to collapse
As a general rule of thumb, read the accompanying text to the link of the download, on a web page where you find one. It will tell you if it's flashable or not.
Factory images, just like what you had to carry out previously, never have, and do not have the `META-INF` directory. They usually contain img files that requires `fastboot flash`.
On the other hand, OTAs and flashable zips will have that in their respective zip file.
Thanks again @t0mm13b for the clarification. I often didn't see info about whether a ROM is flashable in link or web page text, but it may have just been assumed based on being aware of what the zip contains.
How would I go about editing the updater-script on the stock rom that way TWRP can flash the zip to my phone? thanks in advance for any info on how I might do this trying to flash the 8.0 ota for Z012D
Bump anyone?
Any text editor will do to edit it, it's located in META-INF/com/google/android/. Be careful, there are two files in that directory, you want updater-script not updater-binary
Open the file, delete the first few lines, pretty much up to "ui_print....."
Save it back into the rom zip and flash it. I just did this a couple hours ago thru twrp, I'm on 1802.44 with no issues.
wang1chung said:
Any text editor will do to edit it, it's located in META-INF/com/google/android/. Be careful, there are two files in that directory, you want updater-script not updater-binary
Open the file, delete the first few lines, pretty much up to "ui_print....."
Save it back into the rom zip and flash it. I just did this a couple hours ago thru twrp, I'm on 1802.44 with no issues.
Click to expand...
Click to collapse
Are you able to tell me what to get rid of? Also do I use no verify 5.1? or is there a new one?
mastermarkofroms said:
Are you able to tell me what to get rid of? Also do I use no verify 5.1? or is there a new one?
Click to expand...
Click to collapse
take a pic of the script, every one is different.
No-verity file is required when you don't use magisk or supersu. I use magisk and no, there isn't a new one.