Database Develop

[Q] Migration to Android 5.0

Hi,
I have a Motorola Moto G XT1068 - Dualsim, german version. I unlocked the bootloader and installed CWM PhilZ. OTA update does not work so I just skipped it until Android 5.0 is out now.
Questions:
1) I am using Titanium Backup Root for backing up my Apps, SMS, phone lists etc. I did not get any support from them if and how it will work on Android 5.0 due to the rumors that root is harder to enable. Any other update strategies, which programs do you use? ADB?
2) Which Rom (Fullrom?) do i have to flash in order to get Android 5.0 via OTA?
Thx for your answers

AFAIK no flashing of ROM is necessary as long as you're on stock. What you need is a stock recovery. I reckon you flash that ASAP.
Also, you might need to look into your system apps and make sure that you haven't deleted/disabled or converted to user apps.
Besides these steps, you'll be fine and will be able to update.

Androphilius said:
Hi,
I have a Motorola Moto G XT1068 - Dualsim, german version. I unlocked the bootloader and installed CWM PhilZ. OTA update does not work so I just skipped it until Android 5.0 is out now.
Questions:
1) I am using Titanium Backup Root for backing up my Apps, SMS, phone lists etc. I did not get any support from them if and how it will work on Android 5.0 due to the rumors that root is harder to enable. Any other update strategies, which programs do you use? ADB?
2) Which Rom (Fullrom?) do i have to flash in order to get Android 5.0 via OTA?
Thx for your answers
Click to expand...
Click to collapse
You have to install stock firmware and re-lock your bootloader. The guide to install stock firmware is on the general sub-forum and should be here.
I suggest using SMS Backup & Restore to backup your SMS. However, I recommend waiting until root is out to flash Android L. Then you can use Titanium Backup to restore your user apps & data.
I'm running L myself so I have to patiently wait for root. Good news though! The Moto X got a root solution by chainfire for Android L already. This means we could get root soon for Moto G.

Thank you for your answers so far.
I downloaded stock rom yesterday and planning to migrate today, due to the fact that a solution for rooting XT1068 comes near.
I just hope i got the right Stock Rom Version for german version and - always a bit worried that someone has put malware in the roms posted on fileshares.
Now I have to find out the right steps with ADB.
Full wipe, wipe cache, wipe dalvik and restore partition required as I am used to do with Samsung crap due to other mounting of sd card? Always did it with CWM the times before and never had to relock bootloader. But I have also read that locking is not required for flashing 5.0.
Okay, lazy saturday, I am going to find it out myself

Androphilius said:
Thank you for your answers so far.
I downloaded stock rom yesterday and planning to migrate today, due to the fact that a solution for rooting XT1068 comes near.
I just hope i got the right Stock Rom Version for german version and - always a bit worried that someone has put malware in the roms posted on fileshares.
Now I have to find out the right steps with ADB.
Full wipe, wipe cache, wipe dalvik and restore partition required as I am used to do with Samsung crap due to other mounting of sd card? Always did it with CWM the times before and never had to relock bootloader. But I have also read that locking is not required for flashing 5.0.
Okay, lazy saturday, I am going to find it out myself
Click to expand...
Click to collapse
Nope, no re locking required. Just do the samsung needful. I had one of its ****ty mobile too. So hi5 there.
Anyways, I don't understand why are doing this stuff. Most probably a flashable zip would be uploaded on XDA the same day or max the next day. Just chillax and wait for the good news to arrive, which I hope is any day now
P.S Oh and also make sure that you don't lock your bootloader at all. Because then you wouldn't be able to unlock it, at least not right now, hence you wouldn't be able to root.

What you are going to do after reciving your OP3T ?

Hello Everyone
I would like to open a discussion about what usually every one do after receiving their new devices ROOT,Launchers,xposed, etc,,
I'm getting my device today so i don't know what exactly i have to do (wait for nougat releasing , which app i need to backup with etc..)
feel free to share our experience i guess many ppl wants to know
Best regards

Unlocking Bootloader, flashing TWRP. Maybe installing xposed, but I dont know yet. Just need it for Youtube adblock

Wanting something stable, maybe just root for now

First of all you should unlock your bootloader, because that will require a full wipe and that can be annoying if you start setting up your device and then have to wipe everything. Then, you could install TWRP and root your device, but since that does not require a full wipe, you don't have to do it immediately, if you don't want to.

