• 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...

bummpr said:
Now the question is...has any TracFone user applied this update???

Any problems???
Click to expand...

I applied it on my sister's tracfone and it worked just fine but I haven't installed it on mine yet. As far as I know it's a simple fix for the heartbleed bug so they modified the openssl libraries. But I also noticed from the installed-files-verify.txt file in the update.zip that some other things like calculator.apk and browser.apk files have been modifed since their md5 has changed.

I uploaded a comparison report of the installed-files.verify.txt from my un-updated phone and the one I extraced from the update.zip package incase anybody is interested. It just gives an overview of some system files they changed.
 

Attachments

jjfriede said:
I applied it on my sister's tracfone and it worked just fine but I haven't installed it on mine yet. As far as I know it's a simple fix for the heartbleed bug so they modified the openssl libraries. But I also noticed from the installed-files-verify.txt file in the update.zip that some other things like calculator.apk and browser.apk files have been modifed since their md5 has changed.

I uploaded a comparison report of the installed-files.verify.txt from my un-updated phone and the one I extraced from the update.zip package incase anybody is interested. It just gives an overview of some system files they changed.
Click to expand...

Have you seen any noticeable changes in performance or GUI in those apps?
 
I have applied the heartbleed update successfully. I have noticed that the phone seems more unstable. I open Firefox and browse a bit on wifi, and it becomes sluggish and then just closes. Not only Firefox does this, but Chrome and CPU-Z just up and close. I don't know if this has to do with RAM usage, because it seems there isn't much free RAM left (60-100MB), but I have also seem wild swings in RAM usage before the app crashes.

Apps installed are all the default Android and Google stuff and My Account, Firefox, Chrome, TVGuide, iHeartRadio, Accuweather, Solitaire, TWitPro, RadaeePDF and Youtube.
 
benjimt said:
Have you seen any noticeable changes in performance or GUI in those apps?
Click to expand...

As jptech said there are no GUI changes in any of the system apps.

Dk975 said:
I have applied the heartbleed update successfully. I have noticed that the phone seems more unstable. I open Firefox and browse a bit on wifi, and it becomes sluggish and then just closes. Not only Firefox does this, but Chrome and CPU-Z just up and close. I don't know if this has to do with RAM usage, because it seems there isn't much free RAM left (60-100MB), but I have also seem wild swings in RAM usage before the app crashes.

Apps installed are all the default Android and Google stuff and My Account, Firefox, Chrome, TVGuide, iHeartRadio, Accuweather, Solitaire, TWitPro, RadaeePDF and Youtube.
Click to expand...

That is weird, my sister's phone acts completely normal after the update. Maybe something got corrupted during the install process? Check which apps are running in the background maybe an app you installed has a memory leak. If it gets really bad you could try to reset your phone.
 
someone mirror the zip file and i'll take a look at the keys. that way i can get a proper signature and sign a root update and we can try again.
 
I just got an email from ZTE saying the source code was released! Thank you everybody who emailed ZTE for your help! Especially mainefungi for reporting the GPL license violation. And mainefungi, @elliot-labs from github told me to tell you thanks for your work so far since he doesn't have an account here.

Anyways, the source code can be found here Open Source Notices - ZTE Devices - Bringing you closer. It's the top one, the Z665C. Hopefully we'll be able to make more progress now!
 
jjfriede said:
I just got an email from ZTE saying the source code was released! Thank you everybody who emailed ZTE for your help! Especially mainefungi for reporting the GPL license violation. And mainefungi, @elliot-labs from github told me to tell you thanks for your work so far since he doesn't have an account here.

Anyways, the source code can be found here Open Source Notices - ZTE Devices - Bringing you closer. It's the top one, the Z665C. Hopefully we'll be able to make more progress now!
Click to expand...


this is just the kernel source though...

we've already seen what happens when the boot.img is messed with, so...
 
stayboogy said:
this is just the kernel source though...

we've already seen what happens when the boot.img is messed with, so...
Click to expand...

I didn't realize that until I downloaded and unzipped it. From the certificates in the update.zip do you think you'll be able to make a correctly signed update to root the phone?
 
okay test these.

one is signed with the platform key pair, the other with the superuser key pair

using the the secure install method used by zte in their update script of the package

test each one and report results please

(should not damage your phone in any way--if it works it only installs su binary; superuser will still need to be installed if it does work to gain root access)


update-platform-signed

update-superuser-singed


HTML: 
1. rename to update.zip

2. copy to /sdcard

3. reboot into recovery

4. attempt to install

5. if fails, try the second one following the same directions.

6. post results
 
