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

Root Extract Zte Vital Stock Rom DUMP

S

stevestone

Well-Known Member
Hello,

Zte vital is a amesome device.. I am trying to get a dump of stock rom...

I am not able to get partition block..

cat /proc/mtd or emmc displays no such file or directory..

please help?
 
our partition blocks. .. but dont know, whr is recovery or boot, or system.. please help....

cat /proc/partitions
major minor #blocks name

179 0 7634944 mmcblk0
179 1 8192 mmcblk0p1
179 2 8192 mmcblk0p2
179 3 8192 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 8192 mmcblk0p7
179 8 24576 mmcblk0p8
179 9 8192 mmcblk0p9
179 10 8192 mmcblk0p10
179 11 8192 mmcblk0p11
179 12 8192 mmcblk0p12
179 13 8192 mmcblk0p13
179 14 73728 mmcblk0p14
179 15 16384 mmcblk0p15
179 16 16384 mmcblk0p16
179 17 16384 mmcblk0p17
179 18 1056768 mmcblk0p18
179 19 8192 mmcblk0p19
179 20 8192 mmcblk0p20
179 21 311296 mmcblk0p21
179 22 1581056 mmcblk0p22
179 23 4284416 mmcblk0p23
179 24 65536 mmcblk0p24
179 25 8192 mmcblk0p25



some more details :-

cat proc/mounts
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,relatime,data=orde
red 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,nosuid,nodev,relat
ime,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,nosuid,nodev,relatim
e,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,nosuid,nodev,rel
atime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,relatime,uid=1000
,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=low
er,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/carrier /carrier ext4 rw,nosuid,nodev,rel
atime,data=ordered 0 0
/dev/block/vold/179:23 /storage/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:23 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /storage/sdcard0/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
 
8960 uses the by name system

browse to /dev/block/platform/msm_sdcc.1/by-name

you will see recovery, boot, userdata, etc

that being said a stock rom dump.is better off being done differently, if you adb pull the system folder its not all packaged in the partition, itll be smaller and easier to access
 
junkie2100 said:
8960 uses the by name system

browse to /dev/block/platform/msm_sdcc.1/by-name

you will see recovery, boot, userdata, etc

that being said a stock rom dump.is better off being done differently, if you adb pull the system folder its not all packaged in the partition, itll be smaller and easier to access
Click to expand...

Thanks.. I did it..
 
Hi, any chance I could get one of you guys to make the stock rom available?

I rooted my phone to get rid of the annoying virgin mobile ZTE supreme startup sound. So far so good. Then I started toying around with the fonts. After one font change to many I got stuck in a bootloop: the phone gets stuck after showing the intro video. Also I forgot to make a backup beforehand so I'm in trouble.

While I learned a lot about adb pushing and all that I can't get past this bootloop issue. I couldn't find a cwm that is suitable for the zte supreme (=same as vital I think), which means I can't do a dalvik cashe wipe, and I can't find a rom (custom or original) that works for the zte supreme.

Any tips would be greatly appreciated.
 
I did do a cache and factory reset by the way. To no avail.

The program I used was 'font installer *root*'.

I'm a little worried my phone is now a brick, but perhaps one of you guys has a good idea?
 
please create a new topic, if you can mount sdcard in ftm mode. i will upload my system.img and you can push it through ftm mode..
 
I opened a new topic 'unbricking a ZTE supreme'. Yes, I figured out how to get into ftm mode and communicate to the phone through adb. I haven't tried accessing the sdcard yet but I have figured out how to push files to the system folder. I'm sure a bit a sweat and effort will go a long way towards figuring the other details out.

Thank you very much for doing this.
 
I froze/uninstalled the wrong items via System Tuner Pro and I am able to get to stock recovery, but my phone won't boot past bootloader. I just get a blank screen. Do you think I can fix this by replacing the boot.img or system.img. Please help a poor guy out. :) I extracted the kernel from the boot.img and the ramdisk, but I'm at a lost as to what I should do to fix this. Any help would be greatly appreciated.

Thanks,
Thomas
 
boot.img wont help. system img would but none is available for this phone that im aware of. once somebody makes a cwm and puts out a stock rom dump you can do that. or you could go in through adb and manually unfreeze them all. freezing is normally just renaming the .apk in system/app
 
@Junkie - I purchased another zte. Something of Interest, I copied all system apps to bricked phone rather than unfreezing them, and did a md5 check, and some of the system apps have a different sum. I didn't activate the phone yet, and I remember losing apps I installed on my original device after activating. I believe the activation process involves replacing image files. Virgin Mobile piggy-backs off of Sprint, so it makes sense that the bootimages for multiple carries exist. This would also explain why Vital's cwm doesn't work on the Supreme.

Would you tell me what files I would need to extract from the "by-name" that would be needed to restore. I won't ask you for too much help...I promise. I may be a noob, but I pick up fast. I learned all the commands to copy files from secure folders and what-not, I just don't know how to go about creating a Stock ROM to recover from. I work as an enterprise architect for my day job, so I should catch on quickly. I already created a bootable usb drive with Unbuntu, and plan on creating my own ROMs from AOSP. I requested the source code for AOSP and the kernel. They asked for my IMEI...I suppose they wanted to swap out stuff on my phone and give me the source code without the backdoor. ;)

I plan on making it harder for remote access by hardening the kernel/AOSP code. They're taking their pretty time though. I may have to prod them a little more because I'm getting tired of being on my own private ips of 21.86.13.51 or 51.5.207.245. They seem to like poisoning my routing tables...those bastards. ;)

It's time to play! Any help is appreciated.
 
i guess i will start at the beginning and work my way through

