In case I can't solve the whole SIM problem I need to get the phone back to my carrier and get it repaired/replaced so I have to get it back to carrier stock and lock the bootloader. But how do I install a ROM extracted from Update Extractor? Maybe someone has the syntax for a batch file to do it?
Update extractor will produce .img files. You need to follow the steps listed in Chapter 4: Unbricking from: https://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994
You will need fastboot (and fastboot drivers if using Windows) installed.
It's up to your provider to decide if they still offer a warranty. Unlocking the bootloader voids the warranty, and re-locking will show that the bootloader has been previously unlocked.
Related
I just wanted to report that I successfully re-locked my bootloader (did not find that here).
I have an H850 with GPS problems. To return it I wanted it to be as stock as possible.
I used TWRP to flash LG-H85010E-Flashable.COMPLETE.zip from Codefire. Back to unrooted.
I also tried to flash recovery.img from the same source. This seemed to work (no more TWRP), but did not allow for OTAs (update error 0x1125000).
Then I put the phone in download mode, started LG bridge and did the "Updatefehler korrigieren" thing (German, roughly translates to "correct update errors").
To re-lock the bootloader, I put the phone in USB Debugging mode and entered the following commands:
Code:
adb reboot bootlaoder
fastboot oem lock
fastboot reboot
The phone gets wiped by this, but you need to do the initial dialog again: enable developer mode, then go there an disable OEM unlock. After that do a factory data reset one last time.
You should contact @autoprime and have him add this to his all in one thread.
Thanks for the info!
@bornheim2
It's good to see that we have option to turn back to stock, and maybe send phone for warrianty repair. But I have one question... If you had tried to unlock phone once again, would You had to enter LG Unlock Code again?
Hazard17 said:
If you had tried to unlock phone once again, would You had to enter LG Unlock Code again?
Click to expand...
Click to collapse
Obviously. The command to unlock is
Code:
fastboot flash unlock unlock.bin
which means you need to have the unlock.bin file available. You did archive the mail, didn't you?
bornheim2 said:
Obviously. The command to unlock is
Code:
fastboot flash unlock unlock.bin
which means you need to have the unlock.bin file available. You did archive the mail, didn't you?
Click to expand...
Click to collapse
I haven't unlocked my phone yet, but it is important message for me.
bornheim2 said:
Obviously. The command to unlock is
Code:
fastboot flash unlock unlock.bin
which means you need to have the unlock.bin file available. You did archive the mail, didn't you?
Click to expand...
Click to collapse
No I didn't archive the mail
I've got the same problem - seller deceived me and sold phone after water damage. My microphone stopped work and I should send it back. How to lock the bootloader on RS988 model?
I have a doubt that,In some of the devices we can install twrp using adb commands without rooting our device. But in many new generation devices there are always posts or videos about, first rooting the devices and then installing twrp.
So, what are the reasons that we don't directly flash twrp on moto g5 using adb commands, and first we prefer getting device unlocked by getting unlock code.
And for my general doubt can anyone please explain me what does "unlocking a bootloader" means and what does "OEM" means. Also if i unlock OEM using developer options it doesn't show up in the bootloader menu.
I request to please explain elaborately as I am just new to all this.
To flash Twrp you need unlocked bootloader. Rooting has nothing to do with it, that is OS side. If bootloader is unlocked, you can fastboot flash Twrp. However, I suggest if you are unsure but want to have custom ROMs, you should use the tool that does it all for you.
https://forum.xda-developers.com/g5-plus/development/toolkit-moto-g5-plus-toolkit-root-t3605203
This tool will get your unlock information which you must submit on the moto unlock site. They will send you email with your bootloader key. Once you unlock bootloader through the tool, you can also flash twrp through the tool. When you have flashed twrp, you must wipe data in twrp and flash SuperSU to get past the data encryption. There is plenty of info around here on these subjects, I would suggest to read very carefully all the guides before continuing.
next ... After unlocking the bootloader of my g4 plus bike, I made the installation of the rom and an update arrived via ota ... I placed to make the installation and after made the cell phone hung up and did not call any more ... then I did the blankflash and the mobile came back in fastboot mode with the boot blocked again, now I can not install any rom and nor unblock the boot by not having the option oem unlock checked ... my question is the following have some way to enable the option unlock boot without starting the system, by adb or something, or do the installation of some rom with the boot blocked? Thank you very much in advance
Which ROM did you flash onto your device?
As far as I understand, you cannot enable the OEM unlocking option without booting to system, and as your bootloader is set to OEM_locked by the blankflash, you need to flash the stock ROM firmware to get your system working.
I'd suggest looking into flashing the latest stock ROM firmware, follow this unbricking guide here: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
If that doesn't work, then you may have to wait for a newer firmware or submit your device for an expensive service repair.
For future reference, if you did flash an older stock ROM firmware, please delete that and only flash stock ROM firmware as new or newer than your bootloader. If you do want to flash older stock ROM firmware, do not use OTA updates please. Old OTA updates corrupt your bootloader and thus lead to a hard brick.
I had hardbricked my devices while installing an OTA update and the device was Hardbricked .
I blank flashed the device and it booted and bootloader.
Now the problem starts here.
I flashed the OEM_Lock.bat as I wanted to relock the bootloader. I'm not sure what went wrong but the flash didn't complete and stuck in middle.
The problem remains here is it shows
Fastboot Reason: Failed to initialize partition table
I am unable to flash anything now. Recovery.img fails, bootloader.img fails, twrp flashing fails.
Nothing flashes as Bootloader is locked.
I went to Motorola Service Centre. They also couldn't do anything and simply said that their software doesnt read the phone.
Is there anyone whoe can really help me out with anything left to do?
Any method to force flash recovery, even twrp?
Phone is detected as Fastboot athene_16mp S in computer. It doesnt detect as "Qualcomm HS-USB QDLoader 9008".
What firmware are you attempting to flash?
Your device looks like it's still on the blank flash provided bootloader, which means you have to flash at least the GPT and bootloader. The lack of a serial number and the generic identifier implies you have not been able to flash an actual GPT and bootloader. Also, OEM_locked is normal until you get an actual bootloader flashed over the blank flash bootloader, which usually means trying to flash a GPT and bootloader at least as new as the latest version you had on your device (regardless of downgrades).
I'd suggest downloading the latest Nougat stock ROM we have from here. Do not use any of the scripts at this time.
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Unzip the file, delete any old stock ROMs from your ADB folder and copy over the new stock ROM. Try to flash just the GPT and bootloader then reboot to fastboot. See if you reboot into a fastboot screen with details.
If you do, I would proceed to flash the rest of the new ROM without locking your bootloader. If your device boots then, then you can reflash with the locking commands.
Edit - also, this post probably is better suited to the Q and A section...
echo92 said:
What firmware are you attempting to flash?
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Unzip the file, delete any old stock ROMs from your ADB folder and copy over the new stock ROM. Try to flash just the GPT and bootloader then reboot to fastboot. See if you reboot into a fastboot screen with details.
If you do, I would proceed to flash the rest of the new ROM without locking your bootloader. If your device boots then, then you can reflash with the locking commands.
Click to expand...
Click to collapse
The files in mentioned firmware did the trick. It flashed GPT and Bootloader and showed the needed info.:highfive: After that I flashed the same firmware via fastboot commands and device has booted to the stock 7.0 - Bootloader Unlocked. How crazy was I to ignore the proper files to flash? I probably tried 100 times to flash files (wrong once for sure). Thanks alot though for providing the link and instructions. :silly:
Now one last thing, should I flash OEM_Lock file to lock the bootloader so that I can get the lastest Oreo update? I might even think fo selling the device after locking the bootloader. Need your genuine opinion on this as well.
mysteryno46 said:
The files in mentioned firmware did the trick. It flashed GPT and Bootloader and showed the needed info.:highfive: After that I flashed the same firmware via fastboot commands and device has booted to the stock 7.0 - Bootloader Unlocked. How crazy was I to ignore the proper files to flash? I probably tried 100 times to flash files (wrong once for sure). Thanks alot though for providing the link and instructions. :silly:
Now one last thing, should I flash OEM_Lock file to lock the bootloader so that I can get the lastest Oreo update? I might even think fo selling the device after locking the bootloader. Need your genuine opinion on this as well.
Click to expand...
Click to collapse
Eh, you live and learn. Besides, you've now got your device running now!
Honestly, it's up to you. Having a locked or unlocked bootloader will not affect your ability to receive OTA updates - you should still receive updates so long as your firmware matches your software channel (and since your device was XT1643, the NPJS25.93-14-18 April 2018 security update should be the correct firmware). At this moment in time, you'll have to use the NPJS25.93-14-18 firmware to re-lock your bootloader - we don't have the stock Oreo firmware at this time. Thus, if you update to stock Oreo, you will not be able to re-lock your bootloader until you can get a leak of the Oreo firmware.
If you're selling, I'd choose to re-lock the bootloader. Else, a potential buyer who is not used to flashing custom ROMs might wonder if there's any tampering with the device (the bootloader unlocked warning, to someone not used to flashing custom firmware, might scare off potential buyers).
Back to Locked Bootloader, complete stock.
echo92 said:
Eh, you live and learn. Besides, you've now got your device running now!
If you're selling, I'd choose to re-lock the bootloader. Else, a potential buyer who is not used to flashing custom ROMs might wonder if there's any tampering with the device (the bootloader unlocked warning, to someone not used to flashing custom firmware, might scare off potential buyers).
Click to expand...
Click to collapse
I am back to Locked Bootloader as feel the same as you said that anyone buying might get scared by looking the warning sign. Thanks for helping out. :highfive:
Oreo Update via OTA has already started rolling out as per the news I've been reading. I just wanted to see the oreo 8.1 before I sell the phone.
Anyways I got a new device now, Realme C1, 3|32GB as my smartphone usage has declined a lot recently and might remain similar. This device will suffice my requirements.
Thanks for the help and support. :victory:
Disclaimer:I do not take responsibility for your bricked device. Try it at your own risk.
Notice:This guide is written mainly with these references:
Golv's Reply under Thread "NEW link add ...HTC U11 RUU 3.31.401.1 Dual sim"
paulpier007's GUIDE for Downgrading using HTC DevInfo Tool
Jason10246's Thread for Downgrading using hosd.img with RUU Decrypt Tool
Captain_Throwback's Thread for RUU Decrypt Tool
Introduction:
HTC started to use hosd partition to verify version number when you try to flash RUU since I do not know when for that I have been fairly unaware on HTC devices. A signature error 132 is returned when you try to downgrade with only a changed version number after reading Golv's downgrade guide. Which as a result I decided to write a new guide with a more general but not detailed guide for those with basic understandings of how to do this.
Requirements:
You have read those four threads above
RUU Decrypt Tool and Internet connection
RUU file that you would like to downgrade to
TWRP recovery
HTC adb and fastboot drivers installed and you have no issue finding your device in adb & fastboot
htc_fastboot
Steps:
Use RUU Decrypt Tool to decrypt your RUU using firmware option -f. You need internet connection to do this.
After completed, look for hosd.img in the output folder.
Change version number using Golv's method with HTC Version Tool. You can find it as the attachment.
Flash hosd.img file in bootloader, not download mode.
htc_fastboot flash hosd [pathToHosd.img]
Reboot to Download mode. If successful, the OS version will be the same as your RUU file that we would like to downgrade to.
Flash RUU in Download mode and it is done.
However, if your HTC U11 is the same as mine, Single SIM US Unlocked (WHL), you can just grab the 2.42.617.7 hosd.img that I extracted earlier which is in the attchments.