Database Develop

Phone Freezes Randomly (Magic 32B)

Well i´ve got a problem.
I´ve got a Magic 32B (i think its better in the G1´s forum) and it freezes randomly, since i´ve rooted it.
I´ve tried several roms, but the problem is still there.
I´ve tried some sd cards, but it still freezes.
I´ve updated the Radio and the spl (Radio : 2_22_19_26I & Death SPL)
well. i dont know what to do now. it freezes, the display´s still on, but its.. frozen. then half a minute later, it reboots. but its not a kernel panic. it reboots completely.
please help

There's only one thing to do in a situation like this.......
.........get a Dream (G1)!

thank you -. - i really dont need answers like this one.

Also, this is in the WRONG section, this isn't DEVELOPMENT its a Q and A so put it in the QandA section

reformat your sd card(fat32) re partition it , the wipe EVERYTHING YOU CAN ON YOUR PHONE, and flash a STABLE ROM. LIKE SUPERD OR CYANOGENS ROM.

Oh you bricked it, say hello to your new lawn ornament

boldfilter said:
Oh you bricked it, say hello to your new lawn ornament
Click to expand...
Click to collapse
he didnt brick man

boldfilter said:
oh you bricked it, say hello to your new lawn ornament
Click to expand...
Click to collapse
haha hehe
hehe haha

nickstewartroc said:
Also, this is in the WRONG section, this isn't DEVELOPMENT its a Q and A so put it in the QandA section
Click to expand...
Click to collapse
1. Where's your badge? Knock it off tryin to police **** around here.
2. His question has to do with development, sooooooooooooooo....
Knock it off tryin to police **** around here.
3. Since you wanna be a MOD, why don't you put it in Q & A where it (according to you) belongs.
ps.
Knock it off tryin to police **** around here.

@wcdisciple thank you very much
so does someone knows how to fix that problem... please..

alutastisch said:
@wcdisciple thank you very much
so does someone knows how to fix that problem... please..
Click to expand...
Click to collapse
I'm not sure where your problems can stem from.
That being said, I try some of the suggestions stated above, ie.,
1. Complete wipe
2. Repartiton SDcard
3. Maybe even invest in a new battery (you never know)
4. Those are the things I would've tried. Those same things can pretty much eliminate most problems.
5. If all else fails.........get a Dream (G1)
Or you could pray to the Cell Phone Gods...........
Seriously, I know I haven't been much help, but the suggestions I put forth is what I'd do.
Don't forget to pray!
HEHEHEHHAHAHAHAHHEHEHEHAHAHAHAHAHA

wcdisciple said:
1. Where's your badge? Knock it off tryin to police **** around here.
Click to expand...
Click to collapse
Communities police themselves and don't need no STEENKIN' badges to do that. If you don't have an ARM compiler or the Android SDK on your computer you are not a developer and have no business creating new topics in this subforum.
2. His question has to do with development, sooooooooooooooo....
Knock it off tryin to police **** around here.
Click to expand...
Click to collapse
Rooting your phone does not make you a developer. If you don't have an ARM compiler or the Android SDK on your computer you are not a developer and have no business creating new topics in this subforum.
3. Since you wanna be a MOD, why don't you put it in Q & A where it (according to you) belongs.
Click to expand...
Click to collapse
You don't have to be a mod to know who is the intended audience for a forum section. If you expect free technical support the very least you can do is to help out the people doing it by filing your request appropriately and doing your own damn leg work.
ps.
Knock it off tryin to police **** around here.
Click to expand...
Click to collapse
Do YOU have the Android SDK or an ARM compiler installed? Then YOU bugger off back to Q&A.

marxmarv said:
Communities police themselves and don't need no STEENKIN' badges to do that. If you don't have an ARM compiler or the Android SDK on your computer you are not a developer and have no business creating new topics in this subforum.
Rooting your phone does not make you a developer. If you don't have an ARM compiler or the Android SDK on your computer you are not a developer and have no business creating new topics in this subforum.
You don't have to be a mod to know who is the intended audience for a forum section. If you expect free technical support the very least you can do is to help out the people doing it by filing your request appropriately and doing your own damn leg work.
Do YOU have the Android SDK or an ARM compiler installed? Then YOU bugger off back to Q&A.
Click to expand...
Click to collapse
Junior member wannabe fail?
Anyway, the main thing is is that if your phone is relying on your SD card like for Apps2SD you could run into some problems with a badly formatted card. Would you be able to post a logcat of one of these crashes? It would help a lot in trying to find and identify the problem and then fix it.