first off, the phone may have been updated, also if the files are named differently or sometimes even in different directories when you run an md5 check they will be different. ever tried changing the folder name of a cwm backup? itll break the md5. also if you froze them it may have modified the program code...

on the partition note, i have no idea what youre talking about. what are you trying to do? if you messed up some apps, and didnt break the boot.img or recovery.img, neithrr of which you probably did, you shouldnt be messing with the partitions they arent the problem

on the source thing. who exactly do you think is going to give you aosp source? sprint wont give you anything not even kernel source, same goes for the subsidiaries boost and virgin, and zte is legally required to provide kernel source though half the time they wont, but they will never ever ever give you rom code. they will tell you they will give you the source to shut you up and then never speak to you again. aosp and cm both come from a public base you can acquire on your own, then you have yo make a "device tree" which tailors the main base to your chosen device. that is where people like myself come into play, we have yo make the code, no one gives it to us, though often times there are good bases to start with those bases come from customers, not companies
 
let me tell you a story that can help explain where aosp comes from

a year ago, i got a phone that had no development projects finished. playfulgod had made a basic cwm tree but it was unfinished, he had no way to test and alot of projects on his plate as he always does, so it remained unfinished. no cwm, no roms, just root. i knew i would need cwm, especially after bricking the first one and having to exchange it at walmart. so i enlisted the help of a guy named superr who could run the builds while i did the tinkering and testing. it took a little bit but we got it working, and from there playfulgod helped us (and by helped us i mean basically did most of the work lol) make cyanogenmod. i was a guy with a phone, a need, and the will to fight against all odds to make it happen. i was no dev, i wasnt even that advanced of an android user, but that is the only way things like that get done.

sprint wont help you, virgin wont help you, boost wont help you, and zte is the least help of them all. aosp and cm are the product of the people here and at xda and unleashed prepaids and all kinds of other places like them, that dont get paid, that dont hold allegiance to any company, who do it for reasons of their own
 
What I was saying is that the Vital and the Supreme are built/ship with the same images, but after activation, there's an update performed and the System apps are swapped out. I put them in the same folders and the names did not change. Upon a reboot, I found that my su app had been deleted (I didn't do it) and my phone would not boot. I purchased another Supreme for my wife, and I copied all of the system images out of the by-name folder. I was hoping someone could tell me all of the files that I would need to create a cwm, but that's ok if that is too complicated. I'll just learn it myself. Unlike you, I am a program. I just never put forth any effort in the Android OS because I don't like Linux as much...although my opinion has changed about Linux. My next laptop's OS will be Linux. Now I have a reason, as you mentioned being a motivator, and I am going to tackle the Supreme. Any help is appreciated, but not required. I'll do it regardless.

I also understand that ZTE will drag their feet, but one could hope that they'll give in. I am not going through Sprint or Virgin, they did not create the build...ZTE did, so I'm going through them. If I'm provided with it, I'll post a link to it here.
 
zte isnt dragging their feet, theyre hoping you give up. they will never give you rom code... ever. as far as the supreme vs vital no they arent the same images when shipped actually. they sre different from the factory on a very small scale. hence the differences

as far as a recovery you will need the recovery partition. unpack it in dsixdas kitchen and takr the zimage. you can then rename it kernel and plug it into the aurora repo on my github or unpack and repack the force(aurora) one already built with the proper kernel
 
Just for a info. Refer resource thread. He has posted system.img recovery and boot.img.

I have personally compared boot.img and recovery.img with my vital. Both supreme & vital has same boot.img, its identical. Same goes to recovery.

.
 
Someone already flashed boot.img from Vital to Supreme and they were up and running. Steve was a part of that conversation. Anyhow, I found out that my System partition was deleted (not by me). I tried to flash good system.img from new device to the by-name folder of old device (same devices, same provider...Virgin Mobile) but I get an error message stating no memory left on device. I did not Activate new phone as of yet, because I wanted to do a proof of concept to test my theory that phone is modified after activation. Before activating, I wanted to copy all files needed to create a Stock Rom. Would I only need everything from the by-name folder, or are there other folders of importance. Thanks for the feedback.
 
Also, I did a comparison of Kernels extracted from the boot.img in a Hex Editor of the Vital (which Steve posted) and of the Supreme. The Kernels are identical.
 
you wouldnt wanna do it as a system image. someone needs to make a working cwm and a flashable really... but if you want me to do it youll have to wait im kinda in the middle of a few other projects at the moment
 
FYI, I got the supreme up and running. I couldn't write straight to the /by-name folder or it would give me an out of storage error. I ended up copying system.img to /data and then running the following command:

dd if=system.img of=/dev/block/mmcblk0p18

mmcblk0p18 is the block where system.img is stored. It appears the phone company didn't like me locking them out of their malicious apps which could install/run with elevated privileges...looks like I missed the part where they could delete my system.img partition! The bastards. ;) I'll have a surprise for them the next time, once I get a custom ROM running with a hardened kernel.

I work for the Florida Senate as an Information Systems Engineer, and I have access to a couple of lawyer friends within the Senate who could assist me in getting the things ZTE derived from open source. I'm hoping I'm not going to have to go that route, though.

Let me know if you have any questions for your own knowledge.

Thanks,
Thomas
 
Vander.. get that zte bish source :D

Yes profile update do something bitchy on phone. I lost my profile settings sprint logo and wifi hotspot settings, because of RTN dial code. Though i am flashed to other carrier, so its not much issue. But i cant update profile.

Zte is weird. I tried to swap carrier partition of zte flash but it doesnt work either
 
You must log in or register to reply here.
Back
Top Bottom