Am I doing something wrong, I have flashed a few custom ROMs on my nexus 7 and all works perfectly.
Yet I think I'm doing it right on my note, yet I haven't managed to get any of the custom ROMs to run without restarts, lag and other blips to happen, the only ROM that runs perfectly is my backup ICS stock with Hydra.
Basically I Boot into recovery
Wipe data, cache and davlik
Install ROM from zip
Reboot a few times
Use for a day or so
Sent from my Nexus 7 using xda app-developers app
THUDUK said:
Am I doing something wrong, I have flashed a few custom ROMs on my nexus 7 and all works perfectly.
Yet I think I'm doing it right on my note, yet I haven't managed to get any of the custom ROMs to run without restarts, lag and other blips to happen, the only ROM that runs perfectly is my backup ICS stock with Hydra.
Basically I Boot into recovery
Wipe data, cache and davlik
Install ROM from zip
Reboot a few times
Use for a day or so
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
What exactly are the roms you're mentioning? (I'm assuming 4.2.2 ones, right?) are you also flashing a custom kernel afterwards X or Y rom? which one?........ almost any rom has some (more) some (less) lag issues within it, and some others are known to happen random reboots with certain kernels... a little more information could help............ btw, you should try Chasmodo's Asylum, a pretty neat one in all aspects.
Just been out for a run and the Note restarted on my (thought was Trusty) ICS backup ROM, only thing I can think of is it seems to happen when accessing the Ext SD card, perhaps its where i have flashed a few different roms from CM10 to sammy etc...and they use the SD in different ways, so I have just formatted the Ext SD card and will try Chasmodos wonderful rom, does look good
Related
Running stable CM 7.0.3 with CWM 3.0.0.5
I've been getting some intermittent freezes waking from sleep, seems to be worse when the battery is getting low. Maybe it is a Launcher Pro issue? as that is my home and the culprit program when the Force Close or Wait dialogue pops up
I wanted to upgrade to v176 of our CM nightly to see if maybe that'd help but I can't seem to get past the white screen'd/green htc logo
Upgraded my CWM to latest ... nothing
Tried an Amon_RA recovery ... nothing
Re-downloaded latest gapps and tried multiple 'newer' roms multiple times ... nothing
Any ideas here? I used the two wipe everything scripts (only one works in CWM) multiple times before each effort to no avail
Restored from backup and I'm on 7.0.3 again but progress, even on this legacy device (thanks devs!) would be pretty sweet as I've been wanting to pitch it into a wall lately
...paitently waiting on the Epic Touch 4G or iPhone for Sprint, thanks all
mbarnwell said:
Running stable CM 7.0.3 with CWM 3.0.0.5
I've been getting some intermittent freezes waking from sleep, seems to be worse when the battery is getting low. Maybe it is a Launcher Pro issue? as that is my home and the culprit program when the Force Close or Wait dialogue pops up
I wanted to upgrade to v176 of our CM nightly to see if maybe that'd help but I can't seem to get past the white screen'd/green htc logo
Upgraded my CWM to latest ... nothing
Tried an Amon_RA recovery ... nothing
Re-downloaded latest gapps and tried multiple 'newer' roms multiple times ... nothing
Any ideas here? I used the two wipe everything scripts (only one works in CWM) multiple times before each effort to no avail
Restored from backup and I'm on 7.0.3 again but progress, even on this legacy device (thanks devs!) would be pretty sweet as I've been wanting to pitch it into a wall lately
...paitently waiting on the Epic Touch 4G or iPhone for Sprint, thanks all
Click to expand...
Click to collapse
I like to actually wipe instead of flashing a wipe. Try flashing the nightly on top of your current one, just wipe cache and dalvik cache before flashing.
Sent from my HTC Hero making C.R.E.A.M.
dastin1015 said:
I like to actually wipe instead of flashing a wipe. Try flashing the nightly on top of your current one, just wipe cache and dalvik cache before flashing.
Sent from my HTC Hero making C.R.E.A.M.
Click to expand...
Click to collapse
+1. I would go into recovery (I use CWM) and format system, cache, data, boot and then flash whatever rom you are trying to flash. Also, give it some time to boot up. Some roms can take a while. You can try the flashover too as Dastin suggested.
Are you using any tweaks like firerat's? There can be issues with that if your system partition is too small
Good luck!
That is a good idea
Keep rolling back versions of the ROM I want to try until something sticks.
Update the 'new' ROM to the latest version.
In the meantime, I've updated to CWM 4.0.1.5 and wiped everything possible at least twice. Plus a format all script. I will let you know if this does it for me
I still have not been able to flash any other roms, the only thing I can do is change recoveries and do nandroid restores. I am using the latest herodeck rom which is based on the CM roms. Hopefully someone will be able to help us.
And sorry about making a new post I was thinking that we were using different roms but I guess that they are actually pretty close to being the same.
since i first got my phone and flashed the first cm9 build and roms after that it all worked fine with no problems at all,, now within the past 2 months, for me to flash a custom rom like cm9/10 i have to flash stock rom, re-root, then flash the cm..
the problem is no matter what i do, complete wipe etc the rom installations always fail with a status 7 error about symlinks
winxuser said:
since i first got my phone and flashed the first cm9 build and roms after that it all worked fine with no problems at all,, now within the past 2 months, for me to flash a custom rom like cm9/10 i have to flash stock rom, re-root, then flash the cm..
the problem is no matter what i do, complete wipe etc the rom installations always fail with a status 7 error about symlinks
Click to expand...
Click to collapse
Change your recovery !
SnowPluralism @ XDA-Premium using S'periece (GT-I5830)
yeah tried that,, im no using px recovery and it still has problems,, i think its the issue of very little system space on the phone, eve nbefore i zip the rom up the system folder is only under 200mb but still doesnt like to install roms
winxuser said:
yeah tried that,, im no using px recovery and it still has problems,, i think its the issue of very little system space on the phone, eve nbefore i zip the rom up the system folder is only under 200mb but still doesnt like to install roms
Click to expand...
Click to collapse
Flash stock via odin & root back...
I used to have beautiful life before. Now I'm in engineering...!
ive tried them all and the only one i can get to boot is cm10-10121104-unofficial-maserati. all of the akop or asop roms with kexec will not boot on my device. no problems with any rom with stock kernel. im running hashcodes safe-strap 3.05.
I believe it only works with 2.01, not 3.x
Sent from my DROID4 using xda app-developers app
kexec definitely works with the newer safestrap. OP, you might want to:
1) Try doing a data wipe after installing the ROM
2) (Try doing a data wipe before installing the rom?)
3) Reinstalling Safestrap
4) Being more patient. I remember the first time I booted a kexec ROM I thought the thing just died. Eventually it came back to life. I doubt this is your case, but maybe you could a little trigger happy with the reboot key combo? :laugh:
Maybe try creating a new ROM slot, if you have just been trying one?
Hi
Ive been trying different cm7.2 based roms for the last few months (apocalypse,droidace etc etc) and yesterday i wanted to try one of the stock based roms (stocklite, stock on fire, stockrom evolution etc etc).
Ive had problems installing all three of them that i never had when i was flashin the cm7 ones. Phone doesnt boot after flashing them. just stuck. and ive given it a good 10-15 mins for the 1st boot...
Is it something im doing wrong? can i flash the stock ones if i was previously using cm7 roms? or do i have to do something before i flash em?
thanks
dblane79 said:
Hi
Ive been trying different cm7.2 based roms for the last few months (apocalypse,droidace etc etc) and yesterday i wanted to try one of the stock based roms (stocklite, stock on fire, stockrom evolution etc etc).
Ive had problems installing all three of them that i never had when i was flashin the cm7 ones. Phone doesnt boot after flashing them. just stuck. and ive given it a good 10-15 mins for the 1st boot...
Is it something im doing wrong? can i flash the stock ones if i was previously using cm7 roms? or do i have to do something before i flash em?
thanks
Click to expand...
Click to collapse
I'd recommend flashing a stock Samsung ROM via Odin first.
I go from Rom to Rom with out ever flashing with odin and never have boot loops or stuck but sometimes after flashing a Rom you have to reboot recovery an do a factory reset wipe that helps me when i get stuck in a boot loop hope it helps you too
Sent from my GT-S5830 using xda app-developers app
Wipe data/factory reset
Wipe cache
Wipe dalvik cache
Format system
And then try to install
If that doesnt work flash stock rom via odin and root and install cwm 5 again
Sent from Ace on CM 10.1
Dear all,
i have an old samsung galaxy exhibit 2 4g and decided to install a custom rom. i used below mentioned link for the ROMs.
http://forum.xda-developers.com/wiki/Samsung_Galaxy_Exhibit_4G
i have tried majority of the ROMs after v4 but all of them are giving me same problem
Phone hangs on incoming call and only vibrates no sound. and i have to ultimately pull the battery out.
the issue is not observed on stock ROM.
It is also not observed on REMICS 3.0.1 but only if i disable backup and restore option. disabled this option on other custom rom as well but did not fix the issue on other ROMs.
I would appreciate any help.
wonderwall_85 said:
Dear all,
i have an old samsung galaxy exhibit 2 4g and decided to install a custom rom. i used below mentioned link for the ROMs.
http://forum.xda-developers.com/wiki/Samsung_Galaxy_Exhibit_4G
i have tried majority of the ROMs after v4 but all of them are giving me same problem
Phone hangs on incoming call and only vibrates no sound. and i have to ultimately pull the battery out.
the issue is not observed on stock ROM.
It is also not observed on REMICS 3.0.1 but only if i disable backup and restore option. disabled this option on other custom rom as well but did not fix the issue on other ROMs.
I would appreciate any help.
Click to expand...
Click to collapse
sorry late on this. which cwm or twrp version are you using? jfbs twrp 2.7.1.0 or cwm 6.0.4.8 is the latest which is need on kk roms also cars1198 has cwm6.0.4.9. picking one of these 3 is user preference. for kk roms lastest slimbean 7/7build and dcm 6/20 by jfbs is stable and for cm11 cars1198 6/19 build is pretty stable. any of these 3 should work just fine without any issues with latest recoveries. if you dont know how its just like flashing a rom except when you reboot you want to reboot boot back into recovery then do a fresh install. also on a complete fresh install what ever is on on your internal sdcard that you want to keep move it to external sd or pc. then format /system /data /cache /android secure and /sdcard0. then install rom only, reboot and wait for it to fully boot up. then reboot back into recovery and install gapps. then wipe dalvik-cache and reboot. after you sign into gplay give the phone time to sync your contacts and so forth which will bog down the phone for 1-30mins or longer depending how much needs to be sync. after that you should be ready to go with no or very minor issues. in which you would ask in the appropriate rom op.
TripFX said:
sorry late on this. which cwm or twrp version are you using? jfbs twrp 2.7.1.0 or cwm 6.0.4.8 is the latest which is need on kk roms also cars1198 has cwm6.0.4.9. picking one of these 3 is user preference. for kk roms lastest slimbean 7/7build and dcm 6/20 by jfbs is stable and for cm11 cars1198 6/19 build is pretty stable. any of these 3 should work just fine without any issues with latest recoveries. if you dont know how its just like flashing a rom except when you reboot you want to reboot boot back into recovery then do a fresh install. also on a complete fresh install what ever is on on your internal sdcard that you want to keep move it to external sd or pc. then format /system /data /cache /android secure and /sdcard0. then install rom only, reboot and wait for it to fully boot up. then reboot back into recovery and install gapps. then wipe dalvik-cache and reboot. after you sign into gplay give the phone time to sync your contacts and so forth which will bog down the phone for 1-30mins or longer depending how much needs to be sync. after that you should be ready to go with no or very minor issues. in which you would ask in the appropriate rom op.
Click to expand...
Click to collapse
hey there,
thanks for the reply.
I am using cwm v6.0.1.2.
What i get from your reply is that
flash the latest recovery, reboot in to recovery again
flash your suggested ROM, fresh install
boot in to the OS
boot again in to recovery and install gapps
boot the phone and give it a couple of hours to sych data and update if any and then see if its working or not.
i will give it a try and will let you know. btw i was not facing any issues on any other roms except the mentioned issue and all the roms were running pretty fast.
wonderwall_85 said:
hey there,
thanks for the reply.
I am using cwm v6.0.1.2.
What i get from your reply is that
flash the latest recovery, reboot in to recovery again
flash your suggested ROM, fresh install
boot in to the OS
boot again in to recovery and install gapps
boot the phone and give it a couple of hours to sych data and update if any and then see if its working or not.
i will give it a try and will let you know. btw i was not facing any issues on any other roms except the mentioned issue and all the roms were running pretty fast.
Click to expand...
Click to collapse
everyones had different issues using older recoveries. cwm 6.0.4.4-5 works for anything jb or below. the higher ones are for kk roms which is the most recent and both cars and jfbs kk roms are better then aoip or any of the other roms. Since ion hybrid thanks to adc team and more stable kk roms are out now. imo any of cars is cm roms are good for the everyday people while jfbs slim and dcm are geared more to those who want more features and customization (advance users). i always test both devs roms but personally i like jfbs roms better as far as what i do but any of the 3 are stable for everyday use now. but ya let me know if that helped out.
TripFX said:
everyones had different issues using older recoveries. cwm 6.0.4.4-5 works for anything jb or below. the higher ones are for kk roms which is the most recent and both cars and jfbs kk roms are better then aoip or any of the other roms. Since ion hybrid thanks to adc team and more stable kk roms are out now. imo any of cars is cm roms are good for the everyday people while jfbs slim and dcm are geared more to those who want more features and customization (advance users). i always test both devs roms but personally i like jfbs roms better as far as what i do but any of the 3 are stable for everyday use now. but ya let me know if that helped out.
Click to expand...
Click to collapse
tried cynanogen1, worked smoothly but did not fix the issue
slimkat 4.4.4, faced FC every second. it was almost impossible to even boot the phone.
first i thought there is some hardware issue but the phone is working fine on 2 roms so i guess thats out of the question. let me know if you could suggest something else.
wonderwall_85 said:
tried cynanogen1, worked smoothly but did not fix the issue
slimkat 4.4.4, faced FC every second. it was almost impossible to even boot the phone.
first i thought there is some hardware issue but the phone is working fine on 2 roms so i guess thats out of the question. let me know if you could suggest something else.
Click to expand...
Click to collapse
which cwm or twrp version did you use. I too was facing the fc's on my phone for a while but after using twrp 3.7.1.0 or cwm 6.0.4.8 i dont have that issue anymore. my personal exact order including mods i use.
1. flash twrp 3.7.1.0 < if you already have this or cwm 6.0.4.8 already
2. Format /system then /cache, then /data/ then /internal sd < so everything except /boot and /external sd
3. flash rom < if doing cm11 you can flash oc kernel right after
4. flash supersu < optional its the same as stock superuser but little more options like allow su on boot (on xda)
5. wipe davlik cache and reboot system
6. reboot boot back into recovery
7. flash gapps < if slim get it from slimroms, if dcm or cm11 the gapps from cars1189 mass cm build 1-5-14.
8. flash malive booster < (on xda)
9. wipe dalvik cache and reboot system
10. once full loaded back in install seeder 2.0 (on xda) have a check mark on all 3 with light profile then enable.
11. then finish signing in google account and updating apps. 30mins later its smooth as butter.
TripFX said:
which cwm or twrp version did you use. I too was facing the fc's on my phone for a while but after using twrp 3.7.1.0 or cwm 6.0.4.8 i dont have that issue anymore. my personal exact order including mods i use.
1. flash twrp 3.7.1.0 < if you already have this or cwm 6.0.4.8 already
2. Format /system then /cache, then /data/ then /internal sd < so everything except /boot and /external sd
3. flash rom < if doing cm11 you can flash oc kernel right after
4. flash supersu < optional its the same as stock superuser but little more options like allow su on boot (on xda)
5. wipe davlik cache and reboot system
6. reboot boot back into recovery
7. flash gapps < if slim get it from slimroms, if dcm or cm11 the gapps from cars1189 mass cm build 1-5-14.
8. flash malive booster < (on xda)
9. wipe dalvik cache and reboot system
10. once full loaded back in install seeder 2.0 (on xda) have a check mark on all 3 with light profile then enable.
11. then finish signing in google account and updating apps. 30mins later its smooth as butter.
Click to expand...
Click to collapse
you are the MAN man. from your instructions i deduced that i was not wiping davlik cache after flashing but before. now every rom is working fine, no issue is observed. thanks
Since you know your stuff could you let me know which rom is the best in terms of performance and battery life?
thanks again
wonderwall_85 said:
you are the MAN man. from your instructions i deduced that i was not wiping davlik cache after flashing but before. now every rom is working fine, no issue is observed. thanks
Since you know your stuff could you let me know which rom is the best in terms of performance and battery life?
thanks again
Click to expand...
Click to collapse
Stock wise Slim has better performance over cm11 with slightly less bettery life. to get the best performance to battery life follow my oc guide i posted. you want to keep the voltage equal to or less then stock voltage while having the highest frequency as possible. the lower voltage from stock the higher battery life over stock will be. if you do plan on overclocking and undervolting your self make sure you read my oc entirely before attemping. the oc guide methodology is the same for anything that can overclock including desktop cpus, gpus, and yes some nics. some routers as long as it can support a 3rd party firmware such as ddwrt or openwrt. other phones that have oc and voltage control support. you may also get some extra performance and battery saving by trying different build.prop tweaks or mods or any of the combination. some may help you and not me and vise versa and some may help everyone. its more about find what works best for you for what you do.