Database Develop

Steps to protect private info upon selling G1

Caveat: I am a noob and tried to search first but got too many conflicting threads which did not entirely apply to my phone as far as I could understand. Please no flaming if I am beating a dead horse. I swear the horse died before I started beating it.
You may have read my recent thread where I had asked about how to fix my g1 which was sold to me and the rom crashed leaving it "soft bricked".
Since it was taking so long and I got a good deal on it, I went ahead and bought the Samsung Galaxy S. While waiting for this phone to ship, I have fixed the G1 through the unlocker website's guide for one click rooting.
I started to begin the sign in process after re-rooting the phone with unlocker's generic mod but then thought better since my phone would sync.
My question is since I have gone through the unlocker website's process to re-root the phone, is there any personal info left on the phone that I should remove and how would I do that?
Would it be better, if by re-rooting the phone it wipes all info, to sell it as is?
Should I jail break it and sell it and therefore get more for it?
Should I keep the the sd card?
The phone is in good condition with only minor damage to the sides from dropping it, a screen protector and worked perfectly when I signed in on the original platform.img and I have two batteries for it; the double size and original and two backs and one protective case which I could not put on the larger backing of the larger battery which I should have looked harder for one to fit it eliminating the aesthetic scuffs on the side.
All advice is appreciated; thanks guys.
P.S. I will resist messing with the Samsung or at least backup more often b/c I lost a lot of buisness info when the G1 crashed. Although, I have already applied the GPS fix...it was on cnet for goodness sakes, how could I resist?

Just wipe and reflash any rom... No user data will be left...
Sent from my SGH-T959 using XDA App

junkdruggler said:
Just wipe and reflash any rom... No user data will be left...
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
NOT TRUE!!!!!
Wiping ***DOES NOT*** clear data!
In fact, wiping ONLY clears the FIRST 128 KB of the partition selected for wipe!
If you want to do a proper wipe, you should wipe (also called FORMAT) both the userdata and cache partitions from RECOVERY, mount them in their usual spots, and run "dd if=/dev/zero of=/data/zerofile; dd if=/dev/zero of=/cache/zerofile; sync; rm /data/zerofile /cache/zerofile -f". This line in quotes will write a ZERO to EVERY LOCATION within both the cache and userdata partitions, ensuring that the data is there but not visible, is obliterated.

Re poll question:
Jailbreak that mofo
-- can't break out of a jail that never existed. ANDROID DOES NOT USE CHROOT JAILS.
Keep it rooted, buyers like no assembly required
-- and idiots screw themselves up when they don't know what they're doing....
Vanillarize it/keep it stock; would you buy a toyota home modified into a racecar
-- the meaning of this option is partially indecypherable. I assume you mean "make it stock". Would you really, as a decent human being, lock the buyer out of accessing the device that they legitimately own and have the right to use as they wish?
Jailbreak it and keep it rooted because people like a little coke in their weed
-- again, you can't break out of a jail that does not exist and never has!
You forgot the option to install a stock ROM along with an ENGINEERING BOOTLOADER. If they don't know what they're doing, they won't as likely screw it up. If they DO know what they're doing, they'll be able to use it.

lbcoder said:
Re poll question:
Jailbreak that mofo
-- can't break out of a jail that never existed. ANDROID DOES NOT USE CHROOT JAILS.
Keep it rooted, buyers like no assembly required
-- and idiots screw themselves up when they don't know what they're doing....
Vanillarize it/keep it stock; would you buy a toyota home modified into a racecar
-- the meaning of this option is partially indecypherable. I assume you mean "make it stock". Would you really, as a decent human being, lock the buyer out of accessing the device that they legitimately own and have the right to use as they wish?
Jailbreak it and keep it rooted because people like a little coke in their weed
-- again, you can't break out of a jail that does not exist and never has!
You forgot the option to install a stock ROM along with an ENGINEERING BOOTLOADER. If they don't know what they're doing, they won't as likely screw it up. If they DO know what they're doing, they'll be able to use it.
Click to expand...
Click to collapse
No I don't mean lock them out. I mean installing the STOCK/OEM/INCLUDED IN EVERY BOX platform. I don't understand where you are getting this "lock them out" idea; your first post helpful; your second post a little asidic. Drop the Ph a little. Vanilla has a boring connotation like the stock software which is nothing fancy but nice and safe. Perhaps analogies, metaphors and a touch of misunderstood humor goes over your head. I would add some ad hominem speculation as to why you are speaking so but whatever you are irritated about allow me to quote the Beatles, "Let it be". I would want a little more use out of someone with 2000+ posts as a forum is only as good as its leaders.

