Develop Bugs

[Q] Unlock Bootloader Wildfire S

I successfully rooted my Wildfire S 510e but still with S-On and then installed Cyanogen Mod7; I subsequently needed to get the network unlocked so I got the appropriate SIM unlock code and that works. However, every time the phone is rebooted I have to re-enter the SIM unlock code which is annoying. So I looked around and other users suggested I reinstall the stock Gingerbread ROM. I followed the instructions which included relocking the bootloader and then running an RUU.
The bootlocker worked but the RUU failed although the phone still works OK but when I select the Recovery option there's no menu just a red triangle; if I then hold the volume up key and the start button a restricted menu is displayed e.g. install a zip file option is not available.
I've tried the HTCdev Unlock Bootloader but that fails because the Cyanogen ROM doesn't match the expected stock ROM in the RUU.
Questions:
1. Is there a way to unlock the bootloader with Cyanogen Mod7 installed?
2. Can I get the full Recovery menu reinstalled?
Any other tips appreciated.
Thanks

Marnhullman said:
I successfully rooted my Wildfire S 510e but still with S-On and then installed Cyanogen Mod7; I subsequently needed to get the network unlocked so I got the appropriate SIM unlock code and that works. However, every time the phone is rebooted I have to re-enter the SIM unlock code which is annoying. So I looked around and other users suggested I reinstall the stock Gingerbread ROM. I followed the instructions which included relocking the bootloader and then running an RUU.
The bootlocker worked but the RUU failed although the phone still works OK but when I select the Recovery option there's no menu just a red triangle; if I then hold the volume up key and the start button a restricted menu is displayed e.g. install a zip file option is not available.
I've tried the HTCdev Unlock Bootloader but that fails because the Cyanogen ROM doesn't match the expected stock ROM in the RUU.
Questions:
1. Is there a way to unlock the bootloader with Cyanogen Mod7 installed?
2. Can I get the full Recovery menu reinstalled?
Any other tips appreciated.
Thanks
Click to expand...
Click to collapse
If you have installed cyanogenmod 7, then you have probably unlocked the bootloader and installed the recovery.............if the recovery doesn't show up, try flashing it again via fastboot
And NO, I won't tell you how to because there are countless threads on this all over the forum

Is My Phone Bricked?

Let me start by saying this forum has provided me with a ton of support in the past. There is so much information available here that I rarely have to start my own thread. Unfortunately, I have spent the past 18 hours looking for a solution to my current problem and have come up empty handed. I'm hoping some of you are savvy enough to help me out. I will try to provide as much information as possible to help diagnose the issue.
Device
HTC One M8
Carrier: AT&T
CID: CWS_001
Unlocked HTC Bootloader
S-On
I was previously running the stock ROM rooted (based on the above) simply to disable the AT&T bloatware. As of last week, AT&T began pushing the 4.4.4 update and I made the mistake of trying to install it not realizing my custom recovery (TWRP 2.7.1.0) would prevent it. Ever since this occurred, my phone has been doing strange things, i.e. random reboots and the "AT&T" logo in the upper left corner of the task bar would flash and disappear. It eventually got to the point where my phone was stuck in a constant boot loop and the only thing that would fix it was a factory reset from TWRP recovery. The phone would then act normal for about 24 hours and then the boot loop would start again.
I decided to try solving the issue by installing the GPE 4.4.3 ROM. I performed a complete wipe in TWRP (including system) and installed the GPE ROM via ADB/Fastboot. Everything was fine from this point and all apps/data synced after I logged into my Google account. Shortly after the phone booted, I was asked to install the GPE 4.4.4 update. It was at this point that I decided to load the stock recovery image so I could simply install the OTA update. Once again, no problems. Stock recovery flashed fine and I downloaded the 4.4.4 OTA update and rebooted the phone. The phone appeared to finish the install, but failed to boot. Now I cannot get past the HTC splash screen and I do not have a custom recovery.
The factory reset option from stock recovery does not help (still gets stuck at the splash screen) and for some reason my device is no longer recognized in Fastboot which prevents me from flashing a custom recovery. I thought it may have been a driver issue so I uninstalled and reinstalled HTC Sync Manager. I also tried manually uninstalling the drivers from the USB Root Hub, pulled the battery on my laptop, and allowed Windows 7 to auto update the drivers automatically. In each case, the drivers were successfully installed, but the phone is still not recognized in Fastboot (no devices listed). I even did a system restore on my laptop to a few days before the issue and the phone still isn't recognized by HTC Sync Manager or Fastboot.
The stock recovery bootloader displays the following information:
*** TAMPERED ***
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-INVALID_VER_INFO
OpenDSP-INVALID_VER_INFO
OS- (2.12..1700.1)
eMMC-boot 2048MB
Based on all of this, do I have any options or is my phone bricked?
1. Is there anything I can do so my device is recognized by ADB/Fastboot so I can flash a custom recovery?
2. Can I install a ROM from the SD card with the stock recovery? I currently have the GPE 4.4.3 ROM on my SD card, but the zip is not recognized by the stock recovery. Can I rename it to something else so it can be recognized and installed?
3. Because the phone is not recognized by Windows, I cannot use the RUU method. Are there any other ways to return my phone to stock without RUU?
Any help is greatly appreciated.

