Develop Bugs

Error [140]: Bootloader version error?

Hey all, I originally had Damage 3.2.2 installed, had wimax update, and the new radio, everything was fine, I am now trying to restore everything back to factory with the HTC Android ROM update utility, v1.0.2.10. I plug it in, go through the steps, it starts to wipe everything, then when it starts copying files it gives me this error. So when it canceled and the phone rebooted, it was just stuck on the white evo screen and loops. I figured it was just because of the new update and all, so I was still able, (thanks god) to flash over Bugless V03. Tryed to use the utility again, and still gives the error. Can anyone help get me back to factory please? thanks for the help I would like to go get my new EVO with out any worry.

So you still have root and access to the recovery console? Odd that you are having problems restoring. Instead of using the exe file, I believe you can flash the zip file using the phones built in hboot menu instead. I don't think it will check the software version first, it's worth a shot. I think you have to name it PC36IMG.zip I think. I would find the exact info but I'm not on a pc at the moment.
Edit:
Check here too, but it's not good:
http://forum.xda-developers.com/showthread.php?t=714157

Sirchuk said:
So you still have root and access to the recovery console? Odd that you are having problems restoring. Instead of using the exe file, I believe you can flash the zip file using the phones built in hboot menu instead. I don't think it will check the software version first, it's worth a shot. I think you have to name it PC36IMG.zip I think. I would find the exact info but I'm not on a pc at the moment.
Edit:
Check here too, but it's not good:
http://forum.xda-developers.com/showthread.php?t=714157
Click to expand...
Click to collapse
I didnt use the OTA update, I flashed Damage 3.2.2, it never effected my ROOT or NAND, I just need to get it back to factory so I can return my phone for a new one. They got one waitin on me to pick up tomorrow afternoon. I have to work all day so I have to either stay up, and figure this out or, if I cant figure something out then I will have to cross my fingers when I go up there tomorrow. I have already spoke with a rep in person, he seemed cool. He looked at my phone for a good minute, scrolled through a few things, I couldnt see what it was, but he just handed it back to me and told me to just come back tomorrow at the same time, and hell swap it. I didnt realize it but I was already on a list for the phone, so Im gettin it either way I guess. I just dont want anything to happen when I go up there. Even if I could just flash over something updated or not just looked "stock" maybe I can just slip in and out.

Ahh okay. Well, look around for the zip format of the exe file in the "how to go back to stock" thread a few posts down.

Sirchuk said:
Ahh okay. Well, look around for the zip format of the exe file in the "how to go back to stock" thread a few posts down.
Click to expand...
Click to collapse
I see that thread, but all I do see is just the .exe files, no zip. There isnt just a installer like with the old version, I have the older exe, before I flashed damage3.2.2 I could easily go back to factory by running that exe and goin through the steps

Alright, this is what I was talking about, I posted it in another thread:
I think he can try restoring to factory.
Download this:
http://www.joeyconway.me/evo/stock/R...253_signed.zip
Rename it PC36IMG.zip and put it on the root of the SD card.
Turn off the phone, hold volume down and turn it on, it should boot into hboot, sort of a factory recovery
It will automatically detect the zip file and ask if you want to apply it. Select yes, and it should restore to factory.
If you continue to have problems, then there is probably something wrong with the phone and it'll need to be returned.
Click to expand...
Click to collapse
You can give that a shot I guess. There are quite a few posts today in the Q&A section with problems, and they all have one thing in common: Damage Control ROM.

Sirchuk said:
Alright, this is what I was talking about, I posted it in another thread:
You can give that a shot I guess. There are quite a few posts today in the Q&A section with problems, and they all have one thing in common: Damage Control ROM.
Click to expand...
Click to collapse
Oops! The Page Can Not Be Found!
Well sorry if I am cluttering I didnt even know that the bootloader was changed which I guess is what the problem is. I guess this is what I get for being impatient. Thanks for the help chuk. If all ells fails cross your fingers for me.

Sirchuk said:
Alright, this is what I was talking about, I posted it in another thread:
You can give that a shot I guess. There are quite a few posts today in the Q&A section with problems, and they all have one thing in common: Damage Control ROM.
Click to expand...
Click to collapse
This guy is atroll
Bootloader was updated with nw ota. Ur applying an old ruu and getting an errir, that's 100% normal you can't roll.back with ruu. Search the board for ducks sake, look at all the threads about rooting nw ota. This is there problem. Just flash another update zip first then u can ruu back.

