• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root i'll help find a root method if...

gmen6981 said:
Done! Mentioned both the Valet and Savvy in my request..........we'll see what happens.
Click to expand...

Thank you!

I fully expect them to send you the copy and paste response they send everyone about it being confidential. Do not get angry with them. Just explain that by using the Android OS for their device they agreed to the terms of the GPL, which states they must make the source code (including any changes they have made) available to the user.

Lets make this happen! :D

EDIT: Do not tell them the reason we need source. If they ask, it is so that we can build apps that are optimized for their build and others like it.

I feel the reason we are not getting full and permanent root is because we have not been able to actually write anything the the /system partition. The /system write protection has been a challenge for other devices (HTC One, Moto X, etc).

For those devices there is/was a key in the prop file "ro.boot.write_protect" which gets re-written by the kernel. This of course means no changes to /system are real or permanent, so no permanent root. The key to fixing the issue with those devices lied in the kernel, and I believe that is where we will find our issue as well.
 
mainefungi said:
Thank you!

I fully expect them to send you the copy and paste response they send everyone about it being confidential. Do not get angry with them. Just explain that by using the Android OS for their device they agreed to the terms of the GPL, which states they must make the source code (including any changes they have made) available to the user.

Lets make this happen! :D

EDIT: Do not tell them the reason we need source. If they ask, it is so that we can build apps that are optimized for their build and others like it.

I feel the reason we are not getting full and permanent root is because we have not been able to actually write anything the the /system partition. The /system write protection has been a challenge for other devices (HTC One, Moto X, etc).

For those devices there is/was a key in the prop file "ro.boot.write_protect" which gets re-written by the kernel. This of course means no changes to /system are real or permanent, so no permanent root. The key to fixing the issue with those devices lied in the kernel, and I believe that is where we will find our issue as well.
Click to expand...

I agree with you, but even if we patched and flashed a modified kernel how could we pass it through the bootloader's verify function that you discovered when you bricked your phone? Is there any way to modify the bootloader?
 
jjfriede said:
I agree with you, but even if we patched and flashed a modified kernel how could we pass it through the bootloader's verify function that you discovered when you bricked your phone? Is there any way to modify the bootloader?
Click to expand...

It may not be as bad as we think. We only assumed it was the bootloader that killed it. There may be something else going on. We were trying to push modified boot and recovery images...

There are a lot of ideas floating around, but I feel my brick may have been related to a mismatch in the modified boot/recovery images. Of course, I could be wrong.

Several people have bricked phones because they were not yet able to see what was really going on in the background... Thus they were grabbing at straws... much like we have been doing.