dejavecu said:
I would want a little more use out of someone with 2000+ posts as a forum is only as good as its leaders.
Click to expand...
Click to collapse
Your poll is meaningless in the Android world. You talk about both "root" and "jailbreak" as if they are two different things. One doesn't mean anything. lbcoder was trying to help you understand the thing you're trying to sell.

Shrivel said:
Your poll is meaningless in the Android world. You talk about both "root" and "jailbreak" as if they are two different things. One doesn't mean anything. lbcoder was trying to help you understand the thing you're trying to sell.
Click to expand...
Click to collapse
Uggh, notice how I did not reply to his advice except for reverting it to stock and "locking" out the consumer; I found that "indecypherable" but that was much more an issue with tone than the advice itself. Maybe American technology slang is different or I am using it improperly. I don't know which so, to all, if jailbreak is meaningless to you then forget it and please just keep the thread to advice on what you would do. Thanks.

dejavecu said:
Uggh, notice how I did not reply to his advice except for reverting it to stock and "locking" out the consumer; I found that "indecypherable" but that was much more an issue with tone than the advice itself. Maybe American technology slang is different or I am using it improperly. I don't know which so, to all, if jailbreak is meaningless to you then forget it and please just keep the thread to advice on what you would do. Thanks.
Click to expand...
Click to collapse
Look, very simple:
IF you install the stock garbage that comes with the phone, then you ARE LOCKING THE PURCHASER OUT because it will then need to be HACKED to gain proper access.
Also: If YOU do not understand the meaning of certain terms, DO NOT USE THEM!
JAIL has NOTHING to do with ROOT.
JAIL is NOT USED on Android AT ALL.
http://en.wikipedia.org/wiki/Chroot

[Q] How do I root my 2.2.1 N1

I have tried Universal Androot、z4root...but faild...

Read my signature.

Manual method...
http://www.nexusoneforum.net/forum/...mple-sdk-setup-manual-root-guide-windows.html
Sent from my Nexus One using XDA App

I'm not sure why people find it so hard to say 'SuperOneClick' in reply to such an easy question. It's the only one-click method still working for the N1!
As always do your research and read the wiki, but you'll want to find and learn about SuperOneClick for rooting and possibly Rom Manager, if you decide to start using custom ROMs.
If you find yourself at the stage where you are using a custom recovery do yourself a favour and do a Nandroid backup. (learn about that too if you haven't already).

Because:
1) SuperOneClick is not the only option - there is also manual method and the bootloader method.
2) You don't know what tomorrow brings. Wiki will be updated, these threads won't be. Pointing to Wiki will keep the people using updated info. This is what Wiki is for.
3) Personally, I think people asking such question should be banned for a day or two, until they learn to read before asking. It's the most basic question with answers just about anywhere, and it still pops 3 times a week.

