Database Develop

Help Me Please

I feel I've made a terrible (and stupid) mistake. I decided to unroot my phone from cyanogen roms. I read a how to guide that I guess was outdated because now I have android 1.0 firmware. The guidw was [how to] unroot by tubaking182 (absolutely zero offense to him, not his fault, I'm stupid, etc etc.) So I now have stock version 1.0. There's no check for system updates under about phone in settings so I can't do that. There are file manager apps that I could use to rename the necessary updates into update.zip, but there's no apps available like download crutch so I can download them. I also can't enter recovery. It gives me a triangle with an exclamation inside next to a image of a phone and that's it and I have no idea how to install an update without recovery mode. As I'm sure you've noticed by now, I'm the epitome of newb and feel free to laugh at my failure. I just really need someone to help me and would be eternally grateful. In all likelihood, I'll need step by step instructions on what to do. I know this is a lot to ask and I've really done nothing to earn this help... I really just need assistance. Thank you to anyone who helps me in advance

Not to be an asshole and say "Shoulda Coulda Woulda" but you really should have done your research before embarking on bricking your phone.

ItsAndroidsWorld had many videos on You Tube. Look for ones on how to root, then how to install the death spl, then look for the ones with Super D or FastTest .. as it seems as though they are probably the best roms for everyday use at this point.
I've found that using these videos via You Tube is the easiest way to go.
Good Luck.
^^^ ABOVE POST stolen from another similar thread.

psyko-m1 said:
Not to be an asshole and say "Shoulda Coulda Woulda" but you really should have done your research before embarking on bricking your phone.
Click to expand...
Click to collapse
he didn't brick his phone, don't scare him
To OP: The same happened to me when I was a n00b at this ****.
Dude, google is your friend.
Calm down.

tsk tsk tsk.....Im gonig to say this....WRONG SECTION
but I will be nice as well. just find the updates on google from 1.0 to 1.5 and oh yeah to get back into recovery from the triangle withthe !...alt L...but if you somehow brick ya phone youe fault not mine next time do ya research before you mess with ya phone

Technically speaking he is in a DEFCON 2 "Brick" situation.
Sorry.

psyko-m1 said:
Technically speaking he is in a DEFCON 2 "Brick" situation.
Sorry.
Click to expand...
Click to collapse
Well he's in the wet cement

SeEsAw12 said:
Well he's in the wet cement
Click to expand...
Click to collapse
Or...
You are late for work and have a flat...

click on this http://theunlockr.com/category/howto/android_how_tos/htc-mytouch-3g-magic/:cool:

remove the cool http://theunlockr.com/category/howto/android_how_tos/htc-mytouch-3g-magic/

this website should help you get back on track and you just need to download the nbh file to get it back to cupcake

BUT 0MGAWWZZZ N00BZORZ DO3S 1.0 HAVE A DA SENSE RAOM???
in all seriousness, there's nothing actually wrong with your phone. You completely unrooted it. By following the aforementioned instructions, it'll be easy to reroot and update. What I DO find weird is why you're not getting 1.5 OTA...

although i hate when people post in the wrong section - im in a good mood this morning
http://zenthought.org/content/project/flashrec
not sure if it works in 1.0 - it should as it uses a rather old bug to do so

Easy as pie...just follow the guide in my sig.
=)

To those who say I bricked it, I know that's not the case it still works so I obviously didn't brick it... not that fail thankfully.
To thenameismax, AHA! I did not know about alt+l retrieving text so thank you thank you thank you. I just need to get the necessary updates and copy them to sd card root, rename update.zip/install one at a time... I think lol
Thanks again to all who helped and sorry about the wrong section. When I was rooting, it was in development. I assumed that unrooting would be too and therefore problems with that... further fail.

afiellerddr said:
To those who say I bricked it, I know that's not the case it still works so I obviously didn't brick it... not that fail thankfully.
To thenameismax, AHA! I did not know about alt+l retrieving text so thank you thank you thank you. I just need to get the necessary updates and copy them to sd card root, rename update.zip/install one at a time... I think lol
Thanks again to all who helped and sorry about the wrong section. When I was rooting, it was in development. I assumed that unrooting would be too and therefore problems with that... further fail.
Click to expand...
Click to collapse
yeah man no problem. good luck.

Don't do anything. In a day or two you get an OTA update.
You can force the update like people have mentioned, but as long as you can hold off for a day or two you dont need to.
BTW, at some point you will see the E or 3G icon downloading like crazy and you dont know why. It is downloading the update. Stay away from task killers and in my experience it is good to be around wifi.
Just relax.

Sent Move Request

News flash***rom manager***

It does not like our phones. Has great options but.......it sucks. Everytime I flash it on my phone my recovery goes bad in a cpl days. Never had this problem with RA. Do a search rom manager pops up all over the place with bad recoveries. Stop using it ppl. Im sure ill get flamed for this but oh well. Kinda tired of reading of noobs that fall victim to a .apk that seems very easy to use until it craps out and then your stuck at the airport with a bad recovery and ADB no where in sight. Or even if u had ADB you still have no clue how to fix it!!!!!!!!!!!
http://forum.xda-developers.com/showthread.php?t=742007
http://forum.xda-developers.com/showthread.php?t=762325
http://forum.xda-developers.com/showthread.php?p=7443928&highlight=revovery#post7443928

