i just want to lay down and have a tantrum like a 4 year old.
I flashed cm 12.0 on my wifes z1c, wich had cm11 before that. Clean install, total wipe. No problems.
But i lost root, and fastboot wasnt working properly. But cm recovery worked fine. But i could not get anything to work.
So the phone has been working fine, but i changed the theme on the phone, nothing else, and now it reboots constantly, as soon as i get to the password login.
I HATE this phone from the bottom of my heart, i will splitt it in half with my axe soon enough
when the phone still was stock, everything was ****, the camera never worked, it took YEARS before sony released an update with a working camera. Same problem in cm, if i remember properly, this was sonys fault.
when i finally get a stable cm12 release on it, i have constant wakelocks, and i cant find why becouse im missing root.
and now, the f/&ing thing won´t start.
Can i possibly save this phone in some easy way? I will not spend hours on this phone anymore, then it will get the AXE and i will get a new phone from another brand, Sonys lockdown have only been an headache for years.
i cant get fastboot to work, i cant get into recovery, i cant get into the phone, it won´t work with adb, it just sits there and restarts
Related
Has anyone has a similar problem to this or any ideas how to troubleshoot?
I've had my lovely 1X since launch. Soon after I rooted her and then had her run CM nightlies until the past week when I decided I wanted to revert to stock for a while
This went swimmingly; I locked, installed the RUU then a slew of updates and last night the phone was happy, stable, making and receiving calls. I plugged her in as normal before I went to bed.
Got up today, unplugged her and almost immediately she crashes and reboots. Continually getting to the first screen, able to unlock sometimes and then goes black and reboots or just freezes and needs resetting.
So I figure, it's software, right?
I unlock her bootloader again, flash CWR 5.8.4.0 again, flash the boot.img from this JB rom and then the rom itself, then 4.2 gapps.
Everything fine. While plugged in.
Unplug; reboot cycle again
Not entirely sure what to do with her now other than try a bunch of other roms. A problem that's consistent across roms/recoveries/boot images, locked and unlocked though...
Anyone have any ideas, please?
I suppose you did a full wipe every time you changed the ROM? Don't be so sure it's only software... Could be a hardware, too.
[email protected]|-|oR said:
I suppose you did a full wipe every time you changed the ROM? Don't be so sure it's only software... Could be a hardware, too.
Click to expand...
Click to collapse
I did wipe of course.
And if it happens across roms, lock/unlock etc. I probably IS hardware. Just want to be as sure as possible.
Hi all. My finicky T989 is stuck at the Android 4G screen and will not boot past it. Some background on the phone, about a year ago it was dropped in water. Immediately place in rice and after a couple of days it worked fine, with a few odd quirks. Initially the camera LED stayed on all the time, so i didn't use the phone for a couple pf months and when I went back to it, it worked fine. It doesn't like any roms other than TouchWiz, CM or AOKP versions give me all sorts of errors when running, normally I cannot access any of the phones memory.
So.....on to my current issue. The phone has been running fine, but last week told me the headphones were plugged in when they were not. I rebooted to see if it would fix the issue, but the phone is stuck on the Android 4G screen. I can access recovery (TWRP) and download mode, I have reflashed the installed ROM, which is a stock rom titled "UVMC6_HERCULES_TR_STOCK_-IQ_RIPPL-H20" and the phone still sticks at the 4G screen.
I have a backup, but it's a couple of months old. This is my wifes phone, so the lost apps are no big deal, she doesn't use too many to begin with. The big loss are the text messages. Since I can still access recovery and download mode, is there any way to pull the messages from there? My TWRP version is 2.6.0.0. I've tried to backup the data portion of my current rom, to save the messages, but it fails.
twism50 said:
Hi all. My finicky T989 is stuck at the Android 4G screen and will not boot past it. Some background on the phone, about a year ago it was dropped in water. Immediately place in rice and after a couple of days it worked fine, with a few odd quirks. Initially the camera LED stayed on all the time, so i didn't use the phone for a couple pf months and when I went back to it, it worked fine. It doesn't like any roms other than TouchWiz, CM or AOKP versions give me all sorts of errors when running, normally I cannot access any of the phones memory.
So.....on to my current issue. The phone has been running fine, but last week told me the headphones were plugged in when they were not. I rebooted to see if it would fix the issue, but the phone is stuck on the Android 4G screen. I can access recovery (TWRP) and download mode, I have reflashed the installed ROM, which is a stock rom titled "UVMC6_HERCULES_TR_STOCK_-IQ_RIPPL-H20" and the phone still sticks at the 4G screen.
I have a backup, but it's a couple of months old. This is my wifes phone, so the lost apps are no big deal, she doesn't use too many to begin with. The big loss are the text messages. Since I can still access recovery and download mode, is there any way to pull the messages from there? My TWRP version is 2.6.0.0. I've tried to backup the data portion of my current rom, to save the messages, but it fails.
Click to expand...
Click to collapse
It looks like its stored in /data/data/com.android.providers.telephony/databases/mmssms.db
I just tested TWRP's Advanced / File manager on my t889 and i was able to copy it to my external SD
Hope that helps ya out man. If so, dont forget to hit thanks
http://minhdanh2002.blogspot.com/2012/02/raw-access-to-sms-database-on-android.html
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
twism50 said:
Hi all. My finicky T989 is stuck at the Android 4G screen and will not boot past it. Some background on the phone, about a year ago it was dropped in water. Immediately place in rice and after a couple of days it worked fine, with a few odd quirks. Initially the camera LED stayed on all the time, so i didn't use the phone for a couple pf months and when I went back to it, it worked fine. It doesn't like any roms other than TouchWiz, CM or AOKP versions give me all sorts of errors when running, normally I cannot access any of the phones memory.
So.....on to my current issue. The phone has been running fine, but last week told me the headphones were plugged in when they were not. I rebooted to see if it would fix the issue, but the phone is stuck on the Android 4G screen. I can access recovery (TWRP) and download mode, I have reflashed the installed ROM, which is a stock rom titled "UVMC6_HERCULES_TR_STOCK_-IQ_RIPPL-H20" and the phone still sticks at the 4G screen.
I have a backup, but it's a couple of months old. This is my wifes phone, so the lost apps are no big deal, she doesn't use too many to begin with. The big loss are the text messages. Since I can still access recovery and download mode, is there any way to pull the messages from there? My TWRP version is 2.6.0.0. I've tried to backup the data portion of my current rom, to recover the messages, but it fails.
Click to expand...
Click to collapse
Hey! How was it going on finally? Did you try pyraxiate's suggestion?
If it works for you please let me know coz I don't want to try the complicated method that turns out not applicable.
so here's the deal
i've been using my One X for a year or two now, half of the time with cyanogenmod on it, the other with Paranoid Android
but one day, the launcher crashed.
I rebooted it, thinking it was a temporary problem, and everything went fine for a few hours
after which multiple apps started crashing, then the launcher again.
I rebooted it again, hoping the problem would magically vanish, but my phone wouldn't boot, it'd stay on the bootloader screen
for a while now if I stood in the Phone app i'd be fine until the end of the day
since then, every time I install a ROM on my phone, it would go fine for a few hours, even a day or two, but then the problems come back, though I haven't been stuck in the bootloader since
i've tried formatting the SD card, i've tried restoring my phone from a clockworkmod backup and i've tried installing over 10 ROMs now, both sense-based and AOSP
HELP, PLEASE, I DON'T KNOW WHAT TO DO ANYMORE
D851 here, When ever i switched from cloudy 2.5 to blisspop 4.0 and after wiping everything i flashed a various of radios bootstacks and etc to make it boot after many failed attempts to boot ( it boots up but after 4 or so seconds after the lg logo the screen turns black and doesnt turn back on until after i pull out the battery) it worked after i flashed the rom WITHOUT a custom kernel so naturally i booted up just fine and thought maybe now i set up everything on my phone and tweaks i should go back and flash a custom kernel i used to use (777 r16) but then it gave me the problem i faced before the black screen after the lg logo no kernal would work. THEN another problem arised similar to the freezing on the black screen randomly during a usage thru my day the phones screen would be unresponsive animations but touch wouldnt work and i know its not my screen cause when i flash back to cloudy it works fine the freezing happens at least every 5 mins. someone halp?
i know this thread is kinds old...
but i have this same issue too... I found if I switch batteries the problem isn't as bad... but, then it becomes bad again. Its weird. Before I swapped batteries I couldn't even login with my google account, after a fresh flash. then after I swapped batteries (gf has same phone) I was able to get through to the end and setup the phone. But, then an hour later it started happening again....
OP, did you find a solution?
warrior420 said:
i know this thread is kinds old...
but i have this same issue too... I found if I switch batteries the problem isn't as bad... but, then it becomes bad again. Its weird. Before I swapped batteries I couldn't even login with my google account, after a fresh flash. then after I swapped batteries (gf has same phone) I was able to get through to the end and setup the phone. But, then an hour later it started happening again....
OP, did you find a solution?
Click to expand...
Click to collapse
i actaully did i think one of the problems was maybe flashing over the same kernel? see what happened was after i gave up flashing the kernel i just flashed without it and to my surprise the build actually came with the kernel pre-installed...shocker and so i had no need to flash over the kernel that i wants because the maker of g3 tmo blisspop already had it in his build and it boots up fine( DISCLAIMER: i cant say this about other roms because the only one i actually tested and wanted was blisspop)
thelgog said:
i actaully did i think one of the problems was maybe flashing over the same kernel? see what happened was after i gave up flashing the kernel i just flashed without it and to my surprise the build actually came with the kernel pre-installed...shocker and so i had no need to flash over the kernel that i wants because the maker of g3 tmo blisspop already had it in his build and it boots up fine( DISCLAIMER: i cant say this about other roms because the only one i actually tested and wanted was blisspop)
Click to expand...
Click to collapse
Okay.
Well, when I was flashing I never flashed a kernel.
Ill be getting a brand new Anker Battery in the mail today. Ill report my findings.
I ended up going to a stock based rom and the issue never happened. So I stuck with it. Ill have to do some testing later and ill let you know how the battery works.
It's not the battery
I downgraded my T-Mo G3 since I couldn't root it with LP on it. Went back to 4.4.2., rooted it, TWRP'd it, and installed the latest CM12 Nightly, Gapps, SU, etc.
As long as the sim card was OUT the installation was great on wifi only, As soon as I put it in it shut off right after, or during boot up. Take the sim out and it works. And yes, the only way to get back into recovery was pulling the battery and doing the key press to recovery. Mystified.
If I find out anything, I'll post it here.
I'd say do a complete return to stock, upgrade via LG Mobile Support tool all the way to 20G, see how it works stock for a while. Then root ( http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197 using the first method) and see what happens.
Hello everyone. Since the Title has character limit im gonna have to explain myself here better.
Ive had my HTC One M8 for 4 years now. Pretty much since it came out in 2013. I installed ARHD back in 2014 and its been working just fine ever since. A couple of months ago i decided to go back to 45.0. Everything went smooth and everything works just fine.
But a week ago the phone decided to just go woopdido and it wouldnt open up any apps in Playstore although i could still see them. So i tried to restart it and when i did it got stuck at the HTC Logo. I tried to restart it a few times but it kept getting stuck. I was super confused due to the reason that i havent really done anything with my phone besides since the day i installed ARHD 45.0. I got desperate so i reinstalled it but this time with 53.1 and that went fine too except for one fishy thing and that was that i remember before when installing ARHD, when it got 30% it wouldnt take 2-3 minutes for it to finally start installing the ROM. It would take a couple of seconds for it to start right away and be done.
After installing 53.1 phone worked just as fine except for the fact that it was slower than it has ever been before. Which was also weird. Either way. After a couple of hours of it working, setting up every app i needed i restarted it and again it was stuck at the HTC Logo. Welp i guess..
So after that crap i went back to 45.0 again. It went good and all except it keeps getting stuck at 30% for a while but whatever. Going back to 45.0 though didnt help. Keeps repeating the same crap after a while. After a restart when having the phone doing nothing for hours gets it stuck at HTC Logo again. I literally cannot do anything with it atm and i have no clue how to go further from here as i have not had this before.
The HTC One M8 is rooted. S-Off everything you really need. The current TWRP version i have is 3.1.1.0.
Your firmware may be outdated. I would think it would be, as you said you haven't installed anything to the phone since 2014.
This (old firmware) alone would play havoc with the current ROMs. And also not play well with current TWRP, which may explain why going back to ARHD 45 is still resulting in problems.
What goes it day for OS number on the bootloader screen? If blank, what are the hboot and radio numbers?
The original issue could have just be due to some damage or corruption to the OS. It happens.
Also, the phone was released in 2014, not 2013.
redpoint73 said:
Your firmware may be outdated. I would think it would be, as you said you haven't installed anything to the phone since 2014.
This (old firmware) alone would play havoc with the current ROMs. And also not play well with current TWRP, which may explain why going back to ARHD 45 is still resulting in problems.
What goes it day for OS number on the bootloader screen? If blank, what are the hboot and radio numbers?
The original issue could have just be due to some damage or corruption to the OS. It happens.
Also, the phone was released in 2014, not 2013.
Click to expand...
Click to collapse
It was released in 2014? Welp why did i think it was 2013? Either way.
You missunderstood me but its all good because its on me. I was meant to say that i havent touched anything since i installed 45.0 a couple of months ago right. The firmware is fine and all for the current version i have. It was for 53.1 too.
And out of the blue it just got stuck on the HTC Logo. I tried something and it was updating the SuperSU which actually was the reason why it got stuck on the HTC Logo. I installed 2.79 and now it boots just fine and the phone is back on speed again. Apparently 2.82 has issues which is the version i assume it tried to update to through both TWRP and Playstore.
sp3tan said:
You missunderstood me but its all good because its on me. I was meant to say that i havent touched anything since i installed 45.0 a couple of months ago right .
Click to expand...
Click to collapse
Ah, I do see now that you stated you installed ARDH 45 a couple months ago. There is a lot of info there, so I missed that part.
Glad to hear you sorted it out. It's unusual to see a simple SuperSU update cause such a chain of event; but s#it happens I suppose.
redpoint73 said:
Ah, I do see now that you stated you installed ARDH 45 a couple months ago. There is a lot of info there, so I missed that part.
Glad to hear you sorted it out. It's unusual to see a simple SuperSU update cause such a chain of event; but s#it happens I suppose.
Click to expand...
Click to collapse
Yeah it does. I also forgot to mention that my microphone went to sh*t also. But its not because of this event. Although after this last reinstall i did the microphone picks up my voice better than it did before it went crap. But people cant still hear me when they call me