Also, the part which people often struggle with, is the setting up the sdk.
Superoneclick and manual methods both require sdk to be set up.
Most of the instructions in the wiki are outdated in this respect (it points to threads, which don't get updated), which is why I wrote the guide in the link, and is also the reason why I pointed to it...
Sent from my Nexus One using XDA App

danger-rat said:
Superoneclick and manual methods both require sdk to be set up...Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
SOC needs nothing to be set-up. Just stick it on your pc and run it.
Advising people to root by unlocking bootloader/manual method is like telling someone to use a sledgehammer to crack a walnut. Sure it'll work but it'll be messy, possibly do collateral damage, and could be done safer/faster/easier with another tool!
The OP was clearly looking for a 1-click method, which is understandable as MOST people do prefer to take the path of least resistance.

DirkGently1 said:
SOC needs nothing to be set-up. Just stick it on your pc and run it.
Click to expand...
Click to collapse
Try it, and enjoy the results. Return to tell us the story of how you waited hours for it to connect to your phone, until your patience ran out.
Advising people to use bootloader or manual methods has a great benefit - it teaches people things about the system that they need to know when going root, and a side benefit of preventing some of the idiocy going on around. Most idiotic threads on XDA came from people that either rooted or attempted to root, while clearly not understanding a thing about the system they're dealing with.

Touche
Sent from my Nexus One using XDA App

danger-rat said:
Manual method...
http://www.nexusoneforum.net/forum/...mple-sdk-setup-manual-root-guide-windows.html
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Cheers! I previously used one-click but am holding onto that guide should I ever need to do it manually

Jack_R1 said:
Try it, and enjoy the results. Return to tell us the story of how you waited hours for it to connect to your phone, until your patience ran out.
Advising people to use bootloader or manual methods has a great benefit - it teaches people things about the system that they need to know when going root, and a side benefit of preventing some of the idiocy going on around. Most idiotic threads on XDA came from people that either rooted or attempted to root, while clearly not understanding a thing about the system they're dealing with.
Click to expand...
Click to collapse
Takes under 2 minutes for me
I'm all for people doing their research, and i always advise people to do just that, including mentioning the wiki...but...
...just look at the SOC thread and the 1.3M + page views
People like 1-click methods!

SOLVED！
SuperOneClick~
many thx~

DirkGently1 said:
Takes under 2 minutes for me
I'm all for people doing their research, and i always advise people to do just that, including mentioning the wiki...but...
...just look at the SOC thread and the 1.3M + page views
People like 1-click methods!
Click to expand...
Click to collapse
You don't seem to understand. The 1-click method STILL requires Nexus drivers from the SDK to be installed - and if you don't have them installed, it won't work!
People that fail with 1-click methods, usually fail because of that. And that's what danger-rat was trying to explain.

Jack_R1 said:
You don't seem to understand. The 1-click method STILL requires Nexus drivers from the SDK to be installed - and if you don't have them installed, it won't work!
People that fail with 1-click methods, usually fail because of that. And that's what danger-rat was trying to explain.
Click to expand...
Click to collapse
Does that vary with operating system? I didn't need to install any sdk drivers on my Win7 install for SOC to work.
Come to think of it i've never had to manually install drivers on Win7 as it has always picked up on everything i've plugged into it. God bless MS

I believe Win7 will automatically install the correct drivers, yes.
Sent from my Nexus One using XDA App

Phew, thought I was losing my marbles there for a minute!

Take a chill pill
Jack_R1 said:
3) Personally, I think people asking such question should be banned for a day or two, until they learn to read before asking. It's the most basic question with answers just about anywhere, and it still pops 3 times a week.
Click to expand...
Click to collapse
You may feel right about this, but no one asked. There are better times, places, and ways to say this without risking looking like a pompous asshole. If you really want to make a difference, try sending the OP a private message so he will understand, or leave a courteous note in your post. I'm pretty sure most people aren't trying to stir up trouble when they post.
Jack_R1 said:
Advising people to use bootloader or manual methods has a great benefit - it teaches people things about the system that they need to know when going root, and a side benefit of preventing some of the idiocy going on around. Most idiotic threads on XDA came from people that either rooted or attempted to root, while clearly not understanding a thing about the system they're dealing with.
Click to expand...
Click to collapse
I'm not really sure about what causes you to impose what other people's goals on this site are. Everyone is here for various reasons, and they aren't necessarily yours.
You are seemingly acting part of bigger problems encompassing the smaller ones that irk you.

Ahhhh, the old "give the man a fish..." vs "teach him how to fish..." debate...
Sent from my Nexus One using XDA App

Hi. How I posted before un SuperOneClick but i cantar enter ti latest AR recovery menu (previously installed) because e3 default recovery os there. I dont want to lost my warranty. thanks!
Sent from my Nexus One using Tapatalk

kubanito09 said:
Hi. How I posted before un SuperOneClick but i cantar enter ti latest AR recovery menu (previously installed) because e3 default recovery os there. I dont want to lost my warranty. thanks!
Sent from my Nexus One using Tapatalk
Click to expand...
Click to collapse
THIS thread may be of some use to you if you haven't seen it before. The wiki is also full of helpful information.
Let us know if you have any furthur questions.

Signature Checks on Boot

Just so everyone is aware, the kernel and the recovery partition signatures are checked on each boot, changing those will leave you with a brick, until we have proper firmware to recovery with.
I found out the hard way.
On my second Atrix now.

Casualty of war

Taking one for the team

Well that sucks..
any free partitions that we can "steal"? and basically pull a haret where it loads partially from legit bootloader and kernel, then shuffles off to a different partition we CAN write for the real kernel, unloads all that other stuff and then launches the new kernel partiion we've modified?

designgears said:
Just so everyone is aware, the kernel and the recovery partition signatures are checked on each boot, changing those will leave you with a brick, until we have proper firmware to recovery with.
I found out the hard way.
On my second Atrix now.
Click to expand...
Click to collapse
I guess that when we told you this, you just had to find out for yourself. The recovery should only be checked when you attempt to access it, but the kernel is checked on every boot. I hope you did not return to store as defective.