mattv888 said:
Junior member wannabe fail?
Anyway, the main thing is is that if your phone is relying on your SD card like for Apps2SD you could run into some problems with a badly formatted card. Would you be able to post a logcat of one of these crashes? It would help a lot in trying to find and identify the problem and then fix it.
Click to expand...
Click to collapse
Read my sig. respect all members, everyone has rights on this forum as long as they follow the rules.

guys, please, could you please stay by the topic?
i still need help

alutastisch said:
guys, please, could you please stay by the topic?
i still need help
Click to expand...
Click to collapse
This sounds more likely to be a hardware issue, I've heard of many cases of it on the forums every month or so.

but why should it be a hardware issue? i mean, before i rooted it, it worked perfect. but now..

alutastisch said:
but why should it be a hardware issue? i mean, before i rooted it, it worked perfect. but now..
Click to expand...
Click to collapse
Yes, some people had the exact same hardware problem as you. You can try to un-root and root again but the problem may still be persist.

okay, thank you. i´ll try it tomorrow, then I tell you if it worked

Hey wazup man well i see what u talking about but i also have a MT3G (32B) and i had no problems with it. Its just depends of the rom you put on it cuz not all roms are stable some are beta or still working on the rom. So what you need do is find roms that are stable. Try find a rom in here go to the search Tap>and put this SuperCSDIX10 im using right now that rom and its FAST so hopwe it helps out

[PRJ] CM6 system 8/27/2010 ALPHA

Here is the CM6 system built last night by me. Go ahead and do whatever you want with it. This is for those having issues building. Here it is
www.justanotherdev.slackdev.com/froyo.tgz
This is not a ready to flash ROM but just the system folder from the CM6 build for people to play with.
This is for devs looking to play with CM6 which was compiled for the vibrant and not just a generic build. This is NOT A READY TO FLASH ROM. I just built went to sleep and threw this up for people.
Enjoy!

?
can we flash this through odin? pda?

skater991 said:
can we flash this through odin? pda?
Click to expand...
Click to collapse
This is not a ready to flash ROM but just the system folder from the CM6 build
Honestly...

skater991 said:
can we flash this through odin? pda?
Click to expand...
Click to collapse
maybe you shouldnt flash anything cause it seems you dont read thoroughly enough... one day youll miss a step and brick your phone lol

nice! , im gonna mess a bit with it.

DO IT SKATER! lol

nick_karstedt said:
DO IT SKATER! lol
Click to expand...
Click to collapse
lol you should specify which one

The CyanogenMod Wiki Full Update Guide for the Samsung Vibrant
The CyanogenMod wiki has the instructions for the Full CM6 update. I am unable to post the link since I am a new member! I haven't flashed the ROM since I just got my phone last night.

skater4690 said:
lol you should specify which one
Click to expand...
Click to collapse
LOL
10 char

skater991 said:
can we flash this through odin? pda?
Click to expand...
Click to collapse
I couldn't help but smile at that.

skater991 said:
can we flash this through odin? pda?
Click to expand...
Click to collapse
Use odin, you'll love the results

just flashed through cw, runs pretty smooth but needs work...
lol jk

98classic said:
just flashed through cw, runs pretty smooth but needs work...
lol jk
Click to expand...
Click to collapse
Nice attempt at hiding that "lol jk"

chad658eku said:
The CyanogenMod wiki has the instructions for the Full CM6 update. I am unable to post the link since I am a new member! I haven't flashed the ROM since I just got my phone last night.
Click to expand...
Click to collapse
Where was that indicated? There are only two how-tos on the Wiki for CM6 of relevance for Galaxy S/Vibrant: building the CM6 kernel from source, and updating the Galaxy S/Vibrant to CM6. However, the "Full Update Guide" includes the following caveat: NOTE: As of right now CyanogenMod is not available for the Samsung Vibrant.
There are no full instructions on the wiki for building CM6, nor for truly updating a Vibrant since CM6 has not been built for the Vibrant. You will also not find even an alpha release, nor any nightlies.
For those who don't understand why this is the case, or why flashing a ROM through Odin is different than through the recovery console, it's probably best to wait until there is a "one-click" for you ...

so many people are going to download this without realizing that this is for development only and not even for use yet

