hello well first off i just finished troubleshooting the **** out of my phone and i see lots of others are having issues as well and its all scattered. so i am going to post my method which should get you updated with MT's AIO which also includes a fix for those who are having permission problems with the AIO.
(this is optional and for those who were having problems with permission errors using AIO on GV 2.0) (skip below for first step of getting to zv7)
first off the main thing that I figured out is that if you are on GV2.0 the kernel by default (at least for me) disables logcat which gives many problems with MT's AIO solution with the error cannot open dev/log/main with all the permission problems with rooting / unrooting on GV2.0. So for those who are having that issue here is the fix:
open root explorer
go into /system/etc/init.d/12gvtw
long click then open up text editor
go to where it says rm /dev/log/main and change it to
#rm /dev/log/main
then save and then reboot which should fix the permissions errors.
now doing that enabled me to be able to have success with the AIO to prepare for the update to zv8 while on GV 2.0 ...
but then I ran into another problem after that was that the OTA update would fail. most likely because the boot.img was not stock (this is just a guess, probably other reasons as well)
----------------------
but what worked for me was going completely stock gingerbread.
so for this fix I simply went to this thread to get completely to stock zv7
http://forum.xda-developers.com/showthread.php?t=1348637
I then downloaded the nandroid and followed MT's instructions steps 1-6
1.) Download the .zip & make sure 4g is enabled.
2.) Place zip in external sdcard
3.) I recommend to wipe data to prevent any problems
I want to emphasize that you SHOULD WIPE DATA NOW AT THIS STEP IN CWM BEFORE IT GETS TO STOCK RECOVERY.
4.) Go to install zip from sdcard
5.) Select RevoZV7GBStock.zip
6.) Reboot
then after that my phone booted up completely stock (with stock boot.img) and wiped data with root still enabled.
then I went to this thread to get MT's AIO zv8 and followed the steps 1-5 (steps 6 and 7 will be completed later)
http://forum.xda-developers.com/showthread.php?t=1566729
1) Download zip and extract
2) Install drivers if not already installed
3) Make sure you are on stock ZV7
4) Click Root&RecoveryAIO.bat
5) Select "Prepare for Update"
then the phone rebooted and was at stock recovery and unrooted and was completely stock but with the added the data/local.prop edits.
so then I went to this thread to download Broken Out Rom from my computer and followed steps 1-2 (steps 3-9 will be completed later) before i completed the AIO process steps 6-7 stated earlier.
http://forum.xda-developers.com/showthread.php?t=1577423
1.) Download the .zip & make sure 4g is enabled.
2.) Place zip in external sdcard
So now you should have your phone completely unrooted with stock recovery with Broken Out Rom downloaded on your phone's sd card (not installed yet).
You are now ready to go to get the OTA update. (step 6)
go to settings > about phone > software update > check new
then you should have the OTA update successfully installed when it reboots.
you now have zv8 installed with no root or cwm.
then i went to MT's AIO for zv8 and clicked option 7 which is too root zv8.
then the phone gave me an error on AIO when trying to root but then CWM still got installed at the end of the AIO process.
so the phone then booted up with no root but CWM was installed but could not get into recovery mode using quickboot to recovery option on the phone due to no root access..
for this fix I then opened up MT's AIO for zv7 found here under step 2 of "How do I completely Return to Stock"
http://forum.xda-developers.com/showthread.php?t=1348637
and then clicked option 7 which is reboot recovery. this booted my phone into recovery.
then I went to continue the process of installing Broken Out Rom (steps 3 and 4 are skipped because we already wiped data initially above)
5.) Go to install zip from sdcard
6.) Select BrokenOutRevo1.1.zip
7.) Do not wipe data after flashing!!!
8.) Reboot!
9.) To Block CIQ Logs Requires Reboot After Initial Boot
You should now have a fully rooted zv8 phone with CWM and can give yourself a pat on the back.
if i forgot to mention things please let me know. this was just my process which worked after much troubleshooting so i thought i'd share it with you all.
My method
Just for people who might be looking for other ways or are a few steps into it and wondering how to proceed, here is my successful method (GingerVolt -> BrokenOut 1.1):
All of the apps, files, and such are found in the various other threads so I will just summarize without links:
1 - Using LGNPST, push the ZV7 .tot file.
2 - Using the OLD AIO, root it.
3 - Using the OLD AIO, install STOCK recovery.
4 - Use Terminal Emulator to echo/create the /data/local.prop
5 - Go to settings->about phone->update and check for new update (and then let it update)
6 - Once you have updated via OTA, use Root&Recovery from the NEW AIO.
7 - Reboot recovery and wipe data
8 - After wiping data and without exiting CWM, flash BrokenOut.
That is what worked for me, I hope it might help others because BrokenOut is frickin awesome (thanks again MT).
LeadPharmer said:
Just for people who might be looking for other ways or are a few steps into it and wondering how to proceed, here is my successful method (GingerVolt -> BrokenOut 1.1):
All of the apps, files, and such are found in the various other threads so I will just summarize without links:
1 - Using LGNPST, push the ZV7 .tot file.
2 - Using the OLD AIO, root it.
3 - Using the OLD AIO, install STOCK recovery.
4 - Use Terminal Emulator to echo/create the /data/local.prop
5 - Go to settings->about phone->update and check for new update (and then let it update)
6 - Once you have updated via OTA, use Root&Recovery from the NEW AIO.
7 - Reboot recovery and wipe data
8 - After wiping data and without exiting CWM, flash BrokenOut.
That is what worked for me, I hope it might help others because BrokenOut is frickin awesome (thanks again MT).
Click to expand...
Click to collapse
Looks good.. although if you did step 1 using LGNPST you don't need step 3. The .tot contains the stock recovery.
I had every problem you could think of (all problems liste here) and this is my method that finally worked:
1 - Using LGNPST, push the ZV7 .tot file.
2 - Factory reset, just in case
3 - Using the OLD AIO (Root&RecoveryAIO), root it (option 1 only!).
4 - Use Check Root app to make sure you have root
5 - Use fileslick app to Change folder permissions and move local.prop file app to
- Open fileslick, click actions, and click show root
- Swipe all the way left until you are at root and see /data folder
- Tap the data folder so it has a green check and then hit actions and select "permisions"
- Check everything in that menu (This will make it so you don't has any permission denied menus when moving the local.prop)
- Put the local.prop file from the "data" folder in the ZV7toZV8Root.zip by tapping it in fileslick, navigating back to the "/data" folder you just set permissions for, clicking "actions" and clicking "copy file to this location"
6 - Go to about this phone in the settings app and check for updates to update ZV8
7 - After reboot use ZV8CWMRecovery.bat (option 1) to install clockwork
8 - After reboot go back and use OLD AIO (Root&RecoveryAIO) to reboot to recovery (option 7)
9 - Reboot recovery and wipe data
10 - After wiping data and without exiting CWM, flash BrokenOut.
11 - DON'T WIPE DATA AFTER FLASH
Here are instructions on how to upgrade from Android 2.3.6 Gingerbread (build 6.13.219) to Android 4.0.4 Ice Cream Sandwich (build 6.16.206). This is an official build pulled from a Motorola server.
WARNING!!! ONCE YOU INSTALL THIS UPDATE, YOU CANNOT REVERT TO 6.13.219 OR 6.13.215 VIA FASTBOOT. ATTEMPTING TO DO SO WILL RESULT IN A BRICK. YOU MAY ALSO BE TAKEN OFF THE OFFICIAL VERIZON UPGRADE PATH. USE AT YOUR OWN RISK.
Android 4.0.4 System Version 6.16.206
Blur_Version.6.13.219.XT894.Verizon.en.US.zip (354.9 MB)
Blur_Version.6.13.219.XT894.Verizon.en.US.crc (10 bytes)
DOWNLOAD
INSTRUCTIONS:
(If you have never edited your build.prop file or modified the contents of your /system folder, you can most likely skip step 1.)
If you have an external SD card:
Flash the 6.13.219 fastboot file (instructions here) and, if desired, use the Droid 4 Utility to obtain root (instructions here)
(To keep root) Open Superuser, click the Settings icon, and update the su binary
Download/extract D4ics6.16.206.zip and copy only Blur_Version.6.13.219.XT894.Verizon.en.US.zip to your phone's external SD card
(To keep root) Install OTA RootKeeper, select "Protect root", then "Temp. un-root", then "Restore root"
Power off your phone, then hold the volume up, volume down, and power buttons at the same time until you see the bootloader menu
Use the volume down button to navigate to "Recovery" then use the volume up button to select it
When you see the android/triangle, press both volume buttons together
Select "apply update from sdcard" then press the power button
Select the zip file and wait for the installation to finish
Reboot
(To keep root) Open OTA RootKeeper and select "Restore root"
If you do not have an external SD card (root required):
Flash the 6.13.219 fastboot file (instructions here) and use the Droid 4 Utility to obtain root (instructions here)
(To keep root) Open Superuser, click the Settings icon, and update the su binary
Download/extract D4ics6.16.206.zip and copy the enclosed zip and crc files to your phone's internal storage (do not change the file names)
Install ROM Manager
Install ES File Explorer, go to Settings, and check "Root Explorer" and "Mount File System"
Move the zip and crc files from internal storage to the /cache folder
(To keep root) Install OTA RootKeeper, select "Protect root", then "Temp. un-root", then "Restore root"
Open ES File Explorer again, navigate to the /cache folder, click on the zip file, and open with ROM Manager
Select "OK" when you see the Reboot and Install message and wait for the installation to finish
Reboot
(To keep root) Open OTA RootKeeper and select "Restore root"
I wonder if there is a way to use the kexec exploit to make a rom out of this, with custom kernel.
There is no kernel source available to compile custom kernels for Motorola ICS builds, even if kexec were working on CDMA/LTE variants, which it isn't yet, so there is no work being done to debug or fix the current release of the kexec exploit until the ICS 3.0 kernel source drops.
Say you install this leaked ics and the OTA ics comes out... then the OTA ics is by far better then leaked current ics.... I know there is not a way to predict the future... what then do you'll think there will be a way to obtain said OTA update.....?
Sent from my DROID4 using XDA
So, I'm struggling to figure out how an OTA can prevent downgrading by fastboot files. The only thing I can think of is that it updates the kernel in such a way that it isn't compatible with the previous builds and the locked bootloader keeps one from reverting the kernel change. Is that correct? The other thing I don’t understand is how it prevents future updates. I can't figure out any mechanism for that. I would love to get ICS early, but not if there is no way to upgrade in the future.
lorddunlow said:
So, I'm struggling to figure out how an OTA can prevent downgrading by fastboot files. The only thing I can think of is that it updates the kernel in such a way that it isn't compatible with the previous builds and the locked bootloader keeps one from reverting the kernel change. Is that correct? The other thing I don’t understand is how it prevents future updates. I can't figure out any mechanism for that. I would love to get ICS early, but not if there is no way to upgrade in the future.
Click to expand...
Click to collapse
Someone correct me if I'm wrong, but when you start flashing with a fastboot file, there are a certain number of specific partitions that are flashed individually. It's my understanding that this update changes the partitions in some way, so if you try to flash a Gingerbread file, it will expect certain partitions that aren't there any more.
OTA updates are always from one specific version to another. If VZW decides to make the official ICS build anything other than 6.16.200, then when the next update is released however long down the line, it will only push to devices running that particular build.
Doesn't fastboot allow you to change partition sizes? You could try that (don't you have a bricked D4? )
Also, even though we don't have source for the newer kernels, would it be possible to use the kernel from the leak (no changes), or is this just not possible w/out source?
podspi said:
Doesn't fastboot allow you to change partition sizes? You could try that (don't you have a bricked D4? )
Click to expand...
Click to collapse
I'm sure it wouldn't be too difficult for a developer to create a fix similar to the one Timmy10shoes developed for the Bionic.
And VZW sent me a replacement so I was only without my D4 for a day
What version of kernel is included in this rom?
So have people been able to successfully install ICS and keep root with this method? Does safe strap install?
JKingDev said:
So have people been able to successfully install ICS and keep root with this method? Does safe strap install?
Click to expand...
Click to collapse
Yep. I upgraded and kept root. I haven't tried safestarp cuz there's no point right now since there are no roms for the leak yet but I don't see why it wouldn't work.
I upgraded with root intact and I installed Droid 4 Bootstrap recovery and it works.
I made a backup of the ICS install successfully but have not tried restoring it yet.
Grizzy3 said:
Yep. I upgraded and kept root. I haven't tried safestarp cuz there's no point right now since there are no roms for the leak yet but I don't see why it wouldn't work.
Click to expand...
Click to collapse
Thanks! I upgraded and have been running this and it is working great. Well worth the risk. Cant wait to see hashcode's CM builds based on this kernel.
Safe strap would not be too useful without ROMs to flash but it would be useful to backup/restore so I can try modifying system files/bloat removal and have a back to use in case something goes wrong. I did a mod to make the external sdcard the regular sdcard directory and I want to figure out how to add percentage to the battery indicator. There is a mod for this made for the razr with a similar leaked ICS build so I might try it.
JKingDev said:
Thanks! I upgraded and have been running this and it is working great. Well worth the risk. Cant wait to see hashcode's CM builds based on this kernel.
Safe strap would not be too useful without ROMs to flash but it would be useful to backup/restore so I can try modifying system files/bloat removal and have a back to use in case something goes wrong. I did a mod to make the external sdcard the regular sdcard directory and I want to figure out how to add percentage to the battery indicator. There is a mod for this made for the razr with a similar leaked ICS build so I might try it.
Click to expand...
Click to collapse
I actually don't think the safestrap we have now would work on the leak because they had to release a new safestrap specifically for the razr ics leak. But if you do try it let us know if it works out.
Did anybody lose root?
Sent from my DROID4 using XDA
I lost root. Apparently if you don't update the SU binary before you save root on the 2.3 rom, you may not be able to restore it when you upgrade to 4.0.4.
detox702 said:
I lost root. Apparently if you don't update the SU binary before you save root on the 2.3 rom, you may not be able to restore it when you upgrade to 4.0.4.
Click to expand...
Click to collapse
How do you update the SU binary?
GermanGuy said:
How do you update the SU binary?
Click to expand...
Click to collapse
Open the SU app and go to preferences. Down towards the bottom you will see an option to check for updates.
Droid 4 4.0.4
jy3ng4 said:
Here are instructions on how to upgrade from Android 2.3.6 Gingerbread (build 6.13.219) to Android 4.0.4 Ice Cream Sandwich (build 6.16.206). This is an official build pulled from a Motorola server.
WARNING!!! ONCE YOU INSTALL THIS UPDATE, YOU CANNOT REVERT TO 6.13.219 OR 6.13.215 VIA FASTBOOT. ATTEMPTING TO DO SO WILL RESULT IN A BRICK. YOU MAY ALSO BE TAKEN OFF THE OFFICIAL VERIZON UPGRADE PATH. USE AT YOUR OWN RISK.
Android 4.0.4 System Version 6.16.206
Blur_Version.6.13.219.XT894.Verizon.en.US.zip (354.9 MB)
Blur_Version.6.13.219.XT894.Verizon.en.US.crc (10 bytes)
DOWNLOAD
INSTRUCTIONS:
(If you have never edited your build.prop file or modified the contents of your /system folder, you can most likely skip step 1.)
If you have an external SD card:
Flash the 6.13.219 fastboot file (instructions here) and, if desired, use the Droid 4 Utility to obtain root (instructions here)
(To keep root) Open Superuser, click the Settings icon, and update the su binary
Download/extract D4ics6.16.206.zip and copy only Blur_Version.6.13.219.XT894.Verizon.en.US.zip to your phone's external SD card
(To keep root) Install OTA RootKeeper, select "Protect root", then "Temp. un-root", then "Restore root"
Power off your phone, then hold the volume up, volume down, and power buttons at the same time until you see the bootloader menu
Use the volume down button to navigate to "Recovery" then use the volume up button to select it
When you see the android/triangle, press both volume buttons together
Select "apply update from sdcard" then press the power button
Select the zip file and wait for the installation to finish
Reboot
(To keep root) Open OTA RootKeeper and select "Restore root"
If you do not have an external SD card (root required):
Flash the 6.13.219 fastboot file (instructions here) and use the Droid 4 Utility to obtain root (instructions here)
(To keep root) Open Superuser, click the Settings icon, and update the su binary
Download/extract D4ics6.16.206.zip and copy the enclosed zip and crc files to your phone's internal storage (do not change the file names)
Install ROM Manager
Install ES File Explorer, go to Settings, and check "Root Explorer" and "Mount File System"
Move the zip and crc files from internal storage to the /cache folder
(To keep root) Install OTA RootKeeper, select "Protect root", then "Temp. un-root", then "Restore root"
Open ES File Explorer again, navigate to the /cache folder, click on the zip file, and open with ROM Manager
Select "OK" when you see the Reboot and Install message and wait for the installation to finish
Reboot
(To keep root) Open OTA RootKeeper and select "Restore root"
Click to expand...
Click to collapse
I found a Droid 4 Utility jellybean. The utility is very easy to use. But it flashes 4.1.2. I need 4.0.4. How can I downgrade to 4.0.4 on an HTC Droid 4? Please help?
This is for the Motorola Droid 4, try a HTC forum
Sent from my Amazon Kindle Fire using Tapatalk
Hi, I'm having some troubles ...
I have a Karboon Sparkle V
(Android 5.1.1 , Build number: LMY47V) (details of Android version can be found here: http://lifedj.altervista.org/Screenshot_2015-07-09-09-33-58.png )
and I tried to root it!
The problem is that I did an error:
first of all I tried to install Kingroot (starting from my unlocked phone) and then I decided to root it at all but without uninstalling Kingroot (I was unable to uninstall it ... I don't know why).
So, these are the steps I followed:
1. install kingroot
2. follow the following guide to root my phone
http://www.gadgetstroop.com/2015/05/unlock-bootloader-root-karbonn-sparkle-v-androidone-device.html
3. open SuperSU
4. Click on "Continue" at the "SuperSU has to be updated"
5. Click on "Normal" to the following advice
6. Wait -> obtaining "SuperSU failed to update ..... try to reboot"
7. Reboot the system and start again from point 3 (I tried it a lot of time)
8. Install Superuser
9. Update SuperSU from the playstore
10. start again from point 3
11. install "System app remover" (https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp&hl=it)
12. Remove Kingroot
13. Remove superuser
14. Reboot
15. Start again from point 3 (to point 7)
16. Try to install "Root checker" getting "Root access is not properly installed on this device"
17 Factory reset
18. start again from point 3
19. Follow again the guide at point 2
20. start again from point 3
21. Try to install "Root checker" getting again "Root access is not properly installed on this device"
22. Try to download SuperSu update from this site:
https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
23. Recovery reboot and install the downloaded file
24. start again from point 3 (to 7)
25. Install OTA rootkeeper from this site:
http://it.apkhere.com/app/org.projectvoodoo.otarootkeeper
26. open OTA rootkeeper obtaining the following status (OTA rootkeeper results can be found here: http://lifedj.altervista.org/Screenshot_2015-07-09-09-51-49.png )
And now I don't really know what can I do to achieve the root of my smartphone ... or maibe, to unroot it (in order to let me try again the guide).
Thank you in advance for your support!
Part of the problem was solved ... but not at all
After some trials now I have SuperSU that works!
Now it provides root access, but continues to tell me that it has to be updated ... even if there is the last available version!
What can I do?
Here uis the procedure I followed:
I installed "Kingroot" again, then I used the in app feature to deactivate root.
So I uninstalled it.
Then, after a reboot, I found that SuperSU had disappeared!
So I entered the recovery mode and I reinstalled it.
I tried to re-flash the app a lot of times but the result is always the same!
Root your phone again , then go to Play Store and download busybox then install busybox. After confirming that busy box has indeed been installed go back to the Play Store and download a app called SUPERSUME an install it.. After installed open it and press the circular button. This will uninstall all of Kingroots dependencies and then install SuperSu with updated binaries for you.
If this helps you out please hit the thanks button because that will help me.? Enjoy!
Got my new international version of the S4 (i9295) yesterday. Rooted and flashed a custom ROM this afternoon in about 1 hour. Below are the steps that I took to do this.
1.) Preparation: connect a usb micro SDcard reader (with a card in it) to your laptop and load the following files onto the sdcard,
-Towelroot.apk,
-SuperSU.apk
-terminal emulator such as jackpal.androidterm-1.0.70-71-minAPI4.apk
-root browser such as co.jrummy.root.browserfree.apk
-TWRP custom boot image file, Philz boot, recovery.img
-custom rom such as cm-12.1-20150715-NIGHTLY-jactivelte.zip
-Google Applications (GAPPS)2.) Next, turn off your phone, remove the SIM card, insert the sdcard card with the above applications copied onto it.
3.) Turn on your phone. Go to Settings and click the "More" tab. Then go into security and check "Unknown Sources."
4.) Log onto a wifi network to gain internet access.
5.) Go to Applications, select the "My Files" browser and go to the sdcard. Locate Towelroot.apk that you just loaded on the card. Install it and run it. Towelroot will want to talk to the mothership regarding precisely how to root your device. This is okay.
6.) Install terminal emulator, and root browser.
7.) Install SuperSU. Open the SuperSU app and allow application to update binaries.
8.) Open terminal emulator, type in "dd if=/storage/extSdCard/recovery.img of=/dev/block/mmcblk0p21". Now type "reboot".
9.) TWRP should now be installed.
10.) Shut down the phone. Now, hold down the volume up and power buttons at the same time to boot into Philz TWRP bootloader.
11.) Select "Install zip", then select "Choose zip from storage/sdcard1", now choose the custom ROM that you have copied to the root of your external sdcard. Note: I had to do a factory reboot at this point as I was getting an "detected filesystem ext4 for /dev/block/platform/..." error message. I used the "factory reset" option under "wipe and format options" in TWRP with no problems. After this I was able to install the most recent 12.x Cyanogenmod rom with no problem.
12.) Repeat step 11 for GAPPS package.I have moved 5 of the 7 applications listed in step 1 into a zip archive (12.9mb) and uploaded it. The only applications missing are the custom ROM (268mb), and recent GAPPS collection (75mb).
Sources for the resources in step 1 are,
GAPPS- https://itvends.com/gapps/
Cyanogenmod nightlies- http://download.cyanogenmod.org/?type=nightly&device=jactivelte
Towelroot- https://towelroot.com/
SuperSU- https://download.chainfire.eu/396/supersu/
Terminal emulator- http://www.apkmirror.com/apk/jack-p...erminal-emulator-1-0-70-android-apk-download/
Root browser (JRummy apps)- http://jrummy-apps.com/
Philz custom TWRP boot image file- goo.im/devs/philz_touch/CWM_Advanced_Edition/jflte
Have fun.
Hey everyone, sorry if this has been covered already but I don't recall seeing these instructions anywhere. After doing the standard tethered re-root every time there was an OTA update I discovered that you don't need to tether. I've been doing it this way for the past several updates and it has worked perfectly every time. Not sure if this will work for major version updates though. As usual, YMMV, back up your data, I'm not responsible for data loss, bricks, etc. etc.
Install TWRP and Magisk the usual tethered way the first time you root. There's no way around this.
When an OTA update comes out, allow it to download but do not let it install itself.
Download the latest TWRP Fajita zip to your device if you don't already have it. https://dl.twrp.me/fajita/
Reboot to recovery and decrypt if necessary.
Back up your data if you don't feel like living on the edge.
Hit the install button and browse to /sdcard/.Ota and select the latest zip, which was downloaded automatically earlier.
Tap the button to add another zip, and select the TWRP zip that you downloaded earlier.
Swipe to install, reboot when done. It is crucial to install both zips without rebooting in between, otherwise you'll have to tether.
After the post-boot update process completes, open the Magisk Manager app and hit the Install button for Magisk (not Magisk Manager). Choose to download zip only.
Reboot to recovery and decrypt if necessary.
Hit the install button and browse to /sdcard/Download and select the Magisk zip that you just downloaded. Swipe to install, then reboot.
Magisk app should now show Magisk is installed again.
Profit.
If we have twrp retention script we simply can retain magisk and twrp, i think everyone knows that
what is the twrp retention script? have you a link?