Yup, that would do it. Hope you can get it worked out before you take it back.

fallentimm said:
This guy is atroll
Bootloader was updated with nw ota. Ur applying an old ruu and getting an errir, that's 100% normal you can't roll.back with ruu. Search the board for ducks sake, look at all the threads about rooting nw ota. This is there problem. Just flash another update zip first then u can ruu back.
Click to expand...
Click to collapse
I still have the the PCIMG zip from when I nand rooted, would that work? flash that then run the exe?

BAleR said:
I still have the the PCIMG zip from when I nand rooted, would that work? flash that then run the exe?
Click to expand...
Click to collapse
If you still have recovery flash dc 3.2. This should rest you bootlegger.
Then run a ruu.

Nooo, I think that is a different file. You can try searching for the link i tried go link that doesn't work, but I doubt it will work if you updated the boot loader. The method I was suggesting would have restored to stock, but with a newer bootloader I'm not sure what to do exactly.
Edit:
If damage control 3.2 has an older bootloader it should work, give it a go.

fallentimm said:
If you still have recovery flash dc 3.2. This should rest you bootlegger.
Then run a ruu.
Click to expand...
Click to collapse
I had a nan backup of 3.2 but I erased it like a dumbo after I was comfy with 3.2.2

If you still have NAND unlock, then try this starting at step 2. This will enable you to downgrade.
http://forum.xda-developers.com/showthread.php?t=701835 <---link

Yeeeah.... Flashed 3.2 and sent me into boot loops. I dont understand why bugless v3 would work, but not this one?

Your not nand unlocked anymore mostlikely.
Did u wipe between newer and older rom

nunyabiziz said:
If you still have NAND unlock, then try this starting at step 2. This will enable you to downgrade.
http://forum.xda-developers.com/showthread.php?t=701835 <---link
Click to expand...
Click to collapse
I dont know how to use adb, I used terminal to nand root, are you basically telling me to re-nand root?

BAleR said:
I dont know how to use adb, I used terminal to nand root, are you basically telling me to re-nand root?
Click to expand...
Click to collapse
most important part is to enable downgrade

nunyabiziz said:
most important part is to enable downgrade
Click to expand...
Click to collapse
well I am re rooting it is updating now.

BAleR said:
well I am re rooting it is updating now.
Click to expand...
Click to collapse
If it started the update without failing then you are in great shape.

[Q] Need to brick my Tmobile G2

Hello all,
I could not find a thread that directly related to this phone and request.
I am having reception problems and have tried every radio available. I still get dropped calls etc. I think it has been dropped on the floor one to many times.
So, I would like to brick it completely. No bootloader, nothing. I have CM7 and the latest recovery Clockword Mod. If I do not brick it I will need to pay 130 dollars for my deductible... If I brick... well its free =) So does anyone have suggestions or experience with this? And no I cannot set it on fire or throw it in a puddle or etc... Thanks!

I have heard that putting it in a microwave for a couple seconds does the trick.

You could try flashing a corrupted radio image. Though I'm not sure how you would intentionally corrupt the file. Maybe dd if=/dev/urandom into the file?
--MrAnt--

Flash a radio or SPL then pull the battery half way through

type rm -r * in the root?

Suppose I could try the radio flash first... and if that does not work... Microwave for five seconds. I am suprised there isnt a section devoted to this here at xda. -Thanks

Flash a firmware from a diff device ... 100% chance of a brick ... Should be doable if ur completely s-off ...
Sent from my HTC Incredible S using XDA App

knightrocker said:
Flash a firmware from a diff device ... 100% chance of a brick ... Should be doable if ur completely s-off ...
Sent from my HTC Incredible S using XDA App
Click to expand...
Click to collapse
mrant said:
You could try flashing a corrupted radio image. Though I'm not sure how you would intentionally corrupt the file. Maybe dd if=/dev/urandom into the file?
Click to expand...
Click to collapse
dpgc213 said:
Flash a radio or SPL then pull the battery half way through
Click to expand...
Click to collapse
These sound like good ideas! These are more likely to brick your phone!
adamhlj said:
I have heard that putting it in a microwave for a couple seconds does the trick.
Click to expand...
Click to collapse
This idea will leave enough damage to it that T-Mobile will immeadiately think suspiciously. Your device might then get shipped back with no repair.

