Database Develop

Droid 4 Utility Updated

If you are on a ICS leak now and want to move to another check out this new tool here: http://forum.xda-developers.com/showthread.php?t=1779810
You can use this to restore stock Gingerbread if you are on a modified GB or to go from one ICS to another.
This is the original D4 tool with additions created by several others and repackaged-edited by me.
UPDATE NOTICE: If you downloaded the tool on 06/20 from about 10pm eastern till noon the next day the script was an old version. It is correct now. Just download again.
06/22 9 AM Eastern - updated superuser binary to most recent version.
06/23 12:30 PM Eastern - updated links for 6.16.213 (thanks again droidian1441)
06/25 10:30 PM Eastern - Revised script, that includes a data save option for restoring GB and the best change. The flashing of the GB files and the ICS Kernel to jump from one ICS to another is now all in one. Removed the push file to sdcard (some thought you could do this after you started flashing the system).
06/30 11 AM Eastern - add new link to download all files.
07/01 10:30 Eastern - Updated Superuser (3.1.3) + binary and VoodooRootKeeper (2.0.3) to latest versions. Update ICS root for Dan Rosenburg's root script, this will install superuser and busybox. The other root method didn't seem to install busybox in proper location and resulted in some malfunctions of root only apps. If you installed the previous root script, use voodoo to temporary unroot, then uninstall superuser. Run the new script and you should be good. Note on the latest version of superuser scroll to the left for the update binary menu. Also contains a temporary unroot and OTA protect root.
Some users have reported driver trouble especially after moving to ICS and trying to root.
Go here to get the driver update tools: https://motorola-global-portal.custh...p/30,6720,8302
Some have reported that the USB utility didn't fix there trouble and had to download motocast, which downloaded new drivers.
Thanks again to 1898trouble07 (droidforums) for the data save tip.
I am on longer putting a full version out. It was was just too big to maintain updates. Everything you need is here. You just have to download a few things and move around a couple of files.
First read this entire post at least twice, skipping any step will be BAD!. Then download everything you need for this.
1. All downloads are listed here: http://d-h.st/users/jsnweitzel/?fld_id=3413#files
Other download links below.
1. Get the Tool Here: https://docs.google.com/open?id=0Byw...URLSjQ5V29pYk0
or here: https://www.dropbox.com/s/132a5i038luy4vu/Droid4withICSfix-rootLITE (3).zip
or here: https://docs.google.com/open?id=0Byw...XV2N2N3cTBoQW8
This is a double zip extract until you see the .bat files and a "files" folder. Double click the script to run the tool.
2. Get the GB 219 Fastboot files here: http://sbf.droid-developers.org/cdma...1FF_01.xml.zip
or here: https://docs.google.com/open?id=0Byw...WswcF91MkxkODA
3. If you are just restoring GB this is all you need. Extract the fastboot zip files and copy them to "files" folder of the tool.
If you are just restoring GB, rooted and running the data save option...It might mess up your root. I don't really know for sure. It will erase the superuser binary and the backup if you are running the rootkeeper, but should keep superuser installed. Therefore you may be in a half rooted stuck state and running the root again may not work. I don't have a phone on GB to test this out. To be extra cautious you may want to run the unroot, restore GB then root again. Let me know what you experience and I can update the post.
If you want to go to ICS and are on GB. Then download (see item one below) the D4213 and put it on your external sdcard Boot to recovery and flash from external. You don't have to be rooted. but if you are the easy way to keep root is to use voodoo's rootkeeper. Protect root, temporarily unroot, reroot, flash the ota, then restore root. If you mess up just use the tool to run the ICS root.
If you are moving from one ICS to another keep reading. Downloading the following two files.
1. Get the ICS OTA currently 6.16.213 ICS here: https://docs.google.com/open?id=0Byw...jVSanRzaTZ5alU
This is a double zip to open until you see the folder named D4213, then copy this file to the external sdcard of your phone.
2. Get the matching Kernel 6.16.213 (boot.img) here: https://docs.google.com/open?id=0Byw...1J0VFBCY1NBM2M
Unzip this folder and copy the boot.img to the "files" folder of the tool. It must be named "ICSFIX" for the tool to work.
If you are going from one ICS to another this is the basic procedure. This uses a fair amount of your pc resources. Don't have a bunch of other programs running. Set the phone to MTP for USB and be sure debugging is on (system setting, developer options).
Be sure you charge your battery first. This is a long process be patient. You will get several errors (INFO validation type) if you are on ICS and flash the GB files. Just let it finish.
1. Charge your battery to 100% and have a high quality usb cable. Sometimes the process fails so you might have to do it twice. When in fastboot mode the battery will not charge.
2. Put the D4213 zip on your external sdcard; just copy and paste with windows.
3. Boot to bootloader and select fastboot (power down, hold both volume buttons and press power, release power, select ap fastboot). You can use the tool for this step but will have to manually do it later.
4. Select menu 16 and flash the GB files plus the boot.img of 213. This will take a while just let it finish and follow the prompts when ask to press a key to continue. You will get some errors (Info validation type). Just let it run and finish.
5. Your phone will reboot and attempt to update (android with spinning ball).
6. Let it run until the screen goes blank and the red "M" appears.
7. Then force a power down and boot to the bootloader.
9. Select recovery. When you see the android with the red exclamation press both volume buttons. Select apply update from external storage and chose the 213 zip.
10. Once complete reboot.
11. ENJOY
12. Root ICS if you want.
If you use this to install vodoo's root keeper make sure your screen is unlocked. If not it seems to hang up sometimes. You should immediately get a superuser request.
Finally this is windows only. If someone writes the linux script I can add it in later. Let me know if you have any issues, suggestions, questions or problems.
As usual doing any of this is at your own risk and may render your phone to be a nice paperweight.
Here is the full menu of the tool:
1. Fastboot GB to stock and ERASE DATA (You can use this to restore stock Gingerbread if you are on a modified GB)
2. Fastboot GB to stock and SAVE DATA
3. Root GB
4. Unroot GB
5. Install Voodoo Rootkeeper
6. Install Safestrap for GB
7. System Pull
8. Overclock for GB
9. Boot to Fastboot
10. Boot to Recovery
11. ADB Shell
12. Reboot phone
13. Flash the ICSFIX Kernel (This is not necessary to jump from one ICS to another, use menu 16. Left in for advanced users only)
14. Install Safestrap for ICS
15. Droid 4 ICS Root
16. D4 ICS Fix (Jump from one leak to another) and SAVE DATA

