Develop Bugs

[Q] HELP!!

Hello everyone i have an galaxy s3 at&t version and i was trying to install a rom and the rom said it needed a certain bootloader so i download it and flash it and now my phone won reconize my sim or network state nor imei and i need help please !!!
!!!!!
ive tried odin and try reflashing back to stock but odin failed

ImJusDatGuy said:
Hello everyone i have an galaxy s3 at&t version and i was trying to install a rom and the rom said it needed a certain bootloader so i download it and flash it and now my phone won reconize my sim or network state nor imei and i need help please !!!
!!!!!
Click to expand...
Click to collapse
Definitely more info needed.
What ROM is on your device?
What bootloader did you install?
What modem/baseband/radio is on your device?
What method did you use to try to install the bootloader?
Is your phone still showing the correct IMEI in settings or 0 ? (Compare between that shown in settings and under the battery.)
It may be as simple as updating your modem, but I/we can't tell yet.

dawgdoc said:
Definitely more info needed.
What ROM is on your device?
What bootloader did you install?
What modem/baseband/radio is on your device?
What method did you use to try to install the bootloader?
Is your phone still showing the correct IMEI in settings or 0 ? (Compare between that shown in settings and under the battery.)
It may be as simple as updating your modem, but I/we can't tell yet.
Click to expand...
Click to collapse
the rom i have at the moment is the restored verison of the rooted rom i have which is stock 4.1.1 with root
the bootloader i install is I747UCUEMJB
my phone says baseband verison is unknown
i install the bootloader through cwm
the imei is unknown also my phone number to and network and roaming says not roaming mobile network state is disconnected.
everything is messed up thanks for the quick reply man i need help.

ImJusDatGuy said:
the rom i have at the moment is the restored verison of the rooted rom i have which is stock 4.1.1 with root
the bootloader i install is I747UCUEMJB
my phone says baseband verison is unknown
i install the bootloader through cwm
the imei is unknown also my phone number to and network and roaming says not roaming mobile network state is disconnected.
everything is messed up thanks for the quick reply man i need help.
Click to expand...
Click to collapse
I'm new at this, in fact I have flashed by old Captivate several times but yet to flash my SGS3. Anyhow, I have spent many hours reading. Before doing anything I suggest, read, and read some more.
Don't flash back to 4.1.1 or 4.1.2 at this point. They will install an older bootloader than is currently on your phone. From what I have read, you narrowly escaped bricking your phone. You might want to read some of the threads regarding the 4.3 stock ROM and unbricking before making any changes in restoring your device.
You can probably fix this by flashing the modem that goes with the 4.3 series ROMs. It would also be the MJB flavor, although the MJ2 would probably work. Several of the 4.3 TouchWiz ROMs in the development forum have download links for the MJB modem. I would guess you were probably going to install one of them. I would recommend flashing the modem to see if that solves your issues before going ahead with the ROM flash.

dawgdoc said:
Definitely more info needed.
What ROM is on your device?
What bootloader did you install?
What modem/baseband/radio is on your device?
What method did you use to try to install the bootloader?
Is your phone still showing the correct IMEI in settings or 0 ? (Compare between that shown in settings and under the battery.)
It may be as simple as updating your modem, but I/we can't tell yet.
Click to expand...
Click to collapse
dawgdoc said:
I'm new at this, in fact I have flashed by old Captivate several times but yet to flash my SGS3. Anyhow, I have spent many hours reading. Before doing anything I suggest, read, and read some more.
Don't flash back to 4.1.1 or 4.1.2 at this point. They will install an older bootloader than is currently on your phone. From what I have read, you narrowly escaped bricking your phone. You might want to read some of the threads regarding the 4.3 stock ROM and unbricking before making any changes in restoring your device.
You can probably fix this by flashing the modem that goes with the 4.3 series ROMs. It would also be the MJB flavor, although the MJ2 would probably work. Several of the 4.3 TouchWiz ROMs in the development forum have download links for the MJB modem. I would guess you were probably going to install one of them. I would recommend flashing the modem to see if that solves your issues before going ahead with the ROM flash.
Click to expand...
Click to collapse
Could you provide an link by any chance please i dont want to install anything wrong and btw im on jb 4.1.1 do i need to install a 4.3 rom also ? or ?

