right after hours of trouble shooting and trying different things yesterday i have come to the conclusion that my sons galaxy s i9000 will not wipe its memory in anyway at all, now i believe this could be down to the fact he has a virus on the phone of there is some software problem with the phone, has anyone ever had this problem or no a fix for it please, i have tried a few recovery roms now to no joy and tried flashing through odin but nothing seems to wipe the memory anymore.
thanks in advance
So I assume that
A.) The Factory reset setting under "Security" in Settings didn't work, and
B.) Wiping through recovery (no flasging, just wipe data and cache) didn't work either?
Unless you're going from 4.x.x to 2.3.x, flashing roms throuh Odin won't wipe data. If you're flashing a Gingerbread rom over another Gingerbread rom, no data is lost.
Same goes for recovery. If you're flashing roms through recovery, especially of the same version number, no data is lost.
Note that going from ICS to JB will wipe data automatically.
Sent from my GT-I9000 using xda premium
I don't know what rom you are using but you can try install gb with odin using pit file for the repartition to take place.
Did you already followed and tried all the things from your last thread? Especially the additional advices from @wGRV and @popic_u (just posted above), which are btw also mentioned in the HowTo in the rescuepack? And why is a new thread necessary? Just wondering . If you do the restocking via odin propper, with a 3 parted rom and with pit file and Re-partition ticked, as mentioned, then I should work...I never had a problem with restocking and following these steps.
rodman01 said:
Did you already followed and tried all the things from your last thread? Especially the additional advices from @wGRV and @popic_u (just posted above), which are btw also mentioned in the HowTo in the rescuepack? And why is a new thread necessary? Just wondering . If you do the restocking via odin propper, with a 3 parted rom and with pit file and Re-partition ticked, as mentioned, then I should work...I never had a problem with restocking and following these steps.
Click to expand...
Click to collapse
yep sorry about new thread, yes i tried all of the above and the rescue packs and nothing seems to be working on it at all, i myself have a galaxy 2 and never have come across any of the problems when flashing a new rom even from going to ICS and JB, it seems the internal memory can not be wiped at all so making me think its a problem with the phone its self, thank you guys for all your help so far its been great.
Related
Hi,
I have a Samsung Galaxy S i9000 from Switzerland that is unusable due to ESET Mobile Security locking me out of the phone. It boots up fine, but then requires a password before allowing access to the phone's functions.
Swisscom was kind enough to disable recovery mode and download mode for the Android version I have (2.2.1), which is silly because it worked on the previous version.
Anyway, I have some pictures and other data on the internal flash on the phone that I would like to save. Is this possible?
I purchased a USB Jig and it works; I can see the phone in download mode.
Any ideas how I can proceed?
Further, I understand that Odin 1.83 is the version to download for this phone. Is there any official download website of Odin? My virus scanner whined about one download that I attempted and I want to make sure I'm getting something safe.
Info: I'm a pretty savvy guy in most things so, I can take some links to other pages if that's all that is needed.
Thanks a lot.
Best,
C
Sammobile.com and http://forum.xda-developers.com/showthread.php?t=1102881 is the best places to get stock roms.
By data and pictures you mean the internal sd card. The system partition which may contain the settings and data for apps will not be recoverable by this method.
If you odin flash either with re-partition (which is probably what you will need to do) you will loose all apps and data on system partition. NOT the pictures or data on internal sd card where the pictures are stored. So downloads will also not be lost.
Odin should be with whatever firmware you download from sammobile where as the other xda thread link im not sure.
Flashing the firmware will lose data like contact info, calendar and so on too. Pictures will be fine. Not sure if you can save those (maybe try connecting to kies and see if you can export?)
Might want to see if there's a way to undo the eset lock thing.
Thank you very much to Talon26. The links to the XDA site are what got me up and running. I used Odin v1.82 from that page for the following:
I flashed it to the 2.2 Froyo version with a repartition w/ PIT 803 and it kept looping on reboot.
I flashed it to 2.3.6 w/ PIT 512. Same thing.
I flashed it to 2.3.6 without the PIT, but with everything else the same. Same result.
I then used the three button salut (Home, Power, Vol Up) and to my surprise, it worked. I wiped cache and user data, etc.
Next reboot, Bingo.
User data was gone, which I' wasn't concerned about. It was the flash card data I wanted and it is still there. Awesome!
Note, this phone was lagfixed also when this ESET thing happened, so this appears to be a remedy if the phone has a lagfix on it and something strange happens.
Version: latest Gingerbread 2.3.6 European version for GT-i9000.
Anyway, thanks very much for your time to respond Talon26 for the working process and thanks to nwsk for the heads up on user data.
Best,
C
Hello all,
Yesterday I wanted to try the Kingdroid V2.1 + GS3 addon. After installing, everything OK but no addon on the Note so I decided to go back to my good ol
GB Rocket Rom v23.
As the kernel was reported as safe, I did a full wipe and tried first to install my latest backup. --> Dodn't work.
I tried to wipe again to install zip from SD --> Wipe didn't work neither
I tried to install a stock rom KJ1 via ODIN --> Stuck at the end of Nand write start!!
Could anybody tell me what to do next?
Thanks a lot.
May be a case of Superbrick
BruXav said:
Hello all,
Yesterday I wanted to try the Kingdroid V2.1 + GS3 addon. After installing, everything OK but no addon on the Note so I decided to go back to my good ol
GB Rocket Rom v23.
As the kernel was reported as safe, I did a full wipe and tried first to install my latest backup. --> Dodn't work.
I tried to wipe again to install zip from SD --> Wipe didn't work neither
I tried to install a stock rom KJ1 via ODIN --> Stuck at the end of Nand write start!!
Could anybody tell me what to do next?
Thanks a lot.
Click to expand...
Click to collapse
Your post is slightly unclear. Can you please specify from which kernel you wiped the first time?
Kingdroid V2.1 used an unsafe LP8 Kernel. In that case you might have a superbricked phone on your hands. In that case I'm very sorry for you.
Now I cant find Kingdroid 2.1 anymore, it seems to have been taken down.
Hello all,
The Kernel version was indeed LP8! I should have used odin and not wipe
it at all...Sh**!!!!
After trying to restore KJ1 via ODin it failed and now my Note shows
a smartphone + yellow triangle + computer and saying Firmware encoutered an issue. Please select recovery mode in Kies & try again. When doing this I can't find how to recover with Kies.
Superbricked or not?
Do I have any chance to get it fixed in a Samsung Service Center?
Could I say that I was doing a firmware update and that is got stuck or do they have a way to see that I was actualle flashing?
Any idea of what this could cost me?
Thanks guys,
Bruxav
Try getting it to a service center and just tell them that upgrading via kies fooked your phone.
This problem started increasing because of Kingdroid V2. and bad guide on installation of the ROM.
I hope Samsung Service Center is the only solution for it.
I too have tried to use Kingdroid V2 rom and my samsung note is gone now.
for getting little things we wasted a lot time, and we are now paying money to get it to its original condition atleast.
Lesson Learnt is Never ever Root or try any S**t Rom. speciall on Samsung handset.
was good enough to do everything in HTC
I also bricked my device with KingDroid and don't seem to be able to recover. I even tried to repartition from ADB, but I get input/output errors, which means the emmc is corrupted, from what I can understand.
Really sad to hear that. How did you go abot to brick it?
That could be valuable info for others.
I found a threat on this forum and as far as I understood, the kernel I had LP8 was not listed as dangerous (might be misunderstood by myself)
I did install Kingdroid 2.1 without any problem and then the S3 mod too. After rebooting it worked smoothly but had no Svoice or any S3 specs. So I decided to get back to RocketRom V23 wich is to me the best (Quick, smooth, batteryfriendly) I've tried so far.
As I thought Kingdroid was safe I did what NO ONE SHOULD DO...wipe it and there began the sh*t!
I tried installing a KJ1 stock rom this morning using Odin but it got stuck at the end of the process. When I unplugged it said ther had been a problem installing software. As requested I tried to restore with KIES but it didn't recognize the device.
Finally I brought it to the service center saying I got stuck trying to upgrade the software with official release in Kies.
Let's just hope they won't be able to restart it and get to know it was rooted and flashed a dozen times
THanks anyway for all your messages, answers and tips.
See ya,
BruXav
Best of luck to you. Please tell us how it went
Also got bricked today. Also going from Kingdroid 2.1. I'am trying to get on stock rom,but not suceeded yet (sorry for bad english )
Do you have some news from Samsung Service Center?
Hi guys,
Here I am, two weaks after my initial post. My SGN just spent two weeks at the local service center. At least I bricked it so good that they couldn't realize that I had rooted and flashed my Note.
So, I got it back after a mainboard swap!
Thanks for your helpful posts and information!
BruXav
I'm glad you got it back.
have bricked my phone one month ago
tried everything no joy
finally contacted my insurance and they sorted out for me.
Hey guys;
Started on Aussie firmware. Flashed to rootable UK GB, but the thing updated to the new ICS, which I know has an unsafe kernel.
I then rooted using dr.ketans method, and I also installed clockworkmod.
Since the kernel was unsafe, I then reflashed the UK rom and tried to skip the ICS update (no luck), but when it installed everything kept FC'ing.
I did NOT perform any recoveries or wipes!
I flashed to a generic, prerooted GB, but everything kept FC'ing. I couldnt access anything. I then flashed back to stock Indian rootable GB, which didnt auto upgrade to ICS. It was fine until I turned the phone off then back on, but now it is doing the same FC thing as the prerooted rom.
So far, I have only used PC Odin (using the single PDA mostly). I also havent performed ANY wipes (I still have all of my contacts and apps from the original Aussie stock). I stuck to Odin because I was told the eMMC bug from my faulty ICS wouldnt be triggered.
I guess the FCing has something to do with not performing a wipe and changing the firmware like 10 times. Unfortunately, I cannot access the *#1234# because the dialler wont work at all.
Bottom line: If I am on stock GB by flashing through Odin, is there still a chance I have an infected kernel? Also, I imagine my best way out of this would be flashing the prerooted ROM and performing a wipe, before moving to something like Paranoid?
Jesus Christ.
Thanks guys,
Vincent.
Edit: Settings is telling me the kernel version is KL3. Guess its safe?
Only official ICS kernels are affected by the emmc bug so unless you are on a LP* rom/kernel you're safe to do a wipe/factory reset. It will most likely solve all your fc problems.
VincentRC said:
Hey guys;
Started on Aussie firmware. Flashed to rootable UK GB, but the thing updated to the new ICS, which I know has an unsafe kernel.
I then rooted using dr.ketans method, and I also installed clockworkmod.
Since the kernel was unsafe, I then reflashed the UK rom and tried to skip the ICS update (no luck), but when it installed everything kept FC'ing.
I did NOT perform any recoveries or wipes!
I flashed to a generic, prerooted GB, but everything kept FC'ing. I couldnt access anything. I then flashed back to stock Indian rootable GB, which didnt auto upgrade to ICS. It was fine until I turned the phone off then back on, but now it is doing the same FC thing as the prerooted rom.
So far, I have only used PC Odin (using the single PDA mostly). I also havent performed ANY wipes (I still have all of my contacts and apps from the original Aussie stock). I stuck to Odin because I was told the eMMC bug from my faulty ICS wouldnt be triggered.
I guess the FCing has something to do with not performing a wipe and changing the firmware like 10 times. Unfortunately, I cannot access the *#1234# because the dialler wont work at all.
Bottom line: If I am on stock GB by flashing through Odin, is there still a chance I have an infected kernel? Also, I imagine my best way out of this would be flashing the prerooted ROM and performing a wipe, before moving to something like Paranoid?
Jesus Christ.
Thanks guys,
Vincent.
Edit: Settings is telling me the kernel version is KL3. Guess its safe?
Click to expand...
Click to collapse
As chasmodo said that wiping in gb again and again even your arse it will not bricked your phone. If you use the latest mobile odin there a data wipe you can check before it install a new rom try it.
Probably. Non wipe gb rom, leaving many ics stuff that messes gb up.
Migrating from ics to gb, go search on that
Sent from my GT-N7000 using Tapatalk 2
I am assuming you did clear cache and dalvik cache before installing a new rom, that's OK, just not to format system or do a factory reset if you are using a kernel that suffers the emmc problem...
If you don't clear cache and dalvik cache then you will have fc's...
Hey guys:
Ended up flashing Abyss, wiping everything, then CWMing paranoid. All good now.
You guys are terrific, I guess this can be locked now? Thanks again!!!
Sent from my GT-N7000 using xda app-developers app
What's good, chaps? This problem is currently on Overcome 4.1.0--beautiful ROM.
So what had happened was......
My Tab's WiFi worked perfectly, until yesterday (from the time of this post). Before this problem occurred, I had tried to flash a file I though would be useful for the Tab. The file sent my Tab into bootloops, and I scolded myself for not having made a nandroid.
I decided it'd be a good chance to try another ROM.
I eventually lighted on MIUI v4. I liked it for 5 minutes, then wanted to go back to Gingerbread (Overcome). I read that the MIUI ROM was an MTD ROM; I have no idea what that is, heh.
The only way to return to Gingerbread was to use Odin, so I did that. I followed every instruction on flashing the Overcome ROM to the letter. The installation went smoothly....until I found out my WiFI is broken. In fact, the baseband comes up as unknown--that never happened before. The Tab was getting a cellular signal, but that was it. I tried to reinstall the modem using Odin--no good. I tried using the fix from the Overcome Thread--no good.
I don't know what's wrong or what to do next.
If anyone can help me shed some light on this, it'd be greatly appreciated!
Thanks in advance!
I don't know why most people will try to fix their broken tab using overcome rom, find it broken but didn't tell how it was when it was merely on SG-stock-safe-v5
remember, Gb-stock-safe-v5 is Gingerbread from Samsung, JQ1 rom, in fact.
If it is broken at that stage, it is an entire different story than if it broke under Overcome ROM.
So which one is it?
Sorry for my late reply!
I found out it was broken when I reflashed the Overcome ROM. I never tried WiFI when I flashed GB-Stock-Safe-v5, so I can't tell you anything from there.
Did I do the right thing in using Odin, when downgrading from ICS 4.0.4 to GB 2.3.6?
No idea. But re-do the GB-stock-safe-v5 again and see how it goes.
If all good, add overcome kernel, see again how it goes.
if all good, flash overcome rom, and then see again.
Be methodical when you want to find your root cause.
Alright, I'll give it a go. Thanks for your help!
For the record, does downgrading from flashing a ROM with a different partition set-up have to be done a certain way?
just need a rom that has pit file and you tick the repartition in Odin.
That should take care of the downgrading from MTD rom
Followed your instructions and everything is back to normal!
Thanks again!
priyana said:
just need a rom that has pit file and you tick the repartition in Odin.
That should take care of the downgrading from MTD rom
Click to expand...
Click to collapse
tried every thing. flash froyo, flashed ginger. flashed Overcome's. flashed other roms like Boca or Miui.
but nothing can bring back the wi-fi even tried overcome's wi-fi fix and wpa-supplicant with proper permissions bla bla bla...
the tab was working fine before and was on overcome's last rom. but suddenly if wi-fi switched on, tab started giving constant re-starts.
do you think it's a hardware issue now? i flashed 2.3.6 stock on which it doesn't give restarts but wi-fi keeps scanning and switching off by itself.
3G works fine no issues at all.
please someone tell me if there is any thing that i'm not trying.
Yours sounds like hardware issue.
Sent from my GT-N7100 using xda app-developers app
Hello guys
Ages ago I gave my i9000 to my brother, then years later he gave it to my sister. It is uber sluggish, though running CM10.2, so I wanted to flash CM KitKat... by wiping the crap out of it, reformat, repartition, do whatever I can to get it as optimised as possible for KitKat.
The problem is, I have no idea IF/What lagfix I applied years ago, and have a hunch I would have to UN-lagfix it before installing another OS...
So the big question is, IF I do a ODIN flash to a stock rom would repartitioning using PIT file wipe everything in such a way as to remove any lagfix I may or may not have had? What about possible reformatting to EXT-2/4 I may have done back then?
Does it matter that I cant remember what I did?
Help much appreciated,
Tx
Mark
fredphoesh said:
Does it matter that I cant remember what I did?
Click to expand...
Click to collapse
it will matter, so use this app to check your system is in its default rfs format, after that you can use this guide to flash and resolve problems too
Check this out! Links to useful Guides and " Banned " Documentaries
xsenman said:
it will matter, so use this app to check your system is in its default rfs format, after that you can use this guide to flash and resolve problems too
Click to expand...
Click to collapse
Thanks Xsenman, I will definitely install that app and make sure I have the partitions back to nfs... From there I am pretty ok... will use stock gingerbread, PIT 512, CWM & ROOT then KitKat & TWRP... cheers for the help,
Mark.