Database Develop

[Q] Can not unlock Bootloader

I am almost too chicken to post because reading all the developer threads I feel like such a noob.
I recently rooted my Nexus One, thanks to a developer that created a painless one button rooting app. The problem is after downloading and installing many apps that require superuser access I am finding out that I am limited in what I can do without unlocking the bootloader.
I want to find a theme that replaces the standard white bar "which will cause screen burn" with a black bar.
I backed up all my apps, "Titanium Back Up"
I backed up my ROM??? "Maybe not" using a program call Rom Backup. "I have not figure out how to to nandroid backup "not sure the right name"
I googled found many procedures on unlocking the bootloader but I can not get it work.
Download ADK
Found a place that has Fastboot download it
I even found out I need to copy file from ADK folder to the Fastboot folder
Held down the power button trackball got the correct screen "even though my old eyes have a hard time reading the little character"
connected my phone
Ran the batch file
It returns saying wait for device.
The device is connected, in the right mode, my device manage says the is an Android device connected.......
But no matter what I do I can not get the screen warning me that to unlock my bootloader I void my warranty.
I found here some theme labled that hey work Nexus One 2.2 and I want to try them but Metamprgh will not load new themes on a radio that has a locked bootloader.
I am not worried about losing my warranty I live in Canada if I ever need warranty work it be a hassle anyway.
I thought unlock the bootloader.
When the phone powers up login my Google Account, reload Titanium Back up to restore my my phone.
Back up the Rom once more using Rom Backup if I want to recover my stock Rom
Run Metamorph and play with the themes
But I can not unlock the bootloader ....... "waiting for device"
How can I unlock the Bootloader, I there a more current method?
What can I be doing wrong I see a device in my Device Manager?
Will my method for restoring my phone work, never done a full phone wipe?
FYI this forum is scary there should but a developer and a Noob section.

You don't need to unlock your bootloader. My bootloader is locked and I'm rooted. It seems like you're missing superuser.apk. You need that too allow all of the programs like ROM manager and Titanium Backup root permissions. I'm not sure how the one click app works but I know that it probably should have installed the superuser application to allow those apps root access. Check and see if its in your application draw. You might want to try "one click rooting again" because it seems like it didn't work.
Side note: Titanium Backup does not back up your ROM. It just backs up apps and their data stored on your phone so it can be restored when you flash a new ROM. The way you back up your ROM is through the android custom recovery using the nandroid feature.

Thanks Magma,
Yes Superuser is installed.
A program wants superuser access I can grant it.
Metamorph does do several checks and it needs superuser access.
It is my understanding superuser access gives apps access to system hardware but if you want to use Metamorph to change the standard Android Shell that is going to modify your ROM and you will need and unlocked bootloader.
Here is what happens when I run Metamorph it finds the zipped files on my SD card, I select a file, it exacts the package, I say update al .... PLEASE WAIT for 20 or 30 minutes, it may then tell me to reboot but nothing happens my theme is still stock Android 2.2
This is where you can find out about and download the One Click Root App, it is in this section themes and apps.
It roots you device but leaves the bootloader alone
I know titanium backup just restores all your applications and data. The way I understand it if I ever need to do a master reset, I login Google, download Titanimum back up use it to restore every thing else. Yes which every ROM I was running will not be touched.
I am pretty sure I need to unlock the Bootloader.
But to unlock my Bootloader I just as I said get please wait I tried everything.

Alright man, you need the Android sdk for your OS so go to the android site and get the SDK, then install drivers for phone, and you NEED a custom recovery to do a NANDROID of the ROM, from what i understand your like me
have everything stock but with root privileges! and i from what i know as of now, unlockBoot loader gives you the option to do fastboot, if you want to continue messing around with stuff i highly suggest you flash custom recovery like Amon-Ra or even clockwork(from market) then go to Nandroid back up, then flash a custom rom like Enomther's Rom that is nice and stock clean stable, but still able to do themes

