Hello All,
I'm fairly certain there isn't another thread asking this question, if I overlooked it I apologize in advance. Now to the point, I have a dell streak 7 and I have been having some stability issues with it for about the last week. What was happening is I was running Android 2.2.2 and my system would crash randomly eventually it wouldn't start back up. I tried doing a factory restore several times this didn't work so I re-flashed to restore the original file system and I installed the T-mobile system by mistake. I played around with this for a little bit and every thing seemed fine. So I decided to upgrade to 3.2 honeycomb, I flashed the DS7 did all of the set up steps and started reading about rooting the device (I didn't start any of the steps). While it was sitting next to me in sleep mode I noticed it just randomly reset itself and started booting up. I looked around in it and nothing seemed to be changed, so I powered it off and powered it back on to see if it would freeze up and crash again. it didn't so I put it back in sleep mode and kept reading. then the side lights came on and it froze up. I was able to get it to boot by going into recovery mode and then selecting boot normally. So my question is, is this some sort of hardware issue or something that I am doing wrong? I don't think it's hardware but I could be mistaken. Also, has anyone else had an issue like this and if so is there a known fix? I am going to try re-flashing to the original file system again and replace the restore .img and see if this helps. Also, I'm not sure if my DS7 is the mobile version or wifi only version. I entered the service tag at DELL's website and it said I had the mobile version, however it didn't have the t-mobile start up animation before I flashed it the first time and in the sim card slot there is a black piece of plastic or card (IDK which) lodged in there and it wont come out. Any help or advice on this would be greatly appreciated .
Thanks in advance-Woulfenstien
OK I'm pretty sure i got it solved. what I did was I re-flashed everything. I re-flashed the boot.img, the system.img, and the recovery.img using fastboot and then i re-flashed whole system with nvflash. It's been a couple of hrs. and this has seemed to work so far. I upgraded back to 3.2 honeycomb and rooted the device with no problems so far. If any other issues arise I will post them here along with what i did to fix it. I would also like to thank everyone on this forum who has posted the tutorials, it was a huge help I wouldn't have been able to fix my DS7 with out all of your help.
Thanks again-Woulfenstien
Related
Hi,
I have lost the ability to use my internal and external storage memory. Is there anyone that can tell me how to fix this. I am at a loss.
Thanks
Zack Cadieux
I have the same problem after flashing JPH firmware. (I know how to flash FW, I've been flashing every FW as it was released)
It says that there is an I/O error in mmcblk0p1.
I think i'm screwed as well.
Not one person knows what is going on
Hi,
Im supprised that even the dev's know nothing about this issue. I have read almost every thread and nothing to show how to respolve this issue. Is there anyone???
I had the same problem. I have a Bell Vibrant which I flashed to JPH using the Kies method, rooted, then One Click Lag Fix. Things worked for about a day then I lost my storage. Luckily I did the samsung 3 button fix first.
I downloaded the Tmobile Stock Rom, and used the following instructions to flash.
http://forum.xda-developers.com/showthread.php?t=734475
It booted up to the Tmobile Rom, and everything worked. I then used Odin to flash back to JPH.. rooted.. and now am contemplating the Lag Fix.
Not sure if it was related to the problem but I had my phone connected to my computer transferring files before all hell broke loose. I may have yanked the USB without unmounting... Just a thought.
Good Luck..
Dawgplg said:
I had the same problem. I have a Bell Vibrant which I flashed to JPH using the Kies method, rooted, then One Click Lag Fix. Things worked for about a day then I lost my storage. Luckily I did the samsung 3 button fix first.
I downloaded the Tmobile Stock Rom, and used the following instructions to flash.
It booted up to the Tmobile Rom, and everything worked. I then used Odin to flash back to JPH.. rooted.. and now am contemplating the Lag Fix.
Not sure if it was related to the problem but I had my phone connected to my computer transferring files before all hell broke loose. I may have yanked the USB without unmounting... Just a thought.
Good Luck..
Click to expand...
Click to collapse
My situation is about the same. I did the update and applied the root and lag fix. Phone worked fine for a day or so and then it just locked up and couldn't detect the sd cards anymore. I rebooted and it was stuck on the S for over 30 minutes...I flashed HJ2 and when it rebooted all that happens is I get a gray blinking battery if it's attached via USB and if on battery it boots up to the I9000 initial screen and shuts down. Lucky for me the shop will do a swap when they restock in about a week. Back to the HTC for now.
LordSoth said:
My situation is about the same. I did the update and applied the root and lag fix. Phone worked fine for a day or so and then it just locked up and couldn't detect the sd cards anymore. I rebooted and it was stuck on the S for over 30 minutes...I flashed HJ2 and when it rebooted all that happens is I get a gray blinking battery if it's attached via USB and if on battery it boots up to the I9000 initial screen and shuts down. Lucky for me the shop will do a swap when they restock in about a week. Back to the HTC for now.
Click to expand...
Click to collapse
Dont recall if I did any of the Recovery options, but I remember the big Grey Battery... You could even try flashing back to JPH through Odin... It may wake it up. But good to hear they will replace it, at least you have something to fall back on.
Dawgplg said:
Dont recall if I did any of the Recovery options, but I remember the big Grey Battery... You could even try flashing back to JPH through Odin... It may wake it up. But good to hear they will replace it, at least you have something to fall back on.
Click to expand...
Click to collapse
There was another thread I read about this exact same issue happening and the guys had to return the phones in the end. Yea I was lucky I was under the 30 days limit. By the time I get a new one hopefully a proper Froyo build will be out.
hi everyone. i've been following the forum here for awhile and finally decided to root my brand new NC. i autorooted from 1.1. i saw some things weren't working so i quickly decided to unroot back to factory settings. i unrooted by unregistering the device and turning off the power 8 times. my NC boots up fine, but it gets stuck on the "Registering your Device" page and just remains there with the circle spinning. i think i left it there for more than 30 minutes and nothing happens. has anyone experienced this before? if so, how did you fix it? any help would be appreciated.
sorry if this topic has already been asked - i tried searching but didn't find anything on this specific issue. if there's already a thread, please feel free to share the link with me. thank you!
EDIT: really need some help here... i tried to fix it myself (i know i shouldn't have) and might have made it even worse. i tried to re-autoroot my NC but just completely failed. it was not loading anything anymore, so i tried to unroot again by powering off 8 times. when i restarted, everything looked normal, except the bootloader screen was not stock. it brought me back through the normal tutorial and same thing with it getting stuck on "registering your device". could someone please provide a thorough walkthrough on how to reset to factory settings? i'm seeing all these threads throwing around all these acronyms that i don't understand. seems like i need to try running some clockwork rom but not even sure how to do that. please help!!
Bump, i have just encountered this problem and i need help as well.
Update:
actually just figured it out and heres what fixed my problem, i wasn't doing the factory reset part only the 8 reboot interruptions.
hxxp://nookdevs.com/Flash_back_to_clean_stock_ROM
Thanks for your post, even though no one ever helped. I was having the same problem and doing a clear data/factory reset from Clockwork Recover booted from an SD card did the trick for me.
Hi guys,
Gone through about 100 threads these last couple of days, but nothing helps, so have to start a new one.
What happened was that the other day my phone started ringing.
The screen however was black, so I could neither see who was calling nor answer the call.
I let it ring out, then I held the power button so it would shutdown.
Tried to restart it, and that's when the fun started.
The phone got stuck in a boot-loop, only showing the Galaxy S logo (not getting to the animated one).
Left it in this loop for several hours, since I've had problems recently with the phone needing to do this cycle 5-10 times before booting up.
This time it wouldn't boot, however.
I've tried putting the phone in a bag of rice for 18 hours, in case of any moisture inside, not helping.
Then I tried recovery-mode, formatting the whole thing, but I got the following error:
"E:format_volume: rfs format failed on /dev/block/mmcblk0p2"
Found this thread to try to fix the format error.
Got into download mode, but Odin does not recognize the phone, and I started believing all hope for fixing it without sending it in was gone.
I've also tried applying a couple of update.zip's from the SD-card, just to have tried it, but every package got Signature verifcation-error.
Anyway, when I headed to bed last night I left the phone in the boot-loop, and to my surprice, 8 hours later it had booted into first-time configuration.
YES!!!
Configured the phone with language etc., then all of a sudden the animated Galaxy S logo appeared...
And it appeared again, and again, and again for about 15 min., until I unplugged the battery.
And now I'm back at square one, stuck in the boot-loop (not getting to the animated logo)...
I have the latest versjon of KIES, not that it probably matters.
Does anyone have an idea of what the problem might be?
What rom were you using? stock or custom? Maybe it has something to do with lagfix if it was activated... im guesing, im not dev just normal user... Maybe try to reinstal usb drivers.
Just use odin 1.3 reflash official rom , everything would be OK.
Not sure about the ROM, bought the phone used... But pretty sure it's stock..
Since Odin didn't recognize the phone, reflashing it with official ROM would be hard...
However, as for the Odin problem, that was caused by a faulty USB-cable...
Used another one, and Odin worked like a charm.
The phone won't start after running through the steps in the thread I mentioned before, but I will try to reflash it with offical ROM now and see how that works.
mortenlm said:
Not sure about the ROM, bought the phone used... But pretty sure it's stock..
Since Odin didn't recognize the phone, reflashing it with official ROM would be hard...
However, as for the Odin problem, that was caused by a faulty USB-cable...
Used another one, and Odin worked like a charm.
The phone won't start after running through the steps in the thread I mentioned before, but I will try to reflash it with offical ROM now and see how that works.
Click to expand...
Click to collapse
Not sure about used phone, But if I bought the phone used, I would reflash rom first. Because I do not even know what they done before , reflash offical rom would be fix some problem.
porkapple said:
Not sure about used phone, But if I bought the phone used, I would reflash rom first. Because I do not even know what they done before , reflash offical rom would be fix some problem.
Click to expand...
Click to collapse
Well, I would have if I knew... But stupid me thought that a phone was a phone.
How wrong was I?
Anyway, a little update here (the problem is kind of solved now):
Flashed the phone with 2.3.3 Gingerbread I found on dkszone, after running the steps in the previous mentioned thread.
And the phone started like a charm.
But after a few hours of configuring etc, I managed to insert the SD-card again, and all hell broke loose again...
Come to think about it, thats what I did yesterday too, so I've come to the conclusion that the SD-card is the main problem...
However, now the phone is slow... REAL slow... Kind of like my 1.5 year old HTC Touch Diamond 2 with WP6.5...
It takes up to 2 seconds to open menu items, keyboard etc.
Is there any way to fix that?
Or should I flash it with another ROM?
You mean the external sdcard? Maybe try to format it...
OK, so this is what I've now figured out:
The phone is damaged...
It seems that the internal SD has gone AWAL, and internal storage has somehow created itself on the external SD-card, thus the phone crashed when I switched cards...
When trying to format the USB-storage, I receive error: SD-card has been removed
So I guess I have to ship the phone off to Samsung ASAP...
So for awhile I used a droid as my main phone and I flashed countless different roms on it. One day though it just went kaput on me, the led flash started flashing on and off whenever I tried to reboot it and I could not access anything including recovery or boot loader. Eventually the battery died and it would not charge again.
I recently was messing around with it and was able to revive it, would not boot up still but was able to get in the boot loader and eventually sbf it. The battery still wont charge(normally) which tells me at least one issue still exists with hardware. Other than that the phone works fine now on android 2.0. The problem is that I cannot upgrade it to anything higher than that.
The only .sbf I could get to both load and boot up successfully was esd20 anything else would just boot loop indefinitely, after rooting that and trying to go from there anything else also boot looped. I installed every recovery I know of from clockwork to spr to that rzr mod of it but none could flash without the same results(restoring a nandroid of that esd20 still worked though). I've tried different kernels as well to no avail. The first steps I did were an exact procedure that I had done before on the same phone successfully with a 2.2 sbf but now it just wont work.
I don't know if there could be some hardware issue causing these problems though I cannot fathom how when one firmware still works and would appreciate any insight that anyone has as to what may be the problem. Was planning on giving the phone to a young family member to play games on as soon as I managed to boot it back up but I don't want to deal with the compatibility issues with such an old version of android.
Ok so if the answer to this question is already on this forum I searched for a hour and if you could drop me a link that would be great. Last night I flash v10k onto my LG thrill with no hiccups. The only problem is I want to go back to V20p because it changed to a O3D and all I can get is 2g edge service. So this morning I attempted to flash V20p and everything was kosher until it said there was a connection error. "Disconnect phone remove battery..." So i figured I needed to get the phone back into download mode in order to continue. The phone isnt bricked, however, I cant seem to get it back into Download mode to try again. Ive tried everything (that I can think of). Restarted my computer wipe all my phones data... My end goal is to have either v10e or the v20p. So I'm open to any routes to this end. I've read about doing a nandroid backup but all the links are dead. I've already decided I'm going to get the Galaxy Nexus and sell this phone if I can ever get it back to stock or semi stock. This is the second time I've had this connection error the first time it was during the update to GB and that time it bricked it. At the time I thought it was a faulty data cable, however, this time I was using a gold plated gigawire and it still did it... This coupled with the ghost call issue almost costing me my job(the reason for trying to go back to froyo) My experience has been buggy to say the least. Any help at all will be greatly appreciated.
PROlific666 said:
Ok so if the answer to this question is already on this forum I searched for a hour and if you could drop me a link that would be great. Last night I flash v10k onto my LG thrill with no hiccups. The only problem is I want to go back to V20p because it changed to a O3D and all I can get is 2g edge service. So this morning I attempted to flash V20p and everything was kosher until it said there was a connection error. "Disconnect phone remove battery..." So i figured I needed to get the phone back into download mode in order to continue. The phone isnt bricked, however, I cant seem to get it back into Download mode to try again. Ive tried everything (that I can think of). Restarted my computer wipe all my phones data... My end goal is to have either v10e or the v20p. So I'm open to any routes to this end. I've read about doing a nandroid backup but all the links are dead. I've already decided I'm going to get the Galaxy Nexus and sell this phone if I can ever get it back to stock or semi stock. This is the second time I've had this connection error the first time it was during the update to GB and that time it bricked it. At the time I thought it was a faulty data cable, however, this time I was using a gold plated gigawire and it still did it... This coupled with the ghost call issue almost costing me my job(the reason for trying to go back to froyo) My experience has been buggy to say the least. Any help at all will be greatly appreciated.
Click to expand...
Click to collapse
So you want V20P or V10E?
Sent from my Samsung Galaxy S II w/ DUAL BOOT: AOKP / MIUI
I really want V10e if its possible but If not then V20p will work.
I am having similar problems when I try as well. I have tried 5 or six times but tells me something about the b2c not loaded or a connection to the internet. Every time I hit "normal web upgrade test" it throws up a pop up and wont let me proceed any further. It has worked for me twice before, I got the no connection pop up and ignored it, but its not working this time. I set everything up the same from instructions on Acidhazzard rom web site. Please help...
I had to change the port back to 80 and put the orig host file back in the ect file just to download the bc2app then change it all back it worked the first time when i flashed v10k... idk i would delete the lg drivers and everything then start from scratch if i could boot into download mode.
Sent from my LG-P920 using Tapatalk 2
I have been starting...
From scratch. I download the LG flash package and go from there. It does it every time I try. The times I got it to work, I would just hit cancel or OK on the pop up and then hit the OK button I was wanting to hit real fast before the pop up could come back up. I thought it may be a Windows 7 issue (cause I have seen people talk about it) and tried win xp yesterday. Same things happened.
Im running Xp and Im having the same exact thing happen. I got it into download mode finally idk what was going on but now I just keep getting the communications error Ive tried the whole process (each one is like 5 errors) like 3 times now. If it keeps popping up before the update even starts then your probably need to change your small server port from 80 to 9002.
fixed
Somehow after getting the com error 100 times with the flash tool I noticed it had changed my model number back to P925 (I don't know how it did this) I then decided to chance it (after I changed the host file back and changed the port back to 80 and closed the small http server) I went through the LG support tool and clicked start update. After about 20 min of uncertainty during the update and another 5 minutes of self-loathing after getting a bootloop on the at&t screen... I did a hard reset and cleared all data and wah-la... I got it back to V20p. But the flash tool wouldn't flash the v20p for me.. So if I didnt somehow get rid of the P920 model number and back to the P925 model number I don't think it would have worked the way it did.