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] Stock T-Mobile Image and Baseband

Anyone have these yet by chance?

I am sure it is coming. I would like to get my hands on it also.

Would be nice to have as I've already screwed it up.

liquidblue1985 said:
Would be nice to have as I've already screwed it up.
Click to expand...
Click to collapse
did you flash the n7100 stock firmware?

JoJo2211 said:
did you flash the n7100 stock firmware?
Click to expand...
Click to collapse
Nope. Downloading that right now actually. The only issue I'm having is that it's not recognizing the baseband.

It would be nice to be able to flash the Tmobile modem.

gedster314 said:
It would be nice to be able to flash the Tmobile modem.
Click to expand...
Click to collapse
Yeah. I'm pretty much stuck at this point. I have a custom recovery installed, root and on an international rom but I cannot get cell service. Wifi works, but that's about it.

I believe it has to do with the isis security.
Was thinking about going to TMO and getting a non-isis sim card to try.
liquidblue1985 said:
Yeah. I'm pretty much stuck at this point. I have a custom recovery installed, root and on an international rom but I cannot get cell service. Wifi works, but that's about it.
Click to expand...
Click to collapse

+1 I need the modem or a stock tar to odin asap, hope it drops soon...

The non-ISIS sim card did not change anything.
Looks like I need the stock rom also.
:/
luser01 said:
I believe it has to do with the isis security.
Was thinking about going to TMO and getting a non-isis sim card to try.
Click to expand...
Click to collapse

If anyone can help out with getting a flashable radio for this it'd be greatly appreciated. I've looked around on how to extract the radio from the current version with no luck.
As far as the ROM, a user linked one here:
http://forum.xda-developers.com/showpost.php?p=33242968&postcount=67
I've restored that through custom recovery/nandroid and it works fine. But without the radio... I'm lost.

I get a MD5 mismatch when I try to restore it with nandroid.
Downloaded it twice. anyone else had luck?
liquidblue1985 said:
If anyone can help out with getting a flashable radio for this it'd be greatly appreciated. I've looked around on how to extract the radio from the current version with no luck.
As far as the ROM, a user linked one here:
http://forum.xda-developers.com/showpost.php?p=33242968&postcount=67
I've restored that through custom recovery/nandroid and it works fine. But without the radio... I'm lost.
Click to expand...
Click to collapse

luser01 said:
I get a MD5 mismatch when I try to restore it with nandroid.
Downloaded it twice. anyone else had luck?
Click to expand...
Click to collapse
Had the same thing. Best bet is to go into the md5 file with a text editor and just delete everything and save the file. Recopy the md5 file over and reflash. Not sure why it was causing this error because I even re-ran the md5's myself and they were the same.
Also, just got off the phone with Samsung, they pretty much said the phone is not in their system yet and they do not have access to the firmware at this point. Their suggestion was to go back to t-mobile and get an exchange unit.

I will try that..
I called Samsung last night and they gave me the same run around.
liquidblue1985 said:
Had the same thing. Best bet is to go into the md5 file with a text editor and just delete everything and save the file. Recopy the md5 file over and reflash. Not sure why it was causing this error because I even re-ran the md5's myself and they were the same.
Also, just got off the phone with Samsung, they pretty much said the phone is not in their system yet and they do not have access to the firmware at this point. Their suggestion was to go back to t-mobile and get an exchange unit.
Click to expand...
Click to collapse

Just hoping now that maybe someone with enough knowledge sees this and can extract a flashable baseband... I'd really hate to go and buy another unit.

liquidblue1985 said:
Just hoping now that maybe someone with enough knowledge sees this and can extract a flashable baseband... I'd really hate to go and buy another unit.
Click to expand...
Click to collapse
You should find a store with one on the shelf, and not much supervision... and root it/extract a nand image hehehe. Though that would mean you would have be able to do all that and I have no idea how to extract a baseband image that is the power of the xda dev gods!

How hard is it to extract a baseband image?
Could someone that has one do it easily?
MikeBrWade said:
You should find a store with one on the shelf, and not much supervision... and root it/extract a nand image hehehe. Though that would mean you would have be able to do all that and I have no idea how to extract a baseband image that is the power of the xda dev gods!
Click to expand...
Click to collapse

I'm not sure if this is what you're looking for in particular buuut...
http://forum.xda-developers.com/showthread.php?t=1954597
It was (and still is) posted on the N7100 dev forum. It's the T-Mobile boot.img in tar format. Read through the thread for more info.

