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.
Related
This is the word on the 4G forum here on XDA! Hope this soon leads to the incredible root but for now ill just be jealous.
Link: http://www.engadget.com/2010/05/24/htc-evo-4g-rooted-in-record-time-video/
P.S. Thanks to anyone working on incredible root.
i was equally as upset hope this helps us out
nevermind if you go to the source: http://grack.com/blog/2010/05/23/root-on-an-htc-evo-4g/
they state "At this time, we believe that this specific exploit cannot be applied to Incredible."
Darn that really sucks
mejdam said:
i was equally as upset hope this helps us out
nevermind if you go to the source: http://grack.com/blog/2010/05/23/root-on-an-htc-evo-4g/
they state "At this time, we believe that this specific exploit cannot be applied to Incredible."
Click to expand...
Click to collapse
Boo!
When I read the news on engadget, I had the warm and fuzzies. Same android build. Same sense. CDMA radio. Rooted! What a downer!
How can we get an INC into these guys hands? I'd be willing to donate some cash if it helps.
Dont post this crap in the DEV thread, there are 3 other sectiosn for this on XDA
1wayjonny said:
Dont post this crap in the DEV thread, there are 3 other sectiosn for this on XDA
Click to expand...
Click to collapse
Lol not like it would hurt, that **** already full of spam and beggers haha
it was somthing in the bootloader that found that the incredible does not have. But rest assured that its bieng worked on and im sure we will have root.
nah, it wasn't the bootloader
looks to me like he flashed a leaked image based on where he starts the video and seeing how he doesnt show us the bootloader or anything involving recovery/fastboot. My guess is that since this was an evo prerelease is that someone at htc with the shipping rom weasled a su apk in there while also having the test keys to sign. I never see anyone talking on irc and i assume we are months away from root.
edit: after looking on the website it seems as if they have done deeper work than i assumed. I believe there may be similarities in what they did and what we need. He mentions that he used his linux background and knowldge of hacking bootloaders. maybe something is in store for us unlucky incredible users
nope it has been stated that it will not work for us. And it looks like my bootloader theroy is wrong..... mmmmm i wonder what it could be.
are you judging by this little footnote? "At this time, we believe that this specific exploit cannot be applied to Incredible." - taken from grack.com . If they did anything to the bootloader i would assume an exploit can be derrived from this method. we dont need to use their entire method. From what i hear their bootloader is a higher version than ours which should make it more difficult to crack. If they ever release how they did it Im sure we can find some hope to help us.
1wayjonny said:
Dont post this crap in the DEV thread, there are 3 other sectiosn for this on XDA
Click to expand...
Click to collapse
Knowledge is power and not sure what was up your rear when posting but any bit of information on semi similar phones never hurt anyone. Seeing how this isn't a post about an accessory app theme maybe could go into general but this is more of developmental news then general.
Well, I at least feel better knowing others are going through the same "pain" I am faced with. I'll donate my time and resources (I still don't have the Incredible thx to it being sold out everywhere... maybe I will try the Best Buy closest to me... although they kind of stink, they don't even carry any Apple computers while most ever other BB does) to get this fix0rz for the peeple!
Hero_Over said:
looks to me like he flashed a leaked image based on where he starts the video and seeing how he doesnt show us the bootloader or anything involving recovery/fastboot. My guess is that since this was an evo prerelease is that someone at htc with the shipping rom weasled a su apk in there while also having the test keys to sign. I never see anyone talking on irc and i assume we are months away from root.
users
Click to expand...
Click to collapse
Nothing to do with test keys, no leaked images. There is no way to modify it to the incredible.
lol, I knew it was going to be rooted before, but I had some hopes it could have been used to help with the root for the Incredible. Oh well, such is life. I'm sure there are some Verizon Android developers that are still working on this....All the give me root and where's the root and other I want root spamming is not going to help with anything other than the continuous spamming of this section.
I really hate this waiting for the Unlockers/Root for any phone as it's nothing but spamming.
Just be patient and it will come. Then it's time for you to show your gratification to the developers for their hardwork that I'm sure most do in their spare time and not as their source of income...
[Insert some more I want root spam after this message]
As you've probably seen, the2dCour has a very tasty morsel of what's to come for us all. He's one of the many great people in #moto-atrix, including Jug6, Edgan, Sogarth, unknown, Brandon15811, and helpful friends, Pauly, dasmoover, cranch, YellowGTO and more, who have been helping me poke at the Atrix for many weeks. Also, if I know anything at all (I don't) it's thanks to [mbm] and Skrilax and xvilka and the others who implemented the hard work of 2nd init and kexec and beat their head against Motorola's signature chain on the previous generation of phones.
But our biggest thanks go to Motorola. A very friendly 'community-minded engineer' at Motorola posted an interesting message in hex on their support forums yesterday. Turns out, maybe it's no joke after all.
(http://forum.xda-developers.com/showthread.php?t=1134786)
This got me to thinking. I was already looking through some of the ascii / hex of the bootloaders. Search for VOID and you'll find something completely new in the HKTW (Hong Kong / Taiwan) build, which is not in the CGs for any prior Atrix bootloader:
Code:
$ strings CG42.img | grep INFO
...
INFOUnlocking your device can permanently VOID your warranty.
INFOThis process cannot be reversed. If you wish to proceed,
INFOreissue the unlock OEM command containing the unique ID
INFOof your device:
On Edgan's engineering phone, the HKTW build enables a command you may all be familiar with:
fastboot oem unlock
It looks as if it asks you to issue the command twice, after giving you a unique ID (based on your phone) you must enter in. Surrounding parts of the CG suggest this will wipe your userdata much like a "fastboot -w" currently does. Our hypothesis about the fuses may also be backwards, and it is unlocking which burns a fuse, thus making this an operation which "cannot be reversed."
So, I think we can all look forward to Gingerbread's release for many reasons!!!
PS. Beyond voiding the warranty, or access to support, such an operation could potentially make your phone ineligible for OTAs, future retail .sbfs, etc... and we do not yet know which carriers will get it. So don't get TOO excited
PPS. If this is headed to the official release, I'd like to give a HUGE thanks to Irwin Proud and all the others who petitioned Motorola to make this happen!
But there's no time to rest. Now we must pressure all the carriers!
Confirmed working for AT&T users!! Eval emailed me the good news this morning, so we tried it on leaked GB for the Atrix 4G on AT&T.
http://briefmobile.com/exclusive-atrix-4g-bootloader-unlocked-with-android-2-3-update
I tested it out on my Gingerbread beta builds.
This is excellent news everyone.
Be patient, we need to see if this update hits all our devices, but when it does, I guarantee there will be no shortage of Roms and Mods that will come as a result.
I actually think Motorola may see a spike in sales when 2.3.3 hits their Atrix phones.
Thank you everyone who showed your support for the Unlock Motorola campaign and went out of their way to make their voices heard. Together we stand and together we claim victory.
Thank you Motorola.
Intresting
Yay!
Of course, the question becomes... what next?
Sogarth said:
Yay!
Of course, the question becomes... what next?
Click to expand...
Click to collapse
Now that Moto's on our side I will (proudly) use my lapdock. How's your awesome Webtop2SD with my mknod sdcard hack going?
But yes, someone must do the much more time-consuming work of porting CM or other AOSP forks. And we have to pray AT&T lets this happen...
eval- 4 president
eval- said:
But yes, someone must do the much more time-consuming work of porting CM or other AOSP forks. And we have to pray AT&T lets this happen...
Click to expand...
Click to collapse
When this happens, I WILL pinch myself to make sure I'm not dreaming!!
If Bell, lets say, got this and at&t didn't, would we be able to somehow port it?
Swyped from my HoneyGlowed Atrix
Way to guy team This kicks ass!
P.S. the2d is a troll..but a damn good one.
Has this been actually verified, (is there a way to verify on an engineering phone?), as unlocking a bootloader, or is this at the moment still speculation as to what might be possible after the GB update?
Could this just be Moto laying the groundwork for a future update which unlocks the bootloader without us having to do it ourselves voiding warranties, etc?
wakka wakka wakka
crossing fingers
wow! That's awesome news! Can't wait to hear if it's verified.
Verified -- http://briefmobile.com/exclusive-atrix-4g-bootloader-unlocked-with-android-2-3-update
Video in a bit.
kennethpenn said:
Verified -- http://briefmobile.com/exclusive-atrix-4g-bootloader-unlocked-with-android-2-3-update
Video in a bit.
Click to expand...
Click to collapse
Im cheesing so hard right now
Sent from my Moto Atrix using XDA Premium App
Very interesting! Of course, if we have Gingerbread, not much point in CM7 for me, is there an ice cream sandwich or whatever in between or after any time soon from the CyanogenMod bunch?
Cheers!
kennethpenn said:
Confirmed working for AT&T users!!
http://briefmobile.com/exclusive-atrix-4g-bootloader-unlocked-with-android-2-3-update
I tested it out on my Gingerbread beta builds.
Click to expand...
Click to collapse
Holy freakin hell!!! Awesome just awesome!! Can ATT actually stop this from happening though?
joshyy_rey said:
Im cheesing so hard right now
Sent from my Moto Atrix using XDA Premium App
Click to expand...
Click to collapse
I have a raging clue right now
Just as I put my Atrix up for sale . Good news if the OTA comes out like this. I'll keep it and see i think!
Now let's get that CWM Recovery on it!
Since I am on KP's 4.5.91 I have not flashed the released OTA.
I see many people already bricking after installing the upgrade, then trying to flash back.
Do you get a warning either before downloading the OTA, or before installing the OTA that you cannot flash to a previous version afterwards?
If not, it's possible you could return your phone, blaming AT&T/Moto for not warning you about backwards flashing.
If there was a warning, sorry, but you will probably be SOL, and it's your own fault for trying to downgrade after installing the OTA.
A bricked device will display 0x1000 on the screen when trying to boot up.
If you see this, go here ---> http://forum.xda-developers.com/showthread.php?t=1160408
Of course not, why would Motorola put in a warning like that. Motorola never excepts you to flash back to an older firmware.
Sent from my MB860 using XDA App
CaelanT,
I updated to gingerbread on rooted atrix 4.1.83. I did not notice any warning as you are hoping. Though the phone's root privilege is no more, Motorola has enabled the sideloading and I am happy with that.
Sent from my MB860 using XDA App
Are you serious?
Why would AT&T or Motorola be to blame for you bricking your device?
There doesn't need to be a "no flash back" warning... If you're 'flashing back' you are most likely using software you're not technically supposed to have to flash firmware you're not technically supposed to have.
It's really tiring reading these forums where people blame everyone but themselves for their bricked device. (Even after the "THIS WILL BRICK YOUR DEVICE" warnings..)
Technically, people shouldn't be able to flash back... we're not supposed to have RSD software or SBFs to flash in the first place.
ebaychuck said:
Why would AT&T or Motorola be to blame for you bricking your device?
There doesn't need to be a "no flash back" warning... If you're 'flashing back' you are most likely using software you're not technically supposed to have to flash firmware you're not technically supposed to have.
It's really tiring reading these forums where people blame everyone but themselves for their bricked device. (Even after the "THIS WILL BRICK YOUR DEVICE" warnings..)
Click to expand...
Click to collapse
Because technically, if they do not warn you that you can ruin your device by flashing to an earlier version, you have a case to sue them if you so choose to go that route. It's their failure to secure the software, updates, and upgrades they have which allows people to flash something you say they should not have, but is freely available to download through software update. Please do not spout what you hear from other people and think this makes you knowledgeable in any way. There are many legal implications with Moto and AT&T not disclosing what their updates/upgrades will or will not do, especially when they say "you will have unlock ability", then switch that at release with no warning, or for any number of reasons.
I can see you have a large contribution to this community by the grand sum of 5 posts which you have.
Now, I am trying to help some of the people out here who were obviously stupid enough to blindly flash an update released to them without first consulting XDA, because of course when you buy the Atrix it tells you to consult XDA on any matters relating to the Atrix!
Go back to ebay where you belong chuck!
BTW..........yes, I am very serious!
So the boot loader on the OTA is still Locked?!!!
yeah you could try that argument. they could give you the run around that you flashed using stuff not from their site or from their customer service portal and there could be some line in the warranty that would cover their ass from that stuff. but hey, worth a shot.
I updated to ota 4.5.9.1 during the soak and there was a big warning on the website, but nothing that I remember seeing when I downloaded and installed the software. They know the risk obviously. Surprised they wouldn't cover their behind during the install.
Sent from my MB860 using XDA Premium App
sservati said:
So the boot loader on the OTA is still Locked?!!!
Click to expand...
Click to collapse
Yes it is.
Beamed from WinBorg 4G via XDA Premium
CaelanT said:
Because technically, if they do not warn you that you can ruin your device by flashing to an earlier version, you have a case to sue them if you so choose to go that route. It's their failure to secure the software, updates, and upgrades they have which allows people to flash something you say they should not have, but is freely available to download through software update. Please do not spout what you hear from other people and think this makes you knowledgeable in any way. There are many legal implications with Moto and AT&T not disclosing what their updates/upgrades will or will not do, especially when they say "you will have unlock ability", then switch that at release with no warning, or for any number of reasons.
I can see you have a large contribution to this community by the grand sum of 5 posts which you have.
Now, I am trying to help some of the people out here who were obviously stupid enough to blindly flash an update released to them without first consulting XDA, because of course when you buy the Atrix it tells you to consult XDA on any matters relating to the Atrix!
Go back to ebay where you belong chuck!
BTW..........yes, I am very serious!
Click to expand...
Click to collapse
As many people have said.. Motorola does not give you any offical path to unlock your bootloader and flash a previous version. People like XDA do.
I have no problem with putting a custom Rom on my phone. I've hacked every device since my first Windows CE pda. The problem I have is with people like you that want to Sue Motorola because they... What? Told you to unlock your bootloader and try to flash unsupported software? No, they didn't.
Oh, and by the way please show me where you got the Official Motorola Atrix Unlock from.
ebaychuck said:
As many people have said.. Motorola does not give you any offical path to unlock your bootloader and flash a previous version. People like XDA do.
I have no problem with putting a custom Rom on my phone. I've hacked every device since my first Windows CE pda. The problem I have is with people like you that want to Sue Motorola because they... What? Told you to unlock your bootloader and try to flash unsupported software? No, they didn't.
Oh, and by the way please show me where you got the Official Motorola Atrix Unlock from.
Click to expand...
Click to collapse
The unlocked Bootloader is one thing, the fact that some users are bricking their phones after using OTA's is another.
Granted the 0X1000 is coming more from XDA users who have flashed, but Motorola needs to embrace the Android community better.
I'm not a fanboy of any company by any means, currently I own both a SGS and an Atrix.
^ With that said, Motorola needs to be a little more like Samsung.
* Paying attention to forums like XDA would be a start. Giving phones for free to developers would be another. (Samsung had no problem doing this).
*Getting rid of the bootloader FOREVER would also be in their best interest.
* Finally not forcing MotoBlur accounts down people's throats would be a friendlier approach as well.
Android consumers have helped Motorola get back in the game.
It's time for Motorola to repay the favor and start treating Android like "Android", and not like an iPhone...
sservati said:
So the boot loader on the OTA is still Locked?!!!
Click to expand...
Click to collapse
From what I've been reading, yes...
ccrows said:
The unlocked Bootloader is one thing, the fact that some users are bricking their phones after using OTA's is another.
Granted the 0X1000 is coming more from XDA users who have flashed, but Motorola needs to embrace the Android community better.
I'm not a fanboy of any company by any means, currently I own both a SGS and an Atrix.
^ With that said, Motorola needs to be a little more like Samsung.
* Paying attention to forums like XDA would be a start. Giving phones for free to developers would be another. (Samsung had no problem doing this).
*Getting rid of the bootloader FOREVER would also be in their best interest.
* Finally not forcing MotoBlur accounts down people's throats would be a friendlier approach as well.
Android consumers have helped Motorola get back in the game.
It's time for Motorola to repay the favor and start treating Android like "Android", and not like an iPhone...
Click to expand...
Click to collapse
Yeah, it would be nice if they'd support their more advanced users like Samsung and HTC have been doing. It seems like they are about to make some kind of change with Motoblur so maybe they'll ease up on the requirement to use it.
ebaychuck said:
Yeah, it would be nice if they'd support their more advanced users like Samsung and HTC have been doing. It seems like they are about to make some kind of change with Motoblur so maybe they'll ease up on the requirement to use it.
Click to expand...
Click to collapse
I've seen the Motoblur "improvements", but you still need an account, which is BS. Plus its a waste of time to freeze things in TiBU.
Between the last OTA that bricked many phones and the current Motoblur BS, I hope we can get Vanilla Gingerbread on this device more than ever. This will definitely be my last Motoblur phone I ever purchase.
Don't get me wrong I like Motorola a lot, but I also like to have a drama free phone...
I have a question for everyone that upgraded to GB.
After reading about the bugs in GB (like the "battery jumping issue" for instance) -
If you "could" go back to Froyo's latest build, would you do it or are you happier with the current GB?...
Nah.
ccrows said:
I have a question for everyone that upgraded to GB.
After reading about the bugs in GB (like the "battery jumping issue" for instance) -
If you "could" go back to Froyo's latest build, would you do it or are you happier with the current GB?...
Click to expand...
Click to collapse
Even with the few problems i'm enjoying having GB.. I guess I just like something new to look at.
I only miss a few things.
- The Happenings page that used to be attached to contacts. It was nice to be able to see the last post a friend made when calling them.
- Access control in Wireless Tether. (I can't remember if it worked on the Atrix or just my previous phone)
- Working Wired Tether..
- Setting review time on the camera.
CaelanT said:
Since I am on KP's 4.5.91 I have not flashed the released OTA.
I see many people already bricking after installing the upgrade, then trying to flash back.
Do you get a warning either before downloading the OTA, or before installing the OTA that you cannot flash to a previous version afterwards?
If not, it's possible you could return your phone, blaming AT&T/Moto for not warning you about backwards flashing.
If there was a warning, sorry, but you will probably be SOL, and it's your own fault for trying to downgrade after installing the OTA.
A bricked device will display 0x1000 on the screen when trying to boot up.
If you see this, go here ---> http://forum.xda-developers.com/showthread.php?t=1160408
Click to expand...
Click to collapse
"Hi Motorola, I'm using non-public tools that have been leaked, and non-public SBF files that have been gotten in an unofficial capacity to downgrade my phone after the latest update. I'm not breaking my warranty, am I?"
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!
Hey everyone,
I'm actually genuinely curious about this, I'm looking to potentially start developing for this phone but in order to do this I need to know the state of affairs and what exactly we have at the moment and don't. I see we can unlock bootloader and root....but the techniques used to do so seem very......primitive.... to say the least, and quite compressed for a newbie.
What exactly is the issue for lack of ROM development, what are we missing? Is it possible to make a tool to help with bootloader unlock and root, and if it is why hasn't it happened yet? I see we have TWRP but what else do we need?
Like I said I'm genuinely curious and not trying to start a flame war, this is for productive conversation and discussion. I come from a Nexus 6 so the lack of development is something I'm aware of before I bought this phone, but I would really like it to thrive as it's a great phone. As a disclaimer I haven't rooted or unlocked my phone yet, I just got it, and as much as I am very experienced in this field, I'm not yet ready to go through the process if it's not worth it.
Thank you.
A full image from ZTE is what we are waiting on (last I heard)
tele_jas said:
A full image from ZTE is what we are waiting on (last I heard)
Click to expand...
Click to collapse
The full image is not a problem. All binary files can be extracted from partition backups.
If you check https://github.com/hax-on you will see progress. As an developer you will especially see what's missing. The main issue is audio vendor blobs getting to work without help of ZTE devs.
It requires reverse engineering. (IDA Pro, radar2).
Not everyone knows how to RE. That is why the community is pushing ZTE for help or release the sources for the required blobs.
Additionally, I am running into a back order issue so maybe more development will occur when next batch hits the shelves in a few weeks? But op brings up a good question.
Sent from my Pixel using XDA-Developers mobile app
canezila said:
Additionally, I am running into a back order issue so maybe more development will occur when next batch hits the shelves in a few weeks? But op brings up a good question.
Sent from my Pixel using XDA-Developers mobile app
Click to expand...
Click to collapse
Jet.com has it shipping Monday with 30$ off, free shipping, and no tax
Have faith - once they get CM13 going the flood gates will open.
Anything that can be done by us that don't have the experience but want to contribute?
S8ntsHaz3 said:
Anything that can be done by us that don't have the experience but want to contribute?
Click to expand...
Click to collapse
For now only patients. And once CM becomes available testing and reporting bugs using logs and pastebin.