Related
Hi,
I own a Captivate on Rogers (Canada).
I had the ROM Firefly 2.6 (or 2.4) and decided to change to something quicker or at least different.
I decided to put Cyanogen 7 on it, because many people told me to.
I succeeded in installing Cyanogen and it worked great, easy to use, fast, ultra fast reboot, nice looking... but not all the software I was looking for.
So I decided to change again to a JVQ SIMPLY.
Put it on the SD, move it to sdcard via Astro under Cyanogen and reboot in recovery mode to install update from sdcard.
It wrote that it was ok, and needed to reboot.
Now the only thing I have is "booting" from
- the very first screen with Galaxy S I9000 on it to
- a second one with Galaxy S Cyanogen(mod)
I can access the screen with the little android guy in the public works sign, yellow, with Downloading... and Do not turn off Target!!! (did it trying hard reset).
I couldn't reboot with 3 buttons (tested many methods), the one with Odin, I never ever succeeded with that one, and it continues changing from a screen to another without stopping but if I remove the battery of course.
What can I do from there?
Thank you for your help... again...
Just for clarification, did you do the Odin One-Click to stock? If you can get to the download screen (the yellow sign / "Do not turn off target" screen), you should be able to flash back to stock.
I tried the Odin 1-click, but I think that it won't work right now because I can't access the administrator rights (from work).
I must try from home tonight.
Will it remove everything like the fact it is root?
Thank you for your answer by the way.
The lack of admin rights is very possibly why it won't work. There's also the chance that without admin rights, you're not able to install the samsung drivers. Either way, waiting until you get home sounds like a good idea.
You might be able to do the Heimdall one-click without admin rights, but it would probably be wise to read up on that one first as it's in Beta right now.
The one-click to stock will put your phone in the state it came out of the box, but leave all your personal files on the phone. You will have Eclair 2.1, unrooted, straight as it came from (in your case) Rogers. Any pictures, music, etc you saved on your internal sd card (not the microSD) will still be there, but you'll have to re-root and reinstall any rom you want.
Ok, so I tried different Odin (one click) I found here, and the last one, from here:
http://forum.xda-developers.com/showthread.php?t=1126704&highlight=odin
I flashed the PIT only, because I didnùt know what to put where... bad idea, now my phone doesn't switch on.
Soween said:
Ok, so I tried different Odin (one click) I found here, and the last one, from here:
http://forum.xda-developers.com/showthread.php?t=1126704&highlight=odin
I flashed the PIT only, because I didnùt know what to put where... bad idea, now my phone doesn't switch on.
Click to expand...
Click to collapse
Uh oh. Does your phone show any signs of life at all? Any lights come on, buzzers buzz, whistles whistle, etc?
No, nothing.
Soween said:
No, nothing.
Click to expand...
Click to collapse
Sorry to have to tell you this, but it looks like you might have fully bricked yourself.
If you are still under warranty, you can try to send it in for warranty service. If not, or if you aren't comfortable taking that route, look for a member named connexion2005 (or mobiletechvideos on google), who can do JTAG service for you for $50.
The JTAG thing is the special cable made from special resistor, right?
Or do you mean it is hard break and only expert can do something?
Thank you very much for your help and your support.
Soween said:
The JTAG thing is the special cable made from special resistor, right?
Or do you mean it is hard break and only expert can do something?
Thank you very much for your help and your support.
Click to expand...
Click to collapse
You're thinking of a Jig, which is a set of resistors that kicks the phone into download mode.
Unfortunately, you need JTAG, which is a special service that rewrites the bootloaders to the phone so that it can boot normally. That's something that you either need to be fairly knowledgeable about electronics to do yourself, or something you'll need to send in (to Samsung or mobiletechvideos) to have fixed.
Yeah I thought of a jig...
Ok, I will try the warranty, perhaps it is so much messed up, they won't find anything...
I will let you know.
See you.
Soween said:
Yeah I thought of a jig...
Ok, I will try the warranty, perhaps it is so much messed up, they won't find anything...
I will let you know.
See you.
Click to expand...
Click to collapse
Good luck - hopefully your next time around with custom Roms will go better.
I did many, many things with WInMo and never encountered any brick (sometimes I was close to the cliff, but never fell).
Since I have this Captivate, I not sure to really like it, I am fond of android either, and I don't take enough time to read carefully each post...
I think it is time for me to take an iphone...
Although you could do that, I think you'll find if you give yourself a little time with Android you'll come to really like it.
Don't get me wrong - the iPhone is a well made product. But it is one thing, and only one thing. Android devices can really be anything you want.
But that's my opnion. Do with it what you will.
People like you are gold, taking time to help newbie with the always same questions, don't selling android is the best (other are selling ios is the best), ...
I'll see what kind of hone I can find, because the Atrix was a cool phone I liked, and I always liked HTC (qtek before)...
Apple is expensive!!!
Soween said:
People like you are gold, taking time to help newbie with the always same questions, don't selling android is the best (other are selling ios is the best), ...
I'll see what kind of hone I can find, because the Atrix was a cool phone I liked, and I always liked HTC (qtek before)...
Apple is expensive!!!
Click to expand...
Click to collapse
Thank you. I'm just trying to repay the many favors everyone else here on the board has done for me in the past.
Definitely look around - if the Captivate isn't working for you, there's plenty of Android phones that are every bit as good. I've also had good luck with HTC phones in the past, and Motorola's not bad, either.
And yes, Apple is expensive. Can't argue with you on that one.
This might be stupid question but, is your battery charged ?
Hi,
aww.W.T.F, I hope so yes... it was on the usb for hours... you put me a doubt... I need to check now!!
I asked Rogers for warranty, they charge $35 for an exchange, and 5 days to wait, I think this is a little bit too much. But I will do it.
What I discussed with a guy is that I will finish my current subscription with Rogers and take the HTC Sensation with Virgin... Another try with android, to follow jmtheiss.
I will continue to let you know about how it goes.
If my profile is closed tonight, this will be because I will be too ashamed because I had an empty battery...
P.S. Ok it is not the battery... I'm waiting for my new one and will send this one to warranty (I'll see what they can find or not...).
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.
Hey, all. I recently purchased the HTC Desire 510 last Saturday, and so I've been trying to find a way to root it. Ya see, I don't own a computer, and there's no one readily able to lend me theirs. So, a one click would be awesome. But, to my chagrin, Framaroot isn't working. Does anyone know of a one click root app that would allow me to root this phone?
The stock experience has become kind of dull, I'm so used to having a high degree of customization on my phone, as I also own a Samsung Epic 4G Touch and a defunct Nexus 7.
Heh, I got my 510 on Saturday, too. You're not also in Chicago, are you?
I had the same problem with one click/apk roots on my 510, none worked. Towelroot worked great on my LG, but this is my first HTC and it appears you need a computer for the first step, unlocking the bootloader. I tried to do the manual bootloader method of going into the Windows command line to get the phone's token ID and blah blah blah, but that didn't work either as I kept running into the dreaded 'waiting for device' message.
So far the only way I've found that works for me was with this Windows program, which automates the HTC bootloader unlock process. You can root once you've done that, though I haven't gotten around to that part yet. I'm not allowed to post a link, it's called Kingo at kingoapp dot com.
Nah, man. I'm in Brooklyn NY ?
So the only way for me to root it would require a computer? Damn, I can't get access to one until further notice.
I'd have to unlock the bootloader, eh? Dang, so I'm stuck on stock KitKat, at least until this phone recieves the Lollipop update. Who knows how long THAT'S gonna take.
Thanks for the info, though, man. At least I can stop constantly checking Framaroot & Towelroot with my fingers crossed lol.
I'm pretty sure it requires a computer for the bootloader thing, but like I said, I've only been working with HTC as long as you have so I could be wrong.
So far I've been unable to get a working recovery image to flash, but I haven't done this before and I could be completely boning it. Some things I've read seem to imply that this may be because this is the first 64 bit Android phone, so we may have to just wait until something specific is made for it.
But damn, I really wish I could easily disable Sense and go back to vanilla, I hate all the flashy shiny ****.
I think I can help!
I have a HTC desire 510 too and also have no access to a computer. I have doing a lot of research on rooting over the last few days, because this stupid phone has no storage space at all. I kept running into road blocks everywhere like looked, until I found Know ok kingroot. I am still researching right now, so I haven't tried it yet, but I plan to tomorrow night. I just wanted to know everything there is to know about rooting before I don't it. I have my mind made up about it already and I am going to root my phone somehow
I hoped this helps you, after I try it tomorrow I'll post if it works or not. I don't know that I saw a list of HTC phones that Kingroot works on and the HTC desire 510 is on the list. As of if you try it before I get to after work tomorrow, please let me know. I am super excited for tomorrow night, good luck to you.
Your follow HTC desire 510 owner,
Little Debby Mc 28
lafinjack said:
Heh, I got my 510 on Saturday, too. You're not also in Chicago, are you?
I had the same problem with one click/apk roots on my 510, none worked. Towelroot worked great on my LG, but this is my first HTC and it appears you need a computer for the first step, unlocking the bootloader. I tried to do the manual bootloader method of going into the Windows command line to get the phone's token ID and blah blah blah, but that didn't work either as I kept running into the dreaded 'waiting for device' message.
So far the only way I've found that works for me was with this Windows program, which automates the HTC bootloader unlock process. You can root once you've done that, though I haven't gotten around to that part yet. I'm not allowed to post a link, it's called Kingo at kingoapp dot com.
Click to expand...
Click to collapse
littledebbymc28 said:
I have a HTC desire 510 too and also have no access to a computer. I have doing a lot of research on rooting over the last few days, because this stupid phone has no storage space at all. I kept running into road blocks everywhere like looked, until I found Know ok kingroot. I am still researching right now, so I haven't tried it yet, but I plan to tomorrow night. I just wanted to know everything there is to know about rooting before I don't it. I have my mind made up about it already and I am going to root my phone somehow
I hoped this helps you, after I try it tomorrow I'll post if it works or not. I don't know that I saw a list of HTC phones that Kingroot works on and the HTC desire 510 is on the list. As of if you try it before I get to after work tomorrow, please let me know. I am super excited for tomorrow night, good luck to you.
Your follow HTC desire 510 owner,
Little Debby Mc 28
Click to expand...
Click to collapse
You're gonna need a computer to unlock the bootloader first, there's no way around that.
You should probably read some more so you could learn like everybody else here... It's really not that complicated and the tutorials are pretty clear.
Sent from my HTC Desire 510 using Tapatalk
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
As an IT professional, I truly hate looking like an idiot. And I'm pretty sure that's about to happen. But I'm sincerely at the end of my rope, and don't know what else to do.
I've been using my Nexus 6 for over a year and a half now, and I love it. I'm comfortable using WugFresh and recently flashed the 7.1.1 OTA using it. However, I also like using Android Pay, so I don't want to root. I do however want full Google Now integration in Action Launcher 3, now that it's available. I really, really want that.
So I looked into Magisk, and that seems to be the way to go. The problem is that the installation instructions seem inherently contradictory. First, they say you need to revert to stock (does that mean stock 7.1.1 or stock after FDR, btw?). But in the very next step, they tell you to flash Magicsk using TWRP. Huh? How is a custom recovery like TWRP considered stock? I just don't get it.
Any assistance would be greatly appreciated. I'm trying my best here, so please don't flame. I used to be comfortable with rooting and ROMing back in the OG Droid days, but as I said, I enjoy Android Pay and my banking app, etc.
Thanks in advance for some clear, non-contradictory instructions.
unbesorgt said:
As an IT professional, I truly hate looking like an idiot. And I'm pretty sure that's about to happen. But I'm sincerely at the end of my rope, and don't know what else to do.
I've been using my Nexus 6 for over a year and a half now, and I love it. I'm comfortable using WugFresh and recently flashed the 7.1.1 OTA using it. However, I also like using Android Pay, so I don't want to root. I do however want full Google Now integration in Action Launcher 3, now that it's available. I really, really want that.
So I looked into Magisk, and that seems to be the way to go. The problem is that the installation instructions seem inherently contradictory. First, they say you need to revert to stock (does that mean stock 7.1.1 or stock after FDR, btw?). But in the very next step, they tell you to flash Magicsk using TWRP. Huh? How is a custom recovery like TWRP considered stock? I just don't get it.
Any assistance would be greatly appreciated. I'm trying my best here, so please don't flame. I used to be comfortable with rooting and ROMing back in the OG Droid days, but as I said, I enjoy Android Pay and my banking app, etc.
Thanks in advance for some clear, non-contradictory instructions.
Click to expand...
Click to collapse
Well first let me give you some advise. If those apps are important to you then get used to running stock. Google is tighting the grip more and more and very soon you will have to choose. Either having root or using many apps like banking apps and google pay. Cant blame them really.
Now When they say stock then mean bare stock. Full factory wipe (formatting all partitions. Yes you will lose data) then put TWRP on there and go from there.
On a side not. You do yourself a great dis-service by using the tool kit. Make me wonder about the IT professional statement, no true IT person would let something reprogram their equipment without knowing everything that is going on as it happens.
zelendel said:
Well first let me give you some advise. If those apps are important to you then get used to running stock. Google is tighting the grip more and more and very soon you will have to choose. Either having root or using many apps like banking apps and google pay. Cant blame them really..
Click to expand...
Click to collapse
Kind of what I figured, and why I haven't rooted since my Droid Bionic.
zelendel said:
Now When they say stock then mean bare stock. Full factory wipe (formatting all partitions. Yes you will lose data) then put TWRP on there and go from there..
Click to expand...
Click to collapse
So in other words, the correct instructions should be:
1) Perform a Factory Data Reset
2) Flash TWRP
3) Flash Magisk using TWRP
zelendel said:
On a side not. You do yourself a great dis-service by using the tool kit. Make me wonder about the IT professional statement, no true IT person would let something reprogram their equipment without knowing everything that is going on as it happens.
Click to expand...
Click to collapse
So clearly you ignored my request not to flame. My IT job takes up enough of my time and mental resources that I have no problem using shortcuts like WugFresh as long as (a) I know how to do it manually if needed, and (b) I trust the utility. So tired of seeing this lazy insult. Not everyone has time to type out ADB commands all day long. But thanks for insinuating I'm not a "true IT person" because I prefer not to do so.
Now that I understand what is actually involved, I will just stay stock.
unbesorgt said:
Kind of what I figured, and why I haven't rooted since my Droid Bionic.
So in other words, the correct instructions should be:
1) Perform a Factory Data Reset
2) Flash TWRP
3) Flash Magisk using TWRP
So clearly you ignored my request not to flame. My IT job takes up enough of my time and mental resources that I have no problem using shortcuts like WugFresh as long as (a) I know how to do it manually if needed, and (b) I trust the utility. So tired of seeing this lazy insult. Not everyone has time to type out ADB commands all day long. But thanks for insinuating I'm not a "true IT person" because I prefer not to do so.
Now that I understand what is actually involved, I will just stay stock.
Click to expand...
Click to collapse
No need to do a factory reset. The installation instructions state you should restore your BOOT image to stock, nothing else. You can use a custom kernel though (I've been using Franco for some time) and there the recommendation is to flash it before Magisk.
So, in other words, skip step 1.
Edit: But of course, you'll need an unlocked bootloader and if you don't have that already your data will be wiped when unlocking. So... step 1 might be necessary... Oops.
unbesorgt said:
Kind of what I figured, and why I haven't rooted since my Droid Bionic.
So in other words, the correct instructions should be:
1) Perform a Factory Data Reset
2) Flash TWRP
3) Flash Magisk using TWRP
So clearly you ignored my request not to flame. My IT job takes up enough of my time and mental resources that I have no problem using shortcuts like WugFresh as long as (a) I know how to do it manually if needed, and (b) I trust the utility. So tired of seeing this lazy insult. Not everyone has time to type out ADB commands all day long. But thanks for insinuating I'm not a "true IT person" because I prefer not to do so.
Now that I understand what is actually involved, I will just stay stock.
Click to expand...
Click to collapse
And see that is where you not wanting to put the time in is starting to bite you. doing a facotry reset isnt really a full clean wipe. You have to format the partitions.
If you dont have the time then you really shouldnt be doing something that could easily leave you with a bricked device and with no one to blame but yourself as you didnt want to take the time to understand what you are doing.
As to what I said. It wasnt flaming it was simple blunt honesty. I know people are not used to that as everyone tries so hard to be PC and not hurt other peoples feelings. Well that is not how things work here. Here you will get honest answers. Might not be answers you like but that is not really something to worry about.
I wasnt insinuating anything. I cant tell you that most the older members of this site are in IT and have been for longer then smartphones have been around. The yare also the ones that tell people not to use them for the simple matter of not knowing how to fix things if something went wrong or even what went wrong at all.
zelendel said:
Well first let me give you some advise. If those apps are important to you then get used to running stock. Google is tighting the grip more and more and very soon you will have to choose. Either having root or using many apps like banking apps and google pay. Cant blame them really.
Click to expand...
Click to collapse
Yes, sadly I think you are right about this. I have decided to remain stock 7.1.1. The thing I will never understand is why Google chose to make Google Now launcher integration dependent upon the launcher being a system app? I can already have that feature if I use the Google Now launcher which is part of the stock image, but for various aesthetic reasons I just can't stand it. I get that they want to sell Pixels, but honestly I can't stand the Pixel launcher either, due to the ugly icons, so even if I shelled out the price of a desktop computer for a phone that lacks wireless charging, stereo speakers, and water resistance, I still would be stuck not being able to have Google Now integration with my preferred Action Launcher 3. Why? Google's entire business model is based on people using their search engine and seeing their ads, so why on earth wouldn't they want as many people as possible to use Google Now? Plus I can already access it in multiple different ways, they just all suck because it doesn't stay resident in RAM, causing stuttering and delays. If they would just remove that stupid restriction then people like me wouldn't feel the need to root at all, thereby compromising the security of the device which is so important to them, and it would be a win-win all around. Google used to be smarter than this ... what the hell happened? /rant
Thank you Didgeridoohan for your polite and helpful reply. It is truly appreciated. Glad to know there are still kind people to be found on XDA.
My willingness to use ADB commands vs. a root toolkit had absolutely nothing to do with my question. But some people just can't resist any opportunity to display their smug superiority.
unbesorgt said:
Thank you Didgeridoohan for your polite and helpful reply. It is truly appreciated. Glad to know there are still kind people to be found on XDA.
My willingness to use ADB commands vs. a root toolkit had absolutely nothing to do with my question. But some people just can't resist any opportunity to display their smug superiority.
Click to expand...
Click to collapse
He wasn't flaming... Take 2 minutes to learn ADB and fastboot commands and don't rely on some gimmick toolkit. and it will go a long way. For an "it professional" or even anyone relatively familiar with computers this won't be a hard task. If you're messing with your phone you NEED to know how to do this. Don't cry foul when someone points this out.