Access to the source will at least give us a new direction to head. The Amazon Kindle Fire HDX has a locked boo loader (and several have been bricked), yet that did not stop it from being rooted At this point you cannot load a full ROM to it... BUT Hashcode was able to get safestrap working (using Amazon's source code). This is allowing us create and boot into ROM Slots which can be modified safely.

Right now we are driving with one eye closed and steering with our knee... We need to get both hands on the wheel before we can safely reach out destination.

EDIT: There is also a chance we can modify the kernel to 'fool' the bootloader into thinking everything is unchanged. Feeding back what it is expecting to see. This has been done before.
 
mainefungi said:
It may not be as bad as we think. We only assumed it was the bootloader that killed it. There may be something else going on. We were trying to push modified boot and recovery images...

There are a lot of ideas floating around, but I feel my brick may have been related to a mismatch in the modified boot/recovery images. Of course, I could be wrong.

Several people have bricked phones because they were not yet able to see what was really going on in the background... Thus they were grabbing at straws... much like we have been doing.

Access to the source will at least give us a new direction to head. The Amazon Kindle Fire HDX has a locked boo loader (and several have been bricked), yet that did not stop it from being rooted At this point you cannot load a full ROM to it... BUT Hashcode was able to get safestrap working (using Amazon's source code). This is allowing us create and boot into ROM Slots which can be modified safely.

Right now we are driving with one eye closed and steering with our knee... We need to get both hands on the wheel before we can safely reach out destination.

EDIT: There is also a chance we can modify the kernel to 'fool' the bootloader into thinking everything is unchanged. Feeding back what it is expecting to see. This has been done before.
Click to expand...

Sounds good! I haven't gotten anything, not even a generic response to the email I sent ZTE. Anybody else hear anything new from them about releasing the source code?
 
jjfriede said:
Sounds good! I haven't gotten anything, not even a generic response to the email I sent ZTE. Anybody else hear anything new from them about releasing the source code?
Click to expand...

If you (or anyone) feel bold, you can start a Live Chat of your own... It's what I did...

Just click Live Chat... and ask for source code for the Valet and let the games begin :D

Contact Us
 
mainefungi said:
If you (or anyone) feel bold, you can start a Live Chat of your own... It's what I did...

Just click Live Chat... and ask for source code for the Valet and let the games begin :D

Contact Us
Click to expand...

I just got a response from zte along the lines of we don't provide tracfone customers with services, please bother someone else. I'll have to try live chat tomorrow and maybe I'll get better results.
 
jjfriede said:
I just got a response from zte along the lines of we don't provide tracfone customers with services, please bother someone else. I'll have to try live chat tomorrow and maybe I'll get better results.
Click to expand...

LOL, I am not surprised. They are hoping you will accept that and go away. Do what you like, but if it were me, I would reply with something along the lines of...


Tracfone only provides the service for the device. ZTE designed the hardware, provided the software (including the Kernel), they did so using the Android Operating System, which falls under GPL. In order to be GPL compliant they must make available the source code for their modified version of the software.

Provide them the URL...

https://www.gnu.org/licenses/gpl.html

Heck, point them to their own URL

Site the Preamble...

"For example, if you distribute copies of such a program, whether gratis or for a fee, you must pass on to the recipients the same freedoms that you received. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights."

Site Section 6 of the Terms and Conditions...

"Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying."

Last, but not least... Let them of if they refuse to follow the GPL Agreement, you will have no choice but to send an email to license-violation@gnu.org, requesting that they open an investigation.

I am sure they will cave if they get enough pressure... They caved for the Vital. It is easier for them to cave then to keep handling all the inquiries.
 
mainefungi said:
LOL, I am not surprised. They are hoping you will accept that and go away. Do what you like, but if it were me, I would reply with something along the lines of...


Tracfone only provides the service for the device. ZTE designed the hardware, provided the software (including the Kernel), they did so using the Android Operating System, which falls under GPL. In order to be GPL compliant they must make available the source code for their modified version of the software.

Provide them the URL...

https://www.gnu.org/licenses/gpl.html

Heck, point them to their own URL

Site the Preamble...

"For example, if you distribute copies of such a program, whether gratis or for a fee, you must pass on to the recipients the same freedoms that you received. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights."

Site Section 6 of the Terms and Conditions...

"Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying."

Last, but not least... Let them of if they refuse to follow the GPL Agreement, you will have no choice but to send an email to license-violation@gnu.org, requesting that they open an investigation.

I am sure they will cave if they get enough pressure... They caved for the Vital. It is easier for them to cave then to keep handling all the inquiries.
Click to expand...

Thanks for the ammo! I actually emailed them about an hour ago clarifying my request to the source code and that I don't want 'services' so i can at least get them off their copy-and-paste script. Once I have them listening I'll definitely make them read their own policy that I didn't even know existed until you posted that link! On a second thought I doubt they even know their own policy on Open Source code either.
 
jjfriede said:
Thanks for the ammo! I actually emailed them about an hour ago clarifying my request to the source code and that I don't want 'services' so i can at least get them off their copy-and-paste script. Once I have them listening I'll definitely make them read their own policy that I didn't even know existed until you posted that link! On a second thought I doubt they even know their own policy on Open Source code either.
Click to expand...

Don't be fooled, its not their policy... That is the a direct copy from GPL V 2.0 my friend...

If you really want a laugh, scroll all the way to the bottom of their page...

"To obtain the source code covered under above licenses, please visit http://opensource.ztedevice.com , or you can contact us through the email tech.sp@zte.com.cn."

Seriously... Take a look :stupid:

:boxing: :boxing: :boxing: :boxing:

Truth be told, I have not emailed that address yet... Still waiting for my response I was promised for sometime early this week...
 
mainefungi said:
Don't be fooled, its not their policy... That is the a direct copy from GPL V 2.0 my friend...

If you really want a laugh, scroll all the way to the bottom of their page...

"To obtain the source code covered under above licenses, please visit http://opensource.ztedevice.com , or you can contact us through the email tech.sp@zte.com.cn."

Seriously... Take a look :stupid:

:boxing: :boxing: :boxing: :boxing:

Truth be told, I have not emailed that address yet... Still waiting for my response I was promised for sometime early this week...
Click to expand...

Good luck getting that response XD. After reading this i decided to jump the gun sent this to that email address:

Hello! I was referred to this email address by the following webpage: http://resource.ztedevices.com/uploadfiles/copyright/mobilephones/ZTE——NOTICE.html

At the bottom of that webpage it says, "To obtain the source code covered under above licenses, please visit http://opensource.ztedevice.com , or you can contact us through the email tech.sp@zte.com.cn." I could not find the source code for the Z665C at opensource.ztedevice.com so I am emailing you to request a copy as ZTE is required to do so under the GNU General Public License.

thank you

It seems very blunt and straightforward but I'm sick of getting blown off with those cheesy 'dear valued zte customer' emails :P
 
jjfriede said:
Sounds good! I haven't gotten anything, not even a generic response to the email I sent ZTE. Anybody else hear anything new from them about releasing the source code?
Click to expand...
Got a reply this morning. After the usual "Dear valued Customer" stuff, they informed me that after verifying it with their engineering team, that the source code is proprietary and they are not releasing it. I'll try again later reminding them that they are required to release it under terms of the agreement. We really need to get everyone trying to contact them about this!
 
jjfriede said:
I tried using the live chat feature at Contact Us
Here is what i got:


Now I just have to wait for an email
Click to expand...

Sweet!

I also sent a email to the tech.sp@zte.com.cn address, even though I have not heard anything more yet...

I am not buying the whole proprietary garbage mentioned earlier... For the Apps installed, perhaps... but for any part of the OS that they simply modified to fit their needs (Like the Kernel) They must provide the source code. Neither ZTE, or Tracfone are above that requirement...
 
Anybody else get any kind of reply? Isent an additional message citing the links on their own site along with other links to the GPL etc. This afternoon I got a reply stating that " You will receive a reply after your concerns are forwarded to the correct dept." In other words.....a runaround.
 
gmen6981 said:
Anybody else get any kind of reply? Isent an additional message citing the links on their own site along with other links to the GPL etc. This afternoon I got a reply stating that " You will receive a reply after your concerns are forwarded to the correct dept." In other words.....a runaround.
Click to expand...

That is more than I have gotten. And I even followed up with an email. I have heard nothing since their call last week. It is pathetic.
 
hmmm!

ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0

wouldn't we want that -
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1

8a757976-0836-11e4-9efd-b5445ce4daa4.png


Default.prop can be seen here ^ isn't that really inside the bootloader ?
 
defrag said:
hmmm!

ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0

wouldn't we want that -
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1
Click to expand...


It is not so much as knowing what to change, as it is getting changes to stick. Changes made under pseudo temp root are gone on reboot, and the bootloader is locked so no changes can be made there.

One thing is for sure, access to the Kernel source code could at least help us see what is really going on in the background.
 
Okay, so just a quick update. Today I got a response from GNU on my GPL violation report. He seemed very interested in pursuing this, and asked me for the chat log. I send him what I had, and will give another update as soon as I know more.

:D
 
mainefungi said:
Okay, so just a quick update. Today I got a response from GNU on my GPL violation report. He seemed very interested in pursuing this, and asked me for the chat log. I send him what I had, and will give another update as soon as I know more.

:D
Click to expand...

Great! I wonder what will happen next
 
You must log in or register to reply here.
Back
Top Bottom