Related
Hello guys,
OTA update failed on my hero and I can't do anything right now. I understood from other topics that it's possible to use goldenimage card formatted on one android to use it on another. I don't have GC right now and I'd like to 4 question:
1. Did anybody try to use goldencard on hboot 007?
2. Did anybody try to boot GC (which was created on another phone), on hero?
3. What SD Cards did you use [Stock SanDisk[2GB] or others [Names please]?
4. If second question is true, there is a way to create an image for goldenCard and by thus it'll help to newbies like me to survive first flash. Might anybody who uses linux or winhex may help?
Available SD rippers: WinHEX [Windows] and Linux [HexDump].
Thanks in advance,
MrBora
Download this file: ftp://xda:[email protected]_2.73.405.5_WWE_release_signed_NoDriver.exe
Run it. Once you see the ROM update utility GUI, search c:\users (windows 7) or c:\documents and settings (other versions) for a file called rom.zip.
Rename this file HEROIMG.zip and get it onto your SD card.
I think it's HEROIMG.zip. It might be HEROIMAGE.zip. I'm doing this from memory but I'm pretty sure it's HEROIMG.zip.
Power on the Hero holding the VOLUME DOWN button. It should scan the file and then ask you if you want to update. Say yes. This will restore you back to factory and should be able to go from there.
I tried that and I got incorrect CID
If i'm doing it through Windows i'm getting hero 131 customer ID error
thx
Thats because you need to keep trying the goldcard method..Ihad to make the goldcard 3 or 4 times before it worked,used the standard card that same with the Hero (sandisk)
guys it worked with KingSton 2GB image. I succesfully installed stable image, but i can't now to use fastboot for rooting. Write failed. Is there a way to downgrade hboot? no need. with flashapp it works like a charm.
in any case i'll create an image for goldcard
I have a GTab that was running Calkulin + Clemsyn Combo Overclock at 1.5 ghz V8 on the 1.2 branch fine for a couple months now, then something happened today. Woke up to find there was no sound coming from it (I'd left an Anti-mosquito app running all night), so I tried to play a couple music files. Seemed to get frozen instead of playing, so I restarted. That's when it went into a boot loop from 3 birds to the first splash screen of the loaded ROM.
Attempted to do a backup via CWM, and it failed on /data. Tried a data wipe/reset, then reflashing the ROM and finally NVFlash. Still goes into a bootloop. Repartitioning and mounting doesn't do anything; ADB doesn't see the device at all in CWM or APX; /data cannot be mounted and /sdcard mounts only when a card is inserted (doesn't see the internal space) but still doesn't mount USB storage and says: "E:Unable to write to ums lunfile (No such file or directory)"; drive shows in Win7, but is inaccessible;
As mentioned, APX mode and NVFlash along with CWM works fine. And I can mount /cache and /system fine. I've gotten to Code Double Red here and now I'm draining the battery for the next step (really don't want to pull any screws). Also tried the fix here, but it seems that's just for CM7, which I'll probably try flashing some time.
I'm going to return to the 1.1 branch and try a couple ROMs there, but I have a really slow connection and it's taking a while to get nvflash 1.1.
Did a quick search of the forum and didn't find anything quite similar. Obvious question is, has anyone ever experienced this before? What are some other steps I can take to fix this? Is there a way to backup the internal SD before I probably have to wipe it?
Connect the USB cable to the tablet, then boot it into CWM, and run this command on your PC:
Code:
C:\SOME\PATH> [B]adb shell dmesg > dmesg.txt[/B]
Post that dmesg.txt file here. We'll see what's wrong.
Connected the charger long enough to run the command, but all I get is "error: device not found". As I'd said, ADB doesn't detect the tablet, even though Windows knows when it's connected and disconnected. Is there anything that I can flash to get me a terminal? That's the only way I can think of to get that command run and hopefully direct the output to my SD. Thanks.
I now have a completely dead battery. Wondering what to do next since it's supposed to have been hard reset now. Not seeing anything different after booting; same boot loop even though I just flashed a ROM again.
rajeevvp said:
Connect the USB cable to the tablet, then boot it into CWM, and run this command on your PC:
Code:
C:\SOME\PATH> [B]adb shell dmesg > dmesg.txt[/B]
Post that dmesg.txt file here. We'll see what's wrong.
Click to expand...
Click to collapse
I had seen this thread before where you were helping someone last year. Wish I'd read further to see that he eventually got the same problem I now have. I'm currently working my way through everything. First I need to get ADB running though, so I'm working on that now. Think I may be needing that partition swap trick, but we'll see...
Having issues getting the right USB drivers installed for ADB on Windows 7 64 bit. Using instructions here. But each time I uninstall the device, as soon as I plug in the tablet, it installs the default drivers. Using both Device manager and USBDeview. Updating and other options are also disabled when there is nothing installed. Considering to do a direct registry hack of the device info if I can, and hopefully not break anything important.
Try using Linux.
I finally got ADB working on my system and did some experimenting. Seems there's definitely something wrong with my internal SD according to the dmesg output. Luckily I have a SD which I used in my SG3, and it is already properly partitioned, so I'll try using that. Tried making a fstab file in /etc (mtdblock3) but I got "Magic Value Mismatch" error, so I NVFlashed to return it to how it was. I'm currently researching how to create update files, because it seems that's the only way I can get the SDs swapped. Any guidance is still welcomed. Thanks alot.
Skele Drew said:
Seems there's definitely something wrong with my internal SD according to the dmesg output.
Click to expand...
Click to collapse
Yeah. There are clear error messages relating to the internal SD card. You can either return the tablet and get a replacement, or, use my SD card device swapping technique to use the external SD in place of the non-working internal one.
Tried making a fstab file in /etc (mtdblock3) but I got "Magic Value Mismatch" error, so I NVFlashed to return it to how it was. I'm currently researching how to create update files, because it seems that's the only way I can get the SDs swapped.
Click to expand...
Click to collapse
If you use my files, you don't need to modify anything manually. What're you trying to change, BTW?
I can definitely use some help there. Where are the files? I tried modifying the custom ROM I use by adding a custom fstab and vold.fstab to /etc, an init script to init.d and replacing the /data mounting command with:
Code:
ui_print("Copying Data Files");
run_program("/sbin/mount", "-t", "ext3", "/dev/block/mmcblk2p2", "/data");
ui_print("Mount information:");
ui_print(run_program("/sbin/mount"));
Not sure what you're attempting to do here...
If you just want to use an external SD card in place of your non-working internal one, then all you have to do is a) flash either one of the CWM zip files and then b) flash the SD card swapping zip file right after you install the ROM of your choice. And, if you tell me which ROM you plan to install, I can look inside it and tell you if my scripts will work with that ROM.
If you can read shell/awk scripts, you can look inside the zip files to see what they do and how they do it.
rajeevvp said:
Not sure what you're attempting to do here...
If you just want to use an external SD card in place of your non-working internal one, then all you have to do is a) flash either one of the CWM zip files and then b) flash the SD card swapping zip file right after you install the ROM of your choice. And, if you tell me which ROM you plan to install, I can look inside it and tell you if my scripts will work with that ROM.
If you can read shell/awk scripts, you can look inside the zip files to see what they do and how they do it.
Click to expand...
Click to collapse
I was trying to make a swap script myself, but it's not working. /system dir gets corrupted. I'm using Clemsyn_Caulkinver8final2, a Froyo ROM.
Look at my scripts. If you have any questions, just ask.
Where are the scripts? That's what I've been asking...
EDIT: If this is what you use, then all should be ok. Let you know the result when I'm again online. Thanks alot for your help!
That's what I was talking about. I modified the device-swapping script today to fix-up an additional shell script, /system/etc/inandop.sh, on the various Clemsyn/Beasty ROMs (incl. yours), so use the newer zip file.
rajeevvp said:
That's what I was talking about. I modified the device-swapping script today to fix-up an additional shell script, /system/etc/inandop.sh, on the various Clemsyn/Beasty ROMs (incl. yours), so use the newer zip file.
Click to expand...
Click to collapse
Appears it still doesn't work. However, now instead of having a boot loop, it's just stuck at the splash screen after the 3 birds. I'm going to try combining your script and the ROM to see if I can get better results. I'm also going to try inserting some log/debug messages where I can.
Skele Drew said:
Appears it still doesn't work. However, now instead of having a boot loop, it's just stuck at the splash screen after the 3 birds. I'm going to try combining your script and the ROM to see if I can get better results. I'm also going to try inserting some log/debug messages where I can.
Click to expand...
Click to collapse
THANK YOU RAJEEV!!!!!!!
Today I got the time to work on my tablet again, since I just restarted college and it's been a bit hectic. Decided to try CM7 since when I looked into your script I saw direct management for it, so I NV'd back to 1.1 (I didn't know what branch CM7 was on, but flashing CM7 on 1.2 gave an error and aborted). The first time I tried the CM7, it got to the CM7 logo, then was there for a while until I only had a black screen. The only way I knew the tablet was still on was because ADB was still connected. Then I flashed your script and VOILA! everything started great. So now I have my tablet again for my classes .
I am planning to still run a few tests to see if I can somehow recover/fix the internal SD, so I downloaded your set of e2fsprogs. Think I'll make a flashable file for the entire package.
Again, thanks for all your assistance. It's much appreciated. I really didn't have that much time anymore to work on it myself too. I will continue to learn more as time goes on though, and I hope one day I'll become a guru like you .
Skele Drew said:
Decided to try CM7 since when I looked into your script I saw direct management for it, so I NV'd back to 1.1 (I didn't know what branch CM7 was on, but flashing CM7 on 1.2 gave an error and aborted).
Click to expand...
Click to collapse
The official CM7 is, right now, only for 1.1. However, since you can replace just the kernel and instantly make a 1.2 ROM, you'll have to look at the kernel messages to tell which bootloader version you have (Note: this is only for pershoot kernels).
The first time I tried the CM7, it got to the CM7 logo, then was there for a while until I only had a black screen. The only way I knew the tablet was still on was because ADB was still connected.
Click to expand...
Click to collapse
This is to be expected. When a ROM first runs, it writes a whole bunch of stuff into /data; but, your internal SD card is messed up, so every write would've ended up with the kernel retrying for quite a bit and then failing.
You should've flashed the ROM and immediately afterwards my script to fix-up the mount points on the ROM--ie. before the first boot.
I am planning to still run a few tests to see if I can somehow recover/fix the internal SD, so I downloaded your set of e2fsprogs. Think I'll make a flashable file for the entire package.
Click to expand...
Click to collapse
I doubt if you can "fix" your internal SD card error using any of the e2fsprogs--it looks like a card-controller error rather than a media error. You have one of the non-standard internal SD cards which has caused problems for some other users as well.
Ok. I do have a few issues I hope I can get some help on. For one, flash player doesn't work, and that's something very important. All my browsers direct me to get flashplayer. It worked pretty well in my previous ROM, so it may be an issue with CM7, but I haven't seen any similar issues on their site.
Also, the tablet is less responsive now, though I think this has to do with the /data partition being on external SD, though it's a class 6 card.
Sent from my GTablet using Tapatalk
Did you partition the external SD card correctly into 2 partitions (the first as VFAT and the second as ext3) before you installed CM7? I'm not sure what steps from my post you followed and what steps you skipped: you mentioned you were planning to modify the scripts/ROM, right?
It is also possible that my script is not doing the right thing on CM7 since it doesn't touch the vold.fstab on it. Get me the output of a mount command in CM7, and these files:
Code:
/system/etc/vold.fstab
/system/build.prop
Also make sure that you, or the ROM provider, haven't enabled the SD card switching in Settings > Cyanogenmod settings.
The SD I'm using was in a SG3 using this ROM, so I think it's correctly partitioned. I've accessed the partitions before and the correct names are associated with the contents. I only followed steps 1 & 4. The option to use removable for apps and media is disabled.
build.prop
mount.txt
vold.fstab
Need some help with the "AdamOutlerUbuntuTotalReFlash" method. I am missing or overlooking something but, can't figure out what. I have installed the Ubuntu 12.0.4 on an older laptop in an effort to 1) learn but 2) mostly to restore my 16GB NT. Currently the Nook will only boot to CWM. I have tried a few different methods and images but, can't seem to get anything to load. Do I need to repartition and can anyony help with that, I am at apoint wher maybe I have tried to learn or do to many new things at once and am frustrated and confused. I don"t believ all is lost but could sure use a little more help/direction. I have followed all of Adam Outler's steps but, seem to run into trouble with having success writing the image to the SD card.
Is this what you are trying?: http://forum.xda-developers.com/showthread.php?t=1470910
If so, you do not need to have Ubuntu on your computer, nor know anything about it!
Scroll down to "WIndows" instructions and go!
1. Download - extract - rename Adams file
2. Open your disk imager and load the img you "created" in step 1.
3. Burn the image to your sd card
4. Boot into the card created in step 3 and follow the instructions below the picture. starting with "Theory of..."
thanks
asawi said:
Is this what you are trying?: http://forum.xda-developers.com/showthread.php?t=1470910
If so, you do not need to have Ubuntu on your computer, nor know anything about it!
Scroll down to "WIndows" instructions and go!
1. Download - extract - rename Adams file
2. Open your disk imager and load the img you "created" in step 1.
3. Burn the image to your sd card
4. Boot into the card created in step 3 and follow the instructions below the picture. starting with "Theory of..."
Click to expand...
Click to collapse
I would like to say thank you for the help and appreciate the support. I will give this a shot. this evening. a few Questions 1) when renaming the AdamOutlerUbuntuTotalReFlash.tar.gz file do i delete the .tar.gz extensions and replace them with the .img extension? or do i do i leave them so that the extension is now .tar.gz.img ? 2) when powering on the device do I power on with the power button on the NT or use the USB cable and let the device power itself on and does it matter if the device is plugged into the charger or the PC? Any specific instructions or specific utilities for formatting the SD Card?
Thanks Again!
I haven't done this recovery myself, so I really don't know anything about it. I would suggest you to read through that topic and see if the answers are there.
The instructions do say "extract" and THEN "rename"
Some general things I can say though:
When burning an image to sd card the card doesn't need to be formatted before doing it.
To get the NT to boot from sd crad is individual from device to device. Many say they only get theirs to do it by inserting charging cable to power adapter.
The three that have passed through my hands have booted to sd either by themselves when turning on power. If they haven't done so right away I hold down the "n" and that's it.
1_ton said:
Need some help with the "AdamOutlerUbuntuTotalReFlash" method. I am missing or overlooking something but, can't figure out what. I have installed the Ubuntu 12.0.4 on an older laptop in an effort to 1) learn but 2) mostly to restore my 16GB NT. Currently the Nook will only boot to CWM. I have tried a few different methods and images but, can't seem to get anything to load. Do I need to repartition and can anyony help with that, I am at apoint wher maybe I have tried to learn or do to many new things at once and am frustrated and confused. I don"t believ all is lost but could sure use a little more help/direction. I have followed all of Adam Outler's steps but, seem to run into trouble with having success writing the image to the SD card.
Click to expand...
Click to collapse
You should read this post before trying out any "unbricking" method and end up permanently bricking your NT.
asawi said:
I haven't done this recovery myself, so I really don't know anything about it. I would suggest you to read through that topic and see if the answers are there.
The instructions do say "extract" and THEN "rename"
Some general things I can say though:
When burning an image to sd card the card doesn't need to be formatted before doing it.
To get the NT to boot from sd crad is individual from device to device. Many say they only get theirs to do it by inserting charging cable to power adapter.
The three that have passed through my hands have booted to sd either by themselves when turning on power. If they haven't done so right away I hold down the "n" and that's it.
Click to expand...
Click to collapse
o.k. so i have downloaded the image, extracted it using winrar but, when i use the win32diskimager to write the image i can find the file but, the win 32 diskimager does not recognize the sd card or doesn't even let me open the little file foled at all for that matter as far as where to chose to write it to?
Hi all,
I tried Adams' method along with a few days worth of other methods. I've been unable to get past the writing MLO portion in Adams' method. Has anyone been able to get past this?
p.s. I'm a semi-n00b, this is my first tablet If it was a phone I'd be fine lol
Nvmd, I think I was using an old file, got it working now. Large thanks and respect to Adam!
Sent from my DROID RAZR using xda app-developers app
Here it is
http://forum.xda-developers.com/showthread.php?t=2179403
I hope someone can help me. I have a 16gb nook tablet that I rooted using the method described here http://liliputing.com/2012/03/how-to-dual-boot-cyanogenmod-7-nook-tablet-os-with-a-microsd-card.html over a year ago and I've never had an issue until last weekend. My daughter was playing a game and the nook started acting up. The touch screen became unresponsive and the screen started to flash. I let the Nook charge overnight and when I turned it on the next day the screen became stuck at the white Nook welcome screen. After 20 minutes I tried the holding down power and N button to see if I could get it to restart, but unfortunately that may have made it worse. Now my Nook won't start at all. I've read many many threads here on how to fix it, but I am not tech savvy in the slightest. The first thing I tried was Rays method http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/ but instead of getting the green checkmark I got the red X and the "nook is shutting down" message. I tried so many things that I cannot remember them all but I do know that one of the methods I tried I got this message.
E:Can’t mount / cache/recovery/command/
E:Can’t mount / cache/recovery/log/
E:Can’t open / cache/recovery/log/
E:Can’t mount / cache/recovery/last_log/
E:Can’t open / cache/recovery/last_log
After that I tried to use the method described here http://forum.xda-developers.com/showpost.php?p=24995518&postcount=1 and I did make the booktable cwm-sd and I went to lavero.burgos' thread to download the mmcblk files, but they weren't there.
Also I don't understand what adb is but I'm desperate, when I found the thread that explained it and tried to download the ADB + Fastboot + Drivers.zip that was in said thread (I'm sorry I can't remember which thread it was) the zip file didn't work.
I'm really sorry for posting yet another, "please help my nook is borked" thread but after all the reading I've done this past week the only thing I've become is very confused and frustrated. Thank you in advance to anyone who can help.
Notice on the link you posted
Ray Waldo; said:
If this procedure fails, try one of these:
Celtic has a possible solution on XDA here: http://forum.xda-developers.com/showthread.php?t=1513583
Succulent has more info on his Github page: https://github.com/succulent/acclaim_recovery_sdcard.
Click to expand...
Click to collapse
I can see how you got lost. There aren’t really any detailed instructions there.
I got the following zip from 2nd link
Flash the zip with CWM then try the bn_142_factory_recovery.zip SD card again and you should get a green checkmark this time.
udownwitopp said:
Notice on the link you posted
I can see how you got lost. There aren’t really any detailed instructions there.
I got the following zip from 2nd link
Flash the zip with CWM then try the bn_142_factory_recovery.zip SD card again and you should get a green checkmark this time.
Click to expand...
Click to collapse
Thank you for your reply. I will try this tonight and hopefully it will work.
Well I tried, and I hate asking but how exactly does someone add a zip file to an sd card after an image has been flashed to it? I've tried numerous times with sd cards of various sizes and I'm pretty sure I should have been able to do this with a 16gb card, but every time I try to drag and drop the flashstock zip over onto the card it says that there is no room available. Now I have been doing a lot of reading on here and I'm pretty sure I did not set the card up right, I did format it correctly with the sdformatter program, but I'm guessing I have to do something with the partitions on the card. I am not familiar with the programs because I've never had cause to use them before so I am not entirely sure how to do that. I tried following the directions found here http://forum.xda-developers.com/showpost.php?p=24995518&postcount=1 but I couldn't figure out how to enable boot, and lba flags. I realize that this has probably all been answered already, but again, there programs are so foreign to me that I'm not even sure what to look up first. Thank you again for any help that any one can give me.
evm22 said:
Well I tried, and I hate asking but how exactly does someone add a zip file to an sd card after an image has been flashed to it? I've tried numerous times with sd cards of various sizes and I'm pretty sure I should have been able to do this with a 16gb card, but every time I try to drag and drop the flashstock zip over onto the card it says that there is no room available. Now I have been doing a lot of reading on here and I'm pretty sure I did not set the card up right, I did format it correctly with the sdformatter program, but I'm guessing I have to do something with the partitions on the card. I am not familiar with the programs because I've never had cause to use them before so I am not entirely sure how to do that. I tried following the directions found here http://forum.xda-developers.com/showpost.php?p=24995518&postcount=1 but I couldn't figure out how to enable boot, and lba flags. I realize that this has probably all been answered already, but again, there programs are so foreign to me that I'm not even sure what to look up first. Thank you again for any help that any one can give me.
Click to expand...
Click to collapse
I'll try to explain the process for you. "The Red X" is a very common issue that people have with their devices. It's usually caused by digging into something that you don't fully understand. It's VERY important to understand the process of flashing custom ROMs because it could screw up your tablet, delete ROM partitions and such.
The first issue you need to attend to is "The Red X." First download the bn_142_factory_recovery.zip from the ray waldo site found here:
http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
Unzip the zip file and you should have a repart.img. Use win32diskimager to write this to an SD card. Once it's done writing, put the SD card in your device and it should boot from SD card and flash stock B&N 1.4.2 to your nook (if you have problems booting from SD card plug in the USB to your computer).
If you still get "The Red X" during this process please use the following method:
http://forum.xda-developers.com/showthread.php?t=1513583
If you have further problems please post or PM me. Once you have the issue fixed I HIGHLY recommend using the SDC version. It's a lot easier than the Internal Version and will prevent mistakes from happening.
Thank you for responding. I retried the method described on Ray's site, but sadly it's still a no go. I have downloaded the parted binary and I know how to get it onto the sd card, but what I don't know is how to ADB into my device. I'm not even sure I understand what ADB is.
evm22 said:
Thank you for responding. I retried the method described on Ray's site, but sadly it's still a no go. I have downloaded the parted binary and I know how to get it onto the sd card, but what I don't know is how to ADB into my device. I'm not even sure I understand what ADB is.
Click to expand...
Click to collapse
I'm not extremely knowledgeable with the ADB tool, but it's setting up your computer so you can write commands into your command prompt that will execute actions on your device. The link for setting it up is here:
http://forum.xda-developers.com/showthread.php?t=1474956
Once you get it set up just follow the rest of the directions in the parted binary post.
datallboy said:
I'm not extremely knowledgeable with the ADB tool, but it's setting up your computer so you can write commands into your command prompt that will execute actions on your device. The link for setting it up is here:
http://forum.xda-developers.com/showthread.php?t=1474956
Once you get it set up just follow the rest of the directions in the parted binary post.
Click to expand...
Click to collapse
Thank you for a link to the post with a working zip file for adb, I've downloaded and I've tried to follow the video, but unfortunately my laptop will not read my nook at all. Every time I connect it with a usb my device manager tries to find it, but it blinks, makes an error sound and I see
OMAP4330 under other devices. I' did a search for that error and came across this thread, but again the instructions call for installing an apk on the nook and since I can't get mine to turn on, it's a no go
evm22 said:
Thank you for a link to the post with a working zip file for adb, I've downloaded and I've tried to follow the video, but unfortunately my laptop will not read my nook at all. Every time I connect it with a usb my device manager tries to find it, but it blinks, makes an error sound and I see
OMAP4330 under other devices. I' did a search for that error and came across this thread, but again the instructions call for installing an apk on the nook and since I can't get mine to turn on, it's a no go
Click to expand...
Click to collapse
There is a possibility you could have deleted some partitions important to the nook then. Have you tried making an sdc version of cm10 to see if it could boot at all? You could see if you still have the device information to backup, recreate the partitions and flash back to stock.
Use this to make a bootable cm10 card:
http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/
Just write the image file to an SD card and put it in your nook. It will boot into cm10. Once there go into your file manager and turn on root access. Go to your root drive/ROM/devconf to access all your device information. Make a backup of all them. There is a picture of my devices root drive. If you do not have the various partitions you will have to recreate them. There is a method on the Nook General Thread for doing this named "Unbrick Internal Partitions On NT" or something similar. You can use that recreate the internal partitions essential for your nook.
If you deleted the ROM partition with the Nook's product information you may be out of luck. The serial number and Mac address are the most essential, and can be found on your device hardware. The SN is under the SD slot (if readable) and Mac address is located inside your device. Not sure where I've never opened my nook to look, but probably on the WiFi chip.
Slight chance you may be able to fix it with this information and the rest of the device information you can use from a different nook since it doesn't have to do with internet and registration. There may be a way to fix that, but I don't know of any.
Best of luck. If you have problems just post a reply or send me an email.
I can get the Nook to turn on with the bootable cm10 card in it. I get the cyanoboot screen and see the boot menu, but honestly I don't know where to go from there. I think it's time for me to try and find someone who understands all of the programs involved in trying to fix this because I know I'm going to end up making things worse, if that's even possible. Thank you for trying to help me though. I do appreciate it
evm22 said:
I can get the Nook to turn on with the bootable cm10 card in it. I get the cyanoboot screen and see the boot menu, but honestly I don't know where to go from there. I think it's time for me to try and find someone who understands all of the programs involved in trying to fix this because I know I'm going to end up making things worse, if that's even possible. Thank you for trying to help me though. I do appreciate it
Click to expand...
Click to collapse
Hello! Did you ever figure out how to resurrect your Nook? I had trouble signing in Gmail and wanted to just unbrick and have the plain Nook again. I've been struggling getting the device to boot from the sd card with the repart imaged. I'm trying to get back to the ClockworkMod recovery screen but I can't at that moment. Someone suggested that I "flash" the B&N zip to the card but I'm trying to figure out how to do that.
Would love help!
Hey! I am trying to get Cyanogenmod 12.1 on my stock Nook Tablet. I no longer use the Nook Tablet as often and would like to give it a new life by making it an Android. After reading a ton of articles and forums, I have tried a ton of them, but none of them seem to work successfully. One of them I tried was, Install CM for acclaim on the wiki.cyanogenmod.org website , the process went successfully until I rebooted and it continued to boot me to the regular Nook setup. I think it is because the Clockworkmod Recovery is outdated. I also see that Cyanogenmod's latest recovery is also available, but how do I put it on my SD card successfully. Please provide a step to step guide for me. Thank you!
BornReady_ said:
Hey! I am trying to get Cyanogenmod 12.1 on my stock Nook Tablet. I no longer use the Nook Tablet as often and would like to give it a new life by making it an Android. After reading a ton of articles and forums, I have tried a ton of them, but none of them seem to work successfully. One of them I tried was, Install CM for acclaim on the wiki.cyanogenmod.org website , the process went successfully until I rebooted and it continued to boot me to the regular Nook setup. I think it is because the Clockworkmod Recovery is outdated. I also see that Cyanogenmod's latest recovery is also available, but how do I put it on my SD card successfully. Please provide a step to step guide for me. Thank you!
Click to expand...
Click to collapse
I just did this about a week ago (finally) and there are no better instructions for getting started than those provided by digixmax here. Just ignore the statements about CM 11 and forge ahead. Later in that thread there are a variety of recommendations for file substitutions in the method if you are aiming for CM 12 instead of 11. I followed the ones here. These also work.
My own discovery was that you should ignore the TWRP error messages about being unable to mount '/bootdata'. I finally came across that somewhere and it proved to be true for me.
Take it slow. Gather together all the files you will need first. Then prep the SD card (don't forget to set the flag). Then copy the files over in the order specified. It matters. Then go for it! (don't neglect to backup the stock system before wiping things--you may be glad you did).
My start-up with CM 12.1 was really rough and I thought I might abandon it but after a few days and quite a number of reboots things settled down. Maybe that has something to do with coming from CM 10.2.1, maybe not. Anyway, the system is no worse than CM 10.2.1 and I don't have trouble with cold or warm boots hanging like I used to with CM 10.2.1.
My pet peeves are listed here and/or here but may be idiosynchratic to my device or particular flash.
nmyshkin said:
I just did this about a week ago (finally) and there are no better instructions for getting started than those provided by digixmax here. Just ignore the statements about CM 11 and forge ahead. Later in that thread there are a variety of recommendations for file substitutions in the method if you are aiming for CM 12 instead of 11. I followed the ones here. These also work.
My own discovery was that you should ignore the TWRP error messages about being unable to mount '/bootdata'. I finally came across that somewhere and it proved to be true for me.
Take it slow. Gather together all the files you will need first. Then prep the SD card (don't forget to set the flag). Then copy the files over in the order specified. It matters. Then go for it! (don't neglect to backup the stock system before wiping things--you may be glad you did).
My start-up with CM 12.1 was really rough and I thought I might abandon it but after a few days and quite a number of reboots things settled down. Maybe that has something to do with coming from CM 10.2.1, maybe not. Anyway, the system is no worse than CM 10.2.1 and I don't have trouble with cold or warm boots hanging like I used to with CM 10.2.1.
My pet peeves are listed here and/or here but may be idiosynchratic to my device or particular flash.
Click to expand...
Click to collapse
I literally just finished sending a message to digixmax when you posted this. I remember seeing you in the other forum, trying to get CM12.1 to install. I did all this instructions over and over for hours, but I keep getting stuck at the CyanoBoot section. I get the Boot Menu, but then the SDC Recovery option isn't available, I see it, but it isn't clickable.
BornReady_ said:
I literally just finished sending a message to digixmax when you posted this. I remember seeing you in the other forum, trying to get CM12.1 to install. I did all this instructions over and over for hours, but I keep getting stuck at the CyanoBoot section. I get the Boot Menu, but then the SDC Recovery option isn't available, I see it, but it isn't clickable.
Click to expand...
Click to collapse
OK, so as soon as the cyanoboot screen appears you hold down the N button, right?
Also, did you boot with the power cable connected?
nmyshkin said:
OK, so as soon as the cyanoboot screen appears you hold down the N button, right?
Also, did you boot with the power cable connected?
Click to expand...
Click to collapse
Yes, I booted with the power cable connected, I tried on being connected to the laptop and power wall as well. I also held down the N button, which is why I got to the Boot Menu.
Bear with me
Are you sure you got the SD card version of TWRP?
Yes, 100% sure.
BornReady_ said:
Yes, 100% sure.
Click to expand...
Click to collapse
Well that was interesting! We're "live" apparently
I want to help but I'm not digixmax... I'll bet he has an idea. Wait for him to get back to you while I rummage around.
Lol, thanks for the help anyways though. I will have to wait for digixmax.
Wow, everytime you mention digixmax, he replies. He just privated messaged me in return.
If you can get to the CyanoBoot menu but its menu entry for "SDC recovery" is greyed out then it's because CyanoBoot (flashing_boot.img) cannot find a recovery.img file on your bootable SDcard.
Which version of SD-based recovery did you download and use?
You might want to wait for and check against the answer to my inquiry post at http://forum.xda-developers.com/showpost.php?p=65016892&postcount=41 (I no longer have a NT and as such cannot vouch for any specific recent recovery versions).
I'm sorry, I should have been more precise. I don't know if it will help, but this is the TWRP recovery image I used successfully when I tried this process. That's v. 2.8.6.0
digixmax said:
If you can get to the CyanoBoot menu but its menu entry for "SDC recovery" is greyed out then it's because CyanoBoot (flashing_boot.img) cannot find a recovery.img file on your bootable SDcard.
Which version of SD-based recovery did you download and use?
You might want to wait for and check against the answer to my inquiry post at http://forum.xda-developers.com/showpost.php?p=65016892&postcount=41 (I no longer have a NT and as such cannot vouch for any specific recent recovery versions).
Click to expand...
Click to collapse
I have seen everyone else's folders and they seem to include "flashing_boot.img" However, the file I downloaded from your page only has "flashing_boot" When I try to rename the file, the Nook Tablet won't even turn on anymore at all. Matter of fact, I can't even get to the Boot Menu now, it keeps having that red line that states, "booti: bad boot image magic (in memory)" I'm losing hope...
BornReady_ said:
I have seen everyone else's folders and they seem to include "flashing_boot.img" However, the file I downloaded from your page only has "flashing_boot" When I try to rename the file, the Nook Tablet won't even turn on anymore at all. Matter of fact, I can't even get to the Boot Menu now, it keeps having that red line that states, "booti: bad boot image magic (in memory)" I'm losing hope...
Click to expand...
Click to collapse
Don't give up. If you're using a Windows machine to prepare the card then whether the .IMG is displayed or not depends on your settings. It does not show on mine but a look at the file properties shows it is an .IMG file.
So that's the wrong tree. SDCards have been known to be problematic so if you have another around you might want to give it a try. You also might do a slow (complete) format on it before preparing it from scratch.
The other thing, of course, is the integrity of the individual files. Checking the MD5 values is a pain but sometimes reveals a bad download.
nmyshkin said:
Don't give up. If you're using a Windows machine to prepare the card then whether the .IMG is displayed or not depends on your settings. It does not show on mine but a look at the file properties shows it is an .IMG file.
So that's the wrong tree. SDCards have been known to be problematic so if you have another around you might want to give it a try. You also might do a slow (complete) format on it before preparing it from scratch.
The other thing, of course, is the integrity of the individual files. Checking the MD5 values is a pain but sometimes reveals a bad download.
Click to expand...
Click to collapse
I have tried everything. It doesn't seem to work. I'm also sure there aren't issues with downloading because I have redownloaded the files over 7 times. Is there a way I can download the folder of files that you used to install cyanogenmod?
BornReady_ said:
I have tried everything. It doesn't seem to work. I'm also sure there aren't issues with downloading because I have redownloaded the files over 7 times. Is there a way I can download the folder of files that you used to install cyanogenmod?
Click to expand...
Click to collapse
I've already shut down my computer for the night. I'll have a look at the size that an image of the card would be. Maybe that's the easiest way if there's room in my dropbox. If you've read through the CM11/12 thread you know I ran into problems and if you were to look at the CM10 thread you'd find me floundering around there also, so I know how frustrating it can be. And then suddenly it just works.
I'll let you know tomorrow.
BornReady_ said:
I have seen everyone else's folders and they seem to include "flashing_boot.img" However, the file I downloaded from your page only has "flashing_boot" When I try to rename the file, the Nook Tablet won't even turn on anymore at all. Matter of fact, I can't even get to the Boot Menu now, it keeps having that red line that states, "booti: bad boot image magic (in memory)" I'm losing hope...
Click to expand...
Click to collapse
As @nmyshkin pointed out, it's most likely because your Windows Explorer is configured not to display the file-name extension, so when you try to rename "flashing_boot" to "flashing_boot.img" you in effect end up with a file with name "flashing_boot.img.img".
This is likely also the root cause of your original problem: if you now just rename the TWRP recovery file you had downloaded (which already has the hidden .img extension) to "recovery" (and not "recovery.img" lest you end up with a file named "recovery.img.img") then CyanoBoot will see the recovery file.
For avoidance of doubt, just set your Windows Explorer to display file-name extension.
digixmax said:
As @nmyshkin pointed out, it's most likely because your Windows Explorer is configured not to display the file-name extension, so when you try to rename "flashing_boot" to "flashing_boot.img" you in effect end up with a file with name "flashing_boot.img.img".
This is likely also the root cause of your original problem: if you now just rename the TWRP recovery file you had downloaded (which already has the hidden .img extension) to "recovery" (and not "recovery.img" lest you end up with a file named "recovery.img.img") then CyanoBoot will see the recovery file.
For avoidance of doubt, just set your Windows Explorer to display file-name extension.
Click to expand...
Click to collapse
You are totally correct. I enabled Windows Explorer to display file-name extension and the TWRP recovery file turned out as "recovery.img.img" I am going to try it out now and reply with if it works or not.
Alright, I have been trying and following the instructions clearly, but it keeps giving me the red line stating, "booti: bad boot image magic (in memory)" now. I have gotten to the Boot Menu before, but now it won't even let me get there. What does this message mean?
BornReady_ said:
Alright, I have been trying and following the instructions clearly, but it keeps giving me the red line stating, "booti: bad boot image magic (in memory)" now. I have gotten to the Boot Menu before, but now it won't even let me get there. What does this message mean?
Click to expand...
Click to collapse
Is flashing_boot file on your SD card correctly named "flashing_boot.img", and not "flashing_boot.img.img"?