Related
hi guys, im stuck...
well not exactly- i have unlocked the bootloader on my nexus one on FRF91.
but what bout after that? i found some links on XDA and it says to superboot? cant do it i keep getting error and most of the tutorials are on windows OS, i use a mac, i would really appreaciate it if anyone can assist me any further with commands on terminal for mac.
i'm a newbie so i really dont know what to do, i've spend almost 8 hrs on this and only got bootloader unlocked.
thanx for your help guys
Why would you play around with a $580 phone if you don't know what your doing, they had a post showing you how to root without unlocking your bootloader. The other thing is you have to explain exactly what you did, and what stock rom you came from and where your trying to go. I'm not familiar with Mac systems but there should have been instructions for that system to. I'm going to check it out for you and see if I can help.
Sent from my Nexus One using XDA App
http://forum.xda-developers.com/showthread.php?t=636795
Do step IV.
Pick a ROM you like from the list in Developers section, download it.
Do step VI.
Not really hard.
blas4me said:
Why would you play around with a $580 phone if you don't know what your doing, they had a post showing you how to root without unlocking your bootloader. The other thing is you have to explain exactly what you did, and what stock rom you came from and where your trying to go. I'm not familiar with Mac systems but there should have been instructions for that system to. I'm going to check it out for you and see if I can help.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I have unlocked the bootloader- theres a unlock logo on boot screen, but then I know I need to do superboot n then flash recovery image!!
That's the part that I tried to do but can't do.. I have all the files,but commands don't seem to work.
I've been trying for almost 12 hrs.
n I'm on stock frf91 which I did OTA for
Let me know if there's anything you can do thnx
Check this video
Kartikp84 said:
I have unlocked the bootloader- theres a unlock logo on boot screen, but then I know I need to do superboot n then flash recovery image!!
That's the part that I tried to do but can't do.. I have all the files,but commands don't seem to work.
I've been trying for almost 12 hrs.
n I'm on stock frf91 which I did OTA for
Let me know if there's anything you can do thnx
Click to expand...
Click to collapse
This site helped me out alot when I first learned, because they have instructions accompanied with video, so it's like you can't go wrong. Sometime the dudes who have just instructions leave out a step and that can f things up for us. When I rooted my N1, the guy who posted the instructions put a period in the wrong place, and it almost had me stuck, but I knew the recovery image and I knew It did'nt belong there. Anyway check this vid, and let me know what happens, start from the beginning even though your boot loader is unlocked.
http://theunlockr.com/2010/01/02/how-to-root-the-nexus-one/
Here's another video with instructions for Mac.
http://www.droiddog.com/android-blog/2010/02/video-tutorial-hack-your-nexus-one/
There are links to files for each step, and the only suggestion I would make is maybe look for the newer 1.7.0.1 Amon Ra recovery image and to not use the Sense ROM that he links to. The recovery image is here on this forum in the Android Development section. I don't use it since I'm still having no issues with the 1.7.0 version that this guy links to in the guide.
As far as ROMs are concerned, I highly recommend going with either CyanogenMod 5.0.8 Stable (because it has fewer issues and is a good place for a noob to start) or with one of the more stable Froyo roms, like Kang-O-Rama .9.
Just a quick question. How would one update from 5.0.1 to 5.1 if they are on stock rooted rom with a few tweaks such as volume mod, hotspot enabled, and show percentage mod? I guess I am more worried about erasing everything and then re-installing.
Thanks
stas333 said:
Just a quick question. How would one update from 5.0.1 to 5.1 if they are on stock rooted rom with a few tweaks such as volume mod, hotspot enabled, and show percentage mod? I guess I am more worried about erasing everything and then re-installing.
Thanks
Click to expand...
Click to collapse
Flash the stock system.img to remove root. If you are unencrypted, flash the stock boot.img. And if you have TWRP, flash the stock recovery.img.
This is if you want to take the OTA. Or you can wait until someone makes a flashable zip.
Instructions are here, under Method 2 (only flash those files I noted above. No need to flash all of them.) > http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
cam30era said:
Flash the stock system.img to remove root. If you are unencrypted, flash the stock boot.img. And if you have TWRP, flash the stock recovery.img.
This is if you want to take the OTA. Or you can wait until someone makes a flashable zip.
Instructions are here, under Method 2 > http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Click to expand...
Click to collapse
Thanks
cam30era said:
Flash the stock system.img to remove root. If you are unencrypted, flash the stock boot.img. And if you have TWRP, flash the stock recovery.img.
This is if you want to take the OTA. Or you can wait until someone makes a flashable zip.
Instructions are here, under Method 2 > http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Click to expand...
Click to collapse
Just to correct what may be an error here...
If you are unencrypted and flash the stock boot.img, you will be encrypted on boot. So if you are unencrypted and wish to remain so, it would make sense to flash immediately whatever custom kernel you use to not force encryption.
But IMHO this is pretty much the best way as stated.
Flash system.img, boot.img and radio.img via fastboot individually, flash root (SuperSU) from recovery and boot. No wipes etc.
If you're going to follow method 2, you might as well just do it straight with the 5.1 image and call it good.
So just going from stock rooted 5.0.1 to stock rooted 5.1 is the factory reset needed? I know in the past it wouldn't have been, but lollipop changed a lot with this stuff so I'm not sure.
Can't we simply sideload the update using Wugfresh or something and re-root? I have taken OTAs on my OnePlus One and all it does is remove root. I don't understand why I'd have to completely reinstall and wipe just to take an OTA.
greyhulk said:
Can't we simply sideload the update using Wugfresh or something and re-root? I have taken OTAs on my OnePlus One and all it does is remove root. I don't understand why I'd have to completely reinstall and wipe just to take an OTA.
Click to expand...
Click to collapse
You cannot sideload an OTA on lollipop if you have modified anything in system, including adding root. We also discourage using toolkits for those who do not understand how to do the steps without one, because when those people get stuck and need help, we cant simply help and give instructions.. We have to teach them EVERYTHING they didn't bother to learn first - which is a result of using toolkits as shortcuts instead of as aids to existing knowledge
TriBeard said:
So just going from stock rooted 5.0.1 to stock rooted 5.1 is the factory reset needed? I know in the past it wouldn't have been, but lollipop changed a lot with this stuff so I'm not sure.
Click to expand...
Click to collapse
If you fastboot flash the stock system.img, you will be good to install the OTA, with no factory reset necessary. But EVERYTHING must be stock. Recovery, and encrypted kernel/boot.img.
---------- Post added at 01:19 PM ---------- Previous post was at 01:16 PM ----------
greyhulk said:
Can't we simply sideload the update using Wugfresh or something and re-root? I have taken OTAs on my OnePlus One and all it does is remove root. I don't understand why I'd have to completely reinstall and wipe just to take an OTA.
Click to expand...
Click to collapse
If your phone is back to 100% stock (everything, including recovery and encrypted kernel/boot.img), then you can ADB sideload the OTA. But be sure to do some research, so you know what you are doing.
Not to be rude to the veterans (I too know how to flash things manually) but you guys do realize the wug fresh toolkit does have an option to flash stock without wiping right?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
cam30era said:
If you fastboot flash the stock system.img, you will be good to install the OTA, with no factory reset necessary. But EVERYTHING must be stock. Recovery, and encrypted kernel/boot.img.
---------- Post added at 01:19 PM ---------- Previous post was at 01:16 PM ----------
If your phone is back to 100% stock (everything, including recovery and encrypted kernel/boot.img), then you can ADB sideload the OTA. But be sure to do some research, so you know what you are doing.
Click to expand...
Click to collapse
so basically you could flash the stock 5.0.1 system.img, take the update, then root again (assuming the root method doesn't change, or using a new method after one is found?)
TriBeard said:
so basically you could flash the stock 5.0.1 system.img, take the update, then root again (assuming the root method doesn't change, or using a new method after one is found?)
Click to expand...
Click to collapse
Yes, assuming you have stock recovery and are encrypted.
cam30era said:
Yes, assuming you have stock recovery and are encrypted.
Click to expand...
Click to collapse
Yeah, all I did was unlock the bootloader and run one of the automated rooting things, I think from chainfire, but I could be wrong. I didn't mess with unencryption or custom recoveries (yet).
Rooting is so easy. It requires one fastboot command after you're bootloader is unlocked(either to flash a recovery or boot into recovery temporarily) then you just use the SuperSU zip and boom you're rooted. That's why I love Nexus phones so much.
rootSU said:
You cannot sideload an OTA on lollipop if you have modified anything in system, including adding root. We also discourage using toolkits for those who do not understand how to do the steps without one, because when those people get stuck and need help, we cant simply help and give instructions.. We have to teach them EVERYTHING they didn't bother to learn first - which is a result of using toolkits as shortcuts instead of as aids to existing knowledge
Click to expand...
Click to collapse
Not trying to start and arguement but toolkits are here to help for people with busy lives. I know how to do both methods, but using a toolkit isnt all bad if directions are followed. Just about every device out there has some kind of toolkit similiarities.
nexus has its own toolkit, htc 1 m8 has a paid software that unlocks the device, heck even the newest moto E has a toolkit. Just because there are some developers on here that dont like toolkits doesnt mean they are bad. I agree though if people mess up bad and screwed up using a toolkit thats not the toolkits fault. Its user error. Toolkits are a good thing to use if used properly. I encourage everyone I know to use toolkits. I also make sure to tell them to read it twice then go.
---------- Post added at 02:59 PM ---------- Previous post was at 02:58 PM ----------
TriBeard said:
so basically you could flash the stock 5.0.1 system.img, take the update, then root again (assuming the root method doesn't change, or using a new method after one is found?)
Click to expand...
Click to collapse
what root method for nexus? all you have to do is flash custom recovery and then flash supersu within recovery and your good
the_rooter said:
Not trying to start and arguement but toolkits are here to help for people with busy lives. I know how to do both methods, but using a toolkit isnt all bad if directions are followed. Just about every device out there has some kind of toolkit similiarities.
nexus has its own toolkit, htc 1 m8 has a paid software that unlocks the device, heck even the newest moto E has a toolkit. Just because there are some developers on here that dont like toolkits doesnt mean they are bad. I agree though if people mess up bad and screwed up using a toolkit thats not the toolkits fault. Its user error. Toolkits are a good thing to use if used properly. I encourage everyone I know to use toolkits. I also make sure to tell them to read it twice then go.
---------- Post added at 02:59 PM ---------- Previous post was at 02:58 PM ----------
what root method for nexus? all you have to do is flash custom recovery and then flash supersu within recovery and your good
Click to expand...
Click to collapse
Like i said, its fine if you know both methods.
I don't care if someone has a busy life or not. If they don't have time to spend 10 minutes reading and following my fastboot thread, well they shouldn't really be rooting. Further more, how selfish is it for someone who thinks they're too busy to learn the basics to then have to fall back on other people who may also have busy lives for hand holding through something that should be simple just because they wanted to take a small shortcut to save them 3 minutes? Learn the basics and then you don't waste our time trying to not only help you but also teach the basics - which are essentials.
My point isn't that toolkits break things (although sometimes they do) or even user error using the toolkit... My point is if something else unrelated goes wrong and we say "fastboot flash x to fix" and they then reply " what's fastboot?" And then we have to teach the basics whilst they're frustrated and panicking. That is NOT the best time to learn... Or teach
Driving a car requires a licence. Sure, you can fake a licence but I don't want to have to explain what a car is if you need me to tell you how to start the car. Especially not whilst you're late for a job interview
rootSU said:
Like i said, its fine if you know both methods.
I don't care if someone has a busy life or not. If they don't have time to spend 10 minutes reading and following my fastboot thread, well they shouldn't really be rooting. Further more, how selfish is it for someone who thinks they're too busy to learn the basics to then have to fall back on other people who may also have busy lives for hand holding through something that should be simple just because they wanted to take a small shortcut to save them 3 minutes? Learn the basics and then you don't waste our time trying to not only help you but also teach the basics - which are essentials.
My point isn't that toolkits break things (although sometimes they do) or even user error using the toolkit... My point is if something else unrelated goes wrong and we say "fastboot flash x to fix" and they then reply " what's fastboot?" And then we have to teach the basics whilst they're frustrated and panicking. That is NOT the best time to learn... Or teach
Driving a car requires a licence. Sure, you can fake a licence but I don't want to have to explain what a car is if you need me to tell you how to start the car. Especially not whilst you're late for a job interview
Click to expand...
Click to collapse
So your saying if no one uses your fastboot method thread that they are in the wrong. I understand and agree that all users should learn fastboot, but to push your thread on everyone and then to say they shouldnt root at all if they dont is selfish. Theres always more than one method to do a task. Just because one is easier than the other doesn't make it bad.
best example and this still irks me is I knew a developer that had a thread for the ruu on the m8. he found out if you flash it twice(the same file) that it will clean install, and since it was "easier" other developers told him to take it down because its taking away people from using their method. Again i am not saying your in the wrong, but at the same time there is always more than one method, and like myself if I mess up(which i have) before I ask anything I get on here and search and search. I never ask because if ever there is a mistake done its usually the users fault. I have used toolkits for years, and still knowing how to do fastboot i prefer toolkits and never had any issues because I read the directions the minimum of 2 times. This is XDA there is always more than one way to do something. We need to support @WugFresh and his work he has done. Again dont take this to heart I am not bashing you in anyway. All I am saying is we all have options and any member on here should know that if u make a mistake which we all have at one point. We Search first (number one rule on XDA). The answers are always here in XDA. Youtube to an extent also has google back up videos on how to do stuff to. I follow @Tomsgt aka root junky on youtube, and google plus. He does these things.
the_rooter said:
So your saying if no one uses your fastboot method thread that they are in the wrong. I understand and agree that all users should learn fastboot, but to push your thread on everyone
Click to expand...
Click to collapse
You know that's not what I meant. My fastboot thread / any fastboot thread - its not relevant. I know mine describes everything a user needs to know and its succinct so it doesn't take long g to read. Its an example!
Basically learn fastboot. I'm not pushing anything on anyone except morals. Don't be selfish and we'll all get along. Don't and well, people will be less inclined to help.
the_rooter said:
Theres always more than one method to do a task. Just because one is easier than the other doesn't make it bad.
Click to expand...
Click to collapse
You're still completely missing the point. I didn't say toolkits are bad. I said lack of knowledge is bad.
And actually on a nexus, a toolkit isn't really easier at all.
I don't really want to get into a drawn out discussion about this.. I hope you understand where I'm coming from. Use toolkits if you know both methods, but if you don't, go the (ever-so-slightly) longer way the first time so that you're not a drain on our time and helpfulness later on in life, because you didn't learn the basic essentials when you needed to.
TriBeard said:
so basically you could flash the stock 5.0.1 system.img, take the update, then root again (assuming the root method doesn't change, or using a new method after one is found?)
Click to expand...
Click to collapse
instead of going back to stock and then flashing OTA, why not just flash the new system.img directly?
I was big in to rooting and custom roms for both my Epic 4g Touch (s2) and my M7. I just never got in to it with my M8, and this is my first nexus device, so it's been a while, and the process is a little new/different for me. I've used toolkits in the past, but also had to adb/fastboot my way back in to a working rom at times as well. I just used a script to root the nexus 6, and so I didn't use fastboot. I knew it was simple for nexus devices usually, but didn't know specifics.
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
Okay. so after hours of searching and reading about unbricking my nexus 6. I am lost, and very desperate.
So, I unlocked my bootloader, and rooted my phone today using chainfire cf auto root. and all went well. The primary reason I did this was to edit the build.prop file to enable wifi tethering, and this is where my problems started. Using root explorer I added
HTML:
net.tethering.noprovisioning=true
to the end of the build.prop file. I rebooted and now I'm stuck in a bootloop on the google screen.
I did not have a custom recovery installed, so flashing a new rom isn't that easy. I have looked into flashing twrp or cwm from the stock recovery adb sideload feature, but I haven't gotten this figured out either.
So that brings me to where I am at now. I still have an unlocked bootloader, which I guess is leaving me some options, but I just don't know where to go to find information which isn't going to further muck this situation up.
Help, please. I don't have a backup phone. And I am getting desperate.
Thanks in advance
Reboot to the bootloader, flash stock system.img
Sent from my Nexus 6 using Tapatalk
very first off.. http://forum.xda-developers.com/nexus-6/general/attention-questions-t3228454
meaning, you wont get help if tou do ont post it in the right place.
secondly, you have two choices, flash twrp then flash a rom, or flash the factory image(just system.img). what your pro lem is tgat you used a toolkit, instead of learning thd very easy proper way. now you dont know how to do things. its rwally easy to flash twrp via fastboot, and its very easy to flash a factory image using fastboot as well. now ill ask a mod to move your thread into the correct area..
thanks
simms22 said:
very first off.. http://forum.xda-developers.com/nexus-6/general/attention-questions-t3228454
meaning, you wont get help if tou do ont post it in the right place.
secondly, you have two choices, flash twrp then flash a rom, or flash the factory image(just system.img). what your pro lem is tgat you used a toolkit, instead of learning thd very easy proper way. now you dont know how to do things. its rwally easy to flash twrp via fastboot, and its very easy to flash a factory image using fastboot as well. now ill ask a mod to move your thread into the correct area..
Click to expand...
Click to collapse
I am mainly a reader here and don't normally post as I can figure things out on my own normally. So, sorry for posting in the wrong forum.
Help is appreciated..
Thanks.
acscot2 said:
I am mainly a reader here and don't normally post as I can figure things out on my own normally. So, sorry for posting in the wrong forum.
Help is appreciated..
Thanks.
Click to expand...
Click to collapse
i just saw, it was your first post. i didnt mean to sound rude, for that im sorry.
but you have your answer(s). your phone isnt bricked, its just without os. and the os can be flashed, even using a toolkit.
What happened to the recovery partition?
Before posting your reply, just to be clear, I do not need a guide on rooting my device or flashing a recovery. This has already been done! So please don't spam links at me for things I can find with a 5 minute search on google because I have don't this already <3
lukemovement1 said:
Not long go the pixel 5 and its been a while since I've played with flashing device partitions. Can anyone give me some pointers on the below?
Is the recovery now the boot partition and the boot partition boot_a?
Is their a way of rooting lineage os without having to modify the boot.img? (idk about amazon)
Do I need to re-root with magisk after each update?
Click to expand...
Click to collapse
Unfortunately you might have asked this in the wrong forum, thus no replies. Look here in Guides https://forum.xda-developers.com/t/guide-root-pixel-5-android-11-r.4187609/
What on earth makes you think I need a guide to rooting my device?
Made the question a bit simpler to avoid confusion
lukemovement1 said:
What on earth makes you think I need a guide to rooting my device?
Made the question a bit simpler to avoid confusion
Click to expand...
Click to collapse
You did originally ask about rooting so I thought I'd help out a little. What I don't understand is your animosity towards an attempt at posting a possible helpful link. Maybe a simple.. let me clarify my request since it might not have been clear. Oh well good luck.
lukemovement1 said:
What happened to the recovery partition?
Before posting your reply, just to be clear, I do not need a guide on rooting my device or flashing a recovery. This has already been done! So please don't spam links at me for things I can find with a 5 minute search on google because I have don't this already <3
Click to expand...
Click to collapse
Hmmmm, your edit removed the actual question and I don't remember exactly what it was.
xunholyx said:
Hmmmm, your edit removed the actual question and I don't remember exactly what it was.
Click to expand...
Click to collapse
Fastboot says that the recovery doesn't exists?
lukemovement1 said:
Fastboot says that the recovery doesn't exists?
Click to expand...
Click to collapse
I'm not sure what you mean.
fastboot reboot recovery won't work. It never has afaik
fastboot boot *twrp.img name* should work if you are trying the test build of TWRP
adb reboot recovery always works
You can't boot to recovery from bootloader with fastboot commands, but you can boot to it with adb commands while booted to /system
lukemovement1 said:
What happened to the recovery partition?
Before posting your reply, just to be clear, I do not need a guide on rooting my device or flashing a recovery. This has already been done! So please don't spam links at me for things I can find with a 5 minute search on google because I have don't this already <3
Click to expand...
Click to collapse
I'm guessing, as there's really not enough information to know for sure, but is this possibly a google treble question?
prior to treble, yes->recovery partition
with treble->no recovery partition, but another 'slot' for recovery.
cheers
Recovery and boot have merged into one partition, (on a/b devices at least) and you ship your boot and reco partitions in a unified boot image now which you can flash with fastboot flash boot x.img.
lukemovement1 said:
What on earth makes you think I need a guide to rooting my device?
Made the question a bit simpler to avoid confusion
Click to expand...
Click to collapse
Ay, Ay, Ay,,,
To be fair, he was only trying to help, a simple this isn't helpful goes a long way. Being sour though, gets everyone absolutely nowhere.
And you did ask "Is their a way of rooting lineage os without having to modify the boot.img" -- I believe he was guiding you to that thread to possibly ask there as you may get a faster response. I think the question was just taken incorrectly is simply all. No harm, no foul.
bobby janow said:
You did originally ask about rooting so I thought I'd help out a little. What I don't understand is your animosity towards an attempt at posting a possible helpful link. Maybe a simple.. let me clarify my request since it might not have been clear. Oh well good luck.
Click to expand...
Click to collapse
You make more friends with lemonade, or something like that, you were trying to help, so good job in my eyes.
xunholyx said:
Hmmmm, your edit removed the actual question and I don't remember exactly what it was.
Click to expand...
Click to collapse
I'll help.
"Is their a way of rooting lineage os without having to modify the boot.img"
xunholyx said:
I'm not sure what you mean.
fastboot reboot recovery won't work. It never has afaik
fastboot boot *twrp.img name* should work if you are trying the test build of TWRP
adb reboot recovery always works
You can't boot to recovery from bootloader with fastboot commands, but you can boot to it with adb commands while booted to /system
Click to expand...
Click to collapse
I believe he was propbly doing a list of the partition table, and I haven't looked myself, but recovry is missing and instead of doing some research into this, he was simply asking for a simple answer, I feel this is the point of the Q & A forum, so good job to OP.. Personaly I feel this needed a simple answer, as someone coming from like a htc one m8 or htc 10 (like myself) what the hell happened to recovery.img -- a fair question in my eyes, everyone.
AsItLies said:
I'm guessing, as there's really not enough information to know for sure, but is this possibly a google treble question?
prior to treble, yes->recovery partition
with treble->no recovery partition, but another 'slot' for recovery.
cheers
Click to expand...
Click to collapse
Appreciate the info, thank you.
fadedave said:
Recovery and boot have merged into one partition, (on a/b devices at least) and you ship your boot and reco partitions in a unified boot image now which you can flash with fastboot flash boot x.img.
Click to expand...
Click to collapse
Thank you!
Guys, this is how it should work. This is the point of the Q&A thread, ask a question, get an answer, no need for anyone to get upset or to be sour. A question was asked, an answer was kindly given.
Kinda lost all faith in this forum tbh. Loads of incorrect and missing info, asking a question is a battle and half the ROMs and images don't work
lukemovement1 said:
asking a question is a battle
Click to expand...
Click to collapse
That's because you're making it a battle. As mentioned above, you were partly to blame for the initial misunderstanding. If people don't fully understand your question, instead of being upright rude, maybe rephrase or add more clarification as @andybones said.
lukemovement1 said:
half the ROMs and images don't work
Click to expand...
Click to collapse
There are 3 roms in this forum for Pixel 5. They all work and all are regularly updated. You are complaining about the time, sweat and money that developers put in to bring custom roms to us for free. If you don't like something about it, post a feedback or don't use it rather than be disrespectful.
lukemovement1 said:
Kinda lost all faith in this forum tbh. Loads of incorrect and missing info
Click to expand...
Click to collapse
Then leave, or contribute to providing the correct and missing info, rather than, again, complain about free info people bring together in their spare time. None of us here are paid to bring info and provide code. We all do it in our spare time and share our knowledge because we want to make a positive community.
Your total disrespect, negativity and entitlement is not welcome here.
Touché
If you post was removed, it's because I decided to do some house-cleaning -- no one did anything wrong.
And I fixed the title to the thread, so that it's easier on those seeing it and understand what the "simple question" actually is.
Not sure why people get all salty over a simple question...
There is no /recovery partition on Pixel devices. Recovery coresides with the kernel in /boot. Previously, with Android 10, it was possible to install a custom recovery alongside a rooted kernel (such as using Magisk) but Android 11 broke this.
The best and most foolproof option in my opinion is to only temporarily boot a custom recovery to perform modifications. This is what I do every time I get an update on my Pixel 5 - I download the OTA, boot TWRP, install the OTA, reboot to system, let the update finish, boot TWRP again, and flash Magisk.
lukemovement1 said:
What happened to the recovery partition?
Before posting your reply, just to be clear, I do not need a guide on rooting my device or flashing a recovery. This has already been done! So please don't spam links at me for things I can find with a 5 minute search on google because I have don't this already <3
Click to expand...
Click to collapse
agree , the people don't want to help,