Related
Hey guys, I posted this over at Rootz but it's not getting any action. I really appreciate the help...
Hey Gents,
I couldn't wait any longer so I installed Alpha2 on my Touchpad and was happy as a pig in sh*t after spending about two days on it. Then I got curious about the Nightly builds and came across a problem that is killing me. I can not boot into Recovery mode. I've tried everything, I've searched up and down on the forums but it seems like everyone can at least get into recovery. Moboot has "boot webOS Recovery" option but no "boot clockworkmod". I've tried through ROM Manager, I've tried through ROM Toolbox, etc. Nothing. I uninstalled the Alpha2 through ACMEUninstaller and then reinstalled the latest Nighty Build through ACMEIntstaller2 with the other files needed for Android. Nothing. I tried booting into recovery on my S2 Skyrocket, no problem. I'm pulling my hair out here.
Any ideas?
here's exactly what I did:
1- installed novacom driver
2- copied ACMEInstaller2 over to the Palm, Inc folder in Program Files
3- plugged in Touchpad via USB and copied the gapps, Cyanogenmod9, recovery_update_tenderloin and moboot zipped files to my folder I created "cminstall"
4- unplugged TP, put it in USB recovery mode, reattached it via USB and ran the command prompt
5- Ran perfectly smooth, played with Android for a few days.
- ROM Manager is installed, Google apps work perfectly, dual boot is alive and well, etc.
everything works great but RECOVERY. When I reboot and hit recovery or when I go straight into ROM Manager and hit recovery, I end up at the boot screen.
another weird thing... when I checked out my files in "cminstall" via Astro, the recovery one was still there as a zipped file. All the other files were gone. Not sure if this means anything but I figure the more info the better.
I am not totally sure on this so may get blasted, but check the filename of the zip in the cminstall folder. I had this impression that the zip files needed to start 'update-' for AcmeInstaller to handle them. I think some of the cwm zips have other filenames, but it doesn't hurt to rename and try AcmeInstaller2 again.
You probably need to clear up some room in the boot partition. I had the same issue with initial install of cm7. Recovery wouldn't flash properly because there was not enough room. Make enough room in your /boot and flash through ACMEinstaller.
Sent from my PG06100 using Tapatalk 2
Ok, so you mean on the Touchpad I need to get rid of a bunch of data? Like where I store music and movies and all that? I have a HUGE amount of free space on there. Easily 60% of the 32GB is free.
on a side note, would I be able to flash continuously through ACMEInstaller2 rather than CWM Recovery? Like say an official beta comes out, could I just run the command lines without all the other zip folders right over the version installed??
copene said:
Ok, so you mean on the Touchpad I need to get rid of a bunch of data? Like where I store music and movies and all that? I have a HUGE amount of free space on there. Easily 60% of the 32GB is free.
Click to expand...
Click to collapse
in your /boot folder you may have too much stuff... do some reading and delete everything that shouldnt be there
copene said:
on a side note, would I be able to flash continuously through ACMEInstaller2 rather than CWM Recovery? Like say an official beta comes out, could I just run the command lines without all the other zip folders right over the version installed??
Click to expand...
Click to collapse
you could but why would you want to
yup, that was the problem! the CWM file I DL'd from precentral didn't start with "update". I grabbed the file directly from Rootz and it installed perfectly. Thank you so much, everything is working as it should now.
Thanks a lot guys.
In your /boot, if you wanna just have the stuff for WebOS and Alpha2, you should have the following in your /boot:
Folders:
bin/
dev/
etc/
lib/
lost+found/
proc/
realroot/
sbin/
sys/
usr/
Files:
boot-genesis.tar.gz
boot-images.tar.gz
boot.bin
config-2.6.35-palm-tenderloin
genesis-update.xml
image-update.xml
moboot.default
moboot.splash.CyanogenMod.tga
moboot.splash.webOS.tga
moboot.timeout <== You might not have this.
System.map-2.6.35-palm-tenderloin
uImage
uImage-2.6.35-palm-tenderloin
uImage.ClockworkMod <== You apparently don't have this
uImage.CyanogenMod
uImage.moboot
uImage.webOS
updatefs-info
If you have other files in there aside from those listed, feel free to delete the extras. Your /boot partition is only 30 MB, so you need to have some room left in there. The uImage.ClockworkMod is about 5 megs, and if you have nothing BUT WebOS and CM9 installed (I have the last official nightly), you should have 22 megs or so used.
Hope that helps, mate.
I am a complete HD+/Android 4.x noob, but I am not new to fiddling with various "unofficial" firmware projects (CHDK, rockbox...). So in the spirit of hacking it if it's hackable I prepared a 4gb sd card (Kingston, cl 4) with the "new" method of partitioning, formatting and copying the 5 CWM Recovery files plus 2 zips for Universal Root and Enabling unknown sources. (BTW, the NookHDplus-bootable-CWM-6028-for-stock-4GB-rev4-(05.15.13).zip which I also downloaded and inspected sports a partition type of FAT32 (0x0B) and not FAT32 LBA (0x0C), as seems to be required.)
Anyway, this sd booted repeatedly (4 or 5 times) without any trouble on my brandnew HD+. However, I decided not yet to go ahead with installing anything as the thing was still at stock firmware 2.0.4.
I duly let it update itself... and what an efficient process that was: from 2.0.4 to 2.0.6 to 2.1.0 to 2.1.1 -- but that's another story.
(An aside for those folks whose HD+ doesn't want to boot from sd: after this update marathon the very same sd card and the very same HD+, with only the firmware updated to 2.1.1, wouldn't boot anymore from sd. I *knew* the card was bootable so I kept going and after many dozens of attempts it finally did boot. Weird.)
Finally booted into CWM, I duly installed the two zips for root and unknown sources, removed the sd card and rebooted. The bright "nook" screen came up, quickly followed by another screen for a thing called cyanoboot. The HD+ continued after a few secs and booted into the rooted stock. If an sd card is installed, it will sometimes boot from that and sometimes boot into stock.
I now wonder whether installing this 2nd loader (ie cyanoboot) is standard and to be expected when rooting the HD+? I did google for that but I found no clear answer.
Here's a 2nd question. I can't access the HD+ via MTP, one reason why I have to root it anyway. However, I've seen that there are CWM Recovery versions out there which seem to be able to mount some or all of the internal partitions so that they can be accessed via USB ("Mounts and storages" >> "Mount USB storage"). Sadly this option doesn't exist within the 6.0.2.8 I've installed.
Anyone got an idea where or how I can find one of those versions? If not, for the various Nook Touches, there's a addon called noogie that mounts the internal partitions and makes them all accessible via USB. Does something similar exist for the Nook HDs?
Thanks for any help or hints.
Wow, long post, but interesting data. But I will attempt to answer.
Yes, as of the Universal Root rev3, the second bootloader is used to be able to root easily. That second bootloader allows removal of the original file protection scheme that B&N had in the original boot.img. My previous versions did not use that and were more complex. See my HD/HD+ Tips thread linked in my signature for a description of that file protection scheme.
As for MTP in stock, it does work. You need to be sure you have Android Debugging disabled in settings.
You can get verygreen's CWM v6.0.3.2 in the link in my item 5 in my CWM thread where you got the root. He also has TWRP there. But I don't know if they have those features you want. Some of the partition mounts were purposely removed because users were formatting critical partitions and bricking their devices.
And I know of nothing like noogie for this device.
Interesting what you found about the partition types in my burnable image. I just had a devil of a time making a new bootable SD for TWRP recently. That may be why.
And the aside about booting after upgrading is interesting. Booting is controlled by the chip firmware and cannot be changed with flashing ROMs. So it baffles me.
Sent from my Nook HD+ running CM10.1 on emmc.
Thanks for your post.
leapinlar said:
Yes, as of the Universal Root rev3, the second bootloader is used to be able to root easily. That second bootloader allows removal of the original file protection scheme that B&N had in the original boot.img. My previous versions did not use that and were more complex. See my HD/HD+ Tips thread linked in my signature for a description of that file protection scheme.
Click to expand...
Click to collapse
So that means that Cyanoboot (or something CB loads) removes file protection on the fly? I was assuming something along these lines. Maybe a hint in the relevant thread that this is to be expected would be a good idea. I for one was somewhat surprised when that CB screen popped up... but with the sd card removed
Anyway I've since installed CWM on the HD+ itself.
leapinlar said:
As for MTP in stock, it does work.
Click to expand...
Click to collapse
Oh, I am sure it does. But MTP isn't supported by my desktop machine and I do not plan to change that. It would be great if I just could dd the various HD+ partitions onto my desktop machine (and back, if needed). That's why I asked for some sort of noogie for ND+.
leapinlar said:
Interesting what you found about the partition types in my burnable image.
Click to expand...
Click to collapse
Well, I just checked the first 512 bytes of the image file (ie the MBR), but never burned it. And there, the partition type seems to be 0x0B.
leapinlar said:
And the aside about booting after upgrading is interesting. Booting is controlled by the chip firmware and cannot be changed with flashing ROMs.
Click to expand...
Click to collapse
Well, that's what one would think. Perhaps the whole pre-booting process is so brittle that even small external differences (say in temperature or some such thing) can influence the booting behaviour. All I know is that the sd card booted okay and always on the first attempt with v2.0.4 whenever I tried it and that it took me 50+ attempts with v2.1.1. But I am not going back to v2.0.4 to investigate...
TooMuchSloeGin said:
Thanks for your post.
So that means that Cyanoboot (or something CB loads) removes file protection on the fly? I was assuming something along these lines. Maybe a hint in the relevant thread that this is to be expected would be a good idea. I for one was somewhat surprised when that CB screen popped up... but with the sd card removed
Anyway I've since installed CWM on the HD+ itself.
Oh, I am sure it does. But MTP isn't supported by my desktop machine and I do not plan to change that. It would be great if I just could dd the various HD+ partitions onto my desktop machine (and back, if needed). That's why I asked for some sort of noogie for ND+.
Click to expand...
Click to collapse
Yes, the second bootloader (CB) allows removal of the file protection. It gets removed permanently. I will add that warning to expect cyanoboot to my Universal Root item. Thanks.
And you can easily back up your partitions right on the device. Look at my HD/HD+ Tips thread linked in my signature. I have an item that describes how there. You can use Terminal Emulator to do it.
Sent from my Nook HD+ running CM10.1 on emmc.
Terminal Emulator
leapinlar said:
You can use Terminal Emulator to do it.
Click to expand...
Click to collapse
Speaking of which... is there anything out there with some usable line editing capabilities? I'm currently using jackpal's Android-Terminal-Emulator (sorry, can't yet post URLs) but that's not very good at line editing.
I'd also like to replace sh with zsh or some such. Anyone tried that?
TooMuchSloeGin said:
Speaking of which... is there anything out there with some usable line editing capabilities? I'm currently using jackpal's Android-Terminal-Emulator (sorry, can't yet post URLs) but that's not very good at line editing.
I'd also like to replace sh with zsh or some such. Anyone tried that?
Click to expand...
Click to collapse
Not sure wat you mean by line editing. You mean text file editing? Or editing a line of text you typed in the TE?
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
Not sure wat you mean by line editing. You mean text file editing? Or editing a line of text you typed in the TE?
Click to expand...
Click to collapse
The latter... recalling, editing etc. actual command lines.
I installed the jackpal TE on my Nook Simple Touch (runs Android 2.1) and plan to use it on the HD+ as well, if I find no better option. So far I've not really looked into whether and how I can customise its keyboard handling, so any hints are very welcome.
I am used to zsh on my desktops but it seems that's not a viable option here. The HD+ being my first "real" Android machine, I've got no clear picture what's available. I will probably put CM on the it but I have no idea what is included with it.
EDIT: I've just installed CM10.1.3 (nice...) and see that the jackpal TE is included. What's more, on the HD+ it does support some sort of command line editing capability (it doesn't seem to have these when installed on a Nook Simple Touch -- or else I am too daft to find or enable them there).
Anyway, that seems to be sorted now, though a more powerful shell would be a nice thing to have.
leapinlar said:
And the aside about booting after upgrading is interesting. Booting is controlled by the chip firmware and cannot be changed with flashing ROMs. So it baffles me.
Click to expand...
Click to collapse
Actually there's a thing that the kernel could influence. If the reboot is "soft", then the boot tables survive in the SoC and are set up in such a way that the boot fro emmc is attempted. That's the default for crashes, for example, so it boots of emmc instead of sdcard (leading to 99% hang of old before we changed the partitioning scheme).
Normal reboot is hacked to do a cold restart and is just powering the device on from the off state naturally. And that defaults to boot from sdcard first and if that fails, goes on to do emmc boot.
I have not seen any changes to default to non-cold boot on normal reboots, but I also saw frequent crashes on shutdown (that still result in reboot of course so user is none the wiser, except the thing boots off emmc even with sdcard still in. Presense of the /proc/last_kmsg file is the giveaway, though).
---------- Post added at 02:27 PM ---------- Previous post was at 02:25 PM ----------
leapinlar said:
Yes, the second bootloader (CB) allows removal of the file protection. It gets removed permanently. I will add that warning to expect cyanoboot to my Universal Root item. Thanks.
Click to expand...
Click to collapse
Actually it's not a permanent removal in a sense that the next firmware update will write an unpatched kernel boot image back and the file protection would thus be restored, so you better be able to catch it that instant to reflash the patched boot.img or you'dd get through the 8 reboots and the factory reset that follows.
verygreen said:
Actually it's not a permanent removal in a sense that the next firmware update will write an unpatched kernel boot image back and the file protection would thus be restored, so you better be able to catch it that instant to reflash the patched boot.img or you'dd get through the 8 reboots and the factory reset that follows.
Click to expand...
Click to collapse
Not exactly. My testing has shown that the patch updates from B&N fail with your boot.img installed. It has an assert statement that tries to verify the boot.img before it patches it. Of course that fails and it aborts the update. The only way your boot.img gets replaced is with a full ROM flash, which B&N does not do with automatic updates. Users usually have to do that themselves. That is why I call it permanent.
Edit: Of course an 8 failed boot would replace it too, but there is no reason for that to happen with your awesome boot.img installed.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
Not exactly. My testing has shown that the patch updates from B&N fail with your boot.img installed. It has an assert statement that tries to verify the boot.img before it patches it. Of course that fails and it aborts the update. The only way your boot.img gets replaced is with a full ROM flash, which B&N does not do with automatic updates. Users usually have to do that themselves. That is why I call it permanent.
Click to expand...
Click to collapse
Oh, interesting. I did not know there was a partial update available, only the full rom zip that is also available at the support page.
In any case it would sound strange if they only tried to binary patch boot.img instead of writign a full copy of the new one, it's a gzipped image either way so minute changes inside might mean that the entire thing immensely changes after compression.
verygreen said:
Oh, interesting. I did not know there was a partial update available, only the full rom zip that is also available at the support page.
In any case it would sound strange if they only tried to binary patch boot.img instead of writign a full copy of the new one, it's a gzipped image either way so minute changes inside might mean that the entire thing immensely changes after compression.
Click to expand...
Click to collapse
Yeah, partial updates is how B&N does OTA automatic updates. That keeps the downloads small. But they do use binary patches for everything, including boot.img.
Sent from my Galaxy Tab 2 using XDA Premium
I am stuck in boot recycling to cwm recovery v6.0.3.6
problem started when I was running cm10.1 and backuped to internal memory sdcard with cwm
after that the bootloader cycling started
I have restored the CM10.1 using CWM but the bootloader always shows on restart
I restored the original BN stock that was backed up using SD card CWM before flashing CM 10.1, but still in bootloader recycling
all backups to SD or internal had no errors
all restores had no errors
I did not attempt usb connection to windows before CM install
While stuck in cwm recycling attempting to mount USB gives driver install error 1st time; then replugging usb gives no message and no recognition.
I want to boot to any restored OS
I want to have USB mount without drivers error
mmth said:
I am stuck in boot recycling to cwm recovery v6.0.3.6
problem started when I was running cm10.1 and backuped to internal memory sdcard with cwm
after that the bootloader cycling started
I have restored the CM10.1 using CWM but the bootloader always shows on restart
I restored the original BN stock that was backed up using SD card CWM before flashing CM 10.1, but still in bootloader recycling
all backups to SD or internal had no errors
all restores had no errors
I did not attempt usb connection to windows before CM install
While stuck in cwm recycling attempting to mount USB gives driver install error 1st time; then replugging usb gives no message and no recognition.
I want to boot to any restored OS
I want to have USB mount without drivers error
Click to expand...
Click to collapse
I'm not sure what you mean by bootloader recycling. You mean continuously booting only to CWM, or the boot logo (that is the bootloader) just sits there and then it reboots again? The bootloader is supposed to show on every boot, that is how it loads the next step.
Did you by any chance format /bootdata with CWM?
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
I'm not sure what you mean by bootloader recycling. You mean continuously booting only to CWM, or the boot logo (that is the bootloader) just sits there and then it reboots again? The bootloader is supposed to show on every boot, that is how it loads the next step.
Did you by any chance format /bootdata with CWM?
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
The complete CWM is available after the booting; not just the splash screen. That is how I do all the restores and saves (those not from SD)
I do not recall clicking a format button.
I am willing to go back to start with BN original. I downloaded nookhdplus_2_1_1_update.npk but do not know how to load it in this situation.
mmth said:
The complete CWM is available after the booting; not just the splash screen. That is how I do all the restores and saves (those not from SD)
I do not recall clicking a format button.
Click to expand...
Click to collapse
Sounds like your bootdata partition got messed up somehow. If it is messed it will only boot to recovery. I can make a custom zip for you to flash to restore it if you send me your serial number via PM.
Sent from my Nook HD+ running CM10.1 on emmc.
---------- Post added at 08:28 AM ---------- Previous post was at 08:16 AM ----------
mmth said:
I am willing to go back to start with BN original. I downloaded nookhdplus_2_1_1_update.npk but do not know how to load it in this situation.
Click to expand...
Click to collapse
My guess is that won't help at this stage, but just change the npk to zip and flash it.
Edit: that also puts stock recovery back, so there is a chance it can repair itself. In any case you must use your CWM SD to flash after that.
Sent from my Nook HD+ running CM10.1 on emmc.
[/COLOR]My guess is that won't help at this stage, but just change the npk to zip and flash it.
Edit: that also puts stock recovery back, so there is a chance it can repair itself. In any case you must use your CWM SD to flash after that.
I renamed npk to zip and attempted flash using cwm (cwm and zip on SD card; booted to sd card).
error E:Can't open /sdcard/nookhdplus_2_1_1_update.zip
(bad)
Installation aborted.
do I need to wipe data/factory reset first?
mmth said:
[/COLOR]My guess is that won't help at this stage, but just change the npk to zip and flash it.
Edit: that also puts stock recovery back, so there is a chance it can repair itself. In any case you must use your CWM SD to flash after that.
I renamed npk to zip and attempted flash using cwm (cwm and zip on SD card; booted to sd card).
error E:Can't open /sdcard/nookhdplus_2_1_1_update.zip
(bad)
Installation aborted.
do I need to wipe data/factory reset first?
Click to expand...
Click to collapse
No you don't need to wipe first, but you do need to wipe after flashing. That error usually means a bad download. Try going to my HD/HD+ CWM thread linked in my signature and try downloading and flashing my plain stock 2.1.0 zip in item 6.
In the meantime I will try to make you a zip.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
No you don't need to wipe first, but you do need to wipe after flashing. That error usually means a bad download. Try going to my HD/HD+ CWM thread linked in my signature and try downloading and flashing my plain stock 2.1.0 zip in item 6.
In the meantime I will try to make you a zip.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
I was able to flash to nook 2.1.0 and a few updates did appear; but not the 2.1.1 update. Still no USB connectivity on the Windows machine. Makes USB sound but does not install driver or appear in pane of storage devices. I installed several apps from Google Play.
How can I tell if it set to allow install from unknown sources? Can I install the USB host changer on the nook android?
mmth said:
I was able to flash to nook 2.1.0 and a few updates did appear; but not the 2.1.1 update. Still no USB connectivity on the Windows machine. Makes USB sound but does not install driver or appear in pane of storage devices. I installed several apps from Google Play.
How can I tell if it set to allow install from unknown sources? Can I install the USB host changer on the nook android?
Click to expand...
Click to collapse
Stock does not support host changer.
I just wanted you to flash 2.1.0 to see if you could get it to boot. You can flash 2.1.1 now. And you do NOT want to flash that zip I sent you.
What do you mean, USB connectivity? You mean MTP so you can transfer files or do you mean ADB? If you mean MTP, be sure to have android degugging off in settings.
You can tell if unknown sources is enabled if you can side load apps. Try to open an apk file and see if it installs.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
Stock does not support host changer.
I just wanted you to flash 2.1.0 to see if you could get it to boot. You can flash 2.1.1 now. And you do NOT want to flash that zip I sent you.
What do you mean, USB connectivity? You mean MTP so you can transfer files or do you mean ADB? If you mean MTP, be sure to have android degugging off in settings.
You can tell if unknown sources is enabled if you can side load apps. Try to open an apk file and see if it installs.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
flashed 2.1.1 rooted. confirmed in device information.
now nook boots to bootloader splash screen but not to cwm application. Goes to Nook loading screen after splash.
wifi location services does not seem to work, as it did in cm10.1; is this true for the nook android?
weather widget does not seem to install correctly; I only see small unreadable icon on home page.
does rooted nook support host changer?
I still cannot get nook to mount as storage device on windows. (meaning of USB connectivity) What should I expect?
How do I get the apk to nook storage without USB making nook a storage device on windows?
Looking forward to trying CM10.1 again. Should I wait for your custom load or try the flash using the documented way (which seems not to be of recent vintage).
However, I am afraid to backup this version to internal memory or SD card because of my previous disaster of CWM cycling on boot. Where can I find reliable method of doing backup (get into CWM from nook android).
Hi,
I have an HTC One m7 on T-Mobile, rooted and running Android Revolution 82.0.
I messed up, now I need help to dig myself out of this hole. I do not understand some of this, this could be partly due to my stupidity.
I backed up my system and boot in twrp before i had done any of this.
Last night I wanted to update TWRP. I downloaded "TWRP manager" through the play store, I opened the app and went down to "install twrp" - i installed TWRP 2.8.1.0 through the app, it said flashing successful. Everything was fine. I rebooted my phone into recovery to verify that it had worked. The correct twrp version was displayed at the top. I rebooted my phone into system. After the boot sequence it loaded into the first time run set up manager (by this i mean the thing that comes on when you turn on your phone for the very first time). This shocked me. I went through the procedure to "set up" my phone. All my apps were gone, all settings, everything. It looked as if it were brand new. Even the pre-loaded apps for android revolution were gone. I rebooted back into twrp recovery, went to the file manager and went to the main directory "/". I looked for the folder "/storage" but it wasnt there. I went to go restore my phone to the backups i had made before i tried updating twrp to see if that would help. Nothing changed. after this, I reinstalled the rom through TWRP without wiping anything. All my apps were still gone, all settings were gone, yet all my photos were still there. All of my files for the apps are all there, they are all in the internal storage, all the folders are still in /data , i do not understand what happened. I am also concerned that when I am in recovery and i am in the file manager i cannot see "/storage", as if it is hidden from the recovery file manager. Also, when i select "backup" and it gives me options to backup system, data, etc., under data it only shows 756 mb of data, i have at least 2000 mb, I am wondering if my phone is accessing the storage somewhere else? Please help me find out how to fix my errors. I wish to go back to where i was, or at least figure out what happened to increase my knowledge and NEVER do something like this again.
for some reason which i do not know, my sdcard files are saved in different places? i assume this is just how it's supposed to be. these loacations are : "/storage/emulated/0" - "/storage/emulated/legacy" - "/storage/sdcard0" - "/sdcard" (all of these folders have all of the same files etc.)
Thank you,
Evan
ImMrBS said:
Hi,
I have an HTC One m7 on T-Mobile, rooted and running Android Revolution 82.0.
I messed up, now I need help to dig myself out of this hole. I do not understand some of this, this could be partly due to my stupidity.
I backed up my system and boot in twrp before i had done any of this.
Last night I wanted to update TWRP. I downloaded "TWRP manager" through the play store, I opened the app and went down to "install twrp" - i installed TWRP 2.8.1.0 through the app, it said flashing successful. Everything was fine. I rebooted my phone into recovery to verify that it had worked. The correct twrp version was displayed at the top. I rebooted my phone into system. After the boot sequence it loaded into the first time run set up manager (by this i mean the thing that comes on when you turn on your phone for the very first time). This shocked me. I went through the procedure to "set up" my phone. All my apps were gone, all settings, everything. It looked as if it were brand new. Even the pre-loaded apps for android revolution were gone. I rebooted back into twrp recovery, went to the file manager and went to the main directory "/". I looked for the folder "/storage" but it wasnt there. I went to go restore my phone to the backups i had made before i tried updating twrp to see if that would help. Nothing changed. after this, I reinstalled the rom through TWRP without wiping anything. All my apps were still gone, all settings were gone, yet all my photos were still there. All of my files for the apps are all there, they are all in the internal storage, all the folders are still in /data , i do not understand what happened. I am also concerned that when I am in recovery and i am in the file manager i cannot see "/storage", as if it is hidden from the recovery file manager. Also, when i select "backup" and it gives me options to backup system, data, etc., under data it only shows 756 mb of data, i have at least 2000 mb, I am wondering if my phone is accessing the storage somewhere else? Please help me find out how to fix my errors. I wish to go back to where i was, or at least figure out what happened to increase my knowledge and NEVER do something like this again.
for some reason which i do not know, my sdcard files are saved in different places? i assume this is just how it's supposed to be. these loacations are : "/storage/emulated/0" - "/storage/emulated/legacy" - "/storage/sdcard0" - "/sdcard" (all of these folders have all of the same files etc.)
Thank you,
Evan
Click to expand...
Click to collapse
The answer to your mysterious factory reset lies here in this link. For further information see the link in this link
http://forum.xda-developers.com/showpost.php?p=55741117&postcount=83118
When in the TWRP file manger your /storage is a Folder called /sdcard.
And the multiple storage locations. Not all of these are actually physical locations you only have one memory chip with one set of files, the other locations are just emulated/virtual copies of your main storage
If you found my post helpful, no need to say thanks. There's a button for that
Danny201281 said:
The answer to your mysterious factory reset lies here in this link. For further information see the link in this link
http://forum.xda-developers.com/showpost.php?p=55741117&postcount=83118
When in the TWRP file manger your /storage is a Folder called /sdcard.
And the multiple storage locations. Not all of these are actually physical locations you only have one memory chip with one set of files, the other locations are just emulated/virtual copies of your main storage
If you found my post helpful, no need to say thanks. There's a button for that
Click to expand...
Click to collapse
So what I've gathered from this, is that all my apps are gone forever because I forgot to backup the data. And that is because "Then along comes the recent TWRP builds (2.7.1.2+) that read the bcb on boot. You flash it and boot into recovery, TWRP starts, reads the wipe_data command out of the bcb and proceeds to wipe the /data partition."? Also should I run the reset script in this post? http://forum.xda-developers.com/showpost.php?p=54370858&postcount=492
since I have a non-sprint htc one I'm not sure if this would do me harm or not. The reason I am asking all these questions is because I want to make sure I don't do something stupid again.
ImMrBS said:
So what I've gathered from this, is that all my apps are gone forever because I forgot to backup the data. And that is because "Then along comes the recent TWRP builds (2.7.1.2+) that read the bcb on boot. You flash it and boot into recovery, TWRP starts, reads the wipe_data command out of the bcb and proceeds to wipe the /data partition."? Also should I run the reset script in this post? http://forum.xda-developers.com/showpost.php?p=54370858&postcount=492
since I have a non-sprint htc one I'm not sure if this would do me harm or not. The reason I am asking all these questions is because I want to make sure I don't do something stupid again.
Click to expand...
Click to collapse
Yep that's about right. Running the script shouldn't do any harm but since you already experienced the Factory reset. The command should no longer be in your bcb anyway. As far as I'm aware this only happens once after a new flash and shouldn't repeat every time you use recovery.
But using the zip to clear your bcb is not a bad idea for piece of mind.
First of all, sorry for all my possible grammar and usage mistakes, I'm not a native speaker and my English is still rather mediocre. I just couldn't find the solution to my problem and come here though Google.
My problem is that after almost two years of active using my nook HD+ stopped to boot and now behaves pretty much like a brick. I actively used CM10 on emmc all that time without any other upgrades and all went more or less well, until after some installation from Google play all of a sudden the device stopped booting altogether. Unfortunately, I didn’t do any archives.
After some googling I found the thread from the forum on how to recover through downgrading to the stock using the info from the thread: http://forum.xda-developers.com/showthread.php?t=2062613
I prepared the CWM SD (with file :NookHDplus-bootable-CWM-6028-for-stock-BOOTFILES-r4-(05.15.13)) and tried to install plain unrooted factory 2.1.0 (or 2.2.0). Every time just in the middle of installation I got the following messages:
CWM-based Recovery v 6.0.2.8 for HD+ (Stock)
…Installing : /sdcard/NookHDplus –factory-2.2.0-plain-stock.zip…
Opening update package…
Installing update…
Random offset: 0x45
Failed to retouch ‘/system/lib/libemoji.so’
E:Errror in /sdcard/NookHDplus-factory-2.2.0-plain-stock.zip
(Status 7)
Installation aborted.
In another case with NookHDplus-factory-2.1.0-plain-stock.zip I got “Random offset: 0x3da” All the rest of the message was the same as above.
I also tried to install a CWM (v6036) for internal memory (emmc) and Restore stock recovery to emmc (HD/HD+) also with no avail. (I guess so because although I didn’t get any error messages when installing stock recovery from the thread I mentioned above, I still can’t find any traces of stock recovery (v. 6036) on my nook hd+)
And I tried to interrupt the process of booting eight times in a row to facilitate the factory recovery as I read somewhere, also without any success.
I’m not an advanced user, easily could miss somehting important and any help or assistance would be much appreciated.
Alex.
Go to that same thread you referenced and in item 5 it points to a stock recovery you can flash. Flash that and then the 8 failed boot procedure should work, taking you back to stock so you can start over.
It is also possible that your internal memory is bricked (read only) and will accept no changes.
Sent from my BN NookHD+ using XDA Premium HD app
Leapinlar, thank you very much for your advice.
I flashed the stock recovery from item 5 as you mentioned and performed 8 failed reboots. Every time, I turned off my nook emmediatley after I saw the inscription NOOK but before the wheal was shown and then made the 9th normal reboot, and still I got the same wheal as before.
When I flashed the stock recovery, I got the following message after the installation:
CWH-based recovery v.6.0.2.8. fro HD+(Stock)
Installing /sdcard/NookHDplus-emms-stock-recovery-rev0-(05.16.13).zip
Finding update package
Opening update package
Installing update
Installing
Done!
Install from sdcard complete.
I guess the recovery was successfully installed, but for some reason it didn’t work with my failed reboots. Not sure where I made a mistake. Any idea?
aaenaee said:
Leapinlar, thank you very much for your advice.
I flashed the stock recovery from item 5 as you mentioned and performed 8 failed reboots. Every time, I turned off my nook emmediatley after I saw the inscription NOOK but before the wheal was shown and then made the 9th normal reboot, and still I got the same wheal as before.
When I flashed the stock recovery, I got the following message after the installation:
CWH-based recovery v.6.0.2.8. fro HD+(Stock)
Installing /sdcard/NookHDplus-emms-stock-recovery-rev0-(05.16.13).zip
Finding update package
Opening update package
Installing update
Installing
Done!
Install from sdcard complete.
I guess the recovery was successfully installed, but for some reason it didn’t work with my failed reboots. Not sure where I made a mistake. Any idea?
Click to expand...
Click to collapse
You be not doing the 8 failed right. Do it more that 8 times. It should either boot to stock recovery or CWM, depending on which you have in. And it is ok to let it get as far as the cyanoboot logo each time. If you truly have turned the internal memory to read only (bricked), the counter keeping track of the fails will not write and then it won't work. And when the read only happens you are told the write is successful but it really does not take.
Another way to test if the stock recovery took is to try to boot to recovery manually. From powered off, turn it on and hold the power and n key together for a few seconds. Release the power key first before it turns itself back off, followed by releasing the n key. It should boot to recovery, either stock or CWM. If CWM I am afraid you have it bricked.
Sent from my BN NookHD+ using XDA Premium HD app
Leapinlar, thank you once again.
I tried the second option you suggested (boot the recovery manually), and I still get Nook booted by EMC CWM-based recovery v.6.0.3.2 as before. So, my Nook seems to be bricked and nothing can be done to make it working using only software operations, right? ((
Sorry, for the question that may sound silly, but I’m curious if it is possible to install CyanogenMod builds on SD card only and run Nook without internal memory altogether (only on SD); or this is technically impossible and some part of internal memory is necessary anyway to make it working?
aaenaee said:
Leapinlar, thank you once again.
I tried the second option you suggested (boot the recovery manually), and I still get Nook booted by EMC CWM-based recovery v.6.0.3.2 as before. So, my Nook seems to be bricked and nothing can be done to make it working using only software operations, right? ((
Sorry, for the question that may sound silly, but I’m curious if it is possible to install CyanogenMod builds on SD card only and run Nook without internal memory altogether (only on SD); or this is technically impossible and some part of internal memory is necessary anyway to make it working?
Click to expand...
Click to collapse
Yes, verygreen made some older versions of CM that were designed to run on SD with bricked emmc. Search for the term noemmc in the forum.
Sent from my BN NookHD+ using XDA Premium HD app
Some update for my troublesome situation.
I found and downloaded all the files and followed the procedure from the thread
http://forum.xda-developers.com/showthread.php?t=2221289&page=7.
Namely I successfully did everything until the words
“adb push it to /sdcard/ and then install.
Also push and install whatever else you need”
Does “adb push” here means that I necessarily need a Linux run comp, or there’s a workaround for Windows?
Anyways, the size of cm-10.1-20130819-UNOFFICIAL-ovation-noemmc.zip is larger than the size of the disk after burning, and I can’t copy it there. Also, I cant’ apply the gimmick: format another sdcard with SDFormatter, set the first partition as "active" with Mini-Tool Partition Wizard and copy bootfiles from my first sdcard (burned with Win32disk imager) thereafter. Nook doesn’t mount such a sdcard. I tried.
Any thoughts, if there is anything else that can be done on Windows?
aaenaee said:
Some update for my troublesome situation.
I found and downloaded all the files and followed the procedure from the thread
http://forum.xda-developers.com/showthread.php?t=2221289&page=7.
Namely I successfully did everything until the words
“adb push it to /sdcard/ and then install.
Also push and install whatever else you need”
Does “adb push” here means that I necessarily need a Linux run comp, or there’s a workaround for Windows?
Anyways, the size of cm-10.1-20130819-UNOFFICIAL-ovation-noemmc.zip is larger than the size of the disk after burning, and I can’t copy it there. Also, I cant’ apply the gimmick: format another sdcard with SDFormatter, set the first partition as "active" with Mini-Tool Partition Wizard and copy bootfiles from my first sdcard (burned with Win32disk imager) thereafter. Nook doesn’t mount such a sdcard. I tried.
Any thoughts, if there is anything else that can be done on Windows?
Click to expand...
Click to collapse
I don't see the thread and procedure you are talking about. That is an HD thread. But ADB can be set up on Windows. Just look at my HD/HD+ tips thread linked in my signature. Verygreen unfortunately uses Linux and is not much help for Windows users. And that second procedure with setting active, etc is not intended for SD installs.
Sent from my BN NookHD+ using XDA Premium HD app
You could try a fastboot bootable sdcard recovery to fix your partitions.
In some ways I prefer it over a traditional recovery to flash things like, say recovery.img
See my post #16
http://forum.xda-developers.com/nook-hd/help/nook-hd-bricked-flashing-4-4-2-help-t2811998/page2
It's not necessary to have a Linux host (Google fastboot windows), but it will require some adb setup.
Thank you guys for your kind replies. It’ll take probably a while to learn adb from scratch and implement the solutions you suggested and I’m not sure about the duration of this “while”. The OP of the thread, Jon Lee referenced, promised to post back on his progress but never actually did. So, I’m not sure what to think…
Anyways, while searching on how to bypass all the adb related stuff I fond a message of a guy who claimed he was able to do without adb using Linux run Kaspersky Rescue Disk 10.
It actually takes a few minutes to record such a disk but I still have no idea how to find ext4 formatted part of the sdcard and what to do next. Ext4 remains invisible in Dolphin file manager for some obscure reason. I tried to get in touch with the guy but he was not available at the moment.
So, if anyone knows how to use KRD 10 or something like that please write a little bit here about the details of the procedure.
Yes, I know, I should have backed up...but did not. So, this TP, I cannot go into usb mode or recovery mode. For some reason, I get a weird 4 block pattern. Before I messed up, I was able to use TWRP 2.8.3 to load different gapps and roms in the ttinstall file by mounting. Well, I decided Lollipop was not quite what I wanted and wanted to go back to KitKat. Anyway, in my zeal of trying to fix what may be causing the recovery mode issue, I wiped everything and formatted everything...including the ttinstall file. I can still boot to twrp 2.8.3, but honestly, the sequence of invents I have tried to create a new folder called ttinstall and place in there rom and gapps, it will not load. In fact, I'm not sure where the twrp file is located. So, I would appreciate it if someone has detailed instructions beginning with opening twrp 2.8.3. What sd card to use and folder to create where, and so forth. I can mount the TP and load files via the pc, but I don't quite know where they actually go on the tablet. The device shows up as 1gb on the pc and this is a 32gb TP so I know I messed it up. I was spoiled by the TPToolbox when I was able to use the usb recovery mode and make all changes there.
Any help would be appreciated. I did do a search, but I have not found clear instructions for me. I even saw a youtube, but again, it was more confusing. Thanks.
golfnut22 said:
Yes, I know, I should have backed up...but did not. So, this TP, I cannot go into usb mode or recovery mode. For some reason, I get a weird 4 block pattern. Before I messed up, I was able to use TWRP 2.8.3 to load different gapps and roms in the ttinstall file by mounting. Well, I decided Lollipop was not quite what I wanted and wanted to go back to KitKat. Anyway, in my zeal of trying to fix what may be causing the recovery mode issue, I wiped everything and formatted everything...including the ttinstall file. I can still boot to twrp 2.8.3, but honestly, the sequence of invents I have tried to create a new folder called ttinstall and place in there rom and gapps, it will not load. In fact, I'm not sure where the twrp file is located. So, I would appreciate it if someone has detailed instructions beginning with opening twrp 2.8.3. What sd card to use and folder to create where, and so forth. I can mount the TP and load files via the pc, but I don't quite know where they actually go on the tablet. The device shows up as 1gb on the pc and this is a 32gb TP so I know I messed it up. I was spoiled by the TPToolbox when I was able to use the usb recovery mode and make all changes there.
Any help would be appreciated. I did do a search, but I have not found clear instructions for me. I even saw a youtube, but again, it was more confusing. Thanks.
Click to expand...
Click to collapse
Edit: Well, that was easy. I just set up the ttinstall folder, then copied the rom and gapps zip files there, unmounted, then selected install from the twrp menu (rom first then gapps), rebooted and presto...running again.