Hey guys, this is my first time posting here after being a lurker for some time now. Got to say I love the NS, I'm coming from an iphone 3G. Had my phone since christmas. Of course I'm rooted, and I'm running NSCollab's ROM.
I decided to sign up because I have questions for him, but seeing how i cant post in the developer section yet, I need to rack up my 10 posts.
Now I'll probably transfer my question there if its not answered here, but here it goes.
So in his ROM which was running a RC2 and Netarchy's kernel 1.2.8, i had really long boot times. I saw that this was a problem with the kernel as some people mentioned in the thread. Then the ROM was upgraded to nightly #22 I believe with Netarchy's Kernel 1.3.0 which was supposedly suppose to rid of these boot times. I flashed the ROM, and the boot time was still very long. Now for his ROM i dont need to do a factory reset, but after i saw that i still had a very long boot time, I did that to see if it would work. I wiped cache and did a factory reset. THen flashed the ROM again. Same thing. Other people on that thread are reporting normal boot ups now.
Now there's another update thats running CM nightly #25 i believe with the same kernel, and he also added the dark launcher theme and dark camera theme. I do have that the dark camera theme, but the dark launcher theme isnt there, my launcher is still the normal color. Which I would probably prefer anyways.
Point is, why is my phone still have the long boot times, when its clearly been fixed for others? Sorry for the long explanation ahah
That long delay bug was introduced with kernel 1.2.9 (I think) & fixed in 1.3.0 since I have been moving from stable 1.2.5 to all of its successor to the eventual 1.3.0. If my conviction is correct, you shouldn't be seeing any boot time difference from 1.2.8 to 1.3.0 since you missed a hop in between. You may want to try wiping the cache, dalvik cache and battery stats by booting into recovery while you are on the same kernel.
really? Because I dont think GBcollab ever had 1.2.9 kernel on his ROM he went straight to 1.3.0. I'll try it doing what you said.
And is there an option for wiping battery stats in clockwork recovery? I've never seen that before. Also where do you wipe dalvik cache, i only see wipe cache in clockwork never dalvik cache.
tankmaster90 said:
really? Because I dont think GBcollab ever had 1.2.9 kernel on his ROM he went straight to 1.3.0. I'll try it doing what you said.
And is there an option for wiping battery stats in clockwork recovery? I've never seen that before. Also where do you wipe dalvik cache, i only see wipe cache in clockwork never dalvik cache.
Click to expand...
Click to collapse
The option to wipe battery stats is in the Advanced menu.
Even my boot times are very high. We are in the same boat Not its insanely long. Requires forever to boot up
suhas_sm said:
Even my boot times are very high. We are in the same boat Not its insanely long. Requires forever to boot up
Click to expand...
Click to collapse
I think i've seen you NS Collab's thread also, at least someone with your avatar.
Do you have the most recent version? I dont even have the dark launcher and dark camera theme. I dunno why I'm missing that.
Yep. I am there also
haha i just need my 10 posts to get there! Stupid rule haha
yay no i can ask!
Related
Hey all, long term lurker here posting, obviously, for the first time. I'm not sure whether this would be better placed in the general or q&a section, as it seems like a good portion of the general section consists of questions.
Anyways, on to the problem. I recently attempted to flash the mr1 version of CM7 and was greeted by a force close loop, with com.android.phone closing. This was after wiping the dalvik cache and all data before flashing the rom. I was actually getting into a bootloop before that, even thought the md5 of the rom matched up with the one posted. I had redownloaded the rom to try again, and managed to actually boot before running into this fc problem. I have no idea what could be causing this, and it would be great if anyone could offer up some ideas on potential fixes, or at least some insight into what might be going wrong.
What radio are you using?
As far as I know, the stock radio. I don't remember ever flashing anything other than some of the early thunderbolt cm7 builds. Radio version is 1.16.00.0223r.
You have the correct radio (you can use 223r or 402w for MR1 version). Did you wipe /data, /system, /cache, /dalvik-cache?
I believe I wiped all of those. I know for a fact that the dalvik cache got wiped, and I'm pretty sure I wiped /system and /cache
Dark_Rak3r said:
I believe I wiped all of those. I know for a fact that the dalvik cache got wiped, and I'm pretty sure I wiped /system and /cache
Click to expand...
Click to collapse
I'd recommend wiping and flashing back to a Froyo ROM (BAMF is always a good choice, just make sure its not one of the new Froyo mr2 ones), and then attempting to wipe and re-flash CM7. Sometimes these things just happen. If its just a little bug, this will fix it. If theres a deeper issue, we can do more to expose what exactly it is, but lets go in baby steps
MattBeyers said:
I'd recommend wiping and flashing back to a Froyo ROM (BAMF is always a good choice, just make sure its not one of the new Froyo mr2 ones), and then attempting to wipe and re-flash CM7. Sometimes these things just happen. If its just a little bug, this will fix it. If theres a deeper issue, we can do more to expose what exactly it is, but lets go in baby steps
Click to expand...
Click to collapse
I'd agree but me personally I'd just do a wipe of /system, /data, /cache, /dalvik-cache and reload the ROM fresh over a clean system. Once you do that and load up gapps see if you have any issues before reloading apps. It wouldn't hurt to return to a FroYo ROM just to make sure things are good though as well.
Try clearing data on contacts storage, phone, and media storage, for some reason one of those worked for me
Thanks, I'll try your suggestions and see if they get anywhere. @MattBeyers, I'm currently on the stock sense rom (or whatever you end up on after rooting), so would you suggest I flash another froyo rom or should I just go ahead and try a wipe and then reflash cm7?
EDIT: Well something worked. Seems like I'm good to go, although I'm not really sure if anything changed in what I did to try and get cm7 running this time. Thanks for your help guys, and hopefully I won't run into any more problems here.
I have just recently begun modding my G2x. I can install ROMs without any problems but I've since been interested in flashing a custom kernel. Information is sort of everywhere and what I do manage to find I am worried about it being out-of-date. Anyway, I flashed cm7.1 (the stable release) and it worked fine until it started fc-ing everything google related (something to do with sync?). I decided to try flashing kernels (wiping caches as instructed) and could never get one to work. I've since flashed the latest cm nightly (201 I think) and tried trinity with it. Still nothing. I've since read that I should let the phone sit for 10-20 minutes but after about 20 minutes it is just a black screen and nothing ever happens. It does get really hot however. Anyway I have tried flashing kernels multiple times and nothing has ever worked, same story every time. Any way somebody could tell me what I'm doing wrong? Tell me what's compatible (as maybe sorta stable) with the ROMs I'm using? HAHA and if it's not asking too much...maybe some links too? Sorry, just very new to this and very eager to learn. I just have a bit of trouble figuring out what's supposed to be compatible and where to find it. THANKS!
Start over fresh, wipe data x 2, wipe system x 2, wipe cache, wipe dalvik cache, flash cm7 nightly, dont reboot yet, wipe cache ONLY, wipe dalvik cache ONLY, flash kernel try faux123 (make sure kernel is for cm7) latest or morfic latest, reboot, enjoy ....
NVIDIA NEVER AGAIN!
fcisco13 said:
Start over fresh, wipe data x 2, wipe system x 2, wipe cache, wipe dalvik cache, flash cm7 nightly, dont reboot yet, wipe cache ONLY, wipe dalvik cache ONLY, flash kernel try faux123 (make sure kernel is for cm7) latest or morfic latest, reboot, enjoy ....
NVIDIA NEVER AGAIN!
Click to expand...
Click to collapse
Thanks will give it a shot in the morning. Too much of a headache all day. Back in a useable state and I want to keep it that way for a bit haha. Will post results.
I still haven't tried to flash a new kernel... that is coming in a bit. I do have a question though... I'm interested in getting my phone in the cleanest state possible before doing anything further. I basically want my external sd cleaned up (I want to just reformat it) before flashing a rom again. What files/directories are absolutely essential to keep? As I said, I want to just wipe it clean but I'm not sure I can do that.
Sent from my LG-P999 using XDA App
So just to be thorough I can safely remove the cwm directory as well? Just delete it all put my rom and kernel zips back and I'm good?
Sent from my LG-P999 using XDA App
Make sure you flashed recovery through nvflash
NVIDIA NEVER AGAIN!
Tried to just flash 0.4.7 and it did the same thing as before. Waited 20 minutes before taking out the battery then tried to boot it again. Waited 20 more minutes and all it ever did both times was get hot. Same results as before.
Sent from my LG-P999 using XDA App
OK that's what I was missing. Needed to be running SV. Anyway it's working now just fine. Muuuch appreciated.
Sent from my LG-P999 using XDA App
Sorry, I'm new and I understand this is where I have to post. I hope that's right. I've looked everywhere and none of the other posters' responses have helped me.
I have a p7510 which for the moment is rooted stock. I've used other ROMs: AOKP, CM9, CleanROM. They all work fine but recently I tried CM10 and eventually another AOSP JB ROM because I was desperate to exhaust every option. I know about wiping cache, Dalvik and data and formatting system so that's not the issue. I've also switched recoveries and recovery versions, reflashed stock and rerooted, tried again and again between wipes-- I even started to wonder if maybe I just wasn't patient enough but I waited over an hour with no results. Whats the deal here?
I've got the same freakin' problem on my Wildfire S w/ CM9 alpha 7-rom. Bootscreen for over an hour. Cleared cache, installed rom and then gapps with CWM. Starting to wonder if it's the hboot or something.
An answear for what we noobes (maybe just speaking for myself ) is doing wrong, would be fine :good:
(Would have posted this in the developers thread, but i got >10 posts on XDA...)
kailehu said:
Sorry, I'm new and I understand this is where I have to post. I hope that's right. I've looked everywhere and none of the other posters' responses have helped me.
I have a p7510 which for the moment is rooted stock. I've used other ROMs: AOKP, CM9, CleanROM. They all work fine but recently I tried CM10 and eventually another AOSP JB ROM because I was desperate to exhaust every option. I know about wiping cache, Dalvik and data and formatting system so that's not the issue. I've also switched recoveries and recovery versions, reflashed stock and rerooted, tried again and again between wipes-- I even started to wonder if maybe I just wasn't patient enough but I waited over an hour with no results. Whats the deal here?
Click to expand...
Click to collapse
o-l-a-v said:
I've got the same freakin' problem on my Wildfire S w/ CM9 alpha 7-rom. Bootscreen for over an hour. Cleared cache, installed rom and then gapps with CWM. Starting to wonder if it's the hboot or something.
An answear for what we noobes (maybe just speaking for myself ) is doing wrong, would be fine :good:
(Would have posted this in the developers thread, but i got >10 posts on XDA...)
Click to expand...
Click to collapse
Did you do the following? In order and full:
Make a backup
Format data
Format system
Format cache
Format dalvik cache
Factory Reset
Install ROM .zip file
Install the latest (unless otherwise specificed) gapps .zip
, but as you stated, you've supposedly done all of that. The only other thing I can think of is that the ROM might be corrupt and cause a bootloop. Look at the dev thread to see if others are experiencing the same issue. Also i'd recommend TWRP instead of CWM.
I've got the same freakin' problem on my Wildfire S w/ CM9 alpha 7-rom. Bootscreen for over an hour. Cleared cache, installed rom and then gapps with CWM. Starting to wonder if it's the hboot or something.*An answear for what we noobes (maybe just speaking for myself ) is doing wrong, would be fine*(Would have posted this in the developers thread, but i got >10 posts on XDA...)
Click to expand...
Click to collapse
I'm sorry to hear that but I'm also glad it's not just me, and wouldn't be a huge stretch to call me a newb.
Did you do the following? In order and full:
Make a backup
Format data
Format system
Format cache
Format dalvik cache
Factory Reset
Install ROM .zip file
Install the latest (unless otherwise specificed) gapps .zip
, but as you stated, you've supposedly done all of that. The only other thing I can think of is that the ROM might be corrupt and cause a bootloop. Look at the dev thread to see if others are experiencing the same issue. Also i'd recommend TWRP instead of CWM.
Click to expand...
Click to collapse
Unfortunately, I've tried both recoveries already. I've gone through each step every time and I've never done it that specific order consciously, but I feel like I must have just by chance in all the times I've tried this. I'll try again though exactly like you listed and see what happens. Thanks.
No dice. I'd like to give more info than that but I don't know what else to try.
Hi all, first time poster! I was going to post in the development section (CM10 releases) but since I'm a new user, I came here
I just had a few questions about the 8/25 nightly and flashing new ones in general.
The first time, I was on stock (rooted, unlocked), went to CWR, flashed both nightly & gapps without doing a fact reset.
Didn't exactly put me in a bootloop, but it would go to a nexus 7 bootscreen (which I had installed myself, I think), and it would continue forever without visually appearing to loop to boot animation. So maybe it was a bootloop, but the animation just seemed to continue smoothly without any visual glitches...forever. If that made sense. Since it smoothly loops in the first place, I thought a bootloop might make the loop irregular etc. OKAY MOVING ON.
I got back into recovery mode, did a factory reset, wiped the cache partition, flashed everything, then booted it up...and it worked (thank god, no $600 brick)! But for some reason it showed the CM9 boot animation for some reason. Is this what's supposed to happen?
Also, when I flash new nightlies, will I have to factory reset every time? Is there anything else a noob might have to know about CM10, flashing, etc that isn't immediately obvious?
Thanks a lot for your time (fantastic noob video, by the way, and I apologize for my lack of brevity but I try to make up for it with sincerity in thanks)! Any help is greatly appreciated!
It still has the cm9 boot animation(doesnt bother me) it will get updated soon for the cm10 bootanimation. I think you can flash the cm10 bootanimation. You don't have to factory reset every nightly but you mightrun into problems if you dont. for sure wipe dalvik and cache every nightly.For now i would factory reset every nightly because they are still changing alot of things.
Gotcha! Thanks, yeah at first I just went WTF because I thought I had flashed the wrong ROM ^^;;
Hope I'm able to find a stable version then so I can at least get set up and back up my apps etc before having to fact reset for the next nightly haha.
Another issue I was having on stock TW was that for some reason installing third-party apps would be impossible--I could click on cancel but not on install when the package installer screen came up. Flashing CM10 actually fixed this
I forgot to wait 10 minutes after a rom install! I got a bit excited Do I have to reinstall the rom or anything? Does this cause any long term issues?
Not sure what you are talking about.
Sent from my Nexus 5 using XDA Premium App
It is likely that your version of TWRP is old or if you are installing android L preview it takes a while.
you don't have to wait for anything.. once its done, its done.
Is this like the wait parents make kids go through before they can open their Xmas presents?
Some KK stock based ROMs have rubbish updater-scripts that leave the ROM "formatting" for about 10 minutes. Not sure if this is what is being referred to as this is not technically after a ROM install.
That said, no idea what he is talking about otherwise
Hello guys! Thanks for responding super fast.
Im taking about the the "10min" wait that some developers say to have after first booting up a rom. Ive heard it was for all the little bugs and stuff to get worked out, so i should leave the phone alone. I forgot to wait this 10 minutes so i was wondering what would happen.
Yes, I remember the wait 10 minutes from my S2.
You don't see that recommended anymore. ?
Raymondlikesroot said:
I forgot to wait 10 minutes after a rom install! I got a bit excited Do I have to reinstall the rom or anything? Does this cause any long term issues?
Click to expand...
Click to collapse
WHAT HAVE YOU DONE?!?!?!??!?!
Just kidding, nah, you're fine. Like the post above me, the 10mins is more of a 'settling period'/recommendation than anything.
I remember rooting my Evo 4G and installing Cyanogenmod 7, not reading all the way through and neglecting to install Gapps: ".....where's my Gmail???? Uh oh, I think it's broken forever...." Ah, those early days of rooting and flashing, I remember them well
I think our modern processing speeds on these devices have eliminated the need for waiting. Just my guess. ?
Raymondlikesroot said:
Hello guys! Thanks for responding super fast.
Im taking about the the "10min" wait that some developers say to have after first booting up a rom. Ive heard it was for all the little bugs and stuff to get worked out, so i should leave the phone alone. I forgot to wait this 10 minutes so i was wondering what would happen.
Click to expand...
Click to collapse
The only 10 minute wait I have heard of is waiting for Dalvik Cache to rebuild before getting to homescreens. I have never seen a developer recommend waiting 10 minutes after booting... The first Android ROM I flashed was 1.5 Cupcake - so i'm not particularly new to this either :/
Every S2 t989 rom used to have the wait 10 minutes step after first boot. Lol I rarely did... Maybe 5.
KJ said:
Every S2 t989 rom used to have the wait 10 minutes step after first boot. Lol I rarely did... Maybe 5.
Click to expand...
Click to collapse
I wonder if that was one of those "bad rumours" that started like wiping Battery stats... That fooled "developers" and developers alike.
rootSU said:
I wonder if that was one of those "bad rumours" that started like wiping Battery stats... That fooled "developers" and developers alike.
Click to expand...
Click to collapse
like wiping dalvik when flashing a ROM, or better wiping dalvik to flash a kernel.
simms22 said:
like wiping dalvik when flashing a ROM, or better wiping dalvik to flash a kernel.
Click to expand...
Click to collapse
Hah yeah.
My favourite is "wipe data, wipe dalvik if coming from a new ROM".. Well duh, wiping data wipes dalvik anyway.
I never wipe dalvik myself, but many updater-scripts I end up using do
rootSU said:
Hah yeah.
My favourite is "wipe data, wipe dalvik if coming from a new ROM".. Well duh, wiping data wipes dalvik anyway.
I never wipe dalvik myself, but many updater-scripts I end up using do
Click to expand...
Click to collapse
flashing the rom automatically wipes dalvik
rootSU said:
I wonder if that was one of those "bad rumours" that started like wiping Battery stats... That fooled "developers" and developers alike.
Click to expand...
Click to collapse
Very likely. Lol
simms22 said:
flashing the rom automatically wipes dalvik
Click to expand...
Click to collapse
Depends on the updater-script. Some do, some dont.
Some kernel devs recommend to wait 5-10min after flashing their kernel for the first time (like Uber).
1. For best results a install these kernel after a fresh ROM install (although it still should work if you don't do that)
2. Reboot into recovery (needs to be N5 AOSP 4.4.4 compatible)
3. Flash Kernel Zip
4. Reboot and let Settle for ~10 minutes (optional but recommended)
5. Navigate to system/etc/uber_v1.3.cfg using your favorite root file browser and change values based on descriptions to whatever you want.
6. Enjoy!!!
Click to expand...
Click to collapse
When I had my Note 3, a lot of devs recommended that you flashed and let the ROM settle for 10mins or so before setting up. I never used to bother (still don't) It can settle once it's set up and goes into deep sleep.