In the last few months I started to learn how to custom ROM androids and successfully flashed and have been experimenting since with the Galaxy Note 2 and Note 5. However, recently I tried with a Galaxy Note 8 (US version) that wasn't updated since January of this year, so I was still able to use SamFail (the phone itself was stuck in a boot loop). Eventually I found a combination that worked through the boot loop but now set up is stuck on FRP when it originally was not but it doesn't look like FRP lock is on. This is the loading screen that shows up at this point prior to going to phone set up. Does anyone have an idea as to some of the information displayed now on loading that I missed and or suggestions to get past the random FRP during set up? It at least is not stuck on the boot loop but its not responding to profile information. Is it possible that the SamFail uploaded its own profile (this was directly from XD RootSnap Dragon: https://forum.xda-developers.com/galaxy-note-8/development/root-samfail-galaxy-note8-t3685340) ? Thanks again everyone for all of your hard work and really appreciate the community around here! Image below is the info display during boot:
{
"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"
}
I see this your first post around here, you may try to flash whatever firmware your device was running before the problem arose, that should fix the issue, as for FRP, that is another matter, no help will be provided here as to, when the device is lawfully yours, you should have the info to pass it, if for some reason you forgot it or else, you can always take it to your carrier or samsung service to solve the issue, that is, providing proof of purchase or a valid contract and ID
Yes this is my first post although I have been reading through posts the last few months which taught me how to flash / rom in the first place for my Galaxy Note 2 & 5 (I avoided phone technology for awhile). I do want to mention, I legally own the phone and I'm NOT asking for an FRP unlock. What I'm saying is that I was able to flash and rom using the Samfail tutorial above after the first several attempts from original firmware had caused it to go into a boot loop. When eventually it did get itself out of a boot loop, the set up screen created a new "profile" where the original information is no longer able to log back into the phone at all. Thus, I was wondering, is it possible for the ROM during my attempts at flashing the firmware, possibly cause damage to wherever the profiles might be stored thus making it unable to use it? Or if the ROM could have come with a profile that wrote over the original, thus making it impossible to use? Since I "ruined" the warranty, can I not take it back to TMobile (even though I am now on Sprint) with the original receipt and they be able to unlock it even though its not allowing me to or is the part KNOX (I'm still trying to figure out what signs it shows if you activate KNOX)? Or as a final option, which I've avoided doing as I don't want to completely brick my phone by accident , could I flash the phone once again with original firmware to see if that resets it finally (I don't have anything saved on their that I need as its backed up already but really hate to kill a this phone by accident). I appreciate any info you might suggest and completely and fully understand the "stealing" phone frp lock out and again, I am not looking for a workaround and I have full legal evidence to prove ownership just that I didn't know if an previous cell provider of mine would even accept or touch a partially flashed / rommed device since it break warranty. I apologize I'm new to this but its not something I can get another any time in the near future so I'm just playing cautious at this point. Any advice would be incredibly appreciated (didn't nearly have any of this issues with the note 2 and 5 - also I am able to use ADB and Odin in general). Thanks again!
winol said:
I see this your first post around here, you may try to flash whatever firmware your device was running before the problem arose, that should fix the issue, as for FRP, that is another matter, no help will be provided here as to, when the device is lawfully yours, you should have the info to pass it, if for some reason you forgot it or else, you can always take it to your carrier or samsung service to solve the issue, that is, providing proof of purchase or a valid contract and ID
Click to expand...
Click to collapse
Samfail root method does not trip knox, which is the telltale of rooting, which in turn is the reason for voiding warranties in some, not all markets/carriers/countries, therefore, you should be able to get the warranty honored, I understand that maybe you want to fix the problem yourself, that is fine, but sometimes it is somewhat overcomplicated, I have seen here in XDA people that that solved utterly frustrating problems like yours, accomplished success just by repeating the flashing many many times (provided that the files used, odin version are the right ones and the entire process is made very carefully), I would take it to a service center
Related
i was flashing with a rom and i gotted bored so i turen off my computer now phone wont work adn idk how to fix cuz now i want phone for the phone to mak ework. i need phone to make my calls
how do i fix?
wats the point of flashing it just break my fone and why want to break phone anyways?
Assuming that you are flashing through your computer, if you turn off your computer then the phone cannot get all the data needed to successfully flash.
You'll most likely need to do this.
Power your computer back on.
Power your phone off and have the usb cable plugged in.
Hold the volume down button and press the power button (leaving the volume down button pushed) until you get tri-color screen and it should say USB at the bottom.
Flash the phone as you normally would.
Make sure to pay specific attention to all steps listed in the stickies when flashing your rom and never power down the data source.
Don't ask "what's the point in flashing", since the only reason your phone is messed up is because you screwed up and didn't follow the instructions.
You got bored during the flash and turned your computer off? It only takes a couple minutes!
redpoint73 said:
Don't ask "what's the point in flashing", since the only reason your phone is messed up is because you screwed up and didn't follow the instructions.
You got bored during the flash and turned your computer off? It only takes a couple minutes!
Click to expand...
Click to collapse
people that post like you make me want to go clean IN on you. But if you spent all day helping those that may have made small mistakes (like you never had) you wouldn't have a life. So it doesn't happen often. I just chose to acknowledge your ignorance (as i see it)
time to help someone waisted. spent to put them down...hope you got your phone fixed....
If you look at my posts, you will see I try to spend quite a lot of time helping people. But you chose to judge somebody based on one post.
The post above mine already told him how to fix it, so I didn't see the need to rehash.
Also, so many people on here spend tons of time making the stickied guides, detailed instructions in the individual ROM threads, FAQs, etc. that its a bit ridiculous when someone doesn't spend 2 minutes to read them, and then breaks their phone and asks silly questions like "what's the point in flashing".
I really hope this is just a troll post...
vHatch said:
I really hope this is just a troll post...
Click to expand...
Click to collapse
Agreed, this is kind of ridiculous. Even if this person had never performed a flash before, there is a progress bar displayed on the PC screen. It takes literally less than 5 minutes to flash. If this person got that bored in that amount of time, then he will probably be too bored to read the replies here to solve the problem.
It's like he's taken A.D.D. to the extreme.
bijan588 said:
i was flashing with a rom and i gotted bored so i turen off my computer now phone wont work adn idk how to fix cuz now i want phone for the phone to mak ework. i need phone to make my calls
how do i fix?
wats the point of flashing it just break my fone and why want to break phone anyways?
Click to expand...
Click to collapse
HAHAHAHAHAHA, you got BORED?? oh man.... way to go brother. i was gonna tell you how to fix it, but im wwaayy too bored
Ohhhhh boy..... Alright... If you got bored and turned your phone off WHILE it was flashing then it's nobody's fault but your own that you "borked" your phone...
Take the battery out and then put it back in. Turn it on and it "SHOULD" go to a tri-color screen known as the bootloader screen.
While it's in this screen, connect it to your computer and proceed to flash the FACTORY STOCK ROM for your phone. This should fix your phone...
That being said... Try to have a bit more patience and not get so "bored" while it's flashing. If you want to keep your phone as a functional phone and not a paperweight, you'll follow instructions next time...
Now... Before you get flamed any further...
{
"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"
}
My phone has experienced the Internal SD failure.....for the second time.....since November 19th (a miraculous 13 weeks).
I'm unsure of when the first phone I had was made, but my second phone was 10.09. Yesterday just looking around, I noticed it hadn't been turned off in over 2 days, so I decided to turn it off while it charged overnight. I woke up in the morning, turned it on, and all my apps were gone and the background was default. I thought odd, rebooted again, and the phone hung on reboot.
I've tried flashing to my default 2.1 UGJH2 with ODIN. My phone would boot through the Galaxy "S" Loading screen, and then go black (with softkeys still lit).
I've tried using Darky's 9.2 Resurection with ODIN. The phone will load the "Samsung Galaxy GT-i9000" screen, go black, and reboot.
The phone can still enter Download Mode, if anyone has a suggestion to try I am still willing!
This is my SECOND phone, while the first one was an immediate replacement (failed in the first week) I am very dis-satisfied. I know some of you have gone through measures to complain and gain compensation, was hoping you may have some words of wisdom on the best way to tackle this?
Thanks team
my suggestion contact Bell to get you a replacement or contact Samsung and send it in for repair, and wait for like 4 weeks without a phone
You could try flashing JL2 and tick the bootlegger option in odin. Some people have had success with it
GT-I9000M with Doc rom
I've gone to the TBooth where I bought the phone, they have set up a return with Bell/Samsung. They offered me this garbage Nokia in the meantime... Just wondering how you might recommend trying to get some compensation for my troubles?
- 2 dead phones in 13 weeks
- Paying $62 per month for data/service...but with this loaner I get no data (internet, but browser is not worth using). I do not want to pay this months bill...
Kops said:
I've gone to the TBooth where I bought the phone, they have set up a return with Bell/Samsung. They offered me this garbage Nokia in the meantime... Just wondering how you might recommend trying to get some compensation for my troubles?
- 2 dead phones in 13 weeks
- Paying $62 per month for data/service...but with this loaner I get no data (internet, but browser is not worth using). I do not want to pay this months bill...
Click to expand...
Click to collapse
I've had my phone mess up twice - but I just go into recovery mode and wipe/reset everything - then when I reboot it's fine - but I KNOW that mine is somewhat faulty too.
How long does it take to replace? do you have a #? I am in Calgary
Funkadelick said:
I've had my phone mess up twice - but I just go into recovery mode and wipe/reset everything - then when I reboot it's fine - but I KNOW that mine is somewhat faulty too.
How long does it take to replace? do you have a #? I am in Calgary
Click to expand...
Click to collapse
I thought this might work for me too, I can access recovery/download mode but wiping or even flashing new ROM's still don't make this phone boot.
I've been told it will take 2-5 days for the shipping box/label to arrive at my house from Samsung, then 2-5 days return shipping to Samsung, then 2-5 days for processing, and 2-5 days for return shipping once again. I've been told it can take anywhere from 2-6 weeks.
In the meantime...
{
"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"
}
Are Bell phones the only ones that are experiencing Internal SD failures?
Yes, it seems that the chances of your Bell phone failing are almost certain in its lifetime, some more than others.
Call bell customer support. They should credit your account for $100. I'm on my second SGS now. Shipped to me with 2.2 JL2. DOM is Nov 2010.
Sent from my GT-I9000M using XDA App
Hello,
I was asked by my boss to retrieve the data from a not working Huawei P9 if possible.
Following scenario:
A coworker attached his phone via USB to his laptop. The phone restarted two times but he didnt think its a problem.
Next day he thinks its a good idea to restart his phone because it seemed a bit laggy but after turning it of (restarting) the phone doesnt
turn on anymore. No lights, no nothing. If you plug it into the pc you can still hear the "new device attached" sound and can also hear this sound
when pressing the power button and volume down button for about 10 seconds. There is also no charging light when connecting it to the pc.
I repaired some phones before but most of the times it was just hardware stuff which wasnt a problem. I talked to a repair shop that told me
the battery is probably ok and the memory/data has to be read out of the phone and that would cost at least 200€.
Is there anything else I can do?
The phone is a stock Huawei P9. Nothing changed or flashed ever. The data would be crucial for me and my work colleagues.
Thank you!
Here is a screenshot of what my device manager on windows looks like. I installed a driver for the phone I downloaded online with driver signature turned off.. Thats everything I got so far.
{
"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"
}
Keratonko said:
Hello,
I was asked by my boss to retrieve the data from a not working Huawei P9 if possible.
Following scenario:
A coworker attached his phone via USB to his laptop. The phone restarted two times but he didnt think its a problem.
Next day he thinks its a good idea to restart his phone because it seemed a bit laggy but after turning it of (restarting) the phone doesnt
turn on anymore. No lights, no nothing. If you plug it into the pc you can still hear the "new device attached" sound and can also hear this sound
when pressing the power button and volume down button for about 10 seconds. There is also no charging light when connecting it to the pc.
I repaired some phones before but most of the times it was just hardware stuff which wasnt a problem. I talked to a repair shop that told me
the battery is probably ok and the memory/data has to be read out of the phone and that would cost at least 200€.
Is there anything else I can do?
The phone is a stock Huawei P9. Nothing changed or flashed ever. The data would be crucial for me and my work colleagues.
Thank you!
Here is a screenshot of what my device manager on windows looks like. I installed a driver for the phone I downloaded online with driver signature turned off.. Thats everything I got so far.
Click to expand...
Click to collapse
You could check with DC Phoenix, Ministry of Solutions and Chimera - describe them a problem and ask if they can help to retrieve data.
It's probably a hardware issue, and you will not be asking to unbrick (if really a hardware problem, even if you succeed to get it booting again, it could happen again) but just to retrieve data.
With DC and Chimera, you will have to work on your own, just to play for their tools (but it will be cheaper then Huawei service shop).
Ministry of solutions might be even cheaper but they will probably want to work with remote access to your PC - maybe asking you first to open back cover and to short-wire for Test points pins.
Might be best bet for you, but you must consider the security concerns for such a remote access work (at the end of the day, if you bring phone to the service shop, you can also only trust them regarding the data they find on the phone)
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
https://ministryofsolutions.com/paid-services/amp
https://chimeratool.com/
zgfg said:
You could check with DC Phoenix, Ministry of Solutions and Chimera - describe them a problem and ask if they can help to retrieve data.
It's probably a hardware issue, and you will not be asking to unbrick (if really a hardware problem, even if you succeed to get it booting again, it could happen again) but just to retrieve data.
With DC and Chimera, you will have to work on your own, just to play for their tools (but it will be cheaper then Huawei service shop).
Ministry of solutions might be even cheaper but they will probably want to work with remote access to your PC - maybe asking you first to open back cover and to short-wire for Test points pins.
Might be best bet for you, but you must consider the security concerns for such a remote access work (at the end of the day, if you bring phone to the service shop, you can also only trust them regarding the data they find on the phone)
Click to expand...
Click to collapse
Thanks for the answer! I will check out the websites you linked and go from there.
Thanks for helping out!
Hi Guys - as a bit of pretext, I am not an Android aficionado by any means. I’m a regular Australian consumer with a problem I’m struggling to solve...
I have a 6 month old Samsung Galaxy S10. While travelling overseas, I attempted to turn on the WiFi to login to a public WiFi hotspot, and the WiFi button turned blue for about a second or two, then automatically went back to grey. After doing this a few times, I decided to restart the phone. The phone then booted into “Download Mode” with a red error message at the top reading one of a version of the following (Hash of data does not match digest in descriptor):
{
"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"
}
The phone has been somewhat unreliable in the past with bouts of *all* apps crashing on me at once for some reason, but nothing like this had ever happened before.
Googling the issue I’ve tried all combinations of Bixby, Volume Up, Volume Down and Power and after multiple goes and letting the battery drain, eventually got it to Boot (must’ve just got the timing right). However, upon restart, it just does the same thing and I’m back to where I started. I have tried factory reset as well - no change. The only advice I have seen is to attempt to flash new firmware with software such as Odin, but at the risk of bricking the phone and voiding my warranty, I’ve opted to return it to my retailer in the hopes a warranty repair can take place.
My primary concern is that most people I’ve talked to seem to be under the impression that the only way this error can occur is if I had attempted to flash 3rd party firmware onto the phone and have somehow tampered with that which ought not be tampered with. My retailer also appears to be under this impression, and given the splash screen that appears on about 60% of boot cycles has a big warning icon with “The phone is not running Samsung’s official software”, I’m concerned that this will make the case for them that warranty repair is unavailable as I have tampered with the phone and voided the warranty. Even if I knew *how* to do something like this, I’m far too poor to be risking warranties of a $1000 phone, and have never installed anything on the phone except for stuff off of the Google Play store. So I’m at a bit of a loss as to how this happened.
With that novel written, my main questions here are a) are there any “legitimate” reasons I can argue with my retailer that this error might occur through? I have a feeling I’ll have a fight on my hands to be able to claim warranty and I’d like some other reasons this may occur other than tampering to throw at them. B) Failing warranty repair, what is the recommended route through which I may repair this myself? Is it firmware flashing time?
My thanks in advance for your help.
Regards,
QLD.
Norsefire said:
Hi Guys - as a bit of pretext, I am not an Android aficionado by any means. I’m a regular Australian consumer with a problem I’m struggling to solve...
I have a 6 month old Samsung Galaxy S10. While travelling overseas, I attempted to turn on the WiFi to login to a public WiFi hotspot, and the WiFi button turned blue for about a second or two, then automatically went back to grey. After doing this a few times, I decided to restart the phone. The phone then booted into “Download Mode” with a red error message at the top reading one of a version of the following (Hash of data does not match digest in descriptor):
The phone has been somewhat unreliable in the past with bouts of *all* apps crashing on me at once for some reason, but nothing like this had ever happened before.
Googling the issue I’ve tried all combinations of Bixby, Volume Up, Volume Down and Power and after multiple goes and letting the battery drain, eventually got it to Boot (must’ve just got the timing right). However, upon restart, it just does the same thing and I’m back to where I started. I have tried factory reset as well - no change. The only advice I have seen is to attempt to flash new firmware with software such as Odin, but at the risk of bricking the phone and voiding my warranty, I’ve opted to return it to my retailer in the hopes a warranty repair can take place.
My primary concern is that most people I’ve talked to seem to be under the impression that the only way this error can occur is if I had attempted to flash 3rd party firmware onto the phone and have somehow tampered with that which ought not be tampered with. My retailer also appears to be under this impression, and given the splash screen that appears on about 60% of boot cycles has a big warning icon with “The phone is not running Samsung’s official software”, I’m concerned that this will make the case for them that warranty repair is unavailable as I have tampered with the phone and voided the warranty. Even if I knew *how* to do something like this, I’m far too poor to be risking warranties of a $1000 phone, and have never installed anything on the phone except for stuff off of the Google Play store. So I’m at a bit of a loss as to how this happened.
With that novel written, my main questions here are a) are there any “legitimate” reasons I can argue with my retailer that this error might occur through? I have a feeling I’ll have a fight on my hands to be able to claim warranty and I’d like some other reasons this may occur other than tampering to throw at them. B) Failing warranty repair, what is the recommended route through which I may repair this myself? Is it firmware flashing time?
My thanks in advance for your help.
Regards,
QLD.
Click to expand...
Click to collapse
TL : DR (well, didnt read all of it)
you wont void your warranty by flashing factory firmware with Odin. You just wont. Even if you screw it up, it still wont void your warranty. You could even flash the totally wrong firmware and hard-brick it and you still wont void your warranty. Matter of fact, its a: super hard to hard-brick galaxy phones anymore b: a very intentional thing to void your warranty. You have to unlock your bootloader, flash TWRP and root it. Shy of that, flashing stuff will not void your warranty. Thats one of the beauties of Samsung S devices.
Anyways, go to sammobile.com/firmwares and get the latest version of your phones firmware by using Samfirm or the Frija tool (they download the massive files FAR faster than doing it directly from sammobie itself) and flash it in Odin. Instructions on how to use Frija or Samfirm here.
Once the Odin flash completes, your phone should boot normally provided that your phone doesnt have hardware issues etc etc.
Whilst you won't void your warranty, with this not being rooted and likely still in warranty... get it fixed or replaced by sammy?
Did you ever get it to work? Mine is doing the same thing
hi guys
so this is my question\story, back in may '21 got my zf8 8/128gb unlocked eu model.
forward 10 months the phone fell on its rear upper corner, cracked the rear glass and the main camera stopped working.
the price of a new camera module is basically the price of another good second hand smartphone. so, i found by chance zf8 16/256gb with broken (but working) front screen for dirt cheap (everything is in order imei serial numbers etc). first thing, swapping cameras between boards is ok, swapping boards makes the fingerprint scanner useless even though in test mode .12345+= the sensor is ok and i dont get any errors or messages from the system. i tried factory resetting, boot unlocking, factory resetting from recovery mode, setting fingerprint in safe mode, with no luck. what is going on? i found nothing useful on the net. it seems like there is some stupid solution that i am missing. what should i try next?
Maybe try setting the fingerprint in a custom rom, like LineageOS? It could work as it is probably something asus put in their ROM to prevent users from swapping things left and right. So if that lock is set in the ROM it could work, if it is firmware locked, whicch I think is the most likely, it most likely won't work. Still worth the try though
Adaoh said:
Maybe try setting the fingerprint in a custom rom, like LineageOS? It could work as it is probably something asus put in their ROM to prevent users from swapping things left and right. So if that lock is set in the ROM it could work, if it is firmware locked, whicch I think is the most likely, it most likely won't work. Still worth the try though
Click to expand...
Click to collapse
i was gonna try this but got cold feet, afraid i will get stuck with no working scanner with the original mother board. i will try rooting as a last resort although i was almost there. if only there was a way to get an engineer code or put the device in a service mode like the onepluses of the world...
Adaoh said:
Maybe try setting the fingerprint in a custom rom, like LineageOS? It could work as it is probably something asus put in their ROM to prevent users from swapping things left and right. So if that lock is set in the ROM it could work, if it is firmware locked, whicch I think is the most likely, it most likely won't work. Still worth the try though
Click to expand...
Click to collapse
i just tried it and.... its not working... swapped the boards and it worked fine on the original screen. lesson learnt
Another loss for right to repair... That sucks, maybe you could try to detach only the fingerprint scanner from the display to keep on the original motherboard
Adaoh said:
Another loss for right to repair... That sucks, maybe you could try to detach only the fingerprint scanner from the display to keep on the original motherboard
Click to expand...
Click to collapse
{
"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"
}
first, i tried, its nearly impossible to separate the screen from the chassis without pro tools and without breaking it. i dont mind breaking the already broken screen, but it will be risky with the good screen.
second, there is no scanner for sale by asus or any other shop on the internets and by looking at picture above from ebay you can see that the scanner is part of the screen electronic circuit...
i called the service center in my country to ask if its possible for them to swap the screens between my phones, and the answer i got was no. they said that i have to give them about 45 days to check the damage and only then will they give me a quote for the repaire . i dont want to sound like a karen, but i need to speak with a manager. it wouldn’t be fair to talk s**t on asus because the service center is not an asus owned and run operation, its an “authorized“ service center. so i need to hit asus zentalk forum or somethig… lets get this show on the road see whats really going on…
AJ205 said:
i called the service center in my country to ask if its possible for them to swap the screens between my phones, and the answer i got was no. they said that i have to give them about 45 days to check the damage and only then will they give me a quote for the repaire . i dont want to sound like a karen, but i need to speak with a manager. it wouldn’t be fair to talk s**t on asus because the service center is not an asus owned and run operation, its an “authorized“ service center. so i need to hit asus zentalk forum or somethig… lets get this show on the road see whats really going on…
Click to expand...
Click to collapse
Can you update what was the private massage? It's really interesting to see what's going on behind the curtains, if you are not comfortable sharing it here my telegram is @MOSSADAVICH