Thought fastboot back to gb after going to the leaked ics caused a brick?
Sent from my DROID4 using xda premium

twizzles said:
Thought fastboot back to gb after going to the leaked ics caused a brick?
Click to expand...
Click to collapse
Yes, but not completely. The phone will still be able to go into fastboot mode which then allows you to flash the necessary files for the upgrade to work.

Gotcha. Thanks a lot
Sent from my DROID4 using xda premium

What are the necessary files to flash via fastboot after downgrading to gingerbread from ICS?

If you are on GB and want to do a stock restore this will do it for you. If you are on a ICS leak it's one of the steps you need to move up.

Now I will feel more comfortable in flashing the update!, thanks man. Great job.
Sent from my DROID4 using XDA

stereokid said:
What are the necessary files to flash via fastboot after downgrading to gingerbread from ICS?
Click to expand...
Click to collapse
You can't go back to GB if you are on a ICS leak. You can upgrade to a newer leak. Here are the instructions: http://www.droidforums.net/forum/dr...k-200-aka-upgrading-200-206-instructions.html
Same ones can be used to go up to 208. The tool has everything you need.

If im on 206 do i have to flash to 208 in order to flash the new 211 version? And whats in the updates? Enough to take the risk yet again of flashing a leak?
Sent from my DROID4 using xda premium

You can go right up to 211. I haven't changed the tool yet so you will have to replace the 208 files with the 211 files. I will be modifying the tool soon for 211.

Is there an eta for the tool update by any chance? Thanks
Sent from my DROID4 using xda premium

I have started working over the script, with an idea to simplify a step too. But will test on my own phone before I post. You can use the tool as-is if you rename the boot.img and the ota. There is one little hiccup in the script after pushing the boot.img (kernel), but it's doesn't affect the process. Hope to have it up in a few hours.
The new tool is up with some instructions too. The Lite version is good to go, the other is still uploading.

