Alright guys, I have a question for you all. Some of you may remember me from the Atrix HD, and know that I love Motorola. Right now I am using a Samsung Galaxy S4 (go ahead and make fun of my, this phone stinks).
Anyways I want to move back to Motorola and the X is probably the best way to do so. I was smart enough to sign my soul to Verizon for two years and the only way to get an unlocked BL will be through the Dev Edition. Now here is the question, is the Dev Edition worth it? I never thought I would have to ask this, but Moto did a HELL of a job with their software. It seems like there would be no point to this phone if you aren't taking full advantage of the X8 chip. It is another 150 bucks for an non customized/dev edition phone.
Your thoughts on it guys? Unlike I did with the Atrix I plan on making this phone last a long while so that is what makes me think "for longevity and so I don't get bored, maybe an unlocked bootloader is necessary." At the same time, I would like to get input from Moto X owners, since you all will know the phone better than me.
Thanks for all of your opinions in advance!
Edit: Put in general because want to see more of a discussion on benefits vs negatives. Also different points of view.
I can tell you that, as a tinkerer that needed to unlock all his bootloaders all the time, I've only needed root for my VZW Moto X Developer Edition. I unlocked because I could, but I haven't felt the need to install any mods to this phone whatsoever...the software is that good! All I did was root.
Sent from my XT1060 using Tapatalk
MadManMoon said:
I can tell you that, as a tinkerer that needed to unlock all his bootloaders all the time, I've only needed root for my VZW Moto X Developer Edition. I unlocked because I could, but I haven't felt the need to install any mods to this phone whatsoever...the software is that good! All I did was root.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply man! I was just thinking "I root for vanilla android" and that is what the X gives you but with more features lol. We will see how I feel when I decide to pull the trigger. Will I want to customize the phone, or be able to flash the hell out of it. Will all depend on my mood I'm guessing lol
I'm coming from a little different angle. I had the VZW Dev Edition in my cart on CyberMonday, but "thanks" to Motorola's mess-up, lost it in the process. So, no way I'd pay full price for one after they excluded the DE from follow-up deals. Decided to take a peek at the retail version to see if I could tolerate it without an unlocked bootloader (coming from the Razr M with unlocked bootloader). To be honest, I'm really liking the X with just root + Xposed (with GravityBox, Greenify, JellyBean 4.x Airplane Mode Helper, and Xad) ... rather than flashing ROMs, its become checking out Xposed modules.
I would much rather get a MotoMaker one. I have a Sprint Variant, and I can unlock boot loader on there but I haven't. All I need is Root for Titanium backup and I used SlapMyMoto for that. Its really easy if you have used ADB in the past
Dev edition. The option to unlock is there. It also sends a message that people are interested in unlockable phones.
The moto X stock software is good, no doubt, but I always want the option to install something different when I want.
Dev Edition. It was not only nice how quick and easy it was for me to unlock and root it, obtaining the code being the only added step over my nexus devices, and not nearly as drawn out as the locked method. You also maintain warranty through unlocking compared to MotoMaker devices that still allow for it.
If there is even a chance you are going to want advantages of an unlocked bootloader, don't risk it and just grab the DE.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
cvhovey said:
I'm coming from a little different angle. I had the VZW Dev Edition in my cart on CyberMonday, but "thanks" to Motorola's mess-up, lost it in the process. So, no way I'd pay full price for one after they excluded the DE from follow-up deals. Decided to take a peek at the retail version to see if I could tolerate it without an unlocked bootloader (coming from the Razr M with unlocked bootloader). To be honest, I'm really liking the X with just root + Xposed (with GravityBox, Greenify, JellyBean 4.x Airplane Mode Helper, and Xad) ... rather than flashing ROMs, its become checking out Xposed modules.
Click to expand...
Click to collapse
Yup, GravityBox covers everything I wanted out of custom roms.
nhizzat said:
Yup, GravityBox covers everything I wanted out of custom roms.
Click to expand...
Click to collapse
Yup. I won't be using custom roms on this phone. Stock and xposed are all I need. Not messing with a good thing.
Sent from my XT1058 using Tapatalk
If you want to root.. then Dev edition.
With the Retail and Moto Maker variants on Verizon, you can not unlock your boot loader. To Root you are stuck waiting on an exploit to be found and a safe repeatable process being created and released in order to gain root. There is no guarantee that future updates will be rootable, or that you will be able to flash to older stock ROMs if you want to be rooted. While you can safestrap to other "roms" you can't replace the Kernel, so you are a little more limited in that respect, along with the storage space taken up on the phone by the safestrap rom.
With the Dev Edition, you just unlock the bootloader, flash TWRP, boot into TWRP and use its menu option to root, or flash/install SuperSu to gain root. No need to wait. Unlocking your bootloader, you can flash any rom, signed or unsigned so down the road, there is the possibility of flashing custom roms, should Moto/VZW stop pushing updates out. And flashing those roms replaces the stock rom, so no additional storage is taken up.
Yes the DE is more expensive initially to purchase than the Retail or Moto Maker version. Yes, you can currently ROOT the retail or MotoMaker version (using SlapMyMoto), and you can gain full time R/W enablement (using MotoWPNoMo), but they are involved processes, future OTA updates will likely break them meaning you'll need to wait on a process to get to "stock" to accept OTAs, and need to wait on an exploit/procedure to be released to root again, or you are stuck on the current firmware version.
KidJoe said:
If you want to root.. then Dev edition.
With the Retail and Moto Maker variants on Verizon, you can not unlock your boot loader. To Root you are stuck waiting on an exploit to be found and a safe repeatable process being created and released in order to gain root. There is no guarantee that future updates will be rootable, or that you will be able to flash to older stock ROMs if you want to be rooted. While you can safestrap to other "roms" you can't replace the Kernel, so you are a little more limited in that respect, along with the storage space taken up on the phone by the safestrap rom.
With the Dev Edition, you just unlock the bootloader, flash TWRP, boot into TWRP and use its menu option to root, or flash/install SuperSu to gain root. No need to wait. Unlocking your bootloader, you can flash any rom, signed or unsigned so down the road, there is the possibility of flashing custom roms, should Moto/VZW stop pushing updates out. And flashing those roms replaces the stock rom, so no additional storage is taken up.
Yes the DE is more expensive initially to purchase than the Retail or Moto Maker version. Yes, you can currently ROOT the retail or MotoMaker version (using SlapMyMoto), and you can gain full time R/W enablement (using MotoWPNoMo), but they are involved processes, future OTA updates will likely break them meaning you'll need to wait on a process to get to "stock" to accept OTAs, and need to wait on an exploit/procedure to be released to root again, or you are stuck on the current firmware version.
Click to expand...
Click to collapse
I agree with everything in this post. Plus, the ability to do all this stuff without voiding my warranty was a huge selling point for me.
I would say DEV edition. I'm just looking into custom roms, but even without that, I personally want the ability to update the device once Moto stops supporting it.
I might me in the minority here, but get a custom MotoMaker one. The software is perfect as it is. No kernels for the X so far, and I dont believe anyone is working on one either. Rooting isnt hard, takes a little longer than the unlocked BL version, but shouldn't be a concern, as of now. Sure, the unlocked BL gives you a sense of security with the warranty, but since you wouldnt be doing much flashing, I dont see a point.
NPOA556 said:
I agree with everything in this post. Plus, the ability to do all this stuff without voiding my warranty was a huge selling point for me.
Click to expand...
Click to collapse
I agree with that entire post too. This isn't my first rodeo tho so I knew almost everything posted lmao. I was mainly curious to if people that usually flash the hell out of their phones (like me), if they are doing the same with the Moto X. Waiting now to see if I get approved to finance it. If I do the Dev Edition it is!
anirudh412 said:
I might me in the minority here, but get a custom MotoMaker one. The software is perfect as it is. No kernels for the X so far, and I dont believe anyone is working on one either. Rooting isnt hard, takes a little longer than the unlocked BL version, but shouldn't be a concern, as of now. Sure, the unlocked BL gives you a sense of security with the warranty, but since you wouldnt be doing much flashing, I dont see a point.
Click to expand...
Click to collapse
Did you ever root the atrix HD with Dan's second method (I think second at least) now that was a true pain in the ass lol
SirHoover2010 said:
I agree with that entire post too. This isn't my first rodeo tho so I knew almost everything posted lmao. I was mainly curious to if people that usually flash the hell out of their phones (like me), if they are doing the same with the Moto X. Waiting now to see if I get approved to finance it. If I do the Dev Edition it is!
Click to expand...
Click to collapse
I flashed several versions of AOKP on my previous phone (Samsung Fascinate), but I do not plan to do any flashing on my Moto X until it is no longer supported by Moto/VZW. Dev Edition gives me that ability though, plus easy unlocking and rooting. Xposed really negates the need to flash custom ROMs, in my opinion.
1) Has there been any stable ROM worth flashing on the Moto X?
2) If you do flash ROMs on the Moto X, do touchless controls and active display still work perfectly?
I chose the Dev Edition because, well, I like to tinker with my devices. Even if only to prove it to myself that something is possible and revert back. I also wanted the added benefit of future-proofing. If the development scene ever picks up here, I might want to flash a custom ROM. Plus, the ability to have and flash the factory images are probably the most important to me. Along those lines, here's what happened to me recently:
After using everything stock for a few days (well, rooted stock) after getting my Moto X, I decided to start tinkering with it a bit. Changing a few things here and there. I decided that the icons were way too big, so I went in with my file explorer and did an edit of build.prop to change the screen density (DPI). Before editing, I also backed up build.prop to my /sdcard/, just in case. Anyway, after editing it, and rebooting, I decided to change back because I made the density too small. I decided to replace my edited build.prop in /system/ with my backed up one from my /sdcard/ instead of re-editing it. Did it, rebooted, and got into a weird bootloop where it would come on with the standard "OMGOD YOUR BOOTLOADER IS UNLOCKED! DID YOU KNOW THAT!?!?" message that comes from the bootloader (changes to that after unlocking), then seems to pass to regular Android boot process, but the screen stayed black. I thought it just turned off, but it was still drawing power and when I went to boot it back on, it vibrated once, and the screen stayed black. Then trying again, I get the boot process as before (so what I'm saying is it must stay turned on instead of turning off due to failed boot). ANYWAY: I went into recovery to restore my nandroid I had, and for some reason couldn't even get into recovery (which is weird; why would even a fully corrupt /system/ partition affect my recovery partition?). I tried and tried and nothing. I finally decided to get the factory images from Motorola and return to stock.
After a few days of waiting for the factory images and finally getting around to it (I used my Nexus 5 in the meantime), I decided to go ahead and flash everything manually. I went to my computer, got the factory images in place, everything set up, etc. Right before executing the first flash command, I decided to myself that I'd try to get into recovery again, just for the heck of it. Just to see. Well lo and behold. I can get into recovery now, for some magical reason. So I restore my nandroid, and everything is back to normal. I guess I didn't need to grab the factory images yet, but it was nice to get them for when I do. The moral to this story, is it's really nice to be able to flash the factory images if you really get yourself into trouble. Or just to return to stock.
tl;dr I went with the Dev Edition because it's nice to be able to flash anything you want, have a permanent solution to rooting, and it's also great to have an end-all, be-all solution to any trouble you get yourself into (excluding corrupting your bootloader, but let's be honest, you almost have to try to do that).
Varking said:
1) Has there been any stable ROM worth flashing on the Moto X?
2) If you do flash ROMs on the Moto X, do touchless controls and active display still work perfectly?
Click to expand...
Click to collapse
Well idk about #1 but I suppose a customized stock ROM could support all those features. Although watching walk through videos of this phone idk what would be the point of changing the stock ROM.
Also very good points Johmama. Also like someone else stated, you are also supporting the market for developer devices!
Related
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.
I may have messed up, but I am not 100%, not use to Samsung Devices.
I have a developers edition S5.
I tried to run updates but it would not take any update OTA even though there were two, NCG was the current room.
I flashed the ni2 via odin.
Now on the screen, instead of Mode: Developer, it says Qualcomm Secureboot.
I am not sure if I relocked the bootloader, if it can be unlocked,
Or this just the need to go into a recovery and flash a different rom.
Did I relock the bootloader?
hill180 said:
I may have messed up, but I am not 100%, not use to Samsung Devices.
I have a developers edition S5.
I tried to run updates but it would not take any update OTA even though there were two, NCG was the current room.
I flashed the ni2 via odin.
Now on the screen, instead of Mode: Developer, it says Qualcomm Secureboot.
I am not sure if I relocked the bootloader, if it can be unlocked,
Or this just the need to go into a recovery and flash a different rom.
Did I relock the bootloader?
Click to expand...
Click to collapse
I believe you have. But first I need to ask you 1) were you rooted and 2) did you have a custom recovery (TWRP) on your phone before you ODIN'd NI2? If you had TWRP on your phone before ODIN can you get into TWRP recovery now? Just an FYI, Samsung does not send out, in any form (OTA or otherwise) updates to the Developer Edition phones. The explanation for why they don't is long and no one except for Samsung knows for sure and they are not commenting on the issue. Dev owners keep their phones up to date by flashing custom ROMs released by our Dev community for retail and dev edition phones.
hill180 said:
Did I relock the bootloader?
Click to expand...
Click to collapse
When you flashed the stock tar you locked the bootloader and unfortunately you will need to contact Samsung and explain what you did. Most likely you will need to send the phone in so they can unlock it again. Contact them first.
Misterxtc said:
When you flashed the stock tar you locked the bootloader and unfortunately you will need to contact Samsung and explain what you did. Most likely you will need to send the phone in so they can unlock it again. Contact them first.
Click to expand...
Click to collapse
I think you're right Misterxtc, unfortunately all Samsung is going to do is return him a retail version of the S5. According to 3 other Dev owners that locked their bootloaders all Samsung would do is return their phones to working order, but no unlocked bootloader.
jpcalhoun said:
I think you're right Misterxtc, unfortunately all Samsung is going to do is return him a retail version of the S5. According to 3 other Dev owners that locked their bootloaders all Samsung would do is return their phones to working order, but no unlocked bootloader.
Click to expand...
Click to collapse
That doesn't sound too promising. They really need to change their policy on that.
im not sure why you would have flashed a ne9 tar when instructions clearly say NOT to flash odin tars on a dev edition s5 because it will lock the bootloader
Sent from my SM-G900V using XDA Free mobile app
Thank you all.
Yes the phone has been locked. Obviously I blame myself for not researching and just assuming.
If there is a silver lining, it appears my phone has a bad microphone, when I called, Samsung wanted to do an warranty exchange. I told them it was a new item less than 5 days, so I am just going to return.
Still debating if I should wait a few month and get the S5 locked from VZW as I am not seeing a lot of dev (although it makes it easier to root), or if I should get another model of phone all together, or reorder the S5 Dev Edition.
hill180 said:
Thank you all.
Yes the phone has been locked. Obviously I blame myself for not researching and just assuming.
If there is a silver lining, it appears my phone has a bad microphone, when I called, Samsung wanted to do an warranty exchange. I told them it was a new item less than 5 days, so I am just going to return.
Still debating if I should wait a few month and get the S5 locked from VZW as I am not seeing a lot of dev (although it makes it easier to root), or if I should get another model of phone all together, or reorder the S5 Dev Edition.
Click to expand...
Click to collapse
I hope Samsung does right by you. Just my opinion, but I think the Developer Edition S5 is the best phone on the market right now. The only other phone, that I know of, that allows the user the flexibility and performance of a unlocked bootloader phone is the HTC M8. The M8 is a good phone no doubt, but I like the S5 better. True, there aren't that many ROMs rilght now, but more and more get added as time goes by. The ROMs that are available are good, staple ROMs and range anywhere from super customization available to the user to lean, debloated super fast with great battery life...and a couple in between. Your choice, but if Samsung will replace your Dev Edition with a new Dev Edition...I think that is your best bet right now. But that is just my opinion. Good luck.
jpcalhoun said:
I hope Samsung does right by you. Just my opinion, but I think the Developer Edition S5 is the best phone on the market right now. The only other phone, that I know of, that allows the user the flexibility and performance of a unlocked bootloader phone is the HTC M8. The M8 is a good phone no doubt, but I like the S5 better. True, there aren't that many ROMs rilght now, but more and more get added as time goes by. The ROMs that are available are good, staple ROMs and range anywhere from super customization available to the user to lean, debloated super fast with great battery life...and a couple in between. Your choice, but if Samsung will replace your Dev Edition with a new Dev Edition...I think that is your best bet right now. But that is just my opinion. Good luck.
Click to expand...
Click to collapse
Thanks, Samsung is def returning the Dev phone without a 15% restock (have rma). Not because of the locking, but because of the mic. I think you are correct.
I had to go to my standby which is the dev Moto X. Love this phone, but the photos are bad, and it is slow. When I confirm the credit has been giving for the Dev phone, I will reorder the Dev edition. This time I will have to figure out a way to make a backup for resell, and flash only using TWRP.
hill180 said:
Thanks, Samsung is def returning the Dev phone without a 15% restock (have rma). Not because of the locking, but because of the mic. I think you are correct.
I had to go to my standby which is the dev Moto X. Love this phone, but the photos are bad, and it is slow. When I confirm the credit has been giving for the Dev phone, I will reorder the Dev edition. This time I will have to figure out a way to make a backup for resell, and flash only using TWRP.
Click to expand...
Click to collapse
I've always been a Moto fan myself, but although they still make good phones, they're not great phones (camera, display etc). I just post a "Do's and Don'ts" for Dev owners. Give it a read and let me know if I should add something to the thread. I've seen six users brick their Dev S5s in the past couple of weeks, hopefully the thread will help the next guy from making a mistake: http://forum.xda-developers.com/verizon-galaxy-s5/general/developer-edition-s5-dos-donts-t2895563
jpcalhoun said:
I've always been a Moto fan myself, but although they still make good phones, they're not great phones (camera, display etc). I just post a "Do's and Don'ts" for Dev owners. Give it a read and let me know if I should add something to the thread. I've seen six users brick their Dev S5s in the past couple of weeks, hopefully the thread will help the next guy from making a mistake: http://forum.xda-developers.com/verizon-galaxy-s5/general/developer-edition-s5-dos-donts-t2895563
Click to expand...
Click to collapse
great read. (I my case I would have still been returning my phone, but the next S5 will be safe )
The only add, if even possible. It is possible to backup the stock recovery before installing TWRP. So when it is time to sell, you can return the TWRP original backup and flash the original stock recovery?
hill180 said:
great read. (I my case I would have still been returning my phone, but the next S5 will be safe )
The only add, if even possible. It is possible to backup the stock recovery before installing TWRP. So when it is time to sell, you can return the TWRP original backup and flash the original stock recovery?
Click to expand...
Click to collapse
That's a great question and one that I have been trying to figure how to do. I am not sure about this, but in order to backup a stock recovery you would have to use ADB and do a total backup of the phone that way. I have never tried that and I don't know for sure if it will even work using ADB. Here is how I look at it...who would want to pay $550 (or less) for a Developer Edition phone and never replace the stock recovery with a custom recovery? It doesn't make sense. In fact, the only way you can tell that a Developer Edition phone has not been inadvertently "locked" (not trying to stick a finger in your eye here) is to ask/see if a custom recovery is installed. If not, then there is no guarantee to the buyer that the bootloader is truly unlocked. SafeStrap does not count!
So. Here we are.
The Samsung Galaxy S9 and S9+ have been released, and many of us are just now hopping on the S8/+ bandwagon. I, very recently, purchased a SM-G955U model variant of the S8+ (hence the second 5 :silly and, like many of you, wanted to root it as soon as I got my hands on it.
I was happily impressed when I hopped on XDA and saw that there were at least *some* relatively updated custom ROMs and root methods. I tried out several using Odin3 (PCR.. and SamPWND... cuz those were the only two relatively popular threads that I found in my 2 minute search) and PCR struck my eye. I downloaded all the necessary files, taking well over 30 minutes on my potatonet, made sure I had both Odin3 and PrinceComsy Odin3 (and Kies... I think that's still relevant), setup the BootLoader, AP, whatever all the other buttons do, and clicked start.
Waited for a few seconds and... a (Succeed 0 / Failed 1) message appeared, as soon as it started.
Looked at my phone, the realization that it wasn't in Download mode kicked in and I smacked myself in the face.
Rebooted into Download mode, reset PrinceComsy Odin, smashed all the buttons again, clicked start and..
(Succeed 0 / Failed 1).
Great.
This has repeated for 3 days now, on all computers, 10s of different USB cables, well over 20 different USB ports (hubs not included).
So, I decided at a different approach. I'm sure we all know those "CLICK ME DOWNLOAD ME FOR FREE ROOT I-I CAN REALLYDO IT GUYS JU-JUST DOWNLOAD ME!* advertisements. One in particular struck my eye, no names will be given, and I tried it out.
Downloaded the Windows executable for the laughs and giggles (never thinking it would actually work) and whaddya know, right after telling me my device is rootable it's now asking me for 40$.
I figured, what the hell, I just got paid and sent the money over thinking I was about to get scammed. Hoped on live chat and setup everything the way they asked me to (taking even longer than a grandma driving because potatonet) and they start, and I'm not joking, REMOTE CONTROLLING my PC to root my phone (granted, the root method for my phone was advertised, blatantly stating they would have to control my PC but.. come on).
At this point all I can think about is how I'm lucky I have a throwaway PC and this phone doesn't mean my life or I would be really pissed when I start seeing a worm come out of my harddrive.
Needless to say the process took about an hour, maybe an hour and a half (much longer than their *15-20 minute* claim time, but not awful nonetheless) and I walked out of there with a non-bricked rooted S8+.
So.. what exactly went wrong with my setup, and how can you guys avoid spending 40$ just to ROOT YOUR PHONE.
I'm not a professional. I can't offer professional advice. But what I can tell you is I know exactly what went wrong for me in this case.
I never flashed the 7.0 stock android ROM. I was trying to flash PCR (which, ironically enough is what said company used.. yes.. they used PCR. Not a custom method. Not a custom ROM. They literally used PCR) over 8.0.
So, I'm out 40$, but walked out with a rooted S8+ and I'm fairly happy. Apparently those root programs aren't ALL bad.
But seriously.. why aren't there any 8.0 ROMs or root methods that actually work? Every method I've seen requires you to downgrade. I know Oreo only came out last month but there are some seriously talented people here on XDA and the fact that I had to downgrade just to have to reflash in about a month or twos time is frustrating to say the least. But, that's just venting and off-topic.
So, laugh at the idiotboy who couldn't figure out how to read instructions properly or setup his project right, but just know.. just know.. I spent 40$ to root my phone. And that, my friends, is an amazing feat.
(Also, I apologize if this isn't in the right section.. I feel like it's not but I have NO idea where else to post this. This is more of a story thread to make myself the eye of the public humiliation but it does also serve as a reminder to really check everything before you start rooting. I got lucky. I could have potentially hardbricked my brandnew s8+ simply because I didn't read the instructions properly, or plan correctly. This is something that a lot of new users fail to do, and then complain when *their phone is stuck in a bootloop*.
If you don't know what you're doing, there are plenty of people here on XDA and apparently all over the web who will be more than happy to take your money and root your phone, relatively safely, for you.)
well as jrkruse said
"root is not going to happen unless on of two things happen. Either we get combo oreo firmware so we have an oreo boot.img that is permissive or they event root that will work on stock enforcing boot.img for oreo because you can not modify the boot.img on a locked bootloader. Systemless root like on S7 will not work unless we have an eng boot.img with security set to 0 like the s7 has, so that scripts can execute at time of boot to allow a systemless type of supersu to run. I personally would not expect root anytime soon as if you look back at whats been released for combo firmware it only seems to be firmware for the original software that came on the phone. They just update the bootloaders to match the version number so that you can still flash the nougat combo firmware, but I doubt we see oreo combo firmware. It just has not happened on earlier models. The S7 has been lucky that eng boot.img have been released for nougat but the s8 would require also eng bootloaders to be released as you simply cant flash an eng boot.img on regular bootloaders like you can on the s7. There is always hope but in this case it is really dim but we do have some options with safestrap and modded system images but this part could come to an end at anytime if samsung patches the samfail method so enjoy what you have for now"
I have a rooted debloated S8+ (SM-G955U) and I've been looking for custom ROMS for days now and all I could find was the G95XF or whatever that is. And I'm tempted just to throw it on my phone and try but I'm too scarred to do it. I'd really like literally any custom ROM because that's kind of the entire reason I rooted my phone so I'm just a tad aggregated as well. I don't see any progress with the ROMS either I've been searching all over XDA and on youtube. But yet nothing. If anyone finds anything do you think you could msg me? Somehow?
Ryan8675309 said:
I have a rooted debloated S8+ (SM-G955U) and I've been looking for custom ROMS for days now and all I could find was the G95XF or whatever that is. And I'm tempted just to throw it on my phone and try but I'm too scarred to do it. I'd really like literally any custom ROM because that's kind of the entire reason I rooted my phone so I'm just a tad aggregated as well. I don't see any progress with the ROMS either I've been searching all over XDA and on youtube. But yet nothing. If anyone finds anything do you think you could msg me? Somehow?
Click to expand...
Click to collapse
there is only one rooted rom for 950/5 u do not flash f stuff on your phone not only will it fail in odin but if by some weird act of craziness and worked you would be probably near hardbricked
ghxstt said:
But seriously.. why aren't there any 8.0 ROMs or root methods that actually work? Every method I've seen requires you to downgrade. I know Oreo only came out last month but there are some seriously talented people here on XDA and the fact that I had to downgrade just to have to reflash in about a month or twos time is frustrating to say the least. But, that's just venting and off-topic.
Click to expand...
Click to collapse
There actually is a form of root for Oreo but it's not exactly root because you only have access to r/w in recovery/safestrap
https://forum.xda-developers.com/verizon-galaxy-s8+/development/rom-t3771206/page1
Ryan8675309 said:
I have a rooted debloated S8+ (SM-G955U) and I've been looking for custom ROMS for days now and all I could find was the G95XF or whatever that is. And I'm tempted just to throw it on my phone and try but I'm too scarred to do it. I'd really like literally any custom ROM because that's kind of the entire reason I rooted my phone so I'm just a tad aggregated as well. I don't see any progress with the ROMS either I've been searching all over XDA and on youtube. But yet nothing. If anyone finds anything do you think you could msg me? Somehow?
Click to expand...
Click to collapse
EDIT; I misread your thread. I thought you were saying you had a G95xF device you were going to throw a G95xU ROM on.
If you have a G95xU device, here is what I used to flash my ROM/root https://forum.xda-developers.com/ga...root-partcyborgrom-aqk3-samfail-odin-t3717702.
If you have a G95xF device, I cannot give you any links because I haven't done any research into that firmware.
EDIT 2; My points still stand. Do NOT flash custom ROMs on your phone that aren't for your phone model. You will ruin your phone.
Just don't. It's not worth it.