Related
Hello,
Like many other users on this forum, I am having trouble with my i9000M sdcard after doing some ROM flashing.
Although there is some extensive threads collecting the different situations people are experiencing, I was hoping I could get some help for a specific circumstance relating to the sdcard issue.
I'll start by..
- Detailing the firmwares I have flashed, and what happened
- What is working / not working now, and how I got to get to the current situation
- And finally, I'll detail what I'm trying to do and where I'm getting stuck.
I would really appreciate some help with this, and thank anyone who takes the time to read it. I am trying to be very thorough to give you as much information as possible.
-----------------------------------------------------------------------------
1. Started with stock firmware. I am not sure what it was.. I believe the phone is equivalent to the Bell i9000M, but I am on the SaskTel carrier.
2. Flashed firmware I9000XXJP2: This worked, and I was using Froyo 2.2 fine.
3. Tried to root Froyo 2.2 firmware: This FAILED and the trouble began. I was using the update.zip method, and the source claimed it was compatible with 2.2. I had to hard reboot the phone, but it would stall on the white text intro screen (not the animated one).
4. Went into Download mode. Tried to flash firmware I9000UGJH2 (apparently the most current bell firmware), using Odin v1.1. This FAILED, and I had to hard reboot, which resulted in the PHONE - ! - PC error. I am aware the i9000M can still be recovered from this state.
NOTE: I could do nothing at this point: all firmware flashes failed, UNTIL I CHANGED TO ODIN V 1.3!
Using Odin v.1.3:
5. Flashed a series of firmwares.. (I9000UGJG8, I9000XXJM1, I9000XWJG5), ALL resulted in the phone either being in a shutdown-boot loop to the white Glaxaxy text screen, or the battery charging screen.
I could enter Download mode to reflash, but NOT recovery mode.
6. The ONLY semi working firmware is I9000XXJP2, Samsung Froyo 2.2. This is what the phone is now.
- I CAN enter Download mode, Recovery mode, and the phone stalls on the white Galaxy boot screen, but goes no further, and does not restart.
- I CAN run abd commands
Here is the output I get from each of the options in the Recovery mode:
Code:
I9000XXJP2
Odin 1.3
512.pit
Flashes fine
Goes into recovery mode
Displays error:
(No such file or directory)
E:copy_dbdata_media: Can't mount SDCARD
your storage not prepared yet. please use UI me nu for format and reboot actions.
copy default media content failed.
Try to format sdcard:
Formatting SDCARD:...
ensure_root_path_unmounted**
ensure_root_path_unmounted (/mnt/internal_sd)
ensure_root_path_unmounted ret 0
ensure_root_path_unmounted It's not mounted
update media, please wait
E:Can't mount /dev/block/mmcb1k0p1
(No such file or directory)
E:copy_dbdata_media: Can't mount SDCARD
your storage not prepared yet. please use UI me nu for format and reboot actions.
Try to wipe cache partition:
-- Wiping cache...
Formatting CACHE:...
ensure_root_path_unmounted**
ensure_root_path_unmounted (/cache)
ensure_root_path_unmounted ret 0
unmount (/cache) attempt 1 (Unknown error: 0)Cache wipe complete.
Try to apply sdcard:update.zip
Same errors as 1) can't mount sdcard therefor installation fails.
Reboot system:
- Will accept adb download reboot
note: I can reach download mode using the button combination
- recovery mode: can access with button combination or 'adb reboot recovery'
- power off: battery charging indicator shows
note: it does not loop the battery indicator
- power on: stalls at Galaxy S GT-19000 white lettering screen.
note: i recieve an indication on windows desktop that a device has been connected which is capable of USB high speed point
ADB COMMANDS WORKS: device is detected
Things I have tried:
I tried booting into a Ubuntu Live cd to see if I could format the sdcard, as suggested in this thread: (sorry, forum won't allow me to hyperlink, thread id=759910)
The disk utility picked up the Samsung drives (One was labeled something like Samsung_Galaxy, and the other Samsung_Galaxy sdcard, but I'm not 100%) but could not format them. There was also no info being listed about the size.
Things I would like to try / have hunches on:
Before all this happened, I made a Nandroid backup of the orriginal firmware, and copied it from the i9000's sdcard to my computer. I made the backup using Rom Manager's Clockworkmod.
Is there a way to use Odin to flash Clockworkmod, so I can restore this backup?
-everything out there says to use Rom Manager, which I can't access because the phone is pseudo dead.
Will the backup even still be on my sdcard?
Wait, my sdcard isn't mounted.. can we try mounting it with abd? (I tried, but am not sure of the command / path of how to do this..
Can abd be used to restore my backup stored on my computer? Is this dependent on the sdcard being mounted?
I fully appreaciate those you take the time to read through this as it is rather lengthy. I just want to ensure I have tried every means to revive the device, and hopefully some more skilled users can help with the mounting and adb syntax.
All comments and ideas are welcome and appreciated! Thank-you
Sorry to be the bearer of bad news. But time and time again this error has proven to be a hardware error. Mine did the same thing and samsung/bell had to replace the mainboard in my phone. Good luck, but unfortunately, anything you do further is a waste of time short of sending it back for repair.
Hi All:
My Sprint Tab P100 got some strange problems.
It's a second hand P100, Once i turn on the tab, it will warning with 3 Beebee, and nook & Amaza Mp3 & Market will report error.
Below warning will show up:
Amazon MP3_nook
“The application XXX has stopped unexpectedly, pls try again”
Market
"Attention:
An Error has occured, Please try again later."
After check, i found the original usr information still there.
(Gmail/Facebook account will try to sync with previous owner's ID. and i can not remove the account.)
What i have tried:
1) I have tried to WIPE using system recovery, after WIPE both data & Cache partition, issue still exist.
2) Perform the Samsung factory reset by enter *2767*3855# in the Memo, problem still there.
3)Format the SD card with Phone & Windows, still got problem
4) Flashed with the stock EA24 Rom from XDA(with Modem,using Odin), the problem still remain the same.
5)Flashed with DJ30, the problem still exist(Base/Fireware EA24).
6)Tried to install CWM, failed to boot up(Rooted before install CWM, after flash the Zimage to Kernal or recovery, some strings flush in the screen, then the tab hung at Samsung logo and reboot.)
I guess those problem was caused by some program information still remain in the internal storage, even after factory reset or flash with other ROM.
Can somebody help on this? Also prefer someone can help on how to install CWM
I am interesting that the OVERcome 2.01 Rom got a version to WIPE the internal storage, but the OVERcome rom are designed for GSMer. Can i tried to use it to clear my internal storage?
just installed Astro, the program will crashed when launch it
Can some one help on this topic?
I am suspecting my internal storage was locked to Non-Writable.
This might result CWM can not access the internal memory caused the failure of the installation.
Is it related to the Flash lock option in the Odin?
Check this thread..
http://forum.xda-developers.com/showthread.php?t=1133053
That has the stock files, and instructions to get root and CWM installed with the stock software. Using Odin to put the stock firmware (EA24) should wipe anything and everything off the tab and restore it to as if it were new out of the box. You also might want to wipe your sd card as it can cause issues with the CWM ext4 conversion.
Hi pvtjoker42 & All:
During the process of Kernel with CWM Recovery, i has been stopped @ step7
1) Download the zip file here
2) Unzip the file. You will need the file named zimage only.
3) Open Heimdall Frontend
4) Select Browse under Kernel and navigate to the file you downloaded in step 1 and select it
5) Press Start
6) The Tab will reboot, but will freeze on the Samsung logo. Turn it off and boot into recovery (Vol Up + Power)
~~~~~~~~~~~~~~~~~~~~
my tab failed here, no matter what you pressed, it doesn't go to CWM. Do u have any idea?
~~~~~~~~~~~~~~~~~~~~
7) CWM Recovery will attempt to back your tab up, but will fail. Don't fret.
8) Do a factory reset in CWM Recovery and reboot
9) You'll freeze on the Samsung logo again Turn it off and boot into recovery.
10) CWM Recovery will back your Tab up successfully.
11) You now have a CWM backup. Reboot.
12) Your auto rotate is broken.
13) Download the rotation file
14) Put it in /system/lib/hw and change the permissions to match the other items.
Can someone helps?
Today i tried 1 more things, Use a update.zip to update the tab from EA24 to EB28,before try this, i have tried OTA to EB28, it never success.
i download the update.zip from <forum.sdx-developers.com/index.php?PHPSESSID=99sdnmh5pm4rtuv39hk80f7du6&topic=13104.0;nowap> it seems to be official one, and the recovery is the stock version, but it failed again.
I start to believe that my internal storage has been locked, and data can not write in.
Is it possible to due to Fstab issue?
Pls helps to save my tab....
There is only one thing to do : return to stock. Carefully follow the guide. Don't do anything else to your tab, until you go through the restock steps :
http://forum.xda-developers.com/showthread.php?t=1133053
[SPRINT] Sprint Tablet Owners Thread (Root, ROM, Flash to stock, CWM Recovery)
The process reformats/repartitions your internal sd card, and sets the correct permissions. If this process fails, there is probably something wrong with the tab.
you might also try to select the option to repartition in Odin when going back to EA24. Then try the steps to get EB28 OTA update, and once you've got that up and running, you can try the update.zip to get to EF17 (gingerbread, as long as you don't need root)
I wouldn't. Try a different sd card
Sent from my Nexus S 4G using Tapatalk
Hi All:
Thanks for the advice.
I have tried to back to stock EA24 using odin, but the situation still ramain the same.
And it fail to OTA to EB28, the EB28 upgrade program will reboot the machine, and enter recovery model. but it will complete the program. also i have tried to put EB28 update.zip in the SD card, but also fail to upgrade to EB28.
I have repartition the phone by P100 serveral time using odin, also tried update Pit file. All failed.
I have format the SD card in Windows & then in Android, useless.
Now i have some clues:
In P1000 rom Roto-JME, there is Movinand.bin, this one got same name as the internal storage IC from samsung. i am thinking that file could be a file similar to partition table.
Can someone help to dump a "movinand.bin" for me from P100?
steps:
1)Get back to stock EA 24
2)Wipe Cache & factory data
3) Root it (Using superone click , you can find it here http://forum.xda-developers.com/showthread.php?t=803682)
4)Install terminal (i use better terminal) or using a ADB to connect to shell.
5)Type "su", check whether "$" change to "#" in the shell
6) Type “dd if=/dev/block/mmcblk0p2 of=/sdcard/movinand.bin bs=4096”
7) Find the Movinand.bin in the SD card
You can sent it to me by drop a email to [email protected]
If there is anything wrong, pls help to correct me
Thanks in advance
as some people is asking how did i fix the issue, just publish the information here.
I fixed the issue by replaced the internal storage (the chip), cost about US$ 30(RMB 200)
If anyone have better solution, just post here to share
Hey,
A friend gave me his Galaxy S after another friend of him got it into this following state (I'm not sure what exactly he did or tried to do):
The phone is stuck in a boot loop, sometimes it shows the first frame of the boot animation for a second before booting again. When I start it in recovery mode (Android System Recovery (3e)) I get this error messages:
Code:
-- Copying media files...
E:failed to mount /sdcard (File exists)
E:copy_dbdata_media:can't mount /sdcard
your storage not prepared yet. please use UI menu
for format and reboot actions
The phone does not have an SD card in it.
After reflashing with the same firmware as original, I get these errors:
Code:
-- Copying media files...
E:failed to mount /sdcard (File exists)
E:copy_dbdata_media:can't mount /sdcard
your storage not prepared yet. please use UI menu
for format and reboot actions
meida files copy failed.
-- Wiping data...
Formatting /data...
E:format_volume: rfs format failed on /dev/block/mmcblk0p2
Formatting /dbdata...
Formatting /cache...
Deleting Meta Data
Data wipe failed.
I've tried flashing different firmwares too, including rooted ones, and the results were the same except for a case where the first error was about not being about to mount mmcblk0p1 instead of sdcard, and another case where another firmware cause the phone to appear to boot, but after a minute or too it got stuck on a black screen and stopped responding.
I followed many different guides on how to fix similar problems, but none of them actually worked.
Please help, thanks a loooot in advance.
http://forum.xda-developers.com/showthread.php?t=1134975
Maybe it will help?
Thanks for the reply. Solutions 1-3 are irrelevant, as I can get into download mode, but even after flashing, any version, the problem is still there. I tried solution 4 (dbdata flash), but it doesn't solve anything. Are there any other partitions I can flash and might be able to solve this?
Ok, next thread
http://forum.xda-developers.com/showthread.php?t=1069867
Maybe here is solution?
Tried flashing the files there and no luck, still the same error. =/
I sent Faria, who said he has tools for solving this problem in that topic a PM, hopefully he'll share his tools with the community.
Meanwhile, I don't mind trying different solutions.
I also noticed something – if I keep the phone in the boot loop for a long time, it will eventually get to either a loop of the carrier boot animation (Which normally doesn't loop), or actually boot for one time. (When it booted I tried to power it off and see if it would boot again normally, and it didn't =/)
i have this kind of error few months ago, what i do was, flash pit file only with repartition, then flash pda, phone & csc.... agn flash this dbdata.rfs file, should fix the issue.
Just tried it, no luck, exactly the same error as before. =/
ops... sorry to heard that, at least it work for me but too bad not for u.....
I have the exact same error message and problem . Really hope someone can find a fix for this because I've spent hours and hours
Yep, EXACTLY same problem as OP and NO fixes for me yet. Tried everything from this thread and other threads. Let's see who's the real king of knowledge who can fix this.
any luck with this issue?
In my case it was solved by Click, but as in thread: for some people it works with repartition, while for some - without.
Or, try it Here I'd pay attention to page 2, Darky's resurrection... maybe looking for newer version at Darkyrom.
spamtrash said:
In my case it was solved by Click, but as in thread: for some people it works with repartition, while for some - without.
Or, try it Here I'd pay attention to page 2, Darky's resurrection... maybe looking for newer version at Darkyrom.
Click to expand...
Click to collapse
thank you spamtrash.
i tried all this various methods. i was able to boot into android but after reboot, it never got into android anymore. stuck in boot loops. ill try Darky's resurrection now, its the last option i havent tried yet. i cant believe there are no scripts or smth to fix and rebuild file system in such cases.
ambrozic said:
thank you spamtrash.
i tried all this various methods. i was able to boot into android but after reboot, it never got into android anymore. stuck in boot loops. ill try Darky's resurrection now, its the last option i havent tried yet. i cant believe there are no scripts or smth to fix and rebuild file system in such cases.
Click to expand...
Click to collapse
Any Luck????????
I'd be interested with results as well. As last hope, you can try http://forum.xda-developers.com/showthread.php?t=1330491 this one, but it requires hardware mod...
Sent from tam-tam drum
any update or fix?
Someone found any fix for this?
Yep!
Hi guys!
Yep - probably I found the solution. One month ago I have bought i9000 with this problem (as broken). Finally I managed to start that SGS and even install ICS on it. The problem is (as I suppose) that internal flash memory is broken and You have to move /data partition to external SD card. So some flashes, some changes in files and repartitioning of SD card does the thing.
Currenty I am in the middle of preparing a tutorial to be pushed on YT to show how I managed to solve the problem. Stay tuned
Best regards
this is a hope.. =)=)=) please send me a tutorial. thanks
Ready
So.
Finally I had some time to add voice recording to my movie and volia - is ready.
I hope it will help at least somehow.
I am not sure if this manual will help in Your case(s), but it might be at least a hint
Best regards
Fteller.
^ So, umm, where's the link for your YT video? Thanks.
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?
I managed to get my phone into a state where I can only go to download mode or CWM manager (no OS). This is how it happened:
- Installed latest cyanogenmod (9.1) on my Samsung Galaxy S (international version, unlocked).
- New version worked fine!
- Found out I was missing some data so I went back to CWM recovery and did a "backup and restore" > "Restore ALL (Be careful)"
- Restoring old ROM did not work ... decided to go back to cm91
- When I try to reinstall cm91 via CWM I get the following:
Code:
assert failed: getprop("ro.product.device") == "galaxys" || getprop("ro.build.product") == "galaxys" || ... [more similar statements]
E: Error in /mnt/sdcard/cm-9.1.0-galaxysmtd.zip
(Status 7)
Installation aborted
Seems like the "Restore ALL" step messed up with something fundamental... does anyone have a clue in what direction I can go to resolve this? I have been searching frantically for answers but usually a "status 7" is a result from an outdated cwm or such (NOTE: I did manage to successfully install... and ICS was running very well before I did the restore and things went bad)
Seems to me that the ro.product.device property(or/and other properties) from the device has been altered in the restoration process.
- Does anyone know how I can see which value it has? (I can currently only use the CWM manager)
- Can anyone point me in a direction where I could go next to fix the situation?
Any help very much appreciated
gardarh said:
I managed to get my phone into a state where I can only go to download mode or CWM manager (no OS). This is how it happened:
- Installed latest cyanogenmod (9.1) on my Samsung Galaxy S (international version, unlocked).
- New version worked fine!
- Found out I was missing some data so I went back to CWM recovery and did a "backup and restore" > "Restore ALL (Be careful)"
- Restoring old ROM did not work ... decided to go back to cm91
- When I try to reinstall cm91 via CWM I get the following:
Code:
assert failed: getprop("ro.product.device") == "galaxys" || getprop("ro.build.product") == "galaxys" || ... [more similar statements]
E: Error in /mnt/sdcard/cm-9.1.0-galaxysmtd.zip
(Status 7)
Installation aborted
Seems like the "Restore ALL" step messed up with something fundamental... does anyone have a clue in what direction I can go to resolve this? I have been searching frantically for answers but usually a "status 7" is a result from an outdated cwm or such (NOTE: I did manage to successfully install... and ICS was running very well before I did the restore and things went bad)
Seems to me that the ro.product.device property(or/and other properties) from the device has been altered in the restoration process.
- Does anyone know how I can see which value it has? (I can currently only use the CWM manager)
- Can anyone point me in a direction where I could go next to fix the situation?
Any help very much appreciated
Click to expand...
Click to collapse
I just thinking - why not go back to GB and start fresh again or give a try to install Jellybean
erpurohit said:
I just thinking - why not go back to GB and start fresh again or give a try to install Jellybean
Click to expand...
Click to collapse
Thanks for the reply!
Regarding JB, I'd rather want a stable cm build as this is my dad's phone and I'd rather not set him up with something branded as experimental (yes, I bricked my dad's phone ). Regarding GB, I'll give it a try but I'm wondering if the cm installation for GB doesn't have the same assert checks as the installation for ICS...rendering me in the same mess (I don't have the device with me right now but I'll try later today).
Is there a way to get the Samsung stock ROM somewhere?
- That way I'd at least have known a way out of this mess.
Also, I'd like to know WHY this is happening, as I'm curious about where these values are stored and how one changes them.
erpurohit said:
I just thinking - why not go back to GB and start fresh again or give a try to install Jellybean
Click to expand...
Click to collapse
Tried cm10, same error (as I expected). I edited the install script, removing the assert line. This only makes the device go unresponsive on install. I can't mount the system partition (or any other partitions for that matter)... the device appears fubar. Gonna try to use odin to install some stock rom I found. Not very optimistic though.
Any ideas for a fubar phone? Is the only remaining option to use it as a paper press?
gardarh said:
Any ideas for a fubar phone? Is the only remaining option to use it as a paper press?
Click to expand...
Click to collapse
From what you have written, it looks like you restored the old system on a new system setup, thus your CWM will give you status 7 when you try to use it for upgrade . look at status 7 errors in My Android solutions .
All you may had to do was flash the correct semaphore kernel to get back correct CWM and also check your IMEI or like erpurohit said, start from the beginning.
you can get a rescue kit from My Android Collections and or a solution from My Android Solutions Need a guide, look into My Guides and Manuals
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power
button for a minute, than powerup without SIM and Ext.SD Card, after flashing and reboot , insert them back
Tips before Flashing:-
Backup all your important files, contacts, SMS, game data, images etc to PC or
Ext SD card. or make Nanadroid Backup If you have CWM
Backup your EFS Folder to PC or Ext SD card
Enable USB Debugging on Phone. Touch menu> Settings> Applications> Development>
Charge your battery to more than 50% before you attempt any sort of flashing.
Disable Samsung KIES when using Odin. Kill Kies.exe, KiesTrayAgent.exe, &
KiesPDLR.exe using Task Manager on PC
Use only ROM and solution for your model and Wipe x3
xsenman said:
From what you have written, it looks like you restored the old system on a new system setup, thus your CWM will give you status 7 when you try to use it for upgrade . look at status 7 errors in My Android solutions .
All you may had to do was flash the correct semaphore kernel to get back correct CWM and also check your IMEI or like erpurohit said, start from the beginning.
you can get a rescue kit from My Android Collections and or a solution from My Android Solutions Need a guide, look into My Guides and Manuals
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power
button for a minute, than powerup without SIM and Ext.SD Card, after flashing and reboot , insert them back
Tips before Flashing:-
Backup all your important files, contacts, SMS, game data, images etc to PC or
Ext SD card. or make Nanadroid Backup If you have CWM
Backup your EFS Folder to PC or Ext SD card
Enable USB Debugging on Phone. Touch menu> Settings> Applications> Development>
Charge your battery to more than 50% before you attempt any sort of flashing.
Disable Samsung KIES when using Odin. Kill Kies.exe, KiesTrayAgent.exe, &
KiesPDLR.exe using Task Manager on PC
Use only ROM and solution for your model and Wipe x3
Click to expand...
Click to collapse
Hey xsenman,
I think I actually already stumbled upon your posts, I believe I did a PIT restore with the 512 pit and Odin just hung (for an hour or so) before I unplugged. This aggravated my situation (I realized through this whole process that there are multiple levels of fu*ked when rooting).
I finally found a way out of this mess just an hour ago by following this post: http://forum.xda-developers.com/showthread.php?t=1102881 . I reinstalled the stock ROM and then installed cm91 again and now the device is working fine. Odin did hang on me once again when I followed those instructions but I tried again, using the 803 pit file and then it finally worked (don't know if it was a coincidence).
So the state I was describing before was that the partition table was corrupted. From there nothing works (obviously).
Thanks for taking the time to help me out! I have to say I wasn't very optimistic there for a while...
Cheers,
Gardar
Noob with a similar problem
Hi Gardar, hi xsenman,
I stumbled upon this thread by googling the same error message that Gardar initially posted (The error code 7 on attemping to flash CM 9.1).
Unfortunately, being a somewhat naive noob, I feel I am not proficient/confident enough to try the solution that Gardar found for himself just yet.
My problem is that by some dumb attempt to restore to the original GingerBread 2.3.3 after initially successfully installing CM9.1 and then some time later facing some problems concerning the phone not recognizing the SIM card anymore (it said "no service" and couldn't scan for networks and wouldn't ask for the PIN after rebooting the phone), I now seem to have completely messed up the phone's system. The phone won't boot and when I try to flash it to CM9.1 again from CWMR, it aborts, giving me the code 7 error message that Gardar posted.
I was browsing through the forums here, following the links given in this thread, trying to find some answers by myself and stumbled upon this:
" Problem:- ClockworkMod Recovery giving Status 7 error "Installation aborted".
Solution:- One or some of the prerequisite requirement for the needed upgrade is missing or corrupted . So you may need to identify and
replace that requirement for the installation to continue. Most likely could be due to wrong bootloader, wrong CWM, Wrong IMEI, Wrong
Radio etc "
in xsenman's "Android Solutions for Galaxy Phones" thread
( http://forum.xda-developers.com/showthread.php?p=30415128#post30415128 )
This seems applicable but I have no idea what to make of it. I am really lost now, so some dumbed down step-by-step guide of what to do now would be really appreciated.
A quick sum up of what state my SGS i9000 is in right now:
- The phone doesn't boot into operating system (gets stuck on the first Samsung Galaxy S logo screen)
- I can start download mode
- I can access CWM Recovery (v2.5.1.0 SpeedMod Kernel)
- through that I can mount the usb storage to connect it to my Windows PC and access the internal SD card
that is (from my noobish point of view) about all i can do.
What backup I have available:
- NANDroid backup from earlier this day, including
- cache.img (23 KB)
- data.img (51,503 KB)
- dbdata.img (17,016 KB)
- nandroid.md5 checksum file (1 KB)
%note: from what I read somewhere (and tried out), this backup seems useless for recovering to the stock android, because the sys.img is missing. Am I right about that?
- unfortunately, I have NO "EFS"-folder backup. Yes, xsenman will hate me but I can't help it now :'(
%note: I think this might be relevant concerning my phone not getting service and not asking for the PIN after booting.
A chronologic/structured sum up of how I got into this mess and when which problems arose
- I started out with the original GingerBread 2.3.3 (Phone was working fine)
- following this guide step by step ( http://wiki.cyanogenmod.org/wiki/Samsung_Galaxy_S:_Full_Update_Guide ) and using the files linked there, I
- successfully flashed the SpeedMod Kernel and ClockWorkMod to get root access using Heimdall
- successfully installed CM 9.1 via CWM Recovery (from internal SD)
- now the phone worked fine with CM 9.1
BUT
- GPS wasn't working and I didn't have FM radio
- so I got myself the JP5 radio zip from here (http://wiki.cyanogenmod.org/wiki/Samsung_Galaxy_S:_Support_Downloads)
and a GPS fix from here (http://www.android-hilfe.de/root-hacking-modding-fuer-samsung-galaxy-s/250698-fix-gps-fix.html)
- and installed them both at the same time via CWM Recoevry the same way I did with the CM 9.1 zip file
This was probably the first big mistake I made, because
- now I had GPS working again, but from now on
- the phone wouldn't ask for the PIN after booting
- I didn't have service anymore
- the phone failed to scan for networks
- but it wasn't showing the "no sim card" icon in the task bar
I tried rebooting the phone and when that didn't help I started messing around in CWMR
- wipe data/factory reset
- wipe cache partition
- wipe Dalvik cache
When that didn't help either, I
- tried to re-install cm9.1, getting the abort with code 7 error
- then tried to recover the original rom from my backup folder
- that looked promising in CWM as it didn't abort like cm9.1, but when rebooting once it was done in CWM the phone got stuck on the logo screen immediately and won't boot since.
- I retried wiping user data and caches and installing cm9.1, to no effect.
Then I started digging into the forums here and elsewhere but couldn't find specific advice aseful to me in this situation.
Now I'm sitting here with my fubar phone and don't know what to do next -_- crying for help
Please excuse this wall of text, I tried to give as much useful info un my problems as possible.
Any help is greatly appreciated.
Cheers,
Jules
JulesBell said:
Any help is greatly appreciated.
Click to expand...
Click to collapse
you keep mentioning 2.3.3 as your base, as such I am assuming you have an i9000M ...so confirm what is your phone model as upgrade ROMS will vary .
The easiest way to solve this is to start from the beginning ( assuming you have moved all your important files to your PC) If not just mount USB storage using CWM and copy your entire Internal SD card to PC...for salvaging later and you can format your Internal SD card and partitions without worries to start afresh.
First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card, after flashing and reboot , insert them back
Tips before Flashing:-
Backup all your important files, contacts, SMS, game data, images etc to PC or Ext SD card. or make Nanadroid Backup If you have CWM
Backup your EFS Folder to PC or Ext SD card
Enable USB Debugging on Phone. Touch menu> Settings> Applications> Development>
Charge your battery to more than 50% before you attempt any sort of flashing.
Disable Samsung KIES when using Odin. Kill Kies.exe, KiesTrayAgent.exe, & KiesPDLR.exe using Task Manager on PC
Use only ROM and solution for your model and Wipe x3
1) you can download an upgrade ROM, JVU for i9000 or UJKG3 for i9000M or even a rescue kit, which ever suits you and flash back to stock 2.3.6 for i9000 or 2,3.3 for i9000M from My Android Collections
2) After this you can root and get CWM by flashing a semaphore GB kernel for i9000 or UGKG3 root + CWM for i9000M
3) here is where you make an EFS backup to keep for life in your PC
4) after this you can flash the CM 9.1, you can either follow the developers guide or chose one from My Guides and Manuals
Sounds like you're not more of a noob than I am
From what I learned from my battle the assert(...) failures indicate that that the device type cannot be read anymore which in turn indicates that the filesystem storing that information is corrupted (and/or the partition table defining your filesystem). Btw. if you extract the .zip file containing the cm mod and do a "grep -r assert" you can find the installation script (don't remember exactly where it's located right now). It's not very helpful but informative...
The filesystem mess can be fixed with flashing a new pit file (I recommend this post on pit files which seems to be a phenomena specific to Samsung phones), then installing one of the stock ROMs in the post I linked and finally reinstalling CM (which I believe repartitions your internal sdcard again). I think you want to do both the PIT and the stock ROM in the same go with Odin. Of course this is pretty much the same as I said in the post above and therefore probably isn't helpful to you, but it worked for me
Good luck!
JulesBell said:
Hi Gardar, hi xsenman,
I stumbled upon this thread by googling the same error message that Gardar initially posted (The error code 7 on attemping to flash CM 9.1).
Unfortunately, being a somewhat naive noob, I feel I am not proficient/confident enough to try the solution that Gardar found for himself just yet.
My problem is that by some dumb attempt to restore to the original GingerBread 2.3.3 after initially successfully installing CM9.1 and then some time later facing some problems concerning the phone not recognizing the SIM card anymore (it said "no service" and couldn't scan for networks and wouldn't ask for the PIN after rebooting the phone), I now seem to have completely messed up the phone's system. The phone won't boot and when I try to flash it to CM9.1 again from CWMR, it aborts, giving me the code 7 error message that Gardar posted.
I was browsing through the forums here, following the links given in this thread, trying to find some answers by myself and stumbled upon this:
" Problem:- ClockworkMod Recovery giving Status 7 error "Installation aborted".
Solution:- One or some of the prerequisite requirement for the needed upgrade is missing or corrupted . So you may need to identify and
replace that requirement for the installation to continue. Most likely could be due to wrong bootloader, wrong CWM, Wrong IMEI, Wrong
Radio etc "
in xsenman's "Android Solutions for Galaxy Phones" thread
( http://forum.xda-developers.com/showthread.php?p=30415128#post30415128 )
This seems applicable but I have no idea what to make of it. I am really lost now, so some dumbed down step-by-step guide of what to do now would be really appreciated.
A quick sum up of what state my SGS i9000 is in right now:
- The phone doesn't boot into operating system (gets stuck on the first Samsung Galaxy S logo screen)
- I can start download mode
- I can access CWM Recovery (v2.5.1.0 SpeedMod Kernel)
- through that I can mount the usb storage to connect it to my Windows PC and access the internal SD card
that is (from my noobish point of view) about all i can do.
What backup I have available:
- NANDroid backup from earlier this day, including
- cache.img (23 KB)
- data.img (51,503 KB)
- dbdata.img (17,016 KB)
- nandroid.md5 checksum file (1 KB)
%note: from what I read somewhere (and tried out), this backup seems useless for recovering to the stock android, because the sys.img is missing. Am I right about that?
- unfortunately, I have NO "EFS"-folder backup. Yes, xsenman will hate me but I can't help it now :'(
%note: I think this might be relevant concerning my phone not getting service and not asking for the PIN after booting.
A chronologic/structured sum up of how I got into this mess and when which problems arose
- I started out with the original GingerBread 2.3.3 (Phone was working fine)
- following this guide step by step ( http://wiki.cyanogenmod.org/wiki/Samsung_Galaxy_S:_Full_Update_Guide ) and using the files linked there, I
- successfully flashed the SpeedMod Kernel and ClockWorkMod to get root access using Heimdall
- successfully installed CM 9.1 via CWM Recovery (from internal SD)
- now the phone worked fine with CM 9.1
BUT
- GPS wasn't working and I didn't have FM radio
- so I got myself the JP5 radio zip from here (http://wiki.cyanogenmod.org/wiki/Samsung_Galaxy_S:_Support_Downloads)
and a GPS fix from here (http://www.android-hilfe.de/root-hacking-modding-fuer-samsung-galaxy-s/250698-fix-gps-fix.html)
- and installed them both at the same time via CWM Recoevry the same way I did with the CM 9.1 zip file
This was probably the first big mistake I made, because
- now I had GPS working again, but from now on
- the phone wouldn't ask for the PIN after booting
- I didn't have service anymore
- the phone failed to scan for networks
- but it wasn't showing the "no sim card" icon in the task bar
I tried rebooting the phone and when that didn't help I started messing around in CWMR
- wipe data/factory reset
- wipe cache partition
- wipe Dalvik cache
When that didn't help either, I
- tried to re-install cm9.1, getting the abort with code 7 error
- then tried to recover the original rom from my backup folder
- that looked promising in CWM as it didn't abort like cm9.1, but when rebooting once it was done in CWM the phone got stuck on the logo screen immediately and won't boot since.
- I retried wiping user data and caches and installing cm9.1, to no effect.
Then I started digging into the forums here and elsewhere but couldn't find specific advice aseful to me in this situation.
Now I'm sitting here with my fubar phone and don't know what to do next -_- crying for help
Please excuse this wall of text, I tried to give as much useful info un my problems as possible.
Any help is greatly appreciated.
Cheers,
Jules
Click to expand...
Click to collapse
-
xsenman said:
you keep mentioning 2.3.3 as your base, as such I am assuming you have an i9000M ...so confirm what is your phone model as upgrade ROMS will vary .
The easiest way to solve this is to start from the beginning ( assuming you have moved all your important files to your PC) If not just mount USB storage using CWM and copy your entire Internal SD card to PC...for salvaging later and you can format your Internal SD card and partitions without worries to start afresh.
First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card, after flashing and reboot , insert them back
Tips before Flashing:-
Backup all your important files, contacts, SMS, game data, images etc to PC or Ext SD card. or make Nanadroid Backup If you have CWM
Backup your EFS Folder to PC or Ext SD card
Enable USB Debugging on Phone. Touch menu> Settings> Applications> Development>
Charge your battery to more than 50% before you attempt any sort of flashing.
Disable Samsung KIES when using Odin. Kill Kies.exe, KiesTrayAgent.exe, & KiesPDLR.exe using Task Manager on PC
Use only ROM and solution for your model and Wipe x3
1) you can download an upgrade ROM, JVU for i9000 or UJKG3 for i9000M or even a rescue kit, which ever suits you and flash back to stock 2.3.6 for i9000 or 2,3.3 for i9000M from My Android Collections
2) After this you can root and get CWM by flashing a semaphore GB kernel for i9000 or UGKG3 root + CWM for i9000M
3) here is where you make an EFS backup to keep for life in your PC
4) after this you can flash the CM 9.1, you can either follow the developers guide or chose one from My Guides and Manuals
Click to expand...
Click to collapse
Hey again, xsenman and gardarh,
thanks a lot for the quick replies.
I want to go and try to follow the directions you guys gave me, but first of all some additional info and corrections that I forgot or stated wrong after a long night of browsing this and other forums and desperately trying to get my phone working again.
- regarding the model and original firmware: I'm pretty sure it's just the plain sgs gt-i9000 (without the "M"). The latter version seems to be specific for the Canadian/North American market, and my phone (like me ) is from Germany. Also, in the phone status info menu it just said "i9000" when the phone was still working. And I may have been mistaken about the version number 2.3.3, it might as well have been 2.3.6.
I only recently (this week) bought this phone used from a friend. I'm not sure which firmware version the phone was originally shipped with, but since my friend is not a tech geek, I think it is safe to assume she only installed SAMSUNG-official updates.
- then, I think THIS IS IMPORTANT, I think the EFS files may have been corrupted and the IMEI may have been lost when flashing the radio module and the GPS fix, which I guess may have caused the phone to lose network service and not be able to scan for networks.
Will this be miraculously restored when flashing to stock 2.3.6 from an original ROM or do I need to extract the IMEI some way BEFORE I go ahead and re-partition the internal SD card?
- do I need to re-partition anyways? I tried to mount "/system" in CWM and it failed.
- also, I forgot to mention that after the failes recovery from my backup, I couldn't even get to CWM Recovery anymore. I flashed the hardcore kernel onto the phone again via USB using Heimdall, so now I can access CWMR again.
Thanks a lot!
Cheers
Jules
---------- Post added at 04:20 PM ---------- Previous post was at 03:35 PM ----------
I just discovered that there seems to be a backup of my EFS folder after all, which was created at the same time as the nandroid backup. I copied the backed-up "efs" folder to the root directory as well as my PC just to be sure. Copying the folder to root doesn't seem to have any effect on the bootability of my phone though.
However, finding this backup gives me some confidence regarding acomplete reset to stock with an original ROM and PIT-file, so I'll go for that now and update you on the results.
Cheers,
Jules
phone restored
Thanks a lot guys, with your help I was able to restore my phone to a stock GB 2.3.6, using
i9000 Rescue Rescue Kit for i9000 using heimdall packed by ldq
Right now I m just happy it's working again and not in the mood to flash to cm9.1 again, fearing i might hit the problems with GPS and fm radio not functioning again... any suggestions?
Best wishes
Jules
In my limited experience, if you cannot mount /system your filesystem is probably corrupted (at least that was the conclusion I came to).
You should not be worried about which android version the device was running (e.g. 2.3.3) but you do have to be careful about choosing which region the firmware was designed for. See if you can find your device type here:
http://www.sammobile.com/firmware/?page=3
Take note of the code under the PDA column.
The download from that site didn't help me though, but should hopefully help you in finding the correct stock firmware (from my link above).
Chainfire posted some info about stock rom names (See http://forum.xda-developers.com/showthread.php?t=1103399 undir the section "Help! Which file do I use ?". It's for Galaxy S2 but I believe the idea behing the naming is mostly the same.
problem solved
Hey gardarh,
thanks for your reply. I got the phone working again by completely resetting it to a stock 2.3.6 gingerbread firmware, using a rescue kit. What in detail was wrong, I wil never know
salival eedfie
JulesBell said:
Hey gardarh,
thanks for your reply. I got the phone working again by completely resetting it to a stock 2.3.6 gingerbread firmware, using a rescue kit. What in detail was wrong, I wil never know
Click to expand...
Click to collapse
Good to hear! Which rescue kit (for future reference)?
abc
gardarh said:
Good to hear! Which rescue kit (for future reference)?
Click to expand...
Click to collapse
>>> i9000 Rescue Rescue Kit for i9000 using heimdall packed by ldq <<<
from xsenman's list.
Cheers,
Jules