Database Develop

Temporary nand unlock (until you reboot phone)

To make all the crybabies happy heres a disclaimer:
Doing this will not mess up your phone. Doing things after this could mess up your phone. Make nandroid backups before making changes to your phone. If you are inexperienced, don't do anything else besides editing/deleting system files on your phone. Flashing other recoveries and other such things could be risky, but removing files from system should have no adverse effects other then maybe causing a bootloop which could be fixed my restoring your system folder. I don't know why people got upset about this, but if you have any brain at all you could of figured this out yourself.
Click to expand...
Click to collapse
You can unlock your nand temporarily and its easy to do.
All you need is the unrevoked tool.
First understand what it is doing. It unlocks your nand to write your recovery image. Normally we cant do this. So look they made this tool to hide what its actually doing, but if you think about it you realize hey if I unplug my USB cable before it flashes recovery and reboots to recovery, I will still have an unlocked nand.
So simple steps.
1. Plug in phone to your PC
2. Run unrevoked tool
3. Let it reboot to bootloader
4. When in bootloader your screen will flash back to the white HTC Incredible screen, at this point unplug your USB and close unrevoked tool(make sure you do it before your phone completely boots and while the unrevoked program still says Waiting for reboot.)
5. Once you get past the bootanimation your phone is unlocked so you can write to /system/
To test, run the app Ad free and update the hosts file, it should say it was successful. If your phone is rebooted it is no longer unlocked.

How many times have you used this trick?
Lets say 20. Well what if on the 21st try, your phone was bricked?
I'm not saying that'll happen, but clearly you didn't write the program, so you have no idea.
I wouldn't suggest anyone try this until unrevoked release a fully tested NAND unlock. There are very few reasons to have NAND unlocked at this time.

I would do this, bit i trist pmf on this one.
Sent from my Incredible using XDA App

pardonmyfreedom said:
How many times have you used this trick?
Lets say 20. Well what if on the 21st try, your phone was bricked?
I'm not saying that'll happen, but clearly you didn't write the program, so you have no idea.
I wouldn't suggest anyone try this until unrevoked release a fully tested NAND unlock. There are very few reasons to have NAND unlocked at this time.
Click to expand...
Click to collapse
There's really nothing to worry about, once your phone is rebooted after hboot and your phone is booting, the program isnt interacting with the phone notice it says waiting for reboot, so really there isnt anything to worry about.
I have done this many times. This is supposed to be an open development community and hiding stuff or making up BS about bricking phones to scare people from trying stuff is really dumb. You root your phone, you are already taking risks doing it in the first place.

TNS201 said:
There's really nothing to worry about the program once your phone is rebooted after hboot, the program isnt interacting with the phone notice it says waiting for reboot, so really there isnt anything to worry about.
I have done this many times.
Click to expand...
Click to collapse
I have to say, it does make sense, but i dont feel like having an expensive brick, so i will wait until proven that i wont brick my phone. I do not like knocking devs and their ideas, so i will try this when i get a chance
Sent from my Incredible using XDA App

I'll give it a shot if another member confirms it working

jdkoreclipse said:
I have to say, it does make sense, but i dont feel like having an expensive brick, so i will wait until proven that i wont brick my phone
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Most people have already ran unrevoked several times to update the their phone's recovery.
SO HOW THE HELL is this any different. Get it through your head and realize that all you are doing is unplugging your phone before it is even going to flash recovery again. The recovery isnt flashed until you boot back into the OS. So pulling the USB before this when the program still says Waiting for Reboot will cause no issue.
What you do to your phone afterwards might cause issues, but people should make nandroid backups before they ever do anything anyways.

TNS201 said:
Most people have already ran unrevoked several times to update the their phone's recovery.
SO HOW THE HELL is this any different. Get it through your head and realize that all you are doing is unplugging your phone before it is even going to flash recovery again. The recovery isnt flashed until you boot back into the OS. So pulling the USB before this when the program still says Waiting for Reboot will cause no issue.
What you do to your phone afterwards might cause issues, but people should make nandroid backups before they ever do anything anyways.
Click to expand...
Click to collapse
I like this idea, and i want to try it, but i dont want to be first. I domt like knocking devs and their ideas, but i dont want to be tje community ginuea pig. I hope ot works, and it makes lots of sense but most of us dont know EXACTLY what unrevoked3 does. I can honestly say, i know it unlocks nand temp, bit i cant say what hardware of software parts it targets. For all i knoe, it could short circuit my phone because the process didnt initualize correctly. No offense to you at all. I think this is a GREAT find, and is very good for the community.
Sent from my Incredible using XDA App

