Unusable Dell streak 7

[pmarshall_band]

Hi guys. I hope I posted in the correct section. I need some help in fixing my Dell Streak 7 that I bought used off Ebay. I would usually restart itself while using it once in a while. Then it start rebooting itself more frequently. Now, as soon as it boots up, before I can press anything the screen goes blank for a couple seconds then it reboots. And it keeps doing this and will never allow me to use it. I even restarted in safe mode but still was not able to touch anything.

I boot up in recovery mode, but when I try to do any reset or update from sd card, it goes straight in CWM recovery mode. Nothing works in here. If I do any reset or install from zip and even try to backup, it always fail. It says it format data, cache, sd-ext but always get error: error mounting /sdcard/.android_secure. After rebooting, everything remains the same. There was no change.

I boot up in fast mode, but when trying to flash in command prompt or using nvflash, I get an error message failing to write error 00140005 or 0x00140005. I connect using adb command prompt but no changes here remains permanent. Everything is lost during reboot. I also booted in apx mode, tried running the bat file in several streakdroid files, but get this same error message. 00140005. It created but could not format partitions.

I have been trying for a couple days now but not getting any good results. So can you guys provide a solution so I can fix this problem? Thanks in advance.

 

[wptski]

Sounds like your stuck in the so-called "read only" mode. Normally there is no fix other than sending it back to Dell but one user has fixed theirs. It may not be in a thread title, so search posts for "read only". Also user "giveen" has mentioned in one thread that he has some ideas for a fix if someone with the problem contacts him.

 

[ElfinJNoty]

You need to verify what model you have(WiFi or 3g or 4g, us or Europe) that's the first step.

Check the stickies section for the streak wiki that has a list of the factory roms and recoveries. There are a number of nvflash packages, but you will fail at flashing the wrong package to the wrong device. I would recommend sound some reading.... There are tons of threads that will give you a bit of a runaround to find the right files needed but instructions are available.

Without providing more info specific to the device you have there is not much I can help with. Narrow down the basics and go from there, I or others will point you in a good direction after that... Pretty slim following on the streak threads and very limited dev work, and the devs have had it with answering stuff like this unless you put in a little leg work to start.

Read read read
Good luck

Sent from my Galaxy Nexus using xda premium

 

[pmarshall_band]

Thanks for your rapid response. Based on a line from the fastboot screen, it seems to be 3g. I have already downloaded the original stock and recovery roms for both 3g and 4g and tried to flash them but get same error message 0x00140005. It uses a sim card for data. I would like to remove the CWM based recovery but have not been able to.

 

[wptski]

Thanks for your rapid response. Based on a line from the fastboot screen, it seems to be 3g. I have already downloaded the original stock and recovery roms for both 3g and 4g and tried to flash them but get same error message 0x00140005. It uses a sim card for data. I would like to remove the CWM based recovery but have not been able to.

Try the NVflash back to Froyo 2.2 which should wipe everything. Link to the file: http://d-h.st/iXc

 

[pmarshall_band]

Thanks but already tried that. I didnt work. I have spent days researching and downloading lots of files. But nothing works. Take a look at this attempt flash in fastboot:

d:\fastboot>fastboot flash recovery recovery.img
sending 'recovery' <3654 kb>
okay [ 0.547s]
writing 'recovery' ...
FAILED <remote: <00140005>>
finished. total time: 1.776s

At the point of writing recovery, the adb drivers in
device manager suddenly goes as if the device was unplugged
then it returns after the failed error

In apx mode, after creating the partitions, it failed at formatting partition 2 BCT saying
command failure: create failed <bad data>
bootloader status: partition table is required for this command <code: 8> message: nverror:0x2 flags: 0

This is what happens every time I try to flash in fast boot or in apx mode with any of the files I have downloaded.

 

[ElfinJNoty]

Thanks but already tried that. I didnt work. I have spent days researching and downloading lots of files. But nothing works. Take a look at this attempt flash in fastboot:

d:\fastboot>fastboot flash recovery recovery.img
sending 'recovery'
okay [ 0.547s]
writing 'recovery' ...
FAILED
finished. total time: 1.776s

At the point of writing recovery, the adb drivers in
device manager suddenly goes as if the device was unplugged
then it returns after the failed error

In apx mode, after creating the partitions, it failed at formatting partition 2 BCT saying
command failure: create failed
bootloader status: partition table is required for this command message: nverror:0x2 flags: 0

This is what happens every time I try to flash in fast boot or in apx mode with any of the files I have downloaded.

Your streak is all jacked up my dude. You say it was working when you first got it but started random rebooting and then boot loops. What did the OS look like while it was working? Froyo, Honeycomb, ICS, JB? Sounds like your partition sizes have been modified, or you wiped things like a crazy man in this unknown version of CWM you got and nvflash can't determine the block sizes when trying to rewrite the partitions

Sent from my Galaxy Nexus using xda premium

---------- Post added at 12:16 PM ---------- Previous post was at 12:08 PM ----------

Have you tried individually flashing the .IMG files?

fastboot flash /system (file name)
that's not exact... just as a reference

You need to verify what partition sizes you have first. The general consensus for development was to move back to stock partition sizes with the newer ROM versions available. It became a clusterfu** with different stuff on variants of the stock partition table. You may be a casualty of not taking a necessary step in moving from a honey streak ROM.

Sent from my Galaxy Nexus using xda premium

 

[pmarshall_band]

It is the honeycomb 3.2 and the CWM is 6.1.0.2. The person I bought it from on ebay upgraded it to honeycomb 3.2 after I payed for it. I asked him to upgrade it for me. Now I remember he told he had a lot of problems trying to upgrade and it took him a very long time. From the day I got it, it was always restarting on its own while I am using it. When I am in the cwm recovery mode and choose data/wipe option, it always stop on error formatting data or cache. Very few time is says it formatted without any problems but after rebooting its all the same. Yes I have tried flashing individual img files for both boot and recovery. I have even tried the temporary cwm recovery to see if a different version would help, but it wouldnt accept any files except the version that is already installed.

 

