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

Root got it rooted using kingo app

B

bzo22

Well-Known Member
I can confirm kingo app does root the phone.. Now which one of u nice developers one need a copy of system img to work on cwm
 
First off, eww no. DONT USE KINGO! I will have an alternative here shortly!

Second, I can use some stuff. I do not need a copy of system, but I do need this stuff:

You can run these commands on device using terminal emulator, or you can run them on your computer in a command prompt after the command "adb shell"
Code: 
su
mkdir stuffs
cat /proc/config.gz > /sdcard/stuffs
cat /dev/block/mmcblk0p15 > /sdcard/stuffs/boot.img
cat /dev/block/mmcblk0p16 > /sdcard/stuffs/recovery.img
cat /proc/mounts > /sdcard/stuffs/mounts.txt
cat /proc/partitions > /sdcard/stuffs/partsize.txt
ls -la /dev/block/platform/msm_sdcc.1/by-name/ > /sdcard/stuffs/partname.txt
If you could zip up the "stuffs" folder, upload it, and then link it here, I'll have some fun stuff for you shortly!

Edit: I'm assuming partition 15 is boot and partition 16 is recovery, because that seems to be universal with the other zte devices that use the same architecture. If you take a look in the partname.txt file, it will list what the mmcblk0p## is for boot and recovery, but 15/16 should be correct.
 
When I ran command for it it said system was read only.. After that I use root explorer too mount system as r/w an ran the command again and it said the same thing
 
bzo22 said:
When I ran command for it it said system was read only.. After that I use root explorer too mount system as r/w an ran the command again and it said the same thing
Click to expand...

Not sure why it would say that, since the command "cat /proc/config.gz > /sdcard/stuffs/config.gz" doesn't touch /system. :confused:
 
If you grab the system.img and boot.img I will put together some stock roms for this device. I am sure cwm is just around the corner seeing who is on this thread :)

Code: 
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/sdcard/system.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/boot.img
 
SuperR said:
If you grab the system.img and boot.img I will put together some stock roms for this device. I am sure cwm is just around the corner seeing who is on this thread :)

Code: 
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/sdcard/system.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/boot.img
Click to expand...

I've been waiting for this device to come out long before it was publicly announced. I have my ways of finding device info ;) So naturally I'm here lol

Anyway, I have CWM build at the moment, and I will have it uploaded later tonight after I'm home from work, unless it finishes building early enough before I leave.

Here is what I will need tested:
Report any graphical issues
Check to make sure that you have access to sdcard(internal sd) AND sdcard1(external sd)
Check if USB Mass Storage is working.
While still plugged into the computer, unmount USB Mass Storage and see if you still have access to sdcard and sdcard1
Mount/Unmount all the partitions (system, data, etc)
Backup to both sdcard and sdcard1
Restore from both sdcard and sdcard1
Install zip from both sdcard, sdcard1, and sideload

oh and make sure you grab SuperR a copy of system.img before you do remove ANYTHING. I'll have my root guide posted when I upload cwm.
 
cooldudezach said:
I've been waiting for this device to come out long before it was publicly announced. I have my ways of finding device info ;) So naturally I'm here lol

Anyway, I have CWM build at the moment, and I will have it uploaded later tonight after I'm home from work, unless it finishes building early enough before I leave.

Here is what I will need tested:
Report any graphical issues
Check to make sure that you have access to sdcard(internal sd) AND sdcard1(external sd)
Check if USB Mass Storage is working.
While still plugged into the computer, unmount USB Mass Storage and see if you still have access to sdcard and sdcard1
Mount/Unmount all the partitions (system, data, etc)
Backup to both sdcard and sdcard1
Restore from both sdcard and sdcard1
Install zip from both sdcard, sdcard1, and sideload

oh and make sure you grab SuperR a copy of system.img before you do remove ANYTHING. I'll have my root guide posted when I upload cwm.
Click to expand...
Okay, root guide is up. The link to the cwm is there as well. To actually install the recovery, follow these steps since it's not a flashable zip. If you know how to create a flashable zip, then you can do so instead.

After booting into the recovery via fastboot, enter these commands from your computer:
Code: 
adb push recovery.img /cache/recovery.img
adb shell
dd if=/dev/zero of=/dev/block/mmcblk0p16
dd if=/cache/recovery.img of=/dev/block/mmcblk0p16

If you boot into recovery after this, you should boot into philZ recovery. I think the command to enter is VolDown+Power from poweroff, but it might be VolUp+Power. (The ZTE Awe is VolDown, the ZTE Source is VolUp, so I am never sure.)
 
rbheromax said:
4.4 requirements enabled. thats all. nothing added in yet. just wondering if this boots, cuz we can continue from there
Click to expand...
I'm assuming you used the msm8930 kernel source repo? It doesn't have any stormer related bits. those are in the stock hera kernel source.
 
haha nice. :) I need to merge the stormer shit into the msm8930 source, but i'd rather just wait for the kernel and use the hera source for now. lol

I'm still convinced that they took the awe kernel source and used it as the basis for both the hera and the warplte, but both were written at the same time, rather than one after the other. which is why the warplte has newer stuff, but the hera got the stormer shit

Once the stormer kernel is released, I say we use it as the base, or at least take the updates and merge them into the current msm8930 source
 
cooldudezach said:
haha nice. :) I need to merge the stormer shit into the msm8930 source, but i'd rather just wait for the kernel and use the hera source for now. lol

I'm still convinced that they took the awe kernel source and used it as the basis for both the hera and the warplte, but both were written at the same time, rather than one after the other. which is why the warplte has newer stuff, but the hera got the stormer shit

Once the stormer kernel is released, I say we use it as the base, or at least take the updates and merge them into the current msm8930 source
Click to expand...

I think we should wait till the stormer source is released. I wont do a real kernel until then, only a teaser.
 
See what had happened was....
I'm slack lol. But on the brightside nex has bootani on cm11. Get it from hroark13. The problem now is the kernel. Enable selinux and it should boot :) tell him that also
 
rbheromax said:
See what had happened was....
I'm slack lol. But on the brightside nex has bootani on cm11. Get it from hroark13. The problem now is the kernel. Enable selinux and it should boot :) tell him that also
Click to expand...
If you've got bootani, then you should be able to pull logcats :)

Also, messaged him on irc a link to your post.
 
You must log in or register to reply here.
Back
Top Bottom