DG, thank you for putting yourself out there, and putting together roms along with the dev work.
Its nice to see some progress being done along side all the people on here saying what we shouldnt be doing/trying with our phones.

Athailias said:
DG, thank you for putting yourself out there, and putting together roms along with the dev work.
Its nice to see some progress being done along side all the people on here saying what we shouldnt be doing/trying with our phones.
Click to expand...
Click to collapse
Don't thank him for repeating something which had been confirmed.

jimmydafish said:
I guess that when we told you this, you just had to find out for yourself. The recovery should only be checked when you attempt to access it, but the kernel is checked on every boot. I hope you did not return to store as defective.
Click to expand...
Click to collapse
So you told me it was checked every boot (first bold), but it should only be checked when you access it (second bold)? Confused, on drugs or what?
I just found out the hard way for you, it's checked every boot accessed or not.
If you want to be elitist and not post up a FAQ about what you know (do you even have an atrix), please stop posting in here, you've done nothing but spout off what you know about other moto devices, it is clear they tightened things down a bit more.
jimmypopulous said:
Don't thank him for repeating something which had been confirmed.
Click to expand...
Click to collapse
everything you guys say, along with others says it SHOULD be checked when accessed, which means I should have been able to boot normally and fail when I boot recovery.
You guys keep saying its CONFIRMED, where is it documented for the atrix. Tests performed with document results as proof.

designgears said:
So you told me it was checked every boot (first bold), but it should only be checked when you access it (second bold)? Confused, on drugs or what?
I just found out the hard way for you, it's checked every boot accessed or not.
If you want to be elitist and not post up a FAQ about what you know (do you even have an atrix), please stop posting in here, you've done nothing but spout off what you know about other moto devices, it is clear they tightened things down a bit more.
everything you guys say, along with others says it SHOULD be checked when accessed, which means I should have been able to boot normally and fail when I boot recovery.
You guys keep saying its CONFIRMED, where is it documented for the atrix. Tests performed with document results as proof.
Click to expand...
Click to collapse
What is being elitist by my statement? That before you started playing with your shiny new toy, we advised that doing certain things with your phone without proper firmware to restore your phone, WOULD result in a "soft brick".
I do not have a motorola ATRIX, never said I did, but I can read the firmware pretty well. If your offended by my post I assume it is because offered up my standard line of "hope you did not return it as defective", because nothing else in that statement should lead you behave like a child.
Here how about this for a Facts, my rom was the first to safely remove Blur from the Droid series of phones safely, after reading the firmware from your phone, and your deodexed version of the firmware there are many portions you could remove safely.
If you have questions you could ask and get the answers, but as it stands right now, we are just trying to help you save yourselves. Many people will enter these forums, and while each person is responsible for their own device, they will try to follow what you have done and they too will soft brick their phone. I'm not sure of your ethical and moral makeup but too many people return their manipulated device to the provider as defective causing every to pay for their mistake.
I just hope you bought another Atrix outright and did not scam ATT/Motorola.

designgears said:
So you told me it was checked every boot (first bold), but it should only be checked when you access it (second bold)? Confused, on drugs or what?
I just found out the hard way for you, it's checked every boot accessed or not.
If you want to be elitist and not post up a FAQ about what you know (do you even have an atrix), please stop posting in here, you've done nothing but spout off what you know about other moto devices, it is clear they tightened things down a bit more.
everything you guys say, along with others says it SHOULD be checked when accessed, which means I should have been able to boot normally and fail when I boot recovery.
Click to expand...
Click to collapse
DesignGears,
Please don't let a claim-to-know-it-all self-righteous Prick like jimmydafish discourage your efforts.
As far as I'm concerned (and probably the majority of people who mash the refresh button on this subforum multiple times a day would agree) it's people like you (people who have actively contributed to the users here at XDA in the past (all your captivate work)), that make me feel lucky to own the same type of device that you and other dedicated devs like yourself own.
Its hard to imagine how someone who probably played a very small part on a team -- a team that, as far as I can tell, has never managed to actually produce any real results on the DX -- can know so much about a device he doesn't even own.
And if reading this post encourages members of any such team to get their panties in a wad and start talking about how they are not going to contribute here now, well then to that I say: good riddance. For every one small tip you may provide it seams like you offer two holier-than-thou-doughe-bag-comments that frankly this section of this forum could do without.
But again, thank you DesginGears and Devs like you

