I'm trying to get Kies to work with a custom ROM. I've tried several roms over the past few days trying to find one that performs great and feels good to me but I just realised that Kies won't give my info back.
There's a few important things I backed up which I need... It's my own fault for not paying attention when I got giddy with ROM swaps, but I'd sure appreciate some help.
Kies, smart switch, and Odin don't work with cm Roms.
It would be simplest flash stock, restore from kies, save what you need on a non-proprietary format, and then flash a custom rom.
I may flash to stock anyways, then root and remove the garbage programs I don't use.
Related
Hello, I have had no problems flashing various roms on my Samsung vibrant, but I would like to reset the phone completely. As in delete everything as if it were stock. Now that I've found the settings I wanted, I'd like to start from scratch and flash the latest root, OCv4 kernel, and vibrant 6 (I love the swype keyboard and vibrant 7 removes it).
Its very easy to add swype back into vibrant7. I have done it on mine multiple times. As far as complete stock reset you will need to look up odin and get all the accompanying stock files to flash with. If you need more detail search on odin flash stock rom or words like those I dont happen to have the link handy
Back in the old days when I was flashing my HTC Magic, it was a breeze to flash one ROM after another without a glitch. But now I am wondering the rule of thumb when it comes to flash different ROMs on Vibrant.
I have been using Axura 2.1 for a week now and even though I am extremely happy with it, there will be a time when I want to flash something else. When that happens, what is safest way to go? Since I used CWM to flash Axura, I have never used Odin. No idea what a PIT file is etc. etc. Can you please guide me to the right thread? What happens to the OCLF once you want to flash another ROM? Do you need to undo it so it won't cause a brick? Anything else I need to know?
Thanks a bunch!
Always disable a lagfix (and I prefer to not use them) before flashing ANYTHING.
You can swap from rom to rom relatively safely without using ODIN. I tried 3 rom's yesterday and didnt notice anything wrong with any of the roms.
If you do have an issue, you can use ODIN. I have videos in the sticky's, and the development bible sticky makes it very easy to find the files too. Just ODIN to JFD (stock) and then root it again... flash clockwork again... then flash the new rom.
some people say to odin back to stock between roms, but this is unnecessary. i've flashed over 15 roms on my vibrant without touching odin, just using clockwork, with no problems.
Dear,
Who off you will be so kind to send me his/her stock /System/App map to me.
Stupid me....!!!
I was fiddling arround in my Tab and was deleting some stock apps.
Used System App Remover.
I had Launcher Pro so i thought touchwiz can be deleted to.
I had a backup made and copied it (stupid me) to the internal SD
After a while i was doing something which my Tab did not like.
So a full hard reset was necessary.
Stupid me forgot to put touchwiz back.
Now i have a Tab which shows a black-screen with only the notification-bar.
And a lot of errors,especially "proces android.process.acore" and more.
After some searching i downloaded a modified touchwiz from here.
Because i still can boot to the boot-loader and via android-commander i copied that apk to \system\app map.
Did a factory reset via the boot-loader but nothing happens.
I still have the same black-screen with notification-bar.
Before you ask:
I have a stock Tab and stock boot-loader.
It is rooted with Superoneclick.
So there for i can not (i think) flash a new rom.
So please can someone help me out...
Thread can be closed.
Took me two days of searching but i managed to get my Galaxy Tab back in business.
Found a rom on samfirmware an got it flashed by Odin.
I know I am a bit late to your party and sorry for that, but I only got mine done properly yesterday, was a bit confused with the conflicting info.
Anyway my point is you certainly can flash custom roms, use ODIN to flash MoDaCo's Kernel, either ext4 conversion version if you want ext4, or the RFS version if you want to keep RFS, and then use CWM Recovery to flash CWM compatible roms, such as Overcome Rom (Personal Favorite of current roms, especially with the new Kernel included )
Some good instructions here: http://droid-den.com/phone-guides/phone-guide-install-custom-modaco-rom-and-kernel-on-samsung-galaxy-tab-guide
Just filter the instructions for yourself, such as install the Kernel only, different rom, etc.
Thx for your reply.
I will look into those rom and flashing it...
(Swiped from my GT-P1000 using Tapatalk)
corodius said:
I know I am a bit late to your party and sorry for that, but I only got mine done properly yesterday, was a bit confused with the conflicting info.
Anyway my point is you certainly can flash custom roms, use ODIN to flash MoDaCo's Kernel, either ext4 conversion version if you want ext4, or the RFS version if you want to keep RFS, and then use CWM Recovery to flash CWM compatible roms, such as Overcome Rom (Personal Favorite of current roms, especially with the new Kernel included )
Some good instructions here: http://droid-den.com/phone-guides/phone-guide-install-custom-modaco-rom-and-kernel-on-samsung-galaxy-tab-guide
Just filter the instructions for yourself, such as install the Kernel only, different rom, etc.
Click to expand...
Click to collapse
Thx for your tips.
I heave my already rooted SGT flashed with overcome and have Clockwork Recovery v3 flashed aswell.
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".
I have been unsuccessful for a while, and i need to find one. I would love to enjoy KitKat again, but that's just me I guess... Thanks in advance.
Also, i have looked for AGES and cannot find anything. I tried flashing a stock rom but Odin gives me errors.