Related
Hi guys,
I am using a Sony Ericsson Xperia Arc and am having a lot of trouble with the device constantly crashing and rebooting.
when this first happened these are the steps i took.
i completely wiped the device (factory reset, wipe dalvik cache, wipe cache partition, format system)
i then flashed Baseband 77 using flashtool
i then flashed fxp149 using flashtool
i then flashed Baseband 77 libs using CWM
i then flashed AOKP JB M1-R1 ROM using CWM
i then flashed gapps using CWM
i the reloaded all apps from the market and not applied any backups and yet it still rebooted all the time.
Since then i have tried using
Fusion 3.8
Fusion 3.9
Fusion 4.0
FXP 148
FXP 150
Stock Kernel inside ROM .zip file.
I have also tried putting it back to Baseband 72 but it made no difference.
None of these make any difference to my issue and yet before i had the issue, I had used all of these kernels except FXP 150 and they all worked fine with no issues at all.
I then decided to go all the way back to stock firmware as it is out of the box.
so I used flashtool and flashed LT18i_4.1.B.0.587_(1254-2716).ftf
I reloaded my applications and monitored the device only to see that by the next day, the problem had returned.
I am now at the end of my tether and do not know what else i can possibly do to figure out the issue.
the device has not been dropped or damaged in any way so there is no reason for a hardware fault.
i desperately NEED this device to be working as i use it on a daily basis for my business and cannot live with out it.
IF THERE IS ANYONE OUT THERE THAT COULD PLEASE PLEASE PLEASE HELP I WOULD BE FOREVER IN YOUR DEBT!!!!!!!
i also have a logcat that i was running in the background when one of the reboots happened
not sure if that can tell anyone anything but i have it if it does
First flash stock kernel (587), after flash the rom compatible with kernel. Remember full wipe before
have you tried not to restore your apps? Maybe one of them causes the problem. I'd try to stick with the clean (stock) rom an check if it still reboots. If it does I guess your device is ready for ebay
Could be a loose battery, try a bit of paper between the battery and the cover and see if that helps.
XperienceD said:
Could be a loose battery, try a bit of paper between the battery and the cover and see if that helps.
Click to expand...
Click to collapse
thanks for the suggestion but my battery is not loose and i have tried your method but with the same results.
weaselmetal said:
have you tried not to restore your apps? Maybe one of them causes the problem. I'd try to stick with the clean (stock) rom an check if it still reboots. If it does I guess your device is ready for ebay
Click to expand...
Click to collapse
hmmm i thought if that were the case there would be others experiencing it too.
i will take your idea and post results.
thank you very much
rod555 said:
First flash stock kernel (587), after flash the rom compatible with kernel. Remember full wipe before
Click to expand...
Click to collapse
i tried this, unfortunately i had the same issues occurring.
thank you for your suggestion
Needs a trip to the Service Centre then by the sounds of it.
XperienceD said:
Needs a trip to the Service Centre then by the sounds of it.
Click to expand...
Click to collapse
yes i am starting to think that may be my next move
will i have an issue with getting it repaired since i have unlocked my bootloader, flashed different kernels and roms and rooted the device?
if so, is there any way i can get it back to official "out of the box" state?
Flash a stock ftf and get the bootloader relocked. Having it rooted is fine
Sent from my lt18 using xda premium
tangosierra_ said:
Flash a stock ftf and get the bootloader relocked. Having it rooted is fine
Sent from my lt18 using xda premium
Click to expand...
Click to collapse
any chance you could explain a little about how to do that or possibly provide links to downloads or pages of instructions?
plastic_prophet said:
any chance you could explain a little about how to do that or possibly provide links to downloads or pages of instructions?
Click to expand...
Click to collapse
Here:- http://forum.xda-developers.com/showthread.php?t=1324703
Sent from my LT15i using xda premium
i have come across something quite interesting.
i had someone look at the logcat i had running live when i had a reboot and it showed that the last thing to function before the reboot was wifi scanning. they suggested i try turning off wifi and running the live logcat again to see if any reboots occured.
it has now been just over 48 hours and i have not had a reboot at all. i know is because my terminal session is still running the live logcat.
is there anyone that could suggest why this may be happening?
i mean, i know its wifi that is causing the problem, but would that be a hardware issue that could be fixed under warranty? or something else?
any suggestions are appreciated as always
plastic_prophet said:
i have come across something quite interesting.
i had someone look at the logcat i had running live when i had a reboot and it showed that the last thing to function before the reboot was wifi scanning. they suggested i try turning off wifi and running the live logcat again to see if any reboots occured.
it has now been just over 48 hours and i have not had a reboot at all. i know is because my terminal session is still running the live logcat.
is there anyone that could suggest why this may be happening?
i mean, i know its wifi that is causing the problem, but would that be a hardware issue that could be fixed under warranty? or something else?
any suggestions are appreciated as always
Click to expand...
Click to collapse
i don't think i can help, i just wanna say that i had (have) the same problem. I said had/have because probably I still have the issue, but i don't notice it that often. Before, I had my phone set to ask for pin code, but now I have removed it to avoid being unreachable if a restart occurs. I have raised the issue long time ago, but really didn't find any answer. Other ppl had same problem with their phone (look at the thread i started about this issue http://forum.xda-developers.com/showthread.php?t=1765537)
I also have HTC desire in daily use with CM7.2, that also reboots quite often. So I don't think the phones are broken. More likely it's kenel or rom or app issue, or some combination of those.
If you can tell me how to monitor things, I can do it on both phones, maybe we will figure out what's going on.
lalek said:
i don't think i can help, i just wanna say that i had (have) the same problem. I said had/have because probably I still have the issue, but i don't notice it that often. Before, I had my phone set to ask for pin code, but now I have removed it to avoid being unreachable if a restart occurs. I have raised the issue long time ago, but really didn't find any answer. Other ppl had same problem with their phone (look at the thread i started about this issue http://forum.xda-developers.com/showthread.php?t=1765537)
I also have HTC desire in daily use with CM7.2, that also reboots quite often. So I don't think the phones are broken. More likely it's kenel or rom or app issue, or some combination of those.
If you can tell me how to monitor things, I can do it on both phones, maybe we will figure out what's going on.
Click to expand...
Click to collapse
if you open a terminal session and type:
su
cd sdcard
logcat >> logcat.txt
it will create a .txt file and put the live logcat info into it.
you need to leave the terminal running in the background to make sure it continues to update
then when you see a reboot just get the logcat.txt file from the sd card and open it in wordpad or something. (notepad doesnt display properly)
have a look at the last thing that happened before the reboot and see what it tells you
mine had info about wifi scanning and showed that it had seen ssids
next step was to turn wifi off to see if the problem stayed or resolved.
good luck!! id love to hear how it goes
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
I first rooted and flashed a KANG JUGGERNAUT ROM 2 years ago, back when I first got my phone.
Just two days ago, a friend recommended flashing CM10 cause it's nearly up-to-date and stuff.
Was instructed to flash CM10 then GAPPS and wipe after; did so, boot loop.
Told me that I was supposed to wipe beforehand? Wish I known, still had soft bricks / boot loops.
Kept restoring and re-flashing; came to a point CWM became super slow, kept hanging when trying to restore/wipe.
Then I chose to flash ROM again, this time it kept rebooting/looping into installation process, hang, fail then rebooting to continue this cycle.
Told friend about it, said he'd look at it when he came over; cause my Odin kept crashing for some unknown reason.
He couldn't get it to stop boot looping so he offered to take back home where he said he had all the stuff he had installed on his PC/MAC.
After awhile he said it wouldn't boot anymore, hard brick.
Afterward he returned it to me, I confirmed a hard brick according to what I have searched/researched online.
Plugging into the USB gives me a connection beep but hitting the power button, gives a disconnect beep? So unable to go into download mode.
I have looked around and found a couple of possible solutions: JTAGGING and USB JIGGING
I'm not sure but I kept seeing a lot of testimony that jigging it wouldn't work on a hard brick phone, can anyone confirm this?
Not sure what JTAG is but apparently is the sure-fire way to get the device in working condition again; is this something I can do by myself?
I see the costs range from $50-100 but I'm not sure if I can afford that right now/tight pockets/strapped4cash/whatever as an unemployed student from LIF with other crazy stuff to deal with.
Worst come to worst, I will probably opt for this JTAG thing.
EDIT: I have this QHSUSB_DLOAD shown in the device manager as I connected the dead device; while searching/looking around, someone said it was fixable but it wasn't in the T989 thread so I'm unsure.
Is this really fixable? and if so, what would this exactly permit me to do after?
Any insight as what options I have? I really would like to get this resolved ASAP.
Thank you for reading; I am also located in NYC, if any locals can help.
Jtag
Hey buddy i recent hard bricked mine last month got it back today PM this guy tomy1986.nt only charged 25$ and had it back in 7 days sucker working good now hes in texas only cost me 5.80$ shipped from Phx Az hope that helps Sounds like a defint hard brick!!!
JahJahLoO said:
I first rooted and flashed a KANG JUGGERNAUT ROM 2 years ago, back when I first got my phone.
Just two days ago, a friend recommended flashing CM10 cause it's nearly up-to-date and stuff.
Was instructed to flash CM10 then GAPPS and wipe after; did so, boot loop.
Told me that I was supposed to wipe beforehand? Wish I known, still had soft bricks / boot loops.
Kept restoring and re-flashing; came to a point CWM became super slow, kept hanging when trying to restore/wipe.
Then I chose to flash ROM again, this time it kept rebooting/looping into installation process, hang, fail then rebooting to continue this cycle.
Told friend about it, said he'd look at it when he came over; cause my Odin kept crashing for some unknown reason.
He couldn't get it to stop boot looping so he offered to take back home where he said he had all the stuff he had installed on his PC/MAC.
After awhile he said it wouldn't boot anymore, hard brick.
Afterward he returned it to me, I confirmed a hard brick according to what I have searched/researched online.
Plugging into the USB gives me a connection beep but hitting the power button, gives a disconnect beep? So unable to go into download mode.
I have looked around and found a couple of possible solutions: JTAGGING and USB JIGGING
I'm not sure but I kept seeing a lot of testimony that jigging it wouldn't work on a hard brick phone, can anyone confirm this?
Not sure what JTAG is but apparently is the sure-fire way to get the device in working condition again; is this something I can do by myself?
I see the costs range from $50-100 but I'm not sure if I can afford that right now/tight pockets/strapped4cash/whatever as an unemployed student from LIF with other crazy stuff to deal with.
Worst come to worst, I will probably opt for this JTAG thing.
EDIT: I have this QHSUSB_DLOAD shown in the device manager as I connected the dead device; while searching/looking around, someone said it was fixable but it wasn't in the T989 thread so I'm unsure.
Is this really fixable? and if so, what would this exactly permit me to do after?
Any insight as what options I have? I really would like to get this resolved ASAP.
Thank you for reading; I am also located in NYC, if any locals can help.
Click to expand...
Click to collapse
Got your phone this morning, an it is already fixed. Restore it to stock rom 4.1.2 everything is ready to go.
Will ship it tomorrow morning.
Thanks choosing my service.
Praise!
tomy1986.nt said:
Got your phone this morning, an it is already fixed. Restore it to stock rom 4.1.2 everything is ready to go.
Will ship it tomorrow morning.
Thanks choosing my service.
Click to expand...
Click to collapse
All praise Tomy for his swift and kind work in helping a poor Samaritan. Thoust good deed shant go unnoticed.
How do I prevent these bricks? Just bricked mine and getting it back from JTAG
I'M BATMAN
-DarkKnight- said:
How do I prevent these bricks? Just bricked mine and getting it back from JTAG
I'M BATMAN
Click to expand...
Click to collapse
Good morning guys
tomy1986.nt said:
Good morning guys
Click to expand...
Click to collapse
How would I prevent my device from getting bricked?
I'M BATMAN
-DarkKnight- said:
How would I prevent my device from getting bricked?
I'M BATMAN
Click to expand...
Click to collapse
Do not flash modified Rom. :laugh:
tomy1986.nt said:
Do not flash modified Rom. :laugh:
Click to expand...
Click to collapse
What do you mean "modified"
Would I have to compare the md5 or what?
I'M BATMAN
-DarkKnight- said:
How would I prevent my device from getting bricked?
I'M BATMAN
Click to expand...
Click to collapse
-DarkKnight- said:
What do you mean "modified"
Would I have to compare the md5 or what?
I'M BATMAN
Click to expand...
Click to collapse
Alway flash phone with Stock rom.
tomy1986.nt said:
Alway flash phone with Stock rom.
Click to expand...
Click to collapse
What about custom ROMs like cm10.1 or JediMindTrick?
I'M BATMAN
The note 1 SGH-i717 of Keith_Dallas,TX member has already fixed today give it back only about a hours.
Hi,
Been using an Xperia M since Feb 22, and yesterday I experienced a touchscreen 'crash' for the first time: It seems as if no touch is detected. I panicked and eventually reflashed kernel and reinstalled CM (as per this) - problem solved (but lost data).
Just now the problem happened again and I reflashed kernel only, which fixed it.
I'm a noob, so what's going on here?
1) This is a software problem, right? Since reflashing kernel fixed it.
2) Is this some kind of problem with the CM build I'm using (see link above)
3) Is there anything I can do to prevent this from happening?
Thanks for any help!
Well the same thing happened again. Kernel re-flash did NOT fix it this time.
Does anyone have any idea how to prevent this from happening? And anyone who may be able to explain why this happens?
Thanks for any insights
EDIT: A few reboots later it's fixed again. (just reflashed kernel). The previous times rebooting did NOT help.
in deveoloper options have you set the animations and transistions and durations to 0 ? i found this caused my touchscreen on my old x10 running cm10 to stop working
Sent from my C1905 using XDA Premium 4 mobile app
No I haven't set those options
Ok, so, some updates.
I switched from PecanCM's CM11 build to FreeXperia (311), but the problem still happened, just a few hours back.
Maybe it's just some app that's not playing nice or something, but I have very few apps, and nothing weird, so I don't know what it could be.
Anyway, turns out that if I reboot the phone through Flashtool when the touchscreen is frozen, it FIXES it.
But if I "reboot" by removing and replacing the battery, or through SMS TASKS, this does NOT fix it.
Maybe this is useful to someone out there, and I'll post here if I ever figure out the problem
Well, maybe it's a hardware problem after all...
After about a million reboots, the problem persisted this last time. It even persisted after re-flashing boot, re-flashing ROMs (CM11 / FXP311/312, as well as Sony stock).
Guess it's back to the store...
Unless anyone else has any suggestions??
Thanks in advance.
Sony repaired the phone in 10 days, pretty fast!
They replaced a bunch of components, the touch screen and related stuff, so it seemed.
It's working now. Hopefully I won't have the same problem in 3 weeks.
As a final thought: Whenever the problem was "active" the touch screen also didn't respond in CWM recovery, so maybe that was a giveaway that it was NOT a software problem, but a hardware problem?
Thanks and hopefully I won't be revisiting this thread...
Torious said:
Sony repaired the phone in 10 days, pretty fast!
They replaced a bunch of components, the touch screen and related stuff, so it seemed.
It's working now. Hopefully I won't have the same problem in 3 weeks.
As a final thought: Whenever the problem was "active" the touch screen also didn't respond in CWM recovery, so maybe that was a giveaway that it was NOT a software problem, but a hardware problem?
Thanks and hopefully I won't be revisiting this thread...
Click to expand...
Click to collapse
Just out of curiosity, did they charge extra for the UBL?
This message was brought to you from my Sony Xperia M C1905 using Tapatalk.
Antrikos48 said:
Just out of curiosity, did they charge extra for the UBL?
This message was brought to you from my Sony Xperia M C1905 using Tapatalk.
Click to expand...
Click to collapse
Unlocked bootloader you mean?
I relocked it first. I unlocked with Flashtool and then could easily relock with Flashtool as well.
Anyway I wasn't charged a thing.
Torious said:
Unlocked bootloader you mean?
I relocked it first. I unlocked with Flashtool and then could easily relock with Flashtool as well.
Anyway I wasn't charged a thing.
Click to expand...
Click to collapse
That's great. I thought that because you were giving your IMEI to Sony to unlock (at least with the official method), even if you relocked it they could still check.
This message was brought to you from my Sony Xperia M C1905 using Tapatalk.
Antrikos48 said:
That's great. I thought that because you were giving your IMEI to Sony to unlock (at least with the official method), even if you relocked it they could still check.
This message was brought to you from my Sony Xperia M C1905 using Tapatalk.
Click to expand...
Click to collapse
Yeah I requested the unlock code through the official site so I guess they could have checked it.
But maybe I just never used it
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.