That is for people that messed up the rooting.
I flashed a full ITL rom that had the modem in it.
All I need is the modem and I am good to go.
/Waits
anoneemooz said:
I'm not sure if this is what you're looking for in particular buuut...
http://forum.xda-developers.com/showthread.php?t=1954597
It was (and still is) posted on the N7100 dev forum. It's the T-Mobile boot.img in tar format. Read through the thread for more info.
Click to expand...
Click to collapse

luser01 said:
That is for people that messed up the rooting.
I flashed a full ITL rom that had the modem in it.
All I need is the modem and I am good to go.
/Waits
Click to expand...
Click to collapse
Oh so wait. You're using a T-Mobile Note 2 and managed to flash an international ROM with everything working and functional (except for signal/sms/data/call) ? No reboots?
I ask because I've been wanting to somehow "convert" my T-Mobile Note 2 to an international Note 2 (as in, be able to flash the updates the international version gets instead of waiting on T-Mobile). I'm not US based so I don't need it to work with T-Mobile SIM anyhow...

[Q] Help!! SIM not recognized after updating bootloader

I was trying to install the Quantum Rom on my ATT Samsung Galaxy S3.
It failed a few times until someone posted that I need to update my bootloader to I747UCUEMJB. I was able to install the ROM after the update but now my phone won't recognize the SIM card that's worked flawlessly till I performed the bootloader update.
Is my phone done for good or is there something I can do here? Please help!!

Did you flash a compatible or updated modem?

audit13 said:
Did you flash a compatible or updated modem?
Click to expand...
Click to collapse
Sorry not really sure what that means. Also, just went in to my settings and under Baseband version I am seeing Unknown.
I checked the size of the bootloader I downloaded and it's only at 1.1 mbs and I just found the same bootloader online but at 623 mbs. I am assuming the bootloader I installed might be corrupt/fake?
I am downloading the larger file now and am going to try and install that too see if that helps?

There is no way the bootloader would be 623 MB.
Try flashing a modem from here: http://forum.xda-developers.com/showthread.php?t=1831898

audit13 said:
There is no way the bootloader would be 623 MB.
Try flashing a modem from here: http://forum.xda-developers.com/showthread.php?t=1831898
Click to expand...
Click to collapse
Yeah figured as much, especially after looking at the contents of the file, I decided not to use it.
Thanks for the link. Just downloaded modem_CWM_I747UCUEMJB.zip and I have my network signal back up now. I am hoping this means I am good. Will let you know soon. Thanks!!!

theproman23 said:
Sorry not really sure what that means. Also, just went in to my settings and under Baseband version I am seeing Unknown.
I checked the size of the bootloader I downloaded and it's only at 1.1 mbs and I just found the same bootloader online but at 623 mbs. I am assuming the bootloader I installed might be corrupt/fake?
I am downloading the larger file now and am going to try and install that too see if that helps?
Click to expand...
Click to collapse
Your baseband/modem is indeed corrupt. Before downloading or flashing ROMs please research thoroughly to be sure you know what you are doing and understand the difference between all the different files. The file you saw at 623mb is most likely the system or ROM file itself. The bootloader file itself is a much smaller file - consistent with a 1MB+ download. If you succeed with the file you are trying to download, you most probably would be updating your ROM although I'd be very doubtful if it would work. I'm not too certain but the 623MB file looks like the 4.3 update zip which usually works only when you are doing a manual update from an earlier ROM especially the immediate predecessor 4.1.2.
To correct your modem, I would suggest you try downloading and flashing the 4.3 modem file.
You may also need to install custom recovery (e.g. TWRP or CWM) for an easier installation. I presume warranty is no longer an issue with your phone in view of the firmware history.
Edit;
Just saw the last post from Audit after sending mine. Glad to know all is OK now.

