Streak 7 "read only" problem

[stevedebi]

Why not just use it on WiFi at home. Set it to airplane mode and then enable the WiFi. That is how I use my 4g S7

Because I bought a Toshiba "Thrive" while my streak was gone for repair cause of the read only problem. The Thrive blows the streak away as far as ports, etc. 10" screen, on and on.

I like the thrive, but not the large form factor. 7 inch is just right.

Sent from my HTC View somewhere in LALA land

 

[Chris123234]

You can add me to the list.

I pulled it out of the closet after not using it for nearly a year, but didn't remember why I put it away. Couldn't NVFlash or put CWM after factory reset wasn't working and realized what the problem was; same as it was back then. Probably going to take it apart out of spite.

edit: It's a T-Mobile Streak 7

 

[Cerixus]

If "read only problem" means it looks like it flashed a new rom but when you reboot it's still stock 2.2.2 then you can add me to the list

Bought 2 DS7's on Daily Steals. My wife's already had 3.2, mine still has 2.2.2.

 

[aweskelo]

You can attempt to return it to TMO or Dell. I did and they sent me a replacement. But you have to be sure its this problem.

 

[aweskelo]

And by the way...never let the battery die on its own. The streak will not shut down on its own at low battery and that's what corrupts it.

 

[stevedebi]

And by the way...never let the battery die on its own. The streak will not shut down on its own at low battery and that's what corrupts it.

I had mine die that way but luckily it didn't go read only on me. I charged it for a few minutes, then turned it on while plugged in for the rest of the charge cycle.

Sent from my HTC_Amaze_4G using xda premium

 

[WookieFan]

And by the way...never let the battery die on its own. The streak will not shut down on its own at low battery and that's what corrupts it.

I've flashed the OTA Honeycomb on my T-Mo DS7 and it has run down several times without issue. I have to think something else is contributing to this issue.

Sent from my ADR6425LVW using Tapatalk 2

 

[sirbagin]

Hi,
Can anyone recommend an app which can shutdown the system when battery level drops below the pre set value?
I have one ds7 on order and I'm a bit worried about this problem.

Sent from my GT-I9100 using xda app-developers app

 

[otnos]

It's not caused by letting the battery run out. I have own this tablet for almost a year now and have many times used it until the battery died, but never did it go into "read only" mode.

My advice to you is treat this device with care and use it within its limitations. This is not a desktop so don't load it up with everything under the sun. Be careful with apps. Many times bad/poorly written apps may be the culprit to many of the DS7 problems. But we are so conditioned to having a reliable desktop and software that works, that we quickly blame the hardware for problems caused by a less than perfect OS running junk apps.

 

[sirbagin]

Thanks for reply.
The fact that you have yours for more than a year is reassuring however my ds7 will be used by more than one person so I would feel better knowing that it can switch itself off before taking a gamble with it's own power management.


Sent from my GT-I9100 using xda app-developers app

 

[SayaX]

Add me to the list.

A friend gave me the tablet and it was the Tmobile US version with the sim card support. It had not been charged in forever and she couldn't figure out how to get it to work and had given it to me to fix/keep. I had figured out that it only needed an USB>AC since apparently USB Charging doesn't work (pretty lame!). I was pretty impressed until I went to restart the unit, it greets me with the same "Welcome to Android" screen and obviously it didn't save anything I had done to it before I restarted it. Did a hard reset from the bootloader, same problem. It's pretty sad as it seems to be a pretty decent tablet for the price aside from the battery life being abysmal.

However, playing with the tablet spurred me to go ahead and pick up a Samsung Galaxy Tab 2 7.0 which I am pretty happy with.

Has anyone figured out how the hardware plays into this problem? Or is it a strictly a software issue?

 

[bdouglas]

How to tell if you have been "Read-Only"ed?

I have been searching for a little while, and I haven't come up with anything that says "if this happens you are stuck in Read-Only mode."

