Database Develop

Factory reset after every reboot

Weirdest thing happens, I'll boot my DS7 and it's like if I just did a factory reset...every time. I'll customize my homescreens/gmail and what not, and do a normal reboot and it does a factory reset every time. I've read a few threads about similar topics and no one seems to know what's going on.
I've wiped data/cache/dalvik and fixed permissions, doesn't help. Re-install ROM, doesn't help.
I tried reflashing superuser.zip says installation aborted (bad). Same when I try to flash HC (yes, I'm still on Froyo).
Any clues ladies and genitals? Any help would be appreciated.

Sounds like you are experiencing the READ-ONLY bug that plagues this device. Hopefully it is still under warranty so that you can send it to Dell. Last summer I sent my Streak 7 to Dell. They repaired the read-only bug and had it back to my house in about 2 weeks.
Basically, what happens when your tablet goes into read-only mode... any updates, installs, customizing you do will be lost upon a reset... even though it appears like things are updating, they simply are not saved to the internal flash drive. Also, when it gets really bad some of the apps (along with the web browser) will start to get fatal errors.

That sounds about right, especially since even when I try to move a file from my netbook to the device (such as a new ROM to try to flash in CWM) it wont show up after I reboot either.
Don't think its under warranty anymore, dang.

Yes this is what happened to the one I got off Craigslist too the person I bought it from also changed his phone number instantly, so I got screwed but I'm in the process of getting a replacement or getting an extended warranty on it.
Sent from my Galaxy Nexus using XDA App

[Q] DS7 Unstable keeps crashing

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

Accidental delete of recovery partition. need help on how to put OS android again

I am new and in need of your help in reinstalling an OS for my unit LG P925 3D. I toyed around with the recovery menu and decided to delete the partition with recovery in it. I also deleted several options hoping that I would be able to bring back a malfunctioning OS with regards to creating a gmail account that it always says that my password is wrong.
My laptop cannot detect the phone when connected to USB. All i know is how to hard restart, in which it keeps on making a loop of the AT&T start up. I know it would be hard for me since im a newbie but with your instructions, I will try.
Thanks in advance.
PS. if possible , what will be the best OS android version for my unit?

[Please HELP] Problem with touchscreen - After Twrp install

Hi all,
I downloaded the latest TWRP from https://dl.twrp.me/i9305/ - twrp-2.8.7.0-i9305.img.tar 8.1M
I installed it with ODIN. The flash was a success and when the phone rebooted the touchscreen was unresponsive.
I have tried another version of twrp for this phone and I can get into twrp, but the touchscreen doens't work. I tried replugging in the ribbon lead for the digitiser and that made no difference.
Do you think its a software problem or that I have fried something?
Many Thanks
Andrew

Hi,
there are plenty of issues with TWRP and 2.8.7.0. I'm actually surprised you could even boot up your phone. The new recovery messes up with partition sizes and some other things.
I hope you have a backup of the current ROM as I suggest you to install Stock ROM again and stay on TWRP 2.8.5.0 and see if your phones works normally again

Hi,
thanks so much for replying. I still have the stock rom. All I have done is install twrp. I have tried doing a factory reset and it made no difference. I can still use the buttons on the phone, but the touchscreen remains unresponsive.
So if I download the stock rom for the phone and install you think it might make a difference?
Andy

Update:
Downloaded and installed stock rom from samsung (4.4) ... installed with success via odin. The phone boots and the screen is still unresponsive. I just cant believe I have broken the digitiser by installing twrp?!
Andy

Hi,
sorry for the late reply. I didn't get a notification via tapatalk. But anyway to come back to your issue: it's the first time I hear that a "corrupted" recovery could break the digitizer. I did the same mistake with the broken recovery but fortunately no issues afterwards. But apparently it's possible judging by some google search results.
I never had such issues and I don't know how to help you. Maybe there is a possibility to fix it.

Thanks for your reply
I hope there is a way of fixing it. It doesn't seem economical to fix this phone? The digitiser kit is around £60 ... Plus because I can't be 100% why this happened in the first place, it might happen again with a new digitiser?
Thanks
Andrew

I was looking here in Germany right now what I would have to pay for fixing the digitizer - between £50 and £60 as well, some even charging a little more. For £80 I could get a decent looking used S3 4G.
If I were you I'd rather buy another S3 again (or any other device) instead of trying to fix the broken one.

Did you tried to Flash stock recovery

All help needed, is my note 4 dying ?

Hello.
I have a Galaxy Note 4 SM-N910T2. In january of this year i upgraded it to 6.0.1 (N910TUVU2EQI2) from 4.4.4(N910T2UVU2AOG1) using the SM-N910T firmware for the upgrade, everything was working perfectly but the day before yesterday i wanted to perform a wipe cache because the phone was being a bit laggy. after the wipe cache was perform and i hit the reboot, the recovery got stucked on Verifying DMhash tree. so after 30 minutes i took the battery out and powered on my phone, the problem is: The phone started to freeze, reset it self even the process system crashed. I read that downloading the Wake Lock power management helps and it did but i didn't want to use this app forever so i downgraded back to 4.4.4 it's original firmware, it does run better but now my phone reboots itself and it freezes just a little bit. Also i've got the Process system is not responding do you want to close it?
Things i've done so far:
1- Reflashed 4.4.4, 3 times, i've done wipes before reflashing and after. Nothing
2-Flashed TWRP wiped everything, repaired the file system, Flashed the stock again (4.4.4) nothing.
I'm not going back to 6.0.1.
Do i have to buy a new phone or maybe a new rom with a kernel will help ?

Pigoath said:
Hello.
I have a Galaxy Note 4 SM-N910T2. In january of this year i upgraded it to 6.0.1 (N910TUVU2EQI2) from 4.4.4(N910T2UVU2AOG1) using the SM-N910T firmware for the upgrade, everything was working perfectly but the day before yesterday i wanted to perform a wipe cache because the phone was being a bit laggy. after the wipe cache was perform and i hit the reboot, the recovery got stucked on Verifying DMhash tree. so after 30 minutes i took the battery out and powered on my phone, the problem is: The phone started to freeze, reset it self even the process system crashed. I read that downloading the Wake Lock power management helps and it did but i didn't want to use this app forever so i downgraded back to 4.4.4 it's original firmware, it does run better but now my phone reboots itself and it freezes just a little bit. Also i've got the Process system is not responding do you want to close it?
Things i've done so far:
1- Reflashed 4.4.4, 3 times, i've done wipes before reflashing and after. Nothing
2-Flashed TWRP wiped everything, repaired the file system, Flashed the stock again (4.4.4) nothing.
I'm not going back to 6.0.1.
Do i have to buy a new phone or maybe a new rom with a kernel will help ?
Click to expand...
Click to collapse
All i can say is your phone mmc chip is about to die soon or later you will get mmc_read failure message and your phone wont be able to boot into the system and you won'tbe able to flash anything.
My best suggestion is sell it ASAP.

Trex888 said:
All i can say is your phone mmc chip is about to die soon or later you will get mmc_read failure message and your phone wont be able to boot into the system and you won'tbe able to flash anything.
My best suggestion is sell it ASAP.
Click to expand...
Click to collapse
I came across the mmc_read failure before I realized it was happening and have been researching ways to at least verify there was nothing important on the device before retiring it to Samsung heaven.
Instead of useful advice, everyone seems to be spouting "sell it ASAP" as though it doesn't make you trash as a person to attempt selling it as any sort of working device. The inclusion of "ASAP" and lack of "with a disclaimer" tends to suggest they aren't recommending you actually tell anyone about the issue.
Good advice would be to back up everything you can now and begin looking for a new device. You could attempt to sell it for parts, but make sure to inform people of the situation. If it is that close to failure, chances are it will still be well within the 30 day return policy on most sites and they always favor the buyer. Your device is already ruined, but there is no reason to destroy your reputation with it.