I couldn't agree more.

never used it thank goodness.........

Never happened to me
EDIT: Sorry for my rudeness, anyways, people should know that it's not the greatest idea to use rom manager with cm5/cm6. It has already been established that it may be a bad idea to use the program with the following roms. Sorry I get really cranky in the mornings, not the best idea to come onto the forum with some old news :|

protomanez said:
Never happened to me, you're obviously too stupid to use it.
Click to expand...
Click to collapse
I have never used it and I agree with him just from all the posts I have seen related too it messing up people's recovery images. Does that make me stupid?

I've used it for a few weeks now with no problems on my MyTouch on 1.6, 2.1, and 2.2 ROMs. Not saying others aren't having legitimate issues, but people in general are much more likely to post negative reports than positive ones.

protomanez said:
Never happened to me, you're obviously too stupid to use it.
Click to expand...
Click to collapse
hahahahaha good one. Not to stupid to use it. the ui is very simple and easy to use. Flash clockwork or flash alternate. What im to stupid to do is figure out how to fix it after it kills recovery. but thank you for your input, I'm sure it will help someone out.

protomanez said:
Never happened to me, you're obviously too stupid to use it.
Click to expand...
Click to collapse
Please lead us retartds through your install procedure, current rom, set-up so we can be as learndededed as you. I have had cm5&6 with ra installed upon initial set up. No swap/ noext1234, stock mt3g spl 2.22.23.02 radio. Nothing special. I even did it with the donut mytouch rom w/root.I only use basic apps, nothing that would interfere with recovery. to me it seems that when u flash a cpl different roms a day is when it hangs up. I can usually get the phone to boot back up, which gives me a chance to get back into rom manager and flash ra recovery back to the phone. the last cpl times I had to wipe cache before it would actually flash RA recovery. so basically if u can get the phone to boot past the splash screen go to rom manager and flash the **** out of ra recovery until it works. First we found out that clockwork didnt like flashing zip's and backups on low batteries 30% and lower. then the always fun recoverly log issue(cant recall the exact error right now) and of course the cant get to recovery issue. I know it's not a widesporead problem but it is a problem that renders phones useless until u can find someone nice enough to help u and not treat u like a retard. Not everyone knows as much about phones as you guys do....congratulations you know all there is about phones. go learn some ****ing human decency, if u have nothing helpful to say then shut up.

have been using it without Rom manager and highly disagree with the poster.doing it 'wrong' or without knowing 'how to' can certainly cause problems but that should not be described as the problem of the product. lot of people can not use nuclear power correctly (look at the USA) and now we call describe nuclear power as menace which is lame :/
Sent from my T-Mobile G1 using XDA App

arefin said:
have been using it without Rom manager and highly disagree with the poster.doing it 'wrong' or without knowing 'how to' can certainly cause problems but that should not be described as the problem of the product. lot of people can not use nuclear power correctly (look at the USA) and now we call describe nuclear power as menace which is lame :/
Sent from my T-Mobile G1 using XDA App
Click to expand...
Click to collapse
hmmmmm. Maybe since its flashing clockwork from inside rom manager is what might be killing it for some of us. tonight I will try just flashing clockwork outside of rom manager and see how that goes. i like clockwork's set up and it is easy to use, just kinda freaks me out when my recovery goes bad.

arefin said:
have been using it without Rom manager and highly disagree with the poster.doing it 'wrong' or without knowing 'how to' can certainly cause problems but that should not be described as the problem of the product. lot of people can not use nuclear power correctly (look at the USA) and now we call describe nuclear power as menace which is lame :/
Sent from my T-Mobile G1 using XDA App
Click to expand...
Click to collapse
but at the same time thats why it is a part of rom manager. one click recovery flasher. to make it "easy". i highly doubt you can go into rom manager and incorrectly flash clockwork recovery. its a one click thing

it's also spoken out at many threads at xda that flashing the recovery from within the OS causes issues, so trying to install the recovery from PC or even RA1.7 should be a better option.
I'm considering that you already know the commands for that. better luck! remember, clock work will allow you to flash anything without signing - meaning? you can edit any update.zip to your liking and then forget about all the trouble of signing it before flashing. a simple toggle should do the trick while you are in recovery mode happy flashing.
Sent from my T-Mobile G1 using XDA App

It is either a case of your phone, sd card setup/left over files etc..
I use rom manager on every phone I root with no problems since its release. 6 G1's, 3 Fender LE's, 7 Mytouch 1.2 and 4 Evos. Sometimes, it takes couple seconds to show up or go into recovery, but that doesnt mean its gone. Recovery cant just dissapear without something either trying to over write it or it being erased.

crypysmoker said:
It is either a case of your phone, sd card setup/left over files etc..
I use rom manager on every phone I root with no problems since its release. 6 G1's, 3 Fender LE's, 7 Mytouch 1.2 and 4 Evos. Sometimes, it takes couple seconds to show up or go into recovery, but that doesnt mean its gone. Recovery cant just dissapear without something either trying to over write it or it being erased.
Click to expand...
Click to collapse
Im gonna give it one more try. I dont think I have ever.....
flashed clockwork from rom manager
reboot into recovery from rom manager right then (read some where that on some roms when u reboot to recovery using the regular way it might mess up....not sure about this one).
wipe everything (clockwork wipes more that amon ra)
reflash any rom
in my case... above steps then in this order
flash fireats custom mtd part 1.1
super E
Gapps
overclock update
fireats custom mtd part 1.2
anyone see a issue with what I have done so far??
Ok I will post back when clockwork fails again.....and if not f-in sweet

