Database Develop

[Q] Just a few questions ;)

What i have done in the last 24 hours:
1. Updated to 4.3 on stock ROM
2. Unlocked bootloader on my Z1
3. Flashed "PhilZ Touch 6" dual bootloader (idk what "dual means" :S) (Dec 3 2013 version)
4. Used the built in root tool in "PhilZ" to root my phone and installed the corresponding app "SuperSU"
Questions:
Does bootloaders come with a custom kernel?
My bootloaders "About" says its made for the "Z" (not Z1). Did i **** up or is this incorrect?
If i flash kernel (for my device) via CWM will i break something?
Does roms require a certain kernel?
Can i flash .img files via CWM or is it required that the file is .zip?
I see kernels on the forum that advertise being 4 kitkat, do i need to flash that kernel WITH a kitkat rom to use that kernel?
Why shuld i flash a kernel?
As CM is not officially supported on the Z1 yet is there a cool alternative rom i can use?
Thats all the Q's i came up with, hope you can help me answer my ridiculous questions and wish me luck on my first android phone! :good:

bump

I won't get my device until tomorrow, but there a few things I could explain:
Some ROMs need to have a specific kernel. You cannot use Stock kernel with Cyanogenmod, or vice versa. Custom kernels are often a good idea to flash if you want some extra optimizations, you can get extra performance and save battery life with an enhanced kernel.
As for an alternative ROM, why don't you just check out the dev forums? There are Cyanogenmod ROMs, they're just unofficial.
Also, did you back up your TA? Otherwise, you'll be in for some real big trouble.

kusanou said:
I won't get my device until tomorrow, but there a few things I could explain:
Some ROMs need to have a specific kernel. You cannot use Stock kernel with Cyanogenmod, or vice versa. Custom kernels are often a good idea to flash if you want some extra optimizations, you can get extra performance and save battery life with an enhanced kernel.
As for an alternative ROM, why don't you just check out the dev forums? There are Cyanogenmod ROMs, they're just unofficial.
Also, did you back up your TA? Otherwise, you'll be in for some real big trouble.
Click to expand...
Click to collapse
****, i did not backup my TA. What does that mean for me?
I read in some threads that TA only gives you the option to revert back to absolute factory defaults. As i am having no problems i dont see why i would do that.
Edit: Thats wierd, my TrackID still works after unlocking bootloader, flashing recovery and rooting. Am i super lucky?

mrzone64 said:
****, i did not backup my TA. What does that mean for me?
I read in some threads that TA only gives you the option to revert back to absolute factory defaults. As i am having no problems i dont see why i would do that.
Edit: Thats wierd, my TrackID still works after unlocking bootloader, flashing recovery and rooting. Am i super lucky?
Click to expand...
Click to collapse
It's mostly needed for Bravia engine stuff, as well as the BIONZ image processor. I guess if you don't care too much about that, and you don't have any reason to have to go back to absolute factory settings in the case of a warranty return, then it should be fine.

Flashing custom roms on C6606

Ok guys, i figured i've refrained from customizing my phone long enough.
I'm well aware of how to flash things onto the phone. I am currently running 4.2.2 on my C6606.
I have dualboot recovery flashed onto it, phone is rooted, and the only mod i have is pure audio.
I know i have to unlock my bootloader to be able to flash roms that require a custom kernel.
My question is, is there anything i should lookout for before flashing onto my phone?
I just want to know if these roms will also work on the t-mobile network. Haven't seen too much activity from C6606 users on here, so i'm a bit curious on that.

I don't believe you can unlock the bootloader on a C6606. If you could, you would need to back up your AT? partition; the one that has all your DRM keys and stuff. But you can still flash custom roms that are made for locked bootloaders, with stock kernels... I have flashed the stock roms from other regions and never had a problem with my C6606 working on the T-Mobile network.
Good luck!

i flashed NUT's 4.3 rom from 4.2 and running that, we have a locked bootloader which means we cant use a custom kernel. sony's ramdisk layout is bit different then im used to, im used to standard boot.img format on many devices. anyways the dual recovery script allows for booting custom ramdisks, if i can get a cm one setup and going then we could have cm booting on locked bootloaders. this is no easy task and something i have never done before, not to mention there may be issues that isnt there with a custom kernel.

