[Q] I897 Boots only to CWM recovery. Help Please. - Captivate Q&A, Help & Troubleshooting

Hey Guys,
Running CyanogenMod 10.1.2. on Samsung (AT&T)i897. Was using phone, it rebooted as if it crashed. It boots only to the clockwork recovery screen (v6.0.3.6)
Tried reboot- just reboots to cwm recovery
Tried putting the latest cwm 10.3 on external zip and install: IT fails with error "no file_contexts"
Installed adb, (I using linux if that matters) and can connect to phone, and see the file structure (I am a complete noob, but figured out this much)
ANy suggestions on what to try?
thanks in advance.
Edit: Found a log file:
Warning: No File_contexrs
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
init.svc ueventd=runnning
int.svc.recovery=running
sys.usb.config=mass_storage.adb
init.svc adbd=running
sys.usb.state=mass_storage.adb
I: checking foir extendedcommand...
I:Skipping execution of extendedcommand, file not found
W: Failed to mount /dav/lvpool/userdata (no such file or directory)
I: can';t format unknown volume: /emmc

U probably r gonna have to mount storage through the cwm recovery, save ur stuff to ur pc, and then wipe data/factory reset and see if it will reboot.
But...u could try to wipe cache, dalvik cache after u mount and save ur stuff. Not sure if it will work, but worth a try before u wipe data/factory reset.

tried mounting and
Im going to guess I have a hardware failure as Mounting external_Sd gives error "unable to mount external_sd"
with that in mind I continued:
tried wipe cache/dalvik & reboot- no change.
Tried wipe data/Factory reset:- no change.
I believe I am dead in the water. A shame as phone is only 9 months old.
Thanks for the help
JOhn Kilbert

The last thing to try is to restore the original Samsung firmware via Odin one-click. Take a look at sticky threads in Captivate Android Development section, latest AT&T ROM is available. Are you sure the phone is only 9m old? The last Captivate was manufactured around 10/2011, I believe.

Val D. said:
The last thing to try is to restore the original Samsung firmware via Odin one-click. Take a look at sticky threads in Captivate Android Development section, latest AT&T ROM is available. Are you sure the phone is only 9m old? The last Captivate was manufactured around 10/2011, I believe.
Click to expand...
Click to collapse
I will try that and try pushing the captivate.zip to the internal SD and see if I can install from there
Yes, I am sure its 9 mos old, I just bought another one at lunch today from amazon

4 numbers under the battery show manufacturing month and year. What numbers you have there? Just curious...

Val D. said:
4 numbers under the battery show manufacturing month and year. What numbers you have there? Just curious...
Click to expand...
Click to collapse
The new phone say m39 & 11/11 not sure which is hte date code, the other 2 captivates (both dead) do not have a date but say rev 0.4

Related

[Q] Can't boot phone after flashing CM9

