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).
Related
UPDATE: My hosting I had for XDA related work expired, so I re-uploaded everything here: http://www.mods4cars.com/pub/xda
Hi everyone. As pretty much everyone of us who got suckered into buying this excellent (hardware) tab from Verizon knows, their update strategy has been very slow and on top of that, glitchy. Finally, 4 months after the other editions of this tab, we're getting ICS... BUT the update is an incremental OTA update that fails on 99% of the tabs, because it expects a version FD01b instead of the FD01 most of us have. The update seems to have gone through for only 2 or 3 lucky users who must somehow have had FD01b on their tab when they got it.
So after one of the best collaboration efforts on the "Tab 7.7 General" forums, I am happy to present to you
The CWM flashable "full stock" ROM for the SCH-i815 - ICS IMM76D.LP10
First up, let me stress again that this is a HACK and that this is RISKY and that if something goes wrong you MAY end up with a BRICK that will require complicated revival ceremonies! Unfortunately I *have* to say here, that whatever you do here, you do AT YOUR OWN risk, I can not be held liable for anything!
Prerequisites:
Verizon SCH-i815 LTE Tablet (ONLY this version!) with Honeycomb (everyone should have FD01 at this point)
Windows PC with Samsung USB drivers installed, meaning when you connect the tab, you should be able to copy files to it.
A micro-SD Card 2GB or bigger, preferable BLANK, FAT32 formatted.
Step 1: Prepare the SD card
Connect the SD card to your PC and copy the ROM files to it.
ROM Choices:
Original Cloned ROM (First version with direct partition image copy, requires >1GB space on SD card which has caused issues for some)
http://electron73.org/XDA/i815/electron_ICS-LP10_i815.zip
Update 10/12:
NEW ROM with full ext4 optimizations. System, Cache and Data (only in wipe version) will be cleared, formatted and "fsck -Dfy" checked!
DO NOT WIPE ANYTHING IN CWM!!! Just choose the ROM file appropriately.
Non-Wipe Version (This one leaves existing data partition alone, only checks it for errors)
http://electron73.org/XDA/i815/electron_ICS-LP10_i815_nowipe.zip
Wipe Version (THIS ONE WILL FORMAT DATA PARTITION, ALL USER DATA WILL BE LOST!)
http://electron73.org/XDA/i815/electron_ICS-LP10_i815_wipe.zip
Step 2: Download the Odin CWM Recovery pack and get ready to flash
Odin Pack: http://electron73.org/XDA/i815/electron_i815_odin_pack.zip
This ZIP contains everything you need now and later during this process. Extract it in any folder you like (Desktop/Odin or C:\Odin).
Run Odin3 v1.85.exe
Step 3: Bring the tab into Odin mode
Hold down the power and volume down buttons on your tab continuously until you see the big warning. Press volume UP to enter flash (odin) mode. Connect USB. In Odin the leftmost ID:COM field should now be yellow. Click the PDA button and select the cwm-6.0.1.1-i815.tar file. Leave everything else as-is. Click start to flash and when it says rebooting immediately grab the tab and hold down power and volume UP until you see the blue CWM screen! If you don't do this and let the tab boot, then it will automatically kill CWM (yes, bastards!), so don't let it boot the regular ROM!
Step 4: Flash the ICS ROM
Insert the card into the tablet, then in CWM go to install zip from sdcard, then choose zip from external sdcard. Select the electron_ICS-LP10_i815_v2.zip.
It will flash the kernel, the radio (LTE modem), the factory fs (/system) and preload partitions. The whole flash will take about 5 min. Especially on the last two steps be patient, it takes a while to extract 800mb and then flash the full filesystem image. Turning off power here (or running out of battery juice!) will make the rom unbootable and will require a full re-do. IMPORTANT: This requires the use of an external SD card! Using internal storage will not work!
WARNING: DO NOT wipe or factory reset in CWM! You can simply install ICS over an existing Honeycomb setup! Choose the correct ROM version: One erases everything and the other one preserves user data. Since this was originally an OTA, it knows how to convert your saved data. So all your emails, save games etc. will still be there! We had too many reports of problems when wiping/factory resetting with CWM. So for now the best advice for anyone looking into installing the ROM is DO NOT WIPE!
UPDATED PROCEDURE as of 10/16 - NO NEED to flash the old 3e recovery any more! Much easier and quicker baseband update below...
Step 5: Download and flash the baseband modem.bin with ODIN
Download the baseband update: http://electron73.org/XDA/i815/electron_ICS-LP10_i815_modem.zip
Bring the tab back into ODIN mode the same as before. Extract the modem.bin file from the modem.zip and drop it in the PHONE section (not PDA!) in ODIN this time. Click start and let it flash and reboot. Done. Under settings/about device you should now have Baseband Version i815.04 V.LP10 / I815LP10
B]Step 6: Optional: Keep CWM or go all stock[/B]
If you would rather like to be full stock than keeping CWM as the recovery program, then bring the tab back into ODIN mode one last time (pwr + vol down) and Connect USB, then flash LP10_recovery.
The ROM is pre-rooted. SuperSU is pre-installed as part of the ROM.
Trouble?
If the tab for some reason gets stuck in a boot loop with the Verizon animation playing over and over, don't fret! Give it AT LEAST 10 full minutes to start with and if it still doesn't show the home screen after that, hold down power and vol up until you're in CWM and wipe data/factory reset (yes, that will completely kill all user data and the tab will be "like new").
Trickier: If you see any warnings in CWM or 3e stock recovery, that there was an error mounting /data, then you lost the data partition and need to do extensive hacking before the tab will ever boot again. We fixed exactly this problem beginning on the very bottom of the page here http://forum.xda-developers.com/showthread.php?t=1927392&page=16 so don't panic! This repair surgery thanks to the excellent guide by Androguide.fr here: http://forum.xda-developers.com/showthread.php?t=1862294
Thanks
Thanks to everyone involved in making this happen! Especially asenduk for dumping the image backups from his tab, rayjr13 for bringing this whole thing to my attention and sending me the first OTA bin file.
Every use of the thanks button is greatly appreciated
Hi, thank you so much for these instructions and all the help. I was wondering does that 6.0.1.1 protect you from the brick bug and I saw that you hosted the V2 file in the original thread but here you have the regular file hosted. Is the V2 better?
johnny13oi said:
Hi, thank you so much for these instructions and all the help. I was wondering does that 6.0.1.1 protect you from the brick bug and I saw that you hosted the V2 file in the original thread but here you have the regular file hosted. Is the V2 better?
Click to expand...
Click to collapse
What is this brick bug people speak of? Bricking during a flash or bricking when you're sleeping at night and doing nothing to the tab?
Thanks again for this Rom electronic73! Hopefully some devs will take this as a base and run with it!
Sent from my SCH-I815 using xda premium
johnny13oi said:
Hi, thank you so much for these instructions and all the help. I was wondering does that 6.0.1.1 protect you from the brick bug and I saw that you hosted the V2 file in the original thread but here you have the regular file hosted. Is the V2 better?
Click to expand...
Click to collapse
Yes the 6.0.1.1 (as far as I know!) is safe. No need to wipe anyway. The v2 included more files that turned out to be not necessary. The files posted here along with the updated, safer method of flashing, should be the best and quickest way to get to full stock ICS.
The v2 was mainly an attempt to bring user ice's tab back to life after his data partition got killed.
Newbie question of the day - where is the IMEI stored on the 7.7? If it's in /system, won't this result in *everyone* flashing this image ending up with the same IMEI (which causes a whole set of problems of its own)?
Rodney
Thank you so much, and I do plan on doing a wipe to clear out my Tab to bring it to a clean slate. Just didn't want it to be a broken state lol.
rhester72 said:
Newbie question of the day - where is the IMEI stored on the 7.7? If it's in /system, won't this result in *everyone* flashing this image ending up with the same IMEI (which causes a whole set of problems of its own)?
Rodney
Click to expand...
Click to collapse
IMEI and such is stored in the mmcblk0p1 partition which (along with 2 and 3 which are the bootloader) we don't touch. So no, we only flash the factory fs, lte modem and kernel. CDMA modem.bin via the new method.
electron73 said:
Hi everyone. As pretty much everyone of us who got suckered into buying this excellent (hardware) tab from Verizon knows, their update strategy has been very slow and on top of that, glitchy. Finally, 4 months after the other editions of this tab, we're getting ICS... BUT the update is an incremental OTA update that fails on 99% of the tabs, because it expects a version FD01b instead of the FD01 most of us have. The update seems to have gone through for only 2 or 3 lucky users who must somehow have had FD01b on their tab when they got it.
So after one of the best collaboration efforts on the "Tab 7.7 General" forums, I am happy to present to you
The CWM flashable "full stock" ROM for the SCH-i815 - ICS IMM76D.LP10
First up, let me stress again that this is a HACK and that this is RISKY and that if something goes wrong you MAY end up with a BRICK that will require complicated revival ceremonies! Unfortunately I *have* to say here, that whatever you do here, you do AT YOUR OWN risk, I can not be held liable for anything!
Prerequisites:
Verizon SCH-i815 LTE Tablet (ONLY this version!) with Honeycomb (everyone should have FD01 at this point)
Windows PC with Samsung USB drivers installed, meaning when you connect the tab, you should be able to copy files to it.
A micro-SD Card 2GB or bigger, preferable BLANK, FAT32 formatted.
Step 1: Prepare the SD card
Connect the SD card to your PC and copy the ROM files to it.
ICS ROM: http://electron73.org/XDA/i815/electron_ICS-LP10_i815.zip
Modem Upgrade: http://electron73.org/XDA/i815/electron_ICS-LP10_i815_modem.zip
Make sure you have MORE than 1GB of free space left on the SD card when done.
Step 2: Download the Odin CWM Recovery pack and get ready to flash
Odin Pack: http://electron73.org/XDA/i815/electron_i815_odin_pack.zip
This ZIP contains everything you need now and later during this process. Extract it in any folder you like (Desktop/Odin or C:\Odin).
Run Odin3 v1.85.exe
Step 3: Bring the tab into Odin mode
Hold down the power and volume down buttons on your tab continuously until you see the big warning. Press volume UP to enter flash (odin) mode. Connect USB. In Odin the leftmost ID:COM field should now be yellow. Click the PDA button and select the cwm-6.0.1.1-i815.tar file. Leave everything else as-is. Click start to flash and when it says rebooting immediately grab the tab and hold down power and volume UP until you see the blue CWM screen! If you don't do this and let the tab boot, then it will automatically kill CWM (yes, bastards!), so don't let it boot the regular ROM!
Step 4: Flash the ICS ROM
Insert the card into the tablet, then in CWM go to install zip from sdcard, then choose zip from external sdcard. Select the electron_ICS-LP10_i815_v2.zip.
It will flash the kernel, the radio (LTE modem), the factory fs (/system) and preload partitions. The whole flash will take about 5 min. Especially on the last two steps be patient, it takes a while to extract 800mb and then flash the full filesystem image. Turning off power here (or running out of battery juice!) will make the rom unbootable and will require a full re-do. IMPORTANT: This requires the use of an external SD card! Using internal storage will not work!
BTW there is NO NEED to wipe! You can simply install ICS over an existing Honeycomb setup! Since this was originally an OTA, it knows how to convert your saved data. So all your emails, save games etc. will still be there!
Step 5: Flash the old Honeycomb recovery in order to do the modem upgrade
Since CWM does not understand the proprietary command used to flash the "firmware" which is the base modem file, we need to use STOCK recovery for this. The downside is that, of course, the new recovery is now locked down and won't accept unsigned files. So we need to flash the OLD Honeycomb FD01 recovery and feed it the modem update!
When the CWM flash above is finished and tells you to reboot, simple press and hold power and vol down again to get back into ODIN mode. Connect the USB again and this time use Odin the same way as above, but to flash the FD10_recovery.tar. This time uncheck the "reboot" tick mark.
Step 6: Flash the modem upgrade with the old stock 3e recovery
When Odin is done above, hold down pwr and vol up until you see the old school recovery pop up saying *manual mode*. Select flash update zip from sdcard and select the electron_ICS-LP10_i815_modem.zip this time. It will go on for a while in total bling flight. No output apart from rotating gears! This one is tricky. Just wait until it either ends saying that it is done or a yellow exclamation point shows up in the middle of the screen. The flash is done.
Step 7: Choose between Stock and CWM
Now bring the tab back into ODIN mode one last time (pwr + vol down) and Connect USB, then flash either CWM or LP10_recovery if you rather like to be full stock. If you chose CWM then be aware that the ROM will try to overwrite that immediately on first boot!! In order to avoid that, flash it with "reboot" box unticked and manually reset into CWM mode (pwr + vol up) and inside CWM select reboot system. It will then give you a big warning that the ROM has a CWM killer and offers you to disable that, so CWM will stay in place (good for Nandroids etd).
Step 8: Boot the ICS ROM and enjoy!
Once you see ICS, go to the play store and install SuperSU. The rom is pre-rooted and just needs the SuperSU app for full root access control.
Trouble?
If the tab for some reason gets stuck in a boot loop with the Verizon animation playing over and over, don't fret! Give it AT LEAST 10 full minutes to start with and if it still doesn't show the home screen after that, hold down power and vol up until you're in CWM and wipe data/factory reset (yes, that will completely kill all user data and the tab will be "like new").
Trickier: If you see any warnings in CWM or 3e stock recovery, that there was an error mounting /data, then you lost the data partition and need to do extensive hacking before the tab will ever boot again. We fixed exactly this problem beginning on the very bottom of the page here http://forum.xda-developers.com/showthread.php?t=1927392&page=16 so don't panic! This repair surgery thanks to the excellent guide by Androguide.fr here: http://forum.xda-developers.com/showthread.php?t=1862294
Thanks
Thanks to everyone involved in making this happen! Especially asenduk for dumping the image backups from his tab, rayjr13 for bringing this whole thing to my attention and sending me the first OTA bin file.
Every use of the thanks button is greatly appreciated
Click to expand...
Click to collapse
Hey Electron, thanks again for your outstanding work as well as all involved to make this happen. Since I installed your V2 this morning, I can skip the ICS ROM installation and go straight to step 5 right? Or is it better to start over from scratch?
Sent from my Nexus 7 using xda premium
bathanr said:
Hey Electron, thanks again for your outstanding work as well as all involved to make this happen. Since I installed your V2 this morning, I can skip the ICS ROM installation and go straight to step 5 right? Or is it better to start over from scratch?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Same here, what steps do I take to flash the updated modem
Awesome!
ice0901 said:
Same here, what steps do I take to flash the updated modem
Click to expand...
Click to collapse
from step 5 on forward. no need to reflash the whole rom if you already have ICS running.
Just odin the old recovery on, flash the modem update zip, then odin the new recovery or CWM back.
boot loop
Not sure whats up. Ive had your rom on all day. No problems. When i went to install the modem update, i entered odin and installed stock recovery, and boom, went into a verizon logo boot loop. i continued any way with the modem install, then put cwm back on, then wiped and data factory reset. waited 10 minutes during bootloop. Gave up, totally reflashed entire V2 Rom, again, stuck on a bootloop...so nwiped and data factory reset again,,,,still a bootloop....
bummer...does it just run until battery dies?
rspong said:
Not sure whats up. Ive had your rom on all day. No problems. When i went to install the modem update, i entered odin and installed stock recovery, and boom, went into a verizon logo boot loop. i continued any way with the modem install, then put cwm back on, then wiped and data factory reset. waited 10 minutes during bootloop. Gave up, totally reflashed entire V2 Rom, again, stuck on a bootloop...so nwiped and data factory reset again,,,,still a bootloop....
bummer...does it just run until battery dies?
Click to expand...
Click to collapse
Weird. OK did the v2 flash go all the way through? Did it finish at some point and say "please reboot" ? Or did it get stuck half way though?
Can you in CWM mount your internal storage? Did you get any errors when you did the full wipe/factory reset? anything saying "error mounting /data" maybe ?
electron73, did you create the .pit file in the cwm zip? It does not seem to match my i815 (which may be my problem, that mine is wrong)
I noticed the latest stock rom is like 550mb opposed to the one you uploaded this morning which was 990mb.. Is there a difference?
almus said:
electron73, did you create the .pit file in the cwm zip? It does not seem to match my i815 (which may be my problem, that mine is wrong)
Click to expand...
Click to collapse
No I didn't create it but it is guaranteed the right one for i815. I know because I messed up my partition table last night and had to use that pit to repartition Lucky I found that. What you would do in order to re-do your pit is open odin, put the CWM in the PDA section as usual and then click PIT and select that pit. That should activate a checkbox "repartition device". Leave that on for this one run and click start.
As a result it should partition, then flash the CWM and you should immediately be able to enter CWM. With CWM running connect USB
and use adb shell to get onto your tab.
IN the root prompt enter parted /dev/block/mmcblk0
and in the parted prompt enter print. If you see the result as in the attached pic (note: no file system in the DATAFS line) then you need to fix that the same way ice got it fixed last night. I think the link to the thread is in the OP
bathanr said:
I noticed the latest stock rom is like 550mb opposed to the one you uploaded this morning which was 990mb.. Is there a difference?
Click to expand...
Click to collapse
Yes the difference is that the preload partition (550mb decompressed) is not included any longer. Not needed. It was never altered in the first place. It only contains a game and useless verizon demonstration videos. I found out later that it had been untouched since Honeycomb FA02c
Yes. V2 went through with no problems.in CWM I can mount efs,cache,system but not data. Then in cwm... OK..wiping data then I get a error mounting data. Skipping format
Sent from my DROID RAZR using xda premium
chefdave12118 said:
What is this brick bug people speak of? Bricking during a flash or bricking when you're sleeping at night and doing nothing to the tab?
Thanks again for this Rom electronic73! Hopefully some devs will take this as a base and run with it!
Sent from my SCH-I815 using xda premium
Click to expand...
Click to collapse
The flash controller in our tablets is buggy. See here http://forum.xda-developers.com/showthread.php?t=1862294
electron73 said:
Yes the difference is that the preload partition (550mb decompressed) is not included any longer. Not needed. It was never altered in the first place. It only contains a game and useless verizon demonstration videos. I found out later that it had been untouched since Honeycomb FA02c
Click to expand...
Click to collapse
Thanks again man.. You have put forth an awesome effort in this work.. Sent you a little something as an appreciation:good:
---------- Post added at 09:43 PM ---------- Previous post was at 08:46 PM ----------
bathanr said:
Thanks again man.. You have put forth an awesome effort in this work.. Sent you a little something as an appreciation:good:
Click to expand...
Click to collapse
I ran into the splash screen just hanging and followed the data retore steps. I keep getting this error when trying to print the print command from the parted prompt.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Flatlinz>f:
F:\>cd 7.7
F:\7.7>cd adb
F:\7.7\adb>adb shell
adb server is out of date. killing...
* daemon started successfully *
~ # ls
ls
boot init sys
cache init.rc system
charger lpm.rc tmp
data preload ueventd.goldfish.rc
default.prop proc ueventd.rc
dev recovery ueventd.smdk4210.rc
efs res vendor
etc sbin
external_sd sdcard
~ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Error: Can't have the end before the start!
(parted)
Any ideas?
Hello Everyone
I have run into an odd problem. My tf701 ran out of power while I was watching netflix on it. After that it got stuck on boot. When I tried to fiddle using CWM I found out that I cannot mount data or cache. Further more I get to see 5 lines of "E: can't mount /recovery/*" where * are folders within /recovery/ . I tried to format system using CWM or fastboot, they both say they succeed but when I reboot I still get my bootanimation. At this I am out of ideas as to how I can fix it. Furthermore thanks to being unlocked I lost my warranty .
Any suggestions as to how I can fix it?
devbro said:
Hello Everyone
I have run into an odd problem. My tf701 ran out of power while I was watching netflix on it. After that it got stuck on boot. When I tried to fiddle using CWM I found out that I cannot mount data or cache. Further more I get to see 5 lines of "E: can't mount /recovery/*" where * are folders within /recovery/ . I tried to format system using CWM or fastboot, they both say they succeed but when I reboot I still get my bootanimation. At this I am out of ideas as to how I can fix it. Furthermore thanks to being unlocked I lost my warranty .
Any suggestions as to how I can fix it?
Click to expand...
Click to collapse
Maybe I saw something like this I dont know. Did you try mounting system first and see if that fixes it? I have no idea.
EDIT: from CWM I mean. I had a situtation where some things would not mount. data being one of them.. Not sure what else. Then I just mounted /system and everything was ok. Could it be that for some reason system is not getting mounted and you not formatting it besides an empty directory.
YayYouFixedIt said:
Maybe I saw something like this I dont know. Did you try mounting system first and see if that fixes it? I have no idea.
EDIT: from CWM I mean.
Click to expand...
Click to collapse
Yes I tried no luck. When I try to format /data using fastboot it simply hangs both the device and the terminal too.
devbro said:
Yes I tried no luck. When I try to format /data using fastboot it simply hangs both the device and the terminal too.
Click to expand...
Click to collapse
some corruption seems to have occurred.
perform a hard reset in the 'stock' recovery (this will format /data).
then boot in and re-setup. any userdata you had will be gone (including media/content stored locally, etc.).
in case of /system corruption (after performing the above; you still cannot boot in), you can format that partition separately and re-flash it from the CWM file for the latest posted stock update.
you can find file(s) on droidbasement, as needed.
I belive I have the same probleme, how i could i do it right?
devbro said:
Yes I tried no luck. When I try to format /data using fastboot it simply hangs both the device and the terminal too.
Click to expand...
Click to collapse
How did you try to format data in fastboot??
That's done in recovery afaik.
nero0345 said:
I belive I have the same probleme, how i could i do it right?
Click to expand...
Click to collapse
What problem do you have? /data not mounting? Format it in recovery but you will loose everything stored on your internal SD.
I finally took my tablet in for a check with asus. They said that I ahve corrupted my boot and since I replace the recovery there is no way to fix it. the only way to fix it is to replace the motherboard at this point. It will cost 190$ to replace!!!!
Just as an update to the future readers. I ended up replacing my logic board inside using one that I got from ebay. My tablet now works just as new. As per advice of the Asus tech, DO NOT FLASH a new recovery. If anything goes wrong the original asus recovery is the only way to fix things.
devbro said:
Just as an update to the future readers. I ended up replacing my logic board inside using one that I got from ebay. My tablet now works just as new. As per advice of the Asus tech, DO NOT FLASH a new recovery. If anything goes wrong the original asus recovery is the only way to fix things.
Click to expand...
Click to collapse
I beg to differ....
The stock recovery can only flash firmware signed by Asus and perform some crude wipe operations.
With a custom recovery you have way more tools at hand to fix problems:
You can wipe or format partitions selectively
You can take nandroids and restore them
You can check the integrity of file systems on partitions
You can fix permissions
You can flash SuperSU, custom roms and more
Some have a build in file manager allowing you to move data off the tablet even if it doesn't boot anymore
Some have a build in terminal you can run commands from.
The list goes on...
But sure - you have to do all of the above including flashing the custom recovery correctly or you can seriously damage your device like you did.
I am really sorry that you lost your mainboard and had to buy a new one, but don't kid yourself: It was not the custom recovery damaging your tablet. It was you...
berndblb said:
I beg to differ....
The stock recovery can only flash firmware signed by Asus and perform some crude wipe operations.
With a custom recovery you have way more tools at hand to fix problems:
You can wipe or format partitions selectively
You can take nandroids and restore them
You can check the integrity of file systems on partitions
You can fix permissions
You can flash SuperSU, custom roms and more
Some have a build in file manager allowing you to move data off the tablet even if it doesn't boot anymore
Some have a build in terminal you can run commands from.
The list goes on...
But sure - you have to do all of the above including flashing the custom recovery correctly or you can seriously damage your device like you did.
I am really sorry that you lost your mainboard and had to buy a new one, but don't kid yourself: It was not the custom recovery damaging your tablet. It was you...
Click to expand...
Click to collapse
When I talked to the tech at their center, there is apparently some special actions that only their recovery can do. These actions are those that allow changing boot table and other low level functions of the tablet which has nothing to do with the built-in memory or system files.
If I did not replace the recovery, then the repair by asus would have only cost 40$.
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.
Disclaimer: I'm relatively new to the realm of modding the the kindle. I have a 2012 7" hd. I rooted it and loaded a 2nd bootloader and recovery via various tutorials. I attempted to to load a rom (lolipop 5.1 and corresponding gapps). The process seemed to go fine and when it booted into android the initial setup screens appeared (connect to wifi etc); but then I got a message that the setup wizard had failed. I tried "skipping" screens etc and regardless of what I did I couldn't get past that screen. I clearly either did something wrong or didn't have a good rom file. I was an idiot and didn't create a backup before flashing the new rom. So I mounted it in recovery and loaded a factory image that way and flashed back to norm. My intention was to start things over. I rooted again, went through the whole process; however, I'm seeing a weird phenomenon. When I am in windows (or ES explorer for that matter) and access the files on the sd card partition...I can load files onto there (for flashing in recovery etc); however, once I am actually in recovery and go to "install" the partition that I view in recovery is the files I had from the very first flash. I can create new files in windows or ES explorer and everything works as expected....but once in recovery, none of those folders are present...and the only zip files that are available to "install" are the ones I used the first time that didn't work. I'm clearly looking at some other partition or image in recovery than I am in windows. I have cleared cache and everything I can think of (again I'm a complete amateur). Does anyone have a suggestion of what I am doing wrong or how to resolve? Thanks in advance.
Cranky
The issue with your first problem was that it could have been a bad gapps, in the future try different gapps if you see weird problems like that, to your second problem, when flashing lollipop on a device that had ICS it'll change the directory of the SDcard, no biggie though, just search in recovery data/media/legacy or data/media/0 it should be in one of those that your files are in.
Sent from my Nexus 9 using Tapatalk
Try this.
Try to send files over using adb whilst in recovery. If you do not know how then watch this youtube(dot)com/watch?v=NaK5OxUeDKM
sorry im not allowed to post links because im a new user.
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.