[Q] rebooting my phone does factory data reset every time - Fascinate General

i had problems playing with dirrk oc kernals, so i ended up having to do the complete odin restore and managed to get the phone back to stock it seemed. but no setting will save on the phone, its like a factory reset every time i reboot the phone. can anyone help? when i did the odin restore i lost root, not sure if that means anything. anyone else having issues like this?

You have zero internal memory and the phone is not saving that you have run it.
Find the "FIXED 0.00 INTERNAL MEMORY" Topic in this forum.
Sent from my SCH-I500-Fascinate using XDA App

One of the steps I took with the zero memory issues that finally fixed my problem was to "factory data reset" in the privacy menu. I went from 0.0 to 1.0 gb memory.
BTW, I went through the 0.0 internal memory topic as well, but found that the above reset fixed it.

I wasn't patient enough when I did that to my phone on day 1. I just swapped it out at Best Buy, haha. Since it wasn't rooted at all, it just looked like corrupt firmware.
I will keep that in mind if I run into that issue again.

thank you for the quick responses. i tried the factory data reset already and still had zero memory. im not quite sure how to go about trying the solutions suggested in the other thread without having root. maybe im just misunderstanding what they are suggesting? or maybe there is a way i can root my phone now even with no memory???

Meh..
Takes less than 10 minutes, and gets you as close to stock as possible while still being rooted. It's not really monumental or earth-shattering.
I'll be the first to admit I was scared as hell the first time I did it.
Yeah..the first time. You think I actually *learned* from my mistake? Well, I did..I just keep making new, more interesting ones.
That *is* the point of Android, isn't it?
Steps:
Using adb, copy original.mbr (from that thread) to your phone.
flash stock.zip through CWM (you should still be able to get into recovery).
At this point, I diverged from the steps in the topic and restored my original stock+root backup as well)
Reboot, wipe data/cache, delete "databases" folder in /dbdata through root explorer.
(At this point I then did the nandroid revert to stock from the forums, updated, and had a nice functional phone again)
How far are you getting?

ok heres everything i have done and i still have no memory. i used the instructions to get back to stock with odin that came from the sticky on how to do everything. it included putting the original mbr on the phone and a few other things, im not so sure exactly what all it did but i followed those instructions to the t. then i had to use odin to get cwm back and i then used cwm to wipe and then tried to restore a backup. the backup restore didnt fix the memory so i wiped again and reflashed the superclean rom, still with no memory. thats where im at now, im too new to be comfortable doing much in adb without detailed instructions

ok i understand your instructions i think now, but i cant get the mbr on my phone using adb because i lost root. thats where i think im stuck

ok now ive got root back it seems but i cant do the adb thing it says to do for the original mbr. it just says "adb: not found" after i type in the cat /sdcard/original.mbr > /dev/block/mmcblk0 part

adb is part of the root zip you used earlier. Just go into the folder you ran start-root.bat from. Right-click on the folder/command-prompt here, should make it so you can use adb:
Adb shell
Such
Cat.....etc.
G/L.
Beamed from my Zinc 1.1 Fascinate (Dirrks D02 LV 1250) OC.

Related

