Root Root achieved

[stevestone]

somebody should upload a config.gz and a build.prop

config.gz is in /proc
build.prop is in /system

both the files on this folder..

https://www.dropbox.com/sh/rycikcvwmg1oz7x/U0AvfBIWw_

thanks

 

[junkie2100]

yea it seems to use a different source than the devices ive been working with. see what i can find out tho

 

[gothamknight18]

Ok so first off, sorry for interupting all of this, but being a noob on about...all of android development. I was hoping I could get some help considering you guys seems to know things about the ZTE Vital/Surpreme. My phone doesn't show anything after the android guy. I can get into recovery and it shows the charging images when the phone is off. Would flashing any of the files above help fix this so I can actually use my phone? (oh yea, I replaced the boot animation then restarted my phone right before this happened)

 

[junkie2100]

bad boot animation, youd have to get in there and replace it manually or flash a whole.new rom through cwm. if you can learn to use the mount command and the push command through adb you.can just push the stock boot.img through ftms adb connection

 

[junkie2100]

in other words, put the phone in ftm mode, vol up and power, connect to computer, use adb through command prompt to do adb shell, mount system manually as writable, type exit to get out of adb shell but stay in command prompt, then adb push the good boot animation and double check its permissions with a chmod command

 

[stevestone]

I m facing issue in manually mounting the sdcard.. ?? any commands for it?

 

[junkie2100]

why are you manually mounting the sd?
and in what? i dont know the specific command that will work off hand it can be very tricky especially on a zte, mounting regular partitions is still pretty straight forward tho. if you explain to me what youre trying to do i may know a better way

 

[dutchman123]

Right, I figured this bit out.
- Put the phone in ftm mode
- Open adb shell
- Do the following commands in adb shell:
su
mount -o rw,remount -t yaffs2 \system
chmod 777 \system
- exit adb shell (i.e. type 'exit' twice)
- Make sure the file you want to push is in the folder where adb is
- Push the file with adb:
adb push (yourfile) \system\(therightfolder)\(yourfile)

- That should do the trick.

 

[dutchman123]

sorry, it's actually:

mount -o remount,rw -t yaffs2 /system
chmod 777 /system

 

[Shabbypenguin]

its ext4, not yaffs2, yaffs2 hasnt been used since GB

 

[junkie2100]

well if youre trying to mount system as writable after its already mounted you can do

mount -o remount,rw /system

 

[cerebrus21]

well if youre trying to mount system as writable after its already mounted you can do

mount -o remount,rw /system

I have the same problem with the busted boot animation. Im loaded into ftm and I tried the codes that dutchman provided. I get all the way to pushing the fixed boot animation into the /system/media/bootanimation_virgin.zip location but it says permission denied what could be causing this issue?

 

[junkie2100]

lmao oh... yea using that command with yaffs2 in it wont work. as stated already. replace yaffs2 with ext4

if system is already mounted though you can use the command as i put it without the filesystem type

 

[junkie2100]

i will follow this thread. i guess you guys dont have a working cwm yet but it shoulsnt be hard at all. same basic thing as the force and flash just a different kernel. you could most likely unpack the cwm image from either of those, toss in the stock recovery zimage, and be on your way. ill get to it wheb i can tho im fighting an uphill battle with the warp 4g

 

[stevestone]

Cool and thanks..

 

[stevestone]

I tried it but i am getting blank screen.. with dx kitchen.. i tried with flash recovery..

 

[junkie2100]

ok so you went in on the flash recovery. swapped the zimage for your recovery zimage and it didnt work?

 

[junkie2100]

sorry got lost for a minute there got alot of things going on at once. if swapping the zimage file in the recovery didnt work itll have to be built

 

[stevestone]

sorry got lost for a minute there got alot of things going on at once. if swapping the zimage file in the recovery didnt work itll have to be built

I tried with flash recovery by swapping zimage.. It gives blank display.

but it detects on pc with n9100 device (force i guess) but i dont got any driver for that.

So, may be something related display, do you think editing in build.prop will work? as vital is 5inch?

or something related to kernel?
please guide, I have even install ubuntu on my laptop.. TYVM..

 

[junkie2100]

build.prop doesnt get loaded in recovery. only things recovery loads are what you see in the unpacked recovery.img ramdisk

 

[stevestone]

ooops. I mean default.prop which we get when we extract recovery...

 

[junkie2100]

ah. yea that doesnt really matter much either. ill build one in the near future when i find some time to do so been rather busy lately

 

[stevestone]

I tried editing its all same.
Build from source is require.. i might try some other recovery too.. lets see :s

 

[junkie2100]

i wouldnt do that if i were you unless yiu plan on building them from source properly. no other recoveries were made for the device type in question and using some other devices will cause you issues, issues you may never recover from

 

[stevestone]

Thanks man... I looked at other zte recoveries like warp, force all created by you..

Do we need kernel source to build recovery?