Did root +xposed and ARISE sound mod. Everything nice and fast also installed adaway etc
Wysłane z mojego ONEPLUS A3003 przy użyciu Tapatalka

I usually unlock and root, but this thing has so much customization stock, that I'm leaving it alone so I can use Android pay.

Absolutely nothing. I haven't felt the need to root or unlock bootloader with OP3 or this one.

Agree with the two posts above.
I decided to not touch it so I can give Android Pay ago as well as use my banks app which blocks root.

ignorant question...
Do AdBlockers need root to run, or only to install?
ie. can you
- root
- install XYZ
- unroot? (with AdBlock still working)
and then be able to still use Google Pay, etc?

zim2dive said:
ignorant question...
Do AdBlockers need root to run, or only to install?
ie. can you
- root
- install XYZ
- unroot? (with AdBlock still working)
and then be able to still use Google Pay, etc?
Click to expand...
Click to collapse
run

I flashed twrp, rooted and running some exposed modules . Waiting on some Roms.

My plan is to wait a week and then flash TWRP, root Oxygen with SuperSU, and maybe install Xposed. I really want root for AdAway because mobile ads are awful. I will be doing this all this weekend hopefully.
My only concern is that once we get Nougat, there is no Xposed for 7.0+. Killing me to not ask for a timeline on when we could expect a release.

Unlock boot loader install twrp, root, moab,xposed. Then wait for a good stable cm maybe use a custom rom(ehhhhmmmm darkobas).

Unlock the bootloader, custom recovery, root it and install xposed with some adblockers
Edit: and viper4android

dewa710 said:
Unlock the bootloader, custom recovery, root it and install xposed with some adblockers
Click to expand...
Click to collapse
Yes...twrp ..root ..gmd gesture..adaway..viper4arise...and new nougat ROMs to flash....

I'm sure I'm gonna do things that will brick the device for at least 2 times. No full customization, no life

hi guys! my OP3T delivered me between 5th and 12th december if oneplus keep this date
first i will do unlock bootloader, root and flash twrp. then i will look what comes ^^ can i use this guide also for the OP3T to unlock bootloader, root and flash a custom recovery?
after two years of using my lovely great OPO, i get an new great smartphone from oneplus so i hope the OP3T arrive me fast!

justibasa said:
I usually unlock and root, but this thing has so much customization stock, that I'm leaving it alone so I can use Android pay.
Click to expand...
Click to collapse
So........I lied. Being the crackflasher I am, I unlocked and flashed a kernel today. But that's all I'm doing, I promise, maybe. ?

fluke87 said:
First of all you should unlock your bootloader, because that will require a full wipe and that can be annoying if you start setting up your device and then have to wipe everything. Then, you could install TWRP and root your device, but since that does not require a full wipe, you don't have to do it immediately, if you don't want to.
Click to expand...
Click to collapse
Yeah wish I'd seen this earlier
Setting it all up for the second time tonight

zim2dive said:
ignorant question...
Do AdBlockers need root to run, or only to install?
ie. can you
- root
- install XYZ
- unroot? (with AdBlock still working)
and then be able to still use Google Pay, etc?
Click to expand...
Click to collapse
No AdBlock needs root. Search blockada I use it even as I'm rooted as you can turn on and off the ad block allowing me to use specific price apps.
When I receive mine today will update, unlock my bootloader, root and install this kernel
http://forum.xda-developers.com/oneplus-3t/development/kernel-tyranus-kernel-t3507267.

question about maintaining root

So far I've been running my OP3T with stock rom with TWRP recovery and SuperSU to have root. This was mostly because I wanted the Adaway and titanium backup to work. I undid everything so I could update to the latest OxygenOS version, and now I'm on the stock recovery too, but with bootloader still unlocked I believe. I no longer have root after doing the upgrade as far as I can tell, still a bit new to all this flashing, haha. The last time I did this was when the nexus 4 came out
What is the best option for maintaining root while still being able to upgrade smoothly? I'm not against using one of the custom ROMs if that will help, but I do kinda like the stock rom so far!
thanks!

