Hi,
I hope I'm right on this forum, because my A70 is not rooted and has no custom ROM installed.
Despite NOT having touched ROM or any other option for that matter (just regular app update), I noticed the device started bootlooping ever since this morning. It had done this before, but only because automatic updates had been deactivated in google Play and some apps seemed to cause problems.
Battery is charged at 82%
Solutions tried:
Updating all apps in play store
Boot Menu > Wiping Cache
In the beginning it seemed the device was able to restart with the GUI up, but then it went right back into Loop.
Cannot access the phones normal operation mode any more.
Am I the only one to experience this ?
Please help. Thank you.
A factory reset would be my goto...
Try power up in safe mode. alternatively, power off the phone, then startup while holding the vol up button, wipe everything.
It's possible an application was causing this behavior so booting into safe mode would have probably helped, but since you can't access your phone now...a reset is all you can do.
If you have the zipped or "unpacked" files for your current firmware. You can extract AP or copy it to another place i.e. desktop. Delete the .md5 and open the tar as an archive. Extract system.img.ext4.lz4 to your desktop and delete the tar you just copied. Add the system.img.ext4.lz4 to a tar archive with PeaZip. You can use 7zip but I was having problems with it. Flash the system.img.ext4.tar in your AP odin and you should be able to boot up again. It will replace your system partition but you won't lose any data.
Edit: You might have to clear the cache after it is done with Odin. After it boots up regularly you can back up your important stuff on your phone, and possibly delete your third party app that was updated and test the reboot again.
xomikron said:
It's possible an application was causing this behavior so booting into safe mode would have probably helped, but since you can't access your phone now...a reset is all you can do.
Click to expand...
Click to collapse
2ISAB said:
A factory reset would be my goto...
Try power up in safe mode. alternatively, power off the phone, then startup while holding the vol up button, wipe everything.
Click to expand...
Click to collapse
Thank you for your replies & sorry for late reply.
Yes, I tried safe mode also. It does not change behavior. Factory reset would be very last resort.
cealaska said:
If you have the zipped or "unpacked" files for your current firmware. You can extract AP or copy it to another place i.e. desktop. Delete the .md5 and open the tar as an archive. Extract system.img.ext4.lz4 to your desktop and delete the tar you just copied. Add the system.img.ext4.lz4 to a tar archive with PeaZip. You can use 7zip but I was having problems with it. Flash the system.img.ext4.tar in your AP odin and you should be able to boot up again. It will replace your system partition but you won't lose any data.
Edit: You might have to clear the cache after it is done with Odin. After it boots up regularly you can back up your important stuff on your phone, and possibly delete your third party app that was updated and test the reboot again.
Click to expand...
Click to collapse
Thank you for trying to help. Where can I find the files of my current firmware ?
Did you ever download firmware for you phone or were all your updates OTA? You can use SamFirm, Frija or samfrew.com to get the firmware for you phone. First 2 are fast depending on your internet connection. Samfrew is slower but it is the one I use because I don't have a fast internet connection and I can download it on my phone because I don't have WiFi.
cealaska said:
Did you ever download firmware for you phone or were all your updates OTA? You can use SamFirm, Frija or samfrew.com to get the firmware for you phone. First 2 are fast depending on your internet connection. Samfrew is slower but it is the one I use because I don't have a fast internet connection and I can download it on my phone because I don't have WiFi.
Click to expand...
Click to collapse
I started here. BKs thread
https://forum.xda-developers.com/galaxy-a70/how-to/galaxy-a70-firmware-list-variants-t3957239
---------- Post added at 08:27 AM ---------- Previous post was at 08:26 AM ----------
ikkanomyoju said:
Thank you for trying to help. Where can I find the files of my current firmware ?
Click to expand...
Click to collapse
Sorry quoted the wrong person this one's for you
https://forum.xda-developers.com/galaxy-a70/how-to/galaxy-a70-firmware-list-variants-t3957239
Also BK has that device he develops
Hi guys,
thank you for the links and suggestions! - So far I did the following
Updated all the apps
took out the sim card
wiped the cache
and turned on "automatic updates" on google play (yikes!)
Phone seems to run stable so far.
But it will probably start bugging again soon. So I'll bring an update
update
... here we go, the phone crashed again.
So I guess it wasn't the SIM card or the app updates.
Now only the Samsung Boot screen appears and it is stuck. No way to power off device, no way to get past the boot screen.
Using my old phone now.
update 2
ikkanomyoju said:
... here we go, the phone crashed again.
So I guess it wasn't the SIM card or the app updates.
Now only the Samsung Boot screen appears and it is stuck. No way to power off device, no way to get past the boot screen.
Using my old phone now.
Click to expand...
Click to collapse
So here's what happened in the meantime:
> let the battery completely drain
> full charge
> boot to recovery
> wipe cache
Now phone is stable for longer than before (>24h).
It looks like a battery issue. Possibly the battery statistics file. Idk.
Does anyone know if inaccurate battery stats can cause irregular reboots of this kind ?
Update
So my last question can be answered.
It really looks like it's the battery that is causing the problems. Did some research: random reboots have been described with battery problems also.
Yesterday it died completely. Even with the phone off, charging is not possible.
6 months after buying a brand new A70 in a certified store, that is.
Sending it in to Samsung Repair Service.
ikkanomyoju said:
Update
So my last question can be answered.
It really looks like it's the battery that is causing the problems. Did some research: random reboots have been described with battery problems also.
Yesterday it died completely. Even with the phone off, charging is not possible.
6 months after buying a brand new A70 in a certified store, that is.
Sending it in to Samsung Repair Service.
Click to expand...
Click to collapse
If you haven't modified it in anyway just service centre would be do it way to go with warranty but keep in mind there will be if fees.
2ISAB said:
If you haven't modified it in anyway just service centre would be do it way to go with warranty but keep in mind there will be if fees.
Click to expand...
Click to collapse
No custom ROM. The A70 has not been modified in any way.
( ... )
update:
Samsung denies any kind of local guarantee because the A70, though brand new, was bought in the wrong country.
The device is an original Samsung manufactured product, but they "cannot repair it under guarantee, since the phone was bought abroad and necessary spare parts could not be ordered".
- Well isn't this funny: the manufacturer himself cannot order original parts for his own product, while an ordinary phone repair shop has no problem doing that.
They just won't have anything to do with it. To top it all, this A70 was not an intentional buy, it was a replacement for a Galaxy S7 that suddenly went dead while traveling.
Bad joke this must be.
ikkanomyoju said:
update:
Samsung denies any kind of local guarantee because the A70, though brand new, was bought in the wrong country.
The device is an original Samsung manufactured product, but they "cannot repair it under guarantee, since the phone was bought abroad and necessary spare parts could not be ordered".
- Well isn't this funny: the manufacturer himself cannot order original parts for his own product, while an ordinary phone repair shop has no problem doing that.
They just won't have anything to do with it. To top it all, this A70 was not an intentional buy, it was a replacement for a Galaxy S7 that suddenly went dead while traveling.
Bad joke this must be.
Click to expand...
Click to collapse
If you bought it on eBay or Amazon DEMAND a replacement. Or you're going to be forced to get PayPal involved.
Happened to me and my father's phone from a "top seller".
The thing is, they buy the phones cheap without warranty and market them off to a victim unknowingly aware of the legal scam.
My HTC was returned 3 times before I got a new one, I knew it was new because there hadn't been any updates. My father's iPhone was from the same seller.
If you purchased it from another source, making legal threats may just scare the punk in to giving you a refund.
*A legal threat is acceptable in the eyes of any law*
Stay safe
edit..haha
Related
I bought a Galaxy S Glide (I think the same as the Blaze) from an outlet in Hong Kong on import from Canada (on boot it says "Rogers" so I can assume it's from Canada).
After using it for a week it suddenly stopped using the network and said that I need a lock code.
I went back to the shop where I bought it and they said they couldn't do anything immediately and would I like a replacement, which seemed like a nice thing to do.
However, after a couple of days I notice a glitch on the screen happen a couple of times.
I refused to believe it was a big problem (because it was my new phone right!) within a week the screen started to totally crash to the point that it would freeze in the boot up process.
You can see a picture attached of how the screen looks after I managed to do a hard reset.
When it starts to go like this, you cant do anything with it.
The guy at the shop wont change it or refund it, he claims I dropped it.
Samsung Hong Kong don't support it because it's from Canada and the only shop that knows what to do with it is the guy that sold it to me.
I'm taking the guy to the small claims court, but I'd rather have a fixed phone.
Any ideas please?
Thats happen to me, is a problem with the roger version. Everything in internet say the problem is hardware, but now mines works perfect. So, is like a bug in the rogers, maybe hardware problem, but if can be fixed with software i dont think so.
If you flash ICS with superoneclick (will remove rogers bootscreen) the problem will be fixed, of course you can flash it with a tar image with odine and will have the rogers bootscreen too. With that the phone will work again.
links
lorddavid said:
........... problem with the roger version. Everything in internet say the problem is hardware, but ..............
Click to expand...
Click to collapse
I have searched for more information about this problem, but couldn't find anything, do you have any links to anything?
Thanks again for your help.
they dont say exactly, but if you see users with similar problem, they have rogers version, at least all the user that i see with this problem.
Just do what i say, install ICS; and the problem will solve.
Follow this http://www.theandroidsoul.com/andro...ich-update-for-att-captivate-glide-i927uclg9/ for installing the one click.
Sent from my SGH-I927 using xda app-developers app
lorddavid said:
Thats happen to me, is a problem with the roger version. Everything in internet say the problem is hardware, but now mines works perfect. So, is like a bug in the rogers, maybe hardware problem, but if can be fixed with software i dont think so.
If you flash ICS with superoneclick (will remove rogers bootscreen) the problem will be fixed, of course you can flash it with a tar image with odine and will have the rogers bootscreen too. With that the phone will work again.
Click to expand...
Click to collapse
I strongly doubt this, that looks and sounds like a hardware fault. But hey, if there's no warranty option, you've got nothing to lose...
-E- FWIW, I would boot it into download mode, and let it sit on that screen for an hour. Then plug it into your computer and make sure Odin sees it. If it hangs while in download mode DO NOT FLASH ANYTHING. You REALLY don't want your phone to hang mid-bootloader-flashing, that's an automatic fullbrick...
roothorick said:
I strongly doubt this, that looks and sounds like a hardware fault. But hey, if there's no warranty option, you've got nothing to lose...
-E- FWIW, I would boot it into download mode, and let it sit on that screen for an hour. Then plug it into your computer and make sure Odin sees it. If it hangs while in download mode DO NOT FLASH ANYTHING. You REALLY don't want your phone to hang mid-bootloader-flashing, that's an automatic fullbrick...
Click to expand...
Click to collapse
That was all say, but, in odin my glide never freeze, only freeze while booting or charging too. But not in odin. And right now is working without any screen freeze.
lorddavid said:
users with similar problem, they have rogers version, at least all the user that i see with this problem.
Click to expand...
Click to collapse
So you have seen others with this problem? Where have you have seen these?
lorddavid said:
Just do what i say, install ICS; and the problem will solve.
Click to expand...
Click to collapse
Can this be rolled back ?
hkcharlie said:
So you have seen others with this problem? Where have you have seen these?
Can this be rolled back ?
Click to expand...
Click to collapse
If the device is no more under warranty, I would say trying this would not harm the device anymore. Also this is a samsung released update so nothing unofficial about it.
Sent from my SGH-I927 using xda app-developers app
if you search in internet about freeze problem in glide you will see. Can be roll back with odin. But, if you have no warranty on your device, you dont have nothing to lose, and much to win if the problem solve
My brother had this same problem on his glide (bought at newegg). I got him to install galaxym unlock (galaxsim? Something like that), and you purchase an inapp unlock for $3, and it runs, reboots your phone and you regain unlock. They claim its permanent. So far my brother didnt get locked again.
Is cheap, fast and you can also see in the reviews that there are more glides that used it and worked.
Hope this helps!
Sent from my SGH-I927 using Tapatalk 2
luquiyahni said:
My brother had this same problem on his glide (bought at newegg). I got him to install galaxym unlock (galaxsim? Something like that), and you purchase an inapp unlock for $3, and it runs, reboots your phone and you regain unlock. They claim its permanent. So far my brother didnt get locked again.
Click to expand...
Click to collapse
This helped with the frozen screen as shown in the picture?
thats for unlock, is possible that your phone will lock again when update to ICS. my phone was too from newegg and is rogers, thats why i say is a problem with rogers version.
Do what i tell you, you have nothing to lose
lorddavid said:
thats for unlock, is possible that your phone will lock again when update to ICS. my phone was too from newegg and is rogers, thats why i say is a problem with rogers version.
Do what i tell you, you have nothing to lose
Click to expand...
Click to collapse
Thanks for thinking about my problem, but this solution misses one very big point, the phone that was locked was changed for the phone that has a screen that doesn't work.
I do not have the locked phone any more.
probably will lock again after you flash ICS via odin, thats happen to me. Is not a screen problem, again, if you want to try to solve, do what i say before.
I have the exact same problem, was just about to post in the other thread about this: http://forum.xda-developers.com/showthread.php?t=1953672
Bought my phone from Amazon US marketplace about a month ago (but live in the UK), and suddenly the phone did that on start up one day. However, I agree with lorddavid, it is not a hardware fault as it does not freeze in download mode. Samsung service centres won't repair as it does not have a UK warranty, and although I can get a refund by returning I would rather have a working phone.
lorddavid said:
If you flash ICS with superoneclick (will remove rogers bootscreen) the problem will be fixed, of course you can flash it with a tar image with odine and will have the rogers bootscreen too. With that the phone will work again.
Click to expand...
Click to collapse
Was very happy to read this, seems like I'll have to try it. Have been putting it off as it will wipe my phone which I did not want to do just yet - I have a lot of photos and clips which I can't exactly back up as it does not boot normally. Really annoying. Any way to access these/back up before flashing?
And another question, that ICS update is the first leaked one which carried a few bugs (as did the official UCLH2 one) - can I install the fixed UCLJ3 straight away? And do I need a rooted phone in the first place? In Rawr0w0's initial post it seems to suggest I do. Sorry for all the questions, and thanks in advance.
dont remember, i think is the UCLH2, and i think that there was a odin flashable of the latest version (with bug fixes), you can try that (but dont know where download it :/ )
Do you have the photos in your internal storage? i think if you flash with one click, it will delete it, but if you flash the firmware via odin, it doesnt delete it (but i am not 100% sure)
And no, you dont need root to install roms via odin
This is UCLH2 without one click
http://androidromupdate.com/2012/09...-firmware-upgrade-official-kiesota-stock-rom/
And here is the latest version with bug fixes (like keyboard light)
http://androidromupdate.com/2012/11/10/i927uclj3-new-ics-4-0-4-for-samsung-sgh-i927-captivate-glide/
These are the officials. But the second link i never try it to flash because when i has the problem there wasnt that version
Thanks, yeah that's where I was getting the files from, I'll try it tonight, will probably go for the second link, the UCLJ3 rom.
lorddavid said:
And here is the latest version with bug fixes (like keyboard light)
These are the officials. But the second link i never try it to flash because when i has the problem there wasnt that version
Click to expand...
Click to collapse
YES WAHOO!! My phone works! Thank you for the advice! I mainly got it from the other thread but without having read your attempt at flashing I would never have tried it - I'm so happy! I managed to make a back up and copy my media via CWM anyway, but everything was still on there including all my texts and whatsapp messages, and now I have ICM 4.04 too!
Phew I thought I would have to send it back, get a refund and order another one which is a massive pain and lose everything on my phone.
Hkcharlie, you need to try this!
lyricalwax said:
YES WAHOO!! My phone works! Thank you for the advice! I mainly got it from the other thread but without having read your attempt at flashing I would never have tried it - I'm so happy! I managed to make a back up and copy my media via CWM anyway, but everything was still on there including all my texts and whatsapp messages, and now I have ICM 4.04 too!
Phew I thought I would have to send it back, get a refund and order another one which is a massive pain and lose everything on my phone.
Hkcharlie, you need to try this!
Click to expand...
Click to collapse
thats cool Enjoy the phone, is a great phone
---
Is the baseband showing as Unknown instead of I927UCsomething? That we may be able to fix. Otherwise you're kinda screwed :/
The fact the codes don't work suggests that we don't have a Qualcomm radio. Since it's usually inside the SoC that doesn't surprise me.
This may work: http://gsmforum7.blogspot.com/2012/04/samsung-android-repair-efs-imei-repair.html
idulkoan said:
i have recently bought the samsung captivate glide off of ebay. I live in the UK so i am not on att. I updated my glide to ics, installed cwm recovery, and rooted it. The phone is unlocked so it worked great. I was using a giffgaff sim (o2 network), and everythign worked great, except mms. I found an app that fixes mms, but when I ranit it deleted all my apns and froze the phone. I rebooted the phone and now there is no imei. I do not have an efs backup. After i found that my service is gone and that my imei is gone, i backed up the damaged efs and started reading up and editing it. I finally got my imei changed, but its still incorrect and my service was still not working. I restored my corrupted efs folder back and now it still has no imei. How can i repair my imei? i looked all over the internet, and was going to try qpst but i cant get this phone in diag mode for the com port. What should i do?
ps this exact thing happened to me last year when i lived in america on metro pcs, but to fix it I went into the metro pcs store and they flashed my imei back.
Click to expand...
Click to collapse
Read this http://forum.xda-developers.com/showthread.php?t=2019540 and see the post no. 2. It has link to a site run by an individual, see if that helps http://www.cvxcvx.pl/?lang=en as it has i927 in his list.
doesnt work..
---
Have you tried installing a GB ROM, especially stock?
idulkoan said:
i dont have any .bak files in the efs.. :/
The imei editor (generator) only lets me put in 14 characters, but my imei is 15 characters long..
the "Android Language Editor with Android Language Project" requires the purchased version in order to use the imei settings
Click to expand...
Click to collapse
You should have looked on the other link i gave in my post above. anyway check this out http://www.cvxcvx.pl/podstrona-0/check-when-repair-no-problem?lang=en.
For 10 euros, the guy promises to fix it 99% of the cases where the imei no is either shown as all zero's or ending with '640000' . Other cases are also mentioned.
---
efs question
---
idulkoan said:
if i backup my efs on a spare android phone that works but I do not use, and restore it to my glide, wil that work?
[like will my imei be changed to the other phones so that my service will work? and for people that think my phone is stolen, it isnt and my original imei is not blocked especially because im using this phone in a different country (england instead of att in america)]
i dont mind a different imei, as long as i kan get the service back on this phone. I am going to 2 repair shops today to see if they can restore my imei to my original one.
Click to expand...
Click to collapse
The other phone should be samsung glide i927 and not just any other phone. But then i think you'll have 2 phones with same imei no.s which is illegal in many countries and is termed as cloning. And i'm not sure but XDA probably discourages these kind of discussions.
Let us know what was the outcome of going to the repair shops and best of luck. :good:
FIXED
---
idulkoan said:
i dont have any .bak files in the efs.. :/
Click to expand...
Click to collapse
Did you check with ls -a in adb? dotfiles don't show up in most file managers.
fixed.. sort of
---
roothorick said:
Did you check with ls -a in adb? dotfiles don't show up in most file managers.
Click to expand...
Click to collapse
---
idulkoan said:
ok so this problem is still here but randomly. If i reboot the phone, sometimes the imei doesnt show up and i have to turn off turn back on, and then if the imei isnt there i have to take out the battery and wait a minute then turn it back on and then its fixed. SO the problem is here still [randomly happens, usually when not shutting down properly (like holding power button till the screen jsut shuts off) or when rebooting the phone a couple times with the build in reboot option] but the solution is to reboot onces or twice to bring it back to fix it.
Click to expand...
Click to collapse
I had the same problem in India and it keeps increasing till you cant use the phone. I discussed it with some repair shops and they were quite clear that its a software issue and needs "box" to fix it along with Samsung software. Even the samsung service center recommended getting it flashed properly and it will start working. Unfortunately, cant locate a local repair shop here which can flash this.
Suggest u get it properly fixed now, if possible from an official Samsung service center.
oh ok
---
idulkoan said:
oh ok thanks for the info so basically this will keep happening until it stops working? cause it does still happen, but I kn fix it by taking out the battery and putting the battery back in..
Click to expand...
Click to collapse
Atleast thats what happened to my phone. Taking out battery would get the phone working, but the problem would surface after some time.
I flashed a lot of roms and the best rom I used was Osimod GB (with regards to this problem only) as it used to work for 2-3 days before giving the problem. Also, typically, it would happen a bit after you make or get a call. You can observe for sometime and see if its the same problem and if it is growing.
idulkoan said:
whats the full adb command? ahha
Click to expand...
Click to collapse
"adb shell ls -a /efs" should show everything. May need to be root, I'll have to check.
---
mrigancb said:
I had the same problem in India and it keeps increasing till you cant use the phone. I discussed it with some repair shops and they were quite clear that its a software issue and needs "box" to fix it along with Samsung software. Even the samsung service center recommended getting it flashed properly and it will start working. Unfortunately, cant locate a local repair shop here which can flash this.
Suggest u get it properly fixed now, if possible from an official Samsung service center.
Click to expand...
Click to collapse
I have similar problem with my galaxy s2 and posted in the forum
http://forum.xda-developers.com/showthread.php?t=2061816
Did you get your phone fixed ? if so can you let me know the steps .
thanks
---
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.
Attempted to go back to stock ROM. From TWRP, I wiped everything except external and shutdown. Attempted to restart and nothing. Deader than or door nail. Pulled the battery and held down the power button for over a minute with no affect. Battery was 75% charged with I performed the wipe. I connect to phone to my pc and get a "USB Device Not Recognized"
Is the phone a lost cause?
Thanks,
Jeremy
gimmezell said:
Attempted to go back to stock ROM. From TWRP, I wiped everything except external and shutdown. Attempted to restart and nothing. Deader than or door nail. Pulled the battery and held down the power button for over a minute with no affect. Battery was 75% charged with I performed the wipe. I connect to phone to my pc and get a "USB Device Not Recognized"
Is the phone a lost cause?
Thanks,
Jeremy
Click to expand...
Click to collapse
If you wipe everything but extSdCard, you must flash something. Either flash stock tar update in Odin or flash a custom ROM in recovery.
Help any?
Sent from my SM-N920P using Tapatalk
Yes, I know. I was going to go into download mode to Odin stock ROM but the phone will not even turn on anymore.
gimmezell said:
Yes, I know. I was going to go into download mode to Odin stock ROM but the phone will not even turn on anymore.
Click to expand...
Click to collapse
OK. Did you try a long battery pull and try again?
Edit: I may have misunderstood you but you did say you tried to restart. Did you mean download mode with long press of volume up, home plus power button combination.
Sent from my SM-N920P using Tapatalk
Sorry for any confusion. I pulled the batter for a good ten minutes and still unable to turn the phone on. Plugged the phone into a charger has no effects on it either.
So download and recovery key sequence fails for both? Plugging in charger or USB to PC, no beep or display?
What version of TWRP were you using? If 3.0, did you get it from official site? How did you install it?
Sent from my SM-N920P using Tapatalk
Yes, both download and recovery key sequences fail. Plugging into charger, no charge LED comes, no haptic feedback, no beep or display. When I plug it into my computer it says "USB Device Not Recognized".
EDIT - I'm pretty sure my bootloader is hosed.
gimmezell said:
Yes, both download and recovery key sequences fail. Plugging into charger, no charge LED comes, no haptic feedback, no beep or display. When I plug it into my computer it says "USB Device Not Recognized".
Click to expand...
Click to collapse
Just curious about the TWRP version. There's been a couple or more cases like yours and it seemed to show up about the time users reported issues with TWRP update.
I think you should get the phone checked by a tech or engineer. Sprint has been helpful to users having hardware failure with issues like updates bricking the phone. With flagship phones not selling well and carrier wars, retention is key and nearly economical right now.
Sent from my SM-N920P using Tapatalk
Yeah, TWRP 3.0 did come up on my searches. I did have TWRP 3.0 installed that I got from their official site.
I did see the below post on how to unbrick that tells me it may be possible to a Note 4 image onto an sd card.
http://forum.xda-developers.com/showthread.php?t=2660566
Did this work for you? I also have twrp 3.0 and hope to not run into an issue like this.
Alakazamm said:
Did this work for you? I also have twrp 3.0 and hope to not run into an issue like this.
Click to expand...
Click to collapse
I'm using 3.0 too but I waited for the official version that worked and flashed in Odin. No issues for me. Hoping it stays that way.
Sent from my SM-N920P using Tapatalk
gimmezell said:
Yeah, TWRP 3.0 did come up on my searches. I did have TWRP 3.0 installed that I got from their official site.
I did see the below post on how to unbrick that tells me it may be possible to a Note 4 image onto an sd card.
http://forum.xda-developers.com/showthread.php?t=2660566
Click to expand...
Click to collapse
Alakazamm said:
Did this work for you? I also have twrp 3.0 and hope to not run into an issue like this.
Click to expand...
Click to collapse
I did not attempt what was done in the link I posted in my previous post. Today, I mailed the phone off to someone that offers a de-bricking service. Hopefully, they can recover it. I will I knew exactly happened as I did the same procedure many times before. Right now I'm retro-ing it and rocking my Note 2 with STOCK firmware and everything works. :good: :laugh:
@samep mentioned that there were other TWRP 3.0 users that experienced to the something I did or similar. I'm just curious where those threads/posts are.
gimmezell said:
I did not attempt what was done in the link I posted in my previous post. Today, I mailed the phone off to someone that offers a de-bricking service. Hopefully, they can recover it. I will I knew exactly happened as I did the same procedure many times before. Right now I'm retro-ing it and rocking my Note 2 with STOCK firmware and everything works. :good:[emoji23]
@samep mentioned that there were other TWRP 3.0 users that experienced to the something I did or similar. I'm just curious where those threads/posts are.
Click to expand...
Click to collapse
First, I want to acknowledge that what yourself and others have experienced is personal and disappointing. eMMC flash is not the most reliable, efficient and cutting edge memory but it's common to cell phones of previous generations like ours.
It's not easy making an argument that UFS 2.0 used in 2015 Samsung phones is more reliable and less prone to failure but it is faster, lower voltage and far less prone to heat buildup with increased data transfer. So I think that makes a point in favor of the newer tech. Building ART/dalvik-cache can generate a lot of heat as well as 4k recording. The eMMC NAND contributes to that and could also be its undoing.
http://m.tech.firstpost.com/news-an...move-next-gen-ufs-2-0-memory-2015-242072.html
Interesting to see if UFS memory is any more reliable in the months ahead and if Samsung continues to use it this year with micro sdcard making a return to S7. But flashing alone, we know is risky. Proving an application or particular flash causes such would be difficult to prove and it wasn't my intent to point at a particular shared development that is shared freely on XDA. I could have worded that better when I said I hoped my phone continues with no issues- not meaning it to sound like the concern because I flashed the new TWRP. I was merely pointing to the increase of flashing lends to more hardware failure in this forum. We've seen this also with updates and increased flashing when users are confused about which stock tar to flash or thinking they can just go back to KitKat through Odin of KitKat tar. Not blaming users for their failures; anyone of us can the victim with a single flash, not to mention the many flashes and extended boots that are added to a rooted phone's life. To add to that, Samsung still has fixes pending and concerns with download mode.
http://www.slashgear.com/samsung-galaxy-smartphones-receive-security-update-25424269/
Rooted phones may not be getting these updates until another stock tar is released.
Anyway, related or not, here's some other recent failures. There may be others but I'm not trying to prove anything other than saying it seems we have more memory failures than we should on the Note 4.
http://forum.xda-developers.com/note-4-sprint/help/hard-brick-sudden-death-mobo-fried-t3316335
http://forum.xda-developers.com/note-4-sprint/help/screen-pit-partition-firmware-install-t3316162
http://forum.xda-developers.com/showthread.php?p=65018833
I do hope you get a successful and economical repair. It's good that you have a backup phone. And I hope you'll update this thread with progress and result. Best wishes.
Sent from my SM-N920P using Tapatalk
Thank for the info and links @samep.
Update
I sent my phone off last Wednesday to hopefully have it de-bricked and I am happy to report that I will have it back tomorrow. Apparently, some how the custom recovery wiped the boot partition. I'm tempted to keep it stock as my backup phone is stock, uprooted and it just works. Ha
I've ordered a pair of Acker batteries because I was told by Joe, the person who un-bricked my phone, that the battery would drop from 100% to 80% within five minutes.
Needless to say I'm happy to get my Note 4 back tomorrow.
Sent from my SPH-L900 using Tapatalk
Hello folks,
after marshmallow update my note 4 is acting wired (freeze, restart, sometimes doesn't start etc...). Wakelock app is keeping the phone running but still phone is not performing at it's best. It is slow and sluggish etc...
For some reason if I restart the phone (for ota update etc...) it never turns on. It takes multiple attempt of soft resent and taking battery out and in to turn it on. How to fix this?
I did not make any changes to phone in any ways. I am using what ATT has provided me and recently got it unlocked from ATT. Phone is currently running 6.0.1 with February 1, 2017 security patch level.
Any help is appreciated. If there is any existing thread regarding this issue please redirect me there. I may need step by step guide if the solution includes of changing rom, kernel etc... If I have to change rom then I better be changing it to the finest available in the market.
Thanks again
You likely have an app that is causing problems. Look at settings, battery. Is anything hogging your battery use?
Either selectively uninstall apps, or do a factory reset and slowly add apps until your phone states flipping out.
I and others have had this problem, unfortunately you have to figure out what's causing your problem...
Hit thanks If this has helped you...
Shanghai.Knight said:
You likely have an app that is causing problems. Look at settings, battery. Is anything hogging your battery use?
Either selectively uninstall apps, or do a factory reset and slowly add apps until your phone states flipping out.
I and others have had this problem, unfortunately you have to figure out what's causing your problem...
Hit thanks If this has helped you...
Click to expand...
Click to collapse
Hello, I have run the phone in safe mode but phone acts wired ... Have spent hours with tech support but all they said that I have to update for next update from att. Marshmallow has ruined many note 4.
hatemarshmallow said:
Hello, I have run the phone in safe mode but phone acts wired ... Have spent hours with tech support but all they said that I have to update for next update from att. Marshmallow has ruined many note 4.
Click to expand...
Click to collapse
Try to save your data and factory reset. If that not going to work i would consider to ODIN clean firmware on phone. You can find firmware in one of my post about updates
Clicking from Edge of Galaxy
norbarb said:
Try to save your data and factory reset. If that not going to work i would consider to ODIN clean firmware on phone. You can find firmware in one of my post about updates
Clicking from Edge of Galaxy
Click to expand...
Click to collapse
Hello,
Yes, I did factory resets multiple time but still the situation is same.
I am new to XDA and it's hard for me to navigate or find posts. Can you please share the link where I can get information about the solution you mentioned.
Thanks,
P.D.
hatemarshmallow said:
Hello,
Yes, I did factory resets multiple time but still the situation is same.
I am new to XDA and it's hard for me to navigate or find posts. Can you please share the link where I can get information about the solution you mentioned.
Thanks,
P.D.
Click to expand...
Click to collapse
here is EPH5 ODIN firmware : https://forum.xda-developers.com/no...hmellow-att-server-link-installation-t3407308
norbarb said:
here is EPH5 ODIN firmware : https://forum.xda-developers.com/no...hmellow-att-server-link-installation-t3407308
Click to expand...
Click to collapse
I will check this out tonight and will let you know if that helped.
norbarb said:
here is EPH5 ODIN firmware : https://forum.xda-developers.com/no...hmellow-att-server-link-installation-t3407308
Click to expand...
Click to collapse
I have downloaded 2 files.
1) S2EPK4 to S2EPK5 --This I will transfer to phone sd card, correct?
2) ODIN FILES to get back to EPH5 and latest ODIN
ODIN -- This will be for PC when I connect the phone, correct?
Let me know if I need any more files to download.
All these information is not making much sense to me at this stage but I guess as I work on this I will have grasp of the process.
hatemarshmallow said:
I have downloaded 2 files.
1) S2EPK4 to S2EPK5 --This I will transfer to phone sd card, correct?
2) ODIN FILES to get back to EPH5 and latest ODIN
ODIN -- This will be for PC when I connect the phone, correct?
Let me know if I need any more files to download.
All these information is not making much sense to me at this stage but I guess as I work on this I will have grasp of the process.
Click to expand...
Click to collapse
You are correct about files , but you need more files. EPH5 TO EPK1, EPK1 TO EPK2, EPK2 TO EPK3, EPK3 TO EPK4. All of this files are install from sd-card except EPH5
Clicking from Edge of Galaxy
Clicking from Edge of Galaxy
norbarb said:
You are correct about files , but you need more files. EPH5 TO EPK1, EPK1 TO EPK2, EPK2 TO EPK3, EPK3 TO EPK4. All of this files are install from sd-card except EPH5
Clicking from Edge of Galaxy
Clicking from Edge of Galaxy
Click to expand...
Click to collapse
I was traveling last week. BTW here is the update. I switched off the phone to get it in to recovery mode... it's dead since then... It doesn't turn on.. I tried various usb cables, wall adapters, soft reset, new batteries etc... nothing is working to turn the phone on. Does this mean the phone is gone?
Any update on the device? What was happening before this happened? Turning off the device to put it into recovery shouldn't have created a catastrophic event that would have killed the phone...
Are you in the states? Are you close to a Best Buy? Many Best Buy stores have a "Samsung Experience Center" that can help you with your phone... They can apply latest updates, and do some minor technical troubleshooting...
What happens if you put a different battery in, and plug in a charger? Are you using a Samsung charger? Leave it for a few minutes, is there any indication that it is charging?
Did you, per chance, use one of those portable rechargers? Those can wreak havoc on your battery, as well as the phone's built in charging circuits...
What is the status of the device?
Shanghai.Knight said:
Any update on the device? What was happening before this happened? Turning off the device to put it into recovery shouldn't have created a catastrophic event that would have killed the phone...
Are you in the states? Are you close to a Best Buy? Many Best Buy stores have a "Samsung Experience Center" that can help you with your phone... They can apply latest updates, and do some minor technical troubleshooting...
What happens if you put a different battery in, and plug in a charger? Are you using a Samsung charger? Leave it for a few minutes, is there any indication that it is charging?
Did you, per chance, use one of those portable rechargers? Those can wreak havoc on your battery, as well as the phone's built in charging circuits...
What is the status of the device?
Click to expand...
Click to collapse
Hello,
Before it turned off I have downloaded the zip file for update on sd card and then tried to put it in recovery mode to perform the steps but it never turned on. I travel alot so don't get much time to spend to do all these technical things so temporarily switched my old BB Q10. I did try different batteries, chargers, plugging it in various laptops. It's dead dude. I kind of hate ATT and Samsung now. They push an update on us which ruins the phone and then they ask if I have insurance! I mean like dude are you out of your head?
Yes I am states. I did not know that Best Buy do some troubleshooting, I will take phone to them as soon as I can and will update if they were able to solve the issue. Thanks for that suggestion.
If you didn't get into recovery mode, you didn't even start the update. Sounds like the phone died before anything happened. Just trying to put it into recovery doesn't start the update at all...
Sorry about the phone. Hope it's something simple...
For instance, I had a sticky button that made the down volume stop working. A Qtip and rubbing alcohol solved that...
Hope your phone resurrects some how.
hatemarshmallow said:
Hello,
Before it turned off I have downloaded the zip file for update on sd card and then tried to put it in recovery mode to perform the steps but it never turned on. I travel alot so don't get much time to spend to do all these technical things so temporarily switched my old BB Q10. I did try different batteries, chargers, plugging it in various laptops. It's dead dude. I kind of hate ATT and Samsung now. They push an update on us which ruins the phone and then they ask if I have insurance! I mean like dude are you out of your head?
Yes I am states. I did not know that Best Buy do some troubleshooting, I will take phone to them as soon as I can and will update if they were able to solve the issue. Thanks for that suggestion.
Click to expand...
Click to collapse
It may be too late, but put the phone in the freezer with the battery out for 5 minutes. pull it out and put the battery in and try to turn it on. Works for me, but now everytime I need to restart my phone, it has to go into a freezer.
piluvr said:
It may be too late, but put the phone in the freezer with the battery out for 5 minutes. pull it out and put the battery in and try to turn it on. Works for me, but now everytime I need to restart my phone, it has to go into a freezer.
Click to expand...
Click to collapse
Just got active here again. I did try the freezer thing but didn't work for me. I have found a process where one uses USB JIG to put phones in download mode (if the battery is fully charged or charged enough) if the phone buttons are non responsive. I haveordered it from ebay. Let's hope it works. Once in download mode, I will try to flash it. Looking for the best procedure to flash it. not a technical guy.