shabbypenguin said:
i flashed NUT's 4.3 rom from 4.2 and running that, we have a locked bootloader which means we cant use a custom kernel. sony's ramdisk layout is bit different then im used to, im used to standard boot.img format on many devices. anyways the dual recovery script allows for booting custom ramdisks, if i can get a cm one setup and going then we could have cm booting on locked bootloaders. this is no easy task and something i have never done before, not to mention there may be issues that isnt there with a custom kernel.
Click to expand...
Click to collapse
Being able to get CM on the Z without unlocking the bootloader would be awesome.

iDroid8 said:
Being able to get CM on the Z without unlocking the bootloader would be awesome.
Click to expand...
Click to collapse
well i dont want peopel to get their hopes up about myself, its no easy feat and i applied for motorola financing last week, as i might end up going with a moto x. the bill with tmobile is a bit more than expected and going with a moto x would mean unlocked bootloader as well as lower monthly payments. you guys have some very talent people working on this device, it may end up happening on the z1 first and then get backported.

shabbypenguin said:
well i dont want peopel to get their hopes up about myself, its no easy feat and i applied for motorola financing last week, as i might end up going with a moto x. the bill with tmobile is a bit more than expected and going with a moto x would mean unlocked bootloader as well as lower monthly payments. you guys have some very talent people working on this device, it may end up happening on the z1 first and then get backported.
Click to expand...
Click to collapse
I'm just finding the process quite confusing. I haven't found any good videos detailing the entire process for a retard (myself).

iDroid8 said:
I'm just finding the process quite confusing. I haven't found any good videos detailing the entire process for a retard (myself).
Click to expand...
Click to collapse
videos on what?

shabbypenguin said:
videos on what?
Click to expand...
Click to collapse
Of flashing CM11. Most people aren't helpful and say if I can't unlock a bootloader then I shouldn't flash ROM's.

iDroid8 said:
Of flashing CM11.
Click to expand...
Click to collapse
its not possible with a locked bootloader at this time.

sbackus said:
I don't believe you can unlock the bootloader on a C6606. If you could, you would need to back up your AT? partition; the one that has all your DRM keys and stuff. But you can still flash custom roms that are made for locked bootloaders, with stock kernels... I have flashed the stock roms from other regions and never had a problem with my C6606 working on the T-Mobile network.
Good luck!
Click to expand...
Click to collapse
shabbypenguin said:
i flashed NUT's 4.3 rom from 4.2 and running that, we have a locked bootloader which means we cant use a custom kernel. sony's ramdisk layout is bit different then im used to, im used to standard boot.img format on many devices. anyways the dual recovery script allows for booting custom ramdisks, if i can get a cm one setup and going then we could have cm booting on locked bootloaders. this is no easy task and something i have never done before, not to mention there may be issues that isnt there with a custom kernel.
Click to expand...
Click to collapse
So say i tried to flash XperiaBlueLights, its a 4.2.2 rom, and it says its for a locked bootloader, it should work fine right?
Or the CriskeloRom, its 4.3 but it says it works on both locked and unlocked bootloaders. There shouldn't be an issue installing this on a C6606 should there?
Don't mean to ask so many questions, im usually the type to go and find out myself, but so far customizing my first sony phone isn't as fun, or easy as my past phones.

xDC23 said:
So say i tried to flash XperiaBlueLights, its a 4.2.2 rom, and it says its for a locked bootloader, it should work fine right?
Or the CriskeloRom, its 4.3 but it says it works on both locked and unlocked bootloaders. There shouldn't be an issue installing this on a C6606 should there?
Don't mean to ask so many questions, im usually the type to go and find out myself, but so far customizing my first sony phone isn't as fun, or easy as my past phones.
Click to expand...
Click to collapse
I think you would need to flash the C6606 kernel to be able to boot. I have written a C6606 tutorial for MIUI if you are interested in the Chinese version of Android. It is in the first post.
http://forum.xda-developers.com/showthread.php?p=46120012

