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
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?
Hi !
I have a 32 Gb Touchpad on CM10.1 and i'd like to upgrade on CM11 with Milaq ROM.
So, i downloaded The_apes Flashable zip (this one : sys_512mb_data_plus_24576mb-signed.zip) and i flash it with ClockworkMod 5.x. I've got 2 errors like this.
After that, i flashed with the new ClockworkMod 6.x, but, now, when i want to flash ROM, i've got only 0/ and obb/ folders. I can't acces to sdcard/cminstall.
Boot on Android works fine, but, what i have to do to finish my upgrade on CM11 ?
Thanks a lot for your help !
Edit : on ES Explorer you have to activate root access to see /data/media/0
Bristow69 said:
Hi !
I have a 32 Gb Touchpad on CM10.1 and i'd like to upgrade on CM11 with Milaq ROM.
So, i downloaded The_apes Flashable zip (this one : sys_512mb_data_plus_24576mb-signed.zip) and i flash it with ClockworkMod 5.x. I've got 2 errors like this.
After that, i flashed with the new ClockworkMod 6.x, but, now, when i want to flash ROM, i've got only 0/ and obb/ folders. I can't acces to sdcard/cminstall.
Boot on Android works fine, but, what i have to do to finish my upgrade on CM11 ?
Thanks a lot for your help !
Click to expand...
Click to collapse
Welcome to the world of DataMedia.
In CM10.1 use a Root Browser app (e.g. ROM Toolbox lite) or a file manager app with root permissions (e.g. ES File Explorer or X-Plore) to move your CM11 ROM zip to a directory accessible to your new CWM recovery.
Myself I store all my ROM and recovery zips in the Download directory, where Chrome and Firefox also download files to.
e.g.
/storage/sdcard0/Download
/data/media/0/Download
Thanks woodytrain for your quick reply.
I tried to put my ROM /storage/sdcard0/Download but it's the same, i don't see this folder.
In /data, i've no folder
I tried to find obb/ with ES Explorer and it found it on /mnt/, is it normal ?
Last thing, i gone in WebOS in order to use Tailor and found this partition layout, i think it's not ok to flash KitKat :
USB (media) = 25.43 Gib
Android (system) = 408 Mib
Android (cache) = 200 Mib
Android (data) = 1.5 Gib
Unused Space = 8 Mib
I don't knom how to install KK on my touchpad. I don't understand because i don't thing to be a newbie, i flashed i9000 on CM 10.2, Touchpad on CM10.1, but KK made me crazy !
Thanks for your help !
You need to change your partition sizes. At the very least need to increase /system
And if you want to install a DataMedia (DM) ROM, you need to make additional adjustments.
Right now there are three (or four) KitKat (4.4.2) ROM's for the TouchPad (tenderloin) to choose from:
CM11 - 3.0 kernel (Milaq) - DM
CM11 - 3.4 kernel (invisiblek) - DM
Evervolv - AOSP - 3.4 kernel (flintman) - (two version:- one DM and one not)
If you want to install KitKat on your TouchPad will need to do some reading. Keep in mind all these KK 3.x kernel based ROMs are in development (experimental and/or for testing). Each has its own pros and cons, and various TouchPad features are not yet working, features you might have observed working in previous JB 2.6 kernel ROMs.
If you want to stay with JB, until KK is better baked for the TouchPad you may want to try out the new JB 3.x kernel ROM just released from jcscullins (01-25-14). It is NOT a DM ROM, whereas Milaq's CM10.2 (JB) is a DM ROM.
http://forum.xda-developers.com/showthread.php?t=1811480
Suggestions:
1. For each ROM you are interested in thoroughly read the OP. And suggest reading, at the minimum the last five pages of each thread.
2. Then visit [ROM GUIDE] How to Update/Install Android 4.2, 4.3 and 4.4 Builds on the HP TouchPad
http://forum.xda-developers.com/showthread.php?t=2321397
3. Be sure to read the info on how to update your partition for DM support. If you decide to go with a DM ROM, I would suggest using Tailor to change your partitions since you have Tailor installed on your device already.
4. Backup your device before proceeding. Generate a nandroid backup in your recovery as well as back up your app/data with Titanium Backup
5. A "full wipe" in your recovery (factory reset, including clearing caches, formatting /system) is generally recommended when doing major upgrades (not just a nightly flash of the same ROM).
Once you have chosen a ROM to install, and have downloaded the zips for both the matching ROM and Recovery zips (note each ROM has it's own specific recovery version matched to the ROM), then you should be ready to upgrade.
If you have questions before upgrading post your SPECIFIC questions/issues, identifying the ROM version you are coming from and going to.
Thanks woodytrain for your help.
I understood what i missed : root explorer button on Es Explorer
So, now, i can see my files with clockwork Recovery, yes ! I put them in /data/media/0/Download.
After that, i'm gone on Tailor to resize my partitions.
Now, i have :
600 Mb for system
200 Mb for cache
15 Go for media
and ~ 6 Go for data, it's not enough but don't care now...
So, i flashed my rom (Milaq CM11) and gapps (after factory reset, format /system, clear /cache) but now, when i boot on cyanogen, i've cyanogen logo and that's all... only a blank screen, i think i'will made an other post except if you have an idea
Bristow69 said:
So, i flashed my rom (Milaq CM11) and gapps (after factory reset, format /system, clear /cache) but now, when i boot on cyanogen, i've cyanogen logo and that's all... only a blank screen, i think i'will made an other post except if you have an idea
Click to expand...
Click to collapse
Not sure what is meant by "15 Go for media". Recommend you follow the partition instructions as listed in the OP of Milaq's CM11 ROM thread. At any rate...
Before you started the process did you do a nandroid, and backup your apps and data with TiBu or helium?
Then when you did the wipe, did you clear Dalvick cache as well?
And then did you flash the CWM recovery version listed in the OP of Milaq's CM11 ROM thread (CWM 6.0.4.6)? You MUST use that version.
http://milaq.exnet.me/downloads/tenderloin/misc/recovery-clockwork-6.0.4.6-tenderloin.zip
You might want to redo the process and hold off installing gapps until you have booted into CM11. Then go back to recovery and install the gapps listed in the OP. Or install one of the PA-gapps packages.
With a few more posts you receive the right to post to the ROM dev thread. Joy!
I reply only to increase my posts and because i made a big big mistake after this post, i formated all partitions on clockworkmod (6.0.4.6 ). So i will create an other thread on forum...
Mad and Confused
I was duped into updating to 4.4 evervolv when i was on their 4.3.1 rom and im not understanding the layout of my sd-card now. i know all my info is still there but unsure how to reformat so i can use all my space. 32gb touchpad. i will use root explore app to get all my data but can i use onboard storage app to format? Really pissed im in this situation at all. Stupid to be on a 4.3.1 rom and update only to find out it's now a 4.4 rom and my sd-card is different. Thanks much
Nevermind, got it sorted. Good excuse to repartition and reformat everything. Still want nothing from evervolv but there 16mb Gapps package, mwahaha
Hello everyone,
I recently asked my friend to root my phone and flash cyanogen mod 12 on my phone. After he flashed it, I realised that I still have the stock recovery (MI Receovery 2.). I am unable to flash gapps no matter how many times I try. I have added the zip file to internal memory, changed the name to "update", from recovery, i have tried to update.zip but it always fails after it reaches 98%.
I thought the problem was the stock recovery so I tried to flash the cwm recovery the same way as mentioned above, but the result was the same. I couldn't flash that either.
Please help!!!
ynk1 said:
Hello everyone,
I recently asked my friend to root my phone and flash cyanogen mod 12 on my phone. After he flashed it, I realised that I still have the stock recovery (MI Receovery 2.). I am unable to flash gapps no matter how many times I try. I have added the zip file to internal memory, changed the name to "update", from recovery, i have tried to update.zip but it always fails after it reaches 98%.
I thought the problem was the stock recovery so I tried to flash the cwm recovery the same way as mentioned above, but the result was the same. I couldn't flash that either.
Please help!!!
Click to expand...
Click to collapse
Okay it seems that your system partition is full.
You can opt for one of the 2 solutions I'll provide you :
1
So as too much said, you can resize your partition in order to get system1 1.2Gb and system 2 just some Mb.
Here is the thread : http://forum.xda-developers.com/xiaomi-mi-3/general/howto-resize-extend-partition-capacity-t3011918
Or just flash the zip provided here : http://forum.xda-developers.com/showpost.php?p=58591075&postcount=29
But remember to make a nandroid backup of your rom because repartitionning will wipe your system partitions. And also keep the rom zip on your internal memory.
2
But without resizing you can flash a smaller gapps package (just google play services and play store), normally your rom is based on android 5.0.2, so if I'm not mistaking here are the gapps you can flash (smaller one) : https://mega.co.nz/#!1c1VhAKT!SCCXkMJ3oS1bTc-LFFYCjqL0MXVqb4Q8HIEINuZYj98
After that you can install gmail and other google apps from play store. These apps are going to be installed as user app wiythout taking storage on system partition.
Hope it'll help you
If you had problems (like myself) with installing custom roms via twrp where the system would stuck in a bootloop and the recovery would return "No OS Installed" error, here's the solution to how to fix it:
1. Enter TWRP
2. Go to Wipe - Format Data
3. Restart recovery
4. Copy the rom to internal storage and install custom rom
Enjoy!
vulgaran said:
If you had problems (like myself) with installing custom roms via twrp where the system would stuck in a bootloop and the recovery would return "No OS Installed" error, here's the solution to how to fix it:
1. Enter TWRP
2. Go to Wipe - Format Data
3. Restart recovery
4. Copy the rom to sd card and install custom rom
Enjoy!
Click to expand...
Click to collapse
Thanks for the useful info. :highfive:
evanB70 said:
Thanks for the useful info. :highfive:
Click to expand...
Click to collapse
Whoops, forgot it doesn't have the sd card slot I've edited the first post.
Apparently, when you change rom type (for example, from official stable to xiaomi.eu weekly), you have to do this complete device wipe. For updating to a new version only wiping dalvik and cache should do.
not work on me
Thanks but didn't work for me either. After following your instructions, the phone booted into TWRP again. It no longer says there's no OS, but it won't boot. Just stalls into boot animation for a while and then goes into twrp recovery... Bummer!