Larry2999 said:
Your baseband/modem is indeed corrupt. Before downloading or flashing ROMs please research thoroughly to be sure you know what you are doing and understand the difference between all the different files. The file you saw at 623mb is most likely the system or ROM file itself. The bootloader file itself is a much smaller file - consistent with a 1MB+ download. If you succeed with the file you are trying to download, you most probably would be updating your ROM although I'd be very doubtful if it would work. I'm not too certain but the 623MB file looks like the 4.3 update zip which usually works only when you are doing a manual update from an earlier ROM especially the immediate predecessor 4.1.2.
To correct your modem, I would suggest you try downloading and flashing the 4.3 modem file.
You may also need to install custom recovery (e.g. TWRP or CWM) for an easier installation. I presume warranty is no longer an issue with your phone in view of the firmware history.
Edit;
Just saw the last post from Audit after sending mine. Glad to know all is OK now.
Click to expand...
Click to collapse
I completely understand what you're saying. Truth is I don't enough about all this to do what I did. Lesson learned for sure!
So. I was able to install the Modern bootloader and have my LTE signal back up and confirmed things are working given someone already called me and the call came through fine.
Now, the last thing I need to figure out is how to get WIFI to work. It's connecting to my router and has gone through authentication and has saved my network on the list of WIFI spots but I can't seem to connect and start downloading apps without eating my data.
Never mind, finally got wifi to work. Thanks again!!

Are you using any sort of encryption on your wifi network (i.e. WPA, WPA2, etc.)? Can it connect if you disable encryption?

I think I messed up again

For starters, I have an AT&T HTC M9. I unlocked the bootloader, and after a while, got TWRP 3.0.2.0 installed as the custom recovery. I decided to flash ARHD, since that's my personal favorite that I've used on my M7 and M8. After flashing and clearing cache, the phone optimizes apps, reboots, and then stays at the HTC screen for a bit. Finally, the screen will turn off as if it's booted in. I could then wake the device and adjust volume and such, but I still had the HTC logo covering what would be the UI. After a bit more time, the setup menu finally came up. I couldn't set up wifi, as it got stuck on the "connecting" screen. Wiped, re-flashed ARHD. Same thing. Finally got through the setup, and I had no service. What am I doing wrong? Do I need to install a corresponding firmware or something? This happens to me every time. Also the M9 had Android 6.0 with Sense 7.0, for the record.

Have you made sure that the rom is compatible with your phones firmware?.
Beamed in by telepathy.

shivadow said:
Have you made sure that the rom is compatible with your phones firmware?.
Beamed in by telepathy.
Click to expand...
Click to collapse
The thread says it's built off of 3.35.401.12, and my phone is running 3.38.502.12. The thread goes on to say "- If your current firmware version doesn't match ROM firmware version, wiping data inside AROMA is highly recommended!" so I figured if I wiped the data inside AROMA it would still work. Am I just dumb?

manlavi95 said:
The thread says it's built off of 3.35.401.12, and my phone is running 3.38.502.12. The thread goes on to say "- If your current firmware version doesn't match ROM firmware version, wiping data inside AROMA is highly recommended!" so I figured if I wiped the data inside AROMA it would still work. Am I just dumb?
Click to expand...
Click to collapse
Please read the FAQ section of the Readme thread which is pinned above the normal questions here in the Q&A section. There you'll find the reason and the solution for the no service problem.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
Please read the FAQ section of the Readme thread which is pinned above the normal questions here in the Q&A section. There you'll find the reason and the solution for the no service problem.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
"For Sense-based roms you just need to re-flash the stock boot image of your current firmware version." I'm now at a loss. I am in way over my head right now. So technically speaking, I'd be able to get ARHD to run on my ATT M9? That quoted sentence gave me an anxiety attack.
Edit: I've got an RUU that I was thinking of using and then just rooting the stock ROM and then going about my day. I'd be ok with that if I knew for a fact that it wouldn't remove TWRP. That and I was looking forward to the ARHD battery life.

manlavi95 said:
"For Sense-based roms you just need to re-flash the stock boot image of your current firmware version." I'm now at a loss. I am in way over my head right now. So technically speaking, I'd be able to get ARHD to run on my ATT M9? That quoted sentence gave me an anxiety attack.
Click to expand...
Click to collapse
Keep calm. All you need to do is downloading the RUU for your current firmware and the decryption tool that is linked in my thread. Drag'n'drop the RUU onto the *.exe file of the tool and wait some minutes. When it's finished it will give you an output folder. Inside you'll find a firmware folder and inside that one you'll find the needed boot image. All you need to do then is booting your phone to download mode and connecting it via USB with your pc. Copy the boot.img into your adb/fastboot folder and use
Code:
fastboot flash boot <enter name of the boot image - including its file extension - here and delete the less/greater symbols>
E.g. if the file is named boot_signed.img the command would be
Code:
fastboot flash boot boot_signed.img
The next time you boot your rom everything should be working, fine.
Edit: Your edit didn't exist when I wrote this post... The RUU will remove TWRP if you flash it. RUUs always reflash the whole phone (in other words: the system and the firmware).

