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

Root [Avail 2] Root available?

"cannot open for read: no such file in directory"

i dont know if this is where you get kernel info but i went into about phone in settings and got
kernel version 3.4.0- perf
zte-kernel@zdroid-SMT
 
That's not it. Could you try
su
dd if=/dev/block/mmcblk0p17 of=/storage/sdcard0/stock_recovery.img

or

su
dd if=/dev/block/mmcblk0p17 of=/storage/sdcard1/stock_recovery.img

Im not sure which of the SD cards is which.
 
I have a copy of stock recovery so no worries there (who ever uses stock recovery anyways?). Also, I think recovery on this is 16, not 17. I'll look at the fstab to confirm.

EDIT:
My mistake, it is 17. Carry on.
 
say i were to flash the z993 cwm onto it and it doent work wouldnt it brick the phone? if so how would i be able to flash the stock recovery then?
 
brucedroid said:
say i were to flash the z993 cwm onto it and it doent work wouldnt it brick the phone? if so how would i be able to flash the stock recovery then?
Click to expand...

If it hard bricks then you'd be out $80, which is an inherent risk to doing this.

I also have a recovery image ready that I just source built with all the right names on it
 
Your right I flashed there version to my phone but I was hoping using there recovery might fix my bugs. Anyhow how to you boot a z992 into recovery? power off and vol up plus power.
 
Well I will make an OP for the Z992 version. and just let them know It could be vol up or vol down. I tested it and it works though same bugs as the Z993 build though. no luck on twrp though it has a flashing white screen but it does have shell access any ideas.
 
No go flashing white screen just like my twrp builds. Here is a dmesg if it helps. Also what source are you using to compile.
 
CM10.

graphics.c has always been a pain on this phone. And recovery.log may be handy too (I know how to fix the USB mountbut graphics come first).
 
I believe you. My thought was also graphics.c but I don't really know what to try I will be working a few fixes once I sync my source again. I may have deleted it :(. Also is cm 10 source jellybean-release, I have been working with cm10.1 source Maybe time to take a step back.
 
CM10 is 4.1.2,
10.1 is 4.2.2
10.2 is 4.3.1

Glad to see USB is working better. I'm sure if the graphics worked, the USB mount would work too (depending on what device tree you started with)
 
I just started with the generic config and pulled the skeleton files from the stock recovery. Also what repo do I need for Android 4.1.2 as there isn't a cm10 repo for whatever reason.
 
You must log in or register to reply here.
Back
Top Bottom