Database Info

RFS to EXT4

I understand that most one click lagfix apps wont work right away for the DROID Charge, so I would like to start learning how to convert from rfs to ext4 safely and maybe make an app for the phone. Any devs that can give me some advice or instructions would be nice! Thanks guys

jism31 said:
I understand that most one click lagfix apps wont work right away for the DROID Charge, so I would like to start learning how to convert from rfs to ext4 safely and maybe make an app for the phone. Any devs that can give me some advice or instructions would be nice! Thanks guys
Click to expand...
Click to collapse
I believe it will take a voodoo kernel. Is how it works on the fascinate.

I hope some of the Fascinate Devs roll over to this device so we can get some of their past work on it.

RaptorMD said:
I hope some of the Fascinate Devs roll over to this device so we can get some of their past work on it.
Click to expand...
Click to collapse
If you guys can get me a Charge, I'd be more than willing to take my work from the Fascinate and get it going on the Charge Also, I'm sure Voodoo lagfix can be made to work, and Voodoo Sound will also work. not sure about color though due to the different display that is being used. Applying the color fix may actually make it look worse, though supercurio would probably be the person to ask about that one.

I'm sure once it hits many will gather round the devs to support them in their cause, I know I will.

RaptorMD said:
I'm sure once it hits many will gather round the devs to support them in their cause, I know I will.
Click to expand...
Click to collapse
If someone can get me the kernel, I can get you guys CWM and a cleaned up ROM. Not sure how functional CWM will be, but we can work out the bugs then after people can test it.

If you can tell me how to get you the kernel I can get it for you. I work for Verizon and I am trying to slowly learn the developer process. Let me know

jism31 said:
If you can tell me how to get you the kernel I can get it for you. I work for Verizon and I am trying to slowly learn the developer process. Let me know
Click to expand...
Click to collapse
Well, you'd need a rooted device, and after that, you should be able to use dd to get it, but I'm not completely sure where it resides yet. The partitions aren't the same as the Fascinate and Continuum, and I'm guessing it's due to the LTE radio. You could just dump 3 partitions to see which are the correct ones I guess. Via adb, here is the sequence of commands you'd use:
Code:
adb shell
su
dd if=/dev/block/bml7 of=/sdcard/bml7 bs=4096
dd if=/dev/block/bml8 of=/sdcard/bml8 bs=4096
dd if=/dev/block/bml9 of=/sdcard/bml9 bs=4096
exit
exit
adb pull /sdcard/bml7
adb pull /sdcard/bml8
adb pull /sdcard/bml9
Then just tar/zip/7z/whatever the files and put them on a file sharing site and send me the link to them. Just a note that while this shouldn't cause any issues as far as breaking your phone, there is always that possibility, so just be aware of that fact as I'm not responsible if it breaks.

I know there is a user over at android central who is rooted already on his lucky Charge. You should cross-post there and if other are not yet comfortable with rooting, which I do understand.

Voodoo lagfix is a piece of cake, did that a few months ago Lost all the files I had though
Somebody dump their zImage (bml7), and it can be easily hacked in. Will take some rewriting of the lagfix code to merge with mainline cuz the partitions are much different (system/data/cache, all of em are different than other sgs devices), but whipping up a usable kernel is stupid easy, recovery should not be difficult either.
Sent from my SCH-I500 using XDA App

Something I'd like to see is Voodoo's color fix on the super amoled plus screen. They are always just a bit off with colors.

imnuts said:
Well, you'd need a rooted device, and after that, you should be able to use dd to get it, but I'm not completely sure where it resides yet. The partitions aren't the same as the Fascinate and Continuum, and I'm guessing it's due to the LTE radio. You could just dump 3 partitions to see which are the correct ones I guess. Via adb, here is the sequence of commands you'd use:
Code:
adb shell
su
dd if=/dev/block/bml7 of=/sdcard/bml7 bs=4096
dd if=/dev/block/bml8 of=/sdcard/bml8 bs=4096
dd if=/dev/block/bml9 of=/sdcard/bml9 bs=4096
exit
exit
adb pull /sdcard/bml7
adb pull /sdcard/bml8
adb pull /sdcard/bml9
Then just tar/zip/7z/whatever the files and put them on a file sharing site and send me the link to them. Just a note that while this shouldn't cause any issues as far as breaking your phone, there is always that possibility, so just be aware of that fact as I'm not responsible if it breaks.
Click to expand...
Click to collapse
I just tried this and I am getting permission denied. I would really like to help but I don't have much knowledge on adb.

