Root [recovery] ClockWorkMod 6.0.3.7

[junkie2100]

cwm bootable... not sure how well it works and youll need to use the terminal install method because im pretty sure fastboot wont write it though if someone would check that it would be appreciated

to install, put the recovery image on the root of your sd card. that means straight on the card no folders

you will then need to make sure you are rooted and get either terminal emulator on the phone or an adb connection

for adb use the

adb shell

command, for terminal emulator just start it up

then type the following two commands

su
dd if=/sdcard/warplte_cwm.img of=/dev/block/mmcblk0p16

seemingly functional, havent tested a factory reset because i have nothing to reset lol, backup and restore seem to work though it thinks its the 1970s for whatever reason, usb mass storage doesnt work, and some partitions wont work like internal_sd and sdcarddata, not sure whats up with that but i can worry about that later as long as the main functionality is there im happy for now

http://unleashedprepaids.com/upload/devs/junkie2100/warplte_cwm.img

 

[junkie2100]

also, fastboot method doesnt work, you can however fastboot boot and use a flashable version if one has been made

 

[LilBit]

TY junkie2100!!

 

[junkie2100]

nobody has tried it yet? we need to.know if it works or not for any.custom roms to be worked on, and if it doesnt work it needs to be fixed first, we have to have a known working cwm before any other development can take place

 

[LilBit]

nobody has tried it yet? we need to.know if it works or not for any.custom roms to be worked on, and if it doesnt work it needs to be fixed first, we have to have a known working cwm before any other development can take place

As soon as I have the phone in hand, I will test it. Scraping up the money for it now.

 

[junkie2100]

kool thx lilbit. hopefully ill have one soon myself

 

[greek35t]

Ok I tested it. I get a black screen after the green android. It's booting the recovery kernel for sure, but nothing more. Could someone post a stock recovery image? I should have backed mine up before flashing.... I'll keep testing. Keep em coming.

 

[greek35t]

I also will confirm this does not brick your device. I have no recovery now but I boot up no issues and everything works as usual. Just saying.

 

[junkie2100]

lol sorry bout that, check the thread looking for a cwm dev, it has a download called sdcard0 which contains partitions 15 16 and 17. 16 being boot and 16 being recovery

i should be getting a dev unit shortly, so hopefully i can do some testing on my own making things easier

good to.know the bootloader isnt locked tho

 

[greek35t]

I am a seasoned developer. been out of it a few years. I used to build source roms for the droid 1 and droid 2 global. I hate recoveries... but im very useful. Tell me what you need from me and ill test for you. I am compiling device specific files into the source tree to build an AOSP master ROM right now on 4.3. Of course i require your recovery services before i can test

Just let me know what you can crank out and I'll flash happy it. No worries

 

[junkie2100]

awesome, just be careful any android.over 4.1 generally gives problems with the sdcard mounting on a zte. but yea basically my first thought on a culprit is the display, you could try getting a logcat from the current one for me if possible, at least if we xan get logcat or dmsg we will know what is going wrong

 

[junkie2100]

ever since the switch to the zygote controlled storage directory instead of plain old mnt zte devices that came with ics or up have been giving all kinds of issues, cm10 or android 4.1 can be made pretty usable on most, but anything past that we havent managed to figure out the sd issue

 

[greek35t]

Ill try to do what I can. I dont remember logcat working on the recovery side but ill give it a shot and dump it into a file. lets see what we cant find.

 

[greek35t]

yeah not getting a logcat. actually the device is not registering to the pc at all. so that might be a starting point. its not getting far enough to load adbd

 

[greek35t]

where is dmesg outputting to in recovery? Have you enabled it? If so tell me where its writing the log file and ill get it for you.

 

[greek35t]

On a side note, that 16.img worked just fine to restore my stock recovery. Just wanted you to know that it is a viable image and it has it's integrity.

 

[greek35t]

Ok so the USB doesnt work. I split the stock recovery and copied the scripts over to yours and was able to get the usb interface up. I got a dmesg and output it to a file after mounting data manually. I will figure out what is broken in your ramdisk scripts and send the fix for usb to you tomorrow. Either way, here is the DMESG and hopefully it helps you out.

 

[junkie2100]

awesome, good work man i appreciate all the help. ill look over it now

 

[junkie2100]

its just as i had suspected. gpu startup loop

the force had an adreno 225, this phone has an adreno 305. let me check something and ill get back to you

 

[junkie2100]

can you get me the egl?

 

[greek35t]

let me try right now.

 

[greek35t]

I may have to add logcat to the recovery commands.

 

[greek35t]

any idea how to get a log of egl data? I am at a loss for once.

 

[junkie2100]

log i dunno, but the egl itself is what i.need. egl.cfg from /system/lib/egl

 

[greek35t]

Its attached. Renamed to .doc so i could attach.