bluesrph said:
So far I've been running my OP3T with stock rom with TWRP recovery and SuperSU to have root. This was mostly because I wanted the Adaway and titanium backup to work. I undid everything so I could update to the latest OxygenOS version, and now I'm on the stock recovery too, but with bootloader still unlocked I believe. I no longer have root after doing the upgrade as far as I can tell, still a bit new to all this flashing, haha. The last time I did this was when the nexus 4 came out
What is the best option for maintaining root while still being able to upgrade smoothly? I'm not against using one of the custom ROMs if that will help, but I do kinda like the stock rom so far!
thanks!
Click to expand...
Click to collapse
This thread should answer all your questions and doubts
https://forums.oneplus.net/threads/...-or-custom-recovery-without-data-loss.479265/

saurabh40629 said:
This thread should answer all your questions and doubts
https://forums.oneplus.net/threads/...-or-custom-recovery-without-data-loss.479265/
Click to expand...
Click to collapse
Thank you, I have seen that post. I'm guessing any route I go I'll have to flash updates then? I was hoping to find a way to be able to use OTA updates.
I've also never been able to get rid of the dm-verity error, even after going back to stock and locking the bootloader. Is there anything I need to worry about with that or is it just an annoyance?
Sent from my OnePlus3T using XDA Labs

bluesrph said:
Thank you, I have seen that post. I'm guessing any route I go I'll have to flash updates then? I was hoping to find a way to be able to use OTA updates.
I've also never been able to get rid of the dm-verity error, even after going back to stock and locking the bootloader. Is there anything I need to worry about with that or is it just an annoyance?
Click to expand...
Click to collapse
Dm-verity u can bypass but bootloader one, you can not. Look at the apps, mods section.

