Database Develop

ROM Manager Reboot?

Slight issue here, not sure if anyone has had it before.
Just acquired a Captivate as an xmas gift to myself (sick of that iPhone), and began the whole process of getting a new ROM onto it. Rooted, installed ROM Manager, flashed a clockworkmod recovery (2.5.1.2), and hit "Backup Current ROM".
The device reboots into the standard recovery mode with the usual options (reboot system now, reinstall packages, delete all user data, delete cache data).
No backup is made, and I just have to continue the reboot. I've tried flashing to an older version, clearing the download cache, and using the option to go to ROM Manager's recovery mode (just takes me to the default recovery boot).
Am I doing something wrong here? I followed all of the instructions step by step.

Velshtein said:
Slight issue here, not sure if anyone has had it before.
Just acquired a Captivate as an xmas gift to myself (sick of that iPhone), and began the whole process of getting a new ROM onto it. Rooted, installed ROM Manager, flashed a clockworkmod recovery (2.5.1.2), and hit "Backup Current ROM".
The device reboots into the standard recovery mode with the usual options (reboot system now, reinstall packages, delete all user data, delete cache data).
No backup is made, and I just have to continue the reboot. I've tried flashing to an older version, clearing the download cache, and using the option to go to ROM Manager's recovery mode (just takes me to the default recovery boot).
Am I doing something wrong here? I followed all of the instructions step by step.
Click to expand...
Click to collapse
Try doing "reinstall packages".
Steps:
1. Copy the clockwork recovery "update.zip" attached to this post to ur sdcard root.
2. Reboot to recovery.
3. Select "reinstall packages".
4. It would say something like replacing recovery with clockwork recovery, and reboot into recovery. This happens only the first time u use this.
5. Select "reinstall packages" again.
6. You should be in clockwork recovery.

diablo009 said:
Try doing "reinstall packages".
Steps:
1. Copy the clockwork recovery "update.zip" attached to this post to ur sdcard root.
2. Reboot to recovery.
3. Select "reinstall packages".
4. It would say something like replacing recovery with clockwork recovery, and reboot into recovery. This happens only the first time u use this.
5. Select "reinstall packages" again.
6. You should be in clockwork recovery.
Click to expand...
Click to collapse
Good deal. Worked perfectly. Out of curiosity, do we know why the phone was doing this?

Velshtein said:
Good deal. Worked perfectly. Out of curiosity, do we know why the phone was doing this?
Click to expand...
Click to collapse
Ok. I'll explain to the best of my knowledge.
The zip I gave u is the most non-intrusive way of CWM. No ROM manager installer is needed on phone apart from placing this zip on sdcard root.
When the phone boots up, it loads the default recovery console. When we select "reinstall packages", it loads "update.zip" on the sdcard root by default. Since the update.zip we have there is the CWM zip, it loads it therby loading CWM console.
If u don't want CWM, just delete this update.zip.
Hope this helps.

I have this exact same issue ROM Manager is doing nothing but rebooting into recovery. So if I use your workaround, I need to keep this update.zip file on my device at all times?

NISMOFO said:
I have this exact same issue ROM Manager is doing nothing but rebooting into recovery. So if I use your workaround, I need to keep this update.zip file on my device at all times?
Click to expand...
Click to collapse
Yes best to do so

All ROM Manager does is download the update.zip that was posted and put it on your SD Card. The other steps need to be done regardless.

MikeyMike01 said:
All ROM Manager does is download the update.zip that was posted and put it on your SD Card. The other steps need to be done regardless.
Click to expand...
Click to collapse
I got the ROM backup working. I guess I was too impatient the first time. I cleared/moved a lot of stuff off my internal SD card too....doubt that it mattered.
But it works quite well.

[Q] ClockworkMod Recovery v3.0.2.4 Bootloop

