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

Root [Boost Mobile] [Q] RomDump Help

blue2107

blue2107

Well-Known Member
I ran romdump two times with different results.

The first time I got a dump with a few errors. (system.tar 180.08mb)
The second time a larger dump with no errors. (system.tar 180.59mb)

The checksum.md5,config.gz, and system.info.gz were all the same size.
But not the system.tar files

I would like to know:
-Why these "permission denied" errors occurred when I have root?
-Is there a major/critical difference between the two?
-If someone could inspect them and possibly teach me something?
-Can you help me figure out how to install Clockworkmod recovery on this phone?


Code: 
C:\Users\Meek\Desktop>adb push romdump /data/local/
2667 KB/s (1149900 bytes in 0.421s)

C:\Users\Meek\Desktop>adb shell chmod 04755 /data/local/romdump

C:\Users\Meek\Desktop>adb shell /data/local/romdump
Android ROM dumper v0.82b
(c)2011 Sebastian404
You need to be rooted to run this aplication

Device : N860V1.0.0B06

Creating required files... find: /system/etc/firmware: Permission denied
find: /system/etc/gpsone_d: Permission denied
find: /system/etc/firmware: Permission denied
find: /system/etc/gpsone_d: Permission denied
find: /system/etc/firmware: Permission denied
find: /system/etc/gpsone_d: Permission denied
done.
Opening mtd table... done.
Dumping kernel config... done.
Dumping boot partition... done.
Dumping recovery partition... done.
Dumping system partition... done.
Creating Checksums... done.
Cleaning up... done.
All done.
Here's the second readout with no errors.

Code: 
C:\Users\Meek\Desktop>adb shell chmod 04755 /data/local/romdump

C:\Users\Meek\Desktop>adb shell /data/local/romdump
Android ROM dumper v0.82b
(c)2011 Sebastian404
You need to be rooted to run this aplication

Device : N860V1.0.0B06

Creating required files... done.
Opening mtd table... done.
Dumping kernel config... done.
Dumping boot partition... done.
Dumping recovery partition... done.
Dumping system partition... done.
Creating Checksums... done.
Cleaning up... done.
All done.
 
The app is telling you your not running as root, oddly it seems to of worked tho, I suspect the root method you guys are using is not 100%

If you are willing to share the results of the 2nd run with me I can look into it, and also make a clockwork of recovery image for you

UPDATE:

I checked out the root process that is posted here, that is only a partial root, that is the reason it is having problems.
 
is there any chance of perm root? also i see you posted a cwm recovery but the device is not seen by fastboot in ftm mode ..... i did get a driver to install during ftm mode but its nothing that can be utilized by fast boot
 
FTM mode is not the bootloader, its a diagnoistic mode that you can use to access parts of your device with tools like QPST, CDMA Workshop. ZTE have some tools that can reflash the rom and do other things, some of those have leaked but its not something I'd recommend messing with.

I have made an insecure boot.img for the device:

http://android.podtwo.com/beta/N860V1.0.0B14_insecure_boot.img

but it would also depend on getting the device into bootloader and using fastboot...
 
Sebastian404 said:
FTM mode is not the bootloader, its a diagnoistic mode that you can use to access parts of your device with tools like QPST, CDMA Workshop. ZTE have some tools that can reflash the rom and do other things, some of those have leaked but its not something I'd recommend messing with.

I have made an insecure boot.img for the device:

http://android.podtwo.com/beta/N860V1.0.0B14_insecure_boot.img

but it would also depend on getting the device into bootloader and using fastboot...
Click to expand...

Ive Been Keeping up with this and your other posts Sebastian but youre having the same problem in all of them-intrdpths partial root , so you may have to build a root that is 100 knocking out alota birds with one stone because if you dont do it youre/we're going to have this same problem down the road with not only this but roms and everything else i dont know if you read the spped up 3g post but i propose why its slowing down is because its not 100 rooted:cool:
 
I highly doubt that will work as it's probably doesn't support the phone, but what you wanna do it after you pushed it to the phone.

adb shell
su
./data/local/romdump

then it'll run with root permissions.

And once again, Freeze you are completely wrong, he just forgot to do su. lol
 
Romdump won't work with this device since its not mtd based..

It's the first ZTE Device that is it tho, so..

Can someone as root do a 'mount' from the console and paste the results here
 
Sebastian404 said:
Romdump won't work with this device since its not mtd based..

It's the first ZTE Device that is it tho, so..

Can someone as root do a 'mount' from the console and paste the results here
Click to expand...

Here it is:

rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,size=61748k,nr_inodes=15437,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,size=61748k,nr_inodes=15437,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,size=61748k,nr_inodes=15437,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p15 /system ext4 rw,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p18 /data ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p7 /persist ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p17 /cache ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/vold/179:33 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:33 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/org.urbian.android.tools.vintagecam-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/com.skype.raider-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
 
It is very odd, ZTE have lots and lots of devices, all using MTD/YAFF2, but when it comes to SnapDragon devices (there is 2 I've found so far) they have switched to EMMC/EXT4.
 
You must log in or register to reply here.
Back
Top Bottom