Related
Sorry if this might be a redundant post, but i assure you I searched a Lot (in XDA and web in general) for Viable Solve that Works and gets my Dell Tablet Finally Rooted?
BTW, while I am a newer member on XDA and by no means a developer, I am Not a Noob when it comes to these processes.
I've got experience rooting, as my G2x has been Rooted for months, running Hellfire Mod with no problems.....But my Tablet; a Dell Streak 7 is a whole other story.
I've tried Multiple times; different versions of S.O.C., reloading drivers (windows 7 devices & printers shows no yellow warning sign and when checking driver status within S.O.C. it shows No Issues), I've tried with Debugging On AND Off, Shut Down Anti-Virus, etc etc.
Here's a Screenshot (lil faded since the Not Responding Cursor was circling at the time) of what's going on;
Any Assistance Greatly Appreciated, THX!
loanusum said:
Any Assistance Greatly Appreciated, THX!
Click to expand...
Click to collapse
IF YOU ARE INCAPABLE OF DOING THIS WITHOUT THE USE OF FASTBOOT YOU DO NOT DESERVE ROOT!!!!
I don't know how many people have f***ed up their devices by using "one-clicks" so don't do it.
don't be lazy, get off your ass and do it properly, download a custom recovery boot into fastboot, use the command "fastboot flash recovery <insert name & directory to your CWM/TWRP.img here>"
FFS USE THE F***ING SEARCH FEAUTRE AS THIS METHOD OF ROOTING DEVICES IS ALWAYS THE SAME WITH DEVICES WITH UNLOCKED BOOTLOADERS
Deep breaths, Nocturnal_50, lol.
Nocturnal Needs some sleep i think........dude's definitely got some anger issues
loanusum said:
Sorry if this might be a redundant post, but i assure you I searched a Lot (in XDA and web in general) for Viable Solve that Works and gets my Dell Tablet Finally Rooted?
BTW, while I am a newer member on XDA and by no means a developer, I am Not a Noob when it comes to these processes.
I've got experience rooting, as my G2x has been Rooted for months, running Hellfire Mod with no problems.....But my Tablet; a Dell Streak 7 is a whole other story.
I've tried Multiple times; different versions of S.O.C., reloading drivers (windows 7 devices & printers shows no yellow warning sign and when checking driver status within S.O.C. it shows No Issues), I've tried with Debugging On AND Off, Shut Down Anti-Virus, etc etc.
Here's a Screenshot (lil faded since the Not Responding Cursor was circling at the time) of what's going on;
Any Assistance Greatly Appreciated, THX!
> Wow! Chill Nocturnal with the copy/paste same responses I've seen from u to other Noobs with what are to You, ridiculous and simply solved root issues being posted Asking Nicely for Help from those of us Less experienced? You're extremely quick to send angry mean replies Yet Never see a Solved response with your name.........hmmmmmm? As I said, I have a ROOTED G2x running HFS for 6 mos, and couldn't have done it without all the (other than you) folks who offer guidance here on xda! No Not Lazy...........i've searched and tried 3 Dozen ways to unsuccessfully root my ds7 over past 2 weeks, I'm Tired, Not lazy, Big difference! Tired of spending countless hours for weeks going in circles with Dead end threads with No Solves......using outdated 2011 old Pre-Honeycomb rooting du jour "try this it worked for me" replies. But hey, thanks so much for the kind reply and Help.....................that how you get off dude, lashing out out the idiot junior members?
Click to expand...
Click to collapse
Confused by the Contradictory reply given?
Nocturnal_50 said:
IF YOU ARE INCAPABLE OF DOING THIS WITHOUT THE USE OF FASTBOOT YOU DO NOT DESERVE ROOT!!!!
I don't know how many people have f***ed up their devices by using "one-clicks" so don't do it.
don't be lazy, get off your ass and do it properly, download a custom recovery boot into fastboot, use the command "fastboot flash recovery <insert name & directory to your CWM/TWRP.img here>"
FFS USE THE F***ING SEARCH FEAUTRE AS THIS METHOD OF ROOTING DEVICES IS ALWAYS THE SAME WITH DEVICES WITH UNLOCKED BOOTLOADERS
Click to expand...
Click to collapse
You first Scream that if I cannot root Without Fastboot I don't deserve root!?? Then do a 180 telling me "download custom recov and boot into Fastboot and flash from command prompt........which btw I've already tried that as well. Like I said, I'm Tired now. Maybe you're right and I don't deserve root on my DS7? At least my everyday Android ph has Root.............1 outta 2 ain't bad huh?
BTW - Just so u know Nocturnal, I haven't once F***ed up or soft bricked my DS7 during my attempts to root it. SOC just keeps locking up at step 7. Soooo I'd more recently been looking for Unabridged Guidance for custom recovery with flashboot. Again, very minimal help with CURRENT threads I've seen on this with one common denominator they All say; must Already be Rooted????? WTF?
loanusum said:
You first Scream that if I cannot root Without Fastboot I don't deserve root!?? Then do a 180 telling me "download custom recov and boot into Fastboot and flash from command prompt........which btw I've already tried that as well. Like I said, I'm Tired now. Maybe you're right and I don't deserve root on my DS7? At least my everyday Android ph has Root.............1 outta 2 ain't bad huh?
BTW - Just so u know Nocturnal, I haven't once F***ed up or soft bricked my DS7 during my attempts to root it. SOC just keeps locking up at step 7. Soooo I'd more recently been looking for Unabridged Guidance for custom recovery with flashboot. Again, very minimal help with CURRENT threads I've seen on this with one common denominator they All say; must Already be Rooted????? WTF?
Click to expand...
Click to collapse
Most if not all custom DS7 ROMs come rooted with Superuser7. Use Fastboot to install a custom recovery like CWM or TWRP. You can then install the Superuser7 zip file using that recovery.
Thanks for the tip.......
wptski said:
Most if not all custom DS7 ROMs come rooted with Superuser7. Use Fastboot to install a custom recovery like CWM or TWRP. You can then install the Superuser7 zip file using that recovery.
Click to expand...
Click to collapse
This is Very Helpful Info! I've been going round in circles for too many hours going down the rabbit holes that are some of these threads here on xda. You're the first person who's mentioned we can flash a Custom Rom to root? Instead of tearing into me like Nocturnal without any help just put-downs, you offer a short, concise and easy enough (or so it appears, I'll let ya know) answer, rather than the full pages of command prompts and a dozen steps to perform and having to pull drivers from other manufacturers etc. etc.
I've found that with these DS Tabs they can be very tempramental depending on froyo, GB, HC Not to mention if the PC is 64 or 32 bit creates it's own other set of unique challenges from all the threads I've read.......like I said, no one just offered help with a reply to simply flash a CUSTOM Mod recovery? I thought this entire time, I needed CWM first?? Others suggested flashing cwm via renaming to recovery.img, but if as I posted previously, that's a no go if the DS7 not already rooted - as my Streak when in recovery mode looks for Only for Update img or zip files and doesn't recognize the recovery.img file I did as told placing on root directory of device......
Flashing a Custom Rom (brain cramped on the fact they have SU files too, noob error! makes sense and I can't think of any reason it won't work..........thanks again
loanusum said:
This is Very Helpful Info! I've been going round in circles for too many hours going down the rabbit holes that are some of these threads here on xda. You're the first person who's mentioned we can flash a Custom Rom to root? Instead of tearing into me like Nocturnal without any help just put-downs, you offer a short, concise and easy enough (or so it appears, I'll let ya know) answer, rather than the full pages of command prompts and a dozen steps to perform and having to pull drivers from other manufacturers etc. etc.
I've found that with these DS Tabs they can be very tempramental depending on froyo, GB, HC Not to mention if the PC is 64 or 32 bit creates it's own other set of unique challenges from all the threads I've read.......like I said, no one just offered help with a reply to simply flash a CUSTOM Mod recovery? I thought this entire time, I needed CWM first?? Others suggested flashing cwm via renaming to recovery.img, but if as I posted previously, that's a no go if the DS7 not already rooted - as my Streak when in recovery mode looks for Only for Update img or zip files and doesn't recognize the recovery.img file I did as told placing on root directory of device......
Flashing a Custom Rom (brain cramped on the fact they have SU files too, noob error! makes sense and I can't think of any reason it won't work..........thanks again
Click to expand...
Click to collapse
Well, in order to root with Superuser7 on a stock DS7, you'd have install CWM and from there install the Superuser7.zip file. That's what I did, although my signature still shows that, I've moved on to other things.
If you really jacked your DS7 up, you might consider going back to Froyo using this NVflash: http://d-h.st/iXc then using the "stock" recovery to install an HC from this page: http://d-h.st/users/TheManii/?fld_id=1676#files. At that point install CWM from this page: http://d-h.st/users/TheManii/?fld_id=3717#files. Now Superuser from this page: http://d-h.st/users/TheManii/?fld_id=5593#files.
Don't ask why there are so many different versions of files there either! I wonder that myself as it makes for confusion.
First off, I wanna apologize if the has been discussed.
I see a lot of you broke your device by trying some form of method to fix the device in any fancy way.
I had a friend brick by trying the Cyanoboot method.
First off, assuming you have already got CWM installed via the tutorial that's been posted already.
Secondly, make sure you have some form of way to side load apps onto the device. Be it Dropbox, Google Drive, or maybe your using an ADB method.
Lastly, I have found this to be the easiest way.
So, let's begin. Please make sure you have a way of grabbing ROM Manager, back it up, download an .apk from a Google search or just port it from one device to another via an app.
Once you've found your method of getting the side loaded .apk let's make sure it's installed, any newer version will work(Older versions have been reported of not installing and allowing a proper clean reboot). So let's make sure it's a newer updated version, secondly test it and make sure the version you're using will reboot the device properly without issue. Working? Good.
Now let's use our nifty tool as soon as you have CWM installed, you should get a proper reboot!
This is good.
As a side note, I've had mine give issue and make me wait a few for a full reboot into CWM.
Now you're done!
Flashing ROMs.
It's just as easy as you'd think it'd be as long as you've got a properly packed ROM onto your device.
Note: If you're looking for a tut on porting the ROM, please check the Dev forum as there is a tut posted that is clean and simple using ADB.
Also, there are some that say you can using a cloud storage method.(Try it at your own risk!)
Once you've got your ROM onto Ouya you should check with an explorer to confirm that it was saved onto the device.(I have an issue of downloading things of the Internet with Ouya and them not showing up).
Now, using the method I first mentioned to get into CWM, do so.
You should see an option to search through your internal SD, this would be the next step as we can't/don't have any form of using an external SD, that is if you could connect a flash drive to the back and use it, though I can't confirm it would work.
Lastly, once you've scanned the internal SD and found your ROM, flash it. Sometimes this could take a bit, being my case it took 10m to install Ouya Plus.
If any issues occur, feel free to post and I shall try my best to answer anything!
Ouya-XD said:
First off, I wanna apologize if the has been discussed.
I see a lot of you broke your device by trying some form of method to fix the device in any fancy way.
I had a friend brick by trying the Cyanoboot method.
First off, assuming you have already got CWM installed via the tutorial that's been posted already.
Secondly, make sure you have some form of way to side load apps onto the device. Be it Dropbox, Google Drive, or maybe your using an ADB method.
Lastly, I have found this to be the easiest way.
So, let's begin. Please make sure you have a way of grabbing ROM Manager, back it up, download an .apk from a Google search or just port it from one device to another via an app.
Once you've found your method of getting the side loaded .apk let's make sure it's installed, any newer version will work(Older versions have been reported of not installing and allowing a proper clean reboot). So let's make sure it's a newer updated version, secondly test it and make sure the version you're using will reboot the device properly without issue. Working? Good.
Now let's use our nifty tool as soon as you have CWM installed, you should get a proper reboot!
This is good.
As a side note, I've had mine give issue and make me wait a few for a full reboot into CWM.
Now you're done!
Flashing ROMs.
It's just as easy as you'd think it'd be as long as you've got a properly packed ROM onto your device.
Note: If you're looking for a tut on porting the ROM, please check the Dev forum as there is a tut posted that is clean and simple using ADB.
Also, there are some that say you can using a cloud storage method.(Try it at your own risk!)
Once you've got your ROM onto Ouya you should check with an explorer to confirm that it was saved onto the device.(I have an issue of downloading things of the Internet with Ouya and them not showing up).
Now, using the method I first mentioned to get into CWM, do so.
You should see an option to search through your internal SD, this would be the next step as we can't/don't have any form of using an external SD, that is if you could connect a flash drive to the back and use it, though I can't confirm it would work.
Lastly, once you've scanned the internal SD and found your ROM, flash it. Sometimes this could take a bit, being my case it took 10m to install Ouya Plus.
If any issues occur, feel free to post and I shall try my best to answer anything!
Click to expand...
Click to collapse
just as an add: my Ouya did not detect a exFAT MicroSD in a USB reader. Maybe CWM only works with some formats?
glitchhawk said:
just as an add: my Ouya did not detect a exFAT MicroSD in a USB reader. Maybe CWM only works with some formats?
Click to expand...
Click to collapse
I do believe there's been a certain format to use, though I'm unaware on how this works.
Sent from my HTC One VX using xda app-developers app
glitchhawk said:
just as an add: my Ouya did not detect a exFAT MicroSD in a USB reader. Maybe CWM only works with some formats?
Click to expand...
Click to collapse
Ouya-XD said:
I do believe there's been a certain format to use, though I'm unaware on how this works.
Sent from my HTC One VX using xda app-developers app
Click to expand...
Click to collapse
FAT32 is more or less the "golden" standard for portable devices. glitchhaw, you are aware that exFAT is one of the most laughably locked down filesystems for portable devices out there, right? If you're being official at all, you have to pay royalties to Microsoft to be able to work with exFAT, and I doubt OUYA built support in for that.
Rirere said:
FAT32 is more or less the "golden" standard for portable devices. glitchhaw, you are aware that exFAT is one of the most laughably locked down filesystems for portable devices out there, right? If you're being official at all, you have to pay royalties to Microsoft to be able to work with exFAT, and I doubt OUYA built support in for that.
Click to expand...
Click to collapse
i know that I don't like exFAT and that its annoying and glitchy sometimes with android.. but I don't like the fat32 4gb limit.
i wish CWM/TWRP worked with NTFS or EXT, at least they are more reliable.
glitchhawk said:
i know that I don't like exFAT and that its annoying and glitchy sometimes with android.. but I don't like the fat32 4gb limit.
i wish CWM/TWRP worked with NTFS or EXT, at least they are more reliable.
Click to expand...
Click to collapse
NTFS support can be added at the kernel level, but I don't know of any recoveries that support it, sadly. And that's unfortunately the nature of the beast, and probably why many recoveries will break files up into multiple archives.
Go full *nix and use ext4 like a man... Unless you're a woman, then use it like a woman.
Sent from my SAMSUNG-SGH-I317 using xda premium
I am unable to get the unit to respond to Rom managers attempt at rebooting into recovery, I'll give the command via the app and it will just continue sitting there at the menu. CWM was successfully installed and I made a backup. I downloaded the app to my phone and then TB'd it and sent it to my device. did I miss something?
B4 I updated I needed SU to make the reeboot. Feature work.
Sent from my Amazon Kindle Fire using xda app-developers app
that was my thought, however I just reran the .bat for cwm and flashed that way.
Kickbut101 said:
I am unable to get the unit to respond to Rom managers attempt at rebooting into recovery, I'll give the command via the app and it will just continue sitting there at the menu. CWM was successfully installed and I made a backup. I downloaded the app to my phone and then TB'd it and sent it to my device. did I miss something?
Click to expand...
Click to collapse
I'd assume if it's not working that way then to try the ADB method instead, again, please report all issues to me.
Do you have CWM installed, on a final note?
People cry a out signatures, there's no need for one! I love my community and will stand up for it!
App: Quick Boot . reboot into fast boot, recovery, or shut down the console.
Sent from my SGH-M919G using xda app-developers app
Ouya-XD said:
First off, I wanna apologize if the has been discussed.
I see a lot of you broke your device by trying some form of method to fix the device in any fancy way.
I had a friend brick by trying the Cyanoboot method.
First off, assuming you have already got CWM installed via the tutorial that's been posted already.
Secondly, make sure you have some form of way to side load apps onto the device. Be it Dropbox, Google Drive, or maybe your using an ADB method.
Lastly, I have found this to be the easiest way.
So, let's begin. Please make sure you have a way of grabbing ROM Manager, back it up, download an .apk from a Google search or just port it from one device to another via an app.
Once you've found your method of getting the side loaded .apk let's make sure it's installed, any newer version will work(Older versions have been reported of not installing and allowing a proper clean reboot). So let's make sure it's a newer updated version, secondly test it and make sure the version you're using will reboot the device properly without issue. Working? Good.
Now let's use our nifty tool as soon as you have CWM installed, you should get a proper reboot!
This is good.
As a side note, I've had mine give issue and make me wait a few for a full reboot into CWM.
Now you're done!
Flashing ROMs.
It's just as easy as you'd think it'd be as long as you've got a properly packed ROM onto your device.
Note: If you're looking for a tut on porting the ROM, please check the Dev forum as there is a tut posted that is clean and simple using ADB.
Also, there are some that say you can using a cloud storage method.(Try it at your own risk!)
Once you've got your ROM onto Ouya you should check with an explorer to confirm that it was saved onto the device.(I have an issue of downloading things of the Internet with Ouya and them not showing up).
Now, using the method I first mentioned to get into CWM, do so.
You should see an option to search through your internal SD, this would be the next step as we can't/don't have any form of using an external SD, that is if you could connect a flash drive to the back and use it, though I can't confirm it would work.
Lastly, once you've scanned the internal SD and found your ROM, flash it. Sometimes this could take a bit, being my case it took 10m to install Ouya Plus.
If any issues occur, feel free to post and I shall try my best to answer anything!
If this was useful to you, I can only ask of a favor!
Check out my YouTube channel!
http://WWW.YouTube.com/user/TheDarkRosarySubscribe if you will! I will be covering everything Ouya and doing news soon!
Click to expand...
Click to collapse
I have to say this is probably the worst how to/tutorial I have seen on XDA.
If you're intent is to help users inexperienced with CWM, then you need to write clearly defined steps. The whole thing is vague. You don't give links to a single file or other tutorial, a how to shouldn't keep telling people to do a Google search for things. On four steps you make people search for files or another how-to.
What is the new version of Rom manager? How do you make sure it will reboot the device properly? Be specific.
You say flashing Roms is easy as long as you have a properly packed Rom. How does one go about checking that? How do you flash the Rom?
This is what a how-to is supposed to include. This is equivalent to just telling people GIYF and RTM.
Sent from my SCH-I535 using Tapatalk 4 Beta
TadeoNYC said:
I have to say this is probably the worst how to/tutorial I have seen on XDA.
If you're intent is to help users inexperienced with CWM, then you need to write clearly defined steps. The whole thing is vague. You don't give links to a single file or other tutorial, a how to shouldn't keep telling people to do a Google search for things. On four steps you make people search for files or another how-to.
What is the new version of Rom manager? How do you make sure it will reboot the device properly? Be specific.
You say flashing Roms is easy as long as you have a properly packed Rom. How does one go about checking that? How do you flash the Rom?
This is what a how-to is supposed to include. This is equivalent to just telling people GIYF and RTM.
Sent from my SCH-I535 using Tapatalk 4 Beta
Click to expand...
Click to collapse
There's no need to bash peoples thread first of all.
And secondly, you'll be reported for this.
As of how to to do this, I can't always "be specific" like you want when I post a good amount of this from my phone, so do be prepared for a tut that's not fully helpful.
Lastly, I HIGHLY doubt that you've read every tut on here, and trust me, I've seen so much worse that go down to the nick of; "If you wipe and install first, this version will fully brick the device, this version will half brick it".
So explain to me, since I've made ROM packages, I've had more tuts than just this, what do you wanna see more in a tutorial from me? Tell me and I'll try my best to help.
Don't go barging in with the intent of anger in mind and begin bashing me to the fullest.
Most people PM me and I give them what they need if they can't find it, as for you? Nuh uh, after this, NO is my final answer.
Sent from my HTC One VX using xda app-developers app
Oscar_david said:
App: Quick Boot . reboot into fast boot, recovery, or shut down the console.
Sent from my SGH-M919G using xda app-developers app
Click to expand...
Click to collapse
Thanks man, I'll make sure to add it to the OP.
Sent from my HTC One VX using xda app-developers app
Ouya-XD said:
There's no need to bash peoples thread first of all.
And secondly, you'll be reported for this.
As of how to to do this, I can't always "be specific" like you want when I post a good amount of this from my phone, so do be prepared for a tut that's not fully helpful.
Lastly, I HIGHLY doubt that you've read every tut on here, and trust me, I've seen so much worse that go down to the nick of; "If you wipe and install first, this version will fully brick the device, this version will half brick it".
So explain to me, since I've made ROM packages, I've had more tuts than just this, what do you wanna see more in a tutorial from me? Tell me and I'll try my best to help.
Don't go barging in with the intent of anger in mind and begin bashing me to the fullest.
Most people PM me and I give them what they need if they can't find it, as for you? Nuh uh, after this, NO is my final answer.
Sent from my HTC One VX using xda app-developers app
Click to expand...
Click to collapse
You reported me for what? That your feelings are hurt?
Ostensibly you created this tutorial to prevent people from bricking their OUYAs. That is why I was expecting a detailed walkthrough and was very disappointed. You created a tutorial on your phone that is lacking vital info that I have already detailed. I did not bash you to the fullest. You admit that your tut is not fully helpful, and I've seen other comments on another tut of yours that were a great deal harsher than mine about your motivation to post a poorly written tut.
I apologize for the severity of my opening line. I was and am annoyed that the "how-to" does not provide any info vital to users so that they don't brick their OUYA. Every time they are sent elsewhere for a file or info there is a risk of getting bad info or a malicious or corrupt apk. I outlined a lot of the information I think should be included. If I had all the answers I'd have included those as well, but I am here because I thought I could learn something. Maybe I still will.
Edit: I see now what type of person you are and how helpful you can be. http://forum.xda-developers.com/showthread.php?p=43031832 so the next time you see me ask for help go ahead and flame me. Don't worry I have a thick skin, so I won't feel the need to cry to the mods you hypocrite.
Sent from my GT-P3113 using Tapatalk 4 Beta
TadeoNYC said:
You reported me for what? That your feelings are hurt?
Ostensibly you created this tutorial to prevent people from bricking their OUYAs. That is why I was expecting a detailed walkthrough and was very disappointed. You created a tutorial on your phone that is lacking vital info that I have already detailed. I did not bash you to the fullest. You admit that your tut is not fully helpful, and I've seen other comments on another tut of yours that were a great deal harsher than mine about your motivation to post a poorly written tut.
I apologize for the severity of my opening line. I was and am annoyed that the "how-to" does not provide any info vital to users so that they don't brick their OUYA. Every time they are sent elsewhere for a file or info there is a risk of getting bad info or a malicious or corrupt apk. I outlined a lot of the information I think should be included. If I had all the answers I'd have included those as well, but I am here because I thought I could learn something. Maybe I still will.
Edit: I see now what type of person you are and how helpful you can be. http://forum.xda-developers.com/showthread.php?p=43031832 so the next time you see me ask for help go ahead and flame me. Don't worry I have a thick skin, so I won't feel the need to cry to the mods you hypocrite.
Sent from my GT-P3113 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Don't worry, this morning I was frustrated.
I'm sorry, tell me what you think I'm missing and I'll add the quote to the OP.
I plan on doing a video tut though.
Sent from my HTC One VX using xda app-developers app
worst
this is the worst tutorial I've ever read on xda. mods please take down this how to brick your ouya tutorial before people start downloading wrong files and bricking there ouya.
Okay where is your full proof method of rooting and installing cwm on the ouya?
Sent from my Vivid 4G using xda premium
Going by the threads opened/posts by this fellow, maybe a sticky to let people know who to avoid is needed.
OP, maybe your're over-enthusiastic over your new Ouya, but XDA prides itself on people who actually KNOW what they're doing to help, not rambling nonsense.
I have a nexus 6. The sound quality is horrible with headphones and the speakers. I unlocked the bootloader, rooted the nexus 6. A lot of the custom roms I have tried freeze during installation and soft brick the phone. The only rom that works is the stock rom.
alucke
That's a rather non-descript post. Who's your carrier, what Rom's are you talking about, any custom kernels, did you perform a wipe before installing? As far as the Audio goes, I've got no complaints from the speakers nor using headphones (both hardwired and BT headphones). You do realize that the first boot after installing a fresh Rom can take several minutes, some as long as 8 minutes while everything is set in place. More info so that we can help, please.
alucke said:
I have a nexus 6. The sound quality is horrible with headphones and the speakers. I unlocked the bootloader, rooted the nexus 6. A lot of the custom roms I have tried freeze during installation and soft brick the phone. The only rom that works is the stock rom.
alucke
Click to expand...
Click to collapse
lol your doing something wrong.
i have flashed most of the available roms, in total hundreds of times, never failed to boot, not even once.
i know i say this often, but ill say it again(even if im wrong this time).. i bet you used used a toolkit to root your device. too bad that you learn absolutely nothing from a toolkit. what you should do is put your phone down, and not touch it until you do some serious research into your device. how you do things properly, what can you flash, etc. these are things that you have to do before you ever root your device.
Is this a rant or are you asking for help? This is a development forum, so not really the place to rant. If you want help, please ask specific questions whilst supplying relevant information
Need education
simms22 said:
i know i say this often, but ill say it again(even if im wrong this time).. i bet you used used a toolkit to root your device. too bad that you learn absolutely nothing from a toolkit. what you should do is put your phone down, and not touch it until you do some serious research into your device. how you do things properly, what can you flash, etc. these are things that you have to do before you ever root your device.
Click to expand...
Click to collapse
You are correct. Where do I go for help and advice upon this phone OS? I am willing to learn but know of no courses or clubs to join. I am taking lessons online at the Google developers site. This is a start but slow go. As an update, my soft bricked Nexus6 is back in order. I some how managed to use the Root Tool Kit and "pushed" the factory to the phone. I assume this restored my ABD and debug thereby establishing USB connection between PC and phone. I then wiped Cache, system and Dvalick. and loaded Cyanogen Mod 12.1 and Gapps. For a while there I lost debug and was never able to open the phone and enable it.
Still,I would like to know the alternate way such as sideload ABD and commands, Fastboot, Bootloader, etc.. Thank you.
---------- Post added 21st September 2015 at 12:09 AM ---------- Previous post was 20th September 2015 at 11:59 PM ----------
simms22 said:
i know i say this often, but ill say it again(even if im wrong this time).. i bet you used used a toolkit to root your device. too bad that you learn absolutely nothing from a toolkit. what you should do is put your phone down, and not touch it until you do some serious research into your device. how you do things properly, what can you flash, etc. these are things that you have to do before you ever root your device.
Click to expand...
Click to collapse
You are correct. Where do I go for help and advice upon this Android phone OS? I am willing to learn but know of no courses or clubs to join. I am taking lessons online by self at the Google developers site. This is a start but slow go. As an update, my soft bricked Nexus 6 is back in order. I some how managed to use the Root Tool Kit v2.0.4 and "pushed" the factory, I downloaded from Google, to the phone. I assume this restored my ABD allowing debug thereby establishing USB connection between PC and Nexus 6, I then wiped Cache, system and Dvalick. and loaded Cyanogen Mod 12.1 and Gapps. For a while there I lost debug and was never able to open the Nexus 6 bootloader or Fastboot.
Still,I would like to know the alternate way such as sideload ABD and commands, Fastboot, Bootloader, etc.. Thank you.
This is the most idiotic post I've seen here all day. Seriously sell your nexus 6 and go buy a different phone if you don't like the phone or face the fact that you either don't know how to use a nexus device or you have a defective phone. But I'm almost entirely convinced this is 100% user error
Sent from my Nexus 6 using XDA Free mobile app
ray6279 said:
You are correct. Where do I go for help and advice upon this phone OS? I am willing to learn but know of no courses or clubs to join. I am taking lessons online at the Google developers site. This is a start but slow go. As an update, my soft bricked Nexus6 is back in order. I some how managed to use the Root Tool Kit and "pushed" the factory to the phone. I assume this restored my ABD and debug thereby establishing USB connection between PC and phone. I then wiped Cache, system and Dvalick. and loaded Cyanogen Mod 12.1 and Gapps. For a while there I lost debug and was never able to open the phone and enable it.
Still,I would like to know the alternate way such as sideload ABD and commands, Fastboot, Bootloader, etc.. Thank you.
Click to expand...
Click to collapse
here is a good place to start
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot-how-help-t3006500
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
good luck!
Android documentation is kinda lacking
Its not terrible... Its just not entirely coherent, well organized or complete. A lot of poking around and learn by doing, patching together threads that document how things work ect...
Here is my suggestion:
Follow the second link posted by simms22 above, this one here: http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot-how-help-t3006500
Go here: https://developers.google.com/android/nexus/images?hl=en
And download the latest image for your phone (shamu, the images at the bottom of the list are most recent. All carriers currently use same build, unless your on tmobile or Fi)
Use some kind of unzipping program (not sure if winrar can do .tgz, if not just google "Windows .tgz") to decompress the image you download. This will have a few .img files in it and a .zip Unzip the .zip for the rest of the partition images for the phone.
With these you can use fastboot to re-format partition to stock.
Here is an older guide, while devices may vary a little... and things have changed since 2011, were still mostly talking about system, boot, recovery, data....
http://www.addictivetips.com/mobile...plained-boot-system-recovery-data-cache-misc/
I would say read through the above guides thoroughly, then manually update your phone to stock.
You will notice the stock flash-all script will
Code:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.10.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-shamu-d4.0-9625-02.101.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-shamu-lmy48m.zip
You probably don't want to do all this... You will notice the last command I showed is fastboot -w update image-shamu-lmy48m.zip (assuming you downloaded the lmy48m image)
We already unzipped this, so rather then flash it in bulk (flashing userdata.img will wipe device) lets flash everything but leave data in place.
So get fastboot working, go to bootloader, and as the script does
With fastboot:
Flash the bootloader
then use fastboot to reboot, to the bootloader
flash the radio
then use fastboot to reboot to the bootloader
then fasboot flash system, recovery, boot and cache images, skipping userdata to avoid wiping the sd card.
At this point reboot. It may take a while for the first boot as android sets itself up and optimizing applications. If things appear to be hung give it 10 minutes before forcing a reboot checking your images and trying again. Pay attention to the output of the commands and make sure there are no errors. If there are read them, and google them.
Now you should be able to boot, and you will be fully stock. This is what it takes to recover from almost any situation. Often you can just flash system to update. Boot will overwrite your kernel, so it is often skipped when custom kernels are used... particularly when not encrypted.
Now find the website for twrp and find the image for your device, then go back to bootloader mode and flash recovery, after flashing reboot directly to recovery.
Also find chainfire's website with the recovery flashable supersu (should be a .zip)
Make sure the supersu install zip is on your phone, and the recovery is on your computer.
Reboot to bootloader and fastboot flash twrp to your recovery partition, then immediately reboot to recovery mode to finish the install.
In recovery make a backup of your working stock system.
After that install supersu
Reboot, and you should be stock and rooted with a backup of your completely stock system.
From here if your want to install a rom reboot to recovery, wipe caches, system and data. On future upgrades backup first, and try only wiping system and caches, then flash the new version of the rom and you wont have to set anything back up. You will have to reinstall xposed if your use it, as well as supersu if your rom does not include it for some reason.
If you do all that, read those guides to the point where you understand each step, and read the thread or at least the last hand full of pages of any rom or utility that you use... Things should work pretty good.
It so easy for some to assume user error, the phone might be a defective I know hate the layout of mine, and out of 13 android phones currently this d*m thing is the only one that freezes on me and will not show up in Linux (two versions) or windows 7 and it still stock. I have hated the phone from day two and tried very hard to use it stock for as long i could. I finally said screw it and went back to my old lg g flex till just died.. I wish i could sell this...but I am stuck trying to make it work. still cant even make it show up in any os and that makes it a bit hard to do anything (and yes my USB ports and drivers and cables are fine i have checked)
And likewise to this post , useless as well
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app
nevermind
simms22 said:
nevermind
Click to expand...
Click to collapse
:laugh: :laugh:
Was going to post, and had this thought also....
btw JJD loves his N6 and his speakers Rock!
#nuffsaid
Nexus 6 ftw!
disturb1 said:
It so easy for some to assume user error, the phone might be a defective I know hate the layout of mine, and out of 13 android phones currently this d*m thing is the only one that freezes on me and will not show up in Linux (two versions) or windows 7 and it still stock. I have hated the phone from day two and tried very hard to use it stock for as long i could. I finally said screw it and went back to my old lg g flex till just died.. I wish i could sell this...but I am stuck trying to make it work. still cant even make it show up in any os and that makes it a bit hard to do anything (and yes my USB ports and drivers and cables are fine i have checked)
Click to expand...
Click to collapse
It is user error.
SOME hardware is bad... But people like to view their phones as these temperamental beasts that "need to settle" and "all have their own intricacies"
Its a computer. Is this the way we look at laptops?
Two, or two hundred version of linux... Doesn't really matter because linux is a kernel and MTP implementation is handled separately. Not Nexus' fault that you didn't configure linux correctly, or that you expected someone else to do it for you for free, and they didn't do it either.
What file manager do you use, and did you have gvfs-mtp or kio-mtp installed?
What utilities were you using to mount the mtp drive?
These instructions are for arch linux, https://wiki.archlinux.org/index.php/MTP#simple-mtpfs (I use simple mtpfs), adapt them to your distro, find your distros documentation.
But then you don't really need it to show up in the OS? Does fastboot recognize it? Have you installed udev rules for it?
ok, thanks for all the input. I will give the nexus 6 a try again, root it. Can anyone point me to a custom rom that is somewhat close to stock?
I like Pure Nexus
scryan said:
It is user error.
SOME hardware is bad... But people like to view their phones as these temperamental beasts that "need to settle" and "all have their own intricacies"
Its a computer. Is this the way we look at laptops?
Two, or two hundred version of linux... Doesn't really matter because linux is a kernel and MTP implementation is handled separately. Not Nexus' fault that you didn't configure linux correctly, or that you expected someone else to do it for you for free, and they didn't do it
Click to expand...
Click to collapse
Not sure if I just have issues with lollipop or the hardware and lollipop
I have it rooted now and also still hate it I don't have the sound issues that some have but freezing was a constant with nexus T-Mobile stock ROM or maybe I have a lucky lemon ether way
I don't blame others or look to others to do my rooting rom installation or themes nor do I assume that it the phone every time all I am saying is we need to stop blaming every confused user as noob and assume people are not trying to learn
I been here 3 years but I lurk and learn and move on but I constantly see issues of flaming it is sad ...I see your reply and that fact that you offered help is what I like to see what I would offer if I knew an answer..
Honestly I am just not a fan of the phone but I made my bed and in it I must... hack at it till I am happy...
I want to root my Nexus 6 running stock android 6.0.0 but not sure exactly how to do it. Any help would be greatly appreciated. Thanks
dbzturtle said:
I want to root my Nexus 6 running stock android 6.0.0 but not sure exactly how to do it. Any help would be greatly appreciated. Thanks
Click to expand...
Click to collapse
Chainfire just released a new root for mm, http://www.xda-developers.com/chainfire-releases-root-for-android-6-0-without-modifying-system/
Sent from my Nexus 6 using Tapatalk
blueyes said:
Chainfire just released a new root for mm, http://www.xda-developers.com/chainfire-releases-root-for-android-6-0-without-modifying-system/
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
It says that it's experimental and will likely have bugs. is there a stable way to root? If not I don't mind waiting until there is.
dbzturtle said:
It says that it's experimental and will likely have bugs. is there a stable way to root? If not I don't mind waiting until there is.
Click to expand...
Click to collapse
Fastboot flash twrp, and then flash 2.52superuser.sip in recovery. Look up wugfresh Nexus root toolkit, it'll explain the process.
Sent from my Nexus 6 using Tapatalk
I rooted my N6 on Android 6.0 with 2.52 weeks ago and it's absolutely fine - I've seen no problems at all. The "experimental" mention is a disclaimer to cover Chainfire in case you have problems - a very sensible warning in my opinion, but in this case you can probably ignore it.
And I agree with blueyes - Nexus Root Toolkit is pretty much idiot-proof as long as you read the instructions and in particular choose the correct ROM.
dahawthorne said:
I rooted my N6 on Android 6.0 with 2.52 weeks ago and it's absolutely fine - I've seen no problems at all. The "experimental" mention is a disclaimer to cover Chainfire in case you have problems - a very sensible warning in my opinion, but in this case you can probably ignore it.
And I agree with blueyes - Nexus Root Toolkit is pretty much idiot-proof as long as you read the instructions and in particular choose the correct ROM.
Click to expand...
Click to collapse
The problem with using toolkits when they are "idiot-proof" is that if you go into the process as an idiot, you leave the process still an idiot, so if something goes wrong with the device at a later date, the user has not got the skills to fix it, which becomes a problem on these forums as rather than telling someone how to fix it, we also have to teach the skills that should already have been learned.
Toolkits are great if you know what they're doing but if you dont, use fastboot the first time to get an understanding of it and also to ensure you know it is working on your computer correctly. It's easier to troubleshoot PC configurations when the device is fully working rather than waiting until it is "broken"
"you leave the process still an idiot"
I'll take that in the spirit I think you meant it...
Sure, point taken, but the problem with telling someone to start learning to use tools they don't understand is that this forum ends up with a flood of "I've bricked my device" posts. I agree that the manual way is useful for resolving problems, and I don't use NRT for everything - I'd say maybe 50% of the time for installing a brand new factory ROM, and the rest of the time using ADB/Fastboot for stuff I (think I) understand.
I just think that if someone has taken the time and trouble to give me the commands typed perfectly in the correct order and proven to work, why would I risk typing them in maybe in the wrong order or accidentally installing an image into the wrong partition? My own stupid fault, sure, but why take the long way round instead of the simple straight proven path?
Just sayin'...
dahawthorne said:
"you leave the process still an idiot"
I'll take that in the spirit I think you meant it...
Sure, point taken, but the problem with telling someone to start learning to use tools they don't understand is that this forum ends up with a flood of "I've bricked my device" posts. I agree that the manual way is useful for resolving problems, and I don't use NRT for everything - I'd say maybe 50% of the time for installing a brand new factory ROM, and the rest of the time using ADB/Fastboot for stuff I (think I) understand.
I just think that if someone has taken the time and trouble to give me the commands typed perfectly in the correct order and proven to work, why would I risk typing them in maybe in the wrong order or accidentally installing an image into the wrong partition? My own stupid fault, sure, but why take the long way round instead of the simple straight proven path?
Just sayin'...
Click to expand...
Click to collapse
It's not really the long way round. Once everything is installed, its as quick if not quicker. And as I said, you need all this installed for ongoing maintenance anyway so may as well do this whilst your device is working.
You can't brick your device by flashing to the wrong partition so there are no floods of posts from people doing things manually at all. .if you flash to the wrong partition,.just flash to the right partition. It's not rocket science either. If you flash a radio, flash it to the radio partition. If you flash system, flash it to the system partition. ...and if you type something wrong, it won't do anything at all.
Fastboot is well documented (by me and others) in the general forum. People should feel free to nude toolkits once they have learned it, but noobs should definitely learn it and use it the first time for the reasons I have already mentioned.
To root is so simple.
1. In fastboot, use
"fastboot oem unlock"
2. In fastboot, flash a custom twrp recovery image
"fastboot flash recovery twrp.img "
3. If marshamallow, flash a custom boot.img to allow it to be rooted
"fastboot flash boot boot.img"
4. Copy SuperSU to sdcard
5. Flash SuperSU zip from recovery
Once these steps have been carried out, you've used fastboot, know how it works and also have proof your computer has working fastboot. That ticks essential boxes.that every root user needs to have ticked. Once they're ticked, use toolkits to your hearts desire.
The worst thing about noobs using toolkits is when we need them to use fastboot when helping with their issues, they don't know what it is and we have to teach them that. We also need to troubleshoot setting it up which can be extremely hard if their device is bricked or in a state of needing repair. 10 minutes learning now can help prevent hours of wasting our time later. Surely it's only being courteous to learn these things ?
Where can I find a custom boot image ? I'm asking because I'm rooted but every time I try to go into recovery it ask me for a password
getmoneygreen said:
Where can I find a custom boot image ? I'm asking because I'm rooted but every time I try to go into recovery it ask me for a password
Click to expand...
Click to collapse
If you're encrypted, recovery will always ask you for a password. If you've set a password in android, you use that..if you have not set a password in android, you use the default twrp password.
I am an Android Noob! My first Android devices were the Nexus Player and the Nexus 6. (I came from iPhones and Apple TV) It did not take me long at all to learn how to use fastboot and adb. I manually flashed my Nexus 6 and Nexus Player to 6.0 before the OTAs were rolling out no problem. I have root on both of my devices.
My point is, if I can learn how to do this in a matter of a day (I have not had my Nexus 6 a full month yet) You can learn how to do it as well. There are tons of guides out there on how to do all of this. Google is your friend. You will feel awesome and have a sense of accomplishment if you take the time to learn this stuff. It is easy to learn, not hard at all! I come from a pretty extensive tech background so I was a step ahead, but anyone can do / learn this stuff.
There are toolkits that can do this stuff for you pretty much. I have not downloaded or used one myself. I don't trust someone else's code with my device. That's just me though. I like to feel in control when I flash stuff.
@danarama
"Surely it's only being courteous to learn these things ?"
I know that it's all too easy to be taken wrong when writing a post, so I'll say up front that I'm serious - thanks for posting those steps. I've watched the NRT run through its steps a number of times and it clearly does a lot more than this, which is why i'm glad that it's doing the typing for me
I have used your steps when flashing various things, I've just never used them for a ROM upgrade - except once when I was trying to recover a broken-radio N5 and was installing Chroma.
One value at least of the NRT for noobs is its help in setting up your PC's drivers - that alone is a good reason to look at it.
Just for interest, what would happen if I flashed recovery into the radio partition? Or the boot partition?
Seriously, thanks for these steps - I appreciate it.
dahawthorne said:
@danarama
"Surely it's only being courteous to learn these things ?"
I know that it's all too easy to be taken wrong when writing a post, so I'll say up front that I'm serious - thanks for posting those steps. I've watched the NRT run through its steps a number of times and it clearly does a lot more than this, which is why i'm glad that it's doing the typing for me
I have used your steps when flashing various things, I've just never used them for a ROM upgrade - except once when I was trying to recover a broken-radio N5 and was installing Chroma.
One value at least of the NRT for noobs is its help in setting up your PC's drivers - that alone is a good reason to look at it.
Just for interest, what would happen if I flashed recovery into the radio partition? Or the boot partition?
Seriously, thanks for these steps - I appreciate it.
Click to expand...
Click to collapse
Radio may boot but won't connect to a network.
Boot is the kernel so it won't boot without it (bootloop)
Both can be fixed by flashing the correct image to the correct partition.
The images in the factory image are appropriately labelled too, so it would be difficult to flash to the wrong partition without realizing it was wrong.. Eg
"fastboot flash radio boot.img" looks wrong when you have radio.img too.
Thanks, danarama. I suppose that's the point I was trying to make at the top - that if you're a bit of a thicko then you could flash to the wrong partition, which a predefined script won't. As long as it's recoverable, no problem, but I remember the pumping heart and breathlessness as I watched my devices on several occasions sitting with the boot animation for 10-15 minutes and thinking "What the hell do I do now?"
I know I'm hijacking this thread (sorry...) but is there anything you can think of that would definitely hard-brick my device if I'm being thick or careless? I've never managed it, and maybe as Android progresses it's becoming harder to hard-brick, but is there ever a time when I need to think "There's no way back from this one"?
danarama said:
If you're encrypted, recovery will always ask you for a password. If you've set a password in android, you use that..if you have not set a password in android, you use the default twrp password.
Click to expand...
Click to collapse
Thank for the heads up really appreciate that. BTW what is the default password for twrp
getmoneygreen said:
Thank for the heads up really appreciate that. BTW what is the default password for twrp
Click to expand...
Click to collapse
Not sure, Im not encrypted. But its documented somewhere by twrp dev. Maybe on their site or in their thread
Hi all
I'll try and make this as clear as possible as I'm a bit of a noob with all of this. I've been wanting to learn about custom roms etc for a while and I've been searching for a cheap device.
I've found a cheap nexus 6 for £30, but there are some issues I am wondering if I can work around.
Previous owner had a custom rom on it, but failed to make a backup of it before wiping for selling.
The USB port on the phone doesn't work so wireless charging is my only option for power which is fine because that's what I use every day.
The device currently only boots int TWRP, but as the USB isnt working I need to know if there is any other way to get roms onto the device.
I apologise if it's a stupid question but I am still learning about this.
Many thanks!
I don't think you can install anything without either a working USB or a rom file already on the phone.
Some people have been able to replace the USB, but I guess it isn't easy, because it is soldered to the main board.
KhaosEmerald said:
I apologise if it's a stupid question but I am still learning about this.
Many thanks!
Click to expand...
Click to collapse
There are no stupid questions, except for ones that aren't asked. Unfortunately, unless you have the USB port repaired you won't be able to do much.
Strephon Alkhalikoi said:
There are no stupid questions, except for ones that aren't asked. Unfortunately, unless you have the USB port repaired you won't be able to do much.
Click to expand...
Click to collapse
Thank you, I figured as much, and I can't find anywhere local still repairing nexus 6s so I'm gonna hunt for something else thanks for the input!
You might have done this but make sure you boot to twrp and then click on install then select storage and see if the rom file was not erased during the wipe. Probably is not there but worth a try if you haven't done that.