This belongs to this thread: http://forum.xda-developers.com/showthread.php?t=1324831
Sorry if I do not mention every problem in this thread, for there is a lot that can go wrong! If there are any further questions, please feel free to ask. Also, I am not responsible if anything goes wrong, obviously you have a choice to install this ROM. Finally, I am not a dev, I wish I was though. If I have crossed some boundaries, please let me know, I'm sorry this is my first major post. So help me, to help you!
Here is how to install and also get 3G working, don't complain, I tried.
If there are any questions, again, ask.
First, get this ODIN one click, http://forum.xda-developers.com/showthread.php?t=731989 , thank you DG, you are a stud. Download the latest Nightly ,http://download.cyanogenmod.com/?device=captivatemtd , (I used 181). Grab the attached update.zip as well, this will be your CWM, to access it, use the 3 button method to get to recovery (press volume up and down, plus the power. release the power button when you see the ATT logo). Lastly, download Alpha 6, along with the Enable 3g zip and the superuser zip. Put nightly 181, the Alpha 6.zip, superuser.zip, update.zip, and the Enable 3g. zip on your sdcard.
Basic Outline of what needs to be done for original Alpha 6:
Download all the .zip's and the odin. Install drivers, and open up the ODIN.
Put the 4 zip's (Nightly 181, Alpha 6, Enable 3g, and update) on the root of your SDcard.
Open ODIN, and enter download mode on your phone. Connect your phone to your computer.
Press start on ODIN, and let it work.
Once the phone reboots, enter recovery mode. Choose reintsall packages, or install update.zip, whichever is there.
The phone will come back to that same recovery, choose reinstall packages or install update.zip again.
Choose install zip from SDcard, then choose zip form SDcard, and pick the cm7 nightly 181. Let that install.
Once CM7 is intalled, go back to recovery. Choose install zip from SDcard, then choose zip from sdcard, and install Alpha 6. You may have to repeat this step.
Go back into recovery, select install zip from SDcard, choose zip form SDcard, install the superuser.zip. Reboot the phone.
Once booted, log into you Google account, and download Script Manager.
Press the Menu soft key, System Settings, More..., Mobile Networks, Access Point Names, Menu soft key, New APN, Select Name and enter ATT WAP, then select APN and enter wap.cingular, Menu soft key and select save.
Reboot into recovery, install zip from SDcard, choose zip from SDcard, select the Enable 3g.zip, install.
Reboot the phone, open Script Manager.
Select the folder ".." twice (it should be the top folder), your now at the root folder, select etc, then init.d, select 99enable3g. Make sure "Run as root", "Run at boot", and "Run on net.change" are selected. Press save.
Reboot and it should work! Questions? Concerns? Let me know!
Basic Outline of what needs to be done for the Alpha 6 with Hardware Acceleration:
This is optional, but I went back to stock. You need the JF6 like before as well as the update.zip and the Alpha 6HW2D.zip on the SDcard.
Flash back to stock.*
Once finished going back to stock, go into recovery and reinstall packages. Let it reboot and select reinstall packages again.
First, do delete all user data and cache. It works.
Select install zip from SDcard, then choose zip from SDcard.
Select Alpha 6HW2D.zip. Let it complete. Then go back into recovery and repeat. It must be flashed twice.
TADA! let it boot and you should be good to go!
I will be adding more to this, but it will take some time. Thank you.
goob1284 said:
This belongs to this thread: http://forum.xda-developers.com/showthread.php?t=1324831
Sorry if I do not mention every problem in this thread, for there is a lot that can go wrong! If there are any further questions, please feel free to ask. Also, I am not responsible if anything goes wrong, obviously you have a choice to install this ROM. Finally, I am not a dev, I wish I was though. If I have crossed some boundaries, please let me know, I'm sorry this is my first major post. So help me, to help you!
Here is a video on how to install and also get 3G working, don't complain, I tried.
If there are any questions, again, ask.
First, get this ODIN one click, http://forum.xda-developers.com/showthread.php?t=731989 , thank you DG, you are a stud. Download the latest Nightly ,http://download.cyanogenmod.com/?device=captivatemtd , (I used 181). Grab the attached update.zip as well, this will be your CWM, to access it, use the 3 button method to get to recovery (press volume up and down, plus the power. release the power button when you see the ATT logo). Lastly, download Alpha 6, along with the Enable 3g zip and the superuser zip. Put nightly 181, the Alpha 6.zip, superuser.zip, update.zip, and the Enable 3g. zip on your sdcard.
(this video will be added hopefully by the end of today)
Basic Outline of what needs to be done:
Download all the .zip's and the odin. Install drivers, and open up the ODIN.
Put the 4 zip's (Nightly 181, Alpha 6, Enable 3g, and update) on the root of your SDcard.
Open ODIN, and enter download mode on your phone. Connect your phone to your computer.
Press start on ODIN, and let it work.
Once the phone reboots, enter recovery mode. Choose reintsall packages, or install update.zip, whichever is there.
The phone will come back to that same recovery, choose reinstall packages or install update.zip again.
Choose install zip from SDcard, then choose zip form SDcard, and pick the cm7 nightly 181. Let that install.
Once CM7 is intalled, go back to recovery. Choose install zip from SDcard, then choose zip from sdcard, and install Alpha 6. You may have to repeat this step.
Go back into recovery, select install zip from SDcard, choose zip form SDcard, install the superuser.zip. Reboot the phone.
Once booted, log into you Google account, and download Script Manager.
Press the Menu soft key, System Settings, More..., Mobile Networks, Access Point Names, Menu soft key, New APN, Select Name and enter ATT WAP, then select APN and enter wap.cingular, Menu soft key and select save.
Reboot into recovery, install zip from SDcard, choose zip from SDcard, select the Enable 3g.zip, install.
Reboot the phone, open Script Manager.
Select the folder ".." twice (it should be the top folder), your now at the root folder, select etc, then init.d, select 99enable3g. Make sure "Run as root", "Run at boot", and "Run on net.change" are selected. Press save.
Reboot and it should work! Questions? Concerns? Let me know!
I will be adding more to this, but it will take some time. Thank you.
Click to expand...
Click to collapse
Question on the necessity of installing CM7. I came from JF6 stock, and I'm rolling just fine(for a Alpha)
EDIT** adding links for downloads:
A6 Cappy: http://api.viglink.com/api/click?fo...97 ICS!!! A6&jsonp=vglnk_jsonp_13219900825961
SuperuserFix: http://forum.xda-developers.com/attachment.php?attachmentid=776518&d=1320787022
Enable3gv2 fix: http://forum.xda-developers.com/attachment.php?attachmentid=790072&d=1321869485
ICS_VoiceSearchFix: http://forum.xda-developers.com/attachment.php?attachmentid=790280&d=1321887896
Calendar Fix: http://forum.xda-developers.com/attachment.php?attachmentid=790037&d=1321868087
Does downloading apps from the Market work for you? I get the "Insufficient space" error.
swapnil said:
Does downloading apps from the Market work for you? I get the "Insufficient space" error.
Click to expand...
Click to collapse
I am not having that problem. Try clearing the market cache, and reboot
kangi26 said:
Question on the necessity of installing CM7. I came from JF6 stock, and I'm rolling just fine
EDIT** adding links for downloads:
A6 Cappy: http://api.viglink.com/api/click?fo...97 ICS!!! A6&jsonp=vglnk_jsonp_13219900825961
SuperuserFix: http://forum.xda-developers.com/attachment.php?attachmentid=776518&d=1320787022
Enable3gv2 fix: http://forum.xda-developers.com/attachment.php?attachmentid=790072&d=1321869485
ICS_VoiceSearchFix: http://forum.xda-developers.com/attachment.php?attachmentid=790280&d=1321887896
Calendar Fix: http://forum.xda-developers.com/attachment.php?attachmentid=790037&d=1321868087
Click to expand...
Click to collapse
Thank you for the links! I might need help with those instructions, Ill try to look them up. Ill add more to this later, Im gonna be busy for the next couple hours with some house work. Ill be adding the video and clean up the OP. with CM7, ill see how that goes, I just added that in there cause thats how i did it. Ill see if theres a better way. thank you very much for your help!
Just to ask the question - why is the JF6 with bootloaders necessary? Is the current state of the ICS port not compatible with GB bootloaders? Or is it just to have CWM available for flashing?
I'm just asking because if it's just a matter of being on a stock scenario, it would be safer to come from a non-bootloader stock package.
Combined patch:
http://forum.xda-developers.com/showpost.php?p=19596674&postcount=2081
I also did not go from CM7.
Went from KK2 rom --> recovery, clear data, flash ROM -> recovery, clear data, flash ROM --> flash ROM (just for good measure, since I was in endless boot animation) --> flash superuser zip and enable3gv2 zip --> scriptmanager, set script settings --> reboot
Good to go with 3g working. other fixes can be applied too. I think the above package contains all of them.
jmtheiss said:
Just to ask the question - why is the JF6 with bootloaders necessary? Is the current state of the ICS port not compatible with GB bootloaders? Or is it just to have CWM available for flashing?
I'm just asking because if it's just a matter of being on a stock scenario, it would be safer to come from a non-bootloader stock package.
Click to expand...
Click to collapse
You can go with the GB bootloaders, I guess its personal preference. And I did it as a precaution. I like going back to COMPLETE stock to make sure I start from scratch.
zeezz said:
Combined patch:
http://forum.xda-developers.com/showpost.php?p=19596674&postcount=2081
I also did not go from CM7.
Went from KK2 rom --> recovery, clear data, flash ROM -> recovery, clear data, flash ROM --> flash ROM (just for good measure, since I was in endless boot animation) --> flash superuser zip and enable3gv2 zip --> scriptmanager, set script settings --> reboot
Good to go with 3g working. other fixes can be applied too. I think the above package contains all of them.
Click to expand...
Click to collapse
Thank you for that link. And Ill change the directions as soon as i post up that video!
jmtheiss said:
Just to ask the question - why is the JF6 with bootloaders necessary? Is the current state of the ICS port not compatible with GB bootloaders? Or is it just to have CWM available for flashing?
I'm just asking because if it's just a matter of being on a stock scenario, it would be safer to come from a non-bootloader stock package.
Click to expand...
Click to collapse
I dont think it is, I like to make sure I have a known good baseline for testing, so I almost always go to JF6 and MC when I install ROM's like this
Here - I've whipped up a pack with all the fixes (and directions) except the A6 file (as that's pretty big). Enjoy.
SMS Issues
If you're having problems sending SMS:
Open Dialer *#*#4636#*#*
Click: phone info
Press refresh next to smsc and see if the number is 07913121139418f0
If it isn't, input that number and hit Update
Reboot
Thanks Twicebak3d!
jmtheiss said:
Here - I've whipped up a pack with all the fixes (and directions) except the A6 file (as that's pretty big). Enjoy.
Click to expand...
Click to collapse
Wow. Thats amazing. I might do that with all the files! Thanks
FYI, Running A6 with the Cappy kernel. I'm testing the battery now, and hit 100% last night before bed, unplugged, and overnight, dropped to 43%. Limited use since 9am PST, now down to 16%. Something interesting, Screen use is 45%, Phone Idle 20%, Android OS 9%
Device not going to sleep?
kangi26 said:
FYI, Running A6 with the Cappy kernel. I'm testing the battery now, and hit 100% last night before bed, unplugged, and overnight, dropped to 43%. Limited use since 9am PST, now down to 16%. Something interesting, Screen use is 45%, Phone Idle 20%, Android OS 9%
Device not going to sleep?
Click to expand...
Click to collapse
Thats what i think too. Im checking voltage control every once in a while, and the unused state is sleep. 100Mhz is at like 43%+.
goob1284 said:
Thats what i think too. Im checking voltage control every once in a while, and the unused state is sleep. 100Mhz is at like 43%+.
Click to expand...
Click to collapse
Rumor has it that onecosmic is going to release A7 soon. I'll hold on to A6 until then and reflash then. See if that changes anything
I'm getting 65% in deep sleep and 20% in 100mhz...
Sent from ICS captivate. Be jello.
Captivate install instruction for A6
So we start off, of course we need some files & requirements:
Make sure you have a WiFi connection available
The ROM itself: http://forum.xda-developers.com/showpost.php?p=18877954&postcount=1
SuperUser fix: http://forum.xda-developers.com/attachment.php?attachmentid=776518&d=1320787022
3G: fix http://forum.xda-developers.com/attachment.php?attachmentid=790072&d=1321869485
Voicesearch fix: http://forum.xda-developers.com/atta...0&d=1321887896
Calendar Fix: http://forum.xda-developers.com/attachment.php?attachmentid=790037&d=1321868087
I put all of them in a folder called ICS, you name it whatever you want
First of all we need to make sure you do not have simlock enabled.
To disable:
1. Go to settings
2. Go to the security tab
3. Click on sim card lock, and disable it.
You do NOT have to be on any particular ROM to install ICS. I prefer to start from JF6 and Master Clear.
If you are on a custom ROM:
Make sure to disable any lagfix if you have one enabled
Copy folder with your downloads onto your devices SD
If you want to make a backup of your current ROM, now would be the time to do that
Once that is done, power off, and just for safety sake, I remove my Ext SD and SIM
Now we need to wipe the phone.
1. In the recovery menu select “wipe data/factory reset”
2. Go ahead and go to the “advanced” option
3. In there select “wipe Dalvik Cache”
4. Go back to the menu you were before.
5. In the recovery menu navigate to “install zip from sdcard” and press your selection key
6. Now choose the option “choose zip from sdcard”
7. Navigate to the ICS Folder
8. Select the ROM
9. Now navigate to the option “Yes – ROM NAME HERE”
It will now flash the rom.
Once this is done, go back and install the ROM one more time
Once we have done this, go ahead and hit the “reboot system now” option.
Wait for the phone to boot, if it does not go past the boot screen after a few min, pop out the battery, re-install the battery, re-boot into recovery and start at step #1 again
Reboot in recovery.
1. In the recovery menu navigate to “install zip from sdcard” and press your selection key
2. Now choose the option “choose zip from sdcard”
3. Navigate to the ICS folder
4. In there select “Superuser-3.0.6-efgh-signed.zip”
5. Now navigate to the option “Yes – install Superuser-3.0.6-efgh-signed.zip”
Once it’s done, “reboot system now”
Once you’ve restarted. You’ll need to install script manager. For this you must have a WiFi connection, the device will not have a data connection yet. Open up the market and search in for “script manager”, and download & install Script Manager FREE.
When it’s done installing, we are going to add YOUR APN.
1. Open the settings app
2. Click on “more…”
3. Now press “Mobile networks”
4. Then click “Access Point Names”
5. And hit the menu button, then press “new APN”
For AT&T, I have been successful with:
Name: ATT
APN: wap.cingular
Proxy: Not Set
Port: Not Set
Username: Not Set
Password: Not Set
Server: Not Set
MMSC: Not Set
MMS Proxy: Not Set
MMS Port: 80
MCC: 310
MNC: 410
Authentication Type: Not Set
APN Type: Not Set
When you have put these in, hit menu and save
Reboot into Recovery:
1. Navigate to “install zip from sdcard” and press your selection key
2. Now choose the option “choose zip from sdcard”
3. Navigate to the ICS folder
4. Select “enable3gv2.zip”
5. Now navigate to the option “Yes – install enable3gv2.zip”
When it’s done flashing hit the “reboot system now” option.
Thank you to WarDrake in the i9000 threads who simplified this fix. I’m using his instructions and all credits go to him
1. Open script manager and go navigate to : /etc/init.d
2. In here select the script named 99enable3g and open it as a script
3. Now select run as root, run at boot, run on network change (DO NOT RUN IT)
4. Hit the “save” button.
5. Exit script manager
Reboot into Recovery:
1. In the recovery menu navigate to “install zip from sdcard” and press your selection key
2. Now choose the option “choose zip from sdcard”
3. Navigate to the ICS folder
4. Select “ICS_VoiceSearchFix.zip”
5. Now navigate to the option “Yes – install ICS_VoiceSearchFix.zip”
1. Select “choose zip from sdcard”
3. Navigate to the ICS folder
4. Select “CalendarFix.zip”
5. Now navigate to the option “Yes – install CalendarFix.zip”
Reboot, and you should be running ICS.
If you cannot send SMS(Thanks to Thanks Twicebak3d)
Open Dialer *#*#4636#*#*
Click: phone info
Press refresh next to smsc and see if the number is 07913121139418f0
If it isn't, input that number and hit Update
Reboot
jmtheiss said:
Here - I've whipped up a pack with all the fixes (and directions) except the A6 file (as that's pretty big). Enjoy.
Click to expand...
Click to collapse
This looks like I can flash from CWM. Is that right?
Sent from my SGH-I897 using xda premium
elmerct said:
This looks like I can flash from CWM. Is that right?
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
Each individual file, yes
Does wi-fi tethering work?
I have a rooted 2.2 Captivate with Clockwork mod version 2.5.1.2 installed. Rom manger acts as though everything is working but when I go to reboot into CWM recovery I get the stock 3e. I go to reinstall packages. I end up with "E:failed to verify whole-file signature" "E:signature varification failed" My intentions were to follow the instructions I found on Android Authority.
they are:
1. Copy the Devil RC3 kernel and the CyanogenMod 10 V2 ROM files to your Captivate’s internal SD Card.
2. Turn off your Captivate.
3. Boot into Recovery Mode. You can do this by pressing and holding down the Volume Up, Volume Down, and Power buttons. When the screen turns on, let go of all three buttons.
*I'm stuck at this point because it won't load CWM
4. In recovery, use the Volume keys to navigate and the Power button to select.
5. Make a NANDroid Backup of your current ROM. Select Backup and Restore and select Backup.
6. Select Wipe Data/Factory Reset. Confirm the action on the next page.
7. Select Install ZIP from SD Card.
8. Select Choose ZIP from SD Card and locate the Devil RC3 kernel.
9. After the Devil RC3 kernel has finished flashing, choose Install ZIP from SD Card again.
10. Select Choose ZIP from SD Card and locate the CyanogenMod 10 V2 ROM file.
11. After the CyanogenMod 10 V2 ROM file has finished flashing, select Go Back.
12. Select Advanced > Fix Permissions.
Return to main recovery menu and select Reboot System Now.
Thanks in advance.
AllieB said:
I have a rooted 2.2 Captivate with Clockwork mod version 2.5.1.2 installed. Rom manger acts as though everything is working but when I go to reboot into CWM recovery I get the stock 3e. I go to reinstall packages. I end up with "E:failed to verify whole-file signature" "E:signature varification failed" My intentions were to follow the instructions I found on Android Authority.
they are:
1. Copy the Devil RC3 kernel and the CyanogenMod 10 V2 ROM files to your Captivate’s internal SD Card.
2. Turn off your Captivate.
3. Boot into Recovery Mode. You can do this by pressing and holding down the Volume Up, Volume Down, and Power buttons. When the screen turns on, let go of all three buttons.
*I'm stuck at this point because it won't load CWM
4. In recovery, use the Volume keys to navigate and the Power button to select.
5. Make a NANDroid Backup of your current ROM. Select Backup and Restore and select Backup.
6. Select Wipe Data/Factory Reset. Confirm the action on the next page.
7. Select Install ZIP from SD Card.
8. Select Choose ZIP from SD Card and locate the Devil RC3 kernel.
9. After the Devil RC3 kernel has finished flashing, choose Install ZIP from SD Card again.
10. Select Choose ZIP from SD Card and locate the CyanogenMod 10 V2 ROM file.
11. After the CyanogenMod 10 V2 ROM file has finished flashing, select Go Back.
12. Select Advanced > Fix Permissions.
Return to main recovery menu and select Reboot System Now.
Thanks in advance.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1350266
Have a look at this link. Hopefully it will help you get to where you want to be. Also remember over-reading about what you are wanting to do is better than trying to find a solution to something because you missed a step.
m1batt1 said:
http://forum.xda-developers.com/showthread.php?t=1350266
Have a look at this link. Hopefully it will help you get to where you want to be. Also remember over-reading about what you are wanting to do is better than trying to find a solution to something because you missed a step.
Click to expand...
Click to collapse
Thank you.
I have a question. Do I need to flash the Devil RC3 kernel or should I just install the CyanogenMod 10 V2 rom from zip? Or should I flash the speedmod kernel on odin, then from CWM install the Devil RC3 kerenel, Then install CyanogenMod 10 V2. I just wondered if the two kerenels would conflict or if I would even need Devil RC3?
AllieB said:
Thank you.
I have a question. Do I need to flash the Devil RC3 kernel or should I just install the CyanogenMod 10 V2 rom from zip? Or should I flash the speedmod kernel on odin, then from CWM install the Devil RC3 kerenel, Then install CyanogenMod 10 V2. I just wondered if the two kerenels would conflict or if I would even need Devil RC3?
Click to expand...
Click to collapse
First of all you're getting a little ahead of yourself in trying to get to CM10 from where you are. Being on 2.2 you will need to get to a gingerbread ROM first as the bootloaders are different and will cause issues trying to go to CM10 if you don't go to gingerbread first.
The following link will take you to some one-click utilities that will update you to gingerbread along with the needed bootloaders. Also I suggest picking one from the list that says it has a CWM kernel injected so that you can save a step after the flash and have a CWM recovery kernel already installed.
Once you've used the one-click you shouldn't need to flash either of the kernels you've mentioned you should technically be able to just flash the CM10 and be good. Although when it comes to flashing the CM10 I suggest you go to the creaters thread or site and follow their exact directions for installing!
AllieB said:
Thank you.
I have a question. Do I need to flash the Devil RC3 kernel or should I just install the CyanogenMod 10 V2 rom from zip? Or should I flash the speedmod kernel on odin, then from CWM install the Devil RC3 kerenel, Then install CyanogenMod 10 V2. I just wondered if the two kerenels would conflict or if I would even need Devil RC3?
Click to expand...
Click to collapse
I highly recommend you install official cm instead. They are updated and will be more stable.
Sent from a jelly bean
I installed the [ROM] [NIGHTLY] [JB] [4.2.2] CyanogenMod 10.1 nightly from milaq, and when I choose "boot CyanogenMod" from the moboot 0.3.8 menu, it continues with some blue text (loading boot/uimage, ramdisk, kernel, booting...), the screen goes black for a little bit, and then it reboots to the moboot menu again. Both WebOS and ClockworkMod load fine from the moboot menu.
I had some older version of CyanogenMod installed previously that I didn't care about, so this is what I did:
Ran ACMEUninstaller, after which the moboot menu was gone
Within WebOS, ran a Full Reset
Reloaded the WebOS via WebOS Doctor
Mounted the Touchpad and copied these files to /cminstall: cm-10.1-20130601-UNOFFICIAL-tenderloin.zip, moboot_038-tenderloin.zip, update-CWM6_tenderloin-20121215.zip, update-gapps-jb-20130301-signed.zip
Ran ACMEInstaller3 and watched it install/reboot
I also tried the 20130531 build with no change.
atamido said:
I installed the [ROM] [NIGHTLY] [JB] [4.2.2] CyanogenMod 10.1 nightly from milaq, and when I choose "boot CyanogenMod" from the moboot 0.3.8 menu, it continues with some blue text (loading boot/uimage, ramdisk, kernel), the screen goes black for a little bit, and then it reboots to the moboot menu again. Both WebOS and ClockworkMod load fine from the moboot menu.
I had some older version of CyanogenMod installed previously that I didn't care about, so this is what I did:
Ran ACMEUninstaller, after which the moboot menu was gone
Within WebOS, ran a Full Reset
Reloaded the WebOS via WebOS Doctor
Mounted the Touchpad and copied these files to /cminstall: cm-10.1-20130601-UNOFFICIAL-tenderloin.zip, moboot_038-tenderloin.zip, update-CWM6_tenderloin-20121215.zip, update-gapps-jb-20130301-signed.zip
Ran ACMEInstaller3 and watched it install/reboot
I'm not sure, but try putting "update-" at the beginning of the files that don't have it. Without the quotes....lol
Hope it works!
Click to expand...
Click to collapse
chicle_11 said:
I'm not sure, but try putting "update-" at the beginning of the files that don't have it. Without the quotes....lol
Hope it works!
Click to expand...
Click to collapse
I tried this, but it didn't make any difference.
Try this guide: http://forum.xda-developers.com/showthread.php?t=1426244
If you have problems with novaterm, there is a workaround on page 12.
I've done this more than 3 times already. Be aware that you will lose all your data, unless you back it up to your PC.
Good luck.
I was able to delete all of the partitions, reinstall 3.0.0, update to 3.0.5, and then followed the installation instructions again for CyanogenMod, but I'm right back where I started. The moboot menu will load and I can get into WebOS or ClockworkMod, but if I choose CyanogenMod then after it says "booting..." the screen will go black for a bit and then reboot.
Edit: I double checked the MD5 sums of the files I downloaded, just in case.
atamido said:
I was able to delete all of the partitions, reinstall 3.0.0, update to 3.0.5, and then followed the installation instructions again for CyanogenMod, but I'm right back where I started. The moboot menu will load and I can get into WebOS or ClockworkMod, but if I choose CyanogenMod then after it says "booting..." the screen will go black for a bit and then reboot.
Edit: I double checked the MD5 sums of the files I downloaded, just in case.
Click to expand...
Click to collapse
Hmm.... Maybe someone else can step in and help. It's strange, if you can get into moboot, webos and cwm, you should be able to get into android.
Good luck.
I installed moboot & ClockworkMod 6.x with the ACME installer.
I then booted to ClockworkMod and installed CM10.1 & gapps from there, as installing CM10.1 with the ACME installer as well just made it reboot over and over.
No remove the update-. Use gapps-jb-20130301-signed.zip, what version of cm were you on prior to this? Try to flash a different cm10.1.
Sent from my cm_tenderloin using xda app-developers app
chicle_11 said:
atamido said:
I installed the [ROM] [NIGHTLY] [JB] [4.2.2] CyanogenMod 10.1 nightly from milaq, and when I choose "boot CyanogenMod" from the moboot 0.3.8 menu, it continues with some blue text (loading boot/uimage, ramdisk, kernel), the screen goes black for a little bit, and then it reboots to the moboot menu again. Both WebOS and ClockworkMod load fine from the moboot menu.
so this is what I did:
Ran ACMEUninstaller, after which the moboot menu was gone
Mounted the Touchpad and copied these files to /cminstall: cm-10.1-20130601-UNOFFICIAL-tenderloin.zip, moboot_038-tenderloin.zip, update-CWM6_tenderloin-20121215.zip, update-gapps-jb-20130301-signed.zip
Ran ACMEInstaller3 and watched it install/reboot
!
Click to expand...
Click to collapse
Same thing with
moboot_038-tenderloin
update-CWM6_tenderloin-20121215
gapps-jb-20130301-signed
skz_tenderloin-2.00_jb_4.2.2-02JUNE2013-065943_Unsigned
The Touchpad comes into a boot loop and goes into moboot menu again and again. CWM6 starts correctly.
Any solutions ?
Click to expand...
Click to collapse
bernd5 said:
chicle_11 said:
Same thing with
moboot_038-tenderloin
update-CWM6_tenderloin-20121215
gapps-jb-20130301-signed
skz_tenderloin-2.00_jb_4.2.2-02JUNE2013-065943_Unsigned
The Touchpad comes into a boot loop and goes into moboot menu again and again. CWM6 starts correctly.
Any solutions ?
Click to expand...
Click to collapse
Maybe try another cm10.1 rom?
Click to expand...
Click to collapse
BitingChaos said:
I installed moboot & ClockworkMod 6.x with the ACME installer.
I then booted to ClockworkMod and installed CM10.1 & gapps from there, as installing CM10.1 with the ACME installer as well just made it reboot over and over.
Click to expand...
Click to collapse
I just realized I hadn't responded to this thread. The tip from BitingChaos got it done. With moboot and CWM working, I copied the mod and gapps to the folder as before, but booted into ClockworkMod to install it. Rebooted and it booted straight into Cyanogenmod.
What i did is put cm9 and then flash 10.1 from cwm
Sent from my Nexus 4 using xda app-developers app
same issue
I installed CM10.1 on my HP Touchpad and have been facing the same issue.
There was never a version of Android running on my touchpad ever before, so this was the first time.
Following were the steps I followed:-
Copied over the following 4 files to 'cminstall' folder on my touchpad:-
cm-10.1-20130809-UNOFFICIAL-tenderloin
gapps-jb-20130812-signed
moboot_038-tenderloin
update-cwm_tenderloin-1012
Got touchpad to recovery mode and ran ACMEInsaller. Post installation, the tablet came up with a 5 second down timer while showing a moboot menu. I kept the defaults and it restarted to the same menu. I selected it to boot into android and it restarted to the same menu.
Then I wiped off everything using 'AcmeUninstaller', followed the same installation process and was stuck with the same problem.
Did this 3 times with different 10.1 ROMs
Then got all my precious data wiped off after following
http://forum.xda-developers.com/showthread.php?t=1426244
anyhow, went ahead with CM10.1 installation and it happened again
Can someone please help.
I am not that techie... just followed the following liliputing tutorial (with updated files as mentioned above) and it isn't working...
http://liliputing.com/2012/01/how-to-install-android-4-0-on-the-hp-touchpad-cyanogenmod-9-alpha.html
Again, this was the 1st time I had ever attempted to install android on my touchpad.. are there any other per-requisites?
ronsom said:
I installed CM10.1 on my HP Touchpad and have been facing the same issue.
There was never a version of Android running on my touchpad ever before, so this was the first time.
Following were the steps I followed:-
Copied over the following 4 files to 'cminstall' folder on my touchpad:-
cm-10.1-20130809-UNOFFICIAL-tenderloin
gapps-jb-20130812-signed
moboot_038-tenderloin
update-cwm_tenderloin-1012
Got touchpad to recovery mode and ran ACMEInsaller. Post installation, the tablet came up with a 5 second down timer while showing a moboot menu. I kept the defaults and it restarted to the same menu. I selected it to boot into android and it restarted to the same menu.
Then I wiped off everything using 'AcmeUninstaller', followed the same installation process and was stuck with the same problem.
Did this 3 times with different 10.1 ROMs
Then got all my precious data wiped off after following
http://forum.xda-developers.com/showthread.php?t=1426244
anyhow, went ahead with CM10.1 installation and it happened again
Can someone please help.
I am not that techie... just followed the following liliputing tutorial (with updated files as mentioned above) and it isn't working...
http://liliputing.com/2012/01/how-to-install-android-4-0-on-the-hp-touchpad-cyanogenmod-9-alpha.html
Again, this was the 1st time I had ever attempted to install android on my touchpad.. are there any other per-requisites?
Click to expand...
Click to collapse
Well if you look at what your following its saying “STEP BY STEP GUIDE FOR CM9" if your following that guide it would only be correct if you follow it to the T. which is CM9 not CM10 or any 10.1. What you want to do if your following that guide and I know its a hassle.
You want to put all the correct things in it besides gApps which is moboot update cwm tenderloin 1012 along with cm9 and you can option in putting in gApps if you want but “since your going to flash cm10 right after" there's no point for cm9 gApps.
Next all you have to do is boot into webos taking that your starting fresh. Put those files in it. Then run the acmeinstaller3 command prompt then you'll boot and you should be running cm9 now.
Okay since now your running cm9 (which is more stable than cm10) go back into webos then put the 10.1 file that you want to have on your touchpad along with the correct gApps in cminstall reboot after
*notice only those two zips should be in there now.*
Then when you get to moboot toggle to clockworkmod then go to
apply zip from folder-cminstall-toggle to the 10.1 zip then open it then after it finishes installing go back to cm install and install gApps and it should be working.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
---------- Post added at 10:57 AM ---------- Previous post was at 10:55 AM ----------
And this has been answered numerous times before you just have to read I think I helped out 3 other people with the same problem already.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
reboot issue continues
[email protected] said:
Well if you look at what your following its saying “STEP BY STEP GUIDE FOR CM9" if your following that guide it would only be correct if you follow it to the T. which is CM9 not CM10 or any 10.1. What you want to do if your following that guide and I know its a hassle.
You want to put all the correct things in it besides gApps which is moboot update cwm tenderloin 1012 along with cm9 and you can option in putting in gApps if you want but “since your going to flash cm10 right after" there's no point for cm9 gApps.
Next all you have to do is boot into webos taking that your starting fresh. Put those files in it. Then run the acmeinstaller3 command prompt then you'll boot and you should be running cm9 now.
Okay since now your running cm9 (which is more stable than cm10) go back into webos then put the 10.1 file that you want to have on your touchpad along with the correct gApps in cminstall reboot after
*notice only those two zips should be in there now.*
Then when you get to moboot toggle to clockworkmod then go to
apply zip from folder-cminstall-toggle to the 10.1 zip then open it then after it finishes installing go back to cm install and install gApps and it should be working.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
---------- Post added at 10:57 AM ---------- Previous post was at 10:55 AM ----------
And this has been answered numerous times before you just have to read I think I helped out 3 other people with the same problem already.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I'm still struggling with this issue. I got to the point where Installation of ACMEInstaller3 and moboot_038-tenderloin.zip files which completed successfully then when I got to the moboot screen and chose to boot from Cyanogenmod, it keeps rebooting back to the moboot screen. I found your response to the similar problem above so I followed the instruction and placed both cm-10.1-20130808-EXPERIMENTAL-tenderloin-BLUETOOTH_TEST.zip and gApp in the cminstall folder of Touchpad while in USB mode then installed using clockworkmod option from the moboot screen. It cofirmed installation and I reboot Touchpad but it's continuing to repeat reboot process over and over again. Please help. I'm doing this from the fresh install with WebOS for the first time. Thanks in advance.
After you installed cm9? Give me a quick rundown on how your doing it. What type of computer your using
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
and it worked
- Have the zip files for ClockworkMod and AcmeInstaller applications in the 'cminstall' folder
- Copy the CynogenMod and other zip files gApps etc in a different folder (lets say android-setup)
- Reboot and install ClockworkMod
- Reboot and from the moboot, select install from sd card
- Navigate to the folder where you have the CM zip file and select the file. Confirm and install. This will work
- Now reboot and from moboot, select to install from sd card and select the gapps zip file install the google applications.
Hope this works for you
ronsom said:
- Have the zip files for ClockworkMod and AcmeInstaller applications in the 'cminstall' folder
- Copy the CynogenMod and other zip files gApps etc in a different folder (lets say android-setup)
- Reboot and install ClockworkMod
- Reboot and from the moboot, select install from sd card
- Navigate to the folder where you have the CM zip file and select the file. Confirm and install. This will work
- Now reboot and from moboot, select to install from sd card and select the gapps zip file install the google applications.
Hope this works for you
Click to expand...
Click to collapse
Okay so let's start with the basics.
Uninstall everything! you need to get *AcmeUninstaller* http://goo.im/devs/jcsullins/cmtouchpad/tools/
Hook up your touchpad to your desktop Put your touchpad in DFU mode.
(Restart and hold the volume up button)
Place AcmeUninstaller into the *Palm, Inc* folder
Open command prompt via search or find cmd
In cmd prompt you need to.
CD /Program files/Palm, inc
Next
novacom.exe boot mem:// < ACMEUninstaller
Now your touchpad should be removing all those files
*Boot back into webos on the touchpad and mount it*
Next Make sure you have the correct java installed. After you installed java
Install novacom https://code.google.com/p/universal-novacom-installer/downloads/list
Then install Nova com driver.
Next you want to get
*Acmeinstaller3*
*Clockwork mod*
*moboot*
AND THIS IS THE KEY RIGHT HERE!
*CM9 NIGHTLY* http://get.cm/?device=tenderloin
download the top one from this link.
(You can keep cyangenmod 10 and gApps in the android setup folder but you will be needing Cyangenmod 9 for the time being)
Open *my computer* on your desktop go to
*program files*
*palm, inc* now place Acmeinstaller3
Now open your touchpad and create a folder *cminstall*
Now what needs to be in this folder?
*Moboot*
*Clockwork mod* (update-cwm-tenderloin)
AND THIS IS THE KEY!
*CYANGENMOD 9*
you can have cyangenmod 10 and gApps for cyangenmod 10 in another folder say android install
*but the key is you need cyangenmod 9*
After putting those 3 files into cm install
Restart your touchpad and put into DFU MODE (restart and hold the volume up key)
Now on your desktop open up command prompt or cmd
Navigate to
CD /program Files/Palm, Inc
Next
novacom.exe boot mem:// < ACMEInstaller3
Now it should be loading up
Moboot
Clockwork mod
cm9
Once finished it should restart then boot into cyangenmod 9 it'll show the blue android powering up like he was in Dragonball.
After booting into cyangenmod 9 restart your touchpad hold the top button and cm will bring up options to restart.
Now boot into clockworkmod
then go to apply zip from files
Navigate to your android install folder that you put cyangenmod 10 and gApps in then unzip the files.
First do cyangenmod 10 the gApps after
Now reboot and it should load cyangenmod 10 it'll show the android face from angry to calm
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
No android keyboard
I followed your instruction above and I was able to install cyanogen9 then updated to cyanogen10 but now I'm seeing a error message "Unfortunately, Android keyboard has stopped." after it started up. So I'm not able to type in password for Wifi setup nor type anything into the address bar on the browser.
Cyanogen 10.1 version is what I have installed and gapps-jb-20130813-signed.zip is what I installed with it. I'm thinking I have the wrong gapps version. I think the correct version I need to install is gapps-jb-20130812-signed.zip. If this is correct assumption, how do I uninstall and reinstall the correct version? I don't want to screw up by trying to install this copy over the existing copy using Clockworks or is it safe?
Please help!
Minsway said:
I followed your instruction above and I was able to install cyanogen9 then updated to cyanogen10 but now I'm seeing a error message "Unfortunately, Android keyboard has stopped." after it started up. So I'm not able to type in password for Wifi setup nor type anything into the address bar on the browser.
Cyanogen 10.1 version is what I have installed and gapps-jb-20130813-signed.zip is what I installed with it. I'm thinking I have the wrong gapps version. I think the correct version I need to install is gapps-jb-20130812-signed.zip. If this is correct assumption, how do I uninstall and reinstall the correct version? I don't want to screw up by trying to install this copy over the existing copy using Clockworks or is it safe?
Please help!
Click to expand...
Click to collapse
That's good that I was able to instruct you on how to do it. I'm not too sure what went wrong. But it wouldn't be a good idea to flash an older gApps over a newer gApps can you navigate through the settings? Idk if you can uninstall it from the settings but I would try I haven't used android on my touchpad for awhile due to not having WiFi connection so my touchpad basically is a clock.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app