Flippy498 said:
Keep calm. All you need to do is downloading the RUU for your current firmware and the decryption tool that is linked in my thread. Drag'n'drop the RUU onto the *.exe file of the tool and wait some minutes. When it's finished it will give you an output folder. Inside you'll find a firmware folder and inside that one you'll find the needed boot image. All you need to do then is booting your phone to download mode and connecting it via USB with your pc. Copy the boot.img into your adb/fastboot folder and use
Code:
fastboot flash boot <enter name of the boot image - including its file extension - here and delete the less/greater symbols>
E.g. if the file is named boot_signed.img the command would be
Code:
fastboot flash boot boot_signed.img
The next time you boot your rom everything should be working, fine.
Edit: Your edit didn't exist when I wrote this post... The RUU will remove TWRP if you flash it. RUUs always reflash the whole phone (in other words: the system and the firmware).
Click to expand...
Click to collapse
It appears that I may have given some misinformation. Looking in the ROM that I had flashed (Official Build ATT 3.38.502.12 ROM 7-12-2016), the firmware appears as (obviously) 3.38.502.12. However, looking in download mode, OS appears to actually be 3.38.502.41. Are the instructions you gave me still pertinent, or do I need to try something else?

manlavi95 said:
It appears that I may have given some misinformation. Looking in the ROM that I had flashed (Official Build ATT 3.38.502.12 ROM 7-12-2016), the firmware appears as (obviously) 3.38.502.12. However, looking in download mode, OS appears to actually be 3.38.502.41. Are the instructions you gave me still pertinent, or do I need to try something else?
Click to expand...
Click to collapse
In that case you will need the boot image of firmware 3.38.502.41. The correct firmware version of your phone is stated in the download mode. You're lucky since HTC released a RUU for that firmware, as well.
There are two main problems with HTCs website:
a) They only provide RUUs for their US customers. So be happy that you bought a US varaint of the M9.
b) They don't update their website that regularly although the files are already available. Since the URL isn't that complicated you can simply guess the correct one for newer RUUs.

Flippy498 said:
In that case you will need the boot image of firmware 3.38.502.41. The correct firmware version of your phone is stated in the download mode. You're lucky since HTC released a RUU for that firmware, as well.
There are two main problems with HTCs website:
a) They only provide RUUs for their US customers. So be happy that you bought a US varaint of the M9.
b) They don't update their website that regularly although the files are already available. Since the URL isn't that complicated you can simply guess the correct one for newer RUUs.
Click to expand...
Click to collapse
Done deal. So after flashing ARHD and then re-flashing the boot image, I can happily go on my way with a nifty AT&T M9 with ARHD?

manlavi95 said:
Done deal. So after flashing ARHD and then re-flashing the boot image, I can happily go on my way with a nifty AT&T M9 with ARHD?
Click to expand...
Click to collapse
Based on my previous experiences with the M9 I'd say yes.

Flippy498 said:
Based on my previous experiences with the M9 I'd say yes.
Click to expand...
Click to collapse
Thank you for preventing me from dying today. I'll see what I can do. Also, I was sitting here, looking at the HTC site, and I found all the ROMs, but for the life of me could not find the right one. That was when I noticed you had linked it to me. Now I'm actually wondering where you're finding these.

manlavi95 said:
Thank you for preventing me from dying today. I'll see what I can do. Also, I was sitting here, looking at the HTC site, and I found all the ROMs, but for the life of me could not find the right one. That was when I noticed you had linked it to me. Now I'm actually wondering where you're finding these.
Click to expand...
Click to collapse
On their website. Take a look at the URL of the download for the older 3.38.502.12 RUU you can find there, then take a look at your current firmware. If you now look at the link for the latest RUU I posted you'll understand how I guessed the correct link. It's no magic.

