So, I have a Galaxy Exhibit II 4g (Sold here in Canada on Bell's network as the Galaxy W sgh-t679m).
I've had no troubles rooting the device (Though I forget where I got the package to root it and it's not one of the ones on the wiki), or installing CWM, however: My main goal was to get some manner of JB rom set up on the device.
I've tried both Linaro CM 10 and Slimbean.
The problem I'm encountering (with either of them) occurs after flashing the new rom.
When "starting" with the new rom for the first time, it just repeats the loadscreen animation indefinitely. I tried leaving it overnight and it was still doing it. However, When I flash back to the stock rom it works just fine.
Has anyone else encountered this problem? Do you know how to make this problem go away, and make either of the two roms load?
Did you do a wipe before flagging the ROM?
Sent from my SGH-T679 using Tapatalk
Did you do wipe system + cache + dalvik cache then install ROM then wipe dalvik cache + fix permissions?
If not try that. I doubt 2 desperate downloads are at fault here.
Sent from my CM10 Linero Odexed Powered by Evil
Thanks
Aha!
Before, I formatted data and wiped cache. Didn't know to wipe Dalvik Cache or fix permissions.
Thanks afwolfpacked!
What are you using to flash with. Cwm 6.0.1.2 or twrp. You will need to ensure system is wiped. Clean installs I'm twrp for thoroughness I do:
System wipe
Cache wipe
Dalvik cache wipe
Factory reset
Internal storage wipe
Android secure wipe
Post install:
Dalvik cache wipe
fix permission
Reboot
Initial setup: for 5 - 10 minutes don't do anything to phone for complete setup installation from ROM flash before completing initial setup
Sent from my CM10 Linero Odexed Powered by Evil
afwolfpacked said:
What are you using to flash with. Cwm 6.0.1.2 or twrp. You will need to ensure system is wiped. Clean installs I'm twrp for thoroughness I do:
Click to expand...
Click to collapse
I'm using CWM 6.0.2.5.
I did everything but the factory reset. It installed great, but I'm finding that it crashes constantly now that it's up and running (CWM, Linaro CM10, SpeedyGonzales Kernel).
I'm going to try swapping out the Kernel and see if that makes things go a bit better. Going to try Jocalas first. The Demon's Blood Kernel Link is dead.
I'll update the post after I see how Jocalas Kernel works out even though it's not rigged specially for JellyBean - hopefully it will be more stable.
Can someone link me some alternatives or give me some suggestions.
Sylrae said:
I'm using CWM 6.0.2.5.
I did everything but the factory reset. It installed great, but I'm finding that it crashes constantly now that it's up and running (CWM, Linaro CM10, SpeedyGonzales Kernel).
.
Click to expand...
Click to collapse
I don't think the factory reset is optional.
meekrawb said:
I don't think the factory reset is optional.
Click to expand...
Click to collapse
Well, I followed afwolfpacked's instructions to the letter (which didn't include the factory reset).
It installed fine, it just seems rather unstable and it crashes frequently.
Sylrae said:
Well, I followed afwolfpacked's instructions to the letter (which didn't include the factory reset).
It installed fine, it just seems rather unstable and it crashes frequently.
Click to expand...
Click to collapse
Factory reset is NOT optional, check the instructions again. Of course it will install with out wiping, it just wont work well hence the reason you are getting crashes.
Sent from my Nexus 7 using xda app-developers app
theAPANT said:
Factory reset is NOT optional, check the instructions again. Of course it will install with out wiping, it just wont work well hence the reason you are getting crashes.
Click to expand...
Click to collapse
I went back into CWM to switch the kernel, and I looked at the menu options. I thought wipe data and factory reset were separate options, and that I had done the wipe data and not the factory reset. Apparently I *DID* factory reset, as they are apparently the same thing.
So my bugs must be caused by something else. I'm hoping it's the kernel, not CM10.
Suggestions on the Kernel to use?
Sylrae said:
Suggestions on the Kernel to use?
Click to expand...
Click to collapse
You aren't able to download this:
http://www.androidfilehost.com/?fid=9390288116658471104
Although I don't see how it could be the kernel as it happened to you on slimbean as well.
Sylrae said:
I went back into CWM to switch the kernel, and I looked at the menu options. I thought wipe data and factory reset were separate options, and that I had done the wipe data and not the factory reset. Apparently I *DID* factory reset, as they are apparently the same thing.
So my bugs must be caused by something else. I'm hoping it's the kernel, not CM10.
Suggestions on the Kernel to use?
Click to expand...
Click to collapse
Have you tried just installing CM10 and NOT another kernel? CM10 has it's own kernel built-in.
meekrawb said:
I don't see how it could be the kernel as it happened to you on slimbean as well.
Click to expand...
Click to collapse
I was having a different problem with slimbean. I hadn't known the fix permissions or clear dalvik cache and it wasn't starting. I tried both it and Linaro CM10, and I definitely like Linaro CM10 better, at least until it started constantly crashing.
meekrawb said:
You aren't able to download this:
http://www.androidfilehost.com/?fid=9390288116658471104
Click to expand...
Click to collapse
I hadn't come across that particular link actually; and it downloaded just fine. I'll have to give it a try.
shakatu said:
Have you tried just installing CM10 and NOT another kernel? CM10 has it's own kernel built-in.
Click to expand...
Click to collapse
Hmm. No I hadn't realized that. The Linaro CM10 page made it seem like you needed another kernel.
Thanks guys. I'll give them a try tomorrow, and I'll let you guys know if either of those options works out.
If not, I may just have to go back to Slimbean, which didn't have as many shiny features (being slim), but seemed much more stable than the linaro cm10+speedy kernel.
By the way, you guys have been awesome. Done some other modding things before, but this is my first attempt at modding android; and you guys have been a huge help in figuring out how it works.
SG kernel is old and slow compared to evil or demons blood v8 and both those play nice with linero
Sent from my SGH-T679 using xda premium
afwolfpacked said:
SG kernel is old and slow compared to evil or demons blood v8 and both those play nice with linero
Sent from my SGH-T679 using xda premium
Click to expand...
Click to collapse
Yeah. now that I've installed DBv8, things are running much better. The phone's been running since I made that last post, and it hasn't crashed once.
What are the big differences between the linero kernel, DBv8, and Evil?
The linero kernel was optimized but still stock. Powered by Evil and Demons Blood v8 are near on par with each other and are overclockable. I believe sio was included in IO for DB v8 and not in evil and a few differences in governers. Not much differences in those 2.
Sent from my SGH-T679 using xda premium
Related
Hello, I'm having some worrying problems with my device
Like many of you I've been eagerly following TheWhisp in his journey to bring us JB, I had managed to stop myself flashing the earlier experimental versions so as not to just tease myself with a non-daily ROM, but when he announced he'd fixed the incoming call problem I had to try it! I installed the update from the 17th of Jan, everything was going pretty good.
I flashed back to stock via Odin first, booted, thumbed around a bit for nostalgia as I'd been running ReginaROM since it came out. The Cyanogenmod started becoming more and more unstable the next day, things crashing, reboots etc. I thought ok, no problem, I'll go back to Regina and wait. I flashed back to stock again to get a fully fresh install going as that's just the way I like to do things.
My problem is that the stock ROM won't boot, the Samsung logo glows away as normal, but after a moment I get the short vibration followed by three blips of vibration indicating something has crashed, after which the startup animation and sound plays again and the process repeats, I can never reach the lock screen.
Does anyone have any idea what's going on?
it's a bootloop, have you tried to wipe data from CWM?
Yeah I've tried wiping cache, dalvik cache and factory reset.
did you try wipe data/cache and dalvic cache on squads cwm??
Where else would I do it? haha I don't mean to sound *****y
I can't figure it out, I've done everything I can think of, seems sort of bad that I can't get my stock firmware to work if I ever need to go back to it.
Biggles_me said:
Where else would I do it? haha I don't mean to sound *****y
I can't figure it out, I've done everything I can think of, seems sort of bad that I can't get my stock firmware to work if I ever need to go back to it.
Click to expand...
Click to collapse
You have to wipe data after installation of the stock ROM. I had the same problem with the previous build. Just enter in CWM and wipe.
Sent from my GT-S6500 using xda premium
fenomen0 said:
You have to wipe data after installation of the stock ROM. I had the same problem with the previous build. Just enter in CWM and wipe.
Sent from my GT-S6500 using xda premium
Click to expand...
Click to collapse
wipe all in cwm > download mode > put stock rom and wipe one more time all.
fenomen0 said:
You have to wipe data after installation of the stock ROM. I had the same problem with the previous build. Just enter in CWM and wipe.
Click to expand...
Click to collapse
zalukajonet said:
wipe all in cwm > download mode > put stock rom and wipe one more time all.
Click to expand...
Click to collapse
Ah I didn't think of that, thanks guys I'll have a go when I get a chance this evening.
i followed the instructions, flashes the kernel, install from zipcard.. and so on (im not a noob) but it wont load.. im stuck at Google animation.
I tried reinstalling, deleting cache, dalvic and so on.. but i cant get it to boot!!
anyone having the same issue??
pls respond.:crying:
do you have format /system /data and /cache?
Flash the kernel again.
Format /system,data,cache
Do factory reset/wipe data
Wipe cache partition, and dalvik cache.
After this flash the rom. :thumbup:
cdeox8 said:
Format /system,data,cache
Flash the kernel again.
Do factory reset/wipe data
Wipe cache partition, and dalvik cache.
After this flash the rom. :thumbup:
Click to expand...
Click to collapse
That should be enough.
Oh and make sure the ROM installs properly i.e. it's not a bad download.
JB
Having the same issue but it's bootlooping at nAa kernel logo, please help, i followed the instructions correctly, tried the solutions you posted, but still no luck...
It shouldn't bootloop at the kernel logo. If the ROM isn't installed properly, it should boot into CWM. Try reflashing kernel and ROM.
Alchemist32 said:
Having the same issue but it's bootlooping at nAa kernel logo, please help, i followed the instructions correctly, tried the solutions you posted, but still no luck...
Click to expand...
Click to collapse
are you using the correct kernel? it shouldn't bootloop. like sgt.meow said it should go to cwm if anything's wrong.
Seems like my phone doesn't accept any custom ROM, i tried flashing GingerCMX with Alps (wiped everything before doing that), tried reflashing kernel, roms, several times and its just not working, my xperia x8 is xxx29 (the sticker under the battery), rooted, unlocked BL and no luck... :'(
Alchemist32 said:
Seems like my phone doesn't accept any custom ROM, i tried flashing GingerCMX with Alps (wiped everything before doing that), tried reflashing kernel, roms, several times and its just not working, my xperia x8 is xxx29 (the sticker under the battery), rooted, unlocked BL and no luck... :'(
Click to expand...
Click to collapse
Did u flash the LibSensor patch?
Sent from my GT-I9100 using xda premium
Titan9119 said:
Did u flash the LibSensor patch?
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
that's not really required.
cascabel said:
that's not really required.
Click to expand...
Click to collapse
For Alfs, yes.
Sent from my GT-I9100 using xda premium
Titan9119 said:
For Alfs, yes.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
i've used alfs for a couple of roms without that patch. no bootloops or any major bug.
@Titan9119
That libsensor patch is something required at ROM level i.e. after the device has booted up. And even without it, the device would be functional like @cascabel said.
I have the same problem.
I have kernel 2.0.32.61-nAa-06. I cleared the caches as required, flashed the kernel through flashtool and then flashed [ROM] | LiteCM10 | v1.0 | 09/07/2013 | JB 4.1.2 | nAa-06-kernel.
After flashing, I did a system reboot. The phone starts with the nAa kernel logo and then blacks out only to restart on the same. I've left it for a while and it keeps up the exercise. I can initiate the recovery with the back button. But nothing I've done has made a difference. Including repeated flashing.
There were no errors during the installations.
If anyone can help, I'd be most grateful.
aahd81 said:
I have the same problem.
I have kernel 2.0.32.61-nAa-06. I cleared the caches as required, flashed the kernel through flashtool and then flashed [ROM] | LiteCM10 | v1.0 | 09/07/2013 | JB 4.1.2 | nAa-06-kernel.
After flashing, I did a system reboot. The phone starts with the nAa kernel logo and then blacks out only to restart on the same. I've left it for a while and it keeps up the exercise. I can initiate the recovery with the back button. But nothing I've done has made a difference. Including repeated flashing.
There were no errors during the installations.
If anyone can help, I'd be most grateful.
Click to expand...
Click to collapse
full wipe, format data cache and system. flash rom.
cascabel said:
full wipe, format data cache and system. flash rom.
Click to expand...
Click to collapse
Already did that multiple times through the recovery mode. Wipes were completed without errors. The only thing I've not wiped is the SD Card.
aahd81 said:
Already did that multiple times through the recovery mode. Wipes were completed without errors. The only thing I've not wiped is the SD Card.
Click to expand...
Click to collapse
did you format the partitions i mentioned as well? if you did, try reflashing the kernel and rom after redownloading. might be a bad flash even if it looks like nothing went wrong.
No luck
You should go to minicm10 FAQ and look under 19 part.
Sent from my E15i running minicm7
cascabel said:
did you format the partitions i mentioned as well? if you did, try reflashing the kernel and rom after redownloading. might be a bad flash even if it looks like nothing went wrong.
Click to expand...
Click to collapse
I did the formats as well as the wipes. Downloaded the ROM and the kernel again and re-flashed. Now its getting stuck on the kernel after a vibration. Sometimes the mauve coloured light comes on and stays, at other reboots it turns off.. Can't get it into the recovery anymore
---------- Post added at 07:48 AM ---------- Previous post was at 07:31 AM ----------
Lukenda said:
You should go to minicm10 FAQ and look under 19 part.
Sent from my E15i running minicm7
Click to expand...
Click to collapse
Originally Posted by matmutant View Post
change in rom zip to *.61 for kernel version if you want the installation to complete (in META-INF/com/google/android/updater-script)
Click to expand...
Click to collapse
I did read this, and a lot of other posts, before posting. Unfortunately, I don't understand what he is asking me to do there. Which file/filename is being edited?
Many of us are facing this problem where after flashing a 10.2 ROM and rebooting, the device is stuck at boot screen- the Samsung N7000 screen!
This is a strange problem which seems to be affecting only some n7000 handsets as others can keep flashing the ROMs without any issues...wiping, reflashing ROM, etc doesn't work!
I myself faced this problem on almost all custom CM 10.2 Roms and am sharing the solution which worked for me. At the onset, this solution was suggested to me by another member @Super Prince in one of my posts and it worked!!
1. Reboot into recovery
2. Flash the correct gapps once again
3. Reboot
The problem should be gone now and no more stuck-iness for you...
Sent from my GT-N7000 using XDA Premium 4 mobile app
I tried that, and it did not work.
I'm not using the regular Gapps package, but this one:
http://forum.xda-developers.com/showthread.php?t=2012857
What package do you use?
knedge said:
Many of us are facing this problem where after flashing a 10.2 ROM and rebooting, the device is stuck at boot screen- the Samsung N7000 screen!
This is a strange problem which seems to be affecting only some n7000 handsets as others can keep flashing the ROMs without any issues...wiping, reflashing ROM, etc doesn't work!
I myself faced this problem on almost all custom CM 10.2 Roms and am sharing the solution which worked for me. At the onset, this solution was suggested to me by another member @Super Prince in one of my posts and it worked!!
1. Reboot into recovery
2. Flash the correct gapps once again
3. Reboot
The problem should be gone now and no more stuck-iness for you...
Sent from my GT-N7000 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Really? I'll try it next time when I flash some CM based ROM and will get this problem.
I hope it is really the reason.
SirRhor said:
I tried that, and it did not work.
I'm not using the regular Gapps package, but this one:
http://forum.xda-developers.com/showthread.php?t=2012857
What package do you use?
Click to expand...
Click to collapse
Which CM version are you on? This method has worked for me every time on CM 10.2 roms and official CM 10.2 gapps (the one dated 13/08/2013)
I used to get stuck on the GT N7000 screen after every reboot and resorted to all sort of stuff like reflashing, formatting and stuff but to no avail.
The only solution that worked for me was re-flashing the gapps!
Maybe you should try once again with the official gapps..and post your results.
jakuburban said:
Really? I'll try it next time when I flash some CM based ROM and will get this problem.
I hope it is really the reason.
Click to expand...
Click to collapse
The 'Reason', my friend, remains a mystery...
This solution, though worked!
Experienced developers might like to comment on this as to what might be the reason
knedge said:
Which CM version are you on? This method has worked for me every time on CM 10.2 roms and official CM 10.2 gapps (the one dated 13/08/2013)
I used to get stuck on the GT N7000 screen after every reboot and resorted to all sort of stuff like reflashing, formatting and stuff but to no avail.
The only solution that worked for me was re-flashing the gapps!
Maybe you should try once again with the official gapps..and post your results.
Click to expand...
Click to collapse
I'm on Carbon, but I tried another CM based ROM as well and it did not work.
I will try it with the official Gapps and Slim Gapps then report back.
EDIT 1: Well. I tried the lastest Carbon nightly 10/17, with both Slim Gapps and normal regular Gapps and the same result, stuck on boot logo.
Both times I flashed a clean install. I'm out of options now.
EDIT 2: When I'm using a kernel from 4.3 and I'm on CWM trying to format Preload, I always get this message:
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p12
Error formatting /preload
Could that be a possible reason?, does anyone else have that same message?
No suggestions?
Am I'm stuck on 4.2?
Sent from my GT-N7000
It's the same for all on the new Cwm. Preload cannot be formatted in Cwm 10.2.
What happens when you clean install a rom without gapps. And boot it.?
nokiamodeln91 said:
It's the same for all on the new Cwm. Preload cannot be formatted in Cwm 10.2.
What happens when you clean install a rom without gapps. And boot it.?
Click to expand...
Click to collapse
I tried that last night actually, clean flash and no Gapps and the same result, stuck on boot screen.
What I've tried so far:
- Flashing different 4.3 ROMs with three different Gapps combinations.
- Flashing Carbon with no Gapps.
Thank you in advance for any ideas you can provide.
I have never encountered such an issue after a clean flash ever. So not sure what's going on there.
When a clean install, do you format system, data and cache and then install the new rom?
nokiamodeln91 said:
I have never encountered such an issue after a clean flash ever. So not sure what's going on there.
When a clean install, do you format system, data and cache and then install the new rom?
Click to expand...
Click to collapse
Yeah, what I do is to do a factory reset twice, then clear cache, then preload twice, data once, system twice and dalvik twice, and only then I flash the ROM and then Gapps.
I let it settle for one hour and then I start the configuration.
It is weird, because if I leave it to boot up normally for the first time, without opening any apps or configurations, it reboots normally. And only when I open Settings or an app, and then I reboot the phone, it gets stuck on the boot logo.
I've even tried to format the SD Card and no difference.
tried without the external SD card inserted?
nokiamodeln91 said:
tried without the external SD card inserted?
Click to expand...
Click to collapse
No, gonna try that tonight.
EDIT 1: Tried lastest Carbon nightly with NO Gapps and no External SD Card. Same crap.
EDIT 2: I found this thread and it basically says that I have to flash Stock, then root it and then do a factory reset.
http://forum.xda-developers.com/showthread.php?t=2427569
Sent from my GT-N7000
SirRhor said:
No, gonna try that tonight.
EDIT 1: Tried lastest Carbon nightly with NO Gapps and no External SD Card. Same crap.
EDIT 2: I found this thread and it basically says that I have to flash Stock, then root it and then do a factory reset.
http://forum.xda-developers.com/showthread.php?t=2427569
Sent from my GT-N7000
Click to expand...
Click to collapse
@SirRhor Please try anothjer work-around before you do anything else:
1. Do all the wipes from a safe kernel
2. Flash Rom (only rom and no gapps)
3. Reboot the system without gapps
4. Now, reboot into recovery (I prefer to leave the system for 10-15 minutes to settle down before rebooting)
5. Flash the correct gapps
6. Reboot and set up ur google account etc.Restore apps or whatever u need from the play store. Dabble with rom settings
7. Reboot!
Did it work now?
knedge said:
@SirRhor Please try anothjer work-around before you do anything else:
1. Do all the wipes from a safe kernel
2. Flash Rom (only rom and no gapps)
3. Reboot the system without gapps
4. Now, reboot into recovery (I prefer to leave the system for 10-15 minutes to settle down before rebooting)
5. Flash the correct gapps
6. Reboot and set up ur google account etc.Restore apps or whatever u need from the play store. Dabble with rom settings
7. Reboot!
Did it work now?
Click to expand...
Click to collapse
I haven't tried that yet, I'll do it tomorrow, but I really doubt it's going to work. I think this whole problem it's caused by errors located on some blocks of memory.
Sent from my GT-N7000
SirRhor said:
I haven't tried that yet, I'll do it tomorrow, but I really doubt it's going to work. I think this whole problem it's caused by errors located on some blocks of memory.
Sent from my GT-N7000
Click to expand...
Click to collapse
Well, can be!
Much abused handset...and much loved too!
But do give it a try!
SirRhor said:
No, gonna try that tonight.
EDIT 1: Tried lastest Carbon nightly with NO Gapps and no External SD Card. Same crap.
EDIT 2: I found this thread and it basically says that I have to flash Stock, then root it and then do a factory reset.
http://forum.xda-developers.com/showthread.php?t=2427569
Sent from my GT-N7000
Click to expand...
Click to collapse
maybe your bootloader corrupted already. Reflash the bootloader only or whole stock rom using ODIN may help ..
I'm glad to inform you that I was able to solve my problem following this guide:
http://forum.xda-developers.com/showthread.php?t=2427569
But instead of flashing the Stock Rooted ROM using Odin, I just flashed it within Philz Recovery.
Right now I'm changing settings and restarting on Carbon 4.3, and so far I have not had any problems.
To anyone experiencing this, just read this thread so you will not waste your time trying ALL the bullcrap I did and instead just try the guide above.
Thank you for everyone who helped me out.
EDIT: Maybe the OP can change the title of this thread to "FIXED" or "SOLVED".
So...which Stock Rooted ROM using to flash?...
heihei123 said:
So...which Stock Rooted ROM using to flash?...
Click to expand...
Click to collapse
Actually, I found a better more permanent solution.
Follow this guide to check for errors on the different partitions:
http://forum.xda-developers.com/showthread.php?t=1396366
Let me know if it helps.
And to answer your question, I flashed a stock ROM from Hungary I think, no problems.
EDIT: Forgot to mention, instead of using the switches described on that guide, I used -f and -y at same time.
Sent from my GT-N7000
Hey guys,
I was running CM 10.1.3 and decided to go to Slim Bean 2.1. I followed the instructions, but when I rebooted instead of a clean install, I had all my old apps. Naturally, I went back to recovery and wiped everything again including sdcard and flashed Slim again (from external sd card). However, when I rebooted, again I had everything - old apps, music, photos... As you might imagine after this dirty flash the phone is quite laggy. Please tell me how to make recovery properly wipe the old data.
Any help is appreciated
Conquerora said:
Hey guys,
I was running CM 10.1.3 and decided to go to Slim Bean 2.1. I followed the instructions, but when I rebooted instead of a clean install, I had all my old apps. Naturally, I went back to recovery and wiped everything again including sdcard and flashed Slim again (from external sd card). However, when I rebooted, again I had everything - old apps, music, photos... As you might imagine after this dirty flash the phone is quite laggy. Please tell me how to make recovery properly wipe the old data.
Any help is appreciated
Click to expand...
Click to collapse
What recovery are you running? I am going to assume CWM v6.0.3.1...
From main menu;-
Wipe Data/factory rest
Wipe cache partition
From Mounts and Storage menu;-
Format /system
Format /cache
Format /data
Format /sd-card
From Advanced manue;-
Wipe dalvik cache
Now install.
You assume correctly. I had already done that, but I did it again in the order that you described. No difference, I still get all my app, my wallpaper, and all my accounts are still logged on. That is strange. Is there another way to wipe the phone?
Conquerora said:
You assume correctly. I had already done that, but I did it again in the order that you described. No difference, I still get all my app, my wallpaper, and all my accounts are still logged on. That is strange. Is there another way to wipe the phone?
Click to expand...
Click to collapse
Very strange as that is the exact process I always follow to install a new ROM.
SimonTS said:
Very strange as that is the exact process I always follow to install a new ROM.
Click to expand...
Click to collapse
Yes, it's very strange. I have done that before, but never with such results. I think I might have to resort to a kdz flash of stock rom, but I'll wait a bit to see if someone comes up with a solution. Nevertheless, I will have to find a solution, because after the last several dirty flashes one on top of the other the phone does not work as it should. It is very laggy and with an even higher battery drain (which was the initial reason for a clean install).
Conquerora said:
Yes, it's very strange. I have done that before, but never with such results. I think I might have to resort to a kdz flash of stock rom, but I'll wait a bit to see if someone comes up with a solution. Nevertheless, I will have to find a solution, because after the last several dirty flashes one on top of the other the phone does not work as it should. It is very laggy and with an even higher battery drain (which was the initial reason for a clean install).
Click to expand...
Click to collapse
I have to admit that I would look at doing a KDZ reflash to get everything back clean, then CWM and reinstall of the ROM.
Conquerora said:
Yes, it's very strange. I have done that before, but never with such results. I think I might have to resort to a kdz flash of stock rom, but I'll wait a bit to see if someone comes up with a solution. Nevertheless, I will have to find a solution, because after the last several dirty flashes one on top of the other the phone does not work as it should. It is very laggy and with an even higher battery drain (which was the initial reason for a clean install).
Click to expand...
Click to collapse
actually, try flashing with lg flashtool (dz+dll), it's supposed to format your internal storage as well, while kdz flasher doesnt afaik. good luck. strange problem indeed
Conquerora said:
Hey guys,
I was running CM 10.1.3 and decided to go to Slim Bean 2.1. I followed the instructions, but when I rebooted instead of a clean install, I had all my old apps. Naturally, I went back to recovery and wiped everything again including sdcard and flashed Slim again (from external sd card). However, when I rebooted, again I had everything - old apps, music, photos... As you might imagine after this dirty flash the phone is quite laggy. Please tell me how to make recovery properly wipe the old data.
Any help is appreciated
Click to expand...
Click to collapse
What about upgrading CWM to 6.0.4.4 and try again?
Sent from my Optimus 4X HD using XDA Premium 4 mobile app
Conquerora said:
Hey guys,
I was running CM 10.1.3 and decided to go to Slim Bean 2.1. I followed the instructions, but when I rebooted instead of a clean install, I had all my old apps. Naturally, I went back to recovery and wiped everything again including sdcard and flashed Slim again (from external sd card). However, when I rebooted, again I had everything - old apps, music, photos... As you might imagine after this dirty flash the phone is quite laggy. Please tell me how to make recovery properly wipe the old data.
Any help is appreciated
Click to expand...
Click to collapse
too late now to go back to format and reinstall rom. just go in data/app delete everything in there. also in data/dalvic-cache. then if u know from system apps which ones u dont want , go delete them and then find their dalvic-cache in /cache/dalvic-cache.
then go delete from sdcard the folder android. then from sdcard delete every zero and empty folder. last one delete all data/data and reboot. nothing should be left from previous rom. now if u have more leftovers in data/media/obb or data/media/legacy, delete. (dont delete the legacy in storage/emulated...!). about the problem u had. did u choose wipe and selected manually to wipe all those or u chose to format all data ? there must be a choice to format everything. ( dont do it now it will delete everything ). if that doesnt work then fix permissions.
Somehow after several attempts it worked and wiped everything. I am not sure, however, if it works consistently.
Flying_Bear said:
actually, try flashing with lg flashtool (dz+dll), it's supposed to format your internal storage as well, while kdz flasher doesnt afaik. good luck. strange problem indeed
Click to expand...
Click to collapse
I will certainly do that, but I have never used flashtool so far (kdz flasher, as well for that matter), So I just do not have the time to experiment right now, just in case if anything goes wrong. But I will certainly want to try a stock rom again.
[email protected] said:
What about upgrading CWM to 6.0.4.4 and try again?
Sent from my Optimus 4X HD using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I would try that, but in the clockworkmod site 6.0.3.1 is listed as the most recent version for our device.
kessaras said:
too late now to go back to format and reinstall rom. just go in data/app delete everything in there. also in data/dalvic-cache. then if u know from system apps which ones u dont want , go delete them and then find their dalvic-cache in /cache/dalvic-cache.
then go delete from sdcard the folder android. then from sdcard delete every zero and empty folder. last one delete all data/data and reboot. nothing should be left from previous rom. now if u have more leftovers in data/media/obb or data/media/legacy, delete. (dont delete the legacy in storage/emulated...!). about the problem u had. did u choose wipe and selected manually to wipe all those or u chose to format all data ? there must be a choice to format everything. ( dont do it now it will delete everything ). if that doesnt work then fix permissions.
Click to expand...
Click to collapse
Thank you for the detailed explanation! I will hold off from using it for now, but if recovery misbehaves again I will use it.
Deleted
..
[email protected] said:
This works perfectly for me.
http://forum.xda-developers.com/showthread.php?t=2486293
Sent from my Optimus 4X HD using XDA Premium 4 mobile app
Click to expand...
Click to collapse
How is Any Kernel related to the version of CWM Recovery? Otherwise, I am using the Anykernel version of OP 2.7.
Conquerora said:
How is Any Kernel related to the version of CWM Recovery? Otherwise, I am using the Anykernel version of OP 2.7.
Click to expand...
Click to collapse
Sry.. wrong link.. This stupid xda app here is CWM 6.0.4.4 http://forum.xda-developers.com/showthread.php?t=2523732
Sent from my Optimus 4X HD using XDA Premium 4 mobile app
[email protected] said:
Sry.. wrong link.. This stupid xda app here is CWM 6.0.4.4 http://forum.xda-developers.com/showthread.php?t=2523732
Sent from my Optimus 4X HD using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you, I will flash that to be up to date and ready for Kit Kat as soon as a stable build comes out
So today I installed M12 with clean install. At first, everything was veery slow, like it needed 10-15 sec for one operation. Apps were opening to black screen or opening with huge delay. After few hours, it got better, UI is responsive, but apps are still opening slowly(no black screens through). How can I help it?
Sent from my C6603
asakurato said:
So today I installed M12 with clean install. At first, everything was veery slow, like it needed 10-15 sec for one operation. Apps were opening to black screen or opening with huge delay. After few hours, it got better, UI is responsive, but apps are still opening slowly(no black screens through). How can I help it?
Sent from my C6603
Click to expand...
Click to collapse
I suffered a while with this myself, and finally I did a full system reset, even wiping all the appropriate partitions and folders including MEDIA. Since then my Nook HD+ has been snappy and reliable.
danshane said:
... and finally I did a full system reset, even wiping all the partitions...
Click to expand...
Click to collapse
The only partitions that should ever need to be wiped are /cache, /data, and /system. Wiping some partitions other than these 3 (e.g., /rom and /factory) will brick your Nook.
Sent from my C6603
digixmax said:
The only partitions that should ever need to be wiped are /cache, /data, and /system. Wiping some partitions other than these 3 (e.g., /rom and /factory) will brick your Nook.
Click to expand...
Click to collapse
I did exactly that. Now it's better, but some apps are still slow when opening, especially google apps
Sent from my C6603
asakurato said:
I did exactly that. Now it's better, but some apps are still slow when opening, especially google apps
Sent from my C6603
Click to expand...
Click to collapse
asakurato said:
So today I installed M12 with clean install. At first, everything was veery slow, like it needed 10-15 sec for one operation. Apps were opening to black screen or opening with huge delay. After few hours, it got better, UI is responsive, but apps are still opening slowly(no black screens through). How can I help it?
Sent from my C6603
Click to expand...
Click to collapse
My Nook HD+ became intolerably slow on CM roms - so slow that after years of running CM I switched to the latest version of Liquidsmooth in the forums. Liquidsmooth isn't exactly speedy, but it is usable.
freecity said:
My Nook HD+ became intolerably slow on CM roms - so slow that after years of running CM I switched to the latest version of Liquidsmooth in the forums. Liquidsmooth isn't exactly speedy, but it is usable.
Click to expand...
Click to collapse
Just did factory reset and everything is super smooth now!
Sent from my BN NookHD+ using XDA Free mobile app
digixmax said:
The only partitions that should ever need to be wiped are /cache, /data, and /system. Wiping some partitions other than these 3 (e.g., /rom and /factory) will brick your Nook.
Click to expand...
Click to collapse
Right-o! I edited my post to clarify what I actually did. Thanks for that correction -- I might have done someone a mischief.
asakurato said:
Just did factory reset and everything is super smooth now!
Sent from my BN NookHD+ using XDA Free mobile app
Click to expand...
Click to collapse
I'm having the same issue as the OP. Followed these instructions to upgrade to CM11 M12 :
http://forum.xda-developers.com/nook-hd/general/how-to-updating-hd-hd-internal-emmc-to-t2863171
And now stuck with a very sluggish tablet - any apps opening are really slow - has been like this for a couple of days now. Battery life also seems to be worse.
You suggested a factory reset - do you mean the factory reset option in the Backup and reset menu?
Almost tempted to downgrade back to 10.2.1 - it had its faults, but was still better than this.... but i can't find any info on how i'd do that - can i use my current version of CWM Recovery (had to update it to do the upgrade) and just flash the old version of CM10 and the relevant Gapps?
jonas_r said:
I'm having the same issue as the OP. Followed these instructions to upgrade to CM11 M12 :
http://forum.xda-developers.com/nook-hd/general/how-to-updating-hd-hd-internal-emmc-to-t2863171
And now stuck with a very sluggish tablet - any apps opening are really slow - has been like this for a couple of days now. Battery life also seems to be worse.
You suggested a factory reset - do you mean the factory reset option in the Backup and reset menu?
Almost tempted to downgrade back to 10.2.1 - it had its faults, but was still better than this.... but i can't find any info on how i'd do that - can i use my current version of CWM Recovery (had to update it to do the upgrade) and just flash the old version of CM10 and the relevant Gapps?
Click to expand...
Click to collapse
No, you can't use the new CWM to go back to CM10.2.1. It requires the old CWM. And to factory reset boot to CWM to do it (either version).
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
No, you can't use the new CWM to go back to CM10.2.1. It requires the old CWM. And to factory reset boot to CWM to do it (either version).
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
I performed the wipe data & factory reset as instructed after updating CWM recovery and before installing CM11 and the Gapps file - is that the option i could try now? That wont wipe anything "important"?
Also, if i was to downgrade to 10.2.1 could i do it by just copying the files to the internal or external memory and doing the following? :
downgrade the CWM recovery, reboot into the new recovery, wipe data/factory reset and then install chosen CM10 and Gapps?
Thanks for the help!
jonas_r said:
I performed the wipe data & factory reset as instructed after updating CWM recovery and before installing CM11 and the Gapps file - is that the option i could try now? That wont wipe anything "important"?
Click to expand...
Click to collapse
The current ROM, all the apps and their data/settings would be gone -- but your user-media content should be intact.
Also, if i was to downgrade to 10.2.1 could i do it by just copying the files to the internal or external memory and doing the following? :
downgrade the CWM recovery, reboot into the new recovery, wipe data/factory reset and then install chosen CM10 and Gapps?
...
Click to expand...
Click to collapse
Yes.
jonas_r said:
I performed the wipe data & factory reset as instructed after updating CWM recovery and before installing CM11 and the Gapps file - is that the option i could try now? That wont wipe anything "important"?
Also, if i was to downgrade to 10.2.1 could i do it by just copying the files to the internal or external memory and doing the following? :
downgrade the CWM recovery, reboot into the new recovery, wipe data/factory reset and then install chosen CM10 and Gapps?
Thanks for the help!
Click to expand...
Click to collapse
If you only factory reset (in other words don't wipe /system) then your ROM stays and should still run, just settings and installed apps removed.
And yes on procedure to downgrade.
Sent from my BN NookHD+ using XDA Premium HD app
jonas_r said:
I'm having the same issue as the OP. Followed these instructions to upgrade to CM11 M12 :
http://forum.xda-developers.com/nook-hd/general/how-to-updating-hd-hd-internal-emmc-to-t2863171
And now stuck with a very sluggish tablet - any apps opening are really slow - has been like this for a couple of days now. Battery life also seems to be worse.
You suggested a factory reset - do you mean the factory reset option in the Backup and reset menu?
Almost tempted to downgrade back to 10.2.1 - it had its faults, but was still better than this.... but i can't find any info on how i'd do that - can i use my current version of CWM Recovery (had to update it to do the upgrade) and just flash the old version of CM10 and the relevant Gapps?
Click to expand...
Click to collapse
Yes I did it from backup and reset menu, but I think it did reset with cwm anyway, so it doesn't matter.
Sent from my BN NookHD+ using XDA Free mobile app
Just to share my observations. In general the performance is very good. Currently I'm on M12.
I'm mostly using it to read PDFs.
In the past I observed, that after a while of operation it gets slow and even the touchscreen is not responding properly. After a reboot everything is fine again. I couldn't observe it anymore lately, but not sure whether this is because of I did a reboot (before it becomes necessary).
A question because I first read the thread title wrong: will there be a CM12 for this device? Or other way around, is someone (leapinlar?) working on a port lollipop to nook or is intended to do so?
starbright_ said:
Just to share my observations. In general the performance is very good. Currently I'm on M12.
I'm mostly using it to read PDFs.
In the past I observed, that after a while of operation it gets slow and even the touchscreen is not responding properly. After a reboot everything is fine again. I couldn't observe it anymore lately, but not sure whether this is because of I did a reboot (before it becomes necessary).
A question because I first read the thread title wrong: will there be a CM12 for this device? Or other way around, is someone (leapinlar?) working on a port lollipop to nook or is intended to do so?
Click to expand...
Click to collapse
There should be, but I dont know who is working on it.
Sent from my C6603