bluesrph said:
Thank you, I have seen that post. I'm guessing any route I go I'll have to flash updates then? I was hoping to find a way to be able to use OTA updates.
I've also never been able to get rid of the dm-verity error, even after going back to stock and locking the bootloader. Is there anything I need to worry about with that or is it just an annoyance?
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
You shouldn't try to flash the partial OTAs while you are rooted and have a custom recovery installed. The partial zip will try to make specific changes in the restricted partitions (/system, /boot, /recovery, etc.) related to the update and prior modifications to these files may cause the update to fail and the phone to brick. You can still use the "Update" tab in the Settings menu to download the update though as OOS will detect root and download the full zip of the update for you. Simply flash the full zip in TWRP, wipe cache/dalvik, then flash SuperSU and you're good to go the next time an update rolls out. Updating by this method (rooting immedately after flashing update) will also prevent OOS from replacing TWRP with the stock recovery again. When you download the update, you'll know if it's the full zip if the file is >1 GB (they're usually ~1.4 GB,, whereas the partial zips are a few hundred MB).
Unlocked bootloader warning screen is cannot be removed without relocked and fully resetting (wiping) the phone. DM-verity warning screen can be removed by following this guide. Make sure that you are flashing the correct firmware for you current version of OOS though, flashing the wrong version can brick you phone.

Can a rooted phone be updated?

Can a rooted phone be updated? If i root my razor, will i be able to update without re-rooting?

ChronosTrigger said:
Can a rooted phone be updated? If i root my razor, will i be able to update without re-rooting?
Click to expand...
Click to collapse
No, it fails to install. You need to reflash the stock boot image to take an OTA.

Confused still
CurtisMJ said:
No, it fails to install. You need to reflash the stock boot image to take an OTA.
Click to expand...
Click to collapse
I'm Sorry i'm so nooby in this regard.
So do you mean i have to basically get the stock ROM back again.
Then I can re-root like i did with the earlier version?

ChronosTrigger said:
I'm Sorry i'm so nooby in this regard.
So do you mean i have to basically get the stock ROM back again.
Then I can re-root like i did with the earlier version?
Click to expand...
Click to collapse
Yes. Razer's update engine doesn't seem to have the option to download full images like some other OEMs, so only fully stock ROM can be upgraded.
On that note, Razer seems to have set a week as the delay for releasing factory images, so if you want to keep root you might want to wait after an OTA, though we may be able to reproduce a slot earlier if someone captures the OTA package (but it's not as verifiable of course)

CurtisMJ said:
Yes. Razer's update engine doesn't seem to have the option to download full images like some other OEMs, so only fully stock ROM can be upgraded.
On that note, Razer seems to have set a week as the delay for releasing factory images, so if you want to keep root you might want to wait after an OTA, though we may be able to reproduce a slot earlier if someone captures the OTA package (but it's not as verifiable of course)
Click to expand...
Click to collapse
WARNING: This file is really intended for a developer to use in making a rooted slot. Flashing the file below could? remove root or cause other issues if you're rooted. Brick maybe? Although, mostly likely, it won't flash at all if you are rooted.
I used adb to capture the Razer Phone 2 MR2 OTA. It's located here.
I also downloaded it... but figure y'all would prefer a link straight to the Google source
SHA1 is the file name so you can verify it. E9F494FACBF8B7A6DF32F342C84459A7051ACE24
The SHA256 I calculated was: FF571E225BC81C8D450964E0C7BA28DF13E963798F9E5AF7E7C142DE7FBE51A5

translucentfocus said:
WARNING: Flashing the file below could? remove root or cause other issues if you're rooted. Brick maybe? I'm not rooted, just trying to help people get the files they need.
I used adb to capture the OTA. It's located here.
I also downloaded it... but figure y'all would prefer a link straight to the Google source
SHA1 is the file name so you can verify it. E9F494FACBF8B7A6DF32F342C84459A7051ACE24
The SHA256 I calculated was: FF571E225BC81C8D450964E0C7BA28DF13E963798F9E5AF7E7C142DE7FBE51A5
Click to expand...
Click to collapse
So With this. You can root, AND if they have any Update for the phone in the future, I can Update it without losing my root?

ChronosTrigger said:
So With this. You can root, AND if they have any Update for the phone in the future, I can Update it without losing my root?
Click to expand...
Click to collapse
Not quite... The update will likely fail to apply due to checksum failures. If it did go through it would probably brick the kernel so that's a good thing. Sorry, there's not really a way to automatically root after official OTAs as they update block by block between two known states, and neither is rooted. It's just sort of not possible, by design. You have to unroot, update and root again.
The OTA package translucentfocus has provided allows us to reproduce a single slot before the week's wait for the factory image so we can root sooner.

translucentfocus said:
WARNING: Flashing the file below could? remove root or cause other issues if you're rooted. Brick maybe? I'm not rooted, just trying to help people get the files they need.
I used adb to capture the OTA. It's located here.
I also downloaded it... but figure y'all would prefer a link straight to the Google source
SHA1 is the file name so you can verify it. E9F494FACBF8B7A6DF32F342C84459A7051ACE24
The SHA256 I calculated was: FF571E225BC81C8D450964E0C7BA28DF13E963798F9E5AF7E7C142DE7FBE51A5
Click to expand...
Click to collapse
which OTA is this? Also how to update

xterminater07 said:
which OTA is this? Also how to update
Click to expand...
Click to collapse
Sorry, I didn't specify. It's the MR2 update for the Razer Phone 2. Original reply has been also updated with version information in bold.
How to update? Actually, I posted the OTA because it's really for someone to make a slot with root before Razer releases the Factory MR2 Images--as @CurtisMJ mentioned previously.

CurtisMJ said:
Yes. Razer's update engine doesn't seem to have the option to download full images like some other OEMs, so only fully stock ROM can be upgraded.
On that note, Razer seems to have set a week as the delay for releasing factory images, so if you want to keep root you might want to wait after an OTA, though we may be able to reproduce a slot earlier if someone captures the OTA package (but it's not as verifiable of course)
Click to expand...
Click to collapse
Sorry to bring back an old thread but just a few questions if you don't mind.
I just bought a used Razer 2 seems like the user rooted it (I was unaware) and it has been years since I rooted anything. I downloaded root checker and it said I was rooted. I assume I'm running the stock rom, though magisk manager was installed on the phone when I turned it on so I guess it's not stock. I guess this means I can not take any OTA or it could brick? I went into system update and it still checked to make sure I was up to date so maybe OTA isn't disabled? So much has changed with apps and rooting since I messed with it that I don't know enough and I don't want to brick or bootloop the device.
Thanks

Univsoldur said:
Sorry to bring back an old thread but just a few questions if you don't mind.
I just bought a used Razer 2 seems like the user rooted it (I was unaware) and it has been years since I rooted anything. I downloaded root checker and it said I was rooted. I assume I'm running the stock rom, though magisk manager was installed on the phone when I turned it on so I guess it's not stock. I guess this means I can not take any OTA or it could brick? I went into system update and it still checked to make sure I was up to date so maybe OTA isn't disabled? So much has changed with apps and rooting since I messed with it that I don't know enough and I don't want to brick or bootloop the device.
Thanks
Click to expand...
Click to collapse
Yes, that sounds about right. When rooted the OTA function doesn't disable right away. Only after its downloaded an update and actually tries to apply it it'll refuse. The new Android update engine is pretty good at not bricking. My guess is probably stock. If it's rooted, then the bootloader is unlocked, and it's not too bad. For magisk root at least all you need to do is flash the stock boot image and the OTA will apply. With factory images around and an unlocked bootloader you'll have a hard time bricking it. Just don't untick "OEM Unlocking" in developer options. Ever. (Or at least until you've fully restored stock firmware. It's supposed to be disabled so you can't make that mistake but Magisk hide tricks the firmware into believing the bootloader is locked so it's enabled. Whaddayagonnado)

CurtisMJ said:
Yes. Razer's update engine doesn't seem to have the option to download full images like some other OEMs, so only fully stock ROM can be upgraded.
On that note, Razer seems to have set a week as the delay for releasing factory images, so if you want to keep root you might want to wait after an OTA, though we may be able to reproduce a slot earlier if someone captures the OTA package (but it's not as verifiable of course)
Click to expand...
Click to collapse
CurtisMJ said:
Yes, that sounds about right. When rooted the OTA function doesn't disable right away. Only after its downloaded an update and actually tries to apply it it'll refuse. The new Android update engine is pretty good at not bricking. My guess is probably stock. If it's rooted, then the bootloader is unlocked, and it's not too bad. For magisk root at least all you need to do is flash the stock boot image and the OTA will apply. With factory images around and an unlocked bootloader you'll have a hard time bricking it. Just don't untick "OEM Unlocking" in developer options. Ever. (Or at least until you've fully restored stock firmware. It's supposed to be disabled so you can't make that mistake but Magisk hide tricks the firmware into believing the bootloader is locked so it's enabled. Whaddayagonnado)
Click to expand...
Click to collapse
Thanks for the detailed response I managed to get up with the previous owner on swappa last night. He told me he unlocked the phone but never actually got around to rooting it. He also said it is running stock and the reason magisk is still on the phone after a wipe is because magisk persists after a wipe.
Messages from him.
Sorry about that, I did unlock the bootloader but I never actually got around to rooting. I usually relock the bootloader before I sell it but I completely forgot. You can apply an ota because I never installed a custom recovery, something else I didn't get around to doing. You can easily relock the bootloader using adb. If you need help with this let me know and I can walk you through it. But the bootloader being unlocked has zero effect on ota's. You are all good to go as far as that goes.
Oh no you're absolutely fine with an ota. I just looked it up and you're absolutely right, magisk does survive a reboot now. Since I didn't load a custom recovery though an ota will install just fine. Although when an ota does install though it will most likely remove magisk because it will write over the boot.img with the factory one. Here is the link to the factory images. It includes instructions on how to install it. But honestly a new ota should be released any time now since the last one I think was November. Once that installs you will be completely back to stock.
Does this sound accurate to y'all. Thanks again

@Univsoldur His knowledge seems a little dated. Kind of how mine was a few months ago Anyways here goes:
If a root checker says it's rooted then it probably is. I'm not sure why he says it isn't.
Magisk does indeed persist through a data wipe. I wasn't aware magiskinit could unpack the manager APK though. Neat
He's right in that an unlocked bootloader won't affect OTAs, but having magisk installed will.
The RP2 uses the new A/B update scheme. In this case it doesn't matter whether a custom recovery was ever installed. Recovery mode is not used during the process of installation. Unfortunately the new update scheme is also heavily based on deltas, even on the kernel image, so OTAs will be broken as it won't be able to retrieve a full kernel image from the OTA servers. Some OEMs' ROMs can do that, but Razer's can't. You can flash the factory images if you truly want a clean start, but to fix OTAs and remove magisk, reflashing just the kernel image with one from the factory image should be sufficient. The magisk uninstaller won't work due to the data wipe so that's probably the only option.

CurtisMJ said:
@Univsoldur His knowledge seems a little dated. Kind of how mine was a few months ago Anyways here goes:
If a root checker says it's rooted then it probably is. I'm not sure why he says it isn't.
Magisk does indeed persist through a data wipe. I wasn't aware magiskinit could unpack the manager APK though. Neat
He's right in that an unlocked bootloader won't affect OTAs, but having magisk installed will.
The RP2 uses the new A/B update scheme. In this case it doesn't matter whether a custom recovery was ever installed. Recovery mode is not used during the process of installation. Unfortunately the new update scheme is also heavily based on deltas, even on the kernel image, so OTAs will be broken as it won't be able to retrieve a full kernel image from the OTA servers. Some OEMs' ROMs can do that, but Razer's can't. You can flash the factory images if you truly want a clean start, but to fix OTAs and remove magisk, reflashing just the kernel image with one from the factory image should be sufficient. The magisk uninstaller won't work due to the data wipe so that's probably the only option.
Click to expand...
Click to collapse
So you think to get it back to stock I could just go here.
https://developer.razer.com/razer-phone-dev-tools/factory-images/
Will that remove magisk and return it back to stock I would assume there is no threat of flashing the stock image. Besides that do I need to mess with the kernel?

I'm wondering if it would be possible to flash the unlocked Razer phone 2 firmware to the AT&T version. Would the bootloader need to be unlocked?

Univsoldur said:
So you think to get it back to stock I could just go here.
https://developer.razer.com/razer-phone-dev-tools/factory-images/
Will that remove magisk and return it back to stock I would assume there is no threat of flashing the stock image. Besides that do I need to mess with the kernel?
Click to expand...
Click to collapse
Yes, that will return it to stock and remove Magisk. No, if you flash the factory image you don't need to do anything further with the kernel.
---------- Post added at 11:14 PM ---------- Previous post was at 11:11 PM ----------
DrGonzo6o said:
I'm wondering if it would be possible to flash the unlocked Razer phone 2 firmware to the AT&T version. Would the bootloader need to be unlocked?
Click to expand...
Click to collapse
The bootloader needs to be unlocked, yes. I had the unlocked one from the start, so I can't comment on how well that will work though.
Has anyone with an AT&T version successfully flashed unlocked firmware?

Univsoldur said:
So you think to get it back to stock I could just go here.
https://developer.razer.com/razer-phone-dev-tools/factory-images/
Will that remove magisk and return it back to stock I would assume there is no threat of flashing the stock image. Besides that do I need to mess with the kernel?
Click to expand...
Click to collapse
I did post a full unroot guide...

Help with Rooting a Note 8

Hi all.
So it's been a while that I've rooted a phone (Note 4 years ago).
Getting a refurbished Note 8 very soon (UK).
I just want to root it and install only what's needed, without applying custom roms etc.
Just need it rooted for Titanium Backup, modded Google Play. Stuff like that.
Hope someone can help me in how I should go about it.
Also should I update the phone to 9.0 as soon as I boot it up?
Thanks.
Edit: Got the phone now. It took me to the home screen when first booted up. Looks like already updated to version 9. Does rooting still trigger KNOX?

skatlyup said:
Hi all.
So it's been a while that I've rooted a phone (Note 4 years ago).
Getting a refurbished Note 8 very soon (UK).
I just want to root it and install only what's needed, without applying custom roms etc.
Just need it rooted for Titanium Backup, modded Google Play. Stuff like that.
Hope someone can help me in how I should go about it.
Also should I update the phone to 9.0 as soon as I boot it up?
Thanks.
Edit: Got the phone now. It took me to the home screen when first booted up. Looks like already updated to version 9. Does rooting still trigger KNOX?
Click to expand...
Click to collapse
Yes rooting will trip Knox.
To flash TWRP just follow the steps in this thread - https://forum.xda-developers.com/t/recovery-official-3-3-1-x-twrp-for-galaxy-note8-exynos.3832962/ (just use the latest TWRP which is 3.5 I believe)
If you're just going to root stock filmware you will need to flash RMM/KG bypass or you will get locked out of your phone (only official filmware can be flashed error, then you will have to flash stock to fix it) - https://forum.xda-developers.com/t/...ll-twrp-on-exynos-samsung-after-2018.3747535/
If you are going to flash a custom rom they have the RMM state prepatched so this step would not be necessary. To flash a custom rom just follow the steps laid out in the OP of the rom you want to use.