Nandroid Restore not working :(

I haven't used adb cuz i havent been able to set it up. But i have flashed Damaged control succesfully by mounting the zip on the sd card. i flashed it a couple times since ive tried installing Nexus one launcher by flashing from sd card but nothing just messed up rosie. i couldnt restore my older Rom it kept telling me use adb. Fail lol but i flashed damage control 2.05 back and working fine maybe faster. What i want to know is how to get the nandroid restore fixed or working for emergencies.
alt f4 fixes it all
huh? Confused..
he was trying to be "smart" and gave you a bogus answer if you combo press alt + F4 it will exit your screen... Not really sure what your question is though if you are asking as to why your Nandroid won't restore properly it's because you have to "wipe" your cache before doing a nandroid if you are going back to a version that is different than the currently flashed rom. Hope this helps if not then ... perhaps you could re-phrase your question.
~Danny
Rsoehelk said:
I haven't used adb cuz i havent been able to set it up. But i have flashed Damaged control succesfully by mounting the zip on the sd card. i flashed it a couple times since ive tried installing Nexus one launcher by flashing from sd card but nothing just messed up rosie. i couldnt restore my older Rom it kept telling me use adb. Fail lol but i flashed damage control 2.05 back and working fine maybe faster. What i want to know is how to get the nandroid restore fixed or working for emergencies.
Click to expand...
Click to collapse
The only way I fixed that is by running the nandroid restore through adb like it says to do. I don't understand how you don't have adb installed but you have the phone rooted? I had to get all that working to root my phone and having adb is an invaluable tool anyway.
I did read that the nandroid error sometime comes up when the sdcard is too full so you could see if that is the case. Also, as someone suggested you could try a factory reset/wipe and then try again to nandroid through recovery.
richse said:
The only way I fixed that is by running the nandroid restore through adb like it says to do. I don't understand how you don't have adb installed but you have the phone rooted? I had to get all that working to root my phone and having adb is an invaluable tool anyway.
I did read that the nandroid error sometime comes up when the sdcard is too full so you could see if that is the case. Also, as someone suggested you could try a factory reset/wipe and then try again to nandroid through recovery.
Click to expand...
Click to collapse
theres different ways to root your phone lol
The only way I fixed that is by running the nandroid restore through adb like it says to do. I don't understand how you don't have adb installed but
Click to expand...
Click to collapse
theres different ways to root your phone lol
Click to expand...
Click to collapse
Yup,i don't even have a pc (seriously I don't)
I did run into this problem though, not sure exactly what I did but it worked itself out, maybe try flashing a different recovery image,Or try keeping phone plugged into charger(not sure what significance that has but it did seem to go for me after I was having those problems) which recovery image do you have?
Did you rename the Nandroid backup you were trying to restore to? If you did, and the file name has a space in it, it will tell you to restore via ADB. Just a thought from the limited info you provided.
I had this problem and it fixed itself out and all i did was wipe everything thats under the wipe option in recovery and it worked for me.
Yeah it was actually the cache you guys were right. i did it on my own and thought that might be it. and now i know that was it from checkin the thread. yeah i used pre kitchen to auto root my phone. im actually running damage control 2.05 now the newest sprint leak.damn i love it lol. but imma reflash it cuz i tried to flash a nexus theme/ no luck i want a nexus one interface!!!!!

0.00 internal memory, not Voodoo related

So I tried installing the new ASOP rom, and was getting a bunch of force closes. I tried using CWM to revert to a previous backup, unfortunately the force closes continued in the backup. So I want into ODIN to get back to stock. I loading the stock files, did a factory reset, and everything seemed to be fine. However when I went into the market to reinstall appbrain and get my programs back, I kept getting an Out of Space error. I checked the internal memory and sure enough it says 0.00.
I've never installed Voodoo on my phone, because I was trying to avoid issues just like this one. I read over the a similar thread on this issue, but that fix isn't working for me. I tried to reroot, but the SU apk's don't have any place to go, since the phone says there is 0 internal memory.
Luckily I can still use my phone, but every time it turns off it resets, and I can't load my apps back on. Anyone got any suggestions?
The fix should still work for you. I would suggest flashing stock rom, kernel, pit, and cwmrecovery thru odin. After that you can follow the instructions posted on how to completely remove voodoo. Main thing is you need to get the original mbr to your phone.
Well he said he never installed voodoo so he shouldn't have to go through the steps to remove something he never installed in the first place
Sent from my SCH-I500 using XDA App
ckochinsky125 said:
Well he said he never installed voodoo so he shouldn't have to go through the steps to remove something he never installed in the first place
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Hmm I read that part too, but if he follows adrynalyne instructions he should be fine. It is taking care of the same problem. Corrupted rfs. The op just achieved it in a different way. If that does not work for him then maybe some dev will be able to figure out another way to fix the problem.
I'd be curious to see mount results.
Run it from adb shell.
So the short story is I fixed my phone, from force close and zero memory hell.
I noticed when booting into recovery I was getting an error related to /dev/block/mmcblk0. I used the adb code to install the MBR file. Went in CWM and flashed the stock.zip kernel, restarted and got a ton of force closes. Went to the "How to escape the force close loop of hell" thread over at androidcentral, flashed the stock nandroid image, and someway, somehow the android gods took pity on my poor soul and my internal memory partition was restored.
I don't understand exactly how I fixed my phone, and I'm relatively new to this so I'm a little concerned. I'd like to learn from these mistakes, so does anyone understand what I did to fix my phone?
Sounds like it was the nandroid image that did it.
It is, effectively, the same issue the voodoo users have seen.
My "easy" fix was almost exactly the same as yours.
replace mbr, flash stock, revert to backup (which is basically what nandroid is).
I used my original CWM backup instead, and that worked for me. (I now have this stored on several drives/devices)
I also went back in to Root Explorer and nuked the "databases" folder in /dbdata and then wiped cache/data (CWM, then "settings"). Pretty much fixed it all for me.
Couldn't update to D101 for some reason after that, but the unsigned apk for that did the trick nicely. I suppose I'll have to retry the "odin to stock" bit if the 2.2 update fails the same way on me. Not looking forward to that one...

