Develop Bugs

3 Button Fix is not really a "Fix"?

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.

T-mobile S4 Stock Android 4.3, Cannot Unlock, IMEI unknown after attempt by localshop

Hi All,
I had purchased T-Mobile Samsung Galaxy S4 (SGH-M919) with Stock android 4.3 while I was in usa, and want to use it in my home country now as I have left usa. I couldn't found any unlock solution on internet for stock android 4.3, and T-Mobile would not give me the unlock code. I tried third party services to provide unlock code and it did not work either. So I went to a local shop, and he screwed everything up. When I went back to the local shop to receive my phone (hoping it might have been definitely unlocked by them), he told me that he tried to downgrade it to 4.2.2 but it did not work (only after reading through all the forums I realize there is no way to go back to stock 4.2.2 if you are on stock 4.3 because of knox / bootloader issues on 4.3, leads me to think the shopowner did not really do his research before touching my phone, and no, he did not do any EFS backup). In an attempt to unlock my phone, he also flashed Metro PCS stock ROM on my phone, not to mention, my IMEI number is also 'Unknown' now. I managed to get back on T-Mobile stock 4.3 ROM now but still IMEI is unknown. I also tried to go to nearest Samsung center and they said they would not touch international phone models. At this point I have no idea what to do. Any suggestions how to get back my IMEI and or at the least to get the phone working to my country's network?
Thanks.

Try flashing the mk2 modem using odin. That may work but not sure.
Sent from my SGH-M919 using Tapatalk

Shop just need to pay you for new phone.
☞ Sent from here☜???

I won't provide a link but there are ways to restore your imei and as for unlocking I have used fast gsm dot com and it has worked every time. I hope u get ur issues fixed. Good luck
Sent from my SGH-M919 using Tapatalk

sd_N said:
I won't provide a link but there are ways to restore your imei and as for unlocking I have used fast gsm dot com and it has worked every time. I hope u get ur issues fixed. Good luck
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Hi sd_N, is it possible for you to provide me the link in private so I can just restore my original imei. I will then try fastgsm.com to unlock as you suggested. Thanks.

Anyone?

galaxysiv said:
Anyone?
Click to expand...
Click to collapse
Did you ever make any nandroid backups through recovery or save your /efs?

xdapowerapps said:
Did you ever make any nandroid backups through recovery or save your /efs?
Click to expand...
Click to collapse
Hi xdapowerapps, no I did not, I didnt knew the local shop would try to downgrade or flash METRO PCS rom on it :crying:

galaxysiv said:
Hi xdapowerapps, no I did not, I didnt knew the local shop would try to downgrade or flash METRO PCS rom on it :crying:
Click to expand...
Click to collapse
The local shop broke it. Tell them to pay for it.
Also, the only reason T Mobile won't give you an unlock code is if the phone isn't paid for in full. If the phone is paid for in full, they HAVE to give you the unlock code.
Are you sure you didn't buy the phone in the US, then leave the country without paying the bill so you could use the phone internationally without paying full price? If not, there is no reason T Mobile wouldn't give you the unlock code. So there's some missing information in this story.
Also, we do not discuss how to change IMEI's on XDA. The only thing permissable on XDA about flashing IMEI's is restoring YOUR OWN IMEI from a backup. That is done by restoring the EFS partition. But you didn't have a back up so you can't do that. That means anyway to fix your IMEI involves what is an illegal hack and that discussion is expressly not permitted on XDA. That information is used for illegal purposes and XDA is not going to be the place where it's shared for legal reasons.