jjfriede said:
I didn't realize that until I downloaded and unzipped it. From the certificates in the update.zip do you think you'll be able to make a correctly signed update to root the phone?
Click to expand...

the certs are not what i needed. there's no way to get the key used from the zip that i'm aware of.

what i was looking for was the secure asserts used in the updater-script of their update. i'm hoping that's all that was preventing them from installing before.

take a look at my previous post for the zips and try them
 
stayboogy said:
okay test these.

one is signed with the platform key pair, the other with the superuser key pair

using the the secure install method used by zte in their update script of the package

test each one and report results please

(should not damage your phone in any way--if it works it only installs su binary; superuser will still need to be installed if it does work to gain root access)


update-platform-signed

update-superuser-singed


HTML: 
1. rename to update.zip

2. copy to /sdcard

3. reboot into recovery

4. attempt to install

5. if fails, try the second one following the same directions.

6. post results
Click to expand...

I tried both packages and the results were the same:
HTML: 
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
Installation aborted
 
jjfriede said:
I tried both packages and the results were the same:
HTML: 
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
Installation aborted
Click to expand...

well, i'm at a loss then... looks like they're using a private key now. zte used just the keys included in the source in older devices.
 
also, i could have told you all that all they would do was release the kernel source

that's all they ever do.

they don't have to release their device tree because it does contain proprietary binary files and source code that they are not legally able to release. things like the akmd source and similar fall into this realm. the device tree is what is needed to really make some progress on rooting.
 
stayboogy said:
also, i could have told you all that all they would do was release the kernel source

that's all they ever do.

they don't have to release their device tree because it does contain proprietary binary files and source code that they are not legally able to release. things like the akmd source and similar fall into this realm. the device tree is what is needed to really make some progress on rooting.
Click to expand...

That's kind of disappointing but at least have the kernel source now which would be helpful if we could root the thing.

I still wonder why the phone behaves so weird. When we gain shell root access and remount /system it always mounts itself back as ro. However on my sister's phone I can mount /system as rw,ro, and back to rw with no problem but no file changes persist reboot. Some people report that they aren't able to mount it successfully at all. I wonder why everybody's phone's act differently even though they should be exactly the same.
 
jjfriede said:
That's kind of disappointing but at least have the kernel source now which would be helpful if we could root the thing.

I still wonder why the phone behaves so weird. When we gain shell root access and remount /system it always mounts itself back as ro. However on my sister's phone I can mount /system as rw,ro, and back to rw with no problem but no file changes persist reboot. Some people report that they aren't able to mount it successfully at all. I wonder why everybody's phone's act differently even though they should be exactly the same.
Click to expand...

alot of the misinformation is because,

some people just don't plain know what's going on when they are going through the so-called temp root method, which isn't, clearly. it just glitches adb through telnet. nothing else. because of this, trusting anything the terminal says regarding the actual condition of the /system partition is foolish at that point. it might tell you that you're user root, but you're a telnet user, nothing more. it might tell you that you have rw access but since no changes persist then it clearly lied to you... what the terminal says and what is actually going on are two different things.

at this point, the only way that i would think that the device could be rooted is to figure out the bootloader and unlock it. the device must have one that verifies the boot.img md5/sha so it needs to be unlocked. if this is done, flashing an insecure boot.img is easily done since we did it before.

at this point though i find it hard to believe no one has cracked this.

check the zte whirl thread here, as someone posted a root method for that phone a week or so ago, which is a sister device to this one
 
stayboogy said:
alot of the misinformation is because,

some people just don't plain know what's going on when they are going through the so-called temp root method, which isn't, clearly. it just glitches adb through telnet. nothing else. because of this, trusting anything the terminal says regarding the actual condition of the /system partition is foolish at that point. it might tell you that you're user root, but you're a telnet user, nothing more. it might tell you that you have rw access but since no changes persist then it clearly lied to you... what the terminal says and what is actually going on are two different things.

at this point, the only way that i would think that the device could be rooted is to figure out the bootloader and unlock it. the device must have one that verifies the boot.img md5/sha so it needs to be unlocked. if this is done, flashing an insecure boot.img is easily done since we did it before.

at this point though i find it hard to believe no one has cracked this.

check the zte whirl thread here, as someone posted a root method for that phone a week or so ago, which is a sister device to this one
Click to expand...

From the telnet session I was able to patch the adbd to allow insecure adb access and i got root access from adb and ran adb remount and it succeeded but still no changes to /system survived reboot.

I think the root method requires framaroot to work but I don't think the 25% battery trick works on the valet and I don't really understand exactly what dcorely did.
 
You must log in or register to reply here.
Back
Top Bottom