Hi i am wanting to install the CyanogenMod 10.1 official nightlies rom but have just noticed i have to install official ClockworkMod-Recovery
i have the unofficial cwm and could not work out why signiture verifacation kept failing but now i believe its because i need to flash official ClockworkMod-Recovery.
HOW DO I FLASH official ClockworkMod-Recovery AS I HAVE ONLY DISC IMG FROM MANAGER.?
CHEERS
AJT NEW TO TAB
sas007 said:
Hi i am wanting to install the CyanogenMod 10.1 official nightlies rom but have just noticed i have to install official ClockworkMod-Recovery
i have the unofficial cwm and could not work out why signiture verifacation kept failing but now i believe its because i need to flash official ClockworkMod-Recovery.
HOW DO I FLASH official ClockworkMod-Recovery AS I HAVE ONLY DISC IMG FROM MANAGER.?
CHEERS
AJT NEW TO TAB
Click to expand...
Click to collapse
Do the first point here : http://forum.xda-developers.com/showthread.php?t=1722745
Related
Being new to the forums it would appear I can not post this in the relevent thread to tell the Developer perhaps another forum member or a Mod could link to this article later.
Original thread located here: http://forum.xda-developers.com/showthread.php?t=2055430
People flashing the latest nightlies since 2013/07/06 have been unable to install the latest CM10.1 nightlies if they're using the CWM 6.0.2.5 official clockwork mod recovery bootloader.
It would seem the newer recovery flash only supports the TWRP.blob and not the official clockwork recovery mod.
This is not a Bootloader issue caused by having a bootloader that only supports 4.1 and not 4.2
Because the last build before this happened was CM10.1 20130706 (4.2.2) which was working fine when you clicked the CM10.1 update button.
So in order to re-flash the latest nightlies it would seem I have to go and find another PC, dig out the USB cable's put the device back into fastboot and flash the TWRP.blob which I havent had the time to do and fail to see why that's needed if the Official CWM Bootloader was doing the Job previously.
Anyone know why the TWRP.blob seems to have taken precidence over the CWM? Or why the latest nightlies are incompatible with the CWM 6.0.2.5 bootloader which until the 20130707 Nightly update had been working and upgrading the build perfectly???
hello everyone
I have XT926 (verizon one)
my phone system version is 183.46.10
I have rooted my phone using towelroot and unlocked bootloader
now whats next?
latest firmware update (183.46.15) notification is bugging me, should i install it through ota in this condition or directly move to installing custom roms. if install this ota without unrooting, will my phone enter bootloop?
which recovery is recommended for android 5.0 on kk bootloader.
faheemakbar18 said:
hello everyone
I have XT926 (verizon one)
my phone system version is 183.46.10
I have rooted my phone using towelroot and unlocked bootloader
now whats next?
latest firmware update (183.46.15) notification is bugging me, should i install it through ota in this condition or directly move to installing custom roms. if install this ota without unrooting, will my phone enter bootloop?
which recovery is recommended for android 5.0 on kk bootloader.
Click to expand...
Click to collapse
Here ist what i have experienced:
I was on System Version: 181.46.3
Well nevertheless:
It was the most recent version i could get and i wanted to get back to Android L.
I installed CM12 the Following way, I had a lot of problems with that. So here is my experience and everything:
So you need to know, to install CM12 or other CM12 based ROMS you first need to have CM11 installed.
Newer Versions of the recovery might be having problems installing CM11, so i would recommend using PhilZ Touch Recovery. It was working for me.
1st: install PhilZ recovery
2nd: factory reset
3rd: install cm11 (Unified Build, due to no up-to-date-build for XT925)
4th: boot
5th: install latest TWRP XT925/TWRP XT926
6th: factory reset
7th: install CM12 XT925 / CM12 XT926 or other CM12 based ROM
8th: install Gapps
9th: wipe cache/dalvik cache
10: Boot
11: Have fun.
Possible problems:
"This package is for moto_msm8960, xt907, scorpion_mini, smq, xt926, vanquish, this is a xt925" ------> You got a problem with the Recovery, it is too new. Try PhilZ
CM12 Booting, inconsistent Data partition stuff error ---------> you did not install cm11 and did not wipe Data before installing CM12, when coming from Blur Rom
Bootloop ---------> no wiping or you did not install cm11 before installing CM12
I hope this might have helped you.
Greetz Esok
thanks alot @esok44 for detailed reply
which phone you hv xt925 or 926
why install cm11 from moto msm8960 and not from specific xt925,xt926 build
faheemakbar18 said:
thanks alot @esok44 for detailed reply
which phone you hv xt925 or 926
why install cm11 from moto msm8960 and not from specific xt925,xt926 build
Click to expand...
Click to collapse
Heyho
I have an XT925.
I installed the msm8960 Build.
The Reason i used the unified Build was, there is no KKBL build for the xt925.
thanks again, onto the procedure now
just last thing, which version of philz recovery you installed, download link has latest one @esok44
faheemakbar18 said:
thanks again, onto the procedure now
just last thing, which version of philz recovery you installed, download link has latest one @esok44
Click to expand...
Click to collapse
Hey Faheem,
i used the latest one, i guess
Found it here.
Link in my first Post was wrong
esok44 said:
1st: install PhilZ recovery
2nd: factory reset
3rd: install cm11 (Unified Build, due to no up-to-date-build for XT925)
4th: boot
5th: install latest TWRP XT925/TWRP XT926
6th: factory reset
7th: install CM12 XT925 / CM12 XT926 or other CM12 based ROM
8th: install Gapps
9th: wipe cache/dalvik cache
10: Boot
11: Have fun.
Possible problems:
"This package is for moto_msm8960, xt907, scorpion_mini, smq, xt926, vanquish, this is a xt925" ------> You got a problem with the Recovery, it is too new. Try PhilZ
CM12 Booting, inconsistent Data partition stuff error ---------> you did not install cm11 and did not wipe Data before installing CM12, when coming from Blur Rom
Bootloop ---------> no wiping or you did not install cm11 before installing CM12
I hope this might have helped you.
Greetz Esok
Click to expand...
Click to collapse
If you come frome OTA Kitkat 4.4.2
you have to change Step 1st: install PhilZ recovery ------ to ------ Install TWRP2710-RAZR-HD_M-KITKAT.img instead then you can flash the CM 11
If you like philz_touch_6.58.7-moto_msm8960.img recovery (it can mount external Memory Card as USB) you can flash it after all installations after Point 11. The only thing that you cannot start directly to recovery from CM 12.1
I have a p3113 ,as evryone suggested i tried a lot of p3110 lolipop roms.
Recently i tried to flash cm11 unoffcial version of android andi.
It says it cant flash the rom and says error in the zip file and( error 7 ) in recovery.
All this happens only for a kitkat rom but i can flash any other version of android like lolipop or jb.
Pls help me ..currently im on cm9 official build for p3113. I have a cwm recovery,version 6
update your revovery, you can download zip here: https://www.androidfilehost.com/?w=files&flid=25706 Flash it and reboot recovery, then it should work fine
iks8 said:
update your revovery, you can download zip here: https://www.androidfilehost.com/?w=files&flid=25706 Flash it and reboot recovery, then it should work fine
Click to expand...
Click to collapse
Thanks got it..
switch to TWRP
I would alse recomend TWRP. In my opinion runs better than cwm
hi
did something wrong and bricked my 64g opo, managed to unbrick it from advise on here but its stuck on color os, i have been trawling here and trying things all afternoon with no success. is there a certain rom i need to start with?
i have twrp
thanks for looking
done now
You have to tell which twrp version
And color os roms flash their own firmware so you would have to flash latest cm nightly or firmware zips in general section
TWRP should not be 2.8.7.0 it has some problems with firmware flashing.
I recommend unofficial 2.8.6.0 or the newest 3.0.2.0
kunal1540 said:
You have to tell which twrp version
And color os roms flash their own firmware so you would have to flash latest cm nightly or firmware zips in general section
TWRP should not be 2.8.7.0 it has some problems with firmware flashing.
I recommend unofficial 2.8.6.0 or the newest 3.0.2.0
Click to expand...
Click to collapse
thanks
twrp is 2.8.5.1
any pointers to the right place to look
Flash twrp 2.8.6 official and flash COS 12.1 OR 13 signed zip ( twtp flashable )Whichever you want , you are up to date now.
hi all,
I have Samsung Tab 2.7.0 P3100 and an year back i installed CM10. I think i have done some mistake while updating from CM 10 to CM latest version. I have wiped the date and cache.I have the ZIP files (CM 10 and GAPPS) in external memory. when i am trying to install the CM11 it is showing "INSTALLATION ABORTED with error number 7". But when I am trying to install GAPPS it completed successfully.
can someone please help me here to get my tab back in working condition ..!!!
Wondering, is it possible to install the Samsung normal OS back again ?
Any help on this issue is much appreciable.
Thanks
Shibin Shah K J
sskj said:
hi all,
I have Samsung Tab 2.7.0 P3100 and an year back i installed CM10. I think i have done some mistake while updating from CM 10 to CM latest version. I have wiped the date and cache.I have the ZIP files (CM 10 and GAPPS) in external memory. when i am trying to install the CM11 it is showing "INSTALLATION ABORTED with error number 7". But when I am trying to install GAPPS it completed successfully.
can someone please help me here to get my tab back in working condition ..!!!
Wondering, is it possible to install the Samsung normal OS back again ?
Any help on this issue is much appreciable.
Thanks
Shibin Shah K J
Click to expand...
Click to collapse
Any help ....????
sskj said:
Any help ....????
Click to expand...
Click to collapse
you should upgrade your recovery too. try twrp 3.0.2-3 from here https://www.androidfilehost.com/?fid=24591000424954613
and install it with your current recovery. make a reboot back into recovery.
wipe dalvik, cache, system and format data http://andi34.github.io/faq/faq_twrp.html
make a new reboot into recovery and install your rom and gapps.
OK
johneflik said:
Redowload the ROM again it might be corrupt and use the exact gapps
Best ROM for your tab is omni 4.4.4 or cm13 or omni 6.0.1
Just the latest TWRP go wipe then advanced wipe then wipe everything except the external SD. Install install your chosen ROM flash the equivalent gapps, flash super user update reboot you are done. all what you need is here in Andoid-Andi files http://andi34.github.io/
Click to expand...
Click to collapse
sskj said:
hi all,
I have Samsung Tab 2.7.0 P3100 and an year back i installed CM10. I think i have done some mistake while updating from CM 10 to CM latest version. I have wiped the date and cache.I have the ZIP files (CM 10 and GAPPS) in external memory. when i am trying to install the CM11 it is showing "INSTALLATION ABORTED with error number 7". But when I am trying to install GAPPS it completed successfully.
can someone please help me here to get my tab back in working condition ..!!!
Wondering, is it possible to install the Samsung normal OS back again ?
Any help on this issue is much appreciable.
Thanks
Shibin Shah K J
Click to expand...
Click to collapse
don't flash a separate supersu.zip if you would install cm13. supersu causes bootloops on cm13.
if you need root access on cm13, go to dev.-options and enable root access. set it to "apps and adb"
thats all.
cm13 is pre-rooted, so no need for flashing supersu.zip
OK
johneflik said:
[MENTION=457974].. yes you are right about super user. I think pmni6.0.1 needs a super user to be flashed. Any way I have seen SU on cm13 and no problem at all... Untill now. Do I need to remove it or keep the root access from dev tools disabled.
Click to expand...
Click to collapse
omni6 need supersu right.
if supersu are working on cm13 by Markox89 for you everything is fine. i would keep the root access from dev.-options disabled