Swazi Samurai said:
Let me start by saying this forum has provided me with a ton of support in the past. There is so much information available here that I rarely have to start my own thread. Unfortunately, I have spent the past 18 hours looking for a solution to my current problem and have come up empty handed. I'm hoping some of you are savvy enough to help me out. I will try to provide as much information as possible to help diagnose the issue.
Device
HTC One M8
Carrier: AT&T
CID: CWS_001
Unlocked HTC Bootloader
S-On
I was previously running the stock ROM rooted (based on the above) simply to disable the AT&T bloatware. As of last week, AT&T began pushing the 4.4.4 update and I made the mistake of trying to install it not realizing my custom recovery (TWRP 2.7.1.0) would prevent it. Ever since this occurred, my phone has been doing strange things, i.e. random reboots and the "AT&T" logo in the upper left corner of the task bar would flash and disappear. It eventually got to the point where my phone was stuck in a constant boot loop and the only thing that would fix it was a factory reset from TWRP recovery. The phone would then act normal for about 24 hours and then the boot loop would start again.
I decided to try solving the issue by installing the GPE 4.4.3 ROM. I performed a complete wipe in TWRP (including system) and installed the GPE ROM via ADB/Fastboot. Everything was fine from this point and all apps/data synced after I logged into my Google account. Shortly after the phone booted, I was asked to install the GPE 4.4.4 update. It was at this point that I decided to load the stock recovery image so I could simply install the OTA update. Once again, no problems. Stock recovery flashed fine and I downloaded the 4.4.4 OTA update and rebooted the phone. The phone appeared to finish the install, but failed to boot. Now I cannot get past the HTC splash screen and I do not have a custom recovery.
The factory reset option from stock recovery does not help (still gets stuck at the splash screen) and for some reason my device is no longer recognized in Fastboot which prevents me from flashing a custom recovery. I thought it may have been a driver issue so I uninstalled and reinstalled HTC Sync Manager. I also tried manually uninstalling the drivers from the USB Root Hub, pulled the battery on my laptop, and allowed Windows 7 to auto update the drivers automatically. In each case, the drivers were successfully installed, but the phone is still not recognized in Fastboot (no devices listed). I even did a system restore on my laptop to a few days before the issue and the phone still isn't recognized by HTC Sync Manager or Fastboot.
The stock recovery bootloader displays the following information:
*** TAMPERED ***
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-INVALID_VER_INFO
OpenDSP-INVALID_VER_INFO
OS- (2.12..1700.1)
eMMC-boot 2048MB
Based on all of this, do I have any options or is my phone bricked?
1. Is there anything I can do so my device is recognized by ADB/Fastboot so I can flash a custom recovery?
2. Can I install a ROM from the SD card with the stock recovery? I currently have the GPE 4.4.3 ROM on my SD card, but the zip is not recognized by the stock recovery. Can I rename it to something else so it can be recognized and installed?
3. Because the phone is not recognized by Windows, I cannot use the RUU method. Are there any other ways to return my phone to stock without RUU?
Any help is greatly appreciated.
Click to expand...
Click to collapse
There is 2 methods to do an RUU. one is by putting the RUU on your sdcard and booting into the bootloader and waiting a few minutes then accepting the prompt to do it and 2 is the fastboot method. Since you have an SD card you could attempt the first one I listed. Make sure you don't change the name of the RUU and make sure you get the proper one for your phone.