Phone will only boot into clockworkmod recovery, even after pulling battery and powering up using only the power button, it goes into recovery.
Here is what happend leading up to it:
- flash through rom manager the new clockworkmod
- used fireat's mod with mtd 125 2
- flashed aospCmod 2.3.3
- everything booted fine
- re-did firerat's mod with mtd 102 2
- now bootlooping into clockwork mod
I tried duplicating what worked initialy with no luck. Tried booting into hboot and htc reset menu (power + home + back) but not matter what it only goes to clockworkmod recovery.
For my install steps I followed romrepro "install from other rom" guide here: romrepo.info/wiki/index.php?title=Install_from_another_ROM
I have also tried the following:
- restoring through nandroid
- recovery flasher v1.3 to flash older version of clockwork
- lots of stinking google
All have resulted in no success.
Please help!

Are you s-off? You probably shouldn't mess with firerats if you're not. Mount your sdcard in recovery and change your mtd settings and then flash your rom and reflash fr boot.
~maybe I set it too high...

Thank you for responding. I am not s-off and I already tried changing the mtd part, flash rom, flash boot, and it still autoboots back into recovery.
I re ran the mtd part map with the following:
- 102 2
- 105 2
- 110 2
- 115 2
- 120 2
- 125 2
- 190 2
I also tried flashing aospMOD v9.2.2 (which is what I was originaly using) flashing boot and still no success.

Wait, so it opens recovery by just turning on your phone?
~maybe I set it too high...

bphem3 said:
Thank you for responding. I am not s-off and I already tried changing the mtd part, flash rom, flash boot, and it still autoboots back into recovery.
I re ran the mtd part map with the following:
- 102 2
- 105 2
- 110 2
- 115 2
- 120 2
- 125 2
- 190 2
I also tried flashing aospMOD v9.2.2 (which is what I was originaly using) flashing boot and still no success.
Click to expand...
Click to collapse
If you're changing mtdpartmap.txt (try 125 25) you need to wipe ALL, flash fr-recovery, wipe ALL again, reboot recovery (safely), flash rom/gapps, flash fr-boot, reboot. Once you're in the rom, open terminal (su) or adb shell and type "df -h" and it will show you how much system, data, and cache, are using, you then can change your mtdpartmap.txt accordingly, follow the steps I just listed.

Wait, so it opens recovery by just turning on your phone?
Click to expand...
Click to collapse
Yes, exactly.
If you're changing mtdpartmap.txt (try 125 25) you need to wipe ALL, flash fr-recovery, wipe ALL again, reboot recovery (safely), flash rom/gapps, flash fr-boot, reboot. Once you're in the rom, open terminal (su) or adb shell and type "df -h" and it will show you how much system, data, and cache, are using, you then can change your mtdpartmap.txt accordingly, follow the steps I just listed.
Click to expand...
Click to collapse
I will give this a try and report back. Will either be after lunch or this evening.

If you're changing mtdpartmap.txt (try 125 25) you need to wipe ALL, flash fr-recovery, wipe ALL again, reboot recovery (safely), flash rom/gapps, flash fr-boot, reboot. Once you're in the rom, open terminal (su) or adb shell and type "df -h" and it will show you how much system, data, and cache, are using, you then can change your mtdpartmap.txt accordingly, follow the steps I just listed.
Click to expand...
Click to collapse
Gave it a try, still boots directly into recovery.

bphem3 said:
Gave it a try, still boots directly into recovery.
Click to expand...
Click to collapse
what rom and gapps did you flash, and how are you "booting" - like with what buttons?
also, please list the EXACT steps you took. And what version of hboot do you have, and what recovery, and what version of firerat?

il Duce said:
what rom and gapps did you flash, and how are you "booting" - like with what buttons?
also, please list the EXACT steps you took. And what version of hboot do you have, and what recovery, and what version of firerat?
Click to expand...
Click to collapse
1. wipe data/factory reset
2. wipe cache partition
3. format /boot
4. format /cache
5. format /data
6. format /system
7. wipe dalvik cache
8. flash fr-recovery
9. repeat steps 1-7
10. reboot recovery (from advanced menu)
11. flash rom
12. flash gapps
13. flash kernel
14. flash boot
15. reboot system (from main menu)
aospCMod-HC-20110421-signed.zip
gapps-gb-20110325-signed.zip
aospCWMod-HC-20110421.img
DecaFuct-691.zip
FR-boot-v1.5.6.zip (I have tried both 1.5.6 and 1.5.3)
FR-recovery-v1.5.6.zip (I have tried both 1.5.6 and 1.5.3)
mtdpartmap.txt
Not sure on the hboot. When I simply turn the phone on it boots to recovery. I used to have to press and hold power + home to get into recovery. I also used to be able to press and hold power + home + back and get intot he htc reset menu (or whatever it is). Prior to this happening I never tried to get into hboot (vol up/dn + power) however if I try to now it just goes to recovery. All combinations I have tried it just boots to recovery.