Yea the microwave would be the last ditch effort. Tmobile has shipped me a new phone already.. I have to return this one when it arrives. They will probably try to refurbish my phone or something. So a software brick is ideal. I really appreciate all the suggestions. I will post the one that I use and if it works when I recieve the new phone.

Just give it to some crackhead in exchange for a newer Android device.

Just kill your hboot partition using dd while in userland
I dont remember the partition number, but you'd
dd if=/dev/zero of=/dev/block/mmcblk0p*
Where * = the partition number.
Or find an hboot for say the g1 and flash that, out would give new meaning to dangerspl.

amazinglarry311 said:
Just kill your hboot partition using dd while in userland
I dont remember the partition number, but you'd
dd if=/dev/zero of=/dev/block/mmcblk0p*
Where * = the partition number.
Or find an hboot for say the g1 and flash that, out would give new meaning to dangerspl.
Click to expand...
Click to collapse
Wow. Why not just tell him to flash CyanogenMod Recovery 1.4?

Uh.. Because flashing a bad recovery doesn't brick your device.
Read the thread.
He doesn't even want it to power up. A bad hboot will ignore boot signals and give him what he wants.
Do you guys like being contrary and wrong all the time? Or do you just single me out, because I know what I'm talking about?

knightrocker said:
Flash a firmware from a diff device ... 100% chance of a brick ... Should be doable if ur completely s-off ...
Click to expand...
Click to collapse
While a brick is possible, I don't know if its a sure thing. Not sure, but I seem to remember at least one noob on here who unwittingly tried to flash the ROM for another device. The ROM didn't work, but it didn't brick the phone either.

Flashing a rom for another device will only soft brick you.
Kill the hboot, kill the phone.

I've got a wonderful pre-bricked board for you! Let's trade .

Tell em u got an ota and you dropped ur your phone half way through....works every time!!!!!
Sent from my HTC Vision using XDA Premium App

blackknightavalon said:
Just give it to some crackhead in exchange for a newer Android device.
Click to expand...
Click to collapse
You mean like koush? Jaws just playing.. Don't suspend me koush.. I love you... Lol

amazinglarry311 said:
Flashing a rom for another device will only soft brick you.
Kill the hboot, kill the phone.
Click to expand...
Click to collapse
He is correct!
Kill Hboot, It will be all done!

Thanks for making my next HTC device cost more.....
Sent from my HTC Vision using XDA App

Help please...screen stuck at logo

Hello
My phone's screen is stuck at opening htc logo. I never rooted it - shall I just flash it with standard stock rom? Would you please be so kind to point me in the right direction? Bless...
My kindest regards
Pete

Try booting without the sd card.
How old is the phone? What happened / did you do (if such is the case) for it to get like that? Etc.....
Sent from a dream.

Teichopsia said:
Try booting without the sd card.
How old is the phone? What happened / did you do (if such is the case) for it to get like that? Etc.....
Sent from a dream.
Click to expand...
Click to collapse
Tried that before without result...also did a factory reset but to no avail. Phone was just over a year old when it happened, got it from my insurance policy so it's possibly a refurbished one. I can't remember doing anything to cause this...

phosphen said:
Tried that before without result...also did a factory reset but to no avail. Phone was just over a year old when it happened, got it from my insurance policy so it's possibly a refurbished one. I can't remember doing anything to cause this...
Click to expand...
Click to collapse
You Need to provide the Cid number and the Main Version. Do You know how to Get that?

glevitan said:
You Need to provide the Cid number and the Main Version. Do You know how to Get that?
Click to expand...
Click to collapse
Sorry, no idea...

phosphen said:
Sorry, no idea...
Click to expand...
Click to collapse
Ok, enable USB debugging, plug the phone to the PC and then open a CMD ON the PC and type adb reboot-bootloader and once in bootloader type fastboot getvar all. You Need to post the INFOcidnum and INFOmain