S1L3nTShaDoWz said:
There is 2 methods to do an RUU. one is by putting the RUU on your sdcard and booting into the bootloader and waiting a few minutes then accepting the prompt to do it and 2 is the fastboot method. Since you have an SD card you could attempt the first one I listed. Make sure you don't change the name of the RUU and make sure you get the proper one for your phone.
Click to expand...
Click to collapse
Don't you have to be S-OFF or have a locked bootloader to run a RUU? I am unable to achieve either of those since my phone is not recognized by by ADB/Fastboot.
Also, because my most recent functioning ROM was GPE 4.4.3, would I still be able to run the stock AT&T RUU? I thought the partitions were different? I have the GPE RUU as well, but I don't think I can run that either without changing my CID and locking my bootloader.

Swazi Samurai said:
Don't you have to be S-OFF or have a locked bootloader to run a RUU? I am unable to achieve either of those since my phone is not recognized by by ADB/Fastboot.
Also, because my most recent functioning ROM was GPE 4.4.3, would I still be able to run the stock AT&T RUU? I thought the partitions were different? I have the GPE RUU as well, but I don't think I can run that either without changing my CID and locking my bootloader.
Click to expand...
Click to collapse
S-OFF not so sure about, locked bootloader, no you can have it unlocked. But you can try it anyways, the SD card method.
Yes you would be able to run it, I'm quite sure all you did was flash a GPE ROM. I believe all flashing the ROM does is give you a GPE ROM where as the GPE RUU would change all that and give you GPE phones firmware too.
On the off hand you did do a GPE RUU then I'm not sure.

S1L3nTShaDoWz said:
S-OFF not so sure about, locked bootloader, no you can have it unlocked. But you can try it anyways, the SD card method.
Yes you would be able to run it, I'm quite sure all you did was flash a GPE ROM. I believe all flashing the ROM does is give you a GPE ROM where as the GPE RUU would change all that and give you GPE phones firmware too.
On the off hand you did do a GPE RUU then I'm not sure.
Click to expand...
Click to collapse
I have heard it has to be one or the other. If S-OFF, the bootloader can be unlocked. If S-ON, the bootloader has to be locked.
I did not run the GPE RUU originally; I installed the ROM through custom recovery. I'm assuming that is a good thing based on your feedback.
Regardless, I haven't been able to try the SD method because the zip file I extracted from the RUU exe will not transfer to my SD card. I also tried downloading another user's bootable version and it won't transfer either. I have copied many other files to and from my SD card (even larger file sizes) without any issues. I have no clue what is going on now...

Swazi Samurai said:
I have heard it has to be one or the other. If S-OFF, the bootloader can be unlocked. If S-ON, the bootloader has to be locked.
I did not run the GPE RUU originally; I installed the ROM through custom recovery. I'm assuming that is a good thing based on your feedback.
Regardless, I haven't been able to try the SD method because the zip file I extracted from the RUU exe will not transfer to my SD card. I also tried downloading another user's bootable version and it won't transfer either. I have copied many other files to and from my SD card (even larger file sizes) without any issues. I have no clue what is going on now...
Click to expand...
Click to collapse
I formatted my SD card and was finally able to transfer the RUU. The bootloader begins to run the 0P6BIMG file, but it fails right after it starts parsing. I tried running it several times and the results were the same.
I really wish I could get ADB to recognize my phone so I can flash a custom recovery... When I plug my phone into a USB port, my computer makes a noise, the phone says "USB" next to Fastboot, and HTC Sync Manager begins to load. When HTC Sync Manager comes up, it says "HTC Sync Manager couldn't connect to your phone." Windows Device Manager also does not have anything listed for an Android device.
I've noticed when the phone is not powered on and simply charging from the USB port, an "HTC MTP Device" driver tries to install, but fails. Could this be the problem? I've tried plugging the phone into 3 different computers and they all get the MTP failure.

If you are coming from a GSM variant things get a little bit more complicated to install a GPE RUU, as the GPE HBoot is different from the GSM one and partition sizes are as well.
You have to be S-Off to install the proper firmware and prior to doing this, change the CID as well as the MID to a GPE one.
There is a full guide on this forum to convert your M8 from GSM to GPE, bit as I'm on the train at the moment I can't provide you the link right away.
Sent from my HTC One_M8 using XDA Free mobile app