bphem3 said:
1. wipe data/factory reset
2. wipe cache partition
3. format /boot
4. format /cache
5. format /data
6. format /system
7. wipe dalvik cache
8. flash fr-recovery
9. repeat steps 1-7
10. reboot recovery (from advanced menu)
11. flash rom
12. flash gapps
13. flash kernel
14. flash boot
15. reboot system (from main menu)
aospCMod-HC-20110421-signed.zip
gapps-gb-20110325-signed.zip
aospCWMod-HC-20110421.img
DecaFuct-691.zip
FR-boot-v1.5.6.zip (I have tried both 1.5.6 and 1.5.3)
FR-recovery-v1.5.6.zip (I have tried both 1.5.6 and 1.5.3)
mtdpartmap.txt
Not sure on the hboot. When I simply turn the phone on it boots to recovery. I used to have to press and hold power + home to get into recovery. I also used to be able to press and hold power + home + back and get intot he htc reset menu (or whatever it is). Prior to this happening I never tried to get into hboot (vol up/dn + power) however if I try to now it just goes to recovery. All combinations I have tried it just boots to recovery.
Click to expand...
Click to collapse
FYI step 13 is unnecessary, that kernel is already in aospCMod and boots at 691. I guess I would try FR-1.5.8 versions and see what happens (that's what I have), the steps look right to me. You could also try leaving out the gapps and see if just the rom boots, you could also try flashing the last working version of recovery you had (i.e. cwm 3.0.0.5). It's also possible you got a bad download of any one of the above items, so try new DLs too. Report back, I am now officially curious.

I am unsure how to flash another version of recovery, I always use RomManager and I am terrible with adb. I tried using some one of the herocimg.zip to "install from zip" and I kept getting "installation aborted".
I will try FR-1.5.8 and report back.

/me bangs head on keyboard
#eatshit1clickrootmethod!

/me bangs head on keyboard
#eatshit1clickrootmethod!
Click to expand...
Click to collapse
I first used adb and push and blah blah...... 8 months ago.
Then I discovered OneClick! I used to be way more into the technical side of this stuff and then got busy with work and now I am extra lazy!

FYI:
HERCIMG.zip is a partition zip flashable in hboot/bootloader and ONLY if you're s-off
HEROIMG.zip is the same thing, but for a GSM hero....
Hopefully you can figure it out. I hate to say it, but 99.9999999999999999% of the time something doesn't work that others have had success with, it's user error. I'm not trying to be mean, I often miss steps too and need to ask for help. I don't know what you COULD be missing since it sounded like you did everything right, but I would say re-read all the stuff you're doing and hope you see something you may have missed. Best of luck, and please report back if you fix it to help others who may see this thead in the future.

No offense taken. I have had plenty of practice with this with my phone and my wifes and never really had any problems other than user error that I usualy catch. And it's alwasy something silly like flash & wiping out of sequence.
Good information on the HERCIMG and HEROIMG, I did not know that.
Is there a way to RUU the phone from a recovery zip install, (seeming how that is all I can access).

bphem3 said:
No offense taken. I have had plenty of practice with this with my phone and my wifes and never really had any problems other than user error that I usualy catch. And it's alwasy something silly like flash & wiping out of sequence.
Good information on the HERCIMG and HEROIMG, I did not know that.
Is there a way to RUU the phone from a recovery zip install, (seeming how that is all I can access).
Click to expand...
Click to collapse
Not that I know of but you should be able to do it from the bootloader (hold volume down press power - from an off state) and run the RUU.exe from HTC.com.

lol, yeah, that just puts me back in recovery...

bphem3 said:
lol, yeah, that just puts me back in recovery...
Click to expand...
Click to collapse
Well that's nuts. I don't know how you don't have a bootloader, but you do have a recovery... anyway, I guess grab the FR-remove zip that correlates with whatever FR version you have and run the steps again, i.e. wipe all, flash FR-remove, wipe all, reboot recovery, etc. Hope that works. By any chance did you format /misc in the mounts & storage menu?

il Duce said:
Well that's nuts. I don't know how you don't have a bootloader, but you do have a recovery... anyway, I guess grab the FR-remove zip that correlates with whatever FR version you have and run the steps again, i.e. wipe all, flash FR-remove, wipe all, reboot recovery, etc. Hope that works. By any chance did you format /misc in the mounts & storage menu?
Click to expand...
Click to collapse
Format /misc is not listed anywhere. I'm at a loss. I have tried everything over and over and I am still getting the same results. The only thing left I can think of is to redo everything via adb. I'm not 100% on how these phones or linux devices work but it's as if there is something worng with the boot sector and/or sequence of the device.
It doesn't make sense that the first run at all this was flashing aospCmod (mtd 125 2, FR-1.5.3) and everything was working normal. I decided to go back and redo the process with (mtd 102 2, FR-1.5.3). Now this has to be where I or something screwed up. Maybe I did things out of order, got a bad flash, something but I do not know what. When I rebooted, just a normal reboot, it went directly into recovery. Now I have flashed a rom before and had the mtdpartmap.txt too low it caused it to hang on the first boot when the logo for the Rom was shown during loading. To fix this I just adjusted the mtdpartmap.txt.
This time things are different. When I power the hero up the phone vibrates, the white backdrop with green HTC comes up, it sits for approximately 5 seconds, then recovery loads.

bphem3 said:
1. wipe data/factory reset
2. wipe cache partition
3. format /boot
4. format /cache
5. format /data
6. format /system
7. wipe dalvik cache
8. flash fr-recovery
9. repeat steps 1-7
10. reboot recovery (from advanced menu)
11. flash rom
12. flash gapps
13. flash kernel
14. flash boot
15. reboot system (from main menu)
aospCMod-HC-20110421-signed.zip
gapps-gb-20110325-signed.zip
aospCWMod-HC-20110421.img
DecaFuct-691.zip
FR-boot-v1.5.6.zip (I have tried both 1.5.6 and 1.5.3)
FR-recovery-v1.5.6.zip (I have tried both 1.5.6 and 1.5.3)
mtdpartmap.txt
Not sure on the hboot. When I simply turn the phone on it boots to recovery. I used to have to press and hold power + home to get into recovery. I also used to be able to press and hold power + home + back and get intot he htc reset menu (or whatever it is). Prior to this happening I never tried to get into hboot (vol up/dn + power) however if I try to now it just goes to recovery. All combinations I have tried it just boots to recovery.
Click to expand...
Click to collapse
Something about these steps didn't seem correct to me, so went back and read.
After step 8. flash fr-recovery
It says you went back and repeated steps 1. - 7.
I believe you only need to repeat steps 4, 5, 6...the others are probably optional, but I'm pretty sure 3. format boot...is something you don't want to do AFTER doing fr-recovery. then again, I may be overthinking it, and might be completely wrong. I'm sure someone will tell me
My own personal rule is to not make any assumptions and follow the steps listed and don't add extras.
(also, I violate that rule occasionally and usually end up doing a lot more work)

[Q] Sprint P100 can not wipe

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

[Q] Clear Install Android 4.0.4

Hi..
I want to clean install Android 4.0.4 OS on my Samsung galaxy s plus (GT-19001) device.
Clean install means that i 'll have to install OS from scratch. Does i need Micro USb Jig for this purpose?
I have below files.
1-> cm-9-20121011-ivendor-ariesve-rc5.zip
2-> gapps-ics-20120429-signed.zip
3-> recovery-clockwork-6.0.1.2-ariesve.zip
4> CWM-based recovery v5.5.0.4
Guide me in simple steps , i tried many times to install ICS (Android 4.0.4) but unfortunately unsuccessfull each time.
Why it didn't work for me?
I have tried in many ways. Thanks in advancee

Hey,
Could you tell me what was unsuccessful about the install? Did it stop installing, did it bootloop, so on so forth?
But this is how I flashed CM9 onto my I9000, and I know that the I9001 is very similar so...
1.) You've got CWM, sweet. Boot into recovery. Make a bckup of your data through the option provided.
2.) Wipe data/cache/Dalvik cache. The first two are pretty simple to do, the last one is under "Advanced" settings.
3.) Now that you've got that, select "Install zip from SD". Navigate to where your CM9 file is. Select and confirm. Wait for it to flash in...
4.) At this point you might get a recovery bootloop. Don't panic here- just take out the battery, reinsert. Reboot into recovery. You should see that your recovery has been updated.
5.) Reselect the rom from the "Install zip from SD" option. This time it should start flashing in. Wait for it to finish, then it should reboot normally. Be patient as it boots up for the first time.
6.) Once you've done so, reboot into recovery again but this time select the gapps zip.
Unless the I9001 is different in a major way in terms of installing, that should work. I'm not quite sure...
Hope I helped
Sent from my GT-I9000