How old is your phone? Isn't there still any warranty? If so you may try to contact your reseller, service provider or the manufacturer. If not glevitan may be your hero

glevitan said:
Ok, enable USB debugging, plug the phone to the PC and then open a CMD ON the PC and type adb reboot-bootloader and once in bootloader type fastboot getvar all. You Need to post the INFOcidnum and INFOmain
Click to expand...
Click to collapse
Sorry mate, I was offline for a whole day, just managed to get back on it
How can I enable USB debugging if I can get onto HBOOT menu only? Is it possible to switch it on from there? Saludos

phosphen said:
Sorry mate, I was offline for a whole day, just managed to get back on it
How can I enable USB debugging if I can get onto HBOOT menu only? Is it possible to switch it on from there? Saludos
Click to expand...
Click to collapse
Yes, from fastboot, plug the phone (You will see fastboot USB in red) type: fastboot getvar all

sounds like a boot loop?
try removing the battery, once you have done that re boot into boot loader from there you should see an option for recovery.you may want to do a full wipe and re flash the rom.:silly: keep in mind the initial flash normally will take the longest,best to leave it be for a few minutes while the phone adjust to the new settings,that sometimes will seem like you may have an issue, but patience most times is all that is needed.hope this helps.

rdub504 said:
try removing the battery, once you have done that re boot into boot loader from there you should see an option for recovery.you may want to do a full wipe and re flash the rom.:silly: keep in mind the initial flash normally will take the longest,best to leave it be for a few minutes while the phone adjust to the new settings,that sometimes will seem like you may have an issue, but patience most times is all that is needed.hope this helps.
Click to expand...
Click to collapse
It's not rooted, so I don't think that will work.

bananagranola said:
It's not rooted, so I don't think that will work.
Click to expand...
Click to collapse
excellent point,but if that's true what is he flashing?
rooted phone=flash capable non rooted =stock rom with no admin access. am i mistaken,if so slap me and call me susan,if not box that thing up and bring it back,and if that's not an option then warranty time.because that device is chap.

rdub504 said:
excellent point,but if that's true what is he flashing?
rooted phone=flash capable non rooted =stock rom with no admin access. am i mistaken,if so slap me and call me susan,if not box that thing up and bring it back,and if that's not an option then warranty time.because that device is chap.
Click to expand...
Click to collapse
Hello susan
Sent from a dream.

Teichopsia said:
Hello susan
Sent from a dream.
Click to expand...
Click to collapse
LOL,I guess i'm susan and my face now hurt.can you please elaborate a bit so i can also understand what i am missing.

rdub504 said:
LOL,I guess i'm susan and my face now hurt.can you please elaborate a bit so i can also understand what i am missing.
Click to expand...
Click to collapse
Well....
1- over a year old bought refurbished.
2- he never rooted. We could assume that it is s-off from the previous owner but all of us failed to ask that question making another assumption that he isn't s-off.
3- he did a factory reset which didn't work (whatever that means with an s-on device / with an s-off device it really messes things up).
4- glevitan is here. If he doesn't know how to fix it (and from the few active members that tend to lend a hand in these type of posts) there may be just a handful who could help out. Hence, the OP is in good hands.
5- when someone messes up their phone without knowing what happened nor how to fix it, you need to give more detailed instructions on how to get it done.
6- I'm guessing that the info glevitan asked for is to find the correct ruu for the member to flash and to get his phone back to working conditions. If that doesn't work, chances are it's a hardware problem.
Sent from a dream.

