Database Develop

[Q] Security Warning, Stuck In Bootloader...

Hello all,
This morning I decided to clear data/wipe as I wanted to install a new rom, but once I did that the device would not boot up anymore. Yes it was S-Off using the Alpharevx. After I saw that it would not boot up I thought I would try to restore it with the rom that I was using before the S-off (Sasktel Froyo). After flashing the rom I have been stuck in the bootloader with the msg ***Security Warning*** and not been able to fix it since.
I have extracted the rom.zip out of all the stock roms and renamed them PG32IMG but none of them would work... I googled to see if anyone else has had an issue like this and found that an HTC Thunderbolt went through the same thing and all you have to do is flash it with the firmware the phone came with. My Incredible S is from Bell Canada and I cannot find that RUU anywhere...
Can anyone please help me because I really don't know anything else that I can do... I am lost.
I am going to post the image of the bootloader so you guys can see what I am talking about...
Thanks for all your help, I appreciate it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

did you use an goldcard while flashing the PG32IMG.zip? because you will need this

I used a goldcard to flash the Sasktel rom initially, now when I try to flash Sasktel again it says "Main Version is older!". How can I do now when I am in the bootloader?
Is there the stock rom from Bell out by any chance?

When flash new recovery ,do not plug your device in USB.
Sent from my HTC Incredible S using XDA App

^ I have already tried that numerous times still no luck.
I don't understand why it will not boot up with Sasktel rom...
EDIT: Is there any way when the phone is in bootloader for Alpharevx to detect it so I can S-Off again? I believe that if I can S-off the phone again I can flash the other ROMs and install Clockwork again... Is that possible?

Anyone any idea?

try get a hold of one of the devs from alpharev, this goes beyond limits for this sections mate ;/

Hawkysoft said:
try get a hold of one of the devs from alpharev, this goes beyond limits for this sections mate ;/
Click to expand...
Click to collapse
Yes I already have, they have told me that the only way of fixing it is with an XTC clip. Luckily there is someone in my area willing to meet .
Thanks for your help.

An XTC clip is the best option for you...
You cant down grade an S-ON Phone with the goldcard !!! so i dont see ny options for ur case !! u should go with the words of the alpharevx developers !!!
__________________________________________________
[Status] Rooted S-OFF
[Recovery] 4EXTRecovery v 1.0.6 (A CWMR 4.0.0.2 Mod)
[ROM] CyanogenMod cm-7.1.0-RC0
[Theme] CyanogenMod
[Radio] 3805.04.03.22_M
[Hboot] 1.09.1000
[Case] Seidio Innocase Case

Contact the devs from alpha revx
please ask them for help,im sure they ll help u out , they have helped me a lot , one small request they might be busy so its better to ask before pinging them again and again...)...
http://webchat.freenode.net/?channels=alpharevx

telectroguy said:
please ask them for help,im sure they ll help u out , they have helped me a lot , one small request they might be busy so its better to ask before pinging them again and again...)...
http://webchat.freenode.net/?channels=alpharevx
Click to expand...
Click to collapse
Hey thanks for the help...
I met up with someone that tried to S-Off my phone with the XTC clip and that didn't even work. I think the only way to fix the phone is just wait it out until Bell releases their gingerbread update...