Hello everyone,
I've tried to install CM9 on my Samsung Galaxy S I9000. However, I must have done something wrong in the process. I'm totally new to the whole custom ROM thing. I'll try to list the steps I performed to install CM9. I hope someone can point out where I went wrong.
Generally, I followed the instructions given in http://forum.xda-developers.com/showthread.php?t=1363593 .
1) Installed "ROM Manager" (https://market.android.com/details?id=com.koushikdutta.rommanager&hl=de).
2) Rooted my phone according to the instructions in http://androidadvices.com/root-samsung-galaxy-gt-i9000-android-234-xxjvr-firmware/3/ . This uses Odin 3 v1.7 and also installed CWM Recovery (v3.0.0.5) . I checked that my firmware exactly matches the one for which the description is for.
3) Performed a backup using CWM Recovery.
4) Performed wipe (data/factory reset AND cache).
5) Installed CM9 using CWM which I had downloaded from the links given in the thread given at the beginning and placed the four .zip files (CM9, Google apps, Google apps fix and Faceunlock) on my external SD card. I only realized afterwards that the instructions said to place them on the internal SD card.
6) Installed Google apps, Google apps fix and Faceunlock using CWM.
7) Selected reboot in CWM. However, the device didn't boot into Android. First I saw the CM logo screen, then the phone got stuck on the "Samsung Galaxy S I9000" screen.
8) Read instructions again, realized that I forgort the wipe after installing Google apps. Performed the two wipes again, however the problem remained.
9) Read instructions again, realized that I was supposed to install the .zip files from the internal SD card. I assumed that was the step I went wrong. So I decided to restore to my stock ROM which I had backup'ed before. I used the restore option in CWM, selected my previous backup (located on external SD card) and performed the restore.
10) However, the phone still does not get pass the "Samsung Galaxy S I9000" screen. When I boot into CWM, the following appears on my screen
E:unknown volume for path [/data]
E:unknown volume for path [/data]
E:Unable process volume! Skipping...
Checking /cache...
E:unknown volume for path [/cache]
E:unknown volume for path [/cache]
E:Unable to process volume! Skipping...
Done!
E:unknown volume for path [/cache/recovery/command]
E:Can't mount /cache/recovery/command
E:unknown volume for path [/cache/recovery/log]
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:unknown volume for path [/cache/recovery/last_log]
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:unknown volume for path [/cache/recovery/command]
Click to expand...
Click to collapse
The same apperas if I try to do a "restore" from CWM again.
My questions:
1) Where did I go wrong?
2) What must I do to be able to attempt to install CM9 again?
Thanks in advance!
To get back to stock you have to flash a 3 file stock rom with repartition in odin.
i think the best is to get back stock, if you tried to restore a backup. then flash semapore kernel.
Then boot in recovery, wipe. Flash build 12 and gapps then reboot.
Sent from my GT-I9000 using Tapatalk
Hi and thanks for your reply.
Sorry, I don't really understand most of your post
1) What is a "3 file stock rom"? I know what the stock ROM is, however, what is with the "3 file"?
2) Where can I get the proper stock ROM for my phone? Haven't I backup'ed my stock ROM when I did the backup in CWM?
3) What is repartition?
4) What is semapore kernel? Why do I need it? Where can I get it?
5) So according to you I did nothing wrong in my installation and it *could* work if I tried a second time?
oxyris said:
Hi and thanks for your reply.
Sorry, I don't really understand most of your post
1) What is a "3 file stock rom"? I know what the stock ROM is, however, what is with the "3 file"?
2) Where can I get the proper stock ROM for my phone? Haven't I backup'ed my stock ROM when I did the backup in CWM?
3) What is repartition?
4) What is semapore kernel? Why do I need it? Where can I get it?
5) So according to you I did nothing wrong in my installation and it *could* work if I tried a second time?
Click to expand...
Click to collapse
First take a look in ramads thread: http://forum.xda-developers.com/showthread.php?t=1102881
1. Here you can read how to flash with odin and download the latest gingerbread stock rom
2 your backup will work, but you have to be on a stock rom first.
3. read how to flash with odin in the link.
4. Semapore kernel is a custom kernel, comes prerooted and stuff.
so after you are back stock you can flash this in odin, put it in pda and dont thick repartiton. No you are ready again. turn of phone, boot into recovery mode with 3 button combo, here you can restore your backup if you want. or wipe factory reset, wipe catche and dalvik catche flash build 12 and gapps from internal sd. reboot and enjoy ics http://forum.xda-developers.com/showthread.php?t=1112908 remember to download the correct kernel for your build.
5. hard to say, the best way to get correct cwm is to flash a kernel as semapore or cf root. maybe it was somthing with your cwm (recovery)
Edit: it take some time to boot the first time
Thanks again for your reply.
So I managed to flash the stock ROM. I chose the "XFJV7/XXJVQ/OXFJV1/Sbl (MultiCSC)" which is the newest one for Android 2.3.4. I didn't tick "repartition" and didn't select Pit (what is this?) in Odin.
Now considering the Semapore kernel: how do I know which one to download in the thread you posted? Can I just take the newest one? Will I have root once I've installed this kernel? I'm asking because in the FAQ (semaphore.gr/faq) it says it requires another app (Superuser) in order to have root?
oxyris said:
Thanks again for your reply.
So I managed to flash the stock ROM. I chose the "XFJV7/XXJVQ/OXFJV1/Sbl (MultiCSC)" which is the newest one for Android 2.3.4. I didn't tick "repartition" and didn't select Pit (what is this?) in Odin.
Now considering the Semapore kernel: how do I know which one to download in the thread you posted? Can I just take the newest one? Will I have root once I've installed this kernel? I'm asking because in the FAQ (semaphore.gr/faq) it says it requires another app (Superuser) in order to have root?
Click to expand...
Click to collapse
its not the newest. you should have thick repartition and 512 pit here. But if the phone boots up i think its ok. only kernel flash its important not to thick repartition.
its best to use this kernel http://download.chainfire.eu/124/CF-Root/SGS/CF-Root-XX_UNK_JVQ-v3.7-CWM3RFS.zip
I tried flashing CM9 again with the Semapore kernel I had installed first. It seemed to work, however, after booting into CM9, a screen appeared that said something like "Device encryption failed" and I could not get into the OS. Any idea what that could have been?
I'll give it another try anyway, this time with repartitioning and PIT when flashing the stock ROM and with the other kernel you suggested.
Slightly off topic, but what's with this obsession about 3 file roms that's been going around for a long time? I have yet to see any evidence to support the belief that 3 files rom is someone better than single file rom.
@OP: Try flashing CM7 first. See if that works. Then flash CM9.
So what's the difference between a 3 file ROM and a single file ROM?
I've tried again with PIT + repartition, the CF kernel and CM9. However, the whole thing ended in a bootlop (Samsung Galaxy S I9000 foloowed by CM screen).
I don't understand what I'm doing wrong...
I'll try CM7 next...
edit: Something else I noticed. When I connect my phone as mass storage, the internal SD card still contains a bunch of files/folders that belong to apps from my original installation. Shouldn't these be deleted when I did the data/factory reset?
edit2: According to the CM7 thread (http://forum.xda-developers.com/showthread.php?t=1061946), "you're not able to flash any kernel or run any filesystem you want". So which kernel can I use?
oxyris said:
So what's the difference between a 3 file ROM and a single file ROM?
I've tried again with PIT + repartition, the CF kernel and CM9. However, the whole thing ended in a bootlop (Samsung Galaxy S I9000 foloowed by CM screen).
I don't understand what I'm doing wrong...
I'll try CM7 next...
edit: Something else I noticed. When I connect my phone as mass storage, the internal SD card still contains a bunch of files/folders that belong to apps from my original installation. Shouldn't these be deleted when I did the data/factory reset?
Click to expand...
Click to collapse
Hi,
I'll get 3 weeks ago SGS in a bottloop after flashing CM9 build11 (teamhacksung's) from latest CM7.
I went mad four about few hours, afterthat I decided to reflash stock 2.3.6 (JVX_JV3_JVT.tar).
After flashing with Odin, I end-up with in DBDATA error after rebooting..
So I flashed dbdata.rfs.tar and I've got original 2.3.6 working.
So:
-I've rooted my device again (CF-Root-XX_OXA_JVT-v4.3-CWM3RFS.tar)
-Installed ROM manager
-Rebooted into recovery
-Flashed ICS port latest builds + GApps + face unlock (and wiped ALL).
No my device is working with ICS,
hope this will help you guys on flashing ICS and don't waste time.
Cheers
Thanks. I've tried your approach, but I'm only getting the "encryption unsuccessful" screen after entering my PIN. It says something like the encryption was lost and can't be completed and that therefore, the data on the phone is not accessible.
In the "Known issues" list in the CM9 thread it says
Phone unnecessarily gets data connection on device encryption password enter screen.
Click to expand...
Click to collapse
But I'm not sure if they're referring to my particular problem.
oxyris said:
Thanks. I've tried your approach, but I'm only getting the "encryption unsuccessful" screen after entering my PIN. It says something like the encryption was lost and can't be completed and that therefore, the data on the phone is not accessible.
In the "Known issues" list in the CM9 thread it says
But I'm not sure if they're referring to my particular problem.
Click to expand...
Click to collapse
May be the only way is to wait devs to solve that issue.
I'm so sorry that my tips didn't work 4 u...
oxyris said:
Thanks. I've tried your approach, but I'm only getting the "encryption unsuccessful" screen after entering my PIN. It says something like the encryption was lost and can't be completed and that therefore, the data on the phone is not accessible.
In the "Known issues" list in the CM9 thread it says
But I'm not sure if they're referring to my particular problem.
Click to expand...
Click to collapse
One question, do you have your SD Card in your phone when you are going through the install process? If so, take that out before flashing anything. It has been the cause of problems for a lot of people coming to CM9.
Hi, thanks for your replies.
I seem to have solved the issue. When the "device encryption unsuccessful" screen appeared, I booted to recovery using the power button (a menu will appear letting you choose between shut down, restart or recovery) and came into CWM. There, I wiped everything (i.e. factory, cache and dalvik or whatever its called) and rebooted. I could then start the OS without any further problems (until now).
I also noticed that now my internal SD card is actually "clean" again, i.e. it only contains the folders and files that are there when you get your phone new. This wasn't the case when I performed a wipe BEFORE flashing CM9.
I'm using the CF-Root-XX_OXA_JVT-v4.3-CWM3RFS.tar kernel you suggested, maybe that was the problem (I can't recall being able to boot into recovery the first time the "device encryption unsuccessful" screen appeared).
@ryanmat Yes, I did have my external SD card in the phone during the installation process, but thanks for your suggestions.
edit: I will report back if everything goes smooth for a few days.
ok, let me understand...
now you got CWM working and you've got CM9 after wipe all with rooted kernel I suggest you?
Exactly. Let me write down the individual steps I finally performed to get CM9 running.
1) Get Odin and PIT files -> http://www.multiupload.com/51MTA5K1H7
2) Boot phone to download mode
3) Start Odin on computer
4) Connect phone to computer (USB)
5) Flash stock ROM -> http://www.multiupload.com/PKVWPJJZMO (check repartition, put in the 512 PIT file and select the PDA, PHONE and CSC files from the stock ROM, then hit start)
6) Disconnect phone from computer
7) Restart Odin on computer
8) Boot phone to download mode
9) Connect phone to computer (USB)
10) Flash the CF kernel for root access -> http://www.filesonic.ch/file/2356034801 (don't check repartition, no PIT file, select the downloaded tar file as PDA, then hit start)
11) Boot the phone to the stock ROM. After the kernel was flashed, you should have CWM installed. Place the CM9 tar, as well as the gapps, gappsfix and faceunlock tars in your internal SD card. Start CWM and boot into recovery from there.
12) In CWM recovery, select install zip from SD card and select the CM9 ROM. After the installation, my phone automatically rebooted, booted CM9 and got into the "encryption unsuccessful" screen.
13) Hold the power button, select reboot and then select recovery to get back into CWM recovery.
14) Perform factory reset, cache wipe and dalvik cache wipe (found under advanced).
15) Select reboot in CWM recovery, you should now be able to boot into CM9.
16) Reboot into CWM again and install gapps, gappsfix and faceunlock if desired.
I don't know if all of these steps are required or if they must be performed in this exact order. However, it worked for me (CM9 build 12).
and now build 13 is out...!!!

