Related
There are a few users having problems flashing the recent CM7 nightlies. Here is my scenario.
I'm running CM7.0.2 from EMMC. Last night I tried to flash N63. Downloaded the zip from here...http://mirror.teamdouche.net/?device=encore (where I always get them from). Rebooted to recovery, wiped cache and dalvik and installed the zip. Clicked reboot & got stuck at "ANDROID_". I did a hard reboot (holding down power). Booted back to recovery and did a full wipe (system, data, cache, and dalvik)...Installed the zip again, rebooted and same results. I tried re-downloading the mirror and I've tried installing it with my recovery sd. Everything yields the same results......"ANDROID_".
I can reboot to recovery, and load my nandroids (7.0.0, 7.0.2, Nookiecomb, and Phiremod), however I cannot get one of the new nightlies to flash. I have seen other people are having similar issues so I've started this thread in the hopes of resolving this. I have been working on this problem and searching XDA / Google and still no luck.
hockeyfamily737 said:
There are a few users having problems flashing the recent CM7 nightlies. Here is my scenario.
I'm running CM7.0.2 from EMMC. Last night I tried to flash N63. Downloaded the zip from here...http://mirror.teamdouche.net/?device=encore (where I always get them from). Rebooted to recovery, wiped cache and dalvik and installed the zip. Clicked reboot & got stuck at "ANDROID_". I did a hard reboot (holding down power). Booted back to recovery and did a full wipe (system, data, cache, and dalvik)...Installed the zip again, rebooted and same results. I tried re-downloading the mirror and I've tried installing it with my recovery sd. Everything yields the same results......"ANDROID_".
I can reboot to recovery, and load my nandroids (7.0.0, 7.0.2, Nookiecomb, and Phiremod), however I cannot get one of the new nightlies to flash. I have seen other people are having similar issues so I've started this thread in the hopes of resolving this. I have been working on this problem and searching XDA / Google and still no luck.
Click to expand...
Click to collapse
Ok, not a very experienced dev or anything that here. And I have not experienced this problem myself, but a few ideas to throw out:
- Are you trying to install an OC kernel after nightly, or not b4 getting stuck?
- Maybe restore 7.0.x reboot, make sure it comes back. Back into recovery, flash nightly with just a cache wipe, see if it comes up.
Ronin3178 said:
Ok, not a very experienced dev or anything that here. And I have not experienced this problem myself, but a few ideas to throw out:
- Are you trying to install an OC kernel after nightly, or not b4 getting stuck?
- Maybe restore 7.0.x reboot, make sure it comes back. Back into recovery, flash nightly with just a cache wipe, see if it comes up.
Click to expand...
Click to collapse
No OC kernel....Just trying to get the nightly to run before worrying about that. I can nanadroid back to any of my former roms with no problem. I'm going to try just doing a ONLY a cache wipe and load it again......just as soon as I run out of patience with my black "ANDROID_" screen of frustration, I'm currently looking at for the last 7 minutes.
Ronin3178 said:
Ok, not a very experienced dev or anything that here. And I have not experienced this problem myself, but a few ideas to throw out:
- Are you trying to install an OC kernel after nightly, or not b4 getting stuck?
- Maybe restore 7.0.x reboot, make sure it comes back. Back into recovery, flash nightly with just a cache wipe, see if it comes up.
Click to expand...
Click to collapse
Yeah........It's a no go. Nand back to 7.0.2, reboot to recovery, wipe cache only, instal zip for Nightly 63......."ANDROID_".....DAMMIT!!!!
I'm back to 7.0.2 again until someone has something else I can try.
Are you using cwm recovery 3.0.2.8?
Could be an issue if not.
Sent from my NookColor using Tapatalk
ansleyj44 said:
Are you using cwm recovery 3.0.2.8?
Could be an issue if not.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Interesting... I'm using 3.0.1. I'll try updating it tonight.
sent from my Ginger-Hero CDMA
ansleyj44 said:
Are you using cwm recovery 3.0.2.8?
Could be an issue if not.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Good call!!! I flashed Clockwork 3.0.2.8 and all is good. Flashed nightly 63 with no problems. Thanks!
sent from my Ginger-Hero CDMA
Just another quick note.....To anyone having problems overclocking the new nightly builds. You need to use the ext. 4 overclock kernel, which can be downloaded here......http://forum.xda-developers.com/showthread.php?t=925451&page=239
hockeyfamily737 said:
Good call!!! I flashed Clockwork 3.0.2.8 and all is good. Flashed nightly 63 with no problems. Thanks!
sent from my Ginger-Hero CDMA
Click to expand...
Click to collapse
Nevermind.
janko10 said:
Is there a way to update CWM without burning a new image to SD card? I currently have 3.0.1.0 as well and I don't want to wipe my rom or SD card just to update to 3.0.2.8 but I can't seem to find any other way to do that.
Sorry but this is my first Andriod device so bit of a noob here.
Click to expand...
Click to collapse
I was going to say ROM Manager, but forgot it doesn't have 3.0.2.8 for Nook.
Here is the recovery zip file, flash from CWR. http://db.tt/gDlb5mw
- download to your SD card for Nook, boot into CWR, choose install zip from SD/choose zip, flash, reboot recovery
I've been downloading some custom roms off of the chinese forums, but many of them don't have google apps. If I can't sync my contacts and calender to gmail, I won't use the rom.
I downloaded GAPPS, which is meant to go with Cyanogenmod. I flashed it through recovery, but it didn't work.
I'd really like to use some of these Chinese roms, like V7, but I have to have GAPPS.
When installing any ROM I'm fairly sure you do it in this order:
1. Backup
2. Wipe Data/Factory reset
3. Flash ROM
4. Manually mount /system
5. Flash GAPPS
6. Wipe Dalvik and Batterystats (optional)
7. Reboot
I have done it this way with the CM6 and CM7 ROMS and GAPPS works fine for me.
Yes need to mount /system manually before flashing, probably need to install GAPPS before first boot.
Some devs put the GAPPS for their ROM on the forum also. Like Genokolar. You can look at the ROM post for instructions.
Ok. How do you manually mount the system?
@simplistian: where he posts the gaps? i can only find something called gms! or thats it?
http://bbs.goapk.com/thread-2280290-1-1.html
iakoboss7 said:
@simplistian: where he posts the gaps? i can only find something called gms! or thats it?
http://bbs.goapk.com/thread-2280290-1-1.html
Click to expand...
Click to collapse
Yes it is GMS. Flash it after you flash the ROM before the first boot. No need to mount /system.
typci said:
Ok. How do you manually mount the system?
Click to expand...
Click to collapse
With a custom recovery. There is an option of mounting different partitions.
Simplistian, thanks. You've been a great help. I'm going to stick with the B136 for now, and it runs great, and handles high end games without any problems. Next time I flash, I'll probably go with genokolar's V7 like you recommended.
please HELP
i installed franco kernel #156 and after restart no WIFI , if i press the wifi it wont turn on.
now i tried to reflash back to #147 what i had befor..but still no wifi
someone have any idea?
Diymantion said:
please HELP
i installed franco kernel #156 and after restart no WIFI , if i press the wifi it wont turn on.
now i tried to reflash back to #147 what i had befor..but still no wifi
someone have any idea?
Click to expand...
Click to collapse
1. Wipe cache, dalvik and system in recovery
2. Reflash the ROM, GApps, Franco kernel
3. Reboot
Pipusz said:
1. Wipe cache, dalvik and system in recovery
2. Reflash the ROM, GApps, Franco kernel
3. Reboot
Click to expand...
Click to collapse
1: if i wipe this things something in the device will be wiped?
2: i didnt flashed a rom only a kernel..i'm on stock ..damn i dont even know what is Gapps
Diymantion said:
1: if i wipe this things something in the device will be wiped?
2: i didnt flashed a rom only a kernel..i'm on stock ..damn i dont even know what is Gapps
Click to expand...
Click to collapse
1. Your internal storage will not be deleted.
2. GApps is the Google Play store apk file. It's a flashable file.
Have you tried turning wifi on through the settings menu and not in the notification drawer?
Try wiping cache and dalvik, then fix permissions and reboot.
scream4cheese said:
1. Your internal storage will not be deleted.
2. GApps is the Google Play store apk file. It's a flashable file.
Have you tried turning wifi on through the settings menu and not in the notification drawer?
Click to expand...
Click to collapse
1 : ofcourse i tried from the settings wont turn on
2: this GApps is a file that is good to any rom,stock? or i need something file for the stock?
i tired to fix permission and dell this things you told me but still no luck.
edit : i installed the first kernel (franco.Kernel-r147+Prima+FauxSoundControl) ..now the thing is that in franco app is shows that it is r148 and not 147) and WIFI working.
now that means i cant ever upgrade franco kernel?
thanks for all your help
Diymantion said:
1 : ofcourse i tried from the settings wont turn on
2: this GApps is a file that is good to any rom,stock? or i need something file for the stock?
i tired to fix permission and dell this things you told me but still no luck.
edit : i installed the first kernel (franco.Kernel-r147+Prima+FauxSoundControl) ..now the thing is that in franco app is shows that it is r148 and not 147) and WIFI working.
now that means i cant ever upgrade franco kernel?
thanks for all your help
Click to expand...
Click to collapse
Not sure, but maybe there is a difference in the ramdisk and that's why wifi hasn't functioned.
Pipusz said:
Not sure, but maybe there is a difference in the ramdisk and that's why wifi hasn't functioned.
Click to expand...
Click to collapse
What Do your Mean difference in the ramdisk?
What i need to Do?
Some developers provide a reset kernel if coming from a kernel such as franco which makes ramdisk modifications.
If not you can do a full wipe and flash the whole ROM again with kernel and then flash the kernel of your choice.
u don't need to wipe all.
just flash this revert: http://forum.xda-developers.com/attachment.php?attachmentid=1951201&stc=1&d=1368195077
wipe cache and dalvik and reboot.
now u can flash m3 and have the wifi working.
I updated my phone to latest liquidsmooth rom two days ago and the phone freezes and restarts/reboots randomly like sometimes when im on phone/ playing a game/ using browser/ connected to charger. Yesterday I changed rom to latest carbon rom. Did install (3 wipes) as told in the thread but im still having the reboots.
Im using TWRP recovery and had used Utility 1.10 to go back to stock from Energy rom with safestrap recovery.
Can tell me whats the prob? Is it the kernel problem?
Have you tried upgrading or reflashing TWRP and then doing a clean install of Carbon? Its probably worth doing a fresh download of each first just to make sure you cover all your bases. These reboots were happening to me a few months ago and it drove me mad. following these steps fixed it for me.
jcxmej said:
I updated my phone to latest liquidsmooth rom two days ago and the phone freezes and restarts/reboots randomly like sometimes when im on phone/ playing a game/ using browser/ connected to charger. Yesterday I changed rom to latest carbon rom. Did install (3 wipes) as told in the thread but im still having the reboots.
Im using TWRP recovery and had used Utility 1.10 to go back to stock from Energy rom with safestrap recovery.
Can tell me whats the prob? Is it the kernel problem?
Click to expand...
Click to collapse
Honestly, if you're using SafeStrap, that might be your problem. Remove SS and flash the ROM in TWRP. If your bootloader is unlocked, you don't really want to use SS. Also, make a stock backup in TWRP, prior to flashing. This way, it will be easier for you to recover in the future, and you won't need to go through the painful process of fastboot.
RikRong said:
Honestly, if you're using SafeStrap, that might be your problem. Remove SS and flash the ROM in TWRP. If your bootloader is unlocked, you don't really want to use SS. Also, make a stock backup in TWRP, prior to flashing. This way, it will be easier for you to recover in the future, and you won't need to go through the painful process of fastboot.
Click to expand...
Click to collapse
Like I said on first post Im using TWRP now. Previously I was using safestrap. I removed it and installed TRWP. Anyways thanks.
PantherVT said:
Have you tried upgrading or reflashing TWRP and then doing a clean install of Carbon? Its probably worth doing a fresh download of each first just to make sure you cover all your bases. These reboots were happening to me a few months ago and it drove me mad. following these steps fixed it for me.
Click to expand...
Click to collapse
Thanks man. I will upgrade TWRP or reinstall it first. Thanks for that tip. Will post again if it doesnt work.
Still having those restarts. Really irritating. Froze and rebooted 4 5 times today morning while I was on call and trying to message. I reflashed reinstalled everything. I used both Utility 1.10 and 1.20. Im getting reboots even the stock ROM after using the Utility. I am confused which Utility I should be using. I had no issue of rebooting before flashing using Utility. Can someone give me exact procedure to reflash so that i know i am not missing out anything.
jcxmej said:
Still having those restarts. Really irritating. Froze and rebooted 4 5 times today morning while I was on call and trying to message. I reflashed reinstalled everything. I used both Utility 1.10 and 1.20. Im getting reboots even the stock ROM after using the Utility. I am confused which Utility I should be using. I had no issue of rebooting before flashing using Utility. Can someone give me exact procedure to reflash so that i know i am not missing out anything.
Click to expand...
Click to collapse
you might need to do a clean install.
- what version of TWRP are you using (anything other than 2.4 should be fine)?
- to perform the clean install, mount system, then try wiping everything (system, factory reset, & internal storage) - DO NOT WIPE external SD (I presume this is where you store the ROM files
- after wiping, reboot recovery, then install whichever 4.2.2 ROM you want follow by the GApps (use the 3/2013 version)
jco23 said:
you might need to do a clean install.
- what version of TWRP are you using (anything other than 2.4 should be fine)?
- to perform the clean install, mount system, then try wiping everything (system, factory reset, & internal storage) - DO NOT WIPE external SD (I presume this is where you store the ROM files
- after wiping, reboot recovery, then install whichever 4.2.2 ROM you want follow by the GApps (use the 3/2013 version)
Click to expand...
Click to collapse
Since TWRP wasnt working for me, I tried flashing with CWM recovery by hashcode. Still had reboots. I was using TWRP 2.3.2.3
When you say wipe everything, does it include 'modem' and 'pds'? Saw these two options also inside Mount/Format menu of CWM recovery.
Also there was an option 'Mount sdcard' (internal I suppose) but when i click it nothing happens it remains as Mount sdcard. Rest of it changes from Mount to Unmount. Is there some problem with that?
Do I have to just Mount system only? Also after rebooting recovery do I have to mount system again?
I try again as you said meanwhile.
jcxmej said:
Since TWRP wasnt working for me, I tried flashing with CWM recovery by hashcode. Still had reboots. I was using TWRP 2.3.2.3
When you say wipe everything, does it include 'modem' and 'pds'? Saw these two options also inside Mount/Format menu of CWM recovery.
Also there was an option 'Mount sdcard' (internal I suppose) but when i click it nothing happens it remains as Mount sdcard. Rest of it changes from Mount to Unmount. Is there some problem with that?
Do I have to just Mount system only? Also after rebooting recovery do I have to mount system again?
I try again as you said meanwhile.
Click to expand...
Click to collapse
nope, just system/factory reset/internal storage.
yes, make sure everything is mounted (checked) so that they read "unmount"
jco23 said:
nope, just system/factory reset/internal storage.
yes, make sure everything is mounted (checked) so that they read "unmount"
Click to expand...
Click to collapse
Did exactly like said. Got into CWM recovery. Mounted system. Formatted system, data, cache, sdcard. Did factory reset and wiped the caches. Then rebooted recovery. Then installed the ROM, 3/13 gapps, gsm fix. Reboot system. Still no use. I got 2 reboots in 5 mins in the ROM. I checked the md5 of the files and its ok. Dont know what else to try?
jcxmej said:
Did exactly like said. Got into CWM recovery. Mounted system. Formatted system, data, cache, sdcard. Did factory reset and wiped the caches. Then rebooted recovery. Then installed the ROM, 3/13 gapps, gsm fix. Reboot system. Still no use. I got 2 reboots in 5 mins in the ROM. I checked the md5 of the files and its ok. Dont know what else to try?
Click to expand...
Click to collapse
which ROM are you trying to install?
jco23 said:
which ROM are you trying to install?
Click to expand...
Click to collapse
LiquidSmooth v2.9 by DHacker29
http://forum.xda-developers.com/showthread.php?t=2373703
I have also tried Carbon ROM but was having reboots with that too. I liked liquidsmooth better so trying to make this work.
jcxmej said:
LiquidSmooth v2.9 by DHacker29
http://forum.xda-developers.com/showthread.php?t=2373703
I have also tried Carbon ROM but was having reboots with that too. I liked liquidsmooth better so trying to make this work.
Click to expand...
Click to collapse
are you flashing a kernel at the same time?
I would recommend trying a basic 4.2.2 ROM right now - like unoffical AOKP.
another problem could be the GApps or GSM fix. try installing just the ROM without the GApps perhaps?
carbon was very solid too. unfortunately, I can't help you with the GSM fix, as I am CDMA.
jco23 said:
are you flashing a kernel at the same time?
I would recommend trying a basic 4.2.2 ROM right now - like unoffical AOKP.
another problem could be the GApps or GSM fix. try installing just the ROM without the GApps perhaps?
carbon was very solid too. unfortunately, I can't help you with the GSM fix, as I am CDMA.
Click to expand...
Click to collapse
Okay i will try but had this reboot issue even with the stock ROM after flashing with Utility 1.20.
jcxmej said:
Okay i will try but had this reboot issue even with the stock ROM after flashing with Utility 1.20.
Click to expand...
Click to collapse
hmm.... not really sure then. perhaps you lost root? try re-installing SuperSU - I'm just grasping at straws here.
someone mentioned a similar issue:
http://forum.xda-developers.com/showthread.php?p=44317692#post44317692
jco23 said:
hmm.... not really sure then. perhaps you lost root? try re-installing SuperSU - I'm just grasping at straws here.
someone mentioned a similar issue:
http://forum.xda-developers.com/showthread.php?p=44317692#post44317692
Click to expand...
Click to collapse
I think I have root access I had no issue with it. Okay maybe I will check the thread you gave. Anyways I tried Eclipse ROM which is based AOKP. Still had reboots. So I switched back to liquid. Anyways Im gonna keep trying the basics. If anyone has any suggestions I could try its welcome.
PS. Should I flash another kernel with the ROM just in case ? I have been only installing ROM and gapps only till now.
jcxmej said:
I think I have root access I had no issue with it. Okay maybe I will check the thread you gave. Anyways I tried Eclipse ROM which is based AOKP. Still had reboots. So I switched back to liquid. Anyways Im gonna keep trying the basics. If anyone has any suggestions I could try its welcome.
PS. Should I flash another kernel with the ROM just in case ? I have been only installing ROM and gapps only till now.
Click to expand...
Click to collapse
I don't think changing the kernel will do it.... I suspect the issue is with your recoveries - will respond in other thread....
CM11 doesn't seem to have root. I've flashed the latest nightly and for whatever reason, it just doesn't want to work right. Can't delete installed apps, can't remount, or anything...I can't be the only one can I?
RavenII said:
CM11 doesn't seem to have root. I've flashed the latest nightly and for whatever reason, it just doesn't want to work right. Can't delete installed apps, can't remount, or anything...I can't be the only one can I?
Click to expand...
Click to collapse
Probably, the problem is the app you're trying to use...
RavenII said:
CM11 doesn't seem to have root. I've flashed the latest nightly and for whatever reason, it just doesn't want to work right. Can't delete installed apps, can't remount, or anything...I can't be the only one can I?
Click to expand...
Click to collapse
Did you install a custom kernel after flashing the rom?
diogo.sena said:
Probably, the problem is the app you're trying to use...
Click to expand...
Click to collapse
It's got to be a system thing, even adb won't remember when I authorize my computer....
jrosetto said:
Did you install a custom kernel after flashing the rom?
Click to expand...
Click to collapse
Negative, stock kernel. Clean install...
My suggestion is to get the latest TWRP or CWM and factory reset, wipe system, and delvik cache. Then flash the rom again. It is possible you also have a corrupted download. Use an MD5 checker on the ZIP to make sure it isn't corrupted. If you don't want to start over you can also flash the auto root from chainfire from this link.
http://download.chainfire.eu/297/CF-Root/CF-Auto-Root/CF-Auto-Root-mako-occam-nexus4.zip
So I got around to it. Clean wipe, fresh from the start, install latest nightly of CM10, gapps, and no go. It says it's giving romtoolbox Pro permissions, but it can't delete anything. I authorize the computer to communicate through adb, and it forgets after a reboot...
The only thing is that I'm running Philz touch latest recovery...
Have you tried installing supersu? I found that a lot of apps have problems with the default super user.
I guess your /system doesn't have the right permissions. It's maybe set to read only.
IF not.. > Check your developer options and give root access to adb and apps