Question Help with my A32 (A325M) after root, Lost Imei, fingerprint reader is not working - Samsung Galaxy A32 4G

Hello, I am here to help me with a problem I have with my Galaxy A32, it turns out that I wanted to root it, I stay as a dual sim phone when in fact it is a single sim phone and the imei was lost, it also stopped working the fingerprint reader that worked fine before all this happened. Does anyone know what can I do? it's a Galaxy A325M single sim. I speak Spanish, I wrote everything through a translator, if you see something wrongly written, that's why I'm sorry. I leave pictures of my problem. From already thank you very much..

i think you used an older version of magisk that caused that. while i own the A325F model i dont think anything should be different. i was running rooted latest stock firmware just fine although i flashed android 11 firmware and switched to spark os 13. anyways you could follow this to fix your issue. here.
DO ALL OF THIS ON YOUR OWN RISK. hope it goes well! idk abt fingerprint tho mine is also dead. i dont think it'll ever work again. although this happened even before i modified the phone or tripped knox. i didnt eve unlock the boot loader it was fully stock.

Related

[Q] 2 years down, My play is jus a psp

Hi all, Its been almost 2 years since i did an OTA update on my play and bricked it. Using the first patch that came out to fix this problem of phone not booting, i "destroyed" the bootloader or something or RadioRom and my phone does not accept any sim. it was originally unlocked.
Has anyone come up with a way to revive the play to make calls or something. cos its really depressing having a phone jus lying there wasting away, only to be brought out when needed for navigation or games.
Someone please helppppppppppppppppppppppppppppppp
Assuming your radio/sim is in working condition, I don't particularly see how bricking your phone can cause the phone to act like that. Have you tried flashing the stock firmware on again after it was bricked? And have you tried reunlocking the phone and putting on a custom rom/kernel?
jayact~ said:
Assuming your radio/sim is in working condition, I don't particularly see how bricking your phone can cause the phone to act like that. Have you tried flashing the stock firmware on again after it was bricked? And have you tried reunlocking the phone and putting on a custom rom/kernel?
Click to expand...
Click to collapse
about 2 years back, shortly after this phone came out, a problem was noted with OTA updates on unlocked bootloader.
The phone was bought "sim-free" or factory unlocked depending on which nomenclature is correct.
With an unlocked bootloader, the OTA update caused the phone to go dead.
in a haste to get the phone working again, a patch was released which broke the radio rom but got your phone to boot again. i believe the initial patch was released by BLAGUS.
well that killed my radio and now, no sim inserted works.
I reinstalled the stock firmware on it. tried several variants from different regions in the hope that it might work. was getting help from Wazz, Blagus and Bin4ry but seems they've moved on to more important projects now.
2 years ago, I would've brought my phone to the carrier. While your warranty would have been voided, you still should've been able to tell them that it is THEIR fault that it's not working since it was their OTA update that broke the phone. At the very least, they should've been able to get you a discount on a replacement Xperia Play, or at least I think they would have if they wanted to keep a happy customer.
Waqas said:
about 2 years back, shortly after this phone came out, a problem was noted with OTA updates on unlocked bootloader.
The phone was bought "sim-free" or factory unlocked depending on which nomenclature is correct.
With an unlocked bootloader, the OTA update caused the phone to go dead.
in a haste to get the phone working again, a patch was released which broke the radio rom but got your phone to boot again. i believe the initial patch was released by BLAGUS.
well that killed my radio and now, no sim inserted works.
I reinstalled the stock firmware on it. tried several variants from different regions in the hope that it might work. was getting help from Wazz, Blagus and Bin4ry but seems they've moved on to more important projects now.
Click to expand...
Click to collapse
Alright, I understand now. I wish I knew more, so I could help you out.
Was this the patch you used? I believe I used this ftf to relock my bootloader when my phone was bricked after I accepted an OTA update, just as you did. My radio never had any issues, though.. That said, my phone was sim-locked, since I have the R800x, so maybe that has something to do with it..

GT-I1860L No network.

