Thats exactly what happen with mine. I was using the GPS and the battery drained so quickly until 0%. I charged it till full and the rest is history I cant get it to work again.
Streak 7 "read only" problem
- Thread starter onilink67
- Start date
When I first started researching this issue, I found information pertaining to a read-only lock status that can be initiated as some sort of emergency response byt the hardware. I could never find out how to reverse it, but it was looking like something that could only be done with factory hardware or something like what the other fella is talking about, the jtag.
Im having the same problem. I cannot mount or flash to system in abd or fastboot.
Update called dell. They needed information and wouldn't send me a box without the owners information.
I explained how I am doing this for a friend I called him and he told me where he got it. So I called back they told me that wasent where is was bought first.
Kinda bs since the imei is valid and it wasent reported stolen. He bought it used.
Any updates on a work around?
sent from my sense on crack MT4G Slide using xda premium
I explained how I am doing this for a friend I called him and he told me where he got it. So I called back they told me that wasent where is was bought first.
Kinda bs since the imei is valid and it wasent reported stolen. He bought it used.
Any updates on a work around?
sent from my sense on crack MT4G Slide using xda premium
Ok I've gotten another one of these now this time seems the system partition is read-only starting to believe this more. Thinking that the only way may be JTAG.
I'm almost certain system partition is read only fastboot or adb cannot flash or pull anything from it.
sent from my sense on crack MT4G Slide using xda premium
My other one its the bootloader partition it seems but this one is the system can't even do anything in nvflash
I tried nvflash it said success. Upon reboot still the same thing. I wonder why it said successful. It wrote to all 14 partitions. Upon boot somehow it gets deleted. Almost seems like it getting writtten then a master/root command revokes it.
I wish I was savvy enough to figure out which routine it may be. Although I have a feeling it may be on the root partition 1?
I wouldn't be surprised if dell just used a master key program to unlock it and reflash.
Oh update. I finally got my friends streak support.
I had told them that I bought the streak 6 months ago from t mobile. I have a t mobile streak so it was a good guess. They registered it in my name as well.
I also had told them I did both factory resets privacy and boot loader as well as tried adb and fastboot. He didn't even bother troubleshooting. I called 3 times btw.
Hope it helps some other people. I suppose the wifi one may have more sellers? But a few calls and should get the right guess.
sent from my sense on crack MT4G Slide using xda premium
Generally tech support from companies wouldnt involve you trying to fix it on your own with adb/fastboot/nvflash since unless you knew what you were doing there's a real chance you'd make things worse, though given if you knew enough to try those hopefully you'd know enough to at least make things worse.
Not critizising, just trying to give perspective.
I've done a little studying on the s7, but I cant offer much yet. I once managed to somehow brick my loaner s7 and we looked at the adb log and it had a slew of 'nand is in read only mode' stuff.
I reflashed the stock rec and fac resetted and that seemed to fix it, but I kinda doubt it was a true read-only event since we easily fixed it.
Lost all his data though, but he didnt have much on it since i was using it to dev and there's a very real risk i'd brick it and have to rebuild the partitions anyway.
It's a really long shot in the dark, but have you tried fac resetting with a stock rec installed? Though I cant tell if flashing a new rec would even stick at all.
The Streak series have no protection at all, even the s10 is unlocked, apparently it's relatively easy to make locked devices by using the Secure Boot Key command, but that's at the designing stage for a device, you wouldnt go and slap it onto unprotected devices, it's all or nothing.
One final note, for some reason both the s7/10 start at partition #2, there's simply nothing before that as the sector location of partition 2 starts at 0, so there's nothing hidden before it. If there was it's silently converting sector numbers on the fly so it THINKS partition 2 = start from sector 0, which is pretty crazy sounding.
Mabye all tegra2's start at partition 2.
Not critizising, just trying to give perspective.
I've done a little studying on the s7, but I cant offer much yet. I once managed to somehow brick my loaner s7 and we looked at the adb log and it had a slew of 'nand is in read only mode' stuff.
I reflashed the stock rec and fac resetted and that seemed to fix it, but I kinda doubt it was a true read-only event since we easily fixed it.
Lost all his data though, but he didnt have much on it since i was using it to dev and there's a very real risk i'd brick it and have to rebuild the partitions anyway.
It's a really long shot in the dark, but have you tried fac resetting with a stock rec installed? Though I cant tell if flashing a new rec would even stick at all.
The Streak series have no protection at all, even the s10 is unlocked, apparently it's relatively easy to make locked devices by using the Secure Boot Key command, but that's at the designing stage for a device, you wouldnt go and slap it onto unprotected devices, it's all or nothing.
One final note, for some reason both the s7/10 start at partition #2, there's simply nothing before that as the sector location of partition 2 starts at 0, so there's nothing hidden before it. If there was it's silently converting sector numbers on the fly so it THINKS partition 2 = start from sector 0, which is pretty crazy sounding.
Mabye all tegra2's start at partition 2.
You won't brick th device it will go into read only which is worse. Lol
There has to be a command somewhere in the kernal or set of instructions telling the device to put the partitions in read only. Once again nvflash goes threw the partitions one by one reformating them to bonestock.
Using. Stock recovery and fastboot do not work. It says success then boom your homescreen pops up. The dell streak I have is fully stock btw. Hasent been rooted or have a custom recovery image.
sent from my sense on crack MT4G Slide using xda premium
Neat stuff, it will be interesting to see just what is the cause of this problem. VERY strange, for sure.
Iam betting there are several causes. Someone said this happened when the battery died. Which leads me to believe that something went corrupt and the system set off read only mode.Neat stuff, it will be interesting to see just what is the cause of this problem. VERY strange, for sure.
sent from my sense on crack MT4G Slide using xda premium
There must be other complicating factors, I have had my S7 run all the way down (stupid not to have some kind of power off protection when the battery gets critical). I had some trouble getting it booted up, but it has been fine since.
I have 2 s7 both bought from ebay. Both of them became read only after batteries died 0%. Both have stock rom froyo. One rooted and the other is not.
The battery died when one I was using the GPS navigation and the other when playing music. After that it's history, cant boot it up, nvflash and etc. Now both of them becomes paperweight ,Dell refuse to repair it since Im not the original owner.
This happend to mine too the other day. It went to 0, and now is read only. I am not the original owner but I will attempt to call dell anyways.
If discharging to 0 is the key, then Dell needs to own up to this, screw who owns it, used, etc. It's a failure period.
Luckily mine hasn't done this, and it's drained to 0 at least 3 times.. Heats up, locked, and until I discover it in that way it drains about 10%/hr or more. I've had it dead at least 3 times, found it locked up and had to hold power to power it off and back on at least 3-4 times.
Luckily mine hasn't done this, and it's drained to 0 at least 3 times.. Heats up, locked, and until I discover it in that way it drains about 10%/hr or more. I've had it dead at least 3 times, found it locked up and had to hold power to power it off and back on at least 3-4 times.
Battery issues??
I have a "bricked" s7 also. When I try to flash an update pkg from SD I get a 'battery low' message even when the battery has been charged all night. Could there be a bug that won't allow any flash activity when the system thinks the battery is low, even when its not?
I have a "bricked" s7 also. When I try to flash an update pkg from SD I get a 'battery low' message even when the battery has been charged all night. Could there be a bug that won't allow any flash activity when the system thinks the battery is low, even when its not?
You guys found any solution for this? I dont own an Streak 7" but ido own a Motorola Xoom and i have the SAME problem after battery hit 0% (and not the first time it has done it...)
I'm wondering if the Streak has a backup battery for the bios rom, like my Toshiba Thrive has?
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone