Related
I'm new to using non stock ROMs and have heard good things about the Cyanogenmod and wanted to give it a try. I rooted my phone using Super One Click, I installed Clockworkmod to install the ROM and backup my settings, then I got the stable version of Cyanogenmod for my phone HTC Hero CDMA (update-cm-6.0.0-Heroc-signed.zip). I then followed the steps from the WIKI I updated the Radio, wiped my phone's data, then the cache, I selected the ROM to install from the root directory of my SD card, let it run through then told it to reboot the system. thats where the problem shows up it comes to the first HTC screen and will just sit there forever I even tried leaving it on overnight. I tried to flash it with different versions of Cyanogenmod and all had the same result, however I was able to get a version of damagecontrol to flash correctly on my phone so I know its not a brick.
I have searched quite a few posts but have not found anything that helps I have tried wiping multiple times and even wiped Dalvik cache. I ran a logcat to see if it might help me debug whats going on and it appears to be looping through the same things over and over I rebooted it again and had the same results. I can supply any info needed from the logcat needed but not sure what parts might help.
the different versions of ROMs I have tried to use are:
update-cm-6.0.0-Heroc-RC1-signed
update-cm-6.0.0-Heroc-signed
update-cm-6.1.0-RC1-Heroc-signed
Also tried Cyanogenmod nightly 87, 95, & 99
fresh-cdma-hero-1.1
DamageControlv2.08.1
adrazar said:
I'm new to using non stock ROMs and have heard good things about the Cyanogenmod and wanted to give it a try. I rooted my phone using Super One Click, I installed Clockworkmod to install the ROM and backup my settings, then I got the stable version of Cyanogenmod for my phone HTC Hero CDMA (update-cm-6.0.0-Heroc-signed.zip). I then followed the steps from the WIKI I updated the Radio, wiped my phone's data, then the cache, I selected the ROM to install from the root directory of my SD card, let it run through then told it to reboot the system. thats where the problem shows up it comes to the first HTC screen and will just sit there forever I even tried leaving it on overnight. I tried to flash it with different versions of Cyanogenmod and all had the same result, however I was able to get a version of damagecontrol to flash correctly on my phone so I know its not a brick.
I have searched quite a few posts but have not found anything that helps I have tried wiping multiple times and even wiped Dalvik cache. I ran a logcat to see if it might help me debug whats going on and it appears to be looping through the same things over and over I rebooted it again and had the same results. I can supply any info needed from the logcat needed but not sure what parts might help.
the different versions of ROMs I have tried to use are:
update-cm-6.0.0-Heroc-RC1-signed
update-cm-6.0.0-Heroc-signed
update-cm-6.1.0-RC1-Heroc-signed
Also tried Cyanogenmod nightly 87, 95, & 99
fresh-cdma-hero-1.1
DamageControlv2.08.1
Click to expand...
Click to collapse
try this:
using a rom that works flash a new recovery image using ROM Manager (find it in the market)
Tell ROM Manager to flash the recovery for ClockworkMod 2.5.0.1
Then Reboot to recovery.
**********NANDROID FIRST!!*********
Starting the flash:
1. Choose the "Wipe data/factory reset" then click "wipe cache partition"
2. Choose "install zip from sdcard" and choose "choose zip from sdcard"
3. Pick the zip file with the CM6 make sure it completes and the installer confirms that it is complete.
4. Reboot phone. This might take more then 5 mins on the initial boot, when it boots up all the way and everything has loaded, do one more reboot to clear out the cache from the initial boot and you are good to go
**If this doesnt work for you, follow step one, select a DIFFERENT ROM, reboot, then reboot into recovery, then wipe again, and flash back CM6.
I tried this, I already had Rom Manager installed but checked to make sure it was all up to date, flashed it to 2.5.0.1 and rebooted to recovery. I wiped the data and cache and installed the CM6 and rebooted with teh same results of it being stuck at the HTC screen and logcat showed it cycling through the same actions over and over, I then tried to just reboot it and it did same thing. I then wiped and installed a different ROM (the Damage Control one) and it worked fine got all the way booted up. I then rebooted to the recovery manager again, wiped and reinstalled with the CM6and had the same results as the first time. out of curiosity I even tried installing the damage control and then installed CM6 without the wipe and it still did not work.
adrazar said:
I tried this, I already had Rom Manager installed but checked to make sure it was all up to date, flashed it to 2.5.0.1 and rebooted to recovery. I wiped the data and cache and installed the CM6 and rebooted with teh same results of it being stuck at the HTC screen and logcat showed it cycling through the same actions over and over, I then tried to just reboot it and it did same thing. I then wiped and installed a different ROM (the Damage Control one) and it worked fine got all the way booted up. I then rebooted to the recovery manager again, wiped and reinstalled with the CM6and had the same results as the first time. out of curiosity I even tried installing the damage control and then installed CM6 without the wipe and it still did not work.
Click to expand...
Click to collapse
Find a new download of CM6, the one you downloaded was corrupt, try finding the thread, its in Development so find the extreme blue or redglass version.
I tried both the Extremely Blue CM6 Build (EXTBLUE_09NOV.zip) and the Red Glass CM6 Build (REDGLASS_09NOV.zip) that I got from the development area, a poste named
[ROM] (UPDATED 09-NOV) FroYo 2.2 - CM6 Extremely Blue, BlackMod, Red, Purple, Vanilla
the results as far as it looks are exactly the same as when I tried the other ROMs. I know two lines that kinda stand out to me in the endlessly repeating messages I get from logcat are:
E/dalvikvm( 326): Unable to extract+optimize DEX from '/system/framework/framework.jar'
D/dalvikvm( 326): Unable to process classpath element '/system/framework/framework.jar'
I'm not fully sure if these are the issue or if it is just random information about it failing to load the ROMs.
Does anyone know what those error messages could be caused by or a way to get around this issue?
adrazar said:
I tried both the Extremely Blue CM6 Build (EXTBLUE_09NOV.zip) and the Red Glass CM6 Build (REDGLASS_09NOV.zip) that I got from the development area, a poste named
[ROM] (UPDATED 09-NOV) FroYo 2.2 - CM6 Extremely Blue, BlackMod, Red, Purple, Vanilla
the results as far as it looks are exactly the same as when I tried the other ROMs. I know two lines that kinda stand out to me in the endlessly repeating messages I get from logcat are:
E/dalvikvm( 326): Unable to extract+optimize DEX from '/system/framework/framework.jar'
D/dalvikvm( 326): Unable to process classpath element '/system/framework/framework.jar'
I'm not fully sure if these are the issue or if it is just random information about it failing to load the ROMs.
Click to expand...
Click to collapse
adrazar said:
Does anyone know what those error messages could be caused by or a way to get around this issue?
Click to expand...
Click to collapse
What recovery are you using?
I use Rom Manager (clockwork mod) for installing the ROMs and its currently flashed to version 2.5.0.1 to recover my phone to the way it was before I flashed to to the cyanogenmod I use nandroid
adrazar said:
I use Rom Manager (clockwork mod) for installing the ROMs and its currently flashed to version 2.5.0.1 to recover my phone to the way it was before I flashed to to the cyanogenmod I use nandroid
Click to expand...
Click to collapse
That's probably the problem, try the 1.7 Darch RA, much better IMHO
Also ive noticed sometimes when I download a rom onto my computer for some reason it doesnt download the whole file correctly. So just make sure that when you download your rom to your computer the the size of the file is correct.If the rom is 50 mb make sure your download is the same.
I found a post that I believe I got that one from (RA-Darchstar.img) but it is an img file and i am having trouble getting that to install. i found another post elsewhere telling me to use commands from the SDK, it said to use
cd C:\android-sdk-windows\tools
adb devices
adb shell
flash_image recovery /sdcard/RA-Darchstar.img
exit
adb shell reboot recovery
which seems like it should work however when I do the flash_image recovery /sdcard/RA-Darchstar.img it tells me that the flash_image cannot be found. is this the wrong command line? and i do have the file on my phone's SD card in the root directory. or is there another way to get the 1.7 Darch RA?
never mind on my last question I figured it out, I wasn't in the Recovery program I already had when trying to do it. I got the 1.7 Darch RA on and working then tried to flash some of the ROMs again and every one of them failed with the same logcat errors as before.
Try backing up ur SD then taking out ur SD and formatting it on ur CPU then put it back in ur phone and format it threw the recovery I have a 28 MB swap and the rest for the system them go to ext and upgrade/update ur ext from ext2 to ext3 then try and flash CM6.1 hope this helps good luck.
Root-Hack-Mod-Always™
I formatted my card via the computer, formatted everything that RA-Darchstar will let me format, I then set up the partitions and upgraded to ext3, and then copped the CM6.1 to the phone and installed it (also tried EXTBLUE_09NOV). the end result was the same as each other time I have tried to install any of them CM6 ROMs.
Ok I ended up getting it to work by following some of the things I read on
http://forum.cyanogenmod.com/topic/...-cm-build-but-cm-6-nightly-tests/page__st__20
the part where they told this other person to extract the framework.jar to the PC and point adb to it.
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
Hi all,
What is the best way to take the TP from CM7 to one of the latest bleeding edge 4.2 or 4.3 builds?
I've been pouring over the forum for three days now and am unsure how to proceed.
I have so many tabs open I'm waiting for Chrome to crash and tell me to go pound sand.
CM7 has been on it since I got ahold of way back in December of 2011. (time for an update, ya think?)
My idea to to fully wipe it but I haven't found a definitive method to do this.
All my data is backed up and I did a nandroid also. So a complete full wipe is very doable.
Current versions: Moboot 0.3.2, CWM v5.0.2.6, and I think that the ACME is at the first release.
WebOS is at whatever version came on it, never used it.
I've read most of RolandDeschain79's "How-to's" and understand the need for re-partitioning for JB,
I'm just not yet sure what's the best path.
(BTW, kudos to Roland for some very informative info and great videos!)
I've got some time on my hands due to lack of work and thought I could give JB some serious testing.
Thanks Gang,
_mr
I'm on the same boat.
Success!
Well, finally got it, not properly sequenced and a boot loop at first, but installed and running. Very smooth so far...
I most definitely did not get the sequence correct, mostly due to not fully understanding how to use CWM6.
Moboot to v0.3.5 from 0.3.2
CWM to v6.0.3.6 <-- Datamedia version 20130926 per milaq's post.
CM 10.2 Nightlies <-- I used "cm-10.2-20131009-UNOFFICIAL-tenderloin.zip"
GApps - JB - 20130813
Here's what I came away with. (Keep in mind I was going for a total wipe of CM7 and had everything backed up.)
1.) The absolute need to re-partition per milaq's post.
I used 'Tailor' with the help of RolandDeschain79's great videos. Thanks Roland!
I set system @ 640MB, re-sized ../media to 8GB, and the remainder went to ../data. (Had to do this twice due to a misstep on my part.)
Tailor is a great app, gotto go find a donate button for that one...
2.) Copied the following to SDCard via WebOS:
update-cm-10.2-20131011-UNOFFICIAL-tenderloin.zip
update-gapps-jb-20130813-signed.zip
update-moboot_0.3.5.zip
update-recovery-clockwork-datamedia-6.0.3.6-20130926-tenderloin.zip
I added/renamed all with the "update-" prefix out of habit. (Perhaps I should have left out CM10.2 until after ACME3 and Tailor.)
2a.) Rebooted to CWM5 recovery.
3.) Flashed CWM6 from v5.0.2.6. This didn't go right. Complained about 'no root' until I reflashed it again later under v6.
Formatted /cache, /data, /system. I did not perform a 'wipe data/factory reset'.
4.) Tried flashing Moboot v0.3.5 with CWM6. Kept aborting. (Didn't take until I ran ACMEInstaller3.)
5.) Ran ACMEUinstaller via Novacom. (Maybe I didn't need to???)
The ACME files I used came from JCSullins goo.im section - Thanks JC!
6.) Ran ACMEInstaller3. Oops. Wiped out all the partitioning I did with Tailor and then installed all the zips in ../cminstall.
At least Moboot v0.3.5 took.
7.) Re-partitioned with Tailor again.
8.) Re-flashed CWM6 - No Root message went away.
8a.) Rebooted to CWM6 recovery.
9.) Formatted /cache, /data, /system again - just for grins.
Re-flashed cm-10.2-20131011-UNOFFICIAL-tenderloin.zip
Rebooted, letting CM load.
9a.) Bootloop...
10.) Booted to WebOS and copied over cm-10.2-20131009-UNOFFICIAL-tenderloin.zip
Rebooted into CWM6.
11.) Flashed the 20131009, rebooted and Viola! it took. Setup the accounts, tested the Wi-Fi. and went to bed...
As you can see I definitely had the sequence wrong, but it was way late for me but like a dog with a bone.
I wasn't going to bed until I had CM10.2 on this puppy.
_mr
Hi guys I'm running cm10.2 Nightly 13/102013 and have lost both Cwm and the Twrp. I do not know how I've done it and need to get one of them back so I can update the rom. I have installed goo manager and when it tells me that there is an update I download it as usual but then it just reboots only giving me webos or webos recovery and CyanogenMod it is giving me no other options, I have downloaded the openscriptrecovery within goo manager and still nothing. Any help with this would be very much appreciated as I do not want to wipe it clean and doctor it unless I really have to.
garydclarke said:
Hi guys I'm running cm10.2 Nightly 13/102013 and have lost both Cwm and the Twrp. I do not know how I've done it and need to get one of them back so I can update the rom. I have installed goo manager and when it tells me that there is an update I download it as usual but then it just reboots only giving me webos or webos recovery and CyanogenMod it is giving me no other options, I have downloaded the openscriptrecovery within goo manager and still nothing. Any help with this would be very much appreciated as I do not want to wipe it clean and doctor it unless I really have to.
Click to expand...
Click to collapse
same for me, how do you have resolveed?
EDIT: i have to reinstall CWM by novacom from terminal.
If your touchpad boots into 10.2 automatically each time after flashing 10.2 (without going into moboot menu for choice of webOS or recovery even though you have set a count down time previously), use any file explorer with root rights to access /boot and delete or rename the file moboot.next - if you open this file using any text editor, you will most probably find it contains a single word 'cyanogen', telling moboot to boot this the 'next' time.
Copied from another thread
I've been trying to install milaq's 4.4 ROM on my Touchpad and I'm getting a bit stuck.
I've removed my previous 4.0.4 build so that I could start fresh and get my head around the data/media build. I've tried following the text guide and Roland's video guides but keep getting stuck at the same point.
I put the following files in the "cminstall" folder on my touchpad and ran ACMEinstaller5M:
cm-11-20140223-UNOFFICIAL-tenderloin
gapps-kk-20140105
recovery-clockwork-6.0.4.7-tenderloin
moboot_038-tenderloin
update-cm-tenderloin-data_resize_12228-0.1
So far I get the moboot menu and am able to get into the CWM-Based Recovery v6.0.4.7. This is where I'm stumped, I have no idea how to install the milaq ROM. I've had experience putting various CM Android builds on different devices (HD2, Defy+, Touchpad) but I'm struggling with this one. I know that I won't be able to install it the way I'm used to but I've tried searching and can't find what I'm supposed to do next.
I know this is a bit of a simple request but could anyone help me out with the next step? Once I'm past that, it'll be plain sailing I'm sure.
Thanks in advance.
yeoldgreat1 said:
I've been trying to install milaq's 4.4 ROM on my Touchpad and I'm getting a bit stuck.
I've removed my previous 4.0.4 build so that I could start fresh and get my head around the data/media build. I've tried following the text guide and Roland's video guides but keep getting stuck at the same point.
I put the following files in the "cminstall" folder on my touchpad and ran ACMEinstaller5M:
cm-11-20140223-UNOFFICIAL-tenderloin
gapps-kk-20140105
recovery-clockwork-6.0.4.7-tenderloin
moboot_038-tenderloin
update-cm-tenderloin-data_resize_12228-0.1
So far I get the moboot menu and am able to get into the CWM-Based Recovery v6.0.4.7. This is where I'm stumped, I have no idea how to install the milaq ROM. I've had experience putting various CM Android builds on different devices (HD2, Defy+, Touchpad) but I'm struggling with this one. I know that I won't be able to install it the way I'm used to but I've tried searching and can't find what I'm supposed to do next.
I know this is a bit of a simple request but could anyone help me out with the next step? Once I'm past that, it'll be plain sailing I'm sure.
Thanks in advance.
Click to expand...
Click to collapse
I just inherited an already rooted/android touch pad, so I'm in your same shoes right now. So i'm following close! haha.
I'm very new to the whole webos stuff here, but very experienced with rooting android.
But at this point, don't you just start flashing the .zips in clockwork after a full wipe (wipe factory, cache, davlik)?
BRUTAL BROCK said:
I just inherited an already rooted/android touch pad, so I'm in your same shoes right now. So i'm following close! haha.
I'm very new to the whole webos stuff here, but very experienced with rooting android.
But at this point, don't you just start flashing the .zips in clockwork after a full wipe (wipe factory, cache, davlik)?
Click to expand...
Click to collapse
That's what I thought but the ACMEinstaller wipes everything in the cminstall folder. Also, CWM only has the option to install zips from the sdcard which isn't there.
AcmeInstaller won't install the zip that resizes your partitions, and when you flash a data/media rom, the sdcard or media partitions are only accessible thru the rom itself so you won't be able to see them in recovery.
I think you will have to start again. Installing a data/media rom from a fresh install is, to be honest, a pain in the ass! You need to have a non-data/media build installed, ie. Jelly Bean/CM10.x, then resize partitions, etc, etc.
If you want to install kitkat from a fresh start, go for flintman's non-data/media version in the link in this post, and this recovery (20121215). Rename rom update-xxx, same for recovery, include moboot, and also have appropriate gapps to flash.
Hope this helps.
Oh yeah, and don't use AcmeInstaller5M, use the one ending in 5E =)
Data media install guide
Additional resources:
[ROM GUIDE] How to install Android on the HP TouchPad "The Easy Way"
[ROM GUIDE] How to install Android 4.4.2 Data Media builds on the HP TouchPadhttp://forum.xda-developers.com/showpost.php?p=42505399&postcount=2http://forum.xda-developers.com/showpost.php?p=42505399&postcount=2
RolandDeschain79 said:
You can't install CM11 data media builds with the ACMEInstaller. Here is my newest thread that explains how to get them fully installed. Please leave some feedback once you get it setup. :highfive:
[ROM GUIDE] How to install Android 4.4.2 Data Media builds on the HP TouchPad
Click to expand...
Click to collapse
That guide has been really helpful so far. I'm stuck at the last bit though.
I've installed PhilZ Clockworkmod but I don't know what to do from there. When I turn on the USB Drive, my PC can only see one SDcard (the WebOS one it sees normally) so I can't copy over the CM11 files to the Android one.
Any ideas?
If anyone is still having problems, this thread helped me. The instructions are in post #7 but you should read the preceding posts for background info.