Flippy498 said:
On their website. Take a look at the URL of the download for the older 3.38.502.12 RUU you can find there, then take a look at your current firmware. If you now look at the link for the latest RUU I posted you'll understand how I guessed the correct link. It's no magic.
Click to expand...
Click to collapse
Ok, so I flashed the ROM, (ARHD 20.0, 6.0, Sense 7.0) and then flashed the boot. Phone boots up fine, I now have signal and data, but there is one issue. I have no wifi. Is this...radio-related?
Another edit: I also don't see SuperSU anywhere, and that's confusing me just a bit.

manlavi95 said:
Ok, so I flashed the ROM, (ARHD 20.0, 6.0, Sense 7.0) and then flashed the boot. Phone boots up fine, I now have signal and data, but there is one issue. I have no wifi. Is this...radio-related?
Click to expand...
Click to collapse
No, the radio/baseband doesn't deal with the WIFI reception. There are other parts of the firmware like the wcnss that are responsible for that. You may want to ask in the dedicated rom thread for further help. I haven't heard of such wifi problems before.
In regard to your edit: I never flashed ARHD. I can't even tell you whether it's using SuperSU or any other superuser app.

Flippy498 said:
No, the radio/baseband doesn't deal with the WIFI reception. There are other parts of the firmware like the wcnss that are responsible for that. You may want to ask in the dedicated rom thread for further help. I haven't heard of such wifi problems before.
In regard to your edit: I never flashed ARHD. I can't even tell you whether it's using SuperSU or any other superuser app.
Click to expand...
Click to collapse
Alrighty, so it appears support has ended for ARHD. I'll go ahead and ask in the thread anyway, but out of curiosity, I checked out Viper. Looks like that won't work with AT&T. I'll try out ICE maybe. I need more practice.

manlavi95 said:
Alrighty, so it appears support has ended for ARHD. I'll go ahead and ask in the thread anyway, but out of curiosity, I checked out Viper. Looks like that won't work with AT&T. I'll try out ICE maybe. I need more practice.
Click to expand...
Click to collapse
Well, you could use viper. You just need to choose default in the aroma installer. But I don't know whether your reception is supported out of the box or not. And since viper 5 is based on a HTC 10 port the boot image trick might not work, either. Viper 4 on the other hand should be working fine in case you need to reflash the boot image since it's based on the latest wwe M9 firmware.

Flippy498 said:
Well, you could use viper. You just need to choose default in the aroma installer. But I don't know whether your reception is supported out of the box or not. And since viper 5 is based on a HTC 10 port the boot image trick might not work, either. Viper 4 on the other hand should be working fine in case you need to reflash the boot image since it's based on the latest wwe M9 firmware.
Click to expand...
Click to collapse
Would you... recommend Viper by chance? I'm trying to weigh my options at this point.