Phone Totall Messed Up

Ok I had my phone rooted and had voodoo on it. The phone was having issues downloading from the market, plus I couldnt turn the phone on unless i had it pluged in. So I tried to reset it using odin and the Stock-i500-VZW-Recovery.tar.md5. Now when I turn the phone on i get the android application has an uxpected error and I cant get past that. What do I do? Or how can I get my phone back to stock so I can re-root it.
Jeff5886 said:
Ok I had my phone rooted and had voodoo on it. The phone was having issues downloading from the market, plus I couldnt turn the phone on unless i had it pluged in. So I tried to reset it using odin and the Stock-i500-VZW-Recovery.tar.md5. Now when I turn the phone on i get the android application has an uxpected error and I cant get past that. What do I do? Or how can I get my phone back to stock so I can re-root it.
Click to expand...
Click to collapse
Jeff,
See this post for returning to stock http://forum.xda-developers.com/showthread.php?t=782204. I would do this as a last resort only.
Good Luck!
that is what got me to this problem. there are multiple files there what one do i use?
You apply them in the order they are listed.
1. Apply the "/system" file first
2. Apply the "kernel" file second
3. Apply thie "recovery" file third
This restores stock /system, the stock kernel, and the stock recovery. Pretty much brings you back to stock. Is that what you're trying to do?
I was having the same issues with USB cable looking like it was plugged in so I couldn't reboot unless it was plugged. I tried the voodoo uninstall and screwed up my data partition.
I ended up restoring the CWM_Kernel and Di01 Stock update which brought me back to stock with root and OTA update from Verizon BUT my Data partition is screwed and I have no internal app memory. Also, I have an Nandroid backup that I tried to install but that causes the FC issues that you mentioned. My guess is that my nandroid backup will work once I fix the data partition.
Later tonight, I'm going to try to put the stock MBR back onto the phone which I think you need to do as well.
However, it sounds like you didn't complete the whole recovery process and only applied one file. I'm an android newby so you can't take my advice to the bank but I think you need to restore all the files if you're going to flash with Odin per those instructions.
For me, I had CWM loaded so I just wiped the kernel and put back the DI01 ROM which put me back to stock albeit with some work to do to get my data partition back in shape. I hope this helped, for what it's worth.
Since you've already got the original.mbr copied and the stock.zip flashed...
Boot into CWM recovery and wide data/cache.
If you have a CWM backup of your phone in a rooted state, restore that backup through CWM.
Reboot, and go into "settings" if possible at this point, and factory reset.
This got me back from market failure/0.00/fc hell after utterly failing to heed the voodoo warnings and trying to revert to stock without undoing the lagfix.
You'll likely need to use the unsigned d101 apk if your backup/flash is dh12. The OTA update did not work for me at that point.
phispher said:
You apply them in the order they are listed.
1. Apply the "/system" file first
2. Apply the "kernel" file second
3. Apply thie "recovery" file third
This restores stock /system, the stock kernel, and the stock recovery. Pretty much brings you back to stock. Is that what you're trying to do?
Click to expand...
Click to collapse
My question is do i use the phone. pda or csc buttons for these files?
Ok in Odin use the PDA button for the /system
but what button do i use in odden to load the kernal.tar and recovery.tar
i loaded the pit, and installed all the files using the pda button one after the other. now my phone get no service and it still isnt wiped. what is going on? how do i get the phone back to out of the box condition.
also, now i cant do a factory wipe/reset, im getting the error message Can't mount /dev/block/mmcblk0p1
Gotta do the mbr fix from the 0.00 internal memory topic and then restore nandroid recovery.
Oh, and it is PDA for all three files, not just system.
Sent from my SCH-I500 using XDA App
i have the same problem n i havent had a phone for a
week...whats the fix??? did u fix urs??
trapstarr56 said:
i have the same problem n i havent had a phone for a
week...whats the fix??? did u fix urs??
Click to expand...
Click to collapse
Use the uninstaller form Here:
http://forum.xda-developers.com/showthread.php?t=804784
If that does not solve it, follow the steps here:
http://forum.xda-developers.com/showthread.php?t=782204
Read all pages of each topic completely prior to initiating *either* of them.

