Ok, I want to leave a message on here for future noobs like me with a Galaxy S
i9000 but it might work for others too.
My issue when flashing custom roms is that I have not been able to access my galaxy from my computer via usb since literally day 1 (when it did work once).
I spent a week trying to connect to Kies on multiple computers (vista and Windows 7). Tried via Android SDK, even tried hiemdall. I almost tried in ubuntu also but I never did get that working as I really don't know linux well enough. I've now given up...
So then I saw that you can do flashing all on the phone with the clockwork mod. With clockwork, my first rom flashed, well, like clockwork! But then I had some issues with lag and hang ups and reception and I decided to switch to another rom (seearms jl2 based rom - good stuff so far).
However this rom install went sideways... It said that it had installed ok but on reboot it stalled on the Galaxy I9000 screen and froze. Luckily I could still use the 3 button recovery to boot to clockworks but the hitch was that I HAD NO OTHER ROM to flash back to.
I had done a backup through clockworks but when I tried to restore it said the systems.img file was missing so it skipped it and the end result was the same freeze.
Normally everone says to reflash at this point with odin but that was not an option for me. So this is where I got lucky. The SeeARMs rom included Steam recovery module (though I thought it was the stock 3 button recovery menu for a while - I was panicking a little). I highly recommend seeing if you can get steam because it allows access to the External SD card for flashing which can be a lifesaver. Ahh, finally I could get the old rom on that, reflash it and go one with my life. My theory being that at least the issues would be aligned with the this rom and it worked.
So the lessons I learned:
1) Always have your new rom and your old rom on the interanal SD card in case of issues.
2) check your nandroid backup - even try testing it? - they don't always work perfectly with every device.
3)I highly recommend finding out if Steam or similar will work if you cannot access the USB connection and load things on when things go wrong.
Some tips I saw that also worked for me
1) flash a new kernel before you flash a new whole rom.
2) if things go sideways, try redownloading or retransferring the file to make sure there were no errors.
I did both and then reflashed (with my old rom Voodoo Doctor, SeeArms Rom and Darky's 8.1 rom on the card just to have options) and all was good!
PS: the steam recovery knocked off the first letter of the file when executing for some reason so I had to make 2 copy's of each rom I wanted access to ie Darkysrom.zip and arkysrom.zip just look for that error when you are doing this.
Good post - hopefully it'll help someone out who's stuck.
Hopefully
I'd like to stick some of that in on the thread for your rom but I need put another 7 half relevent messages out there before I am worthy... I understand the rule but I'd rather only post where it is meaningful...
GF
Related
I spent all day yesterday trying to fix my Epic with no progress and feeling a little sol.
Yesterday I decided I needed a new ROM/kernel because I was averaging only 4hrs of battery life with Supernova and wanted to try Nebula ROM with EXT4. I backed up everything on my laptop and did a Nandroid backup as well. I also have Titanium backup backed up on my pc. I always always back up. I started fresh by flashing to stock and starting over. I rooted with 1 click, flashed DK28, and where I believe I screwed up is I didn´t upgrade to Clockwork 3 (looking back I don´t know wtf I was thinking by proceeding the following way), instead I went to advanced, reboot recovery and ended up rebooting my system into 2.5.1.2. I rebooted my phone and all was good, powered off, 3 fingered and I still had 2.5.1.2 so like a dumbass I figured I was good to go ahead and flash Nebula. LOL so what happened? the Rom installed, I finished like I always do and when I went to boot up my phone I flashed into v2.5.1.0 and thats where my phone stays. If I try to do anything it gives me E: Can´t open/cache/recovery/log
I tried to restore of course and I get this message. I have tried to Odin back to stock but my phone will not connect to a pc.
Heres my situation. I live in a house with 6 computers that I have attempted to connect to with no luck, 5 of these have adb and the Android SDK, several drivers (including the Epics) installed and the C drives have literally no more space. The other pc has Windows 2000 so I wondered if it won´t install the drivers or pick up my phone because its so old??? My main laptop is running Ubuntu and Im not understanding how or even if I can Odin my phone on it, besides I think this laptop won´t connect to my Epic because of the USB port and I dont have a clue how to detect or fix that. My mom has a brand new PC with Windows 7 thats never had anything connected via USB yet that I thought was worth giving a shot at. I only have the stock USB cable though and I was wondering if I bought a new cable if it would be more likely that my phone would connect.
I am not very educated on Android or computers so I prob shouldn´t have done as much flashing as I have to begin with. If I understood file systems better I would prob figure it out.
Thanks for any help or advice. If I over looked the answer in front of my face I am sorry it is because I am retarded and don´t understand computer lingo.
Are you connecting the proper way to odin?
Step 1: open odin with phone Disconnected from PC (if you dont open it first it may not recognize your phone, so i hear)
Step 2: hold 1 on keypad and power on phone --> download mode
step 3: connect phone to PC
step 4: Flash rom
if odin still isnt recognized I would suggest taking out your microsd card and put it in another phone or a microsd card reader and put a basic dk28 rom/dl18 (maybe the acs one that includes modem) rom on there then put the sdcard back in your phone and flash that in clockworkmod and see if it'll boot (wide data/cache/dalvik before doing this)
Also search the forum i'm pretty sure theres an RFS formatter somewhere that'll format your /system/data/cache back to RFS, you probably need to do that before flashing back the other rom...
So, if I understand the OP correctly, you accidentally flashed an ext4 only rom on rfs with 2.5.1.0?
This thread had a flashable reRFS conversion, just in case you need it.
This thread has a cwm flashable di18 and modem.
Those should get you up and going again with cwm 2.5.1.0. If they don't, Odin is really the answer and I don't know what to tell you.
So I tried both of your ideas and I am so pist off. I am now stuck in download mode and cant get 7 freaken computers (one literally brand new with Windows 7, one with Vista, one with XP, 3 with Linux, 1 with 2000 out of being desperate with 5 different usb cords to connect. Clearly my phone is the problem because the sd reader can read my sd just fine and my mom, sister and gramps connect o the same computers just fine. Ive accepted that I am ****ed at this point. I have never got this phone to stay connected to a pc and I think I hate it.
It is starting to sound like it is time to head to a sprint store.
Erica8123 said:
I am now stuck in download mode and cant get 7 freaken computers (one literally brand new with Windows 7, one with Vista, one with XP, 3 with Linux, 1 with 2000 out of being desperate with 5 different usb cords to connect.
Click to expand...
Click to collapse
Have you tried to just pull the battery out? Then, put it back in the phone and boot into CWM? Or pull the battery, then boot into recovery? I personally hate going to the Sprint store and I try every possible option before going.
If you can get another USB cable it will probably work. I use an evo cable. Also for future reference there are no custom kernels on dk28.
Sent from my Evo Killer!!!
Hey, I just wanted to update.
I had tried several usb cables to connect btw including a new one I just bought. No luck. I had tried literally everything to fix my Epic and I was super pist during my last post lol. I finally had to cave and take the block walk (literally) down to Sprint and thank God I insured my phone. He was hella cool about it, just laughed and said he doesn't want to bother with it and replaced it. I am still trying to decide what I wanna do as rooting goes (besides getting rid of pretty much every app they put on there).
Thanks again everyone
Excuse the long thread title lol..
I've been gently lowering myself into all this tampering with my phone as I've always been a bit of a tinkerer with everything i've ever owned.
So back in march my phone, an unbranded handset on o2 uk was on 2.2.1. My first foray into modifying my handset was to flash the jvk gb firmware. I then rooted it using cf root. All very simple. I then flashed it using cwm with Simply honey 3.2 and then the latest 3.5. No issue.
So this afternoon, I flashed it with the "unspoken ones" kernel just cos I could lol. Something didnt seem right though. There was a bit of lag and I got one or two forced closures so I decided to restore one of the cwm backups I had. Thing is, it hung upon reboot at the i9000 screen, for about 10 minutes so I pulled the battery. Now I couldnt get it restarted. Panic set in. This was my first proper issue and I just wished I was back in march on 2.2.1 again.
As said, couldnt get it started so went hunting some advice. Install a base stock rom with 3 files and a 512 pit. I struggled. Could I find 3 files ? Nope. Not on samfirmware. Every file I downloaded was one file. JP1 JPU JPY. All 1 file. So. As JPY was the firmware I was on originally, I chose the 1 file version, put the phone in download mode and flashed it via odin. It worked !!! And then I plugged it into kies and up popped the box, I have an firmware update ! JPO GB! So i installed that. I'm quite surprised that I got the update because you always see lots of threads regarding people being unable to update by kies once they have modified their phones. Why did mine work? Because the handset in unbranded perhaps ?
Anyway, I wanted to get back to the Simply Honey rom because it ran really well and the battery life is fantastic but Simone hasnt done a version based on JVO yet as far as I could tell so I thought, I know, I'll root with cf root, again and try that backup again using cwm. And it worked, and here I am back where I was earlier today ! Ace ! lol
Sorry about the essay but I'm sure that there are some questions in there worth answering.. ?...and also to serve as a bit of help to those that find themselves in a dodgy situation. Just calm down, search for the advice, it is out there and do as it says and everything will be cool
Posted from my restored and working handset...
the files you download from samfirmware are rar files (have a .rar extention). This means you need to decompress them into a folder and the "three files" will be in there. You need a rar extractor app. You can use 7-zip which is free.
You need odin (or ezodin or heimdal) to flash the stock rom but I am sure you know that already. There are a few guides around for all tools.
There is a lot of information here, especially in the "sticky" posts. If you feel like learning what you are doing rather than copy instructions (as I think you do), it may be a good idea to go through them.
Anyway you got your phone working in the end so that's good!
simple solution when an install hangs is only to reflash the kernel in odin: that restarts the phone.
cwm is not invincible and the restored rom is there but the phone hangs on the boot because of the kernel hiccup. Reflashing the kernel to the one you now want will allow the phone to boot and access the rom that matches -- you do have to ensure the recovery version rom and the kernel you are flashing are in sync.
Persist. You only really panic the first time this happens -- after that you know it is a possibility and how to fix it.
Worst case scenario: pull the battery, reinsert, go to download mode and reflash the kernel and base rom of your choice. At least now you have a clean phone!
Two things are important to remember: (1) always do a backup before installing a new rom or kernel and (2) use titanium backup for all applications -- easy to restore everything.
Also I find it easier to use google calender and my internet email as bases for dates, appointments and contacts -- that way if I loose everything on the phone I can quickly reload my data by sync with online accounts once I have the phone "rebuilt".
My son and his girlfriend have a vega each, however they seem to be both rather unwell after a hasty attempted flash by him, (I know we'd all have stopped at one ). However that's my situation.
I have all the tools and drivers and roms, when they initially both them they were flashed with r8 custom rom from modaco.
He has attempted to flash them both with the new vegacomb rom using the rom manager app, all seemed fine I'm told all prgress bars 100%, on re-boot though they failed into a blank screen.
I have attempted to re-flash (with nvflash) them but I get diferent errors each time from bootloader fails to recovery fails (yes i tried the stock rom from the vega home page, along with many other roms). Any help would be most gratefully accepted
More Info
http://android.modaco.com/topic/345...icked-vegas/page__gopid__1782997#entry1782997
Just to keep a tidy thread I have linked the responses from modaco
Hi there, taken a quick look through the responses over at modaco. I would start totally from scratch. Re-install the usb drivers from the advent webstite. Re-download the stock rom from the advent site (to make sure yours is not corrupt) and flash it. Looks like you have the procedure sorted, so it must be down to the drivers or the rom image. To have the only 2 bricked vegas in existence would be the worst luck ever!
Good Luck
make sure they are charged, it won't do an nv flash if it's not charged past 60%, something I stumbled with for a few days till i left it to charge overnight before flashing
and a slap at the back of your son's head will work well as well.
Edit - should of read the modaco thread first - fixed with a new lead
the newest honeycomb roms need a modified base rom:
http://tabletroms.com/forums/vega-r...ddedstock_1-10-v2-updated-stock-rom-base.html
Then you can apply latest vegacomb using clockwork mod recovery (factory reset and clear dalvik cache in cwm before applying the roms just to be belt and braces):
http://tabletroms.com/forums/vega-rom-development/1923-[rom]-[3-2]-vegacomb-3-2-build-6-a.html
As above make sure USB drivers are installed correctly and Vega has mains plugged in while doing all the flash work.
Not heard of a bricked Vega only physical breakages.
Good luck
Ok, i realize i have a different phone from this thread but it is close and my problems closely reflect the issues ive seen with the Galaxy S.
A little background. Im no perfect i know what im doing when it comes to rooting. I have an HTC Tbolt and rooted many of those, an older touch pro 2, and this is first time doing a samsung. I am getting the hang of ODIN (i wish everyone would just use this program instead of bouncing back and forth between heimdall and ODIn but whatever) Im liking ODIN cause it works well. I was successful at flashing a new rom into this Samsung phone. 95% of it worked, wifi i think didnt but everything else worked. While trying to fix the phones wifi somehow i have stopped the phone from booting into CMW recovery unless forced or booting into a rom. I can get into CMW but i must hold down the Vol Down button to get there, otherwise a clean basic boot takes me to the stock android system recovery screen and will not boot a rom.
I have something backwards or out of order. I am just trying to get the rom to identify the installed CMW and the installed ROM through CMW but it wont do it.
Any help would be appreciated, i dont want my GF to find out i jacked her phone lol
Which phone do you have? SGS? I can just talk about SGS+ but I guess its similiar.
Try to install CWM with Odin, normally it should replace the stock recovery (haven't heard of both running at once).
Once you have installed CWM you can install your custom ROM with CWM (look at the install instructions).
If you want to install stock ROM with Odin it will replace your CWM with stock Recovery.
Post the link of the thread/recovery you want to flash.
annqx said:
Which phone do you have? SGS? I can just talk about SGS+ but I guess its similiar.
Try to install CWM with Odin, normally it should replace the stock recovery (haven't heard of both running at once).
Once you have installed CWM you can install your custom ROM with CWM (look at the install instructions).
If you want to install stock ROM with Odin it will replace your CWM with stock Recovery.
Post the link of the thread/recovery you want to flash.
Click to expand...
Click to collapse
Its a stratosphere. Im using the root and / or stock files in the root method. I use ODIN to flash the StratCWMRecovery.tar.md5 and if i tick "reboot" then it reboots into CWM i install a rom or stock rom and it finishes. I reboot the phone and it instantly goes back to android system recovery. If you like ill make a short video to give you an idea of whats going on.
I will note that im close to making a jig but its not 100% bricked obviously. 3 button method still works (and unecessary at this point since all the phone does is go straight into the stock bootloader) and then after i install CWM i can force it in to CWM but it wont actualy boot into it.
From a programing standpoint i feel the pointers or partitions are incorrect. Its like booting a computer that has a hard drive with windows installed however getting the bios to tell it to boot from the hard drive isnt working. THats the easiest way to explain this.
One thing i want to note is the only errors i am getting are when i try to partition the SD card from CWM. I get an error saying sdparted is not found.
I am not getting a full understanding of how the root system works on this phone.
Again any help is appreciated.
Made a short video. Its uploading now. http://www.youtube.com/watch?v=tFZ5Adm5AdQ
So whatever i did i was able to fix. I think me being a very visual person and normally having access to all files i need or could use in a situation is always nice. Here, i didnt but i found them. Here's the link. Its obviously for stratosphere but i took about 10 minutes and let ODIN install all these files and it worked.
original posting but the link doesnt work for download
http://rootzwiki.com/topic/11183-eh2-full-factory-odin-restore/
where i downloaded it
http://www.fileswap.com/dl/t4D235pUTO/SCH-I405.EH2_rel.md5.html
Again this is for stratosphere. Since it really helped me return to stock and allow me to re root in about 15 minutes this thread should be moved but there is no stratosphere area
So super sorry for this one, but 9 hours of trying has left me no choice but to beg for help and I am running out of time to search for the solution.
Ok, I have softbricked my s5360B, foolishly I didn't make a rom and/or kernel backup before I tried messing around with my phone, I was trying to simply network unlock my device, I return back to the UK from Brasil on Saturday and I need an operational phone so I can get home.
I settled on using JellyBlast rom for my installation but after running into installation errors like (status 7) and later on a (status 0) I got frustrated and tried installing any of the .zip files (JVBota1signed.zip and filetypes similar to). And I think I messed up badly - the phone when booting has the original 'samsung galaxy y s5360b' screen but does not move past it, at one point it flicked back an to from this splash screen and Vivo (brasil network carrier) but now it does not. I still can boot into CWM recovery (v6.0.4.9) which is a good sign I think.
As a mac user I am a little adversed to using Odin - Windows 7 via Parallels recognizes the phone and begins installation of stuff, but hangs up at 'setup connection', so I think I need a solution that I can use just the SD card for. I need a fix as quick as possible - I have only 2 days left here and during that time I have to say my forever goodbyes to my love.
Bottom line - I need my phone operational ASAP - I don't care about what version of rom or kernel it is running (be it factory stock or custom), just so long as I can be network/carrier unlocked. If you have a viable solution for me can you please post links to downloads for the files I need? And if there is any more complexity than 'install this then this' then I may struggle. What do I do?
Really appreciate the efforts of the community, thanks guys!
DreadyBear said:
So super sorry for this one, but 9 hours of trying has left me no choice but to beg for help and I am running out of time to search for the solution.
Ok, I have softbricked my s5360B, foolishly I didn't make a rom and/or kernel backup before I tried messing around with my phone, I was trying to simply network unlock my device, I return back to the UK from Brasil on Saturday and I need an operational phone so I can get home.
I settled on using JellyBlast rom for my installation but after running into installation errors like (status 7) and later on a (status 0) I got frustrated and tried installing any of the .zip files (JVBota1signed.zip and filetypes similar to). And I think I messed up badly - the phone when booting has the original 'samsung galaxy y s5360b' screen but does not move past it, at one point it flicked back an to from this splash screen and Vivo (brasil network carrier) but now it does not. I still can boot into CWM recovery (v6.0.4.9) which is a good sign I think.
As a mac user I am a little adversed to using Odin - Windows 7 via Parallels recognizes the phone and begins installation of stuff, but hangs up at 'setup connection', so I think I need a solution that I can use just the SD card for. I need a fix as quick as possible - I have only 2 days left here and during that time I have to say my forever goodbyes to my love.
Bottom line - I need my phone operational ASAP - I don't care about what version of rom or kernel it is running (be it factory stock or custom), just so long as I can be network/carrier unlocked. If you have a viable solution for me can you please post links to downloads for the files I need? And if there is any more complexity than 'install this then this' then I may struggle. What do I do?
Really appreciate the efforts of the community, thanks guys!
Click to expand...
Click to collapse
How did you tried connecting phone to odin? Did you went into download mode then connected the phone to pc ?
DreadyBear said:
So super sorry for this one, but 9 hours of trying has left me no choice but to beg for help and I am running out of time to search for the solution.
Ok, I have softbricked my s5360B, foolishly I didn't make a rom and/or kernel backup before I tried messing around with my phone, I was trying to simply network unlock my device, I return back to the UK from Brasil on Saturday and I need an operational phone so I can get home.
I settled on using JellyBlast rom for my installation but after running into installation errors like (status 7) and later on a (status 0) I got frustrated and tried installing any of the .zip files (JVBota1signed.zip and filetypes similar to). And I think I messed up badly - the phone when booting has the original 'samsung galaxy y s5360b' screen but does not move past it, at one point it flicked back an to from this splash screen and Vivo (brasil network carrier) but now it does not. I still can boot into CWM recovery (v6.0.4.9) which is a good sign I think.
As a mac user I am a little adversed to using Odin - Windows 7 via Parallels recognizes the phone and begins installation of stuff, but hangs up at 'setup connection', so I think I need a solution that I can use just the SD card for. I need a fix as quick as possible - I have only 2 days left here and during that time I have to say my forever goodbyes to my love.
Bottom line - I need my phone operational ASAP - I don't care about what version of rom or kernel it is running (be it factory stock or custom), just so long as I can be network/carrier unlocked. If you have a viable solution for me can you please post links to downloads for the files I need? And if there is any more complexity than 'install this then this' then I may struggle. What do I do?
Really appreciate the efforts of the community, thanks guys!
Click to expand...
Click to collapse
The rom you mentioned is a banned rom
You have 2 options
Option 1
If you can get into recovery mode (Vol up home button power button)
Download any stock based custom rom
Go into cwm
Format system data cache
Mount system data cache
Flash rom zip
Assuming that you are using a stock based kernel it will boot
Option 2
Flash stock rom via odin
See my firmware thread link in my signature
Note you can use standard 5360 firmware instead of the b variant which may be better
Posting to say I didn't get the phone to work still, but I got home without too much trouble. needless to say this thread is no longer an emergency.
I want to express my gratitude to you guys for helping me out, thank you so very much.
Unfortunately as I say the phone does still not work -
With multiple attempts using ODIN I keep getting the hangup at 'setup connection' - I tried on mac via parallels (windows 7) and a windows 8 machine.
I can successfully install a ROM via CWM but the phone gets stuck in a boot loop (samsung galaxy y splash screen) so I'm guessing I have a kernel problem? When I try flashing a new kernel I get the "error mounting /sd-ext!" message, and the same when I try to format it via CWM. I found this: http://forum.xda-developers.com/showthread.php?t=1750888, but I cannot boot the phone so I guess I'm stuck.
My last install attempt was these
http://forum.xda-developers.com/showthread.php?t=2462914 - V3LenoxEvolution ---- SUCCESSFUL INSTALL.
http://forum.xda-developers.com/showthread.php?t=2644262 - Blackheart kernel ---- FAILED, error mounting /sd-ext
Got any other ideas guys? Or do you know where I'm going wrong?
I think I'm in way over my head :s
Many thanks once again!
EDIT: some additional information, I cannot reboot to bootloader, and as far as I can tell I can't replace the custom recovery CWM v6 (I find a different version, boot into CWM v6, click install .zip from sd card and say CWM v5 launches, but when I reboot it's back to v6)
Flash stock rom via odin....
Flashing other diffrent ROM packages won't help until you have right bootable kernel...
So put your efforts towards making it to boot up on a stock firmware....
By ODIN mode
Try installing drivers and checking that no other device is connected to pc via USB.
Also make sure you follow the guide properly....
Then post errors ...or try google...
We'll help...
Sent from my GT-S5360 using XDA Free mobile app