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

Root Root achieved

stevestone said:
Thanks man... I looked at other zte recoveries like warp, force all created by you.. :D

Do we need kernel source to build recovery?
Click to expand...

yes i have been rather busy lol

probably dont need kernel source, but i should have it ;) im gonna try and get that out today, gotta collect the stuff necessary and then put it all together in a device tree for cwm to build. shoulsnt take long. mostly copy and paste with an adjustment here and there
 
completely spaced I meant to try rebuilding this, I took my old device tree and swapped out the zimage to see if that fixed it at all. if it does then ill push my tree to github

https://mega.co.nz/#!hNgj2KzJ!HxGVXwpIsSTbwnLZ5u9heGFWvYNn5T4Shthu7rUckJY

if it boots and sorta works then awesome, im sure junkie would be better suited to fine tuning it as he has experience with zte's, right now im just trying to figure out what they did to change why its not working anymore.
 
seems the recovery isnt even booting enough to give a log... that would mean the last log was the last recovery that did aka stock
 
i did notice that the stock recovery kernel and the force didnt seem to get along, it required a built kernel if im not mistaken and im not sure of where to get source that would include the quantum. its a 3.4 kernel 8960 device and all i have is 3.0 8960s and 3.4 8930s in which quantum is not included

the source is out im sure of it! just gotta figure our which 3.4 zte kernel source has the quantum config info built into it... like the warplte and hera are both in the nex kernel source, the aurora is in the elden kernel source, its gotta be somewhere buried in someone elses kernel
 
I deleted logs files. Flashed again.. and no log were created.. Junkie is right, I guess. recovery is not booting up to create log.. btw, junkie cwm thread recovery where detecting on pcs..
 
hello,

I tried all the recoverys.. from test1 to shabby..

no one is creating any log :(

junkie test1 one above with the 4hared link, get detected on pc as dfu driver install on it.. :(
 
hey guys

I'm really new to the developing thing and I got my phone stuck on a soft brick. I tried replacing the boot animation with another using adb, but it told me that the directory was read only. Here is the code that I used

adb push \Users\Henry.HenrysPC\Desktop\Nocturnal_ADB_Fastboot\bootanimation_virgin.zip /system/media/bootanimation_virgin.zip

I used this in FTM mode.

I was able to successfully pull the dysfunctional boot animation, but not replace or delete it.

If anyone could help it would be greatly appreciated!
 
mount -o remount,rw /system

but in the future, dont do stuff like that without clockworkmod or some kind of custom recovery in case these things do happen, then you just make a backup while its working and when you mess up you just hit restore
 
Thanks for the quick response Junkie, but I tried remounting the system in adb shell and in adb shell: su

either way when I tried to push files afterwards I got the same error message, and I'm sure I had root access when the phone soft bricked.

How would I flash a new ROM, if that is possible without clockwork mod
 
Thanks for the guide Stevie, unfortunately it did not fix the problem. I get the same error. I there anything more to be done or is it a lost cause?:(
attachment.php
 

Attachments

  • code 1.jpg
    code 1.jpg
    70.1 KB · Views: 191
You must log in or register to reply here.
Back
Top Bottom