Database Develop

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!

New to flashing custom rom

So I've rooted, unlock bootloader but still encrypted on my nexus 6. So far I went with Franco kernel & ViperAudio that's about it and I'm enjoying it.
I'm wanting to flash a custom ROM very soon and I'm new to this. Ive made backups thru twrp with nandroid already.So please bare with me.
Questions
Do I have to be decrypted before flashing a ROM?
Can I load viperaudo.zip & Franco kernel.zip along with Custom ROM, Gapps & SuperSU at the same time on Twrp?
From videos I've seen people just wipe on twrp and then install the ROM, is this a safe? Or is it better to a full factory wipe.
After flashing a ROM, will my old files still be there like pictures ive taken, stuff that I download & will my old apps be there still.
Thank you in advance.

1. its your choice, to stay encrypted or to decrypt. im still encrypted and running terminus rom
2. yes. but tge rom will always be the first flash, since itll overwrite anything you flash before it.
3. i normally dirty flash, meaning i dint wipe a single thing when flashing. that way i lose nothing. but, i always have a nandroid backup, just in case.
4. first off, your storage never gets touched, unless you wipe it yourself. if you dirty flash, you lose nothing. if you clean flash, you factory reset the phone and need to reinstall your apps, through backup of somekind or manually.

simms22 said:
1. its your choice, to stay encrypted or to decrypt. im still encrypted and running terminus rom
2. yes. but tge rom will always be the first flash, since itll overwrite anything you flash before it.
3. i normally dirty flash, meaning i dint wipe a single thing when flashing. that way i lose nothing. but, i always have a nandroid backup, just in case.
4. first off, your storage never gets touched, unless you wipe it yourself. if you dirty flash, you lose nothing. if you clean flash, you factory reset the phone and need to reinstall your apps, through backup of somekind or manually.
Click to expand...
Click to collapse
So flash the ROM, gapps and super su as the thread of the ROM says and then use the ROM for a bit and then twrp and flash ViperAudio and kernel...
So if I lose nothing do I need to reinstall the apps...
Thanks for the response

jussaren said:
So flash the ROM, gapps and super su as the thread of the ROM says and then use the ROM for a bit and then twrp and flash ViperAudio and kernel...
So if I lose nothing do I need to reinstall the apps...
Thanks for the response
Click to expand...
Click to collapse
id flash viper and your kernel at the same time, with the rim, gapps, abd supersu. if you dirty flash, you lose nothing. all you do is update what you already have. your apps stay. buts thats only during a "dirty" flash

simms22 said:
id flash viper and your kernel at the same time, with the rim, gapps, abd supersu. if you dirty flash, you lose nothing. all you do is update what you already have. your apps stay. buts thats only during a "dirty" flash
Click to expand...
Click to collapse
So for my case, stock and rooted and to install this ROM what are the primarily steps instead of dirty flashing. I wanna do everything from the phone.
Sorry for being a noob. I know if I fuxk up anything I can always revert to my nandroid backup.

Stock on Google Unlock screen after flashing recovery? How long? Details below

1.) I decided to install Franco Kernel to see what positive effects if any it had on Light Flow.
2.) Before hand I did a full Backup in TWRP checked everything Boot, Recovery, System, System Image, Data, and Cache.
3.) I installed Franco Kernel No problem, but didn't see any advantages so I Decided to revert back
4.) I ran a TWRP Restore with all the same Items Checked, it finished and Now I stand on the Google screen with the unlocked bootloader Icon and nothing else happening.
I cant even figure out how to connect it to ADB or Wug's Nexus Root Toolkit since it won't show on USB...How do I reboot into a safe mode, nothing seems to work.

Follow UP...
I managed to boot into TWRP recovery again...and it said no OS installed...So I decided perhaps I had checked too many and just re-ran System Image only. It now boots but I still have Franco Kernel..I don't mind it but would rather go stock.
I thought System Image included the Kernel.. Is there an easy way to go back to the original kernel?

flipper44 said:
I managed to boot into TWRP recovery again...and it said no OS installed...So I decided perhaps I had checked too many and just re-ran System Image only. It now boots but I still have Franco Kernel..I don't mind it but would rather go stock.
I thought System Image included the Kernel.. Is there an easy way to go back to the original kernel?
Click to expand...
Click to collapse
Go back to TWRP Restore and check the box for boot only. If you backed up boot it should flash the stock kernel.

flipper44 said:
I managed to boot into TWRP recovery again...and it said no OS installed...So I decided perhaps I had checked too many and just re-ran System Image only. It now boots but I still have Franco Kernel..I don't mind it but would rather go stock.
I thought System Image included the Kernel.. Is there an easy way to go back to the original kernel?
Click to expand...
Click to collapse
There is a thread called:
'How to flash a new boot.img via Fastboot'
But... Franco's kernel is better for your battery.