designerfx said:
so many people are going to download this without realizing that this is for development only and not even for use yet
Click to expand...
Click to collapse
I agree but the OP seemed to be clear about it's intended use so it's buyer beware I feel...

rpcameron said:
For those who don't understand why this is the case, or why flashing a ROM through Odin is different than through the recovery console, it's probably best to wait until there is a "one-click" for you ...
Click to expand...
Click to collapse
I semi understand that stuff but know my limits... But a huge THANKS!!! to those who do!!!
Patiently waiting for "one-click"....

Sorry if you took that as a genuine offer of advice, but it was meant as a sarcastic retort. People who don't understand what is technically involved in "rooting", what it means to "mount" a device or where the line between Linux and Android lays really have no basis in asking for aid when things go awry. (Sorry if I offend you, but seriously, you're asking for help in a development thread without knowing about which what you're actually asking for help? Really? Seriously?!)
No one has created a reliable method to fully supplant the Vibrant's recovery console, the OTA package that is normally used to flashed Android devices cannot be properly compiled and packaged for the Vibrant, users are still having issues building an AOSP directory structure—let alone a truly usable boot.img—and a complete system replacement is expected?! It really is no wonder why those really building apps and systems for various Android platforms avoid XDA, and leave it to those merely "cooking" as was previously the standard with WinMo.
(When is the interrobang going to be finally accepted as a true form of punctuation?! Really?!)

nice work, seems like a lot of devs are finally on this

rpcameron said:
Sorry if you took that as a genuine offer of advice, but it was meant as a sarcastic retort. People who don't understand what is technically involved in "rooting", what it means to "mount" a device or where the line between Linux and Android lays really have no basis in asking for aid when things go awry. (Sorry if I offend you, but seriously, you're asking for help in a development thread without knowing about which what you're actually asking for help? Really? Seriously?!)
No one has created a reliable method to fully supplant the Vibrant's recovery console, the OTA package that is normally used to flashed Android devices cannot be properly compiled and packaged for the Vibrant, users are still having issues building an AOSP directory structure—let alone a truly usable boot.img—and a complete system replacement is expected?! It really is no wonder why those really building apps and systems for various Android platforms avoid XDA, and leave it to those merely "cooking" as was previously the standard with WinMo.
(When is the interrobang going to be finally accepted as a true form of punctuation?! Really?!)
Click to expand...
Click to collapse
People don't stay away from XDA because of the sometimes foolish questions people ask. They stay away because of the way they get treated by pompous d*cks like you that have no tolerance for people trying to learn and enjoy their devices more.
Everyone starts out without a clue and without help from others we'd all still be drooling on ourselves and sh*tting in our diapers.
Grow up and help out... or just go away.

Help on my rom

I built a very basic rom and when I install it on cwm it installs then I reboot and It installs the kernal but not the rom
Any idea why?
Sent from my SAMSUNG-SGH-I897 using XDA App

Two posts, just joined in January and you're already building ROMs? Did you read the ROM Building How-To sticky in the General forum?
http://forum.xda-developers.com/showthread.php?t=928955

Yea
Dude I'm into building stuff and o don't post becuz I find no reason too I can normally find things
And before Jan I used my friends account then I made this
Sent from my SAMSUNG-SGH-I897 using XDA App

well i found the error in my update script
its fixed now

Well if you ever want to post your Phonebrick.zip to the devs forum you need at least 10 posts lol Just teasing. Always good to have more developers around. We will see if you stick around though.

Groundhack said:
Well if you ever want to post your Phonebrick.zip to the devs forum you need at least 10 posts lol Just teasing. Always good to have more developers around. We will see if you stick around though.
Click to expand...
Click to collapse
lol thanks ill try to stick around for a while
btw idk if u could help me but for the installation it stops at
E:Cant chown/mod/system/etc/init.d
(no such file or directory)
E: faliure at line 80
set_perm_recursive 0 0 0777 0777 system: etc/init.d
installation aborted

that means you dont have a /system/etc/init.d folder in your rom zip

Pirateghost said:
that means you dont have a /system/etc/init.d folder in your rom zip
Click to expand...
Click to collapse
do u know were i could get this?
i tried looking around and i couldnt find it...
Edit nvm i found my error
i feel so dumb right now.....

hey would u happen to know how to make my rom so its rooted
cuz i got it to install and so far im happy with it but its not rooted and i want to know how to make it so that it is rooted

Are Custom Roms secure?

