Related
Hello,
I'm not gonna panic, as I think Ive not bricked my phone YET.
Here is what I have done, I have a GALAXY S I9000.
Have been using it for quite some time now. 2 years ago, I have flashed it with - hardcore's kernel with the ClockworkMod Recovery - using Odin.
Today I decided to give Cyanogenmod a go, followed the steps here. - http://wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S:_Full_Update_Guide
Since I have the hardoce's kernel, I skipped this Installing the ClockworkMod Recovery - and moved on to - Flashing CyanogenMod.
I will go step by step from here.
Download the latest version of CyanogenMod.
Optional: Download the Google Apps for the device.
Place the CyanogenMod update.zip file on the root of the internal memory.
Optional: Place the Google Apps .zip on the root of the internal memory also.
Boot into the ClockworkMod Recovery.
Once the device boots into the ClockworkMod Recovery, use the side volume buttons to move around, and either the power button or the trackball to select.
Select the option to Wipe data/factory reset.
Then select the option to Wipe cache partition.
Select Install zip from sdcard.
done these, no problem so far.
[*]Select Choose zip from sdcard.
when I chose this, phone rebooted, it was so fast something may have come up and I didnt see.
Now I am stuck in a boot loop:
- Galaxy S I9000 samsung screen comes up, goes away for a second, comes up again.
- A page with code appearing from the bottom comes up really fast ( logo in the middle changes quickly) then it disappears.
- whole thing starts again.
UPDATE: I got a picture of the fast screen that comes up. : http://localhostr.com/files/b5NzFRy/2012-08-27 05.07.32.jpg
Some observations.
- I can go into download mode when opening it with the key combo.
- loop only stops when I unplug the battery
I need advice on what caused this and how to fix this, please help me.
edizarca said:
I need advice on what caused this and how to fix this, please help me.
Click to expand...
Click to collapse
Just flash it again ...see quick fix and solutions link below
xsenman said:
Just flash it again ...see quick fix and solutions link below
Click to expand...
Click to collapse
I cannot see what will help me on this page, but I understand how flashing again could work.
But how with the situation I have?
edizarca said:
I cannot see what will help me on this page, but I understand how flashing again could work.
But how with the situation I have?
Click to expand...
Click to collapse
are you not able to get into recovery? If only download than you need to get back to GB and than do a progressive update from GB to ICS to JB
Flash it again. From what I've heard, it only flashes the kernel the first time.
I had the same problem today with CM7 today. Just reboot in recovery and flash again cm zip, form there on everything is gonna run smooth!
edizarca said:
Hello,
I'm not gonna panic, as I think Ive not bricked my phone YET.
Here is what I have done, I have a GALAXY S I9000.
Have been using it for quite some time now. 2 years ago, I have flashed it with - hardcore's kernel with the ClockworkMod Recovery - using Odin.
Today I decided to give Cyanogenmod a go, followed the steps here. - http://wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S:_Full_Update_Guide
Since I have the hardoce's kernel, I skipped this Installing the ClockworkMod Recovery - and moved on to - Flashing CyanogenMod.
I will go step by step from here.
Download the latest version of CyanogenMod.
Optional: Download the Google Apps for the device.
Place the CyanogenMod update.zip file on the root of the internal memory.
Optional: Place the Google Apps .zip on the root of the internal memory also.
Boot into the ClockworkMod Recovery.
Once the device boots into the ClockworkMod Recovery, use the side volume buttons to move around, and either the power button or the trackball to select.
Select the option to Wipe data/factory reset.
Then select the option to Wipe cache partition.
Select Install zip from sdcard.
done these, no problem so far.
[*]Select Choose zip from sdcard.
when I chose this, phone rebooted, it was so fast something may have come up and I didnt see.
Now I am stuck in a boot loop:
- Galaxy S I9000 samsung screen comes up, goes away for a second, comes up again.
- A page with code appearing from the bottom comes up really fast ( logo in the middle changes quickly) then it disappears.
- whole thing starts again.
UPDATE: I got a picture of the fast screen that comes up. : http://localhostr.com/files/b5NzFRy/2012-08-27 05.07.32.jpg
Some observations.
- I can go into download mode when opening it with the key combo.
- loop only stops when I unplug the battery
I need advice on what caused this and how to fix this, please help me.
Click to expand...
Click to collapse
Installation Procedure for CM9
If you have CWM Recovery
Copy both zip files int internal SDCARD
Boot into recovery
Do a full wipe (data/factory,cache, dalvik)
Install zip from sdcard
Choose zip from sdcard
Select the ROM
You will get boot loop
Again boot into recovery
Install the same zip file one more time
Install google app
Do a full wipe again (data/factory,cache,dalvik)
Reboot your phone
Enjoy...
Hi,
I had the same pb coming from a GB
I think this pb is very common
1) DON'T WORRY !
2) Unplug the battery when bootlooping
3) Put the SGS in Recovery Mode (the CWM's version has changed)
4) Select the CM .zip and flash it AGAIN
5) When it's done, reboot system
This time, everything shoot be OK
Just be carefull with your IMEI (always have a backup of EFS folder !)
anukilimanoor said:
Installation Procedure for CM9
If you have CWM Recovery
Copy both zip files int internal SDCARD
Boot into recovery
Do a full wipe (data/factory,cache, dalvik)
Install zip from sdcard
Choose zip from sdcard
Select the ROM
You will get boot loop
Again boot into recovery
Install the same zip file one more time
Install google app
Do a full wipe again (data/factory,cache,dalvik)
Reboot your phone
Enjoy...
Click to expand...
Click to collapse
Thanks!, this method worked a treat :highfive:
Anyone have a trick yet for CM 10.1 v.22 Nightly, I keep getting a bootloop on all their versions except the original one. This is so frustrating because I have to keep going back to stock and then update to ICS.
kvarug01 said:
Anyone have a trick yet for CM 10.1 v.22 Nightly, I keep getting a bootloop on all their versions except the original one. This is so frustrating because I have to keep going back to stock and then update to ICS.
Click to expand...
Click to collapse
Same here, after the Samsung and CM logos, and splash animation, it says :
"Encryption unsuccessful.
Encryption was interrupted and can't complete. As a result, the data on your phone is no longer accessible.
To resume using your phone, you must perform a factory reset...."
After I tap Reset phone, it goes to CWM recovery.
Do the factory reset and the same thing occured in loop.
I came from JVU and CF root.
anukilimanoor said:
Installation Procedure for CM9
If you have CWM Recovery
Copy both zip files int internal SDCARD
Boot into recovery
Do a full wipe (data/factory,cache, dalvik)
Install zip from sdcard
Choose zip from sdcard
Select the ROM
You will get boot loop
Again boot into recovery
Install the same zip file one more time
Install google app
Do a full wipe again (data/factory,cache,dalvik)
Reboot your phone
Enjoy...
Click to expand...
Click to collapse
How long should the first boot take after following these steps? And does it have to be from SDCARD, because I can't get the rom onto my sd card, I can only do it via usb otg cable
---------- Post added at 05:11 AM ---------- Previous post was at 04:34 AM ----------
anukilimanoor said:
Installation Procedure for CM9
If you have CWM Recovery
Copy both zip files int internal SDCARD
Boot into recovery
Do a full wipe (data/factory,cache, dalvik)
Install zip from sdcard
Choose zip from sdcard
Select the ROM
You will get boot loop
Again boot into recovery
Install the same zip file one more time
Install google app
Do a full wipe again (data/factory,cache,dalvik)
Reboot your phone
Enjoy...
Click to expand...
Click to collapse
Does it have to be from the sdcard or can you do it from a flash drive via usb otg. I cannot get the rom onto my sd card
paradiselost28 said:
Hi,
I had the same pb coming from a GB
I think this pb is very common
1) DON'T WORRY !
2) Unplug the battery when bootlooping
3) Put the SGS in Recovery Mode (the CWM's version has changed)
4) Select the CM .zip and flash it AGAIN
5) When it's done, reboot system
This time, everything shoot be OK
Just be carefull with your IMEI (always have a backup of EFS folder !)
Click to expand...
Click to collapse
The same thing happend to me.
Just plug out the battery and flash again on cwm recovery.
Sent from my GT-I9000 using XDA Premium 4 mobile app
hi guys after having issu with TWRP ( after a flash via goo manager impossible to boot on it and it always boot on twrp after each restart...), i am wondering how can i replace it by cmw recovery again.
thanks
thi3um said:
hi guys after having issu with TWRP ( after a flash via goo manager impossible to boot on it and it always boot on twrp after each restart...), i am wondering how can i replace it by cmw recovery again.
thanks
Click to expand...
Click to collapse
What did you flash?
What I flash is not the problem
update cm9 aokp webos style to final buid =ok, but fc with Google play so clear data app but still have fc, so I decide to flash gapps again via goo manager but when I select flash rom goo manager tell me that I don't have a recovery script...
so I update twrp via goo manager =ok and finally I select my gapps zip with wipe cache and dalvik, it reboot and stuck in moboot loading twrp img. And then impossible to boot nothing, after many reboot, restart, pushing all the button it finally boot.
Now it work normally except if I boot on twrp.
Voilà
I want to go back to cwm, that's all.
thi3um said:
What I flash is not the problem
update cm9 aokp webos style to final buid =ok, but fc with Google play so clear data app but still have fc, so I decide to flash gapps again via goo manager but when I select flash rom goo manager tell me that I don't have a recovery script...
so I update twrp via goo manager =ok and finally I select my gapps zip with wipe cache and dalvik, it reboot and stuck in moboot loading twrp img. And then impossible to boot nothing, after many reboot, restart, pushing all the button it finally boot.
Now it work normally except if I boot on twrp.
Voilà
I want to go back to cwm, that's all.
Click to expand...
Click to collapse
DL CWM here http://goo.im/devs/jcsullins/cmtouchpad/testing/uImage.CWM6_tenderloin_20121204 . Then with an app like Rom toolbox lite copy and paste it into your boot folder , then delete the TWRP ulimage and edit your default recovery , and you should be good to go.
sstar said:
DL CWM here http://goo.im/devs/jcsullins/cmtouchpad/testing/uImage.CWM6_tenderloin_20121204 . Then with an app like Rom toolbox lite copy and paste it into your boot folder , then delete the TWRP ulimage and edit your default recovery , and you should be good to go.
Click to expand...
Click to collapse
ok, thanks buddy
what do you mean by edit your defaut recovery, i guess it's a text file to mod.
Yes below are 2 screenshots 1 with ES File explorer and the other with Rom Toolbox when you tap to open select open as Text and edit/change with RB text editor this is assuming you have Rom Toolbox lite or another text editor with root privileges.
Hope this helps.
Sent from my cm_tenderloin using Tapatalk 2
Yep found it with root explorer.
Ulmage
sstar said:
Yes below are 2 screenshots 1 with ES File explorer and the other with Rom Toolbox when you tap to open select open as Text and edit/change with RB text editor this is assuming you have Rom Toolbox lite or another text editor with root privileges.
Hope this helps.
Sent from my cm_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
When I went to boot drive I saw several ulmage files. Am I to delete all and replace with the one posted in this thread? Is this how I will delete TWRP?
horaceb said:
When I went to boot drive I saw several ulmage files. Am I to delete all and replace with the one posted in this thread? Is this how I will delete TWRP?
Click to expand...
Click to collapse
NO just delete the TWRP ulimage AFTER you have successfully copied/ placed your CWM their . Then edit the Android. default. recovery file .
I hope this makes it clearer.
If you have any other questions post or PM me.
Good luck.
The images shown are after I deleted TWRP and copied CWM
thi3um said:
hi guys after having issu with TWRP ( after a flash via goo manager impossible to boot on it and it always boot on twrp after each restart...), i am wondering how can i replace it by cmw recovery again.
thanks
Click to expand...
Click to collapse
funny , I have the exact same problem since yesterday and I cant get rid of TWRP in the boot menu even after using acmeuninstaller + webOS doctor.
Advice to everyone, do not install TWRP twice on this device. Goo manager is too lame to see its already there and for some reason, it messes up the boot manager.
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
Hello
I have the problem that I cannot update my i9000 from CyanogenMod 10.1.3 to 10.2.0. After the update, Cyanogenmod doesn’t start anymore. It gets stuck at the boot animation: The blue CyanogenMod-mascot within the round rotating arrow. I waited 15min for it to start, then I left the phone for 2h and it still didn’t start.
I did the update as follows:
First, I tried to update with the automatic updater from CyanogenMod, but that didn’t work. It aborted and restarted CyanogenMod 10.1.3.
So I tried it manually with ClockworkMod (v6.0.3.6):
- wipe data / factory reset
- wipe cache partition
- advanced -> wipe dalvik cache
This message was shown: E:unknown volume for path [/sd-ext]
Dalvik cache wiped.
- install zip -> choose zip from sdcard -> cm-10.2.0-RC1-galaxysmtd.zip
It aborted and the following message was shown:
This ROM uses an incompatible partition layout
Your /data will be wiped upon installation
Run this update.zip again to confirm install
- Did it again: install zip -> choose zip from sdcard -> cm-10.2.0-RC1-galaxysmtd.zip
Now the zip-file was installed completely.
- reboot system now
The result was that the phone got stuck at the boot animation.
Remarks:
- I didn’t do a backup of apps and data, because I didn’t have important data on the phone.
- I didn’t have root-rights in CM 10.1.3.
I tried it again with the stable version of CM 10.2.0. I didn’t have to install the zip twice anymore, but the phone still gets stuck at the boot animation. Wiping cache and dalvik cache again didn’t make it start.
I can still boot into ClockworkMod and it was also possible to go back to CM 10.1.3. Just CM 10.2 doesn’t start up.
What do I have to do to make CM 10.2 start up?
Thank you very much for your help.
Best regards
Tomy
@Tomy_Delmar
Tomy, CyanogenMod is already custom ROM, there is always root access on it
Try it this way:
download Gapps for CM10.2x (Android 4.3.x) and paste them on your external SD card
put the card in your phone
run it in recovery mode
wipe cache and dalvik cache
flash Gapps for 4.3
wipe again cache and dalvik cache.
reboot
Post if it worked.
Tomy_Delmar said:
Hello
I have the problem that I cannot update my i9000 from CyanogenMod 10.1.3 to 10.2.0. After the update, Cyanogenmod doesn’t start anymore. It gets stuck at the boot animation: The blue CyanogenMod-mascot within the round rotating arrow. I waited 15min for it to start, then I left the phone for 2h and it still didn’t start.
I did the update as follows:
First, I tried to update with the automatic updater from CyanogenMod, but that didn’t work. It aborted and restarted CyanogenMod 10.1.3.
So I tried it manually with ClockworkMod (v6.0.3.6):
- wipe data / factory reset
- wipe cache partition
- advanced -> wipe dalvik cache
This message was shown: E:unknown volume for path [/sd-ext]
Dalvik cache wiped.
- install zip -> choose zip from sdcard -> cm-10.2.0-RC1-galaxysmtd.zip
It aborted and the following message was shown:
This ROM uses an incompatible partition layout
Your /data will be wiped upon installation
Run this update.zip again to confirm install
- Did it again: install zip -> choose zip from sdcard -> cm-10.2.0-RC1-galaxysmtd.zip
Now the zip-file was installed completely.
- reboot system now
The result was that the phone got stuck at the boot animation.
Remarks:
- I didn’t do a backup of apps and data, because I didn’t have important data on the phone.
- I didn’t have root-rights in CM 10.1.3.
I tried it again with the stable version of CM 10.2.0. I didn’t have to install the zip twice anymore, but the phone still gets stuck at the boot animation. Wiping cache and dalvik cache again didn’t make it start.
I can still boot into ClockworkMod and it was also possible to go back to CM 10.1.3. Just CM 10.2 doesn’t start up.
What do I have to do to make CM 10.2 start up?
Thank you very much for your help.
Best regards
Tomy
Click to expand...
Click to collapse
As the partition layout is different in cm10.2, you should flash it at least 2 times and wait for system to be stable for about 15-20 minutes
Tetakpatak and Rohitdahiya, thanks for the reply and advice!
In my previous post, I forgot to mention that I installed CyanogenMod without the Gapps. I’d like to try if an android-phone without the Gapps is still useful. Somehow I don’t like the data-collecting-mania of Google.
I tried again the update from CM 10.1.3 to 10.2:
- I downloaded cm-10.2.0-galaxysmtd.zip again and copied it to the internal SD-card of the phone.
- Restarted the phone into ClockworkMod recovery.
- wipe data / factory reset
- wipe cache partition
- wipe dalvik cache
- install zip -> choose zip from sdcard -> cm-10.2.0-galaxysmtd.zip
- install zip -> choose zip from sdcard -> cm-10.2.0-galaxysmtd.zip
(Did it twice. Don’t know if necessary.)
Didn’t install Gapps.
- wipe cache partition
- wipe dalvik cache
- reboot system now
Unfortunately CM still gets stuck at the boot animation. The arrow has been rotating for over an hour now.
To my knowledge the Gapps are not mandatorily required to install CM. I could install CM 10.1.3 without the Gapps without any problems.
Could a full-wipe solve my problem?
ClockworkMod -> mounts and storage -> format /system …?
I have never done this before.
Or is there something else I can do?
Regards
Tomy
Tomy_Delmar said:
Tetakpatak and Rohitdahiya, thanks for the reply and advice!
In my previous post, I forgot to mention that I installed CyanogenMod without the Gapps. I’d like to try if an android-phone without the Gapps is still useful. Somehow I don’t like the data-collecting-mania of Google.
I tried again the update from CM 10.1.3 to 10.2:
- I downloaded cm-10.2.0-galaxysmtd.zip again and copied it to the internal SD-card of the phone.
- Restarted the phone into ClockworkMod recovery.
- wipe data / factory reset
- wipe cache partition
- wipe dalvik cache
- install zip -> choose zip from sdcard -> cm-10.2.0-galaxysmtd.zip
- install zip -> choose zip from sdcard -> cm-10.2.0-galaxysmtd.zip
(Did it twice. Don’t know if necessary.)
Didn’t install Gapps.
- wipe cache partition
- wipe dalvik cache
- reboot system now
Unfortunately CM still gets stuck at the boot animation. The arrow has been rotating for over an hour now.
To my knowledge the Gapps are not mandatorily required to install CM. I could install CM 10.1.3 without the Gapps without any problems.
Could a full-wipe solve my problem?
ClockworkMod -> mounts and storage -> format /system …?
I have never done this before.
Or is there something else I can do?
Regards
Tomy
Click to expand...
Click to collapse
First of all, don't forget to quote the user whom you want to contact, because he don't get any notification until you quote. I was just checking around the questions and thus I saw this.
Sometimes, there is requirement of g-apps for the core system to be working ( Not sure in case of cm10.2). Try with g-apps (you may choose light package).
In my opinion, it should work. If not, try from the start ( flashing gingerbread with Odin with repartition ticked, then its root and finally cm10.2 from recovery)
Also make sure your handset is i9000 and you are using cm10.2 for the same.
And finally, All the best
CM doesn't neccesarily need Gapps to boot up. In fact most custom roms don't - they are still usable, just that everything Google-related doesn't work.
Its a bit odd seeing as how you've pretty much done what I would have done if I was installing CM to a Galaxy S. I can't think of any reason why it wouldn't work.
As far as I know as well, formatting /system is more of a last-resort method, not something you'd immediately do.
However, I had a similar problem installing a rom onto my tablet - different device, I know, but try this anyway and see if you get anywhere:
1.) Go back into recovery if its still bootlooping
2.) Wipe data, cache, Dalvik (and this is after you've flashed the CM10.2 zip twice like you did)
3.) Reboot device without flashing Gapps - this is to see if it boots up.
Let us know what happens.
Sent from my GT-P7510 using Tapatalk
Tomy_Delmar said:
In my previous post, I forgot to mention that I installed CyanogenMod without the Gapps. I’d like to try if an android-phone without the Gapps is still useful. Somehow I don’t like the data-collecting-mania of Google.
Click to expand...
Click to collapse
Tomy, now it is getting clear- of course, I tought you already had Gapps on your CM10.1.3 installed so in such case they would definitely need to be updated to 4.3
Yes, the ROM shouold work perfectly fine also without Gapps
Your workflow sounds correct, but just to make sure: after first attempt to flash CM10.2 build, there should be a warning that all your data will be wiped, right? After that you must again choose the option "install zip" and install CM10.2. It will work this time.
If it doesn't work, download again the CM10.2 zip as it may be corrupted file. BTW, I didn't like that build for several reasons and returned to RC version.
If nothing helps, flash back your CM10.1.3 and restore your nandroid backup if important files were there. If the downgrade won't work for different partition of the /system, use my unbricking guide and revert to stock, then to CM10.1.3, then to CM10.2.
Keep step by step on the guide if you use it, it has important points to control before flashing. Flashing with re-partition needs always a PIT file, or with other words: without that file re-partition option mustn't be checked. Doing it simply by clicking the re-partition (like @Rohitdahiya adviced you to) without a PIT file checked under "PIT" would brick your i9000.
Soryuu said:
However, I had a similar problem installing a rom onto my tablet - different device, I know, but try this anyway and see if you get anywhere:
1.) Go back into recovery if its still bootlooping
2.) Wipe data, cache, Dalvik (and this is after you've flashed the CM10.2 zip twice like you did)
3.) Reboot device without flashing Gapps - this is to see if it boots up.
Let us know what happens.
Click to expand...
Click to collapse
Unfortunately, Wiping data, cache and Dalvik cache again after I had flashed CM 10.2 didn’t make it start.
tetakpatak said:
Tomy, now it is getting clear- of course, I tought you already had Gapps on your CM10.1.3 installed so in such case they would definitely need to be updated to 4.3
Yes, the ROM shouold work perfectly fine also without Gapps
Your workflow sounds correct, but just to make sure: after first attempt to flash CM10.2 build, there should be a warning that all your data will be wiped, right? After that you must again choose the option "install zip" and install CM10.2. It will work this time.
If it doesn't work, download again the CM10.2 zip as it may be corrupted file. BTW, I didn't like that build for several reasons and returned to RC version.
If nothing helps, flash back your CM10.1.3 and restore your nandroid backup if important files were there. If the downgrade won't work for different partition of the /system, use my unbricking guide and revert to stock, then to CM10.1.3, then to CM10.2.
Keep step by step on the guide if you use it, it has important points to control before flashing. Flashing with re-partition needs always a PIT file, or with other words: without that file re-partition option mustn't be checked. Doing it simply by clicking the re-partition (like @Rohitdahiya adviced you to) without a PIT file checked under "PIT" would brick your i9000.
Click to expand...
Click to collapse
When I tried to flash CM 10.2 the first time – at that time RC1 was the newest version – I was asked to flash it a second time, which I did. To be precise, the following message was shown:
This ROM uses an incompatible partition layout
You /data will be wiped upon installation
Run this update.zip again to confirm install
This message hasn’t been shown again since then. I flashed CM 10.1.3 again and tried to flash 10.2 a second time, but the message wasn’t shown again.
Going back to CM 10.1.3 worked without any problem.
------------------------------------------
Now I have CM 10.2 on my phone and it starts normally
I flashed Stock-Android 2.3.6 with Odin (v1.82). Tetakpatak, thank you for the excellent guide and the video! As written in the guide, I used "s1_odin_20100512.pit" as PIT-file.
(I executed Odin on an old computer with Windows XP 32bit, as the guide says Odin 1.82 works better with Win XP.)
Then I installed CM 10.2 over Stock-Android 2.3.6. I followed the official instructions:
http://wiki.cyanogenmod.org/w/Install_CM_for_galaxysmtd?setlang=en
(I executed Heimdall on my new computer with Windows 7. Heimdall 1.4RC2 doesn’t work on Win XP. If one executes Odin and Heimdall on the same PC, I could imagine this could lead to confusion, because Odin needs the Samsung-USB-drivers and Heimdall needs WinUSB. I’m not sure if this really leads to problems. But one should keep that in mind.)
I didn’t flash CM 10.1.3 before 10.2, because I didn’t need to restore a nandroid backup previously made with CM 10.1.3. There were no important data on the phone.
Many thanks to all who gave me advice and helped my solving the problem!
Tomy
HELP MEEE
I put on TWRP 2.6.3.0 on my Nexus 5 (I used towerlroot succesfully) and i tried wiping as you should, i noticed i loaded an old twrp so i quickly powerd off my Nexus5. When i loaded, every app had a "Google play services has stopped" error and some would force close. I reloaded TWRP and tried to flash cyanogenmod and gapps, succelfully they installed. Now cyanogenmod is stuck in the boot animation and i dont know to update TWRP, HELPP PLEASSE!!!!
Pure_Android said:
I put on TWRP 2.6.3.0 on my Nexus 5 (I used towerlroot succesfully) and i tried wiping as you should, i noticed i loaded an old twrp so i quickly powerd off my Nexus5. When i loaded, every app had a "Google play services has stopped" error and some would force close. I reloaded TWRP and tried to flash cyanogenmod and gapps, succelfully they installed. Now cyanogenmod is stuck in the boot animation and i dont know to update TWRP, HELPP PLEASSE!!!!
Click to expand...
Click to collapse
This is the forum for the original Galaxy S, not the Nexus 5, sorry mate
However I think your problem can be fixed by doing a full data/cache wipe so it might be worth a shot
Flash Boot.Img. This might solve the bootloop!
I think, You just need to flash the boot.img (available in the Cynogen Bundle Zip Folder) after installing Cynogen Mod. Me too got stuck on the animation part for a long time. Then I found out this:
CyanogenMod builds for endeavoru currently do NOT support any bootloader version number below: HBOOT 1.28. As the device is S-ON (security-on bootloader), for a working installation you must extract the boot.img from the installer zip and run fastboot flash boot boot.img from fastboot mode.
Source: Cynogen Mod Wiki
Pure_Android said:
I put on TWRP 2.6.3.0 on my Nexus 5 (I used towerlroot succesfully) and i tried wiping as you should, i noticed i loaded an old twrp so i quickly powerd off my Nexus5. When i loaded, every app had a "Google play services has stopped" error and some would force close. I reloaded TWRP and tried to flash cyanogenmod and gapps, succelfully they installed. Now cyanogenmod is stuck in the boot animation and i dont know to update TWRP, HELPP PLEASSE!!!!
Click to expand...
Click to collapse
Which version of CyanogenMod are you using?
I tried to install TWRP from Goo Manager. After when the Touchpad rebooted, I had lost my ClockworkMod and there was no TWRP item. The only recovery left was WebOS recovery. Any suggestions?
Thanks
Gil1957 said:
I tried to install TWRP from Goo Manager. After when the Touchpad rebooted, I had lost my ClockworkMod and there was no TWRP item. The only recovery left was WebOS recovery. Any suggestions?
Thanks
Click to expand...
Click to collapse
Extract the zip and place the uImage.TWRP into the boot folder. Delete uImage.Clockworkmod if it's there. Then reboot.
Is there any instructions on how to install CWM or TWRP recovery? I installed milaq's build using instructions in this thread: http://forum.xda-developers.com/showthread.php?t=2542353
But someone I don't have the CWM or TWRP installed. As a result, in the moboot menu, I can't see a reboot into recovery and can't install any updates either.
I just answered that in the above post. Unzip the install zip. Name the image file.... In your case uImage.TWRP copy it into boot folder.
vishnumrao said:
Is there any instructions on how to install CWM or TWRP recovery? I installed milaq's build using instructions in this thread: http://forum.xda-developers.com/showthread.php?t=2542353
But someone I don't have the CWM or TWRP installed. As a result, in the moboot menu, I can't see a reboot into recovery and can't install any updates either.
Click to expand...
Click to collapse
/boot is possibly too full
Either choose CWM or TWRP and remove one or the other (be sure to employ the recovery specific to the ROM... see the specific ROM thread for more info)
You can use 'Root Browser' in ROM Toolbox Lite app (to copy, paste, move, delete uImage files from the recovery zips to or from /boot)
woodytrain said:
/boot is possibly too full
Either choose CWM or TWRP and remove one or the other (be sure to employ the recovery specific to the ROM... see the specific ROM thread for more info)
You can use 'Root Browser' in ROM Toolbox Lite app (to copy, paste, move, delete uImage files from the recovery zips to or from /boot)
Click to expand...
Click to collapse
If /boot has adequate then you may want to to copy the TWRP installer zip file into the /cminstall folder in WebOS and use ACMEInstaller on your PC to reinstall it.