Related
Ok...I'm at a point where I had no other choice but to get another replacement. I looked just about everywhere my patience would take me, and decided to give up. I hope someone could/would have a solution for me or others like me.
I had EH03 deoxed rom and decided I wanted ICS build5. So I installed CM7, I whiped cache, DLVK, and system data. Then flashed ICSb5 and GAPPS, Rebooted and stuck on ICS splash screen.
At this point USB ports wouldn't recognize fascinate. Downloaded all Fascinate drivers from Samsung, drivers for Nexus S, ADB, Android SK. You name it I got it. Nothing worked for USB detection. I even followed YT videos on turning Vista/PC off and unplug. Nothing.
After messing with data cords,(numerous ones,trying another PC), PC ports, I happened to pull plug and battery out of Fascinate at the same time, not sure what version of CWM, it was blue, came on. Luckily I had two Nandroid backups on SD.
I flashed Nandroid back to CM7 successfully. Rebooted fine and hooked to USB but still not recognized. At this point I was able to get into recovery using ROM. So, I did something stupid...lol...I tried to flash earliest Nandroid which was performed when on EH03 deoxed. Once I did this, I wiped all needed data and rebooted. Now Fascinate shows Samsung logo. It doesnt reboot, just that the logo stays until I pull battery. Now if I have battery in wth phone off and plug in, the charging battery comes on but doesn't show battery level. Doesn't go away till I pull battery.
The funny thing is that I can get into Download mode but USB is still unrecognized/malfunction on PC/Vista. I only wish that I was able to link phone and PC just to use Odin with PIT file and stock EDO5 or EH03.
Any advice?
dssheeley1 said:
Ok...I'm at a point where I had no other choice but to get another replacement. I looked just about everywhere my patience would take me, and decided to give up. I hope someone could/would have a solution for me or others like me.
I had EH03 deoxed rom and decided I wanted ICS build5. So I installed CM7, I whiped cache, DLVK, and system data. Then flashed ICSb5 and GAPPS, Rebooted and stuck on ICS splash screen.
At this point USB ports wouldn't recognize fascinate. Downloaded all Fascinate drivers from Samsung, drivers for Nexus S, ADB, Android SK. You name it I got it. Nothing worked for USB detection. I even followed YT videos on turning Vista/PC off and unplug. Nothing.
After messing with data cords,(numerous ones,trying another PC), PC ports, I happened to pull plug and battery out of Fascinate at the same time, not sure what version of CWM, it was blue, came on. Luckily I had two Nandroid backups on SD.
I flashed Nandroid back to CM7 successfully. Rebooted fine and hooked to USB but still not recognized. At this point I was able to get into recovery using ROM. So, I did something stupid...lol...I tried to flash earliest Nandroid which was performed when on EH03 deoxed. Once I did this, I wiped all needed data and rebooted. Now Fascinate shows Samsung logo. It doesnt reboot, just that the logo stays until I pull battery. Now if I have battery in wth phone off and plug in, the charging battery comes on but doesn't show battery level. Doesn't go away till I pull battery.
The funny thing is that I can get into Download mode but USB is still unrecognized/malfunction on PC/Vista. I only wish that I was able to link phone and PC just to use Odin with PIT file and stock EDO5 or EH03.
Any advice?
Click to expand...
Click to collapse
In the op of ics and also droidstyles guide you have to flash build 1 before you can flash build 5
Sent from my SCH-I500 using XDA App
I've never flashed version 1 before flashing.build 5. In fact I've had the least amount of problems going back to stock (ED05) then flashing ICS.
I bootlooped when i went from stock EH03 to Build 5 so i did 3 first then 5.
But this doesn't help our poster here.
OP:
you get into DL mode but odin wont see your phone?
What i suggest is to try: Move the usb cable to a different port. see if your pc can see it then. Second thing try a totally different computer. Chances are your PC is trying to use borked up drivers.
Once you get odin going flash a stock image [i recommend eh03] then cwm then build 3 and now the new build 6. good luck!
if you need any links or a more detailed guide I STRONGLY suggest Droidstyles guild, it is by far the best and most up to date for the fassy!
OhioYJ said:
I've never flashed version 1 before flashing.build 5. In fact I've had the least amount of problems going back to stock (ED05) then flashing ICS.
Click to expand...
Click to collapse
Consider yourself lucky....going from stock to build 6 causes me problems and many others. Going from stock, to build 1, then build 6 works flawless.
MOD please close thread due to lapsed timeline and no longer support of this model.Ty
Sent from my SGH-i717/GT-N7005 w/phMOD_beta2
dssheeley1 said:
MOD please close thread due to lapsed timeline and no longer support of this model.Ty
Sent from my SGH-i717/GT-N7005 w/phMOD_beta2
Click to expand...
Click to collapse
You realised you just bring a a old thread back yourself and no longer support of this model wtf you realise people.still use this phone everyday Right?
Sent from my SCH-I500 using Tapatalk 2
I recently installed the nightly build of ICS on my samsung vibrant. Today the phone had a error that said encryption cannot be completed phone must be erased. I let it do a factory reset . Then I got stuck in a endless boot cycle showing the vibrant logo and then the cynogen guy for a few seconds then reboot. I could still access the recovery menu but it refused to flash any roms I threw at it. I downloaded and ran odin 1 click recovery and it changed my tmobile phone to a att phone. And it lost the recovery mode. It just shows att screen first then samsung vibrant second and just reboots. I can still get into download mode and flash roms using odin 3 but no matter what rom I select or if I choose repartion or not the flash will go through successfully but then the phone reboots into same problem as before. I suspect the recovery files are gone since no button combination anymore gets me into recovery. Is there anything else I can do?
Man I am having the exact same problem. I really hope someone can figure something out soon. Did yours randomly get that error? Or did you actually try to encrypt your phone?
Sounds like you used the wrong Odin 1 Click. If it installed Captivate bootloaders, that would cause a problem.
This is your best shot I think
http://forum.xda-developers.com/showthread.php?p=24418319
Sent from my A500 using Tapatalk 2
It just happened
It happened on its own. Was working fine all day walked in my house as as soon as it hit wifi it started going crazy. I had the data plan turned off months ago. Maybe theres something to it connecting up to the net. I have found out if you install your sim you get a reduced menu of recovery options but without sim it just constantly reboots. it only gives option of reboot, reinstall packages,delete all user data, delete cache data. If you try reinstalling the packages theres nothing there. Deleting caches made no differance. ADB does work and responds while in this lesser form of recovery is there a easy way to use adb to force a full system flash?
Thanks
That link was perfect had a link to eugenes no brick froyo rom which fixed my problem. Dloaded that used its pit and tar files and repartioned and im back to stock. Going back to team whiskeys mod. If all ICS roms has bugs like that is unusable.
bfranklin1986 said:
This is your best shot I think
http://forum.xda-developers.com/showthread.php?p=24418319
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
Do you have access to BOTH your internal and external SD cards? The Encryption Bug is totally and completely random and does not discriminate. There is currently no known reason or solution. Several of us across a few different devices have been working on this for months.
Consider yourself luck if you have access to both SDs as you are the 2nd person to get in and out today. Many, many others have not been as fortunate.
If you could please pull up this thread and put as much information in there as possible, it would be greatly appreciated. Are you unlocked, what happened right before, what bootloaders are you on, what ROM were you trying to flash, what ROM did you end up getting booted,....those types of things. As much detail as you can muster together, after you catch your breath and relax a minute.
Guys DO NOT run ICS unless you have read up on the Encryption Unsuccessful bug and except the possible consequences! Every ICS T959 rom should have a warning IMO.
There is no known fix > just a work around. Odin / Heimdall / Jtag = useless
Update
I think I might have pulled the trigger to quick. While the link above did give me Eugenes rom which at least got me out of the boot cycle both internal and external sd shows 0 and I am unable to load anything on either card. I have tried differant microsd cards all of them show the same thing. So eugenes rom got me working kind of but cant store anything at all. That sucks loved my vibrant and its almost out of contract and planned on using on prepay.
Agreed 100 %
Had I of known would of stuck around on my team whiskey rom which never gave me any problems. Does this ICS bug affect amazon kindles? Ive put cynogen9 on 2 of them and am wondering if I shouldnt take it off before they turn into paper weights.
Moped_Ryder said:
Guys DO NOT run ICS unless you have read up on the Encryption Unsuccessful bug and except the possible consequences! Every ICS T959 rom should have a warning IMO.
There is no known fix > just a work around. Odin / Heimdall / Jtag = useless
Click to expand...
Click to collapse
chickenmon said:
Had I of known would of stuck around on my team whiskey rom which never gave me any problems. Does this ICS bug affect amazon kindles? Ive put cynogen9 on 2 of them and am wondering if I shouldnt take it off before they turn into paper weights.
Click to expand...
Click to collapse
I got tagged on a Nook Color with it. BUT, since the Nook Color has a feature that no others I think do (you can boot a ROM straight from an SD card and not mess with the oringinal OS at all), I was able to just pull my Microsd out and reformat it and then put CM7 on it for my wife.
So far from what I have seen and been working on:
Vibrant, Captivate, My wife's Nook Color, A few Transformers, SGSII,...
Anything I can do?
Anything I can do to get my partions right again? I can flash the twm 5.2.2 but none of the roms i throw at it including ics passion stays in a boot cycle. Only rom that works is eugenes froyo that does not brick and it doesnt allow internal or external mem to be seen.
chickenmon said:
... Only rom that works is eugenes froyo that does not brick and it doesnt allow internal or external mem to be seen.
Click to expand...
Click to collapse
You may want to bring up this issue directly in Merio90's thread. I believe Alex9090 went thru possibly similar issues and may be able to help you in that thread (unless she happens to pop in here).
I'm assuming you were trying to mount sdcard and emmc within recovery first (storage and mounts)? If you do have access to recovery again and can mount the external sdcard, maybe try repartitioning the card within recovery (using the parameters in Merio90's instructions)? Then transfer your rom zip and re-flash.
People have actually flashed Eugene's Froyo post-EU ... but without an ext sdcard. Quite an oddity. It's the only one (AFAIK) that'll fully boot up (even after losing int sdcard access due to EU) yet without an external sdcard in place.
Your assumptions are correct. I cannot mount emmc. I cannot flash any rom via 2.5 or 5.2 recovery only through odin and only eugenes rom still allows phone to boot but no mounting of internal or external sds. Ive spent about 3 days on this. There must be some hardcore adb commands to force a true factory reset partioning and all. Very annoying. Thanks for the help if I find any ways to fix it I will repost it here.
Might be bricked?
Ok, i will admit up front that I probably did something stupid and now am sending out a cry for help. Until yesterday I had ICS 4.0.3 successfully installed. I believe it was Euphoria flavor. But, I constantly had shortage of memory problems with the new force close language on apps running in bg - was laggy. Here is where it all went wrong - Decided to dl and install CM9 nightly to fix my laggy install. Recovery went fine, but rom failed, rebooted and sent error to cm. Tried new tactic - dl and installed Slim ICS - wrong, got stuck in boot loop - but could still get into download mode. Ran Odin to restore to stock. Ran fine but Failed - no explanation, just failed. Since it would not respond, finally turned it off - OFF has now become permanent! Power button does nothing. Charging does not light up screen. No download or recovery mode! Really fearful that this IS bad. Help, help, help!!
Open to suggestion. . .
JIM in FLA
Not related at all to my original problem.
tenantrep said:
Ok, i will admit up front that I probably did something stupid and now am sending out a cry for help. Until yesterday I had ICS 4.0.3 successfully installed. I believe it was Euphoria flavor. But, I constantly had shortage of memory problems with the new force close language on apps running in bg - was laggy. Here is where it all went wrong - Decided to dl and install CM9 nightly to fix my laggy install. Recovery went fine, but rom failed, rebooted and sent error to cm. Tried new tactic - dl and installed Slim ICS - wrong, got stuck in boot loop - but could still get into download mode. Ran Odin to restore to stock. Ran fine but Failed - no explanation, just failed. Since it would not respond, finally turned it off - OFF has now become permanent! Power button does nothing. Charging does not light up screen. No download or recovery mode! Really fearful that this IS bad. Help, help, help!!
Open to suggestion. . .
JIM in FLA
Click to expand...
Click to collapse
First of all, not to sound like a ****; but it's rude to hijack someone elses thread. You should've created your own thread for this.
Second; you might have fried your bootloader which in turn, yeah, that's bad and you might have bricked your phone.
Did you try to boot into recovery via the battery pull method. If not, try that and see how it works. I would link you to the instructions but I'm too lazy and tired right now to search for it and again, this is someone else's thread. Just do a search for it and you should find it.
If you need more help or guidance, create your own thread and start there.
Noticed your running Ice Cream Zenwich rc1.3. How do you like it. Ive installed slim 3 times today and twice I have gotten the encryption error within a hour. Needless to say not impressed major pain in the ass to have to do a million and half tricks with awm, adb, popping sd cards in and out etc.
Update
Also the current build of ics slim does not allow the imei information to be retrieved from sim for tmobile requiring a reflash of the modem. You have to download and install a new modem. I used csm5. The guide on the link in this post dow work but its a real pain and requires lots of trial and error. Wondering if google intentionally bricking these things knowing we all got gadget lust for the sIII now.
chickenmon said:
Noticed your running Ice Cream Zenwich rc1.3. How do you like it ...
Click to expand...
Click to collapse
ICZen_rc1.8.3 (AOKP #39, ICS 4.0.4) + subZero #144 (New Test Kernel just released in mr_pyscho's RootzWiki kernel thread) is Linaro infused ... and I've got to say the combo is THE fastest rom experience I've ever had on my Vibe. Whatever MP did in his new test kernel just blows the doors off the previous performance limits.
Btw .. you keep encountering EU again. Really odd unless possibly your external card wasn't partitioned correctly. Not a knock directly on you, but it is a common occurrence lately. FYI, I repartitioned mine directly from recovery.
Also ... Br1cK'd (ICZen) and mr_psycho (subZero) are aware of the EU situation and try to include safeguards in their builds. However, until we know the exact root cause of EU, we're all just shooting in the dark. Imo, it's at least comforting to use a rom & kernel where the dev's are at least mindful of EU.
Hello,
I have tried to flash, reflash, and flash again back to the stock froyo for samsung fascinate. I had cm7 on my phone for about 2 years and decided to go to cm10. Well I couldnt get gapps to work in cm10 so I thought that I would take it back to cm9. cm9 gave me the same issues so i decided to just go back to cm7. At this point I couldnt go into CWM and the phone would go straight to the cm9 alien guy and would proceed to do an infinite boot. I decided to try and reload CWM and it worked. The issue now is that I cannot reflash the phone. I have tried http://forum.xda-developers.com/showthread.php?t=1212239 which keeps giving me the 0 succeeded/0 failed message. I am assuming that it is refusing to reflash. I have also tried flashing from the CWM with a file on the sd card. How do i proceed? Also this is my first post, been reading for years. Thanks!
Edit: When I try and clear /cache it is giving me a failed to mount /cache
Not sure where you went wrong here, but use Droidstyle's guide to flash back to stock (btw it's stock GB not Froyo). CM10 is great but I'd recommend trying AOKP JB Sep. 20 with the Devil 1.5.2 Kernel. Smooth as hell.
Grab the proper working and latest Gapps from http://wiki.cyanogenmod.com/index.php?title=Latest_Version/Google_Apps
odin cant see phone
Crawshayi said:
Not sure where you went wrong here, but use Droidstyle's guide to flash back to stock (btw it's stock GB not Froyo). CM10 is great but I'd recommend trying AOKP JB Sep. 20 with the Devil 1.5.2 Kernel. Smooth as hell.
Grab the proper working and latest Gapps from http://wiki.cyanogenmod.com/index.php?title=Latest_Version/Google_Apps
Click to expand...
Click to collapse
Well it seems as though odin cannot see my phone. Heimdall sees it but odin does not. I think that may be the reason that I am getting 0 succeeded/ 0 failed.
There can be many reasons that happens, but usually it's a bad cable or usb port. Try different usb ports first, even on a different computer if you can, and also a different data cable if you have one lying around. Also, uninstall and reinstall the Samsung usb drivers. Sometimes that helps.
Hey all!
Wanting to upgrade my firmware from ICS to Jelly Bean (as a definite noob, though having flashed firmwares before) I opened Odin and added what I considered the correct .tar file from Sammobile in the PDA field. In short, it failed and I thought I had a new brick*. Following Phistacio's guide to fixing an unflashable GSII I've now got my phone back (woohoo!!), but am stupid enough to want to give it another go!
My question really, is what could have gone wrong, and more largely, what are the variable errors that us noobs make when trying to flash? I'm using Odin, but it seems using a CWM (is this the correct term?!) might now be the chosen route to flashing?
I'm rooted, on an unlocked GSII, recently moved from O2 to Everything Everywhere (T-Mob), currently using an O2 issued ICS, stock kernel and tried flashing Jelly Bean from Sammobile.
So what's critical here? Is my carrier relevant? Is it not possible to go from some firmwares to others? Do I need a different kernel for some firmwares? Or is my mistake in thinking it's as straight forward as I'd like, when in fact all the above make a critical difference in which firmware I can flash, and therefore I should stop trying??!
Thanks in advance for any light you can shed!
*I think I was softbricked - could enter download mode but not recovery, flashing would hang on either "Nand write start!!" or Sbl.bin or Cache.img.
my two cents
Hi joelinit,
First of all, should congratulate you on taking the first step of flashing the roms..
Second, good you got an issue while flashing. It helps you understand the intricacies better once you try to solve it yourself.
You need not worry about the brick. Try flashing back to stock rom available from sammobile using Odin(3.04). (United Kingdom (O2) 2013 March 4.1.2 PDA-I9100XWLSD CSC-I9100O2ULS7). Yes carrier is important as Modem file differs based on which carrier you use.
This will fix the recovery and will get you on stock JellyBean.
but it seems using a CWM (is this the correct term?!) might now be the chosen route to flashing?
Click to expand...
Click to collapse
CWM is clockworkmod recovery which provides options for flashing custom roms(CM10, SlimRom, NeatRom etc, there are so many).
So what's critical here? Is my carrier relevant? Is it not possible to go from some firmwares to others? Do I need a different kernel for some firmwares? Or is my mistake in thinking it's as straight forward as I'd like, when in fact all the above make a critical difference in which firmware I can flash, and therefore I should stop trying??!
Click to expand...
Click to collapse
Searching in sammobile for firmwares you will find different firmwares for different carriers. You can flash a UK firmware for some other country, but might have issues with call reception, 3G connectivity, etc. as the modem files are different.
It is possible to go from some firmwares to others.
Stock Roms come with Stock Kernels. When you flash a ROM, kernel will remain the same.
You need to change kernels if your phone is consuming too much battery, crashes etc. This normally happens after flashing custom roms as the kernel is not capable enough to handle the updates in the rom.
Dont stop trying, you will love your phone, once you start flashing the awesome roms,kernels found in xda.
Cheers,
Maddy
Galaxy S2 || CM10.1 nightly 4.2.2 || Dorimanx 9.24
Most of the above is good advice. ....apart from the kernel bit.......
All custom roms and firmwares come with their own optimised kernels. These kernels get flashed during the rom/firmware flash. You can choose to install a custom kernel after you have flashed your chosen rom/fw. Custom kernels offer more control over your OS. All custom kernels offer cwm or twrp (depending on the kernel) and will root an unrooted phone. Most need to be Odin flashed, but some (PhilZ) can be flashed via stock recovery........
Sent from my GT-I9100 using xda app-developers app
Hey guys! Thanks so much for the friendly replies - I thought I might have got abuse as a noob, possibly asking very repetitve questions!!
So then with my recovered GSII, I decided to give it another blast and, inevitably, it's bricked again! Seems to be the same bahaviour - though instead of hanging on either "Nand write start!!" or Sbl.bin or Cache.img., it's failing on them. And this time, I can't seem to fix it,following Phistacio's guide to fixing an unflashable GSII .
I also tried flashing that firmware you suggested (although as I mentioned, I'm now on T-Mobile, not O2? So also tried T-Mobile's Jelly Bean), though with no success.
To clarify, I've installed Kies, then closed down all Kies processes, started Odin and put the .tar file into the PDA field, left Re-Partition unchecked, with both Auto Reboot and F.Reset Time checked, connected my phone and waited for Odin to recognise it, then pressed Start!
Can you suggest anything obvious that I've done wrong or suggest what I should do next? Thanks so much in advance!
4 things to try.....
Use the original usb cable. ..
Try different usb ports on your pc....
Disable any firewalls......
If you are running windows 7, open odin as an administrator. .....
Oh and a fifth suggestion.....
Try different odin versions...
Edit.....Don't ever flash/select pit
And don't select repartition......
Sent from my GT-I9100 using xda app-developers app
These steps are originally posted by MistahBungle. Follow all these steps, he knows what he's talking about.
*Must run Odin as administrator in Windoze.
*Ensure Kies & it's processes aren't running in Windoze task manager. Kill them if they are.
*Try different USB ports; you must be using a 'powered' or mainboard port.
*Try different USB cables (particularly the cable that came with the phone if you're not using it now)
*Try different versions of Odin (search on here/Google)
*Uninstall Kies, reboot, redownload & reinstall it, reboot, try the flash again.
*Turn off antivirus/antispyware/antimalware.
*Check the rom/kernel you download for corruption. Either check the MD5 sum if you have it (use md5summer or similar), if you don't have the md5 sum or can't check it, programs like 7Zip, IZarc, WinRar, etc will allow you to 'test' the rom file you download. If there are any errors/any of the files fail the test, bad download. Try again/try downloading with a different internet connection if it keeps happening.
*Run Windoze Update.
*And if all these steps fail, try a different PC. And if it won't work first go on a 2nd PC, go thru the above steps on that PC. Still doesn't work ? User error (will be almost impossible to say what given we're not there looking over your shoulder, almost always something very obvious being missed) or borked phone - return to service centre or local mobile shop.
I suspect many cases where people (say) they do all the above & still can't get it to work involve problems with the USB ports on the machines they're using. Something along the lines of the port is unable to maintain a constant connection between PC & phone; if that connection drops for even a millisecond (probably not even long enough to be registered as a broken connection by the PC in the normal way), you end up with a constantly failing flash at best and a bad flash which borks your phone at worst.
Obviously the only way I'd be able to test the theory would be to examine/test a bunch of PC's belonging to people who experience this issue, but I've given this issue a lot of thought over the past 18 mths & it's the best explanation I've got for those instances where people are being completely honest about having tried all the steps over & over and on multiple machines (a very very small % of people, most people either simply don't do every step over & over and say they do, or they forget they've forgotten they did A, B & C but not F) & still find they can't flash successfully (and it isn't a case of the phone being borked).
See how you go with that.
Sent from my GT-I9100: Powered by Dorimanx, running RootBox
Thanks so much for all these useful replies - really was expecting to get fobbed off for my noob questions! What a nice community!
I'll try all the above and report back. I have successfully flashed on this computer before and did manage to restore the phone last time, though perhaps the cable is faulty and slightly intermittent? I'm using the USB port that's connected to the mother board too.
Thanks again...
Quite possible. And impossible to diagnose unless you strip the cable (which is pointless given fixing a $10 cable is a waste of time/effort). Go thru the steps Hopper listed (with multiple PC's if necessary) & definitely try a new cable if you need to. Try to get an original Samsung one if you possibly can; for some reason switching to one magically solves this problem for some people when nothing else seems to work.
joelinit said:
perhaps the cable is faulty and slightly intermittent?
Click to expand...
Click to collapse
MistahBungle said:
Quite possible. And impossible to diagnose unless you strip the cable (which is pointless given fixing a $10 cable is a waste of time/effort). Go thru the steps Hopper listed (with multiple PC's if necessary) & definitely try a new cable if you need to. Try to get an original Samsung one if you possibly can; for some reason switching to one magically solves this problem for some people when nothing else seems to work.
Click to expand...
Click to collapse
Thanks! Yeah the cable will be the first thing I'll try changing. It's odd that the flash seems to fail at the same point each time though, kind of implying that it's not an intermitted cable? Unless this particular cable is falling short at those particular functions or something?
Anyway, thanks again - I'm actually kinda enjoying learning about my phone, even though there's the fear it's now a brick!! Fingers crossed that's not the case though...
Well how about that - change the USB cable, and flashes successfully first time round! What a fool! I did also remove the battery/sim for the night and left the sim out during the flash - wonder if that made any difference too?
Thanks so much for all your friendly and helpful replies - I think I'll be sticking around this forum and searching for some custom ROMs to try out!
Happy Wednesdays all...
joelinit said:
Well how about that - change the USB cable, and flashes successfully first time round! What a fool! I did also remove the battery/sim for the night and left the sim out during the flash - wonder if that made any difference too?
Thanks so much for all your friendly and helpful replies - I think I'll be sticking around this forum and searching for some custom ROMs to try out!
Happy Wednesdays all...
Click to expand...
Click to collapse
Good job, glad you got it working keep reading up before you do anything else. The more you read, the better you'll get at all this
Sent from my GT-I9100: Powered by Dorimanx, running RootBox
Hopper8 said:
Good job, glad you got it working keep reading up before you do anything else. The more you read, the better you'll get at all this
Sent from my GT-I9100: Powered by Dorimanx, running RootBox
Click to expand...
Click to collapse
Will do! Looking forward to exploring new firmwares so will get as clued up as poss! Have now successfully flashed SentinelROM and loving having a "new" phone! Much more exploring to come.
Thanks v.much to all who've helped me in this thread...
Hey, guys, I made a mess.
A long time ago I decided to try out CyanogenMod for my S3 and then everything went well. I got it up and running and it was a cool ROM but I decided to stick to stock at that time. So I looked for a tutorial online and managed to get it back to stock 4.1 Android running well and as usual.
The issue I had then was that I couldn't update my phone from Google's servers anymore. Every time the phone tried to update the firmware I'd get an error, no matter if I tried it through Kies, the phone or whatever. So I decided I'd just install a ROM for a more recent version.
I found a post on a tech blog here in Brazil saying that OmniROM promised they finally had a somewhat stable version of KitKat 4.4
I went on to install it to then find a beautiful, but still very glitchy ROM. My phone froze all the time and it was starting to bother me. My initial plan was to stick to it until it got better, get the daily updates and stuff, but my phone was way too unstable for that too. So I said to myself: "Okay, no problem, so let's get a stable ROM on this little guy."
I downloaded PA 4.3 and proceeded to get it on my phone. That's when the issues started happening. I couldn't find the .zip from CWM no matter where I put it, and my sdcard1 was full because of the previous backup I created (there was a problem with that too, MD5 mismatch, but I didn't lose anything important so that's okay).
Then I did something even more stupid. I figured, why not clean up the backup and get the .zip there, so maybe it'll show up? At that point the sdcard0 (internal storage) was all different and I couldn't find the .zip for the OmniROM, but when I was on CWM it showed up instead of PA's. The problem with that is that I somehow wiped out CWM and now I can't get to recovery. If I boot up my cellphone through OmniROM, it loads up fine but I can't download the ROM Manager or the superuser from the Play Store. I'm trapped with OmniROM and it's working even less well than at first.
What should I do? Is there a way back from this? I'd really like to have my phone running again soon, I need it to keep in touch with my parents since my grandma died recently.
Thank you in advance.
EDIT: Okay, some progress. I remembered that I got CWM on the phone through Odin and went through that again. I have CWM back but still, my internal storage fails to recognize the new .zip files and only shows OmniROM's. The folder is completely different when I connect the phone to my computer. I got to see the .zip files at the sdcard1 but CWM says they're bad files. I'll trust it and redownload/transfer again. We'll see what happens.
EDIT 2: Trapped again. Can't find anything on Google. It sure sucks to be me. I can't even figure out how to get everything back to stock so I can try again. Tried turning USB debugging off but it didn't make a difference. The CWM shows me the two OmniROM .zip files and my computer shows me the PA .zip files. I'm just...
first- try to flash newer cwm based recovey. I suggest philz (is has both Odin / cwm based install):
http://forum.xda-developers.com/showthread.php?t=2002953
after flashing is complete- try to download this rom:
http://forum.xda-developers.com/showthread.php?t=2060403
and check if you can see it.
(you can put it in your internal or external sd, philz can access them both)
Before installing the new rom, I strongly recommend doing a 'wipe to istall new rom', cache wipe and delvik.
good luck
Sent from my GT-I9300 using Tapatalk
Yay, thank you! I'm not trapped anymore. The PA rom I downloaded is still "bad", but that's probably its own fault. I'll wait until NeatROM's download is complete and try with that. I'll edit this if things turn out well.
Thanks again!
EDIT: So, I tried with NeatROM and it also says it's bad. But I only tried on the external storage, so maybe that could be it. My sdcard has been returning some really funky errors when I get it on my computer so I'm worried it might be a bit compromised (and I actually found it at a bus terminal, so it never really worked properly even after formatting).
Thing is when I did the wipe I picked the option that wipes it for a new ROM, so OmniROM is gone. Is there a way to get USB connection through CWM so that I can transfer NeatROM to the internal storage? I only have this one sdcard.
EDIT 2: Finally got it! Thanks so much, amirTor, my S3 is back on track! The sdcard was the bad one, not the file. But the PA ROM didn't work anyway. I might stick to NeatROM or maybe look later. I'm gonna take a week off of all this after so much trouble.
Glad I could help (even though it seems that you pretty much helped yourself...)
1)If you got Sandisk SD card, make sure to follow my post on thread: http://forum.xda-developers.com/showthread.php?t=2614170
2)You can mount your phone to be shown in your pc even when in recovery mode: Mounts and storage-> moun usb mass storage
3)You should definitely stick with neat- the best stock (and aosp) rom there is :good::good::good:
ps- hitting the 'thanks' button will be appreciated :angel:
Done and done!