Develop Bugs

[TUTORIAL] Screen freezing after unlock problem solution

I have a screen freezing after unlock or call problem for months, tried differnt things like changing ROMs, lockscreen apps but none of them worked, my screen was still unresponsive for a while after unlocking screen, then i saw senaia's post about TP Calibration and tried, the problem is gone so i wrote this tutorial to help the others.
I take no responsibility for any DAMAGES or BRICKED phone, do it at your own risk
WARNING: This will ERASE all of your data, applications, sd card, messages, contacts etc. so make backups of them.
Here is step by step guide
DONT FORGET TO BACKUP
1. Make a goldcard using tutorial in this thread
2. Unrar attached file to the root of Goldcard
3. Power off phone, boot to bootloader with volume down and power button pressed
4. Wait for while it will search for files
5. Then a screen will show up like
Power => Reflash
Vol-Dn => DIAG
6. Press Volume Down for Diag
7. You will see a screen asking you to put phone on a flat surface, do what it says
8. Once that is done you will see a menu about Clear S58 Data, Ignore it, pull the battery and reboot
9. Repair is done, problem should be solved now
This is my first tutorial for XDA, so any suggestions are welcome
Thanks to senaia, he showed how to do

IT works, finally!
I can confirm that the tutorial made by mstfkaratas is working.
Thank you, I cannot describe how much i appreciate it, my beer money is on it's way!

thanks for beer

nevermind
It seems like i got a bit too emotional on this, and my previous post was a little rushed.
The screen freezing gradually comes back in 24 hours. The waiting times become longer and longer. After i did the above steps the lag was gone, but unfortunately it comes back. Especially after i set up to sync with my google account. I also tries to make a new accont, but without success.

I had this issue but admittedly it had just about disappeared when I upgraded to 2.3.5, but still had the odd freeze when receiving a call but not as bad, I did this tutorial and have not had 1 freeze since, may I suggest your problem is hardware (digitizer) Ivaxona?

hi ivaxona your problem can be hardware related or an app you installed, i can suggest you install apps one by one and check the problem
i cant help you more than this because i am not an expert this solution helped more than 5 phones AFAIK
Sent from HTC WFS

Hi, thanks for the response, i also thought that it may be a touchscreen problem, but it got me thinking, that how could be this possible, when after a short time it start to work absolutely perfect.
I also tried to create a new google account just for testing so the possibility of a 3rd party application causing the problem is eliminated.
I have to mention though that after i place the first call the performance response time degrades significantly. That's why i think that it could be a radio problem as well.
I have to admit that i just recently purchased this digitizer on ebay, and it looked like a second hand unit so i might jut got screwed up.
As a last try before i try to change the digitizer once again, i'll try to upgrade to 2.3.5 as it was suggested.
I'm still on a stock ROM, i suppose there is no 2.3.5 official ROM so i'll have too ROOT the phone, right?
once again thanks for your help!

http://www.filefactory.com/file/c0a...5.3035H_7.53.39.03M_release_225747_signed.exe
this is 2.3.5 EU RUU from shipped roms thread, you can try this, if this doesnt work, there should be tutorials for how to install in this forum. i hope this helps
edit: here is a thread about upgrading 2.3.5 http://forum.xda-developers.com/showthread.php?t=1363693

Thank you very much, got my brothers device to work now

after i upgraded to 2.3.5 the fix is working! Thanks a lot!

Solved!!
Many many thanks!
Ciao.

Thanks brother

thanks brother..!!!

After many months of searching for solution, it is finally fixed.
It's a relief it's not a hardware issue. I am using custom 2.3.5 and it worked.
Thanks.

thanks brother, you saved my cel phone, I wonder which phones this works ???? I tried it with my wildfire s and is worked

nathatheboss said:
thanks brother, you saved my cel phone, I wonder which phones this works ???? I tried it with my wildfire s and is worked
Click to expand...
Click to collapse
the diag file used for this process is only compatible with wildfire s, i dont know if other phones have that kind of diag files
Sent from my HTC Wildfire S