mburris said:
DesignGears,
Please don't let a claim-to-know-it-all self-righteous Prick like jimmydafish discourage your efforts.
As far as I'm concerned (and probably the majority of people who mash the refresh button on this subforum multiple times a day would agree) it's people like you (people who have actively contributed to the users here at XDA in the past (all your captivate work)), that make me feel lucky to own the same type of device that you and other dedicated devs like yourself own.
Its hard to imagine how someone who probably played a very small part on a team -- a team that, as far as I can tell, has never managed to actually produce any real results on the DX -- can know so much about a device he doesn't even own.
And if reading this post encourages members of any such team to get their panties in a wad and start talking about how they are not going to contribute here now, well then to that I say: good riddance. For every one small tip you may provide it seams like you offer two holier-than-thou-doughe-bag-comments that frankly this section of this forum could do without.
But again, thank you DesginGears and Devs like you
Click to expand...
Click to collapse
I can assure you I am not, glad to have support.
--
Jimmy, no hard feelins, sorry I wanted try something and learn from it, sorry you told me two opposing things in the same post(this is what I am *****ing about if you would read you would know that), sorry I act like a child, I guess calling it how I see it is childish. From all the PM's about you I just got and mburris reply, you have made my block list, have fun in there with rafy.

jimmydafish said:
I just hope you bought another Atrix outright and did not scam ATT/Motorola.
Click to expand...
Click to collapse
Maybe if more people softbricked and returned phones that have locked down bootloaders, oems and carriers might finally realize that when someone buys a piece of technology, they own it, and would like to use it as such.
That includes:
1. Not having some POS skin on top of stock android (Blur)
2. Not being locked into paying twice for the data we already pay for (tethering)
3. Not being allowed to easily install non-market apps that we develop without jumping through hoops (slide loading)
4. Not having to wait for the carrier or oem mfg to release an update before we can have a current version of Android.
Call it a Brick-n-Return Protest

mburris said:
Maybe if more people softbricked and returned phones that have locked down bootloaders, oems and carriers might finally realize that when someone buys a piece of technology, they own it, and would like to use it as such.
That includes:
1. Not having some POS skin on top of stock android (Blur)
2. Not being locked into paying twice for the data we already pay for (tethering)
3. Not being allowed to easily install non-market apps that we develop without jumping through hoops (slide loading)
4. Not having to wait for the carrier or oem mfg to release an update before we can have a current version of Android.
Call it a Brick-n-Return Protest
Click to expand...
Click to collapse
LOL, that would surely cause some grief over at at&t, and a good laugh.
They would probably start leasing the phones so you can't say you own them.

Closed by OP request as this is an informational thread stating results of testing.

What should we do now?

I rooted my phone using Kingo. It has been perfect. It appears to be totally fine. I get up this morning and find the below comment and closed thread. Do we need to undo root and flash back to stock? Someone please help with this situation. I'm sure a bunch of people did this and would like to know what we should do now. Thanks Devs.
Kingo and vroot have been determined to be malware and unsafe for use, as such all threads will be closed and links removed.
Thank you

LuckyColdJohnson said:
I rooted my phone using Kingo. It has been perfect. It appears to be totally fine. I get up this morning and find the below comment and closed thread. Do we need to undo root and flash back to stock? Someone please help with this situation. I'm sure a bunch of people did this and would like to know what we should do now. Thanks Devs.
Kingo and vroot have been determined to be malware and unsafe for use, as such all threads will be closed and links removed.
Click to expand...
Click to collapse
This thread would be more helpful if it had an informative subject line, such as "What to do about Kingo malware?". The subject you provided ("What should we do now?") gives readers no clue what the thread is about.
Anyway, does anyone know how the malware determination was made, and by whom? Does the purported malware afflict the PC that runs the software, the phone that gets rooted, or both?
Also, I notice that the locked Kingo thread in the dev forum only mentions the malware determination in the last post of the thread. Anyone who just reads the initial post, or who doesn't read all the way to the end, will still think the software has been confirmed ok. (I know the download link in the initial post has been removed, but that has little effect since the software is trivially Googled.)

