Related
Damnit.. My company required encryption of the data on my Nexus S when I was testing ICS Beta with Email / Exchange.
Went ahead and encrypted the device.
Then, I wanted to install ICS Combo Beta 11, so I formatted /system /data /boot and tried to install from /sdcard/*.zip.
No luck.
Clockworkmod recovery cannot mount /sdcard anymore.
Wanted to try and format it, but the clockworkmod tries to mount it first, before formatting
HELP!
I'm stuck with only recovery now and no way to get the update package installed
Is there a way to install from zip via the command line?
You should be able to use fastboot to load the rom on your device. I haven't tried it this way before but it should work:
Code:
fastboot update rom.zip [-w if you want to erase data too]
Give it a spin.
The SDCard not being able to be mounted has been covered a few times but I can't recall the proper fix by heart - search around and you'll definitely get some results that can help you with that.
Greetz
Sounds like it's busted.
Sent from my Nexus S using xda premium
Can you still enable USB Mass Storage in recovery? Try reformat the SD from your desktop?
Si_NZ said:
Can you still enable USB Mass Storage in recovery? Try reformat the SD from your desktop?
Click to expand...
Click to collapse
Thought about that, but what filesystem? FAT32?
Sure
Greetz
I had the same problem with one of the first ICS betas.
Formatting to FAT32 on my Mac was not enough, I had also to reformat under Android. Hope, you backed up your data
dr911 said:
I had the same problem with one of the first ICS betas.
Formatting to FAT32 on my Mac was not enough, I had also to reformat under Android. Hope, you backed up your data
Click to expand...
Click to collapse
Definately backed up..
This was a real scare.. I couldn't mount or format from clockworkmodrecovery. All I had was the adb shell and the builtin /sbin commands.
LUCKILY I found this article;
http://forum.cyanogenmod.com/topic/...mmcblk0++mkfs++ext2__fromsearch__1#entry56396
It didn't exactly match what I was experiencing, but the key was the parted program.
Using it, I was able to reformat my media (partition 3) and am now able to repush things to it.
Stupid sdcard encryption..
Reinstalling ICS Beta 11 now
Blood pressure slowly decreasing.. damn that was a nightmare
So some lessons learned;
DON'T try to partition your SDCARD from clockworkmod or Windows or Mac. The USB storage presented to your computer is a single partiton from you mmcblk0 sd storage. If you partition it, you've got a partition inside a partition which will only make sense to your windows/mac system. Inside of Android, the partition is essentially corrupted and it won't mount.
Formatting from Windows only makes it appear to be working.. in reality you've created a second partition and it's corrupted from the Android point of view.
parted is the only way to fix it. from parted do mkfs type fat32 partiton 3 (media) that will reformat the partition correctly and give you access from Android and external USB hosts.
That's weird...
People have been able to format the SD as ext4 on a desktop using Ubuntu for example. I don't understand how that is different to mkfs.ext4 vs mkfs.vfat. I mean why am I confined to formatting on the phone itself? I'm really confused now.
On a side note. What you experienced is totally expected if you think about it carefully. It's like you have just lost the key to open your SD content by wiping the phone, of course it can no longer be mounted. But I'm not sure why it cannot be simply formatted in CWM.
nauckwj said:
Formatting from Windows only makes it appear to be working.. in reality you've created a second partition and it's corrupted from the Android point of view.
Click to expand...
Click to collapse
That means, I should check my SD Card, which I formatted under OSX with Disk Utility?
Maybe I'll do it next time I flash a new ROM, because for now it works fine.
nauckwj said:
Blood pressure slowly decreasing.. damn that was a nightmare
Click to expand...
Click to collapse
Yeah, I had a similar situation a few weeks after I got my beloved NS when I tried Whispercore. The hole NS got encrypted and formatting the system partition in CWM didn't work, but what I read it was luckily due to a problem with the CWM version. Flashing a newer Version of CWM solved the problem. First I was dying!
So, when I encrypted with ICS and got this problem I calmed down much faster
Si_NZ said:
That's weird...
People have been able to format the SD as ext4 on a desktop using Ubuntu for example. I don't understand how that is different to mkfs.ext4 vs mkfs.vfat. I mean why am I confined to formatting on the phone itself? I'm really confused now.
On a side note. What you experienced is totally expected if you think about it carefully. It's like you have just lost the key to open your SD content by wiping the phone, of course it can no longer be mounted. But I'm not sure why it cannot be simply formatted in CWM.
Click to expand...
Click to collapse
My problem was I used the Windows fdisk partitioning utility to repartition my /sdcard partition. That was part of the problem. I did also read how some people were repartitioning the /sdcard partition, which is kind of weird. I can understand why someone might want to reformat it as an ext4 filesystem, but why would you want to partition a partition?
The /sdcard partition is actually the third partition on your mmcblk0 device. If you partition it, most utilities will fail to recognize it as a valid media device anymore, because they expect to be able to read the filesystem data structures when they mount it. These won't exist if a partition table is sitting at the beginning of the blocks.
I couldn't reformat from within CWM because it first tries to mount the partition. if it fails to mount, CWM won't reformat it. Only way to reformat it was with parted, unless you have a working system installation.
Last night I was also able to reformat it from within ICS. Had to do a full factory-wipe from within ICS, then it indicated the sdcard was no longer valid and asked me if I wanted to reformat it. Once I said yes, all was back to normal.
Fun fun
This question probably belongs in the thread "[ROMS]NEW! Dualboot Mirage CM7 / ICS CM9 Image for SDcard [3/26]", except that I can't post there yet.
I was able to create a working dual boot card per the instructions. However, I could not make a working card that made use of all 16 GB of my card, rather than just the <4GB size of the image file. The card still worked when I used fdisk on my Mac to increase the size of the last, 'sdcard', partition to fill up the available space. However, that did not increase the capacity of the FAT volume in that partition, leaving the extra space still unavailable.
After saving the files from that volume, I then used the Mac's Disk Utility to erase the partition and re-create it as a FAT partition using all the available space. Once I did that, unfortunately, the Nook would then not recognize anything on the SD card and would only boot into the Nook's own ROM.
As an alternative, I tried leaving the existing partitions alone and editing the MBR with fdisk to create a new partition using the available space, which I then formatted as a FAT partition with Disk Utility. Again, the Nook would no longer recognize the SD card and would only boot into its stock ROM.
I actually tried the above with two 16GB SD cards, a SanDisk Class 4 and a Samsung Class 10, and with two Nooks. Moreover, I tried a number of manipulations of the MBR, mostly to make it identical to the original one except for necessary size changes. Nothing worked to get a card that would boot and use the full 16 GB. I'll admit I haven't tried everything, such as trying to resize to something less than the full 16GB, but I've put so much time into this already that I don't want to do any more until I get some feedback.
aarons510 said:
This question probably belongs in the thread "[ROMS]NEW! Dualboot Mirage CM7 / ICS CM9 Image for SDcard [3/26]", except that I can't post there yet.
I was able to create a working dual boot card per the instructions. However, I could not make a working card that made use of all 16 GB of my card, rather than just the <4GB size of the image file. The card still worked when I used fdisk on my Mac to increase the size of the last, 'sdcard', partition to fill up the available space. However, that did not increase the capacity of the FAT volume in that partition, leaving the extra space still unavailable.
After saving the files from that volume, I then used the Mac's Disk Utility to erase the partition and re-create it as a FAT partition using all the available space. Once I did that, unfortunately, the Nook would then not recognize anything on the SD card and would only boot into the Nook's own ROM.
As an alternative, I tried leaving the existing partitions alone and editing the MBR with fdisk to create a new partition using the available space, which I then formatted as a FAT partition with Disk Utility. Again, the Nook would no longer recognize the SD card and would only boot into its stock ROM.
I actually tried the above with two 16GB SD cards, a SanDisk Class 4 and a Samsung Class 10, and with two Nooks. Moreover, I tried a number of manipulations of the MBR, mostly to make it identical to the original one except for necessary size changes. Nothing worked to get a card that would boot and use the full 16 GB. I'll admit I haven't tried everything, such as trying to resize to something less than the full 16GB, but I've put so much time into this already that I don't want to do any more until I get some feedback.
Click to expand...
Click to collapse
Well you're missing just one step after fdisk. If Disk Utility is failing at it you could try terminal:
First you need to find out where your /sdcard is being mounted at. Use "diskutil list" to find out
Once you find out where it's being mounted (eg. /dev/disk4s7). You will then need to unmount the volumes before you can format it.
Code:
$ diskutil unmountDisk /dev/disk4s*
$ diskutil partitionDisk "/dev/disk*" 1 MBRFormat "MS-DOS FAT32" "sdcard" "*M"
Replace * with the actual values needed. You might need "sudo" to perform the format command. Make sure you're formatting the correct mount point or else you might end up wiping your system. But if you were able to use fdisk, I'm sure you have a good understanding of terminal.
Haven't tried it myself. But it should(might) work.
-Racks
Won't "diskutil partitionDisk ..." wipe out all volumes on disk?
racks11479 said:
[See previous post!]
Click to expand...
Click to collapse
When I type
Code:
diskutil partitionDisk
in Terminal to get usage info, I see, inter alia, the following:
Code:
(Re)Partition an existing disk. All volumes on this disk will be destroyed.
But that is clearly not what I want to do. Am I missing something?
Updated update:
I have tried, several times and on both SD cards and both Nooks, diskutil eraseVolume, a presumably more powerful version of the erase option in Disk Utility. I tried one or another of the commands:
Code:
diskutil eraseVolume MS-DOS sdcard /dev/disk4s7
diskutil eraseVolume 'MS-DOS FAT32' sdcard /dev/disk4s7
on cards that were booting, but with the small sdcard partition or the small volume on the enlarged partition. I also tried at least one of those commands on a card that was already not working after modification. In all cases, the commands ran without error but produced a non-booting card. Changing the 'ob' partition id back to 'oc' with fdisk didn't help, nor did any restoration of the original fdisk MBR info.
In sum, the only change that I have been able to make to a card as originally written from the image without making it unbootable was to enlarge the sdcard partition while leaving the sdcard volume untouched, and therefore not using most of the capacity of the partition.
Some more general but related questions.
Since I've got your attention, Racks, let me ask a few questions whose answers might help me and others understand what is going on here and what might go wrong with this and other Nook Color boot setups. Of course, also please point out where anything I think I know is, in fact, wrong.
1) I understand that the firmware boot code on the Nook first looks for something on an inserted SD card to boot from. It seems it looks for a file named u-boot.bin on the first partition of the inserted card to which to transfer control. Does it also check other things on the card before transferring control to u-boot.bin? Does it look at the file MLO? Does it look at the partition labeled sdcard, or at any other partition, before doing so?
2) Presuming that it does transfer control to u-boot.bin, what does the latter check before either booting from the (default) ROM on the card or, if the Home button is being held down, going to the interactive boot dialogue? My experience has been that, when using one of my 'non-working' cards, the Nook goes quickly to the ROM on internal memory without showing any visible signs of doing anything else first. In other words, it 'knows' that it can't boot from a ROM on the sdcard before actually trying to do so.
Dear Members!
I did the stupid thing of using a tool, not completly knowing what it does.
After using TouchEraser.zip I installed Alpha-FormatTouch-2.zip using clockwork.
I tried to boot the device, no luck...
Clockwork says:
can't mount /cache/recovery/log/log
can't open /cache/recovery/log/log
can't mount /cache/recovery/log/last_log
can't open /cache/recovery/log/last_log
Please help!
Stupidly enough I don't have the devices own factory image.
What to do now?
ok , first boot with noogie image and lets see what partion u got , if u have got rom partions so take a copy all files from it and take backup from the whole nook and do this steps in this post
http://forum.xda-developers.com/showpost.php?p=30722156&postcount=2
but u must try to recovery ur nook partition rom especially cuz very important ..... before do anything above .... i will keep continue active in this thread
good luck
only one partition on on gParted...
Do You think theres any way to fix it? how?
If CWR came up that far then the /rom partition must be ok.
All we know is that the /cache partition has a problem.
That's a disposable partition, you can format the /cache partition.
Be careful, don't make anything worse.
auerg said:
Do You think theres any way to fix it? how?
Click to expand...
Click to collapse
as Renate say ..... dont make anything more worth .... so can u type fdisk for ur nook to see all ur partition table info???
Pretty screwed...
speedman2202 said:
as Renate say ..... dont make anything more worth .... so can u type fdisk for ur nook to see all ur partition table info???
Click to expand...
Click to collapse
I did but what it listed is ONLY ONE 1,8 gb partition. Toucheraser probably wiped the whole table (
I'd need a tool to restore the original filesystem or a factory image ( I don't have my own...).
I found one for glowlight, but probably I shouldn't write that to my mormal NST.
Alpha-FormatTouch-2.zip using clockwork.didn't work.
I'm pretty screwed...
Get Clockwork Recovery working on an SD card.
Get ADB setup and connected to CWR.
Run nookpart.sh from a shell (download the script from my signature).
This will recreate the partitioning without formatting or writing any of them.
You can then see if/what you can mount.
Use either the mount options in CWR or the mount command in ADB.
U kidding with me. Did u format the whole partition.? I suggest u try again and boot ur nook with noogie image and the all sevsen partition will show to U?
Tru agan man. Good luck
Sent from my NOOK using xda app-developers app
resurect nook
Renate NST said:
Get Clockwork Recovery working on an SD card.
Get ADB setup and connected to CWR.
Run nookpart.sh from a shell (download the script from my signature).
This will recreate the partitioning without formatting or writing any of them.
You can then see if/what you can mount.
Use either the mount options in CWR or the mount command in ADB.
Click to expand...
Click to collapse
I even can`t do that!,"my" nook simple are "dead" after, i delette all the memorie intern with MINI TOOL PARTITION WIZARD, without make backup or copy room, very nervius then, with CLOCKWORK RECOVERY in a sd card y instal a program call ALPHA FORMAT TOUCH2, after that my nook are iresponsive .no sd card function
any more no usb conection just charge, ¿can is posible resurrect it by some way?
dummy56 said:
...
i delette all the memorie intern with MINI TOOL PARTITION WIZARD, without make backup or copy room,
...
¿can is posible resurrect it by some way?
Click to expand...
Click to collapse
The only way I can think of to quasi-resurrect your Nook is if you can obtain a full image backup of another Nook (e.g., boot it up with noogie and read/save its entire drive as an image file) then write the backup image file back to your Nook (after booting it up with noogie) -- but then the two Nook devices will have identical device-specific data (e.g., encryption keys, WiFi MAC address, etc.), which can cause Internet access/communication problems of various sorts.
The batery are charged but it won't power on , after i install ALPHA FORMAT TOUCH2
maybe i kill him.
Wow, this is an old thread!
The Nook Simple Touch was/is a simple device.
With its SD card it's almost completely unbrickable.
Add in the stuff we've learned in the last few years about booting over USB and it's almost unsinkable.
First, whenever somebody says "dead", it's never clear what the state is.
Until you get to the point where the screen is initialized you don't know what's going on.
If you have Windows where it goes "bong" when you plug in a USB device, see if it "bongs" when you connect/power up/power down.
As said above, you'll probably need to find a full NST image somewhere.
similar to this http://forum.xda-developers.com/showthread.php?t=2322762
-------------------------------------------------------------------------
the batery are charged the machine have no image and whent i plug in a usb, no screen are inicialized just windowsXP said "OMAP3630 - No driver found". :silly:
Dear Renate, may I kindly ask you to provide the command prompt syntax here for dummies like me: "Run nookpart.sh from a shell (download the script from my signature)"? I know how to use adb, but with a ready syntax only.
And I have a spare completely bricked NSTGL, it was brought to me bricked already, managed to write an image from my current NSTGL using MiniTool Partition Wizard, and was able to open it in Windows Explorer, could see all files and folders, could add, copy and delete anything, but never succeeded in seeing any sign of life at the Nook's screen (nothing at all, never), and tried everything with a battery - disconnected it, pressed the switch button at the mainboard for some time, charged fully etc., then one unhappy day I have tried to overwrite it with a new image, but forgot to delete all partitions first and it crashed during the writing process in MiniTool Partition Wizard and now it is recognized by Windows (bang) and shown as a (some) drive but I cannot open it. Obviously I have damaged the partition table, and since then was unable to restore it, and now came across your messages here. Although, I am afraid restoring the partition table will do me no good, as it already showed no sign of life with a healthy image onboard. And I would appreciate it if you provide here a syntax for adbsync too
Mnurlan said:
Dear Renate, may I kindly ask you to provide the command prompt syntax here for dummies like me: "Run nookpart.sh from a shell (download the script from my signature)"? I know how to use adb, but with a ready syntax only.
...
And I would appreciate it if you provide here a syntax for adbsync too
Click to expand...
Click to collapse
I think a simpler, more expedient alternative to any adb-based method would be:
Use a disk-imaging tool (such as win32diskimager) and write to SD-card the image Noogie.img
Boot your live NSTGL off the Noogie SD-card and connect it to your PC via USB
Use the disk-imaging tool to read/save the NSTGL drive image to a file on your PC
Disconnect your live NSTGL from your PC
Boot your bad NSTGL off the Noogie SD-card and connect it to your PC via USB
Use the disk-imaging tool to write the file containing previously saved image of the live NSTGL drive to the bad NSTGL drive.
When writing out a disk image, make sure that you select the correct target drive (in particular don't select by mistake your PC "C:" drive).
Afterward you will have to figure out how to resolve the issue of the two Nook devices having identical device-specific data (e.g., encryption keys, WiFi MAC address, etc.), which can cause Internet access/communication problems of various sorts.
@Mnurlan I think @digixmax has it about right.
Just copying a whole image over is probably the easiest way.
If you have a raw image of the whole disk then the partitioning comes over just like all the other data.
@dummy56 if your device is IDing as OMAP3630 then what you have there is the bootloader.
The easiest thing to try would be just like above, with noogie and a full 2GB image from a friend.
Depending on what got overwritten, you might be able to fix things with just a recovery and ADB.
2 digixmax and 2 Renate
This is exactly what I did, remember I said that I received the "bad" NSTGL bricked already, so of course I took an image of my healthy (live) NSTGL FW1.2.0 to overwrite (re-write) whatever was left on "bad-dead" NSTGL, and I know in details how to write-read-save an image with win32diskimager, just during the second attempt I forgot to delete all partitions first and that resulted in damaged partitions - that is my educated guess. I would like to point out that my first attempt was successful (I have copied a healthy image of my live NSTGL to a bad one) and I was able to read-see-delete-add anything to NSTGL in Windows Explorer whenever I connect that dead NSTGL to PC directly, without a Noogie.
I am afraid, the screen has been damaged somehow (although it looks visibly intact), as it never showed any sign of life, no matter whatever I've tried.
And now the problem is that no Nook's partition appears in the MiniTool Partition Wizard window, only SD-card with Noogie, so I have nowhere to write an image. This is why I thought the culprit is - a damaged partition table. I have tried to use the GParted Live CD, but my notebook failed to boot on it, so I just postponed it for a while, as I had to leave for my rotation. Currently I am away from home and I left that "bad" NSTGL at home, and won't be able to do anything about it until I am back on Feb. 18.
And having two Nook devices having identical device-specific data is the least of my problems as I am pretty sure that I can easily do without W-Fi functionality of that Nook should I manage to revive it somehow, which I doubt.
Mnurlan said:
This is exactly what I did, remember I said that I received the "bad" NSTGL bricked already, so of course I took an image of my healthy (live) NSTGL FW1.2.0 to overwrite (re-write) whatever was left on "bad-dead" NSTGL, and I know in details how to write-read-save an image with win32diskimager, just during the second attempt I forgot to delete all partitions first and that resulted in damaged partitions - that is my educated guess.
...
And now the problem is that no Nook's partition appears in the MiniTool Partition Wizard window, only SD-card with Noogie, so I have nowhere to write an image. This is why I thought the culprit is - a damaged partition table.
Click to expand...
Click to collapse
Since Wiin32DiskImager can read/write from/to a raw physical device, there is no need to clear/fix the partition table of the bad NSTGL using MiniTool or GParted before re-imaging it.
As long as your bad NSTGL when booted on Noogie appears as a raw physical drive in Win32DiskImager's drive-selection menu, you can re-image the bad NSTGL using the raw drive image of the good NSTGL.
NSTGL in question appears as (some) drive in Windows Explorer window, but does not appear in the Wiin32DiskImager's drive selection window, and I run it As Administrator
hi, i have been trying to get a dual boot with wp7 (hd20 8779) with android jellybean (paranoidandroid) using ext4 on the sd.
i have right now:
magldr v1.13
ext4 recovery nand
partitions:
1st FAT 14gb
2nd EXT4 1gb (made via ext4 recovery)
there is no 'nativesd' folder that i can see on the sd card (to put the jellyb.zip rom in?) and it (ext4 recovery) will not let me install zip from sd (either jellyb.zip rom or dual installer zip. it just says:
Finding update package...
Opening update package...
Installing update...
Installation aborted.
I am also confused about which rom I should go about installing first at this point. wp7 or droid?
---- edit:
ok, i was using the wrong android rom. aokp nativesd worked. booted, tested it, all ok. but then i went to install wp7 and it erased it. wp7 booted, worked. took out sd, hooked sd up to computer, repartitioned to have wp7 ||| fat32 ||| ext4, but then when i put it back into phone and booted to wp7 (to make sure it was still there), it said available storage was entire sd card. so i powered down and tried to boot into android. now android was gone. tried to boot into ext4 recovery and that was gone too.
i am very close now. i just need help partitioning this correctly. i know now that the latest version of minitool will let me partition to ext 4 so that's no problem now. can someone please help me set up my partitions so that i don't lose one installation with another? also, i don't know how to check if something is mmcblk0p2 or how to set it to that. i haven't been able to find any instructions in doing so, just mentions of it across the forums.
please help
Okay.
You probably have WP7 now, right? You've already partitioned the card with xboxmod's CABs, haven't you? If not, please do those two steps before continuing.
Windows Phone 7 wipes entire SD card and creates its own partition every time it's installed or hard reset, and because of that you can't install Android ROM first and then WP7.
After that, just take MiniTool, delete the FAT partition and create two new:
First FAT partition, then on the rest create EXT partition. It should be mmcblk0p2 then, but you want to check it anyway. How to was in that thread:
6. (WP7 users) make sure the EXT4 partition is located @ /dev/block/mmcblk0p2
To check this mount your sd-ext partition in 4EXT recovery and use adb shell or QtADB shell and type df
Click to expand...
Click to collapse
If you don't have ADB yet, please download Android SDK where that tool is included. Or try QtADB, but I haven't used that one.
That instruction translates to:
1. Run 4EXT Recovery
2. Choose Mount... option
3. Mount /sd-ext
4. Run adb shell (type that in CMD when in folder with adb.exe, I hope you can navigate with CMD)
5. Type df and press enter.
Then install the ROM using 4EXT SD Recovery. Nothing complicated, I hope. That's how I've done that at least.
thank you
Spaqin said:
Okay.
You probably have WP7 now, right? You've already partitioned the card with xboxmod's CABs, haven't you? If not, please do those two steps before continuing.
Windows Phone 7 wipes entire SD card and creates its own partition every time it's installed or hard reset, and because of that you can't install Android ROM first and then WP7.
After that, just take MiniTool, delete the FAT partition and create two new:
First FAT partition, then on the rest create EXT partition. It should be mmcblk0p2 then, but you want to check it anyway. How to was in that thread:
If you don't have ADB yet, please download Android SDK where that tool is included. Or try QtADB, but I haven't used that one.
That instruction translates to:
1. Run 4EXT Recovery
2. Choose Mount... option
3. Mount /sd-ext
4. Run adb shell (type that in CMD when in folder with adb.exe, I hope you can navigate with CMD)
5. Type df and press enter.
Then install the ROM using 4EXT SD Recovery. Nothing complicated, I hope. That's how I've done that at least.
Click to expand...
Click to collapse
wp7 is installed. after several searches, i'm not seeing the cab files you're talking about. the current partition structure is 200mb fat ||| 14.67gb 'other' ||| I saw that part in the thread with mmcblk0p2, but I had no idea how to specify that when I made the partition or how to check it. Thank you. Yes, I have the Android SDK (had no idea that's where to find ADB) Thanks for elaborating that for me. I am going to do all this right now!
--- edit
how do i check to make sure its mmcblk0p2?
if i just repartition in minitool everything, do i still need the xboxmod cab files i can't find?
--- edit
i repartitioned with minitool and this is what i have now:
1st) 7.88mb (free) 0 (used) unallocated logical
2nd) 5.81gb (free) 11.65mb (used?) fat32 logical
3rd) 1.46gb (free) 101.80mb (used?) ext4 primary
4th) 7.67gb (free) 7.67gb (used) unformatted primary
now, i'm going to install ext4recovery nand and try to install android, is this correct?
--- edit
i'm not seeing adb anywhere. In android sdk tools i have two shortcuts: AVD Manager and SDK Manager. I don't see adb in either. I'm loaded into EXT4 Recovery Nand now.
--- edit
After looking in the android sdk program directory in windows i found adb-has-moved.txt It says:
Code:
The adb tool has moved to platform-tools/
If you don't see this directory in your SDK,
launch the SDK and AVD Manager (execute the android tool)
and install "Android SDK Platform-tools"
Please also update your PATH environment variable to
include the platform-tools/ directory, so you can
execute adb from any location.
--- edit
when i get this completely finished, I'm going to do it again to another phone, and I'm going to make a COMPLETE step by step guide from start to finish for noobies like me and post it.
---- edit
after going to a cmd prompt and navigating to the 'platform-tools' directory and typing adb, press enter, then typing 'df', press enter, i get this error:
Code:
'df' is not recognized as an internal or external command, operable program or batch file.
--- edit
i'm attaching a screenshot, i used the command 'adb shell' then enter then the command 'df'. although i have no idea if this is doing this to my sd card on my phone which has the sd-ext mounted.
Oh, you resized WP7 like that (with partitioning tool), okay, it's fine too. You will have to hardreset though. No need to use CABs then.
ADB is in C:\android-sdk-windows\platform-tools if you've downloaded it (platform tools) from that installer/updater of course.
Browse there with CMD and use adb shell.
Please remember to set both FAT and EXT4 partitions primary, else it won't work.
After you check if the partition is in that mmc02 thing, you can install the ROM with the recovery.
thank you
Spaqin said:
Oh, you resized WP7 like that (with partitioning tool), okay, it's fine too. You will have to hardreset though. No need to use CABs then.
ADB is in C:\android-sdk-windows\platform-tools if you've downloaded it (platform tools) from that installer/updater of course.
Browse there with CMD and use adb shell.
Please remember to set both FAT and EXT4 partitions primary, else it won't work.
After you check if the partition is in that mmc02 thing, you can install the ROM with the recovery.
Click to expand...
Click to collapse
ok i'm attaching a screenshot of my partitions in minitool. i made the fat primary as well. now i'm going to copy over the aokp jellybean rom and try to install it. fingers crossed! also, i hard reset wp7 when i first installed it. i'm afraid if i do it now, it will undo all the partitioning steps i've taken after that. is this correct?
---- edit
ok, something went wrong, because after i installed android from ext4 recovery nand, i powered down, booted into magldr 1.13 and selected '1. Boot WPH' and it said: 'WPH not installed.' aaaaaaahhhhhh!!!! lol
any ideas where i might have gone wrong?
---- edit
btw, when i booted into android (1st boot) i checked the space, and it said the 5.81gb or whatever it was, so i think the partitions are intact. could this be a 'uselast24NAND' issue? i don't think i did that when i installed wp7, i couldn't remember when i was supposed to do that. ah geeeeeeeez
noobinius said:
ok i'm attaching a screenshot of my partitions in minitool. i made the fat primary as well. now i'm going to copy over the aokp jellybean rom and try to install it. fingers crossed! also, i hard reset wp7 when i first installed it. i'm afraid if i do it now, it will undo all the partitioning steps i've taken after that. is this correct?
Click to expand...
Click to collapse
First check that WP7 still boots (if you've followed most of the tutorial for the old dual boot 1 sd card method you should be fine, otherwise you'll have to start over), and don't use 4ext nand recovery (doubt it'll run anyway), you need the 4ext SD version.
Just follow this , with the difference being having 3 partitions at the end ( FAT32|||EXT4|||WP7) then install via a SD ported recovery
thank you
HypoTurtle said:
First check that WP7 still boots (if you've followed most of the tutorial for the old dual boot 1 sd card method you should be fine, otherwise you'll have to start over), and don't use 4ext nand recovery (doubt it'll run anyway), you need the 4ext SD version.
Click to expand...
Click to collapse
ok, thanks hypoturtle. ok, i am going to take a little break, then find the sd version of 4ext, then i'm going to task29 this monster with hd2 toolkit and completely start over. i will update this thread with what happens and what i did. when i'm done i plan to make a complete step by step guide with links and all so there will be something with ALL the information and links in one place, placing all credit where it is due to the original developers. i am not a developer.
Yeah, that was the problem. You can't use NAND recoveries when on WP7 because they will format NAND and prepare partitions for Android, deleting WP7. For that you need SD Recovery ported by Xylo (available in NativeSD thread). After WP7 is installed, you don't even touch anything that's NAND related because it will break everything.
Check this video tut http://forum.xda-developers.com/showthread.php?t=944288
1. install wp7
2 make android partition as in vid.
You should have after the above.
<50% of sd card volume as FAT32 on first partition (primary)
>50% of volume unformatted (WP7) on second (primary)
Then you can create ext4 partition as second partition (also set as primary), I would use minitool again to shrink your FAT partition (but use 4ext recovery sd to format it see http://forum.xda-developers.com/showpost.php?p=31247925&postcount=3464 and the post before it)
So you have 3 partitions 1. fat android 2. ext4 3. wp7
I have not tried a smaller wp7 partition than 50%, don't know if it would work but 96edwy has suggested not to do this in vid.
thank you
thank you guys for your help. i have got it working and have made a step by step guide as i did it. just one problem, and i reaaaaallly hope its not a big problem. but in android it says no sd card. i need to know how to show whatever explorer program i use in android to look at the fat32 partition. anyone know?
i also need to know how to make wp7 see the fat32 partition that will have all the media files on it. anyone?
as soon as i get this information, i will post the guide. but i don't want to post it if there is something wrong (android and windows not reading the fat32 parition).
other than that both operating systems are still there and android is running from ext4 from folder nativesd!!!
noobinius said:
thank you guys for your help. i have got it working and have made a step by step guide as i did it. just one problem, and i reaaaaallly hope its not a big problem. but in android it says no sd card. i need to know how to show whatever explorer program i use in android to look at the fat32 partition. anyone know?
i also need to know how to make wp7 see the fat32 partition that will have all the media files on it. anyone?
as soon as i get this information, i will post the guide. but i don't want to post it if there is something wrong (android and windows not reading the fat32 parition).
other than that both operating systems are still there and android is running from ext4 from folder nativesd!!!
Click to expand...
Click to collapse
Check that all the partitions are set as primary, that's the only thing I can think of.
HypoTurtle said:
Check that all the partitions are set as primary, that's the only thing I can think of.
Click to expand...
Click to collapse
well, i just checked it. i'm attaching the screenshot that shows the partitions. i'm a little scared to change the last one (the wp7 one) to primary for fear of messing it all up again. also, that shouldn't effect androids view of the fat32 which is set to primary right?
noobinius said:
well, i just checked it. i'm attaching the screenshot that shows the partitions. i'm a little scared to change the last one (the wp7 one) to primary for fear of messing it all up again. also, that shouldn't effect androids view of the fat32 which is set to primary right?
Click to expand...
Click to collapse
Can't imagine that would cause the issue, you have them layed out as Fat32 | EXT4 | Unallocated right? Have a look at df again see if vold/179:1 appears, have attached mine from PA
thank you!
HypoTurtle said:
Can't imagine that would cause the issue, you have them layed out as Fat32 | EXT4 | Unallocated right? Have a look at df again see if vold/179:1 appears, have attached mine from PA
Click to expand...
Click to collapse
so thats how you see if it's called mmcblk0p2 or not.... finally. i never used it to set these up. is it too late? i don't even know how to get adb on my phone like you did, and i tried running adb shell from my computer but it keeps saying error: device not found.
how do i get it running on my phone as you did to check?
noobinius said:
so thats how you see if it's called mmcblk0p2 or not.... finally. i never used it to set these up. is it too late? i don't even know how to get adb on my phone like you did, and i tried running adb shell from my computer but it keeps saying error: device not found.
how do i get it running on my phone as you did to check?
Click to expand...
Click to collapse
Use terminal emulator, type su to get to shell then df (or anyother busybox/adb shell command)
thank you!
HypoTurtle said:
Use terminal emulator, type su to get to shell then df (or anyother busybox/adb shell command)
Click to expand...
Click to collapse
ahh, great. well, i got there did it, no 179 error or any other error. i tried taking a screenshot with volume down + power key, but it doesn't seem to want to do it, maybe cuz it doesn't no where to save it idk.
anywayas, it shows:
/dev/block/mmcblk0p2 /nativesd
/dev/block/mmcblk0p2 /system
/dev/block/mmcblk0p2 /data
tmpfs /dev
tmpfs /mnt/asec
tmpfs /mnt/obb
other than sizes, that is all it shows...
noobinius said:
ahh, great. well, i got there did it, no 179 error or any other error. i tried taking a screenshot with volume down + power key, but it doesn't seem to want to do it, maybe cuz it doesn't no where to save it idk.
anywayas, it shows:
/dev/block/mmcblk0p2 /nativesd
/dev/block/mmcblk0p2 /system
/dev/block/mmcblk0p2 /data
tmpfs /dev
tmpfs /mnt/asec
tmpfs /mnt/obb
other than sizes, that is all it shows...
Click to expand...
Click to collapse
Screenshot is turned on in settings, system, power menu but yea it wouldn't work anyway, other than reformating the fat partition, i can think of much else you can try, i think you may have to tempt fate here and change the wp7 part to primary, can't recall if it messes anything up at this stage, i don't think so, as long as it doesn't require a format.
THANK YOU!!!
HypoTurtle said:
Screenshot is turned on in settings, system, power menu but yea it wouldn't work anyway, other than reformating the fat partition, i can think of much else you can try, i think you may have to tempt fate here and change the wp7 part to primary, can't recall if it messes anything up at this stage, i don't think so, as long as it doesn't require a format.
Click to expand...
Click to collapse
WOW, rock on man.. you did it. reset wp7 partition to primary, both operating systems still working. and android is reading the fat32 partition now. Thank you sooo much for your help. I am thrilled we did it!!
Okay, I posted a guide on EXACTLY what I did with screenshots in an ACTUAL step by step process so it will be easier for the next person that doesn't know what they're doing just like I didn't. It is here: http://forum.xda-developers.com/showthread.php?p=31406820#post31406820
Guide
noobinius said:
thank you guys for your help. i have got it working and have made a step by step guide as i did it. just one problem, and i reaaaaallly hope its not a big problem. but in android it says no sd card. i need to know how to show whatever explorer program i use in android to look at the fat32 partition. anyone know?
i also need to know how to make wp7 see the fat32 partition that will have all the media files on it. anyone?
as soon as i get this information, i will post the guide. but i don't want to post it if there is something wrong (android and windows not reading the fat32 parition).
other than that both operating systems are still there and android is running from ext4 from folder nativesd!!!
Click to expand...
Click to collapse
PLEASE.. let us know where and how to get a hold of your NOOB Guide.. I would be very interested in it even if it all doesn't work!
TERRAREX0784 said:
PLEASE.. let us know where and how to get a hold of your NOOB Guide.. I would be very interested in it even if it all doesn't work!
Click to expand...
Click to collapse
Okay, I posted a guide on EXACTLY what I did with screenshots in an ACTUAL step by step process so it will be easier for the next person that doesn't know what they're doing just like I didn't. It is here: http://forum.xda-developers.com/show...0#post31406820
Hi, I have a Nook Simple Touch device with a traditional problem of improper backup of 76 MB before rooting.
Now I have managed to retrieve files from the /rom partition (/devconf folder with 20 files like serial no, public key etc.) - I have them in my laptop as regular files as well as 16 MB partition image on SD card.
Would anybody be so kind to offer a full recovery method? I believe backup of somebody's full image and then overwriting the /rom partition would revive the device?
How much of your partition table is left, if any, and how familiar are you with linux?
Were it me, I might have a go at creating just the first partition - boot from noogie, connect to a linux box, and use fdisk to create the partition.
I'd then try doing a
dd if=single.partition.backup.img of=/dev/mmcblk0p1
(writing my boot backup to the partition I just created) and see if that file wasn't enough to bootstrap the other partitions. Depending on how you created the backup, you may have the boot flag set and the partition table stored; so long as you haven't actually put data on the other partitions yet, it may be possible to at least trigger the onboard restore.
These are values that work on the glow, and I believe on the touch as well:
Disk /dev/block/mmcblk0: 2000 MB, 2000683008 bytes
128 heads, 32 sectors/track, 954 cylinders
Units = cylinders of 4096 * 512 = 2097152 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 38 77808 c Win95 FAT32 (LB
A)
Of the partitions, I still have:
- boot (I believe it is somewhat corrupted, but this I can restore from the backup)
- NOOK (FAT32) - should be OK, I see files in it;
- cache (Ext3)
- data (Ext3) - seems to be corrupted
Missing: factory (Ext2); one untitled partition and one unallocated segment.
Backup was created with Roadkil's DiskImage, with a source being the locigal drive (original boot partition).
I'm not good at Linux, but I know how to create partitions using Windows tools.
OK, I can try to recreate the boot partition and the rom partition, and restore the backup to it, then I'll see what happens.
Disk configuration for NST is different from the NSTG:
Cylinters: 238 Heads: 255 Sectors: 63
Nook is resurected!
Yes, I have managed to revive the Nook Simple Touch who had survived deletion of all partitions and restore of just the boot partition!
You will need for this:
- an micro SD card and card reader;
- Noogie;
- Minitool Partition Wizard (or other partition management software, if you like and it can do partition recovery and copying);
- ClockworkMod (sd_2gb_clockwork-rc2.zip)
- Alpha-FormatTouch-2.zip - to be copied onto ClockworkMod SD card;
The principle is this:
- first of all, do a PROPER backup of your device - backup ENTIRE PHYSICAL DISK (2 GB) into the image file.
- Using Minitool Partition Wizard, do a partition recovery operation - you should find all your deleted partitions - but do not apply changes yet!. However, due to improper restore of logical disk to a physical disk, the disk config info probably became corrupted and disk size appears to be 78MB, so you won't be able really restore the partitions. So, using Minitool Partition Wizard, do a copy of the recovered partitions one by one onto the SD card - and start with the most important rom partition. From Partion Wizard, you should be able, using Explore function, to check if the partition has all necessary files (20) like serial no, public key, mac address etc.
- from SD card, you can create a backup image of each partition on your hard disk.
- after you have copies of all necessary partitions (boot, rom, nook are vital; others are optional), you need to do a wipe on the NOOK disk to delete all partitions and the disk to obtain the original size of 2 GB.
- on an empty disk after wipe, you have to restore the partitions in the order:
1. restore, by copying using Minitool Partition Wizard, the boot partition (78 MB, FAT32, Primary, set it Active)
2. restore, by copying using Minitool Partition Wizard, the rom partition (16 MB, FAT32, Primary)
3. create manually new partition factory (190 MB, Ext2, Primary)
4. create manually new partition (no label) (288 MB, Ext2, Logical)
5. copy from backup partition NOOK (240 MB, FAT32, Logical)
6. create manually new partition cache (Ext3, 240 MB, Logical)
7. create manually new partition data (Ext3, 801 MB, Logical).
Then, boot the Nook from ClockWorkMod SD card, and format /system, /cache, /data partitions;
afterwards, install from zip card - Alpha-FormatTouch-2.zip.
And, hopefully, your Nook will be alive again!
(Now, I'm sure, you won't forget to do a proper backup of your working Nook :fingers-crossed
Yes, you save my nook. Thanks to your method i could revived my /rom.
but all is not done for me . i have a UK NST Glow and the glow is not working. I would like to update to firmware1.2 and may be this glow will function again. But When i plug the usb, windows cann see the drive but i don't have access to it. i have the message "please insert disc in F: drive"
wow wow wow . At last i successed to update to FW 1.2 for my almost bricked UK NSTGL. Now i have a US NSTGL but nevermind. now time to backup correctly.
but i'm not sure your method is fully working. I had to make a partition table with renater script "nookparted.sh" and then use roustabout's comment "dd if=boot.img of=....". and after that i put update 1.2.
In one week i have learn so much with my broken backup.
Hello, new here so hope it's ok to hijack this thread slightly, seems the original issue has been solved and I think my problem is similar although I'm way out of my depth here... I've managed to brick my nook, and although I took a backup which is AFAIK correctly sized 1.86gb I can't restore it. I've tried putting noogie and cmw on the sd card but it's refusing to boot, I suspect I nonced the partition table up and can't even get the nook to register when I plug it in to the PC now. I suspect is obvious I'm a dumb noob but if anyone could help point me in the right direction it would be much appreciated
welcome to the brave new world of the "bricked forever" and endless nights.
Nobody blames you since everybody and their mothers seem to fall into the trap even if they are told to make a good backup.
i had read so much threads to resurect my nook that i don't exactly know how i made it through, but here are some indications:
Here are the objectives:
1) make a correct backup of your bricked nook: -> you can make after all stupid commands and you 'll come back to this point.
2) you'll have to resurect your /rom or your rombackup.zip (inside factory).
3) have the correct partition of your nook
4) reinstall the rom
for 2) this thread gives a way to get back your /rom. read carefully even roustabout's comment can really help
for 3) thanks to Renate NST in this http://forum.xda-developers.com/showthread.php?t=1805936&highlight=to+stock and her script "nookpart.sh" i could have a correct size for my partition. (method with wizard partition gives wrong cylinders alignement). read all of this thread it is really rich.
for 4) if you reach that point that should be easy.
Thanks for the welcome and the reply jjinkou2.
I'm guessing I need to work on the nook through a PC. I've currently got 2 PCs, one running window 7 and one on vista, I'm mainly working on the W7 machine. When I plug the nook in to it, a device briefly shows up as the h: drive in My computer but then immediately disappears and so I can't actually access it yet. I note that roustabout mentions working in Linux, if I had a Linux machine available would it be easier to get it to recognize the nook?
Edit: Just tried plugging the nook into my vista machine (which it has not been used on before) and the Found New Hardware window briefly pops up but then vanishes and I get a message on the taskbar: Device driver software was not successfully installed - OMAO3630 Device unplugged. Is there a fix for this pelase?
Some easy instructions here http://forum.xda-developers.com/wiki/BN_Nook_Simple_Touch/Installing_ADB
you'll need to install android sdk and check usb install in the extra.
Search for a file named "ADB + Fastboot + Drivers.zip" in the forum to easily have the adb.
With windows the usbdriver can be tricky to install. i had to use usbdview (look for it in google) and uninstall all B&N mass storage and OMAP3630.
The driver for usb inside the previous zip might not work also. i found one in the forum but can't find it right now.
Edit
found the usb driver that worked for me
http://forum.xda-developers.com/showthread.php?t=1125094
Excellent, thanks very much! Not entirely sure how I managed it but I managed to get to a point where I could use the method shown by budriunas and my nook is now working again, albeit with an older firmware and the glow light isn't working but at least it's not bricked! Now just to get the light working and then root the damn thing without killing it....
budriunas said:
Yes, I have managed to revive the Nook Simple Touch who had survived deletion of all partitions and restore of just the boot partition!
You will need for this:
- an micro SD card and card reader;
- Noogie;
- Minitool Partition Wizard (or other partition management software, if you like and it can do partition recovery and copying);
- ClockworkMod (sd_2gb_clockwork-rc2.zip)
- Alpha-FormatTouch-2.zip - to be copied onto ClockworkMod SD card;
The principle is this:
- first of all, do a PROPER backup of your device - backup ENTIRE PHYSICAL DISK (2 GB) into the image file.
- Using Minitool Partition Wizard, do a partition recovery operation - you should find all your deleted partitions - but do not apply changes yet!. However, due to improper restore of logical disk to a physical disk, the disk config info probably became corrupted and disk size appears to be 78MB, so you won't be able really restore the partitions. So, using Minitool Partition Wizard, do a copy of the recovered partitions one by one onto the SD card - and start with the most important rom partition. From Partion Wizard, you should be able, using Explore function, to check if the partition has all necessary files (20) like serial no, public key, mac address etc.
- from SD card, you can create a backup image of each partition on your hard disk.
- after you have copies of all necessary partitions (boot, rom, nook are vital; others are optional), you need to do a wipe on the NOOK disk to delete all partitions and the disk to obtain the original size of 2 GB.
- on an empty disk after wipe, you have to restore the partitions in the order:
1. restore, by copying using Minitool Partition Wizard, the boot partition (78 MB, FAT32, Primary, set it Active)
2. restore, by copying using Minitool Partition Wizard, the rom partition (16 MB, FAT32, Primary)
3. create manually new partition factory (190 MB, Ext2, Primary)
4. create manually new partition (no label) (288 MB, Ext2, Logical)
5. copy from backup partition NOOK (240 MB, FAT32, Logical)
6. create manually new partition cache (Ext3, 240 MB, Logical)
7. create manually new partition data (Ext3, 801 MB, Logical).
Then, boot the Nook from ClockWorkMod SD card, and format /system, /cache, /data partitions;
afterwards, install from zip card - Alpha-FormatTouch-2.zip.
And, hopefully, your Nook will be alive again!
(Now, I'm sure, you won't forget to do a proper backup of your working Nook :fingers-crossed
Click to expand...
Click to collapse
Thank you so much. My nook is back. I described my work in http://forum.xda-developers.com/showthread.php?p=34746242#post34746242.
jjinkou2 said:
wow wow wow . At last i successed to update to FW 1.2 for my almost bricked UK NSTGL. Now i have a US NSTGL but nevermind. now time to backup correctly.
but i'm not sure your method is fully working. I had to make a partition table with renater script "nookparted.sh" and then use roustabout's comment "dd if=boot.img of=....". and after that i put update 1.2.
In one week i have learn so much with my broken backup.
Click to expand...
Click to collapse
how did you do a partition table?? i have run nookpart.sh but i still get the problem : "When i plug the usb, windows cann see the drive but i don't have access to it. i have the message "please insert disc in F: drive"
nookpart.sh will partition the internal memory exactly like it was.
This is important if you actually still have valid data but the partition table was destroyed.
If partitions are not looking correctly they may need to be formatted.
Don't be too quick to repartition/reformat until you know what the situation is.
i have used nookpart.sh but still no good, here is the result when i execute nookpart.sh. Everything works except internal storage not mounted correctly i think, i want to update to 1.2
edit: see my thread http://forum.xda-developers.com/showthread.php?p=48015536#post48015536 for more details