Teichopsia said:
Well....
1- over a year old bought refurbished.
2- he never rooted. We could assume that it is s-off from the previous owner but all of us failed to ask that question making another assumption that he isn't s-off.
3- he did a factory reset which didn't work (whatever that means with an s-on device / with an s-off device it really messes things up).
4- glevitan is here. If he doesn't know how to fix it (and from the few active members that tend to lend a hand in these type of posts) there may be just a handful who could help out. Hence, the OP is in good hands.
5- when someone messes up their phone without knowing what happened nor how to fix it, you need to give more detailed instructions on how to get it done.
6- I'm guessing that the info glevitan asked for is to find the correct ruu for the member to flash and to get his phone back to working conditions. If that doesn't work, chances are it's a hardware problem.
Bullet point,impressive. now a refurb with s off would mean a root from a previous owner?
"S-ON, which means it blocks you from flashing radio images — the code that manages your data, Wi-Fi and GPS connections. Switching your phone to S-OFF lets you flash new radios. Rooting doesn’t require S-OFF, but many rooting tools will give you S-OFF in addition to root access" So hince my question if attempting to flash a rom ,it would be a safe bet he would be rooted,because without it he would have no admin access,recovery or superser access and would not be able to complete the flash process.a factory reset would normally on a stock rom not result in a loss of the entire stock rom but only a loss off data i.e contacts apps etc. and with these things in mind it would seem to be a safe to assume its a hardware issue or a rooted refurb phone from a previous owner in a bootloop becauce a factory reset there would wipe everything?
Click to expand...
Click to collapse

Factory reset resets the phone to it's "as fabricated"-condition, wich means it wipes user data and cache on the phone. With or without root the procedure is the same and should usally not affect /system or /boot.
So we have to find out, if the phone is S-On/S-Off (phosphen, more information on the topic can be read for example here, second post).

Teichopsia said:
Well....
1- over a year old bought refurbished.
2- he never rooted. We could assume that it is s-off from the previous owner but all of us failed to ask that question making another assumption that he isn't s-off.
3- he did a factory reset which didn't work (whatever that means with an s-on device / with an s-off device it really messes things up).
4- glevitan is here. If he doesn't know how to fix it (and from the few active members that tend to lend a hand in these type of posts) there may be just a handful who could help out. Hence, the OP is in good hands.
5- when someone messes up their phone without knowing what happened nor how to fix it, you need to give more detailed instructions on how to get it done.
6- I'm guessing that the info glevitan asked for is to find the correct ruu for the member to flash and to get his phone back to working conditions. If that doesn't work, chances are it's a hardware problem.
Sent from a dream.
Click to expand...
Click to collapse
rdub504 said:
Teichopsia said:
Well....
1- over a year old bought refurbished.
2- he never rooted. We could assume that it is s-off from the previous owner but all of us failed to ask that question making another assumption that he isn't s-off.
3- he did a factory reset which didn't work (whatever that means with an s-on device / with an s-off device it really messes things up).
4- glevitan is here. If he doesn't know how to fix it (and from the few active members that tend to lend a hand in these type of posts) there may be just a handful who could help out. Hence, the OP is in good hands.
5- when someone messes up their phone without knowing what happened nor how to fix it, you need to give more detailed instructions on how to get it done.
6- I'm guessing that the info glevitan asked for is to find the correct ruu for the member to flash and to get his phone back to working conditions. If that doesn't work, chances are it's a hardware problem.
Bullet point,impressive. now a refurb with s off would mean a root from a previous owner?
"S-ON, which means it blocks you from flashing radio images — the code that manages your data, Wi-Fi and GPS connections. Switching your phone to S-OFF lets you flash new radios. Rooting doesn’t require S-OFF, but many rooting tools will give you S-OFF in addition to root access" So hince my question if attempting to flash a rom ,it would be a safe bet he would be rooted,because without it he would have no admin access,recovery or superser access and would not be able to complete the flash process.a factory reset would normally on a stock rom not result in a loss of the entire stock rom but only a loss off data i.e contacts apps etc. and with these things in mind it would seem to be a safe to assume its a hardware issue or a rooted refurb phone from a previous owner in a bootloop becauce a factory reset there would wipe everything?
Click to expand...
Click to collapse
Cfhappy said:
Factory reset resets the phone to it's "as fabricated"-condition, wich means it wipes user data and cache on the phone. With or without root the procedure is the same and should usally not affect /system or /boot.
So we have to find out, if the phone is S-On/S-Off (phosphen, more information on the topic can be read for example here, second post).
Click to expand...
Click to collapse
Sorry guys, but before hijacking this thread maybe you can go and follow the discussion in the off topic thread. The idea here is to lend a hand to someone that is stuck and a noob and this for certain not helping him. Let's keep it clean....
BTW, the only solution in his case is to flash the OEM RUU or make a goldcard and flash an unbranded rom. With no s-off there´s no other way.
Click to expand...
Click to collapse