Skipjacks said:
The local shop broke it. Tell them to pay for it.
Also, the only reason T Mobile won't give you an unlock code is if the phone isn't paid for in full. If the phone is paid for in full, they HAVE to give you the unlock code.
Are you sure you didn't buy the phone in the US, then leave the country without paying the bill so you could use the phone internationally without paying full price? If not, there is no reason T Mobile wouldn't give you the unlock code. So there's some missing information in this story.
Also, we do not discuss how to change IMEI's on XDA. The only thing permissable on XDA about flashing IMEI's is restoring YOUR OWN IMEI from a backup. That is done by restoring the EFS partition. But you didn't have a back up so you can't do that. That means anyway to fix your IMEI involves what is an illegal hack and that discussion is expressly not permitted on XDA. That information is used for illegal purposes and XDA is not going to be the place where it's shared for I also still see the imei folder inside EFS with a file mps_code.bat, but no nv files. (The imei folder was not regenerated on deletion either) Am I missing something? also still see the imei folder inside EFS with a file mps_code.bat, but no nv files. (The imei folder was not regenerated on deletion either) Am I missing something? egal reasons.
Click to expand...
Click to collapse
Hi skipjacks, thanks for responding. Nothing is pending with t-mobile, I was on prepaid account. I bought the phone like 10 days before leaving usa (due to emergency). T-mobile says my number on this new device should have being working for at least 45 days or so with refill balance. My cycle ended after 15 days of purchase and I really didnt see any reason to refill it as I was no more in usa. And no, I dont want to CHANGE my IMEI, only want to restore my own IMEI only. I am not sure if my EFS partition is corrupted, because I rooted my phone tried to backup EFS folder now (I know its too late but still), deleted it and rebooted (as a few threads suggested it would regenerate nv data files), but neither did I see any nv files when I did a back up now, nor after I rebooted. When I rebooted, the EFS folder did regenerate but there were no nv files in there. Also, after deleting EFS and regeneration the serial number was corrupted, but when I restored my backup, the serial number showed up correctly again. Also my current backup contains the imei folder with mps.code_bat file. I noticed that even imei folder was not regenerated on deletion of EFS and reboot. I somehow have the feeling that this is still indicating that my original EFS folder is still present (though I may be wrong, because I dont know). But my concern is the nv data files, which I dont see anywhere. I did come across several threads about imei corruption and restoration, but the only one I didnt come across was T-mobile SGH-M919 with stock android 4.3. I am wondering if this has some different file storage structure for imei (which again I dont know). At this point I am concerned about getting back my imei, I can get the unlock code from some reputed paid service again. I understand that open discussion about imei involving anything CHANGING IMEI is not allowed here. If anyone could just help me out restoring my original imei, even by pm, I would really appreciate it. I just dont want to throw away the phone and lose my money because of the error done by repair shop.

galaxysiv said:
Hi skipjacks, thanks for responding. Nothing is pending with t-mobile, I was on prepaid account. I bought the phone like 10 days before leaving usa (due to emergency). T-mobile says my number on this new device should have being working for at least 45 days or so with refill balance. My cycle ended after 15 days of purchase and I really didnt see any reason to refill it as I was no more in usa. And no, I dont want to CHANGE my IMEI, only want to restore my own IMEI only. I am not sure if my EFS partition is corrupted, because I rooted my phone tried to backup EFS folder now (I know its too late but still), deleted it and rebooted (as a few threads suggested it would regenerate nv data files), but neither did I see any nv files when I did a back up now, nor after I rebooted. When I rebooted, the EFS folder did regenerate but there were no nv files in there. Also, after deleting EFS and regeneration the serial number was corrupted, but when I restored my backup, the serial number showed up correctly again. Also my current backup contains the imei folder with mps.code_bat file. I noticed that even imei folder was not regenerated on deletion of EFS and reboot. I somehow have the feeling that this is still indicating that my original EFS folder is still present (though I may be wrong, because I dont know). But my concern is the nv data files, which I dont see anywhere. I did come across several threads about imei corruption and restoration, but the only one I didnt come across was T-mobile SGH-M919 with stock android 4.3. I am wondering if this has some different file storage structure for imei (which again I dont know). At this point I am concerned about getting back my imei, I can get the unlock code from some reputed paid service again. I understand that open discussion about imei involving anything CHANGING IMEI is not allowed here. If anyone could just help me out restoring my original imei, even by pm, I would really appreciate it. I just dont want to throw away the phone and lose my money because of the error done by repair shop.
Click to expand...
Click to collapse
First off....the enter key is your friend. Hit it every so often when typing giant blocks of text like that. :laugh:
Second, since your IMEI has been deleted, you now have to change it, even if you just want to change it back to what it was before. The process to fix it now is what can't be discussed here.
IF you had backed up your EFS partition, then it would be as simple as restoring it in recovery. That's all well and good. But your IMEI is now 0, so you have to change it to what it was.
But all that aside, you went to a store and they broke it. Take it back there and raise holy hell until they fix it for you or buy you a new one. I know consumer protections are stronger in some countries than others, but wherever you are, yelling and screaming is a universal language.