[ROM] STOCK - FULL ICS IMM76D.LP10 for Verizon i815 LTE Tab (only!) *UPDATE 10/16*

UPDATE: My hosting I had for XDA related work expired, so I re-uploaded everything here: http://www.mods4cars.com/pub/xda
Hi everyone. As pretty much everyone of us who got suckered into buying this excellent (hardware) tab from Verizon knows, their update strategy has been very slow and on top of that, glitchy. Finally, 4 months after the other editions of this tab, we're getting ICS... BUT the update is an incremental OTA update that fails on 99% of the tabs, because it expects a version FD01b instead of the FD01 most of us have. The update seems to have gone through for only 2 or 3 lucky users who must somehow have had FD01b on their tab when they got it.
So after one of the best collaboration efforts on the "Tab 7.7 General" forums, I am happy to present to you
The CWM flashable "full stock" ROM for the SCH-i815 - ICS IMM76D.LP10
First up, let me stress again that this is a HACK and that this is RISKY and that if something goes wrong you MAY end up with a BRICK that will require complicated revival ceremonies! Unfortunately I *have* to say here, that whatever you do here, you do AT YOUR OWN risk, I can not be held liable for anything!
Prerequisites:
Verizon SCH-i815 LTE Tablet (ONLY this version!) with Honeycomb (everyone should have FD01 at this point)
Windows PC with Samsung USB drivers installed, meaning when you connect the tab, you should be able to copy files to it.
A micro-SD Card 2GB or bigger, preferable BLANK, FAT32 formatted.
Step 1: Prepare the SD card
Connect the SD card to your PC and copy the ROM files to it.
ROM Choices:
Original Cloned ROM (First version with direct partition image copy, requires >1GB space on SD card which has caused issues for some)
http://electron73.org/XDA/i815/electron_ICS-LP10_i815.zip
Update 10/12:
NEW ROM with full ext4 optimizations. System, Cache and Data (only in wipe version) will be cleared, formatted and "fsck -Dfy" checked!
DO NOT WIPE ANYTHING IN CWM!!! Just choose the ROM file appropriately.
Non-Wipe Version (This one leaves existing data partition alone, only checks it for errors)
http://electron73.org/XDA/i815/electron_ICS-LP10_i815_nowipe.zip
Wipe Version (THIS ONE WILL FORMAT DATA PARTITION, ALL USER DATA WILL BE LOST!)
http://electron73.org/XDA/i815/electron_ICS-LP10_i815_wipe.zip
Step 2: Download the Odin CWM Recovery pack and get ready to flash
Odin Pack: http://electron73.org/XDA/i815/electron_i815_odin_pack.zip
This ZIP contains everything you need now and later during this process. Extract it in any folder you like (Desktop/Odin or C:\Odin).
Run Odin3 v1.85.exe
Step 3: Bring the tab into Odin mode
Hold down the power and volume down buttons on your tab continuously until you see the big warning. Press volume UP to enter flash (odin) mode. Connect USB. In Odin the leftmost ID:COM field should now be yellow. Click the PDA button and select the cwm-6.0.1.1-i815.tar file. Leave everything else as-is. Click start to flash and when it says rebooting immediately grab the tab and hold down power and volume UP until you see the blue CWM screen! If you don't do this and let the tab boot, then it will automatically kill CWM (yes, bastards!), so don't let it boot the regular ROM!
Step 4: Flash the ICS ROM
Insert the card into the tablet, then in CWM go to install zip from sdcard, then choose zip from external sdcard. Select the electron_ICS-LP10_i815_v2.zip.
It will flash the kernel, the radio (LTE modem), the factory fs (/system) and preload partitions. The whole flash will take about 5 min. Especially on the last two steps be patient, it takes a while to extract 800mb and then flash the full filesystem image. Turning off power here (or running out of battery juice!) will make the rom unbootable and will require a full re-do. IMPORTANT: This requires the use of an external SD card! Using internal storage will not work!
WARNING: DO NOT wipe or factory reset in CWM! You can simply install ICS over an existing Honeycomb setup! Choose the correct ROM version: One erases everything and the other one preserves user data. Since this was originally an OTA, it knows how to convert your saved data. So all your emails, save games etc. will still be there! We had too many reports of problems when wiping/factory resetting with CWM. So for now the best advice for anyone looking into installing the ROM is DO NOT WIPE!
UPDATED PROCEDURE as of 10/16 - NO NEED to flash the old 3e recovery any more! Much easier and quicker baseband update below...
Step 5: Download and flash the baseband modem.bin with ODIN
Download the baseband update: http://electron73.org/XDA/i815/electron_ICS-LP10_i815_modem.zip
Bring the tab back into ODIN mode the same as before. Extract the modem.bin file from the modem.zip and drop it in the PHONE section (not PDA!) in ODIN this time. Click start and let it flash and reboot. Done. Under settings/about device you should now have Baseband Version i815.04 V.LP10 / I815LP10
B]Step 6: Optional: Keep CWM or go all stock[/B]
If you would rather like to be full stock than keeping CWM as the recovery program, then bring the tab back into ODIN mode one last time (pwr + vol down) and Connect USB, then flash LP10_recovery.
The ROM is pre-rooted. SuperSU is pre-installed as part of the ROM.
Trouble?
If the tab for some reason gets stuck in a boot loop with the Verizon animation playing over and over, don't fret! Give it AT LEAST 10 full minutes to start with and if it still doesn't show the home screen after that, hold down power and vol up until you're in CWM and wipe data/factory reset (yes, that will completely kill all user data and the tab will be "like new").
Trickier: If you see any warnings in CWM or 3e stock recovery, that there was an error mounting /data, then you lost the data partition and need to do extensive hacking before the tab will ever boot again. We fixed exactly this problem beginning on the very bottom of the page here http://forum.xda-developers.com/showthread.php?t=1927392&page=16 so don't panic! This repair surgery thanks to the excellent guide by Androguide.fr here: http://forum.xda-developers.com/showthread.php?t=1862294
Thanks
Thanks to everyone involved in making this happen! Especially asenduk for dumping the image backups from his tab, rayjr13 for bringing this whole thing to my attention and sending me the first OTA bin file.
Every use of the thanks button is greatly appreciated
Hi, thank you so much for these instructions and all the help. I was wondering does that 6.0.1.1 protect you from the brick bug and I saw that you hosted the V2 file in the original thread but here you have the regular file hosted. Is the V2 better?
johnny13oi said:
Hi, thank you so much for these instructions and all the help. I was wondering does that 6.0.1.1 protect you from the brick bug and I saw that you hosted the V2 file in the original thread but here you have the regular file hosted. Is the V2 better?
Click to expand...
Click to collapse
What is this brick bug people speak of? Bricking during a flash or bricking when you're sleeping at night and doing nothing to the tab?
Thanks again for this Rom electronic73! Hopefully some devs will take this as a base and run with it!
Sent from my SCH-I815 using xda premium
johnny13oi said:
Hi, thank you so much for these instructions and all the help. I was wondering does that 6.0.1.1 protect you from the brick bug and I saw that you hosted the V2 file in the original thread but here you have the regular file hosted. Is the V2 better?
Click to expand...
Click to collapse
Yes the 6.0.1.1 (as far as I know!) is safe. No need to wipe anyway. The v2 included more files that turned out to be not necessary. The files posted here along with the updated, safer method of flashing, should be the best and quickest way to get to full stock ICS.
The v2 was mainly an attempt to bring user ice's tab back to life after his data partition got killed.
Newbie question of the day - where is the IMEI stored on the 7.7? If it's in /system, won't this result in *everyone* flashing this image ending up with the same IMEI (which causes a whole set of problems of its own)?
Rodney
Thank you so much, and I do plan on doing a wipe to clear out my Tab to bring it to a clean slate. Just didn't want it to be a broken state lol.
rhester72 said:
Newbie question of the day - where is the IMEI stored on the 7.7? If it's in /system, won't this result in *everyone* flashing this image ending up with the same IMEI (which causes a whole set of problems of its own)?
Rodney
Click to expand...
Click to collapse
IMEI and such is stored in the mmcblk0p1 partition which (along with 2 and 3 which are the bootloader) we don't touch. So no, we only flash the factory fs, lte modem and kernel. CDMA modem.bin via the new method.
electron73 said:
Hi everyone. As pretty much everyone of us who got suckered into buying this excellent (hardware) tab from Verizon knows, their update strategy has been very slow and on top of that, glitchy. Finally, 4 months after the other editions of this tab, we're getting ICS... BUT the update is an incremental OTA update that fails on 99% of the tabs, because it expects a version FD01b instead of the FD01 most of us have. The update seems to have gone through for only 2 or 3 lucky users who must somehow have had FD01b on their tab when they got it.
So after one of the best collaboration efforts on the "Tab 7.7 General" forums, I am happy to present to you
The CWM flashable "full stock" ROM for the SCH-i815 - ICS IMM76D.LP10
First up, let me stress again that this is a HACK and that this is RISKY and that if something goes wrong you MAY end up with a BRICK that will require complicated revival ceremonies! Unfortunately I *have* to say here, that whatever you do here, you do AT YOUR OWN risk, I can not be held liable for anything!
Prerequisites:
Verizon SCH-i815 LTE Tablet (ONLY this version!) with Honeycomb (everyone should have FD01 at this point)
Windows PC with Samsung USB drivers installed, meaning when you connect the tab, you should be able to copy files to it.
A micro-SD Card 2GB or bigger, preferable BLANK, FAT32 formatted.
Step 1: Prepare the SD card
Connect the SD card to your PC and copy the ROM files to it.
ICS ROM: http://electron73.org/XDA/i815/electron_ICS-LP10_i815.zip
Modem Upgrade: http://electron73.org/XDA/i815/electron_ICS-LP10_i815_modem.zip
Make sure you have MORE than 1GB of free space left on the SD card when done.
Step 2: Download the Odin CWM Recovery pack and get ready to flash
Odin Pack: http://electron73.org/XDA/i815/electron_i815_odin_pack.zip
This ZIP contains everything you need now and later during this process. Extract it in any folder you like (Desktop/Odin or C:\Odin).
Run Odin3 v1.85.exe
Step 3: Bring the tab into Odin mode
Hold down the power and volume down buttons on your tab continuously until you see the big warning. Press volume UP to enter flash (odin) mode. Connect USB. In Odin the leftmost ID:COM field should now be yellow. Click the PDA button and select the cwm-6.0.1.1-i815.tar file. Leave everything else as-is. Click start to flash and when it says rebooting immediately grab the tab and hold down power and volume UP until you see the blue CWM screen! If you don't do this and let the tab boot, then it will automatically kill CWM (yes, bastards!), so don't let it boot the regular ROM!
Step 4: Flash the ICS ROM
Insert the card into the tablet, then in CWM go to install zip from sdcard, then choose zip from external sdcard. Select the electron_ICS-LP10_i815_v2.zip.
It will flash the kernel, the radio (LTE modem), the factory fs (/system) and preload partitions. The whole flash will take about 5 min. Especially on the last two steps be patient, it takes a while to extract 800mb and then flash the full filesystem image. Turning off power here (or running out of battery juice!) will make the rom unbootable and will require a full re-do. IMPORTANT: This requires the use of an external SD card! Using internal storage will not work!
BTW there is NO NEED to wipe! You can simply install ICS over an existing Honeycomb setup! Since this was originally an OTA, it knows how to convert your saved data. So all your emails, save games etc. will still be there!
Step 5: Flash the old Honeycomb recovery in order to do the modem upgrade
Since CWM does not understand the proprietary command used to flash the "firmware" which is the base modem file, we need to use STOCK recovery for this. The downside is that, of course, the new recovery is now locked down and won't accept unsigned files. So we need to flash the OLD Honeycomb FD01 recovery and feed it the modem update!
When the CWM flash above is finished and tells you to reboot, simple press and hold power and vol down again to get back into ODIN mode. Connect the USB again and this time use Odin the same way as above, but to flash the FD10_recovery.tar. This time uncheck the "reboot" tick mark.
Step 6: Flash the modem upgrade with the old stock 3e recovery
When Odin is done above, hold down pwr and vol up until you see the old school recovery pop up saying *manual mode*. Select flash update zip from sdcard and select the electron_ICS-LP10_i815_modem.zip this time. It will go on for a while in total bling flight. No output apart from rotating gears! This one is tricky. Just wait until it either ends saying that it is done or a yellow exclamation point shows up in the middle of the screen. The flash is done.
Step 7: Choose between Stock and CWM
Now bring the tab back into ODIN mode one last time (pwr + vol down) and Connect USB, then flash either CWM or LP10_recovery if you rather like to be full stock. If you chose CWM then be aware that the ROM will try to overwrite that immediately on first boot!! In order to avoid that, flash it with "reboot" box unticked and manually reset into CWM mode (pwr + vol up) and inside CWM select reboot system. It will then give you a big warning that the ROM has a CWM killer and offers you to disable that, so CWM will stay in place (good for Nandroids etd).
Step 8: Boot the ICS ROM and enjoy!
Once you see ICS, go to the play store and install SuperSU. The rom is pre-rooted and just needs the SuperSU app for full root access control.
Trouble?
If the tab for some reason gets stuck in a boot loop with the Verizon animation playing over and over, don't fret! Give it AT LEAST 10 full minutes to start with and if it still doesn't show the home screen after that, hold down power and vol up until you're in CWM and wipe data/factory reset (yes, that will completely kill all user data and the tab will be "like new").
Trickier: If you see any warnings in CWM or 3e stock recovery, that there was an error mounting /data, then you lost the data partition and need to do extensive hacking before the tab will ever boot again. We fixed exactly this problem beginning on the very bottom of the page here http://forum.xda-developers.com/showthread.php?t=1927392&page=16 so don't panic! This repair surgery thanks to the excellent guide by Androguide.fr here: http://forum.xda-developers.com/showthread.php?t=1862294
Thanks
Thanks to everyone involved in making this happen! Especially asenduk for dumping the image backups from his tab, rayjr13 for bringing this whole thing to my attention and sending me the first OTA bin file.
Every use of the thanks button is greatly appreciated
Click to expand...
Click to collapse
Hey Electron, thanks again for your outstanding work as well as all involved to make this happen. Since I installed your V2 this morning, I can skip the ICS ROM installation and go straight to step 5 right? Or is it better to start over from scratch?
Sent from my Nexus 7 using xda premium
bathanr said:
Hey Electron, thanks again for your outstanding work as well as all involved to make this happen. Since I installed your V2 this morning, I can skip the ICS ROM installation and go straight to step 5 right? Or is it better to start over from scratch?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Same here, what steps do I take to flash the updated modem
Awesome!
ice0901 said:
Same here, what steps do I take to flash the updated modem
Click to expand...
Click to collapse
from step 5 on forward. no need to reflash the whole rom if you already have ICS running.
Just odin the old recovery on, flash the modem update zip, then odin the new recovery or CWM back.
boot loop
Not sure whats up. Ive had your rom on all day. No problems. When i went to install the modem update, i entered odin and installed stock recovery, and boom, went into a verizon logo boot loop. i continued any way with the modem install, then put cwm back on, then wiped and data factory reset. waited 10 minutes during bootloop. Gave up, totally reflashed entire V2 Rom, again, stuck on a bootloop...so nwiped and data factory reset again,,,,still a bootloop....
bummer...does it just run until battery dies?
rspong said:
Not sure whats up. Ive had your rom on all day. No problems. When i went to install the modem update, i entered odin and installed stock recovery, and boom, went into a verizon logo boot loop. i continued any way with the modem install, then put cwm back on, then wiped and data factory reset. waited 10 minutes during bootloop. Gave up, totally reflashed entire V2 Rom, again, stuck on a bootloop...so nwiped and data factory reset again,,,,still a bootloop....
bummer...does it just run until battery dies?
Click to expand...
Click to collapse
Weird. OK did the v2 flash go all the way through? Did it finish at some point and say "please reboot" ? Or did it get stuck half way though?
Can you in CWM mount your internal storage? Did you get any errors when you did the full wipe/factory reset? anything saying "error mounting /data" maybe ?
electron73, did you create the .pit file in the cwm zip? It does not seem to match my i815 (which may be my problem, that mine is wrong)
I noticed the latest stock rom is like 550mb opposed to the one you uploaded this morning which was 990mb.. Is there a difference?
almus said:
electron73, did you create the .pit file in the cwm zip? It does not seem to match my i815 (which may be my problem, that mine is wrong)
Click to expand...
Click to collapse
No I didn't create it but it is guaranteed the right one for i815. I know because I messed up my partition table last night and had to use that pit to repartition Lucky I found that. What you would do in order to re-do your pit is open odin, put the CWM in the PDA section as usual and then click PIT and select that pit. That should activate a checkbox "repartition device". Leave that on for this one run and click start.
As a result it should partition, then flash the CWM and you should immediately be able to enter CWM. With CWM running connect USB
and use adb shell to get onto your tab.
IN the root prompt enter parted /dev/block/mmcblk0
and in the parted prompt enter print. If you see the result as in the attached pic (note: no file system in the DATAFS line) then you need to fix that the same way ice got it fixed last night. I think the link to the thread is in the OP
bathanr said:
I noticed the latest stock rom is like 550mb opposed to the one you uploaded this morning which was 990mb.. Is there a difference?
Click to expand...
Click to collapse
Yes the difference is that the preload partition (550mb decompressed) is not included any longer. Not needed. It was never altered in the first place. It only contains a game and useless verizon demonstration videos. I found out later that it had been untouched since Honeycomb FA02c
Yes. V2 went through with no problems.in CWM I can mount efs,cache,system but not data. Then in cwm... OK..wiping data then I get a error mounting data. Skipping format
Sent from my DROID RAZR using xda premium
chefdave12118 said:
What is this brick bug people speak of? Bricking during a flash or bricking when you're sleeping at night and doing nothing to the tab?
Thanks again for this Rom electronic73! Hopefully some devs will take this as a base and run with it!
Sent from my SCH-I815 using xda premium
Click to expand...
Click to collapse
The flash controller in our tablets is buggy. See here http://forum.xda-developers.com/showthread.php?t=1862294
electron73 said:
Yes the difference is that the preload partition (550mb decompressed) is not included any longer. Not needed. It was never altered in the first place. It only contains a game and useless verizon demonstration videos. I found out later that it had been untouched since Honeycomb FA02c
Click to expand...
Click to collapse
Thanks again man.. You have put forth an awesome effort in this work.. Sent you a little something as an appreciation:good:
---------- Post added at 09:43 PM ---------- Previous post was at 08:46 PM ----------
bathanr said:
Thanks again man.. You have put forth an awesome effort in this work.. Sent you a little something as an appreciation:good:
Click to expand...
Click to collapse
I ran into the splash screen just hanging and followed the data retore steps. I keep getting this error when trying to print the print command from the parted prompt.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Flatlinz>f:
F:\>cd 7.7
F:\7.7>cd adb
F:\7.7\adb>adb shell
adb server is out of date. killing...
* daemon started successfully *
~ # ls
ls
boot init sys
cache init.rc system
charger lpm.rc tmp
data preload ueventd.goldfish.rc
default.prop proc ueventd.rc
dev recovery ueventd.smdk4210.rc
efs res vendor
etc sbin
external_sd sdcard
~ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Error: Can't have the end before the start!
(parted)
Any ideas?