NLBeev said:
There is a thread called:
'How to flash a new boot.img via Fastboot'
But... Franco's kernel is better for your battery.
Click to expand...
Click to collapse
Probably will Go back to Franco, But since I just got this I should probably monitor what I do and don't like over the weekend before choosing my daily Driver Kernel and Rom. Thanks to you both.

prdog1 said:
Go back to TWRP Restore and check the box for boot only. If you backed up boot it should flash the stock kernel.
Click to expand...
Click to collapse
That was Brain Freeze, and minor panic LOL...for some reason I wasn't processing Boot = Kernel..Thanks to both people who answered.

can't flash kernel and rom

Hi there! I want to test the official CM12.1 rom so I decided to format the phone and flash a custom kernel and then the rom.
First I flashed TWRP (2.8.7.0) using fastboot and enter it. I made a complete wipe using the advanced wipe and marking all options (except usb-otg).
Once the partitions are clean I flashed the kernel using the install option and selecting the zip file, finally the same for the CM12.1 rom (nightly). Wiped cache and dalvik and restart, but somehow miui reinstalled.... (it is possible to completely delete miui?). The kernel seems to be the stock (3.4.0-g7f72d41-01413-g70bd50e).
I read in the official CM12.1 post that the rom automatically extends the system partition (merging the two system partitions to have a partition with 1.28GB), is this true or do I have to do it manually (flashing something?).
Thanks.

Flash this once and your partition will be 1.2 GB.

Thanks! Is it normal that it still shows just 629MB? (I can see it in the repair/resize/change-file-system section).
Now, every rom that I flash it stucks at the "mi boot logo"... Maybe I'm doing something wrong; I wipe/factory reset (including cache/dalvik) and then flash the zip, and (wipe again, the option at the left to reboot) and reboot to system.... It's stuck, I tried with other custom roms and it happens the same. What am I doing wrong??

Did you switched the partition (system 1 for non - miui and system 2 for miui)? It's located in advanced options in cwm.

pratyush997 said:
Did you switched the partition (system 1 for non - miui and system 2 for miui)? It's located in advanced options in cwm.
Click to expand...
Click to collapse
I'm using TWRP. So I have to flash CWM to extend the partition?

ChazyTheBest said:
I'm using TWRP. So I have to flash CWM to extend the partition?
Click to expand...
Click to collapse
I do not use TWRP, can't help you.

ChazyTheBest said:
I'm using TWRP. So I have to flash CWM to extend the partition?
Click to expand...
Click to collapse
Yes, the repartition zip only works on CWM. People said that they have problem while repartitioning with TWRP.

zzvilzz said:
Yes, the repartition zip only works on CWM. People said that they have problem while repartitioning with TWRP.
Click to expand...
Click to collapse
did you solve your problem?...im having that same problem of you :crying:

Using Megapixel ROM with Elemental X kernel?

Woops. Wrong section. Please disregard.

In the wrong forum section (you're in Nexus 6, not 6p). But here is a 100% foolproof answer.
I don't know if it will work. But what you should do: in TWRP make a backup of your boot partition. This contains your kernel and RAMdisk. Flash ElementalX and then wipe cache/dalvik. If it doesn't boot or acts wonky, boot back into TWRP and restore boot then wipe cache/dalvik cache. You will now boot back with your original kernel. Also if you're messing with different kernels always be on the stock kernel before you flash. So if you wanted to swtich from Elemental X to Kylo Kernel, make sure you restore back to stock kernel before flashing the newer kernel. Usually you can flash kernels over top of each other, but not always so it's best to take 1 minute and backup the boot partition before messing with kernels. Good luck.

Dopamin3 said:
In the wrong forum section (you're in Nexus 6, not 6p). But here is a 100% foolproof answer.
I don't know if it will work. But what you should do: in TWRP make a backup of your boot partition. This contains your kernel and RAMdisk. Flash ElementalX and then wipe cache/dalvik. If it doesn't boot or acts wonky, boot back into TWRP and restore boot then wipe cache/dalvik cache. You will now boot back with your original kernel. Also if you're messing with different kernels always be on the stock kernel before you flash. So if you wanted to swtich from Elemental X to Kylo Kernel, make sure you restore back to stock kernel before flashing the newer kernel. Usually you can flash kernels over top of each other, but not always so it's best to take 1 minute and backup the boot partition before messing with kernels. Good luck.
Click to expand...
Click to collapse
Yeah I just realized that. Thank you so much for the advice! So I wipe cache/dalvik after flashing Elemental X correct?

BainStain said:
Yeah I just realized that. Thank you so much for the advice! So I wipe cache/dalvik after flashing Elemental X correct?
Click to expand...
Click to collapse
That's what I always do, (wipe cache/dalvik after the kernel) but wiping it before would have the same effect. Some people say it's not necessary to wipe cache/dalvik but I always have. Rather be safe than sorry. All it does is make your boot a little longer by doing the "Optimizing app X of XX" before booting into Android.