The phone has a froyo Rom but it is stuck with a gingerbread radio. That is why the original froyo Rom you went back to will not work. (Can't downgrade from gingerbread radio to froyo radio) Only option is to some how get a gingerbread Rom on your phone.
I don't think you can flash your phone with an RUU the normal way.(goldcard way)
Check this thread out. Info about flashing an RUU for the a Canadian Incredible S.
http://forum.xda-developers.com/showthread.php?p=15166814
Sent from my HTC Incredible S using XDA Premium App

I have the same problem is there a solution to this?

neo-X said:
I have the same problem is there a solution to this?
Click to expand...
Click to collapse
You have to flash the stock RUU the phone came with originally. That is the only way to fix it.

EDIT: Resolved, pm me if you want help claudiujer

neo-X maybe you should share the solution how you did it?

Hawkysoft said:
neo-X maybe you should share the solution how you did it?
Click to expand...
Click to collapse
I flashed the 6.03.03 radio in gu1dry's thread, but they are actually ruu's (i didn't know) and the "main version" in that ruu was 1400 (ieftm has now pointed it out to gu1dry). I then tried to be smart and downgrade to the optus rom which was a lower version which of course failed half way through but by that time it was too late.
I was however very lucky that the higher version RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1 was posted in Football's thread, so i decide to give it all one last shot. So i ran that ruu with a goldcard and i worked.
Claudiu, i can't reply to your PM for some reason. so just reply here (I think you've disabled PM's)
Claudiu, from command prompt run "fastboot getvar all" with your phone connected while in fastboot this will tell you what main version you are running, you are going to have to get an ruu that is higher than this version, otherwise it won't work.

neo-X said:
I flashed the 6.03.03 radio in gu1dry's thread, but they are actually ruu's (i didn't know) and the "main version" in that ruu was 1400 (ieftm has now pointed it out to gu1dry). I then tried to be smart and downgrade to the optus rom which was a lower version which of course failed half way through but by that time it was too late.
I was however very lucky that the higher version RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1 was posted in Football's thread, so i decide to give it all one last shot. So i ran that ruu with a goldcard and i worked.
Claudiu, i can't reply to your PM for some reason. so just reply here (I think you've disabled PM's)
Claudiu, from command prompt run "fastboot getvar all" with your phone connected while in fastboot this will tell you what main version you are running, you are going to have to get an ruu that is higher than this version, otherwise it won't work.
Click to expand...
Click to collapse
So all you did was run the RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1 and it worked?
I have done that so many times and it hasn't worked because I have the Bell IncS. I will try to flash the radio though and hopefully I will get something different...

ClaudiuJer said:
So all you did was run the RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1 and it worked?
I have done that so many times and it hasn't worked because I have the Bell IncS. I will try to flash the radio though and hopefully I will get something different...
Click to expand...
Click to collapse
So you've tried to run the RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1 ruu with a goldcard?
Did it fail, what was the the error message?

neo-X said:
So you've tried to run the RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1 ruu with a goldcard?
Did it fail, what was the the error message?
Click to expand...
Click to collapse
Actually I have't tried it yet because the download link is not working... Where did you download it from?

help please, i need help

I intent flash ics in my att vivid, but my phone bricked, then i want to back stock, i download ruu cingular, and when run the ruu say error 140 eroor bootloader. i need help please you sorry my english i dont speak and write well... i wait for your help.. tks...

I had the same problem. Error 140 means there's a corruption in the a cards data structure.
Did you unlock your bootloader?
Pm me with what you have done so far. I'll help as much as I can, but be forewarned you may need to replace your device regardless.
Sent from my HTC PH39100 using xda premium

discobritanics said:
I intent flash ics in my att vivid, but my phone bricked, then i want to back stock, i download ruu cingular, and when run the ruu say error 140 eroor bootloader. i need help please you sorry my english i dont speak and write well... i wait for your help.. tks...
Click to expand...
Click to collapse
When you run the ruu, you must re-lock your bootloader. Have you locked your bootloader?
Go to this thread, they have the tool you need to fix your phone:
http://forum.xda-developers.com/showthread.php?t=1498003
Hope it helps! Good Luck

you say it's bricked, but yet it goes into bootloader you can flash ruu?
i think you maybe misspoke, what happened exactly? can you show pictures?
error 140 bootloader version error is simple, it means that the main version is newer than the one you are trying to flash. since you flashed ics ruu, you cannot go back to gb ruu. you have to follow the guide here by thecubed
http://forum.xda-developers.com/showthread.php?t=1529669
if u can take pics first and show me what your phone is doing before you do anything else that will be better

Please don't make two separate threads in two different sections asking for the exact same thing.
Sent from my HTC PH39100 using xda premium

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

mod plz move to gen

ebaul said:
When you run the ruu, you must re-lock your bootloader. Have you locked your bootloader?
Go to this thread, they have the tool you need to fix your phone:
http://forum.xda-developers.com/showthread.php?t=1498003
Hope it helps! Good Luck
Click to expand...
Click to collapse
IIRC, you have to be able to boot the phone to get this method to work?
I'm having a similar problem and I tried the file from http://forum.xda-developers.com/showthread.php?t=1529669 to no avail, it doesn't say an error code it just reboots and goes black after HTC boot screen.
I think my problem started when I tried to flash the OTA from androidninjas; he put the ICS hboot on top and I was too excited to read so I d/l and flash the file (was named PH39IMG...) but when I went to boot it turned black. So I d/l and flash the new file, after using HBOOT to clear out the phone etc. Still no luck. And I've tried numerous GB ruu's as well as every ICS one I can find. Brick?
Definitely interested to hear the fix to this.

Before flashing ICS, did you relock your Hboot & were you running GB?
If your screen went dark, but can still get into hboot, you are fine. Just need a recovery. There is an error with the older standard CWM. So you need to install a new version of recovery.

GSLEON3 said:
Before flashing ICS, did you relock your Hboot & were you running GB?
If your screen went dark, but can still get into hboot, you are fine. Just need a recovery. There is an error with the older standard CWM. So you need to install a new version of recovery.
Click to expand...
Click to collapse
Yes to both and I thought relocking got rid of root? So I was afraid I wouldn't be able to flash a custom rom.

Moved to General sub section, please pay attention where you open a thread next time

htc vivid
My phone is similar, I unlocked and all, i got stuck booting...i relocked the phone,i loaded the PH39IMG.zip onto a sd card and booted from it, it says checking the image, next thing it does is update fail main version is older. any help would be appreciated

quepasakimosabe said:
My phone is similar, I unlocked and all, i got stuck booting...i relocked the phone,i loaded the PH39IMG.zip onto a sd card and booted from it, it says checking the image, next thing it does is update fail main version is older. any help would be appreciated
Click to expand...
Click to collapse
if it's locked..just boot to fastboot, plug the phone into your computer, and run the latest ruu. Then unlock

QHSUSB_DLOAD After upgrading firmware (Bricked).

Hello XDA. Today I was upgrading my phone's firmware since it was pretty outdated (I had 1.4.xxx firmware lol), so I downloaded a bunch of firmwares (See picture below) that were compatible with my phone (MID and CID), I installed each of them from the lowest version to the highest. Everything was going fine until I installed the 5.11.401.10 firmware, when I rebooted the phone the screen went completely black, I couldn't reboot it pressing Power + Vol up, plugging the phone into the charger didn't even light the red led and plugging it into my computer just displayed the device as QHSUSB_DLOAD in Window's Device Administrator.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
These firmwares were downloaded from here: https://www.androidfilehost.com/?w=files&flid=32777​
The first thing I did was search for a solution on the internet, I went to a bunch of threads in different forums from guys having the same problem (QHSUSB_DLOAD), but all of them said that they were using their phone and suddenly it powered off. The answers were something like "Your motherboard is dead, you need to take it to htc for them to repair it". I was getting scared when I read those answers, but the thing is that my phone didn't suddenly shut off when I was using it, and I don't think I damaged the motherboard changing the firmware so there's no reason for me to take it to repair (Also, there's no HTC service center in my city so I can't take it there either).
When I was flashing the firmwares I even checked in the .zips that they were compatible with my phone, and they all were, I don't know why the hell my phone got bricked.
---------------------------
SOLUTION:
http://forum.xda-developers.com/showthread.php?t=2770684&page=3

It should work
Sent from my HTC One using Tapatalk

cyrusct82 said:
It should work
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Yes! My phone is wokring now Thanks for the answer.

ElIrvingsillo said:
Hello XDA. Today I was upgrading my phone's firmware since it was pretty outdated (I had 1.4.xxx firmware lol), so I downloaded a bunch of firmwares (See picture below) that were compatible with my phone (MID and CID), I installed each of them from the lowest version to the highest. Everything was going fine until I installed the 5.11.401.10 firmware, when I rebooted the phone the screen went completely black, I couldn't reboot it pressing Power + Vol up, plugging the phone into the charger didn't even light the red led and plugging it into my computer just displayed the device as QHSUSB_DLOAD in Window's Device Administrator.
These firmwares were downloaded from here: https://www.androidfilehost.com/?w=files&flid=32777​
The first thing I did was search for a solution on the internet, I went to a bunch of threads in different forums from guys having the same problem (QHSUSB_DLOAD), but all of them said that they were using their phone and suddenly it powered off. The answers were something like "Your motherboard is dead, you need to take it to htc for them to repair it". I was getting scared when I read those answers, but the thing is that my phone didn't suddenly shut off when I was using it, and I don't think I damaged the motherboard changing the firmware so there's no reason for me to take it to repair (Also, there's no HTC service center in my city so I can't take it there either).
When I was flashing the firmwares I even checked in the .zips that they were compatible with my phone, and they all were, I don't know why the hell my phone got bricked.
---------------------------
SOLUTION:
http://forum.xda-developers.com/showthread.php?t=2770684&page=3
Click to expand...
Click to collapse
If you want to update the firmware using "firmware.zip" extracted from ota updates, you must flash all the versions incrementally or you will brick your phone in QHSUB, hopefully, the linked guide was exactly for your situation. Firmware.zip are not "complete" firmware, these are only patches to be flashed over the previous version.
you have skipped many versions when flashing:
4.19.401.5
4.19.401.8
4.19.401.9
6.09.401.5
6.09.401.11
6.09.401.12
7.19.401.2
If you want to avoid this situation in the future, flash only complete firmware.zip files (not from ota). These are generally about 40mb in size. In your case, you could have flashed directly the 7.19.401.2 full firmware.zip and then flash the 7.19.401.22 firmware.zip from ota.

cyrusct82 said:
It should work
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
alray said:
If you want to update the firmware using "firmware.zip" extracted from ota updates, you must flash all the versions incrementally or you will brick your phone in QHSUB, hopefully, the linked guide was exactly for your situation. Firmware.zip are not "complete" firmware, these are only patches to be flashed over the previous version.
you have skipped many versions when flashing:
4.19.401.5
4.19.401.8
4.19.401.9
6.09.401.5
6.09.401.11
6.09.401.12
7.19.401.2
If you want to avoid this situation in the future, flash only complete firmware.zip files (not from ota). These are generally about 40mb in size. In your case, you could have flashed directly the 7.19.401.2 full firmware.zip and then flash the 7.19.401.22 firmware.zip from ota.
Click to expand...
Click to collapse
Oh, okay, thank you so much for the answer. I'll keep that in mind next time.

Re-locked Bootloader and now facing problems

Hi there this is my first post so excuse me if i'm unclear about stuff. if you need any info just gimme a shout and i can find it for you!
I have an M7 on O2 (UK), I've had it pretty much since it release in 2013.
Upon getting the phone i immediately rooted whilst on Android Version 4.4.3, it's the Sense Version too (i don't know if that's relevant or not).
Anyway it's been a while since this, and i've lost a lot of the knowledge i had on Android & Rooting etc.
I'm looking to un-root my phone to get the OTA Updates which have been alerting my (very annoying) since 2013!
Last week i began watching tutorials and reading up, a few days in and i gave it my first attempt..
I first re-locked my Bootloader successfully and then tried using the RUU Software but was unlucky with numerous versions (i'm still unsure about how to find the RIGHT one). After hours & hours i was at and end and couldnt seem to find the right one for my phone and i gave up.
Since "re-locking" my Bootloader i've been facing an issue where every time i power up or restart my phone it boots in the Bootloader's Fastboot mode, from here i have to navigate to 'reboot'... the phone then restarts and this time round i get my usual home screen.
I'm unsure as to what direction to go now as i'm scared i will brick my phone, i guess i have 2 options;
A. Continue to try and return to stock and then decide if i wish to re-root (probably not)
B. Unlock the Bootloader once again (only this will wipe my phone, and i can't find the original stock rom thus leading to a brick i expect?)
Hope someone can help, any questions please do not hesitate to ask!

gemodubz said:
Hi there this is my first post so excuse me if i'm unclear about stuff. if you need any info just gimme a shout and i can find it for you!
I have an M7 on O2 (UK), I've had it pretty much since it release in 2013.
Upon getting the phone i immediately rooted whilst on Android Version 4.4.3, it's the Sense Version too (i don't know if that's relevant or not).
Anyway it's been a while since this, and i've lost a lot of the knowledge i had on Android & Rooting etc.
I'm looking to un-root my phone to get the OTA Updates which have been alerting my (very annoying) since 2013!
Last week i began watching tutorials and reading up, a few days in and i gave it my first attempt..
I first re-locked my Bootloader successfully and then tried using the RUU Software but was unlucky with numerous versions (i'm still unsure about how to find the RIGHT one). After hours & hours i was at and end and couldnt seem to find the right one for my phone and i gave up.
Since "re-locking" my Bootloader i've been facing an issue where every time i power up or restart my phone it boots in the Bootloader's Fastboot mode, from here i have to navigate to 'reboot'... the phone then restarts and this time round i get my usual home screen.
I'm unsure as to what direction to go now as i'm scared i will brick my phone, i guess i have 2 options;
A. Continue to try and return to stock and then decide if i wish to re-root (probably not)
B. Unlock the Bootloader once again (only this will wipe my phone, and i can't find the original stock rom thus leading to a brick i expect?)
Hope someone can help, any questions please do not hesitate to ask!
you can also contact me here [email protected]
Click to expand...
Click to collapse
Post the output of "fastboot getvar all" (hide your imei and sn)

alray said:
Post the output of "fastboot getvar all" (hide your imei and sn)
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

gemodubz said:
Click to expand...
Click to collapse
If you want to return to stock, you can use the 7.18.206.51 ruu (its the latest version for your phone)
Instructions as post #1, ruu at post #2:
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
Once the RUU flashed you can unlock the bootloader again and re-root. Be sure to use the latest version of supersu.

alray said:
If you want to return to stock, you can use the 7.18.206.51 ruu (its the latest version for your phone)
Instructions as post #1, ruu at post #2:
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
Once the RUU flashed you can unlock the bootloader again and re-root. Be sure to use the latest version of supersu.
Click to expand...
Click to collapse
Thanks a bunch man! Please could you tell me how you found the specific RUU for my phone?
Please could you tell me the method you used to locate the RUU as i had so much trouble before, i was wondering if there is an easy way find the correct RUU (by looking for certain codes etc) ?

alray said:
If you want to return to stock, you can use the 7.18.206.51 ruu (its the latest version for your phone)
Instructions as post #1, ruu at post #2:
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
Once the RUU flashed you can unlock the bootloader again and re-root. Be sure to use the latest version of supersu.
Click to expand...
Click to collapse
won't unlocking the bootloader after flashing RUU just wipe the phone again?

gemodubz said:
won't unlocking the bootloader after flashing RUU just wipe the phone again?
Click to expand...
Click to collapse
Unlocking will wipe user data only.
Sent from my HTC One using XDA Labs

alray said:
Unlocking will wipe user data only.
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
So would that be my media files like photos, music, apps etc?

gemodubz said:
So would that be my media files like photos, music, apps etc?
Click to expand...
Click to collapse
Exactly
Sent from my HTC One using XDA Labs

Network Stopped Working - Need Help!

First of all, i have a bootloader locked XT1254 with SU4TL49 firmware. I use Nova Launcher and was just looking through Nova Shortcuts hoping to make a GSM/UMTS switch on my home screen. I came across BandMode under Settings, and accidentally clicked USA Band. After that my SIM couldnt find any network, i tried everything: Clicked USA Band, Cellular, changed network mode to Global and back to LTE / GSM / UMTS. I even tried everything in the hidden Phone Menu (RadioInfo). After nothing worked i tried Factory reset twice, but still the same.
The phone detects the SIM and shows the SIM contacts too, but cant find any network operators. I know the last thing to try is updating firmware to Marshmallow, but that would also close the window for bootloader unlock if i later need to repair the firmware through custom recovery.
Any help would be greatly appreciated. Screenshots on how to kill the Network and also get to hidden Phone Menu are attached.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

killerxda said:
First of all, i have a bootloader locked XT1254 with SU4TL49 firmware.
I know the last thing to try is updating firmware to Marshmallow, but that would also close the window for bootloader unlock if i later need to repair the firmware through custom recovery.
Click to expand...
Click to collapse
So, go ahead and unlock your bootloader right now. What are you waiting for? You still have Wi-Fi, right?
By the way, Sunshine works with Marshmallow now -- just not the most recent Marshmallow (MCG24.251-5-5, earlier this week). You can re-flash Su4TL-49 firmware or the first Marshmallow image, MCG24.251-5.
[FXZ] Official Stock Firmware 6.0.1 MCG24.251-5
https://forum.xda-developers.com/dr...official-stock-firmware-6-0-1-mcg24-t3531571\
Besides unlocking your bootloader, the first thing you can do is try to re-flash your Lolllipop radio:
firstEncounter said:
Instructions for using fastboot packages:
Code:
mfastboot flash radio radio.img
5.1 (SU4TL-49)
Fastboot package (Mirror)
SHA1 sum: a297a5fd84f906cdfacf4efb8c656babbfe2452f
Click to expand...
Click to collapse
If that doesn't work, then re-flash the entire SU4TL-49 firmware or flash the first Marshmallow image above. But go ahead and unlock your bootloader!

ChazzMatt said:
Besides unlocking your bootloader, the first thing you can do is try to re-flash your Lolllipop radio:
If that doesn't work, then re-flash the entire SU4TL-49 firmware or flash the first Marshmallow image above. But go ahead and unlock your bootloader!
Click to expand...
Click to collapse
Before your reply here i got to the radio thread and tried flashing SU4TL49 radio. BUT what i did was flash all 3 files (radio, GPT, bootloader) as instructed in that thread. Next thing i know my baseband is Unknown and no IMEI is being shown now..... The problems seem to be stacking up.
Was some file not compatible? Do i flash any files from SU4TL44 zip now?
EDIT: FINALLY!! After flashing GPT and Bootloader of SU4TL49 i flashed radio from SU4TL44 and the command fastboot oem config fsg-id ""
Everything back to normal now! :good: :highfive: :laugh: :victory:
Thanks to your reply on the other thread about 2G not working i found out about radio flashing possibility otherwise i was thinking nothing is possible on a locked bootloader :highfive:

Now go unlock your bootloader.

ChazzMatt said:
Now go unlock your bootloader.
Click to expand...
Click to collapse
Haha i think i'll just sell it soon and buy some other