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

mainefungi said:
This is something I have never used or done before. How does it work?

I thought fake flash was installed using an update.zip also... So far we have not been able to get any update.zip to install on the valet... All have aborted... How is this different...
Click to expand...

no, it's not the same...

the cyanogenmod sdk, when clockwork recovery is built for a device, builds both a new recovery.img, and a signed and properly packaged update.zip (for the build in question) that temporarily installs the new recovery into the ramdisk, halts the stock recovery and loads the new.

i can't explain to you the difference between the sdk building one and me building one on my own, but there are vast differences between the jelly bean sdk and the gingerbread sdk, and how packages are accepted in recovery due to keys and api versions. it's technical and beyond me at this point, even though i've been all over the code. everything i have built previously has been using the gingerbread sdk, or files that came from the sdk, like the updater-binary which is tied to a particular api version.

just trust me, it's more likely to succeed than the others, and it's honestly our only shot at getting permanent root at this point.
 
mainefungi said:
This is something I have never used or done before. How does it work?

I thought fake flash was installed using an update.zip also... So far we have not been able to get any update.zip to install on the valet... All have aborted... How is this different...
Click to expand...

need the output of

cat /proc/emmc

***may have to be temp rooted for it to give me all i need, not sure though. try without first.

also need an adb pull of

/proc/config.gz
 
stayboogy said:
need the output of

cat /proc/emmc

***may have to be temp rooted for it to give me all i need, not sure though. try without first.

also need an adb pull of

/proc/config.gz
Click to expand...

Still have not gotten my replacement Valet... Perhaps someone can get this done before I do.
 
Unkn0wn0ne said:
This is where I come in...
As root:
cat /proc/emmc
cat: can't open '/proc/emmc': No such file or directory

Here is config.gz: https://drive.google.com/file/d/0B1qPTRYda2ChOUI5bVRjcWJKS28/edit?usp=sharing

Merry Christmas..
Click to expand...

i need a dd of the recovery.img if possible.

it's obtainable from temp root with telnet

need the recovery.fstab out of its ramdisk. it's most likely the same as the whirl, but i'd rather be sure about it.

thanks for the kernel config upload
 
stayboogy said:
i need a dd of the recovery.img if possible.

it's obtainable from temp root with telnet

need the recovery.fstab out of its ramdisk. it's most likely the same as the whirl, but i'd rather be sure about it.

thanks for the kernel config upload
Click to expand...

Way you guys are going you will have root before I get my replacement! LOL
 
stayboogy said:
i need a dd of the recovery.img if possible.

it's obtainable from temp root with telnet

need the recovery.fstab out of its ramdisk. it's most likely the same as the whirl, but i'd rather be sure about it.

thanks for the kernel config upload
Click to expand...

Also hope I can be of some assistance:

Obtained the recovery image by:

/data/local/tmp # dd if=/dev/block/mmcblk0p17 of=/data/local/tmp/valet-stock-rec
overy.img bs=4096
4096+0 records in
4096+0 records out
16777216 bytes (16.0MB) copied, 1.317070 seconds, 12.1MB/s
/data/local/tmp #

The link for the file is below:

https://drive.google.com/file/d/0Bw7b4Sw9CtykdU5JMFo4eEV3ek0/edit?usp=sharing

Since I'm a new user, apparently I can't post links, so here is the URL to paste:

https://drive.google.com/file/d/0Bw7b4Sw9CtykdU5JMFo4eEV3ek0/edit?usp=sharing

Here's the "recovery.fstab" file found under the etc directory in the recovery image:

[HIGH]# Copyright (c) 2011, Code Aurora Forum. All rights reserved.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions are
# met:
# * Redistributions of source code must retain the above copyright
# notice, this list of conditions and the following disclaimer.
# * Redistributions in binary form must reproduce the above
# copyright notice, this list of conditions and the following
# disclaimer in the documentation and/or other materials provided
# with the distribution.
# * Neither the name of Code Aurora Forum, Inc. nor the names of its
# contributors may be used to endorse or promote products derived
# from this software without specific prior written permission.
#
# THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT
# ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS
# BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
# CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
# SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
# BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
# OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN
# IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

# mount point fstype device [device2]

/boot emmc /dev/block/mmcblk0p16
/cache ext4 /dev/block/mmcblk0p21
/data ext4 /dev/block/mmcblk0p22
/recovery emmc /dev/block/mmcblk0p17
/splash emmc /dev/block/mmcblk0p18
/misc emmc /dev/block/mmcblk0p20
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/system ext4 /dev/block/mmcblk0p19
/amss emmc /dev/block/mmcblk0p13
/oemsbl emmc /dev/block/mmcblk0p3
/emmcboot emmc /dev/block/mmcblk0p15
/cefs emmc /dev/block/mmcblk0p11
/qcsblhd_cfgdata emmc /dev/block/mmcblk0p1
/qcsbl emmc /dev/block/mmcblk0p2[/HIGH]
 