C6606 user here. Currently running @niaboc79 4.3 Black Edition, and couldn't be happier.
I got my Z shortly after it became available, and have had a custom stock based ROM on it since day 1. I will admit there was a slight learning curve, but I knew I was switching to T-mobile and started reading up on the whole rooting/flashtool before I purchased and have stayed out of trouble (for the most part). Once you flash a ROM or two you will get the gist of it and it will become less confusing. The beauty of it is that we don't have to wait for T-Mobile to push out new Android versions. Once the Z gets it, so can we and no T-Mobile bloat. You will not have wifi calling if you haven't figured that out already.
Look for the "LB" (lockedbootloader) tag in the ROM title, and they should be good to go for us C6606 users.
Just follow the OP's instructions for installing and you will be fine. I haven't touched anything directly related to the C6606, other than APN's. I haven't had any luck doing the "download settings for internet and MMS" under wireless & networks settings.
I use these APN's every time I do a clean install and all network modes (3G, 4G, LTE) work just fine - http://forum.xda-developers.com/showthread.php?t=2236735

xDC23 said:
Ok guys, i figured i've refrained from customizing my phone long enough.
I'm well aware of how to flash things onto the phone. I am currently running 4.2.2 on my C6606.
I have dualboot recovery flashed onto it, phone is rooted, and the only mod i have is pure audio.
I know i have to unlock my bootloader to be able to flash roms that require a custom kernel.
My question is, is there anything i should lookout for before flashing onto my phone?
I just want to know if these roms will also work on the t-mobile network. Haven't seen too much activity from C6606 users on here, so i'm a bit curious on that.
Click to expand...
Click to collapse
yeah made sure you back your entire phone completely up! that way if something happens you can always go bck to the orginal state!

Custom Recovery Loop

I know a lot of people are in this sticky situation with me.
But hey guys, XDAers, Googlers, Developers & the rest of y'all
So I have a S3 Mini (with NFC so i8190N) and I hack it a lot, I mod, I do a lot of root-y stuff on it.
Well today's objective for my phone was to flash a Custom ROM that blended together TouchWiz and KitKat since I can't get that officially for my phone, I found LostVirginity V2 from the guy who made the Virginity ROMs (I forgot his name but big ups to him, thanks for the crazy cool ROMs bro!)
So I tried to flash it in TWRP.....and it didn't work because TWRP consistently freezes when I press anything and i have to do a battery pull.
Then I used Odin to flash CWM and it flashed it but when I rebooted it my phone decides to not listen and just go back to CWM like CWM has a leash on it or something, I mean come on! TWRP replaced you for a reason and you're trying to get us all back, you're old and forgotten CWM...
So now I've got that frigging annoying TWRP/CWM loop where whatever you do it just reboots to the custom recovery, pretty much the only thing I can do is use Odin to flash another custom recovery (only ones I can switch between are (any version of) CWM, PhilZ's Advanced CWM and any version of TWRP)
I've been trying everything, some guys on redmondpie, android central and rootzwiki (I think that was the website) fixed the problem on the ASUS Transformer Pad but they installed terminal emulator, I've got that but if I could access that that'd defeat the whole point of this thread because that would mean I'd have access to the Android system.
So my question is: Now that I'm imprisoned by the claws of the custom recovery, how do I escape?
Do I flash another firmware through Odin or something?
Somebody help me, and anybody who's been through this problem or is going through this problem at the moment, tell me what you did/what you're doing so we know what to rule out and stuff
Thanks guys

[Q] [Help] Changing custom ROM from eXistenZ Ultimate to another?

Hi, I rooted my Xperia z around 5 months ago and completely jumped straight into installing a custom ROM and not really done much after that and pretty much forgot everything I knew about rooting, ROM and kernels etc. - The ROM I currently have installed is eXistenZ 3.0.0 with build .283. i also have NDR Utils installed as my recovery option(?) - The installer i used was AROMA if that also helps with my problem. I can't even remember if i unlocked my bootloader or not, if there's a way to find out if it's locked/unlocked then i would be more than happy to try it
okaay so my problem is that I would like to change to a new custom ROM from the current ROM I have, I am aware of all the risks / dangers such as data loss etc. If you could post a tutorial for me to follow, i would be more than grateful. I hope you understand my problem Thanks for reading.
-Cynicaal :cyclops:

Cynicaal said:
Hi, I rooted my Xperia z around 5 months ago and completely jumped straight into installing a custom ROM and not really done much after that and pretty much forgot everything I knew about rooting, ROM and kernels etc. - The ROM I currently have installed is eXistenZ 3.0.0 with build .283. i also have NDR Utils installed as my recovery option(?) - The installer i used was AROMA if that also helps with my problem. I can't even remember if i unlocked my bootloader or not, if there's a way to find out if it's locked/unlocked then i would be more than happy to try it
okaay so my problem is that I would like to change to a new custom ROM from the current ROM I have, I am aware of all the risks / dangers such as data loss etc. If you could post a tutorial for me to follow, i would be more than grateful. I hope you understand my problem Thanks for reading.
-Cynicaal :cyclops:
Click to expand...
Click to collapse
This is from official Sony website
Please note! It will only be possible to unlock the boot loader for certain releases. You can check if it is possible to unlock the boot loader of your device in the service menu by following the steps below:
In your device, open the dialler and enter *#*#7378423#*#* to access the service menu.
Tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.
To change a rom, you would need
an unlocked bootloader or a ROM that supports locked bootloader
A custom recovery
a ROM zip.
Head to the ROM thread you want to flash and read the instructions carefully.
I hope this is enough, however, if you need any further assistance, make sure you quote me for an answer.
Good Luck

[Q] Can I upgrade from a 4.3 based CFW to 4.4.4 and keep my Custom Recovery

Hi Guys,
Hope someone a bit more clued up than myself can clarify my questions or guide me..
I've done some searching, but am not 100% confident.
So, I have a I9305 running a Boeffla Kernel 5.2. If I recall correctly, I upgraded from 4.1.2 to 4.3, but
kept my old bootloader. So I am rooted and have TWRP on this 4.3 based CFW. No KNOX anywhere.
(Did all this about 12 months ago or more, and have had some significant life events in the last year,
so have been completely out of the scene.. )
Anyway, I was considering upgrading to 4.4.4 (stock)
Can anyone tell me if I can do this and remain Knox free and have a custom recovery such as TWRP.
(If so can you point me to a working guide?)
Thanks Heaps in Advance,
BrikHaus

BrikHaus said:
Hi Guys,
Hope someone a bit more clued up than myself can clarify my questions or guide me..
I've done some searching, but am not 100% confident.
So, I have a I9305 running a Boeffla Kernel 5.2. If I recall correctly, I upgraded from 4.1.2 to 4.3, but
kept my old bootloader. So I am rooted and have TWRP on this 4.3 based CFW. No KNOX anywhere.
(Did all this about 12 months ago or more, and have had some significant life events in the last year,
so have been completely out of the scene.. )
Anyway, I was considering upgrading to 4.4.4 (stock)
Can anyone tell me if I can do this and remain Knox free and have a custom recovery such as TWRP.
(If so can you point me to a working guide?)
Thanks Heaps in Advance,
BrikHaus
Click to expand...
Click to collapse
Hi,
you have 3 options:
- Option #1: Stay with your old 4.1.2 firmware base with OLD bootloader and you can flash which custom KitKat ROM you want (N4 Elite ROM, TGP, AMCHA KK, etc.). If your favorite ROM is NOT compatible with TWRP, you will have to flash PHILZ recovery 6.48.4 instead and then flash the ROM. If the custom ROM is compatible with TWRP, you will only have to flash the ROM.
When you will flash the ROM, don't forget to choose a KK modem (XXUFNI3, XXUFNJ1 or XXUFOA1 depending on the ROM base) to have a working baseband and also, don't forget to choose a compatible Kernel with OLD bootloader (AGNi, HBO kernel or Dlite). Note : Stock kernel is not 100% compatible with OLD bootloader : WIFI will not work.
- Option #2: Upgrade to latest official 4.4.4 stock (I9305XXUFOC1) for i9305 with ODIN : this way, you will have new 4.4.4 KNOX bootloader and you will not have custom recovery anymore. If you want to stay like this, you will be 100% stock and 100% up-to-date from Sammy.
- Option #3: Follow the option #2 and then root your phone and flash custom recovery. You could finally stay like this or flash a custom ROM. If you choose to flash a custom ROM, one good thing is that you will be able to use stock kernel (100% working including WIFI) if available with this ROM.
You can follow that guide from @MaHo_66 : http://forum.xda-developers.com/gal...covery-i9305-cwm-philz-twrp-versions-t2694249
Reminder: To go VERY clean wipe and install a custom firmware :
1. Backup all your data
2. Full wipe (data, cache and dalvik) in recovery including internal sdcard (internal sdcard format option in mounts and storage settings)
3. Flash a i9305 official firmware (4.1.2, 4.3 or 4.4.4) via ODIN. IMPORTANT : If you don't want KNOX BL because of warranty purpose, don't flash official 4.3 or 4.4.4 via ODIN.
4. Root
5. Flash custom recovery : (Philz for instance)
6. Install custom ROM
Steps 4 and 5 can be permuted.
PS: Off topic : @MaHo_66, you're now a RC, well done !