Gary02468 said:
This thread would be more helpful if it had an informative subject line, such as "What to do about Kingo malware?". The subject you provided ("What should we do now?") gives readers no clue what the thread is about.
Anyway, does anyone know how the malware determination was made, and by whom? Does the purported malware afflict the PC that runs the software, the phone that gets rooted, or both?
Also, I notice that the locked Kingo thread in the dev forum only mentions the malware determination in the last post of the thread. Anyone who just reads the initial post, or who doesn't read all the way to the end, will still think the software has been confirmed ok. (I know the download link in the initial post has been removed, but that has little effect since the software is trivially Googled.)
Click to expand...
Click to collapse
Looking at it now, I agree with the subject line needing to be a little better.
I was just told by a MOD the following. >
So now that I already have Kingo, what do you think I should do ? Keep it, our undo it? Please let me know, because I dont see anything wrong with it. Phone is working great.
MOD Get rid of it, it steals your information and sends it to remote servers and leaves back doors on your device and pc
MOD Correction, it's thought to do these things
Okay, I will undo it......When I plug my phone back up to PC and run Kingo, it has an Unroot option. Should I do it that way? Or should I look for STOCK files that came with the phone and us Odin to flash it? Thanks for your time.
MOD Stock, don't use the app anymore

If it's really malware (I don't know how that determination was made), any passwords, credit-card or bank-account numbers, etc. on your PC or your phone may have been exposed and should be changed now. Your PC and your phone may need to be disinfected, preferably by clean-installing a known-good system.
Just for future reference, when a company with no known track record offers free, unvetted, closed-source software, it's risky to install it on any system whose integrity you care about. That's especially the case when they claim to be a commercial venture but they say that their product will always be free, and there's no apparent way for them to profit from it.
I still don't know what evidence, if any, shows that this software is malicious. But it seemed blatantly suspicious from the beginning, so I've refrained from installing it.
---------- Post added at 11:29 AM ---------- Previous post was at 11:15 AM ----------
LuckyColdJohnson said:
MOD Get rid of it, it steals your information and sends it to remote servers and leaves back doors on your device and pc
MOD Correction, it's thought to do these things
Click to expand...
Click to collapse
Thought by whom, and on the basis of what evidence, if any?

Gary02468 said:
If it's really malware (I don't know how that determination was made), any passwords, credit-card or bank-account numbers, etc. on your PC or your phone may have been exposed and should be changed now. Your PC and your phone may need to be disinfected, preferably by clean-installing a known-good system.
Just for future reference, when a company with no known track record offers free, unvetted, closed-source software, it's risky to install it on any system whose integrity you care about. That's especially the case when they claim to be a commercial venture but they say that their product will always be free, and there's no apparent way for them to profit from it.
I still don't know what evidence, if any, shows that this software is malicious. But it seemed blatantly suspicious from the beginning, so I've refrained from installing it.
---------- Post added at 11:29 AM ---------- Previous post was at 11:15 AM ----------
Thought by whom, and on the basis of what evidence, if any?
Click to expand...
Click to collapse
Well lets see here. The Devs and Moderators do a lot here at XDA. We trust them, and we do things to our phones.
Why wouldn't we trust what they say about certain methods? Threads and links being closed. I'm just saying...
Now I really want to make my phone go back to how it was when I bought it.
If there is anybody that's done it, I would love to know how.
It would be great if I could just use Odin with a file and not trip anything and go back. Please help me/others if this is possible.
Im sick to my stomach now. I knew I should of waited. **** !!!

LuckyColdJohnson said:
Well lets see here. The Devs and Moderators do a lot here at XDA. We trust them, and we do things to our phones.
Why wouldn't we trust what they say about certain methods?
Click to expand...
Click to collapse
So far, no dev or mod has claimed here to have specific evidence that the software in question is malicious.
Sure, there's reason to be suspicious. But that was already obvious just from looking at the Kingo website.

Gary02468 said:
So far, no dev or mod has claimed here to have specific evidence that the software in question is malicious.
Sure, there's reason to be suspicious. But that was already obvious just from looking at the Kingo website.
Click to expand...
Click to collapse
I don't know what to do. I have been rooting and modding phones and other electronics for years and now I feel like it's just not worth it. I trusted XDA and the Devs a lot. Heck a dev said that this way was easier and closed an old thread. So I ran with it and now 2 days later it's closed as well. I'm disappointed

LuckyColdJohnson said:
I don't know what to do. I have been rooting and modding phones and other electronics for years and now I feel like it's just not worth it. I trusted XDA and the Devs a lot. Heck a dev said that this way was easier and closed an old thread. So I ran with it and now 2 days later it's closed as well. I'm disappointed
Click to expand...
Click to collapse
I think you need to look more closely at what it means to trust someone.
I do trust the devs here regarding the integrity of their own software, because their track record gives me evidence that they're trustworthy in that regard. I've flashed ROMs from here many times.
But I don't trust the devs--or anyone in the world--in the sense of automatically believing what they say about everything. I'm sure they wouldn't expect me to.
So if a dev makes an offhand remark that someone else's software (that they have no way of examining) is safe, then of course I'm not going to just take their word for it. And if they make an equally offhand remark that the software is malicious--but fail to mention why they think so--then I'm not going to automatically believe that, either.