Stuck without a OS

Good Morning
Very ironic,but i came here to ask about rooting my phone a year back and now i'm back in sort of the same situation..
A year back I rooted my froyo 2.2.1 based Galaxy S to a gingerbread version,then i used quite a few of the ICS roms available on this forum,had been using Cyanogen for the past few months.Yesterday i had some free time,so i thought would check out the JB roms available.
So i did the usual,download the JB version of Fishears since i had a iNand.put it in my internal sdcard..but i could not access the memory card from CWM 5.0.2.7..,so i put it in my external memory card and tried to run the zip from there,but the process got aborted in the middle,tried it twice,dint work.
Then i remembered i had faced this internal memory problem before,had to go and switch on the debugging mode in the developer option.[P.S:- i had been facing the encryption successful problem for half a year,was too lazy/busy to fix it,i just took it in my stride and rebooted a lot to get into the homepage]
So,I'm in CWM and i run the usual process and run the zip file from the internal sdcard,it started out fine,them BOOM.my phone reboots all of a sudden.When it restarts,it does not have a OS to boot into,the green android image with a red exclamation mark and a few text appears which happens too fast to read and it keeps rebooting and this process goes on.
I can still access CWM and the download mode,i tried going into CWM but the internal sd doesnt open and the zip file fails to mount from the external sd.
So i thought **** it,i'll do the rooting part again and i run up ODIN,download the semaphore 2.7.4 kernel,and i see it is just 15 mb or so,i remembered i used more than 1 file and used the pit folder also,but i read it on the semaphore website,its only 1 file and have to use it as the PDA.went to download mode and odin recognised it and the process completed without a hitch,it even showed a green PASS..
but the problem came when it had to reboot after the process,it got stuck in the "Galaxy S GT I9000" page and never moved forward.it was there for 30 minutes or so before i pulled out the battery.
Basically
1.I cant get past that page
2.I can access the CWM and Download modes
3.I accepted my mistake and thought of not doing any more mistakes,so icame here
4.When i boot into CWM mode,these errors come
E:failed to open/etc/recovery.fstab (No such file or directory)
E:unknown volume for path[/cache/recovery/command]
E:Can't mount /cache/recovery/command
E:unknown volume for path [/cache/revovery/log]
E:Cant mount /cache/recovery/log
E:Cant open /cache/recovery/log
E:unknown volume for path [/cache/recovery/last_log]
E:Cant mount /cache/recovery/last_log
E:Cant open /cache/recovery/last_log
E:unknown volume for path [/cache/recovery/command]
Click to expand...
Click to collapse
Cant access the external sd from the CWM now
I dont mind any os now,as long as i can take calls.Am leaving college for home by train day after,so i need a working os as soon as possible
Thank you for reading this and thank you in advance for taking your time to help me out
deathstoned said:
Good Morning
Very ironic,but i came here to ask about rooting my phone a year back and now i'm back in sort of the same situation..
A year back I rooted my froyo 2.2.1 based Galaxy S to a gingerbread version,then i used quite a few of the ICS roms available on this forum,had been using Cyanogen for the past few months.Yesterday i had some free time,so i thought would check out the JB roms available.
So i did the usual,download the JB version of Fishears since i had a iNand.put it in my internal sdcard..but i could not access the memory card from CWM 5.0.2.7..,so i put it in my external memory card and tried to run the zip from there,but the process got aborted in the middle,tried it twice,dint work.
Then i remembered i had faced this internal memory problem before,had to go and switch on the debugging mode in the developer option.[P.S:- i had been facing the encryption successful problem for half a year,was too lazy/busy to fix it,i just took it in my stride and rebooted a lot to get into the homepage]
So,I'm in CWM and i run the usual process and run the zip file from the internal sdcard,it started out fine,them BOOM.my phone reboots all of a sudden.When it restarts,it does not have a OS to boot into,the green android image with a red exclamation mark and a few text appears which happens too fast to read and it keeps rebooting and this process goes on.
I can still access CWM and the download mode,i tried going into CWM but the internal sd doesnt open and the zip file fails to mount from the external sd.
So i thought **** it,i'll do the rooting part again and i run up ODIN,download the semaphore 2.7.4 kernel,and i see it is just 15 mb or so,i remembered i used more than 1 file and used the pit folder also,but i read it on the semaphore website,its only 1 file and have to use it as the PDA.went to download mode and odin recognised it and the process completed without a hitch,it even showed a green PASS..
but the problem came when it had to reboot after the process,it got stuck in the "Galaxy S GT I9000" page and never moved forward.it was there for 30 minutes or so before i pulled out the battery.
Basically
1.I cant get past that page
2.I can access the CWM and Download modes
3.I accepted my mistake and thought of not doing any more mistakes,so icame here
4.When i boot into CWM mode,these errors come
Cant access the external sd from the CWM now
I dont mind any os now,as long as i can take calls.Am leaving college for home by train day after,so i need a working os as soon as possible
Thank you for reading this and thank you in advance for taking your time to help me out
Click to expand...
Click to collapse
you may try this, if you can boot to download mode but make sure your is GT-I9000
Before start, please backup all your important data and phones setting. Then,
Step 1:
I) Download Android 2.3.6 Gingerbread Value Pack (XXJVU)
II) Download ODIN http://www.mediafire.com/?nhhhkm5c2j43rhw Extract Odin3 v1.7.zip to get .exe file
also download the pit file, http://www.mediafire.com/?v2rub40k1bvccj4
Step 2: Extract the ROM [password: samfirmware.com]
Step 3: Launch ODIN. (Don’t open Samsung Kies)
Step 4: Turn off your Galaxy S.
Step5: Put your Galaxy S into Download Mode by Press and hold Volume Down + Home + Power buttons to boot into Download Mode.
Step 5: Connect your Galaxy S with your PC using a USB cable. (Before proceed to Next Step, please make sure that ODIN detect your device)
Step 6:
Click on Odin PIT Tab
Select the PIT – s1_odin_20100512.pit
Click on Odin PDA Tab
Select the CODE_I9000XXJVU_CL851880_REV03_user_low_ship.tar.md5 file.
Click on Odin PHONE Tab
Select MODEM_I9000XXJVU_REV_00_CL1092175.tar.md5.
Click on Odin CSC Tab
Select GT-I9000-CSC-MULTI-OXAJVU.tar.md5.
Step 9: Click on START in ODIN to start flash the leaked firmware on your device.
hope this will help.
I had this problem with Paranoid Android before... the zip was corrupt.
If you are able to extract the rom with winrar/winzip/totalcmd or other program, install it, if it is corrupt, download it again again and again...
Sent from my GT-I9000 using xda premium
Samtan4326 said:
you may try this, if you can boot to download mode but make sure your is GT-I9000
Before start, please backup all your important data and phones setting. Then,
Step 2: Extract the ROM [password: samfirmware.com]
Step 3: Launch ODIN. (Don’t open Samsung Kies)
Step 4: Turn off your Galaxy S.
Step5: Put your Galaxy S into Download Mode by Press and hold Volume Down + Home + Power buttons to boot into Download Mode.
Step 5: Connect your Galaxy S with your PC using a USB cable. (Before proceed to Next Step, please make sure that ODIN detect your device)
Step 6:
Click on Odin PIT Tab
Select the PIT – s1_odin_20100512.pit
Click on Odin PDA Tab
Select the CODE_I9000XXJVU_CL851880_REV03_user_low_ship.tar.md5 file.
Click on Odin PHONE Tab
Select MODEM_I9000XXJVU_REV_00_CL1092175.tar.md5.
Click on Odin CSC Tab
Select GT-I9000-CSC-MULTI-OXAJVU.tar.md5.
Step 9: Click on START in ODIN to start flash the leaked firmware on your device.
hope this will help.
Click to expand...
Click to collapse
Did what u said,got past odin,then it went into the setup on the phone and all of a sudden it went into the recovery screen,the message shown is
-- wiping data...
Formatting /data...
E:format_volume: rfs format failed on /dev/block/macblk0p2
Formatting /dbdata...
formatting /cache
Deleting meta data
Data wipe Failed
-- Applying Multi-CSC..
Installing Multi-CSC
APPLIED THE csc-Code "CPW"
Successfully applied multi-CSC
Click to expand...
Click to collapse
I have a option to reboot,its the samsung recovery screen..its still there,i havent touched my phone since then
deathstoned said:
Did what u said,got past odin,then it went into the setup on the phone and all of a sudden it went into the recovery screen,the message shown is
I have a option to reboot,its the samsung recovery screen..its still there,i havent touched my phone since then
Click to expand...
Click to collapse
flash CF-root for xxjuv with a pit512 (repartition ticked) cf-root can download from here http://download.chainfire.eu/132/CF-Root/SGS/CF-Root-XX_OXA_JVU_2.3.6-v4.3-CWM3RFS.zip
Once rooted with CWM, enter CWM using combo keys and enter "mounts and storage" and format everything except Boot and also do the full wipes one more time
Finally Flash the JVU+Root again one more time with PIT (repartition) to resolve this issue ...you may need flashing twice or more to solve this
issued.
http://forum.xda-developers.com/showthread.php?t=1841250 <--- this is very useful link for new user from xsenman
Samtan4326 said:
flash CF-root for xxjuv with a pit512 (repartition ticked) cf-root can download from here http://download.chainfire.eu/132/CF-Root/SGS/CF-Root-XX_OXA_JVU_2.3.6-v4.3-CWM3RFS.zip
Once rooted with CWM, enter CWM using combo keys and enter "mounts and storage" and format everything except Boot and also do the full wipes one more time
Finally Flash the JVU+Root again one more time with PIT (repartition) to resolve this issue ...you may need flashing twice or more to solve this
issued.
http://forum.xda-developers.com/showthread.php?t=1841250 <--- this is very useful link for new user from xsenman
Click to expand...
Click to collapse
flashed it with CWM,went into it and in Mounts and storage there is only 1 option- "mount USB storage"
Nothing else
Below that in the CWM message area,there is
E:unknown volume for path [/system]
E:unable process volume! Skipping...
Checking /data...
E:unknown volume for path [/data]
E:unable process volume! Skipping...
checking /cache...
E:unknown volume for path [/cache]
E:unable process volume! Skipping...
Done!
E:unknown volume for path [/cache/recovery/command]
E;Cant mount /cache/recovery/command
E:unknown volume for path [/cache/recovery/log]
E:Cant mount /cache/recovery/log
and the same for last_log
Click to expand...
Click to collapse
deathstoned said:
flashed it with CWM,went into it and in Mounts and storage there is only 1 option- "mount USB storage"
Nothing else
Below that in the CWM message area,there is
Click to expand...
Click to collapse
select mounts and storage format everything except Boot and also do the full wipes one more time and power off your phone
reboot to download mode follow by Flash the JVU+Root again one more time with PIT (repartition) to resolve this issue ...you may need flashing twice or more to solve this.
Samtan4326 said:
select mounts and storage format everything except Boot and also do the full wipes one more time and power off your phone
reboot to download mode follow by Flash the JVU+Root again one more time with PIT (repartition) to resolve this issue ...you may need flashing twice or more to solve this.
Click to expand...
Click to collapse
I dont think you got what i said.I installed CFW and went into the recovery,there under Mounts and storage ,there was nothing apart from "mount USB storage"..not even Mount BOOT..nothing apart from that 1 option..when i tried to do a wipe "data/factory reset or cache" it showed me that message which i posted above.still i installed the jvu+root again (Twice actually),it was the same result,the error i posted 2 posts above.
I'm in no mans land now and cant do anything apart from my phone apart from go into download and recovery mode
Please someone help me,i've to go on a 33 hr train journey tmrw and without a phone,it'll be really troublesome
Have you tried the EZ Recovery kit by Slaphead20?
http://forum.xda-developers.com/showthread.php?p=29114573
Sent from my GT-I9000
amerkiller1995 said:
Have you tried the EZ Recovery kit by Slaphead20?
http://forum.xda-developers.com/showthread.php?p=29114573
Sent from my GT-I9000
Click to expand...
Click to collapse
New developments now
I followed the steps given in the EZ recovery mode,it crashed into the same e3 recovery mode,for the heck of it i flashed the CFROOT which was provided and it worked fine..all disks were mounted fine and no errors in cwm,
went into Mounts and storage and formatted everything apart from boot and followed the rest of samtans advice
It crashed into the same e3 Rec mode again with the same meta data error message
any suggestions guys,atleast now i'm hopeful after seeing that CWM screen without any errors
deathstoned said:
New developments now
I followed the steps given in the EZ recovery mode,it crashed into the same e3 recovery mode,for the heck of it i flashed the CFROOT which was provided and it worked fine..all disks were mounted fine and no errors in cwm,
went into Mounts and storage and formatted everything apart from boot and followed the rest of samtans advice
It crashed into the same e3 Rec mode again with the same meta data error message
any suggestions guys,atleast now i'm hopeful after seeing that CWM screen without any errors
Click to expand...
Click to collapse
After flashing ez base, flash Cm9 and then if you want cm10
Sent from my GT-I9000
amerkiller1995 said:
After flashing ez base, flash Cm9 and then if you want cm10
Sent from my GT-I9000
Click to expand...
Click to collapse
Ok dont know whether this is good or bad
I installed CM9 from the external sd as the internal sd was inaccesible in any way..the installation showed info like
"the internal sd card marker could not be found
Going ahead with installation"
the installation continues and restarts once and updates but it does not boot into the main page,it directly goes into the Encryption Unsuccessful page.When i try Reset Phone,it goes into the CWM recovery screen with some errors,
when i try to install CM10 from this recvery screen,it initially stops the installation saying the data partition layout is different and all my data will be wiped.run the .zip to go ahead with the progress.I run this it goes directly into the CWM 6.0._._ and it doesnt show any errors,i try to reboot it gets stuck on the galaxy s screen.
this situation is better than the previous condition as i know a OS can still run on my Phone..Just need to get this thing rectified now
Please if anyone could help me right now,i would be really grateful..not able to contact anyone without my phone
It might be a hardware problem... I had something similar
http://forum.xda-developers.com/showthread.php?t=1895224
But for now go to Ez recovery and then try Darky's Resuruction ROM.
Sent from my GT-I9000
amerkiller1995 said:
It might be a hardware problem...
But for now go to Ez recovery and then try Darky's Resuruction ROM.
Sent from my GT-I9000
Click to expand...
Click to collapse
I installed Cyanogen 9 and got through tht EU page by restarting abut 20 times or so,now i'm trying to install a working version of gapps in it.Tried 1 but the setup failed,so i flashed back to Cyanogen 9 and am not touching it till i reach home.a device capable of making and taking calls is better than nothing..
Is there a way to download contacts from gmail without gapps,the play store is not included in the original rom and i'm hesitant to go into CWM recovery mode as i will have to tackle the EU page again
Anyways thanks for your help,will have to fix this problem once and for all after i reach home
I don't know about contacts from gmail. When you're home look at my updated post above
Sent from my GT-I9000
basically
just reflash gingerbread

