Related
I dont think the 3 button recovery mode "fix" that samsung released for Bell Canada i9000m and that was ported to work for other models is really a "Fix".
As dicussed in other threads, the original bug is on the PCB. It's a timing issue on the motherboard. The "fix" installs a software hook in the 4th level bootloader to the 3 buttons in order to trigger the recovery mode.
If you brick your phone such that it does not get to the 4BL stage ...
OR
If your phone freezes even after the 4BL stage ...
then you are **** out of luck.
Only a phone that had the 3BR working before the fix or a phone that gets a MB changed will be able to recover from being bricked.
This fix is only slightly better than installing a software that triggers recovery or using adb to force recovery mode. Basically it only works in conditions where you would not need recovery in the first place.
thats an assumption, but where is the proof and source?
I don't know about you but for me the recovery menu fix works great. I rooted my phone after I used that fix with the update.zip method so unless you have proves I think is better to not scary users.
I thought three limit was cause by the telco not Samsung? Read it from a post where the telco confirm they disable it.
Sent from my GT-I9000 using XDA App
The idea is I don't think Samsung replaced the motherboard of the mobile phones and the prove is that Samsung Canada or something posted a method to enable recovery mode back.
bigl666 said:
thats an assumption, but where is the proof and source?
Click to expand...
Click to collapse
I did say "I think".... but added an ? to the title.
Based my opinion on these posts:
http://forum.xda-developers.com/showpost.php?p=8217641&postcount=390
and the serious part of this one:
http://forum.xda-developers.com/showpost.php?p=8156981&postcount=287
My reply from another thread: http://forum.xda-developers.com/showthread.php?p=8230653
That was my first hypothetis when Samsung released the fix.
That's why I asked technical details and get some after contacting Samsung technical department, to finally speak with a tech, instead of those clueless helpdesk first and secondline helpdesk coworkers. But he couldn't give me more pointers, other than the original working 3br devices do not use the spl at all.
My hypothetis seems right if the bootloader gets overwritten by other firmware who's using spl on the respective partition.
My assumption, like I said before in this thread, is that the original 3br working devices gets triggered via the pcb, which loads the pbl with the safemode, if not on a dedicated module, maybe... That way, the users of such device can always be assured they can flash every firmware. This is how it's done with other many devices too. And that's exactly why I don't buy the story of 'not'-controlled batches by another guy here on the forums in another thread. I can understand why and that's why I'm so disappointed they continue to ship the phone with Android.
If you are like me, you need to test new firmware releases in order to test your own written code in Eclipse. Plus, I want the latest releases...
That's why I suggested to get your mobo replaced now you have the change, before Samsung goes with the spl fix as a standard procedure for future bricked phones.
But, for now, we will not know, unless somebody is disassembling a working 3br and a non working 3br device and have the electronic skills to confirm this.
Click to expand...
Click to collapse
blackdeath09 said:
I don't know about you but for me the recovery menu fix works great. I rooted my phone after I used that fix with the update.zip method so unless you have proves I think is better to not scary users.
Click to expand...
Click to collapse
There is no proof, if there was, there was probably a fix already or at least the technical details published.
xtrememorph said:
I thought three limit was cause by the telco not Samsung? Read it from a post where the telco confirm they disable it.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
No, I got my phone from a Samsung distro, not from any provider and it has 3br disabled.
blackdeath09 said:
The idea is I don't think Samsung replaced the motherboard of the mobile phones and the prove is that Samsung Canada or something posted a method to enable recovery mode back.
Click to expand...
Click to collapse
That could be, then if you have 3br enabled with a firmware without the integrated fix back, it's probably a new phone without replacement.
The prove that a temporary fix exist doesn't mean it's permanent, which is for the original 3br enabled devices.
So then someone should brick his phone after installed the fix and see if he can repair it back (as a user said in the original thread)
blackdeath09 said:
So then someone should brick his phone after installed the fix and see if he can repair it back (as a user said in the original thread)
Click to expand...
Click to collapse
Under what kind of circumstances?
That doesn't prove anything, other than the fix works if the sbl isn't overwritten.
Then flash back to a firmware who does without the fix and tell me the results.
I've read in http://forum.xda-developers.com/showthread.php?p=8230653 that someone flashed back and the fix is gone. Now you have your proof this fix isn't permanent, like I already said a bunch of times. I believe it was firmware JM1 if I can remember correctly. It was tested one time though. Try it and please report your results back.
Proof will come when someone bricks a phone other than by flashing firmware and can not use the 3BR combo even though the "fix" was applied.
Prroving that the "Fix" works is just about impossible. No reports of the condition described above will constitute proof that it works.
I do have an idea for a test:
- With battery fully charged, USB unplugged and phone off,
- Initiate 3BR.
- Calculate time to reach recovery screen.
Compare "fixed" phone with originally working one.
If different assume that fix is not as good as a real working 3BR phone.
My Buddy just had a bad flash and and bricked the phone.. and the recovery saved him so yes it does work....
he did not have the 3 buttons working before but did the update and started flashing roms.. and it saved him... its not a hardware issue.. its always been software.
so it does work.. if this fix didn't come out he would have a good door stop.
TriC_101 said:
My Buddy just had a bad flash and and bricked the phone.. and the recovery saved him so yes it does work....
Click to expand...
Click to collapse
Like I said, proof comes when someone recovers from a brick OTHER than because of a bad flash.
Because, in general, that doesnt touch the BL.
davidke said:
Like I said, proof comes when someone recovers from a brick OTHER than because of a bad flash.
Because, in general, that doesnt touch the BL.
Click to expand...
Click to collapse
why does it really matter? isn't that normally the problem anywayz, bricking from a bad flash?
but then again, this appears to be one of those you can't prove anything to be true, but only to be false scenarios...
TriC_101 said:
My Buddy just had a bad flash and and bricked the phone.. and the recovery saved him so yes it does work....
he did not have the 3 buttons working before but did the update and started flashing roms.. and it saved him... its not a hardware issue.. its always been software.
so it does work.. if this fix didn't come out he would have a good door stop.
Click to expand...
Click to collapse
I disagree.
Without pcb, rom and human-machine-interaction, there is no way the bootloader will load. So you are telling me it's not a hardware issue that 3br isn't working? I fully disagree. IT IS. Why? Because Android already have the recovery / download mode adressesed... Please study mobile phone architecture or at least computer architecture and how the android kernel and os works.
No one knows the exact architecture of sgs here, but one thing is for sure. 3br isn't working, because it doesn't get handled BEFORE spl... And if it is, it's disabled on purpose in bml1 and otherwise there is probably another rom, handling all 3 buttons first, before launching ipl.
Please tell your buddy to flash back to JM1 and let his phone brick and post back your results...
I hope Richthofen and / or some other members can exclude this theory by hexcomparing bml1 from working and not working 3br devices and analyze that, so we can exclude that. If it matches, then it's probably a hardware issue. Like I told you before... Android already adressed the safemode space. So the parameters must come via the 3 buttons by pcb. You are happy now?
Casio1987 said:
I hope Richthofen and / or some other members can exclude this theory by hexcomparing bml1 from working and not working 3br devices and analyze that, so we can exclude that. If it matches, then it's probably a hardware issue. Like I told you before... Android already adressed the safemode space. So the parameters must come via the 3 buttons by pcb. You are happy now?
Click to expand...
Click to collapse
It seems BML1 to BML4 that triggers 3BR recovery mode are differents between countries and could be related to CSC version.
So it seems to be a software problem.
Until you dont flash BLM/SPL everything will be fine, just check before flashing.
I find it hard to believe that it would be a hardware issue.
The first retail European I9000 phones had I9000XXJF3 factory firmware version.
As far as I know all of them had a functional 3-button "wake" function for download and recovery modes.
When Samsung started using I9000XXJM1 as a factory firmware, I have seen only one phone with a functional "3-button wake". And even with that one I could not tell if it was a brand new one or a factory refurbished one.
For some odd reason the first release using the new secondary bootloader was I9000XXJM1. All of the previous versions (from I9000XXJE2 thru I9000XWJFF) have been using the same bootloader. As far as I know none of these phones ever had problems.
Also there is no indication that Samsung would have modified the hardware.
Samsung always makes bulletin about the changes in hardware and I have not seen any. Also the hardware revision has remained the same from the start.
Richthofen said:
I find it hard to believe that it would be a hardware issue.
The first retail European I9000 phones had I9000XXJF3 factory firmware version.
As far as I know all of them had a functional 3-button "wake" function for download and recovery modes.
When Samsung started using I9000XXJM1 as a factory firmware, I have seen only one phone with a functional "3-button wake". And even with that one I could not tell if it was a brand new one or a factory refurbished one.
For some odd reason the first release using the new secondary bootloader was I9000XXJM1. All of the previous versions (from I9000XXJE2 thru I9000XWJFF) have been using the same bootloader. As far as I know none of these phones ever had problems.
Also there is no indication that Samsung would have modified the hardware.
Samsung always makes bulletin about the changes in hardware and I have not seen any. Also the hardware revision has remained the same from the start.
Click to expand...
Click to collapse
Very odd indeed, because how is it possible that some have working 3br and others not with the same firmware jm1, coming from the same csc, coming from the same batch? Maybe the 8gb differs from the 16gb (I don't think so). Maybe asked too much, but it would be great if people can start publishing all their bml's, with the exception of the containing imei.
Because the safemode must be somewhere and it isn't in bml4.
Maybe there is a special ic for it, but it's locked for the 3br disabled phones and it's overridden by the sbl.
Are you sure there isn't a special module with the safemode in it?
That would clarify why the hw still preserves the same revision.
Casio1987 said:
I disagree.
Without pcb, rom and human-machine-interaction, there is no way the bootloader will load. So you are telling me it's not a hardware issue that 3br isn't working? I fully disagree. IT IS. Why? Because Android already have the recovery / download mode adressesed... Please study mobile phone architecture or at least computer architecture and how the android kernel and os works.
No one knows the exact architecture of sgs here, but one thing is for sure. 3br isn't working, because it doesn't get handled BEFORE spl... And if it is, it's disabled on purpose in bml1 and otherwise there is probably another rom, handling all 3 buttons first, before launching ipl.
Please tell your buddy to flash back to JM1 and let his phone brick and post back your results...
Click to expand...
Click to collapse
I do know how phone architecture works and computer architecture as well....... in the end its very simple... it works its saved lots of people from having a bricked phone.. and the recovery mode is different between countries. besides you should not be flashing the SPL/BLM in the 1st place. and like you said your self you don't know how the exact architecture works on the SGS so how can you say its not a software issue. if you fully don't understand it.
I have a i9300 16GB.
1.It was bought from another country. Can I still get warranty from my country? do I need to ship it back to the same country if something happens.
2. If my firmware is updated (as Kies says), is my device safe from sudden death?(it says that "this is the lates firmware")
3. Should I keep the 4.1.2 official ROM or should I replace it with a better phone? is it bad?
4.Is it ok to use a magnetic pouch ?
silvercats said:
I have a i9300 16GB.
1.It was bought from another country. Can I still get warranty from my country? do I need to ship it back to the same country if something happens.
2. If my firmware is updated (as Kies says), is my device safe from sudden death?(it says that "this is the lates firmware")
3. Should I keep the 4.1.2 official ROM or should I replace it with a better phone? is it bad?
4.Is it ok to use a magnetic pouch ?
Click to expand...
Click to collapse
For starters, this is the i747/i747m forum.
If you ever have any issues that may require you to return the device, call samsung and they will take care of the rest. You must be the original owner to be covered under the 1-year warranty. I'm not sure what you mean by "sudden death" but before updating your firmware, it's always recommended to backup your data.
silvercats said:
I have a i9300 16GB.
1.It was bought from another country. Can I still get warranty from my country? do I need to ship it back to the same country if something happens.
2. If my firmware is updated (as Kies says), is my device safe from sudden death?(it says that "this is the lates firmware")
3. Should I keep the 4.1.2 official ROM or should I replace it with a better phone? is it bad?
4.Is it ok to use a magnetic pouch ?
Click to expand...
Click to collapse
You are in the incorrect devices forum. This forum is specifically for i747 and i747m (US/Canadian devices. Not international) These questions would better be asked here: http://forum.xda-developers.com/forumdisplay.php?f=1569
Sent from my SGH-I747 using xda app-developers app
Hello,
2 Days ago my phone unlocked galaxy note 2 in the uk stopped working in the middle of the night, no idea how, My borthers phone stopped the same night also.
My friends note 2 got an OTA update the next morning but his is working fine.
SInce then my phone wont go past the first boot screen, it is completely stock and has no custom rom or root.
I took it to a samsung repair centre they put it in DL mode and they said i had a custom rom and they cant help..
Iv come home and i have tried to now flash a new firmware, i have then tried to flash CWM via odin but it comes up with a message..
No pit partition
then it fails...
Anyone have any ideas? what has caused this the OTA update? Both me and my brother bought the phones directly through samsung trade but my friend bought his through phones 4 u..
The update my friend got was N7100xxdmb2
ANy ideas or help is greatly appreciated
What exactly information (lt upper) you getting on download mode?
Any light blink on charging device?
Sent from my GT-N7100 using xda premium
dr.ketan said:
What exactly information (lt upper) you getting on download mode?
Any light blink on charging device?
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
HI and thanks for quick response!
When i plug in to charge i get a single red flash on the further left light, then the battery image appears witht he spinning circle but then it freezes there, the usual green battery filling doesnt occur. When i disconnect the screen is frozen witht eh battery picture on screen.
In download mode i get:
Odin Mode (in red)
Product name :
Custom Binary Download :NO
Current BInary : Samsung Official
System status: Custom
Thanks again
Sorry to say but yes its bricked, and this is happened due to bug in older rom. It's sds (sudden death syndrome)
Another thing your binary counter on download mode is 'no'
And they can't reject earranty claim, you have to convince them. Otherwise you have to pay for it and you will need to change motherboard, which is costly.
Sent from my GT-N7100 using xda premium
dr.ketan said:
Sorry to say but yes its bricked, and this is happened due to bug in older rom. It's sds (sudden death syndrome)
Another thing your binary counter on download mode is 'no'
And they can't reject earranty claim, you have to convince them. Otherwise you have to pay for it and you will need to change motherboard, which is costly.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Ok thats a shame, pretty poor in my opinion..
Has this affected many others? and was it caused by the OTA update failing or something?
Thanks for the help and i assume that you are certain that i cant fix with software?
Yes there are lots of people affected by this bug just search sds /sudden death in forum. This is purely poor samsung crap and s3 and note2 both devices have same bug (badically faulty emmc chip), you can't fix it with sw once it bricked, latest rom 4.1.2 released in 2013 have fixed for it, but that just can prevent device from getting bricked, who already have bricked have to just replace motherboard.
Sorry and I can feel for it. But you should not put down and let them to know about it to reclaim warranty.
Your downloaf mode information don't suggest you had custom rom, and all the sds victims have same information and got replacement.
Sent from my GT-N7100 using xda premium
dr.ketan said:
Yes there are lots of people affected by this bug just search sds /sudden death in forum. This is purely poor samsung crap and s3 and note2 both devices have same bug (badically faulty emmc chip), you can't fix it with sw once it bricked, latest rom 4.1.2 released in 2013 have fixed for it, but that just can prevent device from getting bricked, who already have bricked have to just replace motherboard.
Sorry and I can feel for it. But you should not put down and let them to know about it to reclaim warranty.
Your downloaf mode information don't suggest you had custom rom, and all the sds victims have same information and got replacement.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
really annoying but... im sure in time i will get over it!
thanks for the help and the reply.
just one last question - when the system status says : custom , what exactly does this mean? and what's the difference between that and official. i am asking as i want to make sure im armed with enough information should they decide to get all official with me!
thanks again.
It should official but
I have seen lots cases who never have flashed any custom stuff and having status Modified, so I think they won't Stand up with argument. Yes if your binary download is non zero then it certainly proves you have flashed custom stuff. I have seen more than 20 sds cases on note2 and I really not remember if anyone have status 'official' and I believe this sds issue itself causing status Modified.
Sent from my GT-N7100 using xda premium
dr.ketan said:
It should official but
I have seen lots cases who never have flashed any custom stuff and having status Modified, so I think they won't Stand up with argument. Yes if your binary download is non zero then it certainly proves you have flashed custom stuff. I have seen more than 20 sds cases on note2 and I really not remember if anyone have status 'official' and I believe this sds issue itself causing status Modified.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
So do we have a solution as of date? what can be done or something?
Just upgrade your FW. Fix has been implemented since January, 2013 in Samsung FWs.
I have the same problem
Memphis_ said:
Just upgrade your FW. Fix has been implemented since January, 2013 in Samsung FWs.
Click to expand...
Click to collapse
it sounds like upgrading would fix this problem.. right?
how about the photos and stuff? am i gonna lose all of that??
---------- Post added at 12:25 PM ---------- Previous post was at 12:21 PM ----------
talboy said:
Hello,
2 Days ago my phone unlocked galaxy note 2 in the uk stopped working in the middle of the night, no idea how, My borthers phone stopped the same night also.
My friends note 2 got an OTA update the next morning but his is working fine.
SInce then my phone wont go past the first boot screen, it is completely stock and has no custom rom or root.
I took it to a samsung repair centre they put it in DL mode and they said i had a custom rom and they cant help..
Iv come home and i have tried to now flash a new firmware, i have then tried to flash CWM via odin but it comes up with a message..
No pit partition
then it fails...
Anyone have any ideas? what has caused this the OTA update? Both me and my brother bought the phones directly through samsung trade but my friend bought his through phones 4 u..
The update my friend got was N7100xxdmb2
ANy ideas or help is greatly appreciated
Click to expand...
Click to collapse
hey, i have the SAME problem here. i'm wondering you got fixed or not. i have unlocked on so don't even know where i should go for warranty because i got it from Amazon.
I am having the exact problem as the OP. Were you able to fix it? I got my phone from eBay, contacted Samsung Canada, and they said I'd have to go contact Samsung Hong Kong
hii
Who sells a motherboard for Note 2 ???
I rooted my a325m by patching the stock AP file with magisk, had to use FRP hijacker by hagard to be able to flash the patched file. I root uninstalled several apps for debloating. The phone worked fine for like a couple of weeks, and now, suddenly I find there's the no SIM indication, and in settings -> about phone it says IMEI: unknown, and in software information it says bandbase version: unknown.
The firmware version I used was exactly the same as when I bought it, A325MUBU2AUJ4, with the right csc (ARO in my case).
EDIT: after a couple reboots, the bandbase version now shows, but still no IMEI or SIM detected.
Can anyone help me? What happened? What can I do? Thanks in advance!
flash all the with odin the correct rom. the twrp unstable and more like shell and who knows what bugs have magisk. until why have a good recovery i would no root my phone reallly if you want to unisstall the software from samsung and google i would say to use the universal debload https://github.com/0x192/universal-android-debloater.
UPDATE: it got unknown baseband againI
I relocked the bootloader and now in download mode I have an option to "show barcodes" pressing the side button. The barcodes show the right IMEI and serial number. Maybe stuff wasn't erased, just inaccesible by the rom?
I was told by a technician to flash the original ROM (already did) then root again. Tried several versions but not an older bandbase because downgrade is forbidden by the bootloader, apparently, to no avail. Would try a newer baseband but i'm afraid it will not work and will be unable to go back to the origial baseband version.
Weird thing is, there is the EFS directory but no /data/nvram or /dev/nvram
Same happened to me.
I tried everything I could think of to get the IMEI back and couldn't.
It was still under warranty and I took it to Samsung.
Before taking it I unrooted it and locked it again.
They fixed it for me with no problem.
edukardo said:
Same happened to me.
I tried everything I could think of to get the IMEI back and couldn't.
It was still under warranty and I took it to Samsung.
Before taking it I unrooted it and locked it again.
They fixed it for me with no problem.
Click to expand...
Click to collapse
How did you root it?
as I understand, after rooting, warranty is void since it implies flashing a magisk patched boot image or AP tar. In my case I was indeed able to relock the bootloader and flash the original firmware but upon entering download mode, it shows "warranty void 0x01".
was it the same in your case?
Flashed original firmware, relocked phone, and then went to Samsung Office. I had no problem with it
edukardo said:
Flashed original firmware, relocked phone, and then went to Samsung Office. I had no problem with it
Click to expand...
Click to collapse
most likely the warranty vod bit was on (you can check it yoursef by entering odin mode) and they didn't notice
so you got it fixed for free?
did they mention what did the fix consist in? I heard they say they change the motherboard, which is a lie, they just write the nvram or efs with the right stuff
ah sos de argentina? lol where did you take it? to a samsung store? I'm from neuquen and got it at musimundo, but here's a samgung store too
myself i was thinking of waiting for an update which should be soon, lock bootloader, flash some official rom and pull off the cable so it gives an upgrade error and doesn't enter download mode, then take it to the store
Unroot before update and unlock
wipe the cache partition . then reset the phone using recovery mode . this is at you own risk .
did you fix it?
applesucksLmao said:
did you fix it?
Click to expand...
Click to collapse
nope, went to samsung, got rejected cause warranty bit on, no choice but take it to a service and I suppose they could do something with Chimera Tool, Z3X or something like that, which, as I've seen, claims to fix it in minutes (and the client gets charged handsomely, like 100 USD)
From Samsung I got the same bullsh*t I read in some threads: "this phone has been tampered with and it's a hardware problem, the board must be replaced"
For the technically savvy, I got a strange Magisk log which kind of looks like it may be the problem. It seems to try to "unlock"* some devices on bootup but gets "permission denied". One of them may be the nvram or something like that. I have an EFS directory but no NVRAM directory anywhere or /dev/nvram.
very strange, i guess we gotta not use magisk until its bug fixed.. i have seen other people have the same problem too, but anyways, i sent my phone to get probably JTagged for 54 us dollars, if they fix it well, great right, but if they dont i guess ill have to buy another motherboard from samsung or go to another city... and the best part is that while my phone is there, im using an S4 mini from 2013 with custom android 11 rom hehe
i saw that auh firmware causes empty imei in another thread and to flash aug, maybe you could try this? https://forum.xda-developers.com/t/has-anyone-successfully-rooted-this-a32-4g.4326193/post-85788523
applesucksLmao said:
very strange, i guess we gotta not use magisk until its bug fixed.. i have seen other people have the same problem too, but anyways, i sent my phone to get probably JTagged for 54 us dollars, if they fix it well, great right, but if they dont i guess ill have to buy another motherboard from samsung or go to another city... and the best part is that while my phone is there, im using an S4 mini from 2013 with custom android 11 rom hehe
Click to expand...
Click to collapse
or atleast use magisk with aug or even older firmware if you can... is your a32 A325M or A325F?
well, your firmware is A325MUB"U2"AUJ4 and that means u cant downgrade to older versions that have binary1 so maybe you could try using samsung's new version which was released past month
applesucksLmao said:
very strange, i guess we gotta not use magisk until its bug fixed.. i have seen other people have the same problem too, but anyways, i sent my phone to get probably JTagged for 54 us dollars, if they fix it well, great right, but if they dont i guess ill have to buy another motherboard from samsung or go to another city... and the best part is that while my phone is there, im using an S4 mini from 2013 with custom android 11 rom hehe
Click to expand...
Click to collapse
what's JTagged?
applesucksLmao said:
i saw that auh firmware causes empty imei in another thread and to flash aug, maybe you could try this? https://forum.xda-developers.com/t/has-anyone-successfully-rooted-this-a32-4g.4326193/post-85788523
Click to expand...
Click to collapse
I found it impossible to downgrade, download mode doesn't allow it. Couldn't find a tutorial to do it either.
applesucksLmao said:
well, your firmware is A325MUB"U2"AUJ4 and that means u cant downgrade to older versions that have binary1 so maybe you could try using samsung's new version which was released past month
Click to expand...
Click to collapse
I did, I tried all combinations rooting/unrooting with the new magisk 24.1 the new version, A325MUBS2AVA1
It's a 325m btw
ok so, i was using my phone normally yesterday, but out of nowhere, my SIM card stopped working and i couldn't use mobile internet/calls anymore. So i checked my settings and i saw my IMEI was marked as unknown, the same with baseband.
The A32 version:
Samsung Galaxy A32 4G SM-A325M (4gb ram) Brazil ZVV/ZTO
What i tried:
- Flashed the right files in odin (CSC, magisk patched AP, BL and CP)
- Tried using 3 different IMEI editors (imei changer free, imei changer pro and device emulator)
- Tried to download a program called Samsung Tool Pro by z3x, but every download was without the crack and the only one that worked was an old 2019 version
- Factory reseted before flashing those files
My phone was rooted working normally for 2 months, cuz i rooted it when samsung introduced ram plus on the november update
I just installed that chinese app WeChat from the samsung galaxy store, just to check it out.... but i dont think hes the cause
thanks for any help , and dont tell me to pay for software, if you can just send me the crack lol (not in xda... atleast not here in this thread)
Network reset and clear sim toolkit.
Try resetting the sim card*.
Replace sim card if that doesn't work.
Handle the new sim card like stick of ram.
ESD sensitive. Any static discharge can damage it. Failure may be immediately or could take days, weeks even years to manifest itself.
*the no imei bothers me, maybe it's more than a sim card failure. If so... a rootkit is a possibility or a mobo failure.
blackhawk said:
Network reset and clear sim toolkit.
Try resetting the sim card*.
Replace sim card if that doesn't work.
Handle the new sim card like stick of ram.
ESD sensitive. Any static discharge can damage it. Failure may be immediately or could take days, weeks even years to manifest itself.
*the no imei bothers me, maybe it's more than a sim card failure. If so... a rootkit is a possibility or a mobo failure.
Click to expand...
Click to collapse
well, i reseted network again because i hard resetted and reflashed the rom. There's no sim card toolkit here, before resetting, there was an icon but it wouldnt work. I'll try another sim card from a working cellphone to see if it works, but probably won't due to unknown imei....
well, i'm sending it to Samsung...
applesucksLmao said:
well, i'm sending it to Samsung...
Click to expand...
Click to collapse
You in the US?
blackhawk said:
You in the US?
Click to expand...
Click to collapse
no, brazil
applesucksLmao said:
no, brazil
Click to expand...
Click to collapse
In the US you have Samsung Experience Centers at Best Buys. Guess send it in...
blackhawk said:
In the US you have Samsung Experience Centers at Best Buys. Guess send it in...
Click to expand...
Click to collapse
to the us? how lol, and here in brazil we got samsung repair shops too
samsung said cuz the bootloader is unlocked they couldnt fix and they said its MOTHERBOARD problems (??) what the actual frick
applesucksLmao said:
samsung said cuz the bootloader is unlocked they couldnt fix and they said its MOTHERBOARD problems (??) what the actual frick
Click to expand...
Click to collapse
Yeah Samsung will do that. They don't like rooted phones. I run stock Samsung's as they can run very well as such once optimized. So I'm be no means an expert on troubleshooting a rooted phone...
If you're rooted (or even if not) you need to be very careful with what 3rd apps you load.
Keep WeChat, FB, Instagram, WhatsApp, etc off the phone. If you can't log into them via the browser, don't use them.
Zero trust level for China software.
You may have inadvertently clicked a download link, been tricked into downloading or otherwise brought in a trojan or rootkit.
I would consider the phone to be infected until proven clean. Scrutinize your saved data carefully for malicious files if infected. Isolate it.
Found this. I don't know if that applies to newer Androids. Do some Google searches.
blackhawk said:
Yeah Samsung will do that. They don't like rooted phones. I run stock Samsung's as they can run very well as such once optimized. So I'm be no means an expert on troubleshooting a rooted phone...
If you're rooted (or even if not) you need to be very careful with what 3rd apps you load.
Keep WeChat, FB, Instagram, WhatsApp, etc off the phone. If you can't log into them via the browser, don't use them.
Zero trust level for China software.
You may have inadvertently clicked a download link, been tricked into downloading or otherwise brought in a trojan or rootkit.
I would consider the phone to be infected until proven clean. Scrutinize your saved data carefully for malicious files if infected. Isolate it.
Found this. I don't know if that applies to newer Androids. Do some Google searches.
Click to expand...
Click to collapse
yeah i tried all of this websites, reflashed all odin files even bootloader, flashed with magisk and without.... efs pro just crashes while trying to detect my phone... guess ill take it to a local repair service because i dont have the box or that paid software, and also for some reason samsung fricked the fingerprint reader (it wont work anymore lol)... thanks for trying to help me hehe and sorry for late answer
blackhawk said:
Yeah Samsung will do that. They don't like rooted phones. I run stock Samsung's as they can run very well as such once optimized. So I'm be no means an expert on troubleshooting a rooted phone...
If you're rooted (or even if not) you need to be very careful with what 3rd apps you load.
Keep WeChat, FB, Instagram, WhatsApp, etc off the phone. If you can't log into them via the browser, don't use them.
Zero trust level for China software.
You may have inadvertently clicked a download link, been tricked into downloading or otherwise brought in a trojan or rootkit.
I would consider the phone to be infected until proven clean. Scrutinize your saved data carefully for malicious files if infected. Isolate it.
Found this. I don't know if that applies to newer Androids. Do some Google searches.
Click to expand...
Click to collapse
and no i didnt click any link, i downloaded wechat from the GALAXY STORE some hours before, it just happened while scrolling instagram
applesucksLmao said:
and no i didnt click any link, i downloaded wechat from the GALAXY STORE some hours before, it just happened while scrolling instagram
Click to expand...
Click to collapse
FB, Instagram, Twitter, WhatsApp, Tic-tok etc are malware. A playground of predators, disinformation and censorship. If I can't log onto and use a forum through the browser, I avoid it.
Loading social media apps is a security risk. Zero reasons for them to be running as an app.
I've seen malware bypass the security settings on the Samsung browser and download unauthorized. A trojan preloader (how cute) but I found and deleted it before it could get it's payload. Not sure how it did that and it hasn't happened again but I'm more careful how I excite bad sites now too. The Brave browser hasn't ever been breached as best as I can tell.
In your case a rootkit be the prime suspect if it's not a hardware failure. Maybe just a random hardware failure... and have nothing to do with what you were doing.
blackhawk said:
FB, Instagram, Twitter, WhatsApp, Tic-tok etc are malware. A playground of predators, disinformation and censorship. If I can't log onto and use a forum through the browser, I avoid it.
Loading social media apps is a security risk. Zero reasons for them to be running as an app.
I've seen malware bypass the security settings on the Samsung browser and download unauthorized. A trojan preloader (how cute) but I found and deleted it before it could get it's payload. Not sure how it did that and it hasn't happened again but I'm more careful how I excite bad sites now too. The Brave browser hasn't ever been breached as best as I can tell.
In your case a rootkit be the prime suspect if it's not a hardware failure. Maybe just a random hardware failure... and have nothing to do with what you were doing.
Click to expand...
Click to collapse
so... how can i remove this rootkit? i even repartitioned and nand erased using odin
applesucksLmao said:
so... how can i remove this rootkit? i even repartitioned and nand erased using odin
Click to expand...
Click to collapse
Which Android version are you using?
applesucksLmao said:
ok so, i was using my phone normally yesterday, but out of nowhere, my SIM card stopped working and i couldn't use mobile internet/calls anymore. So i checked my settings and i saw my IMEI was marked as unknown, the same with baseband.
The A32 version:
Samsung Galaxy A32 4G SM-A325M (4gb ram) Brazil ZVV/ZTO
What i tried:
- Flashed the right files in odin (CSC, magisk patched AP, BL and CP)
- Tried using 3 different IMEI editors (imei changer free, imei changer pro and device emulator)
- Tried to download a program called Samsung Tool Pro by z3x, but every download was without the crack and the only one that worked was an old 2019 version
- Factory reseted before flashing those files
My phone was rooted working normally for 2 months, cuz i rooted it when samsung introduced ram plus on the november update
I just installed that chinese app WeChat from the samsung galaxy store, just to check it out.... but i dont think hes the cause
thanks for any help , and dont tell me to pay for software, if you can just send me the crack lol (not in xda... atleast not here in this thread)
Click to expand...
Click to collapse
Forgive me, but 'out of nowhere' just doesn't happen. No third party app or even first party one could change your IMEI. The only way to have access to all partitions is to unlock bootloader and use custom recovery. In most situations, unless your persist partition is corrupted, you can restore your phone.
You must recreate the steps you took, which caused this problem and depending on what you did, you might be able to restore your original IMEI, but if your persist partition is screwed and you don't have its backup, your only option is to pay Samsung to restore your phone. Even if your have a 'cracked' Samsung flasher, you won't be able to restore persist partition, you can't use persist from another Samsung either.
Next time, the first thing after unlocking bootloader, should be backing up your persist partition.
optimumpro said:
Forgive me, but 'out of nowhere' just doesn't happen. No third party app or even first party one could change your IMEI. The only way to have access to all partitions is to unlock bootloader and use custom recovery. In most situations, unless your persist partition is corrupted, you can restore your phone.
You must recreate the steps you took, which caused this problem and depending on what you did, you might be able to restore your original IMEI, but if your persist partition is screwed and you don't have its backup, your only option is to pay Samsung to restore your phone. Even if your have a 'cracked' Samsung flasher, you won't be able to restore persist partition, you can't use persist from another Samsung either.
Next time, the first thing after unlocking bootloader, should be backing up your persist partition.
Click to expand...
Click to collapse
Is the persist partition part of the /boot partition?
I'm curious...
blackhawk said:
Is the persist partition part of the /boot partition?
I'm curious...
Click to expand...
Click to collapse
No. It's a separate partition.
optimumpro said:
No. It's a separate partition.
Click to expand...
Click to collapse
So normally if you were to flash a stock rom the persist partition would/should not be touched?
Is there a comprehensive guide to this that lists all the partitions and their function?
blackhawk said:
So normally if you were to flash a stock rom the persist partition would/should not be touched?
Is there a comprehensive guide to this that lists all the partitions and their function?
Click to expand...
Click to collapse
Persist partitions don't get touched by any flashing. There is no guide, and even even if you can list all partitions, that won't help you with persist. So, use MSM flasher, if it exists for your phone. If that doesn't fix the problem, you need to pay Samsung.