support required
Soryuu said:
Hey,
Could you tell me what was unsuccessful about the install? Did it stop installing, did it bootloop, so on so forth?
But this is how I flashed CM9 onto my I9000, and I know that the I9001 is very similar so...
1.) You've got CWM, sweet. Boot into recovery. Make a bckup of your data through the option provided.
2.) Wipe data/cache/Dalvik cache. The first two are pretty simple to do, the last one is under "Advanced" settings.
3.) Now that you've got that, select "Install zip from SD". Navigate to where your CM9 file is. Select and confirm. Wait for it to flash in...
4.) At this point you might get a recovery bootloop. Don't panic here- just take out the battery, reinsert. Reboot into recovery. You should see that your recovery has been updated.
5.) Reselect the rom from the "Install zip from SD" option. This time it should start flashing in. Wait for it to finish, then it should reboot normally. Be patient as it boots up for the first time.
6.) Once you've done so, reboot into recovery again but this time select the gapps zip.
Unless the I9001 is different in a major way in terms of installing, that should work. I'm not quite sure...
Hope I helped
Sent from my GT-I9000
Click to expand...
Click to collapse
Hi.
I just started with CWM-based recovery v5.5.0.4 and placed all above mentioned files/packages into the device internal SD card.
That's what i did :
1). Entered into the recovery mode menu by holding down Volume Up + Power and installed CWM-based recovery v5.5.0.4 zip from the selection of Internal SD Card .
2). After reboot, i came up again in Recovery mode using CWM-based recovery v5.5.0.4 application.
3). Now installed cm-9-20121011-ivendor-ariesve-rc5.zip by the navigation of "Install zip from SD".
It took hardly 4 to 5 seconds and displayed a message that it completes . no flash screen or anything came up and reboot.
4). After that installed gapps-ics-20120429-signed.zip by the navigation of "Install zip from SD".
It displayed same complete message but within 5 to 8 seconds i think.
5). I Wipe data/cache/Dalvik cache after above step and then again repeat the process.
After that i did Wipe data/factory reset and wipe cache partition.
Now when i try to start my device then each time it comes into the CWM-based recovery v5.5.0.4' s recovery mode.
Ask please i have tried too many things with it but yet not soft bricked.
I am able to switch into Download mode.