Removing encryption on Galaxy Tab

I encrypted my 10.1 yesterday without thinking all the way though. I found out that I could no longer flash kernels while the tablet is encrypted, since the SD card is not accessible in CWR.
I've tried doing a factory reset on my tab and each time, it boots up like nothing happened. I've also tried removing the pin that I put on it and the option to remove it is grayed out.
Do any of you know of a way to do a full wipe on the 10.1? Or could I reflash it using ODIN?
Thanks in advance.
id like to know this as well
still nothing? im starting to think this is an easy fix that nobody has posted about yet
there has to be something that im missing
try post # 6 in the linked thread, restore with unmodified vanilla version image from second link provided in the post, after booting from fastboot into recovery with clockworkmod recovery img; pushing it into the device sd with adb commandline, check the post for modifications and the link for details.
http://forum.xda-developers.com/showthread.php?t=1161325
whenever i try to reset to factory defaults, it just reboots like nothing happened
re-flash a stock firmware via odin as tar or fastboot/nandroid as img (backup restore)
Ones the tab is encrypted, there's no way to un do it. Unless you do what mughalgxt suggested. Good luck
Thanks guys, I went through some of these steps and found some other good tutorials to get me back up and running. All i wanted was to try the new kernel/bonsai rom out and I'm now able to do that
**** encryption, put a lockscreen password and be done with it.
I'm still struggling with this, as well: off to read some of the linked threads, because even with flashing a stock image with ODIN I'm still not able to recover the device. At least I managed to proceed past the boot loop I WAS in (when attempting to flash from CWM) - but now, I can get to the point where the device prompts me for the decryption key (meaning, it's clearly not yet restored to factory defaults) - but can't get it boot to completion. I also note that I've still got CWM Recovery, not stock.
It seems, at some point, encryption-key be damned, right? Meaning, if I don't care about recovering the contents of the encrypted partition - surely these low-level tools have the ability to simply format the partitions? Perhaps not - at least, not CWM - as attempts to format /data continue to fail.
Off to review the linked threads to try to gain some additional insight.
I ran into this same issue a long while back. As I recall (and it's been a while), you won't be able to wipe from CWM, but you can wipe from Settings / Privacy / Factory Data Reset. I could be wrong, but I know that I didn't have to do any adb pushing or anything with special images.
Hi SacTilt-
Thanks for the reply - and agreed: Had I actively started the effort from a functioning device, I think I could have selected that option.
As it turns out - I ran CWM, rebooted into recovery, and... next thing I knew, I was in boot loop hell.
I've tried flashing a variety of files via ODIN: Some at least allow the device to boot to the point where I get the initial password prompt - which I can provide, and proceed past... but then the device just 'goes blank'.
What I'm looking for is a 'start-from-scratch', no concern for data loss, delete the dang encrypted /data folder already, will ya?... approach.
As I've mentioned, a variety of ODIN files from a myriad of sources haven't seemed to quite do the trick. I feel like I'm missing something obvious - but can't find the right angle to spot it.
Perhaps fastboot might be what I'm looking for?
FWIW: the device was rooted when I started, so I've got full Titanium backups, with which I can restore, once I recover the actual device / OS.
Thanks for any insight.
Hey guys...if anybody finds a solution to this, please let me know...I am stuck with this same damn experimental ROM I've had from day one...it's getting really old. All I want is to get rid of this stupid encryption. Thanks for any help. Tried ODIN flashing, wiping data from security screen, wiping from CMR, etc.
Have you tried formatting the sd? Whenever i had my ns4g i accidentially did the same thing and i wiped the SD and it removed the encryption.
Sent from my GT-P7510 using XDA Premium HD app

recovering data from download mode?

A coworker of mine installed the OTA update Verizon was pushing down, after rebooting the phone was stuck at the Samsung logo.
We can get the phone into download mode, but recovery errors and none of the buttons respond. (Similar to this thread)
If need be I can take a screenshot or type out the error text he receives trying to go into recovery (stock)
A little more info i can give as is: his phone is stock rom, but I do believe he has it rooted.
I have flashed roms onto my phone (Captivate) so I am familiar with working with Odin, but the problem is that he has data on the phone he needs to recover.
ADB does not recognize the phone, but his computer does seem to detect it.
Does anyone have any advice on getting something to recognize the phone so we can pull data, or is there a rom/setting that would leave his data as is?
If you odin a rom or even flash a rom it doesnt touch any of the data on the SDcard. he will loose call history and sms history. Pictures and things will be left on the sdcard untouched.
This is the most complete and up to date guide for the fassy:
http://forum.xda-developers.com/showthread.php?t=1238070
Thanks for the heads up.
Just to be clear we are talking about the internal SD card right? Not the removable one.
He is apparently mostly concerned with losing his app data. As long as that will be safe I can have him up and running in a matter of minutes, especially with your link.
NO app data will be gone as well
What rom did he have or was it stock?
when i said the sd card i was referring to the removable one.
I figured that was the case
He is running the stock Froyo rom.
Would it be possible to use Odin (or some other tool) to push CWM onto the phone and maybe get it to mount from there?
He did say Odin recognizes a device when it's plugged in.
You may be past the point of no return. Since the phone is boot-looping and not actually booting up there may be no way to root the phone to flash CWM.
Odin is unfortunately a one-way street. Its designed to flash data ON to the phone, Not pull data off.
the phone does not have to be rooted to odin cwm....that being said, op try odining cwm2.5.1.x red and three finger into recovery, wipe cache & dalvik, then go to my guide section 1, use ccampos powerwashed ed05 froyo. That rom is close enough to what stock froyo is, so it might work! Or you can try geewiz froyo also, but one of those might get the phone back up and running without completely wiping everything.
just fyi once you odin a full rom all app data is gone. I have never attempted to pull app data from the mounting of the internal memory using cwm.
xwhofarted said:
just fyi once you odin a full rom all app data is gone. I have never attempted to pull app data from the mounting of the internal memory using cwm.
Click to expand...
Click to collapse
Thats why I suggested to try and flash a close to stock froyo rom in cwm without wiping data. odin will do a full wipe, so thats his only option that I am aware of.
Could he odin a recovery, make a back up, flash a new close to stock rom, advanced restore data? It would probable have alot of issues but may give him the opportunity to make a backup.
mentose457 said:
Could he odin a recovery, make a back up, flash a new close to stock rom, advanced restore data? It would probable have alot of issues but may give him the opportunity to make a backup.
Click to expand...
Click to collapse
my co-worker had something similar happen and this is what I had him do. It didn't fair too well but it was worth a shot.
Ended up using odin to push a stock verizon rom and started over. Then I MADE him put cwm on his device and make a backup immediately incase it were to happen again.

Categories

Resources