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.
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.
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
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.
pmarshall_band said:
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.
Click to expand...
Click to collapse
Try the NVflash back to Froyo 2.2 which should wipe everything. Link to the file: http://d-h.st/iXc
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.
pmarshall_band said:
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.
Click to expand...
Click to collapse
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
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.
pmarshall_band said:
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.
Click to expand...
Click to collapse
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
pmarshall_band said:
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.
Click to expand...
Click to collapse
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
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.
pmarshall_band said:
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.
Click to expand...
Click to collapse
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.
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.
pmarshall_band said:
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.
Click to expand...
Click to collapse
Internal memory is emmc flash memory, not a hard drive.
giveen said:
Internal memory is emmc flash memory, not a hard drive.
Click to expand...
Click to collapse
I've got a OBD-II car reader/scanner that makes a high pitched whine.
wptski said:
I've got a OBD-II car reader/scanner that makes a high pitched whine.
Click to expand...
Click to collapse
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
giveen said:
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
Click to expand...
Click to collapse
Correct but I believe that an oscilltor circuit can emit an audible sound at times and maybe not everyone can hear it too.
wptski said:
Correct but I believe that an oscilltor circuit can emit an audible sound at times and maybe not everyone can hear it too.
Click to expand...
Click to collapse
True but again it doesn't have to do with memory
giveen said:
True but again it doesn't have to do with memory
Click to expand...
Click to collapse
The OP was probably just guessing as to what/where the sound was coming from.
wptski said:
The OP was probably just guessing as to what/where the sound was coming from.
Click to expand...
Click to collapse
I know. I'm just stating something and arguing because Im bored.
Sound in CM10 is killing me.
This is a basic question but I can't find the answer anywhere.
I have an unlocked and rooted Moto X DE. I got rid of the bootloader unlocked warning message and replaced it with another image, which is much better. However I also ran the command
fastboot erase clogo
before I knew what I was doing. Fastboot reported back it was erasing clogo. Anyhow, if clogo is the original boot logo with the bluish green Motorola symbol with "a google company" underneath it, I want it back. So my questions are:
1) when you use the command "fastboot flash" where am I flashing to? the boot partition?
2) where is the boot logo (clogo and/or logo) stored and can I see this/these file(s) on my phone using a root explorer like Root Browser?
Thanks!
Cozume said:
This is a basic question but I can't find the answer anywhere.
I have an unlocked and rooted Moto X DE. I got rid of the bootloader unlocked warning message and replaced it with another image, which is much better. However I also ran the command
fastboot erase clogo
before I knew what I was doing. Fastboot reported back it was erasing clogo. Anyhow, if clogo is the original boot logo with the bluish green Motorola symbol with "a google company" underneath it, I want it back. So my questions are:
1) when you use the command "fastboot flash" where am I flashing to? the boot partition?
2) where is the boot logo (clogo and/or logo) stored and can I see this/these file(s) on my phone using a root explorer like Root Browser?
Thanks!
Click to expand...
Click to collapse
I cant answer your questions about where on the device the fasboot flash writes too, but i did come across this post that may help you reach your desired result.
http://forum.xda-developers.com/showthread.php?t=2548566
Teksu said:
I cant answer your questions about where on the device the fasboot flash writes too, but i did come across this post that may help you reach your desired result.
http://forum.xda-developers.com/showthread.php?t=2548566
Click to expand...
Click to collapse
thank you! it worked.
I will come back to hit the thanks button tomorrow because they won't let me do it anymore times today, apparently you only get to do it 8 times a day!
So being the hot headed fool that I am, I pretty much just upped and tried to flash a non-stock ROM onto my L90 D415 10c without reading enough about the process. I rooted with towelroot and got into the bootloader, then I thought that simply with an erase command and an update command my phone would just reboot with the new ROM on it, alas this was not true. What I did was
fastboot erase system
fastboot erase boot
After entering "fastboot update cmod.zip" there was a message:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
My phone is now stuck in the bootloader, what do I do? Is there any way to restore it's previous settings/memory?
The two "guides" that I followed (pretty much exactly) were first this and then this.
Last thing that seems like it may help is when I type "fastboot continue", my phone ends up with a message saying:
ERROR: Invalid boot image header
If anybody can solve this for me I would be eternally grateful. I've already learned my lesson, and I've got a feeling I'll be coming back to xda. For better reasons I hope. Thanks in Advance
EDIT: I guess I should add that I tried to flash the ROM in fastboot, which now that I think of it, I'm not sure is even possible? I do have my entire terminal history if that helps.
karlsin said:
So being the hot headed fool that I am, I pretty much just upped and tried to flash a non-stock ROM onto my L90 D415 10c without reading enough about the process. I rooted with towelroot and got into the bootloader, then I thought that simply with an erase command and an update command my phone would just reboot with the new ROM on it, alas this was not true. What I did was
fastboot erase system
fastboot erase boot
After entering "fastboot update cmod.zip" there was a message:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
My phone is now stuck in the bootloader, what do I do? Is there any way to restore it's previous settings/memory?
The two "guides" that I followed (pretty much exactly) were first this and then this.
Last thing that seems like it may help is when I type "fastboot continue", my phone ends up with a message saying:
ERROR: Invalid boot image header
If anybody can solve this for me I would be eternally grateful. I've already learned my lesson, and I've got a feeling I'll be coming back to xda. For better reasons I hope. Thanks in Advance
EDIT: I guess I should add that I tried to flash the ROM in fastboot, which now that I think of it, I'm not sure is even possible? I do have my entire terminal history if that helps.
Click to expand...
Click to collapse
Just follow my KDZ flashing guide and reflash kdz
http://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479
gdjindal said:
Just follow my KDZ flashing guide and reflash kdz
http://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479
Click to expand...
Click to collapse
The LG Mobile Support Tool doesn't recognize my phone. I followed the directions exactly (plugging the phone in after the first error message), but the same message appears after pressing retry.
karlsin said:
The LG Mobile Support Tool doesn't recognize my phone. I followed the directions exactly (plugging the phone in after the first error message), but the same message appears after pressing retry.
Click to expand...
Click to collapse
Power off the phone, pret volume up and insert USB cable . Now follow the guide.
Sent from my LG-D405 using XDA Free mobile app
If this is covered somewhere, please let me know.
While I was texting this morning, the phone turned off, and then got stuck on the white google logo.
I was able to get into recovery and when I tried to do anything (like look for old backups) nothing was there. When I try and do factory reset, it says unable to mount xxx (everything)
Try to push via adb has been unsuccessful. I've been trying toolkits to see if they have any magic in them, and no dice so far.
Any ideas or help?
Looking like I might have to contact Motorolla.
FWIW I was running rooted stock vzw image.
if you were running stock rooted and your phone is stuck in a loop you probably need to wipe your data, but since you can't wipe anything I would suggest booting into bootloader and flashing a fresh image. Make sure you check you md5's before flashing as you may have gotten a bad download!
sevenpioverthree said:
if you were running stock rooted and your phone is stuck in a loop you probably need to wipe your data, but since you can't wipe anything I would suggest booting into bootloader and flashing a fresh image. Make sure you check you md5's before flashing as you may have gotten a bad download!
Click to expand...
Click to collapse
thanks for the quick reply. maybe i'm doing something wrong, but trying to flash a fresh image isn't working either.
dopepope said:
thanks for the quick reply. maybe i'm doing something wrong, but trying to flash a fresh image isn't working either.
Click to expand...
Click to collapse
Can you list your steps in trying to flash a new image?
sevenpioverthree said:
Can you list your steps in trying to flash a new image?
Click to expand...
Click to collapse
of course.
following this tutorial:
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
i've tried to manually flash via fastboot each portion, and ive tried the flash-all method
get FAILED <remote failure> when its pushing out.
(phone is in bootloader)
dopepope said:
of course.
following this tutorial:
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
i've tried to manually flash via fastboot each portion, and ive tried the flash-all method
get FAILED <remote failure> when its pushing out.
(phone is in bootloader)
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2603245
Not sure if that thread applies to you exactly, I read the first couple pages and it seems that the OP's phone somehow got relocked in the process. You can try running the fastboot oem unlock command again, updating your adb SDK, or trying one of the commands they list there although it's not for our phone so I'm not really sure what those commands will do
sevenpioverthree said:
http://forum.xda-developers.com/showthread.php?t=2603245
Not sure if that thread applies to you exactly, I read the first couple pages and it seems that the OP's phone somehow got relocked in the process. You can try running the fastboot oem unlock command again, updating your adb SDK, or trying one of the commands they list there although it's not for our phone so I'm not really sure what those commands will do
Click to expand...
Click to collapse
At this point I'll give anything a shot. Phone is in the RMA process (they're sending out a new one), so if I can get it working today I guess I can cancel the RMA, but I don't have high hopes.
Can't even re-lock the device:
<bootloader>
failed to erase parition
general lock failure!
sst lock failure!
FAILED <remote failure>
dopepope said:
Can't even re-lock the device:
<bootloader>
failed to erase parition
general lock failure!
sst lock failure!
FAILED <remote failure>
Click to expand...
Click to collapse
reading through the thread, i doubt there is hope. my only thought would be trying to flash the partition table first.
After nothing working got a replacement phone from Motorolla. Looks like I'm not the only one that had this particular issue. Not sure what the common factors are between us on this forum that have had a seemingly random hardware failure, but it doesn't give me a ton of confidence in the hardware. Good reminder to backup the stuff you care about
Hi people. I was trying to install a new ROM on my TF701, 'cause I was very sad to keep that stock 4.4.2.
Of course, I did a mess.
1st thing, I tried to unlock the boot with the Asus apk, but I was struck (it asked for google permission, I tried to give my correct password, but it rejected it. I saw - only too late - that maybe, if I had fully removed my google account before to use that tool, all should have been go right...).
Then, I used an utility to gain root (KingRoot4.1-release-20150703-for-xda.apk). It did the trick, but now I understand that maybe gaining the root rights it's different from "unlocking the boot". Sigh.
Then I used an utility (Flashify if my memory serves me right), to put a clockworkmod in my TF701.
I got the clockworkmod from a droidbasament link (db-blog/?p=3568).
I selected "boot" when the utility asked me what kind of img I was trying to flash... maybe I chose the wrong type again... However, it flashed the img. But now when I boot the device, I get a Signature Mismatch. Booting failed. Unrecoverable bootloader error (0x00000008), with the ASUS logo.
If I reboot with Power + Vol Down, I can get the fastboot USB download protocol, with the 3 icons in the middle of the screen.
I installed the Android SDK. I tried to take the clockworkmod recovery.img and move it in the tablet with:
fastboot boot recovery.img
but I get:
downloading 'boot.img'...
OKAY [ 0.932s]
booting...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.982s
So... the Bootloader is still locked, I imagine. Can I try to return to a full stock ROM, maybe using the microSD?
I tried to download TF701T_11.4.1.30_WW_Boot_TWRP_2870_signed.zip , put on the microSD, and launched RCK. It starts to install, but after a while I get the error broken droid picture.
I tried to rename the file to T4_SDUPDATE.zip, but I get the same results.
Am I screwed? Any help is welcome. Also, if I can fix the problem, I'll offer you a big beer! (paypal?)