This is a long thread because I'm trying to provide the maximum detail possible in the hopes of luring some experts to assist. I am a developer with 30+ years experience, though with little *nix experience, since I hitched my wagon to WinTel when people stopped hiring assembly programmers and the term "GUI" began appearing in help wanted ads.
Yesterday, based upon my experience with one phone that I successfully upgraded to CM6-RC1 and another one that failed, I posted a new thread in the G1 General section, which was probably the wrong place for it. Both phones are US TMo G1's purchased within a few days of each other, around December 2009.
During the subsequent 12 hours I read everything I could find about the dreaded "E: Can't find MISC: / (No space left on device)" problem, which I eventually determined was preventing me from proceeding further.
I found many, many examples of people on all types of hardware who were (and many still are) stuck with a hosed-up misc with no idea how to proceed. This was somewhat alarming to me.
I found a few people who were apparently able to fix it by simply doing a flash_image of a misc.img copied from elsewhere. I found a few who seemed to have fixed it with dd. I found others who went through various combinations of installing other things until the problem mysteriously vanished. I found great info about what the misc partition is and how it's used.
What I did not find is:
(a) any clear explanation of how it gets hosed in the first place,
(b) any clear explanation of how to troubleshoot it,
and most importantly (c) any clear explanation of ways to fix it.
This thread is a request for an expert to step in and fill those gaps. Maybe if we can get some "misc lore" in a single place, other people who encounter the problem won't be left hanging.
So first the back story:
Two days ago I decided to install CM6-RC1 on my own G1. It went very smoothly. I was already on Cupcake, so I formatted the card, downgraded back to RC29, I installed Cupcake, formatted again from the phone, used flashrec to install RA 1.7 (which is amazing, by the way; I may be a n00b to phone-guts but that is already apparent), verified the radio version, installed DangerSPL, installed CM6-RC1, and installed the Google Apps. Flawless process.
Loved it. CM6 is great. So the next morning I had my wife leave her phone at home with me. I had seen a thread which led me to believe that the card didn't necessarily have to be formatted twice. I was under the impression I could format it once and drop all the files out there -- only Cupcake needed to be named update.zip for the process outlined above.
So I connected her phone to my laptop, reformatted to FAT32 over USB from Win7, copied all 211 MB of files over, disconnected and went into flashboot. The RC29 downgrade worked fine. I restarted and logged in just to be sure RC29 was on there. I powered off and restarted in recovery mode -- and the misc problem was already there.
In the stock /!\ recovery screen, ALT+L showed the misc error. I couldn't remember if I had seen that previously (having only done this once before), so I hit ALT+S and hoped for the best. The progress bar went about halfway then bombed on an assert in line 4. And that's as far as I got updating my wife's phone: in theory my story could stop here, but being a lifelong geek-type, I decided to forge ahead. I didn't yet know the importance of misc or even recognize it as my main problem, so bear with me.
I rebooted and rooted via telnet and used flashrec to install RA, and tried installing Cupcake that way. I get a different error from RA: No signature, verification failed. I thought I might have a bad file, somehow, despite having used the same update.zip that went into my G1 just fine, so I downloaded it again from megaupload. Then I downloaded the other one named signed-kila-ota. Then I did a file compare and confirmed they're identical. That won't load through RA. Not sure what's up with that.
But after thinking about it and doing more reading, I concluded I probably didn't need Cupcake for CM6-RC1, I just needed the correct radio image to support DangerSPL. So I grabbed the G1 2.22.23 radio image and tried installing that through RA. It extracts and installs ok, then dumps the Can't read Misc error, then tells me to reboot to complete. So I reboot -- and it goes back into the running OS, of course. And then the light goes on, since I did clearly remember on my own G1 it went back into RA, not into Android.
More digging uncovers the radio/SPL thread that explains how misc is used to control reboots, and I finally clearly realize that misc is my problem. (Actually I still don't know why Cupcake won't load from RA, but I still suspect if I can just load the right radio image, it shouldn't matter.)
During the following six hours I have tried a huge variety of things to fix misc, primarily working through an adb connection.
First I tried making a nandroid backup from my working G1. Took me awhile to figure out I had to do it from the command line to force it to backup misc, then I wasted time trying to get the command line to restore that backup, then I finally made another backup on the non-working G1 and copied the "good" misc over -- and still couldn't get it to restore (kept telling me something about being the current version, which I interpreted to mean it wasn't restoring because it thought the backup already matched the live filesystem).
Again, not knowing much about *nix, at this point I was convinced misc was simply dead and gone. I know what a disk partition is, but I didn't see misc (or the others like recovery) in parted, so I don't think I even understand what it means to say misc is a partition. But I didn't see it anywhere, so I thought it had been erased or overwritten or something along those lines.
Then I ran across a thread in which someone suggested doing a "cat /proc/mtd" which yielded the following:
Code:
dev: size erasesize name
mtd0: 00040000 00020000 "misc"
mtd1: 00500000 00020000 "recovery"
mtd2: 00280000 00020000 "boot"
mtd3: 04380000 00020000 "system"
mtd4: 04380000 00020000 "cache"
mtd5: 04ac0000 00020000 "userdata"
I don't know what it means, but at least I see the system still knows something about misc.
Someone else asked for "dump_image misc /dev/zero" for diagnostic purposes, which yields:
Code:
mtd: ECC errors (0 soft, 1 hard) at 0x00000000
mtd: ECC errors (0 soft, 1 hard) at 0x00020000
Someone suggested "cat /dev/zero > /dev/mtd/mtd0" which results in the error message "cat: write error: No space left on device".
I tried copying misc.img out of the backup folder to the sdcard root and doing "flash_image misc /sdcard/misc.img" and was rewarded with the following lines which I can't interpret, although they're clearly related to the output shown above (I assume flash_image is probably a script or something, which is just doing those same steps internally?):
Code:
mtd: ECC errors (0 soft, 1 hard) at 0x00000000
mtd: ECC errors (0 soft, 1 hard) at 0x00020000
mtd: erase failure at 0x00000000 (I/O error)
mtd: erase failure at 0x00000000 (I/O error)
mtd: skipping write block at 0x00000000
error writing misc: No space left on device
I ran across another thread which suggested the command "dd if=/sdcard/misc.img of=/dev/block/mtd0"... that produced this initially encouraging-looking output, though I don't know what it means and it didn't fix misc:
Code:
512+0 records in
512+0 records out
I also saw a few steps and suggestions relating to fastboot. I didn't try any of these since the only instructions I could find for setting up fastboot (in that stickied noob thread) requires a version 2 radio image, which I can't install because misc is fried.
So, in short, searching xda and the Internet in general hasn't helped much, except perhaps to better prepare me to follow somebody else's instructions . In reality I have gone through several different sets of instructions multiple times and tried a variety of other things, but it always comes back to not being able to complete a radio image installation because of that problem with misc.
I'm willing to try just about anything... and I know there are quite a few others out there with a misc problem who can't seem to make any progress or get any input, so hopefully my exhaustive description of how I got here and what I've tried already will be useful to one of the local experts.
I know that ECC refers to the error correction checksum used to detect memory errors... but I find it awfully suspicious that the two supposed ECC errors fall on the very first and last slots on the misc range -- particularly since everybody else with this problem who posts the results of attempts to troubleshoot it or fix it reports exactly the same thing.
In other words, I assume the error message is wrong. This is pretty much the only reason I don't just conclude that the memory is actually hosed and go shopping for a new phone.
Oh, and... bump.
You are certainly telling the truth about it being quite long. That fact does, unfortunately, make it somewhat difficult to read.
I assume that you've seen a few of ezterry's and/or my own posts about the partitions, which is probably where you saw the info on the misc partition.
In any case, the misc partition isn't a "filesystem" partition as you are familiar with. It is actually just a simple data structure. In fact, only the system, cache, and userdata partitions are actually filesystem partitions, and the cache partition is only a filesystem partition part of the time -- during radio and spl updates, it also is used as a simple data structure with a header field and a payload field. That, along with the misc partition, instructs the SPL to perform a radio or spl update.
Now there is a possibility that it may be possible to salvage the device without a working misc partition. Specifically, the requirement is that you get yourself a high-engineering SPL (one with the ability to fastboot a radio image -- note: it is FAST boot, not flashboot).
One important thing to note that might make things easier is that an error "finding" the misc partition *might not imply a failed misc partition*. It could possibly be a failed CACHE partition. Have you tried FORMATTING your cache partition?
In any case, you are no doubt really wondering about my statement that you might be able to update the SPL without the use of a misc partition.... Read THIS thread and you will see how the partition tables are defined and how they can be overridden. This suggests a way that you can actually DEFINE the SPL partition to the linux kernel, which in turn, should allow you to flash_image an SPL update. What you need to do is determine the starting offset and length of the SPL partition, and define it along with the rest of the partitions on the kernel command line. Once this is done, you should be able to fastboot flash a radio update to the device.
Note: Having just done an RC29 NBH file, there is PRECISELY ONE high-engineering SPL that you can install to the device safely.... 1.33.2003 (ending with a THREE -- very important, a 5 is a brick when combined with an rc29's radio).
Also note: I don't take any responsibility if you fry it completely trying this idiotic procedure without a jtag standing by. It is quite risky. I suggest it because it may be your best chance of getting through this.
Note: fastboot does NOT require a 2.x radio image. Fastboot requires an engineering SPL, which for the same reason, you can't install.
Now as for the location of the read/write errors.... you think that it is suspicious that they occur at the first and last slot of the memory range...
Well this is not unexpected since there are only two slots. Each of 128 kB. The first at 0 offset wrt the start, the second at 20000 offset wrt the start. The ECC error itself says that each of the two blocks has failed whatever operation it was trying to perform.
I suggest that your first step might be to try again writing the RC29 NBH file.
Thank you for the explanations and all the details.
I have actually reloaded RC29 quite a few times. I followed the directions from scratch a couple times in case I had gotten something wrong (of course, this was easy to do since I get stuck pretty early in the process).
I'll try formatting CACHE and I'll take a look at using the SPL you reference and report back later.
I really appreciate the assistance.
Ah, just realized that when you do "Wipe cache" from RA recovery, formatting cache is the second step. Since that is immediately followed by another "Can't read MISC" error message, I guess formatting doesn't fix my misc issue.
In this paragraph:
In any case, you are no doubt really wondering about my statement that you might be able to update the SPL without the use of a misc partition.... Read THIS thread and you will see how the partition tables are defined and how they can be overridden.
Click to expand...
Click to collapse
Your "THIS" didn't link to anything. I'll go search for what you're referring to, since this would appear to be my only remaining solution. No JTAG handy, but if someone of your experience thinks this is probably my last-ditch option, I don't have much to lose anyway, right? I'll take it slowly.
Edit: I think this is it? forum.xda-developers.com/showthread.php?t=704560 Pretty clever... crazy and dangerous, sure, but what the hell, it's just a phone, lol...
Again, thanks for taking the time to help out.
MV10 said:
Ah, just realized that when you do "Wipe cache" from RA recovery, formatting cache is the second step. Since that is immediately followed by another "Can't read MISC" error message, I guess formatting doesn't fix my misc issue.
In this paragraph:
Your "THIS" didn't link to anything. I'll go search for what you're referring to, since this would appear to be my only remaining solution. No JTAG handy, but if someone of your experience thinks this is probably my last-ditch option, I don't have much to lose anyway, right? I'll take it slowly.
Edit: I think this is it? forum.xda-developers.com/showthread.php?t=704560 Pretty clever... crazy and dangerous, sure, but what the hell, it's just a phone, lol...
Again, thanks for taking the time to help out.
Click to expand...
Click to collapse
Before re-writing partitions find a recovery with 'erase_image' (I hear tell clockwork has it) install and try:
erase_image misc
then
flash_image misc <misc.img>
where misc.img is an old nandroid backup from a phone of the same region as your own (least its preferable its the same region your CID is in the structure)
It may correct the issue... if not we can try to flash an engineering SPL via flash_image..
I feel this is very safe in theory (as we don't have to worry about boot mode 3.. thus if a valid SPL is flashed you won't completely brick).. However we have no safeguards at this point in time so be careful that you really understand what is going on.. else you will write garbage to the SPL, and there is no helping that w/o JTAG.
(btw.. the SPL .. even the full engineering ones like 1.33.2003 and 1.33.2005 wont actually let you erase misc.. but will let you flash it)
Thank you, I'll try it later today.
Not that it's relevant to getting me fixed, probably, but no idea how/why this problem crops up? Or is it more a case of an error that can have multiple causes? I found it interesting that so many people were reporting it across the various Android forums, and there seemed to be no attempt to explain it. That kind of thing always makes me curious, particularly in an environment like this -- a room full of curious "dig in and figure it out" personalities...
If it ever happened to me, I would certainly try to figure it out, however this is really difficult since it has never happened to me. I don't think that it is anywhere near as common as you think.
What I believe about the situation at the moment is that it is *probably* a failure somewhere else along the line that simply has this SIDE EFFECT.
ezterry: Do you remember which memory address ranges are written by an nbh file? I recall that the nbh file has divisions for the different partitions, so I suspect that it may not write *everything*. Maybe misc and/or cache are not written?
Note: I have seen plenty of instances of the cache partition getting borked and having weird side-effect. The problem with the cache partition and why IT gets into weird states is that it is a dual-purpose partition -- sometimes a yaffs2 filesystem, sometimes a simple data structure, so if it gets into the data structure mode and something tries to use it as a filesystem, you end up with some interesting side-effects.
lbcoder said:
ezterry: Do you remember which memory address ranges are written by an nbh file? I recall that the nbh file has divisions for the different partitions, so I suspect that it may not write *everything*. Maybe misc and/or cache are not written?
Click to expand...
Click to collapse
The nbh is just a custom archive the header has 3 arrays of 32bit indicating the following for each partition included
> Partition type (this determines the partition via some mapping to flash radio,hboot,misc,cache,recovery,boot,system,splash1,diag)
> Partition offset from start of the nbh file (signature removed if included)
> size of image
The diagnostic nbh only has the fake 'diag' image.. however most others in the wild seem to have radio, hboot, splash1, recovery, system, cache, userdata...
I don't think I've seen one with misc.
Certainly none of my current collection have it. I Wonder if they allow it?
Clockwork's "erase_image misc" returns an error:
mtd: erase failure at 0x00000000
I also tried wiping and formatting the cache again, on the off chance that maybe clockwork did something differently. Nothing new to report there.
As for this kernel partition approach, do I correctly understand that I would be telling the kernel to create a new partition name mapped to a range which precedes misc where the SPL is located? I assume I can derive the size from an img of the stock SPL of the same version. Any tips on how I can figure out where it starts? (Apologies if it's in that thread Ibcoder referenced, I haven't finished reading it yet.)
Or am I thinking about this completely wrong?
Search for my post with the kernel command line with hboot replacing userdata.. it deliberately is not step by step but has the info needed.
On a somewhat peripherally-related note, I see in this post in the De-bricking thread:
forum.xda-developers.com/showpost.php?p=7072492&postcount=195
Ibcoder writes: 3) This person goes to boot to the recovery by issuing a "reboot recovery", which sets the command field of the MISC partition to boot-recovery and reboots.
Earlier I had thought about asking whether "reboot recovery" writes to MISC, since I issued that command from the RA console yesterday and to my surprise it worked. I figured I must have misunderstood something and maybe reboot recovery used some mechanism other than writing to MISC, but now I've run across the comment above.
Wouldn't that boot mode flag be the same thing recovery should use to finish installing a radio image?
ezterry, is this the post you're referring to?
forum.xda-developers.com/showpost.php?p=7064255&postcount=187
MV10 said:
On a somewhat peripherally-related note, I see in this post in the De-bricking thread:
forum.xda-developers.com/showpost.php?p=7072492&postcount=195
Ibcoder writes: 3) This person goes to boot to the recovery by issuing a "reboot recovery", which sets the command field of the MISC partition to boot-recovery and reboots.
Earlier I had thought about asking whether "reboot recovery" writes to MISC, since I issued that command from the RA console yesterday and to my surprise it worked. I figured I must have misunderstood something and maybe reboot recovery used some mechanism other than writing to MISC, but now I've run across the comment above.
Wouldn't that boot mode flag be the same thing recovery should use to finish installing a radio image?
ezterry, is this the post you're referring to?
forum.xda-developers.com/showpost.php?p=7064255&postcount=187
Click to expand...
Click to collapse
Suggesting, of course, that the misc partition itself is actually quite fine, but whatever subsystems responsible for screwing up when it screws up for you are in some other way broken.... which is not inconsistent with the theories I have presented above. Specifically, I am still quite concerned about your cache partition being somehow defective since it is known for having weird side-effects.
What you may possibly be able to do is hack the reboot command into "reboot flash-hboot"... be ***absolutely certain*** that you get your cache partition set up correctly and fully verified before you do this though, otherwise you WILL need jtag to fix it.
Later I wondered whether reboot had options to specify the flashing modes. I take it from your response that it does not. Given my meager relevant knowledge, significant hand-holding would probably be required to pull that one off!
Another oddity I have noticed: my own G1 shows a device ID of HT91CGZ02056 (through something like "adb devices" for example)... but my wife's G1 (with the MISC issue, or whatever it is) just returns a string of zeros: 000000000000. First noticed that in the nandroid backup directory name.
Not sure if that tells anyone anything useful or interesting, but it sure seems weird.
MV10 said:
Another oddity I have noticed: my own G1 shows a device ID of HT91CGZ02056 (through something like "adb devices" for example)... but my wife's G1 (with the MISC issue, or whatever it is) just returns a string of zeros: 000000000000. First noticed that in the nandroid backup directory name.
Not sure if that tells anyone anything useful or interesting, but it sure seems weird.
Click to expand...
Click to collapse
It could mean that there is a serious defect.... or it could be the same glitch that is causing you problems with misc. Remember that the device ID is stored within the same chip as the misc partition, just at a non-writeable address.
Ha, interesting, I didn't know there was any sort of relationship there. Very interesting.
Well, at this point my wife is freaking out without a phone so I'm just buying her a Galaxy S (yeah I know, Samsung... but frickin' T-Mo doesn't have anything else particularly compelling).
I'm sort of interested in what's wrong with her G1 and I have an unhealthy urge to keep fiddling with it, but honestly I can't justify spending much more time on it right now, too many other things going on in my non-phone-based life.
That means I have a thoroughly unexciting RC29 G1. I assume OTA updates aren't likely to work either (assuming they're still sent out). If either you or ezterry would have any interest in this device (maybe some questions about what went wrong since you haven't seen a MISC failure?), shoot me a PM, I'll see about shipping it off to one of you.
Regardless, I can't express how much I appreciate both of your attempts to help a complete stranger, and I look forward to reading about all the other weird and interesting stuff you guys dig up in the future...
I have had my Nook Color rooted for about 3 weeks and have been enjoying it.
But today things started to mess up.... A LOT.
I use my Nook Color in school for reading books and playing Angry Birds when the teacher's not looking, and throughout the day the UI was getting more and more sluggish.
And so, a few hours ago I decided to turn it off and then back on.
After it cut off I let it sit for about 10 mins before trying to boot it back up.
Now, for some reason it just wouldnt.
After fiddling with it a bit I discovered that if I took the SD card out then it would power up, but then freeze at the "touch the future of reading" screen.
But if I put the SD card in and hooked the machine up to my computer it froze at the "n" screen.
Knowing that I probably needed to do the factory reset I plugged it in and turned it off 8 times and that got me to be able to open Clockworld Recovery v3.0.0.5
I scrolled down to the "wipe data/factory reset" option.
Here is what i got:
-- Wiping data...
Formatting /data...
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/ .android_secure...
E:failed to mount /sdcard (No such file or directory)
Error mounting /sdcard/ .android_secure!
Skipping format...
Data wipe complete.
E:Can't mount /cache/recovery/log
E:Cant open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Even after the factory reset or whatever that was it still wont boot all the way up.
So yeah... Is there anything I can do to save my Nook Color? Or is it ruined?
Back up the data on your SD and format it.
If you can still get into CWR, that means you can use adb. Try my method to restore to stock without adb by flashing a zip or snowfox's method with dd and boot img. Both threads are in dev.
Sent from my HTC Desire using XDA App
samuelhalff said:
If you can still get into CWR, that means you can use adb. Try my method to restore to stock without adb by flashing a zip or snowfox's method with dd and boot img. Both threads are in dev.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Can You give me a set of instructions or something? I am VERY new and I'll probably end up making it worse.
Find snowfox's thread in dev, top 15. You will need adb..there are instructions there..
Sent from my HTC Desire using XDA App
Oddly enough a similar thing happened to me while searching and watching Youtube videos.
The longer I searched and watched videos the slower the whole thing got.
Eventually I got a black unresponsive screen.
After I was able to get back to task killer and killed everything, it still made no difference, the entire tablet was so slow it was unusable.
Did a restart and then the touch screen no longer worked.
Did another restart and everything is working fine again so far.
Not as bad as your situation, but it seems like there is a memory leak somewhere..
I powered it up this morning and left in on while I was at school all day, and it still says "Touch the Future of reading"
I'm getting depressed.
***UPDATE***
Thanks at all of you who are trying to help, but now it wont even boot up past the "Touch the Future of Reading" screen.
Also, when I hook it up to my PC it does this:
When SD is removed:
It says "new hardware found" and Then it says "Found new hardware" "RDNIS/Ethernet Gadget"
If I go to My Computer it shows no new drives.
Can anyone explain this?
I have discovered that if I plug it in without the SD card in, let the computer say "found new hardware", then hold power and the n button for about 15-20 seconds it boots to the n logo screen but then just sits there. My PC also recognizes 2 new drives "Removable Disk I:" and "Removeable Disk J:" but when I try to open them it says "Please insert a disk into drive I: or J:" At least now I have access to some drives, anyone know where to go from here??
Ign3nt said:
I powered it up this morning and left in on while I was at school all day, and it still says "Touch the Future of reading"
I'm getting depressed.
Click to expand...
Click to collapse
I'm not exactly 100 percent positive on this but It's supposed to wipe itself back to stock on the 8th failed boot. Have you tried it eight times yet?
vap0rxt said:
I'm not exactly 100 percent positive on this but It's supposed to wipe itself back to stock on the 8th failed boot. Have you tried it eight times yet?
Click to expand...
Click to collapse
It won't with Clockwork installed. I would try the restore image from the developers forum
This happened to me and this is what I did.
My NC was also getting stuck on the touch the future or reading screen. I tried rebooting it several times and it still didn't work. However, I did do this and it worked so give it a try:
1. Make sure your NC is off.
2. Plug it into a computer.
3. Hold down the n and the power button for about 20 seconds.
4. When the ghetto menu shows up, select the first option to reboot.
5. Wait a while for it to boot. It will stay at the touch the future of reading screen for a while, but don't give up; it will boot up fully.
6. Try again if it stays at the touch the future screen for more than 1 minute.
7. If it still doesn't work. try something else
I did this before doing anything more dramatic and it booted right up.
Thanks zen5200 - those steps worked perfectly for me.
Time for some words of wisdom:
If you can't fix something your messing with, then don't mess with it.
I recently aquired a Streak 7 and am having trouble resetting it since it has all the original owners info on it.
1. I encountered a force close error upon first boot.
- android.process.acore stopped unexpectedly
2. After this error continued to appear I said F*** this and rebooted into the Stock Dell recovery(Volume + and Power)
I chose option 3 for a factory reset and erase internal tablet storage.
Rebooted and Bam same bull**** errors. I did this 3 more times powering off with the pin hole off button after the streak kept booting with this error.
I read this entire forum development and general questions to see what problems others are having, I came across a few threads all very informative on how to attempt to restore your Streak 7.
Before attempting the various methods of either NVFlash, the fastboot method and even flashing clockwork recovery through fastboot I figured I would see what I could get the Streak to do in it's current state.
*Note* I am very familiar with ADB and Fastboot but if I over looked something I will not be offended if anyone can provide some useful information.
OK, Here is my story
I put the streak on my HDMI dock and was able to succefully install the ADB drivers on Windows 7 x64. From there I launched the ADB Shell
c:/androidsdk/tools> adb shell
$
once in the shell i found I could launch the android setting using this command
$ am start -a android.intent.action.MAIN -n com.android.settings/.Settings
Once in the settings and periodically hitting forceclose and quit to the .acore error I was able to retrieve this information
Android Version
2.2
Baseband Version
11.809.05.02.00
Kernel version
2.6.32.9
OEM Version
GLUNB1A132433
Build Number
14394
I also realized that I can install apps through adb so I went and installed the latest standalone ADW Launcher which installs fine and allows me to actually use the device a little.
c:\androidsdk\tools>adb install launcher.apk
1307 KB/s (2533717 bytes in 1.892s)
pkg: /data/local/tmp/launcher.apk
Success
You will notice that apps install to this location
/data/local/TMP
it turns out that even installing the new launcher won't allow me to do much because the previose owner changed his google password so I have no market acces or anything like that.
I then tried doing the factory reset within the Android settings>privacy>factory data reset.
The device reboots and I again encounter the same error and the device has also not reset the user data.
So i rooted the device and found that even root was only temporary, the ADB shell returns the # sign indicating that it has root, great but when the device is rebooted it returns to the condition I got it in.
If I run ADB remount with root I get this
c:\androidsdk\tools>adb remount
remount failed: Operation not permitted
c:\androidsdk\tools>
this tells me that even though the phone has root it will not mount any file system with read/write permissions
I then installed the latest free Clockwork Rom Manger via ADB
it prompts me for root permissions I select allow and then the app closes after it downloads and tries to write the clockwork recovery image. I said fine this won't work.
I moved on to the Flashing Clockwork Recovery via Fastboot
In Fastboot I get this
c:\androidsdk\tools>fastboot devices
? fastboot
c:\androidsdk\tools>fastboot -i 0x413C flash recovery clockwork.img
sending 'recovery' (4416 KB)...
OKAY [ 0.560s]
writing 'recovery'...
OKAY [ 0.110s]
finished. total time: 0.670s
c:\androidsdk\tools>
WOW I didn't know that 4MB could be sent and flashed over usb in under a second!!!! WTF!!!!!
So obviously there is something going on here where I cannot write to the internal memory...
I decided to just use NVFlash because people seem to be having luck with it
http://forum.xda-developers.com/showthread.php?t=1018809
I Didn't.......
I spent a hell of a lot of time downloading and redownloading the different images and finally got them all downloaded successfully. I run the restore.bat file and it says everything went fine but it didn't, I tried NVFlash with and without P14.img and it just doesn't seem to do anything it always restores it to how it was when i got it errors and all.
Now for the best method I tried, the fastboot method by flashing boot_orig.img, recovery_orig.img and system_orig.img
http://forum.xda-developers.com/showthread.php?t=1011654
Flash_image is not and ADB Shell command
and I also don't beleive the images are writing to the disc that fast.
I'm tired of typing now so please if anyone has any info on how I can write information to the internal ROM memory not the internal sd card I would greatly appreciate it.
Tom
wikedbubble said:
I recently aquired a Streak 7 and am having trouble resetting it since it has all the original owners info on it.
1. I encountered a force close error upon first boot.
- android.process.acore stopped unexpectedly
2. After this error continued to appear I said F*** this and rebooted into the Stock Dell recovery(Volume + and Power)
I chose option 3 for a factory reset and erase internal tablet storage.
Rebooted and Bam same bull**** errors. I did this 3 more times powering off with the pin hole off button after the streak kept booting with this error.
I read this entire forum development and general questions to see what problems others are having, I came across a few threads all very informative on how to attempt to restore your Streak 7.
Before attempting the various methods of either NVFlash, the fastboot method and even flashing clockwork recovery through fastboot I figured I would see what I could get the Streak to do in it's current state.
*Note* I am very familiar with ADB and Fastboot but if I over looked something I will not be offended if anyone can provide some useful information.
OK, Here is my story
I put the streak on my HDMI dock and was able to succefully install the ADB drivers on Windows 7 x64. From there I launched the ADB Shell
c:/androidsdk/tools> adb shell
$
once in the shell i found I could launch the android setting using this command
$ am start -a android.intent.action.MAIN -n com.android.settings/.Settings
Once in the settings and periodically hitting forceclose and quit to the .acore error I was able to retrieve this information
Android Version
2.2
Baseband Version
11.809.05.02.00
Kernel version
2.6.32.9
OEM Version
GLUNB1A132433
Build Number
14394
I also realized that I can install apps through adb so I went and installed the latest standalone ADW Launcher which installs fine and allows me to actually use the device a little.
c:\androidsdk\tools>adb install launcher.apk
1307 KB/s (2533717 bytes in 1.892s)
pkg: /data/local/tmp/launcher.apk
Success
You will notice that apps install to this location
/data/local/TMP
it turns out that even installing the new launcher won't allow me to do much because the previose owner changed his google password so I have no market acces or anything like that.
I then tried doing the factory reset within the Android settings>privacy>factory data reset.
The device reboots and I again encounter the same error and the device has also not reset the user data.
So i rooted the device and found that even root was only temporary, the ADB shell returns the # sign indicating that it has root, great but when the device is rebooted it returns to the condition I got it in.
If I run ADB remount with root I get this
c:\androidsdk\tools>adb remount
remount failed: Operation not permitted
c:\androidsdk\tools>
this tells me that even though the phone has root it will not mount any file system with read/write permissions
I then installed the latest free Clockwork Rom Manger via ADB
it prompts me for root permissions I select allow and then the app closes after it downloads and tries to write the clockwork recovery image. I said fine this won't work.
I moved on to the Flashing Clockwork Recovery via Fastboot
In Fastboot I get this
c:\androidsdk\tools>fastboot devices
? fastboot
c:\androidsdk\tools>fastboot -i 0x413C flash recovery clockwork.img
sending 'recovery' (4416 KB)...
OKAY [ 0.560s]
writing 'recovery'...
OKAY [ 0.110s]
finished. total time: 0.670s
c:\androidsdk\tools>
WOW I didn't know that 4MB could be sent and flashed over usb in under a second!!!! WTF!!!!!
So obviously there is something going on here where I cannot write to the internal memory...
I decided to just use NVFlash because people seem to be having luck with it
http://forum.xda-developers.com/showthread.php?t=1018809
I Didn't.......
I spent a hell of a lot of time downloading and redownloading the different images and finally got them all downloaded successfully. I run the restore.bat file and it says everything went fine but it didn't, I tried NVFlash with and without P14.img and it just doesn't seem to do anything it always restores it to how it was when i got it errors and all.
Now for the best method I tried, the fastboot method by flashing boot_orig.img, recovery_orig.img and system_orig.img
http://forum.xda-developers.com/showthread.php?t=1011654
Flash_image is not and ADB Shell command
and I also don't beleive the images are writing to the disc that fast.
I'm tired of typing now so please if anyone has any info on how I can write information to the internal ROM memory not the internal sd card I would greatly appreciate it.
Tom
Click to expand...
Click to collapse
Bump for a resolution. A lot of folks seem to be encountering this issue; I think it has something to do with a Linux failsafe measure (from another thread), but I'm not savvy enough in Linux to know for sure. Good luck to you!
Hey Thanks for the Bump, I am tearing my hair out over thins thing.
On another note I found this post for the LG GX2 for flashing clockwork recovery through APX with NVFLASH
http://www.techofweb.com/technology/flashing-cwm-recovery-g2x.html
I hope there might be a way to do this on the Streak, but I don't know that much about NVFlash. My hope in getting the clockwork recovery is that the restore and recovery tools used in clockwork recovery will in theory allow me to format and write roms to the internal memory...... I hope
Anyway I hope someone is reading and understanding my trouble other than Z4nd4r
Tom
I've been having similar problems with my streak7. It was working fine on stock 2.2.2 then got stuck in boot loop at the "stick together" screen.
I tried to factory reset in recovery. No change.
I tried to restore with nvflash. It completed fine, but no change.
http://forum.xda-developers.com/showthread.php?t=1018809
I tried with fastboot (boot.img, restore.img and system.img). It completed fine, no change.
I tried the 2.2.2 update.pkg in recovery, but it stops at "install modem error", no change.
I tried to flash DJ_Steve's honeycomb, and it stops at:
Formatting partition 2 BCT please wait... FAILED!
command failure: create failed (bad data)
bootloader status: partition table is required for this command (code: 8) message: nverror:0x2 (0x2) flags: 0
I tried formatting all partitions with:
nvflash --bl bootloader.bin --format_all
then restore with nvflash
It completes with no errors, but still no change.
I also tried to get clockwork on the streak 7 with fastboot. Even though I didn't get any errors, clockwork recovery did not get installed. So I'm thinking it's some sort of write protect error, since nothing I write to the device seems to be sticking.
If I format all partitions, would the streak 7 even get to the t-mobile "stick together" logo? I would think it would get stuck at the dell logo. I'm stuck at this point and have no idea what to try next. Any suggestions?
Could the problem be due to previous owner(s) trying to root the DS7 and Dell had implemented some kind of security measure to prevent rooting of the DS7?
Bump for a real solution.
I found a solution and my solution was to sell it before I threw it against a wall.
What's the common denominator, here? Were these all purchased used/3rd party?
Mine was bought new and ran great till mothers day and my sis asked to use it to post pics to facebook so I unmounted my sd and gave it to her she poped in her 32 gig sd card and got tired of waiting for the the gallery to populate and ejected the card without unmounting it and handed it back to me and said it was junk an and slow .......ever since its been stuck in read only
Ive dissasymbled it formated it flashed it factory reset it and reguardless of what I do still comes back the same as though I hadnt touched it.......even tried to short the nand chip out to clear it..........its like a cockroarch thats wounded .....it just wont finish dieing
I think we need a jtag solution. Doesn't seem like anything done with current tools will help.
I've scoured the internet and turned up nothing.
My streak 7 is collecting dust and probably going on eBay soon. To hell with Dell. This is my first Dell android device and probably my last.
Edit: found information
So I found the datasheet for the NAND chip the Streak 7 uses (http://omapworld.com/iNAND_e_MMC_4_41_IF_data_sheet_v1_0[1].pdf). Aparently the NAND has a write protect feature (temporary and permanent). Tech5 from this thread http://forum.xda-developers.com/showthread.php?t=1113264 says there's a failsafe function that locks the NAND in write protect mode. I don't have the hardware expertise to dig down and see if the system is write protecting the system by locking the chip in write protect mode. If we can somehow figure out how to disable the write protect on the chip, we may have a solution. Maybe someone with good hardware knowledge can take a look and give some feedback?
I'm having this same issue over here. I've tried NVFLASH and Fastboot and it acts like it's happening and then you reboot and get back to the same image every time. Maybe time for a call to Dell on this?
Call Dell
It looks like these Streaks are all stock and having the same problem. I tried calling dell but they wouldn't help me because the streak I got doesn't have the flap for the sd card and that is where they say the Service Tag is written. Freaking BullSh!t. Anyway if someone is willing to call dell and see what they have to say that would be awesome.
Dell is the only solution?
I had a same problem too. No matter what I do, the unit reverts back. It became Read-Only Mode. I guess it happens often enough DELL aware of this problem and the tech supports knows what to do. Only way to fix the unit at this point is ship it back.
I shipped back to Dell and Dell repaired it. Turn Around time: 1 Week.
This is my 1st post.
I do have Streak 5 and 7. I love Streak 5 and DJ Steve's ROM Rocks in Streak 5.
wikedbubble said:
It looks like these Streaks are all stock and having the same problem. I tried calling dell but they wouldn't help me because the streak I got doesn't have the flap for the sd card and that is where they say the Service Tag is written. Freaking BullSh!t. Anyway if someone is willing to call dell and see what they have to say that would be awesome.
Click to expand...
Click to collapse
Settings > About > Status > Service Tag at the bottom.
I'm on the phone with Dell right now about this as I can't find another solution and another user had to get theirs repaired. We'll see what they say.
Solution to write protect?
I was trying to copy some music to mine and got the write protect error message. I took out the micro SD card holder and it indeed was locked. Flipped the switch and back in business! Hope this helps someone!
I wonder if it is newer streaks that are doing this, because I think mine was in stock with Tmobile for a while. They had plenty of them there. They must be "Locking the bootloader" so to speak. If anyone wants to send one to a Dev maybe they can do something about it.
any luck with this any 1? =(
I had a similar issue last week, it looks to be the "Read-Only" Bug. I had to send mine back to Dell, and they just sent me a new unit.
Whatever you do, make sure your DS7 does NOT hit 0% battery, it seems to be the cause of this "Ready-Only" bug.
Hi,
I have a Nook HD+ which i run with CM13 (cm_ovation-ota-MOB30D.160422) and I've run now into a bizarre problem:
Last week, suddenly the nook started over night to get into an infinite reboot cycle where it goes throught nook start up screen, then cyanogemod universal boot loader screen followed by the pulsing cyanogemod logo. Sometimes it gets to the login screen, sometimes it reboots before but never did i manage to log in.
Trying to restore now older nandroid backups and/or flashing different ROMs and they all fail as they cannot properly update /system (restore fails as it fills up the filesystem even though i haven't resized /system and it definitely was not full at the time of backup; flashing ROM fails as it complains that after update /system did contain unexpected content.
Starting to tinkering with adb shell, i notice that any changes, e.g., adding or removing files, i do on the internal storage (be it /data or /system) seems to be reflected by ls in the same mount cycle but as soon as i umount and remount the device the state is restored to the old state! Similarly, any mkfs.* run without error on the various /dev/block/mmcblk0p* but nothing really changed if i remount the same device after that (i.e., content is not wiped and filesystem type is still what it was before). [the same happens if i try the various wipes/factory reset options in the recovery. No error but no effect].
Note this all happened regardless of recovery (CWM 6.0.4.6 / TWRP 2.8.7.5; the former via external sdcard, the latter internal to the nook). Also strangely, as i boot "normally" (and end up in the boot cycle) i can't run adb logcat as the device is listed as 'unauthorized'. Also for some operations with CWM it warns me at the end that ''root access possibly lost' and asks me whether i want to fix /system/xbin/su) [but either option i choose doesn't change the noticeable behaviour]. Lastly, the whole boot cycles and actions in recovery are very sluggish.
This almost sounds like there is a rootkit on the nook which masquerades the changes but ignores them to stay in control. However, googling i didn't immediately found any hits referring to such a rather sophisticated rootkit.
Did anybody ever see such a behaviour and/or have an idea what's happening? Any thoughts to reset the whole device?
-michael-
PS: Strike-out above part about unauthorized device for logcat: i was trying to do logcat from a device which apparently i've never used before for the nook; doing it on another one which i've previously used allowed for logcat to work but the log itself didn't really give any insights and the adb logcat died a few seconds before the nook rebooted, so i don't have any of these criticial parts of the log ...
Certain models of the HD+ have been known to develop a read only internal memory. It acts like it is being written to but it does not actually happen. When that happens it is not repairable.
Sent from my SM-T707V using XDA Premium HD app
leapinlar said:
Certain models of the HD+ have been known to develop a read only internal memory. It acts like it is being written to but it does not actually happen. When that happens it is not repairable.
Click to expand...
Click to collapse
Hi Leapinlar,
thanks for your feedback: Rather surprising (& unfortunate) behaviour but still better than a rootkit
I guess so my option are only to install/boot CM from an sdcard (or getting a new device)?
-michael-
BTW: to run CM from sdcard i guess i need a no-emmc ROM (even though my emmc still works read-only and i can boot recovery from it)? If so, the latest one i found is https://iamafanof.wordpress.com/201...-4-4-4-for-bricked-no-emmc-nook-hd-04nov2014/ which is rather dated. Is there anywhere a new one or some pointers one what all has to be changed to make a emmc ROM turn into a no-emmc ROM so i could try changing a ROM myself? Thanks!