Related
im gona send my phone in as a replacement, but i want to make sure everything looks stock before it send it in, i found a couple of ways to return to stock but i keep getting signiture verified failed, and i assume its because i have an unlocked bootloader, can any 1 help?
You should be able to find the stock rom for unlocked users in the development section. Just flash that and you will be back on stock.
But you can't re-lock the bootloader. When you unlocked it you voided the warranty, and it stays that way.
If it is a physical hardware problem, you should be able to still get warranty though.
Sorry, I meant to say my bootloader is locked, I don't have a problem with the rom, but the recovery. I am on ra recovery atm and I want to go back to google's stock. Is there anyway to do that?
Im pretty sure this works for all phones but if you flash Official OTA it will put everything back to stock(except bootloader if it has been unlocked) but doing this you will also loose root as well
i would wait for some one to tell you another way to get back to stock recovery, im sure there is a way to do it in adb or something.. Flashing the official OTA should be like a last thing wanting to do
Look for the stock recovery Tom for your phone then just flash with fastboot. That's the easiest way that I. Did it.
sent from outter space
codearray said:
Look for the stock recovery Tom for your phone then just flash with fastboot. That's the easiest way that I. Did it.
sent from outter space
Click to expand...
Click to collapse
He cant do fastboot, he has locked Bootloader.
yeah, it saids verification failed and wouldnt let me flash anything onto it
oops my bad. I had an unlocked bootloader. My other phone is locked.
sent from outter space
vvaffles said:
yeah, it saids verification failed and wouldnt let me flash anything onto it
Click to expand...
Click to collapse
Yeah i had the same problem when i tried to revert mine to stock. My bootloader was lock and wouldnt let me reflash the stock rom with verification failed.
NOT SURE IF THIS IS THE CORRECT WAY, DO AT YOUR OWN RISK :
I renamed the image to PASSIMG.zip and booted into bootloader. The bootloader automatically searches for PASSIMG and when it found it went through an update/installing process which took about 5minutes. When it booted phone was unrooted again, and had the stock recovery.
Once that was done, i installed the FRF85 (i think) update.zip from bootloader recovery, then did the same with update.zip for FRF91.
Again not sure if this was the correct way as i have never seen posts directing to do it this way - have posted questions about it in the past week or two, but never got any responses...
I'm gonna bump this thread up again. I tried downloading the original PASSIMG file for the stock and when I try and flash it by putting it on the SD card I get that the main file is older and the install is aborted. I can't fastboot the files because my bootloader is not unlocked. I'm currently running a FRG83 based ROM, does this matter? I'd like to return my phone to stock recovery and stock ROM, but so far every attempt has been met in failure... I guess it's an irony of rooting a phone without unlocking a bootloader. If you have to send it in for repairs you have to unlock the bootloader to return to stock, or you can't return to stock and you're left with custom recovery and root... either way HTC knows you're rooted. I know my issue is a hardware issue, but it would be my luck they decide to void my whole warranty.
You can't just PASSIMG your way back from FRG83, if you have it - since there's no PASSIMG for FRG83 yet (at least I'm not aware of one, and looks like Google isn't either), and the system is designed not to flash older builds. Trying to use PASSIMG to return to older builds requires some heavy preparations (has to be rooted, then downgrading HBOOT and probably flashing initial system.img from an older build through adb in recovery, using flash_image). It's possible and not very hard to do, but most probably beyond "1-click-root"ers' skills. All the relevant info is in the Wiki, so if you want to attempt it - you can try.
Unrooting FRG83 (reflashing stock recovery from FRF91, removing su and Superuser.apk from root shell) might be easier.
Also, put attention that if the phone has SLCD screen - the official stock FRF91 won't work on it.
I actually was able to PASSIMG to FRG33 then OTA back to FRG83. which I thought was odd due to the fact that I was on a FRG83 based rom. Oh well, it's 100% back to stock now. So even though people say that a rooted/unlocked phone only voids your software warranty I don't have to worry about it. Yay for keeping a locked bootloader.
why I riisk to brit my phone if I install a new firmware? Why could SGS be unable to boot? Is it a problem wit the bootloader?
If you mess around with leaked or custom firmware there are any number of ways your phone could be bricked. That's why it is very important to do a lot of reading and follow instructions very carefully. Nothing is ever fool-proof and there's even risks with official firmwares.
you can brick your phone fully if you flash a bootloader and it fails. most of the time your phone is bricked you should be able to fix it by entering download mode.
do you know if there's a wiki that explains the bootloader in android, the partitions etc.?
Im curious
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 have followed the rooting, backup (drm keys), flash new firmware etc etc procedure. However every time i flash a custom rom and reboot it goes into brick. I mean no bootloop just flashing red led when on charger, i cant even get to recovery to restore.
then i have to do
Flash .105 kitkat stock firmware>giefroot>dualrecovery install.bat>flash new pre rooted firmware>try flashing custom rom again>BRICK>(return to start)^
i have unlocked bootloader, everything done, even when i try and restore drm keys i get bricked.
i have currently given up on custom roms and im living with crap camera, no custom rom.....nothing.
please help, send food n water
Help please
:crying:
Did you find a solution for this.this? I have the same problem. I don't know what to do.
thefanofmusic said:
Did you find a solution for this.this? I have the same problem. I don't know what to do.
Click to expand...
Click to collapse
This was a year old post, but I did manage to fix it, flash stock pre rooted firmwares, then u have lollipop rooted. It was my bootloader was locked or something
xpzx said:
This was a year old post, but I did manage to fix it, flash stock pre rooted firmwares, then u have lollipop rooted. It was my bootloader was locked or something
Click to expand...
Click to collapse
Oh OK. Thanks for replying . Damn but my bootloader is unlocked. No idea what I should do.
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.