Thanks for your how-to...
Sadly it didn't help for me, although I've successfully performed the DIAG boot on my S-OFF WFS. I'm running the latest version of alquez's Cyanogenmod 7.2.0-RC1-marvel-KANG (03-24).
I'm also not sure if I have the problem that is described in this thread.
Whenever I power on the phone and try the unlock-slide the first time, the slider jumps back after some pixels. Everytime, it's really nasty.
Maybe this is something else and I should start a new thead for it?

Thanks!! This really works!!! I had replaced the screen, but it only worked the left side. After applying your method, this little wilfire s works!!! My girlfriend will be very happy!!!

Thanks for the tut.
Sorry, i still have this proble in my phone, one question.
To do this tutorial, we must be S-OFF?
Thx

no need to be s-off, i have positive feedbacks with s-on devices
Sent from my Wildfire S using Tapatalk 2

[Q] Please help I'm soft bricked Sprint Note 2

Yes I am an idiot (point and laugh now) I did something wrong, but have no idea exactly what yet. I searched and couldn't find anything for this version of the Note 2
About 3 weeks ago I updated to the newest version of Whomp, as soon as I did that I would get the hands free activation alert on my phone every time it booted up. It would always error out for code 1500, which is an internal error according to sprint. I was able to still use the phone so I didn't worry about it to much.
Last week the phone stopped switching towers during a phone call. It would drop the call and pick back up at the next tower milliseconds later with full bars. Called Sprint and was advised I needed to update my PRL and Profile, etc. Which couldn't be done because my phone was showing that it wasn't fully activated.
So my plan of attack was to unroot the phone, update everything, then get my root back. Simple enough.
Trying to go back to Stock really broke the phone!
I was trying to flash the stock ROM through Odin last night and it kept erroring out. Now when I try to turn it on or when I try to boot into recovery I get
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I can boot into download mode, so I think it's soft bricked. There has to be some way to fix this... I *might* have impulsed purchased a used Note 2 on ebay last night and the person *might* be overnighting it to me since I seemed pitiful enough. So I have time to get this one working correctly.
I'm just out of ideas... I know when I hard bricked the GS3 (That took a special level of stupid) I mailed it to some place in TX. Is that my only option here? Help please! Also I know just enough to be massively dangerous so use little words please... LOL
I was using this guide last night http://forum.xda-developers.com/showpost.php?p=33558212&postcount=1

JAJameson2010 said:
Yes I am an idiot (point and laugh now) I did something wrong, but have no idea exactly what yet. I searched and couldn't find anything for this version of the Note 2
About 3 weeks ago I updated to the newest version of Whomp, as soon as I did that I would get the hands free activation alert on my phone every time it booted up. It would always error out for code 1500, which is an internal error according to sprint. I was able to still use the phone so I didn't worry about it to much.
Last week the phone stopped switching towers during a phone call. It would drop the call and pick back up at the next tower milliseconds later with full bars. Called Sprint and was advised I needed to update my PRL and Profile, etc. Which couldn't be done because my phone was showing that it wasn't fully activated.
So my plan of attack was to unroot the phone, update everything, then get my root back. Simple enough.
Trying to go back to Stock really broke the phone!
I was trying to flash the stock ROM through Odin last night and it kept erroring out. Now when I try to turn it on or when I try to boot into recovery I get
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I can boot into download mode, so I think it's soft bricked. There has to be some way to fix this... I *might* have impulsed purchased a used Note 2 on ebay last night and the person *might* be overnighting it to me since I seemed pitiful enough. So I have time to get this one working correctly.
I'm just out of ideas... I know when I hard bricked the GS3 (That took a special level of stupid) I mailed it to some place in TX. Is that my only option here? Help please! Also I know just enough to be massively dangerous so use little words please... LOL
I was using this guide last night http://forum.xda-developers.com/showpost.php?p=33558212&postcount=1
Click to expand...
Click to collapse
i may be wrong, but it seems that for whatever reason you are back to stock recovery, but the rest of it went bad... i would follow this http://forum.xda-developers.com/showthread.php?t=2086769 there is a flashable TWRP ODIN tar, so boot into that, flash his MC2 ZIP and you should be good. similar thing happened to me, but i would just at endless bootloop, flashed that MC2 zip and im back to stock. Best of luck

Ha! That's the thread I was searching for. I found the one made for the GS3, but couldn't locate the Note 2 one. Thanks so much! I'll fiddle around with that tonight after work