ImJusDatGuy said:
Could you provide an link by any chance please i dont want to install anything wrong and btw im on jb 4.1.1 do i need to install a 4.3 rom also ? or ?
Click to expand...
Click to collapse
The reason I didn't put a link in the previous posts was to get you to read about what you were doing as you searched for the modem. I am offering advice on things I have yet to experience on this device and only speaking second hand. My advice is only based on what I have read not on anything I have had to correct myself.
In truth I think you just stopped too soon in the process of what you were doing earlier. You said you installed the 4.3 bootloader in preparation to installing a 4.3 or later ROM that required the up to date bootloader. You didn't mention installing the current modem/baseband. You didn't mention trying to flash whatever ROM you had been considering.
You may be able to correct your device simply by installing the 4.3 modem. HERE is the modem thread, it is in the General Forum for our device. Make sure you pick the correct one. I don't know if your device will work well on the MJB bootloader and modem with a 4.1.1 ROM, from something I seem to recall reading I suspect it will.
Take this in steps. Install the correct modem, the one that matches your bootloader. See if that corrects you sim, data, and IMEI problems. If it does correct the issues, the next step is to decide if you want to stay on the 4.1.1 ROM or change to whatever ROM you had been considering. If you decide to change, make backups first. If it doesn't fix the problem while on 4.1.1 you may want to flash the version of the official 4.3 ROM enewman17 has provided on the development thread.
Take it one step at a time. Read about what you are about to do until you understand it well, all before doing anything. Make backups sequentially as you make each corrective step.
HTH.

