Related
I just flashed the CWM to my nook, but now when I try to turn it on, it runs directly into CWM recovery menu. I tried flashing to NC_1.3.zip, even tried dualboot, it does not help.
morph3us5 said:
I just flashed the CWM to my nook, but now when I try to turn it on, it runs directly into CWM recovery menu. I tried flashing to NC_1.3.zip, even tried dualboot, it does not help.
Click to expand...
Click to collapse
What ROM did you flash? CM7? Telll us specifically what you did.
Did something rather stupid, I did dd if=%path to cyanogen mod% of=/dev/block/vold/179:0, believing that it should write to my uSD card, but it written the internal memory instead. Fixed this by booting into Nookie-Froyo, fdisked the partition, and boot to clockworkmod again to restore the whole thing. Now I lack the ROM partition in /dev/block/mmcblk0p2. Is there a guide somewhere or tool to rebuild that partition?
Hey this is happening to me to I can't get in to anything but recovery.
morph3us5 said:
I just flashed the CWM to my nook, but now when I try to turn it on, it runs directly into CWM recovery menu. I tried flashing to NC_1.3.zip, even tried dualboot, it does not help.
Click to expand...
Click to collapse
Sent from my PG06100 using Tapatalk
After few days of research, I found the solution!!!! I am back in CM7!!!!!
morph3us5 said:
Did something rather stupid, I did dd if=%path to cyanogen mod% of=/dev/block/vold/179:0, believing that it should write to my uSD card, but it written the internal memory instead. Fixed this by booting into Nookie-Froyo, fdisked the partition, and boot to clockworkmod again to restore the whole thing. Now I lack the ROM partition in /dev/block/mmcblk0p2. Is there a guide somewhere or tool to rebuild that partition?
Click to expand...
Click to collapse
You need to re create DeviceID, MACAddress and SerialNumber under devconf/ in mmcblk0p2 (FAT).
DeviceID (I used "BNRV200", not sure if it is correct).
MACAddress (I used "11:22:33:44:55:66", not sure if it is correct).
SerialNumber (It is under the SD card door)
...and how can I do that? Which program can I use? I think this'll save me, considering my Nook is unregisterable for some reason...
Try with ADB + CWR uSD card
Boot with CWR card with NC connected to USB.
do adb shell:
# mkdir /rom
# mount /dev/block/mmcblk0p2 /rom
# ls /rom/devconf
# mkdir /bkp
# mount /dev/block/mmcblk0p3 /bkp
# ls /bkp
and pos what you see.
after that:
# umount /rom /bkp
Turn it off.
Take out your SD card then try to boot, sounds like cwm is running off you SD
Sent from my HTC_A510c using XDA App
bigsheep123 said:
Try with ADB + CWR uSD card
Boot with CWR card with NC connected to USB.
do adb shell:
# mkdir /rom
# mount /dev/block/mmcblk0p2 /rom
# ls /rom/devconf
# mkdir /bkp
# mount /dev/block/mmcblk0p3 /bkp
# ls /bkp
and pos what you see.
after that:
# umount /rom /bkp
Turn it off.
Click to expand...
Click to collapse
I think recreating the information within the Nook Color's memory would solve all my problems, since without registration, the Nook stock refuses to update. I tried updating through regular means, but the Stock refuses to take any update or any CWM-flashed ROM.
Android311 said:
Take out your SD card then try to boot, sounds like cwm is running off you SD
Sent from my HTC_A510c using XDA App
Click to expand...
Click to collapse
I do, and then the screen just goes black after the initial boot up.
neoage said:
I think recreating the information within the Nook Color's memory would solve all my problems, since without registration, the Nook stock refuses to update. I tried updating through regular means, but the Stock refuses to take any update or any CWM-flashed ROM.
I do, and then the screen just goes black after the initial boot up.
Click to expand...
Click to collapse
These steps are not flashing with CWM, they are just entering to clockwork recovery system wich allow you access to NC's internal memory.
You need to create three files:
/rom/devconf/DeviceID
/rom/devconf/MACAddress
/rom/devconf/SerialNumber
and fill them with your NC's info...
I dont know exactly wich data must be in those files...
EDIT:
With these files I can run CM7 but not sure for NC stock...
I'll try anything, even if it's random gibberish. I need my Nook back.
neoage said:
I'll try anything, even if it's random gibberish. I need my Nook back.
Click to expand...
Click to collapse
I found a complete list of files you need (maybe, maybe not)...
Archive: rombackup.zip
Length Date Time Name
--------- ---------- ----- ----
rom/devconf/BootCnt
rom/devconf/DeviceID
rom/devconf/MainboardSN
rom/devconf/WiFiBackupCalibration
rom/devconf/MACAddress
rom/devconf/ProductID
rom/devconf/Backlight
rom/devconf/EventType
rom/devconf/DeviceAttribute
rom/devconf/Platform
rom/devconf/DateManufactured
rom/devconf/PublicKey
rom/devconf/HashOfPrivateKey
rom/devconf/ean
rom/devconf/ModelNumber
rom/devconf/SerialNumber
rom/devconf/BootCount
--------- -------
957 17 files
I only want to know their format...
The question is, how can I access these files to edit them? What program can I use to see them? It's possible that if I can see them, I can extract them, edit them, then inject them into the Nook. There has to be a way around the missing addresses and numbers...
neoage said:
The question is, how can I access these files to edit them? What program can I use to see them? It's possible that if I can see them, I can extract them, edit them, then inject them into the Nook. There has to be a way around the missing addresses and numbers...
Click to expand...
Click to collapse
I need that file too.
I just want it as a sample because these files are different for each nook.
How did you lost those files?
If you didnt repartitioned your nook you can look here.
You can access them with CWR + ADB.
I keep giving this advice, I feel like a broken record. Oh well, at least it can be helpful...
Do a hard reboot and take your nook directly back to stocking condition. Hold down power,n, and the volume keys all at the same time for ~10 seconds until the nook turns off. It will flash, and reboot, when it begins to load (if you still have the cyanogen screen, as soon as it appears) hold down all the same buttons again until it goes off again. Do this 8 times total. On the final reboot, the nook will load into froyo, go through the normal B&N registration process and then in settings of the nook OS, erase and dereguster device to complete the wipe. That will send it back to stock.
I have seen this fix anything from a black screen to a completely erased system directory. Give it a shot.
mateorod said:
I keep giving this advice, I feel like a broken record. Oh well, at least it can be helpful...
Do a hard reboot and take your nook directly back to stocking condition. Hold down power,n, and the volume keys all at the same time for ~10 seconds until the nook turns off. It will flash, and reboot, when it begins to load (if you still have the cyanogen screen, as soon as it appears) hold down all the same buttons again until it goes off again. Do this 8 times total. On the final reboot, the nook will load into froyo, go through the normal B&N registration process and then in settings of the nook OS, erase and dereguster device to complete the wipe. That will send it back to stock.
I have seen this fix anything from a black screen to a completely erased system directory. Give it a shot.
Click to expand...
Click to collapse
Thanks. But this method only work if you have third partition (factory) intact.
And all I need is a file located at that partition wich I dont have :S
on my first attempt to put cm7.1 on my emmc using cwm I had the same or a very similar thing happen to me.
I somehow ended up with a bad boot partition. I followed a thread on here that had to do with "reformat and a repartition", (cant find it right now) but downloaded and installed these zips through a cwm card then installed an update for b&n 1.4 zip (I was running 1.3 ) but it worked allowing me to go to stock.
Then I tried it again only this time when I first booted to cwm on the main menu I hit wipe data/factory reset then installed zips and all is well.
*forum.xda-developers.com/showpost.php?p=14101197&postcount=1
I Think the file he's talking about is "E_Recovery". When I tried to register the Nook, I got a message that said that this file was missing...
I recently switched over to team win recovery from cwm. I do like the ui and functionality way better then cwm. The problem I'm having is that I cannot access my back up files from my PC via USB. When I use the file browser that is built into twrp I can see the back up files in the twrp folder. When I plug my tablet into my PC via USB and open the twrp folder it is empty. Also when I open the twrp folder in es file browser it is empty there too. I would like to store the back up on my PC rather then on my tablet. Am I missing something? I was having this same problem with titanium with backed up apps so I upgraded to the paid version and uploaded my back ups to Google drive. After that I looked in the titanium back up folder again on my PC and all the sudden the files were there when before they were not. Its very frustrating. Please help.
Sent from my Nexus 7 using Xparent Green Tapatalk 2
I had this same problem with TWRP when I started using it a couple of days ago. I'm not rooted, just unlocked and using fastboot to load the recovery image temporarily to do backups. And when I went looking for the backup files to move to my computer, I couldn't find them. It turns out to be a permissions issue, with TWRP creating the files/directories owned and visible only to root. Not a problem if backing up to a FAT formatted sdcard, but it is a problem with the Nexus 7 since it honors permissions and ownership of all files on the "sdcard".
Two fixes that I know of, though I have only used one so far:
1) After you do the backup, open up the psuedo terminal in TWRP and manually change the permissions or owner of the files recursively. Just set the starting directory in TWRP to "/sdcard/TWRP" and do "chown -R media_rw.media_rw BACKUPS" to change the owner, or do "chmod -R og+rw BACKUPS" to change the permissions. You really only have to do one of those, and I went with the owner change. I was then able to see the backup when connected to my computer, copy the files off, and then delete them to avoid taking up space on the tablet.
2) Although I haven't tried it yet, supposedly you can backup and restore directly to/from a USB thumb drive connected via OTG cable. This would be the easiest method for me, since I want backup and restore capability but without actually storing anything on the Nexus 7. I'm going to try it with a backup tomorrow, but I read about someone doing just that thing for the same reasons in a comment on reddit.
Hopefully that answers your question and gives you a way around it.
Just wanted to bump and let you know that the permissions issue seems to be properly resolved in the 2.2.1.5 version of TWRP. If you update then you shouldn't have to go through any crap to get at the backups.
Additionally, I tried doing a backup to a USB drive and it worked perfectly, so if you prefer that route it is definitely an option. Just make sure that you have the USB drive connected before you boot into TWRP, otherwise it doesn't notice the drive.
mtrs said:
I had this same problem with TWRP when I started using it a couple of days ago. I'm not rooted, just unlocked and using fastboot to load the recovery image temporarily to do backups. And when I went looking for the backup files to move to my computer, I couldn't find them. It turns out to be a permissions issue, with TWRP creating the files/directories owned and visible only to root. Not a problem if backing up to a FAT formatted sdcard, but it is a problem with the Nexus 7 since it honors permissions and ownership of all files on the "sdcard".
Two fixes that I know of, though I have only used one so far:
1) After you do the backup, open up the psuedo terminal in TWRP and manually change the permissions or owner of the files recursively. Just set the starting directory in TWRP to "/sdcard/TWRP" and do "chown -R media_rw.media_rw BACKUPS" to change the owner, or do "chmod -R og+rw BACKUPS" to change the permissions. You really only have to do one of those, and I went with the owner change. I was then able to see the backup when connected to my computer, copy the files off, and then delete them to avoid taking up space on the tablet.
2) Although I haven't tried it yet, supposedly you can backup and restore directly to/from a USB thumb drive connected via OTG cable. This would be the easiest method for me, since I want backup and restore capability but without actually storing anything on the Nexus 7. I'm going to try it with a backup tomorrow, but I read about someone doing just that thing for the same reasons in a comment on reddit.
Hopefully that answers your question and gives you a way around it.
Click to expand...
Click to collapse
Thank you for the tip. I went everywhere yesterday...
Best buy, radio shack, staples etc looking for an otg cable and had no luck. I'm going to order one online today. I will give the other techniques a try today though. I'm not familiar with pseudo terminal but I'm gonna dig in anyway. That's the best thing about these gadgets for me is hacking in and figuring out. Thanks again for your help!
mtrs said:
Just wanted to bump and let you know that the permissions issue seems to be properly resolved in the 2.2.1.5 version of TWRP. If you update then you shouldn't have to go through any crap to get at the backups.
Additionally, I tried doing a backup to a USB drive and it worked perfectly, so if you prefer that route it is definitely an option. Just make sure that you have the USB drive connected before you boot into TWRP, otherwise it doesn't notice the drive.
Click to expand...
Click to collapse
When I first started out with twrp I flashed 2.2.1.2 via adw. That was before I knew about the goo option in the play store. I've since upgraded to 2.2.1.5 and still having the same issue.
Sent from my Nexus 7 using Xparent Green Tapatalk 2
norcal61 said:
When I first started out with twrp I flashed 2.2.1.2 via adw. That was before I knew about the goo option in the play store. I've since upgraded to 2.2.1.5 and still having the same issue.
Click to expand...
Click to collapse
I think that it only works with newly created files. So your existing backups will still have the wrong permissions, but new ones will be correct.
It's the old permissions on directory structure that will mess you up though. If you delete the "/sdcard/TWRP/BACKUPS" directory through TWRP, you will lose your existing backups, but then the next backup that you do should recreate the full directory path with the correct permissions on all of the files and directories. After that you shouldn't have any trouble accessing the backups. I tested that on mine just to be sure that it worked and it did fine for me.
If you don't want to lose your existing backups then just do the owner/permissions change that I mentioned before and you will have access to the old backups as well as having the new ones created with the correct permissions from the start.
mtrs said:
I think that it only works with newly created files. So your existing backups will still have the wrong permissions, but new ones will be correct.
It's the old permissions on directory structure that will mess you up though. If you delete the "/sdcard/TWRP/BACKUPS" directory through TWRP, you will lose your existing backups, but then the next backup that you do should recreate the full directory path with the correct permissions on all of the files and directories. After that you shouldn't have any trouble accessing the backups. I tested that on mine just to be sure that it worked and it did fine for me.
If you don't want to lose your existing backups then just do the owner/permissions change that I mentioned before and you will have access to the old backups as well as having the new ones created with the correct permissions from the start.
Click to expand...
Click to collapse
Cool, that totally makes sense. Can't believe I didn't try that all ready. I will definitely make a new back up with the latest version of twrp. I'm running the same ROM and kernel as the back up that I currently have stored. Gonna give it a shot right now and let you know how it works.
Sent from my Nexus 7 using Xparent Green Tapatalk 2
mtrs said:
I think that it only works with newly created files. So your existing backups will still have the wrong permissions, but new ones will be correct.
It's the old permissions on directory structure that will mess you up though. If you delete the "/sdcard/TWRP/BACKUPS" directory through TWRP, you will lose your existing backups, but then the next backup that you do should recreate the full directory path with the correct permissions on all of the files and directories. After that you shouldn't have any trouble accessing the backups. I tested that on mine just to be sure that it worked and it did fine for me.
If you don't want to lose your existing backups then just do the owner/permissions change that I mentioned before and you will have access to the old backups as well as having the new ones created with the correct permissions from the start.
Click to expand...
Click to collapse
No luck. That's weird. I deleted the folder SD/twrp/backups containing the back up, did another back up and still not visible on my PC or in es file browser.
norcal61 said:
No luck. That's weird. I deleted the folder SD/twrp/backups containing the back up, did another back up and still not visible on my PC or in es file browser.
Click to expand...
Click to collapse
Hmm, you may have to delete "/sdcard/TWRP" as well, and just let it recreate everything. I might have changed the permissions on it already on mine, which is why it worked for me just deleting BACKUPS. I'll double-check that when I get back home and make sure.
mtrs said:
Hmm, you may have to delete "/sdcard/TWRP" as well, and just let it recreate everything. I might have changed the permissions on it already on mine, which is why it worked for me just deleting BACKUPS. I'll double-check that when I get back home and make sure.
Click to expand...
Click to collapse
It worked! I deleted the twrp folder all together and it worked like a charm. I'm now able to see and move the backups to my PC. Thank you very much for your help. It is greatly appreciated!
Sent from my Nexus 7 using Xparent Green Tapatalk 2
Some path is :
/data/media/TWRP/BACKUPS/
You need copy to /sdcard/TWRP/BACKUPS and connect to pc will see it.
trungdtdev said:
Some path is :
/data/media/TWRP/BACKUPS/
You need copy to /sdcard/TWRP/BACKUPS and connect to pc will see it.
Click to expand...
Click to collapse
I had the same issue and tried searching for "TWRP" to locate every instance of that folder. Turns out that I had previous backups in:
/mnt/shell/emulated/TWRP/BACKUPS/
I am happy to report that I was able to delete several past and hidden backups and recovered over 9gb of space!
So I've installed a custom ClockworkMod recovery and ROM on my Nexus 7 tablet. Life was good. Recently, I was running out of space and decided to delete my CWM backup (after saving it to my computer). And then, I realized I couldn't.
I went into ES File Explorer to try. I couldn't do it there.
I went into the ADB shell as root to try to remove it. No luck again, just the message when I finally DID try to remove one file:
Code:
# rm boot.img
rm failed for boot.img, Operation not permitted
What am I doing wrong?
Edit: This looks like it's ClockWorkMod (5.8.??)'s fault, but besides reading that another backup won't make the current one much larger, I don't actually know how to delete the current one.
Try "rm -rf ddd" (where "ddd" is the directory name) on the directory containing the files.
Sent from my Nexus 7
BillGoss said:
Try "rm -rf ddd" (where "ddd" is the directory name) on the directory containing the files.
Sent from my Nexus 7
Click to expand...
Click to collapse
in the development section there is a cwm flashable.zip that will delete them.. Then upgrade to latest cwm or TWRP.. its a bug from older version of cwm.. its talked about in the dev cwm thread..
good luck..
I did this in a way not mentioned here that still deserves mentioning... First I updated to the latest version of CWM available (via the Nexus 7 Toolkit) and then booted into recovery, opened the backup option, deleted the backup that was there, then cleaned the nandroids.
I could not find the aforementioned flashable zip, and because of the new CWM I had, I wanted to attempt a proper method of removal before running another rm command via the terminal. Therefore I could not verify the other methods mentioned here, my apologies.
erica_renee said:
in the development section there is a cwm flashable.zip that will delete them.. Then upgrade to latest cwm or TWRP.. its a bug from older version of cwm.. its talked about in the dev cwm thread..
good luck..
Click to expand...
Click to collapse
primetechv2 said:
I could not find the aforementioned flashable zip, and because of the new CWM I had, I wanted to attempt a proper method of removal before running another rm command via the terminal. Therefore I could not verify the other methods mentioned here, my apologies.
Click to expand...
Click to collapse
Sorry for re-opening an old thread, but I am having a problem where I have files that I cannot delete from the clockworkmods/blobs folder on my external sd card. So far, I have tried deleting them from a file explorer, deleting them as root from a file explorer, root and non-root deletes from terminal emulator, deleting through windows, adb shell deletes (with system booted).
I also wanted to try adb shell while booted into cwm, but I could not get the adb connection to work from recovery.
I also tried to find the zip file in the developer section and that's the real reason why I revived this thread...Does anyone know where the thread is with the zip file to remove these files?
I think the only way to delete them is through cwm.Boot to recovery and use the menu to delete them.
Sent from my SGH-I927 using xda app-developers app
Kodiack99 said:
I think the only way to delete them is through cwm.Boot to recovery and use the menu to delete them.
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
When I booted to recovery, I am able to delete each of the backups that I created. These all deleted correctly. I then went to Free unused backup files (to delete the files/folders in the blobs folder) and ran that and most of the files are gone. When I boot back into the phone, there are still some files/folders there and they seem to be taking up about 4-5 GB on the card. When I try to delete them through the file manager apps (either as root or not) they will not delete and the manager reports an error (before clicking delete, the manager displays a statistics report that says that the size of the files are over 2TB so obviously something is very messed up about them). I have also tried to delete them through the terminal (again as root and regular user) and they will not delete there either and they totally mess up the terminal window with unprintable characters (the only way to recover is to exit out of the current window and start a new one).
I finally fixed this problem last night by backing up all of my stuff (except the clockworkmod folder) to my computer. I then rebooted into recovery (latest version of CWM non-touch) and formatting the ext SD Card. When I rebooted there were still some folders there (including the clockworkmod folder). I did a format from within the OS and that cleared everything out. I copied all of my stuff back from my computer and I'm now good to go. Not sure how it got messed up to begin with, but the problem is fixed now. I think I'm going to stick with TWRP from now on.
is there a reasonably easy way to replace the factory.zip? (partition 3?)
I have what must be an older color, that if I do the 8 failed boots, it reverts all the way back to software 1.0.0
I find that it wont auto update to 1.4.3.
I have to first apply a 1.2 update, before it will take the stock B&N 1.4.3
(or manually thru cwm apply a 1.3 for example)
its not a deal breaker, but I'd prefer a solution that isnt boot into linux/dd the partition
this is a unit I muck around with, testing various roms, and getting it back to stock just involves a few extra steps.
thanks!
The easiest way to get it back to stock is just to flash it directly back with CWM. Go to my NC Tips thread linked in my signature and follow item A15. I have a CWM flashable 1.4.3 there.
However if you want to change the factory zip in partition 3, I can walk you through how to do that. It basically means mounting p3 in a rooted operating system like CM and copying the new zip there.
Sent from my BN NookHD+ using XDA Premium HD app
"However if you want to change the factory zip in partition 3, I can walk you through how to do that. It basically means mounting p3 in a rooted operating system like CM and copying the new zip there."
I'd like to try that if you are willing. Thanks!
I think im pretty experienced.
I have done cm7 / cm10 / on colors/NT many times, have run all the possible scripts you might think of more than once to fix various issues on many colors
one thing Ive noticed on this one after resetting data to the new partition scheme,
that just sort of nags at me, (besides not having a restore to the way I like it from the 8 failed boots)
after Im at 1.4.3 and think Im done, if I do a factory reset from within the stock rom
going to the "factory" screen (and before skipping oobe) seems to flipflop between thinking its got sw 1.0.0 and 1.4.3 , however, the running version in both cases is 1.4.3.
thanks again
----- edit -----
addl info:
I have a CM7 loaded / with the NookColorUMS am able to mount the partition, but have no idea how to maneuver to it, or the format of the zip I'd be dropping in it. (I assume its just a factory rom renamed) On the tablet, cant seem to find the partition after its mounted in either file manager program I've tried, and I've forgotten any real linux/Unix skills I used to have... and it would appear its not usable on the Windows side.
The zip to use is the one I referenced above in item A15. Just rename it factory.zip.
And since you have the UMS utility, mount p3 in the first section. Then plug in your USB cable to Windows and it should show up as a drive. Look at it with Windows Explorer. You can tell if you are there by seeing the factory.zip. Backup that one to your PC in case something goes wrong. Then copy the new factory.zip on the drive replacing the old one. Be careful with the other files there, especially the rombackup.zip. That is critical and needs to stay there. (In fact back that up to your PC too).
That's it, you're done. Next 8 failed boot you should be on 1.4.3.
Edit: You know instead of doing the 8 failed boot to get back to stock, just do a nandroid backup with CWM while you have stock on it and then you can use that backup for restoring to stock. Much easier.
Sent from my BN NookHD+ using XDA Premium HD app
" And since you have the ums utility, mount p3 in the first section. Then plug in your USB cable to Windows and it should show up as a drive. Look at it with Windows Explorer."
Yeah, this is where the plan goes south,
anything mounted in UMS doesn't seem to be translated properly for Windows. I get a "you must format the disk" but no additional usable mapped drives.
the internal partitions in the version of cm7 UMS I have are all down below, in the 2nd section
do I have to mount the "big" extended partition first? then in the second tab of UMS the factory p3? (ill try it in a few)
No, don't do that. I'll give you alternate instructions.
Go to Terminal Emulator in CM7 and set for superuser (type su enter). Then type these commands.
mkdir /factory
mount /dev/block/mmcblk0p3 /factory
The go to /factory with your root file manager.
Proceed as earlier instructed.
Did you see my edit above?
Edit: and the reason your drives are not showing properly in Windows is you must activate UMS in CM7. Pull up your notification area and tell it to allow access after you plug in the cable
Sent from my BN NookHD+ using XDA Premium HD app
the su/terminal thing is just what I need I think. will report back in 5
re:
"Edit: You know instead of doing the 8 failed boot to get back to stock, just do a nandroid backup with CWM while you have stock on it and then you can use that backup for restoring to stock. Much easier."
Oh, I have no trouble getting em back to stock, and "close" to perfect, but I could sell this unit and 6 months from now I wanna be able to tell the user just do this ( 8 factory failed) , and its good to go, and Im not supporting a rebuild to stock 1.0, then 1.2, or a cwm flash.
Edit2:
re: " Edit: and the reason your drives are not showing properly in Windows is you must activate UMS in CM7. Pull up your notification area and tell it to allow access after you plug in the cable "
Yea, Im doing that. Does one have to disable debugging or something too?
Its not a big deal at all, just didn't have it committed to memory and hasn't been necessary to this point to access the protected partitions.
mikeataol said:
the su/terminal thing is just what I need I think. will report back in 5
re:
"Edit: You know instead of doing the 8 failed boot to get back to stock, just do a nandroid backup with CWM while you have stock on it and then you can use that backup for restoring to stock. Much easier."
Oh, I have no trouble getting em back to stock, and "close" to perfect, but I could sell this unit and 6 months from now I wanna be able to tell the user just do this ( 8 factory failed) , and its good to go, and Im not supporting a rebuild to stock 1.0, then 1.2, or a cwm flash.
Click to expand...
Click to collapse
if you sell or give away your unit, be sure to erase and deregister with stock so it is removed as your device on the B&N servers. Otherwise the new user will not be able to register it. And you know stock recovery must be installed before the 8 failed boot works, right?
Also see my edit above about how to fix ums..... Yes you must disable debugging.
Sent from my BN NookHD+ using XDA Premium HD app
"Go to Terminal Emulator in CM7 and set for superuser (type su enter). Then type these commands.
mkdir /factory
mount /dev/block/mmcblk0p3 /factory"
Hi, I did the whole process twice , just to be sure before coming back... 2nd time was with a newly downloaded copy of the signed A15 zip
Are you sure the factory recovery wants the signed zip file and not the stock?
after 8 failed boots it does a data reset, then tried the factory image reinstall but the factory image reinstall part fails about 1/3rd of the way through
---
had to wing it on the mounting / copy a little as just running terminal put me in a read only file system
but im 100% positive I Installed the signed1.4.3. into factory (backed up the 1.0.0 factory.zip first)
just noting , I DID use the repartition scripts on this prior, setting it to the "new" 5gb data / 1gb media
but it seems to me that the stock recovery isnt liking the signed zip file
mikeataol said:
"Go to Terminal Emulator in CM7 and set for superuser (type su enter). Then type these commands.
mkdir /factory
mount /dev/block/mmcblk0p3 /factory"
Hi, I did the whole process twice , just to be sure before coming back... 2nd time was with a newly downloaded copy of the signed A15 zip
Are you sure the factory recovery wants the signed zip file and not the stock?
after 8 failed boots it does a data reset, then tried the factory image reinstall but the factory image reinstall part fails about 1/3rd of the way through
---
had to wing it on the mounting / copy a little as just running terminal put me in a read only file system
but im 100% positive I Installed the signed1.4.3. into factory (backed up the 1.0.0 factory.zip first)
just noting , I DID use the repartition scripts on this prior, setting it to the "new" 5gb data / 1gb media
but it seems to me that the stock recovery isnt liking the signed zip file
Click to expand...
Click to collapse
That is possible since I modified it. Go get a clean one from B&N. Go their support page and look for update. There will be a link to a big file that ends in .npk. Download that and rename to factory.zip.
Sent from my BN NookHD+ using XDA Premium HD app
It seems the 1.4.3 update zip from B&N isn't suitable as a factory.zip
neither the signed or unsigned works
I've grabbed 2 factory zips from other units
1.2.0 and 1.3.0 and copied them into factory, and they both work as expected on the 8 failed boots
I didn't get the complete result that I wanted , but good enough.
Thanks again for your help leapinlar, It's appreciated.
Could you put a custom rom as a factory.zip? Just a thought. It'd be cool to rollback to a stable rom like cm7 if something in a cm10/11 nightly goes wrong.
EDIT: Solved. See post #5.
___________________________
I had 4.4.4 stock ROM, and installed stock 5.1.1 ROM ([ROM][Manta][5.1.1] *03.05.2015* [Factory Images]) with PhilZ Touch recovery, and it's driving me nuts.
1) All data from my 4.4.4 /sdcard is moved to /sdcard/0.
But the system continues to use /sdcard.
Can I move all content from /sdcard/0 to /sdcard to have it all in one place?
2) I use Total Commander with the ADB file system plugin to copy files to my Android devices.
But now I cannot access /sdcard/clockworkmod anymore, since it doesn't show up.
I can only see it in /data/media/0/clockworkmod and it shows owner and group "0", whereas all other folders/files have "1023" as owner/group....?
Does anybody know why?
random_n00b said:
But now I cannot access the /sdcard/clockworkmod folder anymore, since it simply doesn't show up.
I can only see it in /data/media/0/clockworkmod and it shows owner and group "0", whereas all other folders/files have "1023" as owner/group....?
Does anybody know why?
Click to expand...
Click to collapse
User 0 is root, that is superuser. Any other number means normal underprivileged user.
I use twrp, and I never faced this problem.
[email protected] said:
User 0 is root, that is superuser. Any other number means normal underprivileged user.
I use twrp, and I never faced this problem.
Click to expand...
Click to collapse
OK. I'll give TWRP a try....
Edit:
TRWP does not move data to /sdcard/0/. That's good.
But now /TRWP/ has user/group "0", so it's similar to CWM and /clockworkmod/.
You may back up your data with adb pull or the twrp file explorer and then format back
Envoyé de mon Nexus 10 en utilisant Tapatalk
Finally I found a fix for my problems here.
That solved all access issues I had with the /clockworkmod an the /TWRP folders before.
:laugh::good:
___________EDIT________________
Made a few more tests.
When I switch back to Philz Touch (CWM), alle new backups are *again* not accessible. I need to run the "restorecon" command again to make the new backup folders accessible.
With TWRP no such problems. New backup folders are accessible right away.
--> Philz Touch caused all the problems I had. Will stick with TWRP from now on.
Not sure though if Philz Touch is the root cause, or the combination of ROM + Recovery...