Hello, last week I was given a Samsung Galaxy Ace II to install a custom ROM on, however, after flashing CM 11 I noticed that the phone wasn't recognizing the sim card, so I tried to downgrade again but I got the same issue. So far I've installed about 10 different stock firmware and updates and the phone still doesn't want to recognize the sim card.
The phone was originally working with the operator Movistar (Venezuela). But it seems like there's no official firmware for my country. I've already tried this: http://forum.xda-developers.com/showpost.php?p=53921158&postcount=8 and it didn't work.
There's just one thing that I've read online but haven't tried, something that has to do with the "tee" folder, I don't really know what I'm supposed to do with it, and I also don't know where to get the original files from.
If there's anything that you guys know that might help me, please post it.
PS: The phone was originally running 2.3.6 GB (In case that matters).
PSS: Yes, I am pretty dumb for not backing up the entire firmware prior to installing CM, but there's nothing I can do now.

Install stock SM-N910W8 on SM-910V

Hi, just bought an unlocked Note 4 from USA, it's the Verizon version.
I looked on your forum to find an answer, but I can't.
I'm from Canada, and I'd like to install a stock rom of the canadian version (n910w8), to have less Verizon/Amazon bloatware, and the french language available.
Considering that the N910W8 phone is pretty identical(from what I can see..), same CPU, would I brick my phone from installing this very rom "N910W8VLU1BOE2_N910W8OYA1BOE2_N910W8VLU1BOE2_HOME.tar.md5"?
And if so, why? And what are my alternatives?
see rooting and now you can unlock bootloader too first head to this post
then after that whatever your stock rom you can uninstall the blotware
here are another post for the blot which is safe to remove
and you can use that thing
I am using Indian sim and it is working great
'and you can use that thing'
That thing? The .md5 i mentionned?
When you boot the phone it says 'custom' and has a lock/unlock symbol?
You purchased it unlocked?
Futtermax said:
When you boot the phone it says 'custom' and has a lock/unlock symbol?
You purchased it unlocked?
Click to expand...
Click to collapse
I purchased it unlocked, but it has a Verizon logo whenever I boot it. So, would I be able to install the n910w8 without any trouble? Or is there a way to "install it" and during the process if it is not compatible it will tell it to me?
xDanny1992x said:
I purchased it unlocked, but it has a Verizon logo whenever I boot it. So, would I be able to install the n910w8 without any trouble? Or is there a way to "install it" and during the process if it is not compatible it will tell it to me?
Click to expand...
Click to collapse
He's trying to make sure that "unlocked" means that your bootloader is unlocked. It's a critical point, especially if your "unlocked" is referring to being open to all carriers.
If your bootloader is unlocked, you'll see an open padlock on the first boot screen. If the bootloader isn't unlocked, you won't be able to flash any ROMs until you unlock it.
douger1957 said:
He's trying to make sure that "unlocked" means that your bootloader is unlocked. It's a critical point, especially if your "unlocked" is referring to being open to all carriers.
If your bootloader is unlocked, you'll see an open padlock on the first boot screen. If the bootloader isn't unlocked, you won't be able to flash any ROMs until you unlock it.
Click to expand...
Click to collapse
Now, after a few more research I understand what you guys were trying to make me understand haha
I'm unlocking my bootloader, but my main topic question remain unanswered.
Will my phone be able to take the n910w8 rom even if I have a n910v? (once my bootloader will be unlocked and everything..)
xDanny1992x said:
Now, after a few more research I understand what you guys were trying to make me understand haha
I'm unlocking my bootloader, but my main topic question remain unanswered.
Will my phone be able to take the n910w8 rom even if I have a n910v? (once my bootloader will be unlocked and everything..)
Click to expand...
Click to collapse
The ROM, maybe. Will it work? Not without some serious help.
Since the Verizon variant of this phone isn't getting much developer love... it was locked until recently and true Developer Editions were rare and in smartphone terms, it's old... people are looking at the Snapdragon development.
The biggest headache will be getting the phone and data to work. The W8 is a GSM phone while Verizon uses CDMA.
douger1957 said:
The ROM, maybe. Will it work? Not without some serious help.
Since the Verizon variant of this phone isn't getting much developer love... it was locked until recently and true Developer Editions were rare and in smartphone terms, it's old... people are looking at the Snapdragon development.
The biggest headache will be getting the phone and data to work. The W8 is a GSM phone while Verizon uses CDMA.
Click to expand...
Click to collapse
Ok, I guess I could say I'm a superhero, my name, SuperStupid -_-
I finally got the padlock logo, rooted my phone, installed TWRP, tried to flash n910w8 rom, it didnt work, so I told myself, why not wipe everything, so I did.
Now I have a phone without OS, but! I kept the padlock and TWRP...
A new successful achievment for SuperStupid...
I'm currently downloading (with my superFast 1mb/s connection) the full firmware of N910V, which I didnt think prior to wipe everything, to keep a copy...
And I hope that I'll only have to put the file on my SD card, and then flash it...
I'll stay with my Verizon bloatware, as soon as I get it back, I won't try again soon to do this ****!!!
xDanny1992x said:
Ok, I guess I could say I'm a superhero, my name, SuperStupid -_-
I finally got the padlock logo, rooted my phone, installed TWRP, tried to flash n910w8 rom, it didnt work, so I told myself, why not wipe everything, so I did.
Now I have a phone without OS, but! I kept the padlock and TWRP...
A new successful achievment for SuperStupid...
I'm currently downloading (with my superFast 1mb/s connection) the full firmware of N910V, which I didnt think prior to wipe everything, to keep a copy...
And I hope that I'll only have to put the file on my SD card, and then flash it...
I'll stay with my Verizon bloatware, as soon as I get it back, I won't try again soon to do this ****!!!
Click to expand...
Click to collapse
You'll have to root again, ya know...
I have a Verizon Note 4 arriving today for use in Canada. The seller indicated that it is unlocked which I'm sure refers to the carrier and not the bootloader.
I've owned the Notes 1,2 and 3 and my most stable and satisfying experience was with the 3, not because it was the latest and greatest but because it was the only one I did not root and play around with. I'm getting older and I'm starting to value stability over features. I actually like stock touchwizz and enjoy the built in productivity of the spen. Carrier bloatware really is a minor inconvenience for me.
I've enjoyed the Note line but the Note 4 will be my last as the SD card and removable battery are very important to me. As long as this Verizon Note 4 gives me LTE coverage in the Greater Toronto area (which my research indicates it will) I'll keep it stock. A bonus would be if it shows up with Android 5.1.1 or is upgradeable via OTA or Kies. I don't really see any North American varient receiving Marshmallow and certainly not this Verizon one.
Can you flash N910W8 firmware/rom onto a N910V?
xDanny1992x said:
Hi, just bought an unlocked Note 4 from USA, it's the Verizon version.
I looked on your forum to find an answer, but I can't.
I'm from Canada, and I'd like to install a stock rom of the canadian version (n910w8), to have less Verizon/Amazon bloatware, and the french language available.
Considering that the N910W8 phone is pretty identical(from what I can see..), same CPU, would I brick my phone from installing this very rom "N910W8VLU1BOE2_N910W8OYA1BOE2_N910W8VLU1BOE2_HOME.tar.md5"?
And if so, why? And what are my alternatives?
Click to expand...
Click to collapse
Same here with a N910V wanting to know if N910W8 can flash ok to it. (but already unlocked mine with custom N910V roms on it) Been running LineageOS roms OK for a while but just too many bugs for something dependable.
Runs nice until you really need it not freezing on you lol.
Did try a custom W8 rom that was only flashable after installing TWRPCAN 3.0.2 in place of TWRP 3.2.3 and it did startup but phone ran really hot and broken WiFi so ended up going back.

