Related
i installed pheonix blood 1.6 on my phone. i was previously running 1.5. flashed it using rom manager and it booted up and everything but i cant get in the market and voxer icon is on my phone but says its not installed. im new to rooting so any help will be appreciated
You need to read more for one!
Reflash gapps and never use rom manager.
Sent from my LG-P999 using xda premium
There's nothing at all wrong with Rom Manager. It's a great thing. As long as recovery is flashed with NVflash.
Sent from my LG-P999 using xda premium
I don't recommend it to anyone I've used it once, flash failed or download failed, either way needed a battery pull had to use CWM I will only recommend CWM, lol.
dw9906 said:
There's nothing at all wrong with Rom Manager. It's a great thing. As long as recovery is flashed with NVflash.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
He means if you never used rom manager to ever download or flash recovery and ONLY used nvflash... then rom manager will ALWAYS and ONLY boot into your only cwm recovery.
But yeah, did you download and flash gapps like mt3g asked?
Which gapps are you using? I flashed the one that's said to use in the thread and my phone said they're 2.3.5 and had a few issues, I just googled the 2.3.7 ones and everything works fine for me
Sent from my LG-P999 using Tapatalk
Unfortunately for me modded gapps won't flash, and Gmail from the market isn't marking mail as read. I did use scrubber.. Anybody had this issue?
Sent from my LG-P999 using Tapatalk
januszm said:
Unfortunately for me modded gapps won't flash, and Gmail from the market isn't marking mail as read. I did use scrubber.. Anybody had this issue?
Sent from my LG-P999 using Tapatalk
Click to expand...
Click to collapse
what do you mean won't flash? are you flashing it right after you flash PB rom?
That's correct, scrubber->pb rom->gapps. There is no gmail app after the boot.
i didnt download the rom from rom manager. i installed it from rom manager i ran gapps and everything seems to be in order now
Since I'm not allowed to post anywhere else
I know on the Phoenixblood main thread at the end it says to wipe, but if I am going from 1.6 to 1.7 is that really necessary? It seems like there were only minor changes. Meaning, can I just wipe dalvik and cache and be okay?
Well for others wondering like me, I just wiped cache and dalvik and upgraded to 1.7. So far so good.
Sent from my LG-P999 using XDA App
I've looked around for a little while and can't find any thread that says how to go from one build of a custom ROM to another... I feel extremely noobish asking this as well. I'm on build 11 of bean's custom JB ROM and there have been three new builds and I'm wondering if I need to do a full wipe as if I were flashing a ROM from stock, or if I just go ahead and do a dirty flash... Thanks in advance for the help
Sent from my SCH-I535 using xda app-developers app
jonnyboiii said:
I've looked around for a little while and can't find any thread that says how to go from one build of a custom ROM to another... I feel extremely noobish asking this as well. I'm on build 11 of bean's custom JB ROM and there have been three new builds and I'm wondering if I need to do a full wipe as if I were flashing a ROM from stock, or if I just go ahead and do a dirty flash... Thanks in advance for the help
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
It's really at your own discretion. You can dirty flash, but you might have issues, but clean flashes are always the best path to take. Although, sometimes the devs do recommend a clean flash on some releases when they change something major.
Sent from my SCH-I535 using xda app-developers app
Personally I always dirty flash. A couple of times I've encountered problems, made a backup then wiped to troubleshoot the problem, but its never fixed anything so I just revert to my backup. YMMV
Just read and follow the install instructions for the specific rom.
Sent from my Galaxy SIII
PaulG1488 said:
Just read and follow the install instructions for the specific rom.
Sent from my Galaxy SIII
Click to expand...
Click to collapse
So you're saying I should do a clean wipe and start fresh?
Sent from my SCH-I535 using Tapatalk 2
jonnyboiii said:
So you're saying I should do a clean wipe and start fresh?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
In a nutshell, yes
Sent from my SCH-I535 using xda app-developers app
jonnyboiii said:
So you're saying I should do a clean wipe and start fresh?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
The OP usually tells you what you need to do. If there are major changes, they will tell you to wipe. Sometimes, dirty flashing is okay, just make sure that you follow the directions from the dev that created the ROM.
Sent from my SCH-I535 using xda premium
HHF2 said:
The OP usually tells you what you need to do. If there are major changes, they will tell you to wipe. Sometimes, dirty flashing is okay, just make sure that you follow the directions from the dev that created the ROM.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
But if you encounter errors after dirty flashing, always do a full wipe and reflash before reporting them.
Sent from my GT-I9300 using Tapatalk 2
Just dirty flash it. Backup your apps and etc... prior just in case you do run into issues.
jonnyboiii said:
I've looked around for a little while and can't find any thread that says how to go from one build of a custom ROM to another... I feel extremely noobish asking this as well. I'm on build 11 of bean's custom JB ROM and there have been three new builds and I'm wondering if I need to do a full wipe as if I were flashing a ROM from stock, or if I just go ahead and do a dirty flash... Thanks in advance for the help
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Format and flash.
As a general rule, I do an App backup (I tend to like My Backup Pro for app backups), a full nandroid backup, then dirty flash (wiping dalvik/cache) and see how it goes. Best case, everything works and I save myself a ton of time not having to restore apps/reapply settings. Worst case, if I have problems that don't seem to be generally reported, I do a full wipe and clean install.
jonnyboiii said:
I've looked around for a little while and can't find any thread that says how to go from one build of a custom ROM to another... I feel extremely noobish asking this as well. I'm on build 11 of bean's custom JB ROM and there have been three new builds and I'm wondering if I need to do a full wipe as if I were flashing a ROM from stock, or if I just go ahead and do a dirty flash... Thanks in advance for the help
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
So I'm trying to install CvD Nibbles 1.6 and the installation goes well until about 70% of the way through and then it gives me this message.
Setting up Nibbles
Setting system permissions
file_get prop:failed to stat
"/rpm/aroma/kernel.prop" No such file or directory
Any help would be appreciated
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
what recovery are u using? u need to have twrp 2.3.3 installed
I'm using sk8's latest recovery version. If I switch to twrp how hard is it to switch back?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
y would u want to switch back lol? how often are u in recovery anyway to be honest. u only boot into it to flash a ROM. switch to it and see if that alleviates your issue.
I don't like Twrp that's why I would like to switch back. Lol
Sent from my SAMSUNG-SGH-I727
How can you not like twrp.
Sent from my refrigerator
MrGriffdude said:
I don't like Twrp that's why I would like to switch back. Lol
Sent from my SAMSUNG-SGH-I727
Click to expand...
Click to collapse
Dafuq? U be trippin son! #swag
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
xcrazydx said:
Dafuq? U be trippin son! #swag
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Idk I just like sk8s recovery better no reason I guess. Plus I've used cwm on every android I've ever owned and its what I'm familiar with seems to work for me.. and if its not broken I see no reason to Switch
Sent from my SAMSUNG-SGH-I727
MrGriffdude said:
Idk I just like sk8s recovery better no reason I guess. Plus I've used cwm on every android I've ever owned and its what I'm familiar with seems to work for me.. and if its not broken I see no reason to Switch
Sent from my SAMSUNG-SGH-I727
Click to expand...
Click to collapse
its broken... so switch. lol I don't see why u would switch back to something that can't correctly flash jellybean ROMs. Someone correct if I'm wrong but I do believe u need twrp to flash aosp based 4.2
How is it broken? And sk8's recovery can flash 4.2 roms correctly that was one of the first questions he was asked in his 4.2 compile thread.
Sent from my SAMSUNG-SGH-I727
This has been resolved in the Nibbles thread.
Recovery was not the problem. There's a bug in the installation process within Nibbles for the Base Install. Custom installation works fine. Check my thread for details.
Mods, please lock. Thanks!
I dirty flashed 4.2.2 to 4.3 no problem but I'm having issues lately, is it safe to go back?
Thanks
Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
Full wipe. You dirty flashed already and are experiencing issues. It does not make sense if you were to dirty flash again.
Sent from my SCH-I535 using Tapatalk 4
SlimSnoopOS said:
Full wipe. You dirty flashed already and are experiencing issues. It does not make sense if you were to dirty flash again.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
It was working alright until a newer version that was also 4.3 came out and I flashed that.
Plus I've had to format data because I messed something up with killjoy and tkmod and experience the problems I had before that so I don't think the dirty flash is the issue.
Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
Aight, well you have your answer then.
Sent from my SCH-I535 using Tapatalk 4
SlimSnoopOS said:
Aight, well you have your answer then.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
I don't get how I have my answer..?
Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
Maphack said:
I don't get how I have my answer..?
Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
It's pretty simple, do a clean flash. Anytime you flash different android versions you should never dirty flash. You do realize Android 4.2.2 and Android 4.3 are completely different versions right?
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
It's pretty simple, do a clean flash. Anytime you flash different android versions you should never dirty flash. You do realize Android 4.2.2 and Android 4.3 are completely different versions right?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I guess I didn't make myself clear, I dirty flashed, had to reformat my data and flashed 4.3 again but still had the exact same problem that I did when I dirty flashed. A data format would be a clean flash amirite?
You do realize that flashing from 4.2.2 isn't like flashing 3.0 to 4.0?
Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
Maphack said:
I guess I didn't make myself clear, I dirty flashed, had to reformat my data and flashed 4.3 again but still had the exact same problem that I did when I dirty flashed. A data format would be a clean flash amirite?
You do realize that flashing from 4.2.2 isn't like flashing 3.0 to 4.0?
Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
OK that's much more clear, a clean flash is factory reset, wipe cache and wipe dalvik cache. You can also wipe system to clear out the old rom before flashing a new one.
I don't see how data formatting would fix your bugs, but keeping your data and dirty flashing 4.3 on top of 4.2.2 would certainly give you problems.
I think a clean flash will fix everything, as long as you don't restore system data from titanium backup or something.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
OK that's much more clear, a clean flash is factory reset, wipe cache and wipe dalvik cache. You can also wipe system to clear out the old rom before flashing a new one.
I don't see how data formatting would fix your bugs, but keeping your data and dirty flashing 4.3 on top of 4.2.2 would certainly give you problems.
I think a clean flash will fix everything, as long as you don't restore system data from titanium backup or something.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I had to format data because I messed with ktoons and cputuner from killjoy because I'm an idiot.
I was just hoping someone had personal experience flashing between the two and could give me their personal experience. I was able to find a stable 4.3 version so it didn't even matter in the end.
I figured if I was asking a question like this it could be assumed I'm already aware that clean flashing is always the best thing to do and restating that really is of no use...
Thanks though.
And yeah, dirty flashing from 4.2.2 on PA is no problem if anyone cared.
Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
Maphack said:
I had to format data because I messed with ktoons and cputuner from killjoy because I'm an idiot.
I was just hoping someone had personal experience flashing between the two and could give me their personal experience. I was able to find a stable 4.3 version so it didn't even matter in the end.
I figured if I was asking a question like this it could be assumed I'm already aware that clean flashing is always the best thing to do and restating that really is of no use...
Thanks though.
And yeah, dirty flashing from 4.2.2 on PA is no problem if anyone cared.
Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
I'm really confused what you're getting at here. You asked a question, you got your answers, then you're saying that by the way you stated your question we should already assume that you know what you're doing?
The way you stated your question didn't really sound like you understood the difference between a dirty and clean flash. Wiping your data will have an insignificant effect if there's a problem with the rom itself because you decided to dirty flash.
Snoop obviously knows his stuff, he tells you to clean flash and you ignore it and still point out the issues you're having. If you already know what you're doing then don't waste our time and ask questions you already have your answer to.
Maybe you should point out you're looking for another experience similar to yours, we were simply giving you pointers on how to fix it, which is exactly what this forum is used for.
Just a heads up, if your cpu was giving you issues, then flashing the kernel again would've fixed your problem also. Wiping your data alone won't fix anything, you essentially just erase your own data and do nothing to the rom or kernel itself.
Hopefully your problem is fixed now.
Sent from my SCH-I535 using Tapatalk 2
after i flash a rom and when i get to setup menu it says unfortanately phone has stopped!! doesnt matter which rom i flash it says the same thing!! tried with omni rom official beanstalk rom and bs harmony rom!! please help thx in advance
What steps are you taking when you flash a ROM?
Sent from my Nexus 5 using xda app-developers app
freddienux74 said:
after i flash a rom and when i get to setup menu it says unfortanately phone has stopped!! doesnt matter which rom i flash it says the same thing!! tried with omni rom official beanstalk rom and bs harmony rom!! please help thx in advance
Click to expand...
Click to collapse
Are you wiping data when you flash the rom?
If you don't have any important stuff on your phone, I would just flash the factory images and start over with the rom process.
freddienux74 said:
after i flash a rom and when i get to setup menu it says unfortanately phone has stopped!! doesnt matter which rom i flash it says the same thing!! tried with omni rom official beanstalk rom and bs harmony rom!! please help thx in advance
Click to expand...
Click to collapse
Please tell us also what is your phone's status at the moment. Like is your phone rooted with bootloader unlocked and stuff like that.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Bruce Lee said:
Please tell us also what is your phone's status at the moment. Like is your phone rooted with bootloader unlocked and stuff like that.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well since he's flashing a rom, it would be rooted and the bootloader unlocked.
aooga said:
Well since he's flashing a rom, it would be rooted and the bootloader unlocked.
Click to expand...
Click to collapse
It never hurts to ask though. Maybe he did something different and bypassed something. You never know. You got to have the whole story. :sly:
Sent from my Nexus 5 using XDA Premium 4 mobile app
Kreateablaze said:
What steps are you taking when you flash a ROM?
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
I did full wipe then dalvik cache
Sent from my Nexus 5 using Tapatalk
I'm rooted! When I flashed Mahdi ROM no issues! Mahdi ROM actually is my backup ROM also
Sent from my Nexus 5 using Tapatalk
freddienux74 said:
I'm rooted! When I flashed Mahdi ROM no issues! Mahdi ROM actually is my backup ROM also
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Wait it's working now?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Bruce Lee said:
Wait it's working now? No its not working! Mahdi ROM is my daily driver and my backup! I'm thinking now it might be kernel issue. Do you think the kernel might be issue?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No its not working now! I meant my daily driver is Mahdi ROM and I use
Sent from my Nexus 5 using Tapatalk
When you flash the ROM it also flashes the kernel that comes with it.
So if you are using Mahdi ROM then everything is ok but if you try a different ROM you get the error constantly?
using the ClockworkMod recovery.
If you receive issues on flashing, double check your download. If nothing, I suggest using the ClockworkMod recovery.
mistahseller said:
When you flash the ROM it also flashes the kernel that comes with it.
So if you are using Mahdi ROM then everything is ok but if you try a different ROM you get the error constantly?
Click to expand...
Click to collapse
Yes
Sent from my Nexus 5 using Tapatalk
storm007 said:
If you receive issues on flashing, double check your download. If nothing, I suggest using the ClockworkMod recovery.
Click to expand...
Click to collapse
I switch to cwm and same issue! Its weird! I mean again today I flash 4 different ROMs and as soon as I get to setup same issue! Unfortunately phone has stopped!
Sent from my Nexus 5 using Tapatalk
freddienux74 said:
I switch to cwm and same issue! Its weird! I mean again today I flash 4 different ROMs and as soon as I get to setup same issue! Unfortunately phone has stopped!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Phone has stopped is related to your gapps
freddienux74 said:
I switch to cwm and same issue! Its weird! I mean again today I flash 4 different ROMs and as soon as I get to setup same issue! Unfortunately phone has stopped!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
The type of recovery you use will have no bearing on it, hundreds of people on here use twrp and cwm.
All I can suggest and it was suggested before is to wipe your phone completely and start over again. Something went wrong, clearly.