Anyone have the stock dj11 wpa_supplicant file? I didn't change the stock file to .bak, I saved it to my sdcard. Accidentally deleted the backup and now I can't get the latest update. I was on ec02 but used heimdall to flash stock dj11 thinking it would replace the modified file, but it didn't. Now I'm stuck on dj11 and the update hangs on the wpa check. I've downloaded 2 different supposedly stock wpa_supplicant files, but neither worked with the update. I've double checked and made sure there were no .xxx extensions on the file also.
Thanks,
96cobra
Disregard, found another set of stock files and flashed them with heimdall. Everything working as expected now.
Which method did you use? Can you post a link to the files you used?
I ended up using the files from this post here on xda... http://forum.xda-developers.com/showthread.php?t=1033586
I originally tried files from a different site (droidforums/gizmoninja) and they did get me back to stock dj11, but the left the modified wpa file.
Related
i attempted to replace most of the .apks in the system app folder with the same .apks from an ealier version of the rom (because i prefer black to blue/black). i replaced them in the .zip before i flashed it, hoping it would work.. but it didnt.. in the recovery menu it says:
....
verifying update package...
e:wrong digest:
system/app/browser.apk
e:verification failed
browser was one i replaced. how do i make this work? i dont want to use root explorer to manually replace each ****ing thing, and i have no patients for adb. i must need to sign the package or something? i never unpacked anything, just replaced some contents.. thought id be fine..
on a related note there may be more issues to come. unzipped the framework-res.apk to my computer, renamed it .zip, went inside and replaced the battery icons, renamed it back to .apk and replaced the modified file in the rom. who knows what chaos i might have caused there.. if you know what to expect and how to fix it please feel free to help!
if it matters at all, the rom im modifying and flashing is nonsensikal 9.5 black/blue, the system apps came from version 8.2 black, and battery icon .pngs came from 5.4 black.
Id try and resign the whole rom after you make your changes it should be just fine
you cannot simply replace the apks in the zip, then flash. after replacing, use one of the following methods:
if you use linux, use EasySign (http://android.grdlock.net/index.php?&direction=0&order=&directory=HTC Droid Eris/Extras) or the Android Kitchen (http://forum.xda-developers.com/showthread.php?t=633246).
if using Windows:
Use AutoSign (http://androidforums.com/developer-101/8665-how-signing-roms.html).
Thanks. I'll get on the computer and give it a shot.
Sent from my nonsensikal froyo using XDA App
if you've unzipped the framework-res.apk then none of this will work anyway. You need to pull the images out of the old framework-res.apk and drag and drop them back into the new framework-res.apk without unzipping it. You shouldn't even need to rename it to zip. Just open it with a program like 7zip without unzipping and drop the png's in the correct folders. Then you can put the .apk back in the rom and resign from the links directed above.
Oh it all worked fine. I never unzipped framework, just extracted it from the Rom and renamed it, then replaced files, renamed back to apk, and replaced in original .zip. it worked great.
To achieve full 9.5 black I have to copy all of the previous versions (black) framework .pngs to the new Rom though.
I think the file is like, drawable-mpdi or something. Not landscape or non. I don't really know.. not in right frame of mind
Sent from my nonsensikal froyo using XDA App
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
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.
I wanted to download the firmware and remove all the bloat stuff from my N9108v.
Downloaded the firmware and it is a zip file. NO worries - unzipped and I don't see any ".tar.md5" files. Just various other files that include "mbn img ext4 bin" files. MNone of these look like working in ODIN. Is there anything I'm doing wrong?
Thanks in advance.
Cheers.
s327374 said:
I wanted to download the firmware and remove all the bloat stuff from my N9108v.
Downloaded the firmware and it is a zip file. NO worries - unzipped and I don't see any ".tar.md5" files. Just various other files that include "mbn img ext4 bin" files. MNone of these look like working in ODIN. Is there anything I'm doing wrong?
Thanks in advance.
Cheers.
Click to expand...
Click to collapse
HI OP - please remove thread - I just used a different extractor - less vigorous I guess. Did the trick and just extracted to the first layer. Ok - didn't remove the bloatware either...
Thanks.
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.