I remember reading somewhere (blog) Samsung had released the SDK for the Charge a couple weeks before the original scheduled launch. I may have downloaded it. If not, I can ask my Samsung contact if he can score it for me.
Sent from my Droid Charge using XDA Premium

Go to opensource.samsung.com, go to mobile->mobile phone, and scroll to SCH-I510 and download the source code. That should be everything you need, right?
I would love to post the link directly to the zip file, but I'm not allowed to, having fewer that 8 posts.

moondrius said:
I just tried this and I am getting permission denied. I would really like to help but I don't have much knowledge on adb.
Click to expand...
Click to collapse
After you type in SU, the prompt should go from a '$' to a '#' if it doesn't, then you won't be able to use dd

Yeah thats the problem.

moondrius said:
Yeah thats the problem.
Click to expand...
Click to collapse
When the phone is plugged in and you go to use adb shell, have it up at the home screen. Then type in su and press enter with the home screen still up. Superuser may have captured the event and prevented it from going to root in adb shell until you allow it. If it did, you should see a prompt show up on the screen about allow/deny for root access just after pressing enter for root access. Allow it, and then you should be able to continue.

Thanks a lot, I was able to pull that from the Charge.
http://www.mediafire.com/?kg66bb6cms9m62m

Ok, well I guess its time to put out a call to arms. I am not as familiar with imnuts work on the Fascinate, I had it for about 3 days and returned it. I am more than willing to donate to the Droid Charge cause.
What types of customizations can you bring over to the Charge (assuming it actually goes on sale this year) from the Fascinate? How far away are you from reaching your goal of being able to purchase a Charge, I know retail is up there (that's how I am getting it as well)?

RaptorMD said:
Ok, well I guess its time to put out a call to arms. I am not as familiar with imnuts work on the Fascinate, I had it for about 3 days and returned it. I am more than willing to donate to the Droid Charge cause.
What types of customizations can you bring over to the Charge (assuming it actually goes on sale this year) from the Fascinate? How far away are you from reaching your goal of being able to purchase a Charge, I know retail is up there (that's how I am getting it as well)?
Click to expand...
Click to collapse
imnuts is a pretty prolific dev. I can remember him from the eclair days.
Come onto irc and you can talk to him directly.

Easy root method (Triumph is Factory rooted)

Found this over at SDX Developers
It's so easy a caveman can do it.
http://forum.sdx-developers.com/index.php?topic=17172.0

Be aware that if you do this you have no control over what has root and what doesn't. The "gingerbreak" way, along with the Android SU, does.

couldn't a person just install superuser?

Intercepter said:
couldn't a person just install superuser?
Click to expand...
Click to collapse
yes you can.... ive tested all of the ways of rooting this phone and this one is the easiest! after you do it just install superuser from the market and your all good.

Hey that's my post lol! Yeah well the thing about malware and root access that no one hardly knows is that all these apps that use root exploits to cause harm, they never request su permissions because they use there own exploit to gain root. So superuser wouldn't prompt you on an exploit root being ran. Superuser just prompts when some app requests /system/bin/su or /system/xbin/su. If you want to keep your phone safe its a mater of knowing what you install on your phone. Even with superuser your not safe from root exploit attacks!
Me personally I like nit having to allow everytime I install a new root app. And I know what I install so I never worry about malware.
Sent from my MOTWX435KT using Tapatalk

I noticed that his fix is to basically link su to sudo, which allows "root" programs to run the included superuser applet.
So does this mean someone could just install the SuperUser app without going through the usual rooting process? Is Gingerbreaking unnecessary then?
what concerns me is that if these phones ship with sudo enabled and no root password, then any app can get root without any special effort. That means the Triump is VERY insecure. I'm wondering if we can safely remove sudo and solve that particular problem.

Maybe they did that to make fixing them easier, for when a phone got sent in they could gain root and do whatever they need in it, then turn it back off real quick. This is kinda like the tether menu being hidden but not removed on the OV. How stupid do they think people are?

I don't think it's a question of stupidity - it's more one of knowledge. They don't anticipate the run-of-the-mill user to be digging through the file structure of the phone for something they have no idea of what it does or how it works.
And I'd have to agree - the non-technical people have no desire to start digging through the phone, but rather, to use it as is.

Therefore......
So if this could be made a script. Then we could un-root just as easily for protection. I only need it for barnacle.
root
--------
sudo
ln -s /system/xbin/sudo /system/xbin/su
ln -s /system/xbin/sudo /system/bin/su
unroot
-------
sudo
rm /system/xbin/su
rm /system/bin/su
RIGHT?

Edit: the "shebang" line needs to be changed. Not sure to what. You may be better off just typing in the commands yourself.
Not tested, but this should work.
The root script:
Code:
#!/bin/sh
#filename: rootme
echo "Rooting Device"
sudo
ln -s /system/xbin/sudo /system/xbin/su
ln -s /system/xbin/sudo /system/bin/su
echo 'Root has been achieved'
The unroot script:
Code:
#!/bin/sh
#filename: unrootme
echo "Un-rooting Device"
sudo
rm /system/xbin/sudo /system/xbin/su
rm /system/xbin/sudo /system/bin/su
echo 'Un-root has been achieved'
Make these files somewhere and *cd* to that directory. Type either
Code:
./rootme
or
Code:
./unrootme
Hope this helps someone.

TomXP411 said:
I noticed that his fix is to basically link su to sudo, which allows "root" programs to run the included superuser applet.
So does this mean someone could just install the SuperUser app without going through the usual rooting process? Is Gingerbreaking unnecessary then?
what concerns me is that if these phones ship with sudo enabled and no root password, then any app can get root without any special effort. That means the Triump is VERY insecure. I'm wondering if we can safely remove sudo and solve that particular problem.
Click to expand...
Click to collapse
Yes, that is true that an app could very easily gain root access on the triumph. HOWEVER, as pointed out by b_randon14 above, practically all malware apps use a root exploit to gain root priveliges. This means that even an unrooted device is susceptible. As an example, take a stock samsung captivate. It has no root, and no way to gain root, without flashing a custom rom/kernel. However, if an app used the psneuter exploit, it could still gain root access. (Btw, that is how I originally rooted my captivate, using super one click with the psneauter exploit)
So really, the triumph is no less secure than any other android device. Plus, the triumph is the only android device, aside from dev phones such as the nexus one/nexus s that come pre-rooted. So a triumph specific malware app would have to be written.
Personaly, I like the su+superuser.apk method of rooting, but that is because it is the only method I have ever used. And remember, if you prefer to have su+superuser.apk, you either use gingerbreak, or just use this trick and then install superuser.apk.
Sent from my SAMSUNG-SGH-I897

Yeah and plus an app has to be designed to gain root its not like any old app can just up and decide to request root and start destroying! And stock without any root(I.e. my method or gingerbreak) an app doesn't call /system/xbin/sudo it would call /system/bin/su or /system/xbin/su. Plus I mean if you used gingerbreak you should realize that an app can get root without going through superusrr or calling on su. I mean how else do you think gingrrbreak app gets root in the first place to copy su and superuser? Through the gingerbreak root exploit!!
Sent from my OC'ed Triumph!

The concept of an app being able to gain root makes it just as dangerous as a malignant virus for Android. The only difference is, it's not a virus. It's a nice, helpful, and otherwise very good program. Lucky for us.
I'm working on a batch script that does the same thing as these instructions, anybody vaguely interested in using it (should it be put out)?

primetechv2 said:
The concept of an app being able to gain root makes it just as dangerous as a malignant virus for Android. The only difference is, it's not a virus. It's a nice, helpful, and otherwise very good program. Lucky for us.
I'm working on a batch script that does the same thing as these instructions, anybody vaguely interested in using it (should it be put out)?
Click to expand...
Click to collapse
I wrote one and posted on xda, I think, but the shebang line needs some adjustment to find sh. Hope that helps.
Sent from my rooted Moto Triumph

Why is this not working for me? I downloaded terminal emulator from the market, typed: "sudo" and get:
sudo: permission denied
$

tsac said:
Why is this not working for me? I downloaded terminal emulator from the market, typed: "sudo" and get:
sudo: permission denied
$
Click to expand...
Click to collapse
Did they patch it? These two lines of code run from ADB should "root" the device... and sudo is just there.
adb -d shell sudo ln ln -s /system/xbin/sudo /system/xbin/su
adb -d shell sudo ln ln -s /system/xbin/sudo /system/bin/su
Now you may not be able to run "sudo" alone, you may need to specify a command with it too? Unfortunately I can't try it again, because all of my phones are rooted now
In the event this didn't work, GingerBreak should work regardless.

I'll give it a try when my phone finishes charging.....Thank you

tsac said:
I'll give it a try when my phone finishes charging.....Thank you
Click to expand...
Click to collapse
Sure. although I would still recommend Gingerbreak instead...it's more complete and contains Superuser as an extra security measure.
Sent from my MOTWX435KT using Tapatalk

Never got to try anything....Phones screen is dead. You know how people describe the flashing screen when turned on and off? Well mine flashed once and it has not worked since... Hopefully virgin mobile will honor the 1 year factory warranty. I did absolutely nothing to this phone. It just took a crap. Removal of battery does nothing. Phone will receive calls but there is nothing but a backlight. Tried several different methods. Horrible phone....Should be recalled
Thanks for your trying to help me.
Sent from my reliable homebuilt gaming rig using FireFox

rooted my dad's triumph...question though...couldn't I flash clockworkmod via rom manager or do I have to go the long way?
edit: nvm, i see rom manager doesn't support the triumph

Root and downgrade for Android 2.3.4 {Script included - ShiftySonofA script dl added)

Well, I'm writing this thread because I happily have a root method that doesn't require HTC unlock and you can downgrade to 2.2. Let's get into the information about it:
Required:
ADB
PG06IMG.zip {Downgraded version}
misc.img * {md5sum = c88dd947eb3b36eec90503a3525ae0de}
tacoroot *
*included in zip file
Instructions:
Alright, for this you will need to run the following commands:
Code:
adb push tacoroot.sh /data/local/tmp/taco
adb shell chmod 755 /data/local/tmp/taco
adb shell sh /data/local/tmp/taco --setup
[COLOR="Red"]YOU NEED TO Hit Vol up + Vol Down + Power all at once after it goes into recovery![/COLOR]
After it reboots type:
Code:
adb shell sh /data/local/tmp/taco --root
and then you use
Code:
adb shell dd if=/sdcard/misc.img of=/dev/block/mmcblk0p17
Pull your battery after you check the md5sum of the img by using adb shell md5sum /dev/block/mmcblk0p17
and then reboot into hboot to downgrade
Download here
Script Download, features, changelog is in this post
credits:
Misc.img file: OTAKing (Ohai buddeh)
tacoroot: jcase

Well looks like someone has been at work.

I never doubted you buddy! Good work! Thanks!
Sent from my PG06100

Nice work as always.
Sent from my HTC Evo Shift using Tapatalk

You never cease to amaze young Padawan!!
Just imagine If they could of waited a little longer! Lmao!

Indirect for the win!!!

Script information:
This one is called ShiftySonOfA
It is basically Fre3atlast rewritten for this with about 3/4ths of it changed. Enjoy.
Download link:
here
Features:
Code:
MD5 Check
Easy to use
Includes all information needed
Offers download for EXE or Zip for RUU back to froyo.
Version Changelog:
Code:
1.0: Initial Release

Anyone think we can get this stickied? It's pretty important. :|

You got it...
Sent from my PG06100

Indirect said:
Anyone think we can get this stickied? It's pretty important. :|
Click to expand...
Click to collapse
Done.
EDIT: I've created a single sticky which links to all other stickies. We had about 6 so it needed to be tidied up.

Thanks once again Indirect
TEAM MiK
MikROMs Since 3/13/11

Glad to help out where I started developing.
Sent from my Nexus S 4G using xda premium

Indirect said:
Glad to help out where I started developing.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
I'm just glad your still helping out
TEAM MiK
MikROMs Since 3/13/11

He told me he is too scared to ask anyone for a donation for a shift, he will work on roms if he can get his hands on one, any takers?

gigermunit said:
He told me he is too scared to ask anyone for a donation for a shift, he will work on roms if he can get his hands on one, any takers?
Click to expand...
Click to collapse
Because I knew everyone would say no.

If I had an extra one, you'd be welcome to it. Your work kicks ass.
Sent from my Supremely Shifted Speedy.

I honestly have a extra shift but have been trying to sell it times are tough at the moment, thing is less then 6 months old and doesn't even get used back in the box mint...
Just don't think I'm comin off as a ****, if I could donate bro I define would just can't afford to...
Sent from my PG06100 using Tapatalk

Indirect said:
Because I knew everyone would say no.
Click to expand...
Click to collapse
Im considering reporting my current shift lost and sending it to you.
but after I get money to pay for a replacement lol

guys, look on the bright side: If I have a donated shift, I can also try to develop a root for the rom instead of having to downgrade. I already have some ideas but I need to test on latest version. :|

Indirect said:
... I happily have a root method that doesn't require HTC unlock and you can downgrade to 2.2.
Click to expand...
Click to collapse
Thanks for this! I was able to use the temp root to "adb pull" the entirety of the (kernel visible) flash, as well as the /boot, /system, WiMax, and /data partitions (after remounting r/o). Because of that, after I'd downgraded (which seems really unnecessary JUST to get to a flashable HBoot, but that's another topic), I was able to flash back the new radios and touchscreen firmware (as seen in another thread), then flash the CWM recovery, which let me reflash /system and /data from my previously-unlocked Shift (and Nandroid that for future use, as well). After modifying the stock 2.3.4 /boot to set ro.secure to "0" then flashing that with fastboot, then pushing Superuser.apk and the "su" binary, I was exactly back to where I was before (which was VERY important to me, I didn't want to have to start over from a clean wipe), except now I have root- so I was able to use TiBu to move stuff that was ordinarily marked "Phone Only" to the SD-Card, freeing up some space (which along with how slow this phone is and how little memory it's got are my major gripes with the Shift).
(TL;DR: I now have root and didn't lose anything I had before I started).
It's nice to have the TiBu and Nandroids, too- despite the glowing reviews I read here, I seriously dislike this handset, but I hear there's ROMs out there that make this thing usable. So, now I get to try 'em, and always go back if they're no better after all.

[Q] How To, If Possible, Root With Bad Volume Keys

So, I'm attempting to root a Charge that the volume keys do not work. Apparently, 1 and 2 year olds who have great throwing ability is something the Charge, well, anything really, doesn't exactly appreciate. Normally, I root by going into the download mode, and flashing CWM, then installing the ROM. Obviously, not happening here.
My question is, has someone with more knowledge than I figured out how to accomplish this? Its running stock FP5. I really don't want to send it in because of the contract timing and wasteful of money. I'm also willing to experiment replacing parts, if someone knows anything about it...
Thanks.
Sent from my SCH-I510 (Tweaked 3.0) using xda premium

Yep. There's a jig that will force the phone into dl mode. IIRC it's branded for the gnex but it's confirmed to work on the Charge as well. http://forum.xda-developers.com/showthread.php?p=27533069
Sent from my SCH-I535 using Tapatalk 2

Hey, I had a thought of using ADB to root, and somehow forcing CWM on it, then using an app to boot it into dl mode. I've never used and before and don't know if it's possible, although, from what I read, it seems plausible. Can you offer any insight on this idea?
Sent from my SCH-I510 using xda

edji-x said:
Hey, I had a thought of using ADB to root, and somehow forcing CWM on it, then using an app to boot it into dl mode. I've never used and before and don't know if it's possible, although, from what I read, it seems plausible. Can you offer any insight on this idea?
Sent from my SCH-I510 using xda
Click to expand...
Click to collapse
If you have adb all set up and it properly recognizes your phone (something comes up when putting in the adb devices command) you can boot into download mode with
adb reboot download

Actually it's something I looked into recently for another member. I'm not saying it's not possible but I don't think we have the right tools for it. Originally ginger root was used via adb to root the charge but that's not going to work with our version of gb (assuming you could still find it). I'm not sure the format of cwm will work either. I'm not really proficient with adb so someone with more expertise might be able to get you going.
Sent from my Nexus 7 using Tapatalk 2

Awesome. I don't have it installed yet, but it doesn't look like it takes much to make it work. Plus, I have nine that isn't screwed up, so I think I'll see what I can come up with later.
On a side note, I can't post a reply to your tweaked 3.1 thread, but I ran into somewhat of a problem... run tweaktools, did the tweaks thing, phone BARELY would run. I also couldn't get a shell to run to get back in to uninstall. What I ended up doing to fix was a reinstall of SuperSU and installing a bash shell off a different emulator to get back into tweaktools. This was after I played in /system/etc/init.d awhile trying my hand at fixing it. Thought you may want/need to knoknow.
Sent from my SCH-I510 using xda

By the way, thanks for the tip. I'll report one way or another in a day or 2.
Sent from my SCH-I510 using xda premium

edji-x said:
On a side note, I can't post a reply to your tweaked 3.1 thread
Click to expand...
Click to collapse
You need 10 posts minimum to post in the Dev forums, XDA's rules.
Sent from my Droid Charge running [email protected] 3.2a enhanced by dSlice's Scripts & Tweaks

edji-x said:
Awesome. I don't have it installed yet, but it doesn't look like it takes much to make it work. Plus, I have nine that isn't screwed up, so I think I'll see what I can come up with later.
On a side note, I can't post a reply to your tweaked 3.1 thread, but I ran into somewhat of a problem... run tweaktools, did the tweaks thing, phone BARELY would run. I also couldn't get a shell to run to get back in to uninstall. What I ended up doing to fix was a reinstall of SuperSU and installing a bash shell off a different emulator to get back into tweaktools. This was after I played in /system/etc/init.d awhile trying my hand at fixing it. Thought you may want/need to knoknow.
Sent from my SCH-I510 using xda
Click to expand...
Click to collapse
Sorry to hear of the troubles - not sure what would have caused the issue with tweaktools. You weren't able to su, or you weren't able to open terminal emulator? What were you messing with specifically in the tweaks?

dwitherell said:
If you have adb all set up and it properly recognizes your phone (something comes up when putting in the adb devices command) you can boot into download mode with
adb reboot download
Click to expand...
Click to collapse
:banghead:
Sigh, I don't know why I didn't think of that lol. And I was Ninja'd. Double whammy lol
Sent from my SCH-I535 using Tapatalk 2

Okay, Found it in ADB, and am able to reboot into download, so all is well, I think.
On the tweaktools issue, I kinda did something like this...One tweak does okay, so lets install ALL of them....after that, performed the reboot, and everything went very sloooow. So, I tried to get into a term emulator, and nothing happened, the shell wouldn't even start. Blank screen. So, I tried a different outside of ROM toolbox. Nothing. So, I played around with the settings here and there, and still nothing. I then went into root browser, and started trying to manually move the tweaks out, nothing different. So, I downloaded another term emulator, "Better Terminal Emulator" and got a bash shell to at least open, was able to get into tweaktools, erase all tweaks, clear downloads. But the shells still weren't operating right. They'd open and run, but nothing would show on screen. So, a erase/reinstall of SuperSU, everything good....LOL

Well, maybe it'll help, maybe not, but here's the path I used to do this:
Visit samsung's site for the ADB download and install to c:\android-sdk\ (default)
Put USB Debugging on in phone
Start up command line and Odin 1.82
issue following in command line (notably in the c:\android-sdk\platform-tools)
Code:
adb reboot download
Odin up some Tweaked 2.2 with recovery and kernel for root
once rebooted, issue the following in ADB shell:
Code:
adb shell
su (Checked phone to be sure root was granted)
cd /data
rm -R *
cd /cache
rm -R *
cd /dbdata rm -R *
reboot, then adb reboot download.
Flashed EP4 Stock, updated,
Updated to FP5E
Once again, USB debug, adb reboot download, and Odin Tweaked 3.1 with 0302,
follow above code again, reboot, and I think I have it right....
Since the volume keys don't work on here, is there a way to screw around in the recovery mode via ADB rather than only the keys? I see ADB sees the phone in recovery, and seems to want to connect with it....Second is, is there a way to play with this in the *nix enviroment? I also have been searching for the Gingerbreak, etc to root this thing on stock, but haven't been able to do it....and last, is there a way to do a data wipe other than what I did, and think i accomplished with ADB?
Thanks

With the CWM that I am using, you can use the hard buttons at the bottom of the phone to navigate.
Sent from my SCH-I510 using Xparent Red Tapatalk 2

[Q] Root ZTE Valet Z665c

Does anyone have any information on how to root this phone?
It is a tracfone running Android 4.1 with 1ghz qualcomm cpu.
Thanks.

I'm also looking for someone who might have some pointers on how to root this phone or install KitKat apps from Nexus 5 dump!!!
I know it is a low end phone but there are lots of people in the Tracfone world who are now able to get Android phones and are NEW to the smartphone universe.
Thanks.

I'm thinking of buying this phone. As a low end Android, how does it hold up? And if you want to root it, try Bin4ry's root method here. Just be careful.

Tried Bin4ry on ZTE Valet but it failed to root
I've had the phone a couple of days so far and while I'm by no means a qualified reviewer of smartphones, I do like the ZTE Valet. I'm too cheap to pay the $70-100 USD/month for a post-paid service that I don't need.
After searching the forums and seeing that no one reported trying to root the phone, I took a brave pill and tried the Bin4ry method (v31). I got the same message that many users reported - after rebooting, it fails to mount and copy the necessary files. Both the new standard method and the old method failed. It did no apparent harm to the phone - just didn't work. Here's some details on the phone I have:
Android version 4.1.1
Kernel 3.4.0-perf [email protected]
Thanks for any ideas or advice.

I just picked one up at Kmart for $80 today and am checking things out, trying to see about rooting it. My Hisense Sero 7 Pro tab is rooted and running great with a DoPa custom ROM.

I also purchased one of these and am happy so far. I have a question on the magnetic and rotation sensor. They seem to show up as installed as ak8962 devices but apps like 'my android sensors' don't show any data being returned. are they just not actually installed?
thanks
sam
gberpa said:
I just picked one up at Kmart for $80 today and am checking things out, trying to see about rooting it. My Hisense Sero 7 Pro tab is rooted and running great with a DoPa custom ROM.
Click to expand...
Click to collapse

samcoinc said:
I also purchased one of these and am happy so far. I have a question on the magnetic and rotation sensor. They seem to show up as installed as ak8962 devices but apps like 'my android sensors' don't show any data being returned. are they just not actually installed?
thanks
sam
Click to expand...
Click to collapse
The rotation of the device changes the screen from portrait to landscape and 'maps', 'Gas Buddy' seems to show the right direction for magnetic north. I haven't had much time to check yet. AAMF, I haven't activated or transferred my number to the 'phone' yet as am deciding if is a 'keeper'. So far, I think it is as I can use WiFi and 'turn off' mobile data by option. Now checking things like battery life in standby.. Haven't found an option to shut WiFi when screen is off like in my JB 4.2.1 and HC 3.1 devices. Only seem to be able to turn WiFi on or off or see an option for airplane mode.

I agree - the screen rotates (how - I don't know ) I would assume gas buddy is using GPS to find north.
sam
gberpa said:
The rotation of the device changes the screen from portrait to landscape and 'maps', 'Gas Buddy' seems to show the right direction for magnetic north. I haven't had much time to check yet. AAMF, I haven't activated or transferred my number to the 'phone' yet as am deciding if is a 'keeper'. So far, I think it is as I can use WiFi and 'turn off' mobile data by option. Now checking things like battery life in standby.. Haven't found an option to shut WiFi when screen is off like in my JB 4.2.1 and HC 3.1 devices. Only seem to be able to turn WiFi on or off or see an option for airplane mode.
Click to expand...
Click to collapse

Any update on this?

It isn't looking good so far..
http://androidforums.com/zte-valet/799676-ill-help-find-root-method-if.html
They have tried a bunch of stuff so far.
sam
Unkn0wn0ne said:
Any update on this?
Click to expand...
Click to collapse

samcoinc said:
It isn't looking good so far..
They have tried a bunch of stuff so far.
sam
Click to expand...
Click to collapse
I'm going to get my hands on the phone soon. I'll proceed to attempt to get a recovery or something compiled for it if I can. First, I'd have to dump the rom and kernel which might require root access, but we will see. Once we have a recovery we can port CyanogenMod over to it.
Also I think I know why it's crashing, but I can't be sure until I can test it out myself.

Unkn0wn0ne said:
I'm going to get my hands on the phone soon. I'll proceed to attempt to get a recovery or something compiled for it if I can. First, I'd have to dump the rom and kernel which might require root access, but we will see. Once we have a recovery we can port CyanogenMod over to it.
Also I think I know why it's crashing, but I can't be sure until I can test it out myself.
Click to expand...
Click to collapse
Wish you luck..just got my replacement unit from TracFone after the first one's screen froze.

oooops. Sorry posted in wrong thread.

ZTE Valet Z665c - obtaining temporary root
After trying numerous root methods (Bin4ry, Framaroot, ...), I stumbled on a method of getting temporary root using Cydia Impactor. Cydia Impactor appears to be partially successful. First of all, please note that all credit goes to those involved with Cydia Impactor and the discovery of the original exploits (do a search if you want).
This method might seem a little convoluted, but it works reliably for me. Note that I use a Linux machine so you might have to adapt the steps to work on another platform.
Prerequisites:
1. Menu -> System settings -> Developer options -> USB debugging ->Enabled.
2. Menu -> System settings -> Developer options -> Stay awake ->Enabled (to keep the telnet session from going to sleep).
3. telnet (I am running on Ubuntu, but some sort of telnet program is needed).
4. Cydia Impactor
5. phone is connected to your wifi.
Steps:
1. Run the "Cydia Impactor" to "# drop SuperSU to /system/xbin/su". See what happens.
2. It failed for me giving an error related to not being able to remount /system or not being able to create /system/xbin/su.
3. In Cydia Impactor, run "# start telnetd as system on port 2222". You don't need to bother to telnet in. Just let it finish and then proceed to the next step.
4. In Cydia Impactor, run "# start telnetd as root on port 22". Let it finish.
5. Telnet into your phone from a terminal on your computer: "telnet 192.168.1.117 -l root 22". Note that the ip address is likely different on your network, e.g., 192.168.1.xxx.
6. If everything worked OK, you should be presented with a root prompt ("~ #"). I have busybox (obtained from the Bin4ry exploit download) that I adb pushed to /data/local/tmp. The command "/data/local/tmp/busybox whoami" tells me I am indeed root.
OK - now the bad news for me. I proceed to try to install su but remount fails. If I issue the command:
~ # mount -o rw,remount /system
~ #
A root prompt is returned with no error message suggesting that it successfully remounted /system. Woohoo! But a "mount" command (or cat /proc/mounts) says it is still "ro" or read only. Darn. Does it appear that ZTE has crippled the mount command in some way? Now the question is how to permanently install root? I have poked around and at least was able to make a backup to my sdcard using bzip2
This should at least help as a first step. Others including myself have posted elsewhere on this phone. At this point, I'm not willing to risk flashing anything. I'm a noob so I'm hoping someone who is more familiar with the permissions and that sort of thing can complete the root and post a solution.
Thanks.

Awesome!
These findings are great, I'd be willing to check this out soon. (Linux box is down do to hardware issue. ).
If we can obtain root the remounting issue can definitely be fixed. Also, does busybox have the premissions to run?
Try this:
Code:
mount | grep system
That will give you somewhere within the text the partition that is registered as /system . Then:
Code:
mount -o rw,remount [PARTITION-THAT-COMMAND-RETURNED-HERE-MINUS-BRACKETS] /system
See if that works. But anyways, if it doesn't it can still be rooted! (just temporarily, but it is no longer an 'unrootable' device)
Note: I am not responsible for what happens using those commands.

a little more info in response to your questions
Dear Unkn0wn0ne,
I had messed around with it and also tried something like you suggested, e.g.:
mount -o rw,remount,relatime,data=ordered -t ext4 /dev/block/mmcblk0p19 /system
Also tried it with the "-n" option to avoid a write to mtab although I don't remember seeing mtab while purusing the file system.
Hadn't noticed that busybox was available under /system/bin:
~ # ls -al /system/bin/busybox
-rwxr-xr-x 1 root shell 1075144 Jul 19 11:20 /system/bin/busybox
~ #
Could be that it has a more limited command set than the one I put in /data/local/tmp. A lot of the commands under /system/bin have a symbolic link to toolbox.
Note that the telnet connection needs to be made over wifi and not the one available over usb. I got the ip address from my router's client list.
Oh yes - thanks for the reminder. Forgot to include the disclaimer about harming the phone or voiding the warranty.
Hope it works out well for you. Glad to hear your encouraging remarks.

Awesome!
Alright so that didn't work. This guy over here has a suggestion (he has scene your thread): - I can't publish links so I'll pm the link to you.
Also if busybox is symbolically linked you'd have to tell it specifically to call to the busybox pushed over via adb to: /data/local/tmp/busybox and not the stock.
In this case: /data/loocal/tmp/busybox/mount
Also the disclaimer is a must. There will always be that person that tries to blame it on someone else.
Note: I am not responsible for whatever happens using the information provided in this post.

karmmisht said:
After trying numerous root methods (Bin4ry, Framaroot, ...), I stumbled on a method of getting temporary root using Cydia Impactor. Cydia Impactor appears to be partially successful. First of all, please note that all credit goes to those involved with Cydia Impactor and the discovery of the original exploits (do a search if you want).
This method might seem a little convoluted, but it works reliably for me. Note that I use a Linux machine so you might have to adapt the steps to work on another platform.
This should at least help as a first step. Others including myself have posted elsewhere on this phone. At this point, I'm not willing to risk flashing anything. I'm a noob so I'm hoping someone who is more familiar with the permissions and that sort of thing can complete the root and post a solution.
Thanks.
Click to expand...
Click to collapse
I attempted this myself on my Windows 8 machine. I had to enable telnet, but that was easy. I had to reararange the command to "telnet root 192.168.x.xxx:22" (xxx is my IP). It keeps giving me the error "Connect failed."
Any thoughts out there?

try putty
Ph0enix_216,
I tried to connect from a Windows 7 machine and it works using putty for telnet (www.putty.org, a great program). Be sure to set the Connection->Data->Auto-login name to root.

well the guy in the other thread bricked his it sounds like...
http://androidforums.com/zte-valet/799676-ill-help-find-root-method-if-3.html
They tried to modify the mmcblk0p16 boot image and re-copy it back. It seemed to re-copy but then didn't boot with a verify error.. (I am paraphrasing - and don't really understand what they where doing )
sam
Ph0enix_216 said:
I attempted this myself on my Windows 8 machine. I had to enable telnet, but that was easy. I had to reararange the command to "telnet root 192.168.x.xxx:22" (xxx is my IP). It keeps giving me the error "Connect failed."
Any thoughts out there?
Click to expand...
Click to collapse