I have a Streak 7 (company property) that I think is in Read-Only mode. Another guy with my company flashed this and several other Streaks to dj_steve's HoneyStreak HD7-2.0R1. This one was brought to me about 2 months later because it "would not boot anymore". When I tried to start it up it stuck on the Dell logo. I soon realized though that if I left it on the Dell logo for a really long time (like 30 minutes) it would finally start to boot showing the StreakDroid logo. Once it finished booting it asked for a password. According to many of the posts that I have read this is because something happened to cause the device to "go encrypted." I know that we did not purposefully encrypt the device, but it is encrypted. I have verified that by using adb shell to bring up the settings screen with this command:

am start -a android.intent.action.MAIN -n com.android.settings/.Settings

Nothing I have tried seems to have any effect at all on the device. I have tried Factory Resetting from the settings menu, from the CWM recovery that is already on the device (4.0.1.4-DJ_Steve-Streak7) and by using "fastboot boot recovery.img" with a 5.0.2.7 CWM image. I have tried using NVflash to send the partition images to the device. I have tried using "fastboot flash" to flash the recovery image, the boot image, and the system image. None of them have any effect whatsoever on the tablet. It still takes 30 minutes to boot, and has the same password screen no matter what I do.

Is this what is meant by Read-Only mode?

If so, how can I prevent our other Streaks (we have 4 others) from suffering the same fate?

*EDIT* I also have a logcat saved that was taken one time when the device began booting showing the StreakDroid logo if anyone is interested in that. I don't know if any useful information can be gleaned form that text. I spent about 20 minutes looking through it and nothing jumped out at me as a cause.

 

[wptski]

Some have claimed that allowing to battery run all the way down causes this yet others claim to have done just that several times and have no problems. Go figure.........

 

[bdouglas]

Maybe...

Some have claimed that allowing to battery run all the way down causes this yet others claim to have done just that several times and have no problems. Go figure.........

Yeah I read that in several posts above. I can't say for certain whether the battery ran down on this one or not since I wasn't the one using it, but it had been working fine in the office until we sent it out with one of our technicians. The chances of the battery running down completely are pretty good since the tech's don't always have a good place to charge it.

I also read something suggesting that having a certain combination of ROM and recovery image cause this issue. Basically the gist of what I read seemed to say that some versions of clockwork recovery cause this problem when the device is factory reset because the device usually uses the stock recovery to do the factory default. Does anyone know if that is the case?

 

[trungtuyen66]

For anyone stuck on a read only device, if you try to fac reset, are you using the stock recovery for the installed rom? (This only applies to devices stuck in read only mode with stock roms, it does not apply to Honeystreak R2-R6)

i can not fac reset , or flash stock roms ecovery
help

 

[giveen]

Yes you can.

Sent from my Nexus 7 using Tapatalk 2

 

[Nocturnal_50]

not sure what everyone else is doing wrong... just re-flash your recovery then flash another rom over the top and done, its an emmc bug

turns out its not that simple... gonna chown the whole thing and see if I can mount as r/w

 

[Nocturnal_50]

not sure what everyone else is doing wrong... just re-flash your recovery then flash another rom over the top and done, its an emmc bug

turns out its not that simple... gonna chown the whole thing and see if I can mount as r/w

can someone who has a stable working S7 and someone who has one that is RO'd post a treeview of their /etc/fstab/ both stock preferably but a stable cm9/cm10 one would be great too... if I get it in the next 4 hours we can try some things to get it back to a working standard

 

[TheManii]

if you mean /etc/vold.fstab, it's a static file.
If you mean /etc/recovery.fstab, that's not actually used by the rom, the fact it's in some roms is simply an oversight.

 

[Nocturnal_50]

if you mean /etc/vold.fstab, it's a static file.
If you mean /etc/recovery.fstab, that's not actually used by the rom, the fact it's in some roms is simply an oversight.

why cant it just be like normal linux? gonna chown/chmod the lot and see what that does, what have i got to lose?