Is it possible to use this tool to flash up from gb? I'm currently using eclipse on safestrap (I know id need to remove safestrap) but didn't know if this will only work with those already on the leaks or if we can use straight from gb
Sent from my DROID4 using XDA

This tool can restore your phone to stock GB. If you have the GB Fastboot files and the latest ICS OTA you can use the lite version and just put add the files to files folder.
If you want to move to ICS you might be able to uninstall your rom, safestrap and fix the logwrapper renaming. I think I saw a thread about that somewhere.

For anyone trying to download I was having some issues setting up the links for gdrive. Just haven't used it before for file sharing. All should be good now.

jsnweitzel said:
This tool can restore your phone to stock GB. If you have the GB Fastboot files and the latest ICS OTA you can use the lite version and just put add the files to files folder.
Click to expand...
Click to collapse
If you can, you might want to edit that first sentence to specify that it can restore your phone to stock GB _if you haven't upgraded to ICS_.

Thanks for the suggestion...just saw that 212 is coming. Will be updating once I get a copy.

Ok I just updated the OP, with all the downloads you need. But it's late I am a bit tired. Let me know if something is out of sorts or a link is broke or wrong. It was just too much to keep the full tool up to date and upload.

Link to the tool is broken unfortunately

jgardner said:
Link to the tool is broken unfortunately
Click to expand...
Click to collapse
Not sure what happened there. I did the link over. Try it now:https://docs.google.com/open?id=0BywuYGr-7VrYcURLSjQ5V29pYk0
Some users on droidforums.net had trouble when they just clicked the link. Not sure why, but it worked if they did a copy and paste to the browser.

(Myphone Uno) ota update problem

For those who have myphone uno plss help me it won't update
If someone kind enough to share the link of
ota zip I can just flash It in stock recovery

gabisonfire98 said:
For those who have myphone uno plss help me it won't update
If someone kind enough to share the link of
ota zip I can just flash It in stock recovery
Click to expand...
Click to collapse
Ok lmy47o patch zip is just 23 mb

guys,
i also have a myphone uno rooted but no custom recovery as of now. i had no problem updating the previous system updates. the recent one came in just fine. then now, the phone (every time it connects to wi-fi) would offer a new sys update. but when this is applied, the procedure results with an ERROR. i wonder if you guys are getting similar results.

bodega1968 said:
guys,
i also have a myphone uno rooted but no custom recovery as of now. i had no problem updating the previous system updates. the recent one came in just fine. then now, the phone (every time it connects to wi-fi) would offer a new sys update. but when this is applied, the procedure results with an ERROR. i wonder if you guys are getting similar results.
Click to expand...
Click to collapse
i have the same problem. my current system is version is 5.1.1. i'm using stock recovery. my phone is rooted using superSU.

guys,
i've recently just tried doing a FACTORY RESET (myPhone UNO), Android 5.1.1, and to no avail: still an error when updated a 18MB update. either the update file has an error or my rooted settings are preventing a clean OTA update.
bodega1968

dude,
I finally resolved the update issue. will give you the instructions soon. got to go... but will get back to you once I have composed the procedures... I believe the cause is having rooted and changed some data in the system cache.
bod98