Soryuu said:
Hey,
Could you tell me what was unsuccessful about the install? Did it stop installing, did it bootloop, so on so forth?
But this is how I flashed CM9 onto my I9000, and I know that the I9001 is very similar so...
1.) You've got CWM, sweet. Boot into recovery. Make a bckup of your data through the option provided.
2.) Wipe data/cache/Dalvik cache. The first two are pretty simple to do, the last one is under "Advanced" settings.
3.) Now that you've got that, select "Install zip from SD". Navigate to where your CM9 file is. Select and confirm. Wait for it to flash in...
4.) At this point you might get a recovery bootloop. Don't panic here- just take out the battery, reinsert. Reboot into recovery. You should see that your recovery has been updated.
5.) Reselect the rom from the "Install zip from SD" option. This time it should start flashing in. Wait for it to finish, then it should reboot normally. Be patient as it boots up for the first time.
6.) Once you've done so, reboot into recovery again but this time select the gapps zip.
Unless the I9001 is different in a major way in terms of installing, that should work. I'm not quite sure...
Hope I helped
Sent from my GT-I9000
Click to expand...
Click to collapse
Perfectly simple guide! Thanks.:good:
The only thing I want to ask - what is the backup you have mentioned in point 1)? Is it back up of your personal data, or is it back up of your current ROM?