It worked It worked It worked It worked It worked It worked It worked It worked! You have no idea how happy I am right now!
So now I'm unrooted and back in the stock ROM. I'm going to update my profile/prl/system/firmware then root later on tonight and probably flash the Jelly Bomb ROM
Thanks you for your help! Phone is no longer soft bricked and is activated onto the Sprint account again.

JAJameson2010 said:
It worked It worked It worked It worked It worked It worked It worked It worked! You have no idea how happy I am right now!
So now I'm unrooted and back in the stock ROM. I'm going to update my profile/prl/system/firmware then root later on tonight and probably flash the Jelly Bomb ROM
Thanks you for your help! Phone is no longer soft bricked and is activated onto the Sprint account again.
Click to expand...
Click to collapse
Don't forget to hit the Thanks button for info from kirblar. :good:

lennykravitz2004 said:
Don't forget to hit the Thanks button for info from kirblar. :good:
Click to expand...
Click to collapse
Done! Thanks for the tip

Screen issue after .90 update

Hello,
i have the same issue as described in the thread below and shown in this video ==> https://vid.me/NGc5
== > http://www.asus.com/zentalk/forum.php?mod=viewthread&tid=41205&extra=page=1&page=1
i have been suffering from same issue since the .90 update, i tried flashing the 1.1GB file using adb which didn't solve the issue along with the yesterday update
anyone having the same problem?
i want to flash the older .63 version, but using adb it says that it can't flash older version than the current version , anyone can help with that ?

@Asus_USA
any info please

I downgraded the rom to a version from July, yet the same issue persist
Seems like a member mentioned somewhere else that the. 90 update might have broken some hardware using code that is not reversible
Waiting for any feedback from Asus
Sent from my GT-N7000 using Tapatalk

That's actually a screen or onboard video issue.... I see this on laptops all the time

Frankenberrie said:
That's actually a screen or onboard video issue.... I see this on laptops all the time
Click to expand...
Click to collapse
the weird thing that it only happened after the .90 update and several users are reporting it

And some software works fine, like whatsapp where the screen is normal while inside it
Sent from my GT-N7000 using Tapatalk

more users are reporting the same issue on the zentalk forum, good luck all avoiding this

no one else here on the forum suffering from the same issue ? any ideas for troubleshooting or solving ?

@ASUS_Khang
can you please confirm that this is a software issue that will be solved through an update and not a hardware failure ?

AhmadOkda said:
no one else here on the forum suffering from the same issue ? any ideas for troubleshooting or solving ?
Click to expand...
Click to collapse
I am also having this SAME issue ! I have unlocked my bootloader, root access, and flashed the 2.40.97 update again, I tried downgrading, it won't let me install and lower update over an higher one. and I can't get twrp recrovery to stay after the flash, it always goes back to the stock recovery. Also I know whats causing the problem. it's the Auss / powered by intel animated screen , First you have the Asus splash screen, Then the Animated Asus / Intel animation Then the boot animation screen. after unocking my bootloader, and changing the boot animation. I can tell you for sure, the Asus / Intel animation that is causing the issue !. I don't know where this animation is stored on the phone, if anyone knows. maybe we can restore of get rid of it. Anyway my phone is pretty much useless right now, can't use the keypad on the call screen, and can't even see the bottom half of the phone, IT's NOT a hardware problem. like some people have said. it's that dam Asus / Intel animation at starup.

I tried downgrading (using fastboot and abd) to every available firmware and nothing solved this problem
IMHO I think that the 90 upgrade triggered a bug while flashing boot partition
Sent from my GT-N7000 using Tapatalk

UPDATE.. I was able to install cm-12.1-20151011-UNOFFICIAL-Z00A.zip 2015-10-11 01:29 Using Windroid UIniversal Android toolkit. and it worked. and TWRP also the recovery.
Unlocked bootloader, rooted phone, installwd TWRP. Flashed boot, droidboot, with WW. 2.12.40.09 Z00A Then installed cm-12.1-20151011-UNOFFICIAL-Z00A.zip 2015-10-11 01:29 . The screen problem IS still there ! \ Anyone else have any ideas ? ~ Travis