Silm 3.0 bootloop hell [solved]

Hi all
I'm avoiding posting on the Slim thread as this ends up being a bit of a mess.
I've been using Slimbean 3.0 since last Thursday without major issues (nothing big, I was just waiting for the right moment to do a full backup and clean everything).
What happens is that my phone dies while coming back home from work and when I try to reboot it start bootlooping. There's no way I can get it back to life.
At this point I can get to download mode, but nothing else.
Yesterday I've been suggested to start looking into flashing something like CM10 and so I did.
By following these instruction http://wiki.cyanogenmod.org/w/Install_CM_for_galaxysmtd I manage to flash via heimdall CWM speedmod kernel without problems.
I finally have CWM working.
From there I can't get adb detect the device. The only way I can upload the rom is via CWM itself and so I did: I upload both Slimbean 4.2.1 RC1 and Slim_Gapps and cm10.0, just in case.
What I'm trying next is a full wipe to start from clean: full wipe/factory reset works OK, but when I try to format /system I get:
Code:
E:Can't mount /dev/block/st19 to /system with parameters auto llw,check=no
(File exists)
Error mounting /system/!
Skipping format...
Done.
This is the point where I'm at.
If I try to flash Slim I get (error 0), being unable to format system for the same above reason.
If I try to flash cm10.0 it doesn't even pass the device assertion check.
Now I'm particularly clueless. Do I need a different CWM that better supports Slim? Or is the system error something that is inherently wrong with my current status?
Any help is greatly appreciated.
PS: I was trying to find help on #freenode with no luck, I'm available there if anyone wants to help, my nick is ThePeach.
UPDATE: ok it seems that by trying to flash Slimbean it actually replaced the CWM with the one I was used to that comes with Slim and finally managed to format /system and flash Slim correctly without problems.
Yay!
I really hope nobody will ever find himself in this kind of mess...

[Q] Samsung Galaxy Pop

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

Categories

Resources