Hey man, glad I made it simple
Yeah, its a backup of your whole rom I believe- system apps, system files, all your downloaded apps all your data, so on so forth.
Helps you get back to what you were running before in case something goes wrong during installation.
Sent from my GT-I9000
---------- Post added at 02:29 PM ---------- Previous post was at 02:15 PM ----------
empnetsol said:
Hi.
I just started with CWM-based recovery v5.5.0.4 and placed all above mentioned files/packages into the device internal SD card.
That's what i did :
1). Entered into the recovery mode menu by holding down Volume Up + Power and installed CWM-based recovery v5.5.0.4 zip from the selection of Internal SD Card .
2). After reboot, i came up again in Recovery mode using CWM-based recovery v5.5.0.4 application.
3). Now installed cm-9-20121011-ivendor-ariesve-rc5.zip by the navigation of "Install zip from SD".
It took hardly 4 to 5 seconds and displayed a message that it completes . no flash screen or anything came up and reboot.
4). After that installed gapps-ics-20120429-signed.zip by the navigation of "Install zip from SD".
It displayed same complete message but within 5 to 8 seconds i think.
5). I Wipe data/cache/Dalvik cache after above step and then again repeat the process.
After that i did Wipe data/factory reset and wipe cache partition.
Now when i try to start my device then each time it comes into the CWM-based recovery v5.5.0.4' s recovery mode.
Ask please i have tried too many things with it but yet not soft bricked.
I am able to switch into Download mode.
Click to expand...
Click to collapse
Hmmm... Okay, I see...
What recovery did you start with before flashing CWM 5.5.0.4? Because I think what happens is that in whatever recovery you start with, you start by flashing in the CM9 file directly, instead of flashing a different CWM version in first.
So a good place to start would be back at 2.3.6 (don't know the firmware for the I9001). That can be done through download mode and Odin (If you need help with that feel free to ask). Then root again, get recovery back.
Flashing in the CM9 file the first time actually doesn't take long- maybe 5-10 seconds as you said, before bootlooping. What that bootloop does is it actually sets up a newer recovery, so that you can properly flash CM9 in.
Once you flash in the CM9 file the first time, try flash it in a second time. If it takes 4-5 seconds again then you have a problem, otherwise it should take a little bit for the file to install.
It will reboot; like I said in my little guide, just turn off, reboot into recovery and flash in Gapps, then let it boot.
Also, I don't think you need to wipe everything after the CM9 zip finishes. I didn't need to, and it worked fine...
Again, hope I helped
Sent from my GT-I9000

hi .
i am trying to give answer in point:
What recovery did you start with before flashing CWM 5.5.0.4?
-> yes i t was exactly CWM 5.5.0.4.
Because I think what happens is that in whatever recovery you start with, you start by flashing in the CM9 file directly, instead of flashing a different CWM version in first.
-> Could you elaborate the above sentence please? As long as i understood I initially installed CWM recovery through recovery mode by holding +Vol + Power+ Home.
So a good place to start would be back at 2.3.6 (don't know the firmware for the I9001). That can be done through download mode and Odin (If you need help with that feel free to ask). Then root again, get recovery back.
-> Yes i have been reverted through Odin Stock Gingerbread. How to root again? Could you please enlist in points?
Flashing in the CM9 file the first time actually doesn't take long- maybe 5-10 seconds as you said, before bootlooping. What that bootloop does is it actually sets up a newer recovery, so that you can properly flash CM9 in.
-> I don't think it's a bootlooping situation. When i start my device , It dispays CWM recovery screen each time even after the sucessull completion of CM9 and gapps,
Once you flash in the CM9 file the first time, try flash it in a second time. If it takes 4-5 seconds again then you have a problem, otherwise it should take a little bit for the file to install.
It will reboot; like I said in my little guide, just turn off, reboot into recovery and flash in Gapps, then let it boot.
-> I tried it many time right now and 2-3 months ago too but it took almost 20 - 30 seconds in first attempt.
Also, I don't think you need to wipe everything after the CM9 zip finishes. I didn't need to, and it worked fine...
-> I tried through Wipe and with it but could start my OS. Instead it display everytime a CWM screen.
=================================================================================================
In last , i did below steps :
1) Boot into recovery.
2) Wipe data/Factory reset.
3) Wipe cache.
4) Go to Advanced, then wipe Dalvik cache.
5) Go back, go to Mount & Storage, then Format System.
6) Go back, go to Install zip from SD Card => Choose zip from SD Card => cm-9-20121011-ivendor-ariesve-rc5.zip.
7) Do the same thing for the gapps zip.
8) Wipe data/Factory reset again (just to be sure).
9) Reboot.