My phone (ZE551ML) developed the same issue. When flashing back to stock didn't work, I sent it in for an warranty RMA. A part was replaced and the phone sent immediately back. Not a word to me about the unlocked bootloader. Just make sure if you send it in, that you state you did flash attempt flashing to stock, and make sure the phone is as close to stock as you can get. Factory reset the phone and go.

I tried last week 3 times I got an RMA & then an advanced RMA and i'm getting the run around from them. they even had the hold of 344.00 on my checkings account to the advanced RMA and then THEY canceled the RMA and everytime I talked to them 3 different customer support people then said " sorry we're updating our systems call back tomorrow. " I got told that 3 times and I've called 4 times. the phone is pretty much useless at the moment.

If they send the phone back to you, the part that was replaced on mine is "90AZ00A1-M02610". Dunno if you can get that part yourself and have it repaired by a third party, but other than that I wouldn't know what to do in your situation.

ArmchairWizard said:
If they send the phone back to you, the part that was replaced on mine is "90AZ00A1-M02610". Dunno if you can get that part yourself and have it repaired by a third party, but other than that I wouldn't know what to do in your situation.
Click to expand...
Click to collapse
...This is the Hardware model# of the whole device, not just a part inside , buy a new phone and you have this yourself !
At least for those in Canada, here a short review for my "advanced replacement" experience:
I used the Chat on their website to get a RMA#, then got a confirmation email with a sort of howto. They mentioned to use Fedex or UPS to send the defective device in and noted not to long to wait to do this otherwise the hold on my creditcard... you know! So i sent the package 3 days later with UPS, cost me a bit over CA$60 with insurance and tracking.
Just the other day i got email from Purolator (a Canada only parcel service) to print a return sticker. No one from ASUS mentioned this to me - $60 wasted
The replacement phone came also with Purolator, ASUS emailed me a tracking# but NOT wich carrier they used. Cost me a few hours and a couple phone calls to find out and re-route the package to my workplace.
ASUS did not use a original case, just a folded carton as they stated the replacement would be a new device. In case i decide to sell the phone i don't have original carton
Start to install all my usual App's etc. found that the phone does not receive any GPS signals, so it seems i changed a not usable screen into a not working GPS
For me, this was my last ASUS for a very long time!

Finally got my Advanced RMA going. can't wait to get a working phone, as soon as I do. Going root & unlock bootloader and install CM 12.1 I'm DONE with ASUS's bloatware ! ~ T

I am having the same problem. I have gotten my screen to work, but it still glitches. Is the only solution to send it in?

jeisenhart34 said:
I am having the same problem. I have gotten my screen to work, but it still glitches. Is the only solution to send it in?
Click to expand...
Click to collapse
I think so, I tried to fix it, flash with 2.20.40.97 Four times now, the problem is still there, rooted, unlocked bootloader, and installed CM 12.1 thinking it would get rid of the problem, it didn't. I think the problem is in the boot partition now. I also flashed the splash screen, and the boot animation. the problem is still there, EVEN after returning this phone back to stock to RMA it. the problem is still there.

Rattraps123 said:
I think so, I tried to fix it, flash with 2.20.40.97 Four times now, the problem is still there, rooted, unlocked bootloader, and installed CM 12.1 thinking it would get rid of the problem, it didn't. I think the problem is in the boot partition now. I also flashed the splash screen, and the boot animation. the problem is still there, EVEN after returning this phone back to stock to RMA it. the problem is still there.
Click to expand...
Click to collapse
I contacted Asus and I have to send my phone in. If you haven't dropped your phone, Asus will overnight you a new one for $25. I dropped my phone so they will repair it free of charge if the damage from the drop isn't what caused the issue. Otherwise I'm going to have to pay.

"Compatibility Patch" LG G4

"Compatibility patch" update showed up in my notification area. When I clicked on it, it took me to the LG software update section and said that this file is needed to fix some issues with app compatibility.
After installing the program asks to reboot the phone. Once the notification is clicked on, the phone reboots.
Phone is not rooted. It seemed a little sketchy since there's really no other information anywhere else on the net. It seems a bunch of other people have got this but no real info.
Just wondering if anybody else has got this update.
Thanx.

I didn't get this "comp patch" as an individual update. Last week, I got the update with the security patches from July 1 (German G4, no branding), and it looks like that this patch was included. It now shows in the list of installed LG applications, where it didn't appear before. My wife (LG G3) got this patch as a single install (~1 week ago).