Samsung note 2 TPH asking for network unlock code - URGENT!.

Hello, so I got myself in a kind of a big problem here.
I have a note 2 that was originally running tph 4.4.2 which had this modem N7105XXUFNE3 originally.
I got bored of the stock rom and I installed lineage os official 7.1.2., the installation ran without any issues whatsoever and I was really loving it, the phone was working perfectly with just minor bugs.
The rom provided an updater that allowed the users to choose which updates to download and install (all nightly).
I installed a couple manually via TWRP and it was all good but after one update whenever I turned on my phone it would ask me to write down the sim network unlock code which I found really weird. I thought it was a bug and I rebooted the phone but to no aveil.
after that I figured that the most recent updates to that rom would eventually fix the problem so I kept installing the updates to a point where my phone was stuck loading linease OS.
Somehow in the process of using apps2SD I forgot I had stored my backups in the sd card and I partitioned it...
Now I cameback to the stock rom which I've downloaded from a website which is not sammobile because sammobile's website is bugging and wont let me download the firmware. The rom is suposed to be TPH and comes packed with the same N7105XXUFNE3 moded of the 4.4.2 stock rom, but it still asks me to write down the sim network unlock code...
I don't understand why the hell is it locked if it's suposed to be a TPH rom, I also tried with another ROM (also tph) but I get the same problem, I've also tried to flush a different moded but it's still the same and I don't know what to do anymore.
I would really apreaciate if you could point me in the right direction to sort this problem out.
Much apreaciated in advance.
PS: this has made my work a lot difficult since my phone was a really important basis of my communication in regards to my job and I really need it to be functioning but ran out of ideas.

