For those of us with read only nand

[tech5]

After some....ok lots of reading I have found out Linux based is has a fail safe built in to make a corrupt system still boot so you can fix it.....it switches to read only to prevent further damage ......on a system like Ubuntu you can mount and fdisk ....unfortunately I can't seem to get the streak 7 to mount in anything other then Adb in Ubuntu which means the sdcard is being used .....if we can manage to get it to mount somehow pre clockwork booting then we could wipe it and start fresh.....also if we could use a different version of nvflash there are some format commands that might work.....haven't been able to find one that will work yet but will keep everyone postedposted

Sent from my HTC HD2 using XDA App

 

[ToyGUN]

I'm stuck too, but I bought my streak 7 off of ebay and it has the other guy's data on it.... I had some weird instances where I ran this in fastboot though

fastboot -i 0x413c erase system
fastboot -i 0x413c erase boot
fastboot -i 0x413c flash system system.img
fastboot -i 0x413c flash boot boot.img
fastboot -i 0x413c boot boot.img

It ends up booting after about 5 mins and has superuser access. (I used the boot and system from the Streakdroid.zip) I can at least play around, but don't have busybox commands. So I installed that and started to play with the parted script. The logcat indicates that it is booting from the end of the internal memory, but of course as soon as I turn off the device and turn it back on everything is back to where I started. I'm also looking into whether or not the guy I bought this off of disabled his lookout restore for the device, that could cause trouble. Don't know if that helps. Checkout the advent vega website for updated nvflash (dl the system update and extract the exe)


Update: Lookout wasn't the problem, I confirmed with the techs there that the device wasn't registered to anyone else. Mine is still stuck,

 

[derekedw]

Ever any luck with this? I have the same problem.

 

[cootertwo]

Same here..... help! Seems like a simple problem, but no solution, YET!

 

[new1here]

I'd like to joined the "read-only" member group. I've read and read through every single possible solution....fastboot..adb..nvflash..holy water. No luck. Any help would be truly, truly appreciated. I kind of have an idea what tech5 is talking about, but like name says new1here...lol. I'll keep fingers cross and read up some more.

 

[lynrd]

Another one

My streak also went "Read Only". I called Dell and got a dispatch set up so they can fix it.

Not happy about it as this will be the second time that this thing has gone back to the factory for the NAND issue.

 

[khaytsus]

My streak also went "Read Only". I called Dell and got a dispatch set up so they can fix it.

Not happy about it as this will be the second time that this thing has gone back to the factory for the NAND issue.

Were you doing any custom ROMs etc with it, or can this just happen out of the blue?

And does anyone know what's going on? Bit getting flipped somewhere to make it "read only" or is something really failing?

 

[cootertwo]

I'm starting to suspect some sort of VIRUS

 

[khaytsus]

I'm starting to suspect some sort of VIRUS

Get a clue.

 

[cootertwo]

Well then explain to me why it's happening ???? Im a nubee with android, but it seems as if it is a fixable problem, if we just knew what was going on. Sure dell will re format and load all the good stuff back up, but it has and will happen again. Not very reassuring fo sho.