I have got this compatibility patch too, and in description of this app is 20160809 so it is 1 week old. But what was going about in that "fix"... :/

I've got the patch today too. But haven't rebooted yet.

U talking about this one? What is that supposed to do?

I have got this update and now it keep asking to reboot in notification bar. I have done restart many times but no luck.

akarshad said:
I have got this update and now it keep asking to reboot in notification bar. I have done restart many times but no luck.
Click to expand...
Click to collapse
If you have the encryption on then turn it off and reboot. That should resolve the issue and then you can turn it back on. Hope it works for you.

akarshad said:
I have got this update and now it keep asking to reboot in notification bar. I have done restart many times but no luck.
Click to expand...
Click to collapse
Hi Akarshad, I've got exactly the same issue. Installed, rebooted multiple times and the notification to reboot is still there telling me to reboot to finalise the install.

Problem with the Patch
I got the same patch on my LG V10. Thinking nothing of it I agreed to install and reboot. Once I had done so, I now have the Yellow Boot Warning at every boot. And also a bunch of my system apps stopped working. Camera, Phone, Music. I don't remember ever flashing a ROM that would trigger the warning seeing as how I got the update to 6.0.1 a few days before and hadn't done anything since. So I flashed back to stock with LGUP and the problems still persist. This is my first post ever, any advice. I apologize as I know this is a LGG4 thread.

If you did anything to the system image, you may have issues applying the OTA. @SixTheAmateur: did you modify in any way your V10? Did you flash a KDZ not officially available to your V10?

Index100 said:
Hi Akarshad, I've got exactly the same issue. Installed, rebooted multiple times and the notification to reboot is still there telling me to reboot to finalise the install.
Click to expand...
Click to collapse
Yes that was the problem. Solved after disabling encryption

Guys the compatibility patch dissappeared??? Help yesterday it showed up Today nothing

Ok now i'm getting this on my g4 as well... Anyone ever figure out if this is a worthwhile update fir a non-rooted phone or if it's just LG crapware?

Copperwolf said:
Ok now i'm getting this on my g4 as well... Anyone ever figure out if this is a worthwhile update fir a non-rooted phone or if it's just LG crapware?
Click to expand...
Click to collapse
I've had massive compatibility issues with my g4 and apps I like to use. I noticed this today and definitely installed it. I have been able to use the apps I hadn't been able to use.
It seems to be going well so far. I'd say do it.
It seems to be frozen/disabled after installing, odd.
Sent from my LG-H811 using XDA Labs

Press and hold on notifications to see which app is giving them

Compatibility Patch Mystery to T-Mobile and LG
I got a notice for a compatibility patch several weeks ago.
Rather than click I contacted LG, who knew nothing of it.
So I contacted T-Mobile, my carrier, and they knew nothing of it and suggested I don't down load it.
It popped up again today and I'm going to ignore it until I understand what it will do.
Good Luck!

Similar experience. I had issues with my phone afterward and had to get a new one.
Similar experience. I had issues with my phone afterward and had to get a new one.
nikooe said:
"Compatibility patch" update showed up in my notification area. When I clicked on it, it took me to the LG software update section and said that this file is needed to fix some issues with app compatibility.
After installing the program asks to reboot the phone. Once the notification is clicked on, the phone reboots.
Phone is not rooted. It seemed a little sketchy since there's really no other information anywhere else on the net. It seems a bunch of other people have got this but no real info.
Just wondering if anybody else has got this update.
Thanx.
Click to expand...
Click to collapse

OEM issues

Hello. 3 weeks ago I was testing lineage 19 and had decided to install the gapps. The problem is, when I was trying to start TWRP it did not start from the twrp logo so I tried to flash from odin TWRP 3.4.0 to "try" to fix the recovery. When the phone did not start I decided to reinstall the official rom but I only found a version that worked flashing by odin (mexican version. at&t) the phone started and I decided to wait 7 days for the oem unlock to reappear. The problem is that 8 days have passed and oem unlock is still not available and when I go back to download mode it says rmm prenormal.
Will it have to do with having used a telephony rom when installing stock? I have no idea why it does not appear (it should be clarified. I did not turn off the device or disconnect from the internet in all that time, only when it was already on the eighth day because it was already very saturated) Sorry if I'm posting this wrong, or if you misunderstand what I'm trying to say. It's my first time writing here and I don't speak enough English to write this for myself. So I'm trying to "improve" the google translation changing some words
Thank you very much for reading this post and any help is welcome.

