Shield Kill Switch - Shield Tablet General

Hi figured we could use our own separate thread to discuss the killswitch Nvidia supposedly put in place on our old Shield tablets and see what has worked for those who have received their replacement units. If you've gotten a replacement please share if your old unit has been destroyed or not...if not please let others know what the old tablet has on it or what you did to attempt to prevent the brick! Thanks for helping us all out here!

As I said in the other thread, I received my new one, and my old one is still usable on rooted latest stock, unlocked bootloader, with the only app missing being Chrome for some reason. Nothing else disabled or uninstalled. Maybe they haven't turned on the server that sends the kill signal yet.

If the company wants the other device back (dunno if that is true), why keep it? You are breaking a deal while making it less appeling for companies to do this type of thing...+its a saftey risk for you and others around you.

Nvidia said they do not need it back
ManualG on the Nvidia forum said they are not requiring you send it back
"We don't require you to send it back to us to receive the replacement and are collecting them only to make it less of a burden on everyone else who dont have drop off locations like that close by." So you can keep it if you want ?

16 gig tablet, got it this morning. My original is still functional, it was stock rom, rooted with xposed on it. That's as much modding as I've done with mine.

does anyone have more informations about this killswitch?
Is it a service that needs to be deactivated or deleted or a kernel feature?
I just want to make sure it doesn't kill my old tablet when I set up the new one.
Alternatively, I could just flash an older factory image or custom firmware.

From what I've read on other forums (i.e. reddit) most have indicated that the killswitch is embedded in the bootloader and will activated on the defective tablet once the replacement tablet is registered on the nvidia side. I of course cannot confirm for this to be the case but just sharing what others have reported.

yea but it must communicate with the server then and that only works when Android is booted up and all communication drivers loaded.
So there must be another service running in Android that gives this information to the bootloader to kill itself.

If it's bootloader based, flash a bootloader from one of the older recovery images.

Will try that. BL from Update 2.2.2 should be fine?
actually if I flash it back to 2.2.2 it should be fine too since the changes to 3.X aren't that big

That should work just fine.

big time noob question but where are you getting the old bootloaders from to flash?

Until somebody's tablet gets deactivated and a log is captured during the deactivation process, everything said here or anywhere else is just speculation.

bluegizmo83 is right, however the discussion has to start somewhere so kudos to the OP for getting this thread started.

chicodelta said:
bluegizmo83 is right, however the discussion has to start somewhere so kudos to the OP for getting this thread started.
Click to expand...
Click to collapse
Oh I completely agree. I'm all for conversion. But I don't want people to get the wrong impression, like trying to flash an older bootloader. That may stop the deactivation, but it also may not. Its only speculation at this point.

bluegizmo83 said:
Oh I completely agree. I'm all for conversion. But I don't want people to get the wrong impression, like trying to flash an older bootloader. That may stop the deactivation, but it also may not. Its only speculation at this point.
Click to expand...
Click to collapse
Well said. I apologize if my post came through as a solution. I was only mentioning that as folks had mentioned a possible bootloader lock.

Any thoughts on whether flashing CM would serve as a way to circumvent the killswitch? I see that release for this tablet is already available http://forum.xda-developers.com/shi...-cyanogenmod-12-shield-tablet-lte-na-t3055043. Thoughts?

scorpionx said:
Well said. I apologize if my post came through as a solution. I was only mentioning that as folks had mentioned a possible bootloader lock.
Click to expand...
Click to collapse
No problem. As I said, I'm all for the discussion, I just wanted to make it clear to everyone that its all just speculation at this point.

I think the old bootloaders are in the old full OTA's someone correct me if I'm wrong. You can also extract them from the full OTA

chicodelta said:
Any thoughts on whether flashing CM would serve as a way to circumvent the killswitch? I see that release for this tablet is already available http://forum.xda-developers.com/shi...-cyanogenmod-12-shield-tablet-lte-na-t3055043. Thoughts?
Click to expand...
Click to collapse
To me, this is the most logical place to start at this point! Maybe it works, maybe it doesn't, but unlocking the bootloader, rooting, and installing a custom rom seem like a good starting place. If the stock devices are definitely getting wiped anyways, any changes we make now can't hurt the chances of keeping it alive!

Related

Simple Un-Root!

