I tried installing stock roms as well as cooked ones. I hard SPL'ed, installed newer radio to no avail. What can I do? It's too slow to be used properly.
When you install the ROMs, make sure you clear storage before, during, and after. If you do not clear the storage you may not completely flash all the old files, causing issues, lock ups, and slowness. Also, when testing new ROMs I make sure that all the CABs are compatible by taking a day or two before installing another one.
I tried to do what you recommended. Downloaded that task29 utility and wiped the phone's internal memory. Then I found a stock 6.1 rom and installed it. It looked like it was installing fine, but right now it's just stuck on a white screen and has been like this for the past 10 minutes or so. I don't know if it's going to go anywhere with this, or if it's stuck for good.
By the way, does anybody know EXACTLY where I can find a real stock 6.1 distribution? I'm asking because the ones I've been finding are named European and for other phone makes. It seems as if they are linked by other people as being the correct ones, but then when you go to download them, they turn out to be for other phones, or 6.5's instead of 6.1's. I didn't think it was going to be so hard just to find a stock 6.1 rom with which my phone initially came.
8gkl said:
I tried to do what you recommended. Downloaded that task29 utility and wiped the phone's internal memory. Then I found a stock 6.1 rom and installed it. It looked like it was installing fine, but right now it's just stuck on a white screen and has been like this for the past 10 minutes or so. I don't know if it's going to go anywhere with this, or if it's stuck for good.
By the way, does anybody know EXACTLY where I can find a real stock 6.1 distribution? I'm asking because the ones I've been finding are named European and for other phone makes. It seems as if they are linked by other people as being the correct ones, but then when you go to download them, they turn out to be for other phones, or 6.5's instead of 6.1's. I didn't think it was going to be so hard just to find a stock 6.1 rom with which my phone initially came.
Click to expand...
Click to collapse
Which model/carrier do you have?
I have a T-Mobile Touch Pro 2
8gkl said:
I have a T-Mobile Touch Pro 2
Click to expand...
Click to collapse
Well as long as you mean the US T-Mobile, the stock 6.1 rom is available HERE
I've tried that stock 6.1 from that thread many times, and it doesn't fully install. It goes through the installation, past the green screen with the windows logo, and then gets stuck on a blank white screen. I've tried many times installing it, and it gets hung on the white screen forever. The curious thing is that some other roms install however. One of the newer Energy roms, as well as the Deepshining one installed fine. The only problem is that everything still is extremely slow to respond. Physical buttons pretty much don't do anything at all.
The bottom four buttons don't light up. Pressing the call and end buttons works, but the home and back buttons don't do anything.
Also, pressing the power button doesn't really shut it off either.
8gkl said:
I've tried that stock 6.1 from that thread many times, and it doesn't fully install. It goes through the installation, past the green screen with the windows logo, and then gets stuck on a blank white screen. I've tried many times installing it, and it gets hung on the white screen forever. The curious thing is that some other roms install however. One of the newer Energy roms, as well as the Deepshining one installed fine. The only problem is that everything still is extremely slow to respond. Physical buttons pretty much don't do anything at all.
The bottom four buttons don't light up. Pressing the call and end buttons works, but the home and back buttons don't do anything.
Also, pressing the power button doesn't really shut it off either.
Click to expand...
Click to collapse
Have you tried re-downloading the t-mobile 6.1 ROM? I guarantee you that's the stock ROM, and from a T-mobile 6.1. There's been numerous members that have gotten it to work, so the issue isn't with the ROM itself...
I agree that the issue is probably not the rom, because that stock rom has been used by lots of people. But the fact remains that this stock rom doesn't install on my phone, and certain custom roms do.
My phone is generally fcuked, I don't have insurance, and there's pretty much nothing I could do. There is signs of water damage under the screen, though the touch screen works fine, and the wet seal is pink..
Not trying to troll, just an advice.
I just sold my TP2 and bought an N1.
TP2 is just that - slow and unreliable. After 6 years of WinMo phones, Android feels like waking up from a nightmare. Dump that crap and get a real PDA.
DarkDvr said:
Not trying to troll, just an advice.
I just sold my TP2 and bought an N1.
TP2 is just that - slow and unreliable. After 6 years of WinMo phones, Android feels like waking up from a nightmare. Dump that crap and get a real PDA.
Click to expand...
Click to collapse
But even the N1 isn't waterproof...so I don't think even that fine piece of hardware would have prevented the issues here
I have an android phone myself, the HTC G1 (Dream). I agree that android, though I can't really see all of it's guts like I can on a winmo phone, is more user friendly and stable. I've owned the G1 since the beginning of android's career, ever since that first Android OS was out. It was quite horrible at that time. It came through quite a bit now, as well in terms of all the different roms available.
I don't want to throw this TP2 away though. At this point I'm thinking of the things that I can do to get anything out of it. Apparently the phone insurance can only be purchased within 14 days of the phone purchase, so I'm late there. I just can't think of anything I can do. I'll know better next time to get insurance right away.
Related
Hi guys/gals.
Got a bit of a problem, and not sure whether it's the actual phone at fault, or the software...
Had the phone for about 4 months now, and have noticed this to get worse and worse... I'm pretty sure it's happened before on the stock rom, but can't remember whether it happened before I unlocked the phone to be able to install custom roms (not security/sim unlock, just a standard unlock to allow custom roms).
Anyway, this is basically how my phone's life has been: I got phone, used standard htc rom. Then, the spl unlocker came out, and I installed that about 2 weeks after it came out (waited just to check people had no probs ). Then, I installed one of the energy roms as my first rom. Installed a few other roms in between, then an updated energy rom etc. Then, I installed the official wwe 6.5 rom. Then, I went back to the energy rom. Currently, I'm using the 26th October (iirc) rom. As I said, not sure whether it happened when I had the official 6.1 rom on (spl locked), but I'm quite sure it happened while I had the official 6.5 rom on (spl unlocked). It has happened tho with all different custom rom images I've used...
Basically, what I've noticed, is that sometimes I'm replying to a text message or email, click reply, pull out keyboard, and it seems to cause the phone to power off. Pressing the power button starts it again. Sometimes, I've not been doing anything, and it's turned itself off. Sometimes, I've dropped the phone (even only a slight drop of about 1cm), and it's caused it to power off.
I've also had times where it's turned itself off, and nothing's allowed it to come back on, other than taking the battery out the back of the phone and re-adding the battery. Then, pressing the power button powers the phone on.
Is this a problem with the roms, a problem with the spl unlocker, or a problem with my phone itself? Am I best contacting htc?
Any advice welcome, as it's very annoying coming to use the phone, and finding it's turned itself off, or when I go to reply, I open the keyboard, and then have to wait for it to load up and power it on to reply!!!
Many thanks in advance
Hi.
It's very anoying for you..
I suppose you should try to (re)install the latest Hard SPL, and to install the latest Radio too. After it, make a hard reset. Next, flash with your favorite ROM And come back here to say us what happens.
See you, and good luck for these manips.
lovelldr said:
Hi guys/gals.
Basically, what I've noticed, is that sometimes I'm replying to a text message or email, click reply, pull out keyboard, and it seems to cause the phone to power off. Pressing the power button starts it again. Sometimes, I've not been doing anything, and it's turned itself off. Sometimes, I've dropped the phone (even only a slight drop of about 1cm), and it's caused it to power off.
Click to expand...
Click to collapse
I've had this same trouble. It would happen to me when I would finish typing a text message and hit the send key and slide the keyboard close at the same time. I only really noticed it when I was running the energyroms, however I can not say for sure that they are the root cause of it, as I have waited till the message was sent before closing my keyboard ever since.
Well, since I wrote this message this morning, it's happened at least twice. Both times whilst the phone has been in my pocket...
I will try installing the latest hard spl. Think the radio I have is the latest already. Will also try a different ROM just in case it is energy roms which is causing it (but am pretty sure it happened with other roms).
Thanks for those suggestions, will let you know any outcomes
try Valkyrie. ^^
Well, I went through and installed the new hardspl (altho not sure if any different to the one I had, how would I tell?!). I then installed the image from josh, which had the latest radio and rphone.dll (or whatever the file is called) matched to it. However, doesn't appear to have made any difference. Still doing it...
Does anyone else suffer much with it, and it's just a design fault? Or should I contact htc? As surely it should just turn off when in your pocket?!
No-one else? I'm just the only person. Guess I best drop htc an email then...
my att Rhodium /tilt2 does it too
Ive been dealing with this for awhile now also.... , also return my phone for new one but this one does the same thing my radio is 4.47.25.24 and i have 1.6beta rom by josh build 21882.5.073 .
I have this new T-Mobile Touch Pro 2. I currently have the Stock European ROM (6.5) on it. Before that, I was using the TMO 6.5 version. My problem is that the phone randomly freezes/dies/turns itself off while sitting idle. And every time it happens, I either have to soft reset it or take the battery out and put it back in to turn it back on. Simply pressing the power button doesn't do anything. Funny thing is that this phone is a replacement that was sent to me by T-Mobile because my first device was doing the same thing (which I had for about a month). T-Mobile tech support was just as lost as me. Can anyone here help me?
I have the exact same problem! Have you found a solution or at least learned the cause of the problem ?
Phone turns off ramdomly
Hi
I have the same problem the phone is shutting down ramdomly without any warning and i have to use the power button to turn it on again
any solution guys ??
Did you task29 the rhodium before flashing the new rom?
Sometimes flashing the new rom doesn't clear the memory properly leaving traces of old files to foul up the operation. Flashing task29 before flashing a new rom will stop this.
After you flash task29 there will be NO os on the rhodium. You will need to pull the battery, Put it into bootloader and then flash new rom from PC or use sd card method.
Cheers...
I have exactly the same problem, 2-3 times a day, I need to soft reset it. The phone was working well until I moved from 6.1 (original) to 6.5; I believe the new radio has issues. Any recommendation, flashing the radio does not solve the problem.
I used to have 1-3 SODs a day. Now I have only one SOD a month. My solution was to remove compact framework 3.5 and that weathersolution where you can add new cities. By the way; I upgraded to WM 6.5. Before the upgrade I had no SODs.
Sorry to bring up an old topic, but I recently acquired a Touch Pro 2 (RHOD100, original HTC model) and having exact the same issue. There's no saying when it's happening, but always during an action. Had it when pressing the End key after a call, when pulling the Usb cable from the device, and during other things too.
Hardware seems fine, battery is firmly in place and contacts are fine, and clean.
Having factory WM 6.5 Rom on it. And like mentioned before, I also do have Compact Framework 3.5 installed since it's required by some of my software.
Anyone ever found a solution that's confirmed to solve the issue?
I'm sorry for bumping up an old thread but after doing a search this was the first one that was listed which isn't 'That old'. I have just bought one of these phones, brand new, from factory. It comes with windows 6.5 and runs the OS version for the phone is - 5.2.21887 (21887.5.0.86) The phone seems to randomly just shut off without notice and to be able to turn it back on again to use it, I've got to take the battery out and put it back in again, then it will be able to turn back on. When the phone does enter the state of completely turning itself off. I have noticed that my notification LED light does flash green, I don't know why it does this. But if anyone has some help for me to sort this problem out and enable me to use my phone perfectly then that would be great!
Yet again, sorry for bumping up an oldish thread
Hi,
Right in the middle of use, my ATT Tilt 2 went to a basic, dead screen with red, green, blue, and white bars that says Rhod300 32m SS-BC, etc.
The operating system seems have gone down--it won't respond to anything. Hard reset produces the same results.
Can I flash a cooked or official Rom back onto this? I think activesynch is needed for a normal flash and of course I can't use active synch with the phone in this condition.
I think probably what I need is an original ROM install. Is this possible with a normal Windows 7 PC and a dead phone?
I have so many Windows Mobile programs and peripherals that I am trying to avoid going to Windows Phone at all costs--at least until they have basic stuff like file systems, a way to port over notes, etc. Also need a hard keyboard.
Right now using an older Fuze, which works, but is slower, worse screen, smaller, and lacks some of the features I like.
Thanks for your help.
You sound like you're in the bootloader mode. Tri-color screen.
You can flash from USB or from SD at that screen. I'd recommend trying to flash a stock ROM - as it flashes everything. Assuming that works, hopefully you can flash back whatever ROM you were on.
The phone isn't dead if you're at the tri-color screen. It should say 'serial' at the bottom - when you plug in your USB cable, it should say 'USB' and install some drivers. Then with the RUU software that comes with every ROM, you should be able to flash it.
Phone won't reboot--stuck on tricolored boot screen
Hi,
Thanks so much for replying. I appreciate you pros helping us novices.
Just after I posted the first note, I pulled the battery and hit the power button, it rebooted, and everything was still there in the OS--working fine. But whenever the device had to be rebooted, I would have the same problem of it getting stuck in the boot screen. After that, for the last several days once in awhile, randomly, it would finally reboot from the boot screen after I pulled the battery and hit the power button. The rest of the time (about 5/1) it would just sit there in the boot screen no matter what I did. The "Serial"/"USB" thing would change when I plugged it in, but that's all.
Thought it was the OS, so at a lucky moment where the "pull battery, hit power button" strategy actually worked, I installed the latest official HTC/ATT Rom--it's the next to last one issued that ends in .4.
It was gorgeous and I got all excited--started installing stuff thinking my problem was solved.
Had to reboot to install some programs--now it is stuck again on the boot screen. Tried 30x again--no luck with the "pull battery/hit power button"
strategy. Sometime it would flash a white screen really quickly saying something like "Can't read image!" before going into permanent boot screen. The boot screen will switch from "Serial" to "USB" if you connect it to the computer. So, the problem doesn't seem to be in the OS--rather, in the ability of the device to "read" the OS from the boot screen.
I would be grateful if you or anyone else may know what's going on here, and any ideas on how to fix it. Is there any manual way to get it to read the OS from the boot screen when that's not happening?
I have two guesses (both of which may be wrong):
1. It may be something in the hardware is just worn out and is less and less able to read the Rom--any ROM. I got the phone new off Amazon for a profit of $50 ($.01 cost plus a refund for an older phone) in the summer of 2010 when it was already outdated. and WP was replacing WM. I've certainly gotten my money's worth after 18 months!
Of course we now know that a brand new ROM has the same problem as the older one--which suggests to me it's in the hardware. I'm sure the new OS and the stuff I installed is still there on the phone, but something it appears is not reading something in order to allow the boot up.
2. I have a squirrely free program called Rax Reset (from Windows Mobile Marketplace) that does a software-based hard or soft reboot from inside the OS. The very last time the device went down and didn't come back up, I had used that program to soft reset it. Might have been a big mistake. Could this program be causing the problem? If so, just one reboot would allow me to get rid of it or even hard reset to remove everything but the new OS--but can't get it to boot.
If it turns out the phone is just worn out, I've certainly gotten my money's worth.
I still love WM even with all its problems--and especially the newer Sense version. If this one is shot, I'm thinking about just buying a new Touch Pro2 on Ebay to avoid all of the sacrifices and backwards steps involved with Windows Phone.
Thanks for any help anyone can provide.
Phil Butin
Why are you crossposting? I read this EXACT same post in a thread just below this, in the same section. That's pretty low.. Crossposting across forums isn't welcome, crossposting within forums IN THE SAME SECTION is definitely not welcome.
Don't do it again.
Sorry, just trying to get help
Sorry, just trying to get help, not that familiar with the rules.
I searched on "bootloader" and found a thread (wrote a comment there too), but it's old....
Here is the thread. It doesn't really provide any solution.
HomeArrow
Legacy & Low Activity DevicesArrow
HTC Rhodium: Touch Pro2, Tilt 2Arrow
Touch Pro2, Tilt 2 GeneralArrow
issues with bootloader.
Either way, whether you know the rules or not - why would you think copying and pasting the exact same words in the exact same forum help you any more...
Anyhoo, have you tried the usual? Flash stock? Sometimes I've heard you have to flash several times, I never really understood that logic tho.
I'll try to reinstall the HTC/ATT Sense OS again. I guess you're saying active synch doesn't need to be working in order to do that. I'm at work now--have to wait until i get home. Nothing to lose at this point.
But I'm seriously wondering whether the problem is the OS install or whether there is something in the device that is supposed to read the ROM and start the bootup that is just wearing out.
Thanks.
"No Image File"
The quick little flash of white screen has "No image file" in blue letters--goes by so fast you can hardly see it.
[email protected] said:
The quick little flash of white screen has "No image file" in blue letters--goes by so fast you can hardly see it.
Click to expand...
Click to collapse
That error message is 'normal'. Basically the phone checks the SD card for a file labeled "RHODIMG.nbh". If said file exists, it will flash from it. If no file exists, or no SD present - it continues loading bootloader and should say "Serial" at the bottom. This indicates that it's ready to be flashed. If you plug in your USB cable, it will install some drivers and then it should change to "USB" at the bottom instead of "Serial".
Now you should be ready to flash from a normal RUU. I would recommend flashing STOCK, because this flashes everything.
It might also be good to note a lot of people have experienced something similar - the phone getting "stuck" in bootloader mode, and only occasionally making it to WinMo. I'd guess it's failing hardware in some way shape or form, as none of my RHOD's or RAPH's have ever done this.
Good News--at least for now
Good news--I hooked it up to the computer with the USB cable for awhile and the Windows 7 computer did set up some drivers. For some reason after I disconnected it I reset it, and the reboot worked. Then I immediately uninstalled the squirrely reset program and removed it.
Everything I installed yesterday is working fine--I have soft reset it about 5 times now and each time it has rebooted. So I think maybe I'm back in business. Too soon to tell--but we will pray and keep our fingers crossed.
Thanks so much for your time and help. I don't know how to use the thanks meter but I would have if I could have.
[email protected] said:
Thanks so much for your time and help. I don't know how to use the thanks meter but I would have if I could have.
Click to expand...
Click to collapse
You're welcome. Basically if I or someone else posts something helpful, click the "Thanks" button under that post.
15 hours later, Tilt 2 is still working fine on the newly installed Sense OS. I have rebooted freely (using the stylus button on the side) since removing the program "Rax Reset," and everything seems to be going well. I'm keeping my fingers crossed, and will end my contributions to this thread with a warning about using "Rax Reset."
Thanks to all.
Hi all,
This is The premise:
My note 10.1 has been a good companion for an year and an half now, and i always kept it in good shape.
However, since december the battery just stopped charging as it used to.
To simply put it, it just took a lot to charge (as if the tablet didn't receive enough energy) and the battery drained at insane speed.
Not knowing what to do, and having a void warranty (i know, sucks, but with the vanilla p600 i coulnd't even open the pdfs i use to study, so it was useless to me ) I just had to bring it to a local repairman who is affiliated with samsung. They immediately ruled out the possibility of it being the battery, and they said it was probably something related to the simple connector, that they changed with an original one.
Now the real trouble:
After they gave it back to me, the tablet can't go 5 minutes without the screen flickering like crazy and then rebooting.
I tried different ROMS, thinking it could have been something related to the Ios. CM12, Hyperrom p600, the vanilla Rom that was originally in my tablet and so on.
The big problem is that this unnerving flickering and rebooting is not tied to the ROM, as it happens even when i'm just using TWRP (version 2.6.1.1).
To be more precise: the tablet in recovery mode is fine and nothing happens if i do nothing with it; however the screen starts flickering and the tablet reboots the moment I attempt to flash something, or even everytime I do a factory reset.
Now the situation has worsened: to simply put it, I can't no longer access the tablet with any rom, be it vanilla (touchwiz) or android-stock based.
What could possibly be the reason behind this problem? I guess it has nothing to do with software issues (i have the vanilla 4.4.2 installed right now, but it can't even finish the setup).
Is there any advice you can give me?
To be more precise, the flickering is not like there is some intermitting bright light or anything: it's like the tablet's screen turns off and on very quickly for 30 seconds, and then just reboots.
After a lot of tries, i managed to install the unofficial cm by temasek for note 10.1 2015, but the problem keeps popping up with every rom I tried.
Regarding the kernel I should have the default one, as i don't recall ever changing it or modifying anything about it, but I could check if some kind soul can tell me how.
The problem happens quicker and more frequently when the tablet is put to stress (for example, when i'm flashing something or when a Gapp is updating/intalling).
I thank you in advance
edelmiro11 said:
Hi all,
This is The premise:
My note 10.1 has been a good companion for an year and an half now, and i always kept it in good shape.
However, since december the battery just stopped charging as it used to.
To simply put it, it just took a lot to charge (as if the tablet didn't receive enough energy) and the battery drained at insane speed.
Not knowing what to do, and having a void warranty (i know, sucks, but with the vanilla p600 i coulnd't even open the pdfs i use to study, so it was useless to me ) I just had to bring it to a local repairman who is affiliated with samsung. They immediately ruled out the possibility of it being the battery, and they said it was probably something related to the simple connector, that they changed with an original one.
Now the real trouble:
After they gave it back to me, the tablet can't go 5 minutes without the screen flickering like crazy and then rebooting.
I tried different ROMS, thinking it could have been something related to the Ios. CM12, Hyperrom p600, the vanilla Rom that was originally in my tablet and so on.
The big problem is that this unnerving flickering and rebooting is not tied to the ROM, as it happens even when i'm just using TWRP (version 2.6.1.1).
To be more precise: the tablet in recovery mode is fine and nothing happens if i do nothing with it; however the screen starts flickering and the tablet reboots the moment I attempt to flash something, or even everytime I do a factory reset.
Now the situation has worsened: to simply put it, I can't no longer access the tablet with any rom, be it vanilla (touchwiz) or android-stock based.
What could possibly be the reason behind this problem? I guess it has nothing to do with software issues (i have the vanilla 4.4.2 installed right now, but it can't even finish the setup).
Is there any advice you can give me?
To be more precise, the flickering is not like there is some intermitting bright light or anything: it's like the tablet's screen turns off and on very quickly for 30 seconds, and then just reboots.
After a lot of tries, i managed to install the unofficial cm by temasek for note 10.1 2015, but the problem keeps popping up with every rom I tried.
Regarding the kernel I should have the default one, as i don't recall ever changing it or modifying anything about it, but I could check if some kind soul can tell me how.
The problem happens quicker and more frequently when the tablet is put to stress (for example, when i'm flashing something or when a Gapp is updating/intalling).
I thank you in advance
Click to expand...
Click to collapse
Sounds like a digitizer issue to me. A.K.A. Screen/graphics issue.
LiquidSmooth maintainer for d2usc/vzw & p600
Thank your for your answer:
could you be more precise? Bercause the touch screen and the lcd all look fine, and they are as crisp and reactive as ever.
the thing is that it looks like it goes in idle constantly and very, very quickly turns back on
Update:
so a local technician took a look at it for me and the hardware (lcd digitizer) seems totally fine, so i don't know if that is the problem.
Today somehow worked perfectly fine: no strange flickering, battery charging fine for once...
and then i tried to open the google camera
the camera crashed instantly and the hellish flickering started as it never stopped.
Should i upload a video? I feel like "flickering" is not an appropriate description
[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