LuckyColdJohnson said:
I don't know what to do. I have been rooting and modding phones and other electronics for years and now I feel like it's just not worth it. I trusted XDA and the Devs a lot. Heck a dev said that this way was easier and closed an old thread. So I ran with it and now 2 days later it's closed as well. I'm disappointed
Click to expand...
Click to collapse
Why don't you reroot using De La Vega by DG? Although his method will wipe your phone back to stock but at least you know it works and it's safe.

Gary02468 said:
I think you need to look more closely at what it means to trust someone.
I do trust the devs here regarding the integrity of their own software, because their track record gives me evidence that they're trustworthy in that regard. I've flashed ROMs from here many times.
But I don't trust the devs--or anyone in the world--in the sense of automatically believing what they say about everything. I'm sure they wouldn't expect me to.
So if a dev makes an offhand remark that someone else's software (that they have no way of examining) is safe, then of course I'm not going to just take their word for it. And if they make an equally offhand remark that the software is malicious--but fail to mention why they think so--then I'm not going to automatically believe that, either.
Click to expand...
Click to collapse
I agree man. Thanks for your input, I'm just a little mad. I did pay 399.00 for this and now, I just want it back to Stock. Thanks again, looking for a way.

ukic said:
Why don't you reroot using De La Vega by DG? Although his method will wipe your phone back to stock but at least you know it works and it's safe.
Click to expand...
Click to collapse
Yup. If the phone is infected, wiping it clean is what you want to do anyway.
---------- Post added at 12:38 PM ---------- Previous post was at 12:33 PM ----------
LuckyColdJohnson said:
I agree man. Thanks for your input, I'm just a little mad. I did pay 399.00 for this and now, I just want it back to Stock. Thanks again, looking for a way.
Click to expand...
Click to collapse
I think your course of action depends on how much you have at risk. Do you have sensitive/valuable passwords, account numbers, etc. on your phone or your PC?
If you don't, then you might want to just ignore the risk until and unless someone establishes that Kingo is really malware.
But if you do have sensitive information at risk, your decision is trickier. The only really secure course of action would be to wipe both your phone and your PC, and to reset all your potentially-exposed passwords and financial accounts. But that's a lot of work to go to for a threat that might not even exist. So it really depends on what you have at stake.
In any case, I wish you the best of luck!

If all it does is send info to their servers I ponder if I could just start it under a virtual machine with no internet connection and root.
is the internet connection required?
I would much rather flash two second than a 2 gig file it just sounds alot riskier
Sent from my XT907 using xda app-developers app

mrkhigh said:
If all it does is send info to their servers I ponder if I could just start it under a virtual machine with no internet connection and root.
is the internet connection required?
I would much rather flash two second than a 2 gig file it just sounds alot riskier
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
These are just rumors and a Moderator let us know it wasn't safe so,,,,,,I just want to go back. Cant right now. Cant find the At&T Firmware,,I dont think its available yet.
For all we know, Vroot and Kingo could be okay. IDK

Grrrr so we shouldnt use Kingo unroot method...Im a feard...anyone know what to do now
Sent from my SAMSUNG-SM-N900A using xda app-developers app

mrkhigh said:
If all it does is send info to their servers I ponder if I could just start it under a virtual machine with no internet connection and root.
is the internet connection required?
Click to expand...
Click to collapse
I was thinking this as well but if the application leaves a back door open on the device itself then unless you plan on having your phone in Airplane mode 24/7 it would eventually send its payload over the wire.
I think the PC portion is controllable, its the mobile portion that has a lot of people on edge.
I found this website:
www[dot]majorgeeks.com/files/details/kingo_android_root[dot]html
Which seems to have links back into XDA about who made the claim and what not.
I see it like this, until someone can prove without a doubt that it is opening holes in devices and leaking information, its just another "he-said-she-said" argument.