SOLVING [one solution] OTA PROBLEMS in myPhone UNO (sprout)
Background.
Phone model: myPhone UNO (sprout hardware)
Android 5.1.1
*Problem: OTA update failure.
*Log message:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
VErifying current system...
"/system/bin/app_process32" has unexpected contents.
E:Eror in 0/cache/recovery/block.map
(Status 7)
*Possible Cause: Occurred after rooting with anil293 (Android Root Kit here). I’m not saying that this program is bad, but only to caution anyone who may want to root and possibly lose OTA updates.
Solution. (*This worked for me since I had done a previous NANDROID backup (NB) of the phone prior to any system changes (i.e. rooting, custom recovery, etc.). The following steps were written to help those who may not be too familiar with some basic non-GUI (graphic user interface) commands in order to restore one’s device to it’s original and working condition.
Step 1: I chanced upon DEVAM30’s wonderful contribution on how to run RECOVERY without installing it ‘permanently’ into the phone. Check out his page here. This allowed me to make my NB. Download from this page the PHILZ8.img (*This will be the 'virtual' recovery file which you will boot into in order to make your NB)
Step 2: Assuming that you have a previous NB, this (huge file) should be located in the clockworkmod folder in your SDCard. You will refer to this once you have successfully booted in the PHILZ8 recovery.
Step 3: Set your phone to allow USB Debugging. (*This can be done in the Developer’s Section) NOTE: Prior to all this, make sure you BACKUP your critical personal files (i.e. contacts, SMS, data, etc. GOOGLE this to find out how to backup your personal data. The next steps will ERASE everything in your phone. I will not be responsible for any data lose or the bricking of your phone.
Step 4: Boot your device in FASTBOOT mode (FM). (*Power OFF the device, then after 5-10 seconds, press POWER ON + VOL UP. When screen turns on, release VOL UP followed by POWER ON). MENU comes up. Use VOL UP to SCROLL among the choices, and when you have selected FM, press VOL DOWN and the phone should pretty much be in FMode.
Step 5: While your phone is in FM. In your PC you should have ADB/FASTBOOT functions already set up. Check the link here on how to install and work in fastboot mode. When you have properly installed everything in this STEP, you must copy the PHILZ8.img into the adb/fastboot folder. You may rename it into something simpler like recovery.img
Step 6: Connect your phone (*already in FM) to the PC.
Step 7: In your PC, in adb/fastboot folder (*check if your device is connected properly – adb devices or fastboot devices). If your device is detected some number should appear in the screen. Then you type: fastboot boot philz8.img or the name you gave to the .img file.
Step 8: Wait for the PHILZ8 recovery to kick in. Once it boots up you’re now ready to do a RESTORE of your NB. You will see a TOUCH menu in your screen. You will carry out two important steps. (a) wipe the cache and (b) restore the NB image from the SDCard.
Step 9: Choose the wipe menu. In my case, I chose to WIPE (*Choose wipe cache options) cache and the dalvik cache. The former one will take a while, and the latter only takes a few seconds. Once done, +++GO BACK++ to the main menu and then TAP on RESTORE. It will ask you where you will restore the image from. Choose SD card. If it doesn’t do this automatically, you may have to navigate to the clockworkmod folder where your NB image is located. Choose that image and you’re good to go!
Step 10: Once the entire procedure is over (*be patient, it may take some time to finish the entire restoring of the image), you will now opt to REBOOT the SYSTEM. Now, this is critical (in my opinion) because the virtual recovery (PHILZ8) will ask if you wish to install root. Choose NO! Otherwise, it may make some changes in the system settings that will conflict with the OTA updates we want to work.
The device will reboot and you will pretty much be back to its original settings (more than a simple factory reset). And your phone will update a few times and no error will come out.
For those of your who don’t have or have not been able to make a CLEAN NB, I uploaded this RAW image phone (it does not contain any personal data or programs) . You may download it here.
bod68
*updated 9IX15

LINK to my NANDROID BACKUP
gabisonfire98 said:
Ok lmy47o patch zip is just 23 mb
Click to expand...
Click to collapse
gabisonfire98,
dude, if you're patient enough to follow my 'SOLUTION' to regaining OTA updates, check out the procedure i outlined below, september 4, i believe it was.
the link to my NANDROID BACKUP which could be RESTORED to your device (*Using the wonderful procedure outlined by DEVAM03)!
Download the image here
Just email me if you find some of the instructions confusing, just email me.
bod68

[SOLVED] Captured Latest OTA but . . .

Hey Guys,
I have been getting an 18MB OTA for my Micromax AndroidOne. However the update keeps failing. I have captured the OTA. The lInk is:
Update to LMY47K
The update failed maybe because I was rooted. But then I factory reset the phone so now, Root should technically be gone. Before doing factory reset, I had also removed root from the SU app. Still, when I try to install OTA update, I am getting an error. So I Captured the OTA and then tried to flashed the zip via recovery as well as ADB Sideload. Both of them gave the same error at the Verifying Current System stage:
Verifying current system...
"/system/bin/install-recovery.sh" has unexpected contents.
E:Error in /sideload/package.zip
(Status 7)
Installation Aborted
The same error occurs every time via both flashing methods. Any idea guys??
Thanks
PLEASE FLASH ON YOUR WON RISK. I AM NOT RESPONSIBLE FOR ANY DAMAGE THAT MAY BE CAUSED TO YOUR PHONE

Finally
DO THE FOLLOWING AT YOUR OWN RISK. I AM NOT RESPONSIBLE IF YOU BRICK OR DAMAGE YOUR PHONE
Finally it's done. I did the following steps: (Obviously backup data first)
1. I Unlocked the bootloader *LOST ALL DATA AS EXPECTED*
2. Flashed Philz Recovery (You can install any other but this recovery will be lost once flashing official zip as a result making Official Stock ROM and Official Stock Recovery)
Did these above 2 steps using AndroidOne Tool Kit. There are thorough instructions and warning to do so.
3. Downloaded the official update file from here. Only LMY47O file. Copied it on an External SD card
4. Go to Philz recovery, Select Wipe and then Clean to Install ROM (Preferably without inserting the SD Card).
5. Now insert the SD card, wait for a minute for the recovery to recognize your card and then select, Install Zip and then select from SD Card. Select your zip files, confirm installation.. Reboot once done
6. Once done, you will have a brand new OS. Enter all the information. and you will get the next two updates OTA and get installed just fine
Enjoy Your latest update!!

ashhem said:
DO THE FOLLOWING AT YOUR OWN RISK. I AM NOT RESPONSIBLE IF YOU BRICK OR DAMAGE YOUR PHONE
Finally it's done. I did the following steps: (Obviously backup data first)
1. I Unlocked the bootloader *LOST ALL DATA AS EXPECTED*
2. Flashed Philz Recovery (You can install any other but this recovery will be lost once flashing official zip as a result making Official Stock ROM and Official Stock Recovery)
Did these above 2 steps using AndroidOne Tool Kit. There are thorough instructions and warning to do so.
3. Downloaded the official update file from here. Only LMY47O file. Copied it on an External SD card
4. Go to Philz recovery, Select Wipe and then Clean to Install ROM (Preferably without inserting the SD Card).
5. Now insert the SD card, wait for a minute for the recovery to recognize your card and then select, Install Zip and then select from SD Card. Select your zip files, confirm installation.. Reboot once done
6. Once done, you will have a brand new OS. Enter all the information. and you will get the next two updates OTA and get installed just fine
Enjoy Your latest update!!
Click to expand...
Click to collapse
Justcopying and pasting from www.dileepworld.blogspot.com isillegal...you better know that!

nexi4droid said:
Justcopying and pasting from www.dileepworld.blogspot.com isillegal...you better know that!
Click to expand...
Click to collapse
Hi nexi4droid, greetings of the day.
A few points:
1. I have NOT copied this stuff from anywhere. I have written it myself. However it is but OBVIOUS that the instructions are very similar to other present ALL OVER THE WEB as that is how it is done.
2. Also, as you must have seen, I have given links to official pages of toolkits or OTA captures from where I have taken stuff. If I wanted to "just Copy-Paste", I would not have done so. I am well aware of how much efforts you developers take to bring us custom ROMS and special tools. So, No I am not the type of guy that steals or copies other people's work
3. I went through the link you have given and I could not find identical instructions anywhere on that beautifully blog. But then again, as I said in the first point. That is how it is done so you will find similar instructions all over the web.
4. And finally, My post is OLDER!! than your http://dileepworld.blogspot.in/2015/08/solution-for-canvas-a1-getting-back-ota.html So if anything, I should be blaming you, not me. But I wont as it does not make any sense. Everyone reads things from different places and tries various things the find on the web and then finally may post what worked for them. I did the same in my words taking part instructions from 1cefire's post and the AndroidOne Toolkit (Links in the OP).
I hope I have cleared my self and have no intention to offend you. Have a great day

TWRP, System writing, Supersu, Impossible?

I have had my fair share of problems modifying android before but I have never had a phone flat out lie to me and say an operation was successful and actually nothing happened at all.
Have had my nexus 6 for a year or so now. Have had minor issues rooting / modifying marshmallow in the past but I figured out it was all caused by the system partition having basically 0 free space. Made a huge mistake and installed to the latest 7.0 OTA. Wanted to simply enable tethering and edit the thermal config to not shut cores down. Should be as simple as pulling the files, editing them, pushing them back to the phone in twrp with the system partition mounted and thats the end of it right? Wrong.
First of all twrp 3.0.2 refuses to let me touch the system partition without some giant prompt about how its going to make itself stick and offer to root the phone. Simple enough I have seen it in previous versions I say yes as usual except twrp proceedes to immediately spew a bunch of superuser files that do nothing throughout the system partition without asking me if I want root. Dumb but whatever. I mount /system as read write and I go edit and replace my two files like usual (build.prop and thermal config). No matter if I ADB push or use twrps built in file manager it claims the file replacement is successful. Reboot into android and not only have both files not been touched (Verified by adb pull) but the recovery gets overwritten with the factory recovery anyways. (NEVER had issues with twrp sticking on marshmallow. Now after every reboot it gets wiped out)
Second of all if I select yes to twrp mounting system as writable and it does its spewing as I mentioned before then installing SuperSU instantly causes the phone to not boot. Rewrite the boot.img to factory and it boots fine OR Rewrite the clean factory system image and the SuperSU boot works fine. But modifying /system with twrp and then running supersu at the same time is a no go. TWRP is obviously doing something stupid to system that pisses off supersu so undoing twrps mess or uninstalling supersu makes it bootable again.
I dont even want root! Everyone is claiming you need to run "settings put global tether_dun_required 0" as root along with adding the usual "net.tethering.noprovisioning=true" in the build.prop to get native tethering working again! On 6.X only the build.prop edit was needed to get it working.
So long story short. I just want native tethering to work and to tweak my /system/etc/thermal-engine-shamu.conf . Is there anyone here who has done this successfully on nougat? I feel like its all twrps fault but im far too tired and frustrated to try another version tonight.

You must be running an old version of TWRP. Update to the latest, as the latest no longer offers to root your device for you. The version of superuser included was ancient and caused the device to bootloop.
As to TWRP being overwritten Android 7.0 I believe does that on a stock system. If I recall, there is a script that needs to be modified to prevent it.

Strephon Alkhalikoi said:
You must be running an old version of TWRP. Update to the latest, as the latest no longer offers to root your device for you. The version of superuser included was ancient and caused the device to bootloop.
As to TWRP being overwritten Android 7.0 I believe does that on a stock system. If I recall, there is a script that needs to be modified to prevent it.
Click to expand...
Click to collapse
It's stated in the op he's using twrp 3.0.2.

Didgeridoohan said:
It's stated in the op he's using twrp 3.0.2.
Click to expand...
Click to collapse
I misread his post then. I wonder if perhaps he is running TWRP via fastboot instead of installing it.

Flashing recovery using "fastboot flash recovery XXX.img"

How to remove persistent /supersu dir from unrooted device?

Context: my motorola g4 is 5 years old and saw many different kinds of root attempts and amateurish handling (like modifying the system image) in its early days. I settled on magisk when it became a thing. Now I'm trying to go back to being rootless, including removing left-behind stuff like addon.d scripts.
TWRP shows a /supersu folder in the root fs, containing the usual apk, sh scripts, etc. I can delete this folder, but next time I boot my device (even just recovery!) it gets restored _somehow_. This is the only remaining trace of rooting I'm aware of, aside from the image just "not being untouched stock" anymore.
I'd like to get this folder permanently removed, without erasing my data.
Things I've tried:
- flash the stock rom: somehow it's defective (Package Installer crashes and I can't fix it by any means), despite it being the same zip I flashed two years ago and still use today, so this is not an option
- flashed stock boot
- unSU https://forum.xda-developers.com/showpost.php?p=63615067&postcount=2459
- installed supersu just to run its own unroot procedure, then ran unsu again, then flashed stock boot again
It just keeps coming back after every time I delete it and I'm out of ideas to stop it. All the threads I've found online offered only the above solutions that don't work.
Thanks for any good tips

@Marnes That sounds like it's TWRP's superuser. It won't exist if you are not booted to TWRP and it'll be repopulated everytime you boot to TWRP...

@Didgeridoohan I hadn't considered that possibility... I guess there's no way to verify it since checking after a regular boot if the folder is there would require rooting again. Thanks for the input!