Related
Hello everybody,
I seem to have a major problem with my XDA Orbit: Not only it shuts down with no apparent reason so that I have to reset it, but it shows sometimes the dreaded "white screen of death" - from now on "WHISOD". The screen all of the sudden slowly goes white and sometimes shows dark vertical bands. After that - if I am lucky - I can reset the device, however a couple of times I already had to hard reset end even reflash it.
I have already checked software and plugin problems and would rather say that it seems to be a hardware problem. Any ideas out there. They would be highly appreciated.
Best regards,
Smack
i had the same problem and as at now my phone is dead becuase i did not flash it with the original rom. look for the rom it came with and flash it to the phone ,like how u first got the phone or u will loos ur phone very soon
I am not at all sure if it has to do with the ROM. I have tried different ROMs to check the error but it appeared with all of them. However the next time I will try again with the latest official ROM.
Thanks for the comment and your help. BTW Did you send your Orbit in for repair?
Regards,
Smack
Hi, do you use the uspl before every new rom install? Try it.
I have the same problem, my htc3300 is almost dead I think. No way I can even turn it on, allways end in the windows screen, and it was because I didn`t use the uspl before last rom install.
Give it a try, and let us know.
See ya.
Thanks. No flashing problem. I have flashed a couple of devices (always unlocking them before ;-) )and have had no problems whatsoever.
The problem I mentioned is not connected to any earlier flashing. The device works a couple of hours perfectly. However suddenly it starts to behave like crazy.
Now to your problem: If you can get into boot loader modus you will most probably be able to unlock your item. Search for uspl and download it. Then get into boot loader mode (press voice recorder button and power button while resetting the device) and you will get a three colored screen. Then connect the USB cable. You will see "usb" in small fonts on the screen of the device. Now you can run uspl. With a little luck the device starts again. However you can flash it again with a fresh ROM the same way (after unlocking it). This may (!) work.
Regards,
Smack
Hello,
I have the same problem, I already hard reset end even reflash my p3300 many times with different ROM.
I even tried running it for some time with and without the micro SD, ending with the same result: the screen of death.
Any ideas , tips, anyone ?
Thanks,
Roundi
Ok, I tried the following: Just take the battery out for six or seven hours and insert it again. The device seems to run smoother. Will keep you posted. Tell me if it works out for you.
Regards,
Smack
Ok, just removed the battery, I will leave till tomorrow morning.
I will keep you updated.
Thanks,
Roundi.
I have same problem here - though mine is the second phone and the fifth motherboard I've had. HTC just don't seem to able to fix it. I'm now trying to get a refund.
Hi, Jem.
Yes that's something I have thought about too. Did you you use the original ROM? However right now the system seems to be more stable. I have had only one blank screen after removing the battery (and one shut down).
Regards,
Smack
I have just put in the battery and switched on the phone after almost 24h.
So far so good.... I will try to use it for a while and will let you know.
Regards,
Roundi
Had the same problem again, when using Mortplayer. I have Mortplayer installed on the SD card. Could it be that the problems arise, when there is heavy usage of the SD Card?
Any ideas are welcome.
Regards,
Smack
Again it went SOD shortly after turning it on. I didn't launch any applications.
I am stuck here.....
I'm using an R800x, unlocked bootloader, rooted, stock 2.3.2. I was playing a game on FPSE, turned the screen off, put the phone in my pocket, came back, and the phone was stuck on the android boot logo. Dozens of battery pulls later, it restarted (literally as I was about to post here). Later on however, the same thing happened, and I'm still trying to get my phone to restart (so I'm just going to post question this time). I'm assuming it's FPSE at this point, and plan on uninstalling the app, which is disappointing because I've been having trouble with PSXperia. Has anybody had any similar issues and if so, does anybody have any possible fixes? At the very least, I'm wondering if there are any recommendations (i.e. should I try and restore the phone to factory settings or something? flash stock?). I have the most recent version of FPSE; I bought it last night.
I'm pretty new to the Xperia scene after having used the HTC Eris for the past two years. I've been doing research and trying to learn how to use the sdk and adb, but it's going slow -- there aren't any barebones tutorials for this sort of thing that I can find; most authors assume too much foreknowledge on the part of the reader which I unfortunately do not have.
UPDATE: I've counted over a hundred battery pulls and this time it doesn't seem to be working at all. I'm going to try restoring my phone with flashtool because if this doesn't count as a soft brick, I don't know what does. Surprised FPSE caused it though.
Hello Forum,
seems that my DHD has an irreparable error.
But i've still a little hope that maybe someone of you guys out there can point me into the right direction to repair the phone again.
What happened:
on December, 20. for no apparent reason the Display started flickering approximately 2 cm from the top.
The upper Part (the first 2 cm from the top of Display) was showing the normal Picture, on the lower Part the Picture was flickering at irregular time intervals, but the touch gestures were still working without any Problems.
Setup at that Time:
- Latest 4ext Touch Recovery
- Latest MIUI.us Rom by bliind
- Custom DPI set to '190' (with ROM Toolbox)
- Max CPU Speed set to 1200 Mhz (with Set CPU)
(Had this setup working fine without any issues for approx. last 2 Months...)
Last change i did before the error occured: Set Custom Boot Animation with Rom Toolbox
The Flickering started not immediatly after setting the new boot Animation but i think 2 days and some reboots later...
Actions that i've already tried to solve the Problem:
1. Shut down the Phone, pull out the Battery, wait some Minutes, reboot the phone.
-> The flickering was gone and the Display looked normal after reboot.
2. After some time I took the Phone out of my pocket and the flickering was there again like before.
Tried to set DPI back to original value '240'
reboot the Phone
-> The Flickering still was there and it seemed to me that the responsiveness of the touch was slightly slower than normal.
3. Reboot into Recovery
Nandroid Backup all Partitions to SD-Card
wipe all partitions except SD-Card
new, totally clean flash of latest MIUI.us Rom by bliind
Reboot the phone
-> The flickering was gone; responsiveness of the screen normal as it was always before.
4. restore all apps; put the phone on the charger over night. everything worked fine again.
on the next Morning this strange flickering was there again; the Touchscreen was very slow responsive in the flickering area
Managed once more to reboot into recovery, but the flickering was now even in the Recovery and on the boot screen.
-> The Touch got more and more unresponsive.
Could no more start a new ROM flash out of Recovery.
5. Tried to access the phone via aahk tool and restored last stock ROM
-> After Reboot the DHD vibrates (like it usually does for startup)
the screen shows a bunch of black and white Stripes that chnge their Color when the Boot Animation should show up,
and later again when the lockscreen should appear.
It makes the boot jingle and i can send Commands via adb.
but Touch commands doesnt work, (tried to put in the Pin blind, but it shows no reaction)
Stupid, but I can't change it: my Warranty and the extra Insurance that i purchased for the DHD ended just 2 weeks before on 6. December.
6. Disassembled the whole phone with Help of you tube disassembling Guide, carefully cleaned all contacts and assembled it again.
-> nothing changed; same behavior like before disassembling.
What can I do? Any ideas except of small rasping and stirring into the soup? :crying:
Can it be only the display? Maybe the Graphic Chip?
Any other ideas?
thank you for reading this all and i appreciate any suggestion that might give my DHD a new spirit of life
Greetings from Cologne
I know it's not what you want to hear, but that sounds like a graphics or display hardware problem...
bananagranola said:
I know it's not what you want to hear, but that sounds like a graphics or display hardware problem...
Click to expand...
Click to collapse
Thanks for your reply!
That was the same what I thougt after disassembling and cleaning with no result.
Cause it seems to me that the Display is still working, but the Signal that's coming in is broken.
I alsready supposed that the Graphic engine is broken.
Just had a little Hope that someone might had the same Problem and got it solved,
before I start practice for mobile phone throwing competition...
i suggest another ROM JB used to cause my DHD flickering (earliear versions)
My DHD was with same problem 1 year a go, and that usually happen when i played games like Angrybirds or Asphalt, or when the device temperature was high.
I was worry at that time, thinking that the device was gone.
Take the same solutions that you had (except disassemble the phone) but they're only temporary.
By that time i decide root the device and install a new rom, (nothing to loose had i think) and Revolution HD was my choice.
After that my DHD didn't flick any more.
I didn't ever know what was the origin of that flickering but for me, that was the big solution.
I'm using Viper Venom 1.2.3 for now, and still with no flickering insues.
So, my advice for you is... give a try to other rom's and kernels, maybe you resolve your insue has i did.
Good luck with that.
Sent from my HTC Desire HD using xda app-developers app
Thanks for you Answers guys,
the Problem i have is, that my DHD does show only sripes even if I try to boot into Recovery, I can't see anything and am not able to start a flash process...
cause i have installed 4ext touch recovery i need the screen to wipe and flash a new ROM.
But i will try to flash an CWM - Recovery through ADB and then to start the flash Process blind by tapping the buttons...
let's see what will happen. There's nothing to loose...
For now, cause I was sitting without a mobile phone at all, I've ordered a cheep one from Amazon... - Huawei U8510 (Ideos X3) -
And oh WONDER!!!: I've got a fully functioning phone with CyanogenMod 7.2 and all the stuff i use my phone for is working without any Probs..
And the whole thing has 2 years of warranty at a cost of € 80,-
only the Display for my HTC would cost € 40,-
so I'm thinking of selling the broken phone on ebay and let anyone try to repair it who is able to....
but I will give it a try to flash another ROM.
Already downloaded the JellyTime R30...
Hello unbeteiligter,
seems that my DHD has nearly the same issues, but with some extra problems.
It seems to be broken since today morning. I wiped the phone and restored the backup I made the afternoon before, and then the first vertical stripes occured. I wiped it and flashed the same rom (CodefireX 4.2.1) again. Same issues. Now I tryed to flash a GingerBread Strock Rom. Even the same issues, and even more shocking is that this problem also occurs in the bootloader, recovery, splashscreen and bootanimation.
Stupid situation, today my Warranty ended.
What can I do? Previously I tougth this is a software problem, but now I think it might be a hardware issue.
Thanks in advance!
daniel_DHD said:
Hello unbeteiligter,
seems that my DHD has nearly the same issues, but with some extra problems.
[...] and even more shocking is that this problem also occurs in the bootloader, recovery, splashscreen and bootanimation.
Click to expand...
Click to collapse
Seems to be the same like my DHD. But for me it ended up 2 Weeks after end of Warranty!
daniel_DHD said:
Stupid situation, today my Warranty ended.
Click to expand...
Click to collapse
The T-Mobile Customer Support told me, that they would have accepted the case as Warranty, if my DHD had ended up during the first week after End of Warranty. Don't know where you bought yours, but maybe there's a small chance for you to get Warranty Support through their obligingness.
If I were you I would try this...
daniel_DHD said:
What can I do? Previously I tougth this is a software problem, but now I think it might be a hardware issue.
Click to expand...
Click to collapse
If your dealer don't accept your Warranty Call, I can't give you much Hope... Sorry for you...
... would imagine you should look for a new phone...
That's what I did....
Similar problem
I have also got a similar problem. Had my phone for two years and have also just hit the same problem. Flashed a new ROM, everything was working fine, then all of a sudden top half of the screen is displayed correctly, the bottom half is always flickering. This occurs in the bootloader as well. Anyone would think that HTC decided to make sure the phone only works for two years and a few weeks after the warranty expires to make sure it experiences problems.
[Q] LS980-Cloudy G3 ROM- TWRP installed&accessible- [email protected] Android is Updating screen
Hello everyone,
I would like to say first of all to the community, thank you for SHARING KNOWLEDGE. That is the key to everyone's success.
Now down to the gritty. My, now, I guess, mess of a LS980. For starters, the phone was running I would say very well considering my abuse. Big overclocks, gaming hardcore, and pushing the storage space hard. I performed a very easy and simple rooting and recovery program installation. If I remember properly, it all started with an app/.apk that sparked my interest with making the phone mine, was Autorec? (red roundish logo?) In some time I decided to install my first aftermarket ROM. I chose and installed without any issues , Cloudys G3 ROM. I cannot however remember the version number. It is by no means recent. I think I installed it last September so maybe 1.0 or 1.2 (sorry so much bad luck with stuff recently) TWRP version 2.7.0.0 is my recovery, and its functional. Unfortunately I do NOT have my apps backed up. I have no space. (just managed to get about 7GB on this PC to try to back them up but there is not external back up option, UNLESS you are OTG cable equipped I am not )
Now, I think, (this has been the state of the phone for about 3 weeks now) this all started to go south when I saw there was a Dorimanx OTA app in the play store. I used his Kernel for as long as I have had the G3 ROM installed. With no problems. So I figure this would be easier for me than button mashing trying to get into recovery mode without popping my screen out the front. LOL Upon using the app, I was informed of an update, I read the included information, and generally knew the deal. I allowed the app to download what it needed and restart and install like a good little computer. And this is where it gets a little grey for me in terms of order and symptoms. I remember checking the status of the install and it read failed! I looked into the reason why, and I was just plain full of junk. I then uninstalled painfully a bunch of rarely if that, used apps and gained back about 2.2GB of space. I ran Dorimanxs app again and let it do its thing and reboot. And again it reported fail! I looked into it more and noticed there were newer Kernels than available on his inter-web. Alpha versions. I located them on my device and rebooted into TWRP mode and selected , then flashed his 10.4.1 Kernel. Everything went fine. Phone reboots, the LG logo is no longer animated, and takes a bit longer to actually boot into a GUI. But it was, luckily.
So now, the phone would be a usable thing for about 3 minutes tops, before a power off, to a reboot. Which at first I didnt notice to be a boot loop. My battery surprisingly went from full to about 6% in no more than 15-20 minutes. I noticed the battery was getting warm like I was running the CPUs maxed under a serious load for a good half hour. Around the range to make someone pull it out their pocket wondering wth? So after the next reboot, power cycle, I jumped back into TWRP mode, and dug around for what I thought was the culprit, Xposed. I was having the worst time with my phone after a major Xposed framework error. I picked up my phone one day and out of the blue the xda framework was telling me that there were so many errors with it and my apps that ran fine, not being installed or activated. Upon looking into it, it was removed from the phone. I belive the order was , stable, 2.5/ 2.6, then I tried the beta 2.7. and thats the version that eventually , either broke, or uninstalled, I think, during those frequent Crashes! I tried to install the previous versions, even going back to the versions that came out last year like 2.4 . But none would install. And the phone grew more unstable in terms of its cooperation with its software. My normal apps and games worked fine. The phone worked the same, the music player, but there were apps that only can work with xposed that I utilize constantly, that were kaput. So I left the phone off. For a while. I had/have no time and really no resources to research and rescue a sunken ship. I come back about two weeks to it and I take a look around in the phones storage and hunt for any kind of recovery and disabler. I found xposed's disabler and flashed it. Same luck as before. About 3 minutes on, then dump.
I dig some more and found a ccc71 back up folder with some hearty backups that I didn't know were still there (no wonder I was always loosing space) and found another xposed installer.zip . I figured well , it didn't make any sense trying to disable something that wasnt enabled in the first place. (thats why I walk away and come back . fresh mind to tackle what stumps me) So I flashed the installed zip and reboot. Same thing, but now it started to loop around one minute. I power down. Found the recovery.zip that was saved on the beater PC and adb pushed it over the the phone. Im not good enough to adb install it. So TWRP'd it and rebooted, and d'oh! Now we just have the motionless LG ball, but flashing blue and green LED. And after about 2 minutes it would black screen, but be on. Not hung or anything. I connected to the PC, it never finds the right stuff but I used adb to verify state. And it said device. It still could communicate and push. I had it dump its debug, surprise! as it flashes that crap as fast as it can up the screen. But Im a PC guy so it was a fun, pause/break over and over till I found something useful. I saw some things that I could recognize like, failed starts, and longer than normal (for a speedy experience) function or call times, but nothing that slapped me with a red flag.
And that ended that nights attempts to fix thanks to the slowest no ram having box I was using to try to learn how to have the debug save to a .txt file on my PC so I could take a good look at the results.
Upon reading forum after forum, I came to something that looked promising, telling me that, that particular boot issue was due to the wrong radio being installed. So I hunted, and hunted, and laaaaaged my arse off and finally found it. Great I thought. Powered up ten or twenty times, finally get into TWRP, tried to flash it. BBBBBAAAAAANNNNT! nope. Downloaded another copy of the file and tried it again. No luck. ( I must say not until roaming around in these forums tonight did anyone bother to mention that you dont flash that radio. You instead have to inject it via LGFlashTool, which I have used before, and its a pain in the butt.
But before I go any farther, make anymore mistakes. I need some help.. I would really LOVE to be able to flash this , slap that, curse its name then hug it and get her working, without having to ditch my 492 apps. If I would have to say goodbye to happy times, I would like to say good riddance to ugly and annoying G3 ROM. I like not flat UI. My phone was depressing me every time I had to do any navigating around inside it. So I would love to go back to KK Stock LG ROM if push came to shove. But if possible I would just like to "repair, and regain access into the phones GUI system". So I could backup my apps. And eventually labor back to OEM Kitkat.
I apologize for the length of the post. But I just dont see the point of ping ponging with partial exchanges of information. I hope I have made my situation clear, and someone knows of someway, I can get my GUI/phone working again. Thanks to all in advance.
"a non functional smartphone, is an oxymoron"
Upgrade twrp to the blastagator last and dirty flash the same version of cloudy g3. And backup everything on the cloud. Mega give you a lot of free space.
_____________________________________Read more write less and be smart
strangely enough
siggey said:
Upgrade twrp to the blastagator last and dirty flash the same version of cloudy g3. And backup everything on the cloud. Mega give you a lot of free space.
_____________________________________Read more write less and be smart
Click to expand...
Click to collapse
strange thing,
just about 5 minutes ago, the phone, which I left on sitting at the LG screen by accident yesterday after posting the above, changed screens and presented me with the Launcher selection screen.
I immediately noticed that it looked wrong. Like if the resolution was way off. Like an old low res screen, very dull, sort of blurred looking.
I figured what the heck and tapped the screen and it of course did not immediately respond. It took its sweet time , about 30 seconds to show a change. The menu disappeared and a error message along the lines of , android system UI has crashed.
That is not the message verbatim, it was gone to fast for me to take it all in. And now its sitting at the blank powered on and repeating blue/green LED.
I havent done as you suggested yet. I kept getting results from Norway and other places and didnt understand a thing. But I found a TWRP update from Dorimanx, there was a link to it. And now I have to find my version of the OS. And to be clear, were you suggesting doing a re install, basically a file overwrite? And if so, when doing something like that, do you wipe the Dalvik cache ? Or do you just "dirty flash" it?
Thank you ,
I think that your screen is overheated. Never let the phone in bootloop for long time, it can destroy the screen.
About the cache, is better to clean it, but if I remember well the rom installer alredy do this.
_____________________________________Read more write less and be smart
Hello,
New to the forum, at least posting have been lurking and reading for years, but this will be my first post.
Mi 10T Pro, stuck in bootloop. I have been trying to get it going again and have been having no luck, so I decided it is time to turn to the pros for some help.
Symptoms:
Bootloops 1 or 2 times to the MIUI logo, then boots to the recovery menu
Not possible to turn of completely, bootloops until battery drains completely
Able to get to the fastboot menu
What I have tried:
I had a suspicion that it was a problem with the power button, so i replaced the ribbon but no improvement (Unless new one is bad also?)
Replaced Battery, no improvements
Tried all the button press combinations to try and do hard reboot and so on
About Device:
Software version: Unknown as the phone broke a long time ago, got a replacement and the phone has been sitting in the drawer...
Phone was never rooted or unlocked in any other way
The phone is open and I could unplug battery or try a new ribbon for the power button (I have a new one on hand)
What I would like to achieve:
Save the data that is on the phone.... This is the main thing I would like to do as there is precious pictures of my young kids and so on....
Get the phone working and use it as an emergency device
Options I think are still available in order of how I would like to attempt them:
Do a software recovery, by installing a stock rom, example: (
)
I don't know what version of rom to download as I don't know what version the phone was on
I don't know if this will work since the bootloader has never been unlocked
Anything else possible before next step?
Reset through the reset menu. and cry over all the lost data (
All suggestions are welcome.
Thank you!
this phone is notorious for needing to be reballed after a few years of use. its a trash phone. join any mi 10T groups in facebook and youll see countless users who had to pay specialist technicians to reball their CPU and Memory chips and even then, they still fail after a few weeks/months.
Thank you for your answer ongkal. So you don't think its worth to try to overwrite the loader? I don't want to have to reball if its a software issue, but will if it comes down to it.
Mainly just want to get the files out, went back to samsung after first phone with xiaomi...
I was just looking at the reball videos on youtube and most of the phones are completely dead, mine still turns on but straight into bootloop. Besides they say it might be due to gaming, which that phone has not seen