exaltedgod said:
I was thinking this as well but if the application leaves a back door open on the device itself then unless you plan on having your phone in Airplane mode 24/7 it would eventually send its payload over the wire.
I think the PC portion is controllable, its the mobile portion that has a lot of people on edge.
I found this website:
www[dot]majorgeeks.com/files/details/kingo_android_root[dot]html
Which seems to have links back into XDA about who made the claim and what not.
I see it like this, until someone can prove without a doubt that it is opening holes in devices and leaking information, its just another "he-said-she-said" argument.
Click to expand...
Click to collapse
Or someone is mad because they didn't come up with a root solution like this first, LOL just saying.
I tried the Vroot first, and it had a superuser app (from playstore) but its all in Chinese letters.
So I uninstalled that super user app and used Kingo to unroot (Which works perfectly)
Then I rebooted and rooted using Kingo. (Worked perfectly)
It put the superSU on there (In English) and has been awesome
Now Im going back to stock and never rooting again in my life because it pisses me off I can't trust ...Never mind
I will be using Vega method soon as I get home and Im done. This sucks. Battery life will also suck. Aw well. At least my info will be protected
I guess. Kingo,,,I wish they wouldn't of said that about you. Now I want you gone.

I've contacted Kingo on their website and asked them to comment, hopefully they will respond to the possibility of their app being permanently declared malware on the largest Android forum on the net. We'll see what they have to say about it, if anything.

Response from Kingo.
http://forum.xda-developers.com/showthread.php?t=2515879
Sent from my SAMSUNG-SM-N900A using xda app-developers app

Im back on stock and honestly, the phone fly's better.
I also have the watch so I'm going to wait for a new root method on new updated firmware.
This phone feels better and I got a better AnTUTU score without root.

LuckyColdJohnson said:
I agree man. Thanks for your input, I'm just a little mad. I did pay 399.00 for this and now, I just want it back to Stock. Thanks again, looking for a way.
Click to expand...
Click to collapse
Root De La Vega works fine. Yes it does take a little more work and you have to wipe data but I've rooted/unrooted/rooted again and I've had no issues using DesignGear's method. DesignGear's is a great Dev...I don't think him telling people to use Kingo should change that opinion. Kingo seemed really, really weird to me from the beginning...but it does root the phone!

Android with red triangle and!

I'm a noob and rooted my nexus 6 using NRT, While attempting to upgrade to 5.1 using adb sideload method, when I opened the zip it gave me the android with red triangle. ..phone won't do anything except show the aforementioned icon. ..have access to computer Please help!!!
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app

StakMak99 said:
I'm a noob and rooted my nexus 6 using NRT, While attempting to upgrade to 5.1 using adb sideload method, when I opened the zip it gave me the android with red triangle. ..phone won't do anything except show the aforementioned icon. ..have access to computer Please help!!!
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app
Click to expand...
Click to collapse
Hold power and push volume up, once. You will enter recovery.

Evolution_Freak, THANK YOU, I was afraid of bricking it, people like you are why I go straight to XDA when I'm in those positions and ask for help, NO MATTER HOW STUPID the? is. Once again, Thank you!

while it is nice that people would respond to your questions, it is always better to know what you're getting into before doing something like this. this is also why I highly suggest newcomers to learn adb and not use toolkits even though it's a little daunting at first.

StakMak99 said:
Evolution_Freak, THANK YOU, I was afraid of bricking it, people like you are why I go straight to XDA when I'm in those positions and ask for help, NO MATTER HOW STUPID the? is. Once again, Thank you!
Click to expand...
Click to collapse
Absolutely no problem at all. Remember, some of us here, still genuinely care and want to help. That being said however, please take the time to click the bottom link in my signature and read a great post written by @El Daddy explaining the dangers of toolkits and one click root methods. Not that it pertains directly to your situation but nonetheless, it will enlighten. Also, always, always, ALWAYS read as much as you can about anything you're thinking about doing with any device before actually doing it. Knowledge truly is power. Thank you for your kind words.

Evolution_Freak said:
Absolutely no problem at all. Remember, some of us here, still genuinely care and want to help. That being said however, please take the time to click the bottom link in my signature and read a great post written by @El Daddy explaining the dangers of toolkits and one click root methods. Not that it pertains directly to your situation but nonetheless, it will enlighten. Also, always, always, ALWAYS read as much as you can about anything you're thinking about doing with any device before actually doing it. Knowledge truly is power. Thank you for your kind words.
Click to expand...
Click to collapse
Totally agree here. Kit's are great for streamlining, IMO ONCE you know how to do it yourself, lastly, if you want to know how to do it, pop in here, and search first, most likely there is a thread guide already written.
In that thread, read the whole thing, to see if people doing what you will attempt to do have had issues, and why, and how it was resolved, which can go a long way, in terms of you learning, and preventing you from duplicating earlier made mistakes.
Lastly, with the exception of relocking your bootloader then trying something (dont re-lock it): if you can boot to recovery ok, then whatever you may do to it in general can be fixed.