Hey XDA, I was hoping you could help me out here. I just don't know what to do anymore. So, here goes.
I decided to flash the Terrasilent kernal. All went well during installation. When I booted back into the stock rom after flashing my kernal, I saw that some system apps (gmail and market) were not installed. The icons were there, but they said they weren't installed. Also, all photos, videos, ect were gone. I already had them backed up, so no big deal. So, to try to fix it, I went into Odin and tried to reflash my stock rom through there. Everything worked fine, all was well. That's when I discovered my file system was messed up. Pretty much, it only displays /sdcard/Android, as well as /sdcard/DCIM/, /sdcard/LOST.DIR/ and /sdcard/external_sd/. So, I went ahead and attempted to reflash my kernal (custom kernal, terrasilent if you want to know.) to see if it would fix my ****. **** was not fixed, to say the least. And when Odin said it failed, I flipped out and did the stupidest thing imaginable; I unplugged my USB cable. So, I went and tried to boot up, and got the picture you get when you can't go into recovery, boot up or even download more. A cell phone connecting to a pc picture. So, then I tried following some guides on XDA to fix it, reflashed some stuff, and got close to fixing it. I reflashed my partition table and then tried to flash my terrasilent kernal once more, and it booted up into recovery with no issue. Btw, the kernal installs CWM recovery. But when I tried to reflash my stock rom, it didn't boot up. It said in Odin that it succeded, but in the recovery (which changed back to stock android recovery, I am not sure why) and I got a bunch of errors saying I'm missing all sorts of files. Like, E:failed to mount /cache (invalid argument) or E:copy_kernal_file :: Can't open /cache/recovery/recovery_kernal.log. XDA, please help me. I need this fixed, I can't afford to buy another phone, I'm broke. Help me.
DarkMuffin Inc said:
Hey XDA, I was hoping you could help me out here. I just don't know what to do anymore. So, here goes.
I decided to flash the Terrasilent kernal. All went well during installation. When I booted back into the stock rom after flashing my kernal, I saw that some system apps (gmail and market) were not installed. The icons were there, but they said they weren't installed. Also, all photos, videos, ect were gone. I already had them backed up, so no big deal. So, to try to fix it, I went into Odin and tried to reflash my stock rom through there. Everything worked fine, all was well. That's when I discovered my file system was messed up. Pretty much, it only displays /sdcard/Android, as well as /sdcard/DCIM/, /sdcard/LOST.DIR/ and /sdcard/external_sd/. So, I went ahead and attempted to reflash my kernal (custom kernal, terrasilent if you want to know.) to see if it would fix my ****. **** was not fixed, to say the least. And when Odin said it failed, I flipped out and did the stupidest thing imaginable; I unplugged my USB cable. So, I went and tried to boot up, and got the picture you get when you can't go into recovery, boot up or even download more. A cell phone connecting to a pc picture. So, then I tried following some guides on XDA to fix it, reflashed some stuff, and got close to fixing it. I reflashed my partition table and then tried to flash my terrasilent kernal once more, and it booted up into recovery with no issue. Btw, the kernal installs CWM recovery. But when I tried to reflash my stock rom, it didn't boot up. It said in Odin that it succeded, but in the recovery (which changed back to stock android recovery, I am not sure why) and I got a bunch of errors saying I'm missing all sorts of files. Like, E:failed to mount /cache (invalid argument) or E:copy_kernal_file :: Can't open /cache/recovery/recovery_kernal.log. XDA, please help me. I need this fixed, I can't afford to buy another phone, I'm broke. Help me.
Click to expand...
Click to collapse
I believe what you need to go is go into the android recovery by holding volume up + power. Once you get in there Wipe data/factory reset, and Wipe cache Partition because I believe it's bootlooping.
obscuresword said:
I believe what you need to go is go into the android recovery by holding volume up + power. Once you get in there Wipe data/factory reset, and Wipe cache Partition because I believe it's bootlooping.
Click to expand...
Click to collapse
It didn't work. What do I do now? I tried to flash the Terrasilent kernel over it (which came with CWM) and it gave me the CWM recovery and kernel, but still nothing works. I tried reflashing the rom too but I can't get it to boot, just download mode and recovery loads now.
DarkMuffin Inc said:
It didn't work. What do I do now? I tried to flash the Terrasilent kernel over it (which came with CWM) and it gave me the CWM recovery and kernel, but still nothing works. I tried reflashing the rom too but I can't get it to boot, just download mode and recovery loads now.
Click to expand...
Click to collapse
Well good thing is you're not hardbricked. Have you followed all these steps in this order?
http://forum.xda-developers.com/showpost.php?p=28849870
Do you have the 4.0 stock rom? (Don't use the one I linked since it's for the 5.0). Also did you try wiping the dalvick?
obscuresword said:
Well good thing is you're not hardbricked. Have you followed all these steps in this order?
http://forum.xda-developers.com/showpost.php?p=28849870
Do you have the 4.0 stock rom? (Don't use the one I linked since it's for the 5.0). Also did you try wiping the dalvick?
Click to expand...
Click to collapse
Yes, I followed all those steps perfectly. I have reflashed my stock rom multiple times before. And I have wiped dalvick cache when I was able to get into my CWM recovery a few times to no avail. My pc recognized the device just fine until today. I just flashed my .pit file and the terrasilent kernel through heimdall, and now my device isn't being read through Odin OR Heimdall. It is recognized by my pc but not by those programs. And yes I am in download mode. I also tried flashing back to stock before but the recovery just gave me a bunch of red text errors.
DarkMuffin Inc said:
Yes, I followed all those steps perfectly. I have reflashed my stock rom multiple times before. And I have wiped dalvick cache when I was able to get into my CWM recovery a few times to no avail. My pc recognized the device just fine until today. I just flashed my .pit file and the terrasilent kernel through heimdall, and now my device isn't being read through Odin OR Heimdall. It is recognized by my pc but not by those programs. And yes I am in download mode. I also tried flashing back to stock before but the recovery just gave me a bunch of red text errors.
Click to expand...
Click to collapse
I can't really see the photo, can you type out the error codes lol.
Related
Hi guys, I got a SGS2 just over a week ago, on Bell/Virgin network in Canada. Suffered from the battery drain issue due to being stuck with crappy UGKG2 firmware which my provider still hasn't updated.
I decided to update it myself, and did a ton of research. I successfully got Root tonight by flashing CF-Root-SGS2_ZS-OZS_KG2-v4.1-CWM4 kernel with Odin. In case it matters, I did NOT flash back my stock Kernel, so I still had the insecure kernel installed. From there, I backed up my apps with Titanium.
Went into CWM and selected boot into CWM Recovery. I followed the steps on the wiki, including creating a backup file. My only hint of what I might have done wrong was I originally selected to flash update.zip, and that process failed. I then went to the directory in which cyanogenmod is stored on my SD card, and selected that, then it installed ok. I had downloaded update-cm-7.10-GalaxyS2-signed and that's what I put on the phone. I then also installed the Google Apps.
I then hit reboot, and it only goes to the Samsung screen with the yellow triangle and just hangs there for a few minutes. Not knowing what else to do, I popped the battery out. I have since learned that I can turn it on and off, but it never goes past that screen. Wouldn't go into the recovery or download modes, always that screen. Luckily, I saw somewhere to do the 3 button thing WHILE in that screen, and that works. So I can get to recover, and download modes. So, I think I'm ok. I checked, and it does connect to Odin still.
I just want to know EXACTLY what I should do at this point. I don't want to fully brick it. There are actually two recovery files on the phone... not sure why... Or which one to pick. Should I just flash stock firmware back with Odin? One of my main goals is to get off 2.3.3 so I can have more than 8 hours of battery...
Thanks,
Rob
Boot into tecovery, do a full wipe again. (Wipe data/factory reset, wipe cache partition, advanced>wipe dalvik cache).
Now install CM7 zip twice in a row without reboot. It may take a few minutes for reboot since system is rebuilding dalvik cache. Be patient. After you see the home screen, reboot again.
Sometimes, CM won't install properly with CF root recovery. In that case reboot into download mode, flash codeworkx cwm kernel via ODIN.
http://forum.xda-developers.com/showthread.php?t=1118693
Now reboot into recovery and do full wipe and twice-install !
Ok, working now with the flash twice thing. Well that's weird, would be great if it was in the wiki page...
Thanks!
Rob
Hi,
First time it happened. tried everything but still cant fix it.
after a month or two on MIUI, I wanted to move to AOKP JB.
As I always do when switching ROMs, I backed up everything (efs, pictures, apps with titanium, etc) and format the internal sd card within the os to get rid of all the junk.
Then went into CWM (siyah) and wiped data and cache.
And now for my mistake, I foramt the /system instead of / cache.
So now, when Im trying to install the ROM as a zip file threw CWM I got an error 7.
When trying to do it on ODIN, it stuck on 'factory fs', 'cache', or 'boot'.
After some time, I got the "Firmware upgrade encountered an issue" message.
Then got rid of it after somehow succeeding installing a different cwm (the stock one) but nothing worked there either, exept installing the Siyah kernel zip from there.
What can I do now to get my phone back alive?
THANKS :crying:
pedel said:
Hi,
First time it happened. tried everything but still cant fix it.
after a month or two on MIUI, I wanted to move to AOKP JB.
As I always do when switching ROMs, I backed up everything (efs, pictures, apps with titanium, etc) and format the internal sd card within the os to get rid of all the junk.
Then went into CWM (siyah) and wiped data and cache.
And now for my mistake, I foramt the /system instead of / cache.
So now, when Im trying to install the ROM as a zip file threw CWM I got an error 7.
When trying to do it on ODIN, it stuck on 'factory fs', 'cache', or 'boot'.
After some time, I got the "Firmware upgrade encountered an issue" message.
Then got rid of it after somehow succeeding installing a different cwm (the stock one) but nothing worked there either, exept installing the Siyah kernel zip from there.
What can I do now to get my phone back alive?
THANKS :crying:
Click to expand...
Click to collapse
I jumped from S1 to S3, but I'm sure it's applicable. You need to flash via odin stock rom that originally came with your phone. Then root then flash custom rom. Odd tho in past I've done the 5 formats, boot, cache, data, system, sdcard then while still in recovery flash rom. Good luck
Sent from my GT-I9300 using xda premium
jj92942000 said:
I jumped from S1 to S3, but I'm sure it's applicable. You need to flash via odin stock rom that originally came with your phone. Then root then flash custom rom. Odd tho in past I've done the 5 formats, boot, cache, data, system, sdcard then while still in recovery flash rom. Good luck
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
thanks
The problem is, I really cant remember what was the original ROM version. I bought it end of june 2011.
I cant even remember if it was a UK ROM, or an open europe one, or anything else.
****
Hi Guys
I am new to playing around with android but not to electronics. I have a Verizon Samsung Galaxy Tab 10.1 16gb (SCH-i905) with current 4g service.
Here is the problem I am having:
It started yesterday, I was browsing the web and the tablet froze and then rebooted. After the reboot programs randomly freeze and crash, if I reboot anything I have downloaded is gone and anything I deleted is back and I can't install or remove apps. I figured I had something corrupted and a factory wipe would fix it. Unfortunately when I perform a factory wipe from the menus or through Android recovery nothing happens. The tablet boots up like nothing was erased. Still has all my accounts, security pin, apps, and so on.
So after that I figured I would flash the tablet, I found the thread here in the development forum with the stock 3.2 image to load through ODIN. I downloaded everything, followed the instructions. ODIN says the flash was successful but when the tablet reboots it still has all my info and is running 4.0.4. I have tried this multiple times. I have tried loading CWM with ODIN but it will not stick.
Any thoughts? If you need more information I will get it, I am just stuck and can't find anything that helps me with this problem!
Thanks for your help!!!
If you want cwm to load after you install it using odin, then you must immediately boot the tablet into recovery without letting it run normally. During the normal boot process, CWM is deleted and the stock recovery is restored. Therefore once Odin finishes installing CWM, hold the volume up button and once you get to the recovery mode you will be running CWM instead of the stock recovery module.
Regards,
Michael
Yes, I did read that in the multiple thread about installing CWM and have gone into recovery directly after ODIN reboots the tablet, however it is still only the stock recovery app.
Any ideas why the factory reset / data wipe won't work?
So after several more hours working on this problem I think I have come across the root cause. I believe that my internal storage has corrupted and is now only mounting in Read-Only mode. From everything I can find online, without having root access previously, this is a no go for fix it yourself.
In case anybody happens on this post down the road, I have been unable to find a resolution and it would appear I must sent the unit back to Samsung for repair.
Mixinitup4Christ said:
So after several more hours working on this problem I think I have come across the root cause. I believe that my internal storage has corrupted and is now only mounting in Read-Only mode. From everything I can find online, without having root access previously, this is a no go for fix it yourself.
In case anybody happens on this post down the road, I have been unable to find a resolution and it would appear I must sent the unit back to Samsung for repair.
Click to expand...
Click to collapse
factory reset through the stock recovery should be able to get you out of it (RO filesystem).
pershoot said:
factory reset through the stock recovery should be able to get you out of it (RO filesystem).
Click to expand...
Click to collapse
I guess that blows my theory out of the water. I can't make heads or tails with this. No matter what I do, Menu Factory Reset, Recovery Wipe/Reset, ODIN Flash Stock EG01 firmware, ODIN flash CWM Recovery as soon as this device reboots I am right back where I started....... GAH!!!
Thanks for letting me know I'm probably wrong.
Mixinitup4Christ said:
I guess that blows my theory out of the water. I can't make heads or tails with this. No matter what I do, Menu Factory Reset, Recovery Wipe/Reset, ODIN Flash Stock EG01 firmware, ODIN flash CWM Recovery as soon as this device reboots I am right back where I started....... GAH!!!
Thanks for letting me know I'm probably wrong.
Click to expand...
Click to collapse
it has to be factory reset through the stock recovery (it will format /data), not through CWM.
rozeins gone
pershoot said:
it has to be factory reset through the stock recovery (it will format /data), not through CWM.
Click to expand...
Click to collapse
Yup, done that multiple times. I'll take video of it if you want, Factory Reset in stock recovery has no effect.
Mixinitup4Christ said:
Yup, done that multiple times. I'll take video of it if you want, Factory Reset in stock recovery has no effect.
Click to expand...
Click to collapse
odin flash CWM (you can use 6.0.2.8 in JB CM10 folder on droidbasement), boot it and try to format the /system partition first then /data.
pershoot said:
odin flash CWM (you can use 6.0.2.8 in JB CM10 folder on droidbasement), boot it and try to format the /system partition first then /data.
Click to expand...
Click to collapse
Will Do, ODIN3 1.85?
pershoot said:
odin flash CWM (you can use 6.0.2.8 in JB CM10 folder on droidbasement), boot it and try to format the /system partition first then /data.
Click to expand...
Click to collapse
HI Pershoot!
I forgot to say thanks for your help!! I appreciate someone smarter than me lending a hand.
That said, I just tried to flash CWM from DB Galaxy Roms/CM10 folder. Upon reboot the tablet still entered stock recovery, I have tried this several times, but this time I took a video. If you feel so inclined to watch it maybe you can catch me doing something wrong....
Again thanks for your help!!
Video of me doing the Stock Recovery Factory Reset
Video of me attempting to flash CWM from droid basement
Mixinitup4Christ said:
HI Pershoot!
I forgot to say thanks for your help!! I appreciate someone smarter than me lending a hand.
That said, I just tried to flash CWM from DB Galaxy Roms/CM10 folder. Upon reboot the tablet still entered stock recovery, I have tried this several times, but this time I took a video. If you feel so inclined to watch it maybe you can catch me doing something wrong....
Again thanks for your help!!
Video of me doing the Stock Recovery Factory Reset
Video of me attempting to flash CWM from droid basement
Click to expand...
Click to collapse
I had to do this on mine. http://techne.alaya.net/?p=8829. I rooted and modified the file described in the steps. Weirdly enough it still booted into stock recovery the first time I installed CWM. I installed CWM one more time and the tablet now boots into CWM.
I have an i9300 international version. It began freezing and boot looping.
Recovery and download mode were working. adb shell was working via recovery.
To figure out why it was bootlooping, I wanted to run adb logcat during boot, but to do this you need to enable usb debugging, and mine was disabled. Obviously I couldn't enable it because I couldn't boot, and even tried to enable via adb shell using the following steps:
/data/data/com.android.providers.settings/databases/settings.db: adb_enabled=1
and
/system/build.prop: persist.service.adb.enable=1
But I couldn't find the above sqlite database. In fact /data was empty and I couldn't access any system files via adb shell anyway.
So no usb debugging, which means the next step is flash a stock rom. I flashed I9300XXEMG4 (here) with Odin, wiped system,data,cache. Still bootlooping (samsung logo - kernel i9300 logo - samasung logo - kernel logo etc).
I read about the PIT file here. I read about how you should stay away from it at all costs. As this was a last ditch attempt I flashed the PIT file GT-I9300_mx_20120329.pit along with I9300XXEMG4.
The phone booted fine!
Unfortunately I just read this post about not coming back from EMG4... and I hadn't backed up the efs partition
Disclaimer: do not flash the PIT file unless you know what the hell you are doing.
P.S. if you have any problems with Odin not working (stuck before it starts flashing), close Odin, unplug USB and take the phone battery out, open Odin, put the battery in, boot into download mode then plug USB in. Worked fine for me.
Cheers
Everytime I flash the stock ROM, I will have bootloop. I get into stock recovery mode, do a factory wipe and reboot. My phone boots up normally after that.
YRAJ23 said:
Everytime I flash the stock ROM, I will have bootloop. I get into stock recovery mode, do a factory wipe and reboot. My phone boots up normally after that.
Click to expand...
Click to collapse
Why are you flashing the stock ROM? Upgrading? If you are flashing a different ROM or different Android version, your /data won't work with the new version. If you are flashing to a similar version, try only wiping the cache and dalvik cache.
thejonesyboy said:
Why are you flashing the stock ROM? Upgrading? If you are flashing a different ROM or different Android version, your /data won't work with the new version. If you are flashing to a similar version, try only wiping the cache and dalvik cache.
Click to expand...
Click to collapse
I'm a flash addict. I will try new ROMs. I case anything went wrong, this will by my rescue step. Last week, my phone's external speaker malfunctioned. So I need to get back to stock. I need to unroot and flash stock firmware. I encountered boothloop. So, do a factory wipe and reboot. All was OK.
YRAJ23 said:
I'm a flash addict. I will try new ROMs. I case anything went wrong, this will by my rescue step. Last week, my phone's external speaker malfunctioned. So I need to get back to stock. I need to unroot and flash stock firmware. I encountered boothloop. So, do a factory wipe and reboot. All was OK.
Click to expand...
Click to collapse
what type of speaker malfunctioning you got? I am facing some problem with audio/video apps. all audio/video related apps(even call ringtones) not running smoothly half of the time. I have tried many roms. Now i flashed stock firmware via odin and still have same issue.
I have not done any data/cache wipe before odin flash. Is full data/cache wipe is required for stock firmware via odin. OR any other solution you can suggest.
siwach said:
what type of speaker malfunctioning you got? I am facing some problem with audio/video apps. all audio/video related apps(even call ringtones) not running smoothly half of the time. I have tried many roms. Now i flashed stock firmware via odin and still have same issue.
I have not done any data/cache wipe before odin flash. Is full data/cache wipe is required for stock firmware via odin. OR any other solution you can suggest.
Click to expand...
Click to collapse
My phone was under warranty. So I reset the binary counter and reflashed stock ROM. Send it to Service Centre. They said my speaker was spoilt. So they replaced the speakers
I accidentally formatted my internal SD card with TWRP instead of factory reseting. I can get into recovery, but loading any ROM hangs at the loading screen. For awhile, TWRP was asking for a password, and then somehow I hit the magic combination of things to make that stop happening. I adb pushed an updated TWRP and reinstalling various ROMs.
All this started from trying to install Hyperdrive RLS8. I was running RLS7 fine, went for a clean install, spaced out and formatted the phone, flashed the ROM, and had a whole slew of stability problems. Things would randomly crash instantly, booted only 50% of the time, when it did, installing things would break it, tried various things to fix it, fixing permissions and wiping cache's and such, and results were unpredictable. Kept re-formatting and reflashing with different options until I finally realized that I was formatting it and that's probably what the whole problem was.
Currently I can't boot into a ROM, it hangs on the boot animation. I tried another clean install with RLS7, and the same thing happens. I'm assuming that I need to get back to stock somehow, but I'm not sure how. Odin has always confused me. I used the all in one tool to root awhile back, and I only used odin to send a kernel tar file. If I download a stock build, it's a zip file... so how can I odin it? Is that what I need to do? I'm imagining at this point that the file structure is messed up and I need to rebuild it somehow. I don't have my nandroid backup on this computer, so I haven't tried that yet.
You can either odin stock. It's about a 1.8gb file.
Or you can get a known working ROM on your sd card, factory reset wipe, wipe preload, wipe system, install known working rom+gapps+whatever, wipe cache and wipe dalvik. Reboot. If it sticks at the samsung logo pull the battery and then try to reboot again. Sometimes first boot can take a while. I'd give it 10 minutes before throwing in the towel lol
I bricked my phone by updating Hyperdrive (which I will never (curse words... lots of them) use again. Can someone tell me where to find this stock file? I've been searching long enough to get frustrated and delete several less diplomatic posts, settling with this one.
hey guys, I am a little confused. I just came to the S4 from a galaxy nexus, and I previously used CWM as my recovery option when doing clean install of new ROMS.
When I rooted my S4, I installed TWRP (via goomananger, version 2.5.0.2) because of people saying its much better (on the galaxy nexus forums). However, I keep reading issues of people being stuck in bootloops for TWRP when wiping data.
My question is -- what is this issue? Are you not supposed to clean flash with TWRP?? Or do you only do "factory reset" option in TWRP and not wipe the data?
As I am a little confused on this issue, is it more safe to just install most recent CWM and use that as recovery instead?
Thanks alot
No worries
uberpippi said:
I accidentally formatted my internal SD card with TWRP instead of factory reseting. I can get into recovery, but loading any ROM hangs at the loading screen. For awhile, TWRP was asking for a password, and then somehow I hit the magic combination of things to make that stop happening. I adb pushed an updated TWRP and reinstalling various ROMs.
All this started from trying to install Hyperdrive RLS8. I was running RLS7 fine, went for a clean install, spaced out and formatted the phone, flashed the ROM, and had a whole slew of stability problems. Things would randomly crash instantly, booted only 50% of the time, when it did, installing things would break it, tried various things to fix it, fixing permissions and wiping cache's and such, and results were unpredictable. Kept re-formatting and reflashing with different options until I finally realized that I was formatting it and that's probably what the whole problem was.
Currently I can't boot into a ROM, it hangs on the boot animation. I tried another clean install with RLS7, and the same thing happens. I'm assuming that I need to get back to stock somehow, but I'm not sure how. Odin has always confused me. I used the all in one tool to root awhile back, and I only used odin to send a kernel tar file. If I download a stock build, it's a zip file... so how can I odin it? Is that what I need to do? I'm imagining at this point that the file structure is messed up and I need to rebuild it somehow. I don't have my nandroid backup on this computer, so I haven't tried that yet.
Click to expand...
Click to collapse
Try using odin to flash to stock. Then re-root and install custom recovery and whichever rom. I had a similar problem posted here with no help from the big brains. Had to trial and error with caution on my own. Kinda disappointing since the answer is quite simple once you connect all the dots. Flashing in odin will fix yer internal storage problem because it redefines everything.
cidorov said:
Try using odin to flash to stock. Then re-root and install custom recovery and whichever rom. I had a similar problem posted here with no help from the big brains. Had to trial and error with caution on my own. Kinda disappointing since the answer is quite simple once you connect all the dots. Flashing in odin will fix yer internal storage problem because it redefines everything.
Click to expand...
Click to collapse
uberpippi said:
I accidentally formatted my internal SD card with TWRP instead of factory reseting. I can get into recovery, but loading any ROM hangs at the loading screen. For awhile, TWRP was asking for a password, and then somehow I hit the magic combination of things to make that stop happening. I adb pushed an updated TWRP and reinstalling various ROMs.
All this started from trying to install Hyperdrive RLS8. I was running RLS7 fine, went for a clean install, spaced out and formatted the phone, flashed the ROM, and had a whole slew of stability problems. Things would randomly crash instantly, booted only 50% of the time, when it did, installing things would break it, tried various things to fix it, fixing permissions and wiping cache's and such, and results were unpredictable. Kept re-formatting and reflashing with different options until I finally realized that I was formatting it and that's probably what the whole problem was.
Currently I can't boot into a ROM, it hangs on the boot animation. I tried another clean install with RLS7, and the same thing happens. I'm assuming that I need to get back to stock somehow, but I'm not sure how. Odin has always confused me. I used the all in one tool to root awhile back, and I only used odin to send a kernel tar file. If I download a stock build, it's a zip file... so how can I odin it? Is that what I need to do? I'm imagining at this point that the file structure is messed up and I need to rebuild it somehow. I don't have my nandroid backup on this computer, so I haven't tried that yet.
Click to expand...
Click to collapse
Yes this would probably be your best bet. I wouldn't say the answer "is quite simple when you connect the dots" though, because with that logic there would be no PC problems, you would just connect the dots and format the harddrive and Windows will redefine everything else for you!
But back to seriousness, you have to download a stock factory image and its actually a tar.md5 file and not a .zip because you cant flash zips through odin. The stock factory images can be found in the development section, and they are usually quite large files (2gb+ when extracted!) and you will have to download odin and make sure you have the latest usb drivers from samsung. Then its pretty straight forward, The threads in the development section have guides for how to use odin. The stock image contains all the partitions within in it and will effectively repartition your device when you flash it so no need to use a pit file.
Surge1223 said:
Yes this would probably be your best bet. I wouldn't say the answer "is quite simple when you connect the dots" though, because with that logic there would be no PC problems, you would just connect the dots and format the harddrive and Windows will redefine everything else for you!
But back to seriousness, you have to download a stock factory image and its actually a tar.md5 file and not a .zip because you cant flash zips through odin. The stock factory images can be found in the development section, and they are usually quite large files (2gb+ when extracted!) and you will have to download odin and make sure you have the latest usb drivers from samsung. Then its pretty straight forward, The threads in the development section have guides for how to use odin. The stock image contains all the partitions within in it and will effectively repartition your device when you flash it so no need to use a pit file.
Click to expand...
Click to collapse
Just to follow up, that's what I ended up doing. I used the "No-wipe" factory image, odin'd it, re-rooted (I don't know if I had to do that step, but I did), and then loaded my ROM of choice and it works perfectly now. Thanks!