Thanks @FLooDW
Btw. youre spot on as always helping others, very good explanation you gave here :good:

MaHo_66 said:
Thanks @FLooDW
Btw. youre spot on as always helping others, very good explanation you gave here :good:
Click to expand...
Click to collapse
Thanks
Ok, if it's good, I hope it will help BrikHaus.

FLooDW said:
Thanks
Ok, if it's good, I hope it will help BrikHaus.
Click to expand...
Click to collapse
Im pretty sure it will

Legend!
Thank you VERY MUCH @FLooDW! Wish I could give you 10x Thanks!
Just the answer I was after. I wasn't sure if it was even possible to have a custom recovery on KNOX 4.4.4 bootloader.
I dropped out of the scene just as KNOX raised its ugly head...
I'm not worried about the warranty at all. Phone is two years old and well out of warranty period.
I'll go Option #3, sounds like just what I was after.
Thanks again!

BrikHaus said:
Thank you VERY MUCH @FLooDW! Wish I could give you 10x Thanks!
Just the answer I was after. I wasn't sure if it was even possible to have a custom recovery on KNOX 4.4.4 bootloader.
I dropped out of the scene just as KNOX raised its ugly head...
I'm not worried about the warranty at all. Phone is two years old and well out of warranty period.
I'll go Option #3, sounds like just what I was after.
Thanks again!
Click to expand...
Click to collapse
Yes you can have custom recovery with Knox BL. It's my case and everything is ok for me.
I hope you'll be ok
Please let us know.

I saw your sig..
Philz looks like it has more features than TWRP.. Might try that.
How do you find your performance with that kernel & rom?
Cheers Mate.

BrikHaus said:
I saw your sig..
Philz looks like it has more features than TWRP.. Might try that.
How do you find your performance with that kernel & rom?
Cheers Mate.
Click to expand...
Click to collapse
I'm very happy about perf with latest Amcha and AGNi. I have between 26000 and 26600 in AnTuTu without any overclock.
User experience is great in my case.
I don't use Fly-on mod (available in Amcha for instance) because I've noticed some big lags with my config on my phone.

All went pretty well. Had a couple of hangs, but got them all sorted.
Currently restoring, but having an issue where the phone switches from "USB Media mode" to "Dock Mode" and back and forth.
Weird issue I've never seen before....

BrikHaus said:
All went pretty well. Had a couple of hangs, but got them all sorted.
Currently restoring, but having an issue where the phone switches from "USB Media mode" to "Dock Mode" and back and forth.
Weird issue I've never seen before....
Click to expand...
Click to collapse
About your USB media / Dock issue, I've never read such problem. Moreover, I don't use dock at all. I will not be very helpful about this. Sorry.

FLooDW said:
About your USB media / Dock issue, I've never read such problem. Moreover, I don't use dock at all. I will not be very helpful about this. Sorry.
Click to expand...
Click to collapse
Yeah I don't use dock either. It seems it gets confused about what its actually plugged into..
Anyway, I'll figure it out. Thanks heaps for your help Mate. Very much appreciated.