I couldn't resist.
Maybe it's good practice for him to read through all to learn to discern right info from wrong.
Sent from a dream.

Teichopsia said:
I couldn't resist.
Maybe it's good practice for him to read through all to learn to discern right info from wrong.
Sent from a dream.
Click to expand...
Click to collapse
Yeah, that is right, but with the phone stuck in the splash I don´t think is a good time to think about learning. This experience will definitely be worth for him in the future. :victory:

[Q] Radio and OpenDSP have "INVALID-VER-INFO" beside them. Is this normal? Need help

[Q] Radio and OpenDSP have "INVALID-VER-INFO" beside them. Is this normal? Need help
I just recently purchased the m8. I did lots of research learning everything I could before doing any modding. So today I decided to unlock my boot-loader so it was my first time getting into recovery. But when I get into recovery I see both radio and OpenDSP have "INVALID-VER-INFO" beside them. Its never been modified and I got it from t mobile and was the first to open the device. Not a second hand phone. Is this normal? I've been googling for hours and cant find any information. Its been sort of difficult getting any help in the htc M8 help threads honestly. If anyone can shed any information I would greatly appreciate it. I haven't noticed any thing wrong with my phone out of the box and everything about the functionality of the phone has been stellar.

ahfu25 said:
I just recently purchased the m8. I did lots of research learning everything I could before doing any modding. So today I decided to unlock my boot-loader so it was my first time getting into recovery. But when I get into recovery I see both radio and OpenDSP have "INVALID-VER-INFO" beside them. Its never been modified and I got it from t mobile and was the first to open the device. Not a second hand phone. Is this normal? I've been googling for hours and cant find any information. Its been sort of difficult getting any help in the htc M8 help threads honestly. If anyone can shed any information I would greatly appreciate it. I haven't noticed any thing wrong with my phone out of the box and everything about the functionality of the phone has been stellar.
Click to expand...
Click to collapse
Is that on the bootloader screen? What are u trying to accomplish?

twinnfamous said:
Is that on the bootloader screen? What are u trying to accomplish?
Click to expand...
Click to collapse
In the bootloader screen it says invalid ver info next to both. I want to know if this is normal on an unmodified device. I dont want to mod my phone with it saying invalid version next to radio and opendsp.

ahfu25 said:
In the bootloader screen it says invalid ver info next to both. I want to know if this is normal on an unmodified device. I dont want to mod my phone with it saying invalid version next to radio and opendsp.
Click to expand...
Click to collapse
I think something is off on that phone. I unlocked and s-offed mine and the only thing different was the os is blank but everything else was fine.
But if u have no actual problems with cell reception or audio then maybe u just need to update the firmware to latest after u s-off and that Will fix u up. More than likely.
Let me know I have done a lot on my phone allready. I even switched it to a dev edition just to get the 4.4.3 firmware and then flashed my backup back to my Rom of choice.
I'll help if I can. I notice there ain't many people helping on this forum there all on the international forum

twinnfamous said:
I think something is off on that phone. I unlocked and s-offed mine and the only thing different was the os is blank but everything else was fine.
But if u have no actual problems with cell reception or audio then maybe u just need to update the firmware to latest after u s-off and that Will fix u up. More than likely.
Let me know I have done a lot on my phone allready. I even switched it to a dev edition just to get the 4.4.3 firmware and then flashed my backup back to my Rom of choice.
I'll help if I can. I notice there ain't many people helping on this forum there all on the international forum
Click to expand...
Click to collapse
I appreciate that. I just didn't want to s-off since I dont do any heavy modding. I was just gonna unlock the boot-loader, install custom recovery root and flash arhd. I don't think this is normal either for a brand new phone that hasn't been touched software wise. I might go exchange it at t mobile. This is my screen