Go into the cm10 thread by ivendor in developement section and in the middle of the 1st post is a download link for cwm 6.0.1.9. Flash it in recovery and reboot. The Problem should be gone.
Had the same issue.
Hope i helped

Hi Markey.
Do you mean that I 'll have to get CM10 and CWM 6.0.1.9 and then installed with same approach as i aforesaid?
Elaborate please if i misunderstood. Thanks

empnetsol said:
Hi Markey.
Do you mean that I 'll have to get CM10 and CWM 6.0.1.9 and then installed with same approach as i aforesaid?
Elaborate please if i misunderstood. Thanks
Click to expand...
Click to collapse
No i meant that you can install everything like in your guide and after that you install the cwm 6.0.1.9 and reboot, then you should be in recovery and then you have to reboot your phone and it should start normally
This solved it for me
Hope i helped

That's what I understood now:
0.5) Entered into the recovery mode menu by holding down Volume Up + Power and installed CWM-based recovery v5.5.0.4 zip from the selection of Internal SD Card .
1) Boot into CWM-based recovery v5.5.0.4 Recovery mode.
2) Wipe data/Factory reset.
3) Wipe cache.
4) Go to Advanced, then wipe Dalvik cache.
5) Go back, go to Mount & Storage, then Format System.
6) Go back, go to Install zip from SD Card => Choose zip from SD Card => cm-9-20121011-ivendor-ariesve-rc5.zip.
7) Do the same thing for the gapps zip.
8) Wipe data/Factory reset again (just to be sure).
9) Reboot
10) Then install the cwm 6.0.1.9 and reboot.
It could be solution, i will try and 'll tell at today night (after 6 hours).

It should be the right way but you can skip step 5 and 9
Hope i helped
empnetsol said:
That's what I understood now:
0.5) Entered into the recovery mode menu by holding down Volume Up + Power and installed CWM-based recovery v5.5.0.4 zip from the selection of Internal SD Card .
1) Boot into CWM-based recovery v5.5.0.4 Recovery mode.
2) Wipe data/Factory reset.
3) Wipe cache.
4) Go to Advanced, then wipe Dalvik cache.
5) Go back, go to Mount & Storage, then Format System.
6) Go back, go to Install zip from SD Card => Choose zip from SD Card => cm-9-20121011-ivendor-ariesve-rc5.zip.
7) Do the same thing for the gapps zip.
8) Wipe data/Factory reset again (just to be sure).
9) Reboot
10) Then install the cwm 6.0.1.9 and reboot.
It could be solution, i will try and 'll tell at today night (after 6 hours).
Click to expand...
Click to collapse
It should be the right way but you can skip step 5 and 9
Hope i helped

Dear Markey,
Whyn't should i start from cwm 6.0.1.9 rather than CWM-based recovery v5.5.0.4 .
Should i require to check from it or not? cwm 6.0.1.9 support cm-9-20121011-ivendor-ariesve-rc5.zip ?

