Related
HI people. First of XDA Forum and Dev as you guy's are doing a great job.
Secondly i have this Motorola Milestone GSM version. I am stuck on Android 2.1, as every one how fast Motorola release Android updates for their smartphones. I have gone through lot of Rooting guides but i haven't tried one yet.
As there are lot of Rooting guides and ROM for Motorola milestone on XDA as well, i am kind confuse how to do rooting and how to use a ultimate ROM on Milestone.
If you guy's can look at my Moto version as given below and can suggest me some step by step guide and Some Good ROMS as well i will be very thankful to you guys'
I know there are lot of other users who have asked same question but i want it kind simple and crisp.
Model Number
Milestone
Firmware Version
2.1-update1
Firmware Configuration Versio n
GAS_EMEA_USASHLS00RTINT_P016
Baseband Version
3GSMEPU91A_U_91.07.56I
Kernel Version
2.6.29-omap1
Build Number
SHOLS_U2_02.36.0
Click to expand...
Click to collapse
Most one-click-rooters work fine with the Milestone and it doesn't get any easier then running an app .
That's how I did my at least.
I have used universal root, but that doesn't allow APP2SD and using custom ROMS. So i want complete rooting so that i can load custom roms.
gaggid said:
I have used universal root, but that doesn't allow APP2SD and using custom ROMS. So i want complete rooting so that i can load custom roms.
Click to expand...
Click to collapse
Yes it does...
The problem is that:
-for APP2SD you must have ext2 partition which you probably didnt create and for Custom ROMS you have to load the vulnerable recovery...which you probably didnt do...as well
Just my supposing...Corect me if I'm wrong!
First, ( I think) you have to flash vulnerable recovery, then root. There is also a beta 2.2.1 beta sbf available. after achieving root, you can google GOT TEAM ANDROID and click the first link which should lead to their blog - http://www.google.ca/url?sa=t&sourc...BQ82GR7pNmLJSfPpg&sig2=Jd4iM6Nov5eYhJa2yrZLGg and there should be further instructions there. Good luck ( remember I think these are true, not 100% sure)
mohitrocks said:
First, ( I think) you have to flash vulnerable recovery, then root. There is also a beta 2.2.1 beta sbf available. after achieving root, you can google GOT TEAM ANDROID and click the first link which should lead to their blog - and there should be further instructions there. Good luck ( remember I think these are true, not 100% sure)
Click to expand...
Click to collapse
Can you guide me through on how to do
Flash Vulnerable Reovery.
How to root Milestone
What is SBF and how to use it.
What GOT TEAM ANDROID and why i need them?
If your milestone is anything like mine (I use the milestone available from telus, in canada), then your service provider may have added an un-root and return-to-factory-bootloader check on every boot.
in which case, you would need to install the OpenRecovery backup tool onto your sd card (it's an update.zip file + OpenRecovery directory), then flash a vulnerable bootloader using spf. reboot the phone (as is necessary when doing this flash), and as the system is coming up, start up into recovery (by pressing+holding the camera button, waiting for the yellow triangle w/"!", then pressing vol+ and the camera button), then execute update.zip
drop to terminal, and depending on your model, the .sh file that's un-rooting your phone may be in a different location, and simply rename the file, delete it, or make it non-executable.
Good luck!
Mystik said:
If your milestone is anything like mine (I use the milestone available from telus, in canada), then your service provider may have added an un-root and return-to-factory-bootloader check on every boot.
drop to terminal, and depending on your model, the .sh file that's un-rooting your phone may be in a different location, and simply rename the file, delete it, or make it non-executable.
!
Click to expand...
Click to collapse
I just bought the telus milestone a few days ago and am looking to bypass the update.zip when I go into recovery by permanently replacing the stock recovery with a custom recovery, would disabling this .sh file aid me in this respect?
Where could I find it?
I think i found complete guide for doing this.
Hope it will work.
Which ROM is best for Milestone ?
I am not talking about jazzy ROMs, i want a ROM with all cool features + stable functionality
i always have a hard time rooting Milestones :/
Still not able to get any strong good references on Hacking Milestone.
i was thinking since the razr ics update will have a signed kernel and it will be able to pass through the bootloader if we could use the razr ics update(since its like our roms all cross platform due to same processor,resolutions) and mod it a little so there is no 4G or webtop and change the device name to D3/solana then flash it as an update instead of a zip in recovery/fastboot like as if it was an OTA update that we sideload. we may have to return to stock to do this, or use otaroot keeper? i dont know if it will need to be re signed after changing things. but since this is an official kernel and the zip has a path motorola made it may get passed our bootloader if the unlock process is the same for all phones.
also maybe someone with a RAZR can use adb and see the commands during the update process to see if the phone spits out any lines of code when it opens the bootloader to replace the kernel?
I'm guessing it won't work as the kernel is signed only for that device and not the d3. Not to mention hw differences.
Sent from my XT862 using xda premium
the cameras are the same, they both have the same processors just razr is .2 ghz faster and running a little version different, the way they use the camcorder is the same, and the way they run flash player/hardware accelleration is the same. if we can trick the GB kernel to run the roms we have now then tricking the phone to use the razr kernel could be easy given we can get it passed the bootloader securely. once its passed the BL hashcode can get codecs to take a little easier since we will have the ability to run the DEV- ION drivers instead of getting ducati to decode and re code them for the GB kernel.
this may be worth a try instead of everyone saying "oh that wont work," then waiting god knows how long until hash gets the codecs to work, or motorola might just update up in 3-6 months. it might be a sloppy thing but it may work
double post
I doubt it'll work. The keys used to sign the Droid 3's kernel and the Razr's kernel are different. It would be just as hard (and really, afaik, impossible) to get our devices to run the Razr's kernel than it would be for us to get it to run any other kernel we can make/compile.
Sent from my XT862 using XDA
Keep brow beating Motorola, they "promised" unlock, blah, blah, blah
If we don't push though you'll never get anything.
im hoping hashcode gets the codecs working by may/june, if not then ill just go pick up a used D4/razr since they should be 100% on it by then or maybe a gnex off CL for 300 i really want to keep the d3 though.
It may work if we package the kernel into the ICS rom by hash or flash it separately. But who knows how much work it may take for that to happen. Also some DROID 3s may not be able to run that .2ghz faster so we have to tone that back. It maybe be simpler to port over razr ICS codecs
Sent from my DROID3 using XDA
saintlikesniper said:
It may work if we package the kernel into the ICS rom by hash or flash it separately. But who knows how much work it may take for that to happen. Also some DROID 3s may not be able to run that .2ghz faster so we have to tone that back. It maybe be simpler to port over razr ICS codecs
Sent from my DROID3 using XDA
Click to expand...
Click to collapse
This what will likely happen
Sent from my XT862 using xda premium
I could be mistaken here, but it is my understanding that the kernel acts as a sort of intermediate between the phone's hardware and OS. Seeing as how the RAZR lacks a physical keyboard, there could likely be some very pertinent information missing in it's kernel that is needed in order for the D3 keyboard to be usable. If this is the case, we would probably be better off attempting to utilize an ICS leak for the D4.
Sent from my DROID3 using Tapatalk
Full disclosure: I'm not a dev. My eyes glaze over the second someone mentions compiling or code.
That being said, I feel that at this point, maybe these types of off-the-wall ideas might be valuable. Even if the OP wasn't 100% on the right track, maybe that will light a fire in a more capable person's head.
mikedyk43 said:
I could be mistaken here, but it is my understanding that the kernel acts as a sort of intermediate between the phone's hardware and OS. Seeing as how the RAZR lacks a physical keyboard, there could likely be some very pertinent information missing in it's kernel that is needed in order for the D3 keyboard to be usable. If this is the case, we would probably be better off attempting to utilize an ICS leak for the D4.
Sent from my DROID3 using Tapatalk
Click to expand...
Click to collapse
see thats the thing, our ICS roms werent programmed to utilize a hard keyboard either (sourced on the Gnex) so we can have that fixed. what im getting at is the razr, bionic, D4 and D3 run the same OMAP 4430 processor with the same efuse so it should be the same key for the bootloader. when we package the signed bootloader with either a modded RAZR rom to remove 4G and webtop and/or rename the phone id then resign it OR package the signed kernel in our ics roms then *flash as a manual update* it may get passed the bootloader. since the EFUSE looks for official firmware, the razr ics rom is signed by moto and the kernel has the efuse keys attatched (for OMAP 4430) so it may let it in. we would need root access in the rom to do changes (freeze/delete webtop) etc. we also need to wait for a reliable flashable zip of the razr rom since the only way to get it is a fatal way(cheesecake). BUT this is the deal, if we do this this will totally take you off the upgrade path if there is even one anymore, so an SBF back to 2.3.4 will need to happen in case of anything.
Tyfighter said:
Full disclosure: I'm not a dev. My eyes glaze over the second someone mentions compiling or code.
That being said, I feel that at this point, maybe these types of off-the-wall ideas might be valuable. Even if the OP wasn't 100% on the right track, maybe that will light a fire in a more capable person's head.
Click to expand...
Click to collapse
hashcode is more than capable of doing this its just a matter of if hes brave enough to try since hes tried everything else and we havent heard anything about codecs in awhile.
A few things
1). Signed. This means you can't edit it, change it, modify it or do anything with it...and it has to be signed for your device. Razr kernel will not be usable, nor will a Droid 4 when it comes out later.
2). Our D3 ICS CM9 rom is not built off the GNex ROM, it's built from source (AOSP) modified by CyanogenMod team and then further modified by Hashcode. Hashcode is modifying it to work with the D3 Gingerbread Kernel and that is why the hardware keyboard works.
3). Unless Motorola releases an ICS kernel/Rom for the D3.....OR Motorola releases an unlocker for the bootloader......the best will see is a modified source built ROM running on the stock Gingerbread kernel.
I'm not going to list someone hacking/cracking the D3 bootloader signing key, etc.... While it's entirely possible.......the Droid 2, Droid X have still not been cracked....and they've been out how long now?
We can run something like Hashcode's CM9 ICS and enjoy it and hope that Hashcode can get as much out of it as possible.......running on top of the Gingerbread kernel.....other than that it's just going to be hoping/waiting for Motorola to do something.
T
saintlikesniper said:
It may work if we package the kernel into the ICS rom by hash or flash it separately. But who knows how much work it may take for that to happen. Also some DROID 3s may not be able to run that .2ghz faster so we have to tone that back. It maybe be simpler to port over razr ICS codecs
Sent from my DROID3 using XDA
Click to expand...
Click to collapse
The problem we run into (i messed with this idea a bit) is that /boot wont allow unsigned code, the file containing the kernel needs to be flashed to /boot and is signed by motorola so it cant be tampered with and is also signed with a product code allowing it to only be flashed on that model. We cant changed the model # in the file without altering the signature so the phone wont accept the flash anyways. As for flashing it along with hashcodes rom, i think thats what theyre trying to do with kexec (this seems to be the most likely way we have to get custom kernels running on any bootloader locked phones). The problem with kexec (it's an app that loads you into an alternate kernel after the first kernel has booted, it's like a handover) is that our kernels have to have kexec support compiled into them right now by motorola for it to work(not sure theyve done this). Really, without a bootloader unlock or kernel upgrade by motorola (meaning ics and a 3.0+ kernel signed for our phones) i think we're stuck with what we're doing atm.
Perhaps we could do something like move the /boot partition to somewhere else but i imagine it's been tried and moving /boot to a partition on internal storage or something probably just causes the phone to not boot at all.
Willis111 said:
T
The problem we run into (i messed with this idea a bit) is that /boot wont allow unsigned code, the file containing the kernel needs to be flashed to /boot and is signed by motorola so it cant be tampered with and is also signed with a product code allowing it to only be flashed on that model. We cant changed the model # in the file without altering the signature so the phone wont accept the flash anyways. As for flashing it along with hashcodes rom, i think thats what theyre trying to do with kexec (this seems to be the most likely way we have to get custom kernels running on any bootloader locked phones). The problem with kexec (it's an app that loads you into an alternate kernel after the first kernel has booted, it's like a handover) is that our kernels have to have kexec support compiled into them right now by motorola for it to work(not sure theyve done this). Really, without a bootloader unlock or kernel upgrade by motorola (meaning ics and a 3.0+ kernel signed for our phones) i think we're stuck with what we're doing atm.
Perhaps we could do something like move the /boot partition to somewhere else but i imagine it's been tried and moving /boot to a partition on internal storage or something probably just causes the phone to not boot at all.
Click to expand...
Click to collapse
i dont understand why we cant completely wipe the phone of the data/rom AND bootloader and create a custom bootloader.
I think that would be eFuse and harder than it sounds entirely. Again may be easier to port razr codecs when it becomes available. Which should be soon according to speculation
Sent from my DROID3 using XDA
Willis111 said:
T
The problem we run into (i messed with this idea a bit) is that /boot wont allow unsigned code, the file containing the kernel needs to be flashed to /boot and is signed by motorola so it cant be tampered with and is also signed with a product code allowing it to only be flashed on that model. We cant changed the model # in the file without altering the signature so the phone wont accept the flash anyways. As for flashing it along with hashcodes rom, i think thats what theyre trying to do with kexec (this seems to be the most likely way we have to get custom kernels running on any bootloader locked phones). The problem with kexec (it's an app that loads you into an alternate kernel after the first kernel has booted, it's like a handover) is that our kernels have to have kexec support compiled into them right now by motorola for it to work(not sure theyve done this). Really, without a bootloader unlock or kernel upgrade by motorola (meaning ics and a 3.0+ kernel signed for our phones) i think we're stuck with what we're doing atm.
Perhaps we could do something like move the /boot partition to somewhere else but i imagine it's been tried and moving /boot to a partition on internal storage or something probably just causes the phone to not boot at all.
Click to expand...
Click to collapse
We actually don't need Motorola to have compiled kexec in (fully, at least. I think there has to be some basic support there, which there might be). As long as we can load kernel modules (which I believe we can) we could create our own and run that. The problem with kexec, though, is that it drops kernel communications with the radio for long enough for the radio to think the phone has shut down or errored or something, and it will shut itself off. So, upon loading into the new kernel, the phone will have no radio, and the only way to reinitialize it is to go through the bootloader process again, which would mean we couldn't have an unsigned kernel. It would be nice if there was a way to communicate to the radio that the kernel wasn't actually shutting off yet or if there was a way to reboot the radio after switching kernels, but sadly there isn't (as far as I know).
I say we all put our computing power together to crack Motorola's private key that they signed the kernel with, [email protected] style.
</semi-sarcasm>
Edit: Okay, actually being productive here... is the radio image signed? Because we could use kexec to load a new kernel, but modify the radio code so that it doesn't assume something horrible has happened when the kernel stops communicating with it.
ssinisterss said:
i dont understand why we cant completely wipe the phone of the data/rom AND bootloader and create a custom bootloader.
Click to expand...
Click to collapse
Because even a fully wiped phone will only accept files that are signed by motorola.
I believe the only way we can see a custom kernel is using the method some guy (i forgot who) has been able to kinda do. He's on the Razrs forums and he was able to get a custom kernel running on his phone. Unfortuantly this kernel can only use 1 out of the 2 cores, so it is not done yet. From what I remember he gets the phone to boot with the stock kernel and then has his kernel installed over it. I think the boot up process takes a little bit longer but it is a small price to pay for customization.
Flashing the Razrs ICS is futile. The only thing we can do is maybe kang some prop settings and apks. That's about it. We'd have a better chance with the Bionic, but it's still unlikley it will help anything.
So I've always owned samsung phones...fell in love with amoled and never looked back...and i gotta tell you, my short spurt with the one xl with having to flash kernels and rom separably and unlocking bootloaders and what not man! i really miss the simplicity of being able to root with odin and never having to look back...everything just worked as it should (the biggest inconvenience we had was having to flash an older kernel on the sg2 before flashing anything above gb) but here I am, ready and willing to embrace the atrix's sexy design but limited development...but I need some clarification that simple searches and reading through threads dont seem to explain quite as thoroughly as other devices portals.
1.) I understand the concept of a bootloader and how it needs to be unlocked in order to flash ROM's and kernels and write to specific partitions of the phone, I just want to ensure that this device has an unlockable bootloader with the latest firmware that it ships with
2.) even more important than bootloader unlocking is root...i see references to SBF's and qslite or something...is this similar to odin for samsung? do i use an SBF (perhaps the equivalent of an RUU for htc or .tar for samsung??) to flash firmwares onto the device, and will a modded version provide SU?
3.) no roms! thats unacceptable. if i can obtain root and recovery, trust me when i say that even while i cant build from source, ill put SOMETHING together, even if its only rooted/themed stock. but what are the odds of rom from other devices being ported?
4.) cheesecake. wtf.
which one of these threads should i use for the latest firmware on the atrix to root?
http://forum.xda-developers.com/showthread.php?t=1785401
http://forum.xda-developers.com/showthread.php?t=1940594
which one of these threads should i use for the latest firmware on the atrix to unlock bootloader?
http://forum.xda-developers.com/showthread.php?t=1896526
http://forum.xda-developers.com/showthread.php?t=1985031
does hash's safetrap work for backups on the ahd? i read that flashing is disabled currently, but id still like to backup
gosh so many questions! hope the trolls dont come out on sundays...........................
hapticxchaos said:
So I've always owned samsung phones...fell in love with amoled and never looked back...and i gotta tell you, my short spurt with the one xl with having to flash kernels and rom separably and unlocking bootloaders and what not man! i really miss the simplicity of being able to root with odin and never having to look back...everything just worked as it should (the biggest inconvenience we had was having to flash an older kernel on the sg2 before flashing anything above gb) but here I am, ready and willing to embrace the atrix's sexy design but limited development...but I need some clarification that simple searches and reading through threads dont seem to explain quite as thoroughly as other devices portals.
1.) I understand the concept of a bootloader and how it needs to be unlocked in order to flash ROM's and kernels and write to specific partitions of the phone, I just want to ensure that this device has an unlockable bootloader with the latest firmware that it ships with
2.) even more important than bootloader unlocking is root...i see references to SBF's and qslite or something...is this similar to odin for samsung? do i use an SBF (perhaps the equivalent of an RUU for htc or .tar for samsung??) to flash firmwares onto the device, and will a modded version provide SU?
3.) no roms! thats unacceptable. if i can obtain root and recovery, trust me when i say that even while i cant build from source, ill put SOMETHING together, even if its only rooted/themed stock. but what are the odds of rom from other devices being ported?
4.) cheesecake. wtf.
which one of these threads should i use for the latest firmware on the atrix to root?
http://forum.xda-developers.com/showthread.php?t=1785401
http://forum.xda-developers.com/showthread.php?t=1940594
which one of these threads should i use for the latest firmware on the atrix to unlock bootloader?
http://forum.xda-developers.com/showthread.php?t=1896526
http://forum.xda-developers.com/showthread.php?t=1985031
does hash's safetrap work for backups on the ahd? i read that flashing is disabled currently, but id still like to backup
gosh so many questions! hope the trolls dont come out on sundays...........................
Click to expand...
Click to collapse
Okay, your bootloader (if it is from att) is not getting unlocked. That is the best way to put it because AT&T ruins everything. Firmware flashing, there is a utility out now. It's the best way to get back to stock. Razr HD roms should be portable, we wont know for sure until we have something to test. Cheesecake is worthless now so don't even worry about it. Moto blocked us from accessing their servers. It really seems like you aren't going to like this to be completely honest. You are probably more of a nexus 4 or gs3 guy....
SirHoover2010 said:
Okay, your bootloader (if it is from att) is not getting unlocked. That is the best way to put it because AT&T ruins everything. Firmware flashing, there is a utility out now. It's the best way to get back to stock. Razr HD roms should be portable, we wont know for sure until we have something to test. Cheesecake is worthless now so don't even worry about it. Moto blocked us from accessing their servers. It really seems like you aren't going to like this to be completely honest. You are probably more of a nexus 4 or gs3 guy....
Click to expand...
Click to collapse
sincerely, ill get by with just root so to sum it all up, no bl unlock or proper recovery, but purely just root (which is fine by me ) which i can obtain by using THIS? seems your the one who made that tool kit so your clearly the man to ask i can use your utility to obtain root, and even retain root after the upgrade to the test build of jb?
your so awesome sirhoover
hapticxchaos said:
sincerely, ill get by with just root so to sum it all up, no bl unlock or proper recovery, but purely just root (which is fine by me ) which i can obtain by using THIS? seems your the one who made that tool kit so your clearly the man to ask i can use your utility to obtain root, and even retain root after the upgrade to the test build of jb?
your so awesome sirhoover
Click to expand...
Click to collapse
Yes you can use that utility to obtain root
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.
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!