ahfu25 said:
I appreciate that. I just didn't want to s-off since I dont do any heavy modding. I was just gonna unlock the boot-loader, install custom recovery root and flash arhd. I don't think this is normal either for a brand new phone that hasn't been touched software wise. I might go exchange it at t mobile.
Click to expand...
Click to collapse
I understand about the s-off but really it's the best thing to do because if something ever goes wrong there will be nothing stopping u from fixing it.
Also I was gonna suggest taking it back but they might trip on the unlocked bootloader and if u fastboot oem lock it Will say relocked. So they will know. But it's worth a try. T-Mobile doesn't seem like they know anything about technical stuff. so if you try to explain to them they might look at you like they don't know what your talking about.
I seen the picture if it is still locked take it back. And show them
Your firmware is allready the latest so that's a factory f-up.

twinnfamous said:
I understand about the s-off but really it's the best thing to do because if something ever goes wrong there will be nothing stopping u from fixing it.
Also I was gonna suggest taking it back but they might trip on the unlocked bootloader and if u fastboot oem lock it Will say relocked. So they will know. But it's worth a try. T-Mobile doesn't seem like they know anything about technical stuff. so if you try to explain to them they might look at you like they don't know what your talking about.
I seen the picture if it is still locked take it back. And show them
Your firmware is allready the latest so that's a factory f-up.
Click to expand...
Click to collapse
How would they know the bootloader is unlocked at the tmobile store? Would they check on that before exchanging the device?

ahfu25 said:
How would they know the bootloader is unlocked at the tmobile store? Would they check on that before exchanging the device?
Click to expand...
Click to collapse
More than likely. I got charged 50 bucks one time and I couldn't even fight it because they sent it in and my Bill went up I wondered why so I asked and they said because of modifications all they did was exchange it but I still had to pay. Try it or relock it and do the ruu for that firmware. And see if it will take off the tampered flag and fix the ver info

twinnfamous said:
More than likely. I got charged 50 bucks one time and I couldn't even fight it because they sent it in and my Bill went up I wondered why so I asked and they said because of modifications all they did was exchange it but I still had to pay. Try it or relock it and do the ruu for that firmware. And see if it will take off the tampered flag and fix the ver info
Click to expand...
Click to collapse
I dont have a tampered flag in bootloader. Just "Unlocked"

ahfu25 said:
I dont have a tampered flag in bootloader. Just "Unlocked"
Click to expand...
Click to collapse
So then u never flashed recovery yet. So u should try to take it back.
If they are tripping just tell them the facts that the software was not properly installed on device.

twinnfamous said:
So then u never flashed recovery yet. So u should try to take it back.
If they are tripping just tell them the facts that the software was not properly installed on device.
Click to expand...
Click to collapse
whats that RUU you mentioned? Is there one specifically for the tmobile version that I can flash via stock recovery?

ahfu25 said:
whats that RUU you mentioned? Is there one specifically for the tmobile version that I can flash via stock recovery?
Click to expand...
Click to collapse
Sorry about taking a while.
Here's the link to what u will need http://forum.xda-developers.com/showthread.php?t=2754063

twinnfamous said:
Sorry about taking a while.
Here's the link to what u will need http://forum.xda-developers.com/showthread.php?t=2754063
Click to expand...
Click to collapse
No apology needed. Thank you for helping me out. I was able to s-off and get everything back to stock. Boot loader locked not "relocked" , s-on, unrooted. But the "invalid version" message was still there. I just came back from the tmobile store and they ran some diagnostics and said there was a problem with the software. They exchanged it for me and I checked it before I left the store and this one is perfect. I even asked for them to run the same diagnostics and everything checked out fine. I'm gonna do even a little more research before modding this one. I'm a little nervous now ..lol....but again thank you!!! I really love the M8. I came from the galaxy note 3 from att and sadly att locks the boot-loader on it. I love the note 3 just not on AT&T. I'm trying to sell my AT&T note 3 to buy a tmo version.

ahfu25 said:
No apology needed. Thank you for helping me out. I was able to s-off and get everything back to stock. Boot loader locked not "relocked" , s-on, unrooted. But the "invalid version" message was still there. I just came back from the tmobile store and they ran some diagnostics and said there was a problem with the software. They exchanged it for me and I checked it before I left the store and this one is perfect. I even asked for them to run the same diagnostics and everything checked out fine. I'm gonna do even a little more research before modding this one. I'm a little nervous now ..lol....but again thank you!!! I really love the M8. I came from the galaxy note 3 from att and sadly att locks the boot-loader on it. I love the note 3 just not on AT&T. I'm trying to sell my AT&T note 3 to buy a tmo version.
Click to expand...
Click to collapse
That's great problem solved.
now u know u got a good device.
I love the m8 too. I got mine first day it came out at T-Mobile.
First thing I did was unlock and s-off then recovery and root. Till some roms came out then I went to Bad Seed Customs Rom and that's it.
I've tried a lot of the roms even the new stock with elementalx kernel will last all day.
There's a whole lot u can do but most of the info is in the international forum.
Anyways glad I could help.