I have been wondering, how secure are android roms? What I mean is, if I should be worried about getting personal data stolen or any such thing concerning web surfing, online purchases, etc? Which is more secure? Stock Roms or cusom Roms? Any help would be greatly appreciated! Thanks!

Supermannypr said:
I have been wondering, how secure are android roms? What I mean is, if I should be worried about getting personal data stolen or any such thing concerning web surfing, online purchases, etc? Which is more secure? Stock Roms or cusom Roms? Any help would be greatly appreciated! Thanks!
Click to expand...
Click to collapse
Grow up mate... :laugh:
There are thousands of user who are enjoying custom roms and still you think it insecure...

erpurohit said:
Grow up mate... :laugh:
There are thousands of user who are enjoying custom roms and still you think it insecure...
Click to expand...
Click to collapse
This is a harsh response to what I believe is a very valid question by the original poster. People ask questions because they have concerns or simply do not know the answer. They do not need people like you having a shot at them simply because they asked a question.
To the OP: The people who put together the custom ROMs you find on XDA are mostly genuine people looking to share their knowledge and experience by building ROMs that make our devices operate faster, smoother, and feature enhanced. They are not out to load them with malware to scam you and suck your credit and identity dry.
Having said that however, it could be done if the wrong person or group of people starting building ROMs with that purpose.
I personally will only ever download a ROM from a builder or group of builders who have a credible reputation here in the Forums to be sure.
I hope that eases you mind a little.
Take care.

I didnt meant to be harsh... Sry if it feel so...

Thankyou.
Trinnity66 said:
This is a harsh response to what I believe is a very valid question by the original poster. People ask questions because they have concerns or simply do not know the answer. They do not need people like you having a shot at them simply because they asked a question.
To the OP: The people who put together the custom ROMs you find on XDA are mostly genuine people looking to share their knowledge and experience by building ROMs that make our devices operate faster, smoother, and feature enhanced. They are not out to load them with malware to scam you and suck your credit and identity dry.
Having said that however, it could be done if the wrong person or group of people starting building ROMs with that purpose.
I personally will only ever download a ROM from a builder or group of builders who have a credible reputation here in the Forums to be sure.
I hope that eases you mind a little.
Take care.
Click to expand...
Click to collapse
I have always had that question. I have to agree on only installing roms from devs with a credible reputation, at the end of the day this is what I would use for everything and I need to feel ane be sure I am secure. Thanks for your answere, I can keep my peace in that aspect.
Thanks to all the devs that dedicate there time with their amazing Rom projects!! Keep up the great work!!!

Allmost every "custom" roms include a rooted kernel and CWM recovery. That will give anyone who can do "adb" operations the option to reboot your phone to recovery. Sim,pattern or pin lock doesn't matter as long as phone is in their hand.
Battery off - reboot to CWM, connect usb, and everything on your phone is available to copy to computer using adb commands.
The only way to secure custom ROM run by a rooted kernel with CWM is to ENCRYPT all files on your phone.

As a ROM Maker, I always care about every permissions for every single file. I everytime match everything true permissions but not 777 even if I fail 999 times.
Sent from my GT-I9000 using xda app-developers app

Think about this. Someone finds your phone, you had lost it. Turns off pulls out sim so you can't find its location, reboots into recovery, connects to computer, then adb shell and do the command dd /data. Dumps all the data into a .IMG file. Repacks it into an Odin flash able tar. Flashes to his phone. Has all your info.
I wouldn't worry though, most people know nothing of this. I don't worry
Sent from my GT-I9000 using xda premium

O-T and AlwaysDroid, you guys are absolutely right, but the OP still raises a legitimate concern. There's lots of other threat assessments that will rule out physical access. It's a matter of practicality. In some places, traditional martial arts self-defense training can help or save you, in others most clashes do not involve hand-to-hand fighting.
I'm typing on xda app, do forgive Mr for forgetting names, but others here are right, too. A developer's reputation goes a long way, and these teams also put their code out for others to see. I can't tell what's inside, but rely on the fact that others look at it to learn, compile themselves, cherry pick, etc. Also, I do prefer when devs post MD5s.
Back to OP, which primarily asked about data leakage, is there an android equivalent of Little Snitch on Macs?
sent from a telephonic device

Yes they are
use basic custom roms if u wish. . which r stable..
dont prefer nightlies/ alpha if u r a starter
---------- Post added at 12:19 PM ---------- Previous post was at 12:13 PM ----------
burakgon said:
As a ROM Maker, I always care about every permissions for every single file. I everytime match everything true permissions but not 777 even if I fail 999 times.
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
Nobody like frequent force closes.. do they ?