manlavi95 said:
Would you... recommend Viper by chance? I'm trying to weigh my options at this point.
Click to expand...
Click to collapse
I guess my signature should be sufficent for answering that question.
(And yes, I do know that my firmware and the TWRP version I'm using are outdated. I didn't have the time nor the motiviation that would be needed for updating them. I'll probably just wait until HTC distributes android 7 for my SKU.)

Flippy498 said:
I guess my signature should be sufficent for answering that question.
(And yes, I do know that my firmware and the TWRP version I'm using are outdated. I didn't have the time nor the motiviation that would be needed for updating them. I'll probably just wait until HTC distributes android 7 for my SKU.)
Click to expand...
Click to collapse
I hope I'm not taking up too much of your personal time from asking such questions, as the thread's original question has been answered. I'm currently looking at how to install 5.3, because it looks like a wonderful ROM to have.

manlavi95 said:
I hope I'm not taking up too much of your personal time from asking such questions, as the thread's original question has been answered. I'm currently looking at how to install 5.3, because it looks like a wonderful ROM to have.
Click to expand...
Click to collapse
Flash it like any other rom. The aroma installer is actually pretty straight forward. Choose default since there is nor AT&T specific installation.
Just make sure that you read what it wants you to do. Sometimes it asks which apps you want to install and sometimes which you want to uninstall.

Question Baseband Version UNKNOWN

Tried everything. Searched through the webs for past couple of days. Everything failed.
Majority of articles are from times of Ancient Rome. None work and are outdated.
Reflashed stock with nand erase and pit file. Checked and failed.
Tried root related solutions? Checked and failed.
Searched modem file. Failed.
Downgrade to prev version? No longer plausible. Due to BIT.
I flashed and reflashed with odin numerious of times. Nothing. Useless. Absolutely useless.

did u solve it?

Did you guys find anything? I think I'm gonna go check at a repair shop for someone with the z3x box and hope for the best.

Mighty_Rearranger said:
Did you guys find anything? I think I'm gonna go check at a repair shop for someone with the z3x box and hope for the best.
Click to expand...
Click to collapse
any luck?

dronkit said:
any luck?
Click to expand...
Click to collapse
Nope, he said no matter what rom he flashed it was always unknown IMEI.
However I found something interesting, turns out my IMEI and baseband numbers are intact when I check them from recovery. Maybe downgrading this phone should fix that, although I'm not sure if it is possible.

Mighty_Rearranger said:
Nope, he said no matter what rom he flashed it was always unknown IMEI.
However I found something interesting, turns out my IMEI and baseband numbers are intact when I check them from recovery. Maybe downgrading this phone should fix that, although I'm not sure if it is possible.
Click to expand...
Click to collapse
no, its not possible because of the bit.... can you try using an old modem to see if it solves the problem?

applesucksLmao said:
no, its not possible because of the bit.... can you try using an old modem to see if it solves the problem?
Click to expand...
Click to collapse
You mean like flashing an older modem? How can I do that?

Mighty_Rearranger said:
You mean like flashing an older modem? How can I do that?
Click to expand...
Click to collapse
its the CP file in odin

try flashing one from may or august.. don't try november or newer

You need to download an older firmware (older than november, never try that ****ty november update!) of your country's a32 and use just the cp file

applesucksLmao said:
You need to download an older firmware (older than november, never try that ****ty november update!) of your country's a32 and use just the cp file
Click to expand...
Click to collapse
I'll get an older firmware from sammobile and get back to you if anything different happens. Just as a note, someone here on XDA said they were able to downgrade when using a Magisk altered ROM.
Edit: I found something similar on another samsung phone here on XDA: thread here.

Mighty_Rearranger said:
I'll get an older firmware from sammobile and get back to you if anything different happens. Just as a note, someone here on XDA said they were able to downgrade when using a Magisk altered ROM.
Edit: I found something similar on another samsung phone here on XDA: thread here.
Click to expand...
Click to collapse
Could you flash it with a magisk modified rom?

@Mighty_Rearranger maybe you could try flashing an android 12 gsi? https://forum.xda-developers.com/t/...sing-odin-without-twrp-phh-lineageos.4114435/ I don't have the phone with me right now so I can't test it

applesucksLmao said:
You need to download an older firmware (older than november, never try that ****ty november update!) of your country's a32 and use just the cp file
Click to expand...
Click to collapse
OK I tried doing that and now phone is bootlooping with secure check fail md1img error, that's the anti-downgrade thing complaining. No luck down the downgrade hallway.
I think the only option is to wait for a possible solution from the Magisk people or check if a future update somehow fixes the problem.

Mighty_Rearranger said:
Nope, he said no matter what rom he flashed it was always unknown IMEI.
However I found something interesting, turns out my IMEI and baseband numbers are intact when I check them from recovery. Maybe downgrading this phone should fix that, although I'm not sure if it is possible.
Click to expand...
Click to collapse
how do you check them from recovery? I was able to see them once after a botched flashing, entering download mode, there was a "show barcode" option or something like that.
I have read in an older thread in this forum, some guy solved it by downgrading, but to a version which is impossible to downgrade to for us, because our phones already came with the AUJ4 firm, and acannot go back.

applesucksLmao said:
@Mighty_Rearranger maybe you could try flashing an android 12 gsi? https://forum.xda-developers.com/t/...sing-odin-without-twrp-phh-lineageos.4114435/ I don't have the phone with me right now so I can't test it
Click to expand...
Click to collapse
what's the idea? there aren't any custom roms, are there?
or you mean this way it could be possible to downgrade?

dronkit said:
what's the idea? there aren't any custom roms, are there?
or you mean this way it could be possible to downgrade?
Click to expand...
Click to collapse
if someone manages to create twrp for a32 4g maybe there's a way back

applesucksLmao said:
if someone manages to create twrp for a32 4g maybe there's a way back
Click to expand...
Click to collapse
TWRP lets you bypass the binary version check?

Mighty_Rearranger said:
TWRP lets you bypass the binary version check?
Click to expand...
Click to collapse
i don't know probably, and we could get a backup from someone with a not fricked phone and edit it to our imeis