Hi there fellow robot lovers (or killers as it may be) !
Before we start, both identical phones (public mobile zte n762), both rooted, both booting normallish, meaning they get to keyguard screen, apps are starting, messages coming in, etc. Only one is activated, which would be the one with the broken screen, which boots fine, the touch membrane works, it's just the screen only displays pure white light, from total dark to overbright (meaning brighter than full brightness)
What I want from this one is an up to date backup that I might flash on the other one when its softish brick status is resolved.
Then, I can think of hacking the hardware itself, as in changing screen.
Goal for this one is to get a full backup so I can then mess around with it. Or if someone knows that the screen is not dead, since it does light up, I'm all ears on way to play with it. After a backup.
For the little history : I dropped my activated phone while trying to figure out the problem with the other one, to my great dismay and no immediate hilarity I had been running it for more than 4 months with a nasty crack on the screen, and it seems the dropping from a foot high the other night was the shock that sent it over the top.
Now it seems this can also be caused by software glitches ? aka White Screen Of Death
Now, the soft brick phone, which I got for nothing before it was thrown to the garbage (supposedly defective, it was just very barebones, and missing its sdcard)
Now, why do I say very softly bricked ? Well, it works, fully boots, and I sometimes manage to get a glimpse of the running OS "behind" the boot anim when I let if fully boot.
It's running a varianf of the Warp Cream sandwich rom for the n762, called Ice Cream Sandwich 420
It's like the boot anim is looping as an overlay over the running OS. Even managed to get Text+ in the foreground yesterday and chat with a buddy for a while.
Now, why didn't I just wipe it and reinstall ? For one, I thought [ I had no copy of the rom, just a cwm recovery backup once it started acting up.
Mostly, because the challenge in getting it (both phones if it so happens the screen on the other one can be brought back to normal operation) back to glorified PDA status without wiping it, as that's a bit like the good ole, reinstall DOS/Windows/etc. tech support level 1 answer, isn't it ?
So what options exist for soft brick to resume normal activities without wiping the whole thing ?
What could lead to the custom boot anim playing as an overlay to the OS ?
All ears and eyes on your suggestions, shouldn't be that hard for someone who knows, as I have read quite a bit of information that doesn't agree with each other...
anything in italic is edit(s)
Related
Hi everyone. This is a weird thing - I haven't found anyone with a similar issue, either here or with Google-fu.
I successfully rooted my HTC Desire a while ago (S-Off) and was pretty happy with it, the LCARS bootanimation installation also went well. After trying out a lot of apps, finding the best configuration for the phone etc. I decided to format and set up the whole thing again on Monday, to have a clean installation and no more space issues.
Although I went for the CyanogenMod V7.1.0-RC1 this time 'round I somehow doubt that has something to do with it, but who knows. Okay, SD card was set up anew, custom mod got installed, everything went as smoothly as it possibly could. (cool story, bro)
However, after I moved the bootanimation.zip into the system\media folder and rebooted, the animation started, but only at half the size it usually has, in the middle of the screen. I tried another one and it was the same thing. The longer one of the two also broke off in the middle with a brief flash, as if I'd pressed the Power button, then stayed dark until I pressed the Power button twice (turn off/ back on), only then it would show me the pin number display.
Apart from that the phone works perfectly.
It's not an incredibly important issue, just something I find weird and would like to fix, if possible. Does anyone have an idea what could be the source of this?
Doesn't anyone have the slightest idea?
you try flash bootanimation over Android Flasher..
Hi majko11293 - first of all thanks for pointing me to this programm. I'd used it before (worked brilliant with my own custom splash screen), but somehow lost it again.
Anyway, even when flashing it with Android Flasher, the bootanimation stays at half size. The animation itself changes depending on which one I choose, but the size issue remains...
while i was using my phone the screen just started going white...until it was completely white with just a few shadows of what was originally there. turned it off and on...and now some black and white screen.
Is my phone just dead..permanently?
................................................................
i did the camera, volume down power reset....the bootloader writing is very vague.... going to try rsd lite in the morning...
Does anyone know if this sounds like i just physically messed it up or a software problem (as i recall i did reduce the vsel 10 mins before this happened)
----------------------------------------------------------------------
ok so weird .... i left in on bootloaded for a few minutes and then suddenly the screen went normal again and i restarted the phone..all good.....
wt the hell just happened , i am soo confused
-----------------------------------------------------------
and now the same thing just happened again.. all white
I'm not one of the dev experts around here, so don't hold my word on this. If you've got everything backed up (or at least able to back it up now), throw a new (stable) ROM onto it. If the new ROM is acting normally as it is, restore your texts/contacts/etc...and then slowly re-introduce all the apps and tweaks you had on there that may be questionable. Make sure you can isolate the problem to a specific tweak and/or background program that is causing the problem, then get rid of it.
If you pitch on a new ROM and it immediately starts acting screwy (or worse, just buckles over even in the middle of a ROM update*), you've probably got a case of hardware failure (likely due to heat) on your hands. x.x
* - In bootloader/recovery, not the OS of course.
I may not be able to save my settings so im holding of rsd lite for now
But if bootloader mode is randomly shady (theres a grey strip made of smaller vertical lines running down the left hand side of the screen where the bootloader writings are), then does that mean its hardware.
Hoping an expert can tell me if all the customisations, vsel changes etc...can affect the performance on bootloader. because if it can;t then in narrows it down to hardware straight away.
prelim research suggest the flexi ribbon that connect the screen to somthing is loose. Might have to open it up
What was your OC and vsel settings ?
880, 62 vsel,
yh rsd lited it...similar funky screen...white strip going down the middle at bootup...and then green, black white vertical lines once its at the welcome to android screen..prob the colours that make up the lil robot thing. the notification bar is fine though
Time to open it up
IronMit said:
880, 62 vsel
Click to expand...
Click to collapse
Strange, I don't know what is your problem but I think your vsel is too low, I am [email protected]
But I don't know if OC is load in bootloader mod so it's maybe another problem.
I using my Xoom earlier today and after a while I noticed that the display looked a bit strange. On closer inspection/further use, there is *massive* ghosting/burn in (I think).
If I turn the screen off/on, I can actually see through the lockscreen to the homescreen underneath. When I unlock it I can see previous apps burned in there.
If I shut it down and reboot, I can see the homescreen through the bootscreen (which should be completely black excepting the red Moto logo and the ripple effect).
I've only had it for about a month and mostly use it for browsing the web/facebook and reading comics. I could understand gradual burn-in if I was using a certain app really heavily but that isn't the case here. It seems to have gone from fine to completely f**ked in the space of about half an hour.
I guess my question is, is there any chance it's software based and a factory reset will help or do I go back to where I got it and try to get it repaired/replaced under warranty? And if I do take it back, is the fact that I rooted going to cause problems?
*************
After a factory reset (which did nothing) I used OTA RootKeeper to try and unroot before sending it to Motorola (turns out it's only a temp unroot), then used Titanium Backup to restore apps + data and the display returned to normal as suddenly as it broke 0_o
I have no idea what caused the problem and no idea what fixed it but it seems fine now 0_o
After installing Lollipop, everything became unbearably slow. I've tried flashing multiple ROMs, both Lollipop and Kitkat, but everything remains so slow: the actual boot-up process and the ROM itself. Does anybody have any ideas about what can be done about this? In fastboot I see hammerhead D820(H) 32GB; HW version rev_11; Bootloader version HHZ12d, Baseband M8974A-2.0.50.2.22. Lock state is unlocked. Any suggestions will be highly appreciated!
Wipe cache and see if that helps and disable Chrome's integration into the app switcher. Also get rid of Facebook and FB Messenger.
Sent from my Nexus 5 using XDA Free mobile app
Instead of Lollypop try some LSD
Thanks. But it is that slow even before any of these apps are loaded (e.g. after I do a factory reset and flash a new rom). Is it possible that Lollipop did sthg to the hardware? If so, how could I find out? Just to give you an idea about how slow exactly it is: when I am typing 5 letters at normal speed, it takes until the fifth letter before the first letter actually displays on the screen. I should also note that when the screen goes off, I can no longer get it on again without a reboot...
I'm still trying to figure out what this might be. I first thought my problems were similar to those that others have described, but I now think they be different. Here are some of the issues I'm encountering:
when I boot up the phone (whether in kitkat or lollipop), the initial android (animation sequence is already incredibly slow
there are all sorts of strange things happening with my screen. When it goes to sleep in Android, I can not wake it up anymore. When it goes to sleep in recovery, and I push the power button, the screen goes (again after some time) from pitch dark to a slightly 'lit' dark, but it never displays anything, and I have to reboot again to get the info on the screen. Also, the screen is even slow in twrp - when I swipe to do a factory reset, for instance, there is also a noticeable lag.
I have tried with various ROMs (both stock and not); with ART and Dalvik, etc. but none of these changes seem to affect the slow screen issues
Does anybody have any ideas about what the problem might be? I should also add that we had the screen replaced a few months ago - could that have something to do with it?
sdspieg said:
I'm still trying to figure out what this might be. I first thought my problems were similar to those that others have described, but I now think they be different. Here are some of the issues I'm encountering:
when I boot up the phone (whether in kitkat or lollipop), the initial android (animation sequence is already incredibly slow
there are all sorts of strange things happening with my screen. When it goes to sleep in Android, I can not wake it up anymore. When it goes to sleep in recovery, and I push the power button, the screen goes (again after some time) from pitch dark to a slightly 'lit' dark, but it never displays anything, and I have to reboot again to get the info on the screen. Also, the screen is even slow in twrp - when I swipe to do a factory reset, for instance, there is also a noticeable lag.
I have tried with various ROMs (both stock and not); with ART and Dalvik, etc. but none of these changes seem to affect the slow screen issues
Does anybody have any ideas about what the problem might be? I should also add that we had the screen replaced a few months ago - could that have something to do with it?
Click to expand...
Click to collapse
Probably the replacement screen has been reconnected poorly. There's nothing you can do on software side, for me, it's more like a hardware problem.
Searched around, and didn't see this one. Tablet was a refurb, added the keyboard dock, updated to last system asus released, unlocked the bootloader, rooted. System is stock 4.2.1 with Google bloatware frozen and a handful of free apps, nothing particularly exciting (unless you're thrilled by fbreader, etc.).
Occasionally, the screen "rolls up" to a thin area at the top of the screen. A "swat" (light tap) on the top or sides brings it back, which implies the cable is loose or making intermittent contact. Since the site doesn't allow video as attachment, I stuck a badly-shot short 4M FLV video at http://bes.lofcom.com/tf300t/ to explain better the symptoms. Clearly not too worried about the warranty tag at this point, but of course tearing apart any electronic device should only be attempted as a last resort.
Weird thing is, though, is that it never does it during the two boot screens...even when it's acting up, the initial asus screen and the second metallic-logo spinning-balls screen look fine, but at the moment it switches to the PIN screen it'll roll-up, implying a software cause. Which doesn't jive with tapping it to get it back.
So before I get out the chain saw to take it apart (kidding!), I'm wondering if there's anything else I should look at first.