AlwaysDroid said:
Think about this. Someone finds your phone, you had lost it. Turns off pulls out sim so you can't find its location, reboots into recovery, connects to computer, then adb shell and do the command dd /data. Dumps all the data into a .IMG file. Repacks it into an Odin flash able tar. Flashes to his phone. Has all your info.
I wouldn't worry though, most people know nothing of this. I don't worry
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
Wow! I had no idea that someone could do that... I know that this has a very slim chance of happening, but is there anyway to avoid it?

Yes, they are.

since the source is open to all
and anyone could examine it
i would say they are somewhat secure

Supermannypr said:
Wow! I had no idea that someone could do that... I know that this has a very slim chance of happening, but is there anyway to avoid it?
Click to expand...
Click to collapse
Not really :/ almost no one can do this, I mean unless the guy that finds your phone is a resident here or at roots wiki and even then, I doubt it. The thing is, as long as your rooted, your data just isn't as safe. You couldn't do that on stock, cause its not rooted. The only thing I could imagine for the future would be a recovery that asks for a pin code before allowing you to enter. Its unavoidable, and really nothing to worry about. Just turn off USB debugging when not in use, use dev options to only give apps root access and not adb (not sure if it stops it in recovery as well) and don't lose your phone.
Sent from my GT-I9000 using xda premium

Apropos encryption
O-T said:
Allmost every "custom" roms include a rooted kernel and CWM recovery. That will give anyone who can do "adb" operations the option to reboot your phone to recovery. Sim,pattern or pin lock doesn't matter as long as phone is in their hand.
Battery off - reboot to CWM, connect usb, and everything on your phone is available to copy to computer using adb commands.
The only way to secure custom ROM run by a rooted kernel with CWM is to ENCRYPT all files on your phone.
Click to expand...
Click to collapse
Is there a way to enable file system encryption in Cyanogenmod 7?

AW: Are Custom Roms secure?
de333 said:
Is there a way to enable file system encryption in Cyanogenmod 7?
Click to expand...
Click to collapse
System encryption is a 4.1 feature; not with cm 7
Sent from my Nexus 7