chrisgto4 said:
It does not like our phones. Has great options but.......it sucks. Everytime I flash it on my phone my recovery goes bad in a cpl days. Never had this problem with RA. Do a search rom manager pops up all over the place with bad recoveries. Stop using it ppl. Im sure ill get flamed for this but oh well. Kinda tired of reading of noobs that fall victim to a .apk that seems very easy to use until it craps out and then your stuck at the airport with a bad recovery and ADB no where in sight. Or even if u had ADB you still have no clue how to fix it!!!!!!!!!!!
http://forum.xda-developers.com/showthread.php?t=742007
http://forum.xda-developers.com/showthread.php?t=762325
http://forum.xda-developers.com/showthread.php?p=7443928&highlight=revovery#post7443928
Click to expand...
Click to collapse
chrisgto4 said:
hahahahaha good one. Not to stupid to use it. the ui is very simple and easy to use. Flash clockwork or flash alternate. What im to stupid to do is figure out how to fix it after it kills recovery. but thank you for your input, I'm sure it will help someone out.
Click to expand...
Click to collapse
You found your answer within the first example link that you provided, look at post #3:
http://forum.xda-developers.com/showthread.php?t=742007

rom manager is not for idiots like yourself. rom manager is a great tool for many different phones. sometimes it doesnt flash a recovery correctly maybe it be poor service to download the recovery, or low memory when flashing it. an advanced user (who its made for) can still flash recovery via fastboot, and have all the helpfulness and easy ui of rom manager and easy access to cm nightlies.
dont knock a dev who works on many different phones, and dont rely on noob application reports and bad reviews. anyone who finds rom manager crap is just a poor android user.

tehseano said:
sometimes it doesnt flash a recovery correctly maybe it be poor service to download the recovery, or low memory when flashing it.
dont rely on noob application reports and bad reviews. anyone who finds rom manager crap is just a poor android user.
Click to expand...
Click to collapse
i didn't want to get into this pointless discussion, but you have made a ****ty argument for rom mgr, you have confirmed that it doesn't work properly in certain circumstances, which is a good enough reason to not bother with it.
also, why shouldn't we rely on bad reviews? that's the point of a review, to give some idea about what experience to expect.
(i have never used it myself, amon ra recovery is enough for me.)

I agree it is an 'easy' shortcut that is not the best decision.. Like for example I think it killed my phone. I repaired permissions via rom manager, rebooted as it told me to and now my g1 wont boot past the g1 logo. I could install from a backup but the backup is 1+ month old (my error oops!). I am hoping to find a solution... Really dont wanna wipe everything..