HTCNerdYoda said:
If you are coming from a GSM variant things get a little bit more complicated to install a GPE RUU, as the GPE HBoot is different from the GSM one and partition sizes are as well.
You have to be S-Off to install the proper firmware and prior to doing this, change the CID as well as the MID to a GPE one.
There is a full guide on this forum to convert your M8 from GSM to GPE, bit as I'm on the train at the moment I can't provide you the link right away.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
I'm not specifically trying to install the GPE RUU at the moment. I had the stock GSM recovery installed based on my original CID and I'm trying to load the associated RUU.
I originally loaded GPE 4.4.3 with TWRP and downloaded the 4.4.4 update OTA from Google. Before restarting my phone and installing the update, I flashed the stock GSM recovery for CID CWS_001. This may have been what caused the issue initially when the phone tried to apply the update if it was looking for a GPE recovery.
I know I cannot install the GPE RUU because I'm S-ON and ADB does not recognize my device so I cannot change the MID or CID. At this point, I'm really just trying to get back to stock so I can start fresh.
Is it possible that when the 4.4.4 update tried to run, it associated my recovery with GPE and now that's why it will not install the stock RUU due to a mismatch? I'm really just guessing at this point.

Look here at post #28 and #30. http://forum.xda-developers.com/showthread.php?t=2717928&page=3 . Download that .zip template
I think you can put the TWRP recovery.img (it has to be renamed to recovery.img) inside the zip as directed, put it on the SD card and let the bootloader automatically detaect and flash it. Once its completed you would have to power down and remove it from the SD card otherwise it would try to update again next time you go into the bootloader. That should load a recovery from which you can flash a ROM.

3484jacks said:
Look here at post #28 and #30. http://forum.xda-developers.com/showthread.php?t=2717928&page=3 . Download that .zip template
I think you can put the TWRP recovery.img (it has to be renamed to recovery.img) inside the zip as directed, put it on the SD card and let the bootloader automatically detaect and flash it. Once its completed you would have to power down and remove it from the SD card otherwise it would try to update again next time you go into the bootloader. That should load a recovery from which you can flash a ROM.
Click to expand...
Click to collapse
I'll give that a try and report back. Thanks for the input.

3484jacks said:
Look here at post #28 and #30. http://forum.xda-developers.com/showthread.php?t=2717928&page=3 . Download that .zip template
I think you can put the TWRP recovery.img (it has to be renamed to recovery.img) inside the zip as directed, put it on the SD card and let the bootloader automatically detaect and flash it. Once its completed you would have to power down and remove it from the SD card otherwise it would try to update again next time you go into the bootloader. That should load a recovery from which you can flash a ROM.
Click to expand...
Click to collapse
You are the freakin man!!! I edited the template from the post you suggested, added my MID/CID, and packaged it with the TWRP image. Booted right from the SD and I now have custom recovery! I wish I could buy you a beer!

No problem mate. Glad I could help. :thumbup::thumbup::beer:
Sent from my HTC One_M8 using XDA Free mobile app

[Q] SOLVED brick with chili peppers: Logo-hboot, NO os/rec/bl and can't install bl:(

Hai,
long time lurker here...
I've managed to get my hands on a Wildfire S, yet there are so many anomalies with it that now I'm turning to the collective...
Problem
Phone's seem only to be soft-bricked/non bricked, there is hboot, htc logo, but no OS and seemingly no bootloader either. Managed to charge its battery to the minimal level (around 3.86+) and can now freely enter into hboot.
I wanted to just install a quick recovery, some stable custom rom...now get very interesting
MARVEL PVT SHIP S-OFF RL
HBOOT-0.90.0000 (!)
RADIO.7.46.35.08
Apr 8 2011 etc
-When trying to install recovery through fastboot, it gives the error "NOT ALLOWED". Tried cwmod and twrp and a custom zip, no luck
-This made me think that loaders locked too, so I tried HTCDEV, but was unable to get the indentifier token and the hboot update was unsuccessful (written in several ways, just to be sure). ERROR: Command error!!!
-Also tried searching for custom firmware and bootloader unlock methods, but nearly all the links are offline by now...
...the phone seem to be unlocked and rooted, yet the hboot is ancient, there is no bootloader (it just shows the htc screen upon restart) and there is seemingly no way for me alone to find a solution to install anything
Any leads for the bootloader to work would be very much appreciated!!!! ty
UPDATE: solved possibly by trial and error:
1) try out
https://drive.google.c om/folderview?id=0B5cR4v1TTgVVOVRad0dNTERkcFU&usp= sharing these bootloaders through hboot as SD-card auto-install (fat32). Each time you update check whether the hboot FW and/or the logo screen is updated. Thats the one to stick with
2) Install
https://drive.google.co m/file/d/0B5cR4v1TTgVVOUppMVc4eTk1X0E/view?usp=sharing this all-in-one rom package through hboot/SDcard. Every time the filename must be "PG76IMG.ZIP" (its possible that this is all what you need as its installs the stock recovery along with the stock 2.3 rom
3) from there you can just install CWmod or TWRP via apk/market -> flash preferred custom

