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

Root [Device tree] Work in progress... Warp3 Dev edition lol

no. everything has changed, even kernel versions, android versions, and chips. this phone is much closer to the force than either of the other warps. the only thing closer than that is the awe and source which are part of this dev project meaning theres no progress past cwm, and then next in line is the vital/supreme which i havent even got cwm for yet. there may be other devices similar but they would probably be foriegn devices and not necessarily even on this site. if you want you can do research into 8930, 8630, and 8960 zte devices that come with jellybean, find whatever you can on them there may be a repo buried deep somewhere that can help
 
as far as who superr is, hes a buddy of mine from when i started developing about a year ago, together we made the first usable cwm for the warp sequent by fixing up a few minor things in playfulgods original repo. you can normally find him in the sequents all things root section. not sure what android manager youre talking about tho. you mean rom manager? i dont usually use or recommend use of rom manager but it can be used if you know what youre doing
 
NM Nandroid manager.apk . Somebody on one of the 4G threads said it would work to flash your CWM

@Junkie I know right the chip set and the 3D-ish screen . Nice..
I just check sequent thread. Junkie if you get a chance ask him if he can add "build box" thread on this G4 section
 
i am not sure, probably an option that says flash recovery... i never touch the stuff i flash it the old fashion way through adb or fastboot though fastboot doesnt seem to work right on this device
 
i could easily make a program to do the hard part for you, but you guys should really be learning to do things manually not depending on us to make it point and click
 
Its still cheating but I set up my build environment like Warp told me. I open a tutorial on half the screen and terminal on the other side . And copy and paste

Its precise and faster than typing from memory
 
well i mean you gotta have some frame of reference eapecially as a beginner. now you just gotta get something to build and make what builds work on the device, which is hard as hell. there will be no copying and pasting from a tutorial
 
I have been researching this on github. When I have something and I test it a few times I'll send it to Warp so he can push to his account. He is putting it on a master I think. Just let me know what parts of your d- tree that are concrete and we can blend our stuff.
 
BobDabolina said:
Truth be told, That thread I made will become reality, locked or unlocked. Every phone can be hacked
If it takes the better half of a year so be it
Some may not know but there are many ways to skin a cat.
I have studied for 6 month and lurking threads
Many threads . New users understand for every custom rom
there is a separate way to config. It. The pacman rom by far I believe is the worse. I have yet to figure it out.
If you can get CM then you can get J-beer and Chaos. Not much of a difference. Idk about paranoid & the bean series. I mean I read a tut about paranoid its different codes but workable
I'm a firm believer in teamwork tho. You will have trouble hacking a phone by yourself. Nothing to push you to that level where you want to be the first person to put out a new creation
As of lately I have been studying the Devs githubs. Junkie and PG and some other people. I see so many techniques that these devs use. Github is a gift for a newcomer like myself.
The thing I do not know is after boot how do you read the gibberish on a log cat. I see pastebin and it is complicated
Click to expand...
If you look into the Kyocera Rise, I started the dev work on that about two years ago, and we made almost no progress, because we couldn't find a way past the bootloader. I jumped ship the first chance I could, and grabbed the Awe this past black friday. Immediately started dev work on it as well, the day after I bought it! Got CWM booting pretty quickly, and I fell in love. :D

junkie2100 said:
no. everything has changed, even kernel versions, android versions, and chips. this phone is much closer to the force than either of the other warps. the only thing closer than that is the awe and source which are part of this dev project meaning theres no progress past cwm, and then next in line is the vital/supreme which i havent even got cwm for yet. there may be other devices similar but they would probably be foriegn devices and not necessarily even on this site. if you want you can do research into 8930, 8630, and 8960 zte devices that come with jellybean, find whatever you can on them there may be a repo buried deep somewhere that can help
Click to expand...
I'm thinking about grabbing the Overture, which is a GSM ZTE 8930 based device as well, so it should fit into our scheme of things pretty smoothly. It'll cost me a pretty penny when I do, but then I'll have essentially the same phone if I need to transition between CDMA and GSM. :)
 
@cooldudezach, good stuff bro.
@Junkie , I dont know if you can tweak it like you and SuperR did on the sequent but Warp has $tock recovery posted on his thread. I think he has the $tock 3.4 kernel as well. Your AIO root program is tight. Warp sent me a copy and I extracted it to look at how you did it. Quite impressive.
You would probably need to break apart the frama root apk and grab the exploit unless its zergrush in which I have a copy already.

Just a tid bit of advice to people posting new threads.
Tags can help keep our G4 section looking professional and clean.
Just add tags before your thread title.
You need help [question] or [help]
U want to make a tut. [ tutorial] or [guide]
Etc...
 
BobDabolina said:
@cooldudezach, good stuff bro.
@Junkie , I dont know if you can tweak it like you and SuperR did on the sequent but Warp has $tock recovery posted on his thread. I think he has the $tock 3.4 kernel as well. Your AIO root program is tight. Warp sent me a copy and I extracted it to look at how you did it. Quite impressive.
You would probably need to break apart the frama root apk and grab the exploit unless its zergrush in which I have a copy already.

Just a tid bit of advice to people posting new threads.
Tags can help keep our G4 section looking professional and clean.
Just add tags before your thread title.
You need help [question] or [help]
U want to make a tut. [ tutorial] or [guide]
Etc...
Click to expand...
That's a great idea. I've been doing that over in the awe section. Is there a set of guidelines for what tags to add?
 
no real quidelines for tags that im aware of. and as far as converting the root method you can just use fastboot to boot cwm, mount system, then push the necessary files. no exploit needed really. and that isnt done in the main code thats done in a .junkie file which i never fully perfected to my liking
 
the java tool itself can be adapted for any phone using a plugin file i called .junkie files to avoid confusion and conflicts. load up the plugin and said phone is added to the program, the program runs on windows, linux, or mac, and it has alot of neat little extras like buildprop editor but i never continued it kuz superr came out with something better for a novice user
 
i can adapt it for these phones if thats what people really want and teach you guys to make a .junkie file, but it still leaves the need for the user to get drivers working where as superrs tool doesnt
 
@Cooldudezach I dont guess there are rules to it, you could probably even double it up.
Ex.
[HELP][question][brick] ....................................words here..

@Junkie , How many languages you code in? I see C++ java bash lol .good stuff bro
 
I have a question. The system.prop is just a copy of the build prop from the phone?
Also in your tree @ Junkie it says msm8960 but we are on a msm8930 snapdragon 400.. is this an update you hadnt got to or typo?
 
8930 didnt exist when that cm came out... and its all still krait. look at other 8930 devices it works

and the system prop is NOT just a copy, right now it is but its not supposed to be
 
heres the thing tho, adjusting the buildprop is not gonna be your first priority, getting a build that boots is then you can make a proper buildprop
 
right now all you guys really need to worry about is ramdisk and stock files. its a guessing game at this point, keep throwing stock files and shit at it till it comes on to the point of getting logcat
 
stock binaries and stock libs, some of them the phone cant boot without, some of them cm wont boot with, good luck. also the best way to test is to build all you can non stock then start throeing things at it manually, its just an educated guessing game tho
 
You must log in or register to reply here.
Back
Top Bottom