I don't know much about root with the mytouch 4g Or any phone for that matter A
except that it is considered very very good However it may or may not want a warranty that is where I hear different issues
Could someone clarify the two things first what are the exact benefits I get out of it. would it take me back to what I had on my nexus --basic android. nd
Secondly would it void my warranty? If so is there a way of getting back to the original factory settings where they would not know?
Lastly there is no way I would be able to do this is there anyway of getting anyone else to do it in person or over the computer By giving me instructions I know there is a list of instructions but I was thinking more along the lines of seeing or speaking to someone
I would pay handsomely for this
Thank you and this was typed and sent using Dragon dictation so forgive me for any misspellings or punctuation I correct is almost all spelling and punctuation till the end
eric0668 said:
I don't know much about root with the mytouch 4g Or any phone for that matter A
except that it is considered very very good However it may or may not want a warranty that is where I hear different issues
Could someone clarify the two things first what are the exact benefits I get out of it. would it take me back to what I had on my nexus --basic android. nd
Secondly would it void my warranty? If so is there a way of getting back to the original factory settings where they would not know?
Lastly there is no way I would be able to do this is there anyway of getting anyone else to do it in person or over the computer By giving me instructions I know there is a list of instructions but I was thinking more along the lines of seeing or speaking to someone
I would pay handsomely for this
Thank you and this was typed and sent using Dragon dictation so forgive me for any misspellings or punctuation I correct is almost all spelling and punctuation till the end
Click to expand...
Click to collapse
1 - Simply rooting the phone would not give you the same setup that you had on your Nexus One, but it would allow you to get there. By rooting the phone, you are getting complete access to every partition on that phone and THAT is what allows changes to be made to the kernel and operating systems (aka ROMs). Unless you are a developer and know how to create your own ROM, you'd have to wait until one is created for us. Right now I believe there is one called Ice or something to that extent. You can check the Development section for that.
2 - Rooting technically does void your warranty, however there are way to get back to the original stock ROM/settings. There are threads in the Development section as well. As with anything that is in unfamiliar territory, take care and precaution when modifying your phone...especially if you use it on a daily basis and aren't sure of the exact steps to take.
Hopefully this was somewhat useful. Good luck!
Allen, and everyone, thank you
Yes, it does help
You say I can wait for one, or do my own, or use one by ??Ice.
Is that the one that was on the net, namely one like this, created by Scotty also?
http://www.intomobile.com/2010/11/11/root-mytouch-4g-install-custom-recovery/
1. Is that safe
2. Is the "flash" the thing that can get you back to factory settings
3. As far as the ? about getting anyone to take baby steps with you in doing this OR somewhere to take the phone to do it, has anyone heard of this.
Lastly, Allen
did you know anything about the phone locking up after a break, when using WiFi (EDIT: Oops thought I mentioned this in the post above. fwiw, anyone know why I can use wifi over the net quite well, using my browser (not to confuse using the wifi calling app, as one gent thought I meant. But then after a brief break, it locks up. even if I switch back to hspa. I have to restart. any ideas?)
Again, Thanks Allen, and all
If the only thing you know about rooting is "its very very good" then my suggestion would be to not do it just to do it.... do your research first, learn the basics and what its all about, yes there are pro's but theres con's. A simple mistake could leave you with a very expensive paper weight. All I'm saying is there's no need to jump in to it. root was around far before android and wont disappear over night. The only thing that I can't stress enough is research research research.
Sent from my HTC Glacier using XDA App
pack said:
If the only thing you know about rooting is "its very very good" then my suggestion would be to not do it just to do it.... do your research first, learn the basics and what its all about, yes there are pro's but theres con's. A simple mistake could leave you with a very expensive paper weight. All I'm saying is there's no need to jump in to it. root was around far before android and wont disappear over night. The only thing that I can't stress enough is research research research.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Hey, thanks pack
eric0668 said:
You say I can wait for one, or do my own, or use one by ??Ice.
Is that the one that was on the net, namely one like this, created by Scotty also?
1. Is that safe
2. Is the "flash" the thing that can get you back to factory settings
3. As far as the ? about getting anyone to take baby steps with you in doing this OR somewhere to take the phone to do it, has anyone heard of this.
Click to expand...
Click to collapse
For a beginner developing your own rom would be extremely difficult/almost impossible... no other roms have been released yet except for the ice one but that is the exact same thing as what you have now minus the stock apps
One problem with using other peoples roms is if you can't read the code you really don't know what your putting on your phone... with XDA a decent amount of us can read code and would say something if we found it malicious but what if noone took the time on that specific rom? unless you can read it that just brings me back to you really never know
So I guess that answers your is it safe question... its safe if you know what your doing... and don't get me wrong I'm not tryin to make it sound scary it'll be a 1 in a million shot to find a malicious file on xda but it could happen
2 flash an equal to install ... as installing a rom flashing a rom
3 no idea what you mean
Sent from my HTC Glacier using XDA App
pack said:
For a beginner developing your own rom would be extremely difficult/almost impossible... no other roms have been released yet except for the ice one but that is the exact same thing as what you have now minus the stock apps
One problem with using other peoples roms is if you can't read the code you really don't know what your putting on your phone... with XDA a decent amount of us can read code and would say something if we found it malicious but what if noone took the time on that specific rom? unless you can read it that just brings me back to you really never know
So I guess that answers your is it safe question... its safe if you know what your doing... and don't get me wrong I'm not tryin to make it sound scary it'll be a 1 in a million shot to find a malicious file on xda but it could happen
2 flash an equal to install ... as installing a rom flashing a rom
3 no idea what you mean
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
thanks. No, that just about answers it. very well, I might add. I will wait
what i meant, is if there is one that comes out, might there be someone who will walk you thru it, i.e for a newbie either thru chat, phone, or somewhere to take your phone to get it flashed with the new rom
oh ok i see, you would probably not want someone to do it for you because youll need to do it more than once... if someone walks you through it at least you learn how to do it and you'll be able to do it next time (and trust me theres always a next time) if your interested in doing it i pm'd you my aim name and id help you out with it... its really quite simply when its broken down... but like i said before id do some more research on it first and come up with some reason you personally need root access because its importance to other people may not mean anything to you n vice versa.
I called customer service just a minute ago and they told me they would send me a new Nexus that will get here and in about two days, and after that I ship mine back to them. Should I return it to stock or is Google usually pretty cool about this? Has anyone else done this?
I would go back to stock. Its pretty simple at at least with wugfreshs toolkit. Which is something I usually stay away from but it was the simplest way especially since I just got mine.
Sent from my Nexus 7
Yeah, I usually stay away from toolkits, at least when it comes to actually rooting the device. But, I'll try that! Thanks for the fast response.
Benjamin150 said:
Yeah, I usually stay away from toolkits, at least when it comes to actually rooting the device. But, I'll try that! Thanks for the fast response.
Click to expand...
Click to collapse
No problem was a breeze with the toolkit.
https://www.youtube.com/watch?v=5HW_e99I5iM&feature=youtube_gdata_player
Video you can use. Used this as a refrence. But the extra steps he takes for downloading the .tgz wasn't necessary for my case.
Sent From My Toro+ via RED Tapatalk
I'm seeing that from Android phone to phone, each manufacturer tends to place the back key (whether usual hardware or Nexus Galaxy/4 software/virtual) in different locations. This tends to be annoying, especially if you have got used to placing your thumb in the "back" location.
I'm sure that on the Nexus 4, the software/virtual based BACK / HOME / APP buttons can be assigned. But can they be done without rooting and putting on a custom ROM? I'm not ready to go through rooting my new Nexus 4 (yet), and I'm hoping that Google put a little freedom into their 4.2.1 O/S.
Thank you.
PiCASSiMO said:
I'm seeing that from Android phone to phone, each manufacturer tends to place the back key (whether usual hardware or Nexus Galaxy/4 software/virtual) in different locations. This tends to be annoying, especially if you have got used to placing your thumb in the "back" location.
I'm sure that on the Nexus 4, the software/virtual based BACK / HOME / APP buttons can be assigned. But can they be done without rooting and putting on a custom ROM? I'm not ready to go through rooting my new Nexus 4 (yet), and I'm hoping that Google put a little freedom into their 4.2.1 O/S.
Thank you.
Click to expand...
Click to collapse
Nope
Not stock
Need custom ROM AFAIK
Sent from my A510 using Tapatalk HD
PiCASSiMO said:
I'm seeing that from Android phone to phone, each manufacturer tends to place the back key (whether usual hardware or Nexus Galaxy/4 software/virtual) in different locations. This tends to be annoying, especially if you have got used to placing your thumb in the "back" location.
I'm sure that on the Nexus 4, the software/virtual based BACK / HOME / APP buttons can be assigned. But can they be done without rooting and putting on a custom ROM? I'm not ready to go through rooting my new Nexus 4 (yet), and I'm hoping that Google put a little freedom into their 4.2.1 O/S.
Thank you.
Click to expand...
Click to collapse
Doubt Google would add that in. Have to flash a custom ROM.
Custom ROM is the only way. If you want we can guide you through the process of flashing one if you like to. Don't use a toolkit is the first step. Take the time and learn it as it takes < 30 minutes to learn and it will be a basic "get me out of this hole!" method when your phone is somehow ever in a non bootable state and you won't mistaken yourself for bricking your phone when its not
http://forum.xda-developers.com/showthread.php?t=1972508 is a good guide to get started on for unlocking your bootloader which is the first step.
Don't know why everyone is so against toolkits. I have used them on my galaxy nexus. Sgs3 and now my nexus4 numerous times and haven't had a single issue. Ever.
The toolkits runs the same commands that you would if you were to do it in fast boot and cmd.
Sent from my A510 using Tapatalk HD
c_86 said:
Don't know why everyone is so against toolkits. I have used them on my galaxy nexus. Sgs3 and now my nexus4 numerous times and haven't had a single issue. Ever.
The toolkits runs the same commands that you would if you were to do it in fast boot and cmd.
Sent from my A510 using Tapatalk HD
Click to expand...
Click to collapse
I am personally against toolkits because people are using it without knowing what they're doing and not knowing how to do basic things such as fastboot and adb. Then they come to using recoveries not knowing what happened and end up messing their phones up.
Yes it runs the SAME commands, but you aren't doing it yourself.
It's like what I said in other threads,
Let's say you wanted to go from Home (point A) to school (point B). You can do it in two ways,
1) Do it manually and learn the steps on how to go from Point A to B.
2) Use a toolkit that will get you to Point A to B, not knowing HOW you got to Point B.
I'm not saying this to get people to become smart or learn some stupid commands that they will never use. Chances are, every user flashing things on XDA should know these basic commands (not even know because you can just look it up).
If you used Method 2, what happens if theres a road closure? What do you do there?! you used a toolkit, you are stuck and you resort to asking questions on how to get back to Point A to reroute yourself to Point B.
If you used Method 1, you are able to backtrack yourself to fix problems leading to a better community which will result in less questions on how to return back to stock for warranty purposes, RMA purposes, flashing something and their phone isn't booting up but THEY CAN boot into bootloader mode (if they used toolkit, they dont know how to flash back to stock or flash a new recovery). Things like that. After all, this is a DEVELOPER forum not a tech support forum, am I not right about this?
Both method 1 & 2 brings you to Point B. But method 1 is more important as eventually, people using toolkits will need to use fastboot and adb sometime. Maybe not today, but sometime in their lifetime they will have to use it and will have to learn. So why not spend the 15-20 minutes and learn it now? Not be spoon fed. I used the G1, I had to work my butt to obtain root via 30-35 minute of using ADB shell and terminal emulator.
Yes method 1 takes longer (not that much longer) but in the end it'll pay off and is worth spending that 15-20 minute reading it, it's a step-by-step process and doesn't take a rocket scientist to know how to do it. It looks difficult at the start (it really doesn't, just follow the steps in the guide as it goes) but after that it looks like a walk in a park and is just as easy as using a toolkit.
Hey folks! I have an Acer A500 that I have been working on "with" dibb_nz over the past week. I have no idea what was on it originally, it came to me nearly dead. After a TON of attempts and hard work from dibb, I now have Skrilax's bootloader and recovery installed. I flashed CM10-10 Flex_V6 ROM from Civato onto the device successfully. Here is the problem: no matter how I boot up, it either goes directly into "Power off - Shutting down" then vibrates and blanks out or, after a fresh install, it will say "Android is upgrading", "Optimizing apps", "Starting Apps", then on to the Power Off-shutting down thing.
Does anyone have any clue what may be going on here? I have tried earlier ROMS, all from Civato, but with the same Power OFF result.
Any help would be MUCH appreciated!
Thanks in advance,
Sharkguy
hey sharkguy, I've been combinf forums and threads with no joy at all, the only thing I haven't checked is the rom thread, might pay you to look thru that, just in case its rom related ( I doubt it really, but there maybe other reports such as yours ) If I ever come across something I'll be sure to get back to you, good luck m8
Calling @Moscow Desire---are you out there Mr Moscow?? Ever heard of something like this before, my friend, very strange....Hope you are well MD its been awhile
dibb_nz said:
hey sharkguy, I've been combinf forums and threads with no joy at all, the only thing I haven't checked is the rom thread, might pay you to look thru that, just in case its rom related ( I doubt it really, but there maybe other reports such as yours ) If I ever come across something I'll be sure to get back to you, good luck m8
Calling @Moscow Desire---are you out there Mr Moscow?? Ever heard of something like this before, my friend, very strange....Hope you are well MD its been awhile
Click to expand...
Click to collapse
Hey Dibb! Offhand, I think it may be the old power part that used to be flashed with stock ROMs. Forget what its actually called. Typically we removed this from the install as its generally not needed. That's a guess, but am at work for the night so can't check my stuff. Could explain the shutdown. But if it shuts down when updating the apps, then its probably bad memory partition.
But I'll lean more towards the power part. Will have to check a stock ICS ROM. Might need to make a separate flash install just for it. It it would boot to the display and it had horrible display and battery issues then that would be it.
Well, that sounds complicated. I should have the new battery by the weekend so let me at least try that before anyone gets all technical. Unfortunately I dont know anyone with another a500 to test batteries...
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Moscow Desire said:
Hey Dibb! Offhand, I think it may be the old power part that used to be flashed with stock ROMs. Forget what its actually called. Typically we removed this from the install as its generally not needed. That's a guess, but am at work for the night so can't check my stuff. Could explain the shutdown. But if it shuts down when updating the apps, then its probably bad memory partition.
But I'll lean more towards the power part. Will have to check a stock ICS ROM. Might need to make a separate flash install just for it. It it would boot to the display and it had horrible display and battery issues then that would be it.
Click to expand...
Click to collapse
Hey MD good to see u my friend
oh, the eec thing? Rings a bell...
The bad memory partition, do you mean the memory chip itself or just the partition.
I've just never heard of the faulty chip causing a spontaneous shut down, sure has me beat....and I Hate that, lol
But thanks for the response MD, if you can offer any solution from your archives of knowledge and wisdom, I know someone who'd be forever grateful
Have a great day all!!
rgds Donna
Yeah Dib, the eec thing. Just couldn't remember. Usually we just removed that command from the install script as usually once it was flashed at the factory, rarely did you ever have to flash it again. I will have to look and see in the next couple of days. Worth a shot though. Might be able to put it in a CWM install.
Oh, forgot to add @sharkguy
As with a damaged partition, if the memory got hosed in that particular partition, whichever, there's not a whole lot that can be done. Could try running babsector, but not sure if it would fix it or not. There's been success running it before, but only about 30% as I can tell. Devblks can get physically damaged. Usually the partitions are large enough to mark the bad spots as bad, and still be able to install things. That's what babsector did I think as near as I can tell.
A faulty chip "could" cause a shutdown, especially if it couldn't create the dalvak which is kind of the next step when "starting applications" If I guess right, although I would think it would bootloop rather than shut down. As you say, I've never heard of a power off before, unless the eec was bad and it thinks the battery is dead.
I'm just curious if the OP has done a full format on internal memory via CWM? Before installing. Not the usual wipes, but going into advanced, and triggering the full format. I used it after running that CM stuff awhile back, as it messed up everything (lots of testing). Needed a clean sweep of the internal memory.
As you see, I am still around Just with being a senior mod, not a lot of time for messing with things.
I'm still leaning towards eec pwr. (I'm using beer logic at this point)
Bear with me on this. Let's say the eec got hosed somehow. It happens on occasion. And you install several custom roms, which of course don't have eec pwr in the install script as we removed it. Here's what I know.
1) Battery won't charge and is always going to shut down
2) No response on the touch screen if indeed the OS starts.
3. Tab shuts down after OS start.
So you see why I am leaning towards this.
MD
EDIT: The reason why we removed eec from the custom roms to begin with, primarily as it really wasn't needed, but it "could" cause an issue if the flash went bad. But considering the OP has UID and NVFlash, that isn't an issue now.
dibb_nz said:
Hey MD good to see u my friend
oh, the eec thing? Rings a bell...
The bad memory partition, do you mean the memory chip itself or just the partition.
I've just never heard of the faulty chip causing a spontaneous shut down, sure has me beat....and I Hate that, lol
But thanks for the response MD, if you can offer any solution from your archives of knowledge and wisdom, I know someone who'd be forever grateful
Have a great day all!!
rgds Donna
Click to expand...
Click to collapse
Hey MD, thanks for thr insight on my issue. I worked closely with Dibb_nz for close to a week. I am not entirely sure if I did the wipe you mentioned, but believe me, if I could find a way to format, erase, wipe or clear memory I did. Everything you described as what you knew is correct with one exception: if it is relevant the touch screen works in recovery mode.
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
sharkguy said:
Hey MD, thanks for thr insight on my issue. I worked closely with Dibb_nz for close to a week. I am not entirely sure if I did the wipe you mentioned, but believe me, if I could find a way to format, erase, wipe or clear memory I did. Everything you described as what you knew is correct with one exception: if it is relevant the touch screen works in recovery mode.
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Click to expand...
Click to collapse
Always works in recovery, as it is independent of the OS...
Righto. I figured it didnt matter in this case. But yes, the rest of the facts are as you understand them.
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
sharkguy said:
Hey MD, thanks for thr insight on my issue. I worked closely with Dibb_nz for close to a week. I am not entirely sure if I did the wipe you mentioned, but believe me, if I could find a way to format, erase, wipe or clear memory I did. Everything you described as what you knew is correct with one exception: if it is relevant the touch screen works in recovery mode.
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Click to expand...
Click to collapse
The FULL wipes as stated in the guide m8 or via fastboot erase.
@Moscow Desire _bab sector was run and successfully, boot loader and recovery installed with no errors.
As far as the eec thing I do have a copy of that in my stash if that's any help, but no idea how to apply it????
Sent from my HTC_PN071 using Tapatalk
Well at this point I am open to anything. I just passed up on a steal of a deal on a Samsung Galaxy Tab 3 7" so im itching to know I made the right choice. I am at your mercy. Doesnt look like I will have that battery until saturday at the earliest, but so far all of the work I have done on it has been with AC power and has been successful.
Sent from my SGH-I317M using xda app-developers app
sharkguy said:
Well at this point I am open to anything. I just passed up on a steal of a deal on a Samsung Galaxy Tab 3 7" so im itching to know I made the right choice. I am at your mercy. Doesnt look like I will have that battery until saturday at the earliest, but so far all of the work I have done on it has been with AC power and has been successful.
Sent from my SGH-I317M using xda app-developers app
Click to expand...
Click to collapse
Well m8 I dunno if u made the right choice there, I guess only time will tell...there is this thread http://forum.xda-developers.com/showthread.php?t=2617196. I cannot recommend it but then my tab has never been in that state...and I'm not sure I could bring myself to put it in the oven lol...u nut wanna take a look at it any way
Sent from my HTC_PN071 using Tapatalk
Oh I've heard of ppl doing such things, but I'm luckily far mor fortunate than that. I am an electronics technician and have access to far for humane methods than an oven! Maybe I will see if I can still get the deal, then hack the a500 to pieces after geting the new battery in the mail. Lol
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
sharkguy said:
Oh I've heard of ppl doing such things, but I'm luckily far mor fortunate than that. I am an electronics technician and have access to far for humane methods than an oven! Maybe I will see if I can still get the deal, then hack the a500 to pieces after geting the new battery in the mail. Lol
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Click to expand...
Click to collapse
Well, you'll be in your element then,lol...Yeh, your issue is rather unique...with babsector not returning any error its out of my area of expertise!!! But I do know that Acers build quality isn't the best....from power buttons falling out to the memory chip failure and their dodgy soldering techniques, i'm leaning towards a hardware fault 'somewhere'....
But then, it does seem strange the tab powers off during "updating apps" that points to software doesn't it???? Have look in the guide for fastboot commands (if you still have the unlocked bootloader on there) I'd erase all partitions, /system, /data, /cache etc....then run babsectot again to repartition -flash a rom and see what happens...or use tdv4 to do the same, but no rom flash needed for that as it comes with HC 3.2.1 rooted and cwm.
Anyways m8 keep us updated - and fingers crossed you end up with a positive resolution
rgds Donna
One of the last things I think I did was tdv4 without a rom flash. It still came up with the same issue. I did notice that when I took the battery out to charge on the equipment at work (closely monitored of course) to see if there was an issue with the charging circuit, that I could still do all of the same things as before with just the AC plugged in. No battery. This is why I bought a battery to try that out. The Galaxy 3 guy realized what a steal he was offering me and bumped up his price so it looks like I'm stuck woth the A500.
Thanks for the crossed fingers!!
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Well new battery us in and seems to charge just fine. In fact the tablet would not even attempt to power on before without AC so that is a plus. However, the same thing happens still. Boots up, and as soon as it enters the OS it gies straight to powering down.
What was the EEC thing you guys were discussing? Would it potentially help here?
Thanks again!
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Used all of the elements at my disposal at work to reflow the board without any change in the status of the tablet. Any ideas based on that EEC thing you guys discussed above?
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
sharkguy said:
Well new battery us in and seems to charge just fine. In fact the tablet would not even attempt to power on before without AC so that is a plus. However, the same thing happens still. Boots up, and as soon as it enters the OS it gies straight to powering down.
What was the EEC thing you guys were discussing? Would it potentially help here?
Thanks again!
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Click to expand...
Click to collapse
sharkguy said:
Used all of the elements at my disposal at work to reflow the board without any change in the status of the tablet. Any ideas based on that EEC thing you guys discussed above?
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Click to expand...
Click to collapse
Soz m8 been full on at work to even check emails let alone reply...phew!!!!
As MD pointed out above, the EEC file thing, devs have dealt with that particular issue, but b/c yours is a relatively unique issue I guess it can't be ruled out...
Have you managed to take a look at fastboot and using the erase command to delete EVERYTHING - at least u can be sure its as clean as can be, then using babsector with an appropriate rom and see what happens there.
In that "tab flu" thread there are links to another thread (somewhere) re: eec thing - If you find it can link it here in this thread and I'll track down the file -
Oh, just to be clear - when it boots into to the OS and powers off - is it completely shutting down i.e. power led is off or is it actually booting to apx mode, black screen power lite on...whats the chances of a vid so we can see exactly what it does???
rgds dibb
Sure I can video it for ya, but how should I link it? Can I link to YouTube on these forums?
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
sharkguy said:
Sure I can video it for ya, but how should I link it? Can I link to YouTube on these forums?
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Click to expand...
Click to collapse
Ok, so new development, so to speak. As you can see from the crappy video I shot just now, I can boot the tablet into the start of the OS, but it hangs at Powering Down. The new part is that I had to manually shut it off, it did not do that itself this time. I showed you the power light (orange) and when I press it again, it does power on, but is still hung up on the same screen. I don't know if that helps any, but now you can see it. By the way, sorry it is upside down, it was the only way to show you the power button after it booted.
http://youtu.be/pG_efbq6DZg
Can anyone please help me? Today I got my 6P and decided to try and root it. Now it wont get out of the boot animation and ADB devices no longer lists my phone. Is there a chat room or walk through for fixing this? I'm in a pretty large amount of mental agony over this. I just want stock back and will never fiddle again. Promise.
Hawkison said:
Can anyone please help me? Today I got my 6P and decided to try and root it. Now it wont get out of the boot animation and ADB devices no longer lists my phone. Is there a chat room or walk through for fixing this? I'm in a pretty large amount of mental agony over this. I just want stock back and will never fiddle again. Promise.
Click to expand...
Click to collapse
How did you root it? If you follow my guide you'll have no problems.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
You'll need to start from scratch though so follow the directions in section 9 first, that'll take your phone back to stock.
I used the Nexus Root Toolkit I found because I figured I'm a novice, this will do it for me. Hah! Nope. Also tried to restore it that way. No go, surprising no one at this point.
Ok. So i had the wrong file, because again, I'm a moron and it has been proven. Looks like things are going back to stock ok now. <3 :crying: so happy
Hawkison said:
I used the Nexus Root Toolkit I found because I figured I'm a novice, this will do it for me. Hah! Nope. Also tried to restore it that way. No go, surprising no one at this point.
Click to expand...
Click to collapse
Hawkison said:
Ok. So i had the wrong file, because again, I'm a moron and it has been proven. Looks like things are going back to stock ok now. <3 :crying: so happy
Click to expand...
Click to collapse
A word of advice: don't use toolkits. While they may seem helpful for a novice like yourself, they'll keep you at a novice level because they allow you to do things to your device without actually knowing what's going on. This prevents you from doing any learning and advancing. Take the time to learn how to use fastboot and you'll see it isn't as daunting as you may think, plus you'll get great satisfaction from doing these things yourself. Have a look at my guide, and if you have any questions myself and others are there to help.