Skipjacks said:
First off....the enter key is your friend. Hit it every so often when typing giant blocks of text like that. :laugh:
yelling and screaming is a universal language.
Click to expand...
Click to collapse
You
learn
new
things
every
day. :silly:

Can someone at least tell me what file in T-Mobile Galaxy S4 SGH-M919 Stock Android 4.3 contains imei number, so at least I know if I even have that file or not or whether it is missing? Thanks.

galaxysiv said:
Can someone at least tell me what file in T-Mobile Galaxy S4 SGH-M919 Stock Android 4.3 contains imei number, so at least I know if I even have that file or not or whether it is missing? Thanks.
Click to expand...
Click to collapse
Whether your file is missing, modified, or corrupted, you need your /efs folder to restore it. You do not have have a nandroid backup or the /efs folder. I am sorry but the simplest we can put it without sounding harsh, you're screwed. You need to request the local shop give you a replacement phone or credit to get a new one.

Update: I went back to the shop and told them "You broke it, you fix it, I don't know how and I don't care, you gotta fix it". They managed to fix the imei number somehow. Regarding unlock, the shop ended buying the unlock code themselves. They mentioned that no one is able to unlock T-Mobile S4 with Stock 4.3 as of now without unlock code, unless they have some device like Z3x box. The phone is finally unlocked and working fine on my network. (YES, A HUGE HUGE RELIEF).
Everything is fine, except for 2 issues.
1. I want to backup my EFS folder so that I don't enter into trouble with IMEI again. I tried EFS Pro, but its not working. All I see is "'Initializing ADB server..." (the phone is rooted, usb debugging mode enabled, and supersu permission granted when prompted). I also tried to backup using Andromizer, but it says "Notification: File not found in /storage/emulated/0/Amdromizer/efs/efs.img". What is my best option as of now to backup and store my imei safely somewhere?
2. I am having issues with Wi-Fi. Before the shop flashed my phone, it was all good, but now it doesn't auto-connect to my home Wi-Fi anymore. Everytime I reboot or get out of range, I have to manually select my home network everytime and also enter the password everytime. Nothing has changed on my router. The other Samsung device that I have still auto-connects to my home Wi-Fi as usual. How can I fix this?
Thanks.

galaxysiv said:
Update: I went back to the shop and told them "You broke it, you fix it, I don't know how and I don't care, you gotta fix it". They managed to fix the imei number somehow. Regarding unlock, the shop ended buying the unlock code themselves. They mentioned that no one is able to unlock T-Mobile S4 with Stock 4.3 as of now without unlock code, unless they have some device like Z3x box. The phone is finally unlocked and working fine on my network. (YES, A HUGE HUGE RELIEF).
Everything is fine, except for 2 issues.
1. I want to backup my EFS folder so that I don't enter into trouble with IMEI again. I tried EFS Pro, but its not working. All I see is "'Initializing ADB server..." (the phone is rooted, usb debugging mode enabled, and supersu permission granted when prompted). I also tried to backup using Andromizer, but it says "Notification: File not found in /storage/emulated/0/Amdromizer/efs/efs.img". What is my best option as of now to backup and store my imei safely somewhere?
2. I am having issues with Wi-Fi. Before the shop flashed my phone, it was all good, but now it doesn't auto-connect to my home Wi-Fi anymore. Everytime I reboot or get out of range, I have to manually select my home network everytime and also enter the password everytime. Nothing has changed on my router. The other Samsung device that I have still auto-connects to my home Wi-Fi as usual. How can I fix this?
Thanks.
Click to expand...
Click to collapse
For the efs you can back it up using recovery. Just boot to recovery and its one of the options in the backup menu. The resulting file will be like a few KB. Its supposed to be small. Dont worry
Sent from your phone. You should be more careful where you leave that thing.