twinnfamous said:
That's great problem solved.
now u know u got a good device.
I love the m8 too. I got mine first day it came out at T-Mobile.
First thing I did was unlock and s-off then recovery and root. Till some roms came out then I went to Bad Seed Customs Rom and that's it.
I've tried a lot of the roms even the new stock with elementalx kernel will last all day.
There's a whole lot u can do but most of the info is in the international forum.
Anyways glad I could help.
Click to expand...
Click to collapse
Weird bro...now I go into boot loader with this phone and I'm getting the invalid ver message again. I'm still unmodified with bootloader still locked. I haven't even connected the phone to my computer yet.

ahfu25 said:
Weird bro...now I go into boot loader with this phone and I'm getting the invalid ver message again. I'm still unmodified with bootloader still locked. I haven't even connected the phone to my computer yet.
Click to expand...
Click to collapse
That's crazy what are you gonna do?

twinnfamous said:
That's crazy what are you gonna do?
Click to expand...
Click to collapse
Lol....I'm gonna keep it. I think it's software related. Nothing wrong functionality wise just like the other one. And I went to a different tmobile store for inventory purposes and lessen the chances of me getting a bad phone. Like I said I checked it at the store it didn't have that message. And they ran diagnostics and it read clean. I'm just gonna flash away lol

ahfu25 said:
Lol....I'm gonna keep it. I think it's software related. Nothing wrong functionality wise just like the other one. And I went to a different tmobile store for inventory purposes and lessen the chances of me getting a bad phone. Like I said I checked it at the store it didn't have that message. And they ran diagnostics and it read clean. I'm just gonna flash away lol
Click to expand...
Click to collapse
That's cool. I would do the same thing. Have a great time

twinnfamous said:
That's cool. I would do the same thing. Have a great time
Click to expand...
Click to collapse
Some research needs to be done to figure it out. I know I'm not the only one

ahfu25 said:
Some research needs to be done to figure it out. I know I'm not the only one
Click to expand...
Click to collapse
Probably not but everybody just gets to unlocking and s-offing so fast they probably don't notice.
It's probably just the ones coming with that firmware out of the box.
When I got mine it had a different version.

Question My phone is completely effed up now....

Locked my boatloader by mistake now it won't boots I need help ASAP.... I'm losing my mind over here I need someone to help me please for the love of God somebody... Just bought this phone for like $1,000 and now I'm looking at a ****ing brick......

no worries, you technically cant brick it that easily.
Check the MSM thread for your exact model and follow the steps get it back and running again.

^ Yeah an MSM flash will have you right as rain. Just wondering how the you locked the bootloader "by mistake" that seems like a difficult mistake to make.

was trying to restore and forgot how op works lol...i got it fixed now. while your here, how can i flash twrp and flash a rom? having issues with this now..

Anybody have any ideas of how I can ROM my phone? Been sitting here trying to do it for the last I don't know how long now

So I'm not sure about YOUR phone, if you have a recovery partition you can just flash recovery, if you don't have a recovery partition then you need to fastboot boot twrp first. And there are a few ways to flash a rom, my recommendation would be Fastboot Enhance I personally haven't tried it yet but it seems to work pretty good and even though it's in the 8T category it should work fine. Now one thing that is noteworthy with Fastboot enhance though is that it flashes the current slot instead of the inactive slot.

this.guy.lol said:
Anybody have any ideas of how I can ROM my phone? Been sitting here trying to do it for the last I don't know how long now
Click to expand...
Click to collapse
Didn't reply accidently, not the first time I've done that. Read my previous post.

Brandon.Bissonnette said:
Didn't reply accidently, not the first time I've done that. Read my previous post.
Click to expand...
Click to collapse
thx man