ilostchild said:
Alright man, you need the Android sdk for your OS so go to the android site and get the SDK, then install drivers for phone, and you NEED a custom recovery to do a NANDROID of the ROM, from what i understand your like me
have everything stock but with root privileges! and i from what i know as of now, unlockBoot loader gives you the option to do fastboot, if you want to continue messing around with stuff i highly suggest you flash custom recovery like Amon-Ra or even clockwork(from market) then go to Nandroid back up, then flash a custom rom like Enomther's Rom that is nice and stock clean stable, but still able to do themes
Click to expand...
Click to collapse
Wow lot to digest. I do have and install Android SDK the instructions in the tutorial I googled said I needed it, The Fastboot command needed files in the ADK directory.
The thing is since my command window did not see a device,
With your Nexus One in bootloader mode and connected to your computer via USB cable, go back to the command prompt and type “fastboot-windows oem unlock”.
Would even be able to flash anything?
At the end of the day I am very happy with Android 2.2 and I do not think I want custom roms at least for now. All I want is to get Metamorph to work so I can change how it looks.

try to type fastboot oem unlock

You do not need to unlock.
You used the one click root.
Now download Rom Manager and flash the Clockwork Recovery.
There, now you suddenly have a custom recovery, can flash custom roms, and flash custom themes on top of the roms.
And you still have a locked bootloader.
You don't even need to manually go into the recovery to flash your roms and themes, Rom Manager will do it for you. Chose the rom or update.zip file for the theme and it will automatically reboot and flash it for you.
From clockwork you can also make a backup of your phone. Through Rom Manager choose to back it up, and it will restart and do a nandroid backup for you automatically.

try to type fastboot oem unlock (Done but it just responds wait for device)
Now download Rom Manager Done and it seemed to back up my OEM Rom no problem and flash the Clockwork Recovery. Question is this over writing existing Nexus One ROM because as I said since really have nothing against OEM ROM I would like to keep it?
There, now you suddenly have a custom recovery, can flash custom roms, and flash custom themes on top of the roms. At this point my phone would be powered up with the Clockwork Recovery ROM? I want to use Metamorph to flash themes on top of the Nexus One ROM
And you still have a locked bootloader.Well if Clock Recovery does the job and at the end of the day I get OEM 2.2 ROM which I can theme with Metamorph I am ok never unlocking the Bootloader.
You don't even need to manually go into the recovery to flash your roms and themes, Rom Manager will do it for you. Chose the rom or update.zip file for the theme and it will automatically reboot and flash it for you.
Yes Understood I have the program
From clockwork you can also make a backup of your phone. Through Rom Manager choose to back it up, and it will restart and do a nandroid backup for you automatically. But as the questions above do I really what to keep the Clockwork Recovery ROM. I do not know what the Clockwork recovery ROM does but I do just want to theme my Nexus One OEM ROM.
So let me see if I got the steps straight.
Head to the download section find the Clockwork recovery ROM.
Copy it to my SD Card.
Open ROM Manager and install it.
Reboot my Nexus One, the ROM manager forces the Reboot and I will be running my phone with Special ROM, old version of Android?
Then do I load my back my OEM ROM and modify it with Metamorph?
or is what loading the Clockwork ROM actually do is it is not a full ROM when I load it with ROM Manager what it does is add to my existing OEM ROM. This process will then let me modify the ROM with themes. When I reboot after loading the Clockwork ROM I will find the phone looks and behaves the same as always "running Android 2.2" but the Clockwork ROM will add files and when I use Metamorph it will work......
............. Man I am such a noob, but i guess at one time we were all noobs.

You are still mixed up:
Clockwork is not a rom. It is just replaces the stock recovery.
To install the Clockwork Recovery you:
1. Download Rom Manager
2. Press the first item "Flash ClockworkMod Recovery"
Done, nothing has changed, except your recovery partition is now different, which allows the flashing of other stuff.
Anything you do from now on could wipe your curent install, so make sure things are backed up in case you want to go back.
Now from Rom Manager you can flash any other rom or update.zip
The biggest issue you might face is that I don't think you can theme the stock froyo rom. You will need a special de-odexed rom. So you would have to go to the development section and find a custom 'stock' rom. Then flash that one though Rom Manager.
Keep in mind, when you do all this, you will not get any OTA updates anymore either, unless you flash back to the real stock rom and the stock recovery. But most people don't care, since the custom roms will be updated eventually to the latest, if not before.