Tmobile gave me an unlock code and my phone isn't paid for but I used the region lock away app before I got the unlock code and it worked but u got to be rooted
Sent from my SGH-M919 using xda app-developers app

Bought an FRP locked phone, need a serial number

I bought a phone that was FRP locked (I know, stupid me) and cannot access the serial number in order to emergency flash it with Smart Switch. Can someone please share their serial number with me so I can reflash it? If not, does anyone have any help? I am on G920PVPU3CPF4

Even doing a SmartSwitch (or Odin) flash won't remove the lock. No amount of flashing or resetting will remove it. The lock is stored in a hidden partition that is never touched by flashes and resets.
There are ways to remove the lock, but they're paid services offered by professionals

iBowToAndroid said:
Even doing a SmartSwitch (or Odin) flash won't remove the lock. No amount of flashing or resetting will remove it. The lock is stored in a hidden partition that is never touched by flashes and resets.
There are ways to remove the lock, but they're paid services offered by professionals
Click to expand...
Click to collapse
I have a similar issue, could this be fixed with a Z3X Box?

you could try this method . . .
https://www.youtube.com/watch?v=ggRhkme9FC0
if for any reason didn't work try this one
https://www.youtube.com/watch?v=KRUp09bXnDA

JeffB81 said:
I have a similar issue, could this be fixed with a Z3X Box?
Click to expand...
Click to collapse
Yes it can be, do you have one?

discomaniac said:
Yes it can be, do you have one?
Click to expand...
Click to collapse
No, but I was able to repair my phone with Odin and the CPI3 firmware. Thank you

JeffB81 said:
No, but I was able to repair my phone with Odin and the CPI3 firmware. Thank you
Click to expand...
Click to collapse
You took off FRP lock with software?

JeffB81 said:
No, but I was able to repair my phone with Odin and the CPI3 firmware. Thank you
Click to expand...
Click to collapse
Confirm?

vazersecurity said:
Confirm?
Click to expand...
Click to collapse
I have read elsewhere that flashing the original firmware the phone was factory installed with can fix the frp lock

crazynapkinman said:
I have read elsewhere that flashing the original firmware the phone was factory installed with can fix the frp lock
Click to expand...
Click to collapse
Incorrect. FRP is held in a partition that is not touched during a firmware flash

vazersecurity said:
Confirm?
Click to expand...
Click to collapse
iBowToAndroid said:
Incorrect. FRP is held in a partition that is not touched during a firmware flash
Click to expand...
Click to collapse
Then what about this Cl3? Are there steps after flashing the firmware?

crazynapkinman said:
Then what about this Cl3? Are there steps after flashing the firmware?
Click to expand...
Click to collapse
Flashing firmware can't fix an FRP lock - period.
If you want to know what that poster meant by his message, I suggest you ask him directly

Samsung phones can be frp unlocked by flashing firmware
I have personally FRP unlocked 2 Samsung phones by flashing the stock firmware usin Odin. A samsung j7 and a Samsung s5. I am getting so sick of people saying you can't do something when they have no clue. I have also flashed older versions into phones. That's how I rooted the s5 infact. When everyone was saying it was impossible to root at the time. As soon a I figure out how to use sp flash or something to flash different phones other than Samsung I will post saying how it worked not get on someone else's post and say it will never work it's impossible. The world of computers, phones and software is suppose to be open source not locked, hidden and full of viruses.

