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

Root Lets root this thing.

Hello guys I am (small time) dev, sadly not for Android devices, but I am here to change that. I would like to begin my attempting to root this device. I know C, and C++ fairly well. (besides the regular web languages PHP,SQL,etc..) So if anyone here could help me start up, I would greatly look through and spend a good amount of time trying to mess with it. I will contact other devs for assistance also.
 
Hello guys I am (small time) dev, sadly not for Android devices, but I am here to change that. I would like to begin my attempting to root this device. I know C, and C++ fairly well. (besides the regular web languages PHP,SQL,etc..) So if anyone here could help me start up, I would greatly look through and spend a good amount of time trying to mess with it. I will contact other devs for assistance also.

Welcome to the AndroidForums, irapbeterthanu :).

I'm sure the folks here in the Quattro area would appreciate any and all help with rooting their device.

Not all root exploits require programming knowledge--oftentimes a stubborn doggedness and some ingenuity are what's required (with a bit of insight about what has worked before or might be exploited this time).

I'm aware of these type of root exploits:

- via adb (many based off of this--tricking adb to give you a root shell)

- file permission exploits (getting your file to be run as root via insertion into a file that was not properly secured)

- kernel / memory exploits (buffer overruns, code insertions, etc.)

- forcing race / timing conditions (often involving hardware or a driver)

- unlocked bootloader / S-OFF, etc.

- using a manufacturer's installation / maintenance software (like HTC's RUU) to flash a signed ROM for you

And many, many others...

Also, since Android is based on Linux at it's core, some Linux exploits might also apply:

 
Welcome to the AndroidForums, irapbeterthanu :).

I'm sure the folks here in the Quattro area would appreciate any and all help with rooting their device.

Not all root exploits require programming knowledge--oftentimes a stubborn doggedness and some ingenuity are what's required (with a bit of insight about what has worked before or might be exploited this time).

I'm aware of these type of root exploits:

- via adb (many based off of this--tricking adb to give you a root shell)

- file permission exploits (getting your file to be run as root via insertion into a file that was not properly secured)

- kernel / memory exploits (buffer overruns, code insertions, etc.)

- forcing race / timing conditions (often involving hardware or a driver)

- unlocked bootloader / S-OFF, etc.

- using a manufacturer's installation / maintenance software (like HTC's RUU) to flash a signed ROM for you

And many, many others...

Also, since Android is based on Linux at it's core, some Linux exploits might also apply:



You might wanna ask Shabbypenguin what dan tried on my phone to get a better insight on things
 
i am not at liberty to discuss what exploits may or may not have been used when you were connected.

i tried levitator here is the log of it:

$ ./levitator
./levitator
[+] looking for symbols...
[+] resolved symbol commit_creds to 0xc00963dc
[+] resolved symbol prepare_kernel_cred to 0xc0096284
[-] dev_attr_ro symbol not found, aborting!

we know zergrush, RATC, gingerbreak etc arent going to work. you need some form of new exploit usually made for the device in question.
 
i am not at liberty to discuss what exploits may or may not have been used when you were connected.

i tried levitator here is the log of it:



we know zergrush, RATC, gingerbreak etc arent going to work. you need some form of new exploit usually made for the device in question.
o figured dan might have maybe told ya what he tried.. did he say anything about the error code?
 
o figured dan might have maybe told ya what he tried.. did he say anything about the error code?

he said it didnt look good. he doesnt tell me what he tries as one less person that knows about the exploits he knows about there is less chance of them being wasted and going public.

I Hope An Exploit For The Quattro 4G Comes Soon. I Cant Waitt To Overclock This And Put An ICS Or JB ROM On It!
rooting doenst mean you can overclock or put a rom on. has anyone checked the bootloader to see if its unlocked and has fastboot access?
 
he said it didnt look good. he doesnt tell me what he tries as one less person that knows about the exploits he knows about there is less chance of them being wasted and going public.

Are we talking about djrbliss here, Shabby?

rooting doenst mean you can overclock or put a rom on. has anyone checked the bootloader to see if its unlocked and has fastboot access?

Yeah, looks like radford confirmed fastboot access in post #2 (edit: and unlocking didn't work).
 
indeed we are :) me and him are pretty good buddies.

if there is fastboot then you could always flash cwm if its not locked

:eek: 'Nuff said ;) :) [I'm a bit jealous, though :p].

:)

~ ~ ~

Sorry if you didn't catch my late edit on the post about fastboot. I added the part about radford saying that unlocking didn't work :(.
 
my daughters have this phone and having two unrooted androids in the house is making my eye twitch. would it be of any help if i were to purchase one and send it to someone with real ability/chance to root this thing? i understand the risks of the phone locking up or whatever just wanna see it happen (root not brick). and also dont anyone get your hopes up on getting a free phone. there are only a select few that post here i would consider sending it to. so chances are it aint you lol
 
my daughters have this phone and having two unrooted androids in the house is making my eye twitch. would it be of any help if i were to purchase one and send it to someone with real ability/chance to root this thing? i understand the risks of the phone locking up or whatever just wanna see it happen (root not brick). and also dont anyone get your hopes up on getting a free phone. there are only a select few that post here i would consider sending it to. so chances are it aint you lol
already offered the same thing. i was told its not needed but thanx.
 
already offered the same thing. i was told its not needed but thanx.

what he said. at least regarding the team im on.. if djrbliss couldnt find an exploit remotly then having it really doesnt change much.

as it stands the best shot for you guys is figuring out how the OP got into fastboot mode and replicate it. you do that you might have a shot at flashing cwm directly from fastboot and rooting via that way...

with all that being said im sure there is someone out there willing to make the claim of how they would try rooting but they can mess around cuz its their work/mom's/wife's phone and dont want to risk bricking it. the sad truth is 99.999999% of teh time there isnt even a whisper of the word brick/bootloop possible with root (the ones that worry people the most are htc devices cuz you have to overwrite some low level stuff to get past their bootloaders which can brick)
 
I just ran fastboot. It's stuck at waiting for device. I do have the drivers installed, I think. I can't be sure now. Will have to recheck and make sure
 
Can't You Try To Get A Nandroid Backup And Put The SU.apk In An Update Zip Like The Huawei Activa 4G?

I'm guessing it's not that simple since it looks like that device's (the Huawei ) stock recovery will flash an update.zip that not signed with the manufacturer's (usually secret) signing keys.

I can't say for sure though because I don't have a Quattro to test this on :).

FYI, typically, to take a Nandroid backup, you need to have a custom recovery installed. To have a custom recovery installed, you need to be able to either soft boot a custom recovery from fastboot (which requires an unlocked bootloader / S-OFF device) or the ability to overwrite the stock recovery with the custom recovery (which requires that the stock recovery file/partition be writable which (typically) requires root).

Can't hurt to try, though :).
 
I tried flashing an update.zip through recovery with superuser and su and always got a signature fail. Tried several signing options and still failed. PG said that you could try signing the zip with a certain flag via command prompt, but he forgot which flag to use and cant find the site he saw it on, lol.
 
Just installed root browser to see if I can find anything. Haven't got too far into it, yet, but found something interesting. Default.prop, on my phone, is dated December 31, 1969.

weird.

When I viewed the file with a text editor, I got the following:

ADDITIONAL_DEFAULT_PROPERTIES

ro.secure=1
ro.allow.mock.location=0
re.debuggable=0
persist.service.adb.enable=0

Not sure if that will be any help with anything, but at least I'm trying, and learning things as I go.
 
Back
Top Bottom