Related
I'm desperate I just followed the steps given for installing CM7:
# Make sure your phone is fully charged! Update process will take some time.
# Make sure there's enough free space at your internal sdcard (200MB)
# Make sure you've not disabled HSPA by using the dialer code *#301279#
# Download following files from sourceforge: Captivate | Galaxy S | Galaxy S B | Vibrant
- DEVICE-efsbackup.zip
- cm7-DEVICE-initial-kernel.tar
- cm7-DEVICE-initial-XXXXXXXX.zip
# Copy following files to your internal sdcard
- DEVICE-efsbackup.zip
- cm7-DEVICE-initial-XXXXXXXX.zip
# Flash a kernel which comes with clockworkmod-recovery using odin: Captivate | Galaxy S | Vibrant
# Reboot into recovery using 3-button-combo and apply DEVICE-efsbackup.zip.
- Don't use "reboot recovery" command or other shiny things to do this!
# Flash cm7-DEVICE-initial-kernel.tar as pda using odin without auto-reboot and without re-partition
after this when i try to install zip from sd card i get the following error:
assert failed: getprop("ro.product.device") == "galaxys" || get prop("ro.build.product") == "galaxys" || getprop("ro.product.board") ++ "galaxys"
E:Error in /sdcard/update-cm-7-03122011-NIGHTLY-GalaxyS-signed.zip
(Status 7)
Installation aborted
I'm still sitting in CWM scared to do anything! Tried to restore backup but that failed too
What do i do??
Any help would be extremely appreciated!!
Martin
Looks like you didn't install the initial CM7 Zip, if it's not on your sd card already you should be able to push it with adb then install., after that try and install the nightly.
Which one is the initial cm7?
Should be called "cm7-galaxys-initial-20110304.zip" if you didn't download it, http://sourceforge.net/projects/teamhacksung/files/galaxys/
Also you may have to go through the whole procedure again. Give it a try though.
Mabee said:
Which one is the initial cm7?
Click to expand...
Click to collapse
http://sourceforge.net/projects/teamhacksung/files/galaxys/cm7-galaxys-initial-kernel.tar/download
Thats the initial kernel to get CWM it has to be flashed thru Odin. then when that is done you flash the rest thru CWM (recovery)
He flashed the kernel, missed out the initial cwm zip though.
so should i install nexus drivers (since my phone doesn't have drivers right now) and just start from the beginning or push the initial cm7 file to the phone ( I have never pushed a file before so unsure how it's done)
Really appreciate you guys helping me
Btw i dowloaded the initial zip just need to get it to my phone now
You'll need to get the android sdk, or just adb.
Assuming you're using windows:
Connect your phone, open a command prompt on your pc and navigate to where you saved adb. Then type "adb devices" If it finds something then you can use "adb push cm7-galaxys-initial-20110304.zip /sdcard"
cm7-galaxys-initial-20110304.zip will need to be in the same folder on your PC as adb for this to work.
what do i do with my phone to push the file i have installed sdk and adb but my phone is sitting in cwm still
Yeah, adb should work in cwm. If it doesn't then you'll have to restore to stock and begin process from beginning.
I managed to push file and installed cm7 initial zip sucessfully. did a factory reset / data wipe and rebooted
so it's been stuck on the stock galaxy s loading screen for some time now not really sure if i should do something else
Double post
The text or the animation?
Just the text
can i just start from the beginning and flash CF root?
I'd go back to stock firmware first. Use JPC with 3 files 512.pit and repartition checked.
I'm sorry for being retarded but i don't know how to do that. i am immensely thankful for all your help so far!
Ok, first you need to get XXJPC firmware here. It should extract to 3 files, pda, modem and csc. Load them into odin (one for each box on the right) and select a 512.pit file for pit (might have come with odin otherwise download it), tick repartition. Put your phone in download mode then connect it to your pc. Press start. Wait for odin to say success, then your phone should reboot (it can take a while).
I'm running a european galaxy does that matter or can you flash any stock firmware i remember i wasn't a JPC before i was stock XW somehting
Yeah, it won't matter, I just know JPC contains dbdata which is needed to make sure it restores properly.
btw as i'm waiting for the dl to finish i see it's an exe file is that right? shouldn't it be a rar file?
Well, I was trying to move from Darky 10.1-3 to CM7.1 oona GT-i9000 and whatever method I have tried I couldn't do so.
1. When I tried flashing CM7.1 directly from Dark Core Recovery (threads show it's supposed to work) I have first encountered some sort of a boot-loop. I see console flashes quick and then it reboots. I have entered CWM recovery mode and reflashed and now the phone starts, with the USIM card inside I have no reception and com.android.phone continuously crashes. Was unable to do much with that.
2. As method 1 failed I have downloaded EZBase's Froyo bootloader and flashed it. There from CWM Recover I have tried flashing but it failed and I'm getting the following:
assert failed: getprop("ro.product.device") == "galaxys" || getprp("ro.beuild.product") == "galaxys"
and it keeps repeating itself, just instead of "galaxys" it says "GT-I9000" and other possible names for an i9000.
Any advice anyone ?
Did you Wipe? (wipe data/factory reset + wipe cache partition)
Also you might have ext4 lagfix enabled. Go to CWM and disable it.
Then try again.
I normally flash the CM7 initial kernel using odin and then only use CWM to flash CM7 nightly or stable.
Doesn't meter what rom I Flash I get this error: http://imageshack.us/photo/my-images/823/img201207201510251.jpg/
I have copyed all files: parted, e2fsck etc and did what says on this post: http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/page__st__20 (number 23)
When im trying to parted, its just says: "no such file or directory" http://imageshack.us/photo/my-images/844/shell2.jpg/
If i try to format - i receiving such errors: http://imageshack.us/photo/my-images/801/img201207201436181.jpg/
http://imageshack.us/photo/my-images/841/img201207201437371.jpg/
please advice how to use parted?
Edit:
I have managed to open parted, but now i cant remove any partitions, after rm command its remains same.
http://img685.imageshack.us/img685/5201/printuo.jpg
How can i remove partitions?
Bezeq said:
Doesn't meter what rom I Flash I get this error: http://imageshack.us/photo/my-images/823/img201207201510251.jpg/
I have copyed all files: parted, e2fsck etc and did what says on this post: http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/page__st__20 (number 23)
When im trying to parted, its just says: "no such file or directory" http://imageshack.us/photo/my-images/844/shell2.jpg/
If i try to format - i receiving such errors: http://imageshack.us/photo/my-images/801/img201207201436181.jpg/
http://imageshack.us/photo/my-images/841/img201207201437371.jpg/
please advice how to use parted?
Edit:
I have managed to open parted, but now i cant remove any partitions, after rm command its remains same.
http://img685.imageshack.us/img685/5201/printuo.jpg
How can i remove partitions?
Click to expand...
Click to collapse
You do not need to remove any partitions... Just flash stock rom, and try again... Same happened to me, i couldnt mount any partition in recovery, now it fine
foggydisaster said:
You do not need to remove any partitions... Just flash stock rom, and try again... Same happened to me, i couldnt mount any partition in recovery, now it fine
Click to expand...
Click to collapse
I have tryed to flash many roms, 2.2.1 2.3.1 2.3.5 .2.3.6, (JVT, JVR, LPY, and new ones) always same issue: "E: failed to mount /data (invalid argument) and then bootlooping.
I`m sure my mmcblk0p2 is broken, question is how to force delete this partition or flash rom in to external SDcard!
Bezeq said:
I have tryed to flash many roms, 2.2.1 2.3.1 2.3.5 .2.3.6, (JVT, JVR, LPY, and new ones) always same issue: "E: failed to mount /data (invalid argument) and then bootlooping.
I`m sure my mmcblk0p2 is broken, question is how to force delete this partition or flash rom in to external SDcard!
Click to expand...
Click to collapse
Well you cant flash roms onto sdcard... But if your partition is broken, then sorry but im a noob
Sent from my GT-I9000 using xda app-developers app
Have you tired using a pit file?
flash a stock rom from samfirmware.com with ODIN.(eg. jw5)
to extract the password is "samfirmware.com"
tick repartition and use 512 pit file(included in rom from samfirmware).
check youtube for "flash with odin" if u dont know how.
edit:u are trying to flash from from samsungs 3 recovery.u need cwm(clockworkmod) to flash.
go to CF-ROOT(for i-9000) thread and follow instructions and read all in the OP(1-2-3 posts)
again u need ODIN to flash it.
hey
there is the best wasy to do that...just go to sammobile.com
there sign up first and then download the firmware (in firmware tab) and flash-programs...
the make sure to use oidn3_v1.0 only...
you can also download the flash-guide if you need it...
its simple..:laugh:
Thanks to everyone for replays, but nothing helped me x_x
if i flash 2.2.1 or 2.3.6 i receiving this error:
https://www.box.com/s/4d4b108a0246f9f56c7c
If i flash 2.3.3 or 2.3.4:
https://www.box.com/s/f09fd945620c03daffa9
And then it keep showing me GT 9000 logo......
yes i used 512pit and using 1.82 odin
I know there is way to install in to external SDcard: http://www.youtube.com/watch?v=zdMhYYdMB08
I had such error and successfully installed rom in to sdcard but i had issue with phone signal, so tried to re install rom and now its keep teling me cant mount data..
What can i do?
Hello,
Did you try this http://forum.xda-developers.com/showthread.php?t=984140 ?
mystic324 said:
Hello,
Did you try this http://forum.xda-developers.com/showthread.php?t=984140 ?
Click to expand...
Click to collapse
Yep, keep shows only gt-9000 logo..
I had a very similar problem earlier this year.
From what I could see the partitions on the phone's internal storage weren't able to be accessed. In adb I tried using parted and rm but the partitions there (/dev/block/mmc/blk0) didn't ever change. I also tried various .pit files and Android versions through Odin but nothing worked.
I took my phone in for repairs after flashing a really old version; as close as possible to what it came with, and they fixed it. The repair was due to 'mechanical fatigue' according to them. I assumed the internal storage was some how broken or corrupted and couldn't be written to.
Not sure, if you manage to solve this.
From you screenshots I can see you are using 3e recovery. I would suggest you to flash a kernel which support cwm recovery mode.
I have heard peoples getting this error while using it on 3e.
Captain_17
Yes Captain_17, i have exactly same problem, cant give it to repair since purchased it from abroad.
erpurohit said:
Not sure, if you manage to solve this.
From you screenshots I can see you are using 3e recovery. I would suggest you to flash a kernel which support cwm recovery mode.
I have heard peoples getting this error while using it on 3e.
Click to expand...
Click to collapse
3e recovery because i`ve flashed 2.2 and 2.2.1 or any other official roms, i can flash CWM easy but as Captain_17 said i can see but cant touch
files or partitions.
If flash CWM then phone will boot to CWM only, and i cant flash any rom from CWM because i cant copy files to internal storage and external (sdcard) cwm doesn't see it.
Sorry man, wish I could be of more help. I tried every available option I could find online but nothing worked.
Seems to be a hardware problem and replacing the damaged part is the only solution.
Silly question, but you ticked re-partition? try flash 2.2.1 or 2.3.3 with 512 pit and repartition
Also, you could try to flash Darky ressurection via odin, not completely stock rom. I know that this is just tweaked stock, but you could try do that.
And, you could try to use Heimdall instead of odin - http://forum.xda-developers.com/showthread.php?t=1196179
I have read somewhere that heimdall is more preferable than odin in some cases.
Bezeq said:
Yep, keep shows only gt-9000 logo..
Click to expand...
Click to collapse
I once also a similar problem and flash2.1 Eclayr. But then I had to restore recowery to flash. as with you, I do not know if it helps.
Hi guys,
I think I (soft-)bricked my Galaxy Tab (P1000). I hope you can help me
About a month ago, my tablet had installed the Overcome Rom 4.1, based on Android 2.3.
I then decided to try CM9, so I installed one of the first CM9 official nightly builds. I think I installed it simply through the CMW Recovery.
Yesterday I found that the 9.0.0 stable build was out, so I downloaded it from get.cm.
I used Titanium Backup to backup important app data into the "internal sdcard".
Then I used ROM Manager to "install rom from sdcard", choosing to erase cache only (not data), and to create a nandroid backup of my current rom.
ROM Manager rebooted into CWM recovery and started to nandroid backup and to install the new rom.
But, sadly, at next reboot, the tablet was stuck at the samsung boot screen.
It was also impossible to enter recovery mode with the volume up key. The only working mode was the download mode (activated with volume down key)
Today I tried to flash the CWM boot image (downloaded from the Samsung Galaxy Tab (GSM): Full Update Guide" on CM website) using Odin.
Now I can access to CWM Recovery, but it shows a lot of errors.
E.g.:
entering CMW Recovery
Code:
CWM-based Recovery v.5.0.2.8
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
backup and restore > restore from internal sdcard > 2012-08-10-18-55-42
Code:
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoring system...
E:format_volume: no MTD partition "/dev/block/st19"
Error while formatting /system!
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
mounts and storage > mount /sdcard
Code:
Error mounting /sdcard!
mounts and storage > mount USB storage
Code:
E:Unable to write to ums lunfile (No such file or directory)
Now here's my questions:
1. What happened? Did I do something wrong in updating CM9 to the stable version?
2. Will I be able to restore my data and/or my nandroid backup?
I can't mount my sdcard from CMW, but when I choose "restore from internal sdcard" it correctly tells my backup date, so I think the internal sdcard content is still there somewhere...
I'd really appreciate to restore all my apps and data!
3. How can I fix this mess? I'd like to have the CM9 installed and working.
Thank you very much!! :angel:
Ok, I've just realized that the internal sdcard is /emmc and not /sdcard.
So the "mount /sdcard" error is normal.
I can correctly mount /emmc from CWM, but if I try to install a rom from a zip file (either the CM9 old nightly or the stable build, which are both saved on the internal emmc), it says:
Code:
-- Installing: /emmc/cm-9.0.0-p1.zip
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "galaxytab" || getprop("ro.build.product") == "galaxytab" ||
getprop("ro.product.device") == "GT-P1000" || getprop("ro.build.product") == "GT-P1000"
E:Error in /emmc/cm-9.0.0-p1.zip
(Status 7)
Installation aborted.
Code:
-- Installing: /emmc/cm-9-20120713-NIGHTLY-p1.zip
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "galaxytab" || getprop("ro.build.product") == "galaxytab" ||
getprop("ro.product.device") == "GT-P1000" || getprop("ro.build.product") == "GT-P1000"
E:Error in /emmc/cm-9-20120713-NIGHTLY-p1.zip
(Status 7)
Installation aborted.
Just restock and start over again:
From the thread: http://forum.xda-developers.com/showthread.php?t=1385153
How to Flash the above zips :
You need to restock your tab if you are running an old MTD build, (only if /system isn't 406 mb, check it by the command `df system` or use an app (such as root explorer) )
IF you are coming from a FSR (STL/BML) ROM (aka Samsung ROM - anything else than the latest CM9 builds / AOKP builds, i.e. any GB ROM, no need to restock)
IF you are coming from a froyo ROM, you need to flash a stock GB ROM first, follow the guide below :
Restocking :
Follow the team overcome restock guide [http://www.teamovercome.net/p1000/?page_id=17], and completely restock your tab.
Once you've flashed it, reboot into download mode again and flash any kernel with recovery (any non-MTD kernels from humberos.com.br, or this forum, for your tab model)
After you've flashed the kernel, reboot into recovery, and this time, install the zip you just downloaded from CyanogenMod servers.
Install Google Apps if you want (gapps-ics-* from goo.im) [optional]
Reboot and enjoy your tab
Normal install :
You need to have a kernel with CWM Recovery
Get the zip from the above download links
Put the zip on your sdcard, reboot into recovery, and install the zip
It'll reboot a few times during the install, that's normal
Will I lose all data on the /emmc partition (including all my TitaniumBackup files) if I restock?
If the answer is yes, is there a way to copy some files from the emmc to an external sdcard before restocking? (e.g. using CWM, or Odin/Heimdall)
Thanks.
Sent from my HTC Vision using xda app-developers app
sigitm said:
Will I lose all data on the /emmc partition (including all my TitaniumBackup files) if I restock?
Click to expand...
Click to collapse
Only if you install overcome rom (via CWM).
Sent from my GT-P1000 using Tapatalk 2
Restock to 2.3.3. Then flash overcome before flashing cm9.
sigitm said:
Ok, I've just realized that the internal sdcard is /emmc and not /sdcard.
So the "mount /sdcard" error is normal.
I can correctly mount /emmc from CWM, but if I try to install a rom from a zip file (either the CM9 old nightly or the stable build, which are both saved on the internal emmc), it says:
Code:
-- Installing: /emmc/cm-9.0.0-p1.zip
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "galaxytab" || getprop("ro.build.product") == "galaxytab" ||
getprop("ro.product.device") == "GT-P1000" || getprop("ro.build.product") == "GT-P1000"
E:Error in /emmc/cm-9.0.0-p1.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
I have exactly the same scenario as you described, so I'm interested, could you find a solution?
I can restock with Odin using theTeam Overcome Guide, the tab boots ok. So I try to install CM9 again, I can flash the zImage with Heimdall no problem, but when I choose install the CM9 zip from the internal sdcard, I always get the same getprop assert above. I made this loop a few times now (trying to install CM9, restock), but it's always the same.
Weird that never happen to me.
Just to be crazy, can you try flash AOKP build 40 instead?
If it works, then flash cm9.
Someone got that working before.
Sent from my GT-P1000 using xda app-developers app
priyana said:
Weird that never happen to me.
Just to be crazy, can you try flash AOKP build 40 instead?
If it works, then flash cm9.
Someone got that working before.
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
restock -> overcome 4.1 -> CM9
This worked for me, thanks!
You mean restock - overcome kernel - overcome 4.1 - cm9 ?
Sent from my GT-P1000 using xda app-developers app
Qqqxxxzzz said:
sigitm said:
Will I lose all data on the /emmc partition (including all my TitaniumBackup files) if I restock?
Click to expand...
Click to collapse
Only if you install overcome rom (via CWM).
Click to expand...
Click to collapse
I restocked but sadly I lost all data on the internal sdcard. :crying:
Then I copied latest CM9 nightly rom to the internal sdcard, installed the Overcome Kernel via Odin, booted into Overcome Clockwork Mod, and successfully installed CM9.
priyana said:
You mean restock - overcome kernel - overcome 4.1 - cm9 ?
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
1. restock as described the overcome guide
2. oneclick rooting
3. overcome 4.1 with odin
4. cm9 with cwm
setalosas said:
1. restock as described the overcome guide
2. oneclick rooting
3. overcome 4.1 with odin
4. cm9 with cwm
Click to expand...
Click to collapse
Sent from my GT-P1000 using xda app-developers app
Sorry, by now I know overcome guide by heart and probably can write it out with my eyes closed.
but...
3. overcome 4.1 with odin
What is that?
I thought you flash overcome 4.0 kernel tar using Odin,
Not overcome 4.1 rom
Overcome rom is flashed using CWM only.
So, You mean restock - overcome kernel - overcome 4.1 - cm9
Rooting is redundant.
priyana said:
3. overcome 4.1 with odin
What is that?
I thought you flash overcome 4.0 kernel tar using Odin,
Not overcome 4.1 rom
Overcome rom is flashed using CWM only.
So, You mean restock - overcome kernel - overcome 4.1 - cm9
Rooting is redundant.
Click to expand...
Click to collapse
No, I didn't flash the overcome 4.0 kernel.
I used odin with the Overcome_7_Series_v4.1.0_Wipe.zip file unzipped, and put the proper files into the pit/pda/phone fields of odin. That's all.
bummer
flashed GT-P1000 with CM9.1 stable version too. Suddenly the device keeps auto shutdown with unknown problems, app crashes such as Google Play (which I itched to remove and updated to the somenumber version) and changed Apollo app back and forth and back again of 1.0 version from the separate developed apk with the original cm9 Apollo. and then after many times flashing and tried to restore the CM9.1 Stable, the device wont let me use CM9 again. On boot scanning sd card, it shuts down weirdly. maybe there's some problem for my device with CM9. sigh.
I have a Samsung Galaxy Pop with “com.android.phone” error each time the device restarts. The network goes down and comes back again. This happens twice.
I had upgraded my handset from 2.2.1 to 2.2.2 using Kies in Sept 2012. I somehow got a chance to copy the I559DDEH31_HOME.tar.md5 file which Kies creates for upgrade. The contents of the file are amss, boot.img, cache.rfs, recovery.img & system.rfs.
I have tried Odin to flash but have been unsuccessful.
I would like to know if I can use “dd if=/dev/block/stl12 of=/sdcard/system.rfs bs=4096” command using adb shell to restore the handset to its original state?
I am not that good at Android so would like to know if somebody can help me.
deep143in said:
I have a Samsung Galaxy Pop with “com.android.phone” error each time the device restarts. The network goes down and comes back again. This happens twice.
I had upgraded my handset from 2.2.1 to 2.2.2 using Kies in Sept 2012. I somehow got a chance to copy the I559DDEH31_HOME.tar.md5 file which Kies creates for upgrade. The contents of the file are amss, boot.img, cache.rfs, recovery.img & system.rfs.
I have tried Odin to flash but have been unsuccessful.
I would like to know if I can use “dd if=/dev/block/stl12 of=/sdcard/system.rfs bs=4096” command using adb shell to restore the handset to its original state?
I am not that good at Android so would like to know if somebody can help me.
Click to expand...
Click to collapse
No replies??
deep143in said:
No replies??
Click to expand...
Click to collapse
Why don't u flash a new gingerbread 2.3.6 stock rom? Froyo is kind of outdated. Make sure to backup your contacts and everything if u decide to do so.
kirakun said:
Why don't u flash a new gingerbread 2.3.6 stock rom? Froyo is kind of outdated. Make sure to backup your contacts and everything if u decide to do so.
Click to expand...
Click to collapse
Hi Kirakun,
I would love to do that but unfortunately I am not able to find dedicated Gingerbread 2.3.6 stock rom for Samsung Galaxy Pop CDMA (India) SCH-I559.
I have searched a lot but found only for Samsung Galaxy mini or S5570 which are the GSM versions of the same model.
I have also found that some have already bricked their phones using the other versions.
So I have decided to stick to froyo.
I just wanted to make sure that if I restore the /system partition using system.rfs command (dd if=/dev/block/stl12 of=/sdcard/system.rfs bs=4096) shouldn't create any new problems.
deep143in said:
Hi Kirakun,
I would love to do that but unfortunately I am not able to find dedicated Gingerbread 2.3.6 stock rom for Samsung Galaxy Pop CDMA (India) SCH-I559.
I have searched a lot but found only for Samsung Galaxy mini or S5570 which are the GSM versions of the same model.
I have also found that some have already bricked their phones using the other versions.
So I have decided to stick to froyo.
I just wanted to make sure that if I restore the /system partition using system.rfs command (dd if=/dev/block/stl12 of=/sdcard/system.rfs bs=4096) shouldn't create any new problems.
Click to expand...
Click to collapse
that will ruin your phone
and for the message just need to wipe data from recovery
deep143in said:
Hi Kirakun,
I would love to do that but unfortunately I am not able to find dedicated Gingerbread 2.3.6 stock rom for Samsung Galaxy Pop CDMA (India) SCH-I559.
I have searched a lot but found only for Samsung Galaxy mini or S5570 which are the GSM versions of the same model.
I have also found that some have already bricked their phones using the other versions.
So I have decided to stick to froyo.
I just wanted to make sure that if I restore the /system partition using system.rfs command (dd if=/dev/block/stl12 of=/sdcard/system.rfs bs=4096) shouldn't create any new problems.
Click to expand...
Click to collapse
My bad i was not aware of this different version. Yes do try what dheeraj has said.
I think that entering recovery should be same for u, just switch off phone, press home button and power button simultaneously and hopefully you will enter recovery.
Navigate using volume button and do a wipe data and cache. Doing so you will lose any app and everything from your phone, so do a backup before.
dheeraj (dhlalit11) said:
that will ruin your phone
and for the message just need to wipe data from recovery
Click to expand...
Click to collapse
I have already tried to wipe from recovery twice but still face the same error. Everything resets to factory defaults except this error which pops up at every restart..
reflash firmware through odin
and I will recommend you to take it to Samsung care
---------- Post added at 04:50 PM ---------- Previous post was at 04:50 PM ----------
reflash firmware through kies
and I will recommend you to take it to Samsung care
dheeraj (dhlalit11) said:
reflash firmware through odin
and I will recommend you to take it to Samsung care
---------- Post added at 04:50 PM ---------- Previous post was at 04:50 PM ----------
reflash firmware through kies
and I will recommend you to take it to Samsung care
Click to expand...
Click to collapse
I have done the wipe data and cache. Below is the response:
-- Wiping cache...
Formatting CACHE:...
umount(/cache) attempt 1
(Unknown error: 0) rc=0
Cache wipe complete.
-- Wiping data...
Formatting DATA:...
Formatting CACHE:...
umount(/cache) attempt 1
(Unknown error: 0) rc=0
Cache wipe complete.
But unfortunately same error.
I cannot flash firmware as I do not have one supported for this model of samsung (CDMA version). KIES says that the firmware is up to date so cannot flash from there as well.
deep143in said:
I have done the wipe data and cache. Below is the response:
-- Wiping cache...
Formatting CACHE:...
umount(/cache) attempt 1
(Unknown error: 0) rc=0
Cache wipe complete.
-- Wiping data...
Formatting DATA:...
Formatting CACHE:...
umount(/cache) attempt 1
(Unknown error: 0) rc=0
Cache wipe complete.
But unfortunately same error.
I cannot flash firmware as I do not have one supported for this model of samsung (CDMA version). KIES says that the firmware is up to date so cannot flash from there as well.
Click to expand...
Click to collapse
In case if you don't mind I would like to know how my phone will get ruined if I use the system.rfs from the original firmware file downloaded by Kies?
Secondly, is there a particular version of ODIN I need to use for this handset? I have tried 1.85, 3.07 and 4.38 versions.
Actually I do not have any other files than the I559DDEH31_HOME.tar.md5 required by ODIN.
I would prefer to go to Samsung service centre only when I am left with no option or if the handset fails to do its regular tasks.
Anyways, thanks for your suggestion.
you will do it while your phone is running and while doing it your mobile will reboot in the process due to change in some critical files
and we also don't know what is the structure of system.rfs
dheeraj (dhlalit11) said:
you will do it while your phone is running and while doing it your mobile will reboot in the process due to change in some critical files
and we also don't know what is the structure of system.rfs
Click to expand...
Click to collapse
Dheeraj, I understand what you are trying to say. I was plannning to do so in recovery mode. I have checked through ADB that I can access the device when in recovery mode. Will it still be a problem?
deep143in said:
Dheeraj, I understand what you are trying to say. I was plannning to do so in recovery mode. I have checked through ADB that I can access the device when in recovery mode. Will it still be a problem?
Click to expand...
Click to collapse
Alternatively I can also do when the phone is in download mode..
What do u think?
well you can't in download mode
but of you have cwm then it would be easy
open system.rfs with soft which can mount iso etc.
Copy the content of system to you sdcard
now flash aroma file manager and with the help of that copy all the files your your system.rfs to your system partition
and with dd it may copy files to /system/system or directly to /root
dheeraj (dhlalit11) said:
well you can't in download mode
but of you have cwm then it would be easy
open system.rfs with soft which can mount iso etc.
Copy the content of system to you sdcard
now flash aroma file manager and with the help of that copy all the files your your system.rfs to your system partition
and with dd it may copy files to /system/system or directly to /root
Click to expand...
Click to collapse
I used a linux machine to mount the system.rfs. Extracted phone.apk and installed the app using root explorer.
Finally the problem com.android.phone has been resolved..
Thanks for your help.
deep143in said:
Hi Kirakun,
I would love to do that but unfortunately I am not able to find dedicated Gingerbread 2.3.6 stock rom for Samsung Galaxy Pop CDMA (India) SCH-I559.
I have searched a lot but found only for Samsung Galaxy mini or S5570 which are the GSM versions of the same model.
I have also found that some have already bricked their phones using the other versions.
So I have decided to stick to froyo.
I just wanted to make sure that if I restore the /system partition using system.rfs command (dd if=/dev/block/stl12 of=/sdcard/system.rfs bs=4096) shouldn't create any new problems.
Click to expand...
Click to collapse
the upgrade is available in India but only at the official samsung repair center.
u will have to visit 'em get it upgraded