Related
Ok so, I bought this awesome device and Im waiting for it to be delivered. I know that rooting has awesome features and great things, but Im wondering if someone has experienced any kind of issue after rooting... I read somewhere here in the forum, that the Wifi on someone's tablet stopped working and he had to return it.. Sadly, I can't be returning stuff since I live out of the states and is not that easy... Hope someone can tell me ^^ Would love to have 3 or 4 answers for me to take my decision. Thanks in advance.
Jailuis
jailuis said:
Ok so, I bought this awesome device and Im waiting for it to be delivered. I know that rooting has awesome features and great things, but Im wondering if someone has experienced any kind of issue after rooting... I read somewhere here in the forum, that the Wifi on someone's tablet stopped working and he had to return it.. Sadly, I can't be returning stuff since I live out of the states and is not that easy... Hope someone can tell me ^^ Would love to have 3 or 4 answers for me to take my decision. Thanks in advance.
Jailuis
Click to expand...
Click to collapse
If you follow instructions to a complete letter and make sure it's the correct rooting instructions for your version number, then all should be well but I do have to say that it's always done at your own risk. There's no way around that.
I have not read anyone else with rooting problems on here for the KFHD. The guy with the wifi post which I've read most likely got a dud. Mine was rooted and ran fine for me. I returned mine for other reasons.
Just be careful on what you do to your device. If you do something you shouldn't with your "extra privileges", it can be easy to brick your device. Especially when it's so young in development stages right now.
I received my fire a week ago. I intended to root it like I have all other android devices I own.
I have kept it stock and probably will for awhile. I just did not feel the need to root. I side loaded GMail and most other Google apps I wanted. I side loaded adw launcher and dolphin browser. So I feel no real reason to root since a few people have had problems.
Now when the boot loader gets unlocked and there is custom Roms now that is a different story.
Sent from my KFTT using Tapatalk 2
I rooted yesterday. Got go ex as default launcher, play store, dolphin, etc. No problems yet. Seems faster, if anything.
There aren't many risks with it other then the average (brick). Which can occur with any device. Just make sure you follow the steps correctly step by step, and make sure your adb drivers are installed correctly.
Pirub said:
I rooted yesterday. Got go ex as default launcher, play store, dolphin, etc. No problems yet. Seems faster, if anything.
Click to expand...
Click to collapse
About the only reason I'd root is for the play store
Sent from my Galaxy S3
You risk having a better running tablet
Sent from my EVO using xda premium
My devices are all rooted, for my Bionic, it's so that I can use AdFree, Titanium Backup and to run AirBubble, which let's AirPlay devices see the phone and ply music to it remotely (or to whatever speakers it's plugged in to! ) It doesn't have to be used for illegal stuff, it just unlocks your phone's administrator privileges so that those that know specific use cases which require lower level code can go ahead and run. If you can already do everything you want with your phone, you don't need to root it.
GeekSpeak411 said:
My devices are all rooted, for my Bionic, it's so that I can use AdFree, Titanium Backup and to run AirBubble, which let's AirPlay devices see the phone and ply music to it remotely (or to whatever speakers it's plugged in to! ) It doesn't have to be used for illegal stuff, it just unlocks your phone's administrator privileges so that those that know specific use cases which require lower level code can go ahead and run. If you can already do everything you want with your phone, you don't need to root it.
Click to expand...
Click to collapse
Rooting is good for getting rid of bloatware too.
With rooting there is always a risk that you are going to screw something up. The easiest way to ensure that doesnt happen is to not root the device. But if you are going to anyway just don't do something you don't fully understand unless you are willing to take the risks.
For example if you do not know how to use adb then don't try at this time, play around with it on something else. If you still want root and don't know adb then use the automated root tool. All the hard stuff is done for you and there is no chance of inputting something wrong and causing problems. To avoid any conflicts with apps or settings reset the device to factory. Just one more step to take human error out of the equation.
After the device is rooted is when people tend to cause problems for themselves. IF YOU DON'T KNOW WHAT IT IS/DOES DON'T TOUCH IT!!! If you are messing around inside a file manager any folder outside the sdcard folder has the potential to cause problems so- IF YOU DON'T KNOW WHAT IT IS/DOES DON'T TOUCH IT!!!(unless you can afford the risk)
When making changes, research what you are trying to do extensively and don't rely on one source. What worked for one person will not always work for another, to many variables.
All in all just aire on the side of caution.
Thanks for all responses ^^ I've had other android devices and I had rooted them, but Im afraid with this one since I read about the wifi not working anymore... But thanks to all of you I might give it a shot. One last thing, I have 2 KFHD, do I have to install Adb for both?
Sent from my KFTT using xda premium
jailuis said:
Thanks for all responses ^^ I've had other android devices and I had rooted them, but Im afraid with this one since I read about the wifi not working anymore... But thanks to all of you I might give it a shot. One last thing, I have 2 KFHD, do I have to install Adb for both?
Sent from my KFTT using xda premium
Click to expand...
Click to collapse
I used the auto root tool without issues. I would think once you install adb on your Pc it should work for both. I had to also install the android sdk tool.
Sent from my KFTT using Tapatalk 2
no risk.just go ahead.toot it.lol
onemeila said:
With rooting there is always a risk that you are going to screw something up. The easiest way to ensure that doesnt happen is to not root the device. But if you are going to anyway just don't do something you don't fully understand unless you are willing to take the risks.
For example if you do not know how to use adb then don't try at this time, play around with it on something else. If you still want root and don't know adb then use the automated root tool. All the hard stuff is done for you and there is no chance of inputting something wrong and causing problems. To avoid any conflicts with apps or settings reset the device to factory. Just one more step to take human error out of the equation.
After the device is rooted is when people tend to cause problems for themselves. IF YOU DON'T KNOW WHAT IT IS/DOES DON'T TOUCH IT!!! If you are messing around inside a file manager any folder outside the sdcard folder has the potential to cause problems so- IF YOU DON'T KNOW WHAT IT IS/DOES DON'T TOUCH IT!!!(unless you can afford the risk)
When making changes, research what you are trying to do extensively and don't rely on one source. What worked for one person will not always work for another, to many variables.
All in all just aire on the side of caution.
Click to expand...
Click to collapse
Thanks.
Hi All,
I'm a complete Noob to the Android world so I passed my Kindle Fire HD to friend who said he can install Jellybean on for me, but now the unit does not respond to anything? Has he bricked it and is there any way of fixing it?
Yes bricked. At this point doesn't look good.
ammo789 said:
Hi All,
I'm a complete Noob to the Android world so I passed my Kindle Fire HD to friend who said he can install Jellybean on for me, but now the unit does not respond to anything? Has he bricked it and is there any way of fixing it?
Click to expand...
Click to collapse
If you plug it into a pc does it recognise the device, or even an android device?...Im no expert but Ive had some bad roots in my time and got very affraid. Ive found that if a pc can recognise it all hope is not lost. Saying that Ive also found that PC's have problems with very flat batteries. Leave on the the PC usb to charge for several hours before you pass judgement...I know this is a difficult option on the Fire but if that doesnt work you could try to remove the battery for a couple of hours. This is hands on stuff I never tried....there might be something on You Tube? Im Guessing since the battery is enclosed it might not be a simple "lift out"!!!!! As far as I am aware there isnt a recovery or download mode you can boot into... You could try seaching Kindle fire Hard Brick / soft brick for more information....A soft brick is good!!! Not very good but better than hard brick!
In future Id ask to see your friends device running rooted or with a different ROM. I only do mine and family until I know I can make it work...
Im not really liking the fire so much! I tried rooting one today....It didnt brick and it rooted....However Super user didnt get root access....Those tricksters at Amazon are trully annoying
thedeester1 said:
If you plug it into a pc does it recognise the device, or even an android device?...Im no expert but Ive had some bad roots in my time and got very affraid. Ive found that if a pc can recognise it all hope is not lost. Saying that Ive also found that PC's have problems with very flat batteries. Leave on the the PC usb to charge for several hours before you pass judgement...I know this is a difficult option on the Fire but if that doesnt work you could try to remove the battery for a couple of hours. This is hands on stuff I never tried....there might be something on You Tube? Im Guessing since the battery is enclosed it might not be a simple "lift out"!!!!! As far as I am aware there isnt a recovery or download mode you can boot into... You could try seaching Kindle fire Hard Brick / soft brick for more information....A soft brick is good!!! Not very good but better than hard brick!
In future Id ask to see your friends device running rooted or with a different ROM. I only do mine and family until I know I can make it work...
Im not really liking the fire so much! I tried rooting one today....It didnt brick and it rooted....However Super user didnt get root access....Those tricksters at Amazon are trully annoying
Click to expand...
Click to collapse
Cheers Mate,
Will try and charge it first and see if there is any life and if my machine picks it up.
Bricked!
Sorry, but you're likely bricked. There is another thread on here about the same thing. Your buddy messed up royally as the ROMs available are only for the original KF, not the KFHD and most of the ones I've seen clearly spell that out (although some development is under way). I'd say it's time to pay him a visit!
no99sqrd said:
Sorry, but you're likely bricked. There is another thread on here about the same thing. Your buddy messed up royally as the ROMs available are only for the original KF, not the KFHD and most of the ones I've seen clearly spell that out (although some development is under way). I'd say it's time to pay him a visit!
Click to expand...
Click to collapse
Yeap I guess it's R.I.P Kindle
He has offered to buy a new one foe me but I have told him to hang on for a couple of weeks just incase someone finds a fix and to be honest he was trying to help me out so can't really go mad at him when he has offered to buy a new one.
ammo789 said:
Yeap I guess it's R.I.P Kindle
He has offered to buy a new one foe me but I have told him to hang on for a couple of weeks just incase someone finds a fix and to be honest he was trying to help me out so can't really go mad at him when he has offered to buy a new one.
Click to expand...
Click to collapse
So no life what so ever....
Well Like you say hang on to it. I wouldnt hold your breath for a fix in the next couple of weeks though....The root is only an exploit and roms are pretty far away. Given the fact that there isnt a DL mode or recovery mode your brick is still gonna be just as broken in 2 weeks time.
As far as I am aware the Root is an Exploit. It doesnt actually unlock the bootloader it just tricks it, so ROMS are a long way away..
Someone will do it...they always do. If it can be programmed by people it can be hacked by people. Given the way Amazon locked it down though it might be months. Mind you they said that about the ROOT and that took days...So I could be wrong!
How about selling it for spares on E-bay....The battery is gonna be good and people are always dropping stuff so the case and screen will be worth something!
Im really sorry about your device...Im pretty noob to android and have screwed a device trying to go a step further. It does suck but I kept at it and I am learning......SO next time dont give it your M8 to screw up....Try not to screw it up yourself....
For me thats the whole point of Android. Stick with this forum and all the helpfull people on it!
You should read this post: http://forum.xda-developers.com/showthread.php?t=1951254
Im doing a lot of work on a family members Kindle Fire HD at the moment and your plight made me think I ought to make provisions for a bricking.
Found the post above hope it helps!!!!
thedeester1 said:
You should read this post: http://forum.xda-developers.com/showthread.php?t=1951254
Im doing a lot of work on a family members Kindle Fire HD at the moment and your plight made me think I ought to make provisions for a bricking.
Found the post above hope it helps!!!!
Click to expand...
Click to collapse
I dont think that will work. Thats if the KFHD is not recognized by the PC. I bricked mine b4, where all it would to is launch into recovery mode. If the KFHD still turns on, I recommend a factory cable. You can find them on ebay or other places. It worked for me.
I tried all known methods for rooting but all failed.
Even when you unlock it there is still no TWRP available for the 701.
I asked the devs of twrp on their website to take a look at the 701.
If anyone has more knowledge about progress made on this subject please react here.
Sent from my superfast Asus Infinity TF701with Dock
Knock it Off Please
Ok, forum just opened and;
1. Posted in the development forum instead of General or Q & A (shame shame)
2. Flaming already starts
Knock it off people. Jeeze..... Things will come in good time. Unless of course you want to rush things and brick yer tabs
Keep it clean people.
MD
Now, if you have fastboot OEM unlock,
,
Then perhaps you can pull your boot.img, separate zImage from Ramdisk, modify ro.secure=0, add RW comments, repack your boot.img, fastboot flash boot boot.img, then install BB and SU.
Just a thought.
MD
Moscow Desire said:
Now, if you have fastboot OEM unlock,
,
Then perhaps you can pull your boot.img, separate zImage from Ramdisk, modify ro.secure=0, add RW comments, repack your boot.img, fastboot flash boot boot.img, then install BB and SU.
Just a thought.
MD
Click to expand...
Click to collapse
Sad part the "Fastboot OEM unlock" won't work cause Asus has theirs encrypted. You have to use their unlocking tool to unlock your bootloader. Given fact it can work, been trying it for 2 days now and stupid app won't unlock my bootloader. Read my S/N may not be registered in their database so emailed them complaining about another service that doesn't work.
Tiger62651 said:
Sad part the "Fastboot OEM unlock" won't work cause Asus has theirs encrypted. You have to use their unlocking tool to unlock your bootloader. Given fact it can work, been trying it for 2 days now and stupid app won't unlock my bootloader. Read my S/N may not be registered in their database so emailed them complaining about another service that doesn't work.
Click to expand...
Click to collapse
They'll get around to it. Heck, when I had to turn in my A701 to service center, they didn't even know it had been released Tried telling me it was a "leaked and illegal" tablet.
Good luck with the bootloader mate, but root after that should be pretty straight forward. (fingers crossed)
I think that unlocking bootloader is bad idea. After that the warranty will be void...
Moscow Desire said:
They'll get around to it. Heck, when I had to turn in my A701 to service center, they didn't even know it had been released Tried telling me it was a "leaked and illegal" tablet.
Good luck with the bootloader mate, but root after that should be pretty straight forward. (fingers crossed)
Click to expand...
Click to collapse
Yeah well tried to call them and got the usual "just send it back" well not waiting 2-3 weeks just get to get it back. Since there is something wrong with the charge port anyways just gonna send it back to amazon to have new one in couple days. Gotta love the return policy.
HaPe000 said:
I think that unlocking bootloader is bad idea. After that the warranty will be void...
Click to expand...
Click to collapse
Um thats just lame excuse from companies to force us to keep their crap on the devices we purchase. All my devices are rooted and unlocked and not one has died yet. After going through and disabling 2/3rds of crap on this tablet now I want that few hundred megabytes back in space. For as much crap I disabled I wouldn't be surprised im more close to 1gb back.
Moscow Desire said:
They'll get around to it. Heck, when I had to turn in my A701 to service center, they didn't even know it had been released Tried telling me it was a "leaked and illegal" tablet.
Good luck with the bootloader mate, but root after that should be pretty straight forward. (fingers crossed)
Click to expand...
Click to collapse
What a morons sometimes. Strange because I had the issue with the connection between dock and tablet where the connection between the 2 for a split moment was gone when adjusting the tilt angle, I got an immediate replacement. This problem I guarantee you we will see more often showing up here.
And what the rooting concerns: when the TWRP devs have their version for the 701 finished, it will be not that hard anymore. Just takes some time before that is done.
And for the flaming thing sorry, but I don't like to get hit by childish behavior when just reporting and next to that by a guy that is probably half my age and just comes looking in here (look @ date I joined xda lol)
Thanks for removing that post.
Snah001 said:
What a morons sometimes. Strange because I had the issue with the connection between dock and tablet where the connection between the 2 for a split moment was gone when adjusting the tilt angle, I got an immediate replacement. This problem I guarantee you we will see more often showing up here.
And what the rooting concerns: when the TWRP devs have their version for the 701 finished, it will be not that hard anymore. Just takes some time before that is done.
And for the flaming thing sorry, but I don't like to get hit by childish behavior when just reporting and next to that by a guy that is probably half my age and just comes looking in here (look @ date I joined xda lol)
Thanks for removing that post.
Click to expand...
Click to collapse
Hate returns. Took 3 months to get a refund. (welcome to Russia). Honestly, it was all due to rush jobs on CWM for the 510 and 700's. Bozos were in a rush to be the first, and used the "fstab's" from the wrong device. Bricked several tabs before I put a stop to it. Basically ruined the emmc memory. Mainboard replacements.
Well, I know folks are itchy to get things going. What starts as a joke, turns into flaming.
You folks always remember, takes 2 people for an argument. You all have the "Report Post" button on the toolbar. Please use it.
Honestly, I expect you folks to help each other out. Makes for a better forum.
Carry On!
MD
Snah001 said:
What a morons sometimes. Strange because I had the issue with the connection between dock and tablet where the connection between the 2 for a split moment was gone when adjusting the tilt angle, I got an immediate replacement. This problem I guarantee you we will see more often showing up here.
And what the rooting concerns: when the TWRP devs have their version for the 701 finished, it will be not that hard anymore. Just takes some time before that is done.
And for the flaming thing sorry, but I don't like to get hit by childish behavior when just reporting and next to that by a guy that is probably half my age and just comes looking in here (look @ date I joined xda lol)
Thanks for removing that post.
Click to expand...
Click to collapse
well next time you may want to think twice before asuming someone younger than you. guess i am to young to know where the movie that reference came from. i already have the boot.img altered and ready to try. also dont ask for it, havent tested it yet so going to have to wait till amazon gives me new one. it really isnt hard to alter, moscow already gave instructions.
Update Amazon has shipped my new tablet so may be here tomorrow (i hope) if my new boot.img works and gives me root then I will pass it on, sadly though it won't be in a format in which you can just use a custom recovery, you have to flash it manually but if it works I will post how to flash it (all i need to remember is which tools to zip up in the entire SDK) LOL.
Interesting discussion..
Sent from my New Asus Transformer Pad TF701T using Tapatalk HD
Tiger62651 said:
Um thats just lame excuse from companies to force us to keep their crap on the devices we purchase. All my devices are rooted and unlocked and not one has died yet. After going through and disabling 2/3rds of crap on this tablet now I want that few hundred megabytes back in space. For as much crap I disabled I wouldn't be surprised im more close to 1gb back.
Click to expand...
Click to collapse
It is VERY lame. I sold my TF700 because of the slow I/O causing lag that I couldn't live with. Of course I had the bootloader unlocked, so the warranty was void. I divulged that info in the eBay auction for the most part (I didn't say the warranty was void because I didn't know that was the case. Ignorant, I know). Anyway, the new owner of my TF700 emailed me after a couple months asking me why ASUS was charging them $280 for fixing the faulty touchscreen. They said ASUS says it's not under warranty because of the unlocked bootloader. I felt bad for the new owners, having to fork out the money. They're $800 into the TF700 w/dock at this point.
So I would say: Think twice before unlocking the bootloader on the TF701, when custom-recovery even comes out for it.
Personally, with my TF701 that I ordered on newgg today, I am going to leave the bootloader locked for awhile. I can live with the stock ROM, hopefully with root access. Maybe after a few months I'll unlock the bootloader. It would be nice to do it in a way that didn't void the warranty. What an asinine policy by ASUS. There is no way the unlocked bootloader led to the touchscreen failing on my old TF700....no way!
snake2332 said:
It is VERY lame. I sold my TF700 because of the slow I/O causing lag that I couldn't live with. Of course I had the bootloader unlocked, so the warranty was void. I divulged that info in the eBay auction for the most part (I didn't say the warranty was void because I didn't know that was the case. Ignorant, I know). Anyway, the new owner of my TF700 emailed me after a couple months asking me why ASUS was charging them $280 for fixing the faulty touchscreen. They said ASUS says it's not under warranty because of the unlocked bootloader. I felt bad for the new owners, having to fork out the money. They're $800 into the TF700 w/dock at this point.
So I would say: Think twice before unlocking the bootloader on the TF701, when custom-recovery even comes out for it.
Personally, with my TF701 that I ordered on newgg today, I am going to leave the bootloader locked for awhile. I can live with the stock ROM, hopefully with root access. Maybe after a few months I'll unlock the bootloader. It would be nice to do it in a way that didn't void the warranty. What an asinine policy by ASUS. There is no way the unlocked bootloader led to the touchscreen failing on my old TF700....no way!
Click to expand...
Click to collapse
Gee thanks for the advice. Lets just say for practicality so you know when I got my Xoom 2 days later I rooted it. Couple years later works fine just slow now so time for new one. I have 701 right now and its blazing fast.
2nd let me shine some advise for you. For starters you can't "root" a device with a locked bootloader. Requires altering the boot.img to tell system to boot up differently and allow you access to the "restricted" file system. To access the flash portion of that requires you to open it up. One way or another you will have to unlock the bootloader to root the device. I myself just want root, I want to just remove the unwanted junk and free up that wasted space and install ad blocking software.
What each person chooses to do with the root is up to them, regardless if Asus wants to void the warranty or not. Just need little common sense and know how to use google to figure what you want to do. If your to cautious to do that then I highly suggest not touching it and leave it as is. To me its never a "think twice" once you root and have full access to the product you bought, it makes the device so much better to use and gets rid of unwanted bloatware. Especially the ad blocking apps which helps on phone contracts with capped data helps keep your data way down since ads use a lot of data.
Tiger62651 said:
2nd let me shine some advise for you. For starters you can't "root" a device with a locked bootloader. Requires altering the boot.img to tell system to boot up differently and allow you access to the "restricted" file system. To access the flash portion of that requires you to open it up. One way or another you will have to unlock the bootloader to root the device. I myself just want root, I want to just remove the unwanted junk and free up that wasted space and install ad blocking software.
Click to expand...
Click to collapse
Your statements sound completely wrong to me. Of course you can root without unlocking the bootloader. I have rooted two phones and my TF201, all without unlocking; I rooted the TF201 soon after buying it, and only unlocked the bootloader more than a year later.
Rooting doesn't force you to forfeit warranty service, but unlocking does. (Note that you can unroot a device before sending it in for service, but you can't "relock" an unlocked device.) So it makes perfect sense as Snake suggests to hold off on unlocking, at least until you are sure all the hardware in your device is working perfectly.
Tiger62651 said:
Update Amazon has shipped my new tablet so may be here tomorrow (i hope) if my new boot.img works and gives me root then I will pass it on, sadly though it won't be in a format in which you can just use a custom recovery, you have to flash it manually but if it works I will post how to flash it (all i need to remember is which tools to zip up in the entire SDK) LOL.
Click to expand...
Click to collapse
You can use a windows app called Virtuous Ten Studio (created by Diamondback ) Senior Mod and RD. It'll unpack your boot.img to allow editing ramdisk. Heck, it'll also de-odex, decompile apks with built in support for most API levels in a windows UI. No need to mess with apktools and such.
Free version in the XDA forums. Think you have to install latest MS .Net though. Can't remember. Give it a go. If you're a ROM cooker, it's a must.
An unlocked bootloader is usually 90% of the battle when getting full root (full means system RW access). Locked bootloaders is why rooting can involve finding exploits, which is why so many root apps are out there. Not saying what worked on the Acer 500/501, 510/511 and 700/701 tabs will work for the TF701, but it's worth investigating.
Moscow Desire said:
You can use a windows app called Virtuous Ten Studio (created by Diamondback ) Senior Mod and RD. It'll unpack your boot.img to allow editing ramdisk. Heck, it'll also de-odex, decompile apks with built in support for most API levels in a windows UI. No need to mess with apktools and such.
Free version in the XDA forums. Think you have to install latest MS .Net though. Can't remember. Give it a go. If you're a ROM cooker, it's a must.
An unlocked bootloader is usually 90% of the battle when getting full root (full means system RW access). Locked bootloaders is why rooting can involve finding exploits, which is why so many root apps are out there. Not saying what worked on the Acer 500/501, 510/511 and 700/701 tabs will work for the TF701, but it's worth investigating.
Click to expand...
Click to collapse
Thanks for the windows tip but I use VMware with Ubuntu installed and have my harddrive mapped as network drive to transfer files between. Much easier this way. I will check out the program though may need it for some APK altering of certain app (I hope).
Tiger62651 said:
Thanks for the windows tip but I use VMware with Ubuntu installed and have my harddrive mapped as network drive to transfer files between. Much easier this way. I will check out the program though may need it for some APK altering of certain app (I hope).
Click to expand...
Click to collapse
Ha, I use a dual boot (win7 and Ubuntu). Old lappy didn't run too well with VM. Need any help, shoot me a PM. Will share what I know.
There's a few other things you can do im Ramdisk, like increase read ahead cache, run a service to update lto.dat automatically (GPS) and a few others.
I only boot to win7 when I want to unpack/repack and boot images when I do kernel builds. (I'm lazy)
MD
Moscow Desire said:
Ha, I use a dual boot (win7 and Ubuntu). Old lappy didn't run too well with VM. Need any help, shoot me a PM. Will share what I know.
There's a few other things you can do im Ramdisk, like increase read ahead cache, run a service to update lto.dat automatically (GPS) and a few others.
I only boot to win7 when I want to unpack/repack and boot images when I do kernel builds. (I'm lazy)
MD
Click to expand...
Click to collapse
Yeah that works just pain to have to shut down windows to boot ubuntu. My PC is a power house, set VMware with 4gb of RAM and still not slowing my PC down LOL.
well new tablet in and little troubleshooting seems problem is bad charge cable, new one starts to charge 1/2 way in, other little flaky. but even new tablet fresh out of box wont let me unlock it so asus tw asked for screen shot of my ids, waiting reply.
So I dropped my Galaxy S4 and destroyed the display, rendering it useless. Then I ordered a Nexus 6 and its amazing! I love it. I had rooted my S4 successfully and I had some root apps running, which I came to love and now I'm having trouble to live without them.
I want to root my Nexus 6, but my mom won't let me. She says she wants to learn more about the risks.
I don't understand her reasoning because rooting a Samsung on Verizon is extremely tricky compared to a Nexus, and I was able to do that without any problems. From what I can tell the risk is very low for a Nexus, and it's hard to completely brick as long as you don't go flashing the wrong stuff and I probably won't go flashing anything fancy until there are some more ROMs for Marshmallow. And if I ever do physically break it, its really easy to go back to stock and make it like it was never even messed with. I've tried to tell her this but she won't listen.
If anyone has a minute, can someone confirm and possibly reinforce my statement? I'd love to root this baby in the next few days. Thanks!
zfrnz said:
So I dropped my Galaxy S4 and destroyed the display, rendering it useless. Then I ordered a Nexus 6 and its amazing! I love it. I had rooted my S4 successfully and I had some root apps running, which I came to love and now I'm having trouble to live without them.
I want to root my Nexus 6, but my mom won't let me. She says she wants to learn more about the risks.
I don't understand her reasoning because rooting a Samsung on Verizon is extremely tricky compared to a Nexus, and I was able to do that without any problems. From what I can tell the risk is very low for a Nexus, and it's hard to completely brick as long as you don't go flashing the wrong stuff and I probably won't go flashing anything fancy until there are some more ROMs for Marshmallow. And if I ever do physically break it, its really easy to go back to stock and make it like it was never even messed with. I've tried to tell her this but she won't listen.
If anyone has a minute, can someone confirm and possibly reinforce my statement? I'd love to root this baby in the next few days. Thanks!
Click to expand...
Click to collapse
Tell her that you won't use a phone with restrictions. Give the phone back. Be strong, don't complain. Just leave the phone alone.
zfrnz said:
So I dropped my Galaxy S4 and destroyed the display, rendering it useless. Then I ordered a Nexus 6 and its amazing! I love it. I had rooted my S4 successfully and I had some root apps running, which I came to love and now I'm having trouble to live without them.
I want to root my Nexus 6, but my mom won't let me. She says she wants to learn more about the risks.
I don't understand her reasoning because rooting a Samsung on Verizon is extremely tricky compared to a Nexus, and I was able to do that without any problems. From what I can tell the risk is very low for a Nexus, and it's hard to completely brick as long as you don't go flashing the wrong stuff and I probably won't go flashing anything fancy until there are some more ROMs for Marshmallow. And if I ever do physically break it, its really easy to go back to stock and make it like it was never even messed with. I've tried to tell her this but she won't listen.
If anyone has a minute, can someone confirm and possibly reinforce my statement? I'd love to root this baby in the next few days. Thanks!
Click to expand...
Click to collapse
Just tell her your grandma`s phone is rooted too
NLBeev said:
Tell her that you won't use a phone with restrictions. Give the phone back. Be strong, don't complain. Just leave the phone alone.
Click to expand...
Click to collapse
If I did that then she would get pissed and just take the phone away... Stock is better than no phone at all. If I give her some evidence then that would most likely do the trick. I've learned that if I go about things in smart ways and don't get angry, I get what I want more often. Thanks though
gee2012 said:
Just tell her your grandma`s phone is rooted too
Click to expand...
Click to collapse
Lol... My grandfather's phone actually is rooted. He's got sprint though and they're better when it comes to fixing rooting.
Your mother is just being cautious. Yeah, the chances of brick on nexus phones are slim, but that depends on how much you know about rooting and such; or how well you can follow instructions to the letter. And, like any other phone, Nexus' can be very expensive to fix if damaged too much (hard brick). Especially with the Marshmallow update, anything can go wrong. If you're confident in what you're doing, go for it. Otherwise, listen to your mother.
zfrnz said:
If I did that then she would get pissed and just take the phone away... Stock is better than no phone at all. If I give her some evidence then that would most likely do the trick. I've learned that if I go about things in smart ways and don't get angry, I get what I want more often. Thanks though
Click to expand...
Click to collapse
No, be consequent, the phone is yours or not. You can not change the idea that there risks. Because there is a risk.
You could change the strategy. The risk is not the rooting process. The risk is the person that roots the phone. Show/tell her that you know all the howto's. You must give the impression you are an expert.
toledodj said:
Your mother is just being cautious. Yeah, the chances of brick on nexus phones are slim, but that depends on how much you know about rooting and such; or how well you can follow instructions to the letter. And, like any other phone, Nexus' can be very expensive to fix if damaged too much (hard brick). Especially with the Marshmallow update, anything can go wrong. If you're confident in what you're doing, go for it. Otherwise, listen to your mother.
Click to expand...
Click to collapse
Yeah but compared to rooting an S4 a nexus is not risky at all... And wugfresh toolkit works on Marshmallow so that makes it even easier
zfrnz said:
Yeah but compared to rooting an S4 a nexus is not risky at all... And wugfresh toolkit works on Marshmallow so that makes it even easier
Click to expand...
Click to collapse
I didn't know the toolkit could now root Marshmallow. I could've sworn using it would brick the phone. If the root toolkit can do it, by all means go for it
toledodj said:
I didn't know the toolkit could now root Marshmallow. I could've sworn using it would brick the phone. If the root toolkit can do it, by all means go for it
Click to expand...
Click to collapse
This page has mixed answers... One guy said it worked but another got bootloop. But a boot loop is easy to get out of and that seems like the worst thing that happened
zfrnz said:
Yeah but compared to rooting an S4 a nexus is not risky at all... And wugfresh toolkit works on Marshmallow so that makes it even easier
Click to expand...
Click to collapse
Last remark. Arguments won't change the idea's of your mother. Tell her you should be very happy when your phone is rooted. Because of the customizing possibilities, like the use of layers.
Happiness is a state of mind and you will remember many many years later the fun of using a smartphone that was rooted. Thanks to your mother.
first off, it is EASY to brick a nexus, especially if you go the toolkit route. why? because when you use a toolkit you never learn how to do anything, like fixing your device, or how to actually root properly. that said, if you do decide to go that way, ill expect to see a thread titled.. "my mom was right about me bricking my n6".
zfrnz said:
This page has mixed answers... But a boot loop is easy to get out of and that seems like the worst thing that happened
Click to expand...
Click to collapse
Still a hassle though. Luckily, I've never heard of anyone hard-bricking a nexus
---------- Post added at 01:05 PM ---------- Previous post was at 01:00 PM ----------
simms22 said:
first off, it is EASY to brick a nexus, especially if you go the toolkit route. why? because when you use a toolkit you never learn how to do anything, like fixing your device, or how to actually root properly. that said, if you do decide to go that way, ill expect to see a thread titled.. "my mom was right about me bricking my n6".
Click to expand...
Click to collapse
In that case, it's always wise to learn both methods. From my experience, as long as you unlock the bootloader and enable USB debugging, the root kit is foolproof
It's possible her concern isn't about bricking but data security risks?
Sent from my P01MA using Tapatalk
toledodj said:
Still a hassle though. Luckily, I've never heard of anyone hard-bricking a nexus
---------- Post added at 01:05 PM ---------- Previous post was at 01:00 PM ----------
In that case, it's always wise to learn both methods. From my experience, as long as you unlock the bootloader and enable USB debugging, the root kit is foolproof
Click to expand...
Click to collapse
both methods? theres is only one right method, pressing a button isnt a method. but, once you learn the proper method, feel free to use a toolkit. the problem is that a lot of newbies use toolkits, then run into easily fixable problems that they cant solve.
and it appears that you dont read much, as very many have bricked their nexus. most common way recently is by running into a bootloop without having your bootloader unlocked nor the option to unlock it enabled. thats a 100% brick, and its happened to very many people.
Not that I'm condoning defying your mom's explicit wishes, but she's not even going to know if you root it. Better to ask forgiveness after than permission before...
If you learn to do everything manually and not use a toolkit then it is quite hard to brick a Nexus device. BUT, I've not rooted my last two (N5 and this N6) as there's no point these days.
Bricking will occur if you try and take a short cut or don't follow instructions.
simms22 said:
both methods? theres is only one right method, pressing a button isnt a method. but, once you learn the proper method, feel free to use a toolkit. the problem is that a lot of newbies use toolkits, then run into easily fixable problems that they cant solve.
and it appears that you dont read much, as very many have bricked their nexus. most common way recently is by running into a bootloop without having your bootloader unlocked nor the option to unlock it enabled. thats a 100% brick, and its happened to very many people.
Click to expand...
Click to collapse
I mentioned unlocking the bootloader and enabling USB debugging when using the root kit
toledodj said:
I mentioned unlocking the bootloader and enabling USB debugging when using the root kit
Click to expand...
Click to collapse
id even unlock my bootloader even if i never rooted.
simms22 said:
id even unlock my bootloader even if i never rooted.
Click to expand...
Click to collapse
Mine is always unlocked also
Hi okay um I have never owned an android, nor have i ever tried to root or unlock a bootloader. I have jailbroken an IPod so many times, SO many times. I want to cry because of how confused I am.
I followed this video: How to Unlock Bootloader on HTC Desire! Works on All HTC Devices (livingandroid)
I did perfectly, no hiccups
I then followed this video: The Easiest Way To Root Any Android Device Without A Computer (2017) (The Android Guy)
This is where i STARTED to mess up. My phone wouldnt go past the HTC screen (It would start up the metro opening screen but then go back to the htc screen)
So in my genius i thought (well dang why dont i just wipe everything and it'll be good "just like my iPod")
Guys i want to cry from how dumb i am. I've never posted here. I have never had an android much less messed with one. It tells me that if i reboot the system I will have no OS. That sounds extremely bad in my head. Is there anything i can do to somehow just fix this. Anything at all? Thank you so much for any help.
From
Someone that will never try anything ever again
Yeah, going through with that last part sounds like a pretty poor idea. I don't think you're totally screwed yet, though. Try finding the *RUU* for your version on the HTC website, paying close attention to the model and carrier. In theory, the RUU alone should reset your OS back to the factory state, but it apparently doesn't work 100% of the time. If it doesn't work, say something and I'll reply with new instructions.
Good luck out there, man.
Jake
P.S. I think all you had to do to root this thing is flash SuperSU. At any rate, there's a tutorial in this forum that makes it pretty easy; you shouldn't be able to do this again if you follow it. Check it out if you get the chance.
EDIT: This tool should be able to do everything you need after you fix your current issue: https://forum.xda-developers.com/devdb/project/dl/?id=17244