Related
I tried using the search but I get NOTHING relating to how to root a Nexus One, so if someone has the link can you please paste it here? Trust me I wouldn't bother posting this but the forum search is pissing me off.
Try the sticky thread at the top of this forum?
http://forum.xda-developers.com/showthread.php?t=636795
I followed this to the letter the first time through, very straight-forward and easy to follow.
This is either a troll, or a bad attempt at sarcasm
Either way, I'm sure the mods won't like it.
Thread moved to Q&A.
Paul22000 said:
This is either a troll, or a bad attempt at sarcasm
Either way, I'm sure the mods won't like it.
Click to expand...
Click to collapse
Or else a standard iPhone user who doesn't know how to do anything without Apple's iRon iCurtain.
codesplice said:
Try the sticky thread at the top of this forum?
http://forum.xda-developers.com/showthread.php?t=636795
I followed this to the letter the first time through, very straight-forward and easy to follow.
Click to expand...
Click to collapse
****, do I need to go back to 2.1 to root then? Or am I good to do rooting straight from 2.2?
aniteshj said:
****, do I need to go back to 2.1 to root then? Or am I good to do rooting straight from 2.2?
Click to expand...
Click to collapse
The basic steps are the same. Flash the recovery image as instructed in that guide, and then flash a pre-rooted kernel like this one: http://forum.xda-developers.com/showthread.php?t=686627
That's gonna be the easiest method for you I think.
codesplice said:
The basic steps are the same. Flash the recovery image as instructed in that guide, and then flash a pre-rooted kernel like this one: http://forum.xda-developers.com/showthread.php?t=686627
That's gonna be the easiest method for you I think.
Click to expand...
Click to collapse
Hmm I did it the way I remembered with the oem unlock, recovery image flash, then the addon zip and it seems to have worked fine. Bootloader is unlocked and I am rooted, still running Froyo, but now am missing my keyboard...
Ah screw it I'm going to go with the FRF50 and see if that pans out and if not there is always a CM'd 2.1 to fall back to.
Try it with the kernel I linked to? It's optimized for FroYo.
codesplice said:
Try it with the kernel I linked to? It's optimized for FroYo.
Click to expand...
Click to collapse
Alright if the FRF50 doesn't install or work properly I'll go with a stock 2.2 and try that.
I love how easy it is to **** up this phone and yet fix it so easily.
aniteshj said:
Alright if the FRF50 doesn't install or work properly I'll go with a stock 2.2 and try that.
I love how easy it is to **** up this phone and yet fix it so easily.
Click to expand...
Click to collapse
And that, right there, is one of my favorite things about this platform. You're free to break the rules and try new things. When something doesn't work, you're not stuck - you can find a way to fix it or work your way around it. I love it
codesplice said:
And that, right there, is one of my favorite things about this platform. You're free to break the rules and try new things. When something doesn't work, you're not stuck - you can find a way to fix it or work your way around it. I love it
Click to expand...
Click to collapse
Yup couldn't agree more and 99% of the time all it takes is a wipe of everything and start over, and I love that I can do that. Like I screwed up the root and the OS was booting into landscape mode, for everything. Thank god the files downloaded fast and its back to normal!
By the way, with the root on 2.2, all the applications and what not should still work right? Like marketenabler and setcpu? Speaking of setcpu am I still safe to use the UV and OC kernal with 2.2 or should I avoid that?
aniteshj said:
Yup couldn't agree more and 99% of the time all it takes is a wipe of everything and start over, and I love that I can do that. Like I screwed up the root and the OS was booting into landscape mode, for everything. Thank god the files downloaded fast and its back to normal!
By the way, with the root on 2.2, all the applications and what not should still work right? Like marketenabler and setcpu? Speaking of setcpu am I still safe to use the UV and OC kernal with 2.2 or should I avoid that?
Click to expand...
Click to collapse
I'm running the 2.6.34 OC/UV kernel that I linked you to - clocked to 1113MHz with SetCPU - works flawlessly. No issues here so far, and I've been running that setup since Sunday.
codesplice said:
I'm running the 2.6.34 OC/UV kernel that I linked you to - clocked to 1113MHz with SetCPU - works flawlessly. No issues here so far, and I've been running that setup since Sunday.
Click to expand...
Click to collapse
How would I do that then, my Froyo is already rooted, can I just reflash that and be all good or how else do I get that kernal?
If you've got an aftermarket recovery image installed, you can just download the zip file that is linked in that other thread, put it on your microSD card, and flash it from recovery.
codesplice said:
If you've got an aftermarket recovery image installed, you can just download the zip file that is linked in that other thread, put it on your microSD card, and flash it from recovery.
Click to expand...
Click to collapse
Very awesome and it worked fine.
I'm going to guess I am missing a nice chunk of Marketplace apps because this is 2.2, notably some of the ones I bought, but its no biggie; marketplace enabler isn't installing but once again its a small trade off for what I am getting.
Glad it worked for you.
On the Market stuff, look around - I believe there are several threads discussing the issues and possible fixes/workarounds. I'm roaming in the middle of the desert so no Market to be found here or else I'd be able to help more.
Good luck!
Is there a way to remove your recovery in ADB when youre not rooted?
I did it, but i had to clash CWM 3.0.2.4 and format recovery, then when it rebooted. i did adb reboot recovery, it went to fastboot (which makes sense)
then i entered fastboot erase recovery. which might have been pointless but still did.
But my question is if i can erase my recovery through ADB when im rooted or even unrooted?
davidevan said:
Is there a way to remove your recovery in ADB when youre not rooted?
I did it, but i had to clash CWM 3.0.2.4 and format recovery, then when it rebooted. i did adb reboot recovery, it went to fastboot (which makes sense)
then i entered fastboot erase recovery. which might have been pointless but still did.
But my question is if i can erase my recovery through ADB when im rooted or even unrooted?
Click to expand...
Click to collapse
I have no idea if you can adb remove recovery.img or not, you probably could though. You would have to have r/w access to it's mtdblock. Even so, it sounds like you got it. You can always RUU which removes recovery as well. If you are really "unrooted" you wouldn't have a recovery to remove fyi. Also, most adb codes only work with r/w access to your /system partition, so unrooted would likely kill off adb, for what it's intended to do anyway. I am curious though, why do you ask/want to do this?
il Duce said:
I have no idea if you can adb remove recovery.img or not, you probably could though. You would have to have r/w access to it's mtdblock. Even so, it sounds like you got it. You can always RUU which removes recovery as well. If you are really "unrooted" you wouldn't have a recovery to remove fyi. Also, most adb codes only work with r/w access to your /system partition, so unrooted would likely kill off adb, for what it's intended to do anyway. I am curious though, why do you ask/want to do this?
Click to expand...
Click to collapse
Well here was my story, i wanted to go to Sprint to get a new hero cause my hardware was a little bit sticky/not working right, like the volume rocker and call button. So i unrooted with z4 (thats how i rooted). I double checked to see if i had root or busybox. through root checker in the Market. So i made my marry way over there, and these guys have all there phones rooted so they know what they are doing and if it might be rooted. he couldnt find the # or busybox, but he found my recovery img, by going into it manually. AND I WAS SCREWED. haha. so apparently z4 doesnt remove the recovery. To my knowledge thats the only way he found out i had prior root, and it took him bout 20 min to figure that out, so i thought i did a good job, except for having the recovery img
davidevan said:
Well here was my story, i wanted to go to Sprint to get a new hero cause my hardware was a little bit sticky/not working right, like the volume rocker and call button. So i unrooted with z4 (thats how i rooted). I double checked to see if i had root or busybox. through root checker in the Market. So i made my marry way over there, and these guys have all there phones rooted so they know what they are doing and if it might be rooted. he couldnt find the # or busybox, but he found my recovery img, by going into it manually. AND I WAS SCREWED. haha. so apparently z4 doesnt remove the recovery. To my knowledge thats the only way he found out i had prior root, and it took him bout 20 min to figure that out, so i thought i did a good job, except for having the recovery img
Click to expand...
Click to collapse
So what you really needed to do was run the Rom Update Utility to get back to the stock recovery image, not erase the recovery image.
davidevan said:
Well here was my story, i wanted to go to Sprint to get a new hero cause my hardware was a little bit sticky/not working right, like the volume rocker and call button. So i unrooted with z4 (thats how i rooted). I double checked to see if i had root or busybox. through root checker in the Market. So i made my marry way over there, and these guys have all there phones rooted so they know what they are doing and if it might be rooted. he couldnt find the # or busybox, but he found my recovery img, by going into it manually. AND I WAS SCREWED. haha. so apparently z4 doesnt remove the recovery. To my knowledge thats the only way he found out i had prior root, and it took him bout 20 min to figure that out, so i thought i did a good job, except for having the recovery img
Click to expand...
Click to collapse
Oh, now it makes sense. Yeah what Jason said, run the RUU. Did they help you or just say "bugger off you hacker" lol. If you RUU just go to a DIFFERENT store, they might help.
il Duce said:
Oh, now it makes sense. Yeah what Jason said, run the RUU. Did they help you or just say "bugger off you hacker" lol. If you RUU just go to a DIFFERENT store, they might help.
Click to expand...
Click to collapse
Thats the thing i cant run any damn RUUs haha
i always get a bootloader error. i think i literally done every RUU imaginable, except (i forgot the dev) came with a flashable RUU
davidevan said:
Thats the thing i cant run any damn RUUs haha
i always get a bootloader error. i think i literally done every RUU imaginable, except (i forgot the dev) came with a flashable RUU
Click to expand...
Click to collapse
I bet it's error 140 right? look here if I am right: http://forum.xda-developers.com/showthread.php?t=843544
il Duce said:
I bet it's error 140 right? look here if I am right: http://forum.xda-developers.com/showthread.php?t=843544
Click to expand...
Click to collapse
Hhaha oh god this looks technical (for me) i get a lot, but itll probably take me a day to understand the meaning of what it does and how to execute properly
Thanks to the the both of you!
davidevan said:
Hhaha oh god this looks technical (for me) i get a lot, but itll probably take me a day to understand the meaning of what it does and how to execute properly
Thanks to the the both of you!
Click to expand...
Click to collapse
What is a region version exactly? and do i HAVE to set a different path, or will it typically go where it needs too?
davidevan said:
What is a region version exactly? and do i HAVE to set a different path, or will it typically go where it needs too?
Click to expand...
Click to collapse
I don't think you need to worry about the region. I think you just flash the first zip there....... REVISION ........ looks like the dude pulled the zip I would send him a pm to see if he'll give it to you, and if he does, send the zip to me too. FYI I have never actually done that, never needed to.
il Duce said:
I don't think you need to worry about the region. I think you just flash the first zip there....... REVISION ........ looks like the dude pulled the zip I would send him a pm to see if he'll give it to you, and if he does, send the zip to me too. FYI I have never actually done that, never needed to.
Click to expand...
Click to collapse
Iactually got it!
like 15 min ago and i flashed it, ran regaws RUU he uses for unrooting and BAM,
back to stock. Thanks so much =]
Im not sure what your issue was about removing the zip? maybe i got extremely lucky before he removed it haha. if you want it i can send you it via PM
davidevan said:
Iactually got it!
like 15 min ago and i flashed it, ran regaws RUU he uses for unrooting and BAM,
back to stock. Thanks so much =]
Im not sure what your issue was about removing the zip? maybe i got extremely lucky before he removed it haha. if you want it i can send you it via PM
Click to expand...
Click to collapse
Dkd you get my PM?if you ever need anything else ill try to find it for you!
davidevan said:
Dkd you get my PM?if you ever need anything else ill try to find it for you?
Click to expand...
Click to collapse
LOL yeah I got it. I got confused reading that thread and thought the "unneeded" one was still there and the "needed" one was was missing, I think I was wrong. I downloaded it anyway - safety first. I usually don't need help finding anything, I have a BUNCH of threads saved in my userCP, and a crapload of zips/apps/roms/themes/tweaks/kernels/etc that I'll probably never need, lol. Thanks though.
il Duce said:
LOL yeah I got it. I got confused reading that thread and thought the "unneeded" one was still there and the "needed" one was was missing, I think I was wrong. I downloaded it anyway - safety first. I usually don't need help finding anything, I have a BUNCH of threads saved in my userCP, and a crapload of zips/apps/roms/themes/tweaks/kernels/etc that I'll probably never need, lol. Thanks though.
Click to expand...
Click to collapse
screw his threa i got confused too too haha
the. zip i sent is all you nedd and it flashed you is flashed through recovery; I used a stock rom to do this but i guess it doesnt matterwhich rom, guess it just fixed the boot loader entirely (the zip that is) and here is the RUU i persoanlly used... you might use a different one, but this was sufficient for me
http://www.mediafire.com/file/zoutcenvr20udwu/RUU_Hero_C_Sprint_2.27.651.5_R_signed_release.exe
So I accidentaly flashed the wrong root file thus making my systemui continuously crash. Any suggestions as to what I can do?
shahrukhraza said:
So I accidentaly flashed the wrong root file thus making my systemui continuously crash. Any suggestions as to what I can do?
Click to expand...
Click to collapse
Stock recovery or TWRP?
Are you looking to undo what you did without having to do a complete wipe, or are you open to more drastic solutions? Because you can always run the toolkit to reset to complete stock by flashing the stock images over your current system. But that would of course perform a complete wipe.
Paddington said:
Stock recovery or TWRP?
Are you looking to undo what you did without having to do a complete wipe, or are you open to more drastic solutions? Because you can always run the toolkit to reset to complete stock by flashing the stock images over your current system. But that would of course perform a complete wipe.
Click to expand...
Click to collapse
I dont really mind a complete wipe. And are you referring to this toolkit? http://forum.xda-developers.com/mot...l-windroid-universal-android-toolkit-t3048099
if not could you please tell me which one?
And to clarify, I followed this tutorial: https://www.youtube.com/watch?v=_fPIYhzWlnw . The file that I flashed to attempt to root is in the description of that.
shahrukhraza said:
I dont really mind a complete wipe. And are you referring to this toolkit? http://forum.xda-developers.com/mot...l-windroid-universal-android-toolkit-t3048099
if not could you please tell me which one?
And to clarify, I followed this tutorial: https://www.youtube.com/watch?v=_fPIYhzWlnw . The file that I flashed to attempt to root is in the description of that.
Click to expand...
Click to collapse
I actually used this one: http://forum.xda-developers.com/moto-x-2014/development/tool-moto-x-pure-edition-recovery-t2897819 when I was messed around, but I would imagine either would work. When I needed to return to unrooted stock, I believe that toolkit returned me to 4.4.4 unrooted stock, then I just ran the 5.0 OTA once the phone booted up.
The toolkit you referenced is the one I used to unlock the bootloader, flash TWRP, and root my phone. As long as you can get to recovery or fastboot, either toolkit should work to return you to stock. BUT I caution you, I have a pure edition, and these toolkits were made for the pure edition. If you do not have a pure edition, you'll want to read the disclaimers/instructions/other posts to make sure it will work on your phone.
Okay so this escalated quickly.
So here I am being my dumb self , I try to flash TWRP. That goes fine and then I try to wipe my data. After that I reboot it and as its turning on it foes black on the boot animation. and now I cant even get into freaking recovery mode. I dont know what I did but im pretty sure I messed up bad. I need some serious help now and anything is appreciated.
Paddington said:
I actually used this one: http://forum.xda-developers.com/moto-x-2014/development/tool-moto-x-pure-edition-recovery-t2897819 when I was messed around, but I would imagine either would work. When I needed to return to unrooted stock, I believe that toolkit returned me to 4.4.4 unrooted stock, then I just ran the 5.0 OTA once the phone booted up.
The toolkit you referenced is the one I used to unlock the bootloader, flash TWRP, and root my phone. As long as you can get to recovery or fastboot, either toolkit should work to return you to stock. BUT I caution you, I have a pure edition, and these toolkits were made for the pure edition. If you do not have a pure edition, you'll want to read the disclaimers/instructions/other posts to make sure it will work on your phone.
Click to expand...
Click to collapse
Yessir thanks for replying. However I now have a whole new problem. Do you have any suggestions for that? It is the post above^
shahrukhraza said:
Okay so this escalated quickly.
So here I am being my dumb self , I try to flash TWRP. That goes fine and then I try to wipe my data. After that I reboot it and as its turning on it foes black on the boot animation. and now I cant even get into freaking recovery mode. I dont know what I did but im pretty sure I messed up bad. I need some serious help now and anything is appreciated.
Click to expand...
Click to collapse
Hey thats an easy fix just load into the boatloader and reflash the rom through mfastboot
edit: you should be able to get all the files you need from his website http://forum.xda-developers.com/moto-x-2014/general/ota-pure-edition-lollipop-5-0-t2932625
ewalk4866 said:
Hey thats an easy fix just load into the boatloader and reflash the rom through mfastboot
edit: you should be able to get all the files you need from his website http://forum.xda-developers.com/moto-x-2014/general/ota-pure-edition-lollipop-5-0-t2932625
Click to expand...
Click to collapse
Bootloader as in vol. down + power button right? Thats not working too. I also tried other combinations to no luck. And before it was turning on but now its not even booting to the boot animation. Thanks for the link though, if it does magically boot into the bootloader then i'll know what to do at least.
Edit: Okay so theres the charging animation, so thats a start, I guess. Still no luck on the bootloader tho.
Okay got it into bootloader mode!
Now before I do any other stupid thing can somebody just confirm one thing for me? On Graffix's website, this is the img I should flash through mfastboot right
Lollipop 5.0 22.21.11 FULL IMAGE PACKAGE Zip
Just a confirmation because I dont really trust my judgement. Thanks again everybody
shahrukhraza said:
Okay got it into bootloader mode!
Now before I do any other stupid thing can somebody just confirm one thing for me? On Graffix's website, this is the img I should flash through mfastboot right
Lollipop 5.0 22.21.11 FULL IMAGE PACKAGE Zip
Just a confirmation because I dont really trust my judgement. Thanks again everybody
Click to expand...
Click to collapse
Yes that's right remember you only have to flash system
Sorry that my Toolkit suggestion messed you up. I really thought that solution would work, not make it worse.
Paddington said:
Sorry that my Toolkit suggestion messed you up. I really thought that solution would work, not make it worse.
Click to expand...
Click to collapse
Toolkit are never really a good idea it just makes people lazy and not learn how to flash or fix problems on there own.
Paddington said:
Sorry that my Toolkit suggestion messed you up. I really thought that solution would work, not make it worse.
Click to expand...
Click to collapse
Nah man that didnt mess it up, some other stupid thing did it lol. Nothing on you, rather thanks for the help.
ewalk4866 said:
Toolkit are never really a good idea it just makes people lazy and not learn how to flash or fix problems on there own.
Click to expand...
Click to collapse
I agree that Toolkits can make you lazy and not learn how to fix things on your own, but when you need a quick fix and don't have time to figure out what is going wrong, it's always nice to just boot your phone into fastboot or recovery and fix things with a few keystrokes on your computer.
I got it to work guys! Thanks for all the help. It was much appreciated.
I just bought myself an almost mint condition Nexus 6 (build MRA58R). It's running Marshmallow and I tried rooting it today. After I researched how to go by obtaining root I tried it out, felt very confident, didn't come across any errors. But then when I was booting back up, a screen with red letters saying something about my phone being corrupted was not allowing my phone to boot. Naturally, first I panicked. Afterwards I researched, found and then executed a manual flash of system, boot, bootloader, cache and recovery images. Then, my phone was back up and running. Discouraged and defeated, here I am knowing I could've done some better things with my time than mash commands into a terminal to fix my nooby mistake for a few hours. How should I approach obtaining root on my phone if at all possible with my model?
meeniemuffin said:
.... But then when I was booting back up, a screen with red letters saying something about my phone being corrupted was not allowing my phone to boot.
Click to expand...
Click to collapse
You could bring Google to court when your device is working 100% and the message says it is corrupt. Read the OP of this link. http://forum.xda-developers.com/showthread.php?t=3059493
meeniemuffin said:
I just bought myself an almost mint condition Nexus 6 (build MRA58R). It's running Marshmallow and I tried rooting it today. After I researched how to go by obtaining root I tried it out, felt very confident, didn't come across any errors. But then when I was booting back up, a screen with red letters saying something about my phone being corrupted was not allowing my phone to boot. Naturally, first I panicked. Afterwards I researched, found and then executed a manual flash of system, boot, bootloader, cache and recovery images. Then, my phone was back up and running. Discouraged and defeated, here I am knowing I could've done some better things with my time than mash commands into a terminal to fix my nooby mistake for a few hours. How should I approach obtaining root on my phone if at all possible with my model?
Click to expand...
Click to collapse
-enable "OEM unlocking" in developer options
-unlock bootloader
-flash TWRP using fastboot
-flash a custom kernel
-flash SuperSU 2.52
-KEEP BOOTLOADER UNLOCKED
-KEEP "OEM unlocking" ENABLED
---------- Post added at 09:50 AM ---------- Previous post was at 09:42 AM ----------
NLBeev said:
You could bring Google to court when your device is working 100% and the message says it is corrupt. Read the OP of this link. http://forum.xda-developers.com/showthread.php?t=3059493
Click to expand...
Click to collapse
There's nothing mentioned there.
Droidphilev said:
There's nothing mentioned there.
Click to expand...
Click to collapse
Hmm, here the links works. It is a link to a stock rom that is already rooted.
The rom is updated with the latest security OTA.
Full name of the OP.
[ROM]【6.0_r3】Stock MRA58R [Lite] - 【Marshmallow】【hC kernel】- 11/05/15
NLBeev said:
Hmm, here the links works. It is a link to a stock rom that is already rooted.
The rom is updated with the latest security OTA.
Full name of the OP.
[ROM]【6.0_r3】Stock MRA58R [Lite] - 【Marshmallow】【hC kernel】- 11/05/15
Click to expand...
Click to collapse
It indeed works but i thought it would bring to a page about the court thing you have mentioned.
Droidphilev said:
It indeed works but i thought it would bring to a page about the court thing you have mentioned.
Click to expand...
Click to collapse
No I was joking, sorry. But there is something serious behind the joke.
Here on XDA there are too many posts/questions about the 'corrupt message'.
The distance between ' customizing the phone' and 'Google' is growing.
NLBeev said:
No I was joking, sorry. But there is something serious behind the joke.
Here on XDA there are too many posts/questions about the 'corrupt message'.
The distance between ' customizing the phone' and 'Google' is growing.
Click to expand...
Click to collapse
Aha! i saw you posting this before but never knew that it was a joke
I didn't even need to read all this stuff. First thing I did was get into developer mode and almost instinctual that I turned on OEM unlocking before setting about unlocking the bootloader.
Sent from my Nexus 6 using Tapatalk
Yeah I bought my N6 recently and had a bad first time experience too. I ended up using a toolkit to root and all that, didn't need a custom rom so I kept it stock with TWRP and I'm very happy. Since then, I rooted some of the old devices I had laying around (you can check my signature), so I should be more prepared next time I need to update. My problem is I didn't really understand the commands, what did what and what exactly was required for root. Now that I have had plenty to practice with I'm pretty comfortable with commands and recoveries. Practice makes perfect I guess
NLBeev said:
No I was joking, sorry. But there is something serious behind the joke.
Here on XDA there are too many posts/questions about the 'corrupt message'.
The distance between ' customizing the phone' and 'Google' is growing.
Click to expand...
Click to collapse
Pretty much the trend. I bet by Android 7.0, rooting will be impossible.
shadowcore said:
Pretty much the trend. I bet by Android 7.0, rooting will be impossible.
Click to expand...
Click to collapse
I hope not. Google's software and design will be the weak point. Google could not give us some simple options like a dark interface, reboot options and dpi settings.
So, people, to sum it all up... The road to obtaining root on this Marshmallow enabled phone is?
If bootload is locked, unlock it - This will erase everything backup your device
1. Get modified boot.img for your version, flash it
2. Flash twrp
3. Flash SuperSu 2.52
meeniemuffin said:
So, people, to sum it all up... The road to obtaining root on this Marshmallow enabled phone is?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=63999613&postcount=3
!!!
Droidphilev said:
http://forum.xda-developers.com/showpost.php?p=63999613&postcount=3
!!!
Click to expand...
Click to collapse
Sorry! Slow to learn over here. I still have a question...do I need a custom kernel and flash stock rom? Or just a custom stock ROM thats already prerooted? Both, perhaps? Would I have to flash Twrp in order to even do this?
meeniemuffin said:
Sorry! Slow to learn over here. I still have a question...do I need a custom kernel and flash stock rom? Or just a custom stock ROM thats already prerooted? Both, perhaps? Would I have to flash Twrp in order to even do this?
Click to expand...
Click to collapse
You have a stockrom now, right?
if you want to keep that for now then this is the easiest way. The TWRP step is there to be able to flash the custom kernel. (and of course make backups and flash other roms in the future)
Droidphilev said:
You have a stockrom now, right?
if you want to keep that for now then this is the easiest way. The TWRP step is there to be able to flash the custom kernel. (and of course make backups and flash other roms in the future)
Click to expand...
Click to collapse
I had an epiphany earlier. I did everything....it all hit me at once. I finally managed to get Pure Nexus ROM working. Time for a test drive.
Thanks for the advice.
meeniemuffin said:
I had an epiphany earlier. I did everything....it all hit me at once. I finally managed to get Pure Nexus ROM working. Time for a test drive.
Thanks for the advice.
Click to expand...
Click to collapse
enjoy!
but DO NOT forget to keep "OEM unlocking" enabled!
(it will save you when you ever get locked out from your google acoount because you became aflashoholic)
Hey guys! So this is a very strange issue. When I power off my nexus, a lot of times I have to wait a good 30 seconds or so before I can power it back on or go into the bootloader. If I power it off, and try to turn it back on fast, it stays black screen almost as of it's frozen or just not responding. I noticed this issue begun when I flashed the radio from N preview 2, and didn't happen before that. My question here, is what could this be? Can the radio really cause odd things like this to happen? Or is there another cause? I am running the newest Android version MOB30I, and have multirom installed with about 4 or so secondaries.
H4X0R46 said:
Hey guys! So this is a very strange issue. When I power off my nexus, a lot of times I have to wait a good 30 seconds or so before I can power it back on or go into the bootloader. If I power it off, and try to turn it back on fast, it stays black screen almost as of it's frozen or just not responding. I noticed this issue begun when I flashed the radio from N preview 2, and didn't happen before that. My question here, is what could this be? Can the radio really cause odd things like this to happen? Or is there another cause? I am running the newest Android version MOB30I, and have multirom installed with about 4 or so secondaries.
Click to expand...
Click to collapse
You flashed Npreview radio on a marshmallow build?
Dead-neM said:
You flashed Npreview radio on a marshmallow build?
Click to expand...
Click to collapse
Yes! Yes I did. Could this be an issue?
H4X0R46 said:
Yes! Yes I did. Could this be an issue?
Click to expand...
Click to collapse
no. as im using the n preview radio on marshmallow, which is the same radio that came out with the last security update.
---------- Post added at 05:48 PM ---------- Previous post was at 05:46 PM ----------
H4X0R46 said:
Hey guys! So this is a very strange issue. When I power off my nexus, a lot of times I have to wait a good 30 seconds or so before I can power it back on or go into the bootloader. If I power it off, and try to turn it back on fast, it stays black screen almost as of it's frozen or just not responding. I noticed this issue begun when I flashed the radio from N preview 2, and didn't happen before that. My question here, is what could this be? Can the radio really cause odd things like this to happen? Or is there another cause? I am running the newest Android version MOB30I, and have multirom installed with about 4 or so secondaries.
Click to expand...
Click to collapse
im going to guess, try a different kernel. as its the kernel that will boot up the device?
H4X0R46 said:
Yes! Yes I did. Could this be an issue?
Click to expand...
Click to collapse
Yes it can. Why did you do that?
Make a backup (android or titatium backup)
Then reflash stock n6 firmware (erase data so put your backup and important files into pc)
Dead-neM said:
Yes it can. Why did you do that?
Make a backup (android or titatium backup)
Then reflash stock n6 firmware (erase data so put your backup and important files into pc)
Click to expand...
Click to collapse
the N radio, is the same exact radio that google released for the may security patch. so the N radio, is the latest official radio for the nexus 6. so no, that wont be the problem.
simms22 said:
no. as im using the n preview radio on marshmallow, which is the same radio that came out with the last security update.
---------- Post added at 05:48 PM ---------- Previous post was at 05:46 PM ----------
im going to guess, try a different kernel. as its the kernel that will boot up the device?
Click to expand...
Click to collapse
I wonder if it is. I'm using the newest Elite kernel for Marshmallow, it's always been my go to kernel. It's strange because after turning the device off, I can't turn it back on instantly, screen stays black as if it's not 100% shut down yet. I have to wait a bit before turning it back on, or entering the bootloader.
simms22 said:
im going to guess, try a different kernel. as its the kernel that will boot up the device?
Click to expand...
Click to collapse
No, it's the bootloader that boots the device.
If he's hitting the power button and unable to get to the "Google" splash screen or the bootloader, the kernel is very irrelevant.
I'd be more curious if he's trying to use the bootloader from the N-Preview 2 with MM. Even though I think it's supposed to be backwards compatible, the bootloader is the only thing that would cause that sort of issue.
*technically* I'm pretty sure that you could format /boot (where the kernel is stored) and still get to your bootloader for fastboot and such. So, the kernel is really irrelevant until after the bootloader does it's thing.
*edit*
also, there's a reason that these are known as "Developer Previews" not "End-User Previews"... If you don't know how to fix weird issues that pop up like that, you should probably avoid them.
Yoinx said:
No, it's the bootloader that boots the device.
If he's hitting the power button and unable to get to the "Google" splash screen or the bootloader, the kernel is very irrelevant.
I'd be more curious if he's trying to use the bootloader from the N-Preview 2 with MM. Even though I think it's supposed to be backwards compatible, the bootloader is the only thing that would cause that sort of issue.
*technically* I'm pretty sure that you could format /boot (where the kernel is stored) and still get to your bootloader for fastboot and such. So, the kernel is really irrelevant until after the bootloader does it's thing.
*edit*
also, there's a reason that these are known as "Developer Previews" not "End-User Previews"... If you don't know how to fix weird issues that pop up like that, you should probably avoid them.
Click to expand...
Click to collapse
Mmm yes after what said simms22 I've check the n preview and the bootloader is xxx.18 instead of last mm which is xxx.17 but a bootloader downgrade is risky right?
@H4X0R46 do you use the .sh file and update your bootloader and radio with n preview?
Dead-neM said:
Mmm yes after what said simms22 I've check the n preview and the bootloader is xxx.18 instead of last mm which is xxx.17 but a bootloader downgrade is risky right?
@H4X0R46 do you use the .sh file and update your bootloader and radio with n preview?
Click to expand...
Click to collapse
It can be. Normally, once you upgrade, you just stick with the new one as they're backwards compatible normally. But, the ones for the Previews aren't always 100%. The whole reason these previews come out is so that developers can start making their apps compatible prior to the official release. Ideally, this is supposed to be done in emulators not necessarily real devices.
If the 30 second delay in powering back on is *that* big of a deal (to him) to risk bricking the phone by downgrading the bootloader and having something go wrong... I say go for it.
Yoinx said:
It can be. Normally, once you upgrade, you just stick with the new one as they're backwards compatible normally. But, the ones for the Previews aren't always 100%. The whole reason these previews come out is so that developers can start making their apps compatible prior to the official release. Ideally, this is supposed to be done in emulators not necessarily real devices.
If the 30 second delay in powering back on is *that* big of a deal (to him) to risk bricking the phone by downgrading the bootloader and having something go wrong... I say go for it.
Click to expand...
Click to collapse
Is downgrading the bootloader really risky? I've done it before without issue and never knew this was risky! Are you supposed to just stay with the newest bootloader if you already flashed it? I always flash the bootloader for the image I'm flashing, even if I'm downgrading.
Dead-neM said:
Mmm yes after what said simms22 I've check the n preview and the bootloader is xxx.18 instead of last mm which is xxx.17 but a bootloader downgrade is risky right?
@H4X0R46 do you use the .sh file and update your bootloader and radio with n preview?
Click to expand...
Click to collapse
I flash each partition manually.
H4X0R46 said:
Is downgrading the bootloader really risky? I've done it before without issue and never knew this was risky! Are you supposed to just stay with the newest bootloader if you already flashed it? I always flash the bootloader for the image I'm flashing, even if I'm downgrading.
Click to expand...
Click to collapse
It's always risky when you're messing with essentially the lowest level software on the device. For instance, lets say that something happens while you're flashing the bootloader and it corrupts. What do you use to reflash it? You can't get to fastboot anymore...
As long as you know what you're doing, don't have corrupt images, and don't lose power or have lightning strike your computer while you're doing it, you would be fine.
The issue is that many/most people on XDA these days have no idea how to recover from problems or even what problems the things that they're doing might cause. So I tend to approach every situation under the assumption that the other poster may not have a full understanding.
No offense intended of course.
Yoinx said:
It's always risky when you're messing with essentially the lowest level software on the device. For instance, lets say that something happens while you're flashing the bootloader and it corrupts. What do you use to reflash it? You can't get to fastboot anymore...
As long as you know what you're doing, don't have corrupt images, and don't lose power or have lightning strike your computer while you're doing it, you would be fine.
The issue is that many/most people on XDA these days have no idea how to recover from problems or even what problems the things that they're doing might cause. So I tend to approach every situation under the assumption that the other poster may not have a full understanding.
No offense intended of course.
Click to expand...
Click to collapse
Alright so that's just to be safe then? My laptop sometimes freezes solid out of the blue, uncommon but does happen, and I always thought "what if I'm flashing stuff?" Scary thought. ESPECIALLY the bootloader! So the danger you're referring to is flashing a bootloader in general, not so much downgrading? Like I said, I always match the bootloader to the version I'm running. This is okay?
EDIT: I ALWAYS ALWAYS ALWAYS check the MD5 checksum for EVERYTHING before flashing. Can never be too safe
H4X0R46 said:
Alright so that's just to be safe then? My laptop sometimes freezes solid out of the blue, uncommon but does happen, and I always thought "what if I'm flashing stuff?" Scary thought. ESPECIALLY the bootloader! So the danger you're referring to is flashing a bootloader in general, not so much downgrading? Like I said, I always match the bootloader to the version I'm running. This is okay?
EDIT: I ALWAYS ALWAYS ALWAYS check the MD5 checksum for EVERYTHING before flashing. Can never be too safe
Click to expand...
Click to collapse
In general, the bootloader needs to match the highest version of android you intend to run. They're typically always backward compatible. On some phones, you can't downgrade the bootloader (at least not easily). This phone you should be fine doing so. However, there's not usually any reason to (backwards compatible afterall).
Yoinx said:
In general, the bootloader needs to match the highest version of android you intend to run. They're typically always backward compatible. On some phones, you can't downgrade the bootloader (at least not easily). This phone you should be fine doing so. However, there's not usually any reason to (backwards compatible afterall).
Click to expand...
Click to collapse
Cool! Thanks for your input on that! Much appreciated! Yea I'm always wary of the bootloader because like you said, it IS the lowest software on the device. Quick question, if that were to get corrupted, does the device just not boot resulting in permanent brick? Or does it boot just no fastboot access? Might be a noob question, but why not ask lol
H4X0R46 said:
Cool! Thanks for your input on that! Much appreciated! Yea I'm always wary of the bootloader because like you said, it IS the lowest software on the device. Quick question, if that were to get corrupted, does the device just not boot resulting in permanent brick? Or does it boot just no fastboot access? Might be a noob question, but why not ask lol
Click to expand...
Click to collapse
Depends, I've never really looked into unbricking this phone. Never had to yet.
Depending on the phone you can use tools like QHUSB and similar which let you reflash partitions just through the USB connection.
I know it's late but it could also be just the rom setup. I know a while ago there were commits that shut the device screen and buttons off before it was done shutting down (to make it appear faster) this made devices seem bricked for a short period. I don't know what ever happen to those commits, so I can't say for sure that it is them. But your issue fits perfectly.
So have I been flashing the bootloader wrong all along? I flashed in twrp a couple times but I try to flash them individually and wipe after flashing.
Sent from my Nexus 6 using XDA-Developers mobile app
Anybody able to find out why? I'm surprised to see I'm not the only one having this issue, it's annoying really.