Related
First let me say that I installed CWM once already so I am fairly confident that I understand the basic steps. However, after I had initially installed CWM I tried to install a new ROM, but my tablet just hung on the "Viewsonic Birds" screen for like 45 mins. So, I shut down and booted to CWM but now my tablet is empty. I mean literally empty because I wiped everything in order to install the new ROM and somehow I messed that up big time because even that .zip file is no longer there. After some searching through the forums, I found a stock image of TnT 3588 and got it loaded, but in doing so lost CWM. So, I reinstalled CWM and saw it load (saw the cardboard box etc.), rebooted holding down Vol + key and saw the 'recovery key detected'. Then it goes to a screen with a progress bar and then it just boots normally....
Any help would be appreciated. Thanks!
I'm having the same issue after a nvflash that didn't take. Can't get into recovery.
I've had a few issues with that also. I try the SD card installer, drop it on the card named update.zip, reboot, it looks like it installs, but after rebooting it won't let me boot to CWM. So, I try the internal installer, drop it on the SD card named udpate.zip, it installs, I reboot, and go right into CWM. So either when I connect my tablet it somehow doesn't mount the SD card but mounts one of the internal partitions, or the SD and Internal installers were mixed up...
So I am a noob and I may not know enough to be rooted, but I love the custom ROM's they work so much better than stock. Anyway, I started using the new Theory of Ginger Candy ROM and all was going well, until I downloaded the power options download that lets you restart into recovery from the power options. I downloaded it and then rebooted into recovery using ROM manager then I installed the .zip file for the advanced power options. Then, I rebooted and it freezes up at the lightning bolt. I let it sit on there for 20 min thinking maybe it was just going to take a long time then I did a battery pull and rebooted and got stuck again at the lightning bolt. Next I tried to pull the battery and then reboot into recovery by holding the volume down key and power key at the same time. This reboots into bootloader and automatically runs bootloader and then it asks if I want to update. How can I stop it from running bootloader automatically and then be able to scroll down into recovery? Or do I just flash the Radio again and will that take me back to a stock ROM that is with the radio, and then I can restore my backup I made before installing this advance power option .zip. Thanks for your help guys!
Sounds like you still have a PG05IMG.zip on your sdcard. Can you pop the card out and remove it manually on your computer? Dunno if ADB's active during recovery, but you might also be able to get a shell via USB and delete the file that way and reboot.
Otherwise, you might be able to flash the file that currently exists, but I don't know what that's going to do; depends on which version is on your sdcard.
robertesteele said:
So I am a noob and I may not know enough to be rooted, but I love the custom ROM's they work so much better than stock. Anyway, I started using the new Theory of Ginger Candy ROM and all was going well, until I downloaded the power options download that lets you restart into recovery from the power options. I downloaded it and then rebooted into recovery using ROM manager then I installed the .zip file for the advanced power options. Then, I rebooted and it freezes up at the lightning bolt. I let it sit on there for 20 min thinking maybe it was just going to take a long time then I did a battery pull and rebooted and got stuck again at the lightning bolt. Next I tried to pull the battery and then reboot into recovery by holding the volume down key and power key at the same time. This reboots into bootloader and automatically runs bootloader and then it asks if I want to update. How can I stop it from running bootloader automatically and then be able to scroll down into recovery? Or do I just flash the Radio again and will that take me back to a stock ROM that is with the radio, and then I can restore my backup I made before installing this advance power option .zip. Thanks for your help guys!
Click to expand...
Click to collapse
Go to Frys or Radio Shack or best buy and buy yourself an SD card reader. Dont buy the most expensive one, just buy the cheapest one you can find. Take it home, slap the SD card in there and put it in the first USB slot you find. Open up the SD card on your computer and delete the PG05IMG.zip file. Youll see it at the bottom of the list if you organize by type.
Sorry buddy, I know I am the one that directed you to that post about the advanced power menu. It worked for me, I am really sorry this messed things up for you. In the past I have had a similar problem and as mentioned, getting that image file off the root of your sdcard is key. I too would recommend a microsd reader for your computer and making sure you rename or delete the image file. This will allow you to get back into CWM.
Props to you too for being a noob and still knowing enough to make a backup!
Thanks for you help everyone. I did make a back-up but I couldn't log into CWM recovery with the PGOIMG file on my SD card, and I didn't have a microsd card reader or anyway to plug the sd card into my computer to get the file off, so I found a tricky little way to do it. I pulled the SD card just barley out and held the battery in at an angle so that it didn't push the sd card back in. Then with the sd card out I was able to get into recovery. Then came the tricky part of getting the sd card back in without loosing a conection with the battery. I ended up using a bent paper clip to push the sd card into place. After a few attempts I was able to get the sd card in place and the battery back in place while staying in cwm. The next problem was that it sitll wouldn't recognize my sd card. I went into mounts and tried to unmount and remount the sd card with no luck, but then I noticed in the advanced options there is the option to reboot recovery. This allowed me to reboot back into recovery and then it saw my sd card. So after all that I was able to restore my back-up version of B1.7. I now promptly remove the PGOIMG file after flashing a radio.
I posted this question in the general forum but now I am posting it here because I think this is probably the more appropriate forum. So I am a noob and I may not know enough to be rooted, but I love the custom ROM's they work so much better than stock. Anyway, I started using the new Theory of Ginger Candy ROM and all was going well, until I downloaded the power options download that lets you restart into recovery from the power options. I downloaded it and then rebooted into recovery using ROM manager then I installed the .zip file for the advanced power options. Then, I rebooted and it freezes up at the lightning bolt. I let it sit on there for 20 min thinking maybe it was just going to take a long time then I did a battery pull and rebooted and got stuck again at the lightning bolt. Next I tried to pull the battery and then reboot into recovery by holding the volume down key and power key at the same time. This reboots into bootloader and automatically runs bootloader and then it asks if I want to update. How can I stop it from running bootloader automatically and then be able to scroll down into recovery? Or do I just flash the Radio again and will that take me back to a stock ROM that is with the radio, and then I can restore my backup I made before installing this advance power option .zip. Thanks for your help guys!
Delete PGO5IMG.zip from your SD card.
feedhead said:
Delete PGO5IMG.zip from your SD card.
Click to expand...
Click to collapse
Uh... Yep! I think that we've found the problem! Ha!
If you don't have a SD card reader there is a trick over in the General forum for how to get around that!
Thanks for you help everyone. I now know to delete the PGOIMG file from my sd card promptly after flashing a radio. I couldn't find the way around not having an sd card reader but I did find a way around it. I did make a back-up but I couldn't log into CWM recovery with the PGOIMG file on my SD card, and I didn't have a microsd card reader or anyway to plug the sd card into my computer to get the file off, so I found a tricky little way to do it. I pulled the SD card just barley out and held the battery in at an angle so that it didn't push the sd card back in. Then with the sd card out I was able to get into recovery. Then came the tricky part of getting the sd card back in without loosing a conection with the battery. I ended up using a bent paper clip to push the sd card into place. After a few attempts I was able to get the sd card in place and the battery back in place while staying in cwm. The next problem was that it sitll wouldn't recognize my sd card. I went into mounts and tried to unmount and remount the sd card with no luck, but then I noticed in the advanced options there is the option to reboot recovery. This allowed me to reboot back into recovery and then it saw my sd card. So after all that I was able to restore my back-up version of B1.7. I now promptly remove the PGOIMG file after flashing a radio.
I just book the 8G nook tablet. I comes with 1.4.2 so from reading different threads I thought the it would be easier to root with 1.4.0 so I tried the 1.4.0 SDcard.
Ever since my tablet won't turn on. I even tried http://forum.xda-developers.com/showthread.php?t=1470910 But no luck.
Any ideas or suggestions of what to try?
hold n and power button till it turns on. make sure sd card is ejected
Sent from my sensation 4G
nba1341 said:
hold n and power button till it turns on. make sure sd card is ejected
Click to expand...
Click to collapse
I held them for over a min, no response.
ajprog said:
I held them for over a min, no response.
Click to expand...
Click to collapse
Will the unit still boot from the 1.4.0 sd card? If so, you could try to reflash that again. Otherwise, I would keep trying to hold down both of those buttons (without the sd card in) for even longer. I had some instances where I thought mine was bricked (I have the 16 gb model), but eventually it came around. No real rhyme or reason to it.
Bob
Well assuming by this thread that Adam's 1.4.0 Booted and trashed your system.... you'll either have to try taking it back in and playing real real stupid, like too stupid to program the vcr stupid, or you'll just have to wait until someone makes recovery for the 8GB nooks.
Let me explain, the Boot Loader files for 1.4.0 are designed to run for the 16GB devices only, it wasn't until 1.4.2 (which is available for both devices) that B&N modified the Boot Loader files to run on both 16GB and 8GB. Therefore when MLO tries to initiate memory it's trying to initiate for the 16GBs 1GB memory as opposed to the 512MB of the 8GB device, this will cause the device not to boot.
the boot sd methods for 16gb dont
even work for 8gb so how could you even mess anything up? you sure you removed sd card?
Sent from my sensation 4G
I'm guessing you had SD in there and connected usb cable, it attempted to boot form sd and locked up with nothing happening on screen. Just tried it on the 8gb that I have here (just opened box this minute)
If thats the case all you need do is remove sd card, remove USB cable and hold power for 15 seconds. Then wait a couple of secs and power it back on with the power button again. If like mine it will boot back up fine and isn't bricked.
CelticWebSolutions said:
I'm guessing you had SD in there and connected usb cable, it attempted to boot form sd and locked up with nothing happening on screen. Just tried it on the 8gb that I have here (just opened box this minute)
If thats the case all you need do is remove sd card, remove USB cable and hold power for 15 seconds. Then wait a couple of secs and power it back on with the power button again. If like mine it will boot back up fine and isn't bricked.
Click to expand...
Click to collapse
Ok so there is a simple solution to this with the SD Root that is provided by Indirect. After you have a CWM SD Card by using winimaging (or what ever its called)take the MLO and the u-boot.bin from the 1.4.2 update package and place them inplace of the MLO and u-boot.bin on the SD Card. Once you have done that get the update.zip from B&N and flash that. That should fix most of your problems.
PS. The reson that he cannot get it to work is that the update.zip's uboot and MLO are form 1.4.0 which did not support the correct addressing.
Loglud said:
Ok so there is a simple solution to this with the SD Root that is provided by Indirect. After you have a CWM SD Card by using winimaging (or what ever its called)take the MLO and the u-boot.bin from the 1.4.2 update package and place them inplace of the MLO and u-boot.bin on the SD Card. Once you have done that get the update.zip from B&N and flash that. That should fix most of your problems.
Click to expand...
Click to collapse
I was about to do that but was also going to compile a new kernel. You reckon it will work without the new kernel do you? I best have a go
CelticWebSolutions said:
I'm guessing you had SD in there and connected usb cable, it attempted to boot form sd and locked up with nothing happening on screen. Just tried it on the 8gb that I have here (just opened box this minute)
Click to expand...
Click to collapse
No nothing is in there, when you use the 1.4.0 SDcard it loads the update image and replaces the current image. I thought there would be check so it wouldn't put a bad image that wouldn't work in place but I guess there isn't any safety checks on the built in update firmware routine.
Loglud said:
Ok so there is a simple solution to this with the SD Root that is provided by Indirect. After you have a CWM SD Card by using winimaging (or what ever its called)take the MLO and the u-boot.bin from the 1.4.2 update package and place them inplace of the MLO and u-boot.bin on the SD Card. Once you have done that get the update.zip from B&N and flash that. That should fix most of your problems.
PS. The reson that he cannot get it to work is that the update.zip's uboot and MLO are form 1.4.0 which did not support the correct addressing.
Click to expand...
Click to collapse
Are the new files posted yet with the correct addressing for the 8G? Or is there instructions on how to get them from clean 8G?
This is what I did to brick my NT. http://forum.xda-developers.com/showthread.php?t=1402190
Yes my NT is bricked, I have tried numerous times to shut it down (incase the screen was blacked instead of off) and turning it back on.
I have tried both the factory reset (power and home) and just the power button.
I as much as I can guess, when I did the firmware update above I messed up the internal booting. So I need to have the files for 8G so I can boot off of an SDcard.
I checked the B&N website if they had the 1.4.2 files (MLO and u-boot.bin) but they only have one updates file which I figure is for 16G.
Yup you're screwed take it into B&N and hope they'll replace it.
We have a working 8G SD boot!!!
http://forum.xda-developers.com/showthread.php?t=1517513
Thanks to bauwks and AdamOutler I now have some life (not fully restore yet) but it is progress.
probably many others would like to know what you did
Just looking at a few other threads, I think several people have made the same mistake and are looking for solutions on this. If you can give some additional details as to what you had to do to get going again, it would be helpful.
It still isn't working, but we have the first step done which is getting the 8GB to boot off the SDcard, they are now working on the Ubuntu recovery SDcard.
I will post back here when there is any more progress.
drt4nrg said:
Just looking at a few other threads, I think several people have made the same mistake and are looking for solutions on this. If you can give some additional details as to what you had to do to get going again, it would be helpful.
Click to expand...
Click to collapse
ajprog said:
We have a working 8G SD boot!!!
http://forum.xda-developers.com/showthread.php?t=1517513
Thanks to bauwks and AdamOutler I now have some life (not fully restore yet) but it is progress.
Click to expand...
Click to collapse
I jast passed a copy of all the internal partitions onto Adam so you should now be able to completely restore you're 8GB NT back to stock. Or if you now have adb access via SD card I posted the files on the forum so you could quite easily restore the system completely yourself.
CelticWebSolutions said:
I jast passed a copy of all the internal partitions onto Adam so you should now be able to completely restore you're 8GB NT back to stock. Or if you now have adb access via SD card I posted the files on the forum so you could quite easily restore the system completely yourself.
Click to expand...
Click to collapse
Unfortunately I don't know of any full images for SDcards that have be released yet for 8GB. I only know of the 2uboot which "crashes" when it reads the internal image to create the menu.
If anyone can help me get something else to work like maybe CWM that would be appreciated.
I'm out all day today (uk and I'm on way to work) but I'll happily help you later when I'm home.
HELP!!!
i was attempting to downgrade the software back to 1.4.0 with the acclaim download and my nook tablet went to black screen. now the only thing it does is occasionaly bing when i plug it to the computer. i cant tell if the thing is on or off. What do i do?
send it back to b&n and tell them it won't boot. that what I did and they gave me a new one. if you search thru the forum, you'll see that I missed the warning too and bricked. posted a warning after that and you missed it too.
Damn google search and my lazy ass, went straight for the fix.
So we are all confused with the tablets that boot straight to SD from power button and others that boot from usb cable put in. Everyone wants to see the tablets boot straight to sd when they hit the power button.
As seen in the below video, I was able to turn a usb only boot tablet into an always boot to sd from power tablet by forcing my tablet to brick and then recovering it. this got me thinking... maybe Barnes and Noble isnt as inconsistent as I thought... maybe they made all tablets to boot from usb and something some of us have done caused them to now always boot without usb.
Video: http://www.youtube.com/watch?v=0HC9XL_9aXk
So, I need some tester. I am not responsible for the loss of your tablet, you do this at your own risk.
Requirements: You need to have an 8gb or 16gb nook tablet that can currently only boot to SD from usb. This means that with bootable sd in, you can not boot to sd by hitting the power button from an off state and you require the usb cable to be connected from an off state to boot to SD.
File you must download: We are going to test this with the CWM bootable SD cards I have made: File here: http://forum.xda-developers.com/showthread.php?t=1439630
FIRST Make the SD card and then make sure you cant boot to it from the power button, and then make sure that you can boot to it from the usb
Second Make sure you make a backup of your tablet, I am not going to tell you to do anything that will brick you, but I am not going to be responsible for lost data... or atleast not bricks that I dont know how to get out of
Stop testing at any point that you become successful
Third TEST 1 Perform an 8 failed boots
With the SD card in and the tablet off, I want you to hold the power button down until you see the black N appear and maybe a white screen and the tablet turn off. This is one failed boot. Do this 7 more times and then let it boot the 9th time and allow it to factory restore. Now test to see if you can boot to sd with power button, if not, test with usb.
Fourth TEST 2 Unrooter http://forum.xda-developers.com/showthread.php?t=1380235
Root your tablet, then install the unrooter app, and then run the unroot script from the app
Test power and usb boot again
Fifth Test 3 Brick (8gb only)
Install cm7 rom, should brick on bootup, then flash back your recovered rom that you should have made before you started all this crap. Then test boot again for power or usb.
Fifth Test 3 brick (16gb only- Warning, I have not tried this)
Install my recovery rom for the 8gb NT, I think it might brick, then restore back with the recovery you should have made before starting all this.
Sixth Test 4: CWM, after installing CM7, clear cache, factory restore and clear devlic. Then restore back to your recovery and test.
Make sure you post as soon as something becomes successful. Do not proceed if something started working.
Please report back in this thread your findings.
Sorry Albert, I just noticed this thread. I will get a hold of an 8gb nt this weekend that I'm fairly sure only boots with usb.
albertwertz said:
So we are all confused with the tablets that boot straight to usb from power button and others that boot from usb cable put in. Everyone wants to see the tablets boot straight to sd when they hit the power button.
Click to expand...
Click to collapse
Albert - thank you for looking into this. Bless you if this can be resolved. Just a quick note about your post, however: I think there are several places you talk about "boot to usb" when you meant "boot to sd". I've made the same typo lots of times myself.
I am one of the people who can only boot with USB attached. I will be HAPPY to try this out as soon as I can.
So interesting thing here, my nook tablet behaves differently depending exactly how long I hold down the power button and the home button.
If I hold it down for ~1 second after the "boot flash" (screen flashes)
it will boot to the sd card
if I hold it down much longer and it either turns off, or reboots (or tries recovery)
an odd thing is if I turn off the power, let it power off completely, wait an hour and turn it back on, it almost always boots SD and then any further reboot boots to stock.
DemonicPhantasm said:
So interesting thing here, my nook tablet behaves differently depending exactly how long I hold down the power button and the home button.
If I hold it down for ~1 second after the "boot flash" (screen flashes)
it will boot to the sd card
if I hold it down much longer and it either turns off, or reboots (or tries recovery)
an odd thing is if I turn off the power, let it power off completely, wait an hour and turn it back on, it almost always boots SD and then any further reboot boots to stock.
Click to expand...
Click to collapse
Is this after any of Albert's experiments or just as you have it now? What root method did you use? 8GB or 16GB?
Ok, so I managed to pick up the 8gb NT today. It has been previously rooted. Here are the results of TEST 1:
First try, I must have miscounted because on what I thought was the 9th time, it loaded normally, and did not try to factory restore.
On the second attempt, @ power-on no.5, CWM loaded.
Third attempt, CWM loaded @ power-on no.2
Forth attempt, CWM loaded @ power-on no.4
At no point was the usb lead attached. Also I was only using the power button, never touching 'n'.
Will I remove the card, do a factory restore and proceed to TEST 2?
pretence ryiutte
PlacidCat said:
Is this after any of Albert's experiments or just as you have it now? What root method did you use? 8GB or 16GB?
Click to expand...
Click to collapse
16 GB root through the SD card, I've since done a complete factory restore from the 8 boot recovery partition and the behavior persists this way.
I haven't had a chance to mess with it, since my wife sold her nook which I used for reading books while I messed with mine...
I got a new 16GB class 4 card on which I've backed up my apps with TB. I hope I will have some time to do some tests in the next few days. I have a bootable 32GB card (SanDisk class 4) with CM7 alpha final on it that I'll use as my test card for booting.
My Tablet is a 16GB model, so I'll likely have to try the "brick" with the 8GB image of CM7.
los101, so I am confused, did it work with just powering it on to start? or just doing 8 failed boots got it to boot to sd with just power and not usb?
FWIW... Just got my wife a n 8GB Nook Tablet for our anniversary. I used my MacBook to image your root card from this thread:
http://forum.xda-developers.com/showthread.php?t=1439630
I imaged it to a 2GB Kingston card. No idea what class it is because I haven't tested it. Stuck it into the 8GB NT, booted it *without* the power cable and it boots to SD just fine.
I then stuck in the 32GB Sandisk class-4 card onto which I installed CM7 alpha final... and it booted to stock.
It would seem we still might have a card issue, not just an internal issue. Tried turning off the 8GB NT, ejected the 32GB card, re-inserted it, still booted to stock. Turned the tablet off, removed the 32GB card, replaced the 2GB card and it immediately booted into the CWM recovery tool.
I then rooted by applying the zip using CWM from the 2GB card. Rooted successfully and asked CWM to reboot. Tablet rebooted to the (rooted) stock. I turned off the Tablet, turned it back on with the 2GB card still inserted and it, again, booted immediately to the CWM menu.
ALL BOOTS (except from CWM menu) WERE DONE WITH JUST THE POWER BUTTON. No finagling with the "N" button required.
I don't know if this helps, Albert. I'll still plan on eventually testing on my 16GB model. Also, when I have a free moment, I'll see if the 2GB card boots on my 16GB NT. If it does, what I would find interesting is if there is a way to get cards in general to boot more reliably across the board.
Edit: BTW - the 32GB Sandisk does boot to CM7 using the power cable.
Edit 2: Yes, indeed, the 2GB CWM root utility card boots great on my 32GB tablet without using the power cable (just pressing power).
albertwertz said:
los101, so I am confused, did it work with just powering it on to start? or just doing 8 failed boots got it to boot to sd with just power and not usb?
Click to expand...
Click to collapse
Booted off SD just by powering on. '8 failed boots' was not required.
You know, just had a thought. I can try writing the CWM root image to the 32GB Sandisk SD card to see if it truly is the card at fault or how the partitions are set up. I'll also expand the last partition to fill the entire card as a test.
Is there anything fundamentally different in how the boot partition is set up for your root image over the CM7 (external SD) image, Albert? I want to make sure my tests actually are valid for comparison's sake and that I'm not just making the proverbial comparison between two dissimilar fruits...
I have CM 7 and have tested booting on two NTs that I have. I also have 32GB, 16GB and 8GB SD cards (each created from the same image and then increasing the 4th partition to full capacity for the card), and each behaves the same as the other depending on which NT I use. One NT always boots directly to CM7 using any of the cards, the other does not. However, if I first tether the one that doesn't normally boot to CM7, and immediately remove the tether when the first screen comes on, the unit will boot to CM7 (as expected) but will the always boot to CM7 again without tethering (even after a reboot to NT mode, a shutdown and then a new power on) until the unit is charged. After a charge I then have to re-tether the NT once, removing the tether quickly at power on, and from then on tethering is not required (again, until the next charge) just like before.
This behavior is fully repeatable for me and has been checked over the course of several weeks. It's magic I'm sure.
PJLLB said:
... It's magic I'm sure.
Click to expand...
Click to collapse
My vote is Leprechauns.
PJLLB said:
...
However, if I first tether the one that doesn't normally boot to CM7, and immediately remove the tether when the first screen comes on, the unit will boot to CM7 (as expected) but will the always boot to CM7 again without tethering (even after a reboot to NT mode, a shutdown and then a new power on) until the unit is charged. After a charge I then have to re-tether the NT once, removing the tether quickly at power on, and from then on tethering is not required (again, until the next charge) just like before.
This behavior is fully repeatable for me and has been checked over the course of several weeks. It's magic I'm sure.
Click to expand...
Click to collapse
This has been working for me when using the CelticWebSolutions' CM7 SD, but I found that it does not work for the Succulent "CM9 SD" (created using the method posted here).
digixmax said:
This has been working for me when using the CelticWebSolutions' CM7 SD, but I found that it does not work for the Succulent "CM9 SD" (created using the method posted here).
Click to expand...
Click to collapse
I had trouble getting succulents dual boot setup to boot at all. Neither from power button nor usb cable. I finally got it to work by burning celticwebsolutions cm7 image to sd (which booted perfectly from the power button), and modifying it with MiniTool Partition Manager per succulents instructions. It worked perfectly. Now I have stock rooted 1.4.2 on emmc and cm7/cm9 on sd. See my description here.
Perhaps this is not the place for this oddity/question, but I am attempting to root my 16GB NT and it will not boot to SD by *any* method. Neither Power, nor Power+N work, and when I try USB method, it will boot to stock after about 2-3 minutes, whether I've left the cable plugged in or not. Ideas?
wbickler007 said:
Perhaps this is not the place for this oddity/question, but I am attempting to root my 16GB NT and it will not boot to SD by *any* method. Neither Power, nor Power+N work, and when I try USB method, it will boot to stock after about 2-3 minutes, whether I've left the cable plugged in or not. Ideas?
Click to expand...
Click to collapse
In my experience, if the NT cannot boot off an SD card with powered USB then the problem lies with that SD card's format and/or content. You would be better off researching & asking your question in the forum thread that covers the SD-card rooting method you're using.
I am using Albert's R3 SD card (4.6 I think) method, one I created from his video instructions not one received from Albert. But I did locate Albert's troubleshooting thread and will try reposting the issue there, thanks. Otherwise, I'd be happy to help with the experiment!
wbickler007 said:
I am using Albert's R3 SD card (4.6 I think) method, one I created from his video instructions not one received from Albert. But I did locate Albert's troubleshooting thread and will try reposting the issue there, thanks. Otherwise, I'd be happy to help with the experiment!
Click to expand...
Click to collapse
I too was not able to create a bootable R3 card, until I abandoned using PowerISO to assemble files for the R3 disk image -- see my post here re: the alternative method suggested by Albert.