Un-root And update download the file from here: http://forum.xda-developers.com/showthread.php?t=975888 and apply. This will give you stock and S-on.
That simple!
Thanks for the info, but the fun is just beginning. This is always good to have just in case you have to return it.
You should be able to load any stock RUU. As long as the hboot and the recovery exist in the RUU, it should return you to a stock condition.
Jaywan, how about a simple root and s-off?
It's simple to make a app run the commands needed to make a one click rooter. And easier to edit a already working rooter to work for this phone. Idk why he don't want the one click released. Took me 30 minutes to root.. maybe he only want people to root using his method. I not gonna step on his toes by posting one tho...
Sent from my ADR6400L using XDA Premium App
ok ok, I hear yah. I will just bite the bullet and type in all 90 of the commands tomorrow when I get off work.
BTW, I left the MT4G and came over to verizon also. I went to the SGS4G before I left tmobile. Lack of dev support for that phone made me give it up. Thanks for coming over to the Thunderbolt.
also, take a look at this thread I started. Somethings up with this one click unroot deal.
http://forum.xda-developers.com/showthread.php?t=1004567
Jaywan said:
It's simple to make a app run the commands needed to make a one click rooter. And easier to edit a already working rooter to work for this phone. Idk why he don't want the one click released. Took me 30 minutes to root.. maybe he only want people to root using his method. I not gonna step on his toes by posting one tho...
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
I heard him meantion he wants people to learn adb so if something happens further down the line they can use it
Seriously I'm with him, the hardest part about adb for me was getting it installed. The root was easy and took 30 min
sent from my Thunderbolt
For what its worth, he said feel free to post the one clicks, just give credit. I dont honestly care however, copy, paste, seemed simple enough. Was no where near as hard as the original root method for the DInc.
Sent from my ADR6400L using XDA App
The only legitimate reason I could buy about not wanting a one click released, is if SOMEHOW it would make our phones vulnerable to some sort if attack.
As background, I've ben using custom roms since my old g1 was new and JesusFreke was just getting started and I dont ever recall ANY dev with holding something that would make the users lives easier. In recent history I've done a ton of flashing roms with both mine and my wifes old vibrants and the only time I used adb was if I wanted to push a file to the phone without mounting it on my computer.
PERSONALLY, this whole mess sounds of ego and elitism. I am incredibly greatful to the devs who have paved the way, but fearful of what they are trying to do. No one should have the right to prevent another from releasing something, it's in gross violation of the gpl. If a dev wants to code something under a different license, fine. However it needs to be clearly annotated as such, and devoid of any gpl work itself. In other words, it basically can't contain anything related to android unless it was developed 100% blind through an emulator.
Sent from my ADR6400L using Tapatalk
Can't step on my toes, I got stealtoe boots...
I want a chance to review any one clicks before release. I REALLY want new users to understand what they are doing BEFORE they try one clicking.
I want proper md5sum verifications, I want proper warnings, etc.
I already stopped the release (until fixed) of one 1click root that would of been REALLY bad for the community and anyone using it.
Ppl need to stop blaming me for this crud.
ShanDestromp said:
The only legitimate reason I could buy about not wanting a one click released, is if SOMEHOW it would make our phones vulnerable to some sort if attack.
As background, I've ben using custom roms since my old g1 was new and JesusFreke was just getting started and I dont ever recall ANY dev with holding something that would make the users lives easier. In recent history I've done a ton of flashing roms with both mine and my wifes old vibrants and the only time I used adb was if I wanted to push a file to the phone without mounting it on my computer.
PERSONALLY, this whole mess sounds of ego and elitism. I am incredibly greatful to the devs who have paved the way, but fearful of what they are trying to do. No one should have the right to prevent another from releasing something, it's in gross violation of the gpl. If a dev wants to code something under a different license, fine. However it needs to be clearly annotated as such, and devoid of any gpl work itself. In other words, it basically can't contain anything related to android unless it was developed 100% blind through an emulator.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
Are you a troll or do you really believe all that crock you just posted?
The issue with one clicks was an increased risk of bricking with this method. And where does the GPL even come in here at, any GPL code we used as released before the root was even up.?
I stopped a one click from being released today that not only left your phone vulnerable to an attack, but also left you with an outdated, faulty radio and other faulty firmware.
Either you are a troll, have a personal issue with me, or have a seriously problem.
jcase said:
Can't step on my toes, I got stealtoe boots...
I want a chance to review any one clicks before release. I REALLY want new users to understand what they are doing BEFORE they try one clicking.
I want proper md5sum verifications, I want proper warnings, etc.
I already stopped the release (until fixed) of one 1click root that would of been REALLY bad for the community and anyone using it.
Ppl need to stop blaming me for this crud.
Click to expand...
Click to collapse
omfg most of us been rooting since g1 came out THE FIRST DAY come on if modaco was working on this aka paul. like his app visionary he would have it out.... who cares most of us know adb... but i dont want to turn s off i just want root access to remove **** and do a couple mods. why is this such a big fuc88ing deal just release the app and we will all be grateful of who release one click root
jesemalave1 said:
omfg most of us been rooting since g1 came out THE FIRST DAY come on if modaco was working on this aka paul. like his app visionary he would have it out.... who cares most of us know adb... but i dont want to turn s off i just want root access to remove **** and do a couple mods. why is this such a big fuc88ing deal just release the app and we will all be grateful of who release one click root
Click to expand...
Click to collapse
o.m.g.
Dude it doesn't work that way on this phone. It is not the G1, z4/visionary/anyonphoneroot does not work, root REQUIRES adb (even with one click).
Fact is, you can't root this phone, temp or perm, one click or not, without ad.
If you can find a way, please do. We are awaiting your one click, root that does not use adb, and is not dangerous.
fyi one click has been released, hours before your post.
Code:
while (true) {
facepalm();
}
I'm going to cut out all your attacks, because you've clearly missed my point in its entirety and decided to get defensive.
jcase said:
The issue with one clicks was an increased risk of bricking with this method. And where does the GPL even come in here at, any GPL code we used as released before the root was even up.?
Click to expand...
Click to collapse
I brought the GPL in because like it or not, you don't have the right to say who can and cannot release anything regarding "one click" roots UNLESS you yourself made an essential piece of the current rooting method, that is in its entirety your own. To make an analogy, you can't patent (and thus control the distribution) to a Toyota Carolla, simply because you assembled the whole thing from spare parts. If you were to completely design and fabricate a motor vehicle without using off-the-shelf parts you WOULD have that right.
There is nothing personal in my view of this against you, I don't hold any grudges against anyone; but its the mentality here that irritates me, and it just happens that you're the one that posted it:
jcase said:
I want a chance to review any one clicks before release. I REALLY want new users to understand what they are doing BEFORE they try one clicking.
Click to expand...
Click to collapse
I understand you want people to learn; I really do. I've done enough work with computers that I too get really irritated at people who demand answers to questions answered much faster by doing a quick search. I also understand why you want to avoid screw ups because of a poorly made one click. HOWEVER, just because you WANT people to get them cleared through you first; does not mean they HAVE to or that you have a right to demand that they do.
jcase said:
I stopped a one click from being released today that not only left your phone vulnerable to an attack, but also left you with an outdated, faulty radio and other faulty firmware.
Click to expand...
Click to collapse
And thus you've found the wonder of open source software. Sometimes crap gets released. But guess what? Every one of us here are supposed to be adults, or at the very least the authorized users of our phones; which means that if we screw something up, or use something that screws up; its our own damn fault.
The whole purpose of OSS is to allow freedom of ideas and development. I don't know how old you are, or what your experience with OSS outside of Android phones are; but I personally have seen PLENTY of OSS software that started out as utter crap, turn into wonderful software packages. Maybe you're old enough to remember KDE2 vs KDE4, or how about pre v1 Mozilla vs modern versions of Firefox.
I'm not some OSS nutter; I've got no problem with closed source or proprietary software; just a problem with others trying to control things they have no right to.
All that having been said, maybe you DO hold software rights related to some piece of the current rooting method. If so I've seen nothing indicating so, nor anything indicating that any part of the rooting method is not OSS; however if you DO, then you have my apologies, as you would indeed have control over distribution of that specific piece. You still would not be able to prevent distribution of any one click that were released provided they simply had users download your piece separately.
You are missing the point, and obviously did not read anything. This will be my last time wasting time with you until then.
I never said THEY CANT release, I asked them not to, until we had a safer way and time to check it out. Big difference. I stopped one from going out today that would of more or less ruined phones until someone fixed them.
Fact is, MOST of the one clicks I have seen lately, violate the GPL, why don't you go after them, or hell even better we could really use you to go after HTC (in all seriousness).
ShanDestromp said:
I'm going to cut out all your attacks, because you've clearly missed my point in its entirety and decided to get defensive.
I brought the GPL in because like it or not, you don't have the right to say who can and cannot release anything regarding "one click" roots UNLESS you yourself made an essential piece of the current rooting method, that is in its entirety your own. To make an analogy, you can't patent (and thus control the distribution) to a Toyota Carolla, simply because you assembled the whole thing from spare parts. If you were to completely design and fabricate a motor vehicle without using off-the-shelf parts you WOULD have that right.
There is nothing personal in my view of this against you, I don't hold any grudges against anyone; but its the mentality here that irritates me, and it just happens that you're the one that posted it:
I understand you want people to learn; I really do. I've done enough work with computers that I too get really irritated at people who demand answers to questions answered much faster by doing a quick search. I also understand why you want to avoid screw ups because of a poorly made one click. HOWEVER, just because you WANT people to get them cleared through you first; does not mean they HAVE to or that you have a right to demand that they do.
And thus you've found the wonder of open source software. Sometimes crap gets released. But guess what? Every one of us here are supposed to be adults, or at the very least the authorized users of our phones; which means that if we screw something up, or use something that screws up; its our own damn fault.
The whole purpose of OSS is to allow freedom of ideas and development. I don't know how old you are, or what your experience with OSS outside of Android phones are; but I personally have seen PLENTY of OSS software that started out as utter crap, turn into wonderful software packages. Maybe you're old enough to remember KDE2 vs KDE4, or how about pre v1 Mozilla vs modern versions of Firefox.
I'm not some OSS nutter; I've got no problem with closed source or proprietary software; just a problem with others trying to control things they have no right to.
All that having been said, maybe you DO hold software rights related to some piece of the current rooting method. If so I've seen nothing indicating so, nor anything indicating that any part of the rooting method is not OSS; however if you DO, then you have my apologies, as you would indeed have control over distribution of that specific piece. You still would not be able to prevent distribution of any one click that were released provided they simply had users download your piece separately.
Click to expand...
Click to collapse
I agree!! If anyone is in violation of GPL license it is HTC.
And once we have that kernel source in the hands of the community amazing things will happen!!
Once the custom kernels start flying you will see the TB doing crazy things. I can only imagine 2GHz speeds or insanely efficient battery life (to name a few)!
ShanDestromp says "And thus you've found the wonder of open source software. Sometimes crap gets released. But guess what? Every one of us here are supposed to be adults, or at the very least the authorized users of our phones; which means that if we screw something up, or use something that screws up; its our own damn fault. "
This has got to be the stupidest statement I have read in a long time, I can guarantee, If you used a 1-click method and it bricked your phone you would be screaming " where's the oversight in this forum, I cant' believe that that mods would allow faulty programming to be posted."
Jcase I for one am glad you are stepping up and doing what needs to be done to prevent a potential $750 brick, thank you sir.
jcase said:
I never said THEY CANT release, I asked them not to, until we had a safer way and time to check it out. Big difference. I stopped one from going out today that would of more or less ruined phones until someone fixed them.
Click to expand...
Click to collapse
I'm not privy to any private conversations, nor do I read every thread here on XDA, so my general impression, which I'm sure is shared based upon what others have said, was of a more explicit "No you cannot," not a "do you mind if I take a peek first". Furthermore, I did not name any one individual "responsible" for any blockade; I only began to interact with you once you brought yourself into the thread. Beyond that, if you go back to my original post, I explicitly thank the people who made root possible at all.
jcase said:
Fact is, MOST of the one clicks I have seen lately, violate the GPL, why don't you go after them
Click to expand...
Click to collapse
For starters I don't know much, if anything about them other than they exist. Unless I personally see something that I think is in violation, I assume good faith. I certainly don't seeking violations.
jcase said:
or hell even better we could really use you to go after HTC (in all seriousness).
Click to expand...
Click to collapse
I'm guessing you're referring to the fact that they didn't release the kernel source as expected this week? I'd mentioned it in another thread, though I don't recall which anymore; but from what I recall of GPLv2 developers have 60 days from the "official" binary release to provide source. To expand on that, HTC has 60 days from when the phone officially went on sale, to provide upon request the source code to any GPL licensed software, however it is version specific. That is to say 60 days from March 17th to make available the source to the firmware that was on the phone when released (since to the best of my knowledge there have been no other OFFICIAL firmware versions released).
Of course any such source will inherently exclude any third party proprietary software, for example if HTC used a closed-source bluetooth stack (not saying they did, just a hypothetical example). Additionally, there isn't any specific method to release stipulated. If HTC wishes they could mail out copies of the source on 3.5" floppies and still be within the rules; and all this assumes GPLv2 is how Android is licensed. If its v3 then I honestly have no clue if any time provisions exist.
I just want to reiterate, I have no ill-will to you nor anyone else. It appears as though the whole issue stems from miscommunication.

