Related
Hi
I have been flashing for many years, but I think for the first time in 7 years, I am not feeling safe to flash on the Nexus 6.
I upgraded the stock to 5.1, and had a hard time figuring out what people did, other then flashing the CM 12 5.01 to brick thier phone.
Could someone Help compile a list of what not to do on the Nexus 6 and upgraded to stock 5.1?
What should I and others do in stead to insure we can unlock teh bootloader, flash recovery and flash custom rom safely
Thanks in advance
Flashed 5.1 BL and Modem on euphoria 5.0.2, then flashed back to stock 5.0.1, then flashed euphoria again, the same build upon which i flashed the 5.1 BL and Modem.
I didn't flash CM, still bricked my phone . And i don't know why. Coz after flashing it worked for a while and next morning it was bricked.
pallefar said:
Hi
I have been flashing for many years, but I think for the first time in 7 years, I am not feeling safe to flash on the Nexus 6.
I upgraded the stock to 5.1, and had a hard time figuring out what people did, other then flashing the CM 12 5.01 to brick thier phone.
Could someone Help compile a list of what not to do on the Nexus 6 and upgraded to stock 5.1?
What should I and others do in stead to insure we can unlock teh bootloader, flash recovery and flash custom rom safely
Thanks in advance
Click to expand...
Click to collapse
Most of the others relocked their bootloader after flashing the full 5.1 image and ended up in a bootloop. Not the end of the world but now the "enable OEM unlock" unsets every time you boot so if you lock the bootloader and end up in a bootloop, you cannot unlock the bootloader which means you cannot flash anything to recover.
Dont relock your bootloader?
So would you say that if you have unlocked the bottloader then dont relock it untill a fix for the brick has been found?
Also if you update to 5.1, the stay with 5.1 Roms to be on the safe side?
Thanks in advance, just want to help pthers with same questions
pallefar said:
What should I and others do in stead to insure we can unlock teh bootloader, flash recovery and flash custom rom safely
Click to expand...
Click to collapse
I think people are bricking b/c they are attempting to downgrade the bootloader and/or the partition table. In general, you should never do that with a Motorola phone. There are some examples when it could be done in the past, but those are few and far between.
The best advice is to know what you are flashing before you flash and make sure you never attempt to downgrade the bootloader or partition table. And never take an OTA until you revert back to stock.
Also, always enable OEM lock and USB debugging. If that makes your phone too insecure for you b/c you keep trade secrets, classified information or pictures of your private parts on your phone, then you shouldn't be unlocking and rooting your phone to begin with.
So based on what has helped avoid bricks on the Moto X:
1) ensure your bootloader is unlocked before you flash anything to your phone;
2) do not attempt to downgrade the bootloader or partition table*;
3) know what you are flashing and make sure whatever it is does not include files that would attempt to downgrade your bootloader or partition table*;
4) make sure OEM unlock and USB debugging are enabled each time you flash;
5) never take an OTA unless you have reverted back to stock completely;
6) never upgrade the bootloader w/o also upgrading the partition table* and vice-versa; and
7) use mfastboot for flashing**.
* there is apparently no partition table on a Nexus
** this may or may not be necessary on the Nexus 6
Now the above is a bit overkill - for instance, there may be situations in which you can take an OTA w/o reverting completely back to stock or there may be situations in which you can downgrade your bootloaders. But if you follow those rules above you should be safe from bricking your device.
As long as your bootloader is unlocked and you can get into bootloader mode and you have the factory images, you aren't bricked.
---------- Post added at 05:07 PM ---------- Previous post was at 04:57 PM ----------
randy6644 said:
Flashed 5.1 BL and Modem on euphoria 5.0.2, then flashed back to stock 5.0.1, then flashed euphoria again, the same build upon which i flashed the 5.1 BL and Modem.
I didn't flash CM, still bricked my phone . And i don't know why. Coz after flashing it worked for a while and next morning it was bricked.
Click to expand...
Click to collapse
Did you flash the 5.1 partition table when you flashed the 5.1 bootloader? I would never have a mismatch of versions b/t the bootloader and the partition table.
Once you upgraded the bootloader to 5.1, do you know if any of the subsequent flashes you did included earlier versions of the bootloader or the partition table?
pallefar said:
So would you say that if you have unlocked the bottloader then dont relock it untill a fix for the brick has been found?
Click to expand...
Click to collapse
I personally.
I'm not on 5.1 yet so I cant say if the "Enable OEM lock" is controlled by the bootloader at boot or the Kernel / OS..
Better be safe then sorry
JulesJam said:
I think people are bricking b/c they are downgrading the bootloader and/or the partition table. In general, you should never do that with a Motorola phone. There are some examples when it could be done, but those are few and far between.
The best advice is to know what you are flashing before you flash and make sure you never attempt to downgrade the bootloader or partition table. And never take an OTA until you revert back to stock.
Also, always enable OEM lock and USB debugging. If that makes your phone too insecure for you b/c you keep trade secrets, classified information or pictures of your private parts on your phone, then you shouldn't be unlocking and rooting your phone to begin with.
So:
1) ensure your bootloader is unlocked before you flash anything to your phone;
2) do not attempt to downgrade the bootloader or partition table;
3) know what you are flashing and make sure whatever it is does not include files that would attempt to downgrade your bootloader or partition table;
4) make sure OEM unlock and USB debugging are enabled each time you flash; and
5) never take an OTA unless you have reverted back to stock completely.
Now the above is a bit overkill - for instance, there may be situations in which you can take an OTA w/o reverting completely back to stock or there may be situations in which you can downgrade your bootloaders. But if you follow those rules above you should be safe from bricking your device.
As long as your bootloader is unlocked and you can get into bootloader mode and you have the factory images, you aren't bricked.
Click to expand...
Click to collapse
Thanks mate, I think for now it is better to be dafe then sorry and follow your steps above
i believe it would be controlled by the kernel/OS...and thats how it gets disabled upon boot of 5.1
pallefar said:
Thanks mate, I think for now it is better to be dafe then sorry and follow your steps above
Click to expand...
Click to collapse
I think I would add to that not to do anything to cause a version mismatch b/t the bootloader and the partition table. And since you shouldn't be downgrading those, what that means is never upgrade the bootloader w/o also upgrading the partition table and vice-versa.
Again, maybe you can get away with upgrading the bootloader w/o upgrading the partition table but I can't think of any reason not to have those both be on the same version.
One more thing - use mfastboot not fastboot to flash. mfastboot may only be needed for the larger files like system.img but I just use mfastboot all of the time and then I don't have to worry about it.
benefit of mfastboot
What is the benefit of mfastboot compared to normal fastboot flashing? just want to make sure everyhitng is covered
thanks in advance
pallefar said:
What is the benefit of mfastboot compared to normal fastboot flashing? just want to make sure everyhitng is covered
thanks in advance
Click to expand...
Click to collapse
http://mark.cdmaforums.com/MotoX-mFastboot.htm
pallefar said:
Hi
I have been flashing for many years, but I think for the first time in 7 years, I am not feeling safe to flash on the Nexus 6.
I upgraded the stock to 5.1, and had a hard time figuring out what people did, other then flashing the CM 12 5.01 to brick thier phone.
Could someone Help compile a list of what not to do on the Nexus 6 and upgraded to stock 5.1?
What should I and others do in stead to insure we can unlock teh bootloader, flash recovery and flash custom rom safely
Thanks in advance
Click to expand...
Click to collapse
The issue with bricking is that after updating to 5.1 people flashed CM which for some reason includes a bootloader. (no rom should include a BL and radio) When they flashed CM it tried to load an older bootloader which caused bricks. This will be seen by any roms that pretty much is just a renamed CM rom. My advise would be to know what your flashing by always inspecting the zip file before you flash it.
Is the nexus locking its bootloader itself now...I unlocked mine and never have knowing locked it back....So on every flash or after every reboot always turn OEM unlock on?
Sent from my Nexus 6 using Tapatalk
safe side
So basicly to be on the safe side, stay away or evestigate any Rom which is using the CM 12 source.
I guess AOSP is a safer bet at the moment? like Chroma rom
pallefar said:
So basicly to be on the safe side, stay away or evestigate any Rom which is using the CM 12 source.
I guess AOSP is a safer bet at the moment? like Chroma rom
Click to expand...
Click to collapse
Pretty much. Many claim to be based off of AOSP but most are just using CM sources. I know Slim and DU are based off of AOSP. DU uses the theme engine from CM but thats about it. Slim doesnt use anything from CM last I knew. Many are moving away from using anything CM related so there may be more.
zelendel said:
Pretty much. Many claim to be based off of AOSP but most are just using CM sources. I know Slim and DU are based off of AOSP. DU uses the theme engine from CM but thats about it. Slim doesnt use anything from CM last I knew. Many are moving away from using anything CM related so there may be more.
Click to expand...
Click to collapse
Yep. I think @zephiK chroma is aosp no-cm.
awesome thanks guys, I think this thread will guide people to not brick thier phones
kenbrownstone said:
Is the nexus locking its bootloader itself now...I unlocked mine and never have knowing locked it back....So on every flash or after every reboot always turn OEM unlock on?
Click to expand...
Click to collapse
No it doesn't relock itself but lots of people who are on these forums don't really understand what they are doing/flashing and so to be extra safe, I put that in there for people always to double check that OEM unlock is enabled.
People may think they have unlocked when they haven't or may not realize they relocked. I know that seems hard to do but I have never seen so many bricked nexi in my life before.
Just trying to help the less experienced from bricking. If you know what you are doing you don't need to take advice from me.
---------- Post added at 10:37 PM ---------- Previous post was at 10:32 PM ----------
zelendel said:
The issue with bricking is that after updating to 5.1 people flashed CM which for some reason includes a bootloader. (no rom should include a BL and radio) When they flashed CM it tried to load an older bootloader which caused bricks.
Click to expand...
Click to collapse
Yep, that will do it - downgrading the bootloader is a no-no on a motorola phone except in rare cases when it was possible.
zelendel said:
My advise would be to know what your flashing by always inspecting the zip file before you flash it.
Click to expand...
Click to collapse
Always!
Great write up! Saved my a$$ for sure. I updated my bootloader and radio the day it was available and I'm running a 5.0.1 CM12 based ROM. Here's where sometimes you get lucky, I was on v8.7 of this ROM, after I did the 5.1 bootloader and radio flash, an update came out to 8.8, I'm usually flash happy, but I figured why bother if I can wait for the 5.1 integration! I did unzip the update and no bootloader.img to be found, so I suppose the dev was wise enough not to put it in, but still.
I was curious about why most are moving away from CM? Because of these types of oversights? Their"interesting" business model?
JulesJam said:
I think people are bricking b/c they are attempting to downgrade the bootloader and/or the partition table. In general, you should never do that with a Motorola phone. There are some examples when it could be done in the past, but those are few and far between.
The best advice is to know what you are flashing before you flash and make sure you never attempt to downgrade the bootloader or partition table. And never take an OTA until you revert back to stock.
Also, always enable OEM lock and USB debugging. If that makes your phone too insecure for you b/c you keep trade secrets, classified information or pictures of your private parts on your phone, then you shouldn't be unlocking and rooting your phone to begin with.
So:
1) ensure your bootloader is unlocked before you flash anything to your phone;
2) do not attempt to downgrade the bootloader or partition table;
3) know what you are flashing and make sure whatever it is does not include files that would attempt to downgrade your bootloader or partition table;
4) make sure OEM unlock and USB debugging are enabled each time you flash;
5) never take an OTA unless you have reverted back to stock completely;
6) never upgrade the bootloader w/o also upgrading the partition table and vice-versa; and
7) use mfastboot for flashing.
Now the above is a bit overkill - for instance, there may be situations in which you can take an OTA w/o reverting completely back to stock or there may be situations in which you can downgrade your bootloaders. But if you follow those rules above you should be safe from bricking your device.
As long as your bootloader is unlocked and you can get into bootloader mode and you have the factory images, you aren't bricked.
---------- Post added at 05:07 PM ---------- Previous post was at 04:57 PM ----------
Did you flash the 5.1 partition table when you flashed the 5.1 bootloader? I would never have a mismatch of versions b/t the bootloader and the partition table.
Once you upgraded the bootloader to 5.1, do you know if any of the subsequent flashes you did included earlier versions of the bootloader or the partition table?
Click to expand...
Click to collapse
Does nexus have a partition table to flash? I've never heard of that from a nexus forum. I just flashed the 5.1 BL and went back to 5.0 stock rom ,then flashed euphoria. I believe that you flash via Fastboot if your bootloade is mismatched, that you can't acutally flash it. Not unless you use dd command. I'm not sure about this, though. I'm no way a dev or someone with knowledge in this field. But for nexus devices i owned, i never saw any nexus could be bricked this easy. Yes, they're made by motorola, but it's still a nexus . LG makes nexus 4 and 5, doesn't mean LG locked their bootloader as well. I don't think it's a fault of Motorola or has anything to do with its manufacturer. It's a nexus.
I am ever impatient. So when I saw new factory images up on the Google page, I just had to try them out. I upgraded to LMY47E, then naturally the next day I saw the news about LMY47M. Being that I'm a T-Mobile customer, I want the M version (reported the T-Mobile version) of the new 5.1. Unfortunately, as part of the LMY47E upgrade, the bootloader was moved from 71.05 to 71.08.
Now, trying to flash factory images from LRX22C results in a bootloader mismatch error. I got around this by manually flashing radio, system, boot, etc. images on the phone, and I do in fact now have the 5.01 build showing. However, when I try to sideload the LMY47M build, I'm receiving an error from this line in the updater script:
Code:
#getprop("ro.build.fingerprint") == "google/shamu/shamu:5.0.1/LRX22C/1602158:user/release-keys" ||
abort("Package expects build fingerprint of google/shamu/shamu:5.0.1/LRX22C/1602158:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
It's stating that I have 5.0.2 LRX22G signed with test keys. I don't know how I would have got an engineering build installed from flashing factory firmware from the Google page, but apparently something is confused somewhere along the way. The best I can guess is that perhaps that's some leftover remnants from when I had installed a CM12 nightly build (which I believe is based on 5.0.2).
I don't know what I need to flash with what to get that cleared so I can sideload the LMY47M OTA, and I'm concerned that I may be unable to properly upgrade to additional OTA upgrades if there's a missmatch along the way. There was a confirmed update coming to move from LMY47E to LMY47M per T-Mo support , also confirmed by @askdes) but again, if I have some funky mismatched stuff, unsure if I can upgrade to LMY47E again and still expect to receive the OTA.
I'd love to have someone with more knowledge of these wonderful things weigh in on this. Educated opinions are always welcome, but someone with actual first-hand knowledge would be incredibly helpful to my sanity as well.
Thanks!
Theres nothing you can do to receive the OTA now.
Maybe the M factory image will become available. If so, you'll be able to flash that. Well at least the system and boot image. If the bootloader is newer, that too.
I suppose the other options are that if someone could install TWRP with an unmodified, unrooted M on, they could take a backup of system and boot and give you them to do a Nandroid restore via TWRP... Or maybe someone can take a system dump for you. But you cannot downgrade the bootloader.
mikecole79 said:
I am ever impatient. So when I saw new factory images up on the Google page, I just had to try them out. I upgraded to LMY47E, then naturally the next day I saw the news about LMY47M. Being that I'm a T-Mobile customer, I want the M version (reported the T-Mobile version) of the new 5.1. Unfortunately, as part of the LMY47E upgrade, the bootloader was moved from 71.05 to 71.08.
Now, trying to flash factory images from LRX22C results in a bootloader mismatch error. I got around this by manually flashing radio, system, boot, etc. images on the phone, and I do in fact now have the 5.01 build showing. However, when I try to sideload the LMY47M build, I'm receiving an error from this line in the updater script:
Code:
#getprop("ro.build.fingerprint") == "google/shamu/shamu:5.0.1/LRX22C/1602158:user/release-keys" ||
abort("Package expects build fingerprint of google/shamu/shamu:5.0.1/LRX22C/1602158:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
It's stating that I have 5.0.2 LRX22G signed with test keys. I don't know how I would have got an engineering build installed from flashing factory firmware from the Google page, but apparently something is confused somewhere along the way. The best I can guess is that perhaps that's some leftover remnants from when I had installed a CM12 nightly build (which I believe is based on 5.0.2).
I don't know what I need to flash with what to get that cleared so I can sideload the LMY47M OTA, and I'm concerned that I may be unable to properly upgrade to additional OTA upgrades if there's a missmatch along the way. There was a confirmed update coming to move from LMY47E to LMY47M per T-Mo support , also confirmed by @askdes) but again, if I have some funky mismatched stuff, unsure if I can upgrade to LMY47E again and still expect to receive the OTA.
I'd love to have someone with more knowledge of these wonderful things weigh in on this. Educated opinions are always welcome, but someone with actual first-hand knowledge would be incredibly helpful to my sanity as well.
Thanks!
Click to expand...
Click to collapse
What about relashing the factory image? Of course, this would wipe all data, config, apps, etc.
clairez said:
What about relashing the factory image? Of course, this would wipe all data, config, apps, etc.
Click to expand...
Click to collapse
Thank you both for the replies. My course at this point seems to be "wait until M is up on the factory images page", which is what I suspected.
I have done a full factory flash of the LRX22C image, manually (since the script fails because of the newer bootloader) and it has still left me with the engineering build stamp showing. Any idea where that information is coming from? The image I used to flash back was the LRX22C for Shamu from developers <dot> google <dot> com/android/nexus/images. I would think that would have wiped the world (exception of the bootloader that doesn't know how to travel back in time; should really introduce that thing to Doc....). I'm not sure if it's because of the bootloader itself, or because of some other thing that just didn't get wiped properly. I flashed the radio, boot, cache, recovery, userdata, and system images initially, then re-flashed recovery to TWRP 2.8 after. Where does ro.build.fingerprint get it's information from? Is that all from the bootloader?
clairez said:
What about relashing the factory image? Of course, this would wipe all data, config, apps, etc.
Click to expand...
Click to collapse
But you can not flash an older bootloader So far for the developer phone At least HTC has S-Off.
gee2012 said:
But you can not flash an older bootloader So far for the developer phone At least HTC has S-Off.
Click to expand...
Click to collapse
I could be wrong (often am), but I thought several folks tried and succeeded with a factory image flash, by using the following methodology:
1. If your phone is showing OEM Unlock in the developer options and you can boot into recovery, then
2. Boot into android and remove all security
3. Set OEM Unlock and USB debugging
4. Perform several reboots to ensure OEM Unlock is persistent (if not, do not proceed)
5. Perform a factory reset/data wipe in recovery
6. Reflash the 5.01 factory image (or wait for 5.1 M version) using the manual method located here:
[TUTORIAL][GUIDE][HOW TO] Flash Factory Images || Unroot || Relock bootloader
http://forum.xda-developers.com/nexu...shamu-t2954008
* Use Method 2 from this tutorial, Method 1 does not work
7. You can relock the bootloader as outlined in the tutorial.
8. At this point if all went as expected, the N6 is factory fresh and eligible for the OTA.
But before you proceed check out some of the other posts to ensure that others have succeeded. So many reports of bricked phones it is hard to tell what caused the problem.
I have used the above method several times, but only reflashing to a newer version.
Hope this helps ....
PS: I missed the mention of CM12! There are so many variables in your situation, I am unsure now that there is a way back. So many of the hard bricked cases involved CM12. Good luck, I hope you come out of this right side up!
mikecole79 said:
Thank you both for the replies. My course at this point seems to be "wait until M is up on the factory images page", which is what I suspected.
I have done a full factory flash of the LRX22C image, manually (since the script fails because of the newer bootloader) and it has still left me with the engineering build stamp showing. Any idea where that information is coming from? The image I used to flash back was the LRX22C for Shamu from developers <dot> google <dot> com/android/nexus/images. I would think that would have wiped the world (exception of the bootloader that doesn't know how to travel back in time; should really introduce that thing to Doc....). I'm not sure if it's because of the bootloader itself, or because of some other thing that just didn't get wiped properly. I flashed the radio, boot, cache, recovery, userdata, and system images initially, then re-flashed recovery to TWRP 2.8 after. Where does ro.build.fingerprint get it's information from? Is that all from the bootloader?
Click to expand...
Click to collapse
I am in the same situation as you are, mine shows my build fingerprint as "google/omni_shamu/shamu:5.0.2/LRX22G/dees_troy020120939:eng/test-keys" I have gone through the same steps as you have and tried to reflash LRX22C. I guess we wait until the factory image!
wadsface said:
I am in the same situation as you are, mine shows my build fingerprint as "google/omni_shamu/shamu:5.0.2/LRX22G/dees_troy020120939:eng/test-keys" I have gone through the same steps as you have and tried to reflash LRX22C. I guess we wait until the factory image!
Click to expand...
Click to collapse
Have you flashed a custom kernel? Sounds like a non-google boot.IMG or something is on the device.
clairez said:
4. Perform several reboots to ensure OEM Unlock is persistent (if not, do not proceed)
Click to expand...
Click to collapse
That is absurd.
Unlocked is unlocked is unlocked.
The only thing that may not be persistent is the flag in the dev settings menu, ENABLE oem unlock.
Once you enable the unlock, you may *immediately* try to unlock it. If the enable setting isn't persistent, then it just won't unlock.
ONCE IT IS UNLOCKED, IT IS UNLOCKED. DON'T EVER LOCK IT AGAIN.
I also received that error when trying to sideload the OTA. The only modification I made was using a custom kernel, but I flashed the stock boot.img before attempting to sideload. So I'm not sure what could have caused the error?
I just read somewhere that we can get the sideload to work if a line in the updater script is deleted or modified. Has anyone else read this?
To sideload an OTA you need a stock recovery. I have been unable to sideload an OTA with a custom recovery installed since 5.0. The Dees Troy (guessing TWRP recovery) in the path is a dead giveaway that it is from the recovery. I don't think it is checking bootloader version when sideloading OTA.
android_mp99 said:
TI don't think it is checking bootloader version when sideloading OTA.
Click to expand...
Click to collapse
It is. OTA doesn't replace the bootloader. It patches the existing BL with the deltas - I.e. the code that have changed. Obviously the bootloader must be the exact expected version for a patch to work, so it is definitely being checked when you install an OTA, no matter what method you use..
If you patched the BL with an incorrect patch, you could very easily be facing a brick.
Then I'm guessing the people that were able to sideload the OTA with the new bootloader got lucky or are talking a bunch of BS (totally possible). I haven't tried it myself but I know for sure that the stock recovery is needed to sideload the OTA since 5.0 and the error reported earlier by some could be because of the recovery installed.
You definitely need stock recovery, yes
Since I have never updated my bootloader, I'm inclined to think it must be recovery. I was trying to sideload via TWRP.
doitright said:
[snip]
ONCE IT IS UNLOCKED, IT IS UNLOCKED. DON'T EVER LOCK IT AGAIN.
Click to expand...
Click to collapse
There are many reasons that people want to have a locked bootloader, such as, among many other reasons, your employer requires it, for example.
rootSU said:
It is. OTA doesn't replace the bootloader. It patches the existing BL with the deltas - I.e. the code that have changed. Obviously the bootloader must be the exact expected version for a patch to work, so it is definitely being checked when you install an OTA, no matter what method you use..
If you patched the BL with an incorrect patch, you could very easily be facing a brick.
Click to expand...
Click to collapse
No, OTA updates do not verify which bootloader your device is running, and they do NOT patch the bootloader -- they fully replace it.
android_mp99 said:
Then I'm guessing the people that were able to sideload the OTA with the new bootloader got lucky or are talking a bunch of BS (totally possible). I haven't tried it myself but I know for sure that the stock recovery is needed to sideload the OTA since 5.0 and the error reported earlier by some could be because of the recovery installed.
Click to expand...
Click to collapse
rootSU said:
You definitely need stock recovery, yes
Click to expand...
Click to collapse
You can use TWRP as well. It just requires an edit to one line in the updater-script file.
efrant said:
There are many reasons that people want to have a locked bootloader, such as, among many other reasons, your employer requires it, for example.
No, OTA updates do not verify which bootloader your device is running, and they do NOT patch the bootloader -- they fully replace it.
Click to expand...
Click to collapse
Yes you're right, my mistake.
efrant said:
You can use TWRP as well. It just requires an edit to one line in the updater-script file.
Click to expand...
Click to collapse
You need to have stock recovery to apply a stock ota. You could edit the updater-script for any amount of purposes, but that isn't really the point. The people who simply want to "check for updates" and use the standard mechanism to apply it, it will not work with twrp.
rootSU said:
You need to have stock recovery to apply a stock ota. You could edit the updater-script for any amount of purposes, but that isn't really the point. The people who simply want to "check for updates" and use the standard mechanism to apply it, it will not work with twrp.
Click to expand...
Click to collapse
Yeah, ok, but we were talking about sideloading the OTA, no? You can sideload an OTA update file (or even flash it directly from your device) using TWRP just by editing one line. But yes, as far as clicking on "check for updates" and having it install that way requires the stock recovery.
efrant said:
Yeah, ok, but we were talking about sideloading the OTA, no? You can sideload an OTA update file (or even flash it directly from your device) using TWRP just by editing one line. But yes, as far as clicking on "check for updates" and having it install that way requires the stock recovery.
Click to expand...
Click to collapse
You technically can. But then you edit the line, side load the ota via twrp, and immediately flash SuperSU to stop the updated system image from replacing the recovery.. It all seems a little pointless to me. If you're going to modify an ota (or download a modified ota) to side load from custom recovery rather than use a pre-rooted ROM.zip, it seems to add unnecessary steps.
Is it okay to flash the newest image (LMY74I) coming from LMY47O? I won't do any harm in skipping 5.0.1 will I?
Fastboot or recovery? Stock or custom rom? Best to fastboot the updated bootloader and radio if you are updating via custom recovery. I run stock and fastboot bootloader, radio, and system. Boot into recovery and then reboot. Before it reboots you will be prompted to install root. I use this updating method to keep my apps and settings.
mymusicathome said:
Fastboot or recovery? Stock or custom rom? Best to fastboot the updated bootloader and radio if you are updating via custom recovery. I run stock and fastboot bootloader, radio, and system. Boot into recovery and then reboot. Before it reboots you will be prompted to install root. I use this updating method to keep my apps and settings.
Click to expand...
Click to collapse
That didn't answer my question. I'm wondering if I can skip 5.0.1 stock and go straight to 5.1 still stock.
Forerunner326 said:
That didn't answer my question. I'm wondering if I can skip 5.0.1 stock and go straight to 5.1 still stock.
Click to expand...
Click to collapse
He couldn't answer your question because you were too vague. And still are.. What method are you using (now we know you're stock)? And will you be remaining unrooted?
rootSU said:
He couldn't answer your question because you were too vague. And still are.. What method are you using (now we know you're stock)? And will you be remaining unrooted?
Click to expand...
Click to collapse
Unrooted, stock, 5.0 LMY47O to 5.1 LMY47I still stock and unrooted. I am sorry for the confusion.
Forerunner326 said:
Unrooted, stock, 5.0 LMY47O to 5.1 LMY47I still stock and unrooted. I am sorry for the confusion.
Click to expand...
Click to collapse
If you're planning on unlocking the bootloader and flashing the full factory image then yes I that should be fine. Just a word of caution, relocking the bootloader has left some people in a bad place so do ensure if you just relock, that your phone is fully working and booting before hand.
rootSU said:
If you're planning on unlocking the bootloader and flashing the full factory image then yes I that should be fine. Just a word of caution, relocking the bootloader has left some people in a bad place so do ensure if you just relock, that your phone is fully working and booting before hand.
Click to expand...
Click to collapse
Is this because oem unlocking was unchecked for those people?
rootSU said:
If you're planning on unlocking the bootloader and flashing the full factory image then yes I that should be fine. Just a word of caution, relocking the bootloader has left some people in a bad place so do ensure if you just relock, that your phone is fully working and booting before hand.
Click to expand...
Click to collapse
Even if the device is rooted, all it will do is cause root to be lost correct?
Forerunner326 said:
Is this because oem unlocking was unchecked for those people?
Click to expand...
Click to collapse
See this post on relocking instructions:
http://forum.xda-developers.com/showthread.php?p=59699095
Forerunner326 said:
Even if the device is rooted, all it will do is cause root to be lost correct?
Click to expand...
Click to collapse
Yes but if its rooted, you'll never get OTA, so there's no point flashing the entire factory image.
If you flash the entire factory image and dont root, you'll get ota in future.
Though, I'm guessing g you'll be impatient anyway so its will be irrelevant. In which case since you'll probably just want to flash yourself and be rooted, why bother flashing the entire factory image? You dont need to flash recovery or bootloader... Just flash radio, system and boot.
rootSU said:
Yes but if its rooted, you'll never get OTA, so there's no point flashing the entire factory image.
If you flash the entire factory image and dont root, you'll get ota in future.
Though, I'm guessing g you'll be impatient anyway so its will be irrelevant. In which case since you'll probably just want to flash yourself and be rooted, why bother flashing the entire factory image? You dont need to flash recovery or bootloader... Just flash radio, system and boot.
Click to expand...
Click to collapse
so if you are rooted on 5.0 stock and unlocked bootloader and no custom recoveries. How do you install the 5.1 update without losing everything?
theDXT said:
so if you are rooted on 5.0 stock and unlocked bootloader and no custom recoveries. How do you install the 5.1 update without losing everything?
Click to expand...
Click to collapse
Flash everything from the factory image except the userdata.img
I got my MotoX about a year ago, non-dev edition on VZW. I installed Hashcode's SafeStrap custom recovery and flashed Kryptonite's "stock" 4.4.2 rom to the stock slot. That satisfied me for the time being and I lost track of current development on the Moto X.
I've been itching for a change though and a software update is just the fix. Since I haven't kept up thoug, I really don't know how to go about it. I've been reading about the options but I don't know where my phone stands. Can I go the CM11-> CM12 route with Safestrap even though my bootloader is locked? Or do I need to use SunShine to unlock my bootloader and install a different custom recovery? And do I need to revert to stock to stock at any point? I'm pretty comfortable with all of this, I just need some nudging in the right direction.
llsmith said:
I got my MotoX about a year ago, non-dev edition on VZW. I installed Hashcode's SafeStrap custom recovery and flashed Kryptonite's "stock" 4.4.2 rom to the stock slot. That satisfied me for the time being and I lost track of current development on the Moto X.
I've been itching for a change though and a software update is just the fix. Since I haven't kept up thoug, I really don't know how to go about it. I've been reading about the options but I don't know where my phone stands. Can I go the CM11-> CM12 route with Safestrap even though my bootloader is locked? Or do I need to use SunShine to unlock my bootloader and install a different custom recovery? And do I need to revert to stock to stock at any point? I'm pretty comfortable with all of this, I just need some nudging in the right direction.
Click to expand...
Click to collapse
If you NEVER took the 4.4.4 OTA you might want to consider unlocking your bootloader via "Sunshine" Then you can flash CM or anything you want with a real recovery and not safestrap. Just know that unlocking your bootloaer on a reatail device will void your warranty.
Travisdroidx2 said:
If you NEVER took the 4.4.4 OTA you might want to consider unlocking your bootloader via "Sunshine" Then you can flash CM or anything you want with a real recovery and not safestrap. Just know that unlocking your bootloaer on a reatail device will void your warranty.
Click to expand...
Click to collapse
Right, my phone has never seen 4.4.4. So I'm going to go ahead and use Sunshine to unlock my boot loader as the first step. The warranty I'm not too concerned about.
I guess the next question is how do I go about replacing safestrap with TWRP? Is it the same as installing TWRP from stock?
llsmith said:
Right, my phone has never seen 4.4.4. So I'm going to go ahead and use Sunshine to unlock my boot loader as the first step. The warranty I'm not too concerned about.
I guess the next question is how do I go about replacing safestrap with TWRP? Is it the same as installing TWRP from stock?
Click to expand...
Click to collapse
You should be familiar with flashing a custom recovery via adb if you have used TWRP on other devices. Once you have the bootloader unlocked you would need the correct recovery image of TWRP for the Moto X and then in bootloader mode use the command "fastboot flash recovery 'recovery.img'" where 'recovery.img' is the exact name of the file. If it flashed and it works properly then you could flash CM12 and Safestrap should be gone if you followed the flashing directions exactly. Don't forget to make a Nandroid of your current setup before you begin! Factory Resetting the device would be crucial if jumping from one ROM to another so it kind of takes care of itself.
I have the Amazon variant of the 16gb Blu R1 HD. I installed TWRP with the Unlock Tool for all versions tutorial (https://forum.xda-developers.com/r1-hd/how-to/unlock-tool-t3561333) on this forum and also removed ads. I would like to get back to the stock bootloader and image for my phone, to receive OTA updates and have the original experience, I am alright with having the ads back, I would just like my phone the exact same way it came from the factory. I know the updated roms will be ported and etc. I would like it back as the way it came, ads and all. (I'm aware I will not get my warranty back.) I read this tutorial: https://forum.xda-developers.com/r1-hd/how-to/firmware-amazon-blu-r1-hd-t3428197 but I'm not sure if it will work with TWRP, I'm confused whether or not fastboot works with TWRP installed. I would also like the bootloader to be locked again as well, I'm not sure whether or not flashing stock firmware would do this. If anyone could help explain this to me or point me to a tutorial somewhere it would be appreciated. I searched through the forum for similar entries, I didn't find anything for the R1 HD specifically, and entries for other phones on removing twrp/flashing stock recovery didn't seem to make sense. I apologize if I missed another post concerning this issue. Thanks.
Ladyslayer said:
I have the Amazon variant of the 16gb Blu R1 HD. I installed TWRP with the Unlock Tool for all versions tutorial (https://forum.xda-developers.com/r1-hd/how-to/unlock-tool-t3561333) on this forum and also removed ads. I would like to get back to the stock bootloader and image for my phone, to receive OTA updates and have the original experience, I am alright with having the ads back, I would just like my phone the exact same way it came from the factory. I know the updated roms will be ported and etc. I would like it back as the way it came, ads and all. (I'm aware I will not get my warranty back.) I read this tutorial: https://forum.xda-developers.com/r1-hd/how-to/firmware-amazon-blu-r1-hd-t3428197 but I'm not sure if it will work with TWRP, I'm confused whether or not fastboot works with TWRP installed. If anyone could help explain this to me or point me to a tutorial somewhere it would be appreciated. I searched through the forum for similar entries, I didn't find anything for the R1 HD specifically, and entries for other phones on removing twrp/flashing stock recovery didn't seem to make sense. I apologize if I missed another post concerning this issue. Thanks.
Click to expand...
Click to collapse
this is not quite a normal request.
any and all changes done to your phone are done at your own risk, no guarantee that the process will be "safe". and no guarantee the end result will be as expected.
I can upload stock system, boot, and recovery images.
download them, unzip the file. put the 3 .img files to the phone.
reboot phone to twrp.
select install, browse to the folder you loaded files to, you should not see the file yet. Select flash image in lower part of screen. Now select system.img, on next screen select system and swipe to confirm.
when done do same for boot.img to boot
then recovery to recovery
when all three are done do a wipe(factory reset)
this should bring you back to prime v6.1
be advised that re-locking the boot loader has potential of bricking the pone so it is not advised to do it.
also on all the early versions there are reports that after ota update with unlocked bootloader it caused a bootloop most times it was recoverable by performing "oem unlock" again.
once booted to v6.1 I suspect there will be proper update notice. but if not here is a list of the official update download links.
6.1 to 6.4
http://hwfotadown.mayitek.com/ota/r....4_GENERIC_6.0_20160710-00151468612925207.zip
6.4 to 6.5
http://hwfotadown.mayitek.com/ota/r....5_GENERIC_6.0_20160729-21551470255454500.zip
6.5 to 6.6
http://hwfotadown.mayitek.com/ota/r....6_GENERIC_6.0_20160823-20201472826184648.zip
7.4.2 to 8.4
http://hwfotadown.mayitek.com/ota/r..._V8.4_GENERIC_6.0_20170505-18551493981392.zip
17 to 21
http://hwfotadown.mayitek.com/ota/r...RIC_6.0_20170505-17451495815395129/update.zip
==>>V6.1 images.zip
.
.
@Ladyslayer
Can you tell your experience to restore phone to original condition?
Were you able to avoid bootlop and relock bootloader?
After development ceased I also wanted to restore my phone to original factory state but following restore guides leaves my phone in bootloop. BTW in @rootjunky thread there are all original 6.1 partitions that is if you feel brave and lucky, myself am scared to flash these.
@mrmazak
I think warnings in guides are misleading. Most people are aware of risks to flash modified firmware but they are not aware there is no way to restore phone to original firmware once they modify phone.
No intention to criticize you. Thank you for your effort to keep modified firmwares up to date. Looks like you are only one not giving up
kfn said:
@Ladyslayer
Can you tell your experience to restore phone to original condition?
Were you able to avoid bootlop and relock bootloader?
After development ceased I also wanted to restore my phone to original factory state but following restore guides leaves my phone in bootloop. BTW in @rootjunky thread there are all original 6.1 partitions that is if you feel brave and lucky, myself am scared to flash these.
@mrmazak
I think warnings in guides are misleading. Most people are aware of risks to flash modified firmware but they are not aware there is no way to restore phone to original firmware once they modify phone.
No intention to criticize you. Thank you for your effort to keep modified firmwares up to date. Looks like you are only one not giving up
Click to expand...
Click to collapse
well you can go back to locked but it is tricky. Think of it like this.
unlocking , allows anything you put on phone to try and load.
when you re-lock it only properly signed images are allowed to load.
so you can potentially lock yourself out of allowing phone to boot up, so the warning is more relevant when trying to go back to a locked state.
kfn said:
@Ladyslayer
Can you tell your experience to restore phone to original condition?
Were you able to avoid bootlop and relock bootloader?
After development ceased I also wanted to restore my phone to original factory state but following restore guides leaves my phone in bootloop. BTW in @rootjunky thread there are all original 6.1 partitions that is if you feel brave and lucky, myself am scared to flash these.
@mrmazak
I think warnings in guides are misleading. Most people are aware of risks to flash modified firmware but they are not aware there is no way to restore phone to original firmware once they modify phone.
No intention to criticize you. Thank you for your effort to keep modified firmwares up to date. Looks like you are only one not giving up
Click to expand...
Click to collapse
Sorry guys I have yet to try it out, I don't have a lot of time and am a little nervous to bite the bullet. @kfn, did you follow the guidelines in the above post to restore to original condition or a different set of instructions from somewhere else? Btw any suggestions on how to back up pretty much everything? Sorry Noob here obviously.
I flashed 3 original partitions system, boot, recovery as described by mrmazak then I took OTA update. After OTA update phone was in bootloop. I did not bother with backup because I do not have important data on phone.
kfn said:
I flashed 3 original partitions system, boot, recovery as described by mrmazak then I took OTA update. After OTA update phone was in bootloop. I did not bother with backup because I do not have important data on phone.
Click to expand...
Click to collapse
Which version update was it?
I can't be certain about the 8.4 or 21 updates, but older ones when that happened you needed to boot into fastboot mode and do oem unlock again.
kfn said:
I flashed 3 original partitions system, boot, recovery as described by mrmazak then I took OTA update. After OTA update phone was in bootloop. I did not bother with backup because I do not have important data on phone.
Click to expand...
Click to collapse
Did you re-lock the bootloader or was this because of an unlocked bootloader?
It was a quite a while ago, got 3 partitions from ColtonDRG's thread:
https://forum.xda-developers.com/r1-hd/how-to/guide-convert-to-prime-rollback-ota-t3432499
I downloaded from his website, I believe they were 6.1 versions.
At the time 7.4.2 was current firmware, I think phone rebooted few times taking OTA updates. And yes 'fastboot oem unlock' trick worked to get rid off bootloop.
I presume fastboot oem lock might relock bootlader but got scared to try it because of bootloop.
kfn said:
It was a quite a while ago, got 3 partitions from ColtonDRG's thread:
https://forum.xda-developers.com/r1-hd/how-to/guide-convert-to-prime-rollback-ota-t3432499
I downloaded from his website, I believe they were 6.1 versions.
At the time 7.4.2 was current firmware, I think phone rebooted few times taking OTA updates. And yes 'fastboot oem unlock' trick worked to get rid off bootloop.
I presume fastboot oem lock might relock bootlader but got scared to try it because of bootloop.
Click to expand...
Click to collapse
Do you still have the phone? Have you done the OTA updates since then with an unlocked bootloader?
did not try another OTA, put back modified ROM and disabled OTA.
Here post #312 with similar unanswered question about relocking bootloader, it is unclear for me if another OTA would properly relock it without bricking.
https://forum.xda-developers.com/r1...tock-rom-6-5-flashed-via-twrp-t3455532/page32
@mrmazak, do you know whether or not installing OTA updates would relock the bootloader? Wouldn't it be possible to do fastboot OEM lock and then do OTA updates without the risk of a bootloop? Noob question: does locking the bootloader reset the phone as well? I seem to have read something about this but I can't remember.
Ladyslayer said:
@mrmazak, do you know whether or not installing OTA updates would relock the bootloader? Wouldn't it be possible to do fastboot OEM lock and then do OTA updates without the risk of a bootloop? Noob question: does locking the bootloader reset the phone as well? I seem to have read something about this but I can't remember.
Click to expand...
Click to collapse
The update has not relocked the bootloader before.
Let me clearify a little.
There are three things I know that get changed when doing OEM unlock
1. Unlock status changed to a yes
2. Secure status changed to a no
3. Warranty status changes to no
After an ota #2 above( secure ) changes back to yes
This conflict is what makes the boot loop. As far as I know.
I do not know what it does when put back to lock and you do an ota.
I think each time you change, lock or unlock it needs to be reset the phone.
mrmazak said:
The update has not relocked the bootloader before.
Let me clearify a little.
There are three things I know that get changed when doing OEM unlock
1. Unlock status changed to a yes
2. Secure status changed to a no
3. Warranty status changes to no
After an ota #2 above( secure ) changes back to yes
This conflict is what makes the boot loop. As far as I know.
I do not know what it does when put back to lock and you do an ota.
I think each time you change, lock or unlock it needs to be reset the phone.
Click to expand...
Click to collapse
Wouldn't it change number one to a no, and two to a yes? What is the likelihood of a bootloop out bricking the phone if I re-lock the bootloader or do an OTA with the bootloader relocked? Isn't that the same as doing a normal OTA with a phone that had no changes from factory version, just the warranty status is a no and that's it?
Ladyslayer said:
Wouldn't it change number one to a no, and two to a yes? What is the likelihood of a bootloop out bricking the phone if I re-lock the bootloader or do an OTA with the bootloader relocked? Isn't that the same as doing a normal OTA with a phone that had no changes from factory version, just the warranty status is a no and that's it?
Click to expand...
Click to collapse
I do not know for sure. And there fore cannot recommend to do it. In the event something goes wrong and bootloader is locked, you cannot use fastboot to flash a repair, there fore MY opinion is the same "DO NOT relock bootloader". If something goes wrong it will be a brick.
Run stock version un modified all you want but if you unlocked I do not think you should relock. My opinion, do as you want.