Hi Everyone, How I can install a custom recovery in a500 On ICS
The Build Number is : 1.031.00_WW_GEN1
Image Version is : RV03RC01_WW-GEN1
If You help me i can help you :highfive:
Sorry For My Bad English
:silly:
________________________________________
Acer A500 Stock ICS
HTC Incredible 2 Stock ( For Now)
1. Install acer recovery installer from market. This apk is free.
2. Keep with you the .zip or .image file of recovery which you want to install and place it in sd card.
3. Run the apk and select install from sd card.
4. If apk do not detect .zip file in your sd card than extract recovery.image from that file and store it in sd card.
---------- Post added at 11:39 AM ---------- Previous post was at 11:27 AM ----------
You can get custom recovery files from tegraowners.com or any other custom recovery in development section.
jancarlos1597 said:
Hi Everyone, How I can install a custom recovery in a500 On ICS
The Build Number is : 1.031.00_WW_GEN1
Image Version is : RV03RC01_WW-GEN1
Click to expand...
Click to collapse
The real answer is if you have ICS, to install a custom recover or custom kernel you must have an unlocked bootloader.
The following resources are related to the new bootloader, a quick read of the OPs of the first two are highly recommended, even if you install with the third link. (This is to have a highlevel idea of what you are changing on your device, as it will help you find what you need to look closer at in future if something goes wrong, or possibly prevent a problem in the first case)
bootloader thread
civato's guide
Afterota tool (windows users bootloader install tool)
If you already have the unlocked bootloader installed, but can't boot into recovery:
This is likely because you have a stock ICS rom overwritting recovery with the stock recovery in every boot; either use fastboot or (if you have root) a program such as acer recovery installer to force the install of a recovery and immediately reboot into it. (Most bootloader installers will also install a recovery that you can immediately boot into)
Once in recovery you can backup/restore/or install a rom modified to prevent the overwrite of recovery. (More advanced users can stop this from adb by removing some files)
Personally I use a lightly modified version of the stock rom you are using now:
http://forum.xda-developers.com/showthread.php?t=1661492
it ought to be safe to do a no wipe update to that and receive a more expected environment with a custom recovery, optional custom OC kernel, and busybox support.
However if you explore the dev section, many other (both more and less modified) versions of ICS roms exist. Themed and otherwise. So feel free to explore.
Closed
:good: MOD Please Close This, I Fix This.
Related
1. Place the superuser.zip file attached at the end of the post on your sd card.
2. Flash recovery in bootloader with "fastboot flash recovery <filename>.img". I recommend CWM 5.0.2.3 found in this thread - http://forum.xda-developers.com/showthread.php?t=988686&highlight=recovery
3. Go to recovery, in "mounts and storage" select "mount system" and then flash su-install.zip (EDIT : Mounting system not necessary, the script does it automatically while flashing the zip, but just in case)
4. Fix Permissions and reboot system.
5. Use any root explorer (i recommend ROM Toolbox, free in market) and go to /etc and either rename "installrecovery.sh" to "installrecovery.sh.old" or just delete it (its not needed).
6. There it is - Rooted ICS with a recovery that sticks.
EDIT -- IF, by any chance, after following the above steps, you find that you're stuck without a recovery (android exclamation screen), just flash a recovery via fastboot and you'll be fine. This time the recovery WILL stick. I think its something to do with the su-install.zip. I dont know for sure because I found it off the internet, its not mine.
Also, I did the superuser market update and I DID NOT lose root. I have an I9020T. So others with the same can safely update, imo.
Thanks to ab.grafix for being a part of the team.
IMPORTANT -- The su-install.zip posted previously is NOT mine. I didnt know who made it but just found out. All credit to dzo binary and Chamb'. I just made a guide coz it worked for me and I thought it might help others too.
Tested on I9020T and I9023
Don't forget to click on that thanks button if this helped.
UPDATE -- Superuser was updated by ChainsDD to support ICS 4.0.3. Thank you ChainsDD! Updated zip is now attached.
So now that we have root we need a overclocked kernel...
Sent from my Nexus S using XDA App
works great but very old cwm
Worked as described. Thanks !
Old cwm? Wich version? Is it possible to flash the latest one with rom manager?
So I am on ICS alpha13.
I9023
- wipe everything and Flash Android 2.3.6/GRK39F/XXKF1 Radio/KA3 Bootloader via clockworkmod
- Reboot in stock recovery and flash stock ICS
- Boot in ICS enable debug mode
- Run the bat follow instruction?
Is it ok?
Thanks
Hi will it work on the rogers i9023a? Can someone tell me which stock ICS to flash?
Thanks
Thanks, it worked and nothing was wiped since I was already unlocked. With apps that require root you no longer get asked for root permission nor do they show in app list in superuser but it seems to have root for now
For the guys using linux (like me ) , just download the archive in the first post , retrieve from there 2 files: root.zip and recovery.img and use them with your current ADB setup.
HOW-TO:
Prerequisites: you have installed Android SDK, fastboot and you have set-up correctly the udev (ubuntu).
1. Place the above mentioned 2 files in the working directory
2. reboot in bootloader mode (vol-up + power)
3. connect USB cable
4. run "./fastboot-linux-i386 flash recovery recovery.img"
5. reboot bootloader
6. reboot recovery
7. mounts and storage -> usb mass storage
8. copy root.zip in the phone storage
9. go back -> install zip from sd card -> root.zip
DONE !
I just tested and is working fine.
If there are newbies out there trying to understand the nonsense I wrote, try following the rooting guide for Gingerbread and just use the 2 files I mentioned in this post instead of the ones in the archive for gingerbread.
when in BL i dont have Unlock option :|
Thanks for your effort.
But I'm curious about the flashable zip file.
What's the difference of the zip file between the orignal superuser ?
And did the recovery do some magic which CWM can't do?
After reading the script , I just see the zip is important ,maybe the recovery is doing some magic too.
I'll just flash the zip and see what happen.
ro_explorer said:
For the guys using linux (like me ) , just download the archive in the first post , retrieve from there 2 files: root.zip and recovery.img and use them with your current ADB setup.
HOW-TO:
Prerequisites: you have installed Android SDK, fastboot and you have set-up correctly the udev (ubuntu).
1. Place the above mentioned 2 files in the working directory
2. reboot in bootloader mode (vol-up + power)
3. connect USB cable
4. run "./fastboot-linux-i386 flash recovery recovery.img"
5. reboot bootloader
6. reboot recovery
7. mounts and storage -> usb mass storage
8. copy root.zip in the phone storage
9. go back -> install zip from sd card -> root.zip
DONE !
I just tested and is working fine.
If there are newbies out there trying to understand the nonsense I wrote, try following the rooting guide for Gingerbread and just use the 2 files I mentioned in this post instead of the ones in the archive for gingerbread.
Click to expand...
Click to collapse
In fact, you can use any recovery image you want, including the latest clockwork for example. I used TWRP to do this and it worked just fine. On linux, just flashed root.zip.
I've done it, thanks a lot. I've also replaced the recovery.img file with the last cmw and all went well.
Now the rom doesn't show the root permission request toast but it works however.
I'd ask if its possible to manually update the superuser.apk or its better to mantain this one?
sakisds said:
In fact, you can use any recovery image you want, including the latest clockwork for example. I used TWRP to do this and it worked just fine. On linux, just flashed root.zip.
Click to expand...
Click to collapse
Great .. I'll do that because I miss my "old" cwm
EDIT: it worked, thanks!
thanks, working here on 9023. warning for other users - do not update superuser from the app itself, or it'll stop working. at least it did for me, when i updated it to 3.0.3
confirmed working I9020a...
[INFO] Working root for ICS 4.0.3
Credits to Chamb'.
Flash via CWM and you're done.
Tested working for ICS 4.0.3 I9020T.
Enjoy!
Source: http://forum.xda-developers.com/showpost.php?p=20394635&postcount=4
It seems to have worked like a charm, thank you!
I was even able to flash the latest CWM Recovery using ROM Manager
can I flash stock 2.3.6 with cwm?
Im on ics alpha13
Anyone got a download link for the stock 2.3.6?
bratfink said:
Anyone got a download link for the stock 2.3.6?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1063664
Hi guys. Can someone please post a step by step guide for updating a european Xoom to 4.0.2 ICS, then rooting it and flashing the Nightlies kernel from Team EOS? I couldn't find a tutorial just yet so I would appreciate every help I can get.
Greetings
Faceball
Not to be mean… but stop being lazy. I mean everything you are asking for is basicaly right infront of you.
Sent from my DROID3 using XDA App
Any guide that shows you how to root + install CWM + Tiamat rom but replace tiamat rom with ICS!
Hey, it's pretty difficult to navigate all the threads and guides sometimes, I'm a new to XDA as well.
This thread should help you out, there's a breakdown below from me as well
If anything below is wrong, could someone correct me - my Xoom arrives today and below is what I understand the process to be from my reading ...
http://forum.xda-developers.com/showthread.php?t=1249798
1. Install Motorola USB drivers, Java SDK and Android SDK tools (for adb and fastboot)
3. Unlock the device or "bootloader") allows the flashing or replacement of recovery and boot images
4. Install a modified recovery image (ClockWorkMod recovery for Android). This is known as CWM and is an app that allows you to easily flash new ROMS and Kernals etc to the device.
5. Root the device (Allow r/w access to the device filesystem)
6. Do Nandroid (full backup) with CWM (Optional)
7. Party on and Flash new ROMS / Kernals etc!
====
You can restore your device to Stock by downloading a stock image for your Xoom model and flashing via Fastboot...
I'm not allowed to post in the Development forum, so I will ask my question here:
I updated to ICS successfully by changing the update-script in the update.zip.
I removed the lines which delete the recovery or reinstall it; I deleted the whole recovery folder as well.
But now I can't get back into CWM, it just doesn't start, it stops during "booting into recovery kernel" ( it was not overwritten).
So, is the ICS update changing so much in the system that CWM stops working? (through google I found something about different kernels, but didn't understand it)
I think I'll try to install the original recovery, better than nothing.
(this may also be a warning to people who think that they can roll back to honeycomb with CMW - apparently, once the update was succesfull that's it with honycomb)
daniel
I think it might have to do with the updated bootloader that comes with the ICS OTA.
I just had a look at the "blob"-file in the update.zip and was able to unpack it with the BlobTools for the Asus Transformer (https://github.com/AndroidRoot/BlobTools). Inside it was an EBT-file, which, according to my research, should be an image for the bootloader.
Looking through the strings in the blob, it seems to be one indeed: "Bootloader Start at:%d ms".
So I guess the new bootloader loads the recovery system from a different address or partition than the HC bootloader, which is why CWM won't start.
So adding the lines for flashing the OTA recovery-from-boot.p to the updater-script and re-running the update over HC should theoretically solve the issue. Or, if that doesn't work, flash the recovery image manually and flash the blob via nvflash (I'm not sure, though, if that is possible without the keys).
Maybe then someone with enough reverse-engineering skills could determine what has changed in the update and patch CWM accordingly...
Similar Issue..
In CWM, from [ROM][JB] CM10 for Ideapad K1 [Updated 8/29] (I'm running version 2). Whenever I attempt to use any of the features it asks me to install the recovery (which I know I have, and can boot to it) and asks me to choose my device.. Which it then only gives me the ASUS TRANSFORMER as an option.
So, on Version 1 of this build, some time back. I said, what the heck, why not. Let it do its thing,rebooted.. and the system would not ever boot. Just hung at the CM10 boot animation.
Whatever. I used the NVFlash version, got it back up and running. Rebooted in to CWR, and flashed the [ROM]CM10 for Ideapad K1 version 2 CWM version on it. Id really rather not have to wipe my device again to go to version 3, or 4.. and I don't want to get stuck at a boot animation again.
Any thoughts?
It will work again. Just find the file "k1recovery" from the system/bin folder of a rom that has it. Push it in the device, fix permissions and execute it using ADB. The combination Power Btn & VOL+ doesn't work on some devices.
Rooting Kindle Fire HDX 7 32gb 3rd Gen Fire OS 13.3.2.1
Airplane Mode ON WIFI Off
Kindle Fire ADB Composite Drivers must be installed to working PC
In KFHDX Settings
Set Enable ADB - ON
Set Apps from unknown sources - ON
Faznx's KF-HDX Toolkit v0.95
https://www.androidfilehost.com/?fid=95832962473395302
KFHDX ToolKit v0.95.zip
MD5: 3C1D7DB855E54A39BF2FD59BE6ABA9DC
SHA-256: 614A0D077BEC8B85F6D6B377D2D18EB719AB9ED15B08B41CD5 8968BEED653C0C
Rooted KFHDX using Towelroot in above toolkit. - No Issues
Then applied:
1> SuperSU v2.14 installer in Faznx's KF-HDX Toolkit v0.95 - No Issues
2> Over the air update blocker and re-enabler for all current rootable versions in Faznx's KF-HDX Toolkit v0.95 - No Issues
Airplane Mode ON WIFI Off
Use adb to install ES File Explorer
http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
ADB install (installs application) -- adb install c:\com.estrongs.android.pop.apk - No Issues
Checked in ES File Manager to make sure I had root.
Next rename the /system/etc/security/otacerts.zip file - one issue - resolved
Even though I ran the disable OTA updates, I am concerned that some post I have read said their system was update even though they renamed.
I think now it's possible they get around us by running an MD5 hash on files in that folder and compare to the hash they store for that version.
The better idea may be to move that file out of that folder. I did just that.
Here are the directions to rename:
see the contents of that folder with adb shell ls -Ral /system/etc/security
Example:
C:\Users\davcam\AppData\Local\Android\sdk\platform-tools>adb shell ls -Ral /system/etc/security
/system/etc/security:
drwxr-xr-x root root 2014-02-07 04:23 cacerts
-rw-r--r-- root root 1337 2014-02-07 04:23 otacerts.zip
Before you can rename this file you must set the \ and \system file systems to r/w - then you can rename or mv the file.
When completed, change \ and \system file systems back to ro
Next : Safestrap
https://goo.im/devs/Hashcode/thor/safestrap/
I tried Safestrap-Thor-3.72.apk and it did not seem to work. I unistalled recovery and Safestrap-Thor-3.72.apk.
I was able to successfully install Safestrap-Thor-3.75-os3.2.4-B02.apk, install recovery, boot into recovery, backup up stock, create a new rom slot,
change to that Rom slot and restore stock backup into that slot.
Now on startup i get the Safestrap screen.
One thing I noticed was that the stock values for the rom slots are a little small, so keep that in mind.
Thanks to everyone on XDA Forums, especial to EncryptedCurse for the terse, meaningful tips., Faznx's KF-HDX Toolkit v0.95, Geohot's Towelroot,
hashcode0f's Safestrap, OTA disable, and Supersu.
Current Status:
Using a copy of stock on a somewhat larger partition, no otacerts.zip file
Next steps:
0> Thank and donate to the developers I mentioned above.
1> Airplane mode OFF, wifi ON , register with Amz
1.1> Get GAPPS installed on this copy of stock I'm booting into
2>to see if possible to load a CM11 image into one or my bran new slots.
Question: If Amazon were able to push an update to me, would I just be able to recover to my stock image and move on?
Thanks for the help and education!
reggie9 said:
Next steps:
0> Thank and donate to the developers I mentioned above.
1> Airplane mode OFF, wifi ON , register with Amz
1.1> Get GAPPS installed on this copy of stock I'm booting into
2>to see if possible to load a CM11 image into one or my bran new slots.
Question: If Amazon were able to push an update to me, would I just be able to recover to my stock image and move on?
Thanks for the help and education!
Click to expand...
Click to collapse
Dont try to install CM11 with Safestrap!! It wont work, and you will brick your device! You have to install TWRP 2.8.4.0 and only then you can install CM11 safely.
If your device get FW 4.X.X, you lost root and ability to install custom roms through custom recovery (Safestrap, TWRP 2.8.4.0) - and only way to get the root again is rollback from 4.x.x to 3.2.7-8 (by amazon tech support), and then you can use only Safestrap, so no CM11 or Nexus 2.0.4 ROMs for FW 3.2.7-8!
Edit: Looks like jeryll already said it.
jeryll said:
Dont try to install CM11 with Safestrap!! It wont work, and you will brick your device! You have to install TWRP 2.8.4.0 and only then you can install CM11 safely.
If your device get FW 4.X.X, you lost root and ability to install custom roms through custom recovery (Safestrap, TWRP 2.8.4.0) - and only way to get the root again is rollback from 4.x.x to 3.2.7-8 (by amazon tech support), and then you can use only Safestrap, so no CM11 or Nexus 2.0.4 ROMs for FW 3.2.7-8!
Click to expand...
Click to collapse
Thanks! I appreciate the heads up. Any idea where I can locate TWRP 2.8.4.0 for this device?
Sorry - Found it here: http://forum.xda-developers.com/kindle-fire-hdx/development/recovery-twrp-2-8-1-0-thor-t2986004
Reggie9
jeryll said:
Dont try to install CM11 with Safestrap!! It wont work, and you will brick your device! You have to install TWRP 2.8.4.0 and only then you can install CM11 safely.
If your device get FW 4.X.X, you lost root and ability to install custom roms through custom recovery (Safestrap, TWRP 2.8.4.0) - and only way to get the root again is rollback from 4.x.x to 3.2.7-8 (by amazon tech support), and then you can use only Safestrap, so no CM11 or Nexus 2.0.4 ROMs for FW 3.2.7-8!
Click to expand...
Click to collapse
Everything has seemed pretty clear up to now, but I am trying to understand what I should do next? I have Safestrap 3.72 beta installed and I'm running off of a backup of stock running in ROM-Slot 1.
Do I need to wipe rom slot one, remove recovery and uninstall Safestrap? Then install TWRP? Can I take a backup of my current ROM Slot one and use it in TWRP. I am looking for a good install post or video for installing TWRP 2.8.4.0 on KFHDX. It appears that TWRP does not use the concept of ROM slots but actually wipes the main system (that has been backed up to the builtin recovery area?) Then installs an image on the main system? I understand basically what Safestrap is doing, but not TWRP.
reggie9 said:
Everything has seemed pretty clear up to now, but I am trying to understand what I should do next? I have Safestrap 3.72 beta installed and I'm running off of a backup of stock running in ROM-Slot 1.
Do I need to wipe rom slot one, remove recovery and uninstall Safestrap? Then install TWRP? Can I take a backup of my current ROM Slot one and use it in TWRP. I am looking for a good install post or video for installing TWRP 2.8.4.0 on KFHDX. It appears that TWRP does not use the concept of ROM slots but actually wipes the main system (that has been backed up to the builtin recovery area?) Then installs an image on the main system? I understand basically what Safestrap is doing, but not TWRP.
Click to expand...
Click to collapse
You are on compatible firmware so dont complicate things so much If you want to understand how Safestrap or TWRP itself work - google is your friend, you will certainly find plenty of information about how things works: here is little introduction about differencies between them, not all of course...
And here is little something from ggow about how to install twrp and remove safestrap, you can later find safestrap slot image files in data/media/safestrap - and after you have functional TWRP 2.8.4.0, you can delete safestrap folder safely and free some space taken by these image files
Normal way is how TWRP 2.8.4.0 works (IMHO) - only one big playground managed by mighty TWRP recovery always accessible by shortcut when you made mistake and need to repair something...
Safestrap uses multiple slots for (un)modified stock roms simply because is too dangerous to play with stock rom on systems with locked bootloader, so you can play with slot rom instead of stock where small mistake leads to different types of bricks - some repairable, some not
And yes you can make a backup of your current ROM and use it later with TWRP, but here comes catch, Safestrap only backups system and data partition, not boot (contains kernel), so I recommend after you install your preferred CM11 or Nexus 2.0.4, restore only DATA part of your backup
jeryll said:
You are on compatible firmware so dont complicate things so much If you want to understand how Safestrap or TWRP itself work - google is your friend, you will certainly find plenty of information about how things works: here is little introduction about differencies between them, not all of course...
And here is little something from ggow about how to install twrp and remove safestrap, you can later find safestrap slot image files in data/media/safestrap - and after you have functional TWRP 2.8.4.0, you can delete safestrap folder safely and free some space taken by these image files
Normal way is how TWRP 2.8.4.0 works (IMHO) - only one big playground managed by mighty TWRP recovery always accessible by shortcut when you made mistake and need to repair something...
Safestrap uses multiple slots for (un)modified stock roms simply because is too dangerous to play with stock rom on systems with locked bootloader, so you can play with slot rom instead of stock where small mistake leads to different types of bricks - some repairable, some not
And yes you can make a backup of your current ROM and use it later with TWRP, but here comes catch, Safestrap only backups system and data partition, not boot (contains kernel), so I recommend after you install your preferred CM11 or Nexus 2.0.4, restore only DATA part of your backup
Click to expand...
Click to collapse
jeryll - Thanks for the the thoughtful response - will study this. - reggie9
The objective of this post is to explain how to currently install a custom ROM in our device. (for total newbies like me, you can also refer -among others- to my previous post). I give the general procedure which wipes everything in your device, but you can check various precious posts in xda that variate this procedure.
The codename for our device is "pollux_windy", which is the Wifi-only version. The LTE version (I should probably get the LTE!) is "pollux" and I suppose the general procedure (with the corresponding firmwares to your specific device) will work for any Xperia device. You can also get the general idea from this post.
As a general rule of thumb do not forget after/before every firmware flashing to:
Enable developer mode (explained here)
Enable the USB Debugging mode (explained here)
Trust installation from unknown sources (explained here)
Steps.
A. Unlock the bootloader.
You can refer here and then check that it is successfully unlocked with these steps (taken from here ):
Open the Contacts app.
Click the menu button.
Click Settings.
Long press (for about 5 seconds) somewhere in the empty space just above status bar, as indicated by the red frame in the screenshot below, and then release your finger. A button named Enter service code will then appear in the same area (this may take a few tries).
Click Enter service code. A dialler will appear.
Dial *#*#7378423#*#* . Then go to -> "Service Info" -> "Configuration". If there is:
Bootloader unlock allowed - Yes << this means that your Bootloader is Locked
Bootloader Unlocked - Yes << this means that your bootloader is unlocked
B. Flash a firmware in which you will root the device
Download/install FlashTool.
Download and place to the FlashTool's folder "firmwares" the firmware "SGP312_10.5.A.0.230_VMo UK_IE.ftf". More information here . In sort, download and extract http://d-h.st/MrI and http://d-h.st/ULc
Open FlashTool and connect the powered-off device (USB cable) in Flashmode, holding the Volume Down button while you plugin the usb cable. The FlashTool should say that it is connected in Flashmode. Then flash the 10.5.A.0.230 firmware in it.
C. Gain root to the new firmware
Open the device, complete the setup wizard and connect to a wireless network. You do not have to setup the Google Account since you can download every application googling the respective APK files, but Google Play is easier to use.
Get (click λ) the towelroot APK, install it and run it (click "make it rain"). You should have root, which you can check with a Root Cheker like this one.
Download/Install SuperSU APK (this is actively developed, while SuperUser is abandoned at the moment) as described here.
D. Install a Recovery to easily flash new ROMs
NUT has done excellent work with XZDualRecovery.Follow the instructions for installing it in his thread. In short:
Download the installer, run it and follow its instructions.
Select SuperSU and of course grant access to your computer from your tablet (watch the tablet screen).
E. Download a Custom ROM and Google Apps
I had problems with Cyanogenmod (versions 11 and 12) that I cannot explain. I had no GPS and no media sound from the speakers, but I did have "notifications" sound! I could listen to "media" sounds using headphones, though. So I tried the nightly OmniROM which seems very stable and fast at the moment, with no sound problems and also has a working GPS! You can get it directly from their site (the NIGHTLY I downloaded is omni-4.4.4-20150223-pollux_windy-NIGHTLY.zip which runs just fine). Somewhere I read that PacMan ROM - also works perfectly but I have not tested it yet.
I had device recognition problems from the Recoveries ("Status 7 Error") that I think dear NUT will solve promptly. What I did to solve them is
Upack the ROM zip.
Remove the first line (from assert(...); till the column) of META_INF/com/google/android/updater-script and save the file.
repack the ROM to a zip.
Then copy this zip to your external SD card. If you need google apps (you probably do, to use Google Play instead of other applications like Aptoide), you will also need to download and place to your external SD card the corresponding google apps from here - (I found it in this post - which also explains the different gapps versions)
F. Install the Custom ROM
So now that both the ROM and (optionally) gapps are in the device's SD card:
Enter the Recovery while repeatedly pressing Volume Up or Down while the device boots.
Wipe everything (except the external SD card, obviously --- if you delete the zip files by mistake you must begin again from step B. using the FlashTool to flash the *.230* ftf).
Reboot and setup/enjoy your new ROM.
It seemed that with OmniROM I had lost root access so I had to reinstall SuperSU. I did this by downloading the flashable/installable zip - and flashing/installing it through the recovery.
In the end a did a full backup with the TWRP recovery and one with Titanium backup
Magnus_E said:
The objective of this post is to explain how to currently install a custom ROM in our device. (for total newbies like me, you can also refer -among others- to my previous post). I give the general procedure which wipes everything in your device, but you can check various precious posts in xda that variate this procedure.
Click to expand...
Click to collapse
For installing customs (CM/AOSP/GPe based ROM's), you don't need to install .230 firmware, furthermore you don't need root (except for backup TA procedure), furthermore you don't need XZDualRecovery (cause it works only for Stock and Custom STOCK based rom's - see this post).
So you you only need to flash kernel via fastboot, and then enter recovery (integrated in kernel), and install .zip with custom, SuperSU and Gapps from there.
hello i was following this guide but im stuck on status 7 error, i tried deleting assert but the twrp recovery dont get any answer to "getprop ro.product.device" and it just doesnt proceed...
and Rootk1t i cant find any kernels flashable via fastboot or flashtool can you point one to me? all of the kernels i see are in '.zip's .... i want to have android 6.0 so i think i should have black kernel but how?
bluealef said:
hello i was following this guide but im stuck on status 7 error, i tried deleting assert but the twrp recovery dont get any answer to "getprop ro.product.device" and it just doesnt proceed...
and Rootk1t i cant find any kernels flashable via fastboot or flashtool can you point one to me? all of the kernels i see are in '.zip's .... i want to have android 6.0 so i think i should have black kernel but how?
Click to expand...
Click to collapse
.zips are installed through recovery, .ftf through flashtool.
6.0.1 ROM you can find here.