I know some people have asked about porting AOSP to the Fire TV. It's probably still a long way off, but I have managed to get it to start booting and have the boot animation display. Some stuff crashes early on, and then later in the boot, other things crash because that first thing is missing. And then it just constantly bootloops... but it's a start.
Spectacular!
My main goal is to get a full-fledged modern Linux OS with access to running my Android apps inside a window while having real-time access to Linux and all of its programs.
Thanks rbox! You're awesome! That's exactly what i wanna in my box.
I think that you can enable the "donante" in your profile, i would like to donate to reward your wonderful work!
I too would like to donate.. As well as test.. Willing to capture and submit log files. How are you booting this ROM? Unlocked boot loader on the way?
LittleBear1981 said:
I too would like to donate.. As well as test.. Willing to capture and submit log files. How are you booting this ROM? Unlocked boot loader on the way?
Click to expand...
Click to collapse
I enabled the paypal donate in my profile but it seemed a little tacky to me to have it on all my posts. So here is a donate link.
As for how I'm booting this, right now very haphazardly. In the end it will require an unlocked bootloader but jcase is the one that has to provide that. Technically, it does work with the stock kernel and I am playing around with some ideas for booting into recovery with the locked bootloader. But hopefully jcase will be able to provide the unlock soon.
rbox said:
In the end it will require an unlocked bootloader but jcase is the one that has to provide that. Technically, it does work with the stock kernel and I am playing around with some ideas for booting into recovery with the locked bootloader. But hopefully jcase will be able to provide the unlock soon.
Click to expand...
Click to collapse
IMO, it seems like jcase has no interest in releasing it. He's already said he doesn't care about the community. Just does what he does for the challenge, and I guess publicity. I could go on with more to support my theory, but don't want to come across a complainer, as no one owes us anything.
Agreed, no one owes us anything.. That said.. Jcase wherever you are.. I would like to send you 25$ (US) too. I do not ask for support.. Just the means.. The knowledge. Thanks again everyone.
LittleBear1981 said:
Agreed, no one owes us anything.. That said.. Jcase wherever you are.. I would like to send you 25$ (US) too. I do not ask for support.. Just the means.. The knowledge. Thanks again everyone.
Click to expand...
Click to collapse
he also seems to be a man of few words, so its possible hes still waiting on amazon to fix the security vulnerability before he releases it, thats the last thing he said here before he went silent, either way tho, good job RBOX, and everyone else helping.
Luxferro said:
IMO, it seems like jcase has no interest in releasing it. He's already said he doesn't care about the community. Just does what he does for the challenge, and I guess publicity. I could go on with more to support my theory, but don't want to come across a complainer, as no one owes us anything.
Click to expand...
Click to collapse
Very, very true. E-publicty ruined that guy. Its awesome to see someone still working on this box though, gj Rbox hopefully your work will lead to greater things in the future.
So it's booting all the way. I'm not sure why there is a black bar on the right side.
rbox said:
So it's booting all the way. I'm not sure why there is a black bar on the right side.
Click to expand...
Click to collapse
Are you booting from a USB stick?
jocala said:
Are you booting from a USB stick?
Click to expand...
Click to collapse
I'm actually booting it off my network right now with NFS and loop mounts. I suppose I could use a similar method to boot it from USB. I'm thinking about creating a system based on 2nd-init which some phones with locked bootloader use. Hopefully the unlock will be released before I have to do that though.
rbox said:
I'm actually booting it off my network right now with NFS and loop mounts. I suppose I could use a similar method to boot it from USB. I'm thinking about creating a system based on 2nd-init which some phones with locked bootloader use. Hopefully the unlock will be released before I have to do that though.
Click to expand...
Click to collapse
Good luck. A rescue stick for the aftv would be mighty handy.
I've worked on 2nd init for some Motorola phones back in the day.. The trick is finding a script that is not in /system that runs from init early in the boot process...
FireTV + AndroidTV
I know it is a basic question, but theoretically if you get the 2nd Init working, we could port an AndroidTV ROM into the FireTV and use it as such, right?
At the end the remote control has also the Voice functionality.
Just wondering or am I missing something?
Fgarcor said:
I know it is a basic question, but theoretically if you get the 2nd Init working, we could port an AndroidTV ROM into the FireTV and use it as such, right?
At the end the remote control has also the Voice functionality.
Just wondering or am I missing something?
Click to expand...
Click to collapse
It depends on the sourceness of Android TV (probably not open source), the availability of a system dump, and the hardware compatability. I'm not sure what you are saying about the remote control... but it doesn't have "voice functionality", it has a microphone and the system software has the support for the voice.
It seems that unlock won't be released from Jcase:
https://twitter.com/TeamAndIRC/status/505926495835922434
(it's about Kindle HDX, but it's the same case as FTV).
So... Help us rbox kenobi, you're our only hope!
Who or what exactly is responsible for the prevention of the unlocker getting released?
Wouldn't it be a middle finger to their consumers if Amazon was actually the cause of this trajedy?
krasny2k5 said:
It seems that unlock won't be released from Jcase:
https://twitter.com/TeamAndIRC/status/505926495835922434
(it's about Kindle HDX, but it's the same case as FTV).
So... Help us rbox kenobi, you're our only hope!
Click to expand...
Click to collapse
Seems I was finally able to get TWRP to display on the screen. Unfortunately it was only for a second and then it crashed and rebooted. But I'm making progress. Unfortunately I had some family issues to take care of this weekend so I didn't have as much time as I had hoped.
retroben said:
Who or what exactly is responsible for the prevention of the unlocker getting released?
Wouldn't it be a middle finger to their consumers if Amazon was actually the cause of this trajedy?
Click to expand...
Click to collapse
Of course Amazon is the "cause". They don't want you unlocking it, hence the reason it's locked in the first place. Unfortunately it looks like the DMCA is preventing the unlock from being released.
krasny2k5 said:
It seems that unlock won't be released
Click to expand...
Click to collapse
You may not need an unlocker.
As a simple test unpack recovery, modify icon_error.png, repack, dd to recovery partition and reboot recovery.
I'd be interested to know if this works on releases other than 51.1.0.2
Related
noticed that the psfree has been ported to a couple of cell phones (palm pre, nokia n900). i was wondering if it was possible for this to be ported over to our phone. it would be nice not to have to buy any extra hardware to do this. anyone who's smart know anything about this? like if it can be done, what would need to happen to make it work?
here is a site discussing the port to the pre. http://psx-scene.com/forums/showthread.php?t=65355
they released a version for nexus one
needs unlocked bootloader
well that sucks. there is really no way around it? i'm sure if someone smart enough really wanted to do it, someone would. probably not that much interest in it though. too bad, although if someone were to figure it out i would definitely throw a coffee donation their way.
well seems a lot of devices are compatible:
http://psfreedom.com/wiki/index.php?title=Device_compatibility_list
droid x not listed though, hopefully someone gets interested in doing this.
jbaruch76 said:
well that sucks. there is really no way around it? i'm sure if someone smart enough really wanted to do it, someone would. probably not that much interest in it though. too bad, although if someone were to figure it out i would definitely throw a coffee donation their way.
well seems a lot of devices are compatible:
http://psfreedom.com/wiki/index.php?title=Device_compatibility_list
droid x not listed though, hopefully someone gets interested in doing this.
Click to expand...
Click to collapse
Well it says compatibility for the Milestone is in progress...which also has a locked bootloader like the X. So maybe you could check with the devs working on the Milestone or try the Milestone release when it comes out?
drewden123 said:
Well it says compatibility for the Milestone is in progress...which also has a locked bootloader like the X. So maybe you could check with the devs working on the Milestone or try the Milestone release when it comes out?
Click to expand...
Click to collapse
That would be awesome.
drewden123 said:
Well it says compatibility for the Milestone is in progress...which also has a locked bootloader like the X. So maybe you could check with the devs working on the Milestone or try the Milestone release when it comes out?
Click to expand...
Click to collapse
i don't think the milestone will help us, it seems like it works because it has the musb usb controller. not sure what we ahve with the dx but somenoe woudl definitely have to do some work to make this happen. too bad nobody seems to have this phone.
I've been looking today for a good way to go about compiling the module for froyo-based dx, as I've been wanting to for tun.ko as well to get vpn working again. Prior I found a .config and module compiled, but haven't seen anything for Froyo around the tun. Now there's additional motivation to make the psjailbreak module loadable, and figure there's got to be a way to resolve symbol issues.
I also saw another thread for overclocking modules, so figure someone's got to have a clean .config that works to also produce these *other* modules on and for a dx.
Not sure also how the boot.img file works in the exploit, if the signed bootloader would play against this. If the module were loaded after the boot process, it doesn't seem to care, but not at all certain how much this is modifying the boot process yet.
mbutash said:
I've been looking today for a good way to go about compiling the module for froyo-based dx, as I've been wanting to for tun.ko as well to get vpn working again. Prior I found a .config and module compiled, but haven't seen anything for Froyo around the tun. Now there's additional motivation to make the psjailbreak module loadable, and figure there's got to be a way to resolve symbol issues.
I also saw another thread for overclocking modules, so figure someone's got to have a clean .config that works to also produce these *other* modules on and for a dx.
Not sure also how the boot.img file works in the exploit, if the signed bootloader would play against this. If the module were loaded after the boot process, it doesn't seem to care, but not at all certain how much this is modifying the boot process yet.
Click to expand...
Click to collapse
literally did not understand one thing you said but glad to know someone is on it, hopefully others can pitch in and help out.
http://forum.xda-developers.com/showpost.php?p=8025887&postcount=19
t4tav says that this bypasses the bootloader so no need to unlock it
this should work if the ps3-signed.zip flashes into the X with the custom recovery!
otherwise the files inside it need to be replaced with X compatible ones, I can't try because I'm at work but I will later. if it doesnt work you can always flash sfb back to stock
sp1kez said:
http://forum.xda-developers.com/showpost.php?p=8025887&postcount=19
t4tav says that this bypasses the bootloader so no need to unlock it
this should work if the ps3-signed.zip flashes into the X with the custom recovery!
otherwise the files inside it need to be replaced with X compatible ones, I can't try because I'm at work but I will later. if it doesnt work you can always flash sfb back to stock
Click to expand...
Click to collapse
well this sounds promising, has anyone tried yet? looks like just about everyone's got this running but us now.
any progress on this? I am very interested =)
Okay so I've got a theory about Motorola encrypted bootloaders like the ones on DX and Milestone. What I'm looking for is definitive information on the droid x lockout mechanism. Any information would be greatly appreciated. Also, if anyone knows of a broken DX to utilize for this experiment please let me know. It involves a hardware based process so a complete functional phone is not necessary. This method has been known to work with RSA encryption so it shows promise. Thank you.
MrKaz
From what I've heard, the "key" so to speak, in burned into the CPU itself. Its my understanding the only true way to unlock the BL is with Moto's keys, which we wont be getting any time soon. Whatever your plan is, I wish you the best. But we've had roughly 20+ of these threads come and go on here with everyone thinking they can crack it, and nothing ever pans out. Its a matter of the right people with knowledge and the right equipment to do the job, but those things have just not come together yet.
Once again, I wish you the best!
You may want to contact @aliasxerog, @_mrbirdman_, and/or @nenolod on twitter as they have all worked on trying to break/circumvent the bootloader. @P3Droid may be knowledgeable as well.
Yeah, I realize there's been a lot of threads on this. Having read a good deal of them I've determined that for the most part the consensus is that it can't be done, or at least not by any brute force means. However, I'm interested in other ways like signal injection and other hardware based avenues. After all, it is a chip and chips have flaws... Maybe I don't know enough to realize what it would take, and maybe being too stupid to understand that it can't be done is exactly what is required...
Thanks for all your input
MrKaz
MrKazman said:
Yeah, I realize there's been a lot of threads on this. Having read a good deal of them I've determined that for the most part the consensus is that it can't be done, or at least not by any brute force means. However, I'm interested in other ways like signal injection and other hardware based avenues. After all, it is a chip and chips have flaws... Maybe I don't know enough to realize what it would take, and maybe being too stupid to understand that it can't be done is exactly what is required...
Thanks for all your input
MrKaz
Click to expand...
Click to collapse
MrKaz,
+1 to your idea. Hey, who knows what will work.. with all that is going on, I wouldn't be surprised if the one idea that works..is some off the wall idea such as a chip flaw... Go for it man... I say take the idea and run with it.
best of luck
Your idea is one that I have been working on. All that needs to happened is find a way to dump the info to a computer and resign or make a dummy key to patch and inject back in.. unfortunately I have yet been able to inject anything because once dumped and cleared it doesn't regonize still active.. blah DX
MrKazman said:
Okay so I've got a theory about Motorola encrypted bootloaders like the ones on DX and Milestone. What I'm looking for is definitive information on the droid x lockout mechanism. Any information would be greatly appreciated. Also, if anyone knows of a broken DX to utilize for this experiment please let me know. It involves a hardware based process so a complete functional phone is not necessary. This method has been known to work with RSA encryption so it shows promise. Thank you.
MrKaz
Click to expand...
Click to collapse
Is this the electron starvation method that you speak of? From my understanding, that's a server exploit. Not really useful for a DX.
You want to be gamed up with the isht? #milestone-modders on freenode
gpaulu said:
You may want to contact @aliasxerog, @_mrbirdman_, and/or @nenolod on twitter as they have all worked on trying to break/circumvent the bootloader. @P3Droid may be knowledgeable as well.
Click to expand...
Click to collapse
Boooooooooooooooo...
_mrbirdman_ & nenolod dropped the ball and jumped ship.
P3Droid is better at BS and espionage than development. I mean, who actually uses tranquility? Or hasn't been bricked by it? Beside, what's been the biggest draw TBH has had to their app? The tether patch? If you were me, you'd be LYAO... LOL
As for @aliasxerog, from what I've seen, I've got very little faith that his efforts will pan out. Unless he stops looking to the above mentioned "devs", and starts working with the milestone guys. Especially yakk, who's probably done the most work on the kexec kernel module(Funny, aliasxerog's src makes no mention. He just says he ported it from the milestone efforts.). Yakk hasn't even released all of his code for kexec, so what aliasxerog is working with is incomplete, and certainly not up-to-date. His source doesn't even compile. Not even on my trusty build system that built the first DX overclock kernel module for Froyo, which jumped off JRummy's DX career(Jared didn't even bother to say "hey, mind if I use the module you built?"). Gotta love the DX devs! They bring so much laughter into my life!
.....
With that said, MrKazman, good luck in your efforts.
http://www.and-developers.com/boot:boot_chain
You may want to take a look at this. I think it's about the milestone, but it is similar to if not the same as the droid x
tekahuna said:
Is this the electron starvation method that you speak of? From my understanding, that's a server exploit. Not really useful for a DX.
You want to be gamed up with the isht? #milestone-modders on freenode
Boooooooooooooooo...
_mrbirdman_ & nenolod dropped the ball and jumped ship.
P3Droid is better at BS and espionage than development. I mean, who actually uses tranquility? Or hasn't been bricked by it? Beside, what's been the biggest draw TBH has had to their app? The tether patch? If you were me, you'd be LYAO... LOL
As for @aliasxerog, from what I've seen, I've got very little faith that his efforts will pan out. Unless he stops looking to the above mentioned "devs", and starts working with the milestone guys. Especially yakk, who's probably done the most work on the kexec kernel module(Funny, aliasxerog's src makes no mention. He just says he ported it from the milestone efforts.). Yakk hasn't even released all of his code for kexec, so what aliasxerog is working with is incomplete, and certainly not up-to-date. His source doesn't even compile. Not even on my trusty build system that built the first DX overclock kernel module for Froyo, which jumped off JRummy's DX career(Jared didn't even bother to say "hey, mind if I use the module you built?"). Gotta love the DX devs! They bring so much laughter into my life!
.....
With that said, MrKazman, good luck in your efforts.
Click to expand...
Click to collapse
I love your honesty!
Sent from my DROIDX using Tapatalk
Syco54645 said:
I love your honesty!
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
Beesley doesn't... LOL
http://twitter.com/TheRealBeesley/status/30036655129763840#
@LexusBrian400
build.prop edits vs. Droid X Froyo Overclocking & AP Mode Tethering
Maybe I should put up a donation link, huh? LOL
P.S. I can't help but think your username is a reference to B-Legit's verse on Sideways... Little known fact: The Ambassador himself gave me the handle FreeWELL.
http://www.youtube.com/watch?v=3YXGvsbSjLw
Didn't notice that you mentioned jared. I rather like him. Let's just leave it at that...
Sent from my DROIDX using Tapatalk
Update
I'm getting more and more familiar with this situation every day. I'm also starting to realize what a big problem this is. I've spent a good deal of time pouring over the work they're doing with the Milestone which is kind of the same thing but isn't. Nonetheless I applaud the work they do and donate my CPU to Androinc. After that I've been reading and collecting every Block Diagram, Datasheet, Whitepaper, and post about mbmloader, m-shield, omap, and the like. Yeah, its complicated alright. The fact is though that its just a lock. A lock is a system based on deterrent not prevention. Systems built for mass production have accepted flaws to keep costs down. Chips aren't perfect, code is not perfect. Use the weakness against the system and the lock is picked. The more complex the system the more chances to get in....
Eh, I digress...
Anyone wanting to learn more about this let me know.
The search continues....
Kaz
Motorola, I paid for the Hardware. I can handle my own software and security...
The Bootloader has been bypassed, its just that the custom kernel has no drivers to run.
Ubermicro13 said:
The Bootloader has been bypassed, its just that the custom kernel has no drivers to run.
Click to expand...
Click to collapse
Well ill drive to help out...as long as someone has some snaps on the petro!
Sent from my DROIDX using XDA App
If this is anything like any other locked software, it's based around asymmetric encryption: Motorola HQ has a super-secret key that they use to encrypt their bootloaders, and they put the decryption key on every device, so that only things that are encrypted with their key will be decrypted correctly. The only way we're going to get the encryption key is by sleeping with the CEO of Motorola. It is - by design - not on the device.
The only way to replace the bootloader would be to replace the decryption key with one of our own or by bypassing it completely(using a buffer overflow or something similar).
As much as I want to believe that this can be done, its close to impossible and honestly not worth the persons time to try it, they did a good, well great, job of locking this thing down but ill say that liberty actually makes this feel like a new phone.
Sent from my DROIDX using XDA App
IWHBYD said:
If this is anything like any other locked software, it's based around asymmetric encryption: Motorola HQ has a super-secret key that they use to encrypt their bootloaders, and they put the decryption key on every device, so that only things that are encrypted with their key will be decrypted correctly. The only way we're going to get the encryption key is by sleeping with the CEO of Motorola. It is - by design - not on the device.
The only way to replace the bootloader would be to replace the decryption key with one of our own or by bypassing it completely(using a buffer overflow or something similar).
Click to expand...
Click to collapse
Just take one for the team there buddy.... lol
Sent from my DROIDX using XDA App
what does the CEO of motorola look like?
Enjoy
http://mediacenter.motorola.com/Executive-Team/Sanjay-Jha-31da.aspx
openbox9 said:
Enjoy
http://mediacenter.motorola.com/Executive-Team/Sanjay-Jha-31da.aspx
Click to expand...
Click to collapse
not it *noses*
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!
I've wanted to grill out some of the problems with the A7 that's came with it, but after realizing I've never done this before, I've also noticed there's no actual ROM out yet
Should I just wait until the ROM comes and maybe some full guides?
Rigby J said:
I've wanted to grill out some of the problems with the A7 that's came with it, but after realizing I've never done this before, I've also noticed there's no actual ROM out yet
Should I just wait until the ROM comes and maybe some full guides?
Click to expand...
Click to collapse
Welcome to the A7 Family,
which problems are you running into right now? if you have no need for Root. i'll just say hold on till some development start to kick.......
P.S. not every problem can be fix having root access
DrakenFX said:
Welcome to the A7 Family,
which problems are you running into right now? if you have no need for Root. i'll just say hold on till some development start to kick.......
P.S. not every problem can be fix having root access
Click to expand...
Click to collapse
Really just cosmetic things like the notification bell, maybe switching up the emojis, small things. I always wanted to try a different ROM on this phone, so I guess it isn't anything that needs to be done right now.
Rigby J said:
Really just cosmetic things like the notification bell, maybe switching up the emojis, small things. I always wanted to try a different ROM on this phone, so I guess it isn't anything that needs to be done right now.
Click to expand...
Click to collapse
just unlocked my bootloader and rooted. Wonderful being able to use my root apps again. Chnaged my emoji using emoji switcher which i really wanted to do. Hate the stock android emoji.. debloated a little, and now about to change the system to my favorite font. I say go for it. If you do, let me know. I can send some pointers
considering there is absolutely no rom support yet I would hold off, wait out your 30 day return period and if there are roms after that and you want to void your warranty then do it then. Also I'm sure people are working on getting the bootloader unlocked without contacting ZTE so there is another reason to wait.
pwnerman said:
...Also I'm sure people are working on getting the bootloader unlocked without contacting ZTE so there is another reason to wait.
Click to expand...
Click to collapse
Already done: http://forum.xda-developers.com/axon-7/how-to/bootloader-unlock-t3437778
osmosizzz said:
just unlocked my bootloader and rooted. Wonderful being able to use my root apps again. Chnaged my emoji using emoji switcher which i really wanted to do. Hate the stock android emoji.. debloated a little, and now about to change the system to my favorite font. I say go for it. If you do, let me know. I can send some pointers
Click to expand...
Click to collapse
Thank you, I'll message you when I do.
pwnerman said:
considering there is absolutely no rom support yet I would hold off, wait out your 30 day return period and if there are roms after that and you want to void your warranty then do it then. Also I'm sure people are working on getting the bootloader unlocked without contacting ZTE so there is another reason to wait.
Click to expand...
Click to collapse
I see, I see
Rigby J said:
Thank you, I'll message you when I do.
I see, I see
Click to expand...
Click to collapse
If you want to wait until the 30 day period is over, you can go ahead. im keeping the phone for a while so ive just gone ahead and rooted. there is a method to unlock the bootloader without contacting ZTE. I did it that way. its fairly easy.
Rigby J said:
I've wanted to grill out some of the problems with the A7 that's came with it, but after realizing I've never done this before, I've also noticed there's no actual ROM out yet
Should I just wait until the ROM comes and maybe some full guides?
Click to expand...
Click to collapse
There is a fairly simple way to Unlock your boot loader right now, it seems to work for most people. Its possible they may figure out a way to block this in future updates (I am not an expert). If you are with in your retail return window I would recommend trying the method because if you manage to really mess something up, you can at least return it.
Just take your time.
The instructions are for multiple versions and slightly out of order. Make sure everything is working before you begin.
If you plan to go through ZTE and in theory void your warranty, then by all means wait until you really need it.
Good luck.
osmosizzz said:
If you want to wait until the 30 day period is over, you can go ahead. im keeping the phone for a while so ive just gone ahead and rooted. there is a method to unlock the bootloader without contacting ZTE. I did it that way. its fairly easy.
Click to expand...
Click to collapse
How is this done?
Rigby J said:
How is this done?
Click to expand...
Click to collapse
http://forum.xda-developers.com/axon-7/how-to/bootloader-unlock-t3437778
xtermmin said:
http://forum.xda-developers.com/axon-7/how-to/bootloader-unlock-t3437778
Click to expand...
Click to collapse
thanks
I just got my A7. Coming from OPO with a sultan rom running xposed. I want to root but honestly I am not super smart developer. I am good following direction and figuring things out. I honestly love Sulan rom and would love it on A& but I doubt he does a rom for it as he mostly is busy with school and sticks with OPO or OP3.
I am debating on rooting as I mostly just want xposed for its youtube app adblocker and in app blocking apps.
I would suggest waiting til roms are developed and little more mature. Which if judging by the speed of root being available I would say could be as soon as few months or less.
Big respect for the developers and who keep the community and advancements going. Thanks all!
Does anyone know a way to disable the notification bell with root? Thanks
mmamedov said:
Does anyone know a way to disable the notification bell with root? Thanks
Click to expand...
Click to collapse
I don't think you can disable the bell and keep the lockscreen exactly as it is.
http://forum.xda-developers.com/axon-7/themes/skipping-notification-bell-root-t3441787
Anyone hear if they are going to be developed friendly our like Samsung locked down?
I'm a Nexus user for years & running the great Android O beta rooted already.
eturk01 said:
Anyone hear if they are going to be developed friendly our like Samsung locked down?
I'm a Nexus user for years & running the great Android O beta rooted already.
Click to expand...
Click to collapse
Bump. I wonder the same. Running with my old OnePlus one, all custom software, but have a preorder on a white PH-1....
Given its an unlocked phone, I'd assume the intention is to provide ROOT and encourage development
I really hope so. ??
Sent from my SM-T800 using Tapatalk
I guess we're still waiting on the kernel source and that's why?
eturk01 said:
Anyone hear if they are going to be developed friendly our like Samsung locked down?
Click to expand...
Click to collapse
Cowbell_Guy said:
Given its an unlocked phone, I'd assume the intention is to provide ROOT and encourage development
Click to expand...
Click to collapse
It's carrier unlocked. I haven't heard anything about bootloader unlocked. Which i'm sure it's not, but probably able to unlock easily with "oem unlock" command (hoping anyway). I expect this phone to be easy to unlock, get root, and have a plethora of development. Although it could take some time to get rolling depending on how many devs buy it.
BTW- this thread should be in Discussion or Q & A.
https://www.xda-developers.com/essential-phone-will-have-an-unlockable-bootloader/
Bootloader will be unlockable
The biggest thing is that no one has the phones yet. To really start development we need the phones to extract the firmware and start messing around with the software. Patience, mods will come.
This runs almost completely stock Android, which means we will be abel to do ROMs just like any Nexus/Pixel phone does assuming Essential didnt lock down the "oem unlock" ability. Though they have said in a not 100% official capacity that it will be bootloader unlockable so we should have full ROM and kernel capability .
The bootloader unlock sounds pretty guaranteed, however the roms for Pixel/Nexus devices are built using the official source and kernels released from Google. I wonder how close to stock Essential will run that either they will release sources hopefully close to Google's schedule (which I sort of doubt considering they are launching with 7.1.1 and not 7.1.2) and how much modification their roms may need to run the wireless addon feature and camera on this device. I am hoping we can install and get full functionality out of the Google camera on this device as the stock one does look, limiting, however the wireless addons hopefully will be an easy addon that can be ported to whatever OS builds come down the line..
But like said above, only time and actual hands on can tell.
This thread really doesn't belong in the development section since it's a question it would belong in the Q&A
Anybody getting worried..lol
I'm just hoping for TWRP and Root soon... I'm not in a big hurry for any custom roms.
I'm just hoping that someone could make a custom kernel with gesture support such as dt2w/s2w and wave to activate ambient display.
If this phone doesn't get rooted within my return window, I'm going to be forced to send it back. I can't get by without titanium
Cowbell_Guy said:
If this phone doesn't get rooted within my return window, I'm going to be forced to send it back. I can't get by without titanium
Click to expand...
Click to collapse
All we need is twrp to get root. Hopefully soon.
NeonHD said:
I'm just hoping that someone could make a custom kernel with gesture support such as dt2w/s2w and wave to activate ambient display.
Click to expand...
Click to collapse
YES. Would love this.
Cowbell_Guy said:
If this phone doesn't get rooted within my return window, I'm going to be forced to send it back. I can't get by without titanium
Click to expand...
Click to collapse
Rubin's doing an AMA on Thursday so hopefully we get an answer.
I think we need to wait for the Q&A from Andy tomorrow. That is when we can find out a timeline for when we can get source code to start doing things such as rooting and other modding/ ROM making. Just need to have patience and this phone will take off I think.
Cowbell_Guy said:
If this phone doesn't get rooted within my return window, I'm going to be forced to send it back. I can't get by without titanium
Click to expand...
Click to collapse
This is akin to putting the cart before the horse. Wouldn't it have made more sense to get the phone WHEN root and etc was available for it?
The phone isn't going anywhere..