All I would like to do is get my (not unlocked, but un-rooted) back to a stock recovery (I think?) and a stock OS. I want to be able to do updates OTA as they arrive on my phone, and the only reason I rooted in the first place was to get Gingerbread from CM7 and they didn't work. It got stuck in a endless boot loop and once I finally got a nightly working, it wasn't even worth it to me anymore.
I have used this thread: http://forum.xda-developers.com/showthread.php?t=614850
and done hours and days of research to try and solve my problem and get me to where I would like to be. I'd like to think I am not a noob to Android but clearly I am and I can't achieve 100% of my goal.
Where I am currently: Stock image, not sure of recovery, unrooted, bootloader unlocked.
Where I would like to be: Stock everything (I know I cannot relock the bootloader) just like when I bought it, so I can patiently wait for Gingerbread to push OTA whenever Google solves the issues.
Thank you and I apologize.
That guide has pretty much all the information you need. Flashing the stock HTC images and stock recovery will enable you to get OTA updates.
Read my signature, find "Unroot/restore" guide, look for the part for unlocked bootloaders.
Clearly that did not work for me or I would not have posted my concern.
@Jack_R1 I will attempt this again, thanks.
rynstphn said:
Clearly that did not work for me or I would not have posted my concern.
@Jack_R1 I will attempt this again, thanks.
Click to expand...
Click to collapse
You didn't explain where you got stuck, what you attempted, what went wrong and couldn't even state your recovery image. The guide you linked to is there for a reason, it works, however onlyif you follow it correctly without jumping in with 2 feet. If in future you require more precise help perhaps you should give precise information.
Perhaps the OP has encountered some of the issues i've posted about HERE?
Don't mean to kind of hi-jack this thread...
Don't mean to kind of hi-jack this thread but on the related topic of rooting the N1...is there some way to root it and still receive the OTA update for gingerbread(whenever it will come out)?
I did look through the threads and found nothing related unless it was further discussed on page x of 25, for example.
Also, are all wallpapers 960/980 by 800 for the N1 and other android phones? Is this so that when you scroll through screens you will still be able to see the image? That was the only possible answer I could think of.
Thanks in advance.
CTR01 said:
Don't mean to kind of hi-jack this thread but on the related topic of rooting the N1...is there some way to root it and still receive the OTA update for gingerbread(whenever it will come out)?
I did look through the threads and found nothing related unless it was further discussed on page x of 25, for example.
Also, are all wallpapers 960/980 by 800 for the N1 and other android phones? Is this so that when you scroll through screens you will still be able to see the image? That was the only possible answer I could think of.
Thanks in advance.
Click to expand...
Click to collapse
Yes and yes.
You can root using SuperOneClick and still recieve OTA updates. You only lose that ability once you've installed a custom recovery.
Thanks!
DirkGently1 said:
Yes and yes.
You can root using SuperOneClick and still recieve OTA updates. You only lose that ability once you've installed a custom recovery.
Click to expand...
Click to collapse
Awesome! Thanks for the reply and details.
DirkGently1 said:
Yes and yes.
You can root using SuperOneClick and still recieve OTA updates. You only lose that ability once you've installed a custom recovery.
Click to expand...
Click to collapse
Having a custom recovery has NOTHING to do with your ROM's ability to receive OTA updates... it has to do with you ROM, not your recovery.
And, as mentioned, rooting or unlocking has no impact on you being able to receive OTA updates.
Sent from my Nexus One using XDA App
efrant said:
Having a custom recovery has NOTHING to do with your ROM's ability to receive OTA updates... it has to do with you ROM, not your recovery.
And, as mentioned, rooting or unlocking has no impact on you being able to receive OTA updates.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Sorry, but that is wrong.
http://forum.xda-developers.com/showpost.php?p=10871795&postcount=1
Read that post. There is a stock recovery supplied in case anybody wishes to recieve future OTA updates.
DirkGently1 said:
Sorry, but that is wrong.
http://forum.xda-developers.com/showpost.php?p=10871795&postcount=1
Read that post. There is a stock recovery supplied in case anybody wishes to recieve future OTA updates.
Click to expand...
Click to collapse
Uh, sorry, but NO. What he says in that post is incorrect.
I have been using a custom recovery since I first got my Nexus One, and I have received EVERY OTA update.
EDIT: But hey, don't take my word for it. Try it yourself.
efrant, for clarification, do the OTAs auto install, or do you have to manually flash them?
Sent from my Nexus One using XDA App
danger-rat said:
efrant, for clarification, do the OTAs auto install, or do you have to manually flash them?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
So, in my setup (which is a rooted-but-otherwise-stock ROM and Amon_RA's 1.9.0 recovery), I receive OTA updates, and they auto-install with no problem (as Amon_RA's 1.9 recovery does not verify signatures). Note, however, that every OTA update also does two things: 1) it removes the permissions on the su binary (which obviously disables root access), and 2) it copies two files (/system/recovery-from-boot.p and /system/etc/install-recovery.sh) back onto the system partition, which will flash the stock recovery back to your devices as soon as you reboot. You will need to root first (either manually or by flashing ChainsDD su update before you reboot, or use SOC), then delete the two files, then reflash the custom recovery you want.
This is true only for Amon_Ra's 1.9 and later recoveries that either don't verify signatures at all, or allow turning verification off.
Jack_R1 said:
This is true only for Amon_Ra's 1.9 and later recoveries that either don't verify signatures at all, or allow turning verification off.
Click to expand...
Click to collapse
Yes, you are correct for the installation part of the update. However, you can have any recovery whatsoever, and it will not impact you receiving OTA update notifications.
efrant said:
Yes, you are correct for the installation part of the update. However, you can have any recovery whatsoever, and it will not impact you receiving OTA update notifications.
Click to expand...
Click to collapse
Yep, that's correct.
Cool
thanks for all the other responses to my question! I will look into this further when i have more time
Of course you can still 'receive' OTA but what's the point if you can't install them? I'm pretty sure that everybody understands the distinction!
DirkGently1 said:
Of course you can still 'receive' OTA but what's the point if you can't install them? I'm pretty sure that everybody understands the distinction!
Click to expand...
Click to collapse
If you read post 14, you will see that you CAN install them with a custom recovery...
Related
Those of us who flashed rootboot.img to install a rooted/insecure boot image were unable to update via the 2.3.1 OTA (Status 7 Error). A few different solutions have been posted. Here's one which worked for me, courtesy of momohammed20 and Luxferro:
Step 1: Restore the "2010-12-22.21.06.07" Nandroid backup which momohammed20 shared in this thread. That wipes your phone completely and gives you stock 2.3.1 without root.
Step 2: Follow the steps provided by Luxferro in this post. That gets you back root along with ClockworkMod Recovery.
Worked perfectly for me. Again, the solution is already out there in a few other threads, but I thought this deserved its own thread since a lot of folks have been stuck with the Status 7 error when trying to update.
Thanks again to momohammed20 and Luxferro!
Umm if we have 2.3 we can't nandroid a 2.3.1 backup. Ull get an error every time.
Sent from my Nexus S using XDA App
I followed these steps, and they worked nicely with no errors whatsoever. Others have done the same.
U were runninr2.3 rooted and then nandroid the 2.3.1 and u didn't get a MD5 error? Hard to beloved BC I've tried 5 times. Can anyone else try this out n let us know? ?
Sent from my Nexus S using XDA App
EDIT: just got it to work.. I re-downloaded it and it loaded. Seems the nandroid I dl from that thread the first time got renamed n it had a "(" in it, and recovery couldn't read the file...
Thanks alot tho, u were right!!
Sent from my Nexus One using XDA App
So will this allow the future flashing of OTAs without issue?
i also want to know if this will allow for future updates. i dont want to be reflashing my phone for every minor update.
Yes it will. The bootloader remains unlocked. But it restores everything to stock 2.3.1, and will have stock recovery, so next time there's a OTA it won't get an error when Its flashing BC u will be using the stock recovery n not CWR
Oh btw there's no root, in case u didn't understand what Stock 2.3.1 meant.
Sent from my Nexus S using XDA App
petep86 said:
Yes it will. The bootloader remains unlocked. But it restores everything to stock 2.3.1, and will have stock recovery, so next time there's a OTA it won't get an error when Its flashing BC u will be using the stock recovery n not CWR
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
From what I understand, the problem lies in the boot.img and not ClockworkMod.
TheBiles said:
From what I understand, the problem lies in the boot.img and not ClockworkMod.
Click to expand...
Click to collapse
What problem are u referring to?
That u can't ota the update??
Sent from my Nexus S using XDA App
petep86 said:
What problem are u referring to?
That u can't ota the update??
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
"Status 7" is the result of a rooted boot.img. It has nothing to do with ClockworkMod Recovery.
TheBiles said:
So will this allow the future flashing of OTAs without issue?
Click to expand...
Click to collapse
I don't know about that. For this particular OTA, it seems that the problem was the root boot. The method in the OP addresses that. However, I wouldn't assume that the next OTA will be compatible with a rooted device. My understanding (and I am no authority) is that the only way to know you're going to be getting OTAs is to revert to full stock. My intent was to have root and recovery in 2.3.1, not to get back to stock and stay there.
Wish this was posted this morning before i gave up
between some people getting it to work and other not working. People posting methods with stock boot.img but come to find out it wont work with rootboot....ect
Then realizing some people are on one root method while other used another...too confusing and i gave up after countless tries and gave and flashed modaco GRH78 r2 and glad i did because its pretty good..
IMO guys if this is going to require to you wipe your data save your self from headaches and just flash modaco GRH78 r2 with supercurio's EXT4 tweak it also rooted has new market and other fun stuff
demo, that's a good point. I'm using the r2 MoDaCo ROM now - it seems very good!
Amin Sabet said:
I don't know about that. For this particular OTA, it seems that the problem was the root boot. The method in the OP addresses that. However, I wouldn't assume that the next OTA will be compatible with a rooted device. My understanding (and I am no authority) is that the only way to know you're going to be getting OTAs is to revert to full stock. My intent was to have root and recovery in 2.3.1, not to get back to stock and stay there.
Click to expand...
Click to collapse
Nope, that is false. I had initially used superboot to root my phone when I first got it (w/ the pre-rooted modified boot.img). And I still got the prompt for the update. It will just give you a MD5 mismatch error when you accept the prompt and try to update.
deleted (accidental double post)
Luxferro, I think you misunderstood what I wrote. I too was rooted and got the prompt for this particular OTA, and some folks who were rooted (without root boot) were able to apply the OTA without an error. What I was trying to say was that the only way to be sure that they can receive and apply all future OTA updates would be to revert to stock (or have a means to revert to stock).
the status 7 error is a result of the patch process not finding a proper checksum for the things its patching if you have deleted system/framework apk's/odex's de-odexd the system/framework themed the system/framework changed the kernel this will cause status 7 error and will give you a hint on where the issue lies i.e. it will say somthing about calculator not match if you deleted it and error code 7
Hi!
Is it possible? I just bought a white Note Open Line but didn't noticed that it was released from India, My Blue one came from Singapore and already getting official update while the white one did not. Now my question is If I flash a stock ROM http://forum.xda-developers.com/showthread.php?t=1424997&page=3, would I be able to get an official update OTA? I wanna change the firmware the same as the blue one.
Many Thanks!
If you flash new firmware like LA4 you can't update using Kies .
Sent from my GT-N7000 using XDA App
ranjan.alva said:
If you flash new firmware like LA4 you can't update using Kies .
Sent from my GT-N7000 using XDA App
Click to expand...
Click to collapse
Thanks for replying! I update mine over the air. Currently I'm on KL2, if I change the white note with KL2 same as mine will I be able to download updates over the air if there is new update? Or if I flash any of the stock rom even if there's an update I won't be able download official update over the air?
Thanks!
Sent from my GT-N7000 using Tapatalk
bratboo said:
Thanks for replying! I update mine over the air. Currently I'm on KL2, if I change the white note with KL2 same as mine will I be able to download updates over the air if there is new update? Or if I flash any of the stock rom even if there's an update I won't be able download official update over the air?
Thanks!
Sent from my GT-N7000 using Tapatalk
Click to expand...
Click to collapse
Yes you will get updates. find the latest update available for your region then flash it.
What if your phone is rooted?
I would like to know if OTA updates are possible if you have rooted it. I gather from my experience in the past that you cannot. My phone now fails to connect to the server.
TBH, it is not a drama form me, I have no lag, and the phone seems to work brilliantly, apart from battery life. I had to root in order to get even reasonable battery life, as the bloatware was killing it.
The other issue is, as far as I can tell, we cannot get root access for stock LA4 OTA updates. Is this true, and can anyone say why? Of course, I may have that completely wrong.
Generally, after my attempt at using the Note without root for a month, I prefer root to a new ROM, at least until ICS. Even then, I think I'll wait until the bugs are ironed out, and then get an update that is rootable.
---------- Post added at 09:21 AM ---------- Previous post was at 09:09 AM ----------
OK, I have just read another of dr.ketan's most excellent and informative posts, and I think I can see the answer.
Real soon now, I'll have enough information and courage (and enough time) to start flashing custom roms at will!
After rooting phone you wont get OTA updates. and no warranty.
ranjan.alva said:
After rooting phone you wont get OTA updates. and no warranty.
Click to expand...
Click to collapse
I know many people in this forum who continue to have updates OTA with rooted phones.
Sent from my GT-N7000 using xda premium
You may get OTA after root,Only if you have selected right ROM for your region.
But remember if you update with OTA, you will lose Root. And now a days newer update is non rootable. so you cant root it again after update.
dr.ketan said:
You may get OTA after root,Only if you have selected right ROM for your region.
But remember if you update with OTA, you will lose Root. And now a days newer update is non rootable. so you cant root it again after update.
Click to expand...
Click to collapse
Thank you for this info! I just found out that my white note came from Samsung India and from what I heard they update pretty long. I won't mind if I will lose the root after as long as I got the white one the same firmware with my blue one so they will update at the same time. Thanks again!
Sent from my GT-N7000 using Tapatalk
What is the overall strategy for someone like me who is not intending (yet) to flash
dr.ketan said:
You may get OTA after root,Only if you have selected right ROM for your region.
But remember if you update with OTA, you will lose Root. And now a days newer update is non rootable. so you cant root it again after update.
Click to expand...
Click to collapse
Many thanks for that, but what is the overall strategy for someone like me who is not intending (yet) to flash ROMs? Should I wait until an OTA ROM is rootable, then unroot, get an OTA update, and the root again? Or should I go the whole hog and start flashing stock ROMs instead.
I am not (yet) talking about flashing custom ROMs. All I want is root access and the stock ROM.
BTW, I sincerely appreciate the time you personally have spent helping all of us with an enormous range of issues on this and related matters. I run my own support forums for a particular software product (which I was involved with writing) and I understand very well how much time and effort is involved with keeping up this level of support.
One thing i like to say what is wrong to update it manually rather then OTA?
OTA is the choice, who dont care Root. If you like to Root your device, just forget OTA, there is no guarranty wat thing when gets available, just try to use your device in best way with watever available right Now.
I dont see near future someone find out a method to root latest Or each n every ROM. this is hide n seek game, if someone find it, samsung will patch that thing in next update. so it become non usable.
What i believe is get Root n CWM/Mobile Odin Pro. Install any ROM, you like to try with Rooting function active. If you dont like just change it. Itz just simple.
Root also get you facility to keep Backup of your data n all.
dr.ketan said:
One thing i like to say what is wrong to update it manually rather then OTA?
OTA is the choice, who dont care Root. If you like to Root your device, just forget OTA, there is no guarranty wat thing when gets available, just try to use your device in best way with watever available right Now.
I dont see near future someone find out a method to root latest Or each n every ROM. this is hide n seek game, if someone find it, samsung will patch that thing in next update. so it become non usable.
What i believe is get Root n CWM/Mobile Odin Pro. Install any ROM, you like to try with Rooting function active. If you dont like just change it. Itz just simple.
Root also get you facility to keep Backup of your data n all.
Click to expand...
Click to collapse
+1 .. Totally agreed..
jeromepearce said:
Should I wait until an OTA ROM is rootable, then unroot, get an OTA update, and the root again? Or should I go the whole hog and start flashing stock ROMs instead.
I am not (yet) talking about flashing custom ROMs. All I want is root access and the stock ROM.
Click to expand...
Click to collapse
C'mon, mate, you're an Aussie: since when do the Aussies let others decide what they should or shouldn't do? You're going to wait for Samsung to let you have what you need when they see fit? Or are you going to take it yourself when and how you want?
Rooting is the way to go for the most people around here. That way you:
1. get the newest updates only a couple of days after they are released (good people in Dev section need just a day or two to let you download new stock Roms, already rooted)
2. get to play with lots of custom Roms out there - it's such fun, you wouldn't believe
3. get to backup your phone - system and data both - so you are safe to play on without fear that something bad is going to happen: you always have your backups to fall back on if it does
4. get to test various kernels, themes, rooted apps and whatnot to your heart's content
5. get enormous fun doing all of the above
Just follow the first link in DrKetan's signiture, read carefully, follow the instructions to the letter, and you'll never look back.
OK, I am getting the message
chasmodo said:
C'mon, mate, you're an Aussie: since when do the Aussies let others decide what they should or shouldn't do? You're going to wait for Samsung to let you have what you need when they see fit? Or are you going to take it yourself when and how you want?
Rooting is the way to go for the most people around here.
...
Just follow the first link in DrKetan's signiture, read carefully, follow the instructions to the letter, and you'll never look back.
Click to expand...
Click to collapse
OK, I am getting the message
BTW, I'm not just an Aussie, I'm an Aussie By Choice! Took me 10 years to get citizenship because my wife is disabled and they kept refusing us based on that (it went to the minister in the end). So, no, I definitely do not let others decide what I can and cannot do!
chasmodo said:
Just follow the first link in DrKetan's signiture, read carefully, follow the instructions to the letter, and you'll never look back.
Click to expand...
Click to collapse
Amen - this is all you need to know. Don't worry about getting updates from Samsung... your in better hands here.
Subject says it all. No luck with Google. Don't want to update until I know what's being updated.
Sent from my HTC first using xda app-developers app
not sure but...
jonslice said:
Subject says it all. No luck with Google. Don't want to update until I know what's being updated.
Sent from my HTC first using xda app-developers app
Click to expand...
Click to collapse
I installed the update last night. I honestly don't know what all the changes are, but I'm pretty sure it is a bugfix release. Still android 4.1.2. The only thing that I have noticed is that after the update my led will actually flash green for a text message or email. Before the update, my led only worked for charging, so I would have no idea whether I had email or messages without turning my screen on.
I have not noticed any other changes. No noticable speedups or slowdowns. Haven't discovered any issues. None of my apps have ever forced closed on this phone, and that has not changed after the update.
So...not a bad upgrade, although it might be pointless if you don't have any issues.
19.8MB update. Can't be too much going on in there, but I'd also think it's more than a few lines of code being updated...
Ooh, fun. Looks like I can't install the OTA with CWM or TWRP. Jonslice, are you rooted?
EDIT:
Weird. Now my phone says the software is up to date. What's the Build info under About Phone for you guys? Wondering if it did actually update even though it said it failed...
The OTA zip is on my dropbox in case anyone is curious to look at it. [1] Looks to me like it's updating a handful of system files, as well as the boot and recovery images. With clockworkmod installed, I was prompted to confirm installing the update because its signature wasn't verified, but I haven't yet attempted to let it install it. This should definitely give us an "official" image for the boot and recovery partitions though, which never hurts.
1: https://dl.dropboxusercontent.com/u/7859496/Android/mystul/OTAPkg.zip
nuclear_eclipse said:
The OTA zip is on my dropbox in case anyone is curious to look at it. [1] Looks to me like it's updating a handful of system files, as well as the boot and recovery images. With clockworkmod installed, I was prompted to confirm installing the update because its signature wasn't verified, but I haven't yet attempted to let it install it. This should definitely give us an "official" image for the boot and recovery partitions though, which never hurts.
1: https://dl.dropboxusercontent.com/u/7859496/Android/mystul/OTAPkg.zip
Click to expand...
Click to collapse
It'll fail if you try to install it. I'm thinking it needs the official bootloader to work. Someone will need to make this flashable. I was trying to extract it from my phone, but you beat me to it. Thanks!
chrisliphart said:
It'll fail if you try to install it. I'm thinking it needs the official bootloader to work. Someone will need to make this flashable. I was trying to extract it from my phone, but you beat me to it. Thanks!
Click to expand...
Click to collapse
I pulled this recovery.img from the firmware.zip that's included inside OTAPkg.zip: https://dl.dropboxusercontent.com/u/7859496/Android/mystul/recovery.img
I would assume that a simple `fastboot flash recovery recovery.img` should suffice.
nuclear_eclipse said:
I pulled this recovery.img from the firmware.zip that's included inside OTAPkg.zip: https://dl.dropboxusercontent.com/u/7859496/Android/mystul/recovery.img
I would assume that a simple `fastboot flash recovery recovery.img` should suffice.
Click to expand...
Click to collapse
Huh. I couldn't get the Firmware.zip to open on my system. Thanks for doing that. Now I'm gonna go be an idiot and possibly brick my device by pushing this recovery to my phone to try and install the OTA. lol
I did also manage to snag the recovery.log from clockwork recovery when the update first tried to run, just in case that actually proves useful to anyone... https://dl.dropboxusercontent.com/u/7859496/Android/mystul/recovery.log
nuclear_eclipse said:
I did also manage to snag the recovery.log from clockwork recovery when the update first tried to run, just in case that actually proves useful to anyone... https://dl.dropboxusercontent.com/u/7859496/Android/mystul/recovery.log
Click to expand...
Click to collapse
Thanks. I posted both the update and your log to the development forum to see if someone with more knowledge can do anything with them.
For the record, pushing that recovery doesn't work. Well, pushing it works, but you can't get into it on the phone. I repushed TWRP to my phone in the interim.
chrisliphart said:
19.8MB update. Can't be too much going on in there, but I'd also think it's more than a few lines of code being updated...
Ooh, fun. Looks like I can't install the OTA with CWM or TWRP. Jonslice, are you rooted?
EDIT:
Weird. Now my phone says the software is up to date. What's the Build info under About Phone for you guys? Wondering if it did actually update even though it said it failed...
Click to expand...
Click to collapse
I got failed update with CWM also. I'll try to post a build info screen shot once I'm on my desktop when my work week is over. Manual check for update says I still need update.
Note: unlocked boot loader, CWM and rooted.
Sent from my HTC first using xda app-developers app
As long as this doesn't remove the ability to disable Facebook Home, I'll probably update it. Can anyone confirm that this is the case?
Daman09 said:
As long as this doesn't remove the ability to disable Facebook Home, I'll probably update it. Can anyone confirm that this is the case?
Click to expand...
Click to collapse
That's a feature of Home, not the firmware. So yeah, you can still disable it. I don't ever see even Facebook changing that.
If you didn't know the 5.1.1 update comes with a "locked" bootloader (G920T) that does not allow you to flash custom recoveries. I would like to know what your status is if you don't mind because I think the more people who are stuck like me the more developers will say we need to come up with a fix for flashing custom recoveries issue.
The bootloader isn't locked. Twrp just needs to be updated. Won't happen til kernel source for 5.1.1 drops
Did we really need another thread about this?
Edit: Please explain how someone "accidentally" upgraded from rooted 5.0.2 to 5.1.1
mikeyinid said:
The bootloader isn't locked. Twrp just needs to be updated. Won't happen til kernel source for 5.1.1 drops
Click to expand...
Click to collapse
That is why I put "locked" in quotes and no I am not sure of that the phone blocks any custom recovery installed and I explained in another thread how cf-auto-root is just a recovery that is why it isn't working either.
se1000 said:
Did we really need another thread about this?
Edit: Please explain how someone "accidentally" upgraded from rooted 5.0.2 to 5.1.1
Click to expand...
Click to collapse
What I mean by that is if you had no knowledge of the changes in the bootloader and the fact you can't downgrade
ethanscooter said:
Accidently* wasn't really paying while typing and what I mean by that is if you had no knowledge of the changes in the bootloader and the fact you can't downgrade
Click to expand...
Click to collapse
So what you meant is, "If you downloaded a 1.3GB file and ODIN'ed back to stock just to upgrade and ignored the big bold warning that you couldn't downgrade" OR "If you downloaded a 1.3GB file and ODIN'ed to a new version of android that there was an active thread where it was CLEAR there was no root method"
"Accidentally"
ethanscooter said:
That is why I put "locked" in quotes and no I am not sure of that the phone blocks any custom recovery installed and I explained in another thread how cf-auto-root is just a recovery that is why it isn't working either.
Click to expand...
Click to collapse
You don't have to take my word for it. But I'm telling you, the bootloader is not locked.
se1000 said:
So what you meant is, "If you downloaded a 1.3GB file and ODIN'ed back to stock just to upgrade and ignored the big bold warning that you couldn't downgrade" OR "If you downloaded a 1.3GB file and ODIN'ed to a new version of android that there was an active thread where it was CLEAR there was no root method"
"Accidentally"
Click to expand...
Click to collapse
LOL some people did it look in the Q&A section people are posting things about recovery not being seandroid enabled because of the bootloader for me I was actually in a boot loop so I just downloaded the latest version from Sammobile
OH and sorry for the last typo I thought you were correcting me
mikeyinid said:
You don't have to take my word for it. But I'm telling you, the bootloader is not locked.
Click to expand...
Click to collapse
I understand it isn't locked but what I mean is for the time being it feels like it is locked considering we can't root or install a custom recovery or downgrade.
ethanscooter said:
LOL some people did it look in the Q&A section people are posting things about recovery not being seandroid enabled because of the bootloader for me I was actually in a boot loop so I just downloaded the latest version from Sammobile
OH and sorry for the last typo I thought you were correcting me
Click to expand...
Click to collapse
Of course people did it, but don't make it seem like you clicked one button and the upgrade went through and now you're stuck. You ACTIVELY went through the upgrade process to force it through.
Plus, you don't need THREE threads on the same subject.
se1000 said:
Of course people did it, but don't make it seem like you clicked one button and the upgrade went through and now you're stuck. You ACTIVELY went through the upgrade process to force it through.
Plus, you don't need THREE threads on the same subject.
Click to expand...
Click to collapse
I didn't make the 3 threads others did I just responded to all 3. Also the whole point of that one choice in the poll is for people who were expecting a normal tmobile update and didn't get what they thought they would usually tmobile let's you downgrade and you can flash a recovery right away but this time it was different and not a ton of people knew it was going to be different maybe I should've worded it better I am sorry.
ethanscooter said:
I didn't make the 3 threads others did I just responded to all 3. Also the whole point of that one choice in the poll is for people who were expecting a normal tmobile update and didn't get what they thought they would usually tmobile let's you downgrade and you can flash a recovery right away but this time it was different and not a ton of people knew it was going to be different maybe I should've worded it better I am sorry.
Click to expand...
Click to collapse
You have 2 threads in the QA section that are on this same subject.
Look, if you want to have a rooted, custom recovery, custom kernel device, don't be the first to update. That's just how things go.
From the Moderator
Redundant Thread ......... So........
..............THREAD CLOSED...........
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)