A month ago I unlocked the bootloader to get root access but i started getting troubles with some apps. Today i decided to return it to stock so i did what i used to do with my nexus devices that was to flash clean firmware(the one from the this forum) and re lock bootloader.
After the bootloader lock I got the message that my device was corrupted and wasn't able to boot. I used the Msmdownload tool to fix it. Everything was great until I realized there was no bootloader or modem versions in the bootloader. Also I am not getting the latest update.
TL;DR
Unlocked to root
Root caused problems
Factory reset, clean firmware flash, oem lock
Device corrupted message, no boot
MsmDownloadTool to unbrick.
Can boot into system
No boot or baseband version, no february update.
You faked up with restoring device after device is corrupted message
Richard_Black said:
A month ago I unlocked the bootloader to get root access but i started getting troubles with some apps. Today i decided to return it to stock so i did what i used to do with my nexus devices that was to flash clean firmware(the one from the this forum) and re lock bootloader.
After the bootloader lock I got the message that my device was corrupted and wasn't able to boot. I used the Msmdownload tool to fix it. Everything was great until I realized there was no bootloader or modem versions in the bootloader. Also I am not getting the latest update.
TL;DR
Unlocked to root
Root caused problems
Factory reset, clean firmware flash, oem lock
Device corrupted message, no boot
MsmDownloadTool to unbrick.
Can boot into system
No boot or baseband version, no february update.
Click to expand...
Click to collapse
I don't have either listed in my bootloader and received last update
---------- Post added at 09:40 PM ---------- Previous post was at 09:37 PM ----------
EugenStanis said:
You faked up with restoring device after device is corrupted message
Click to expand...
Click to collapse
So what is the correct method how I'd he mess up the restore. I used the msm tool just like I did on my op6t is there something new to do it correctly on op7tpro?
toolhas4degrees said:
So what is the correct method how I'd he mess up the restore. I used the msm tool just like I did on my op6t is there something new to do it correctly on op7tpro?
Click to expand...
Click to collapse
No, but in this case he should leave bootloader unlocked because relocking after unlock is buggy and somethins is corrupted like it was in my case and they had to replace mobo.
Related
I've had a lot of trouble upgrading to KitKat. After attempting to flash different image files for stock recovery/boot/system, I found it impossible to completely unroot the phone using the instructions posted because the phone kept re-rooting itself. Finally, I S-offed, wrote superCID, used the Telus RUU, applied the OTA downloaded to the phone, changed the CID back to GLOBA001 (my carrier is WindMobile). And finally! I know I relocked and unlocked the bootloader somewhere in the process, but I can't quite remember when.
Now, before I even think of re-rooting the phone or installing a custom recovery, I'd like to create a backup of the stock boot, recovery, and system. I tried running
Code:
fastboot boot openrecovery-twrp-2.7.1.1-zaracl.img
using the special KitKat TWRP. There's a message about boot.img being downloaded successfully but the phone reboots to a black screen.
I know that TWRP 2.7.1.0 downloaded from their website worked fine on my phone before I ran the RUU . So I'm not sure that the new TWRP is incompatible with my phone.
If I wanted to use adb instead, I'd need to root the phone before being able to pull the stock recovery, boot, and system images using adb shell. If I have to resort to rooting, is there any way to do so without flashing a custom recovery first? If there is, I might be able to unroot the phone afterward and make it stick. (Delete the supersu apk and su binary, right?)
I remember that the first time my phone attempted to download and apply the OTA automatically, my phone wiped itself. It was a lot of hard work to get it back to a usable state, but it was my own fault for not having a proper backup. I'd like to avoid making that mistake again, and have a stock backup handy on my computer in case there are carrier updates for my phone in the future.
To re-iterate, possible to back up stock everything without root? If not, possible to root without installing custom recovery?
You can no longer boot into a custom recovery, you have to actually flash it.
As far as having the stock recovery and boot, those are actually inside the OTA so you can pull it from there.
Since you'll have the stock recovery already, you can flash TWRP and use that to backup boot and system.
When you need to go stock, just use TWRP to restore your backup and then manually flash the stock recovery.
Since you made the device S-OFF, I recommend that if you need to lock/unlock the bootloader that you use the commands in this thread versus using the htcdev method as that wipes the /data/preload/ folder (as part of its normal /data wipe) which includes a few stock apps.
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
EveKnight75 said:
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
Click to expand...
Click to collapse
Locking the bootloader won't do anything, it's only unlocking using the htcdev token that causes the data wipe. So if you haven't unlocked using the htcdev method since running the RUU you will still have the 2 - 3 apps.
I don't know if the /data/preload/ folder is a requirement for a successful OTA update or not but I checked inside my OTA zip for my phone and it does include the 3 items stored there for the VM variant.
The unlock was AFTER the RUU. I ran the RUU, then used the OTA to upgrade to KitKat, then unlocked the bootloader again. However, I didn't notice any apps disappearing and the OTA zip for Wind also has a /data/preload folder.
*Shrugs* Seems good enough to me. TWRP, here I come!
needing wind stock stuck with wind awsy amd wont connect
I have an unlocked desire 601 it finds only wind away I'm trying to get a backup of the stock Rom to flash it does anyone k ow if there any around or even a back up I can use to try to get my phone working on wind home
jayjsteez said:
I have an unlocked desire 601 it finds only wind away I'm trying to get a backup of the stock Rom to flash it does anyone k ow if there any around or even a back up I can use to try to get my phone working on wind home
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2804427
needing help for s-off
EveKnight75 said:
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
Click to expand...
Click to collapse
hey i have unlocked desire 601 but only says wind away and wont connect ive knoticed the wind version is the same as the other versions but im wondering do i need the wind rom in order for it to pick up the wind home i cant seem to find anywhere online the wind rom and everytime i try to s-off it saysfailed and ive followed everything is there any insite you could give me to help me with this issue if its fixable again my phone says wind away but wont connect to it and i need to get it working as its my only device and carrier i use thx
---------- Post added at 11:29 PM ---------- Previous post was at 11:16 PM ----------
EveKnight75 said:
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
Click to expand...
Click to collapse
hey i have unlocked desire 601 but only says wind away and wont connect ive knoticed the wind version is the same as the other versions but im wondering do i need the wind rom in order for it to pick up the wind home i cant seem to find anywhere online the wind rom and everytime i try to s-off it saysfailed and ive followed everything is there any insite you could give me to help me with this issue if its fixable again my phone says wind away but wont connect to it and i need to get it working as its my only device and carrier i use thx
-Duir- said:
You can no longer boot into a custom recovery, you have to actually flash it.
As far as having the stock recovery and boot, those are actually inside the OTA so you can pull it from there.
Since you'll have the stock recovery already, you can flash TWRP and use that to backup boot and system.
When you need to go stock, just use TWRP to restore your backup and then manually flash the stock recovery.
Since you made the device S-OFF, I recommend that if you need to lock/unlock the bootloader that you use the commands in this thread versus using the htcdev method as that wipes the /data/preload/ folder (as part of its normal /data wipe) which includes a few stock apps.
Click to expand...
Click to collapse
I don't understand how you can pull the stock recovery from the OTA. I thought OTA's are immediately installed, instead of stored untill you want to install it? So, how do you backup the stock recovery?
It is saved until you want to install. When it go finishes Downloading, just choose install later. And you will be able to copy it into other storage devices and extract files and what not. I'm not sure if it stores in internal or external I'm 80% sure external sd if you have one.
Sent from my HTC0P4E1 using XDA Free mobile app
So, long story short, I recently bought a Nexus 9 from ebay which arrived with factory reset protection.
I have spoken to both Google and HTC about the situation and both were of no real help except for saying a few things outright between them to give me good enough reason to believe one of two things.
That 1 - it is possible to flash factory images over a device with a locked bootloader
or 2 - it is possible to unlock the bootloader without having access to developer settings
Anyone have any experience with either of these possibilities?
https://developers.google.com/android/ota
Full OTA Images can be flashed onto devices with locked boot loaders.
You need to boot into recovery and select sideload update.
Yeah, I know how to do that, but that only goes for updates, doesn't it? I tried to sideload a previous build onto the tablet but it failed the procedure, so it doesn't really solve the issue and if I flash a more recent update I still get FRP :/ If I wanted to revert back to the 7.0, or even marshmallow, would that be possible? Or does that require an unlocked bootloader?
enriquejones666 said:
https://developers.google.com/android/ota
Full OTA Images can be flashed onto devices with locked boot loaders.
You need to boot into recovery and select sideload update.
Click to expand...
Click to collapse
Yeah, I know how to do that, but that only goes for updates, doesn't it? I tried to sideload a previous build onto the tablet but it failed the procedure, so it doesn't really solve the issue and if I flash a more recent update I still get FRP :/ If I wanted to revert back to the 7.0, or even marshmallow, would that be possible? Or does that require an unlocked bootloader?
BigDomTheFirst said:
Yeah, I know how to do that, but that only goes for updates, doesn't it? I tried to sideload a previous build onto the tablet but it failed the procedure, so it doesn't really solve the issue and if I flash a more recent update I still get FRP :/ If I wanted to revert back to the 7.0, or even marshmallow, would that be possible? Or does that require an unlocked bootloader?
Click to expand...
Click to collapse
Those are full ota images, same as factory image. Meaning full package.
BigDomTheFirst said:
Yeah, I know how to do that, but that only goes for updates, doesn't it? I tried to sideload a previous build onto the tablet but it failed the procedure, so it doesn't really solve the issue and if I flash a more recent update I still get FRP :/ If I wanted to revert back to the 7.0, or even marshmallow, would that be possible? Or does that require an unlocked bootloader?
Click to expand...
Click to collapse
Ah yes, now I see your predicament. Unfortunately, there is no "there" there. You do need an unlocked bootloader to wipe the system clean with a factory image, and as you noted, the Full OTA Image will recover you from a system that won't boot, but it won't get rid of FRP.
enriquejones666 said:
Ah yes, now I see your predicament. Unfortunately, there is no "there" there. You do need an unlocked bootloader to wipe the system clean with a factory image, and as you noted, the Full OTA Image will recover you from a system that won't boot, but it won't get rid of FRP.
Click to expand...
Click to collapse
Exactly Hence my questions as to how do the manufacturers wipe everything and flash the new image without unlocking the bootloader? Or will it always be a trade secret?...... Hmmmm
BigDomTheFirst said:
Exactly Hence my questions as to how do the manufacturers wipe everything and flash the new image without unlocking the bootloader? Or will it always be a trade secret?...... Hmmmm
Click to expand...
Click to collapse
did we ever fix this? my bootloader is locked and no os installed. Was trying to return to factory and went thru all the flashing steps successfully then at the end locked the bootloader. Now tablet says "for development purposes only not for production use" and boots back to fastboot. It will not reboot at all
Uncleheff said:
did we ever fix this? my bootloader is locked and no os installed. Was trying to return to factory and went thru all the flashing steps successfully then at the end locked the bootloader. Now tablet says "for development purposes only not for production use" and boots back to fastboot. It will not reboot at all
Click to expand...
Click to collapse
Never found out how they do this.... are you able to boot in to recovery? if you can do that you may be able to flash a recovery OTA through 'apply update from ADB'. Worth a shot
Uncleheff said:
did we ever fix this? my bootloader is locked and no os installed. Was trying to return to factory and went thru all the flashing steps successfully then at the end locked the bootloader. Now tablet says "for development purposes only not for production use" and boots back to fastboot. It will not reboot at all
Click to expand...
Click to collapse
If up dont mind my asking how did it get that way by just locking the bootloader? I was just about to flash stock and lock on my volantis, then read this...?
Bryanx86 said:
If up dont mind my asking how did it get that way by just locking the bootloader? I was just about to flash stock and lock on my volantis, then read this...?
Click to expand...
Click to collapse
definitely don't lock your bootloader. That is a horrible move and serves no purpose
madbat99 said:
definitely don't lock your bootloader. That is a horrible move and serves no purpose
Click to expand...
Click to collapse
I actually reflashed last factory stock image and relocked without issue. It is a horrible move, I agree...I already miss root, but it suits the purpose. Thanks for your reply.
Bryanx86 said:
I actually reflashed last factory stock image and relocked without issue. It is a horrible move, I agree...I already miss root, but it suits the purpose. Thanks for your reply.
Click to expand...
Click to collapse
it's only a bad move if you make a mistake and can't repair it because your bootloader is now locked. But if it goes well then you're all set.
I impulsively unlocked the boot-loader on my Mate 20 Pro last night because Funky Huawei was selling the codes for $20. Today I can't really think of a good reason I actually need the bootloader unlocked since I have no interest in rooting my phone and there are update methods for manually flashing firmware that don't require an unlocked bootloader. In fact, the tool posted on XDA for updating firmware with an unlocked bootloader apparently requires that you be rooted to use it.
Is there a way to relock the bootloader?
The only mention I could find in these threads was someone who said you need to factory reset the phone and then go back into fast-boot. I don't think the person who wrote that even tried it and that he was just making a generalization.
Does anyone know if there are actual steps that relock the bootloader without bricking the phone--which the e-recovery restore method might do since it will try to install an older firmware than is currently on my phone.
I might just keep it unlocked anyway but I was curious if there was a known relock method that works on this phone.
jhs39 said:
I impulsively unlocked the boot-loader on my Mate 20 Pro last night because Funky Huawei was selling the codes for $20. Today I can't really think of a good reason I actually need the bootloader unlocked since I have no interest in rooting my phone and there are update methods for manually flashing firmware that don't require an unlocked bootloader. In fact, the tool posted on XDA for updating firmware with an unlocked bootloader apparently requires that you be rooted to use it.
Is there a way to relock the bootloader?
The only mention I could find in these threads was someone who said you need to factory reset the phone and then go back into fast-boot. I don't think the person who wrote that even tried it and that he was just making a generalization.
Does anyone know if there are actual steps that relock the bootloader without bricking the phone--which the e-recovery restore method might do since it will try to install an older firmware than is currently on my phone.
I might just keep it unlocked anyway but I was curious if there was a known relock method that works on this phone.
Click to expand...
Click to collapse
Have a look at my post in thread below .. have done this method a few times and works for me.
https://forum.xda-developers.com/ma...ocking-bootloader-magisk-root-t3885422/page22
jhs39 said:
I impulsively unlocked the boot-loader on my Mate 20 Pro last night because Funky Huawei was selling the codes for $20. Today I can't really think of a good reason I actually need the bootloader unlocked since I have no interest in rooting my phone and there are update methods for manually flashing firmware that don't require an unlocked bootloader. In fact, the tool posted on XDA for updating firmware with an unlocked bootloader apparently requires that you be rooted to use it.
Is there a way to relock the bootloader?
The only mention I could find in these threads was someone who said you need to factory reset the phone and then go back into fast-boot. I don't think the person who wrote that even tried it and that he was just making a generalization.
Does anyone know if there are actual steps that relock the bootloader without bricking the phone--which the e-recovery restore method might do since it will try to install an older firmware than is currently on my phone.
I might just keep it unlocked anyway but I was curious if there was a known relock method that works on this phone.
Click to expand...
Click to collapse
Use dload method, but pba that will erase everything like your 1st setting of your phone. Phone will be locked again, FRP will still unlocked.
Sent from my LYA-L29 using Tapatalk
does dload method altso come with recovery_ramdisk fixed? for us that have modified it for root or twrp??
So that the device becomes out of the box like new?
Yes, recovery_ramdisk back to stock with dload method
Sent from my LYA-L29 using Tapatalk
i can confirm dload method lock back the bootloader.
i had install an alternate fw but was not satisfied cause too much features were not working, i used first erecovery to download official fw but unlock bl was still present. then i try dload and phone was completly reset with bl locked.
dload method isn't working for me. I extracted the UPDATE.APP from the firmware version that is currently installed on my phone (using the update_full_base version), created a dload folder on my external card, copied the UPDATE.APP into that folder and then did the dial code and selected update from memory card. My phone reboots and then I get an error that says that the update failed.
Do I need to use the UPDATE.APP from a specific build to get this to work?
I installed firmware via the Funky Huawei method. It seems to have relocked the bootloader because the warning about the bootloader being unlocked doesn't come up when the phone boots but the data on my phone wasn't erased. Can the bootloader be relocked without erasing all the data on the phone? If so this is the first I've heard of it.
jhs39 said:
I installed firmware via the Funky Huawei method. It seems to have relocked the bootloader because the warning about the bootloader being unlocked doesn't come up when the phone boots but the data on my phone wasn't erased. Can the bootloader be relocked without erasing all the data on the phone? If so this is the first I've heard of it.
Click to expand...
Click to collapse
Go to fastboot mode and check if bootloader is locked again.
Sent from my LYA-L29 using Tapatalk
ubersapian said:
Have a look at my post in thread below .. have done this method a few times and works for me.
https://forum.xda-developers.com/ma...ocking-bootloader-magisk-root-t3885422/page22
Click to expand...
Click to collapse
Will we able to reclaim warranty after relock? Anyway the service guys would be able to know that the bootloader was unlocked before?
Soo what is the legit way to relock the bootloader and the FRP?
is the FRP from stock/defualt locked?
Verstuurd vanaf mijn LYA-L29 met Tapatalk
Please take this as a curiosity, and don't try it at home?
It is easy and possible (almost the same procedure as on unlocked bootloader) install magisk on K20 and root it without unlocked bootloader.
On edl validated account u can via edl flash boot image and have root without unlock and wipe data.
But phone after ota stuck on bootlogo. And need edl flash.
But if you root it when waiting for unlock you can work with root and wait for unlock. And unlock it (and factory reset).
If someone need exaxcly procedure, write pm.
You will get "system has been destroyed" after flash boot-modified image, please dont post crap
Have you actually tried this?
---------- Post added at 10:29 AM ---------- Previous post was at 10:27 AM ----------
Because the last time I tried on Z2 plus it didn't boot. Bootloader actually checks for modified system image ohh booting and halts it when it senses bits are changed
You're guaranteed to get a hard brick and need that EDL authorised account a second time if you ever try this.
So yeah don't do it... If you want root/Magisk you have to unlock the bootloader, there's no way around it.
Hi, I'm trying to relock my phone but I can't get it to boot, 1 logo and Android logo below appear and then it shuts down and reboot to this screen again and finally I end up in recovery. If I unlock my phone I can get it to boot properly.
I suspect a wrong vbmeta. I'm on A14, I've searched everywhere trying to find the appropriate one, but no one works.
Any help?
Hi,
Did you read this one:
https://forum.xda-developers.com/t/stuck-on-red-dot-twrp-screen.4405605/
I had the same problem and tried everything but IMPOSSIBLE to relock bootloader.
Out of last hope, I tried to flash all the partitions of A17 with mtkclient but my phone was then completely bricked (couldnt even access to fastboot or the chinese error message)
Send it to oneplus customer service and they fixed it for free. It would be so nice to have an unbrick tool or a relock bootloader method (the one with mtkclient presented on this forum doesn't seem to work all the time)
JustMan said:
Hi,
Did you read this one:
https://forum.xda-developers.com/t/stuck-on-red-dot-twrp-screen.4405605/
Click to expand...
Click to collapse
Yes I read that but that's not exactly the same. I wasn't stuck at this boot logo, I mean the red dot. I was stuck "before".
Anyway I've fixed it.
I've fixed the problem.
Originaly I was rooted on A14. I've managed to update to A17 while rooted.
Then I relock the bootloader with the tutorial you can find on the forum.
I had multiple issues rooted. My phone seems much more stable now relocked.
I think all the issues I had where caused by inapropriate boot.img or vbmeta.img.
It can be tricky sometimes to find these files matching your oos version.
Anakill said:
I've fixed the problem.
Originaly I was rooted on A14. I've managed to update to A17 while rooted.
Then I relock the bootloader with the tutorial you can find on the forum.
I had multiple issues rooted. My phone seems much more stable now relocked.
I think all the issues I had where caused by inapropriate boot.img or vbmeta.img.
It can be tricky sometimes to find these files matching your oos version.
Click to expand...
Click to collapse
i have no problems all working as well. Did you re lock with Python method?
Mr.Vag said:
i have no problems all working as well. Did you re lock with Python method?
Click to expand...
Click to collapse
Yes python mtk.