karmmisht said:
Also hope I can be of some assistance:

Obtained the recovery image by:

/data/local/tmp # dd if=/dev/block/mmcblk0p17 of=/data/local/tmp/valet-stock-rec
overy.img bs=4096
4096+0 records in
4096+0 records out
16777216 bytes (16.0MB) copied, 1.317070 seconds, 12.1MB/s
/data/local/tmp #

The link for the file is below:

https://drive.google.com/file/d/0Bw7b4Sw9CtykdU5JMFo4eEV3ek0/edit?usp=sharing

Since I'm a new user, apparently I can't post links, so here is the URL to paste:

https://drive.google.com/file/d/0Bw7b4Sw9CtykdU5JMFo4eEV3ek0/edit?usp=sharing

Here's the "recovery.fstab" file found under the etc directory in the recovery image:

[HIGH]# Copyright (c) 2011, Code Aurora Forum. All rights reserved.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions are
# met:
# * Redistributions of source code must retain the above copyright
# notice, this list of conditions and the following disclaimer.
# * Redistributions in binary form must reproduce the above
# copyright notice, this list of conditions and the following
# disclaimer in the documentation and/or other materials provided
# with the distribution.
# * Neither the name of Code Aurora Forum, Inc. nor the names of its
# contributors may be used to endorse or promote products derived
# from this software without specific prior written permission.
#
# THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT
# ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS
# BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
# CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
# SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
# BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
# OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN
# IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

# mount point fstype device [device2]

/boot emmc /dev/block/mmcblk0p16
/cache ext4 /dev/block/mmcblk0p21
/data ext4 /dev/block/mmcblk0p22
/recovery emmc /dev/block/mmcblk0p17
/splash emmc /dev/block/mmcblk0p18
/misc emmc /dev/block/mmcblk0p20
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/system ext4 /dev/block/mmcblk0p19
/amss emmc /dev/block/mmcblk0p13
/oemsbl emmc /dev/block/mmcblk0p3
/emmcboot emmc /dev/block/mmcblk0p15
/cefs emmc /dev/block/mmcblk0p11
/qcsblhd_cfgdata emmc /dev/block/mmcblk0p1
/qcsbl emmc /dev/block/mmcblk0p2[/HIGH]
Click to expand...


this will not permanently change your device

all this does is install a new recovery to stock recovery's ramdisk and runs it

it's temporary


update


attempt to install it from stock recovery and report back please

if it doesn't install, i need the error if there is one

if it does install, does the new recovery load properly?

***do not install anything with it if it does work***
 
stayboogy said:
this will not permanently change your device

all this does is install a new recovery to stock recovery's ramdisk and runs it

it's temporary


update


attempt to install it from stock recovery and report back please

if it doesn't install, i need the error if there is one

if it does install, does the new recovery load properly?

***do not install anything with it if it does work***
Click to expand...

Fails to install mid through verifying package with 'Installation aborted'

This is the last part of the recovery log made by cat /cache/recovery/last_log:

-- Install /sdcard ...
Finding update package...
I:Update location: /sdcard/update.zip
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1738 bytes; signature 1720 bytes from end
E:failed to verify whole-file signature
I:verify_file returned 2
E:signature verification failed
update_eror_code: status = 0x2, error code = 0x5a5a0002
Installation aborted.
 
I just found a file in the /system/etc partition named verify.zip, so I pulled it and discovered the following:

-a file with a list of checksums for all the system file
- another file named "md5checkm
- ZTE's otacert file
- CERT.RSA
- CERT.SF
- MANIFEST.MF

Do we need the file or is it not worth my time?
 
Unkn0wn0ne said:
I just found a file in the /system/etc partition named verify.zip, so I pulled it and discovered the following:

-a file with a list of checksums for all the system file
- another file named "md5checkm
- ZTE's otacert file
- CERT.RSA
- CERT.SF
- MANIFEST.MF

Do we need the file or is it not worth my time?
Click to expand...

thanks for testing that...

now to figure out why it didn't work exactly.

i'd like to take a look at that zip if you want to upload it somewhere.
 
I have an avail 2 that is 4.1.1 and I used cydia impactor to root mine I know this is a zte valet y'all are talking about but it is a good idea to at least try it
 
William Adams ii said:
I have an avail 2 that is 4.1.1 and I used cydia impactor to root mine I know this is a zte valet y'all are talking about but it is a good idea to at least try it
Click to expand...

Thank you... Cydia Impactor has been tried, and it was unable to root.

However, it did allow partial root access through a terminal session over wifi.

However, it has opened the door for us to peak at how the device is running under the hood....
 
Dad mine is soft bricked I can get into recovery and everything but I can't boot up because it boot loops tried flashing a different font and didnt work
 
You must log in or register to reply here.
Back
Top Bottom