Related
Please bear with me. I tried posting questions about this in the Q/A forum and received no real help.
I recently went from FRF50 to FRF83 and started getting random reboots. I'm on the 4.06.00.12_07 radio with the stock kernel. I wiped everything before flashing.
Today I wiped again and reflashed FRF50 and everything seemed to be okay aside from maybe 1 reboot.
I just flashed the stock FRF85B and rooted it and I'm back to rebooting. It's even worse now. It reboots the instant everything loads.
I got the last_kmsg:
http://pastebin.org/365407
Please let me know what's wrong. I'm dying to know. Is it hardware? Is it the battery? Am I going to have to pay a buttload of cash for HTC to fix it?
Thanks for any help
1) This is the wrong forum and you know it.
2) Wipe everything, start over from stock rom.
GldRush98 said:
1) This is the wrong forum and you know it.
2) Wipe everything, start over from stock rom.
Click to expand...
Click to collapse
Is it the wrong forum? Do people at the Q/A or general forum know about kernels/deeper info and do the people who know about that stuff venture over to those forums?
I tried getting info there, and I got none. This is the last place to turn.
What would wiping and starting from stock achieve?
No excuse for posting in the wrong location. But wipe data, all caches and reflash stock rom + radio. Report in General Section.
S_Dot said:
No excuse for posting in the wrong location. But wipe data, all caches and reflash stock rom + radio. Report in General Section.
Click to expand...
Click to collapse
How will this help me? Okay if stock works, but what about the update?
Why not maybe looking at using one of the moded versions of the Rom. If those dont work then maybe you need to think of going back to the Stock 2.1 and waiting for OTA to hit your phone. Going back to 2.1 will fix the problem and getting the OTA should work. Other wise wiping and reflashing is all that someone can tell you to do since I know i am using FRF83 right now with no reboots.
Just wipe everything inc dalvik-cache
Stock kernel keeps rooting so I guess its a framework issue
Prod1702 said:
Why not maybe looking at using one of the moded versions of the Rom. If those dont work then maybe you need to think of going back to the Stock 2.1 and waiting for OTA to hit your phone. Going back to 2.1 will fix the problem and getting the OTA should work. Other wise wiping and reflashing is all that someone can tell you to do since I know i am using FRF83 right now with no reboots.
Click to expand...
Click to collapse
leonnib4 said:
Just wipe everything inc dalvik-cache
Stock kernel keeps rooting so I guess its a framework issue
Click to expand...
Click to collapse
I'm going to try to go back to stock and see if it works. If not I can only assume that it is a hardware problem and I'll have to bite the bullet and pay for repairs.
What kind of a hardware problem could it be???
Can someone help me get back to stock properly?
See sticky.
Mod move to q&aplease.
leonnib4 said:
See sticky.
Mod move to q&aplease.
Click to expand...
Click to collapse
Sticky is full of bad info. I have new radio (4.06.00.12_07).
I'm assuming that if I get stock radio and the ERD79 update.zip I should be fine?
GldRush98 said:
1) This is the wrong forum and you know it.
2) Wipe everything, start over from stock rom.
Click to expand...
Click to collapse
You sir, are a complete asshole.
Sent from my Nexus One using XDA App
Yes the new radio won't work on 2.1 so change Ur radio and flash that update.zip and cross Ur fingers that Ur problem is fixed good luck let us know
Sent from my Nexus One using XDA App
FML. Hardware issue. Just went through CM 5.0.8. flash from scratch including re-flashing new radio and new recovery and I got a reboot during sign-in to Google.
God ****ing dammit.
Any logcat?
if you have an ext partition.. wipe that as well..
might be a battery issue. my battery had been overheated during navigation and right after boot it would give out turn off and boot again. just replaced it and worked fine.
To check battery issue, I suppose running with charger inserted would be enough.
Jack_R1 said:
To check battery issue, I suppose running with charger inserted would be enough.
Click to expand...
Click to collapse
What do you mean by this?
I'm pretty sure it is the battery. Been keeping minimal use today without USB charging and haven't had a reboot.
Any other ways I can confirm a bad battery?
Sent from my Nexus One using XDA App
If you can successfully boot and use the phone heavily while connected to a charger (preferrably AC charger - it can provide twice the current of USB cable), and you see no reboots - I believe that would point to your battery with a very high probability.
Hi! I root my o2x Ics using the latest AIO. It was successful but after that google play doesnt work. Pls. Help me im new in tweaking/ customizing things on android so im not sure what to do. I cant post on the AIO thread coz I'm new so I'm posting my concern here. What are the things i should do? TIA.
com.adroid.phone not working
hapilynvraftr said:
Hi! I root my o2x Ics using the latest AIO. It was successful but after that google play doesnt work. Pls. Help me im new in tweaking/ customizing things on android so im not sure what to do. I cant post on the AIO thread coz I'm new so I'm posting my concern here. What are the things i should do? TIA.
Click to expand...
Click to collapse
I factory reset my phone coz i thought it might fix the applications. but now my phone wont start. it pops up an error com.android.phone has stopped. and the background is something like encryption *****.
i search how to fix it and found it on another thread. says "after flashing another rom do a data wipe and ur problem will be resolved.
i have also faced this problem it happens sometimes when changing basebuilds."
well im not sure what to do. and how to do it. there is an wipe data on custom recovery but still nothing. pls help me guys. :crying:
Did you try to go to ALL APPS-FORCE STOP PLAY-CLEAR DATA and do the same on ALL DATA-MARKET UPDATER? I had this issue once and it was resolved
yep
johnkabou said:
Did you try to go to ALL APPS-FORCE STOP PLAY-CLEAR DATA and do the same on ALL DATA-MARKET UPDATER? I had this issue once and it was resolved
Click to expand...
Click to collapse
Yup but still google play doesn't load. it only shows not connected or something similar. but now my problem is not the google play anymore.
my phone wont start. after the LG logo my phone gives an error and that says com.android.phone has stopped with the background encryption unsuccessful.
I'm a complete noob on this. but i think I'll just flash a stock rom.
Fixed
i fixed my phone. thanks to spyrosk AIO toolkit. and who ever made the list of stock roms.
i had a hard time restoring my phone but after several errors I've done it.
Google play works fine now. I want to root my o2x again but i'm not sure if it will trigger my first problem.
any ideas or proper instructions ?
AW: [Q] Google Play dont work after rooting
hapilynvraftr said:
i fixed my phone. thanks to spyrosk AIO toolkit. and who ever made the list of stock roms.
i had a hard time restoring my phone but after several errors I've done it.
Google play works fine now. I want to root my o2x again but i'm not sure if it will trigger my first problem.
any ideas or proper instructions ?
Click to expand...
Click to collapse
The AIO toolkit is way to go to root properly. You should think if you want to stay GB bootloader or switch to oval. You should also think which rom it should be. Stock or custom stock or cm/miui. That error never occurred by me BTW.
If I helped click thanks like mummy told ya
Sent from my LG-P990 using xda premium
Darkmind82 said:
The AIO toolkit is way to go to root properly. You should think if you want to stay GB bootloader or switch to oval. You should also think which rom it should be. Stock or custom stock or cm/miui. That error never occurred by me BTW.
If I helped click thanks like mummy told ya
Sent from my LG-P990 using xda premium
Click to expand...
Click to collapse
Thanks for the reply. yes! everything is fine and working. Now i need to read/study other things for me to understand. i'll try reading about Custom Roms.
Running Beanstalk.
Have been having intermittent issues with mobile data, so I'm sadly familiar with toggling Airplane mode, changing the CMDA subscription, rebooting, etc. in order to jog mobile data into working again. Lately have been having a weird, sporadic problem with people I call only hearing static on my end, so I chatted with Sprint, got to the point where they suggest typing the code to reset/update PRLs into the dialer, and bailed.
Then, in my infinite wisdom decided to try flashing a Sense ROM, proceeding with the manual PRL update/reset, and then wiping and restoring my Beanstalk nandroid.
Now I can't make or receive calls or texts at all, no matter what I do. Have tried all the old toggles. Have tried a complete reflash of Beanstalk. I'm beginning to worry I seriously borked something up.
Is anyone familiar with this kind of situation? Did I screw up, and if so, how bad? Any solutions anyone can think of? I'd be most grateful for any and all help. Thanks guys.
Reinstalling ROM from scratch and if that doesn't work then running ARU.
EPayne123 said:
Reinstalling ROM from scratch and if that doesn't work then running ARU.
Click to expand...
Click to collapse
What's ARU? I did try reinstalling the ROM from scratch and it didn't fix it.
thedodus said:
What's ARU? I did try reinstalling the ROM from scratch and it didn't fix it.
Click to expand...
Click to collapse
Okay here is what you can do, there is an app floating around these forums that can allow you to manually write the prl, find that, and then use a stock prl for sprint. I believe this post will help:
http://forum.xda-developers.com/showthread.php?t=2296167
Let me know if that helps.
Oh and also yeah flashing a different rom wouldnt help because they do not contain any of that information, in fact i think all the carrier information is stored in a different partition for this exact reason -so they cant be easily overwritten.
I build the Beanstalk here and haven't come across that issue yet. Do you have a backup of your original stock ROM? You need to get back to straight stock, like out of the box stock. From there, you can update your prls or anything else OTA-style, check your functionality, then redownload the Beanstalk ROM from here, do a full wipe(no internal data), install the fresh DL, Gapps, fix permissions(PhilzTouch 6.0.3.3 only), and reboot. Should be good to go and should only need to toggle airplane for reboots and occasionally for the wifi. Let me know how it goes, either here, on the BS thread or by PM. Good luck....
If you have no original back up(after getting back to straight stock, MAKE ONE), then use Bigdaddy619s threads on getting back to stock. After that, then follow the steps above.
You should always make an original back up of stock directly after rooting and unlocking. ALWAYS
BMP7777 said:
I build the Beanstalk here and haven't come across that issue yet. Do you have a backup of your original stock ROM? You need to get back to straight stock, like out of the box stock. From there, you can update your prls or anything else OTA-style, check your functionality, then redownload the Beanstalk ROM from here, do a full wipe(no internal data), install the fresh DL, Gapps, fix permissions(PhilzTouch 6.0.3.3 only), and reboot. Should be good to go and should only need to toggle airplane for reboots and occasionally for the wifi. Let me know how it goes, either here, on the BS thread or by PM. Good luck....
If you have no original back up(after getting back to straight stock, MAKE ONE), then use Bigdaddy619s threads on getting back to stock. After that, then follow the steps above.
You should always make an original back up of stock directly after rooting and unlocking. ALWAYS
Click to expand...
Click to collapse
Thanks, both of you.
BMP - Beanstalk rules - it's definitely my fault. If I have a back-up made just after getting S-OFF, would that work?
matinm90 - thanks for the info...that explains exactly what the problem I'm having is.
I'll try these solutions out and post back. Thanks again guys.
Yes, it should as long as everything worked then. Driving right now. Try it and let me know. When I get home I'll help however I can.
Sent from my One using XDA Premium 4 mobile app
thedodus said:
Thanks, both of you.
BMP - Beanstalk rules - it's definitely my fault. If I have a back-up made just after getting S-OFF, would that work?
matinm90 - thanks for the info...that explains exactly what the problem I'm having is.
I'll try these solutions out and post back. Thanks again guys.
Click to expand...
Click to collapse
Your welcome and yeah it should defintely work, just make sure you use the right prl
Worked!
I think what I'd originally goofed was not immediately rebooting after the prl update, since the Sprint lady didn't mention that step (or maybe I didn't hear her). This time I immediately rebooted and data came back, and then I was able to flash BeanStalk and stay functional.
Many thanks to both of you!
thedodus said:
Worked!
I think what I'd originally goofed was not immediately rebooting after the prl update, since the Sprint lady didn't mention that step (or maybe I didn't hear her). This time I immediately rebooted and data came back, and then I was able to flash BeanStalk and stay functional.
Many thanks to both of you!
Click to expand...
Click to collapse
More than welcome. Glad you're up and running.:highfive:
thedodus said:
Worked!
I think what I'd originally goofed was not immediately rebooting after the prl update, since the Sprint lady didn't mention that step (or maybe I didn't hear her). This time I immediately rebooted and data came back, and then I was able to flash BeanStalk and stay functional.
Many thanks to both of you!
Click to expand...
Click to collapse
Your welcome glad you got everything straightened out
Sent from my HTCONE using Tapatalk
i have the virgn mobile HTC Desire 510 and i recently started experimenting with ROM's. The very first rom i flashed was RaptorRom 1.1 and i had no problems at all with it. But for some reason every other ROM i flash, it gives me the "Unfortunatley, the process com.android.phone has stopped" right at startup. it pop up ever seconds. does anyone know how to fix this? i have tried everything!
Floam said:
i have the virgn mobile HTC Desire 510 and i recently started experimenting with ROM's. The very first rom i flashed was RaptorRom 1.1 and i had no problems at all with it. But for some reason every other ROM i flash, it gives me the "Unfortunatley, the process com.android.phone has stopped" right at startup. it pop up ever seconds. does anyone know how to fix this? i have tried everything!
Click to expand...
Click to collapse
Did you happen to delete anything (bloat) when using RR. if so, most likely you deleted something you shouldnt have. Probably going to have to go back to the beginning and start over.
CSP III said:
Did you happen to delete anything (bloat) when using RR. if so, most likely you deleted something you shouldnt have. Probably going to have to go back to the beginning and start over.
Click to expand...
Click to collapse
Dirty flashing can cause this too.
CSP III said:
Did you happen to delete anything (bloat) when using RR. if so, most likely you deleted something you shouldnt have. Probably going to have to go back to the beginning and start over.
Click to expand...
Click to collapse
how can I reset my phone to how it came out of the box?
Floam said:
how can I reset my phone to how it came out of the box?
Click to expand...
Click to collapse
Heres a stock backup. Just Unrar and put in your backup folder on your SD in TWRP/Backups/FAxxxxxxxx/
Also theres a RUU somewhere on this forum, just don't know where.
LarryBoyG said:
Dirty flashing can cause this too.
Click to expand...
Click to collapse
Exact same thing I thought. That's why I wipe everything and I never have problems. Leave nothing to chance.
I am having this problem as well...
I placed the stock recovery in the TWRP folder and recovered 100% fine, but when I boot up my phone is still on RaptorRom GPE v2, still displaying, "Unfortunately, the process com.android.phone has stopped". Is there a problem here or am I not doing something right..?
**Also, I don't know if it's a hardware problem but my front camera is no longer working, looked everywhere on threads but nobody has addressed anybody else with this problem
(This is also happening with every other ROM I am trying to flash)
,thanks in advance.
ThePluviophile said:
I placed the stock recovery in the TWRP folder and recovered 100% fine, but when I boot up my phone is still on RaptorRom GPE v2, still displaying, "Unfortunately, the process com.android.phone has stopped". Is there a problem here or am I not doing something right..?
**Also, I don't know if it's a hardware problem but my front camera is no longer working, looked everywhere on threads but nobody has addressed anybody else with this problem
(This is also happening with every other ROM I am trying to flash)
,thanks in advance.
Click to expand...
Click to collapse
Are you doing a complete wipe of the caches, system and internal storage? You should be wiping them all except the SD card and the usb-otg ones otherwise you're dirty flashing. Regarding the camera, flash a different kernel.
Same problem here...... Any solution?
Hello. Ive been searching around for a solution to my problem and found this thread.
I tried all the suggestions on this thread and still no luck. If anyone has an answer or
a suggestion Im all ears and Thank You in advance.
LarryBoyG said:
Heres a stock backup. Just Unrar and put in your backup folder on your SD in TWRP/Backups/FAxxxxxxxx/
Also theres a RUU somewhere on this forum, just don't know where.
Click to expand...
Click to collapse
im having a problem with google play store. i have the rh-01 error. i tried reinstalling it but i still have that problem. can u please help me. sorry for asking
I want to start this off by acknowledging that this is my fault. I didn't heed the warning I was given when installing Xposed.
I installed Xposed, and when my phone restarted it just got stuck in the loading screen for Verizon.
I've tried putting a "factory" ROM on my device with no luck, multiple error codes, went through all the steps I could find online to try to resolve those.
I'm really lost here. There are a lot of important verification apps on my phone, and I really need this resolved. If anyone could please help bail me out of my stupidity it would be greatly appreciated.
Blueroad12 said:
I want to start this off by acknowledging that this is my fault. I didn't heed the warning I was given when installing Xposed.
I installed Xposed, and when my phone restarted it just got stuck in the loading screen for Verizon.
I've tried putting a "factory" ROM on my device with no luck, multiple error codes, went through all the steps I could find online to try to resolve those.
I'm really lost here. There are a lot of important verification apps on my phone, and I really need this resolved. If anyone could please help bail me out of my stupidity it would be greatly appreciated.
Click to expand...
Click to collapse
Maybe have a look at the S7 Verizon subforum. Someone over there might be able to help you. Good luck.
https://forum.xda-developers.com/verizon-galaxy-s7
Portgas D. Ace said:
Maybe have a look at the S7 Verizon subforum. Someone over there might be able to help you. Good luck.
https://forum.xda-developers.com/verizon-galaxy-s7
Click to expand...
Click to collapse
Will do, thanks.
For what I recall there was (don't know if it's still there) an "emergency way" to boot the phone preventing xposed to kick in. It saved my *ss many times, but you should see if and how this can be achieved with actual version of xposed. Good luck mate.
Sent from my Samsung G935F with Tapatalk 6
Blueroad12 said:
I want to start this off by acknowledging that this is my fault. I didn't heed the warning I was given when installing Xposed.
I installed Xposed, and when my phone restarted it just got stuck in the loading screen for Verizon.
I've tried putting a "factory" ROM on my device with no luck, multiple error codes, went through all the steps I could find online to try to resolve those.
I'm really lost here. There are a lot of important verification apps on my phone, and I really need this resolved. If anyone could please help bail me out of my stupidity it would be greatly appreciated.
Click to expand...
Click to collapse
You tried flashing stock rom with Odin on PC? Flashing Xposed uninstaller?
Verizon S7 is this with locked bootloader?
Sent from my S7.
FlemishDroid said:
You tried flashing stock rom with Odin on PC? Flashing Xposed uninstaller?
Verizon S7 is this with locked bootloader?
Sent from my S7.
Click to expand...
Click to collapse
I'm an idiot and didn't do my research.
I tried flashing a stock rom and got errors every time with odin.
Okay, I got it fixed by flashing a fresh ROM off of sammobile.