Bullshipcaptcha said:
I have personally FRP unlocked 2 Samsung phones by flashing the stock firmware usin Odin. A samsung j7 and a Samsung s5. I am getting so sick of people saying you can't do something when they have no clue. I have also flashed older versions into phones. That's how I rooted the s5 infact. When everyone was saying it was impossible to root at the time. As soon a I figure out how to use sp flash or something to flash different phones other than Samsung I will post saying how it worked not get on someone else's post and say it will never work it's impossible. The world of computers, phones and software is suppose to be open source not locked, hidden and full of viruses.
Click to expand...
Click to collapse
LOL.
The FRP data is stored in the "persistent" partition, which is never touched by a firmware flash, just like EFS and a bunch of other partitions.
So no.

That doesn't matter when the phone no longer has a persistent partition.
iBowToAndroid said:
LOL.
The FRP data is stored in the "persistent" partition, which is never touched by a firmware flash, just like EFS and a bunch of other partitions.
So no.
Click to expand...
Click to collapse
You obviously think you know something and I wont argue or dispute whether you do or dont but I know what I did for sure and what I did was flash stock firmware into those phones and they where no longer FRP locked afterwards. Also When the phone is bricked the phone is flashed blank. There are no patitions if flashed blank. Even when there is persistent data it's still data that is able to be edited with a custom rom which can be flashed after you flash stock rom. I dont know much but I know what I have done personally. My wife is still using her rooted j7 with note 8 D.N.A undetected that we bought f.r.p. locked.
So ya. Just because the internet says it's not possible doesn't mean it's not possible It just means you haven't tried hard enough to prove it yourself. Brick that phone if you have to. Build with that brick.

Bullshipcaptcha said:
You obviously think you know something and I wont argue or dispute whether you do or dont but I know what I did for sure and what I did was flash stock firmware into those phones and they where no longer FRP locked afterwards. Also When the phone is bricked the phone is flashed blank. There are no patitions if flashed blank. Even when there is persistent data it's still data that is able to be edited with a custom rom which can be flashed after you flash stock rom. I dont know much but I know what I have done personally. My wife is still using her rooted j7 with note 8 D.N.A undetected that we bought f.r.p. locked.
So ya. Just because the internet says it's not possible doesn't mean it's not possible It just means you haven't tried hard enough to prove it yourself. Brick that phone if you have to. Build with that brick.
Click to expand...
Click to collapse
I own a business that does FRP removals and many other software-related services for mobile devices . I've done this for years - knowing this type of thing is literally my job.
The "persistent" partition is ALWAYS there - just like system, boot, recovery, and all the others. And I promise you, you can't remove an FRP lock by throwing it in Download mode and flashing some firmware with Odin, just like you can't remove it by booting to recovery mode and doing a factory reset. It's just not that easy.

