Related
Hello All,
This is my first post! But I have been visitor of this forum for some time now. Its been a great learning experience! OK ...let me come straight to the point..
Important Phone Specs:
-Samsung Captivate with stock ATT froyo (UCKB1)
-rooted, installed one-click lag fix (other minor things, like removed all bloatware, overclocked etc.)
I am planning on changing the icons in the notification bar (for example battery icon mod) using UOT (ultimate online theme kitchen) and I have the UOT zip file ready.
Q1. It is not clear if this zip file can be flashed from the stock recovery mode.
Per my understanding, these are unsigned files and hence might not work with stock recovery mode. Can some one please confirm?
Q2. If stock recovery mode does not work, then I plan to install clockwork mod recovery from the ROM Manager apk available on the market.
a) Since I will be using a custom recovery image, I assume I will no longer be able to use KIES to perform any stock updates if and when they become available. Is that correct?
b) How easy is it to revert back to stock recovery? Can you please let me know the procedure (or) point me to a link with this information?
The reason I ask is because I would like to stay stock as much as I can for the moment.
Thanks all for your help.
Regards.
I have used the UOT kitchen zips on stock KB1 but not with the stock recovery. I think you have to use CWM recovery. There's really no reason to go back to stock recovery. If you ever want to use Kies in the future to get updates (assuming ATT ever releases GB through Kies), you would have to flash back to stock anyway for Kies to recognize the phone.
Jackman,
Thanks for the response. I agree with you. I am not hopeful that ATT would release GB any time soon for captivate...so yeah I makes sense to go ahead with the CWM recovery.
I just wanted to know the pros and cons before I get started with the process.
read the how to flash custom roms link in my sig. new user guide too, find the part about stickies.
#1 correct.
#2 rom manager is only good for froyo roms on captivate... there are froyo kernels with CWM built in and tweaked that run fine on stock roms, but you must Odin flash the kernel.... which leads to...
#3 keis is garbage we use odin, the official samsung flasher utility. and we flash the same .tar files keis uses.
#4 easy to get back to stock. odin-one-click stock flashes are ONE CLICK. Sticky in Captivate Dev section. (use new user guide to find.)
Kies is trash. Even if you go back o stock, you probably need to modify code to make sure your phone's ID is still the correct one. It really isn't worth it considering Kies is just ODIN with a different UI and a craptistic amount of "checks" wich makes it fail 90% of the time.
I hardly ever have problems with odin. odin 1.3 sucked 1.5and newer work great. the homemade one clicks can be buggy. md5 check wont let you edit file names of tars. other than that i DONT have problems. its all i use. dont like heimdall and having to change my drivers for it.
Hello everyone!
Have a froyo 2.2.1
These are the details from my phone (SAMSUNG GALAXY MINI GT-S5570):
Have a baseband S5570XXKA5
with kernel 2..6.32.9-perf
and build number FROYO.XWKAC
from dialing *#1234# got this info:
PDA: S5570XWKAC
PHONE: S5570XXKA5
CSC: S5570TMNKB1
Already have a CWM (ClockworkMod Recovery v4.0.0.5)
tried to backup stock rom several times I attach two log files that I extracted.
I am unable to mount (even mannualy) some partitions (if I am reading the logs correctly...)
Does this mean I can't backup stock ROM?
If I do can backup, how should I do it?
Can these errors be related to the fact that I am not using the most recent version of CWM?
I also have another version of CWM for my device. This is a zip file with version 5.0.2.6.
But, as it is a zip file with no IMG file in it, I am afraid that it would harm the phone if I would use it on the CWM recovery that is accessible through boot.
Is it possible to use CWM 4.0.0.5 to update itself?
I tried to use Rom Manager to update CWM (and to backup the rom, and you may very well check that because the names of the logs are different) RM didn't even recognize the already installed CWM, let alone update it or backup the stock rom...
So... can I really update CWM to try that route to backup stock rom?
How to use the zip file? (can I use it with CWM v4.0.0.5 or with ODIN 4.38?)...
I must say that I used ODIN 4.38 to flash the current CWM but the 4.0.0.5 CWM was a tar file.
Finally, all the info that I searched (here and elswhere) says that it is possible to come back to froyo (with the help of samfirmware site) but as I am such a noob I cannot find any ROM that is the same as the one I currently have.
I currently have Titanium Backup installed and it states that the ROM was build on the 2011/02/01 12h12 (can that be of any help to locate the default stock ROM from the ones that are available at SAMFIRMWARE?).
My carrier is TMN from Portugal, but until now, with this info I haven't been able to locate the 'one' ROM that would reassure me that I could upgrade and still have plenty of odds to come back to the startup 'scenario'.
Any help would be very much appreciated.
Thanks.
mzcl-mn said:
Hello everyone!
Have a froyo 2.2.1
These are the details from my phone (SAMSUNG GALAXY MINI GT-S5570):
Have a baseband S5570XXKA5
with kernel 2..6.32.9-perf
and build number FROYO.XWKAC
from dialing *#1234# got this info:
PDA: S5570XWKAC
PHONE: S5570XXKA5
CSC: S5570TMNKB1
Already have a CWM (ClockworkMod Recovery v4.0.0.5)
tried to backup stock rom several times I attach two log files that I extracted.
I am unable to mount (even mannualy) some partitions (if I am reading the logs correctly...)
Does this mean I can't backup stock ROM?
If I do can backup, how should I do it?
Can these errors be related to the fact that I am not using the most recent version of CWM?
I also have another version of CWM for my device. This is a zip file with version 5.0.2.6.
But, as it is a zip file with no IMG file in it, I am afraid that it would harm the phone if I would use it on the CWM recovery that is accessible through boot.
Is it possible to use CWM 4.0.0.5 to update itself?
I tried to use Rom Manager to update CWM (and to backup the rom, and you may very well check that because the names of the logs are different) RM didn't even recognize the already installed CWM, let alone update it or backup the stock rom...
So... can I really update CWM to try that route to backup stock rom?
How to use the zip file? (can I use it with CWM v4.0.0.5 or with ODIN 4.38?)...
I must say that I used ODIN 4.38 to flash the current CWM but the 4.0.0.5 CWM was a tar file.
Finally, all the info that I searched (here and elswhere) says that it is possible to come back to froyo (with the help of samfirmware site) but as I am such a noob I cannot find any ROM that is the same as the one I currently have.
I currently have Titanium Backup installed and it states that the ROM was build on the 2011/02/01 12h12 (can that be of any help to locate the default stock ROM from the ones that are available at SAMFIRMWARE?).
My carrier is TMN from Portugal, but until now, with this info I haven't been able to locate the 'one' ROM that would reassure me that I could upgrade and still have plenty of odds to come back to the startup 'scenario'.
Any help would be very much appreciated.
Thanks.
Click to expand...
Click to collapse
No, you can't backup stock rom.
Sent from my GT-S5570 using xda premium
Thank you for the answer.
Hello thadead,
Yours is a very assertive answer. So I don't have any chance...
But with the info I gave, can I have the 'stock' ROM from samfirmware???
And just some doubt: how did samfirmware got the so called stock roms in the first place?
Thanks for any assistance.
Samfirmware probably could have ripped from Kies update I guess. Not sure though!
Sent from SGM
here some infos on how i made a backup of my roms...
only need to say that you cannot spli CSC and /system, as in original ROMS.
another way can be to check with "check fus downloader" for you rom...
let us know...
Thank you all for all your input!
Will read as thoroughly as I can
Cheers!
mzcl-mn said:
Hello everyone!
Have a froyo 2.2.1
These are the details from my phone (SAMSUNG GALAXY MINI GT-S5570):
Have a baseband S5570XXKA5
with kernel 2..6.32.9-perf
and build number FROYO.XWKAC
from dialing *#1234# got this info:
PDA: S5570XWKAC
PHONE: S5570XXKA5
CSC: S5570TMNKB1
Already have a CWM (ClockworkMod Recovery v4.0.0.5)
tried to backup stock rom several times I attach two log files that I extracted.
I am unable to mount (even mannualy) some partitions (if I am reading the logs correctly...)
Does this mean I can't backup stock ROM?
If I do can backup, how should I do it?
Can these errors be related to the fact that I am not using the most recent version of CWM?
I also have another version of CWM for my device. This is a zip file with version 5.0.2.6.
But, as it is a zip file with no IMG file in it, I am afraid that it would harm the phone if I would use it on the CWM recovery that is accessible through boot.
Is it possible to use CWM 4.0.0.5 to update itself?
I tried to use Rom Manager to update CWM (and to backup the rom, and you may very well check that because the names of the logs are different) RM didn't even recognize the already installed CWM, let alone update it or backup the stock rom...
So... can I really update CWM to try that route to backup stock rom?
How to use the zip file? (can I use it with CWM v4.0.0.5 or with ODIN 4.38?)...
I must say that I used ODIN 4.38 to flash the current CWM but the 4.0.0.5 CWM was a tar file.
Finally, all the info that I searched (here and elswhere) says that it is possible to come back to froyo (with the help of samfirmware site) but as I am such a noob I cannot find any ROM that is the same as the one I currently have.
I currently have Titanium Backup installed and it states that the ROM was build on the 2011/02/01 12h12 (can that be of any help to locate the default stock ROM from the ones that are available at SAMFIRMWARE?).
My carrier is TMN from Portugal, but until now, with this info I haven't been able to locate the 'one' ROM that would reassure me that I could upgrade and still have plenty of odds to come back to the startup 'scenario'.
Any help would be very much appreciated.
Thanks.
Click to expand...
Click to collapse
Welcome! to xda-forums. If I can guess it correct then I know you ( I don't want to name you here for your privacy concern).
So, after some research around, I found it very difficult to find a firmware for your TMN device. However, I suggest you try another sim card and see if your device is sim unlocked or not.
If you phone is sim locked either wait for TMN to upgrade your rom or just unlock it. Also, since you said you have CWM v4, is it in Froyo that you have to the rom? If yes then I suggest you have CWM v5 and try to do a nandroid backup [I believe v5 will work since v4 worked]. If you are already on GB rom then try flashing a custom rom.
More talk when I hear from you!
Will try your suggestions
yagya said:
Welcome! to xda-forums. If I can guess it correct then I know you ( I don't want to name you here for your privacy concern).
So, after some research around, I found it very difficult to find a firmware for your TMN device. However, I suggest you try another sim card and see if your device is sim unlocked or not.
If you phone is sim locked either wait for TMN to upgrade your rom or just unlock it. Also, since you said you have CWM v4, is it in Froyo that you have to the rom? If yes then I suggest you have CWM v5 and try to do a nandroid backup [I believe v5 will work since v4 worked]. If you are already on GB rom then try flashing a custom rom.
More talk when I hear from you!
Click to expand...
Click to collapse
Hello Yagya!
Yes you got it right! (It's who you think it is...)
Now, yes, it's on froyo that I have the CWM (4.0.0.5 that you have on your blog on the tools section, I found that out by comparing md5 hash from the one that I had downloaded from bunnybugs_007 tutorial).
But I am curious to what makes you think version 5 would work on my froyo? Isn't v5.0.2.6 designed for GB or later??? And also isn't v.5.0.2.6 a buggy version?
Summing up: You say I should try v5.0.2.6 out. Should I use my zip file (which I downloaded from clockworkmod site), and use the option '(..)update.zip' from the CWM recovery itself, or should I flash your recovery.tar.md5 that you linked on your blog, doing it with ODIN?
This question is puzzling me: can CWM be used to 'update' itself on its own recovery mode???? Am almost sure it is impossible... and scares me to try...
Besides, the CWM zip file that I've gotten from Koush site doesn't have an IMG file in it, but only folders and such...
Finally I am sure I have the android simlocked (because I've just checked it)...
Will try then to unlock if that is the scenario...
If the carrier would be more thoughtful I would be less troubled...
Thanks...
I am having a dilemma, and google is not forthcoming with relevent results, nor was searching the threads here.
So here is my issue, I have updated my sgh-i957r lte to the stock 4.0.4 ics, and cannot find a plausable way to root.
All of the guides on flashing I have found are either for honeycomb, or a leaked version that is not compatable.
The adb guides I have found are also for the previously leaked versons of ics or honeycomb.
So I suppose my question is, how would I go about rooting this update?
I am a fairly new android user, and this has me stumped.
Anybody? I would really appreciate some input on this, even if it's just saying if it is even possible or not.
Go to the i957 development thread, then look for the root method.
Ignore kernel stuff, download the Odin package and the clockwork recovery.
On a windows PC, unzip Odin, and put the clockwork recovery in the PDA slot and run it.
Then, on your tab, download the TWRP 2.1.1 package and install it from clockwork recovery.
That will get you a really good recovery, but not root.
AFAIK, there is no root package for ICS as a standalone zip or Odin tar. But you can then try out danno 2.0.6 and go from there.
Its a telus base, but that doesn't matter as long as you don't use the rogers apps. This will get you rooted.
You can also try nrvates cm10 or dannos AOKP, which are both excellent.
Sent from my SAMSUNG-SGH-I957 using XDA Premium HD app
Hi guys,
First of all, I apologize in advance if this isn't the correct place and/or thread title for my question. I've rarely posted in this forum as I'm usually able to find what I'm looking for.
I'll try to describe the issue fully so bear with me. If you're not patient, skip the next two paragraphs and go to the problem.
I bought my Galaxy S more than two years ago; back then it had Android 2.1 and I believe I also flashed to 2.1.1 via Samsung Kies.
I later flashed Froyo via Odin, rooted with 1ClickLagFix and installed a ton of apps. I haven't updated anything for more than a year, perhaps year and a half. I recently uninstalled many applications I wasn't using, including the lag fix, unrooted and began preparing to flash something newer. I didn't have the time though, so I dropped the project, and besides, the phone is working much smoother without all the unnecessary crap I had before.
Yesterday I decided to finish the job and flash DarkyROM 11 Black Edition. I rooted the phone again using Z4root, installed CWM ROM Manager and flashed CW recovery. I need the recovery in order to flash CM9 and then the ROM per the installation instructions for DarkyROM.
At this point I might as well wait for v.12, but I'll still need the CW recovery I guess. Or I may flash v.11 as planned; I still haven't decided.
The problem: CW recovery is flashed, but when I reboot I go to 3e recovery instead (tried with the 3 buttons or boot to recovery from ROM Manager, same result). I then copied the CW recovery file directly on the SD card and renamed it update.zip (it was recovery-update.zip) and tried to apply it. Didn't work. As far as I remember it said it couldn't verify file integrity or something. I can check for sure if you'd like.
Here's what I'm running (I'll put what I see, let me know if you need more):
GT-I9000
Firmware: 2.2
Baseband version: I9000XXJPP
Kernel version: 2.6.32.9
[email protected] #1
Build number: FROYO.XFJP7
ROM Manager (installed v. 5.5.1.4 yesterday) says current recovery is ClockworkMod 2.5.1.2.
I'd appreciate any insight. I don't have much experience flashing my phone, so if you have a solution, it would be best to include not only links to relevant threads but also an explanation as to what steps I should follow in my specific case.
Thanks in advance!
Filkolev said:
Hi guys,
First of all, I apologize in advance if this isn't the correct place and/or thread title for my question. I've rarely posted in this forum as I'm usually able to find what I'm looking for.
I'll try to describe the issue fully so bear with me. If you're not patient, skip the next two paragraphs and go to the problem.
I bought my Galaxy S more than two years ago; back then it had Android 2.1 and I believe I also flashed to 2.1.1 via Samsung Kies.
I later flashed Froyo via Odin, rooted with 1ClickLagFix and installed a ton of apps. I haven't updated anything for more than a year, perhaps year and a half. I recently uninstalled many applications I wasn't using, including the lag fix, unrooted and began preparing to flash something newer. I didn't have the time though, so I dropped the project, and besides, the phone is working much smoother without all the unnecessary crap I had before.
Yesterday I decided to finish the job and flash DarkyROM 11 Black Edition. I rooted the phone again using Z4root, installed CWM ROM Manager and flashed CW recovery. I need the recovery in order to flash CM9 and then the ROM per the installation instructions for DarkyROM.
At this point I might as well wait for v.12, but I'll still need the CW recovery I guess. Or I may flash v.11 as planned; I still haven't decided.
The problem: CW recovery is flashed, but when I reboot I go to 3e recovery instead (tried with the 3 buttons or boot to recovery from ROM Manager, same result). I then copied the CW recovery file directly on the SD card and renamed it update.zip (it was recovery-update.zip) and tried to apply it. Didn't work. As far as I remember it said it couldn't verify file integrity or something. I can check for sure if you'd like.
Here's what I'm running (I'll put what I see, let me know if you need more):
GT-I9000
Firmware: 2.2
Baseband version: I9000XXJPP
Kernel version: 2.6.32.9
[email protected] #1
Build number: FROYO.XFJP7
ROM Manager (installed v. 5.5.1.4 yesterday) says current recovery is ClockworkMod 2.5.1.2.
I'd appreciate any insight. I don't have much experience flashing my phone, so if you have a solution, it would be best to include not only links to relevant threads but also an explanation as to what steps I should follow in my specific case.
Thanks in advance!
Click to expand...
Click to collapse
clockworkmod 2.... really ? because cwm 5 or 6 is the actual version .. maybe rom manager cannot flash the recovery in froyo, try to connect phone .with kies and update to gingerbread
Sent from my GT-I9001 using xda premium
Jonboy2011 said:
clockworkmod 2.... really ? because cwm 5 or 6 is the actual version .. maybe rom manager cannot flash the recovery in froyo, try to connect phone .with kies and update to gingerbread
Sent from my GT-I9001 using xda premium
Click to expand...
Click to collapse
Can't do... Kies cannot upgrade the firmware since I'm on a custom ROM (or because it didn't match my country, I don't quite remember the reason).
I was following the installation instructions for DarkyROM for Froyo; it says I should have it rooted with CWM and use the recovery to flash CM9 and the ROM itself afterwards, so I believe Froyo isn't the issue. The kernel perhaps? Have no idea, I'm a novice more or less. I do know how to follow instructions though, so I'm not a complete idiot
Besides geting a newer ROM with newer Adnroid version I'd also like to clean up the mess I've been creating for the past year and a half. Maybe flashing a stock ROM and then DarkyROM would be easier. I'm looking for the most time-efficient method.
I have been reading this website and several others over the last few days and last night decided to give rooting a go. Trouble is - I am not sure where to begin.
Last night I tried downloading Philz kernel - PhilZ-cwm6-DXLR5-OLB-v2.7 since my kernel version is 3.0.15-n7000dxlr5-cl968032.
I then followed these instructions:
Download xxx-signed.zip kernel matching your ROM
Put the previously downloaded xxx-signed.zip file on your external sd card
Boot into stock recovery (volume up+home+power)
Select "apply update from external storage".
Now select the xxx-signed.zip file you copied in previous step
You are rooted + new PhilZ-cwm6 kernel with CWM6
What I got was a message like - signature authorization failed.
Not sure what to do next and would appreciate some guidance.
I am doing this basically because Ive decided to keep this phone a little longer, learn about rooting and try my hand at experimenting some of the custom roms.
Again appreciate any assistance / guidance anyone might be willing to provide
thank you
Is this the one you tried?
http://d-h.st/o9X
yes... i think that is it
download using phone browser. the move it to ext sd and try again..
case sensitive link.... my bad
Obviously Not. The link i posted links to the kernel. It should be downloading the kernel.
same result..... signature verification failed
The otherday I use PhilZ 3.99 for LR5 from his thread in ori dev. It works fine.
http://www.mediafire.com/?3ale6m9q6b6a3
Sent from my phone.
Like I said... im new to this, but the instructions seem simple enough (as above). Wish I could get it to work for me....
I saw you are using ver 2.7. On the PhilZ he has 3.99 for lr5. It worked for me.
Sent from my phone.
i am downloading the 3.99 version now - see how it goes
tried 3.99 and get the same result -- signature verification failed
Strange. Maybe check if there a box in the stock recovery that can be ticked or unticked? Otherwise, check other root method from dr.ketan sticky at android dev thread. Many easy method, even an apk that root.
Sent from my phone.
dont know if this is relevant to the issue, but here it goes
About a month ago, I let the phone update some software - didnt really pay attention what it was updating as i was working.
Later that day i noticed my company email was not coming through. I raised a ticket with IT and received a response after looking into my case stating that the company does not allow rooted devices to access the email system. I found this strange because I had never tried to root the device. Is it possible that somehow an update occurred that rooted my phone?
Im aware that there are several ways to root, but again, im new to this would appreciate further guidance that might help me get this phone rooted.
thanks again
I would try method 0 and 1B from dr.ketan thread below.
http://forum.xda-developers.com/showthread.php?p=18978158
Let us know how it goes.
Sent from my phone.
willing to try these methods - if i start with method 0, how do i go about flashing with a safe kernel?
i have read quite a bit about kernel issues for 4.0.4 so just dont want to create a serious issue
newman330 said:
if i start with method 0, how do i go about flashing with a safe kernel?
Click to expand...
Click to collapse
once rooted, use mobile odin to flash tar.md5 version of philz kernel, not zip
ok.... im rooted - thanks to both of you for the assistance.
now.... im rooted at 4.0.4. If i want to install a custom rom say for 4.2 or 4.3, I guess I need to root to the appropriate operating system. how does this process work? do i need to first flash to a safe kernel?
bear with me.... this is very complicated for my non-IT brain : )
The most reliable roms now are still stockbased custom roms 4.12. Other newer roms are still experimental. I like Sweet rom 10.5. You need to read instructions for rom flashing from the rom thread.
Sent from my phone.
i have downloaded the following files to computer and getting ready to place them on my phone:
PhilZ-cwm6-DXLR5-OLB-3.99.tar.md5
MobileODIN_FlashKernel_N7000-v3.0
MobileODINLite-v3.85.apk
Is there any special instructions i need to be aware of for mobile odin? I assume i just run the apk program and follow instructions from there to get my safe kernel flashed?