Clarkster said:
You are still mixed up:
Clockwork is not a rom. It is just replaces the stock recovery.
To install the Clockwork Recovery you:
1. Download Rom Manager
2. Press the first item "Flash ClockworkMod Recovery"
Done, nothing has changed, except your recovery partition is now different, which allows the flashing of other stuff.
Anything you do from now on could wipe your curent install, so make sure things are backed up in case you want to go back.
Now from Rom Manager you can flash any other rom or update.zip
The biggest issue you might face is that I don't think you can theme the stock froyo rom. You will need a special de-odexed rom. So you would have to go to the development section and find a custom 'stock' rom. Then flash that one though Rom Manager.
Keep in mind, when you do all this, you will not get any OTA updates anymore either, unless you flash back to the real stock rom and the stock recovery. But most people don't care, since the custom roms will be updated eventually to the latest, if not before.
Click to expand...
Click to collapse
I need to learn how to use the search better. If I had read this first I assume I could have updated the radio without unlocking the bootloader. arg.

Yes I did not understand, ROM Manager first entry is Clockwork Recovery.
You said I can install themes using ROM manager?
I click on "Install ROM from SD Card", I had a pretty scary moment not know what I am doing I tried it the phone reboot to an "exclamation mark and Android". I pulled the battery and it booted.
This make me wonder if yor find an unstable theme or ROM how can you use ROM manager to restore a backup?
Could the reason Metamorph did not work is having "Clockwork Recovery"?

AstroDigital said:
Yes I did not understand, ROM Manager first entry is Clockwork Recovery.
You said I can install themes using ROM manager?
I click on "Install ROM from SD Card", I had a pretty scary moment not know what I am doing I tried it the phone reboot to an "exclamation mark and Android". I pulled the battery and it booted.
This make me wonder if yor find an unstable theme or ROM how can you use ROM manager to restore a backup?
Could the reason Metamorph did not work is having "Clockwork Recovery"?
Click to expand...
Click to collapse
Sorry, but I am going to have to recommend you do a lot more reading in the development section, the wiki, and all the sticky posts. Don't try anything until you understand how linux works, partitions, bootloaders, how Android roms work, even how a metamorph works.
Spend a few weeks or a month reading about everything, through the whole threads before trying to jump in. That's how I learned everything.
You seem intelligent enough to do everything, but what you lack is an actual understanding of what those things are, so you just need to spend a lot more time on it.
When you do fully understand everything, it will be a breeze and you will enjoy it a lot more. You will be less likely to completely screw your phone, and if you do you will know exactly how to recover.

I need to learn how to use the search better. If I had read this first I assume I could have updated the radio without unlocking the bootloader. arg.
You saying yes it is true I need to unlock bootloader?
Sorry, but I am going to have to recommend you do a lot more reading in the development section, the wiki, and all the sticky posts. Don't try anything until you understand how linux works, partitions, bootloaders, how Android roms work, even how a metamorph works.
You maybe right, maybe I should give up for now. Learn to do a backup and restore using nandroid. Just not sure how much time I am willing to invest just to gain the able to put themes on my phone.

AstroDigital said:
I need to learn how to use the search better. If I had read this first I assume I could have updated the radio without unlocking the bootloader. arg.
You saying yes it is true I need to unlock bootloader?
Click to expand...
Click to collapse
Yeah, you shouldn't do anything yet, read up on stuff for fun until you know what is going on.
For instance, in what I quoted above, you understood the exact opposite of what he was saying.
He was upset that he didn't find out about this way to root before he unlocked. He didn't have to unlock and is now disappointed he did.

OP. What ROM are you currently running? Stock FRF91 or something else?
To my understanding you need a De-Odexed ROM to apply themes that modify the framework.

[Q] Help (Rooting/Brick issue)

I will try to be as detailed as possible. I have been long time user here, but this is the first time I'm posting. I usually read the instructions and posts and that usually suffices my needs. I was on a rooted galaxy note running chasmodo's assylum rom for quite some time now. For Flashing a new rom, I used to go to recovery mode, flash abbysnote kernel (v 3.9) and install a new rom. A few days ago i tried to flash Ezaechiel XXLT6 KM edition - V2.1. I guess I should have checked md5 of the downloaded rom coz after flashing it, my phone refused to boot up. It always took me to the recovery mode screen where i tried to install abyssnote kernel and reinstall assylum. but it didn't work. So I went to dr. ketan's post and tried to flash a pre rooted rom (SGN_XX_OXA_KJ1_FACTORYFS.zip) using pc odin. Now my phone works fine but i'm on ginger bread. I tried to flash new roms using recovery mode (abbyssnote kernel method) but no new rom can be installed. Everytime I try to install a new rom i face boot loop or get stuck on the setup screen. So I follow the PC odin method to flash the same pre rooted rom (SGN_XX_OXA_KJ1_FACTORYFS.zip) to get my phone working again. I would like to go back to assylumrom because i got used to aosp jellybean so much now. Anybody who has faced a similar problem in the past, please help

