Database Info

[TUTORIAL] Prepare Your AT&T HTC One X for Custom ROMs

OUT OF DATE USE THE ONE CLICK 1.85 ROOT TOOL IN THE FORUMS
As the ROM chefs go to work, we want to be sure that we are ready to flash the ROMs when they come to be available! This guide will help you set up your phone so that you can flash custom ROMs.
After this process you will have a phone on the latest firmware (1.85 at the moment) with bootloader unlock, rooted, and busybox installed.
This guide assumes you are on a root friendly firmware (as of now, it is firmwares 1.82.502.3 and below).
This is really going to be done in a four step process. First we need to root the device in order to access the place where the CID is stored so that we can change it and get unlocked. After changing the CID, we can unlock via htcdev.com. Then we can go on to installing a custom recovery and finally rooting!
From there I will give you some tips on installing ROMs.
NOTE: THIS PROCESS IS EXTREMELY DANGEROUS. IT MAY BE A BIT CONFUSING. READ OVER THE STEPS BEFORE STARTING. IF YOU DO NOT THINK YOU WANT TO RISK YOUR DEVICE BECOMING A BRICK THEN DO NOT ATTEMPT THIS. THIS VERY EASILY COULD RUIN YOUR DEVICE.
BACKUP EVERYTHING BEFORE STARTING AS EVERYTHING ON YOUR DEVICE WILL PROBABLY BE WIPED.
I, XDA, AND THE ORIGINAL TOOL CREATORS DO NOT TAKE RESPONSIBILITY FOR ANYTHING THAT HAPPENS TO YOUR DEVICE. IT IS SOLELY YOUR RESPONSIBILITY FOR WHAT YOU DO TO YOUR DEVICE.
Click to expand...
Click to collapse
Your warranty will be void if you unlock the bootloader. If you just root though then you can return to 100% stock by running the RUU.
This guide is for Windows only at the moment though I will try to post Mac and Linux guides at some point.
ORIGINAL TOOL THREADS:
One Click Root for 1.82 and below: http://forum.xda-developers.com/showthread.php?t=1644167
Spoof CID Script: http://forum.xda-developers.com/showthread.php?t=1672284
I will try to keep this as up to date as possible! Taking a visit to the index of the development forums (http://forum.xda-developers.com/showthread.php?t=1671237) is also a good idea!
Last Updated: 5/28/12

0. Getting the prerequisites:
Download the package at the bottom of the first post to get started.
Extract the package somewhere you will remember (like on your desktop).
Connect your device via USB and make sure you have USB Debugging enabled under settings.
Click to expand...
Click to collapse
1. Root your device
1. Open the folder you downloaded and navigate to the "root" directory.
2. Double click on the root-windows.bat file
3. Let the root run and do not touch your device. It will reboot several times- do not touch it or you may brick your device. Just let it do its thing and eventually after around 3 minutes you will have a rooted device in your hand.
Click to expand...
Click to collapse
2. Get the unlock token
In order to unlock the bootloader we will need to change a value called the CID. This will allow the htcdev.com site to unlock our phones.
1. Go to the downloaded folder and go to the "change_cid" folder.
2. Click on the "Spoof-CID.bat" file. Follow the instructions. Your CID will change from CWS__001 (stock AT&T CID) to 11111111 (called "SuperCID," will allow you to flash anything)
3. Log in to htcdev and go here: http://www.htcdev.com/bootloader/unlock-instructions (NOTE: This skips the agreements you need to click through as some of the buttons on their website are wonky. Doing this assumes you agree to their policies that are listed there)
4. Follow the instructions very carefully (they are written very well) untill the point where you get the file "Unlock_code.bin" via email. Stop there.
5. You should now have the file for bootloader unlock. MAKE SURE TO SAVE THAT FILE "Unlock_code.bin" TO THE "generic" FOLDER IN THE PACKAGE YOU DOWNLOADED! YOU WILL NEED IT LATER.
Click to expand...
Click to collapse
3. Run the RUU to update to latest firmware
1. Download the latest RUU from the xda forums (should be an .exe file)
Currently it is version 1.85.502.3 and you can download it here:
http://briefmobile.com/download-htc-one-x-att-1-85-update
2. Follow its instructions very carefully. It will take approximately 20 minutes to complete. BE PATIENT. IF YOU UNPLUG YOUR PHONE HERE YOU WILL GET A BRICK.
3. Let your phone reboot and go through initial setup again
Click to expand...
Click to collapse
4. Unlock your bootloader using Unlock Token
1. Navigate to the "generic" folder in cmd (you should have added the Unlock_code.bin file to this folder already) and plug your phone in in fastboot mode. To do this, first shut off your phone. Wait for it to turn off. Then hold the volume down button. Press the power button for 3 seconds while still holding the volume down key. Let go of the power button but keep holding the volume down button untill you see a white screen with a bunch of small text on it. Use the volume up and down keys and the power button to select the FASTBOOT option. Plug your phone into your computer. Then wait for the FASTBOOT text to turn into FASTBOOT USB.
2. Type the following into cmd on your computer:
fastboot flash unlocktoken Unlock_code.bin
NOTE: This step might take quite a few tries. For some it works on the first time. For others, it may take around 20 times. Just keep typing in the command until you get a sucessful flash. We aren't sure why it does this at the moment but just keep trying and don't give up.
3. Use the volume keys to say that you do want to unlock your bootloader and wait for reboot
4. Bootloader should be unlocked! Congrats, most of the grunt work is done! Go to Settings - Developer Options - Enable USB Debugging. This will allow us to continue
5. Re-set up phone and enable USB debugging again
Click to expand...
Click to collapse
5. Install a custom recovery so that we can gain root access
1. Currently there are two recovery options: ClockWorkMod Touch and TWRP (TeamWinRecoveryProject). Both are pretty much the same as they both use touch input but TWRP does have some other nice features like a built in file browser and more. It is also more touch optimized. ClockWorkMod is more "old school" and I personally feel more comfortable using it, but using TWRP is fine as well. It doesn't really matter which recovery your choose, both are good choices. Download whichever one you want below:
CWM Touch: http://forum.xda-developers.com/showthread.php?t=1677304
TWRP: http://forum.xda-developers.com/showthread.php?t=1677447
2. Drag the .img recovery file you just downloaded into the "generic" folder
3. Connect your phone via fastboot
4. Type the following:
fastboot flash recovery <insert name of recovery .img file here>
Replace the stuff between the <> with the name of the file you just downloaded
5. Wait for your device to reboot. Then type into cmd which is cd'ed to the "generic" folder:
adb reboot recovery
6. Make sure your recovery works as soon as it is done loading and then press "reboot system"
7. Follow its instructions
Click to expand...
Click to collapse
6. Root your system
1. Connect your phone as a "Disk Drive" and drag the "root.zip" file in the "root" folder to your phone's memory
2. Reboot into recovery with the adb command (adb reboot recovery)
3. Go to install zip from sdcard and navigate to the zip file you downloaded. Say "yes" and watch it flash
4. Reboot system now
5. Go to the play store and download any app that has "Busybox installer" in its name (the one by JRummy16 works good I believe)
Click to expand...
Click to collapse
If all goes well, you should be sitting at an AT&T HTC One X which is on the latest RUU leaked firmware (1.85.502.3 at this moment), rooted, busyboxed, and unlocked.
Congrats!
If you want to flash any ROMs, download the .zip file of the ROM, place it on your phones memory, and then install the zip like you did to the root.zip file.
Enjoy your AT&T HTC One X!

CREDITS:
kennethpenn: For initial root, getting all the RUUs from the "source" and for giving the HTC One X's situation prime press appearance on his website, BriefMobile.com
grankin01: For finding out how to edit the CID originally
designgears: For creating the One Click Super CID tool for bootloader unlock
paulobrien: For porting CWM Touch to our device
sk08: For leading the way in terms of MODs and organizing an S-OFF thread to get this thing fully ours
JSLEnterprises: For initially being there to help organize a bootloader unlock
Team Nocturnal: For their awesome ROM
Click to expand...
Click to collapse
If you want to thank or donate to someone, please do not do so to me. The people above are the ones that deserve the thanks and the donations to encourage them to keep doing the fantastic work they have been doing! I'm just a high school student
Some common terminology:
Deoxdexed: OEMs package their apps with .odex files because they are more optimized for your device. However, this makes the file uneditable by developers and things like mods cannot be used with odexed ROMs. A ROM with "deodexed" as a feature means it is easier to use mods with that ROM
Busybox: A collection of linux tools that are helpful for flashing ROMs and doing other basic Android tasks
RUU: ROM Update Utility, made by HTC, completely reflashes device firmware, useful if you get bricks. Only for Windows.
Root: Allows you to edit system level files
S-OFF: (currently unattainable) Security-OFF, it is a "feature" in HTC phones that allows us to modify almost any part of your system.
Unlocked Bootloader: Allows us to flash custom images to the device.
Click to expand...
Click to collapse

As I understand and appreciate the work put in this thread, do we need another how to? Using the index sticky alone anyone should be able to root/unlock/flash their device. There's already scripts for everything and virtually no ADB required for nubs.
I would assume with the other info already in this section if someone can't figure out how to flash their phone, then they don't need to flash at all.

HydroSkillet said:
As I understand and appreciate the work put in this thread, do we need another how to? Using the index sticky alone anyone should be able to root/unlock/flash their device. There's already scripts for everything and virtually no ADB required for nubs.
I would assume with the other info already in this section if someone can't figure out how to flash their phone, then they don't need to flash at all.
Click to expand...
Click to collapse
Wasnt sure, there are still a few people asking how to do it since it is a bit complicated with the 1.85 update breaking root so I just compiled everything into a master one.
And yeah, I use a lot of the scripts in the package I put for download.
Anyway, mods do what you think with this thread! And this might be in the wrong section, wasnt sure if it goes in general or development.

Please keep this up. As it is the most aggregated list of instructions, I'm sure it will help many who have just gotten their phone. Great work by the way.

HydroSkillet said:
As I understand and appreciate the work put in this thread, do we need another how to? Using the index sticky alone anyone should be able to root/unlock/flash their device. There's already scripts for everything and virtually no ADB required for nubs.
I would assume with the other info already in this section if someone can't figure out how to flash their phone, then they don't need to flash at all.
Click to expand...
Click to collapse
As I agree with you, a "one stop shop" that can be pointed out to for the noobs who got their mommy's to buy them their cool phone should at least keep the redundant questions to a minimum.

you cant ruu WITH a UNLOCKED bootloader these directions are wrong there would need to be a relock step added in.
ALSO THE CWM STEP NEED A ROOT FOR IT TO WORK LOOK AT THE PAGES
READ UP ON THE STUFF BEFORE YOU MAKE A GUIDE BECAUSE THIS IS WRONG

squishy5 said:
you cant ruu WITH a UNLOCKED bootloader these directions are wrong there would need to be a relock step added in.
ALSO THE CWM STEP NEED A ROOT FOR IT TO WORK LOOK AT THE PAGES
READ UP ON THE STUFF BEFORE YOU MAKE A GUIDE BECAUSE THIS IS WRONG
Click to expand...
Click to collapse
Locked boot loader yes.
Root for cwm no.
Sent from my HTC One X using xda premium

squishy5 said:
you cant ruu WITH a UNLOCKED bootloader these directions are wrong there would need to be a relock step added in.
ALSO THE CWM STEP NEED A ROOT FOR IT TO WORK LOOK AT THE PAGES
READ UP ON THE STUFF BEFORE YOU MAKE A GUIDE BECAUSE THIS IS WRONG
Click to expand...
Click to collapse
Why don't you read before you comment on things like this?
I never "Unlock the bootloader"
I simply get the Unlock token from HTC.
So stop acting like you know everything, because you dont
Don't ever use caps with me and expect me to come back with a nice response. I put this out for the community, not for some kid who thinks he knows it all to come back and say that I did it wrong when he didn't even read the post properly.
And you don't need root to install CWM, just an unlocked bootloader.
Stop calling my stuff wrong if you yourself don't even know what is right

rohan32 said:
Why don't you read before you comment on things like this?
I never "Unlock the bootloader"
I simply get the Unlock token from HTC.
So stop acting like you know everything, because you dont
Don't ever use caps with me and expect me to come back with a nice response. I put this out for the community, not for some kid who thinks he knows it all to come back and say that I did it wrong when he didn't even read the post properly.
And you don't need root to install CWM, just an unlocked bootloader.
Stop calling my stuff wrong if you yourself don't even know what is right
Click to expand...
Click to collapse
He put his foot in his mouth, apology should be coming oh and Good job man, Good job. Thanks for the work, this should be a sticky.

This is a great write up and would have been extremely helpful last night. I will admit I have done a lot of reading before I unlocked the bootloader and updated to 1.85, but it was still very confusing at some points. The htcdev site actually gave me the most trouble because I didn't realize most of the steps were completed and I could skip all the way to entering the token and the site was simply used for entering the token and getting the unlock file.
And yes, I almost said the same thing about the relock step. I had to read it twice to realize you didn't unlock yet. That's another thing that confused me last night was unlocking/relocking immediately.
I think this should be a sticky and all the other tutorials and such should be deleted. This is a perfect summary IMO and will use it when I unlock my friends one x
Sent from my HTC One X

My problem with this is that you packaged it all up while the individual threads for each thing are updating and you are severing up potentially outdated scripts.

designgears said:
My problem with this is that you packaged it all up while the individual threads for each thing are updating and you are severing up potentially outdated scripts.
Click to expand...
Click to collapse
I agree. While it is nice to have a all-in-one, you should be linking to the threads since they are updating them on a daily basis instead of linking to their scripts. Ive already had to change JeepFreaks script this morning as he updated it. It would make your world a lot easier if you did it that way, and also not risk giving some new user outdated scripts.
I think this should go in the General section as the first few pages should redirect to the original threads anyway.

Red5 said:
I agree. While it is nice to have a all-in-one, you should be linking to the threads since they are updating them on a daily basis instead of linking to their scripts. Ive already had to change JeepFreaks script this morning as he updated it. It would make your world a lot easier if you did it that way, and also not risk giving some new user outdated scripts.
I think this should go in the General section as the first few pages should redirect to the original threads anyway.
Click to expand...
Click to collapse
Sure thing, I will add to the original post for the links.
Also I will try to keep this updated, but yeah I might not catch all the updates

Thank you so much Rohan! Really appreciate it! Took me about 4 hours to get this done but it was worth it. Now to install cleanrom. Thanks again. This is my first time doing something like this.

Duse ijuat saw this and I'm going to do this and flash clean from when I get home and I read through this I honestly love you for doing this it helps more than you think thanks a lot
Deffinitlet should be stickied
Sent from my HTC One X using XDA

These are the best instructions! Wish i had them when all this shenanigans started. Thx

ethantarheels123 said:
Please keep this up. As it is the most aggregated list of instructions, I'm sure it will help many who have just gotten their phone. Great work by the way.
Click to expand...
Click to collapse
I agree. This guide is very helpful for me. I consider myself to be fairly computer literate and have flashed ROMs on previous phones, but I am a complete n00b to android and linux. Looking around some of the other threads -- it appears to me that there are many people who could have much confusion resolved by reading this. Thanks for the thread.
-- Jon

Not quite sure what's going on with my update...
I'm using the exe that updates the RUU and it gets stuck on the "sending to phone" step. Reboots the bootloader once, gets stuck again (as far as I can tell , nothing is ever sent) and then gives me an error telling me "The ROM Update Utility cannot update your Android Phone. Please get the correct ROM Update Utility and try again"
i've got the correct drivers installed (was having some trouble related to that a couple days ago but have since figured it all out ) would it be better to just do the update manually? (On my evo you just change the update file to Update.zip and it automatically installs it for you when you boot into bootloader)
maybe I'll have to look into it further, but just curious if anyone's run into this issue or figured out how to get past it as of yet...
Edit: Just an update- I'm betting its because I forgot to relock my bootloader before updating. So anyone who's already completed SOME of the steps in the second post here, make sure you relock your bootloader if you haven't already done so.
Edit1.5: This assumption was correct and the bootloader is now unlocked.
Edit 2- Almost done here... Busybox wont install. Tried two different apps, neither one worked. No indication as to why (got very vague error messages to the effect of "busybox was not installed")
Edit 3- FIXED- Ok, figured it out. As far as I can tell, the process should be Root first, THEN install busybox. It doesn't work without root privelages (at least that was my experience here)

Update on How to Root from Scratch, (Backup TA, Unlock Bootloader, then Recovery)

First off, i'm sorry if the title is misleading and/or belong in the wrong part of this forum.
So, I'm late to the party, just got myself a Z5 E6653 and when I look for guides on how to obtain root they kind of out-of-date. So i'm here to make sure the path I choose to follow will be the correct one as I dont want to lose my TA partition. As far as I know, according to this guide to back up my TA partition I have to downgrade to Lollipop, but I found something interesting about backing up TA partition on Marshmallow using dirtycow method (sorry Nougat users).
So, the steps I'm proposed is, if my device is already on stock MM unrooted, locked bootloader.
1. Go here Sony cross-devices development and download file called backupTA_v2.zip this shouldnt makes us need to downgrade
2. Run the BackupTA.cmd file if you're on windows
3. There will be errors about dirtycow failed but the script automatically retry, me myself got screen-full of retries before the script actually backed up my TA partition and you'll be presented with .imgfile called TA_devicemodel_somenumbers_timestamp.img about 2MB in size (am i correct so far? this is why i want to make sure this will work)
4. Save your file in a very secure place.
That concludes the Backup TA part of rooting process am I on the right path so far?
To get unlocked bootloader according to this :
Given that you have downloaded flashtool and installed the drivers in the \drivers folder in flashtool installation
!!THIS WILL WIPE ALL DATA!!
1. Click the BLU button at top then open Sony developer website
2. Select device and follow instruction until you get a key
3. Paste the key to flashtool
4. THAT'S IT?
Now after this we can use fastboot command to flash kernel and the kernel includes recovery.
Are these steps correct so far?
I might as well add these here.
To get kernel and recovery up and running, I'll be taking androplus kernel for example, I'm assuming it works with stock ROM.
1. Get the kernel .zip here at Androplus homepage
2. And download latest TWRP recovery from androplus download page, at this time of writing it should be TWRP-3.0.2.2-e6653.img
3. Notice that it's in .zip format which we cannot use yet since we don't have custom recovery.
4. Open the zip file you just downloaded and you should see boot.img That's your brand new shining kernel, extract it outside put it in a folder along with your favorite fastboot.exe file
5. Go to fastboot, as far as I know you go to fastboot by turning off the device -> hold volume down then plug USB cable. (see note)
6. First, according to Androplus page, flash the kernel first using the command
Code:
fastboot flash boot boot.img
7. Then the recovery
Code:
fastboot flash recovery TWRP-3.0.2.2-E6653.img
8. Reboot by unplugging the USB cable
Note: some interesting thing I found while trying to enter fastboot or flashmode that it might not work if your USB port is powered How to tell if your port is powered? I'm not sure. You will have to change port and hope for the best ^_^

Yes. Explained many times. Not hard to do.. 4-5 minutes then WHOLA!

sceryavuz said:
Yes. Explained many times. Not hard to do.. 4-5 minutes then WHOLA!
Click to expand...
Click to collapse
Ahaha, sorry. Those guides are "old" in android way of changing things very fast, and I haven't seen a guide which includes backup TA partition on marshmallow so I wasn't sure it'd work correctly. Now that I know it worked, I can proceed to unlock my bootloader.
Any tips or Kernel/Rom I should use for first time flash?

webslasher said:
Ahaha, sorry. Those guides are "old" in android way of changing things very fast, and I haven't seen a guide which includes backup TA partition on marshmallow so I wasn't sure it'd work correctly. Now that I know it worked, I can proceed to unlock my bootloader.
Any tips or Kernel/Rom I should use for first time flash?
Click to expand...
Click to collapse
LineageOS, CarbonROM, eXistenZ, SunKernel..

Dear both,
I was just doing quite the same, so it was nice to read the short summary. Honestly, I'm doing these "Flash ROM stuff" very rarely, so I'm not 100% confident how to bring back those DRM/TA. I recorded it - the device came with Android LP 5.11, so this was easy done by iovyroot.
Anyway, I have the TA-backup - so I'm also going to unlock the Boot Loader now. :good:
Good to know I spend a day on reading so many related stuff, and it could be done in 4-5 min

sceryavuz said:
LineageOS, CarbonROM, eXistenZ, SunKernel..
Click to expand...
Click to collapse
I will try Existenz as I want to keep it stock looking, thanks!
bosquarid said:
Dear both,
I was just doing quite the same, so it was nice to read the short summary. Honestly, I'm doing these "Flash ROM stuff" very rarely, so I'm not 100% confident how to bring back those DRM/TA. I recorded it - the device came with Android LP 5.11, so this was easy done by iovyroot.
Anyway, I have the TA-backup - so I'm also going to unlock the Boot Loader now. :good:
Good to know I spend a day on reading so many related stuff, and it could be done in 4-5 min
Click to expand...
Click to collapse
I'm glad to find someone that is going to go through these procedures too! I will also proceed to unlock my bootloader what rom and kernel do you plan to flash?

Hi, thanks for this. I just got the Z5 today so my first port of call was coming here and finding out how to root it. I previously had the Z2 and Z2 tablet which I rooted last year with the help of the members here, I hope the process for this isn't too different for this one. I think I forget more than I remember so the guide is helpful.

[ROM] Stock Oreo 8.1 With June Security Patch (OPM1.171019.019.V9.6.2.0.ODHMIFE)

Ladies and Gentlemen,
It is my pleasure to present the latest stock Oreo 8.1 (Beta) ROM for Xiaomi Mi A1. Up till now, only a handful of testers were able to use the stock beta 8.1
But now, everyone has the opportunity to use it on their device.
Disclaimer:
If you are planning to flash the ROM on your device, you are on your own. I would not be responsible if anything happens to your device. Your warranty will be void after flashing the ROM. You need to go back to stock stable ROM with a locked bootloader for Warranty.
Requirements:
1. Xiaomi Mi A1 (Ofcourse)
2. A PC (I am using Windows 7 here)
3. The ROM file (Available on the link below)
4. MiFlash Tool ( Link: http://en.miui.com/thread-345974-1-1.html ) (A big thanks to Miui forum for making the tool available on miui forum)
5. ADB Platform tool (Search on google)
6. Patience
Installation Process:
1. Download the ROM file from the given link and unzip it.
2. You will see a folder with name as tissot_images_V9.6.2.0.ODHMIFE_8.1
3. Keep it on C drive
4. Install MiFlash Tool on your PC from the given link
5. Set up ADB driver properly on your PC (It's very important)
6. Now go to your device and enable Developers option by tapping on Build Number 7 times.
6. Open Developers Option and enable "OEM Unlocking" and "USB Debugging" option.
7. Now press and hold the power button and Volume down button for about 10 seconds until you see a small bunny on the screen.
Now connect your device to your PC and open a command box and type fastboot oem unlock
8. Once the bootloader is unlocked, put your device in fastboot mode again and connect it to PC. (BE WARNED!!! if anyone is on May security patch, unlocking bootloader will erase everything from the device and device will restart again. You will need to unlock developers option again and enable "USB debugging" option once more)
9. Now open MiFlash Tool and see if it reads your device serial number by clicking on "Refresh". Now, select tissot_images_V9.6.2.0.ODHMIFE_8.1 and click on "Flash". Make sure you are doing it in a proper way.
10. Wait until you see a "Flash Done" message on the screen. It may take around 5-10 minutes. Once done, your device will boot into system and Congrats! Now you have Oreo 8.1 on your device with June security patch.
N.B. It is best that you select "Clean all and lock" option on MiFlash tool.
Flashing Guide For TWRP & Custom Kernel:
1. Grab the latest twrp recovery image (Oreo) and twrp installer zip file.
2. Put the recovery image in ADB folder and the installer zip in your device.
2. Boot your device into fastboot mode and connect it to the PC.
3. Make sure the bootloader is unlocker.
4. Open a command box and type fastboot boot xxx.img (xxx= recovery image name)
5. Once your device is boot into twrp, flash TWRP installer zip file and reboot back to recovery.
6. Now flash the custom kernel of your choice and Magisk (optional).
7. Reboot back to system.
Important Note:
If anyone has any problem understanding the steps, I would recommend that you google or search on Youtube. There are lots of Videos showing on how to flash stock ROM on MiFlash tool. Please don't blame me if you skip any step or do it wrong. I have shared the standard steps that remain the same for flashing both stable and beta rom. It is advised that you STAY AWAY if you don't know what you are doing. I am certainly not going to take any blame for improper flashing. As you have decided to flash the ROM, I expect you to have a little knowledge about how to use MiFlash tool. A lot of newbees have problem at first, especially when flashing rom on MiFlash tool. That's because of selecting and flashing the rom file in an improper way. You need to first learn exactly which folder to flash or else you will always end up on a bootloop. Please don't blame me for not spoon feeding you.
Bugs Encountered:
I have been using the ROM for two days and I am yet to find any bugs except ctsProfile shows as false and Google Play Store shows Uncertified.
*For better battery life, you can try Void kernel (Choose the stock version).
ROM Download Link:
https://www.androidfilehost.com/?fid=818222786056041186
Credit:
Xiaomi, 4PDA, @topjohnwu for Magisk, @flex1911 for Void kernel, @CosmicDan & @mohancm for their work on TWRP.
Special Note:
I apologize to all for breaking any possible XDA rule and hurting anyone here!! Please note that I am not getting paid for sharing this post here. If anyone still feels something bad, you can either let me know or you can report it to the admin. But again, I am extremely sorry for breaking any rule here.

MiFlash Tool

Screenshots will be added shortly.

Screenshots

Already posted here https://forum.xda-developers.com/showpost.php?p=76813554&postcount=340
And fyi, i already been using this rom for past 2 days, back to AEX coz battery drain is fast, not recommended for daily usage.

exodius48 said:
Already posted here https://forum.xda-developers.com/showpost.php?p=76813554&postcount=340
And fyi, i already been using this rom for past 2 days, back to AEX coz battery drain is fast, not recommended for daily usage.
Click to expand...
Click to collapse
I can confirm battery drain with this rom.

Rowdyy Ronnie said:
Credit:
Xiaomi for allowing me to try their Beta ROM and allowing me to share it on XDA
N.B. Sharing the ROM file anywhere else without my permission will be considered as stealing and will be reported to XDA if found.
Click to expand...
Click to collapse
Did xiaomi give you the permission to share it on xda?

muruu said:
Did xiaomi give you the permission to share it on xda?
Click to expand...
Click to collapse
No, this is leaked beta. He just reshare from displax @ 4pda.ru

after sucessfully flashing using miflash it stucks on andriodone

N1ck474 said:
This update is leaked from weeks, why complaining here and now?
We're getting delayed updates cause Xiaomi is far away from Quick updates (MIUI or Stock, still Xiaomi).
Click to expand...
Click to collapse
Can we root it or when unlock bootloader cause erase all information like may update + is it good for daily use ?

joeniz said:
when unlock bootloader cause erase all information like may update?
Click to expand...
Click to collapse
Why would they remove a security feature they just recently added?

joeniz said:
Can we root it or when unlock bootloader cause erase all information like may update + is it good for daily use ?
Click to expand...
Click to collapse
It doesn't wipe data partition like what was happening on May security patch. And I haven't noticed any bug as of now. Some people said battery life is not that good. I can't comment on that as I use Void kernel.

Seems like a lot of people have some sort of issue with this post. First of all, this is not a custom rom and I didn't build it. So, if there is some sort of bugs on the ROM, that's not my fault. Second, yes I brought the file from somewhere else so that more people can use it. So, what is the problem here? Before you point your finger on me for a bootloop or bad battery life, you should read the disclaimer first. When you decide to do any experiment with your device, you should have a fair amount of knowledge of what you are doing. Before sharing the file on XDA, I flashed and tried it on my device and there was no bootloop or any other issue whatsoever.

dback31 said:
Why would they remove a security feature they just recently added?
Click to expand...
Click to collapse
Cause i found no phone that u can't root !!
---------- Post added at 09:18 PM ---------- Previous post was at 09:15 PM ----------
Rowdyy Ronnie said:
It doesn't wipe data partition like what was happening on May security patch. And I haven't noticed any bug as of now. Some people said battery life is not that good. I can't comment on that as I use Void kernel.
Click to expand...
Click to collapse
What about messenger fb in any rom i use i get animation lag in messenger when message appear things like that and if someone send me message while i using phone the phone animation lag .... Only in fb messenger i found this problem i hate this app .... Anybody have that issue because iam going mad .

Rowdyy Ronnie said:
Seems like a lot of people have some sort of issue with this post. First of all, this is not a custom rom and I didn't build it. So, if there is some sort of bugs on the ROM, that's not my fault. Second, yes I brought the file from somewhere else so that more people can use it. So, what is the problem here? Before you point your finger on me for a bootloop or bad battery life, you should read the disclaimer first. When you decide to do any experiment with your device, you should have a fair amount of knowledge of what you are doing. Before sharing the file on XDA, I flashed and tried it on my device and there was no bootloop or any other issue whatsoever.
Click to expand...
Click to collapse
If you just share a rom build by someone else, this is the wrong section of the forum to post it.
Too, you say (in op) you have permission from xiaomi to post it here in xda. This sounds unusual. Do you have any proof for this claim?

Thread cleaned.
Thread moved to the guides section where shared ROMs belong. The redirect from development section will expire in 24 hours.
:good:

Rowdyy Ronnie said:
N.B. Sharing the ROM file anywhere else without my permission will be considered as stealing and will be reported to XDA if found.
Click to expand...
Click to collapse
hahahah oh wow
the best joke i ever seen
seriously
copyright to leaked build? hahaha i can't stop

Closed beta ROM, so no point in "allowing" you to share it. They could open beta and do it themselves.
I call fake news on that
You share a rom from another forum. Okay. It was already been shared in XDA by the original poster in 4pda.
I call this reposting in the same forum.
You state that the ROM isn't yours and you "share" it with other people on XDA. And then you say reposting is stealing? Didn't you repost it as well? For you is not stealing but for others is?
Conclusion: Are you that desperate for attention?

Is this the official beta rom?

Rowdyy Ronnie said:
Credit:
Xiaomi for allowing me to try their Beta ROM and allowing me to share it on XDA
Click to expand...
Click to collapse
How did you manage to get permission from Xiaomi? Have some proofs?

[Recovery] TWRP for the Nubia Z18(NX606J)

Hey,
youyim123 recently made his TWRP build available that I was trying to compile myself. So without further ado, here is a more or less working TWRP for the Nubia Z18 with instructions of how to install it.
Link to recovery.img
How to install it:
Boot into bootloader using
Code:
adb reboot bootloader
Unlock the bootloader using
Code:
fastboot oem nubia_unlock NUBIA_NX606J
Flash the recovery.img using
Code:
fastboot flash recovery recovery.img
IMPORTANT! Navigate to "reboot to emergency recovery mode". Do not use
Code:
fastboot reboot recovery
as it might not work correctly!
I found disconnecting the device from USB to be more reliable, so do that for stability
If it gets stuck, repeat steps 1 and 4. No need to reflash, just be patient
Language will be Chinese, so change that by using the settings button (second from below on the right)
That's it, you have a working TWRP now Enjoy!
EDIT: DO NOT TRY FLASHING MAGISK AS IT WILL DAMAGE DM-VERITY AND YOU'LL HAVE TO BOOT RESCUE YOUR DEVICE! YOU CAN USE MY recovery script in the bloat remover thread to fix your device
In case you get stuck in a bootloop, repeat the installation guide, then use
Code:
adb push stock.zip /data/media/0
and reflash stock firmware as a last resort until a custom ROM is available.
All credit for this goes to youyim123 and his amazing work! I know he struggled releasing this because his work is often used or redirected without his consent or giving him credit, so I'm grateful he decided to release it.

*reserved*

Can i use this to flash Gapps

aqblwd said:
Can i use this to flash Gapps
Click to expand...
Click to collapse
In theory, yes. In practice, it somehow doesn't give me any GApps when flashing it. I'm trying to cooperate with the OpenGapps team to fix this.

any update info for flashing gapps ? i really want to use my nubia z18 with google environment on it. tks

shevaman7 said:
any update info for flashing gapps ? i really want to use my nubia z18 with google environment on it. tks
Click to expand...
Click to collapse
None yet. I'd say community involvement isn't exactly one of the OpenGapps team's good points
See the Gitter thread for tracking updates here: https://gitter.im/opengapps/general
If you know of any other way to contact them, feel free to do so and send them the logs I attached in the gitter post (same username as here)

shevaman7 said:
any update info for flashing gapps ? i really want to use my nubia z18 with google environment on it. tks
Click to expand...
Click to collapse
You can use google xspace

elnas1369 said:
You can use google xspace
Click to expand...
Click to collapse
EDIT: Okay I tried the app and it's doing something that looks like installing play services? @elnas1369 would you mind explaining what you did in detail? Because most of us probably can't speak chinese and it's not intuitive unfortunately

curtisy said:
EDIT: Okay I tried the app and it's doing something that looks like installing play services? @elnas1369 would you mind explaining what you did in detail? Because most of us probably can't speak chinese and it's not intuitive unfortunately
Click to expand...
Click to collapse
I did it on my Nubia X and it works pretty good, you just have to follow the steps, i've found some tutos on youtube it's very easy. You can search for google xspace installing or something like that

curtisy said:
Hey,
youyim123 recently made his TWRP build available that I was trying to compile myself. So without further ado, here is a more or less working TWRP for the Nubia Z18 with instructions of how to install it.
Link to recovery.img
How to install it:
Boot into bootloader using
Code:
adb reboot bootloader
Unlock the bootloader using
Code:
fastboot oem nubia_unlock NUBIA_NX606J
Flash the recovery.img using
Code:
fastboot flash recovery recovery.img
IMPORTANT! Navigate to "reboot to emergency recovery mode". Do not use
Code:
fastboot reboot recovery
as it might not work correctly!
I found disconnecting the device from USB to be more reliable, so do that for stability
If it gets stuck, repeat steps 1 and 4. No need to reflash, just be patient
Language will be Chinese, so change that by using the settings button (second from below on the right)
That's it, you have a working TWRP now Enjoy!
EDIT: DO NOT TRY FLASHING MAGISK AS IT WILL DAMAGE DM-VERITY AND YOU'LL HAVE TO BOOT RESCUE YOUR DEVICE! YOU CAN USE MY recovery script in the bloat remover thread to fix your device
In case you get stuck in a bootloop, repeat the installation guide, then use
Code:
adb push stock.zip /data/media/0
and reflash stock firmware as a last resort until a custom ROM is available.
All credit for this goes to youyim123 and his amazing work! I know he struggled releasing this because his work is often used or redirected without his consent or giving him credit, so I'm grateful he decided to release it.
Click to expand...
Click to collapse
any news update about stable TWRP for Z18. I have Z18, a very beautiful and strong device

md07 said:
any news update about stable TWRP for Z18. I have Z18, a very beautiful and strong device
Click to expand...
Click to collapse
It is stable. Just make sure to unplug your phone after flashing it as otherwise it will probably get stuck after a few seconds. If you need to have your device connected to your pc, do the following:
Start adb sideload in TWRP, connect your phone to your pc, stop sideload. That way you have a working connection with adb again
Hope this helps!

curtisy said:
It is stable. Just make sure to unplug your phone after flashing it as otherwise it will probably get stuck after a few seconds. If you need to have your device connected to your pc, do the following:
Start adb sideload in TWRP, connect your phone to your pc, stop sideload. That way you have a working connection with adb again
Hope this helps!
Click to expand...
Click to collapse
i read somewhere in Nubia forums (chinese language), some dev is going to release TWRP for Z18, but it need poll to decide.
So that, i dont know this version on XDA is official or unofficial ? And as you said, if it is stable, so can i flash Gaap package to get full Goolge and service for Z18? have you tried ?

Already try few weeks ago, not working...!
The only temperary solution is "Google Space", or just wait for the global version release
As one Dev which working on LOS fot this machine point out that Lineage is very hard to compile since there's no other Dev help him, the System is block by something call AVB2...pretty ironic as this twrp not even let us using Magisk at all!
md07 said:
i read somewhere in Nubia forums (chinese language), some dev is going to release TWRP for Z18, but it need poll to decide.
So that, i dont know this version on XDA is official or unofficial ? And as you said, if it is stable, so can i flash Gaap package to get full Goolge and service for Z18? have you tried ?
Click to expand...
Click to collapse

sky104hk said:
Already try few weeks ago, not working...!
The only temperary solution is "Google Space", or just wait for the global version release
As one Dev which working on LOS fot this machine point out that Lineage is very hard to compile since there's no other Dev help him, the System is block by something call AVB2...pretty ironic as this twrp not even let us using Magisk at all!
Click to expand...
Click to collapse
I tried Gplay space. But all app installed from there seem work slowly and not appear on home screen (must go Gplay space and run app)

md07 said:
i read somewhere in Nubia forums (chinese language), some dev is going to release TWRP for Z18, but it need poll to decide.
So that, i dont know this version on XDA is official or unofficial ? And as you said, if it is stable, so can i flash Gaap package to get full Goolge and service for Z18? have you tried ?
Click to expand...
Click to collapse
Please read the first post precisely and then the post in the nubia forum again. Youyim is the guy who made the poll and he made it public. I simply brought it to a wider audience and link to his official GitHub for the img.
You cannot flash Gapps with this because it errors. I said so a couple of times before and would appreciate a bit of effort reading before asking. You probably spent more time on writing this than you would've reading the first three post entries here, disregarding the fact that I'm trying to reply in detail. It's all in the first post, please read that before asking next time..
To sum up:
- It's the "official" TWRP from youyim, all credit goes to him
- You can not install Gapps with this, I haven't found a resolution for this but am working on an alternative. See my other thread or post #3 here

sky104hk said:
Already try few weeks ago, not working...!
The only temperary solution is "Google Space", or just wait for the global version release
As one Dev which working on LOS fot this machine point out that Lineage is very hard to compile since there's no other Dev help him, the System is block by something call AVB2...pretty ironic as this twrp not even let us using Magisk at all!
Click to expand...
Click to collapse
It's the same dev I'm the guy working on LineageOS as well and yes AVB2 (Basically think of it as Android's answer to secure boot on Computers) is a pain in the a** to deal with. Compiling itself is rather easy compared to the pain that comes after it, it's just killing lots of time and I unfortunately don't have that with a full time job. That's why I tried getting more people involved but (again) failed apparently.
TWRP doesn't have anything to do with Magisk either. Magisk is modifying the boot partition as far as I'm aware (don't hate me topjohnwu) and it relies on either no AVB/DM-Verity or a flag that doesn't work here either. TWRP in contrast just modifies/overrides the boot partition and is (mostly) used to flash many things including Magisk.

I think Z18 not have a global version, so we'll never see international firmware for this product. The only way I hope is some one or some dev support official method for install Google. And hope good news come soon.
Thanks all!

md07 said:
I think Z18 not have a global version, so we'll never see international firmware for this product. The only way I hope is some one or some dev support official method for install Google. And hope good news come soon.
Thanks all!
Click to expand...
Click to collapse
Isn't a global release coming in like 2 weeks or something? At least that's what I read last time I checked
I can tell you an official method. Root your phone and rewrite google services to system. Otherwise wait until developers can take a look at Rom building like I do now or even better, get involved. Being a one man show isn't helping the cause even if you have a couple spectators because it makes you feel more or less like a monkey in a cage

curtisy said:
Isn't a global release coming in like 2 weeks or something? At least that's what I read last time I checked
I can tell you an official method. Root your phone and rewrite google services to system. Otherwise wait until developers can take a look at Rom building like I do now or even better, get involved. Being a one man show isn't helping the cause even if you have a couple spectators because it makes you feel more or less like a monkey in a cage
Click to expand...
Click to collapse
Where did you read about global version Z18??? I checked only on Nubia website, in some global region (like India...) they are only going to release global Red Magic Mars.
I know method get Google and service by rooted and I read in Nubia forums they released tool to root current Version Z18, but I can not download

md07 said:
Where did you read about global version Z18??? I checked only on Nubia website, in some global region (like India...) they are only going to release global Red Magic Mars.
I know method get Google and service by rooted and I read in Nubia forums they released tool to root current Version Z18, but I can not download
Click to expand...
Click to collapse
https://www.gadgetsnow.com/mobile-phones/Nubia-Z18 for instance. India isn't global lol. They mostly just buy masses of phones and then resell. And yeah I can understand they won't release a global version anytime soon. The phone is great but looking at the source code, it's horrible. I even had to submit a patch so they get their build fixed!
As for the download, try the second one. Baidu is blocking anything non China by now afaik. It will also be included in the LineageOS ROM whenever I'll get that done..

custom rom question

Hi im just new in this kind of stuffs and i dont know where to start.
Base on others said that its better to use custom rom than miui
I am afraid that i might brick my phone thats why i afraid to do it.
Im currenty playing wild rift and so far, for the past weeks im experiencing FPS drop which is so annoying.
So whats the most stable custom rom you can recomend?
and just in case something wrong happened. can i still revert it back to miui?
any topic or thread you can link in comments would be really appreciated.
thanks

I haven't done that for long so I can't give you an accurate answer, but if you brick your phone you should be able to unbrick it using Mi FlashTool. Example here: https://www.technobuzz.net/xiaomi-unbrick-guide. I've never had completely bricked a phone even though I did take very very bad decisions. And yes custom roms are lighter than MIUI. Try to find a step by step tuto.

so where should i start?
any thread you can link?

Some will say this is outdated, but I still find it a good starting point: https://forum.xda-developers.com/t/4196271/ (especially this step-by-step guide: https://telegra.ph/How-to-install-Poco-x3-ROM-10-14; unless your preferred ROM developer tells you otherwise -- if unsure, always follow dev instructions).
After that, you could maybe proceed with the Index: https://forum.xda-developers.com/t/4176491/.

pnin said:
Some will say this is outdated, but I still find it a good starting point: https://forum.xda-developers.com/t/4196271/ (especially this step-by-step guide: https://telegra.ph/How-to-install-Poco-x3-ROM-10-14; unless your preferred ROM developer tells you otherwise -- if unsure, always follow dev instructions).
After that, you could maybe proceed with the Index: https://forum.xda-developers.com/t/4176491/.
Click to expand...
Click to collapse
thanks bud. highly appreciated

pnin said:
Some will say this is outdated, but I still find it a good starting point: https://forum.xda-developers.com/t/4196271/ (especially this step-by-step guide: https://telegra.ph/How-to-install-Poco-x3-ROM-10-14; unless your preferred ROM developer tells you otherwise -- if unsure, always follow dev instructions).
After that, you could maybe proceed with the Index: https://forum.xda-developers.com/t/4176491/.
Click to expand...
Click to collapse
btw im getting an error opening this link https://telegra.ph/How-to-install-Poco-x3-ROM-10-14
it says error 404

pakloybaloy said:
btw im getting an error opening this link https://telegra.ph/How-to-install-Poco-x3-ROM-10-14
it says error 404
Click to expand...
Click to collapse
Just tried it, works fine from here. Try a webproxy, maybe.

pakloybaloy said:
Hi im just new in this kind of stuffs and i dont know where to start.
Base on others said that its better to use custom rom than miui
I am afraid that i might brick my phone thats why i afraid to do it.
Im currenty playing wild rift and so far, for the past weeks im experiencing FPS drop which is so annoying.
So whats the most stable custom rom you can recomend?
and just in case something wrong happened. can i still revert it back to miui?
any topic or thread you can link in comments would be really appreciated.
thanks
Click to expand...
Click to collapse
custom rom don't destroy/brick your fone, its
a) wrong kernel or right kernel taken from unpopular source (telegram groups etc)
b) flashing error due to cable or otg failure!
where to start?
1. download miui unlocker, on windows pc/laptop
2. from developer option miui12, link miui account (which you must've already signed in to, )
3. don't use wifi, use 4g sim to link account in developer options
4. shutdown device and goto fastboot mode by pressing volume downd+power button for 10+ seconds untill u see fastboot and BOT
5. runn miui unlocker and attach cable, sign in to your miui account. it will verify and give you one week waiting time! , DONOT TOUCH ANYTHING IN THE SETTINGS OR MIUI ACCOUNT NOW. after one week, unlock the device (take backup before)
6. flash recovery
7. flash rom ( i would suggest RR8.0 or HAVOC) , if you want android 11, then go for Crdroid!
8. flash google apps / or nick apps IF the rom doesn't have it!
9. keep oem firmware 90mb file handy! sometimes o translate programming language the script requires latest Fw. , you can download it from xiaomifirmwaredownloader site!
10. flash magisk if you want rooted poco
11. reboot!