dawgdoc said:
The reason I didn't put a link in the previous posts was to get you to read about what you were doing as you searched for the modem. I am offering advice on things I have yet to experience on this device and only speaking second hand. My advice is only based on what I have read not on anything I have had to correct myself.
In truth I think you just stopped too soon in the process of what you were doing earlier. You said you installed the 4.3 bootloader in preparation to installing a 4.3 or later ROM that required the up to date bootloader. You didn't mention installing the current modem/baseband. You didn't mention trying to flash whatever ROM you had been considering.
You may be able to correct your device simply by installing the 4.3 modem. HERE is the modem thread, it is in the General Forum for our device. Make sure you pick the correct one. I don't know if your device will work well on the MJB bootloader and modem with a 4.1.1 ROM, from something I seem to recall reading I suspect it will.
Take this in steps. Install the correct modem, the one that matches your bootloader. See if that corrects you sim, data, and IMEI problems. If it does correct the issues, the next step is to decide if you want to stay on the 4.1.1 ROM or change to whatever ROM you had been considering. If you decide to change, make backups first. If it doesn't fix the problem while on 4.1.1 you may want to flash the version of the official 4.3 ROM enewman17 has provided on the development thread.
Take it one step at a time. Read about what you are about to do until you understand it well, all before doing anything. Make backups sequentially as you make each corrective step.
HTH.
Click to expand...
Click to collapse
i've read this one thread and ive downloaded the modem and the rom ive tried to instal was a kitkat version of quatom v3.3 and it say get prop bootloader and i looked up the error everyone said to update your bootloader and thats how i got into this mess. :'( but thank you bro i really appreciate you took the time out of your day to help me.

ImJusDatGuy said:
i've read this one thread and ive downloaded the modem and the rom ive tried to instal was a kitkat version of quatom v3.3 and it say get prop bootloader and i looked up the error everyone said to update your bootloader and thats how i got into this mess. :'( but thank you bro i really appreciate you took the time out of your day to help me.
Click to expand...
Click to collapse
thanks man for telling me what was wrong your an amazing human being and i love you (no homo) and thanks again a million thanks bro.

Did that modem fix some of the problems?

If your on 4.1.1 shouldn't you flash the DKL3 version or can't you just flash thru Odin the DLK3 stock ROM thru Odin Amd start all over again
I've been on 4.3 with that bootloader Amd have flashed back to 4.1 back to the baseband version DLK3 firmware. I would think being on 4.1 you should be able to reflash using Odin to fix the issue or flash the modem for 4.1 .

AT&T SGH-i747u

Well, I am on CM11 nightly, all was fine with the original radio I assume it was, I was getting intermittent data transfer issues on CM11 and original AT&T Samsung android, so I thought trying different modems would help. Now it refuses to recognize any of them. I've tried clearing dalvik cache and cache afterward. It does not show an IMEI either anymore (which I read of others having the same issue). Would flashing back the original rom help at all?

The radio needs to match the bootloader. What bootloader is on your phone?

ok, through trying to update the bootloader in twrp, it told me i cannot, it says I have I747UCUFNE4
I cannot find this modem online so far...

I am not certain this is what you need since the thread title says you have a I747U. (Not familiar with that one.) But IF it uses the same NE4 firmware as the I747 you can try flashing this modem.
http://forum.xda-developers.com/showthread.php?p=53627484

[Q] i747m 4.4.2 brick

So first off I know I messed up bad. I had 4.4.2 bell s3 i747m. I was able to go from 4.1.2 to 5.1 with cwm. I wanted 4.1 to unlock sim. I saw the warnings but they were a cpl years old. Nothing new. And it said 4.3 and above only. Since I could get to 4.1.2 I thought maybe it wasn't still ongoing. I downgraded the bootloader. Phone went black from recovery and now nothing. The tuts are for 4.3. What works on 4.4.2? Does the sd card boot work for 4.4.2?

The phone was running a stock 4.4.2?
Did you try using the 4,3 de-brick image?

I did. It doesn't boot. And yes stock 4.4.2

I need the 4.4.2 bootloader

Also is it Knox bricking the phone? And if so will removing it (if I can boot it) stop future bricks? Anyone out there got a bell s3 they can get the bootloader and debrick from on 4.4.2

godkingofcanada said:
Also is it Knox bricking the phone? And if so will removing it (if I can boot it) stop future bricks? Anyone out there got a bell s3 they can get the bootloader and debrick from on 4.4.2
Click to expand...
Click to collapse
It's not Knox, it's just the newer bootloaders. Disabling Knox doesn't make any difference. You still can't downgrade the more recent bootloaders.
They might be somehow related. The bootloaders that produce bricks when downgraded emerged at the same time as Knox when Samsung started their corporate device push. Better to brick a phone than risk it running on a downgraded bootloader, when the bootloaders are all unlocked and will run unsigned code anyway It always seemed a little half-baked, but I'm sure there's something I'm failing to grasp.

Me as well. And I've only got mild understanding about this brick. I'm thinking with the right 4.4.2 bootloader and whatnot I may be able to use my 16 gig sd card to boot the phone. Is there any way to connect it in raw data mode? I remember older phones had to be off and have a button held while plugging it in to flash firmware.

I'm really stuck here

Also does anyone know where the extra hidden files internally are? I know it won't boot the phone because the phone knows the bootloader is invalid. Maybe if I just reinstall the right one I may revive it. But I assume I need sd boot for that to get to cwm

You should try different sd cards. Some members had to try a few different cards.

Has anyone out there successfully debrick the s3? On 4.4.2? Or should it let me force 4.3 rom and bootloader to work? I'm not sure if the method posted works for kit kat

I gotta locate a member with a bell s3 for the 4.4.2 debrick img. I can't just flash any 4.4.2 I wouldn't imagine. Maybe at&ts will work since that's i747 and this is i747m? I'm fine having to fix the modem and all that good stuff manually. I just need to get it on n I can fix the rest. Never bricked a phone before

godkingofcanada said:
I gotta locate a member with a bell s3 for the 4.4.2 debrick img. I can't just flash any 4.4.2 I wouldn't imagine. Maybe at&ts will work since that's i747 and this is i747m? I'm fine having to fix the modem and all that good stuff manually. I just need to get it on n I can fix the rest. Never bricked a phone before
Click to expand...
Click to collapse
did you check here
http://forum.xda-developers.com/showthread.php?t=2549068
sorry , that's all I got. good luck.
"all i can really do , is stay out of my own way and let the will of heaven be done"

Yeah that's not going to work thanks tho. Anyone know how to flash to the boot sector while device off? Like raw data read/write?

so to clarify where im at. im at the dreaded QHSUSB - DLOAD with my s3. meaning there is hope. its hard bricked but it still connects in fast download mode. is there a program i can use to connect to it at this point? im not able to find usb drivers for that. so it must be an app that reads it

What do you mean fast download mode? You mean you see the android guy with the shovel?

No I mean even tho the phone doesn't turn on or do anything it pops up on the computer.

You will have to have the phone repaired via jtag if you can't get it to work using a de-brick image.

I can. I just need a 4.4.2 bell debrick img. It's got to be the exact same no? Isn't 4.4.2 a different bootloader? Also does it matter if I flash a non bell bootloader and rom? Say at&t? It's i747 instead of i747m but I've used an at&t rom n it worked fine. I just don't know what works at bootloader level. Anyone out there got a bell s3 they can take the files from?

godkingofcanada said:
I can. I just need a 4.4.2 bell debrick img. It's got to be the exact same no? Isn't 4.4.2 a different bootloader? Also does it matter if I flash a non bell bootloader and rom? Say at&t? It's i747 instead of i747m but I've used an at&t rom n it worked fine. I just don't know what works at bootloader level. Anyone out there got a bell s3 they can take the files from?
Click to expand...
Click to collapse
might be one in here.
http://forum.xda-developers.com/showthread.php?t=2549068
"all i can really do , is stay out of my own way and let the will of heaven be done"

Need advice n7105 strange knox bootloop with every rom but 4.1.2 stock after cm10.1

Hello,
I'm a noob but usually try to fix this kind of issues on my own, looking at the boards, following tutorials, learning, but this time I think I'm not able to find a solution on my own so I'm asking for advice here.
Some time ago I installed cyanogenmod 10.1 on my Note 2 LTE and was happy with it for some month, than last week I tried to upgrade to cm12.1 It worked but there where some issues and bugs, mainly I wasn't able to swap internal/external sd cards.
So I decided to go back to latest available stock rom 4.4.2 from sammobile.
Here is where the problem starts. The stock 4.4.2 resulter in a bootloop, tried cache/dalvik/factory reset, flash again, whipe again.. nothing.
The phone is not able to get past the white label "Samsung Note 2 gt-n7105" screen. It goes black than the white label again and again.
It doesn't even get to the Samsung animated logo.
Ok bottloop, no problem, try to flash again something else.
I tried different Custom roms, different kernels, different flashing methods. I can flash anything with no problem but every time a get a bootloop.
During the various attempts knox fired, but I don't care. I don't know if this could be the cause.
Actually the only firmware that works is the original oldest STOCK 4.1.2, every other stock firmware past that or any custom rom is bootlooping the same way. To fix I only can reinstall stock 4.1.2 with odin.
I really need any advice or hint.
At the moment my goal is to get at least to stock 4.3 but I cant.........
Thanks!

When you first bought your phone, did it come with Knox?

ErnestChia said:
When you first bought your phone, did it come with Knox?
Click to expand...
Click to collapse
nope it doesn't existed before, but now I can see it when I boot in download mode "knox warranty void:1"

Try to get the latest firmware available via kies ,that worked for me
http://forum.xda-developers.com/showthread.php?t=2088809/[URL]

From what you've described, I think the Stock ROM 4.4.2 from Sammobile contained a bootloader update. So when you flashed this ROM, it updated your bootloader from the non-Knox version to the Knox version.
I am very unfamiliar with the technical details of Knox, but I think the new Knox bootloader is causing your bootloop problem.
However, I don't know why 4.1.2 works when everything else doesn't work!
Can you check the Stock ROM 4.4.2, and see whether it really contains a bootloader update?

mysuperdonghae said:
Try to get the latest firmware available via kies ,that worked for me
http://forum.xda-developers.com/sho...can flash cm10, 11 and 12 with no issue too..
Click to expand...
Click to collapse

misthero said:
I think so, there is a boot.im, anyway I also discovered that I can flash cm10, 11 and 12 with no issue too..
Click to expand...
Click to collapse
Since a boot.img is present, it means that it would flash your boot partition. So now we know for sure that when you attempted to flash the Stock ROM 4.4.2, your bootloader was changed to the Knox version.
So the lesson here is: before you flash anything via ODIN, always check to see if there is a bootloader update. Usually you don't want to be changing the bootloader on your phone.
***
So now there are 2 possible ways to reach your goal:
1) Keep your new bootloader and see whether you can get Stock 4.3 or Stock 4.4.2 running on your phone
2) Try to restore your old bootloader
As I said earlier, I'm not familiar with the technical details of Knox, so I'm not sure how to get Stock 4.3 or Stock 4.4.2 running on your phone when your Knox indicator is already 0x1. You need someone else to help you.
And you can only restore your old bootloader if you happen to have made a copy of your boot partition before you flashed the Stock ROM 4.4.2. Even if you did have a copy of your original boot partition, I'm not confident with helping you to restore your old bootloader. You need someone else to help you in this case too.
Conclusion: I don't think I can help you to solve your problem I'm sorry. Hopefully someone else who is more of a pro than me will come along to help you out.
Good luck!

