Related
I just got my Nexus 10 and haven't even turned it on yet. Giving it a nice charge.
So what's the first steps?
With my Galaxy Nexus, the very first thing I did was unlock the bootloader because anyway it wipes the device. Then I rooted it. And then I went along my jolly way. Eventually, months down the line, I installed Bugless Beast.
So what about this tablet? Turn on and unlock bootloader then root? Or do I want to get an OTA first in case it's on 4.2 and needs 4.2.1?
Anything else someone new to the Nexus 10 should know about?
By the way, I choose stability over experimental features. Hence, Bugless Beast on my GNex instead of some of the more feature-filled (but less stable) ROMs.
Thanks for you help!
turn it on --> get your update(s) to 4.2.1 --> unlock bootloader --> root --> install adaway and just leave it. the stock rom is great but i can't live without an adblocker. otherwise just give the developers time, as i said before, the stock rom is great
renna1992 said:
turn it on --> get your update(s) to 4.2.1 --> unlock bootloader --> root --> install adaway and just leave it. the stock rom is great but i can't live without an adblocker. otherwise just give the developers time, as i said before, the stock rom is great
Click to expand...
Click to collapse
Exactly what I did
I prefer ROM Toolbox Pro for add blocking many other features that a rooted user will appreciate. I have the pro ver.
ROM Toolbox Lite (free version)
https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolbox
Sent from my Nexus 10 using Tapatalk HD
Thanks guys. I'll do exactly that.
I hope we reach the point where ROMs are more stable and less experimental for the Nexus 10.
@jjdevega, Since I like to compartmentalize my tools (I already have a favorite ad blocker, file explorer, titanium backup, etc), ROM toolbox is less useful for me. Thanks for the suggestion though.
I'd recommend just keeping the bootloader unlocked
I like my device to either be completely stock, or custom. Leaving the bootloader unlocked on a stock, non-rooted ROM bothered me quite a bit lol (not sure why; I mean I know leaving the bootloader unlocked doesn't really do anything, but still...), and I would go between custom ROM's and stock a lot, locking and unlocking the bootloader each time too.
Yea, I was planning on leaving it unlocked. Unless I need to return the tablet for warranty purposes, there's no reason to re-lock the bootloader.
Well, actually there are security implications regarding unlocked bootloaders. That's actually why unlocking wipes your device, so that an outsider can't bypass security by unlocking the bootloader and then getting whatever information he/she wants.
Now that the OTA has locked everyone up or those of us that got a device that didn't have the chance to unlock the bootloader, do most/some/all/etc roms that we have for the Razr M work with Safestrap?
Sorry if this is posted elsewhere but I didn't see it and only saw mention of roms having to be compatible with it
collins521 said:
Now that the OTA has locked everyone up or those of us that got a device that didn't have the chance to unlock the bootloader, do most/some/all/etc roms that we have for the Razr M work with Safestrap?
Sorry if this is posted elsewhere but I didn't see it and only saw mention of roms having to be compatible with it
Click to expand...
Click to collapse
I don't know the exact roms, but I know there are a few. Since the bootloader was unlocked though, the development for safestrap roms has slowed or stopped. Check in the Android Development section and scroll through for the safestrap roms. I believe they were 4.1.2 roms only, but don't quote me on that.
Sent from my Droid Razr M using xda app-developers app
Jersey846 said:
I don't know the exact roms, but I know there are a few. Since the bootloader was unlocked though, the development for safestrap roms has slowed or stopped. Check in the Android Development section and scroll through for the safestrap roms. I believe they were 4.1.2 roms only, but don't quote me on that.
Sent from my Droid Razr M using xda app-developers app
Click to expand...
Click to collapse
ROMs developed for SS stopped at 4.1.1, meaning that there not any 4.1.2 custom ROMs available. bootloader was unlocked prior to 4.1.2 rolling out.
there might be a way to convert them to SS though - I know that a dev was able to convert a SS ROM to TWRP flashable recovery, so perhaps he might be able to do the reverse.
jco23 said:
ROMs developed for SS stopped at 4.1.1, meaning that there not any 4.1.2 custom ROMs available. bootloader was unlocked prior to 4.1.2 rolling out.
there might be a way to convert them to SS though - I know that a dev was able to convert a SS ROM to TWRP flashable recovery, so perhaps he might be able to do the reverse.
Click to expand...
Click to collapse
I believe DeadCalm was updated to 4.1.2. Also, Eclipse v1.2 is still SS compatible but it leans more heavily on AOSP styling.
SS compatible ROMs:
-Early builds of CM10 (way early, like at the beginning of thread early)
-DeadCalm was SS enabled, not sure if it was modified for an unlocked bootloader only
-Energy is SS enabled and never altered for unlocked bootloader
-Flying Jelly was SS enabled and I don't think it was modified to work only on an unlock bootloader
-Eclipse v1.2 was SS enabled, I don't think it was modified for unlocked bootloader
RikRong said:
I believe DeadCalm was updated to 4.1.2. Also, Eclipse v1.2 is still SS compatible but it leans more heavily on AOSP styling.
SS compatible ROMs:
-Early builds of CM10 (way early, like at the beginning of thread early)
-DeadCalm was SS enabled, not sure if it was modified for an unlocked bootloader only
-Energy is SS enabled and never altered for unlocked bootloader
-Flying Jelly was SS enabled and I don't think it was modified to work only on an unlock bootloader
-Eclipse v1.2 was SS enabled, I don't think it was modified for unlocked bootloader
Click to expand...
Click to collapse
yeah, but those are all 4.1.1 ROMs - and I'm fairly certain deadcalm is unlocked bootloader only, as it was created for just 4.1.2.
but I really don't think it matters much anymore - Motorola has been quite diligent on providing updates, so I would not be surprised to see an official 4.2.2 release by the end of this year, with a 4.3 release by next summer.
jco23 said:
yeah, but those are all 4.1.1 ROMs - and I'm fairly certain deadcalm is unlocked bootloader only, as it was created for just 4.1.2.
but I really don't think it matters much anymore - Motorola has been quite diligent on providing updates, so I would not be surprised to see an official 4.2.2 release by the end of this year, with a 4.3 release by next summer.
Click to expand...
Click to collapse
Yeah, you're right on all those being 4.1.1, but I was just throwing out some options. Personally, I think very few of the devs, if any, will develop for SS. Sure, the people that are getting new phones or maintenance replacements are hosed. However, people that owned the phone and decided to install the update and not unlock their bootloader? Well, it's their own fault. They've been warned for 4 months that the patch could be locked. Look what happened, it was locked. The one thing the devs could do, that would be fairly easy, is just update the older SS ROMs to the newer OTA. That would help out a lot of people.
RikRong said:
Yeah, you're right on all those being 4.1.1, but I was just throwing out some options. Personally, I think very few of the devs, if any, will develop for SS. Sure, the people that are getting new phones or maintenance replacements are hosed. However, people that owned the phone and decided to install the update and not unlock their bootloader? Well, it's their own fault. They've been warned for 4 months that the patch could be locked. Look what happened, it was locked. The one thing the devs could do, that would be fairly easy, is just update the older SS ROMs to the newer OTA. That would help out a lot of people.
Click to expand...
Click to collapse
100% agreed on the warnings - but I also understand why folks may have been skittish beforehand (took me 3 months of reading before I rooted my first device). given that this phone is now offered for free, I can see many new folks to this community, but they'll be SOL unless we are blessed with the help from a dev to unlock their bootloader.
that being said, the devs are not required to create a hack or make their ROMs SS-compatible, but I would not be surprised if locked bootloader phones soon begin to outnumber the locked one. i'm just thankful that they are here.
To be fair, the droid razr m that I'm working on has its bootloader locked because my girlfriend is skittish about me touching her phone. Women
I could barely even get any to work when they were still developing SS Roms, so goodluck... Never accept OTA's...
AK47sForAll said:
I could barely even get any to work when they were still developing SS Roms, so goodluck... Never accept OTA's...
Click to expand...
Click to collapse
Unfortunately the one I have had the OTA already downloaded so I didn't even get a chance to unlock the bootloader...been trying to find a white one at a reasonable price and haven't' had much luck
collins521 said:
Unfortunately the one I have had the OTA already downloaded so I didn't even get a chance to unlock the bootloader...been trying to find a white one at a reasonable price and haven't' had much luck
Click to expand...
Click to collapse
What do you consider reasonable? And have you tried eBay?
AK47sForAll said:
What do you consider reasonable? And have you tried eBay?
Click to expand...
Click to collapse
Ya I've been watching eBay and other sites for a good deal on a white one. Under $200 and in great shape is where I'm looking to get one. I'm in no real rush so I can wait for a deal to pop up
http://www.droidrzr.com/index.php/t...calm-v14-7172013-412-base/page-30#entry333531
That being said.
An activated DC is a path to this & you take your data with you.
http://forum.xda-developers.com/showthread.php?t=2246081
Edit Yet this is a backup made by the full twrp. Yet again they are supposed to be compatible....
This post is to try to sort out the questions, concerns and troubles that users come up against when using.the "SlapMyMoto" rooting method to gain "Root" on the Moto X.
[Question]What happened to my "Recovery"--
[ANSWER]- It's gone. There's no "Recovery". Now you have read/write access to /system instead of a recovery. Your system will boot normally, except /system will be read-write accessible.
[Question ] - Can I flash Xxx-xxx.zip through recovery like it says here - xxxxxx.com/yada/yada/instructions (with link to. Zip file) .com
[Answer] No.
[Question ] Why not?
[Answer] Because you have a "Custom" Recovery that does nothing more than provide read-write access. to the /system partition , ..period.
[Question] -- Can I use some other"Recovery"?
[Answer ] -- ? DUNNO? Maybe jcase will chime in and clarify that. As it stands, maybe the 4.4 recovery, don't know for sure what it will do to your root. Whether it is the 4.4, or 4.2 recovery, without unlocking your Boot loader it will have to be a signed. zip file for system security.
Where else can I turn for answers?
Hopefully, here: http://forum.xda-developers.com/showthread.php?t=2538896
SlapMyMoto 0.5c Beta (4.4 root, RW to system)
As it stands, jcase is attending to family/personal matters. I'm sure he will be back sometime. Until then, just have to wait it out.
Sent from my XT1055 using Xparent Cyan Tapatalk 2
Question- Why with a locked bootloader do I need recovery?
Answer- You don't!
Comment- Good, because you don't have one now that you used SlapMyMoto to root. Your recovery has been replaced by write protection off.
lowvolt1 said:
Question- Why with a locked bootloader do I need recovery?
Answer- You don't!
Comment- Good, because you don't have one now that you used SlapMyMoto to root. Your recovery has been replaced by write protection off.
Click to expand...
Click to collapse
Unless you want to clear cache, flash a signed update.zip you really don't need it. Until you do.
Sent from my XT1055 using Xparent Cyan Tapatalk 2
dtrud0h said:
Unless you want to clear cache, flash a signed update.zip you really don't need it. Until you do.
Sent from my XT1055 using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
Or I could just use adb
via my slapped KIT KAT moto X rockin on Verizon
Yup, you sure could. What I'm trying to get across to the masses is, its not all about you lowvolt1, there are many new, or people that don't known their way around all this that read the "How-to" from xyz.com and expect it to work.
If you can read, apply your good judgement, and move on then great.
There are other people that can't yet wrap their heads around the bootloader/recovery thing that just got a phone, have no clue, and want help or answers. This is the thread for them.
Maybe you should start a thread for stuff that's all about you if that's what you want.
Sent from my XT1055 using Xparent Cyan Tapatalk 2
dtrud0h said:
Yup, you sure could. What I'm trying to get across to the masses is, its not all about you lowvolt1, there are many new, or people that don't known their way around all this that read the "How-to" from xyz.com and expect it to work.
If you can read, apply your good judgement, and move on then great.
There are other people that can't yet wrap their heads around the bootloader/recovery thing that just got a phone, have no clue, and want help or answers. This is the thread for them.
Maybe you should start a thread for stuff that's all about you if that's what you want.
Sent from my XT1055 using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
My narcissistic nature is not in question here. What is in question is why you are trying to help new people or people with questions, yet you continue to blurt out false truths.
Maybe you should listen to the people that have alot more knowledge than you and I put together and do a little more research before you continue to confuse people.
via my slapped KIT KAT moto X rockin on Verizon
lowvolt1 said:
My narcissistic nature is not in question here. What is in question is why you are trying to help new people or people with questions, yet you continue to blurt out false truths.
Maybe you should listen to the people that have alot more knowledge than you and I put together and do a little more research before you continue to confuse people.
via my slapped KIT KAT moto X rockin on Verizon
Click to expand...
Click to collapse
OK I for one found your (original) explanation quite helpful as I didn't pick up on the recovery/bootloader thing. I'm still not rooted...
The recovery I can live without - I think you've explained it well.
What happens to the bootloader? it looks like (in step "5") it is downgraded to the 4.2.2 bootloader? So we're running 4.4 with a 4.2.2. bootloader when all said and done?
tdiman said:
OK I for one found your (original) explanation quite helpful as I didn't pick up on the recovery/bootloader thing. I'm still not rooted...
The recovery I can live without - I think you've explained it well.
What happens to the bootloader? it looks like (in step "5") it is downgraded to the 4.2.2 bootloader? So we're running 4.4 with a 4.2.2. bootloader when all said and done?
Click to expand...
Click to collapse
Yes. As I understand it your statement is correct.
via my slapped KIT KAT moto X rockin on Verizon
Guys-
I don't feel like going through all 80+ pages on the slapmymoto thread, so I will ask it here.
I have the at&t version with 4.4 on it. Can I root at the moment with the 0.5 slapmymoto, if not, is 1.0 going to be solving this issue?
Thanks in advance-
Dodolom said:
Guys-
I don't feel like going through all 80+ pages on the slapmymoto thread, so I will ask it here.
I have the at&t version with 4.4 on it. Can I root at the moment with the 0.5 slapmymoto, if not, is 1.0 going to be solving this issue?
Thanks in advance-
Click to expand...
Click to collapse
I am assuming your on the non Dev edition. I am not familiar with at&t, so I will ask this. Can you unlock the boot loader on that version? If not then yes I believe you can root using slap. But you have to downgrade to 4.2.2 first.
via my slapped KIT KAT moto X rockin on Verizon
lowvolt1 said:
I am assuming your on the non Dev edition. I am not familiar with at&t, so I will ask this. Can you unlock the boot loader on that version? If not then yes I believe you can root using slap. But you have to downgrade to 4.2.2 first.
via my slapped KIT KAT moto X rockin on Verizon
Click to expand...
Click to collapse
Yeah, this is jus the retail at&t version on the Cyber Monday sale. I had the GSM DE from day 1 but sent it to a friend in england to play with and then Cyber Monday deal popped up, so I ordered one but this time I went with the custom design which only comes with the carriers.
Anyways, how can I know if I can unlock the bootloader or not?
Dodolom said:
Yeah, this is jus the retail at&t version on the Cyber Monday sale. I had the GSM DE from day 1 but sent it to a friend in england to play with and then Cyber Monday deal popped up, so I ordered one but this time I went with the custom design which only comes with the carriers.
Anyways, how can I know if I can unlock the bootloader or not?
Click to expand...
Click to collapse
Try Google searching it. I don't think you can. Verizon can't and since you made mention of a Dev edition I am guessing you can't unlock.
via my slapped KIT KAT moto X rockin on Verizon
lowvolt1 said:
Try Google searching it. I don't think you can. Verizon can't and since you made mention of a Dev edition I am guessing you can't unlock.
via my slapped KIT KAT moto X rockin on Verizon
Click to expand...
Click to collapse
I think I will wait for the 1.0 and see what happens or if I get some time this week, I will give it a shot with the downgrading and all that.
Thanks
Dodolom said:
I think I will wait for the 1.0 and see what happens or if I get some time this week, I will give it a shot with the downgrading and all that.
Thanks
Click to expand...
Click to collapse
You may be waiting awhile for 1.0. If it comes at all.
via my slapped KIT KAT moto X rockin on Verizon
I just recieved a Moto X on Verizon in the mail and I really would like to root it to debloat and run a custom rom but I have always had Samsung and worked with odin. How do we go about rooting this? What do you think is the easiest way? For some reason ADB isnt working on my computer. Thanks in advance! I REALLY NEED SOME HELP!!
ehusidic said:
I just recieved a Moto X on Verizon in the mail and I really would like to root it to debloat and run a custom rom but I have always had Samsung and worked with odin. How do we go about rooting this? What do you think is the easiest way? For some reason ADB isnt working on my computer. Thanks in advance! I REALLY NEED SOME HELP!!
Click to expand...
Click to collapse
1. There are no custom roms at the moment. Unless you have the Verizon Dev edition.
2. You will only gain root access and RW permissions
3. The easiest way is slap my motto is the only way if you want to be rooted on kit Kat 4.4
4. You will definitely need adb
Sent from my GT-P3110 using Tapatalk 4
[Q] Say if you boot into "recovery," otherwise write protection-off mode, then you reboot. Do you boot back into normal mode? Or does it default into write protection-off mode until you explicitly tell it to boot normally?
erikikaz said:
[Q] Say if you boot into "recovery," otherwise write protection-off mode, then you reboot. Do you boot back into normal mode? Or does it default into write protection-off mode until you explicitly tell it to boot normally?
Click to expand...
Click to collapse
That depends, are you rebooting in to recovery again, or rebooting in to Android? Android = WP on. Recovery = WP off.
A couple of non-SlapMyMoto questions have been asked here so... (dtrud0h, feel free to add these to your OP)
[Q] What is the best way to root my Moto X?
[A] Depends what Rom is on your X. Generally there are 3 "stock" motorola rom versions for the X. The ROM it shipped with (android 4.2.2), the "camera fix" update (4.2.2), and Kit Kit (4.4). And it depends on if you have a locked bootloader or not.
Locked Bootloader with KitKat (4.4) see SlapMyMoto -> SlapMyMoto 0.5c Beta (4.4 root, RW to system)
Locked Bootloader with "Camera Update" see -> [Root] RockMyMoto (Yes, even the first OTA)
Locked Bootloader with initial shipping rom see -> [Root/Write Protection Bypass] MotoX (no unlock needed)
UNLOCKED bootloader see -> https://plus.google.com/110773150384694258853/posts/VhtJtg92sTP
NOTE: these should work across all carrier variants of the Moto X. that means ATT, VZW, TMO, TIM, Rogers, etc.. should be able to use these. You just need to pick the right process based on your ROM or locked vs unlocked bootloader.
[Q] Once I root, can I accept an OTA update on my phone?
[A] If you have rooted with SlapMyMoto, RockMyMoto, PwnMyMoto, or have otherwise replaced stock recovery, then please do not let your phone try to install any OTA updates!!!
As stated in another Question/Answer, using JCASE's SlapMyMoto, RockMyMoto and PwnMyMoto to root will replace your recovery to allow for the ability to boot with R/W permitted. When the OTA update downloads to your phone, and it tries to reboot to install it, the phone/update is trying to use the stock recovery to install the update. Since it is not there, the update will fail and the phone will reboot and it will likely try to reboot and try to install again. This can often result in the phone being stuck in a boot loop of continually retrying to reboot and install the update. There are ways to fix this posted in other threads. NOTE: there may be ways to get around this and install the OTA zip but that is a topic for another thread.
If you have an unlocked bootloader and have installed a custom recovery, it might be possible to install the OTA ZIP manually, but again that is a topic for another thread.
[Q] Can I unlock the Bootloader on my Moto X? or How do I know if I can unlock my bootloader or not?
[A] If you have a Developer Edition Moto X, yes you can unlock the bootloader and it doesn't void your device warranty. If you have a MotoMaker or Carrier Branded model, it depends on IF your carrier allows Motorola to do it, and it will void your warranty. For example, Verizon and ATT does now allow Motorola to unlock your boot loader. T-Mobile users can unlock their bootloader but it will void their warranty.
To see if your Moto X bootloader can be unlocked visit -> https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth You can step through the process until you get to the final submit WITHOUT voiding your warranty. Based on the site's wording, once you hit the final submit to request the code, your warranty is voided (unless your phone is a developer edition)
[Q] How do I run a custom rom on my X?
[A] SlapMyMoto and the like is/are not a process to allow you to run custom roms.
Unless you have an unlocked bootloader, you can't remove the Stock Motorola ROM and run a completely custom rom. And because most X owners generally agree the stock X ROM is very good, there are not many custom roms available for the X, even for those with unlocked bootloaders. Any available custom roms are posted in -> http://forum.xda-developers.com/moto-x/development so please use those threads for info/discussions.
If you have locked bootloader, there are a few options for using Safestrap to allow for some customization or "alternate roms", but that is a topic which doesn't apply to this thread.
So what can we really do after we gain root. The obvious is run apps that require root but what else? I am a user and follow directions from devs on how to do things. So without the knowledge or experience of the deep pits of android what can I do with root? This root process looks a little tough but I could figure it out once I piece all the threads together to understand it better.
Sent from my vzw moto X
---------- Post added at 10:00 AM ---------- Previous post was at 09:54 AM ----------
Will this work on a non developer vzw phone?
http://forum.xda-developers.com/showthread.php?t=2521509
Sent from my vzw moto X
I am here to give a quick warning to all users. Please, do not revert to older versions of Android. This can cause your device to brick when you take an ota. The reason for the brick is because the ota process flashes secure elements and these elements can not be mixed. Once, you mix these you will brick. Also, if you have reverted the only safe way to update is thru a full xml.
If anyone would like to extend on this point please do. I am writing this up before class as I see people are bricking.
Sent from my XT1053 using Tapatalk
papi92 said:
I am here to give a quick warning to all users. Please, do not revert to older versions of Android. This can cause your device to brick when you take an ota. The reason for the brick is because the ota process flashes secure elements and these elements can not be mixed. Once, you mix these you will brick. Also, if you have reverted the only safe way to update is thru a full xml.
If anyone would like to extend on this point please do. I am writing this up before class as I see people are bricking.
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
1+^
Sent on my Gummy running Lenoto X
I'll only add that the first few bricks from this were just bad luck.....but after the posts about it.....the further bricks can be blamed on poor research, reading and self learning. These things are what XDA is supposed to be about. Blindly flashing this and that without doing homework first is a recipe for disaster with what we do here.
Sometimes people, like me, are brushed off as jerks or know it all's when we remind people of these things, or tell them to read and search instead of answering their questions.....but really we're just trying to help people help themselves and learn more about what they are doing.
Anyway.....personally ...I'll continue to be a "jerk" and remind people of this stuff occasionally, cause it just may get through to some people.
Also.....XDA rules state to search before posting....Wow has that been forgotten these days. LOL
Peace all!
Sent from my Moto X cellular telephone...
My sentiments too, at this rate I think the moto x will have the world record for hard bricks
Sent on my Gummy running Lenoto X
flashallthetime said:
My sentiments too, at this rate I think the moto x will have the world record for hard bricks
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
No kidding! LOL. I despise Samsung....but it was very hard to brick. LOL. This bootloader version mixed with OTA stuff on the X is a mess.
Sent from my Moto X cellular telephone...
---------- Post added at 07:21 PM ---------- Previous post was at 07:19 PM ----------
Oh...throw in unlocked bootloader methods, vs locked bootloader methods and the x can get pretty confusing. Personally.....I think people should avoid the phones that can't be boot loader unlocked like the plague. LOL
Sent from my Moto X cellular telephone...
Avoid flashing firmware at the least, there's now a flashable 4.4.2 stock ROM too, so you have options to safely flash roms
Sent on my Gummy running Lenoto X
If you are going play then you must be read to play. As for people who want to use otas there's a trick. Remove all secure elements from the zip just keep the patches to system boot and modem. That way you do not brick. But please don't return your X when you do brick because of taking OTAs on a Frankenstein device with this bootloader and that gpt
Sent from my XT1053 using Tapatalk
i think it's always a good idea not to go back in android versions!
Reading this makes me feel sad. I come from a SGSII, on which I could flash anything, without braking it .
So let me get this straight: if I have the Sprint version (no dev version available) and want root without voiding the warranty I have to downgrade to 4.2.2 and use RockMyMoto, flash 4.4, and use SlapMyMoto. However, if I do that, any future OTA upgrades will cause a brick so while I can flash future ROMs I will be stuck on the current firmware?
ahecht said:
So let me get this straight: if I have the Sprint version (no dev version available) and want root without voiding the warranty I have to downgrade to 4.2.2 and use RockMyMoto, flash 4.4, and use SlapMyMoto. However, if I do that, any future OTA upgrades will cause a brick so while I can flash future ROMs I will be stuck on the current firmware?
Click to expand...
Click to collapse
No , the problem happens when you upgrade your boot loader to 4.4.2, you can not downgrade. As long as you stay with 4.4 BOOTLOADER you can downgrade to 4.2.2 post camera ota. If you flash the 4.4.2 BOOT LOADER and decide to Frankenstein your phone and flash an older boot loader , you're SOL, 4.4.2 BOOT LOADER is a one way ticket
Regardless if your boot loader is unlocked or locked. Just because I have a unlocked boot loader does not give me Amy extra ability to flash an older boot loader ,it gves me a better way of rooting and flashing roms
Sent on my Lenoto A2109 tablet
flashallthetime said:
No , the problem happens when you upgrade your boot loader to 4.4.2, you can not downgrade. As long as you stay with 4.4 BOOTLOADER you can downgrade to 4.2.2 post camera ota. If you flash the 4.4.2 BOOT LOADER and decide to Frankenstein your phone and flash an older boot loader , you're SOL, 4.4.2 BOOT LOADER is a one way ticket
Regardless if your boot loader is unlocked or locked. Just because I have a unlocked boot loader does not give me Amy extra ability to flash an older boot loader ,it gves me a better way of rooting and flashing roms
Sent on my Lenoto A2109 tablet
Click to expand...
Click to collapse
Thanks. My motomaker Moto X is on its way, hopefully it won't have the 4.4.2 boot loader from the factory.
Personally I think that anyone even remotely interested in hacking, flashing, or anything of that nature should have gotten a developer edition. Especially if you're not sure of what you're doing. No company has ever offered something that makes being a phone geek so easy and yet, not many have taken advantage.
I also feel that not enough people try to do things the "hard way". But I find fastboot way easier and safer than many of the tools provided. And once you learn it it's useful on many devices and similar to Odin etc. I just don't want Motorola getting a bad rap for other people's foolishness
MotoX GSM Developer Edition, Bootloader Unlocked, Rooted, Stock 4.4.2 Great Britain on T-Mobile !
SymbioticGenius said:
Personally I think that anyone even remotely interested in hacking, flashing, or anything of that nature should have gotten a developer edition. Especially if you're not sure of what you're doing. No company has ever offered something that makes being a phone geek so easy and yet, not many have taken advantage.
I also feel that not enough people try to do things the "hard way". But I find fastboot way easier and safer than many of the tools provided. And once you learn it it's useful on many devices and similar to Odin etc. I just don't want Motorola getting a bad rap for other people's foolishness
MotoX GSM Developer Edition, Bootloader Unlocked, Rooted, Stock 4.4.2 Great Britain on T-Mobile !
Click to expand...
Click to collapse
It makes no difference having a DE edition or a Rogers unlockable boot loader moto as I have , they are essentially the same beast, I can do everything you can do, a DE edition will brick as fast as any other moto variant. I think people who have no common sense is the problem, they assume that flashing firmware is like flashing custom ROMs and its not
Sent on my Lenoto A2109 tablet
papi92 said:
If you are going play then you must be read to play. As for people who want to use otas there's a trick. Remove all secure elements from the zip just keep the patches to system boot and modem. That way you do not brick. .........
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
Out of curiosity. Have you done this with your X? From what I gather it seems to be a "safe(r)" way of upgrading without compromising the bootloader, yet I haven't read where anyone has actually tried doing it. The threads where those on 4.2.2 flashing 4.4.x firmwares from other carriers is coming to mind. Why risk it if what you are saying works? I have a new VZ dev ed that I'm trying to figure out how to handle the 4.2.2 update on, if it ever comes.
edthesped said:
Out of curiosity. Have you done this with your X? From what I gather it seems to be a "safe(r)" way of upgrading without compromising the bootloader, yet I haven't read where anyone has actually tried doing it. The threads where those on 4.2.2 flashing 4.4.x firmwares from other carriers is coming to mind. Why risk it if what you are saying works? I have a new VZ dev ed that I'm trying to figure out how to handle the 4.2.2 update on, if it ever comes.
Click to expand...
Click to collapse
He's a developer, staying with only system images and modems your safer, modems do not always work in specific locations, UK modem will not work in Brazil, so keep your existing modem , the system files are all basically the same with minor changes, T-Mobile and rogers have no bloat, rogers has the carrier logo, where T-Mobile doesn't, at&t has at&t bloatware. As for Verizon,spring and us cell I have no idea as its CDMA and I have the gsm variant
Sent on my Lenoto A2109 tablet
flashallthetime said:
He's a developer, staying with only system images and modems your safer, modems do not always work in specific locations, UK modem will not work in Brazil, so keep your existing modem , the system files are all basically the same with minor changes, T-Mobile and rogers have no bloat, rogers has the carrier logo, where T-Mobile doesn't, at&t has at&t bloatware. As for Verizon,spring and us cell I have no idea as its CDMA and I have the gsm variant
Sent on my Lenoto A2109 tablet
Click to expand...
Click to collapse
It's starting to come together...
Knowing this I still don't quite get why so many people seemed to be flashing firmware from other carriers when they could have cherry picked what they "needed".
It would be nice to figure out how to use the system.img from other carriers as VZ's firmware appears to have about 100MiB of "added features" that I'd prefer not to have.
Being that the risk appears to be negligible I may attempt to push the system.img from another carrier to see what happens.
edthesped said:
It's starting to come together...
Knowing this I still don't quite get why so many people seemed to be flashing firmware from other carriers when they could have cherry picked what they "needed".
It would be nice to figure out how to use the system.img from other carriers as VZ's firmware appears to have about 100MiB of "added features" that I'd prefer not to have.
Being that the risk appears to be negligible I may attempt to push the system.img from another carrier to see what happens.
Click to expand...
Click to collapse
You can flash other carrier images, sprint and us cell are 2 CDMA carriers without any issues, system IMG ,boot IMG and non_hlos.bin are the files you need (not motoboot.IMG that's the bootloader)
Sent on my Lenoto A2109 tablet
So many of the brick stories I'm reading about could have been avoided had people trying to expedite the upgrade to 4.4.2 just flashed everything but the bootloader?
At some point I need to figure out how to get one of the bloatless system files VZ X as I'm not sure where the 100MB of stuff comes from.
Next steps, tell self "yes this phone is worth keeping" and unlock the bootloader.
Again, thanks for your patience
edthesped said:
So many of the brick stories I'm reading about could have been avoided had people trying to expedite the upgrade to 4.4.2 just flashed everything but the bootloader?
At some point I need to figure out how to get one of the bloatless system files VZ X as I'm not sure where the 100MB of stuff comes from.
Next steps, tell self "yes this phone is worth keeping" and unlock the bootloader.
Again, thanks for your patience
Click to expand...
Click to collapse
Yes but people always jump in head first, the only issue is if they happen to flash the old system.img 4.4 and have the 4.4.2 boot loader, chances are they will end up hard bricked, why? Going back to 4.4 will ping moto servers for the ota, it gets downloaded and installed, bam hard bricked,
If you flash just system.img , do not take any ota at all
Sent on my Lenoto A2109 tablet
So I just rooted my Verizon Samsung Galaxy Note 3 with Kingo. All I have installed so far is SuperSu Pro and Titanium backup. Im on android 4.3 and I have the MJE version. (which seems to be the most uncommon because I cant find any help anywhere, so im posting this thread). All I want to know is how or if I even can get the CyanogenMod rom on my phone. This is my first android device ever and I've had it for 5 months and Im definitely never going back to Apple devices. Anyway, I just rooted, I dont care about tripping Knox because I dont have a warranty anyways. I just need someone to explain to me how to get all the things I need including CM. From what ive read I need CWM and GAPPS.
khampton_03 said:
So I just rooted my Verizon Samsung Galaxy Note 3 with Kingo. All I have installed so far is SuperSu Pro and Titanium backup. Im on android 4.3 and I have the MJE version. (which seems to be the most uncommon because I cant find any help anywhere, so im posting this thread). All I want to know is how or if I even can get the CyanogenMod rom on my phone. This is my first android device ever and I've had it for 5 months and Im definitely never going back to Apple devices. Anyway, I just rooted, I dont care about tripping Knox because I dont have a warranty anyways. I just need someone to explain to me how to get all the things I need including CM. From what ive read I need CWM and GAPPS.
Click to expand...
Click to collapse
Slow down there. Lol. Do you have a developer edition Note 3 or just a regular retail Note 3 you purchased from Verizon?
Adam Browning said:
Slow down there. Lol. Do you have a developer edition Note 3 or just a regular retail Note 3 you purchased from Verizon?
Click to expand...
Click to collapse
Lol sorry Im very new to android. I got it from Verizon but i enabled Developer mode if thats what youre asking haha.
khampton_03 said:
Lol sorry Im very new to android. I got it from Verizon but i enabled Developer mode if thats what youre asking haha.
Click to expand...
Click to collapse
It's all good lol. No, developer mode just gives you some extra features if you want to debug your device. A developer edition Note 3 is a phone that was available directly from Samsung in a small quantity. It had the bootloader unlocked, which is a must for a AOSP ROM such as Cyanogenmod. Cyanogenmod requires a custom kernal, which a retail Note 3 (that you purchase through Verizon or another retail store) can not flash due to the locked bootloader. I would suggest peeking over in the Android Development section to check out the ROMs you are able to flash. Just steer clear of the ones saying for the developer edition or DE (for short). If you're wanting a ROM that has an AOSP feel to it though, check out Eclipse.
Here is a link for the Eclipse thread: http://forum.xda-developers.com/showthread.php?t=2620723
Adam Browning said:
It's all good lol. No, developer mode just gives you some extra features if you want to debug your device. A developer edition Note 3 is a phone that was available directly from Samsung in a small quantity. It had the bootloader unlocked, which is a must for a AOSP ROM such as Cyanogenmod. Cyanogenmod requires a custom kernal, which a retail Note 3 (that you purchase through Verizon or another retail store) can not flash due to the locked bootloader. I would suggest peeking over in the Android Development section to check out the ROMs you are able to flash. Just steer clear of the ones saying for the developer edition or DE (for short). If you're wanting a ROM that has an AOSP feel to it though, check out Eclipse.
Click to expand...
Click to collapse
So could I somehow unlock the bootloader??
khampton_03 said:
So could I somehow unlock the bootloader??
Click to expand...
Click to collapse
Many people have looked into that, and no luck so far. It is still locked for devices such as ours. Kind of sucks, I know. Almost every Android phone I've owned, I have ran Cyanogenmod on it. With Verizon being difficult about locking the bootloaders, and Samsung introducing Knox, I don't think we will see a bootloader unlock anytime soon, if ever. With the new 4.4.2 leak that BeansTown106 has made available for us here:
http://forum.xda-developers.com/showthread.php?t=2726558
Kernal modules are enabled, so we may have a workaround in the near future for the locked bootloader. I would suggest not taking the OTA for 4.4.2, but instead flashing the leaked 4.4.2 that is available via that thread. Once you take the OTA, it isn't known if you'll ever be able to flash this leak, which may allow for a modified kernal and therefore AOSP ROMs. I may be mistaken in some of the details, and someone can correct me if I have said something wrong in this, but this thread will explain it a little better:
http://forum.xda-developers.com/showthread.php?t=2727876
Adam Browning said:
Many people have looked into that, and no luck so far. It is still locked for devices such as ours. Kind of sucks, I know. Almost every Android phone I've owned, I have ran Cyanogenmod on it. With Verizon being difficult about locking the bootloaders, and Samsung introducing Knox, I don't think we will see a bootloader unlock anytime soon, if ever. With the new 4.4.2 leak that BeansTown106 has made available for us here:
http://forum.xda-developers.com/showthread.php?t=2726558
Kernal modules are enabled, so we may have a workaround in the near future for the locked bootloader. I would suggest not taking the OTA for 4.4.2, but instead flashing the leaked 4.4.2 that is available via that thread. Once you take the OTA, it isn't known if you'll ever be able to flash this leak, which may allow for a modified kernal and therefore AOSP ROMs. I may be mistaken in some of the details, and someone can correct me if I have said something wrong in this, but this thread will explain it a little better:
http://forum.xda-developers.com/showthread.php?t=2727876
Click to expand...
Click to collapse
So back to the beginning haha how do I flash a rom or what should I do since I just rooted and only have supersu haha
khampton_03 said:
So back to the beginning haha how do I flash a rom or what should I do since I just rooted and only have supersu haha
Click to expand...
Click to collapse
It all depends on what you want to do. How knowledgeable are you with rooting, Odin, and flashing in general?
Adam Browning said:
It all depends on what you want to do. How knowledgeable are you with rooting, Odin, and flashing in general?
Click to expand...
Click to collapse
Ive never flashed anything and I dont know how to use odin. Lol
khampton_03 said:
Ive never flashed anything and I dont know how to use odin. Lol
Click to expand...
Click to collapse
Lol. Oh goody. Well you're in for a lot of reading then. If you're already rooted and have supersu installed, then at least you have that part out of the way. The way that we install custom ROMs onto our phones (since the bootloader is locked) is by using Safestrap, developed by Hashcode. You can find any and all information you will need on it here:
http://forum.xda-developers.com/showthread.php?t=2517610
Safestrap gives you the ability to have multiple custom ROMs on your phone, without having to flash directly over your stock ROM (if you don't want). It is an application that you download onto your phone, you then open it up and install custom recovery. Once that is completed, you will then see a Safestrap screen everytime you turn on or restart your phone. I would suggest reading through or at least skimming the thread via the link provided above.
Once you have created a ROM slot and have it selected as the active slot, you can then proceed to install a custom ROM into that slot. Once you have everything set up, you can then switch between the custom ROM in "Slot x" to the stock ROM slot, giving you a cushion in case you completely screw up.
You're going to have to decide whether or not you want to stay on the 4.3 base, or update to the 4.4.2 base leak. The only advantages of either one are strictly your personal preference. There are a few that prefer the 4.4.2 base over the 4.3 base due to one reason or another. If you want to update the the newest 4.4.2 base leak though, follow the instructions provided via this link:
http://forum.xda-developers.com/showthread.php?t=2726558
Adam Browning said:
Lol. Oh goody. Well you're in for a lot of reading then. If you're already rooted and have supersu installed, then at least you have that part out of the way. The way that we install custom ROMs onto our phones (since the bootloader is locked) is by using Safestrap, developed by Hashcode. You can find any and all information you will need on it here:
http://forum.xda-developers.com/showthread.php?t=2517610
Safestrap gives you the ability to have multiple custom ROMs on your phone, without having to flash directly over your stock ROM (if you don't want). It is an application that you download onto your phone, you then open it up and install custom recovery. Once that is completed, you will then see a Safestrap screen everytime you turn on or restart your phone. I would suggest reading through or at least skimming the thread via the link provided above.
Once you have created a ROM slot and have it selected as the active slot, you can then proceed to install a custom ROM into that slot. Once you have everything set up, you can then switch between the custom ROM in "Slot x" to the stock ROM slot, giving you a cushion in case you completely screw up.
You're going to have to decide whether or not you want to stay on the 4.3 base, or update to the 4.4.2 base leak. The only advantages of either one are strictly your personal preference. There are a few that prefer the 4.4.2 base over the 4.3 base due to one reason or another. If you want to update the the newest 4.4.2 base leak though, follow the instructions provided via this link:
http://forum.xda-developers.com/showthread.php?t=2726558
Click to expand...
Click to collapse
So I am going to install Kitkat by watching the video on the thread. He said something about making sure the "MD5's match". What does that mean?
khampton_03 said:
So I am going to install Kitkat by watching the video on the thread. He said something about making sure the "MD5's match". What does that mean?
Click to expand...
Click to collapse
That, you don't really have to worry about honestly. I never check, though it may be good practice to. Just follow along with the video in the thread and you will be good to go. Just remember that after you install 4.4.2, you cannot flash 4.3 based ROMs. Also, there is a bug in Safestrap right now that renders the ROM slots somewhat useless, though you can attempt to use them at your own risk. If you want to flash one of the 4.4.2 based ROMs afterwards, it is suggested to back up the stock ROM, and flash the custom ROM in the stock ROM slot. All I can say is, goodluck. Lol. It is a fun process, though somewhat difficult at times. If you have anymore questions after the fact, just reply here. I'll help out as much as I can. It always puts a smile on my face to help convert an Apple fanboy/girl over to Android.