Well, Samsung stopped updating this capable phone which is similar to the nexus s(they claimed it can't handle ICS or jb while nexus s gets the latest firmware) Custom ROMs especially jb ROMs make your phone feel new unlike stock which are outdated. Just flash one from a credible developer & u won't regret

There is no motive from the developers. What should they get? Your FB passwords? And sell them to your girlfriend?

Agree
Supermannypr said:
I have always had that question. I have to agree on only installing roms from devs with a credible reputation, at the end of the day this is what I would use for everything and I need to feel ane be sure I am secure. Thanks for your answere, I can keep my peace in that aspect.
Thanks to all the devs that dedicate there time with their amazing Rom projects!! Keep up the great work!!!
Click to expand...
Click to collapse
I am 100% agree, with the your comment bro. We should install the ROM from recognized and good reputed developers.
:good::good::good::good:

Eirwn said:
There is no motive from the developers. What should they get? Your FB passwords? And sell them to your girlfriend?
Click to expand...
Click to collapse
Really? So if there was - just for the sake of argument - a backdoor or a keylogger on your phone that was placed there by a dev, you're saying they would get nothing out of that? Is a bit naive dont you think?

How to root Pixel / XL on 7.1?

I'm wondering what the process for the Pixel devices is, and if anyone has had any success with existing tools/SuperSU.
It's running 7.1 if that's relevant.

sturmeh said:
I'm wondering what the process for the Pixel devices is, and if anyone has had any success with existing tools/SuperSU.
It's running 7.1 if that's relevant.
Click to expand...
Click to collapse
The same way you root other phones, flash custom recovery and supersu.
Sent from my SCH-R220

mattzeller said:
The same way you root other phones, flash custom recovery and supersu.
Sent from my SCH-R220
Click to expand...
Click to collapse
I guess I have to wait for custom recoveries that support this phone then? I can't see a build for TWRP that supports sailfish.

sturmeh said:
I guess I have to wait for custom recoveries that support this phone then? I can't see a build for TWRP that supports sailfish.
Click to expand...
Click to collapse
You'll first need to unlock the bootloader and then wait for chainfire's magic. It is possible to root through fastboot also so there is a good chance that you'll get root before a custom recovery.
Due to seamless updates, things have changed a bit so it'll take some time to be figured out

eatsleep said:
You'll first need to unlock the bootloader and then wait for chainfire's magic. It is possible to root through fastboot also so there is a good chance that you'll get root before a custom recovery.
Due to seamless updates, things have changed a bit so it'll take some time to be figured out
Click to expand...
Click to collapse
Buy it directly from Google and the bootloader won't be locked, only if you buy it through a carrier like Verizon will the bootloader be locked
Sent from my SCH-R220

This is the first device with Android's new partition layout. Having looked at the firmwares and at running devices (remotely), I have some ideas on how to do it.
However, it will be a while before I have SuperSU fixed up. The changes will be quite a bit of work and testing, and doing so remotely will make that take significantly longer. So I'm just going to wait for my own device, but as they aren't available in my country, it has to be shipped from another country and go through customs. I don't expect my device to arrive for another week or two.
In the meantime, it's always possible someone else releases root for it.
I saw @jcase and @Dees_Troy have been playing with TWRP, to me it seems wholly possible to fix that up (mostly) as well. But even if TWRP is released tomorrow, using the existing SuperSU ZIP will not work on it, due to all the breaking changes in Android 7.1.

Will be interesting if you can do it CF... Looking forward to release - Ill send a donation your way when done

fkofilee said:
Will be interesting if you can do it CF... Looking forward to release - Ill send a donation your way when done
Click to expand...
Click to collapse
The worst possible thing you could write...

ldeveraux said:
The worst possible thing you could write...
Click to expand...
Click to collapse
Hmmm... Does it matter ive donated like 3 or 4 times to him already over the years xd
Either way looking forward to it

fkofilee said:
Hmmm... Does it matter ive donated like 3 or 4 times to him already over the years xd
Either way looking forward to it
Click to expand...
Click to collapse
If your intent was truly altruistic, you wouldn't feel the "burden" of stating it publicly. So no, it doesn't matter.

Chainfire said:
This is the first device with Android's new partition layout. Having looked at the firmwares and at running devices (remotely), I have some ideas on how to do it.
However, it will be a while before I have SuperSU fixed up. The changes will be quite a bit of work and testing, and doing so remotely will make that take significantly longer. So I'm just going to wait for my own device, but as they aren't available in my country, it has to be shipped from another country and go through customs. I don't expect my device to arrive for another week or two.
In the meantime, it's always possible someone else releases root for it.
I saw @jcase and @Dees_Troy have been playing with TWRP, to me it seems wholly possible to fix that up (mostly) as well. But even if TWRP is released tomorrow, using the existing SuperSU ZIP will not work on it, due to all the breaking changes in Android 7.1.
Click to expand...
Click to collapse
Confirmation number: 57C48888US937054E

Chainfire said:
This is the first device with Android's new partition layout. Having looked at the firmwares and at running devices (remotely), I have some ideas on how to do it.
However, it will be a while before I have SuperSU fixed up. The changes will be quite a bit of work and testing, and doing so remotely will make that take significantly longer. So I'm just going to wait for my own device, but as they aren't available in my country, it has to be shipped from another country and go through customs. I don't expect my device to arrive for another week or two.
In the meantime, it's always possible someone else releases root for it.
I saw @jcase and @Dees_Troy have been playing with TWRP, to me it seems wholly possible to fix that up (mostly) as well. But even if TWRP is released tomorrow, using the existing SuperSU ZIP will not work on it, due to all the breaking changes in Android 7.1.
Click to expand...
Click to collapse
Appreciate all you do Chainfire, seriously. Can't wait for you to work your magic

Ah its so funny to what people write after all these years of people spending their own time to work out back doors and exploits to enable root / Xposed / Custom bootloaders / Kernels / Recoveries.
People can't just wait and see and if the devs ask for help or testers just be part of it, throwing a few dollars at them is not going to push things forward . . . let them do what they want to do its their project / baby and it will happen when it does.
Support the devs after the fact dont try and attempt to influence them into it with beer money.

Some of y'all are ridiculous! The guy made a harmless statement and didn't mean anything negative by it. And what do all of the analytical geekers do? Just that... Analyze his comment to the bone and find all sorts of self-serving intent within it. Blows my mind...

hutzdani said:
Ah its so funny to what people write after all these years of people spending their own time to work out back doors and exploits to enable root / Xposed / Custom bootloaders / Kernels / Recoveries.
People can't just wait and see and if the devs ask for help or testers just be part of it, throwing a few dollars at them is not going to push things forward . . . let them do what they want to do its their project / baby and it will happen when it does.
Support the devs after the fact dont try and attempt to influence them into it with beer money.
Click to expand...
Click to collapse
Oh shut up. What a stupid thing to say. People are excited about dev work, and if they suggest a donation, what do you care? Why is it any of your business? If the dev has a problem with people providing positive feedback and offering donations, they will make it known.
---------- Post added at 10:10 PM ---------- Previous post was at 10:08 PM ----------
Ker~Man said:
Some of y'all are ridiculous! The guy made a harmless statement and didn't mean anything negative by it. And what do all of the analytical geekers do? Just that... Analyze his comment to the bone and find all sorts of self-serving intent within it. Blows my mind...
Click to expand...
Click to collapse
Totally agree. Thanks for speaking up!

Chainfire said:
This is the first device with Android's new partition layout. Having looked at the firmwares and at running devices (remotely), I have some ideas on how to do it.
However, it will be a while before I have SuperSU fixed up. The changes will be quite a bit of work and testing, and doing so remotely will make that take significantly longer. So I'm just going to wait for my own device, but as they aren't available in my country, it has to be shipped from another country and go through customs. I don't expect my device to arrive for another week or two.
In the meantime, it's always possible someone else releases root for it.
I saw @jcase and @Dees_Troy have been playing with TWRP, to me it seems wholly possible to fix that up (mostly) as well. But even if TWRP is released tomorrow, using the existing SuperSU ZIP will not work on it, due to all the breaking changes in Android 7.1.
Click to expand...
Click to collapse
Hey I've unlocked my bootloader, but with the different partition layout and file based encryption (assuming this device uses that), is there any chance I'll have to erase my data and start over for root?
Because I got the 128GB model and I'm ready to start filling up with apps and keep a big portion of my Google Play music library to save on data and everything but I don't want to do it if there's a real possibility I'll have to erase everything if to achieve root.
I guess it is possible to use a custom recovery (once they come out) to backup, but that'll be a huge backup if I start keeping all my music to the device.
Sent from my Pixel XL using Tapatalk

tveith said:
Oh shut up. What a stupid thing to say. People are excited about dev work, and if they suggest a donation, what do you care? Why is it any of your business? If the dev has a problem with people providing positive feedback and offering donations, they will make it known.
---------- Post added at 10:10 PM ---------- Previous post was at 10:08 PM ----------
Totally agree. Thanks for speaking up!
Click to expand...
Click to collapse
What ever but tour the same guys who's going to be asking for OTAs and asking devs to do this that and the other as fast as humanly possible.
If you want it that bad do it your self or sit and wait like a good little child.
No dev is going to rush something because of some people in a forum get a grip, like I said it's their time and it will be ready when it's ready.
You might think I'm going off on one but read the rules page for Christ's sakes.

sionicion said:
Hey I've unlocked my bootloader, but with the different partition layout and file based encryption (assuming this device uses that), is there any chance I'll have to erase my data and start over for root?
Because I got the 128GB model and I'm ready to start filling up with apps and keep a big portion of my Google Play music library to save on data and everything but I don't want to do it if there's a real possibility I'll have to erase everything if to achieve root.
I guess it is possible to use a custom recovery (once they come out) to backup, but that'll be a huge backup if I start keeping all my music to the device.
Click to expand...
Click to collapse
The chance you'll have to erase is always present when rooting. Even when your device is fully prepared something may go wrong. At least you have already unlocked your bootloader, which reduces that chance.
File-based encryption will probably not be a reason to for wiping, though. It works fine in the dev version of SuperSU with Android 7.0 on a 5X.

Hey guys. Found this on the interwebs and was wondering how valid it is. http://www.technobuzz.net/root-google-pixel-xl/
Seeing as it calls for twrp which is not yet available, would flashfire work?
Sent from my Pixel using XDA-Developers mobile app

mrnovanova said:
Hey guys. Found this on the interwebs and was wondering how valid it is. http://www.technobuzz.net/root-google-pixel-xl/
Seeing as it calls for twrp which is not yet available, would flashfire work?
Sent from my Pixel using XDA-Developers mobile app
Click to expand...
Click to collapse
Looks interesting, but without twrp you sure are taking a big chance if something goes wrong.
Sent from my Pixel using Tapatalk