Your going to need to go against the grain her a moment . Business or no business
iBowToAndroid said:
I own a business that does FRP removals and many other software-related services for mobile devices . I've done this for years - knowing this type of thing is literally my job.
The "persistent" partition is ALWAYS there - just like tem, boot, recovery, and all the others. And I promise you, you can't remove an FRP lock by throwing it in Download mode and flashing some firmware with Odin, just like you can't remove it by booting to recovery mode and doing a factory reset. It's just not that easy.
Click to expand...
Click to collapse
I'm telling you. I'm not debating the facts. Im telling you what I did. Kinda like I did today with a Moto e4 play. I bypassed frp with flashing stock rom through Odin and then custom rom on the Samsung J7. Today I bypassed frp lock with twrp on the Moto e4 with the bootloader still saying OEM locked . I don't have a business in the phones field but I am a business man and sittin on 12 frp locked phones gets tire some. Thant goodness for broken digitizers and displays or I'd still have a bunch more of them. I wont dipute that you know what your doing because likely you do more so than I; we can can probably be certain. I'm just going to tell you the 100 percent fact. Upset wife as my motivating factor I successfully unlocked and rooted a j7 by flashing stock rom into it with Odin then custom reccovery then root then custom rom. The custom recovery I used by accident was for a different brand Jay 7 so mysecond time around I tried the "right" recovery and bricked it. Then again and again and again until Knox was tripped and that's when finally I took bl,ap cp, csc and flashed them in dl mode successfully from there I had Rob from simple cell unlock ( Thanks Rob your the best) remotely unlock the jay7 from T-Mobile after which I flashed the "wrong" proper twrp file giving me the ability to install custom note 8 dna rom into the system. Took two tries, first try I flashed no encrypt no verity but it custom rom frp locked. So second time I made sure I install the developer tools package with OEM unlock switch not able to be turned off then no encrypt no verity. It was a very long process since especially since it was only my second successful full root. Then vallet. Man becomes praised by wife. Man feels empowered man tears apart more phones makes mess, MAN HAPPY! WIFE HAPPY! LOL okay sorry about that part.
---------- Post added at 04:18 PM ---------- Previous post was at 04:06 PM ----------
iBowToAndroid said:
LOL.
The FRP data is stored in the "persistent" partition, which is never touched by a firmware flash, just like EFS and a bunch of other partitions.
So no.
Click to expand...
Click to collapse
None the less each developer has a different approach that being said you frp unlocking phones? I have a Samsung s8 Moto e5 five LGs one zte n835 a couple of alcatels and a few more I couple reassemble real quick If I knew some one who had the abilitby to unlock especially if said amazing developer was teaching El padawan young Como. Yo tango mucho programs, apps and software. Just need the knowledge.

Bullshipcaptcha said:
Today I bypassed frp lock with twrp on the Moto e4 with the bootloader still saying OEM locked
Click to expand...
Click to collapse
Thinking you can flash TWRP on a locked bootloader device shows me exactly what your knowledge level is when it comes to all of this. Future discussion would be futile, and no more responses from me will be had. I do wish you luck with your devices though

How frustrating you are.
Your business need some schooling it sounds like. Your business can't be doing good. Go ahead and Google the Moto e4 unlock method. You will see. You have to try before you say it won't work.