No Sim detected after flashing Custom ROM

Hey guys... Been a LONG time since messing with an S3, and I don't want to brick it... SO, figured I'd reach out and ask before doing anything...
I downgraded a friend's S3 to UVDLJC to sim unlock it and it seemed to work fine on stock ROM. I then rooted the rom, flashed TWRP and factory reset the device and then flashed a custom ROM (this version is SlimKat but I had tried CM13 as well.. both have the same issue, no SIM detected)...
Anyway, I assume that it is a modem/radio issue and I should just be able to flash the modem firmware and be fine.. Problem I'm having is I'm not sure what to use... The phone is a T-999L Which, as I understand it, is the LTE GS3, but the software that was on it was based on the non LTE version (not sure if I'm correct about this)...
Anyway, looking to get this phone working for the friend's daughter (it was supposed to be a christmas present )...
Any and all help is appreciated.
Additional Info:
Phone model is T-999L
Boot loader is T999UVDLJC
Build version reports 4.4.4
Rom is currently SlimKat
Unified tools reports model as SGH-T999, type as d2tmo
Not sure what other info can help, but happy to provide.

RBThompsonV said:
Hey guys... Been a LONG time since messing with an S3, and I don't want to brick it... SO, figured I'd reach out and ask before doing anything...
I downgraded a friend's S3 to UVDLJC to sim unlock it and it seemed to work fine on stock ROM. I then rooted the rom, flashed TWRP and factory reset the device and then flashed a custom ROM (this version is SlimKat but I had tried CM13 as well.. both have the same issue, no SIM detected)...
Anyway, I assume that it is a modem/radio issue and I should just be able to flash the modem firmware and be fine.. Problem I'm having is I'm not sure what to use... The phone is a T-999L Which, as I understand it, is the LTE GS3, but the software that was on it was based on the non LTE version (not sure if I'm correct about this)...
Anyway, looking to get this phone working for the friend's daughter (it was supposed to be a christmas present )...
Any and all help is appreciated.
Additional Info:
Phone model is T-999L
Boot loader is T999UVDLJC
Build version reports 4.4.4
Rom is currently SlimKat
Unified tools reports model as SGH-T999, type as d2tmo
Not sure what other info can help, but happy to provide.
Click to expand...
Click to collapse
Odin'ed back to LJC original firmware... still shows no Sim card.

The latest custom ROMs require the latest bootloader and modem to function properly so the phone probably needs an update. Once the phone is running a 4.3 or higher bootloader means the bootloader cannot be downgraded in the future.
I don't see the LJC firmware for the T999L: http://www.sammobile.com/firmwares/database/SGH-T999L/
I see LJC for teh T999: http://www.sammobile.com/firmwares/database/SGH-T999/

audit13 said:
The latest custom ROMs require the latest bootloader and modem to function properly so the phone probably needs an update. Once the phone is running a 4.3 or higher bootloader means the bootloader cannot be downgraded in the future.
I don't see the LJC firmware for the T999L: http://www.sammobile.com/firmwares/database/SGH-T999L/
I see LJC for teh T999: http://www.sammobile.com/firmwares/database/SGH-T999/
Click to expand...
Click to collapse
Yeah, I'm thinking the phone is a T999, not a T999L. In my best estimation, the motherboard was swapped to a T999L case/screen. The sticker shows T-999L, the phone reports T-999. Additionally, under settings, the IMEI differs from the IMEI reported on the sticker. (Neither He, nor I was the original owner of the phone... so who knows it's history... For all I know, I really am working with a T-999L and someone flashed a different IMEI (worst case scenario I guess).
Is there any way to know for absolute sure? and should I go ahead and just flash 4.3? is there any downside to doing it other than that the boot loader can't be rolled back afterwards?

Personally, I would go by the model # shown with the phone in download mode.
Did it ever detect a sim card after unlocking restoring to stock?

It detected a sim when we got it (on 4.1.2), it detected a sim when i downgraded to 4.1.1, it detected a sim when i unlocked the sim, it did not detect a sim after flashing CM13, it did not detect a sim on SlimKat, and now it does not detect a sim after 4.1.1 (flashed via Odin) (LJC) and Download mode shows T-999 (NOT T-999L).
audit13 said:
Personally, I would go by the model # shown with the phone in download mode.
Did it ever detect a sim card after unlocking restoring to stock?
Click to expand...
Click to collapse

The 4.1.1 firmware came from sammobile? The baseband under settings is also LJC?

audit13 said:
The 4.1.1 firmware came from sammobile? The baseband under settings is also LJC?
Click to expand...
Click to collapse
Correct and correct.

This is bizarre because I don't understand why it would suddenly stop working. Did it say SGH-T999 on the download screen before flashing to 4.1.1?
I assume the stock ROM boots without issue?
Also try this: download and install the Samsung Phone Info from the play store to confirm the bootloader and baseband currently on the phone.
When flashing from a custom ROM to stock 4.1.1, did you perform a factory wipe?

audit13 said:
This is bizarre because I don't understand why it would suddenly stop working. Did it say SGH-T999 on the download screen before flashing to 4.1.1?
I assume the stock ROM boots without issue?
Also try this: download and install the Samsung Phone Info from the play store to confirm the bootloader and baseband currently on the phone.
When flashing from a custom ROM to stock 4.1.1, did you perform a factory wipe?
Click to expand...
Click to collapse
Stock rom boots without issue...
Yes i did a factory wipe between flashes. (Although, first flash of CM13 I did not, it ran weird, i rebooted, factory reset, flashed again then it worked fine minus the sim card issue).
Phone Info confirms SGH-T999, type: d2tmo
Boot loader: T999UVDLJC, Baseband: T999UVDLJC

Not sure what else to suggest other than reflashing the LJC ROM and performing a factory wipe from stock recovery before the phone's first boot of LJC.

audit13 said:
Not sure what else to suggest other than reflashing the LJC ROM and performing a factory wipe from stock recovery before the phone's first boot of LJC.
Click to expand...
Click to collapse
Nope...no go.

Hmm, I'm out of suggestions because you did everything I would do other than either flashing the latest stock 4.3 since the phone is now sim unlocked or running OTA updates. on a stock ROM.
The sim card in the phone works properly in another phone? Is it possible the sim reader was damaged in some manner? I know it can happen when using micro/nano sim card adapters.

audit13 said:
Hmm, I'm out of suggestions because you did everything I would do other than either flashing the latest stock 4.3 since the phone is now sim unlocked or running OTA updates. on a stock ROM.
The sim card in the phone works properly in another phone? Is it possible the sim reader was damaged in some manner? I know it can happen when using micro/nano sim card adapters.
Click to expand...
Click to collapse
Oh... adapters is a good suggestion. Yes, when I originally unlocked the phone, I used an adapter as my sim is a nano sim... Whats the damage look like? and is it fixable? I'm assuming just bent pins?
Is flashing an LTE Rom a possible solution? or is that a hard brick result?

You could try flashing TWRP and an older build of CM that will work with a 4.1.1 bootloader and modem just to see if the sim card is detected.
The metal housing on top of the sim pins is difficult to remove so it may be easier to just buy a replacement sim/sd card reader.

audit13 said:
You could try flashing TWRP and an older build of CM that will work with a 4.1.1 bootloader and modem just to see if the sim card is detected.
The metal housing on top of the sim pins is difficult to remove so it may be easier to just buy a replacement sim/sd card reader.
Click to expand...
Click to collapse
The posts aren't real specific... do you know which CM is 4.1.1 friendly?

I would try the latest cm10 or cm10.1.
https://download.cyanogenmod.org/?device=d2tmo&type=snapshot

dang you rock @audit13. as always :thumbup: , aint enuff. happy good new year for you and yours sir.
"all i can really do is stay out of my own way and let the will of heaven be done"

Any luck getting the phone to recognize the sim card?
@mrrocketdog, thanks

audit13 said:
Any luck getting the phone to recognize the sim card?
@mrrocketdog, thanks
Click to expand...
Click to collapse
Sorry for the delayed response... Yes, I finally got it to recognize (last night) ordered a new sim card tray.. interesting way to mount it by the way...
Anyway, seems as if the guess at the adapter damaging the original was correct... new one seems to be good to go.