.

right now im waiting the 7 days but its weird, i installed the stock of my country but the boot have a att logo and in my country there is no att company lol i even tried downloading from oficial samsung and same logo... hope it work without problem, so Did you fix your problem?

ShadowDeath said:
right now im waiting the 7 days but its weird, i installed the stock of my country but the boot have a att logo and in my country there is no att company lol i even tried downloading from oficial samsung and same logo... hope it work without problem, so Did you fix your problem?
Click to expand...
Click to collapse
not really. After what I have mentioned, I completely cleaned the phone many times. until a week ago I remembered that I just bought the mobile it took approximately 13 days for the oem unlock to appear. (I suppose that because it is a company it will take longer, I don't know) and a friend told me to wait approximately 300 hours (I have currently 222 hours). I feel that if it does not appear again I will be forced to buy a new phone :/

Camkdls said:
not really. After what I have mentioned, I completely cleaned the phone many times. until a week ago I remembered that I just bought the mobile it took approximately 13 days for the oem unlock to appear. (I suppose that because it is a company it will take longer, I don't know) and a friend told me to wait approximately 300 hours (I have currently 222 hours). I feel that if it does not appear again I will be forced to buy a new phone :/
Click to expand...
Click to collapse
damn that sucks and weird, everyone said they just wait 7+ days without power off the phone and worked... first time i read about waiting more time, are you sure your phone isnt power off in the waiting time?

ShadowDeath said:
damn that sucks and weird, everyone said they just wait 7+ days without power off the phone and worked... first time i read about waiting more time, are you sure your phone isnt power off in the waiting time?
Click to expand...
Click to collapse
I am pretty sure. I do not turn off the mobile at all or disconnect it from the mobile data since I cannot make calls because of the VoLTE that is not available so I always receive calls through third-party applications. It should be clarified that I do not have an automatic restart activated, I also registered the mobile in the updates. At the moment I have 250 hours, I will wait 2 days to see if my theory is true.

Camkdls said:
I am pretty sure. I do not turn off the mobile at all or disconnect it from the mobile data since I cannot make calls because of the VoLTE that is not available so I always receive calls through third-party applications. It should be clarified that I do not have an automatic restart activated, I also registered the mobile in the updates. At the moment I have 250 hours, I will wait 2 days to see if my theory is true.
Click to expand...
Click to collapse
It still appears that the phone has been on for 250 hours in the settings. so I don't think it's because of some reboot or shutdown :/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Camkdls said:
It still appears that the phone has been on for 250 hours in the settings. so I don't think it's because of some reboot or shutdown :/
View attachment 5566123
Click to expand...
Click to collapse
If you dint re lock the bootloader when you installed that rom, the bootloader is unlocked right now, but pretty sure you have the samsung rmm in prenormal and thats why to "fix" it we need to wait 7+ days of usage so you should enter in download mode and check your RMM setting again or you should try to install another rom, could be some issue with that one

ShadowDeath said:
If you dint re lock the bootloader when you installed that rom, the bootloader is unlocked right now, but pretty sure you have the samsung rmm in prenormal and thats why to "fix" it we need to wait 7+ days of usage so you should enter in download mode and check your RMM setting again or you should try to install another rom, could be some issue with that one
Click to expand...
Click to collapse
I had thought about that, but there are a lot of problems to find and download the correct version for the binary. I was still doing searches when I updated to android 8 just to install TWRP and they also match the 13 days that I had mentioned before. if it doesn't appear again I'll have to download another rom at 50kbps
When updating use odin since by chance the OTA update did not work. The same thing happened to lose the oem unlock and while I was preparing everything to install TWRP, approximately 20 days passed. but I already had the unlocking after 15 days.

Camkdls said:
I had thought about that, but there are a lot of problems to find and download the correct version for the binary. I was still doing searches when I updated to android 8 just to install TWRP and they also match the 13 days that I had mentioned before. if it doesn't appear again I'll have to download another rom at 50kbps
When updating use odin since by chance the OTA update did not work. The same thing happened to lose the oem unlock and while I was preparing everything to install TWRP, approximately 20 days passed. but I already had the unlocking after 15 days.
Click to expand...
Click to collapse
Yeah that sites with ultra low speed sucks, use Bifrost for your pc, it download the specific and latest rom of your device from the samsung servers

ShadowDeath said:
Yeah that sites with ultra low speed sucks, use Bifrost for your pc, it download the specific and latest rom of your device from the samsung servers
Click to expand...
Click to collapse
I want to thank you for the program. It worked perfectly (although I used it from android because I was too lazy to turn on the PC) Today at dawn I installed the romania version (I used that version the first time I installed TWRP) All the AT&T garbage is gone
Now I only have to wait 7 days to see if the rom had any errors (Curiously when trying to update the available time zones by restarting it never updated. I think that was the problem)
Sorry for the question. But, did the oem unlock appear to you in all this time that passed?
Since you commented approximately 9 days ago until now I thought I'd ask you if the oem unlock appeared even using a rom that had the at&t logo

Camkdls said:
I want to thank you for the program. It worked perfectly (although I used it from android because I was too lazy to turn on the PC) Today at dawn I installed the romania version (I used that version the first time I installed TWRP) All the AT&T garbage is gone
Now I only have to wait 7 days to see if the rom had any errors (Curiously when trying to update the available time zones by restarting it never updated. I think that was the problem)
Sorry for the question. But, did the oem unlock appear to you in all this time that passed?
Since you commented approximately 9 days ago until now I thought I'd ask you if the oem unlock appeared even using a rom that had the at&t logo
Click to expand...
Click to collapse
Your welcome mate right now i have 143h(my fault i restart it lol) so we will see tomorrow if the option appear, still i dont care about the OEM option because it was set ON last time because i was using LOS, but the "RMM state = Prenormal" in download mode its what is locking my phone to be available to change rom, so yeah we will see tomorrow!

Saddly dint work, gonna try installing a old version of my country code or try to get a clean version, not this weird thing with att $ht
Edit:nothing seems to work so i installed the newest update of my country and debloat the rom... it let it to my mom again and she will be using a good amount of time 4 weeks and ill check again.
Edit 2: seems we are out of options now https://forum.xda-developers.com/t/...d-expired-certificate-whats-next-lol.4403393/

Yup. that explains everything. It seems that in the end I will have to change my phone, do you think there is a way to remove the prenormal RMM? I'm not very experienced in mobile development. This really makes me cry

Camkdls said:
Yup. that explains everything. It seems that in the end I will have to change my phone, do you think there is a way to remove the prenormal RMM? I'm not very experienced in mobile development. This really makes me cry
Click to expand...
Click to collapse
There are apps for repair services (like ChimeraTool) that can unlock it. Wouldn't be free, though.

Camkdls said:
Yup. that explains everything. It seems that in the end I will have to change my phone, do you think there is a way to remove the prenormal RMM? I'm not very experienced in mobile development. This really makes me cry
Click to expand...
Click to collapse
Again im in the 7th day with 171+h and OEM is missing so pretty sure the rmm its prenormal i really dont know now, you can search the telegram group and ask its called "A5/A7 2017 ROMS" i asked for help but they just give me this, they say for them works this method and they did it recently.

ShadowDeath said:
Again im in the 7th day with 171+h and OEM is missing so pretty sure the rmm its prenormal i really dont know now, you can search the telegram group and ask its called "A5/A7 2017 ROMS" i asked for help but they just give me this, they say for them works this method and they did it recently.
View attachment 5577843
Click to expand...
Click to collapse
I wonder what is "recent" I also tried this when I had the ATT rom. it didn't work for me anyway. I would try if it works but I'm already tired of flashing stock rom every time I try
I guess I'll wait for it to just unlock or I don't know

Camkdls said:
I wonder what is "recent" I also tried this when I had the ATT rom. it didn't work for me anyway. I would try if it works but I'm already tired of flashing stock rom every time I try
I guess I'll wait for it to just unlock or I don't know
Click to expand...
Click to collapse
Yeah forget about it, I tried today all the tricks again many times and nothing, I'm gonna try a month without power off the phone but right now my hopes are lost.