discomaniac said:
I bought a phone that was FRP locked (I know, stupid me) and cannot access the serial number in order to emergency flash it with Smart Switch. Can someone please share their serial number with me so I can reflash it? If not, does anyone have any help? I am on G920PVPU3CPF4
Click to expand...
Click to collapse
I just removed the frp lock on my s6 using a combination firmware (found here-https://firmware.gem-flash.com/index.php?a=downloads&b=folder&id=7410) which completely erased all partions and allowed me to access the settings menu to enable the OEM unlock setting. They are two different firmware there. I used the second one and it worked like a charm. Hope this helps

No IMEI, IMEI SV, or Signal after flash rom stock

First of all, i started being a newbie, i just wanted to install magisk for cam2api, but i messed up: i combined for error 2 different system (mine that was ios9 and ios8). So i tried to read more and more threads and it just got worse. to make the story short: i had to get to test-point and restore the phone with Xiaomi Mi Flash tool & an original rom stock.
So now that i can go inside the Android System and use the phone, my sim card is just not working, i checked and my imei was 0 and my IMEI SV also 0.
I tried deleting modemst 1 and 2, i tried to reflash the phone with another stock images, updating the phone via android (normal way), i tried to restore my imei with the QPST Dual Imei (and it worked but the IMEI SV still in 0). nothing is working Please i need help i think my efs folder it's corrupted but i'm not shure.
Also i don't have any EFS backup or System backup, nothing.

JoiaDG said:
First of all, i started being a newbie, i just wanted to install magisk for cam2api, but i messed up: i combined for error 2 different system (mine that was ios9 and ios8). So i tried to read more and more threads and it just got worse. to make the story short: i had to get to test-point and restore the phone with Xiaomi Mi Flash tool & an original rom stock.
So now that i can go inside the Android System and use the phone, my sim card is just not working, i checked and my imei was 0 and my IMEI SV also 0.
I tried deleting modemst 1 and 2, i tried to reflash the phone with another stock images, updating the phone via android (normal way), i tried to restore my imei with the QPST Dual Imei (and it worked but the IMEI SV still in 0). nothing is working Please i need help i think my efs folder it's corrupted but i'm not shure.
Also i don't have any EFS backup or System backup, nothing.
Click to expand...
Click to collapse
I´m not sure what you mean by ios8 and ios9, maybe oreo and pie.
For the next time just so you know test point method is not recommended while you are not completely bricked (although is recommended out there without care), on a unlocked device most probably you won´t need it to solve this kind of issue, there are other resources to try previous to this stage.
I never had this kind of problem, you might try this https://zfirmware.com/how-to-repair-qualcomm-imei-via-qualcomm-write-imei-tool/

Sadly not working
SubwayChamp said:
I´m not sure what you mean by ios8 and ios9, maybe oreo and pie.
For the next time just so you know test point method is not recommended while you are not completely bricked (although is recommended out there without care), on a unlocked device most probably you won´t need it to solve this kind of issue, there are other resources to try previous to this stage.
I never had this kind of problem, you might try this
Click to expand...
Click to collapse
Sadly, it didn't work. i was thinking if there was a way to do it with root

JoiaDG said:
Sadly, it didn't work. i was thinking if there was a way to do it with root
Click to expand...
Click to collapse
Try rewriting the IMEI's from the box (I hope you still have the box and paperwork since there is the original IMEI's) with the Qualcomm IMEI Tool. Reflash full stock rom.
The tool is here: https://androidmtk.com/download-qualcomm-smartphone-write-imei-tool
If everything fails and your knowledge is not helping you to find a solution and you are still under warranty and respect the warranty for physical aspect of the device (no scuffs, no damage, no aftermarket replaced parts that may damaged warranty voids inside the phone) you can flash it stock, lock bootloader and file a warranty replacement as "damage from OTA". The service will replace your motherboard.

I need help
TheoXSD said:
Try rewriting the IMEI's from the box (I hope you still have the box and paperwork since there is the original IMEI's) with the Qualcomm IMEI Tool. Reflash full stock rom.
The tool is here:
If everything fails and your knowledge is not helping you to find a solution and you are still under warranty and respect the warranty for physical aspect of the device (no scuffs, no damage, no aftermarket replaced parts that may damaged warranty voids inside the phone) you can flash it stock, lock bootloader and file a warranty replacement as "damage from OTA". The service will replace your motherboard.
Click to expand...
Click to collapse
I know i have to use that tool, but my device is not recognized by that app, i tried to install all the drivers, but nothing's working.

JoiaDG said:
Sadly, it didn't work. i was thinking if there was a way to do it with root
Click to expand...
Click to collapse
I knew that there is a method to restore IMEIs via adb but I don´t remember commands so I never need it. First I do before tinkering device is to backup IMEI/EFS/NVram.
I had a theory that years ago I proved, IMEI is not really lost but just overlapped so if you have some friend that can give you their backup this will recover the yours but won´t overwrite/replace the yours. Not sure if it works yet.
About the tool that I linked maybe you need to get it through either in fastboot or download mode, try both; I don´t think that detect it while device is on.

https://forum.xda-developers.com/mi-a2-lite/how-to/sim-network-solution-alternatively-t3914161 i fixed the phone with this tutorial

JoiaDG said:
https://forum.xda-developers.com/mi-a2-lite/how-to/sim-network-solution-alternatively-t3914161 i fixed the phone with this tutorial
Click to expand...
Click to collapse
Yeah this fixed my phone too, now I'm making backups

Question [fixed] rooted a325m suddenly no imei, no sim

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