Related
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
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...!!!
I have an N7000 with stock gb and stock KK2 kernel.
I followed these instructions from Dr. Ketans to root my galaxy note n7000: http://forum.xda-developers.com/showthread.php?t=1329360
Then I verified that it was indeed routed by downloading an app the claimed to check this. All seems ok so far.
Then I downloaded paranoid_note_v04a.zip & gapps-ics-20120511-fixed.zip
I'm pretty sure my download was ok since they will extract without errors.
Then I copied these two files to the note - in the DCIM folder (for lack of a better place to put it). I had to turn off usb debugging first, otherwise I couldn't do the copy of these two files.
Then I turned usb debugging back on again
Then I held the 3 buttons, got into "Android system recovery (3e)" and tried to flash the PA 04a. I quickly get the following error: E:signature verification failed
Do you know what I have done wrong?
I have a sneaking suspicion it's because I don't have something called CWM (although the routing instructions I was following never said I needed it).
If that's the answer, now that I'm routed what is the easiest way to get it.
Thanks
~Paul
if you have rooted your gn then download the cwm recovery in the link and put it in your external sd card go into your stock recovery (holding volume up + home + power buton) from there choose the second option i.e. apply update from sd card and navigate to where you have placed the downloaded cwm recovery and open it now you will be able to use cwm recovery and flash any rom without any error
http://forum.xda-developers.com/attachment.php?attachmentid=1056408&d=1336826886
As above you need cwm recovery to install paranoid.
Sent from my GT-N7000 using xda premium
Hello,
I tried installing a custom ROM on my 7310 and it had issues. I have tried installing the original ICS from the sammyfirmware site using ODIN. Now I have a boot loop. I think I need to repartition, but when I click the repartition checkbox in ODIN I get an error.
Do I need to repartition? If so, how do I do it? If not, how do I fix this error?
Thanks.
A few questions:
spazlon said:
I tried installing a custom ROM on my 7310 and it had issues.
Click to expand...
Click to collapse
What did you try to flash and how did you try doing it (CWM, ODIN, ...)?
What 'issues'?
I have tried installing the original ICS from the sammyfirmware site using ODIN. Now I have a boot loop.
Click to expand...
Click to collapse
How far into the boot sequence does it get?
Are you able to get into recovery?
If so, what recovery do you have (Stock vs CWM)?
Have you tried seeing what is causing the boot-loop using adb?
Do I need to repartition? If so, how do I do it? If not, how do I fix this error?
Click to expand...
Click to collapse
This is an action of last resort. Exhaust all other avenues first.
boscorama said:
What did you try to flash and how did you try doing it (CWM, ODIN, ...)?
What 'issues'?
Click to expand...
Click to collapse
I used CWM to flash AOSP 4.1.2. It seemed to work fine for a day or two, but then it needed charging (as normal). I let it charge over night and in the morning it had less battery. I figured the charger or cable were flaky so I tried another set on another outlet and same thing. Then it finally ran out of battery. I let it charge again over night and when I tried to turn it on it was really slow. The boot animation was only 1 frame every couple seconds. It would eventually boot all the way up, but it was still REALLY slow. So I went into CWM and reflashed the same ROM. Then I got a boot loop of the boot animation. I couldn't get into CWM any more, so then I went into download mode and flashed the official firmware and flashed it with ODIN.
boscorama said:
How far into the boot sequence does it get?
Click to expand...
Click to collapse
Now when I turn it on it just says, "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I can flash again with ODIN and it will get to the Samsung boot animation and just pulse SAMSUNG.
boscorama said:
Are you able to get into recovery?
If so, what recovery do you have (Stock vs CWM)?
Click to expand...
Click to collapse
If I hold power and volume down I can get into download mode or Samsung recovery, not CWM, and power with volume up doesn't do anything.
boscorama said:
Have you tried seeing what is causing the boot-loop using adb?
Click to expand...
Click to collapse
I don't know anything about adb and I'm not sure what I would be looking for. Is there a tutorial I can follow somewhere?
Thanks for any help!
This worked for me with similar problem
Hi Spazlon,
Sorry I'm not allowed to post links yet as I am also very fresh. But I've underlined the addresses so you should be able to find them
I just spent the best of 2 days trying to solve a similar issue - my 8.9 P7300 kept running in boot loop. It had been running ICS stable for several weeks, then suddenly started to loop boot for no good reason. Anyway - you need two programs installed on your computer as well as USB drivers for your tablet. The two programs are Odin and SDK developer package. Odin3 v 1,87 and 1.85 are found here: filecrop.com/Odin-1.87 - try some of the links, one of them should work without having to type a password. The SDK is found here: developer.android.com/sdk You can find more about how to use the developer package on that site as well, but I installed as support for Android 2.1 through to 4.1
Also install the USB driver files for your tablet on your PC. For example from here: xpdrivers.com/usb/_1_24.cfm?gclid=CL2iDs7MCFWF7cAodxFYANQ
You also need the following recovery files which you can find by searching the developer forum for galaxy tab 8.9:
ClockworkMod_Recovery_v5.5.0.4.tar
P73xx_Stock_Recovery.tar
Clockwork_Recovery_6.0.0.8_GT-P7300.zip
and finally a ROM of your choice, for example the ICS rom cm-9-20121028-NIGHTLY-p5.zip that I just used. You can find the latest official ICS ROM's here get.cm/?device=p5
Now - hold down the volume down button on one of the boot cycles. You should now get into a menu with two choices - Download and Recovery. Default is "Download" - if you press volume down you switch between the two choices. Press volume up to select the choice you want.
First you want to select the "Download" option. Then connect your tablet to your PC. The drivers should now install and your tablet should read that you are connected.
Now start Odin3. Click the PDA button and select your P73xx_Stock_Recovery.tar file. Then press Start.
Once finished the tablet will reboot, and you now need to once again get into the recovery menu. Now select the recovery option, not the download menu. You get into the stock recovery menu where you navigate with the volume buttons and select choices with the power button. Do a full factory reset and wipe the cache. WARNING - you will loose ALL your data, but it'either that or stick to a bricked tablet so.... You will also loose your root access,m which is why the next step is needed.
Now that everything is wiped clean you can use Odin again in "download mode" to install ClockworkMod_Recovery_v5.5.0.4.tar with the same procedure as before. You now have root access.
Reboot again and once again into the recovery mode (not download mode). Once you get into the CWM recovery menu you are ready for the final step, which is to install your new operating system.
Go to your SDK installation folder and find the folder named "platform-tools".
First you want to copy two files into this folder (provided you want to install Cynaogen Mod 9):
Clockwork_Recovery_6.0.0.8_GT-P7300.zip
and
Your ROM file of choice
Press shift and right-click in that folder and select "Open command window here". In the command prompt write
adb shell
Note - I had some problems here which was caused by lack of permissions. On your tablet in the CWM menu there should be a choice under the advanced menu for fixing permissions. Use that and you should be able to get into the terminal shell afterwards with the adb shell command
Now write the following command sequence:
• mount /data (don't worry if you get an error message - it means the folder is already mounted)
• cd /data
• mkdir media (if you get an error message saying the folder already exists, that's also OK!)
• exit
• adb push Clockwork_Recovery_6.0.0.8_GT-P7300.zip /data/media
Now you may have to wait a little while until your command prompt is back confirming that the file was uploaded.
Now on your tablet go to the menu point "install zip from sdcard" and find your CWM file that you just uploaded and run that.
Reboot once again into the "recovery mode" - we are now nearly finished.
Run the above push command again from the computer terminal window, this time to upload the ROM file you want to install. (the command is adb push [filename].zip /data/media)
Now on your CWM recovery menu once again run the zip file you just uploaded from the "install zip from sdcard" menu
When completed and you now reboot you should have a completely fresh android installation. Hope this helps.
Remember to mark this thread with solved if it works!
Thanks to kallt_kaffe and all the others who helped me through their various posts (hope that coffee isn't getting too cold again), as well as the following web sites that indirectly helped me resolve this issue googleymind.com/2011/11/guide-so-you-think-you-bricked-your.html#.UJUNN8XAd8G and galaxytabhacks.com/galaxy-tab-10-1-hacks/how-to-root-galaxy-tab-10-1-the-easy-way/
Good luck.
Thanks! I'll give this a try when I get home. I'll let you know how it works out.
Don't ever try to 'repartion unless you really know what you're doing. You're soft bricked. Repartion and you'll hard brick.
I'd go back and get hc from sammobile and flash that with Odin. Ics has had some problems.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
jd1639 said:
Don't ever try to 'repartion unless you really know what you're doing. You're soft bricked. Repartion and you'll hard brick.
I'd go back and get hc from sammobile and flash that with Odin. Ics has had some problems.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Agreed - my procedure avoids manual repartitioning - I tried lots of other procedures but none worked. I think my data partition had become corrupt because I kept getting error messages. My first try was to recover with my cwm recovery file I made originally but I kept getting back to the boot loop .
spazlon said:
Hello,
I tried installing a custom ROM on my 7310 and it had issues. I have tried installing the original ICS from the sammyfirmware site using ODIN. Now I have a boot loop. I think I need to repartition, but when I click the repartition checkbox in ODIN I get an error.
Do I need to repartition? If so, how do I do it? If not, how do I fix this error?
Thanks.
Click to expand...
Click to collapse
I always got something like that ...
After bootloop just go to recrovery mode then factory riset ... its 100% WORK
Sent from my GT-P7300 using xda premium
I followed the steps outlined by mobjunky and was able to get an official Honeycomb ROM installed, boot the official and copy my custom ROM and CWM 6.0.0.8 on it. Then install CWM 5.4.0.4 followed by 6.0.0.8.
Now my problem is that any custom ROM I put on there just does a boot screen loop. I tried CM10 and the latest AOSP. To install the ROMs I just booted into CWM, installed the ROM from zip, then installed the gapps. I've tried with and without formatting the cache, user data, and Dalkiv, same results.
What am I doing wrong? I have loaded tons of ROMs on this before without any issues, then all of a sudden I can't get anything except official loaded.
spazlon said:
I followed the steps outlined by mobjunky and was able to get an official Honeycomb ROM installed, boot the official and copy my custom ROM and CWM 6.0.0.8 on it. Then install CWM 5.4.0.4 followed by 6.0.0.8.
Now my problem is that any custom ROM I put on there just does a boot screen loop. I tried CM10 and the latest AOSP. To install the ROMs I just booted into CWM, installed the ROM from zip, then installed the gapps. I've tried with and without formatting the cache, user data, and Dalkiv, same results.
What am I doing wrong? I have loaded tons of ROMs on this before without any issues, then all of a sudden I can't get anything except official loaded.
Click to expand...
Click to collapse
Sorry - being a newbie myself I'm at a loss. It worked a charm for me.
spazlon said:
I followed the steps outlined by mobjunky and was able to get an official Honeycomb ROM installed, boot the official and copy my custom ROM and CWM 6.0.0.8 on it. Then install CWM 5.4.0.4 followed by 6.0.0.8.
Now my problem is that any custom ROM I put on there just does a boot screen loop. I tried CM10 and the latest AOSP. To install the ROMs I just booted into CWM, installed the ROM from zip, then installed the gapps. I've tried with and without formatting the cache, user data, and Dalkiv, same results.
What am I doing wrong? I have loaded tons of ROMs on this before without any issues, then all of a sudden I can't get anything except official loaded.
Click to expand...
Click to collapse
did a format /system before installing the custom roms? This is an important step.
prince93 said:
did a format /system before installing the custom roms? This is an important step.
Click to expand...
Click to collapse
This fixed it. Never had to do it with any of my other devices. CM10 loaded quickly after that. Loving how fast JB is!
Thanks!
Sent from my GT-P7310 using Tapatalk HD
It worked
mobjunky said:
Hi Spazlon,
Sorry I'm not allowed to post links yet as I am also very fresh. But I've underlined the addresses so you should be able to find them
I just spent the best of 2 days trying to solve a similar issue - my 8.9 P7300 kept running in boot loop. It had been running ICS stable for several weeks, then suddenly started to loop boot for no good reason. Anyway - you need two programs installed on your computer as well as USB drivers for your tablet. The two programs are Odin and SDK developer package. Odin3 v 1,87 and 1.85 are found here: filecrop.com/Odin-1.87 - try some of the links, one of them should work without having to type a password. The SDK is found here: developer.android.com/sdk You can find more about how to use the developer package on that site as well, but I installed as support for Android 2.1 through to 4.1
Also install the USB driver files for your tablet on your PC. For example from here: xpdrivers.com/usb/_1_24.cfm?gclid=CL2iDs7MCFWF7cAodxFYANQ
You also need the following recovery files which you can find by searching the developer forum for galaxy tab 8.9:
ClockworkMod_Recovery_v5.5.0.4.tar
P73xx_Stock_Recovery.tar
Clockwork_Recovery_6.0.0.8_GT-P7300.zip
and finally a ROM of your choice, for example the ICS rom cm-9-20121028-NIGHTLY-p5.zip that I just used. You can find the latest official ICS ROM's here get.cm/?device=p5
Now - hold down the volume down button on one of the boot cycles. You should now get into a menu with two choices - Download and Recovery. Default is "Download" - if you press volume down you switch between the two choices. Press volume up to select the choice you want.
First you want to select the "Download" option. Then connect your tablet to your PC. The drivers should now install and your tablet should read that you are connected.
Now start Odin3. Click the PDA button and select your P73xx_Stock_Recovery.tar file. Then press Start.
Once finished the tablet will reboot, and you now need to once again get into the recovery menu. Now select the recovery option, not the download menu. You get into the stock recovery menu where you navigate with the volume buttons and select choices with the power button. Do a full factory reset and wipe the cache. WARNING - you will loose ALL your data, but it'either that or stick to a bricked tablet so.... You will also loose your root access,m which is why the next step is needed.
Now that everything is wiped clean you can use Odin again in "download mode" to install ClockworkMod_Recovery_v5.5.0.4.tar with the same procedure as before. You now have root access.
Reboot again and once again into the recovery mode (not download mode). Once you get into the CWM recovery menu you are ready for the final step, which is to install your new operating system.
Go to your SDK installation folder and find the folder named "platform-tools".
First you want to copy two files into this folder (provided you want to install Cynaogen Mod 9):
Clockwork_Recovery_6.0.0.8_GT-P7300.zip
and
Your ROM file of choice
Press shift and right-click in that folder and select "Open command window here". In the command prompt write
adb shell
Note - I had some problems here which was caused by lack of permissions. On your tablet in the CWM menu there should be a choice under the advanced menu for fixing permissions. Use that and you should be able to get into the terminal shell afterwards with the adb shell command
Now write the following command sequence:
• mount /data (don't worry if you get an error message - it means the folder is already mounted)
• cd /data
• mkdir media (if you get an error message saying the folder already exists, that's also OK!)
• exit
• adb push Clockwork_Recovery_6.0.0.8_GT-P7300.zip /data/media
Now you may have to wait a little while until your command prompt is back confirming that the file was uploaded.
Now on your tablet go to the menu point "install zip from sdcard" and find your CWM file that you just uploaded and run that.
Reboot once again into the "recovery mode" - we are now nearly finished.
Run the above push command again from the computer terminal window, this time to upload the ROM file you want to install. (the command is adb push [filename].zip /data/media)
Now on your CWM recovery menu once again run the zip file you just uploaded from the "install zip from sdcard" menu
When completed and you now reboot you should have a completely fresh android installation. Hope this helps.
Remember to mark this thread with solved if it works!
Thanks to kallt_kaffe and all the others who helped me through their various posts (hope that coffee isn't getting too cold again), as well as the following web sites that indirectly helped me resolve this issue googleymind.com/2011/11/guide-so-you-think-you-bricked-your.html#.UJUNN8XAd8G and galaxytabhacks.com/galaxy-tab-10-1-hacks/how-to-root-galaxy-tab-10-1-the-easy-way/
Good luck.
Click to expand...
Click to collapse
WOw! This fixed my Tablet! thank you ever so much!!
mjramos15 said:
WOw! This fixed my Tablet! thank you ever so much!!
Click to expand...
Click to collapse
mobjunky said:
Hi Spazlon,
Sorry I'm not allowed to post links yet as I am also very fresh. But I've underlined the addresses so you should be able to find them
I just spent the best of 2 days trying to solve a similar issue - my 8.9 P7300 kept running in boot loop. It had been running ICS stable for several weeks, then suddenly started to loop boot for no good reason. Anyway - you need two programs installed on your computer as well as USB drivers for your tablet. The two programs are Odin and SDK developer package. Odin3 v 1,87 and 1.85 are found here: filecrop.com/Odin-1.87 - try some of the links, one of them should work without having to type a password. The SDK is found here: developer.android.com/sdk You can find more about how to use the developer package on that site as well, but I installed as support for Android 2.1 through to 4.1
Also install the USB driver files for your tablet on your PC. For example from here: xpdrivers.com/usb/_1_24.cfm?gclid=CL2iDs7MCFWF7cAodxFYANQ
You also need the following recovery files which you can find by searching the developer forum for galaxy tab 8.9:
ClockworkMod_Recovery_v5.5.0.4.tar
P73xx_Stock_Recovery.tar
Clockwork_Recovery_6.0.0.8_GT-P7300.zip
and finally a ROM of your choice, for example the ICS rom cm-9-20121028-NIGHTLY-p5.zip that I just used. You can find the latest official ICS ROM's here get.cm/?device=p5
Now - hold down the volume down button on one of the boot cycles. You should now get into a menu with two choices - Download and Recovery. Default is "Download" - if you press volume down you switch between the two choices. Press volume up to select the choice you want.
First you want to select the "Download" option. Then connect your tablet to your PC. The drivers should now install and your tablet should read that you are connected.
Now start Odin3. Click the PDA button and select your P73xx_Stock_Recovery.tar file. Then press Start.
Once finished the tablet will reboot, and you now need to once again get into the recovery menu. Now select the recovery option, not the download menu. You get into the stock recovery menu where you navigate with the volume buttons and select choices with the power button. Do a full factory reset and wipe the cache. WARNING - you will loose ALL your data, but it'either that or stick to a bricked tablet so.... You will also loose your root access,m which is why the next step is needed.
Now that everything is wiped clean you can use Odin again in "download mode" to install ClockworkMod_Recovery_v5.5.0.4.tar with the same procedure as before. You now have root access.
Reboot again and once again into the recovery mode (not download mode). Once you get into the CWM recovery menu you are ready for the final step, which is to install your new operating system.
Go to your SDK installation folder and find the folder named "platform-tools".
First you want to copy two files into this folder (provided you want to install Cynaogen Mod 9):
Clockwork_Recovery_6.0.0.8_GT-P7300.zip
and
Your ROM file of choice
Press shift and right-click in that folder and select "Open command window here". In the command prompt write
adb shell
Note - I had some problems here which was caused by lack of permissions. On your tablet in the CWM menu there should be a choice under the advanced menu for fixing permissions. Use that and you should be able to get into the terminal shell afterwards with the adb shell command
Now write the following command sequence:
• mount /data (don't worry if you get an error message - it means the folder is already mounted)
• cd /data
• mkdir media (if you get an error message saying the folder already exists, that's also OK!)
• exit
• adb push Clockwork_Recovery_6.0.0.8_GT-P7300.zip /data/media
Now you may have to wait a little while until your command prompt is back confirming that the file was uploaded.
Now on your tablet go to the menu point "install zip from sdcard" and find your CWM file that you just uploaded and run that.
Reboot once again into the "recovery mode" - we are now nearly finished.
Run the above push command again from the computer terminal window, this time to upload the ROM file you want to install. (the command is adb push [filename].zip /data/media)
Now on your CWM recovery menu once again run the zip file you just uploaded from the "install zip from sdcard" menu
When completed and you now reboot you should have a completely fresh android installation. Hope this helps.
Remember to mark this thread with solved if it works!
Thanks to kallt_kaffe and all the others who helped me through their various posts (hope that coffee isn't getting too cold again), as well as the following web sites that indirectly helped me resolve this issue googleymind.com/2011/11/guide-so-you-think-you-bricked-your.html#.UJUNN8XAd8G and galaxytabhacks.com/galaxy-tab-10-1-hacks/how-to-root-galaxy-tab-10-1-the-easy-way/
Good luck.
Click to expand...
Click to collapse
Gee thanks. This saved my tab. I'd almost given up on it and then voila.
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