CPD1 bootloader to CQL1, tried with partialfirm stuck with CPD1

I tried flashing n910vvru2cql1 partial firmware in odin and phone info is still showing cpd1 as my bootloader.
history:
my phone was acting kinda buggy, wouldnt charge, turned off, got really hot about a year ago on a old version of RR and wasnt responding to anything usb so i threw it in a box and used one of my backups, a month ago or so, i moved some firmware files over by sdcard and flashed with twrp and it seems like it cleared up a lot of my issues.
I have been trying to get any rom past 6.0.1 on it and they just dont seem stable enough to run everyday so I found modest rom flashed that and it seemed pretty good except for the random restarts and lagg. i flashed flashpoint v4 kernel to try to clear problems up and it ran better but yet still kinda buggy so said screw it and flashed stock firmware cql1 kernel and over 2 days seems like everything cool except now im trying to get my bootloader up to CQL1 just so everything is unified and Sam Phone Info shows CPD1 for bootloader but CQL1 for pda, csc,baseband-radio
Are there any reason to upgrade bootloader since im already on 6.0.1 unlocked?
I wouldnt think so because my thoughts are its more like an efi bios/grub2/mbr which load the os and the kernel later gets lowerlevel access to the hardware????
Bottomline, I guess i would like to upgrade the bootloader, someone please clarify and help.
Thanks.
brianmilw said:
I tried flashing n910vvru2cql1 partial firmware in odin and phone info is still showing cpd1 as my bootloader.
history:
my phone was acting kinda buggy, wouldnt charge, turned off, got really hot about a year ago on a old version of RR and wasnt responding to anything usb so i threw it in a box and used one of my backups, a month ago or so, i moved some firmware files over by sdcard and flashed with twrp and it seems like it cleared up a lot of my issues.
I have been trying to get any rom past 6.0.1 on it and they just dont seem stable enough to run everyday so I found modest rom flashed that and it seemed pretty good except for the random restarts and lagg. i flashed flashpoint v4 kernel to try to clear problems up and it ran better but yet still kinda buggy so said screw it and flashed stock firmware cql1 kernel and over 2 days seems like everything cool except now im trying to get my bootloader up to CQL1 just so everything is unified and Sam Phone Info shows CPD1 for bootloader but CQL1 for pda, csc,baseband-radio
Are there any reason to upgrade bootloader since im already on 6.0.1 unlocked?
I wouldnt think so because my thoughts are its more like an efi bios/grub2/mbr which load the os and the kernel later gets lowerlevel access to the hardware????
Bottomline, I guess i would like to upgrade the bootloader, someone please clarify and help.
Thanks.
Click to expand...
Click to collapse
Sorry for responding late but in case anyone else is wondering, most partial firmwares that you see posted for our device model (even the ones posted in the international snapdragon rom threads that have Lineage, RR, and ported TW roms) do not contain the aboot.mbn file, aka bootloader. So it will not change our bootloader in anyway.
That's not say a dev or someone like myself who's just a beginner couldn't make a mistake and forget to remove it or maybe they don't know that it's supposed to be removed. So it would be best to stick with the tried and true links that have been posted of you're needing to update your modem. I know for certain the ones that have been posted by ripee, hsbadr, and me are safe, but I've never used not have heard anything negative about the other ones posted.
All that being said, you can update the SM-N910V bootloader if you'd like. Mine is updated to where it ends with CQI2 which is the penultimate update. If there is a difference between CQI2 and CPD1 (initial 6.0.1 bootloader) then it is a slight difference. Sometimes I think I just want to believe that tweaks and changes are working, especially if you put a lot of effort and time into it(which is required when you don't have much knowledge).
This was just posted recently;
VZW_NOTE4_EMMC_15_Chipset_Only_Bootloader_Unlock_U p/Dwngrade_Bootloaders_KK/LL/MM by jkruse
I haven't tried it yet but it looks much easier than the method I used, which is below;
For the folks that just like to tinker and break things....... How else you supposed to learn how to fix it?
How-To Update Your Bootloader from CPD1 to CQI2 by this fool

Categories

Resources