M9 s-off no OS

I have HTC M9 bootloader unlocked s-off CID 11111111 TWRP 2.8.7.0. I had tried to convert from android 6 to developer RUU with fastboot method found in ATT to developer edition forum that left me with no recovery or os. I was able to put TWRP 2.8 on with fastboot but more recent versions did not hold. I attempted to flash developer RUU (5,5.1,6) with TWRP and get "updating partition details...done,full selinux support is present,mtp enabled" then returns to TWRP main menu, reboot says no OS installed. Attempt with SD card/0pjaimng method with 5.0 RUU and bottom of screen showed file (filename) exit in yellow without ability to access, no other prompts. I am able to change CID (had started with developer Cid). Attempted to fastboot multiple versions of RUU and received file to large and several other messages. I am using a Macbook Pro OS X as computer. This is info displayed from download mode: ***unlocked***,HTC_himaulatt PVT s-off, CID-11111111, LK-1.0.0.0000,RADIO-01.01_U11440801_96.01.51207A_F, OpenDSP-15.6.1.00522.8994_1026, OS-3.38.502.12, Mar 23 2015,23:33:55(506785),
No meid listed on system info if that matters. Any ideas on getting to a working RUU would be appreciated. (I do not have easy access to PC)

THulbert said:
I have HTC M9 bootloader unlocked s-off CID 11111111 TWRP 2.8.7.0. I had tried to convert from android 6 to developer RUU with fastboot method found in ATT to developer edition forum that left me with no recovery or os. I was able to put TWRP 2.8 on with fastboot but more recent versions did not hold. I attempted to flash developer RUU (5,5.1,6) with TWRP and get "updating partition details...done,full selinux support is present,mtp enabled" then returns to TWRP main menu, reboot says no OS installed. Attempt with SD card/0pjaimng method with 5.0 RUU and bottom of screen showed file (filename) exit in yellow without ability to access, no other prompts. I am able to change CID (had started with developer Cid). Attempted to fastboot multiple versions of RUU and received file to large and several other messages. I am using a Macbook Pro OS X as computer. This is info displayed from download mode: ***unlocked***,HTC_himaulatt PVT s-off, CID-11111111, LK-1.0.0.0000,RADIO-01.01_U11440801_96.01.51207A_F, OpenDSP-15.6.1.00522.8994_1026, OS-3.38.502.12, Mar 23 2015,23:33:55(506785),
No meid listed on system info if that matters. Any ideas on getting to a working RUU would be appreciated. (I do not have easy access to PC)
Click to expand...
Click to collapse
Update- have been able to get TWRP 3.0 installed. Have been able to flash both ViperOne 1.9.1 and Android 5.0.2/HTC 7/ 1.32.617.30. Software update shows modified system, unable to update with both CID 11111111 and BS_US001. I am not getting wireless service and my IMEI, IMEI SV are blank, baseband version is unknown. Tried to repair with fastboot OEM writeimei #### but did not work. Still hoping for help. Thank you

What was the real cid and mid of the device ??

THulbert said:
Update- have been able to get TWRP 3.0 installed. Have been able to flash both ViperOne 1.9.1 and Android 5.0.2/HTC 7/ 1.32.617.30. Software update shows modified system, unable to update with both CID 11111111 and BS_US001. I am not getting wireless service and my IMEI, IMEI SV are blank, baseband version is unknown. Tried to repair with fastboot OEM writeimei #### but did not work. Still hoping for help. Thank you
Click to expand...
Click to collapse
I didnt know any M9 models were still using Android 5.x Lollipop. Oofta.
It will be important to know the original information about your phone - CID & MID would be great. Even better would be the original SKU.
For your information, SuperCID (11111111) is no longer useful - official software doesn't accept it and will fail to install on phones with it. Your CID and your MID must match the SKU of update (OTA) or RUU you are attempting to install.
By the way, are you using HTC fastboot or the Android fastboot? I wonder if the blank values you are getting for various fields is because the Android fastboot isn't entirely compatible with the M9. If you download HTC Sync Manager, that will install the HTC ADB tools (including fastboot).

