Related
Hello guys,
I have a little problem which seems to be coming when I move the dalvik cache to the EXT partition of my device.
I am using the latest version of MIUI. It has A2SD built in, but it doesn't seem to be working. It was working before though...
What happened:
I restored the NANDROID backup of the stock ROM I had made before flashing MIUI. Once I booted into it, it warned me about the 2.3.4 OTA update. I did it, but forgot that it overwrites the bootloader, removes root and I will not be able to revert to MIUI.
I pushed the Clockwork recovery and immediately started restoring the NAND backup of my MIUI ROM. Without gaining root on the Stock 2.3.4 ROM.
The Dalvik was moved to the EXT on the MIUI I was trying to restore and functioning properly.
The restore went fine, until it got to restoring the sd-ext. It stood there at some *.tmp file for an hour or so. I removed the battery, booted into recovery, wiped and started the restore again. This time it finished, but when I went to start the phone, it got stuck at the Nexus logo, not even showing the MIUI boot screen.
Wiped again. Tried booting into a previous backup, which didn't have the Dalvik moved to the EXT partition. Restored and booted just fine.
I tried several more times restoring the latest backup I had (the one with dalvik to ext) and got the same result.
Then I tried installing the MIUI backup that didn't have Dalvik moved to EXT and tried moving the Dalvik to EXT. The phone rebooted and same thing happened. Didn't want to get past the Nexus logo.
I then wiped everything except batt stats, formatted ext, and flashed the MIUI ROM. It booted perfectly, but A2SD was not working, just like before (solution was to move dalvik to sd). I downloaded the A2SD GUI only and moved the dalvik to EXT AGAIN. And AGAIN - not booting past Nexus logo.
The only thing I still haven't done is formatting the SD and re-creating the EXT partition.
Any other suggestions on what may be causing this and how to fix it?
I want to have a2sd on this ROM and moving the dalvik to EXT seems to be the only way of achieving this.
Repartition SD card, you've most probably corrupted the EXT partition by pulling the battery.
Do you think that restoring the last MIUI backup I had after this will do the job?
After repartitioning? As long as you back up the files from the main FAT32 partition on the computer, and restore them back - the EXT will be overwritten when restoring nandroid anyway.
Well.... I just formatted the card with Panasonic SD formatter. Transfered only the nandroid backup (without creating an ext partition beforehand) and restored it successfully, but when the phone starts booting it is stuck at the Nexus logo.
I also checked the MD5 of the backup and everything is fine.
Godzi said:
Well.... I just formatted the card with Panasonic SD formatter. Transfered only the nandroid backup (without creating an ext partition beforehand) and restored it successfully, but when the phone starts booting it is stuck at the Nexus logo.
I also checked the MD5 of the backup and everything is fine.
Click to expand...
Click to collapse
Wipe Cache and dalvic. Than try again. Your System Need a ext wenn you push dalvic to sd before.
I ran out of options.
Formatted the card, tried restoring - Nexus logo
Wiped Everything + Dalvik and Cache, restored - Nexus logo
Wiped Everything + Dalvik and Cache, didn't restore old MIUI backup - successful boot. When I tried to move Dalvik to EXT after the successful boot - Nexus logo after restart.
If anyone can suggest anything... Because this way I have no access to the A2SD on the device with this ROM. And everything was working fine before I restored the Stock Ginger.
Did you try installing DT on any other ROM and try and move dalvik to the sd to see if it does the same thing?
Dude Random21 said:
Did you try installing DT on any other ROM and try and move dalvik to the sd to see if it does the same thing?
Click to expand...
Click to collapse
No. I haven't tried with another ROM. I guess I will try CM7 and see what happens when I move the Dalvik to the EXT.
I repartitioned once again, this time using the same EXT size as before the breakdown (512MB). When the backup I am trying to restore was made.
Was using 1024 when I partitioned previously and got the Nexus logo again.
Edit: Same thing. Successful restore and then the Nexus Logo.
I suspect it's the ext partition. Why don't you try formatting through recovery, and do a clean install?
Which recovery do you use? I would avoid Clockwork 3.x...
Well. I formated using Panasonic SD Formatted and then partitioned using the recovery. I did a clean install after that and as soon as I move the Dalvik to the EXT, I can't boot past the Nexus logo.
Yes, Clockwork 3.x. I guess I will try Amon_RA as well. Nothing left to lose.
If you partition with Amon Ra, make sure you up the partition from ext2 to ext3 (available through the Ra menu options)...
Ok. Partitioned with RA.
Tried to transfer the nandroid backup made by Clockwork to a sd/nandroid folder so I can restore it from within RA but it kept giving out some error telling me to look at the recovery log when I selected *.img files from the list.
Good news. I booted into MIUI and installed a2sd GUI. Moved Dalvik to EXT without a problem. I guess Clockwork's partitioning is flawed. Everything is working fine now.
Thank you.
Can anyone suggest a method I can use to restore the Clockwork made NAND backup + the EXT backup now when my partitions are finally alright.
Any method would be fine. Even manual through adb. I don't care. As long as I restore my phone to yesterday.
Thank you guys once again.
You should be fine if you load a clockwork prior to v3.x. I think 2.5.1.4 was the latest version prior to the v3.x series. The issues only arise with v3.x.
But only clockwork is able to restore clockwork backups, and the same goes for Amon_RA.
As an alternative, you can just extract the img files and manually load your data back on. It is definitely more time consuming, but it wouldn't matter what recovery you use. It has been a while since I extracted anything from the img files, and when I did, I just got the data from apps stored on the internal (apps and dalvik were stored on the sdcard), and I think the only program I used was unyaffs2 to extract the data.
Thank you guys!
Partitioning the card with Amon_RA and restoring the old Clockwork-made backup with Clockwork 2.* worked perfectly.
I will not use Clockwork ever agian. Putting Amon_RA and that's it.
You will only have this problem with clockwork 3.x - there doesn't appear to be the same issue with clockwork 2.x
I have been using v2.x without any issues (never upgraded to v3.x). I prefer it because it gives me the option to wipe the /system partition, whereas Amon_RA is missing this feature and you can only do it with a flashable zip.
I use 2.x for a number of reasons. I tried 3.x a few times, but always had ext issues on my N1. Having said that, I've used 3.x on my nook, MT4G and G2, and never had issues with them - just on the N1...
I've used RA 2.2.1 on CM7, MIUI ,Sense rom. I never seen sd-ext issues on my Nexus One.
Hey Guys.
I'm in a bit of ****.
I did my first rom flash yesterday, and all worked well. However the system would reboot once every 12 or so hours.
I noticed when I did CWM Recovery 5.5, that the total data wipe failed, but I researched that it was an issue, and had been fixed in CWM 6.0
The rom description said that if a total data wasn't done, you would have problems.
So I flashed 6.0, and did the CWM Recovery again with all the wiping options, but when I went to 'install zip from sd card', the file wasn't there. I assumed that the contents of the card wouldn't move, or be deleted, but it obviously was.
Now when I followed the original guide on XDA, I did the backup as stated, but it must not have worked, as in restore it's telling me there's no backup file found.
So at the moment, all i'm getting is the Samsung Galaxy S3 loading screen, but it's not going beyond that.
All I can access is CWM, and the Downloading screen.
What can I do to get my phone accessible again?
Thanks
plug your phone to PC (with downloaded ROM)
go to cwm -> mounts and storage -> mount usb storage. Now you should see Phone SD card on your PC. Put ROM in main folder uplug and flash.
if it doesn't help you should flash via odin (at download mode) 3 file ROM (f.e. JW1) with pit512 and re-partition checked, then flash kernel with cwm and start fun with cwm flashing.
Keep your ROMs and gapps and kernels etc on microSD next time
I do that so when I flash a new ROM I just wipe and format everything. I know its not necessary to format SD, I just do it anyway to clean up folders from old apps etc.
Sent from my GT-I9000 using Tapatalk 2
Hi all, this is my first post on XDA. I'm having big troubles with my device, a Samsung Galaxy S Plus i 9001 and I'm looking for some advice.
After a clean installation of the rom i had been using for some time I started to get messages of force close for most of the apps installed at every boot. The ROM in question is SmoothieICS v2. I believe that the reason of this issue is the fact that I restored all the apps and the data with Titanium backup. To solve the problem I tried to restore a nandroid backup via CWM (version 6.0.1.0), but when a rebooted, the backup was not installed at all and the force close messages continued. After that I tried to wipe data and cache, reinstall the ROM via CWM and Odin, install the stock ROM, fix permissions, format the partition, but nothing worked. Every time I reboot the device, the old ROM boot up with the same force close messages.
I've read several posts on XDA with similar issues, but usually a clean reinstall worked fine. At the moment I'm out of option.
Find attache a copy of the logcat recorded after rebooting the device.
Any suggestion to save my phone is really appreciated.
Thnaks in advance.
Some tips here:
1: Flash BroodROM RC5 (this is an Gingerbread ROM with all the partitions of our device) via odin
2: flash CWM 5.5.0.4 (this is in my eyes the most stable recovery) and wipe all (system, data, cache,dalvic etc)
ibacco said:
Hi all, this is my first post on XDA. I'm having big troubles with my device, a Samsung Galaxy S Plus i 9001 and I'm looking for some advice.
After a clean installation of the rom i had been using for some time I started to get messages of force close for most of the apps installed at every boot. The ROM in question is SmoothieICS v2. I believe that the reason of this issue is the fact that I restored all the apps and the data with Titanium backup. To solve the problem I tried to restore a nandroid backup via CWM (version 6.0.1.0), but when a rebooted, the backup was not installed at all and the force close messages continued. After that I tried to wipe data and cache, reinstall the ROM via CWM and Odin, install the stock ROM, fix permissions, format the partition, but nothing worked. Every time I reboot the device, the old ROM boot up with the same force close messages.
I've read several posts on XDA with similar issues, but usually a clean reinstall worked fine. At the moment I'm out of option.
Find attache a copy of the logcat recorded after rebooting the device.
Any suggestion to save my phone is really appreciated.
Thnaks in advance.
Click to expand...
Click to collapse
First solution,
SmoothieICS is an outdated ROM. Currently there are more stable and bug free releases are available for our device. You can try that.
But, the choice is yours, if you want to continue with it,
Access download mode, install a stable and safe recoveries like CWM 5.5.04, TWRP 2.2.1, or CWM 6.0.3.2 via odin or you can try to flash it via current recovery.
Then do a full data wipe, wipe cache, wipe dalvic cache. If necessary, delete the partition and do a full format
Restore the nandroid backup or do a fresh install
Edit: @mrjraider Haven't seen your reply. Silly me, repeated the same thing you said..
jabrif said:
First solution,
SmoothieICS is an outdated ROM. Currently there are more stable and bug free releases are available for our device. You can try that.
But, the choice is yours, if you want to continue with it,
Access download mode, install a stable and safe recoveries like CWM 5.5.04, TWRP 2.2.1, or CWM 6.0.3.2 via odin or you can try to flash it via current recovery.
Then do a full data wipe, wipe cache, wipe dalvic cache. If necessary, delete the partition and do a full format
Restore the nandroid backup or do a fresh install
Edit: @mrjraider Haven't seen your reply. Silly me, repeated the same thing you said..
Click to expand...
Click to collapse
No problem mate
Things happen
Thank you both, but your solutions didn't work. After installing BroodROM via Odin my phone rebooted in SmoothieICS just like nothing happened. Also a new recovery can't be installed, Tried with TWRP and CWM with no luck :crying:
ibacco said:
Thank you both, but your solutions didn't work. After installing BroodROM via Odin my phone rebooted in SmoothieICS just like nothing happened. Also a new recovery can't be installed, Tried with TWRP and CWM with no luck :crying:
Click to expand...
Click to collapse
That's strange. How is it possible to show up again after deleting and formatting the partition completely.. Are you sure you formatted the data and system in mounts and storage menu of cwm recovery.?
Anyway, Remove your external sd card, and try all the methods again..
Tried again. Did the following:
- removed the external sd card
- rebooted in recovery
- format system and data
- installed CWM 5.5.0.4
- rebooted in recovery
The recovery version installed is still the 6.0.1.0!!!!
It is like the internal SD card can't be written any more.
One thing I maybe didn't mention is that if I delete a file in the internal SD card and the reboot, the file is still there. it is not deleted.
This is really frustrating.
ibacco said:
Tried again. Did the following:
- removed the external sd card
- rebooted in recovery
- format system and data
- installed CWM 5.5.0.4
- rebooted in recovery
The recovery version installed is still the 6.0.1.0!!!!
It is like the internal SD card can't be written any more.
One thing I maybe didn't mention is that if I delete a file in the internal SD card and the reboot, the file is still there. it is not deleted.
This is really frustrating.
Click to expand...
Click to collapse
That's strange and weird. Haven't heard about such a problem before. I will look in to it and will reply you if i get something..
ibacco said:
Tried again. Did the following:
- removed the external sd card
- rebooted in recovery
- format system and data
- installed CWM 5.5.0.4
- rebooted in recovery
The recovery version installed is still the 6.0.1.0!!!!
It is like the internal SD card can't be written any more.
One thing I maybe didn't mention is that if I delete a file in the internal SD card and the reboot, the file is still there. it is not deleted.
This is really frustrating.
Click to expand...
Click to collapse
I recognize those symptoms. The i/o of the sdcard is defect.
What happens is that when you want to format random 0 and 1 are being written to remove the data on the card. If your card is broken and cant be written to you will be unable to format or flash anything. And thus the data on the card remains.
Verstuurd van mijn GT-I9001 met Tapatalk
mrjraider said:
I recognize those symptoms. The i/o of the sdcard is defect.
What happens is that when you want to format random 0 and 1 are being written to remove the data on the card. If your card is broken and cant be written to you will be unable to format or flash anything. And thus the data on the card remains.
Verstuurd van mijn GT-I9001 met Tapatalk
Click to expand...
Click to collapse
Does this mean that the only way to solve the issue is to replace the internal SD card?
Same Issue, but with SGS GT-I9000
I have pretty much the same problem!
Ive been reading a lot and it really seems to be a problem of the internal SD card!
I tried many times to delete all the files on the internal SD card via USB and via Recovery Mode, installed different OS ...nothing worked and most of my apps crash the whole time, so force close to all!
Im now about to decide to use my external SD as internal!
What do you say?
Any ideas
Thanks
This is related to http://forum.xda-developers.com/showpost.php?p=44237167&postcount=39259
Problem:
Stuck at bootscreen after installing Roboto 4.3 via Rom Toolbox Pro. I'm on ARHD 12.0.
Fastboot erase cache, full wipe, dalvik wipe etc. pp didn't help.
ADB-Sideload also didn't work due to a mysteriously & out of the blue non-mountable internal SD. Something was borked when I installed the new typo, dunno how and why.
So, re-flashing ARHD from my laptop wouldn't work, furthermore I deleted ARHD.zip from my internal SD; but anyway, the SD was to no avail -> no chance to grab a Nandroid.
Solution:
I firstly changed the recovery on my black lady by flashing TWRP in order to substitute CMW. TWRP allowed me to access and mount an USB-OTG, which hasn't shown up on CMW (v6.0.3.4) at all.
So, finally I placed the ARHD.zip on the external drive, mounted the drive and flashed the ROM 2 times, as the first flash freezed on 20%. But then it went throu, the ROM settled down and the bootscreen stuck was gone.
I got nook hd+ and used cm version 10.2 something for a while.
The device keeps crashing and restarting like crazy.
1 out of 10 times, it launches, but before I do anything, it crashes. Hell.
It has been crashing and restarting quite often these days, but since last night, all it does is crashing and restarting.
To make matters worse, I tried to format the device and install cm again. It did not work.
I made booting SD card and chose 'wipe data/ factory reset'. And nook said it wiped /data /cache data wipe complete etc. However, files were still there in internal storage.
On top of that, I had to try 4 times to install newest cm-11. It aborted.
Next, I tried to installnookjdplus factory2.2.0 . It had error. (status 6) to ne specific.
So, I tried newest cwm recovery. It installed, but nook still crashed.
I persevered and tried to install cm 11. It installed, but still crash and restart.
Hell. I literally spent whole day doing this. I am confused and frustrated and angry and experiencing a few other negative emotions English language dows not have in words.
Please, some advice.
Venrun said:
I got nook hd+ and used cm version 10.2 something for a while.
The device keeps crashing and restarting like crazy.
1 out of 10 times, it launches, but before I do anything, it crashes. Hell.
It has been crashing and restarting quite often these days, but since last night, all it does is crashing and restarting.
To make matters worse, I tried to format the device and install cm again. It did not work.
I made booting SD card and chose 'wipe data/ factory reset'. And nook said it wiped /data /cache data wipe complete etc. However, files were still there in internal storage.
On top of that, I had to try 4 times to install newest cm-11. It aborted.
Next, I tried to installnookjdplus factory2.2.0 . It had error. (status 6) to ne specific.
So, I tried newest cwm recovery. It installed, but nook still crashed.
I persevered and tried to install cm 11. It installed, but still crash and restart.
Hell. I literally spent whole day doing this. I am confused and frustrated and angry and experiencing a few other negative emotions English language dows not have in words.
Please, some advice.
Click to expand...
Click to collapse
CM10.x, CM11, and stock ROM need different versions of CWM recovery.
See http://forum.xda-developers.com/showthread.php?t=2679899 for info/pointers on flashing CM11.
To go back to stock ROM, see http://forum.xda-developers.com/showthread.php?t=2062613(item #6).
When switching between CM10, CM11, and stock ROM, you need to do "wipe /data & factory reset".
If none of the above helps the your problem might be due to an unruly app or hardware related.
digixmax said:
CM10.x, CM11, and stock ROM need different versions of CWM recovery.
See http://forum.xda-developers.com/showthread.php?t=2679899 for info/pointers on flashing CM11.
To go back to stock ROM, see http://forum.xda-developers.com/showthread.php?t=2062613(item #6).
When switching between CM10, CM11, and stock ROM, you need to do "wipe /data & factory reset".
If none of the above helps the your problem might be due to an unruly app or hardware related.
Click to expand...
Click to collapse
Ok. At least I got my biggest problem now.
I think my roblem is wipe data/factory reset does not do job it is supposed to do.
I still see folders and files in internal memory after factory reset. I think that is why install aborts and crashes even after successful install.
I think my problem is that wipe data/factory reset does not do its job
It gives me message it is formatting data cache and stuff. And last day they gave me data wipe complete. But the problem is, in internal memory, I can still see old folders and old files.
I think he should be gone if it is formatted. Where do I get the meaning of factory reset wrong?
Its not what is wrong with me. And how can I make factory reset work
And second question is that I tried to install B&N original operating system from cwm-based recovery. I tried a few different versions of
nookHDplus-factory-2.1.1-plain-stock.zip
However it always fail to install. Install aborted for some reason.
Thanks. It seem helpful.
digixmax said:
CM10.x, CM11, and stock ROM need different versions of CWM recovery.
See http://forum.xda-developers.com/showthread.php?t=2679899 for info/pointers on flashing CM11.
To go back to stock ROM, see http://forum.xda-developers.com/showthread.php?t=2062613(item #6).
When switching between CM10, CM11, and stock ROM, you need to do "wipe /data & factory reset".
If none of the above helps the your problem might be due to an unruly app or hardware related.
Click to expand...
Click to collapse
Thanks a lot for your advice
Going back to stock Rom 6 explains error message and aborting of install.
However the problem is where do I get CWM V 60036 or eariler?
Googling does not work.9
Venrun said:
Thanks a lot for your advice
Going back to stock Rom 6 explains error message and aborting of install.
However the problem is where do I get CWM V 60036 or eariler?
Googling does not work.9
Click to expand...
Click to collapse
You can get v6036 on that same thread digimax referenced above (my CWM thread linked in my signature). And a data wipe does not wipe your media files. To do that, go to mounts and storage and select wipe "data and datamedia".
Sent from my SM-T707V using XDA Premium HD app
thanks
leapinlar said:
You can get v6036 on that same thread digimax referenced above (my CWM thread linked in my signature). And a data wipe does not wipe your media files. To do that, go to mounts and storage and select wipe "data and datamedia".
Sent from my SM-T707V using XDA Premium HD app
Click to expand...
Click to collapse
trying it. hope it works.
did not work
for about deleting internal data, I went to 'mounts and storage'. used 'format /sdcard' and 'format/ data and/ data/media (/sdcard), but still has stuff in internal memory.
and to my surprise , I have been using CWM-6028. so far. I thought its name was 'NookHDplus-bootable'.
hell. stupid me.
Anyhow, CWM-6028 has been giving me troule
so, I would try other versions.
So far, I have done
1. made boot sd by burning image.
2. copy 'NookHDplus-factory-2.1.0-plain-stock' files and other versions.
3. Insert SD in device and boot CWM.
4. choose zip from sdcard.
5. install factory plain stock.
then I get message 'Failed to retouch 'system/lib/libemoji.so' (WTF is libemoji? and it is always this same file.)
E: error in sdard/nookHDplus-factort-2.2.1-plain-stock.zip(status7)
Installation aborted.
hell. And I tried every factory zip.
Am I doing something wrong?
Failed tp retouch '/system/lib/libemoji' is error message I get
Everytime I tried to install factory stock.
I tried every version of stock files. And I tried all CWM. And even tried TWRP, but it is always the same message what the hell is that emoji?
And what can I do with it?
What frustrates me the most is the fact that it installed 99% in a minute without trouble and stays there 410 minutes until it fails to install. It's driving me crazy
Does CM makes Factory reset by power button and home button does not work either.
Because I am getting message factory reset failed.
If CM is not the reason for it, well, something is wrong. Very wrong.
I am suspecting Internal memory corrupted lr something.
I should seriously consider throwing it away now.
Venrun said:
Because I am getting message factory reset failed.
If CM is not the reason for it, well, something is wrong. Very wrong.
I am suspecting Internal memory corrupted lr something.
I should seriously consider throwing it away now.
Click to expand...
Click to collapse
It is possible you have a bricked emmc. When bricked it looks like it is writing but is really read only and nothing takes. If you still have media files after a successful format data and datamedia then it is bricked. Probably best to get rid of it. You can buy a refurbished unit very cheaply these days.
Sent from my SM-T707V using XDA Premium HD app
Venrun said:
Because I am getting message factory reset failed.
If CM is not the reason for it, well, something is wrong. Very wrong.
I am suspecting Internal memory corrupted lr something.
I should seriously consider throwing it away now.
Click to expand...
Click to collapse
Assuming that your EMMC is shot, you can try running off SD card this no-emmc version of CM11 ROM: https://iamafanof.wordpress.com/201...-4-4-4-for-bricked-no-emmc-nook-hd-04nov2014/. It's best to use a card with fast randomized block read/write (which is what Class 4 cards are typically best at).
Thanks guys. By the way, what is emmc?
Is it part of CM software?
Does not sounds like hardware.
If I had factory resetted a day earlier, I would not have had problems.
Well. That is the way it is.
I finally kind of got nook working. I am running it on SD card now.
I got to thank you guys for your good advices.
Problem is that this ecmm free booting shrinks storage space.
No matter what is size of SD card, Internal storage is 900mb and SD card got 100mb. (I mean virtual Internal storage the file made in SD card) Not enough space to hold a movie.
I am happier to have tab working, but also wish to use full space of my SD.
At least I wish I can have a few Gs of storage.
Venrun said:
I got to thank you guys for your good advices.
Problem is that this ecmm free booting shrinks storage space.
No matter what is size of SD card, Internal storage is 900mb and SD card got 100mb. (I mean virtual Internal storage the file made in SD card) Not enough space to hold a movie.
I am happier to have tab working, but also wish to use full space of my SD.
At least I wish I can have a few Gs of storage.
Click to expand...
Click to collapse
Right after burning the ROM image to SDcard, it should be possible to use a disk partitioning tool such as MiniTool Partition Wizard to examine the SDcard ROM image's partitions and resize the /data partition to fill up the un-allocated space.
digixmax said:
Right after burning the ROM image to SDcard, it should be possible to use a disk partitioning tool such as MiniTool Partition Wizard to examine the SDcard ROM image's partitions and resize the /data partition to fill up the un-allocated space.
Click to expand...
Click to collapse
Thanks a lot. That sounds I can do it.
how you did it
Venrun said:
I got to thank you guys for your good advices.
Problem is that this ecmm free booting shrinks storage space.
No matter what is size of SD card, Internal storage is 900mb and SD card got 100mb. (I mean virtual Internal storage the file made in SD card) Not enough space to hold a movie.
I am happier to have tab working, but also wish to use full space of my SD.
At least I wish I can have a few Gs of storage.
Click to expand...
Click to collapse
Please tell how you made SD card work.
thanks.
rkgarg2000 said:
Please tell how you made SD card work.
thanks.
Click to expand...
Click to collapse
See http://forum.xda-developers.com/showpost.php?p=49007593&postcount=84 for some pointers on how to create a CM SD card with customized partition sizing for HD+. Although it was written for CM11, you should be able to adapt it for CM10.2 by using the appropriate ROM and GApps zip files corresponding to CM10.2.
Please confirm if my problem has any other solution
my NOOK HD+ I have CMW 10.2.1 with 6.0.4.6 recovery. Nook went to loop while booting. Now I can go to recovery and able to boot SD recovery CMW 6.0.2.8. But issue is:-
1. For any update even for Stock ROM it gives status 7 error.
2. With system recovery 6.0.4.6 when I try factory reset the TAB reboot same happen when i try to format DATA. While factory reset and DATA format happens with 6.0.2.8 position remains same.
3. When I try to make backup on internal storage both with 6.0.4.6 (TAB recovery) or 6.0.2.8 (From SD card) it makes boot,recovery and system image but give error as failed to backup /DATA.
4. I have done every thing right from various and latest ROM's ( error Status 7), Formatting boot,system but 6.0.4.6 on NOOK is intact and is in loop.
Please tell How I can over come this STATUS 7 error or DATA backup error.
thanks.
digixmax said:
See http://forum.xda-developers.com/showpost.php?p=49007593&postcount=84 for some pointers on how to create a CM SD card with customized partition sizing for HD+. Although it was written for CM11, you should be able to adapt it for CM10.2 by using the appropriate ROM and GApps zip files corresponding to CM10.2.
Click to expand...
Click to collapse
rkgarg2000 said:
my NOOK HD+ I have CMW 10.2.1 with 6.0.4.6 recovery. Nook went to loop while booting.
Click to expand...
Click to collapse
Does it boot-loop to recovery?
If so, see http://forum.xda-developers.com/showpost.php?p=55582281&postcount=1459 for potential causes and solutions.
Now I can go to recovery and able to boot SD recovery CMW 6.0.2.8. But issue is:-
1. For any update even for Stock ROM it gives status 7 error.
2. With system recovery 6.0.4.6 when I try factory reset the TAB reboot same happen when i try to format DATA. While factory reset and DATA format happens with 6.0.2.8 position remains same.
3. When I try to make backup on internal storage both with 6.0.4.6 (TAB recovery) or 6.0.2.8 (From SD card) it makes boot,recovery and system image but give error as failed to backup /DATA.
4. I have done every thing right from various and latest ROM's ( error Status 7), Formatting boot,system but 6.0.4.6 on NOOK is intact and is in loop.
Please tell How I can over come this STATUS 7 error or DATA backup error.
...
Click to expand...
Click to collapse
CWM v6.0.4.6 is not compatible with CM10.x, you need to flash back to the CWM version you previously used.