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
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
so, i'll start with the begining...
i successfully rooted my phone using this tutorial: http://www.youtube.com/watch?v=KqXzpqcMOtQ (check desription, instructions in romanian, but there is the link to xda forum). I guess i used the 3rd method of this: http://forum.xda-developers.com/showthread.php?t=1719699
my phone worked just fine, i wasn't able to overclock, just to keep the processor at max clock.
so i searched more informations about overclocking and i figured out that i need a custom kernel. i installed "ROM Manager" from "Google play" and flashed with odin "clockworkmod-jena.5.2.0.8.tar.md5" from here: http://forum.xda-developers.com/showthread.php?t=1768622 .
after that i copyed in my phone the "Universal OverClocked kernel upto 1.1Ghz (For Stock Rom)" from the same link above...
so, in the next step (bricking one) i've opened "ROM manager" and decided to do a data recovery.it requested for root access and i answered yes, with the check to always let this app to have root access. after that i selected "my phone is not listed(or some like that)" and installed the 2.xyz version. then my phone booted with the yellow triangle and after that "CWM-based Recovery v5.0.2.8" screen asked me what i want to do. i chosed "backup and restore" >> "backup" and an error message apeares. after that the phone keep booting in "CWM-based recovery"....
my short story(and question) is: how can i get over boot in recovery mode after using ROM manager to get in?
LATER EDIT:
whiting right now i chosed "backup to sd card" the process started but after some minutes ended with error. i chosed reboot now and some white little code show on my screeen, with a flickerring white band on right.
althought is hard to read that, this is what i understood:
###########################
# #
# ROMDUMP Mode #
# (ARM9 mode) #
- AP -
Oups
recovery PID-89
- CP -
vmem Ovil tmp_e LINE_0
Format 1
qxdm message 1
##########################
how i get rid of that? i get it everytime i choice to reboot phone now...should i reinstall another ROM? im afraid i might do more bad than good, so i'm asking you guys what should i do...
flash whit odin stock rom and begin hole fun from begin
not working, i get this on odin: imageshack.us/a/img542/2788/21136667.png
and this is what i get on boot: imageshack.us/a/img32/6774/bootr.jpg
and when i choice reboot i get: imageshack.us/a/img600/6725/rebootr.jpg
on the last screen when i press vol.down key i get some underlines like that: imageshack.us/a/img824/673/reboot2.jpg
also my PID changed in 89 and 90....
try to flash via odin only squadzone's recovery
please check my photos, i cant go to download mode, i get the last 2 screens (check photos)
my odin cant make setup conection....
i will try to contact clockworkmod for this problem too...
and tnx you guys for trying to help me any other sugestion is welcomed
i think this may work... forum.xda-developers.com/showthread.php?t=1514088
Don't try anything from that ASUS thread , it will screw it up even worse .
Out of the three (actually there are 4 but one , which is the best , isn't listed there) methods to root your phone , you chose the worst . From what I can see from your Odin screenshot , you flashed Galaxy Y firmware on a S6500D (Odin version seems to be the same but I have a bad feeling about that tar you flashed first) .
But the main thing that I think bricked your device was ROM Manager . A thing that no one seems to have pointed out around here , is that ROM MANAGER DOES NOT WORK WITH S6500/D AND WILL MOST LIKELY BRICK IT . . Some people had similar experiences after using it .
Right now try not to do anything stupid with it . I will try to provide you a stock backup to restore on your phone today .
// Here it is : Stock_S6500D_Backup.zip (bassed on S6500DXXLC4_S6500DXXLC3_S6500DORLLC2_HOME) .
Extract it and put the "Stock Backup" folder inside SD Card/clockworkmod/backup/ , on any SD Card you want . Then insert the SD card in your phone , boot into recovery , choose "Backup & Restore" -> "Restore" -> "Stock Backup" and it will start restoring .
If there's any error during the restore , tell me . Also , if everything went fine , tell me as well . I'll tell you how to properly root and overclock your phone as well .
thank you for your time i will try to find a sd-card somewhere... and i will let you know about my progress
cute THANKS button :laugh::good:
is restore working?
your in deep mess man
i guess that rom manager(cwm recovery) can't find my sd card, it tells me when i go to restore from sd:
Couldn't open directory.
No files found
Click to expand...
Click to collapse
could i try something from "mounts and restore"?
Later edit: i managed to force the phone go in gownload mode(unplug your battery, plug the usb, press vol.down+home+power, while pressing those insert your battery )
odin still detect it as mini, although is mini2 (i used mini ROM to root it)
PHONE UNBRICKED!!! you guys can move it back to mini2 development forum, because this thread has developed a way to unbrick sgm2
I've also, dead bricked, it's because I try to use 'swapper2'. As a result had to re-flash with JTAG.
Sent from my GT-S6500D | CM10
I have bricked my s6500d and now when boot it open only in CWM v5.0.2.8 ! What should i do ? need some help .
Hi there, only just joined site as have had problem with this phone for a while now but left it alone untill my GF nagged me to try and fix it, but am very stuck and confused so here it goes....
the phone's carrier was virgin mobile so i downloaded an app to unlock it to another carrier but phone froze during process so had to power off and on the it got stuck on logo screen so some how i managed to install twrp v2.6.3.0 onto the phone but i am now just stuck here the phone now has no operating system and it showing internal memory as 0mb and i can only mount external SD.
Please if someone can help me i would be very very happy as its driving me crazy...serious.
Hope this post is in the correct section and any other info required i can give if needed.
Thanks in advance
John
johnlfc81 said:
Hi there, only just joined site as have had problem with this phone for a while now but left it alone untill my GF nagged me to try and fix it, but am very stuck and confused so here it goes....
the phone's carrier was virgin mobile so i downloaded an app to unlock it to another carrier but phone froze during process so had to power off and on the it got stuck on logo screen so some how i managed to install twrp v2.6.3.0 onto the phone but i am now just stuck here the phone now has no operating system and it showing internal memory as 0mb and i can only mount external SD.
Please if someone can help me i would be very very happy as its driving me crazy...serious.
Hope this post is in the correct section and any other info required i can give if needed.
Thanks in advance
John
Click to expand...
Click to collapse
if you've got a working CWM or TWRP Recovery then it should be easy to flash a new firmware onto the phone. I haven't done this but try the following steps :
1. Download this http://www.ipho9.com/install-dmod-custom-rom-galaxy-s3-mini-gti8190/ custom ROM
2. DO NOT extract it (keep the .zip file, well, zipped )
3. Copy/Paste the above .zip file to your external sd card
4. Start the phone and go to recovery (power+home+volume up buttons)
5. Choose install zip from external sd card
6. Find the .zip file that you just copied and select it
7. Now wait until it installs (can take about 10 mins or more - just be patient)
8. Reboot phone when the installation of the ROM is complete
9. Have fun with your completely new S3 Mini with a new great S4 look&feel
Hope that works !
koragg97 said:
if you've got a working CWM or TWRP Recovery then it should be easy to flash a new firmware onto the phone. I haven't done this but try the following steps :
1. Download this http://www.ipho9.com/install-dmod-custom-rom-galaxy-s3-mini-gti8190/ custom ROM
2. DO NOT extract it (keep the .zip file, well, zipped )
3. Copy/Paste the above .zip file to your external sd card
4. Start the phone and go to recovery (power+home+volume up buttons)
5. Choose install zip from external sd card
6. Find the .zip file that you just copied and select it
7. Now wait until it installs (can take about 10 mins or more - just be patient)
8. Reboot phone when the installation of the ROM is complete
9. Have fun with your completely new S3 Mini with a new great S4 look&feel
Hope that works !
Click to expand...
Click to collapse
1. Download this http://www.ipho9.com/install-dmod-custom-rom-galaxy-s3-mini-gti8190/ custom ROM
Click to expand...
Click to collapse
you can download every ROM you want for s3 mini (somin.n, Virginity, CM, ...) - steps 2 - 9 are the same
good luck
JackoMJ is right. I just posted the one i'm on 'cause i know that all the stuff are working