New Release end of July

I've been in close contact via email with Acer and reporting all the problems and so on.
And now the latest email I got was saying they are not sure about the exact date of release but that it will definately be in the end of july. But they did not state what issues they would fix.
Just sharing some info.
Cheers!
Thanks for sharing.
the information my contact gave me was very blurry...
something about 3.2 and A100.
also about the Iconia Smart
Thanks to the Senior Members
Thanks to the senior members from a newbie for staying on top of 3.1 release of honeycomb for the A500. It's very fustrating not knowing when the release is coming out and not getting squat from Acer for information. I've only had my Iconia for 6 weeks and I'm holding out paying any money for Apps or rooting my tablet until the new version comes out but my patience is wearing out. Do you think that's the right strategy.
Why hold out on buying apps? Anything you buy now isn't going to suddenly stop working with 3.1...
Same goes for rooting, really. It's an easy process to undo, and 3.1 is already out and rooted, there's just an unconfirmed rumour that it has been temporarily withdrawn.
And besides that, even after a hard reset you can still download your previously bought apps without having to pay for them again. Google knows how to remember what you bought
And you need to root to create a system backup. My device for example updated to a "dud" - a firmware that was withdrawn and couldn't update further. Had to flash the right update.zip upgrade to be able to get 3.1.
Bec07 said:
And you need to root to create a system backup. My device for example updated to a "dud" - a firmware that was withdrawn and couldn't update further. Had to flash the right update.zip upgrade to be able to get 3.1.
Click to expand...
Click to collapse
I think it's the same case for me. I had a nandroid backup of my official firmware before going custom. Sad to say, it seems that the OTA update I had was a dud like yours. It updated to Acer_A500_1.126.03_COM_GEN1 and I was unable to get any updates.
Constant negative responnses
FloatingFatMan said:
Why hold out on buying apps? Anything you buy now isn't going to suddenly stop working with 3.1...
Same goes for rooting, really. It's an easy process to undo, and 3.1 is already out and rooted, there's just an unconfirmed rumour that it has been temporarily withdrawn.
Click to expand...
Click to collapse
Really.. uncomfirmed rumour that t has been temporarily withdrawn? Is that why I can no longer get it? I read your posts and so often they flame.. Just like the rumour of global warming right?
lanisan said:
Really.. uncomfirmed rumour that t has been temporarily withdrawn? Is that why I can no longer get it? I read your posts and so often they flame.. Just like the rumour of global warming right?
Click to expand...
Click to collapse
Huh? What the f--- are you talking about? I'm not flaming anyone, just telling the OP there's zero need to wait regarding buying apps from the market.
Get back under your bridge, troll.
Im thinking Acer is trying to conserve resources. Instead of working thruball the bugs are waiting for Google's release.then making there adjustments. And pushing big releases instead of a bunch of minor releases.and I think it might be best for everyone in the long run.less fragmentation with all the small updates
Again my openion only
So, basically, August.
I predict I'll get my update the 2nd week of - or later.
My Iconia updated without issue on the 9th. And aside from doing the double restet button to fix wifi, I've been enjoying all the new features and speed (the screen scrolling/swiping finally matches the rest and pricier other HC tablets).
As for the end of July date you posted, I think it might be HC 3.2 after reading this-
http://gizmodo.com/5820527/your-android-tablet-just-got-better-whats-new-in-android-32
jacobras said:
And besides that, even after a hard reset you can still download your previously bought apps without having to pay for them again. Google knows how to remember what you bought
Click to expand...
Click to collapse
awesome.. I did not know that. Since we're on the subject of buying Apps I read on another post that some clown took apps and added some malware and a root kit to hack your system. I guess he got caught when someone noticed the new version wasn't being sold by the original developer or something like that. Anyway since I'm not that saavy yet is there a way to make sure I'm buying something that's clean.
FloatingFatMan said:
Why hold out on buying apps? Anything you buy now isn't going to suddenly stop working with 3.1...
Same goes for rooting, really. It's an easy process to undo, and 3.1 is already out and rooted, there's just an unconfirmed rumour that it has been temporarily withdrawn.
Click to expand...
Click to collapse
Alrighty then... I guess I'll go back to the threads on rooting and give it a shot. Since I've got some droid heads here I can ask another dumb question. Once I root this puppy is there a way to get a terminal window to run some linux-like commands or am I out to lunch on that
paulmceh said:
Alrighty then... I guess I'll go back to the threads on rooting and give it a shot. Since I've got some droid heads here I can ask another dumb question. Once I root this puppy is there a way to get a terminal window to run some linux-like commands or am I out to lunch on that
Click to expand...
Click to collapse
Terminal emulator, I think that's it...In the market.
I've a question, do providers have to get extra bandwidth to push out updates, and could that be a factor why some of them might do it in batches so they don't have to pay up for extra bandwidth? Acer reps saying that the update may arrive in a week or two doesn't make sense when some have received their updates already even two successive builds in some cases :/

motorola razr M prototype?