warsng said:
i didn't want to get into this pointless discussion, but you have made a ****ty argument for rom mgr, you have confirmed that it doesn't work properly in certain circumstances, which is a good enough reason to not bother with it.
also, why shouldn't we rely on bad reviews? that's the point of a review, to give some idea about what experience to expect.
(i have never used it myself, amon ra recovery is enough for me.)
Click to expand...
Click to collapse
I made a perfectly good argument. Yes it can "mess up", but thats not at the fault of the app. It's at the fault of the phone. There are things that can go wrong that Koush cannot control. It is for ADVANCED users as a quick helpful UI for recovery-based operations. People that don't know what they're doing, or only half-way do shouldn't be using it. However, too many Android users *think* they are advanced enough, yet 5 minutes after using it, post a "PLEASE HELP, PHONE IS BROKEN", because they DON'T know what they're doing.
I'm not saying that all bad reviews are missguied, but I can assure that 90% of them are from noobs that have no idea what they're doing. They rooted their phone because someone told them it was cool, and they have absolutetly no idea whats in their hands and what they can do with it. Let alone, how to properly work it and fix problems. It's easy as pie to point out noobs from those crowds of users, those 3 links in the OP's post are all perfectly examples. People who came to XDA, signed up, never posted anything, then messed up and came crying to the board asking for help (usually in Android Development because people like them, and the OP too, don't how to to post in the correct section).
So for the last time, if you don't know what you're doing on your phone, don't do it. Just because you have root, and an app says "for root users", doesn't mean its for you, which EVERYONE assumes it is. It's piss-poor users like that, that ruin app reviews and the name of Android everywhere.

tehseano said:
I made a perfectly good argument. Yes it can "mess up", but thats not at the fault of the app. It's at the fault of the phone. There are things that can go wrong that Koush cannot control. It is for ADVANCED users as a quick helpful UI for recovery-based operations. People that don't know what they're doing, or only half-way do shouldn't be using it. However, too many Android users *think* they are advanced enough, yet 5 minutes after using it, post a "PLEASE HELP, PHONE IS BROKEN", because they DON'T know what they're doing.
I'm not saying that all bad reviews are missguied, but I can assure that 90% of them are from noobs that have no idea what they're doing. They rooted their phone because someone told them it was cool, and they have absolutetly no idea whats in their hands and what they can do with it. Let alone, how to properly work it and fix problems. It's easy as pie to point out noobs from those crowds of users, those 3 links in the OP's post are all perfectly examples. People who came to XDA, signed up, never posted anything, then messed up and came crying to the board asking for help (usually in Android Development because people like them, and the OP too, don't how to to post in the correct section).
So for the last time, if you don't know what you're doing on your phone, don't do it. Just because you have root, and an app says "for root users", doesn't mean its for you, which EVERYONE assumes it is. It's piss-poor users like that, that ruin app reviews and the name of Android everywhere.
Click to expand...
Click to collapse
Get a clue , its a program any gimp, including you, can install from the market, it is made in such way ...the fact that it dosent fail to write the recovery in fastboot mode means nothing!
This program shouldnt let the G1 user flesh any rec image. Till that happens it is the DEV's fault. Shouldnt be in the G1 CM's either.

HTC VIVID Super User Problems....

So I am a new person and therefor can not post this in the development thread under the forum where I feel it would belong with the other root related questions.... So i followed the SUPER GUIDE to root my phone (Thank you so much Slapshot and PirateGhost, I was beginning to regret not getting a skyrocket until I found your thread). My super user is running into an issue I can not seem to fix.....
Maybe this is simple or maybe I really messed something up....
Basically none of my apps have root anymore (they did at one point and to my knowledge I change nothing...)
When I go to the Super User app to update my binaries and hopefully get any issues resolved I am greeted by the following error message in the update log: "Failed to find currently installed SU binary. Update cannot continue"
Is there a resolution for this? I have not found anyone even running into the same issue on the Vivid.....
A little nervous.... I didnt have near this many issues rooting my ATRIX and modding the living daylights out of that.

Have you checked with Root Checker Basic to see if you even have Root? If you didn't follow the Super Guide step by step your phone could have relocked after you turned your phone off/on.
If it still fails to update you could try SuperUser Update Fixer.

Yes I have check with root checker.
This may be a dumb question but how do I uninstall Superuser? When I go to the typical application management it does not give me the option. I have done an install again to overwrite the files and nothing changed there.
I followed the instructions step by step (though obviously I messed up somewhere...)
Sent from my HTC PH39100 using XDA App

Kraizk said:
So I am a new person and therefor can not post this in the development thread under the forum where I feel it would belong with the other root related questions.... So i followed the SUPER GUIDE to root my phone (Thank you so much Slapshot and PirateGhost, I was beginning to regret not getting a skyrocket until I found your thread). My super user is running into an issue I can not seem to fix.....
Maybe this is simple or maybe I really messed something up....
Basically none of my apps have root anymore (they did at one point and to my knowledge I change nothing...)
When I go to the Super User app to update my binaries and hopefully get any issues resolved I am greeted by the following error message in the update log: "Failed to find currently installed SU binary. Update cannot continue"
Is there a resolution for this? I have not found anyone even running into the same issue on the Vivid.....
A little nervous.... I didnt have near this many issues rooting my ATRIX and modding the living daylights out of that.
Click to expand...
Click to collapse
Interesting... maybe your root didn't stick. We had a little trouble with that before but pirateghost fixed the CWM ROOT zip. You have a working CWM Recovery, correct?
In the superguide, I have a second option for root in case the first doesn't work. In your case, go ahead and try the second option. The one involving the supertool. That should get you perm root. If that doesn't even work, then we might have to put you back to stock and go at it again.
EDIT: BEFORE TRYING THE SUPERTOOL, try flashing the new CWM ROOT VER2 zip from CWM recovery and see if root sticks.

Slapshot, thank you for checking the General Thread, I really do appreciate that. I have tried both methods multiple times since the root failure seeing as so many people said they had to run the methods multiple times to make them stick (this admittedly may be part of the issue). The most recent one has been the CWM ROOT VER2. Still no dice. Is there a method to remove and re install super user? Or am I reading into the error too literally and instead I just basically do not have root.

Kraizk said:
Slapshot, thank you for checking the General Thread, I really do appreciate that. I have tried both methods multiple times since the root failure seeing as so many people said they had to run the methods multiple times to make them stick (this admittedly may be part of the issue). The most recent one has been the CWM ROOT VER2. Still no dice. Is there a method to remove and re install super user? Or am I reading into the error too literally and instead I just basically do not have root.
Click to expand...
Click to collapse
No problem. At this point I think you may just not have root... but first, go ahead and go into bootloader (power off, then power on while holding power and vol down). Does your device say unlocked?

*Just a clarification*
You have to unroot your phone to get rid of it Idk why I put uninstall/reinstall earlier...still out there from last night I guess.

slapshot30 said:
No problem. At this point I think you may just not have root... but first, go ahead and go into bootloader (power off, then power on while holding power and vol down). Does your device say unlocked?
Click to expand...
Click to collapse
Yes the device still says unlocked. That was one of the first things I checked... Haha....
As I said ive flashed the rooted CWM and it says it went over successfully.
If i use the Zerg exploit it still seems to go over successfully (I realize this has a tenancy to mess with internal storage and only provide a temp root but i do not even get that temp root).
How would I unroot my device? Do you mean flash to stock and relock my boot loader?
As I said I have flashed several devices in the past (Atrix, eee pad transformer, HTC Inspire, HTC DINC, SAMSUNG GALAXY S T-Mobile) but I am not completely up to date on all of the technical terms...

Kraizk said:
Yes the device still says unlocked. That was one of the first things I checked... Haha....
As I said ive flashed the rooted CWM and it says it went over successfully.
If i use the Zerg exploit it still seems to go over successfully (I realize this has a tenancy to mess with internal storage and only provide a temp root but i do not even get that temp root).
How would I unroot my device? Do you mean flash to stock and relock my boot loader?
As I said I have flashed several devices in the past (Atrix, eee pad transformer, HTC Inspire, HTC DINC, SAMSUNG GALAXY S T-Mobile) but I am not completely up to date on all of the technical terms...
Click to expand...
Click to collapse
Yes, I mean relock the bootloader and back to stock rom, then try again. Do you know how to get back to stock?

slapshot30 said:
Yes, I mean relock the bootloader and back to stock rom, then try again. Do you know how to get back to stock?
Click to expand...
Click to collapse
actually that one I do not know how to do... I realize this is probably somewhat annoying because I am sure you have said how to do it before.... Some help would be greatly appreciated

Kraizk said:
actually that one I do not know how to do... I realize this is probably somewhat annoying because I am sure you have said how to do it before.... Some help would be greatly appreciated
Click to expand...
Click to collapse
I haven't told anyone how to do it surprisingly, and I'm more than happy to help . I was honestly thinking about adding reverting back to stock to the superguide, and I think I just may do that. Here is the link. Pirateghost is the man.
http://forum.xda-developers.com/showpost.php?p=20821226&postcount=4

Thank you for this and all of your help, people like you and ghostpirate are why i still feel like I can turn to the XDA community. I will try this firs thing in the morning and give an update on how things went. I would try it tonight but lets be honest, its the 1st of the year and the last thing I need to be doing is messing with technology.....

Kraizk said:
Thank you for this and all of your help, people like you and ghostpirate are why i still feel like I can turn to the XDA community. I will try this firs thing in the morning and give an update on how things went. I would try it tonight but lets be honest, its the 1st of the year and the last thing I need to be doing is messing with technology.....
Click to expand...
Click to collapse
It's no problem, this isn't a dumb question or easy issue by any means. If the method I directed to you doesn't work, let me know. There is another way to do it without all the code.

slapshot30 said:
I haven't told anyone how to do it surprisingly, and I'm more than happy to help . I was honestly thinking about adding reverting back to stock to the superguide, and I think I just may do that. Here is the link. Pirateghost is the man.
http://forum.xda-developers.com/showpost.php?p=20821226&postcount=4
Click to expand...
Click to collapse
Worked perfectly. I flashed it back to stock using the thread you linked me to. Then I did the CWM Root method and so far so good. I appreciate all of your help

Nice, I'm glad you were able to get everything working.
Sent from my HTC PH39100 using xda premium

New N6 shipped with developer build?

Just bought a brand new N6 and its not downloading any ota's, still on 5.0. The build is LNX07M which is a developer build and apparently will not download any ota's. Has anyone heard of this? Did a quick Google search and there is hardly anything about this build.
I have no access to a computer, am I stuck on this build and 5.0?

csdaytona said:
Just bought a brand new N6 and its not downloading any ota's, still on 5.0. The build is LNX07M which is a developer build and apparently will not download any ota's. Has anyone heard of this? Did a quick Google search and there is hardly anything about this build.
I have no access to a computer, am I stuck on this build and 5.0?
Click to expand...
Click to collapse
no access at all?

simms22 said:
no access at all?
Click to expand...
Click to collapse
Not at the moment. What will I need to do?
This is my first nexus device and the last phone I rooted/flashed was the G1 way back in the day.
I was excited to get my phone today so this kind of sucks....

csdaytona said:
Not at the moment. What will I need to do?
This is my first nexus device and the last phone I rooted/flashed was the G1 way back in the day.
I was excited to get my phone today so this kind of sucks....
Click to expand...
Click to collapse
ohh.. that sucks. i remember my g1
i have a way that will probably work out fine, but this way is highly looked down upon on xda. would you be willing to try? btw, im one of those that would look down on this way, unless in certain situations..

simms22 said:
ohh.. that sucks. i remember my g1
i have a way that will probably work out fine, but this way is highly looked down upon on xda. would you be willing to try? btw, im one of those that would look down on this way, unless in certain situations..
Click to expand...
Click to collapse
OK what is it and why is it frowned upon?

csdaytona said:
OK what is it and why is it frowned upon?
Click to expand...
Click to collapse
because its not "proper", and normally isnt used properly. but ill explaine to you the proper way. you can try an app called kingsroot. you csnt get it at the play store, youll have to search google for it. after you install it, then run it, youll have root. but, youre not done yet. you will want to download the latest twrp recovery for the nexus 6 with your phone and keep it there. then you will unstall flashify from the play store. you will now use flashify to flash the twrp recovery. now, last thing, to get your bootloader unlocked. you will install any bootloader unlock apps, like boot unlocker or similar(that might delete everything from your phone), then youre done. ive never tried this on a nexus, but have on other devices, just so you know.

simms22 said:
because its not "proper", and normally isnt used properly. but ill explaine to you the proper way. you can try an app called kingsroot. you csnt get it at the play store, youll have to search google for it. after you install it, then run it, youll have root. but, youre not done yet. you will want to download the latest twrp recovery for the nexus 6 with your phone and keep it there. then you will unstall flashify from the play store. you will now use flashify to flash the twrp recovery. now, last thing, to get your bootloader unlocked. you will install any bootloader unlock apps, like boot unlocker or similar(that might delete everything from your phone), then youre done. ive never tried this on a nexus, but have on other devices, just so you know.
Click to expand...
Click to collapse
That seems like a lot of work. If I can get to a computer tomorrow, what can I do then?
Btw, thanks for helping me out.

csdaytona said:
That seems like a lot of work. If I can get to a computer tomorrow, what can I do then?
Btw, thanks for helping me out.
Click to expand...
Click to collapse
If you can get to a computer, download this: https://dl.google.com/dl/android/aosp/shamu-mra58k-factory-5b07088c.tgz
It's the Marshmallow (6.0) factory image for the Nexus 6. Run the batch file inside and it'll flash your phone. Note that this WILL wipe it.
Here's the actual Google-supplied information on it: https://developers.google.com/android/nexus/images?hl=en

|Jason8| said:
If you can get to a computer, download this: https://dl.google.com/dl/android/aosp/shamu-mra58k-factory-5b07088c.tgz
It's the Marshmallow (6.0) factory image for the Nexus 6. Run the batch file inside and it'll flash your phone. Note that this WILL wipe it.
Here's the actual Google-supplied information on it: https://developers.google.com/android/nexus/images?hl=en
Click to expand...
Click to collapse
First time doing this, but it's OK to jump straight to 6.0?

csdaytona said:
First time doing this, but it's OK to jump straight to 6.0?
Click to expand...
Click to collapse
It'll be fine. It's the complete system image, so it doesn't matter what you're on currently. Note that you will have to install all sorts of extra crap to get the Android SDK installed and working and the proper drivers, but it's not that hard, just gigs of downloads when everything is all said and done.
Like I said, it WILL wipe your phone completely.

csdaytona said:
That seems like a lot of work. If I can get to a computer tomorrow, what can I do then?
Btw, thanks for helping me out.
Click to expand...
Click to collapse
if you can get to a computer..
you can unlock your bootloader with "fastboot oem unlock"
then fastboot flash twrp recovery
then flash a custom kernel wiyh the latest supersu in your new recovery.
and then boot up with root, an unlocked bootloader, and a custom recovery

|Jason8| said:
It'll be fine. It's the complete system image, so it doesn't matter what you're on currently. Note that you will have to install all sorts of extra crap to get the Android SDK installed and working and the proper drivers, but it's not that hard, just gigs of downloads when everything is all said and done.
Like I said, it WILL wipe your phone completely.
Click to expand...
Click to collapse
Not worried about wiping the phone, I've literally only had it for a few hours and nothing is loaded on it.
Would be possible to just install an ota to get me on the right upgrade path? I'm just trying to do the quickest and easiest method possible.

csdaytona said:
Not worried about wiping the phone, I've literally only had it for a few hours and nothing is loaded on it.
Would be possible to just install an ota to get me on the right upgrade path? I'm just trying to do the quickest and easiest method possible.
Click to expand...
Click to collapse
If it's not grabbing an OTA, not sure what else you can do, short of downloading all the OTAs and flashing via recovery. But no guarantee that'll work as you're on a development build... There probably isn't an OTA to go from your development build to a release build.

csdaytona said:
I have no access to a computer, am I stuck on this build and 5.0?
Click to expand...
Click to collapse
simms22 said:
no access at all?
Click to expand...
Click to collapse
csdaytona said:
Not at the moment.
Click to expand...
Click to collapse
csdaytona said:
That seems like a lot of work. If I can get to a computer tomorrow, what can I do then?
Click to expand...
Click to collapse
Dude, come on... I know this is the Q&A section, and were supposed to be nicer here... But this lazyness is bull****.
You act like using a computer is impossible, then as soon as it takes some work.... You can get at one the next day?
Stop expecting to be spoon fed and at least try to learn something fist. There are a TON of write ups on how to do this. You spend how much money on a phone, and now you don't care to educate yourself on it?
Instead of expecting other to do all the work for you, read through the stickied index thread in the general section
http://forum.xda-developers.com/nexus-6/general/nexus-6-index-thread-t3229412
It has a newbie guide that literally holds your hand through the whole process. Post 2 has info on "how to flash factory images", use method 2 as method 1 in that thread will not work with the MM factory image.
Nice people have already spend a lot of time and effort documenting these things for you, as they are common questions. People like Simms and the other posters in this thread answer questions and offer support for free out of the kindness of their heart... Don't create extra work for them by ignoring all the effort already put out by other members, expecting it all to be regurgitated to you.
|Jason8| said:
If it's not grabbing an OTA, not sure what else you can do, short of downloading all the OTAs and flashing via recovery. But no guarantee that'll work as you're on a development build... There probably isn't an OTA to go from your development build to a release build.
Click to expand...
Click to collapse
Fastboot, as described in the threads mentioned above, will completely overwrite the pertinent partitions, regardless of what was there... dev build or not. No need to flash and apply countless incremental updates. Google provides not only full system images, but the information to use them on their web page...

|Jason8| said:
If it's not grabbing an OTA, not sure what else you can do, short of downloading all the OTAs and flashing via recovery. But no guarantee that'll work as you're on a development build... There probably isn't an OTA to go from your development build to a release build.
Click to expand...
Click to collapse
Gotcha. I'll try to flash 6.0 tomorrow. Wish me luck.
Thanks for the help!

scryan said:
Fastboot, as described in the threads mentioned above, will completely overwrite the pertinent partitions, regardless of what was there... dev build or not. No need to flash and apply countless incremental updates. Google provides not only full system images, but the information to use them on their web page...
Click to expand...
Click to collapse
I linked him to that already. No need to be a **** about it. He was looking for an easy way to do it now, when he doesn't have a computer. **** got crazy, so he asked if it would be easier with a computer, which the answer is yes.
Wouldn't you be excited as **** if you had a new phone? Wouldn't you want to get it up and running as quickly as possible? Well... now he's gotta wait until he has a computer. Obviously installing an OTA and doing the incremental updates would be easier, which is what he was looking for. Since that's not an option, we laid out other ways to go about doing it. So he's getting to a computer tomorrow.
---------- Post added at 09:51 PM ---------- Previous post was at 09:50 PM ----------
csdaytona said:
Gotcha. I'll try to flash 6.0 tomorrow. Wish me luck.
Thanks for the help!
Click to expand...
Click to collapse
No problem man. I wish you luck!
If you do plan on modding it/rooting it/romming it in the future, DEFINITELY unlock your bootloader before you set up the phone or that'll wipe it, too.

|Jason8| said:
Wouldn't you be excited as **** if you had a new phone? Wouldn't you want to get it up and running as quickly as possible? Well... now he's gotta wait until he has a computer. Obviously installing an OTA and doing the incremental updates would be easier, which is what he was looking for. Since that's not an option, we laid out other ways to go about doing it. So he's getting to a computer tomorrow.
Click to expand...
Click to collapse
You act like I was born with a nexus 6... It was a new phone to me too. I was so excited I read as much as I could on it, thanking the people who were so gracious to spend their personal time writing guides so I could understand the process well enough to be comfortable with my phone and help others here.

scryan said:
Dude, come on... I know this is the Q&A section, and were supposed to be nicer here... But this lazyness is bull****.
You act like using a computer is impossible, then as soon as it takes some work.... You can get at one the next day?
Stop expecting to be spoon fed and at least try to learn something fist. There are a TON of write ups on how to do this. You spend how much money on a phone, and now you don't care to educate yourself on it?
Instead of expecting other to do all the work for you, read through the stickied index thread in the general section
http://forum.xda-developers.com/nexus-6/general/nexus-6-index-thread-t3229412
It has a newbie guide that literally holds your hand through the whole process. Post 2 has info on "how to flash factory images", use method 2 as method 1 in that thread will not work with the MM factory image.
Nice people have already spend a lot of time and effort documenting these things for you, as they are common questions. People like Simms and the other posters in this thread answer questions and offer support for free out of the kindness of their heart... Don't create extra work for them by ignoring all the effort already put out by other members, expecting it all to be regurgitated to you.
Fastboot, as described in the threads mentioned above, will completely overwrite the pertinent partitions, regardless of what was there... dev build or not. No need to flash and apply countless incremental updates. Google provides not only full system images, but the information to use them on their web page...
Click to expand...
Click to collapse
i have absolutely no computer nor laptop access, so i completely understand(understood) his side as well.

scryan said:
You act like I was born with a nexus 6... It was a new phone to me too. I was so excited I read as much as I could on it, thanking the people who were so gracious to spend their personal time writing guides so I could understand the process well enough to be comfortable with my phone and help others here.
Click to expand...
Click to collapse
He googled his build number and didn't get many hits on it. So he's asking if there's a way to get it up and running tonight without a computer. Seems valid to me. You jump into the thread offering no help at all and start talking **** about the guy. That's the exact opposite of what you're saying you strive to do. I don't get it.

simms22 said:
i have absolutely no computer nor laptop access, so i completely understand(understood) his side as well.
Click to expand...
Click to collapse
At that point its a legitamate question. This is a very different situation that is not well covered here, and requires a unique solution not many would come up with.
But "I absolutely have no computer nor laptop access" is pretty different then "I can access one TOMORROW. Sheesh, having something 1 day away is pretty far from it not being a possibility.
And I think you would agree it would be a significantly better idea to wait that day then to proceed with the method you gave (not that it was bad of you to give it... but you tried to differentiate and he held out to avoid being told to do it the hard way)
|Jason8| said:
He googled his build number and didn't get many hits on it. So he's asking if there's a way to get it up and running tonight without a computer. Seems valid to me. You jump into the thread offering no help at all and start talking **** about the guy. That's the exact opposite of what you're saying you strive to do. I don't get it.
Click to expand...
Click to collapse
We are told time and time again that their are no bad questions. Truth is there are more bad questions then good ones.
Him asking about a build that provides few google hits is very legitimate.
Him asking about doing it without a computer because he doesn't have one is legitimate.
It only becomes an issue when he doesn't get the answer he wants, and all of a sudden he does have computer access.
And given that he is going to proceed in a computer... It becomes nothing more then "How do I update my phone?", which is VERY well documented.
I not only gave him the link to the information he needed, AND even corrected the information pointing out that the flashall script fails and that he would need to use the second method listed in the instructions I linked him to (since I know he will likely have limited time to fail and figure out whats wrong)
"That's the exact opposite of what you're saying you strive to do. I don't get it."
Then let me explain.
Would you skip your homework, ignore your textbook, then show up to class asking your teacher to explain it again? We are here to help... but how or why should I care more about it then he does? With no attempt made to learn, how much should I care to teach him?
Its a pretty big **** you to all those who have spend countless hours documenting this stuff to help new people to ignore their work and tell someone to do it again.

rooted sm-n910t3 Note 4 phone and now have error messages. please help with recovery.

Before coming across the link in this forum here at http://forum.xda-developers.com/not...y-steps-n910t3-dofc-dog1-how-to-root-t3177225 ...
I thought I could shortcut all the work by going to the auto root chainfire site to download the actual CF Auto Root File for model sm-n910t3. I successfully flashed that file using odin. It went into a bootloop and then I freaked out.
The error messages when I turn on the phone first show
"kernal is not seandroid enforcing" in red, and
"Set Warranty Bit: kernal" in yellow writing.
After being in this bootloop i went to the link posted above and followed each step by step. My phone is successfully rooted now and I can log in to my phone fine. However, there are two problems. First, those error messages are still there. How do I get rid of that? I tried a factory reset on my phone and it wont do it.
Will get to that after. Second, when I go into twrp by hitting volume up+home+power, once im in there it wont allow me to backup my current rom. It says an error message about E:/ data mount or something like that. And also while in twrp it won't let me factory reset my phone. So the recovery program is pretty useless to me. I don't know why it doesn't work properly.
Where do I go from here? Can someone help me out in fixing this error message and getting a recovery program to work? I'm just wondering why the twrp that I flashed while following that root guide above does not work. Has anyone ever encountered those two error messages while turning on their phone? Thanks.

The error messages are normal after rooting.
Sent from my SM-N920T using Tapatalk

mrfordwrench said:
The error messages are normal after rooting.
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
So other people have those messages on the top of their phone after rooting this device? Im guessing we just ignore that message then? I thought it was there because I flashed the wrong kernal before doing it the right way and following the forum...
What if I flashed the original firmware for this note 4 phone that I have a copy of, then root the phone going through that tutorial step by step? Wouldn't that get rid of the error messages? And my twrp would work then?
Im not able to make a backup of my current rom. And Im not even able to factory reset this phone. This is a problem for me since I want to put marshmallow on here soon. When I do I get an error message. Part of my second question is wondering why twrp isn't working correctly?

please help
i took my battery out to charge it and put a new one in. now it wont even boot up. it turns on and says
"custom binary blocked by FRP"
"secure fail: kernal"
for those of you who followed my other post i rooted my phone and tripped knox. phone was giving a message but would still turn on. where do i go from here? i have everything backed up and can start fresh. please provide step by step instructions on how i can fix this phone. thank you so much in advance and god bless.

I went to samsung and downloaded the firmware for this device and then flashed it. Now it's back to normal so you can disregard my post. Thanks guys.

scary
areininger30 said:
I went to samsung and downloaded the firmware for this device and then flashed it. Now it's back to normal so you can disregard my post. Thanks guys.
Click to expand...
Click to collapse
#UberNoob Drink your ovaltine. You should probably get an iPhone.
Everything worked as expected you are just so inexperienced you just gave us a play by play of your ignorance and then went running scared from the fear of 2x hello worlds and the unknown right back to momma Samsung. Good post

V3racious said:
#UberNoob Drink your ovaltine. You should probably get an iPhone.
Everything worked as expected you are just so inexperienced you just gave us a play by play of your ignorance and then went running scared from the fear of 2x hello worlds and the unknown right back to momma Samsung. Good post
Click to expand...
Click to collapse
Easy dude, that's not how things are done around here.

Ubernoob?
Drink my ovaltine? Hash tag for uber noob? Didn't your parents raise you to not say something if you have nothing nice to say at all? Apparently not so who's really the ignorant. Ask yourself that question. Ignorance is bliss. That's a good hashtag huh.
And the bottom line is that we were all beginners at one point right? So cut me some slack im learning. It will take me time to get to where you guys are at. Yes I am brand new to this stuff and no I don't like the iphones. Androids are more user friendly. I like Samsung phones and want to learn more about them.
Its people like you that keep us beginners from wanting to come back to this website, when guys say blatantly rude comments. It shouldn't be a bashing forum. Let's all chill and get along.

areininger30 said:
Drink my ovaltine? Hash tag for uber noob? Didn't your parents raise you to not say something if you have nothing nice to say at all? Apparently not so who's really the ignorant. Ask yourself that question. Ignorance is bliss. That's a good hashtag huh.
And the bottom line is that we were all beginners at one point right? So cut me some slack im learning. It will take me time to get to where you guys are at. Yes I am brand new to this stuff and no I don't like the iphones. Androids are more user friendly. I like Samsung phones and want to learn more about them.
Its people like you that keep us beginners from wanting to come back to this website, when guys say blatantly rude comments. It shouldn't be a bashing forum. Let's all chill and get along.
Click to expand...
Click to collapse
Good for you. If you need anything further, please don't hesitate to ask. There are a lot of great, talented and humble people on here, who would be glad to help.