[ElfinJNoty]

It is the honeycomb 3.2 and the CWM is 6.1.0.2. The person I bought it from on ebay upgraded it to honeycomb 3.2 after I payed for it. I asked him to upgrade it for me. Now I remember he told he had a lot of problems trying to upgrade and it took him a very long time. From the day I got it, it was always restarting on its own while I am using it. When I am in the cwm recovery mode and choose data/wipe option, it always stop on error formatting data or cache. Very few time is says it formatted without any problems but after rebooting its all the same. Yes I have tried flashing individual img files for both boot and recovery. I have even tried the temporary cwm recovery to see if a different version would help, but it wouldnt accept any files except the version that is already installed.

Try the latest twrp recovery, I only tried cwm on my WiFi streak once and it didn't do well wiping, typical probability of wipe issues with cwm across many devices. Have been using twrp without fail since. Check in dev thread, fast boot flash recovery... See if that helps

If you've got just a stock 3.2 honeycomb you should have stock partitions, but without the stock recovery to match it won't install an official update.pkg correctly(assuming you were just trying to reinstall the honeycomb)

If you can't fast boot flash recover.IMG of twrp I don't know what to tell ya. Sorry
Sent from my Galaxy Nexus using xda premium

---------- Post added at 03:51 PM ---------- Previous post was at 03:43 PM ----------

You could also start over from scratch, delete drivers on PC and reinstall, make sure everything from the ground up is in order, and reread whatever instructions you are following, sometimes it is the smallest details we miss

Sent from my Galaxy Nexus using xda premium

 

[wptski]

Thanks but already tried that. I didnt work. I have spent days researching and downloading lots of files. But nothing works. Take a look at this attempt flash in fastboot:

d:\fastboot>fastboot flash recovery recovery.img
sending 'recovery' <3654 kb>
okay [ 0.547s]
writing 'recovery' ...
FAILED <remote: <00140005>>
finished. total time: 1.776s

At the point of writing recovery, the adb drivers in
device manager suddenly goes as if the device was unplugged
then it returns after the failed error

In apx mode, after creating the partitions, it failed at formatting partition 2 BCT saying
command failure: create failed <bad data>
bootloader status: partition table is required for this command <code: 8> message: nverror:0x2 flags: 0

This is what happens every time I try to flash in fast boot or in apx mode with any of the files I have downloaded.

If that doesn't work, you are either stuck in the "read only" mode or it's bricked for some other reason. Look at post #125 in this thread: http://forum.xda-developers.com/showthread.php?p=31710460#post31710460

 

[pmarshall_band]

Hi guys, I still havent found any solution as yet. I have researching very hard, reading and trying all different ideas seen in this and other forums. I have tried many commands from adb, fastboot and even tried unlocking bootloader. I have backed up another tablet like mine and tried to restored on mine. The tablet refuses to accept any change to the data partition. I have even looked at the possiblity of changing the internal memory card. But nothing as yet up to this point. Right now the problem seems hardware related.

 

[wptski]

Hi guys, I still havent found any solution as yet. I have researching very hard, reading and trying all different ideas seen in this and other forums. I have tried many commands from adb, fastboot and even tried unlocking bootloader. I have backed up another tablet like mine and tried to restored on mine. The tablet refuses to accept any change to the data partition. I have even looked at the possiblity of changing the internal memory card. But nothing as yet up to this point. Right now the problem seems hardware related.

You may be stuck in the so-called "read only" mode. I've suggested things to try, either try that, return it to Dell for repair or chuck it.

 

[pmarshall_band]

I had suspected the internal memory to be the problem as I could hear some whining sounds coming from inside. I opened it and verified. However, while trying to figure out if it could be changed, the tablet suddenly lost it. It will no longer boot. Seems to have completely died. No more response. So I will now rest my case and thank all you kind people for your quick response and assistance. I will be looking for another tablet, but definitely not a Dell. Happy new year. Take care.

 

[giveen]

I had suspected the internal memory to be the problem as I could hear some whining sounds coming from inside. I opened it and verified. However, while trying to figure out if it could be changed, the tablet suddenly lost it. It will no longer boot. Seems to have completely died. No more response. So I will now rest my case and thank all you kind people for your quick response and assistance. I will be looking for another tablet, but definitely not a Dell. Happy new year. Take care.

Internal memory is emmc flash memory, not a hard drive.

 

[wptski]

Internal memory is emmc flash memory, not a hard drive.

I've got a OBD-II car reader/scanner that makes a high pitched whine.

 

[giveen]

I've got a OBD-II car reader/scanner that makes a high pitched whine.

Yeah but it doesn't mean there is a magnetic had drive inside. Memory does not whine.

Sent from my Nexus 7 using Tapatalk 2

 

[wptski]

Yeah but it doesn't mean there is a magnetic had drive inside. Memory does not whine.

Sent from my Nexus 7 using Tapatalk 2

Correct but I believe that an oscilltor circuit can emit an audible sound at times and maybe not everyone can hear it too.

 

[giveen]

Correct but I believe that an oscilltor circuit can emit an audible sound at times and maybe not everyone can hear it too.

True but again it doesn't have to do with memory

 

[wptski]

True but again it doesn't have to do with memory

The OP was probably just guessing as to what/where the sound was coming from.

 

[giveen]

The OP was probably just guessing as to what/where the sound was coming from.

I know. I'm just stating something and arguing because Im bored.
Sound in CM10 is killing me.