hi everyone, so i recently saw motorola razr m. the thing is, it had motorola markings on it like it is some kind of prototype or test device. it was running jellybean. just the markings were a bit curious, if someone can shed some light on what it was. thanks !
mikeverne said:
hi everyone, so i recently bought a second hand motorola razr m. the thing is, it has motorola markings on it like it is some kind of prototype or test device. it works totally fine, gsm unlocked and its running jellybean. everything runs as it should, just the markings are a bit curious. ive attached a pic to see if someone can shed some light on what it is. thanks !
Click to expand...
Click to collapse
Seems kinda fishy lol
https://forums.motorola.com/posts/0dc68e3f0d?commentId=716757#716757
Somber73 said:
Seems kinda fishy lol
https://forums.motorola.com/posts/0dc68e3f0d?commentId=716757#716757
Click to expand...
Click to collapse
yea i saw that too. but that doesn't really tell me anything apart from the fact that other phones like mine were also sold(which i already knew).
It would be best to just drop the subject. You have something rare, and if you want to keep it, I would keep it quiet. The guys on the Motorola forum are launching a pretty big investigation into this. I would delete your pic and edit your OP. Don't get me wrong, I DO NOT condone illegal activity, but there is a reason these are out in the open...
Regardless of the circumstances surrounding where or how he got the phone, there ought to be someplace where this guy can get answers as to its origin or what it is exactly without everybody overreacting.
Sent from my XT907 using xda app-developers app
It is an Engineering model device and it will have a fully unlocked bootloader Status 1 when you boot into AP Fastboot mode from the boot menu.
It will also have engineering firmware with userdebug testkeys builds unless it was flashed by prior owner to stock or a custom build.
These are very valuable devices to a developer because they can run any firmware, including the engineering bootloaders and radio images, which cannot be run even on devices with unlocked bootloaders via exploit or the official Development edition devices, all of which have a Status 3 bootloader.
The good news is you can run any firmware you like safely on them, but you must flash them manually and you can't run any OTA updates until you do so because they will fail signatures and checksums on engineering builds.
There is also usually a lot of debugging binaries and apps and monitoring components on these builds that you want to disable generally.
It's a great opportunity, but comes with some greater responsibility.
The official forum, as noted above, is an extremely poor place to get this kind of information and is basically useless, as you discovered.
More of these devices have been showing up lately and I have seen several posts by confused users like yourself regarding such phones.
Consider yourself lucky and start learning how to take advantage of your rare device!
It would seem, especially from the reaction by Motorola, that it is indeed an internal phone. I'm guessing they want the IMEI so they can take someone's head off.
I doubt Motorola would go after any end users, they didn't seem too mad at the guy who posted there. Someone inside will probably not be happy after that investigation though
Sent from my XT907 using Tapatalk 4 Beta
cellzealot said:
It is an Engineering model device and it will have a fully unlocked bootloader Status 1 when you boot into AP Fastboot mode from the boot menu.
It will also have engineering firmware with userdebug testkeys builds unless it was flashed by prior owner to stock or a custom build.
These are very valuable devices to a developer because they can run any firmware, including the engineering bootloaders and radio images, which cannot be run even on devices with unlocked bootloaders via exploit or the official Development edition devices, all of which have a Status 3 bootloader.
The good news is you can run any firmware you like safely on them, but you must flash them manually and you can't run any OTA updates until you do so because they will fail signatures and checksums on engineering builds.
There is also usually a lot of debugging binaries and apps and monitoring components on these builds that you want to disable generally.
It's a great opportunity, but comes with some greater responsibility.
The official forum, as noted above, is an extremely poor place to get this kind of information and is basically useless, as you discovered.
More of these devices have been showing up lately and I have seen several posts by confused users like yourself regarding such phones.
Consider yourself lucky and start learning how to take advantage of your rare device!
Click to expand...
Click to collapse
thank you! and btw, that wasn't me who posted in the official forums lol. thats the lase place i would think of posting if i had a prototype haha.
sloosecannon said:
It would seem, especially from the reaction by Motorola, that it is indeed an internal phone. I'm guessing they want the IMEI so they can take someone's head off.
I doubt Motorola would go after any end users, they didn't seem too mad at the guy who posted there. Someone inside will probably not be happy after that investigation though
Sent from my XT907 using Tapatalk 4 Beta
Click to expand...
Click to collapse
thank you! and yea, i agree.
that convo on the motorola forum is hilarious!
buyer claimed he got it from someone he does not know that placed an ad on pakistani forum.
jco23 said:
that convo on the motorola forum is hilarious!
buyer claimed he got it from someone he does not know that placed an ad on pakistani forum.
Click to expand...
Click to collapse
uh, actually im pretty sure he is telling the truth. its sort of a Pakistani craigslist.
RSD is proprietary software, owned by Motorola. While I know it's very easy to find online, it's not intended for public use. The rules of this site forbid discussion of software installation or use unless that software is distributed by Motorola or one of its partners.
That pretty much sums it up. Had he come to xda, he'd have gotten help. He didn't seem too open to helping the Motorola guys out though, so they didn't help him. Don't see why he would lie about that, he's just a poor guy who wants his confidential Motorola property to work for him... By asking the people that someone stole it from... Yeah...
Sent from my XT907 using Tapatalk 4 Beta
guys, i am going to buy a similar "confidential" razr m phone. what do you suggest? is this going to cause software issues like installing new roms or gapps?
dasche said:
guys, i am going to buy a similar "confidential" razr m phone. what do you suggest? is this going to cause software issues like installing new roms or gapps?
Click to expand...
Click to collapse
Nope. Since it's factory unlocked, you should be able to install TWRP and go about flashing whatever you want. It might be a wiser choice to buy a regular handset, since you want have Motorola property all over the front.

New to XDA, ETA on custom Roms for MF3?

I understand it will be out when its out, but I just migrated from iOS and I would always see postings from certain sites on when the next Jailbreak is coming. I am getting used to Android and I was wondering if anyone has heard anything and if not is this the best place to follow to find out?
There are already mf3 based roms...check the development section
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
milkeeway said:
I understand it will be out when its out, but I just migrated from iOS and I would always see postings from certain sites on when the next Jailbreak is coming. I am getting used to Android and I was wondering if anyone has heard anything and if not is this the best place to follow to find out?
Click to expand...
Click to collapse
If you are on the AT&T S4 that has been updated to MF3 we will have to wait until a bootloader exploit is found. There is NO ETA for this and it may take a while... maybe never. Just keep an eye on one of our many bootloader threads and pledge to pay the dev if you want to help motivate.
If you are on a custom rom and waiting for more keep an eye on the development section
mg2195 said:
There are already mf3 based roms...check the development section
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
I think the problem is that I purchased my GS4 and it came with MF3 pre-installed. Right now they have MDL Roms with MF3 features in it. Last I checked there was no way to flash custom Roms onto a phone that has MF3 on it!
milkeeway said:
I think the problem is that I purchased my GS4 and it came with MF3 pre-installed. Right now they have MDL Roms with MF3 features in it. Last I checked there was no way to flash custom Roms onto a phone that has MF3 on it!
Click to expand...
Click to collapse
then see my post. Sucks but we are locked down
milkeeway said:
I think the problem is that I purchased my GS4 and it came with MF3 pre-installed. Right now they have MDL Roms with MF3 features in it. Last I checked there was no way to flash custom Roms onto a phone that has MF3 on it!
Click to expand...
Click to collapse
You are correct, there is currently not a way to flash custom roms.
God promised man he'd put beautiful women in all corners of the world. Then he laughed and laughed and made the world round.
joshuadjohnson22 said:
If you are on the AT&T S4 that has been updated to MF3 we will have to wait until a bootloader exploit is found. There is NO ETA for this and it may take a while... maybe never. Just keep an eye on one of our many bootloader threads and pledge to pay the dev if you want to help motivate.
If you are on a custom rom and waiting for more keep an eye on the development section
Click to expand...
Click to collapse
Thanks for that information. That is a bummer to hear the realistic possibility that it may never come. I guess I would be extremely bummed as rooting is the main reason I came to Android and bought the S4. I was naive in the sense I thought all S4 were the same. Little did I know there was so many variations. I even came to the forums before I bought it but everything seemed like a foreign language coming from iOS.
Any idea who I might be able to talk to to Pledge some cash to see that it gets worked on?
And also is there any way to see a MOD about this captcha restriction lol!
milkeeway said:
Thanks for that information. That is a bummer to hear the realistic possibility that it may never come. I guess I would be extremely bummed as rooting is the main reason I came to Android and bought the S4. I was naive in the sense I thought all S4 were the same. Little did I know there was so many variations. I even came to the forums before I bought it but everything seemed like a foreign language coming from iOS.
Any idea who I might be able to talk to to Pledge some cash to see that it gets worked on?
And also is there any way to see a MOD about this captcha restriction lol!
Click to expand...
Click to collapse
Now rooting is available, but this thread is to pledge http://forum.xda-developers.com/showthread.php?t=2361870
You can always just buy the tmobile version, they don't have a locked bootloader so you can flash away. Just a thought
joshuadjohnson22 said:
Now rooting is available, but this thread is to pledge http://forum.xda-developers.com/showthread.php?t=2361870
You can always just buy the tmobile version, they don't have a locked bootloader so you can flash away. Just a thought
Click to expand...
Click to collapse
Thanks for all that info. I am an idiot honestly that's all that can be said. I should have done a little more research before I made a purchase. I traded my iPhone 5 with a little cash on top for a brand new Galaxy S4 on AT&T (My carrier) had I known all of this before I would have searched Craigslist for a T-Mobile version and then sim unlocked it for AT&T...
Guess I learned my lesson, I really wish I could afford to go buy a T-Mobile S4 too but they sell for like $500-$600 out of contract.... Just can't do it and I am stuck with AT&T right now. Meanwhile my buddy who told me I should buy an S4 is laughing his rooted and recovered ass off right now lol...
Good to hear rooting is available
soccer_rm said:
Good to hear rooting is available
Click to expand...
Click to collapse
What can you do with a root if you are not able to install custom roms?
Is there anything I could do in the meantime that would improve the functionality or performance of my phone?
milkeeway said:
What can you do with a root if you are not able to install custom roms?
Is there anything I could do in the meantime that would improve the functionality or performance of my phone?
Click to expand...
Click to collapse
You can install a lot of mods which will archive a lot of the same things as a custom rom. You can remove bloat, theme, add things... it is pretty awesome. See the development sections and the themes and app sections to see all the awesome stuff. Some people always stay with stock and just add mods
milkeeway said:
What can you do with a root if you are not able to install custom roms?
Is there anything I could do in the meantime that would improve the functionality or performance of my phone?
Click to expand...
Click to collapse
joshuadjohnson22 said:
You can install a lot of mods which will archive a lot of the same things as a custom rom. You can remove bloat, theme, add things... it is pretty awesome. See the development sections and the themes and app sections to see all the awesome stuff. Some people always stay with stock and just add mods
Click to expand...
Click to collapse
...you can also do some serious damage, and without recovery, you can easily "Brick" your device... Please be careful what you remove/change/mod, as if you bootloop or fubar your current OS, you will NOT be able to Odin Back to stock to recover just yet...
removing some of the Samsung Apps will break things when they are removed, and TiBU can't always put them back... for now I just froze all the bloatware, and won't remove anything until there is a way to go "Back to Stock"
Hope this helps.
slyguy2000 said:
...you can also do some serious damage, and without recovery, you can easily "Brick" your device... Please be careful what you remove/change/mod, as if you bootloop or fubar your current OS, you will NOT be able to Odin Back to stock to recover just yet...
removing some of the Samsung Apps will break things when they are removed, and TiBU can't always put them back... for now I just froze all the bloatware, and won't remove anything until there is a way to go "Back to Stock"
Hope this helps.
Click to expand...
Click to collapse
Those are very good points! No nandroids either. It's best not to mess with a lot of those areas unless you know what your doing.
God promised man he'd put beautiful women in all corners of the world. Then he laughed and laughed and made the world round.
slyguy2000 said:
...you can also do some serious damage, and without recovery, you can easily "Brick" your device... Please be careful what you remove/change/mod, as if you bootloop or fubar your current OS, you will NOT be able to Odin Back to stock to recover just yet...
removing some of the Samsung Apps will break things when they are removed, and TiBU can't always put them back... for now I just froze all the bloatware, and won't remove anything until there is a way to go "Back to Stock"
Hope this helps.
Click to expand...
Click to collapse
Yeah, thanks for clarifying, I should also let the OP know I have the S4 Active which has the ability to ODIN back to stock if something goes wrong. I do not know if you will have that pleasure so think twice and read before trying anything
I have decided I probably won't take advantage of the root until I can safely make a recovery. I actually posted a $25.00 pledge (I know it isn't much) towards finding a fix for newer users of the S4. People who have to warranty their phones will likely have the update installed.
Crossing my fingers now.
Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
And we do not ask for ETAs on XDA
This would be on hold for awhile until another bootloader fix surfaces, then you will see a whole bunch of MF3 custom roms.
milkeeway said:
I have decided I probably won't take advantage of the root until I can safely make a recovery. I actually posted a $25.00 pledge (I know it isn't much) towards finding a fix for newer users of the S4. People who have to warranty their phones will likely have the update installed. Crossing my fingers now.
Click to expand...
Click to collapse
That's probably a good choice and you can enjoy the S4 i337 without doing anything, it is a great phone.
Of course, rooting -basic rooting using the new technique for the MF3 rom-- seems to work well enough for many so far. So please don't view it as jumping off a cliff and hoping to find a vine on the way down or something so bleak.
For your model, which does not currently have as many recovery options as the earlier MDL versions, it certainly pays to be careful and also to understand your options for return or exchange if you do muck up the phone. The trick is to understand the specific risks up front. In this case, what can go wrong in the rooting process and how often does it seem to occur.
Read the XDA thread on this new rooting exploit for MF3 and see exactly what others did to get root without ruining their phone -and do only and exactly the steps that have worked for others. The rooting process takes only a couple of minutes --but so does bricking your phone when it rooting is done incorrectly.
The differences between success and failure are:
1. How much you understand of the procedure?
2. How much you have prepared in advance for what you are doing and trying to accomplish? and
3. How carefully and patiently are you doing each and every step of the process?
I've rooted several phones and tablets and been fortunate to get it right most of the time, or to be able to recover when I did not get it right. Unfortunately, in your case it appears that you need to get it right the first time for rooting, and many many folks have. So while this is very different from the iPhone "click on this site and you're jailbroken" approach, it is not low-percentage surgery either :good::good::fingers-crossed: So, I'd recommend that you continue to read up on that new root technique for MF3:
-- read to see how it is being accepted, what kind of feedback folks have and also
-- how safe/or comfortable folks seem to be in using it. and
-- what problems have come from trying it -bricks? soft bricks? recoverable or not?
I've read the original post (OP) on the exploit, but not all the information is in the one thread.. I am sure there are several threads that echo this development. . . Might have even more information too. After, that you will know if you want to try the rooting step. Or not.
Good Luck!
P.S.
- While root does not sound as valuable as being able to switch roms and use full customizations, it does provide quite a bit. For example: you can add (root-requiring) apps like "Titanium Backup" (which not only backsup all of your programs and data, but also can "freeze" programs that are useless and running in the background when you don't want them to do so!) Or Greenify, which has the same functionality for dealing with unwanted apps (better actually!) and apps like Cerberus to help you keep track of your phone or find it if lost.
- Rooting to add these types of add ons, without fiddling with some of the more invasive mods that others have already warned about in the other posts, may be acceptable middle ground for you -it does provide customizations for your phone without stretching the safe use limits very far.
Take your time. . . keep reading and move at your own pace. It's hard to come here, start reading and simply "get it" on first bounce. . .It's just a shame that your friend with the older S4 didn't provide a couple of hints or tips about which versions to by ("buy the red ones"... :laugh so you could have picked up one that is easily customizable. . .(of course if you are still in the 14 day window you might go back and try to exchange for another one and look for a MDL version -according to some posts they seem to be the red ones that no one wanted to buy early on . . . . hmm
Good Luck!
markbc01 said:
That's probably a good choice and you can enjoy the S4 i337 without doing anything, it is a great phone.
Of course, rooting -basic rooting my upgradeusing the new technique for the MF3 rom-- seems to work well enough for many so far. So please don't view it as jumping off a cliff and hoping to find a vine on the way down or something so bleak.
For your model, which does not currently have as many recovery options as the earlier MDL versions, it certainly pays to be careful and also to understand your options for return or exchange if you do muck up the phone. The trick is to understand the specific risks up front. In this case, what can go wrong in the rooting process and how often does it seem to occur.
Read the XDA thread on this new rooting exploit for MF3 and see exactly what others did to get root without ruining their phone -and do only and exactly the steps that have worked for others. The rooting process takes only a couple of minutes --but so does bricking your phone when it rooting is done incorrectly.
The differences between success and failure are:
1. How much you understand of the procedure?
2. How much you have prepared in advance for what you are doing and trying to accomplish? and
3. How carefully and patiently are you doing each and every step of the process?
I've rooted several phones and tablets and been fortunate to get it right most of the time, or to be able to recover when I did not get it right. Unfortunately, in your case it appears that you need to get it right the first time for rooting, and many many folks have. So while this is very different from the iPhone "click on this site and you're jailbroken" approach, it is not low-percentage surgery either :good::good::fingers-crossed: So, I'd recommend that you continue to read up on that new root technique for MF3:
-- read to see how it is being accepted, what kind of feedback folks have and also
-- how safe/or comfortable folks seem to be in using it. and
-- what problems have come from trying it -bricks? soft bricks? recoverable or not?
I've read the original post (OP) on the exploit, but not all the information is in the one thread.. I am sure there are several threads that echo this development. . . Might have even more information too. After, that you will know if you want to try the rooting step. Or not.
Good Luck!
P.S.
- While root does not sound as valuable as being able to switch roms and use full customizations, it does provide quite a bit. For example: you can add (root-requiring) apps like "Titanium Backup" (which not only backsup all of your programs and data, but also can "freeze" programs that are useless and running in the background when you don't want them to do so!) Or Greenify, which has the same functionality for dealing with unwanted apps (better actually!) and apps like Cerberus to help you keep track of your phone or find it if lost.
- Rooting to add these types of add ons, without fiddling with some of the more invasive mods that others have already warned about in the other posts, may be acceptable middle ground for you -it does provide customizations for your phone without stretching the safe use limits very far.
Take your time. . . keep reading and move at your own pace. It's hard to come here, start reading and simply "get it" on first bounce. . .It's just a shame that your friend with the older S4 didn't provide a couple of hints or tips about which versions to by ("buy the red ones"... :laugh so you could have picked up one that is easily customizable. . .(of course if you are still in the 14 day window you might go back and try to exchange for another one and look for a MDL version -according to some posts they seem to be the red ones that no one wanted to buy early on . . . . hmm
Good Luck!
Click to expand...
Click to collapse
Well my Galaxy S4 on MF3 I actually bought on craigslist so the only exchange options are through the manufacturer. What I ended up doing was going to AT&T and using my upgrade to buy another S4 I just told the sales Representative to look on the side of the box for MDL software version or I was not going to upgrade. He was happy to make the sale. Now I have two s4

[Q] Please Help! New S5 BRICKED!!

1.) Rooted S5 900V (Verizon Model) using towel root.
2.) Installed Safestrap Recovery.
All this went perfectly fine..
I forget exactly which ROM i tried to install but it boot looped my phone.
I need to know which ROMs i can use and which ones that i CANNOT,
Can i only use certain ROMs based off of which recovery i've installed?
What is ADB Side Load?
I want to ask all of these questions, no matter how noobish, so that i can write every single one of these things down in lamens terms for the average (or slightly below average) user.
If we understood what half of these options meant and would do we could do this stuff yourself and leave you guys alone so you can develop stuff for my Verizon S5 !!! lol :laugh:
Not only that, but most of these ROM's come with ZERO instructions on how to install them properly. I mean i understand that if your flashing then you should have an underlying knowledge of what you doing but COME ON!!! BE smart about it. You take all that time to develop a decent ROM but don't but info on how to install it properly. WTF is the deal with that?
Also... Can i use Odin309 within Linux via Wine? I am trying to install the firmware i got from Sam's.
If you have a verizon S5, (SM-G900V) then you can only flash a rom, made by the devs here, for the 900V. If you try to flash a variants S5 rom, your phone will brick.
I always recommend that before somone flashes anything to their phone or tablet to do research on the subject. Read, and reread everything. Double check. Make sure you have everything you need.
Also, pretty much all of the devs have install instructions for their work in our phones dev section.
---------- Post added at 05:04 PM ---------- Previous post was at 04:47 PM ----------
Also about your question about using odin within linux via wine, here are a few threads that aks the same thing.
http://forum.xda-developers.com/showthread.php?p=55539300
http://forum.xda-developers.com/showthread.php?p=55569056
Personally, I'd rather use a Windows PC. Less headaches that way. But thats just my opinion.
warpedmind0u812 said:
If you have a verizon S5, (SM-G900V) then you can only flash a rom, made by the devs here, for the 900V. If you try to flash a variants S5 rom, your phone will brick.
I always recommend that before somone flashes anything to their phone or tablet to do research on the subject. Read, and reread everything. Double check. Make sure you have everything you need.
Also, pretty much all of the devs have install instructions for their work in our phones dev section.
---------- Post added at 05:04 PM ---------- Previous post was at 04:47 PM ----------
Also about your question about using odin within linux via wine, here are a few threads that aks the same thing.
http://forum.xda-developers.com/showthread.php?p=55539300
http://forum.xda-developers.com/showthread.php?p=55569056
Personally, I'd rather use a Windows PC. Less headaches that way. But thats just my opinion.
Click to expand...
Click to collapse
Yes I do read, but somethimes it can be
exitpr0gram said:
1.) Rooted S5 900V (Verizon Model) using towel root.
2.) Installed Safestrap Recovery.
All this went perfectly fine..
I forget exactly which ROM i tried to install but it boot looped my phone.
I need to know which ROMs i can use and which ones that i CANNOT,
You can only use ROMs labeled for the retail Verizon S5. Not spring, tmobile.. etc.. Verizon.
Can i only use certain ROMs based off of which recovery i've installed?
As of now, you can only use safestrap. Any of the current ROMs can be flashed by our current safestrap
What is ADB Side Load?
ADB Sideload
I want to ask all of these questions, no matter how noobish, so that i can write every single one of these things down in lamens terms for the average (or slightly below average) user.
If we understood what half of these options meant and would do we could do this stuff yourself and leave you guys alone so you can develop stuff for my Verizon S5 !!! lol :laugh:
Not only that, but most of these ROM's come with ZERO instructions on how to install them properly. I mean i understand that if your flashing then you should have an underlying knowledge of what you doing but COME ON!!! BE smart about it. You take all that time to develop a decent ROM but don't but info on how to install it properly. WTF is the deal with that?
Most? That's a bit harsh. Last I checked, most (if not all) of the ROM devs (including myself) provide thorough instructions. There is no "WTF deal".
Also... Can i use Odin309 within Linux via Wine? I am trying to install the firmware i got from Sam's.
Simple answer: no. Don't take the risk to your device.
Click to expand...
Click to collapse
Answered your questions above in RED.
exitpr0gram said:
1.) Rooted S5 900V (Verizon Model) using towel root.
2.) Installed Safestrap Recovery.
All this went perfectly fine..
I forget exactly which ROM i tried to install but it boot looped my phone.
I need to know which ROMs i can use and which ones that i CANNOT,
Can i only use certain ROMs based off of which recovery i've installed?
What is ADB Side Load?
I want to ask all of these questions, no matter how noobish, so that i can write every single one of these things down in lamens terms for the average (or slightly below average) user.
If we understood what half of these options meant and would do we could do this stuff yourself and leave you guys alone so you can develop stuff for my Verizon S5 !!! lol :laugh:
Not only that, but most of these ROM's come with ZERO instructions on how to install them properly. I mean i understand that if your flashing then you should have an underlying knowledge of what you doing but COME ON!!! BE smart about it. You take all that time to develop a decent ROM but don't but info on how to install it properly. WTF is the deal with that?
Also... Can i use Odin309 within Linux via Wine? I am trying to install the firmware i got from Sam's.
Click to expand...
Click to collapse
No offense meant, but based on the questions you've asked I suggest you do more research before flashing anything on your phone.
The ROMs listed in this forum have pretty good install instruction for anyone who has a basic knowledge of what they are doing (err go the comment about doing more research).
Did you make a backup before you flashed the ROM you can't even remember the name of? What slot did you flash the ROM to?
It would be helpful if you could tell us what ROM you tried to flash and where you found it.
Always make a backup of your stock rom before flashing anything.
Thanks
BigBot96 said:
Answered your questions above in RED.
Click to expand...
Click to collapse
I guess what i meant to say is that some information is just hard to locate. They keep the fancy art easy to see but the installation instructions you actually have to search for. I love the DEV's for there work, TRUST ME. Android wouldn't be Android without you guys.
I would like to get more involved in the XDA and AndroidForums to make a one stop shop for ALL of the popular devices. Basically, just gather up all pertinent information (after receiving permission from the dev) and put it in one nice and easy spot to read.
exitpr0gram said:
I guess what i meant to say is that some information is just hard to locate. They keep the fancy art easy to see but the installation instructions you actually have to search for. I love the DEV's for there work, TRUST ME. Android wouldn't be Android without you guys.
I would like to get more involved in the XDA and AndroidForums to make a one stop shop for ALL of the popular devices. Basically, just gather up all pertinent information (after receiving permission from the dev) and put it in one nice and easy spot to read.
Click to expand...
Click to collapse
You mean something like this thread which already exists?
http://forum.xda-developers.com/showthread.php?t=2784860
landshark68 said:
You mean something like this thread which already exists?
http://forum.xda-developers.com/showthread.php?t=2784860
Click to expand...
Click to collapse
Yes. That is an excellent example of what i am wanting to do and I actually used it when i started reading up on my S5.The only thing is that it does not specify the Verizon 900V. So someone with any model phone could read that and brick their phone.
But i will want to go in to more detail such as exactly what the "NE9" is.. Is it an update? Firmware? What?
Regardless, i just want to add another page that has information that one that already exists, such as that one, may be missing.
There is WAY too much information about our phones to say that one page covers every single aspect of it.
I'm just wanting to help clearly state the information thats already out there. Alot of these people are already busy and cannot give 110% towards there pages.
exitpr0gram said:
Yes. That is an excellent example of what i am wanting to do and I actually used it when i started reading up on my S5.The only thing is that it does not specify the Verizon 900V. So someone with any model phone could read that and brick their phone.
But i will want to go in to more detail such as exactly what the "NE9" is.. Is it an update? Firmware? What?
Regardless, i just want to add another page that has information that one that already exists, such as that one, may be missing.
There is WAY too much information about our phones to say that one page covers every single aspect of it.
I'm just wanting to help clearly state the information thats already out there. Alot of these people are already busy and cannot give 110% towards there pages.
Click to expand...
Click to collapse
It literally says "How to root Verizon's Samsung Galaxy S5" in the title.
If you feel theres a need for another thread explaining things, talk to a moderator about making one.
warpedmind0u812 said:
It literally says "How to root Verizon's Samsung Galaxy S5" in the title.
If you feel theres a need for another thread explaining things, talk to a moderator about making one.
Click to expand...
Click to collapse
I think we both know that one carriers phone could have compatible root/roms for others carrier's phones. Specifying the model name i would think would be the most appropriate way. You have to realize not everyone has been doing this for as long as you and does not necessarily have a keen eye for such things..
There is absolutely nothing wrong with over explaining things.
With that being said, i do believe that post is an extremely helpful page.
But discussing whether or not the page has enough information is not worth debating over.
When i find time to do my own then we can have this discussion.
I mentioned i wasn't exactly sure how i boot looped my. Still don't because I can't remember for the life of me which ROM it was! I thought i book marked it... Whichever one it was, it wanted me to flash 3-4 different zips once in SafeStrap. First ZIP is when the boot loop occuured.
ANYWAY...
I installed SafeStrap using the instructions found HERE.
I wanted to install THIS ONE because it had the KTweaker which is totally awesome toplay with but i dont think my 900-V allows sit.\\
BUT:
I want as many people's opinion as possible on this (I will create a separate thread). I have T-Mobile but was old a Verizon Phone. I have issues with dropped calls, slow speeds, among others. I want to know if this is legal.
Any and all are welcome to respond as i feel they should pay for making me pay $60 fora cab (Oneway) and then selling me a crap phone. Plus the wall charger didn't work. The data cable did so at least i had another wall charger.
In Case your Wondering... yes i do have the receipt.
THE BEST PART IS: T-Mobile said they've never heard of them when i called and gave them the address off of the receipt.
Honestly, i would like to go in there and walk out with another S5, maybe even with this one paid off, lol. But PLEASE ALL OPINIONS ARE WELCOME.
exitpr0gram said:
I think we both know that one carriers phone could have compatible root/roms for others carrier's phones. Specifying the model name i would think would be the most appropriate way. You have to realize not everyone has been doing this for as long as you and does not necessarily have a keen eye for such things..
There is absolutely nothing wrong with over explaining things.
With that being said, i do believe that post is an extremely helpful page.
But discussing whether or not the page has enough information is not worth debating over.
When i find time to do my own then we can have this discussion.
Click to expand...
Click to collapse
So... Do you actually need help with your phone?
warpedmind0u812 said:
So... Do you actually need help with your phone?
Click to expand...
Click to collapse
I fixed it, thanks.
Sammobile firmware+Odin309+download mode= Magic.
How i Fixed + A 10x More Complicated Question
BigBot96 said:
Answered your questions above in RED.
Click to expand...
Click to collapse
jpcalhoun said:
No offense meant, but based on the questions you've asked I suggest you do more research before flashing anything on your phone.
The ROMs listed in this forum have pretty good install instruction for anyone who has a basic knowledge of what they are doing (err go the comment about doing more research).
Did you make a backup before you flashed the ROM you can't even remember the name of? What slot did you flash the ROM to?
It would be helpful if you could tell us what ROM you tried to flash and where you found it.
Always make a backup of your stock rom before flashing anything.
Click to expand...
Click to collapse
warpedmind0u812 said:
It literally says "How to root Verizon's Samsung Galaxy S5" in the title.
If you feel theres a need for another thread explaining things, talk to a moderator about making one.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2732110
Any Input/Opinions WELCOME!!!!!!!!!!
BigBot96 said:
Answered your questions above in RED.
Click to expand...
Click to collapse
jpcalhoun said:
No offense meant, but based on the questions you've asked I suggest you do more research before flashing anything on your phone.
The ROMs listed in this forum have pretty good install instruction for anyone who has a basic knowledge of what they are doing (err go the comment about doing more research).
Did you make a backup before you flashed the ROM you can't even remember the name of? What slot did you flash the ROM to?
It would be helpful if you could tell us what ROM you tried to flash and where you found it.
Always make a backup of your stock rom before flashing anything.
Click to expand...
Click to collapse
landshark68 said:
You mean something like this thread which already exists?
http://forum.xda-developers.com/showthread.php?t=2784860
Click to expand...
Click to collapse
I mentioned i wasn't exactly sure how i boot looped my. Still don't because I can't remember for the life of me which ROM it was! I thought i book marked it... Whichever one it was, it wanted me to flash 3-4 different zips once in SafeStrap. First ZIP is when the boot loop occuured.
ANYWAY...
I installed SafeStrap using the instructions found HERE.
I wanted to install THIS ONE because it had the KTweaker which is totally awesome toplay with but i dont think my 900-V allows sit.\\
BUT:
I want as many people's opinion as possible on this (I will create a separate thread). I have T-Mobile but was old a Verizon Phone. I have issues with dropped calls, slow speeds, among others. I want to know if this is legal.
Any and all are welcome to respond as i feel they should pay for making me pay $60 fora cab (Oneway) and then selling me a crap phone. Plus the wall charger didn't work. The data cable did so at least i had another wall charger.
In Case your Wondering... yes i do have the receipt.
THE BEST PART IS: T-Mobile said they've never heard of them when i called and gave them the address off of the receipt.
Honestly, i would like to go in there and walk out with another S5, maybe even with this one paid off, lol. But PLEASE ALL OPINIONS ARE WELCOME.
exitpr0gram said:
I mentioned i wasn't exactly sure how i boot looped my. Still don't because I can't remember for the life of me which ROM it was! I thought i book marked it... Whichever one it was, it wanted me to flash 3-4 different zips once in SafeStrap. First ZIP is when the boot loop occuured.
ANYWAY...
I installed SafeStrap using the instructions found HERE.
I wanted to install THIS ONE because it had the KTweaker which is totally awesome toplay with but i dont think my 900-V allows sit.\\
BUT:
I want as many people's opinion as possible on this (I will create a separate thread). I have T-Mobile but was old a Verizon Phone. I have issues with dropped calls, slow speeds, among others. I want to know if this is legal.
Any and all are welcome to respond as i feel they should pay for making me pay $60 fora cab (Oneway) and then selling me a crap phone. Plus the wall charger didn't work. The data cable did so at least i had another wall charger.
In Case your Wondering... yes i do have the receipt.
THE BEST PART IS: T-Mobile said they've never heard of them when i called and gave them the address off of the receipt.
Honestly, i would like to go in there and walk out with another S5, maybe even with this one paid off, lol. But PLEASE ALL OPINIONS ARE WELCOME.
Click to expand...
Click to collapse
You need to seriously stop and do a lot more reading before you try anything else with your phone. The ROM you linked above that you said you want to flash is for the International version of the Galaxy S5 and will hard brick your phone. The forum where that ROM is posted (Samsung Galaxy S5) is for the International version. The US variants of the S5 are broken down by carrier. Hence this is the Verizon Galaxy S5 forum. You bought your phone from some fly-by-night place, and it turned out to be a Verizon variant when you needed a T-Mobile variant.
If you are going to keep the Verizon variant you bought and use it on T-Mobile, you will only get Edge speeds through T-Mobile and never get 4G speeds. It is legal to use a Verizon phone on T-Mobile's network, it just won't work as well as you have already experienced. You need to change the APNs on your phone to get the best performance you can on T-Mobile. But it's still not going to be as good as using the T-Mobile variant on the T-Mobile network. If you went into that store and specifically asked for a T-Mobile Galaxy S5 and they sold you a Verizon variant, they would have a problem. If you went into the store and simply bought the cheapest S5 they had without telling them you needed a T-Mobile variant, then that is completely legal on their part. You don't need to create a separate thread to get everyone's opinions on the legality of your purchase. What I said above pretty much sums it up.
Also, if you are planning on keeping the Verizon variant and want to flash a ROM through safestrap, the ROM you want to flash has to be of the same build as the current build on your phone. So if your S5 is on NHA, you should only flash an NHA based ROM in safestrap. Or if you phone is on NI2, an NI2 based ROM. So letting everyone know which build your phone currently has will help us let you know which ROMs are safe to flash on your phone.
Sorry if all of this comes across as harsh, but I'm trying to help prevent you from turning your phone into a useless paperweight. You seem very confused by a lot of the information found here in the forums, and that is a very good time to slow down, take your time, and make sure you understand what you are doing at every step.
landshark68 said:
You need to seriously stop and do a lot more reading before you try anything else with your phone. The ROM you linked above that you said you want to flash is for the International version of the Galaxy S5 and will hard brick your phone. The forum where that ROM is posted (Samsung Galaxy S5) is for the International version. The US variants of the S5 are broken down by carrier. Hence this is the Verizon Galaxy S5 forum. You bought your phone from some fly-by-night place, and it turned out to be a Verizon variant when you needed a T-Mobile variant.
If you are going to keep the Verizon variant you bought and use it on T-Mobile, you will only get Edge speeds through T-Mobile and never get 4G speeds. It is legal to use a Verizon phone on T-Mobile's network, it just won't work as well as you have already experienced. You need to change the APNs on your phone to get the best performance you can on T-Mobile. But it's still not going to be as good as using the T-Mobile variant on the T-Mobile network. If you went into that store and specifically asked for a T-Mobile Galaxy S5 and they sold you a Verizon variant, they would have a problem. If you went into the store and simply bought the cheapest S5 they had without telling them you needed a T-Mobile variant, then that is completely legal on their part. You don't need to create a separate thread to get everyone's opinions on the legality of your purchase. What I said above pretty much sums it up.
Also, if you are planning on keeping the Verizon variant and want to flash a ROM through safestrap, the ROM you want to flash has to be of the same build as the current build on your phone. So if your S5 is on NHA, you should only flash an NHA based ROM in safestrap. Or if you phone is on NI2, an NI2 based ROM. So letting everyone know which build your phone currently has will help us let you know which ROMs are safe to flash on your phone.
Sorry if all of this comes across as harsh, but I'm trying to help prevent you from turning your phone into a useless paperweight. You seem very confused by a lot of the information found here in the forums, and that is a very good time to slow down, take your time, and make sure you understand what you are doing at every step.
Click to expand...
Click to collapse
ALL of this information can be confusing and I doubt anyway one will deny that fact. The MAIN point is that i know how to fix it, right? This is why I eventually want to make a straight-forward thread about how to do things to which phone properly.
People learn from their mistakes.
I have been learning more and more as i go along but the fact i have T-Mobile service but a Verizon phone just added to the confusion.
Secondly i went in to a T-Mobile Store, so of course i wanted a T-Mobile phone, not a Verizon one. See, everyone makes stupid mistakes and misinterprets things :laugh:
exitpr0gram said:
ALL of this information can be confusing and I doubt anyway one will deny that fact. The MAIN point is that i know how to fix it, right? This is why I eventually want to make a straight-forward thread about how to do things to which phone properly.
People learn from their mistakes.
I have been learning more and more as i go along but the fact i have T-Mobile service but a Verizon phone just added to the confusion.
Secondly i went in to a T-Mobile Store, so of course i wanted a T-Mobile phone, not a Verizon one. See, everyone makes stupid mistakes and misinterprets things :laugh:
Click to expand...
Click to collapse
I didn't make a stupid mistake and misinterpret anything. Please show me where in your previous posts you wrote you went to a T-Mobile store. The only thing you wrote was you had the receipt and T-Mobile never heard of the store. Logical to assume you didn't go to a T-Mobile store from that description.
Yea. Whatever.
landshark68 said:
I didn't make a stupid mistake and misinterpret anything. Please show me where in your previous posts you wrote you went to a T-Mobile store. The only thing you wrote was you had the receipt and T-Mobile never heard of the store. Logical to assume you didn't go to a T-Mobile store from that description.
Click to expand...
Click to collapse
OK Your right, i didn't meantion it. You feel like your testosterone levels have increase now? Jesus.
From the moment you've replied to my posts you've had an attitude that is barely detectable.
Thanks for your help but you need to get out more and learn some people skills,dude. ****.
Look dude, we get it. You went and bought a new toy and couldnt wait to play with it. We're all guilty of that at some point. But blaming your mistakes on someone else, like when you blame the devs for not being straight forward with their roms, although with every example you have given here they really have been, all you need to do is read their posts, you'll get what your getting now. The only one you have to blame here is yourself. For not researching what you have first and just jumping into flashing a rom that was not developed for the phone you actually have. We tried to help you out and point you in the right direction but you decided to be the one with the attitude. Not landshark or my self. I think before you shell out advice on leaening people skills to someone else, you might want to practice what you preach first.
Hello,i need help, i was trying to root my wifes samsung s5 G900F with lollipop , and used in download mode odin with CF-Auto-Root-klte-kltexx-smg900f.tar with only auto reboot checked and after rebbot gave an error and went again to download mode tried to install openrecovery-twrp-2.8.1.0-klte now with f.reset time checked also, with error of not been able to open mtp. made shutdown and tried to turn on phone and now it doesnt work nothing, not even light when charging.
can somenone help...

Categories

Resources