SKU is 6735A. I was following instructions to set developer Cid to us_b001 , it is att brand US. Have not been able to get TWRP higher than 3.0.0 to flash successfuly. Haven't been able to find higher than 5.0 to flash successfully. Am using HTC sync manager adb and fastboot. Also tried using Flashify and TWRP manager apps but experienced errors with both.

THulbert said:
SKU is 6735A. I was following instructions to set developer Cid to us_b001 , it is att brand US. Have not been able to get TWRP higher than 3.0.0 to flash successfuly. Haven't been able to find higher than 5.0 to flash successfully. Am using HTC sync manager adb and fastboot. Also tried using Flashify and TWRP manager apps but experienced errors with both.
Click to expand...
Click to collapse
Your SKU is 6735A? That's nothing I've heard of before for the HTC One M9 - how did you gather this information? Your second sentence suggests that your phone is actually an AT&T branded M9. If that is correct, we can point you to the correct SKU and it's related software.

computerslayer said:
Your SKU is 6735A? That's nothing I've heard of before for the HTC One M9 - how did you gather this information? Your second sentence suggests that your phone is actually an AT&T branded M9. If that is correct, we can point you to the correct SKU and it's related software.
Click to expand...
Click to collapse
It is ATT branded. I had initially rooted it and had been using android 6. I got the SKU # printed on sticker on back of phone under imei and serial numbers. Thank you for helping.

THulbert said:
It is ATT branded. I had initially rooted it and had been using android 6. I got the SKU # printed on sticker on back of phone under imei and serial numbers. Thank you for helping.
Click to expand...
Click to collapse
A stick on the back of the phone under the IMEI & serial numbers? I don't have that on my model, but maybe that's because I bought the developer edition straight from HTC. I wonder if you are reading the SKU for AT&T's store (as in, the barcode they use for their own inventory to scan and sell the device), rather than the SKU of the phone OS. But that's beside the point - if it is indeed AT&T branded (USA), the phone's original SKU was 502. That's good information to know - both if you want to restore your phone to original software and to help you avoid incompatible software.
[EDIT]Sigh. I missed it in your original post, but your SKU is right there in the information you gave from download mode: OS-3.38.502.12. Sorry for the inconvenience.[/EDIT]
If your goal is to convert your phone to the developer edition, you'll need to change the CID and MID to match SKU 617. Follow the instructions in Q9 of the Flippy498's FAQ in the readme thread. Once you've done that, you can install the developer edition RUU.

RUU Problems Cant install OR get into Recovery :(

OK Got htc one m9, had stock software from 3UK rooted, TWRP installed. Then I installed AICP Oreo. Now I wish to return to stock. I relocked the bootloader & downloaded an ruu file. From that point as soon as the phone rebooted I can not enter TWRP, nor can I get adb access via PC. All I did was rename the ruu to 0PJAIMG.zip put in root of SD.Now I get a message when rebooted RU_CID_FAIL cid in android-info mismatched. Selecting Vol+ & Pwr gives me reboot to bl, download or recovery options. Selecting recovery gives a "failed to boot to recovery" message.Selecting download gives me the download menu." Googling doesnt really help me. Expert advice would be MASSIVELY appreciated
Update, unlocked bl again. Have AICP working again AND TWRP but still cant get back to stock grrrrr
Thanks
John

Check your cid and mid are correct for the file you are trying to flash.
There is always the fact you locked the bootloader with a custom recovery on it. You can only lock again if the phone is completely stock (except bootloader and s-off status).

shivadow said:
Check your cid and mid are correct for the file you are trying to flash.
There is always the fact you locked the bootloader with a custom recovery on it. You can only lock again if the phone is completely stock (except bootloader and s-off status).
Click to expand...
Click to collapse
Thank you. Yes you were spot on. I ended up unlocking the bl again and everything went smooth from there. Cheers