Use one of PhilZ kernels and then in his recovery prepare your device for a clean install (there is an option that does more than only "factory reset". With the old ones you didn't clean /preload.
Then follow the instructions to install your preferred Rom.

Thanks
ThaiDai said:
Use one of PhilZ kernels and then in his recovery prepare your device for a clean install (there is an option that does more than only "factory reset". With the old ones you didn't clean /preload.
Then follow the instructions to install your preferred Rom.
Click to expand...
Click to collapse
Thanks for the quick reply thaidai. I will try the method and get back to you I used to do a clean wipe every time.

Mate first upgrade your stock ROM to ICS or JB. The ROMs like Asylum aren't supposed to be installed in GB, so first upgrade, then root and do a full wipe (data,cache,preload,dalvik) and get back to flash the ROM. No need to flash the Abyssnote every time, why do you do that?

Varad297 said:
Mate first upgrade your stock ROM to ICS or JB. The ROMs like Asylum aren't supposed to be installed in GB, so first upgrade, then root and do a full wipe (data,cache,preload,dalvik) and get back to flash the ROM. No need to flash the Abyssnote every time, why do you do that?
Click to expand...
Click to collapse
I tried installing Cassies Xtraliterom XLC1 after the PC odin method. Got boot loop. What I'm basically saying is, after trying the PC odin method to rescue the device, I can't seem to install any other rom on it using the recovery mode route. Not even other GB roms. What am I to do??

Varad297 said:
Mate first upgrade your stock ROM to ICS or JB. The ROMs like Asylum aren't supposed to be installed in GB, so first upgrade, then root and do a full wipe (data,cache,preload,dalvik) and get back to flash the ROM. No need to flash the Abyssnote every time, why do you do that?
Click to expand...
Click to collapse
I started using abyssnote kernel to install new roms after the "brick scare" of last year after which a lot of developers started recommending the method. I used to change between GB, ICS and JB roms easily using the abyssnote kernel. Don't know why it's not working anymore.

Trying to install 4.4 Rom, falling at every hurdle.

Hi There,
Just wondering if anyone had any ideas why my phone refuses to co-operate!
Basically, after getting bored of the stock rom when I first got my phone, I somehow managed to install a CM based rom. That worked, but I got bored of the fact that the camera never seemed to work right, and some apps didn't work/ were graphically buggy. Assuming it was just a badly ported graphics driver or whatever, I found a way, using FlashTool, to revert to the stock rom (C6603_10.3.1.A.0.244_Generic UK to be precise). I wasn't sure exactly what it did, but it was back how it used to be. sorted.
So, since kitkat made it's way to the XZ, I thought I'd try one of those roms, being the curious bugger that I am. The process I ended up going with eventually was:
>Downgrading Kernel to a lower version because the root explot wouldn't work on 10.3.1.A.0.244
>Rooting using "DooMLoRD_Easy-Rooting-Toolkit_v18"
>Upgrading kernel to one that would accept a recovery
>Installing TWRP
>Booting into recovery, CWM appeared instead. Strange, I thought. Oddly, mount USB wouldn't work at all, so I had to boot the phone back up to transfer the kitkat rom over
>Trying to flash the rom gave me an error number 7
>Boot Loop, at which point I just flashed 10.3.1.A.0.244 again.
I've tried this twice now, first with DooM Kernel, and then once with a different one. Neither CWM or TWRP have worked properly. Any help? Or am I just cursed?
Cheers

Tried this again, did literally everything I could think of and still no dice. Help? Have I somehow forced my phone to be on stock software forever?

If you dont unlock your bootloader, you can not use any kind of custom kernel.
That means aosp or aokp based firmwares can not run over locked bootloader.
Locked bootloader checks sign of kernel, if not certificated you will stuck on bootloop.
If you want to use any kind of custom rom... basicly.
1. Backup ta partition. " so you can revert any time you want."
2. Copy firmware zip file tou your internal or external sdcard.
3. Flash custom kernel. "Most of kernel have recovery option build in".
4. Boot in recovery mod. "Mostly press volume down while booting"
5. Insall custom rom.
6.a wipe dalvik-cache
6.b factory reset
Old setting might work or not with new rom. So first try to wipe dalvik- cache. If you stuck on boot loop or any kind of problem, just boot in recovery again and run factory reset.
Sent from my C6603 using Tapatalk

eryen said:
If you dont unlock your bootloader, you can not use any kind of custom kernel.
That means aosp or aokp based firmwares can not run over locked bootloader.
Locked bootloader checks sign of kernel, if not certificated you will stuck on bootloop.
If you want to use any kind of custom rom... basicly.
1. Backup ta partition. " so you can revert any time you want."
2. Copy firmware zip file tou your internal or external sdcard.
3. Flash custom kernel. "Most of kernel have recovery option build in".
4. Boot in recovery mod. "Mostly press volume down while booting"
5. Insall custom rom.
6.a wipe dalvik-cache
6.b factory reset
Old setting might work or not with new rom. So first try to wipe dalvik- cache. If you stuck on boot loop or any kind of problem, just boot in recovery again and run factory reset.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Hey, thanks for your reply!
I had unlocked the bootloader when I first got the phone and just assumed it would be permanent. Would flashing it back to stock firmware re-lock the bootloader?
But yes, assuming my boot loader is still unlocked ( I have tried to check and it doesn't seem to be locked) I have been through those steps basically. I am fine to flash a kernel with a recovery but the recovery never works properly/ at all. I can root the phone no problem though.

Best to extract the boot.img from the zip file of the ROM you want to flash, and flash that first. Then flash the ROM from its recovery.
Sent from my C6603 using xda app-developers app

shoey63 said:
Best to extract the boot.img from the zip file of the ROM you want to flash, and flash that first. Then flash the ROM from its recovery.
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
Cheers, I'll give that a go - I was under the impression that you weren't supposed to flash kernels that weren't designed for the currently installed ROM though? It just seems that any kernel I flash isn't working properly so I didn't think doing that would play any nicer with the phone

SuburbanKnight said:
Cheers, I'll give that a go - I was under the impression that you weren't supposed to flash kernels that weren't designed for the currently installed ROM though? It just seems that any kernel I flash isn't working properly so I didn't think doing that would play any nicer with the phone
Click to expand...
Click to collapse
You're not actually going to boot into your current rom after flashing the kernel.
Flash the kernel via fastboot, then boot into recovery and flash the rom.
All this should be covered in the installation instructions of whatever rom you're trying to flash in any case....
Sent from my C6603 using Tapatalk

Well, that seems to have done it! Thanks very much for your help.
So, I guess the moral here is that if you're on stock and need a recovery to flash a new ROM, always use the boot.img from the ROM you'll be using.
Thanks again - I'd never seen that said before but quite possibly I wasn't paying attention!

(Q) Any way to flash a rom without needing an FTF

As the title states, is there a way to flash a new rom without being tied down to a PC / laptop?
Bootloader's unlocked, rooted, it's strange how with this phone we're forced to stay locked down to a PC.
Have never flashed anything from the Original Dev section on this phone yet, would that be the same method as normal rom's like monx's and IHackers?
Cheers.

huh? TFTs are for returning to stock ROM and/or kernel and baseband, custom ROMs come in ZIP files which are flashable in recovery. What I do is download the ROM zip on my phone and flash it straight after via recovery, no need for a computer at all.

tomascus said:
huh? TFTs are for returning to stock ROM and/or kernel and baseband, custom ROMs come in ZIP files which are flashable in recovery. What I do is download the ROM zip on my phone and flash it straight after via recovery, no need for a computer at all.
Click to expand...
Click to collapse
FTF's are not just for returning to stock, not at all, they're used to flash rom's too as the kernel and baseband needs to be flashed also.
Check out monx's thread, the instructions for install states to flash the rom and then without allowing a reboot, flash kernel and system (afaik)
Simply flashing the rom wouldn't be enough without flashing those files via flashtool.
What i'm trying to ascertain is do I have to do this every time as it's a pain in the backside.
Quote from Monx
LOCKED & UNLOCKED BOOTLOADER
BACKUP any critical data to microSD
Copy this rom zip package to microSD
Reboot in recovery, (do nandroid backup), do factory reset & install rom until finish
IGNORE RECOVERY INSTALLATION WARNING. SELECT NO & PROCEED AT THE END OF RECOVERY IF USING CWM RECOVERY
Skip (x) steps if u already running same base firmware with latest monxDIFIED base rom. Else, proceed.
(x) Turn off device. (Hold power button + vol up until vibrates 3 times) [or use recovery turn off device option, if any]
(x) Flash latest Sony's firmware (FTF) matching current latest monxDIFIED base rom using latest flashtools. UNCKECK all WIPE options and CHECK only SYSTEM & TA in EXCLUDE options.
(x) Disconnect USB cable & turn on phone. Done.

Notice how I write "and/or kernel and baseband"?
FTF only necessary if changing bases, don't need to flash every time going from ROMs on same base.
Sent from my C6903 using Tapatalk

tomascus said:
Notice how I write "and/or kernel and baseband"?
FTF only necessary if changing bases, don't need to flash every time going from ROMs on same base.
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
Because you wouldn't be performing a full wipe right?
Thing is I would never do a dirty flash over another rom, you're asking for problems if you do, so in which case I'm guessing that I'd need to use an FTF file to replace the files needed that aren't flashed with the rom right?
Thanks by the way.
Reason i'm asking all this is because this is the first phone that i've had were i've needed to be tied down to a PC to flash a rom, it's a bit crap really.

dladz said:
Because you wouldn't be performing a full wipe right?
Thing is I would never do a dirty flash over another rom, you're asking for problems if you do, so in which case I'm guessing that I'd need to use an FTF file to replace the files needed that aren't flashed with the rom right?
Thanks by the way.
Reason i'm asking all this is because this is the first phone that i've had were i've needed to be tied down to a PC to flash a rom, it's a bit crap really.
Click to expand...
Click to collapse
I used to have the HTC One X which required the same trouble-some computer steps.
The kernel and baseband don't even get affected when you do a full wipe, they're separate from the system, data, and cache partitions which gets wiped. Basically the stripped FTF holds the stock kernel and baseband needed to get compatible mobile signal and this only needs to be done once moving from base to base.
Going to and from ROMs with same base:
1. Full wipe
2. Flash ROM
ps. some ROMs flash their own kernel during ROM install i.e iHackers.

tomascus said:
I used to have the HTC One X which required the same trouble-some computer steps.
The kernel and baseband don't even get affected when you do a full wipe, they're separate from the system, data, and cache partitions which gets wiped. Basically the stripped FTF holds the stock kernel and baseband needed to get compatible mobile signal and this only needs to be done once moving from base to base.
Going to and from ROMs with same base:
1. Full wipe
2. Flash ROM
ps. some ROMs flash their own kernel during ROM install i.e iHackers.
Click to expand...
Click to collapse
Nice one m8, that's put an end to my misery, cheers for that, makes a lot of sense now, i wasn't aware of how Sony rom's were flashed, it's strange as the bootloader is unlocked? What more is needed lol.
As for the one x, that's the only HTC i skipped and glad i did apparently they had a lot of problems with flashing and stuff, S-OFF.
Anyway, thanks m8.

C6903 unlocking -> root -> drm -> recovery.

Guides are over detailed and confusing...
I installed kingroot long ago to try get somewhere.
This has screwed up the stock update system and root is lost after each reboot.
So time to go full custom in hopes that the phone will be able to update and run root apps, be junk free and run like a beast.
i have read so many thread for months now and i am getting more and more confused.
i'm on 5.1.1.
please if anyone has the time run me thru the process.

What do you mean root is lost after each reboot??
And what exactly are you trying to achieve?

If i use kingroot and reboot root no longer works.
So i have to root again.
I want to pretty much reflash stock or switch to custom rom.
My stock rom is acting very sick.

Oh OK. But u shouldnt mess with DRM keys or the bootloader on your first go - flashing a stock based custom ROM is what you should do. Its a good start for a newbie
1. Root ur phone using kingroot
2. Install XZDR - XZ dual recovery ( it installs a recovery for flashing ROMs and mods)
3. Download your ROM of choice( dstrikers , kryptonian etc are stock based and hence donot require an unlocked bootloader, u can flash them straight and not have to worry about anything else.)
4. Reboot to recovery ( after installing XZDR you get an app that let's you reboot to recovery)
5. Wipe the data partition( as the name suggests , it contains all ur apps and data , so back up everything) so that all the old settings and configuration doesn't mess up your new ROM.
6. Flash the ROM and reboot
7. There,you have a custom ROM on your phone
It might be confusing at first but there are lots of videos on YouTube detailing each of the steps above watch them.
Have fun.

ahh thanks!
you legend.

Glad to know I helped