That makes sense(pardon the pun!), TNS201.

jdkoreclipse said:
I like this idea, and i want to try it, but i dont want to be first. I domt like knocking devs and their ideas, but i dont want to be tje community ginuea pig. I hope ot works, and it makes lots of sense but most of us dont know EXACTLY what unrevoked3 does. I can honestly say, i know it unlocks nand temp, bit i cant say what hardware of software parts it targets. For all i knoe, it could short circuit my phone because the process didnt initualize correctly. No offense to you at all. I think this is a GREAT find, and is very good for the community.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Well a few weeks back someone posted some file with a list of commands that temporary unlocks the nand and basically this is what unrevoked is doing along with flashing a new recovery and rooting the phone. Basically its a made program so it can hide what its doing so you the person doing it, doesn't know what their program is doing and also to make it easier for people that are inexperienced with rooting and doing other tasks such as using adb. It basically simplifies the process for the enduser to not have to fuss with adb and any other program or entering commands, etc.

TNS201 said:
There's really nothing to worry about, once your phone is rebooted after hboot and your phone is booting, the program isnt interacting with the phone notice it says waiting for reboot, so really there isnt anything to worry about.
I have done this many times. This is supposed to be an open development community and hiding stuff or making up BS about bricking phones to scare people from trying stuff is really dumb. You root your phone, you are already taking risks doing it in the first place.
Click to expand...
Click to collapse
Where would we be without Unrevoked? They don't hide stuff, they protect stuff. They're protecting exploits from being closed by HTC and phones from being bricked. What it is, is that people are greedy fux and use the phrase OPEN SOURCE/DEVELOPMENT as an excuse to post their (unrevoked's) long hard work all over the forums cause "hey now my adblock works". Its really pathetic! Unrevoked thinks of the big picture, like people being able to root their phones in the future while these other people posting their work are just actually HURTING the community! Now you're gonna post some schlep way to get NAND unlock for one boot, using their tool and then talk **** about their methods. THERE WOULD BE NO DEVELOPMENT SECTION UNDER HTC DROID INCREDIBLE IF IT WASN'T FOR UNREVOKED! Here on XDA or any other site. It would be sad if Unrevoked decided not to release the REAL FULL NAND UNLOCK/UNLOCKED BOOTLOADER cause people keep posting stolen work or schlep methods of using their tools for the non-intended purposes!

Has anyone tried this yet?
Sent from my Incredible using XDA App

SoCalMiles said:
Where would we be without Unrevoked? They don't hide stuff, they protect stuff. They're protecting exploits from being closed by HTC and phones from being bricked. What it is, is that people are greedy fux and use the phrase OPEN SOURCE/DEVELOPMENT as an excuse to post their (unrevoked's) long hard work all over the forums cause "hey now my adblock works". Its really pathetic! Unrevoked thinks of the big picture, like people being able to root their phones in the future while these other people posting their work are just actually HURTING the community! Now you're gonna post some schlep way to get NAND unlock for one boot, using their tool and then talk **** about their methods. THERE WOULD BE NO DEVELOPMENT SECTION UNDER HTC DROID INCREDIBLE IF IT WASN'T FOR UNREVOKED! Here on XDA or any other site. It would be sad if Unrevoked decided not to release the REAL FULL NAND UNLOCK/UNLOCKED BOOTLOADER cause people keep posting stolen work or schlep methods of using their tools for the non-intended purposes!
Click to expand...
Click to collapse
Umm,
If a person such as myself can figure this out.
If a person like you and myself and others all have access to unrevoked program.
This means HTC has access to these programs as well.
HTC hires people who have college degrees and know how to program and know much more about the phones then us.
I'm sure they already have disassembled their program and know what they are doing and knew what it was doing before they did so.
I want to try other things like Metamorph and make themes.

pardonmyfreedom said:
How many times have you used this trick?
Lets say 20. Well what if on the 21st try, your phone was bricked?
I'm not saying that'll happen, but clearly you didn't write the program, so you have no idea.
I wouldn't suggest anyone try this until unrevoked release a fully tested NAND unlock. There are very few reasons to have NAND unlocked at this time.
Click to expand...
Click to collapse
I will assume that they could have given us NAND unlock already. But they haven't. They must have a good reason for holding out. I for one would like to be able to use my Root Explorer instead of getting out my laptop and using that frigging command line interface. I'm not a Linux person. I was raised on the Windows GUI. My previous 2 phones ran Windows Mobile. This is my first Android. I don't like the command line interface. It may be handy for techies and developers, but not for me... So gimmie NAND unlock! I'll take my chances.

Lexus One said:
I will assume that they could have given us NAND unlock already. But they haven't. They must have a good reason for holding out. I for one would like to be able to use my Root Explorer instead of getting out my laptop and using that frigging command line interface. I'm not a Linux person. I was raised on the Windows GUI. My previous 2 phones ran Windows Mobile. This is my first Android. I don't like the command line interface. It may be handy for techies and developers, but not for me... So gimmie NAND unlock! I'll take my chances.
Click to expand...
Click to collapse
So lexus one, ur gonna try it? If so please report back. I would love to try it, but im a little uneasy about it.
And as for the op, this is a schlep method. There is a really good reason unrevoked didnt release the unlocked bootloader. I still lile your idea, but imma go with pmf and SOCALMiles on this one until ot is proven that it works
Sent from my Incredible using XDA App

SoCalMiles said:
Where would we be without Unrevoked? They don't hide stuff, they protect stuff. They're protecting exploits from being closed by HTC and phones from being bricked. What it is, is that people are greedy fux and use the phrase OPEN SOURCE/DEVELOPMENT as an excuse to post their (unrevoked's) long hard work all over the forums cause "hey now my adblock works". Its really pathetic! Unrevoked thinks of the big picture, like people being able to root their phones in the future while these other people posting their work are just actually HURTING the community! Now you're gonna post some schlep way to get NAND unlock for one boot, using their tool and then talk **** about their methods. THERE WOULD BE NO DEVELOPMENT SECTION UNDER HTC DROID INCREDIBLE IF IT WASN'T FOR UNREVOKED! Here on XDA or any other site. It would be sad if Unrevoked decided not to release the REAL FULL NAND UNLOCK/UNLOCKED BOOTLOADER cause people keep posting stolen work or schlep methods of using their tools for the non-intended purposes!
Click to expand...
Click to collapse
As much as I want the nand unlock I have to agree this thread should be closed. Unrevoked has done to much for us.

jdkoreclipse said:
So lexus one, ur gonna try it? If so please report back. I would love to try it, but im a little uneasy about it.
And as for the op, this is a schlep method. There is a really good reason unrevoked didnt release the unlocked bootloader. I still lile your idea, but imma go with pmf and SOCALMiles on this one until ot is proven that it works
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
I'm not gonna try it! You try it! Hey, let's get Mikey!

cheifkeiff said:
As much as I want the nand unlock I have to agree this thread should be closed. Unrevoked has done to much for us.
Click to expand...
Click to collapse
+1. I dont like to knock our valuable devs, but this is a schlep method that is a mockery of sorts of unrevoked. This was a good find, just not the rght thing to do to support unrevoked.
Ps. Sorry if im clogging the thread, i jabe a lot to say on the subject.
Sent from my Incredible using XDA App

i tried it, installed adfree and it worked.

jdkoreclipse said:
+1. I dont like to knock our valuable devs, but this is a schlep method that is a mockery of sorts of unrevoked. This was a good find, just not the rght thing to do to support unrevoked.
Ps. Sorry if im clogging the thread, i jabe a lot to say on the subject.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
+2 UnRevoked your doing a hell of a job, 90% of us understand why the nand unlock has not been released, I want nand but i'm not willing to try what the op has suggested. Perhaps if I were building themes I might use this method for a faster testing procedure. Yet I dont belive it should have been posted here seems alot of new poeple lurking might unplug at the incorrect moment and create issues that would spur a whole bunch of "help me!!" threads.
What UnRevoked is doing is no different than me or anyone else running company server patches in a sandbox for a few weeks before I pushed it to all the servers. Test test test test THEN release!
No doubt HTC has already seen and disected their code. Do you think your the first to figure out how UnRevoked managed to flash the custom recovery? Why has no one else posted this? hmm..
Dont kill me with flames I'm just sayin.
Just my .02 cents

Should I Rom

Should i Rom
Sent from my SAMSUNG-SGH-I897 using XDA App

Um...that depends. Do you want to?
If you're comfortable with flashing then I would, if not then probably no.
Sent from 234 Elm Street

should you rom?
if you have to ask....
NO.
you should read.
then decide for yourself.
and know what you are doing before you are the 4th person in 24 hours to PERMANENTLY brick thier phone.
rom? no.... not yet at least...
read yes.

TRusselo said:
should you rom?
if you have to ask....
NO.
you should read.
then decide for yourself.
and know what you are doing before you are the 4th person in 24 hours to PERMANENTLY brick thier phone.
rom? no.... not yet at least...
read yes.
Click to expand...
Click to collapse
I absolutely agree with this answer. If you are thinking of flashing a ROM, what is the reason you are thinking about doing it? If you decide to go for it, then absolutely make sure you know completely what you are doing by reading as much as you can. Research first will save grief and frustration later. Let's just say I learned that the hard way. The only time I had any issues was when I didn't follow this advice.
Good luck with whichever way you decide to go.

TRusselo said:
should you rom?
if you have to ask....
NO.
you should read.
then decide for yourself.
and know what you are doing before you are the 4th person in 24 hours to PERMANENTLY brick thier phone.
rom? no.... not yet at least...
read yes.
Click to expand...
Click to collapse
^^^THIS^^^

Damn 4 ppl in a day...wow
Sent from my GT-I9000 using XDA Premium App

Just take time to read and understand the while process before you start flashing. DO NOT try and figure out stuff as you go, as that is how stupid mistakes are made and you mess up your phone.
Check to make sure the 3 button combo for recovery and download modes are working, and just know and follow the steps laid out in the many tutorials you can find here on xda. If you can follow directions at all, your phone will soon be doing sweet ****, and you will probably become addicted to flashing and trying new things.
I am not all that knowledgeable about how stuff works, so I never try and modify stuff that hasn't been tried and tested by somebody else, and I've never run into any serious problems. I've flashed too many roms to remember, and never screwed up my phone beyond a simple fix, all thanks to a little careful reading.
Once you flash your first rom successfully, the process is simple and fun. Just make sure and read the thread for each rom you want to try carefully so that you know of all possible issues, and you shouldn't have any problems.
Sent from my 2.3.3 Cappy running Mosaic I with Talon 1.5 using XDA Premium App

Make sure you know all the worst things that can happen. Not to scare you from doing it. On the contrary, once you know what's the worst, and you know how to fix it or prevent it, you're good to go.
Like everyone here says (because it's true) READ everything. Read the WHOLE OPs and multiple pages of everything. If someone had problem with something, they probably already mentioned it somewhere in the 23482 pages (it sucks, but you rather spend some time reading than have a dead phone).
At first everything will be uncertain (first time watching the bar go across the download mode screen when flashing from Odin) and sometimes you'll feel like you've bricked your phone. Just read the threads about ACTUAL bricked phones to know what NOT to do.
Actually, what I suggest is to find a rom that you like, but more importantly has REALLY thorough documentation about how to install. Once you do it a couple of times it'll be smooth sailing from there, and you'll be able to work with any kind of rom easily (terminology and stuff becomes more familiar too).
glhf

I got an rma phone and i am not sure if i should rom

mwiz123 said:
I got an rma phone and i am not sure if i should rom
Click to expand...
Click to collapse
So you ask the same question in a different format. Tell us that you at least read some of the replies above. Right?

Talk to people that have rommed (if that's a word. If not, then Copyright bdgiese90 2011). If they know your phone well and can help if you have questions beyond what is answered in OP's, then you can make a choice from that too. But seriously. Do your reading first. Installing a ROM isn't something other people decide for you.
And one more thing. Don't ask the same question again with different wording. Read what all of these intelligent people are posting to you. Believe it or not, they ARE helpful
Sent from my robot vacuum smartphone using black magic and goat blood

You sound ambivalent and unsure. Bad combination. Step away from the phone before you hurt it.

IM the biggest noob

Hey gsuys i was wondering if anyone knows a video on youtube that shows exactly installing a Tom? Also can someone please tell me what a bootloader and a kernel is? I've been researching but i can't find anything since im a noob..
Sent from my SAMSUNG-SGH-I897 using XDA Premium App

I think you mean a ROM. Bootloaders are files which load other data and programs which are then executed from RAM. Often, multiple-stage boot loaders are used, during which several programs of increasing complexity sequentially load one after the other in a process of chain loading.
As far as Android is concerned, the kernel file is related to threading and memory management. It's sort of the map of the infrastructure that helps the other programs when and how to act and manage the resources.
For your own sake, take a week or two to do some reading and get familiar with the terminology, software, and processes involved with flashing a ROM. I can promise you that without some basic slef-taught information, you will end up bricking the hardware 75% of the time. Get to understand how the phone works and why other people have problems, and how they solved them. Don't make mistakes that others have made when the information on how to avoid it is here in the forums.
Many people are too impatient or uninterested in how these phones work to do the due diligence. You can find ROM flashing guides, but without some basic knowledge, if something goes wrong you will find yourself in panic mode. Just look through these forums. Half of them start with 'HELP!' or 'Phone Bricked'. Don't be one of them. Arm yourself with some information and you will soon be solving your own problems, and possibly helping others.
Good luck and have fun. The Captivate is one of the most moddable smartphones out there, you have already made a good decision. Don't stop now!

see that wasnt hard to ask without a subtle insult. mobiletechvideos has plenty of install tuts for 2.2 and 2.3.3 based roms. stick with 2.2 roms to lessen the chance of a perma brick

Listen to clemmie.
Sent from my SAMSUNG-SGH-I897 using XDA App

CremeFraiche said:
see that wasnt hard to ask without a subtle insult. mobiletechvideos has plenty of install tuts for 2.2 and 2.3.3 based roms. stick with 2.2 roms to lessen the chance of a perma brick
Click to expand...
Click to collapse
+1 on josh @ mobile tech videos. That site was 85% of the research I did on my first flash. The other 15% was asking courteous questions to the great people on this forum.
Agreed on sticking with 2.2 ROM at first, less chance of hard brick and they are very stable.
Sent from my GT-I9000 using XDA App

esteban836 said:
Also can someone please tell me what a bootloader and a kernel is?
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
Check THIS out!

CremeFraiche said:
see that wasnt hard to ask without a subtle insult. mobiletechvideos has plenty of install tuts for 2.2 and 2.3.3 based roms. stick with 2.2 roms to lessen the chance of a perma brick
Click to expand...
Click to collapse
I second, third, and fourth, the Mobiltech videos for the cappy. They should be mandatory for every noob to watch.

axis01 said:
I second, third, and fourth, the Mobiltech videos for the cappy. They should be mandatory for every noob to watch.
Click to expand...
Click to collapse
Whats wrong with reading forums of the rom before hand? Don't get me wrong I've used videos (my very first flash and my first GB rom) but I had done a good reading before hand. I had a decent idea on what I had to do before watching videos. =/

prbassplayer said:
Whats wrong with reading forums of the rom before hand? Don't get me wrong I've used videos (my very first flash and my first GB rom) but I had done a good reading before hand. I had a decent idea on what I had to do before watching videos. =/
Click to expand...
Click to collapse
I don't think theirs anything wrong with reading up in the forums, its just a lot more easier on newcomers to watch the videos so they have something to look at step by step and if they want to they can go back and watch different parts over and over =] well at least that's how I see it lol

MonoControl said:
I don't think theirs anything wrong with reading up in the forums, its just a lot more easier on newcomers to watch the videos so they have something to look at step by step and if they want to they can go back and watch different parts over and over =] well at least that's how I see it lol
Click to expand...
Click to collapse
I understand you but I feel like op hasn't read anything about flashing or the risk of it. Don't know feel like he trying to take shortcuts and is going to end up bricking his phone. Hope I'm wrong though.

MonoControl said:
I don't think theirs anything wrong with reading up in the forums, its just a lot more easier on newcomers to watch the videos so they have something to look at step by step and if they want to they can go back and watch different parts over and over =] well at least that's how I see it lol
Click to expand...
Click to collapse
+1
When I flashed my first ROM, I had read quite a bit on here, but I watched one of Josh's videos and paused at about every step! Bottom line here is, everyone is different and some people are "visual" learners. Having said that, I agree whole heartedly with the "read twice flash once" (then follow a vid if ya have to) mentality.

Of course, the videos are very good and simplify things immensely. However, what the videos do not show you often times is how to avoid mistakes and errors and how to fix them if you make them. This is why it is always a good idea to read through the thread of the kernel or ROM or what have you to see what has gone wrong for others. It can seem daunting to try to read through a 20+ page thread, which may take an hour, but that hour might save you 4 or more hours while trying to recover from a brick or failed flash. Add to that some peace of mind because perhaps you've seen or read about the same issue and can do some problem solving.
Both are helpful, but reading threads is essential.

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.