Related
Ok, I have an AT&T HTC One X. I have already rooted the phone and I have been running Venom Rom successfully for quite some time now. I decided I wanted to give some other roms a try today and I am running into some weird issues that I can't seem to figure out. To clarify my set up, I am not trying to run any custom kernels or anything that would potentially cause the issues I am experiencing. The roms I have tried and had these issues on are King Kang, Paranoid Android, and CM 10 official. With each the issues are always the same. First of all, I can't even type anything because Android Keyboard keeps force closing. Secondly, none of my hardware keys work at all except the back key, volume rocker, and power (home and recent apps do not function at all except to vibrate). Basically it leaves the phone completely unusable. I have gone back to Venom Rom for now because I have NEVER had any issues out of it. If anyone has any ideas why I am being plagued with these issues I would appreciate some feedback because I can't seem to find anyone else experiencing these kinds of issues honestly. Also I might add that I used a method to downgrade my HBOOT to, I believe, 1.09 instead of 1.14 because of the need to flash kernels separately with 1.14. My phone has worked flawlessly installing any ICS roms. This seems to only happen with JB roms. Thanks for your help in advance guys!
Factory reset in TWRP, and wipe Dalvik and cache before flashing any new ROM?
And to confirm, you are flashing the respective boot.img extracted from each ROM file, every time you've flashed a new ROM?
redpoint73 said:
Factory reset in TWRP, and wipe Dalvik and cache before flashing any new ROM?
And to confirm, you are flashing the respective boot.img extracted from each ROM file, every time you've flashed a new ROM?
Click to expand...
Click to collapse
Yeah, I of course did a factory reset and wiped cache and dalvik.
As far as the boot.img, I was under the impression that was only necessary for those with HBOOT 1.14 which is why I reverted my HBOOT. That was the only reason I have read anywhere to have the extract the boot.img. I am not new to Android or rooting.
guitarjuggalo said:
Yeah, I of course did a factory reset and wiped cache and dalvik.
Click to expand...
Click to collapse
If you don't tell us, we don't know. Its a common mistake, and better to ask, rather than the possibility of your issue just being something simple like not wiping.
guitarjuggalo said:
As far as the boot.img, I was under the impression that was only necessary for those with HBOOT 1.14 which is why I reverted my HBOOT. That was the only reason I have read anywhere to have the extract the boot.img. I am not new to Android or rooting.
Click to expand...
Click to collapse
Ah, I see I read that part too quickly. Confirm on the hboot screen that you are in fact on hboot 1.09, since you seem unsure.
And you are on TWRP, not CWM right?
Yea he wouldn't even boot up if he was on 1.14...
OP, are you doing a titanium backup?
Sent from my One X using Tapatalk 2
redpoint73 said:
If you don't tell us, we don't know. Its a common mistake, and better to ask, rather than the possibility of your issue just being something simple like not wiping.
Ah, I see I read that part too quickly. Confirm on the hboot screen that you are in fact on hboot 1.09, since you seem unsure.
And you are on TWRP, not CWM right?
Click to expand...
Click to collapse
Yes, I am on 1.09 for sure and using TWRP.
InflatedTitan said:
Yea he wouldn't even boot up if he was on 1.14...
OP, are you doing a titanium backup?
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
No, I haven't done a titanium backup. When things didn't work for whatever reason in any of those roms I just went back to the nandroid backup I had for Venom Rom that I did before jumping to any of those roms.
That's odd... usually a 100% fresh install comes out with good results lol.
Sent from my One X using Tapatalk 2
InflatedTitan said:
That's odd... usually a 100% fresh install comes out with good results lol.
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Yeah, it is very weird. I have never encountered these kind of issues. I have been using android since the original G1 on T-Mobile and haven't encountered issues with roms this horrible. Installing any of those roms makes my phone pretty much unusable. All 3 of them (haven't tried others) exhibit the same issues. Android keyboard force closes over and over again and won't ever pull up, and the home and recent apps buttons don't work at all. Also just about any Google app or service I tried to use was crashing out.
What are you using to download?
Sent from my One X using Tapatalk 2
InflatedTitan said:
What are you using to download?
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Downloading through wi-fi on my computer and sending it to the phone via USB. Also dried downloading directly to the phone over wi-fi. Results are all the same.
So, it appears that nobody has an answer?
Did you check the md5 of the zip before flashing?
I had a problem where the Rom would install fine but issues loading. Md5 of the zip on my pc was good but was bad on my sdcard. Got messed up while transferring I guess.
Also try updating to latest twrp
Sent from my HTC One XL using xda app-developers app
Make sure you aren't flashing 4.2 gapps on a 4.1 ROM. That could cause a lot of Google app FCs.
Sent from my One X using xda app-developers app
lauterm said:
Make sure you aren't flashing 4.2 gapps on a 4.1 ROM. That could cause a lot of Google app FCs.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I officially feel retarded. Thank you so much! That was indeed the issue. FML lol :good: :victory:
Its amazing that gapps controls so much that it even screwed my hardware keys with the wrong version. I really appreciate all the suggestions guys.
Hi. I recently installed Liquid Smooth (Unofficial) 4.3 onto my Skyrocket. Since install, if I reboot the phone it will get the ever dreaded Black Screen Of Death. The only way I've found to fix this is to clear the data partition in my recovery (TWRP updated to most recent version) and then reflash the ROM and the gapps. Any ideas on how to keep the BSOD from happening again? I've tried everything I can think of. I tried just wiping the dalvek, cache and system and then flashing the ROM again. As I said, the only way I can find to "fix" it is to wipe the data partition and then flash the ROM and gapps again. I would have asked in that specific thread, but since I am a new member I can't until I reach the 10 post requirement.
CoolWolf22 said:
Hi. I recently installed Liquid Smooth (Unofficial) 4.3 onto my Skyrocket. Since install, if I reboot the phone it will get the ever dreaded Black Screen Of Death. The only way I've found to fix this is to clear the data partition in my recovery (TWRP updated to most recent version) and then reflash the ROM and the gapps. Any ideas on how to keep the BSOD from happening again? I've tried everything I can think of. I tried just wiping the dalvek, cache and system and then flashing the ROM again. As I said, the only way I can find to "fix" it is to wipe the data partition and then flash the ROM and gapps again. I would have asked in that specific thread, but since I am a new member I can't until I reach the 10 post requirement.
Click to expand...
Click to collapse
Try using the latest CWM recovery. Some people are reporting having better luck using this for the BSOD issue.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
jondroid2 said:
Try using the latest CWM recovery. Some people are reporting having better luck using this for the BSOD issue.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
I will try this and will get back to you. I'd still like to know what's causing the issue in the first place. I've been flashing on Samsung devices since the original Epic 4G launched. Never have had any issues like this before.
CoolWolf22 said:
I will try this and will get back to you. I'd still like to know what's causing the issue in the first place. I've been flashing on Samsung devices since the original Epic 4G launched. Never have had any issues like this before.
Click to expand...
Click to collapse
I've had the same issue and switching to cwm solved it. It's a real pita though as a prefer twrp and my nandroids are twrp. I switch back and forth between them.
jd1639 said:
I've had the same issue and switching to cwm solved it. It's a real pita though as a prefer twrp and my nandroids are twrp. I switch back and forth between them.
Click to expand...
Click to collapse
CWM fixed my BSOD. I've had 2 successful reboots so far. I too preferred TWRP over CWM. But oh well. I am in contact with the devs for TWRP to see if they are aware of the issue and can issue a fix for it.
CoolWolf22 said:
CWM fixed my BSOD. I've had 2 successful reboots so far. I too preferred TWRP over CWM. But oh well. I am in contact with the devs for TWRP to see if they are aware of the issue and can issue a fix for it.
Click to expand...
Click to collapse
There's an build of TWRP 2.7 that I've been using and haven't had any issues with. The only thing "wrong" with it is it only reads internal storage. Here's the Link
theesotericone said:
There's an build of TWRP 2.7 that I've been using and haven't had any issues with. The only thing "wrong" with it is it only reads internal storage. Here's the Link
Click to expand...
Click to collapse
Thanks. I'll download that and keep it in reserve for future reference.
Hey Guys,
So I decided to be a little bit dangerous at work today and flashed cyanogenmod but I didn't really like it all too much so I tried to flash back to franco's kernel. Now my phone's messed up and wont go pass the google screen. I don't have my usb cords either. What can I do?
Well, you will obviously need a usb cable to push the cyanogenmod zip to your device if it's not there already.
If you have the rom in your sdcard, then boot to recovery and flash cm again. It should boot.
We need your firmware you were running what cyagenomod you flashed what firmware you tried to go back to how you flashed it and what colour of T-shirt you were wearing at the time. ANY info you have. And yes you are going to need the USB lead. Anyway you can prob just fix it with Wugfresh nrt
Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
bullsrfive said:
Hey Guys,
So I decided to be a little bit dangerous at work today and flashed cyanogenmod but I didn't really like it all too much so I tried to flash back to franco's kernel. Now my phone's messed up and wont go pass the google screen. I don't have my usb cords either. What can I do?
Click to expand...
Click to collapse
Get back to recovery and flash CM or adb sideload another custom rom or flash the factory image in fastboot. Franco kernel is not compatible with CM atm.
gee2012 said:
Get back to recovery and flash CM or adb sideload another custom rom or flash the factory image in fastboot. Franco kernel is not compatible with CM atm.
Click to expand...
Click to collapse
I just flashed CM again to get my phone working. So to get back to franco's kernel I pretty much have to flash my phone back to stock?
bullsrfive said:
I just flashed CM again to get my phone working. So to get back to franco's kernel I pretty much have to flash my phone back to stock?
Click to expand...
Click to collapse
Or a custom rom based on AOSP (stock) scources like most are, read the OP of the different devs. If CAF is mentioned in a OP Franco kernel is not compatible.
bullsrfive said:
I just flashed CM again to get my phone working. So to get back to franco's kernel I pretty much have to flash my phone back to stock?
Click to expand...
Click to collapse
Yup stock or any other aosp based rom such as paranoid etc.
varuntis1993 said:
Yup stock or any other aosp based rom such as paranoid etc.
Click to expand...
Click to collapse
Thanks for the reply guys! Unfortunately my phone is going crazy right now and every thing isn't work. The internet browser stops sometimes and I definitely cannot download anything. Do I have to wipe anything for the device to start working properly?
bullsrfive said:
Thanks for the reply guys! Unfortunately my phone is going crazy right now and every thing isn't work. The internet browser stops sometimes and I definitely cannot download anything. Do I have to wipe anything for the device to start working properly?
Click to expand...
Click to collapse
Yup, just do a data factory reset, backup first though.
gee2012 said:
Yup, just do a data factory reset, backup first though.
Click to expand...
Click to collapse
Okay I'll do that. I have a question about downloading paranoid rom. If I flash that then flash franco, am I just adding franco to paranoid or am i going back to just franco?
bullsrfive said:
Okay I'll do that. I have a question about downloading paranoid rom. If I flash that then flash franco, am I just adding franco to paranoid or am i going back to just franco?
Click to expand...
Click to collapse
First flash PA and straight after that Franco.
bullsrfive said:
Okay I'll do that. I have a question about downloading paranoid rom. If I flash that then flash franco, am I just adding franco to paranoid or am i going back to just franco?
Click to expand...
Click to collapse
You're mixing up roms and kernels. There not the same thing
Sent from my Nexus 5
I think that you urgently need to read here http://forum.xda-developers.com/wiki/index.php?title=ROM-VS-Kernel
Or will brick your phone as soon as today.
I am a dummy. Basically what I was running before was stock rom with franco kernel. I loved it! Looks like I'll hav to flash back to stock and load up franco. I guess I'll need my USB cable for that.
I'm having major problems with the PA rom though. It keeps saying the process com.android.phone has stopped and I can't really do anything. A lot worse than when I was on CM. Ughh ....
Never mind it works now after I wiped the data from recovery mode. Man once I get it back to what it was before I'm never downloading another rom again lol. Thanks for all your help guys
bullsrfive said:
Never mind it works now after I wiped the data from recovery mode. Man once I get it back to what it was before I'm never downloading another rom again lol. Thanks for all your help guys
Click to expand...
Click to collapse
The best thing to do in these situations is to stay calm. When your about to flash something to your device, Always read the OP and then read it again, just to make sure you didn't miss anything or misunderstand something. Your not a dummy and It's not that there's a problem with the ROM's or the kernel's... its the lack of compatibility of the kernel with ROM. Which as you found out will get you stuck on the splash screen or in a bootloop, but its an easy fix.
Also when ever your flashing a completely new ROM, (like going from CM to PA) do a clean install, generally by just wiping the dalvik cache, the cache partition and performing a factory reset in recovery or what the ROMs OP suggests. This will make sure that there's nothing left over from the previous ROM and won't cause weird issues like the com.android.phone has stopped problem.
bullsrfive said:
Never mind it works now after I wiped the data from recovery mode. Man once I get it back to what it was before I'm never downloading another rom again lol. Thanks for all your help guys
Click to expand...
Click to collapse
You don't have to feel discouraged about flashing Roms. All of us were on trouble at lest 3 times during android experience. Now you know what to do if run into the same problem. This is about informing before doing things we are not used too. If you like a new Rom, don't flash it without understanding its features and kernel compatibility. Read threads, they are huge but at least firs pages and last ones too. Ask questions, get answers and evaluate the challenge.
There is a lot of juicy info on the first 4 threads on the general section that will provide almost all you need to know to go safe.
Hey guys, i'm posting here because I have a huge issue with my phone.
I think I have an idea of what caused my phone to go haywire, but i'm gonna post my phone specs:
Red Nexus 5 32gb
Rooted
Franco Kernel
4.4.2 (however, I think it may have somehow updated to 4.4.3 OTA somehow, which may be the root of the problems)
TWRP
Nandroid backup but done once i've been experiencing these problems
-The phone boots up normally and then abrubtly freezes.
-The dialogue "Unfortunately, the process com.android.systemui has stopped."
-I press ok, the screen turns black
-"Unfortunately, Update Device has stopped"
-I press ok, shortly after, both prompts pop up again repeatedly.
I literally have no way to get to the home menu, even using Safe Mode.
My main priority is to at least recover my SMS files. And obviously fix my phone..
NotReallyKnown said:
Hey guys, i'm posting here because I have a huge issue with my phone.
I think I have an idea of what caused my phone to go haywire, but i'm gonna post my phone specs:
Red Nexus 5 32gb
Rooted
Franco Kernel
4.4.2 (however, I think it may have somehow updated to 4.4.3 OTA somehow, which may be the root of the problems)
TWRP
Nandroid backup but done once i've been experiencing these problems
-The phone boots up normally and then abrubtly freezes.
-The dialogue "Unfortunately, the process com.android.systemui has stopped."
-I press ok, the screen turns black
-"Unfortunately, Update Device has stopped"
-I press ok, shortly after, both prompts pop up again repeatedly.
I literally have no way to get to the home menu, even using Safe Mode.
My main priority is to at least recover my SMS files. And obviously fix my phone..
Click to expand...
Click to collapse
reflash your rom, or flash another rom. if using stock, you can reflash the factory img or find a rooted stock rom. anyways, you DO want to update to 444, as many bugs have been fixed from 442 to 444. if yoy dont want to lose any data, grab a stock rooted rom and flash it dirty, as in dont wipe a single thing. and your phone can not update itself, only you can let it update. and with you using franco kernel, it can not flash an ota, you would have to do it manually.
simms22 said:
reflash your rom, or flash another rom. if using stock, you can reflash the factory img or find a rooted stock rom. anyways, you DO want to update to 444, as many bugs have been fixed from 442 to 444. if yoy dont want to lose any data, grab a stock rooted rom and flash it dirty, as in dont wipe a single thing. and your phone can not update itself, only you can let it update. and with you using franco kernel, it can not flash an ota, you would have to do it manually.
Click to expand...
Click to collapse
Do you mind linking me a good thread on how to dirty flash a rom? I've been looking all over and i'm getting a lot of results that simply don't work.
Edit:
Nevermind, found out how to use adb. Can you at least tell me where the SMS files are stored? I used Textra.
NotReallyKnown said:
Do you mind linking me a good thread on how to dirty flash a rom? I've been looking all over and i'm getting a lot of results that simply don't work.
Edit:
Nevermind, found out how to use adb. Can you at least tell me where the SMS files are stored? I used Textra.
Click to expand...
Click to collapse
well, theres no such thing. as most everyone will tell you the proper way is to clean flash, you wont find a dirty flashing thread. regardless, im known for my dirty flashing of everything. generally, what you do to dirty flash is make a backup in recovery first, then just flash what you need to flash, without wiping anything. the thing about dirty flashing is that you dont lose any data(while clean flashing you do).
where the sms files are stored, i have no idea. have you checked if your sms app created a file?
simms22 said:
well, theres no such thing. as most everyone will tell you the proper way is to clean flash, you wont find a dirty flashing thread. regardless, im known for my dirty flashing of everything. generally, what you do to dirty flash is make a backup in recovery first, then just flash what you need to flash, without wiping anything. the thing about dirty flashing is that you dont lose any data(while clean flashing you do).
where the sms files are stored, i have no idea. have you checked if your sms app created a file?
Click to expand...
Click to collapse
So what I should do is push the rooted stock rom somewhere into my phone and use TWRP to install it straight?
NotReallyKnown said:
So what I should do is push the rooted stock rom somewhere into my phone and use TWRP to install it straight?
Click to expand...
Click to collapse
right. adb push it to your phone, then flash it in twrp. if the dirty flash doesnt work out(chances are that it will) then you would have to wipe data(factory reset) and reflash.
simms22 said:
right. adb push it to your phone, then flash it in twrp. if the dirty flash doesnt work out(chances are that it will) then you would have to wipe data(factory reset) and reflash.
Click to expand...
Click to collapse
You are a f**king god. It worked perfectly! Thank you so much!
Why isn't Dirty Flashing suggested by most?
NotReallyKnown said:
You are a f**king god. It worked perfectly! Thank you so much!
Why isn't Dirty Flashing suggested by most?
Click to expand...
Click to collapse
because most follow older "proper" ways to flash software. and the proper way to flash, and to make sure all is working as should, is to clean flash. dirty flashing can cause issues, but its issues that are usually fixable. the problem is that most dont know that, or how to fix. 99.99% of issues caused by dirty flashing are caused by corrupt or incompatible data. where a data clearing for that particular app will usually fix. anyways, roms based on the same sourcw, and not far from what you are running, you can dirty flash. roms that have a different base than what you are running, you should factory reset first.
Dirty flashing has the potential of causing conflicts and issues. Of course it is not so bad if you back up your data. One problem though, is you might use your phone for a few weeks before the issues show up, then suddenly you are unable to backup data. So you lost a week or two of stuff.
By the way, I often dirty flash when I run into issues. After that though, it is a good idea to back everything up, wipe, and reflash everything. Limits potential issues arising and also causes of said issues.
wangdaning said:
Dirty flashing has the potential of causing conflicts and issues. Of course it is not so bad if you back up your data. One problem though, is you might use your phone for a few weeks before the issues show up, then suddenly you are unable to backup data. So you lost a week or two of stuff.
By the way, I often dirty flash when I run into issues. After that though, it is a good idea to back everything up, wipe, and reflash everything. Limits potential issues arising and also causes of said issues.
Click to expand...
Click to collapse
issues from dirty flashing do not appear weeks later, dirty flashing issues show up right away. all dirty flashing issues are caused by data, whether corrupt or incompatible. other issues are blamed on dirty flashes, but arent the real cause. issues like app fc's are the most common, and very fixable. the only issues that arent fixable are when you dirtt flash two completely different roms that are based on different sources, or different android versions. i have dirty flashed every single thing ive flashed onto my n5, since december, no issues. the only issue i had dirty flashing my n5 was dirty flashing L over rastakat. and the issue was minor. everything worked great except the status bar didnt go down all the way. why did it mess uo? because of incompatible data from rastakat with the new status bar code in L.
You are correct Simms, but it must be noted that you dirty flash the same version, for dirty flash to work. If just updating a rom it is usually fine, but if they have made a major change then it is not.
Have no tales to tell of my N5, but my Samcrap S3 (cracked the screen and she died, then I bought this bad boy ) had issues that would appear later. Maybe due to the dirty flash. Who knows, that is why I mentioned a clean flash rules that out.
Anyway, backing up everything leads to a carefree life!
Hi at all
I didn't reached 10 messages so I can't post my question on developer's thread, so I'm going to ask it here
I have a PureWhite L preview ROM updated to semptember release
yesterday the developer updated to a new version and I don't know if I can upgrade to a new version without a FullWipe
Thanks for the patience
If it doesn't say clean flash (full wipes) then you can try a dirty flash (no wipes).
If you have any issues at all after tho, you need to clean flash before reporting them, to see if that solves it.
Use titanium backup to back up user apps and data, and clean flash....that's the best way in my opinion. (obviously don't wipe internal SD)
---------- Post added at 06:42 PM ---------- Previous post was at 06:41 PM ----------
Oh, when devs make major changes, they usually will tell us to clean flash....in that case, do it. ?
Thank you for the reply
I alreary use Titanium, I'm not a beginner but I don't want to soft brick my phone doing a dirty flash and the autor didn't mentioned if I can do it
Worst case usually if updating same Rom is some issues like force closing, or maybe a bootloop or something. If so, then just clean flash it.
I've never heard of a brick from dirty flashing a Rom update.
But, there's risk with everything we do as always. ?
sas46 said:
I'm not a beginner but I don't want to soft brick my phone
Click to expand...
Click to collapse
Hehe that's an oxymoron. No such thing as a soft brick. Only beginners believe it exists
Seriously though the reason for boot loops with dirty flash is incompatible data. Nothing more. Nandroid. Titanium. Flash. If it boot loops, wipe.
Sent from my Nexus 5 using Tapatalk
rootSU said:
Hehe that's an oxymoron. No such thing as a soft brick. Only beginners believe it exists
Seriously though the reason for boot loops with dirty flash is incompatible data. Nothing more. Nandroid. Titanium. Flash. If it boot loops, wipe.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
You are saying that, more than one year ago I bricked my gNex doing an update of PA without a full wipe (only cache, dalvik and format system)
That rom is a cooked rom from an unstable preview, so if the developer made some important changes it can cause some major problems with booting like happened with PA and my Gnex
sas46 said:
You are saying that, more than one year ago I bricked my gNex doing an update of PA without a full wipe (only cache, dalvik and format system)
That rom is a cooked rom from an unstable preview, so if the developer made some important changes it can cause some major problems with booting like happened with PA and my Gnex
Click to expand...
Click to collapse
Whatever caused your "brick" on your gnex, I 100% guarantee you that it was absolutely nothing to do with whether you wiped or not.
Sent from my Nexus 5 using Tapatalk
rootSU said:
Whatever caused your "brick" on your gnex, I 100% guarantee you that it was absolutely nothing to do with whether you wiped or not.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I'm not a developer, I'm an user that like, sometimes, to test some new roms and I really like thi one. I'm only reporting you my experience. I can't waste half a day to put my phone back working and that's why I asked there my think
When I'll reach 10 posts I will ask to the developer directly
Thank you for your patience
sas46 said:
I'm not a developer, I'm an user that like, sometimes, to test some new roms and I really like thi one. I'm only reporting you my experience. I can't waste half a day to put my phone back working and that's why I asked there my think
When I'll reach 10 posts I will ask to the developer directly
Thank you for your patience
Click to expand...
Click to collapse
I'm trying to help you. Your question is basic and any user who flashes ROMs should at least understand these basics. This is not a question you need to ask the developer. We've already answered. Its an answer we give a hundred times a day.
Try reading our sticky threads which you can get to via my signature. We've written everything you'd ever need to know
Sent from my Nexus 5 using Tapatalk
Guaranteed you didn't brick your gnex from a dirty flash.
You can't brick your phone from a dirty flash.
#stayparanoid
Honestly, if you are worried about needing time to fix the odd issue, flash stock and call it a day. This hobby can very often require some time when things don't work right.
That's just how it is. ?