empnetsol said:
Dear Markey,
Whyn't should i start from cwm 6.0.1.9 rather than CWM-based recovery v5.5.0.4 .
Should i require to check from it or not? cwm 6.0.1.9 support cm-9-20121011-ivendor-ariesve-rc5.zip ?
Click to expand...
Click to collapse
I don't know if cwm 6.0.1.9 supports cm9 but it should.
You could try it out and tell me back

when i go in advance and select wipe dalvik cache option.
it display an error:
E:unknown volume for path [/sd-ext]
Dalvik Cache wiped.
After completion of each step, i tried again but still not start OS.

empnetsol said:
when i go in advance and select wipe dalvik cache option.
it display an error:
E:unknown volume for path [/sd-ext]
Dalvik Cache wiped.
After completion of each step, i tried again but still not start OS.
Click to expand...
Click to collapse
Got the same error, i think its normal
Ok, then flash this file: http://forum.xda-developers.com/attachment.php?attachmentid=861538&d=1326841043 in recovery, reboot and tell me back if it works
Or you could try this way if the other isn't working: http://forum.xda-developers.com/attachment.php?attachmentid=928219&d=1330695090 its the stock recovery, flash it in recovery and reboot and tell me back. I think you should first try stock recovery and then the other file. Sry for the wrong order
Hope it will work again

hi markey.
how to flash these files? i didn't understand the flashing word.

Got an error from mentioned recoveries.
Installing update...
E:Error in /tmp/sideload/package.zip
(Status 2)
Installation aborted.

empnetsol said:
hi markey.
how to flash these files? i didn't understand the flashing word.
Click to expand...
Click to collapse
empnetsol said:
Got an error from mentioned recoveries.
Installing update...
E:Error in /tmp/sideload/package.zip
(Status 2)
Installation aborted.
Click to expand...
Click to collapse
I mean that you have to install them via recovery with install update from sd card or with install zip from sd card -> its called flashing
And i meant that you have to install the first file first and reboot and if its not working when you reboot then install the stock recovery and then the problem should be solved. But then you have to flash the cwm recovery everytime you want to flash something like a new kernel or a custom rom
Hope i could help

Markey,
I did the same as you are saying and got the above error on each file.
Could you explain the below linw please ?
But then you have to flash the cwm recovery everytime you want to flash something like a new kernel or a custom rom
What i 'll have to do now?

empnetsol said:
Markey,
I did the same as you are saying and got the above error on each file.
Could you explain the below linw please ?
But then you have to flash the cwm recovery everytime you want to flash something like a new kernel or a custom rom
What i 'll have to do now?
Click to expand...
Click to collapse
Which recovery do you use?
Cwm or stock recovery?
If you use stock then you have to reboot without installing one of the files and the problem should be solved
I meant that if you want to install another kernel or custom Rom you have to install the cwm recovery because its better then stock and after installation of the Rom or kernel you have to reinstall the stock recovery
If you don't understand i'll write you a guide for what you have to do

Flashed Miui rom, now black screen

Hi guys! Followed the simple guide of flashing a miui rom>
Install:
-1. Put MI-ustone-UIVxx.zip on Internal or External Storage
-2. Goto Recovery and Install MI-ustone-UIxx.zip
-3. Reboot to Recovery
-4. Goto Wipe Menu->Advanced Wipe and Check everything except USB OTG and SD (or what you want;- )
-5. Install again MI-ustone-UIxx.zip
-6. Wipe Cache/Dalvik after successfully install
-7. Reboot & Enjoy!
(Give it time to boot !)
I have rooted phone, places zip on internal. Installed the bootmanager that you install with a .apk file...XZ recovery? In that app I chose boot into recovery and worked. I then Installed zip file. Wiped some stuff and then wiped cache&dalvik. I went back to menu and tried to install zip again but did nothing. I then pressed BOOT and BOOT TO RECOVERY. After this I am experiencing black screen and bootloop. I press volume- volume+ and power etc but just get vibration on phone and nothing else.
What to do now?
Update: Trying to flash recovery with fastboot but getting error:
FAILED remote: command not allowed
Update: Downloaded stock 244 rom and flashed it and now phone is back to normal but no root So what was wrong?