>This is a solution, not a question<
I am following the instructions in this thread:
[UNOFFICIAL][ICS][NIGHTLIES] CM9/ICS Nightly Builds
http://forum.xda-developers.com/showthread.php?t=1444943
I used Win32DiskImager (thanks bobtidey) to load the img. I held the Nook N key and then pressed and held power until the "Loading..." message appears and iIt booted up, the linux penguin showed, and I got...
Error! Unexpected lack of boot partition on the SDCARD!
Please report!
Poweroff when ready
BUT, I booted a second time and it loaded and installed ICS. So, if you are having that problem, try it a couple times before you give up.
If the very first time installing ROM, you do NOT need to hold the N & pwr button.
Related
Using the verygreen instructions I have been running CM-7.0.3 encore signed off of SD for about 2 months now and want to try to update to the current nightly.
I put cm_encore_full-176.zip in the /boot directory of the SD and tried all of these without success:
1) Used the boot select u-boot.bin to boot from sd and recovery. It just hangs.
2) Used the boot select u-boot.bin to boot from sd and alternate. It just hangs.
I reverted to the standard u-boot.bin and did these without success:
1) Booted into CM7 then using the shut down menu rebooted into recovery. The update was not applied and boot was normal.
2) From power off, held down the power on and N buttons. After loading... appeared counted to 4 and released both buttons. No update applied and booted normall.
3) From power off, held down power on and N buttons. After loading... appeared, released power button, then pressed and held it for 5 seconds, waited for the screen to blank and let go of both buttons. No update applied and NC shut off.
Anyone know what I am doing wrong? I have been scouring all of the NC root sites and it seems everyone has a different hold buttons and release sequence. Is there a special /boot folder or something that can only be accessed while the sd card is in the NC where I have to copy the update zip file?
Imbroglio said:
1) Used the boot select u-boot.bin to boot from sd and recovery. It just hangs.
2) Used the boot select u-boot.bin to boot from sd and alternate. It just hangs.
Click to expand...
Click to collapse
Why you doing that?
Because there were recommendations to do to those steps on this site and others.
Do you have a solution to my problem?
You are going from a .29 kernel to a .32 kernel... From VG's SASD thread... first post... you need to update the version of the SASD.
How to update if you already installed using older version of the installer and don't want to reinstall (understandably):
•Get update zip from http://crimea.edu/~green/nook/update-genimage-1.3.zip
•Put the zip file as is onto the first partition of your sdcard..
•reboot into recovery (triggered by the keys, the reboot into recovery does not work yet).
•The new version would be installed and you are done.
•You can combine this installation together with updating to .32 kernel in one step. Just put the update-cm file and the update-genimage-1.3.zip to the first partition. Make sure there is still at least 1M of space left!
Click to expand...
Click to collapse
Imbroglio said:
Because there were recommendations to do to those steps on this site and others.
Do you have a solution to my problem?
Click to expand...
Click to collapse
Just put the new nightly build into the root folder and boot into recovery.
The only thing you need to do is your skill to boot into recovery, that's all.
The rest should be taken off.
DizzyDen said:
You are going from a .29 kernel to a .32 kernel... From VG's SASD thread... first post... you need to update the version of the SASD.
Click to expand...
Click to collapse
Ok copied the file onto /boot.
Tried a different button sequence:
http://www.youtube.com/watch?v=Kps9cWvyzqo
It still will not go into recovery mode. The thing is that I used the instructions on the video to help me install CM7 and gapps in the first place and it worked fine.
What exactly is the correct button sequence to get the NC to power on to recovery mode?
As you can see I found 3 different people saying to do it 3 different ways and none of them seem to work.
I am waiting for someone to say you have to wait until the 4th tuesday of the odd numbered month and hold down the buttons to the count of pi * the number of times Lindsay Lohan violates her probation in the past 4.5 months.
Do I need another program installed for this to work? Something like clockwork recovery mod (whatever that is)? Is there a difference that my NC doesn't say "Touch the Future of Reading" but just says "Loading..."?
It is making me pull my hair out and I didn't have that much hair left to begin with!
Just wanted to add an observation that after doing the button sequence in the video, "Loading.." the screen blanks for about .5 second and then is displayed again off center. The it goes into normal boot up.
Imbroglio said:
What exactly is the correct button sequence to get the NC to power on to recovery mode?
Click to expand...
Click to collapse
I've had to use the "rhythm method" for the first time in a while this week, setting up my dual boot on eMMC, and verygreen's instructions were the only thing that worked for me:
verygreen said:
hold nook N key and then press and hold power until the "Loading..." message appears and then disappears with screen going blank. Release power button, then press it again and hold for ~5 seconds, the bootloader "Loading..." message should be on the screen for three seconds or so before you release power button, keep holding N button until screen blanks again. If the screen went off while you were holding the power key, that means you were holding it for too long
Click to expand...
Click to collapse
This:
Imbroglio said:
Just wanted to add an observation that after doing the button sequence in the video, "Loading.." the screen blanks for about .5 second and then is displayed again off center.
Click to expand...
Click to collapse
is what should be happening--when the message comes back, press the power button again for five seconds, then release. Anamardoll's videos were made prior to the B&N 1.2 update, prior to CM7.1's existence, and prior to any of verygreen's SASD updates, so the behavior was a little different then.
Also, you may have successfully booted into recovery and installed the SASD 1.3 update file without realizing it--small packages can flash very quickly in verygreen's installer, and iirc, the "Loading" message you describe is expected behavior for SASD 1.3. If you look at the SD's boot partition in your PC and the .zip file is gone, it very likely installed. If that's the case, Power > Reboot > Recovery ought to be working now; copy over the CM7 update .zip, attempt the rhythm method again (may as well), and if you go straight through to CM7, try Power > Reboot > Recovery.
If none of the above works, you have very likely hosed your boot sector with some of the shenanigans in your OP, and may as well format the card and start from scratch with an up-to-date SASD image.
Imbroglio said:
Do I need another program installed for this to work? Something like clockwork recovery mod (whatever that is)?
Click to expand...
Click to collapse
CWM cannot help you with an SD install. If, however, you have chosen at any point to "Flash ClockworkMod Recovery" from ROM Manager, then you've already written CWM to your internal recovery partition, and might want to consider installing CM7 internally, as it would now be much easier than fixing your card (assuming none of the above got it done).
Thanks for the help all.
I am just going to redo the sd with the 177 nightly.
I downloaded the CVM 5.0.4 and now every time I do this on repeat REBOOT I G. Rickover =
What do \?
I want to go first?
This started since last weeks for a lot of peoples using the new "Official" CWM recovery image.
http://forum.xda-developers.com/showthread.php?t=1519635&highlight=boot+into+cwm
http://forum.xda-developers.com/showthread.php?t=1528929
http://forum.xda-developers.com/showthread.php?t=1528490
Other people are having issues with 5.5.0.4 as well. You should read through the 5.5.0.4 thread to see what others are doing.
If your tf is only booting into recovery then power it off by holding the power button for 10-15 secons.
Power it on holding Power and Volume down button.
When writing shows up DO NOT PRESS UP, just wait.
Then you will get two images on the screen, the one on the left is wipe data, the one on the right shows a little android guy and says boot linux.
You want to press vol down until the android guy is highlighted then press vol up and you'll boot into android.
I'd recommend going back to a known working recovery like 3.2.0.1 You can either flash it via the recovery you currently have, or GnuFabio's Recovery Installer Apparently it's not as simple to overwrite... See post above mine.
This is a really good example of why you should always READ through a thread before flashing/tweaking/installing!
ive been running rouge recovery here: http://forum.xda-developers.com/showthread.php?t=1446019 and ive had ZERO problems its not the newest, but its super stable and haven't had any problems flashing any of the honeycomb or ICS roms... check it out
i install 5.2.0.7 with nvflash .
is work good
How you flashed via NVFLASH?
What SN have you? B70 or +?
I have a old honeycomb version and was good until I found the microsd card slot was bent so I can't boot any sd... then I wiped data/cache and it will only show the setup wizard and I can't click the android guy. I then followed the directions in various posts trying to use the 8 failed boot attempts and format system but to no avail. NOw it won't boot at all... Can I use adb to flash a stock system boot and data img?
I read somewhere something like this,you can try it
1. turn the Nook completely off
2. turn it on and immediately on seeing the first message "the future of reading" press and hold the power button until it turns off again
3. repeat this 7 more times for a total of 8
4. on the 9th time, let the Nook completely reboot without holding the power button - you will see a message saying "installing a software update..." and after this everything will be back to factory new (the system will be totally restored)
If you're missing the timing, I believe there is a way to use a script with adb to cause 8 fail boots and force the restore. I can't find it off hand, but I'm sure if you do some searching it'll come up.
Nikola_r said:
I read somewhere something like this,you can try it
1. turn the Nook completely off
2. turn it on and immediately on seeing the first message "the future of reading" press and hold the power button until it turns off again
3. repeat this 7 more times for a total of 8
4. on the 9th time, let the Nook completely reboot without holding the power button - you will see a message saying "installing a software update..." and after this everything will be back to factory new (the system will be totally restored)
Click to expand...
Click to collapse
You don't even have to count....Just keep doing the interrupted boots until the nook tells you that it is resetting.
This is a painful message to write, but I am desparate. This should be so simple!
Have a U8800 standard (at least it says only "U8800" in settings/about phone.
What have I done:
- Upgraded some time ago to 2.3.5 Rev B522 from Huawei.
- Then rooted it with SuperOneClick.
- Installed ClockWorkMod from Play Store.
- Downloaded CWM Recovery 5.5.0.4 stable from xda and placed the file into the /.cust-backup/image folder via Remount.
- Turned off Fast boot under settings/applications
:: What worked/happened.
- Rooting went fine, ES file explorer and others get root-permissions ok.
- But got into CWMRecovery only via CWM program (Choosing "Reboot into recovery"). Never with the holding buttons vol+ and power-button during power-on.
Figured it was that locked bootloader on B522 that was the problem.
What I did:
- Followed the instructions in http://forum.xda-developers.com/showthread.php?t=1457490 (Get your pink screen back).
- In CWM Recovery flashed "update-B518-bootloader.zip".
- Got "ok installed or something to that effect" from CWM Recovery.
:: What worked/happened.
- Still could not get into CWMRecovery via button-holding. Tried reflashing the B518 bootloader a few times, but just no difference.
Read somewhere that each Huawei firmware-release comes with it's own bootloader, so lets try to install Huawei B518.
- Only place I could find the image was here http://huaweiideosx5.blogspot.no/2012/03/u8800-b518-23-software.html
- U8800V100R001C00B518G001.zip
- Had to take out the external SD-card to get the /sdcard/dload directory on the internal SD-card.
-Seems to be important to have dload on the internal SD-card and not the external.
- Booting the phone with vol+, vol-, power did not start the downgrade, but was able to trigger it via settings/storage/software upgrade.
After downgrade to B518 (Checked version in settings/about phone):
- Deleted /sdcard/dload directory.
- Rooted with SuperOneClick
- Installed ClockWorkMod from play store again.
- Put CWM Recovery 5.5.0.4 into ./cust_backup/image again (think this was unecessary. I think it was already there but did it anyways)
- Turned off Fast boot under settings/applications.
:: What worked/happened.
- The phone is now in B518 software, but still can not get into CWM Recovery via keypressing at boot.
I hold the vol+ and power-buttons all the way to "desktop" so to say, but can not for the life of me get into CWM Recovery that way. Getting into CWM recovery 5.5.0.4 via instructing CWM application to boot into recovery works fine, though.
I am drooling at the thought of ICS Aurora, but I don't dare before I can reliably get into CWM Recovery via keypress.
Sorry if this is very stupid post, but I have tried so much.
Maybe the volume buttons are faulty? Turn off the phone and try this: hold down volume up; while holding press power button as long as the logo comes up. Release power button but continue holding volume up. If it did not work, try doing same with volume down.
Yeah, do what Blefish advised you but do it while the phone is off and charging. I have a kinda broken power key and with this 'trick' it boots faster and more reliable. Keep holding the 3 buttons until you see the recovery.
Sent from my U8800
Thank you both for trying to help me here!
Unfortunately I have had no luck with your suggestions.
Re: Broken keys.
Power and volume-buttons seems to work well when the phone is on. Also when I boot into recovery through the CWM program, navigate to advanced/key-test, the vol+, vol- and power button seems to work well there too.
On pressing the power-button, CWM-R reports Key: 116
On pressing the vol+-button, CWM-R reports Key: 115
On pressing the vol--button, CWM-R reports Key: 114
So I think the keys must be ok, right?
Blefish: I did what you suggested, as I understood it.
When the phone boots, there are three stages of logos.
1. A static logo of Huawei's red "fan?".
2. A short "comet" animation.
3. An animated logo of Huawei's "fan", where some highlight flashes from left to right over the fan.
I hold the power-button in until I see the first static logo, then let go of the power-button and hold the volume-key(s).
Is this the same stage in the boot-process that you were thinking of?
I have tried vol+, vol- and both vol+ and vol-, together with releasing the power-button at that point.
Have not had any success with that, and ended on the "desktop" each time.
AceDroidX: I tried your suggestion as well.
I did this:
1. Shut down the telephone
2. Plugged in the power.
3. A "fan"-logo appears which is replaced by an animated battery.
4. Upon seeing the animated battery, I tried the various key-hold variants.
- vol+ and power : Ended up at desktop.
- vol- and power : Ended up at desktop.
- vol+ and vol- and power : Ended up at desktop.
So not much success either.
I am out of ideas... Can it be that B522 bootloader that still lingers in there, not replaced by installing the B518 software?
Well, idk what else to suggest.. Maybe your problem is here?
Downloaded CWM Recovery 5.5.0.4 stable from xda and placed the file into the /.cust-backup/image folder via Remount.
Click to expand...
Click to collapse
I remember that when i mount my phone in linux, there was a partition with just the image folder. Some files like boot.img and recovery.img where there. Try to put the recovery image in there and see if it makes any difference.
I'd like see your versioninfo, can you upload a screenshot?
You can check mine from B528
AceDroidX: When I use Remount, I am able to mount that partition as read/write so that I can copy CWM's Recovery image in there. I think it is identical as mounting it up remotely, as you do. I am after all able to boot into CWM-Recovery, just not by key-pressing? I suppose I could boot into Linux and try to mount up the partitions as you do.
Hi kilroystyx: I can not figure out where to find a similar-looking page as the one you have in your picture.
I have the settings/about phone, if that is an older version of what you have there?
Treq01 said:
Hi kilroystyx: I can not figure out where to find a similar-looking page as the one you have in your picture.
I have the settings/about phone, if that is an older version of what you have there?
Click to expand...
Click to collapse
You have to dial *#*#2846579#*#*
Off.. I completely forgot about that place!
Here are the right screenshots.
What can you see from this?
Treq01 said:
Off.. I completely forgot about that place!
Here are the right screenshots.
What can you see from this?
Click to expand...
Click to collapse
Based on the screenshots your installation is fine.
Just one last shoot based on what AceDroidX says, with phone off press Vol+ and hold then connect USB cable to PC or charger and stay holding Vol+ then wait...wait and what you see?
hi all,
i'm using some ics roms and it seems ics supports natively vol++power button to take screenshots but it doesnt work for me... do you know if there are some custom ics rom where it will work?
thank you
Wow.. It is hard to believe.. but I have actually ... eventually found a way to get into that CWM-Recovery every time.
It is a combination of your suggestions.
I have been doing variations, trying to figure something out and eventually there is a method.
What I must do, on this phone, in order to get into CWM-R is this:
1. If the charging cable is in, then unplug first.
2. Turn the phone off.
3. Take out the battery and put it back in.
- This makes a difference on my phone, at least. I am not able to get into CWM-R wihtout taking the battery out first.
4. Press and hold Vol+
5. With Vol+ being pressed continously, insert the charging-cable.
6. Wait for the Fan-animation to finish and the "battery-charging" animation to start.
7. When the battery-charging animation is running and the screen eventually goes black, keep holding the Vol+ button for some time.
- Sometimes it works to keep holding the Vol+ button for only a second or two. Sometimes I must hold it up to 30 seconds.
7. Press and hold the power-button in addition to the Vol+
8. Wait for CWM-Recovery to start.
Thank you very much for your help.
Now I think I can try for ICS!
imsonica said:
hi all,
i'm using some ics roms and it seems ics supports natively vol++power button to take screenshots but it doesnt work for me... do you know if there are some custom ics rom where it will work?
thank you
Click to expand...
Click to collapse
Try Vol- and Power ON
OK so hi guys,
after I tried, search, read tons of stuff, I finally decided to post a thread because I have no clue what else I could do.
I have have a lenovo tab4 8 plus / tb-8704x tablet by my hand and it only boots into the recovery menu like u hold volume down and power.
1. I don't know what happened to it before, I got it like it is.
2. If u plug in powe supply the red led blinks and u can only power it on by holding power for around 10 seconds, then the lenovo logo -> then recovery menu
3. Also If I hold down volume down and power it on it boots into the test app, to test if all stuff works.
4. In the test app I tested the volume buttons and recognized the up button had no response, so I took it apart and measured it. And if I press volume up then I get a good reading (peep). So the volume keys both are good.
5. The I tested flash a stock rom to test if that fixed the problem. I used TB_8704X_S001025_190606_ROW from the lenovo rescue program, but if I try to flash it inside the recovery menu over SD Card it only said wrong footer, error 21.
6. So i decided to use the qfil and the base stock rom TB-8704X_S000026_170707_ROW_QFIL. And after I always get sahara error messages if I use it only windows 10, I booted up an old win xp PC installed version .460 and the Qualcomm drivers, then hold down volume up plugged in USB, clicked the right Qualcomm com port and all went well first try no errors.
7. Then I unplugged the tablet, hold down power until it reboots but still nothing only recovery menu.
That's why I decided to post here, in hope someone can help, has new ideas or something else.
I hope all is good understandable.
//edit I uploaded to images, that's what I get if I boot f.e. the latest stock rom (named as factory_update.zip) from lenovo on an fat32 formatted sd card (exfat will give error and is not been able to mount)
Update:
I also managed to update to the latest rom from lenovo. Then it boots again in recovery mode but a different error.
For testing I've put the sd card with the same lasted update file inside. Then it starts the update process again. It starts install, tries to erase and then error and it boots again and then I'm in a boot loop until I remove the SD (because the image is named factory_update.zip so it's auto starts update process)
Pictures in attachment
Im pretty sure after all my testing, it's a hardware failure so, this thread can be closed.