Related
i have been downloading CM nightlys to my pc, copying them to my phone's internal storage, then flashing the zip using recovery (twerp v2.6.3.0) successfully for 3 or 4 months. I found CM Downloader app on the app store and down loaded that. I set the setting to automatically check for a new build, and download it. it did download the new builds although they failed to flash. 3 days after this started happening, CM came out with a 'snapshot' version. that one flashed ok. but the 'nighly' builds no longer flash. I have uninstalled CM downloader, and tried downloading them to the PC and copying them to the phone, that no longer works either. I have reinstalled CM downloader no change. so I think there is something changed on the phone that needs to be fixed, or reset or something. I appreciate any ideas here, I am still entry level skill level, so be gentle
blairman
TWERP failed flash message
blairan said:
i have been downloading CM nightlys to my pc, copying them to my phone's internal storage, then flashing the zip using recovery (twerp v2.6.3.0) successfully for 3 or 4 months. I found CM Downloader app on the app store and down loaded that. I set the setting to automatically check for a new build, and download it. it did download the new builds although they failed to flash. 3 days after this started happening, CM came out with a 'snapshot' version. that one flashed ok. but the 'nighly' builds no longer flash. I have uninstalled CM downloader, and tried downloading them to the PC and copying them to the phone, that no longer works either. I have reinstalled CM downloader no change. so I think there is something changed on the phone that needs to be fixed, or reset or something. I appreciate any ideas here, I am still entry level skill level, so be gentle
blairman
Click to expand...
Click to collapse
Updating partition details
Processing OpenRecoveryScript file
unable to locate zip file "/CyanogenRob_Downloa
E:Error installing zip file "/CyanogenRob_Downloa
Don processing script file
Installing ' /sdcar/CyanogenRob_Downloader/cm1
skipping MD5 check: no MD5 file found
E:Error executiong updater binary in ' /sdcar/CyanogenRob_Downloader/cm1
Error flashing zip ' /sdcar/CyanogenRob_Downloader/cm1
updating partition details
then under that in red letters "Failed'
blairan said:
Updating partition details
Processing OpenRecoveryScript file
unable to locate zip file "/CyanogenRob_Downloa
E:Error installing zip file "/CyanogenRob_Downloa
Don processing script file
Installing ' /sdcar/CyanogenRob_Downloader/cm1
skipping MD5 check: no MD5 file found
E:Error executiong updater binary in ' /sdcar/CyanogenRob_Downloader/cm1
Error flashing zip ' /sdcar/CyanogenRob_Downloader/cm1
updating partition details
then under that in red letters "Failed'
Click to expand...
Click to collapse
TWRP that works:
http://forum.xda-developers.com/showpost.php?p=50383573&postcount=3
Why (changelog):
http://forum.xda-developers.com/showpost.php?p=50383578&postcount=4
i'm part way there...
tdhite said:
TWRP that works:
http://forum.xda-developers.com/showpost.php?p=50383573&postcount=3
Why (changelog):
http://forum.xda-developers.com/showpost.php?p=50383578&postcount=4
Click to expand...
Click to collapse
OK, I have downloaded the 2 files. placed them in a directory near my root directory on my pc. placed the phone in fastboot usb, opened a command prompt window from that directory. typed in fastboot flash recovery openrecovery-m7wls-2.7.0.9-05-01-2014
and I get error: cannot load 'fastboot flash recovery openrecovery-m7wls-2.7.0.9-05-01-2014'
per a video showing how to flash recovery, I also tried the command adb reboot bootloader I get error : device not found
back to my pc, I open device manager, and I show a device labeled android device that is working properly.
stumped at this point.
is updating recovery the same as the initial install of a custom recovery?
do I need updated drivers for win 7? where are the latest? all videos say they are the latest, but that was when they were recorted.
thanks for help!
Yes u need updated drivers....any easy solution however is go and get the app flashify u will need root of course...it allows u to flash recovery that is on ur sd card. Just choose the img and flash recovery in the app then reboot into recovery and u will be good to go.
Sent from my HTCONE using Tapatalk
Thank you!
Thanks to both of you, updated TWERP did the trick and Flashify allowed me to install it without the fastboot, and PC hookup which was not working. Latest nightly installed, I am a happy camper!
Ok, let me get this straight, snag this Flashify, then snag TWRP 2.7.1.1, flash it with Flashify and I am golden????
(I am unlocked and S-Off running CM-11)
Slagathor01 said:
Ok, let me get this straight, snag this Flashify, then snag TWRP 2.7.1.1, flash it with Flashify and I am golden????
(I am unlocked and S-Off running CM-11)
Click to expand...
Click to collapse
All u have to do is update your recovery. So u can grab the latest TWRP and flash it any method u wish. Fastboot is best but flashify is the most convenient. After u flash your recovery the CM Rom should flash perfectly. Note: If u experience any failures in flashing any Rom that u know is good just downgrade your recovery via which ever method u prefer and that should flash fine now. You can always use the recovery zip floating around on the android development thread I'll see if I can find it for u.
Here u go bud http://forum.xda-developers.com/showthread.php?t=2656065
Note if the flash fails try a older zip until it works and flash the twrp by TD. Don't forget to thanks rootlinux for the zips. Might also want to keep the zips in handy on the phone storage incase the Note situation appears.
Sent from my HTCONE using Tapatalk
luigi311 said:
All u have to do is update your recovery. So u can grab the latest TWRP and flash it any method u wish. Fastboot is best but flashify is the most convenient. After u flash your recovery the CM Rom should flash perfectly. Note: If u experience any failures in flashing any Rom that u know is good just downgrade your recovery via which ever method u prefer and that should flash fine now. You can always use the recovery zip floating around on the android development thread I'll see if I can find it for u.
Here u go bud http://forum.xda-developers.com/showthread.php?t=2656065
Note if the flash fails try a older zip until it works and flash the twrp by TD. Don't forget to thanks rootlinux for the zips. Might also want to keep the zips in handy on the phone storage incase the Note situation appears.
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
I got it with fastboot, I forgot I re installed windows since I did it initially, so I was pulling my hair out wondering why fastboot wouldnt see it, and I couldnt even get files to or from it till I installed HTC sync.....heh
thanks for the info.....
Hi all,
I have a bit of a problem here, whenever I try to flash a .zip file in Cyanogen Recovery (CM12) it says: E: signature verification failed. Installation aborted.
Does anyone know how to solve it?
Thanks in advance!
xChillz (C6603)
I had that issue with the same recovery on a number of zips. Have you considered using another recovery?
Parker-ivxx said:
I had that issue with the same recovery on a number of zips. Have you considered using another recovery?
Click to expand...
Click to collapse
Yes I did, noone seems to be able to answer this question, so I'm going to plan B.
I would like to know how I can install TWRP over the CM12 recovery again, because when I flash the TWRP .img file with fastboot, it replaces my whole CM12 Rom.
Could someone explain to me how I can keep both CM12 + TWRP recovery?
Thanks in advance!
xChillz said:
I would like to know how I can install TWRP over the CM12 recovery again, because when I flash the TWRP .img file with fastboot, it replaces my whole CM12 Rom.
Click to expand...
Click to collapse
It replaces your Rom with what exactly
Try formatting the FOTAKernel either using xperia recovery manager or flashtool and then flash twrp/cwm and report back.
xChillz said:
Yes I did, noone seems to be able to answer this question, so I'm going to plan B.
I would like to know how I can install TWRP over the CM12 recovery again, because when I flash the TWRP .img file with fastboot, it replaces my whole CM12 Rom.
Could someone explain to me how I can keep both CM12 + TWRP recovery?
Thanks in advance!
Click to expand...
Click to collapse
I had the same problem.And i got permission denied when flashing fotakernal in flashboot mode.
I solved it by using "[ROOT] Rashr - Flash" Tool.It is in google play.
Hi guys,
I just saw about new Xposed frameworks for Lollipop and excited, I tried to install zip from recovery.... Without success!! I saw somewhere here that CM Recovery have some problem with zip file. If it's true, and there's not solution, what I can do? I must flash new recovery?
Thanks for help
AndyMoscow said:
Hi guys,
I just saw about new Xposed frameworks for Lollipop and excited, I tried to install zip from recovery.... Without success!! I saw somewhere here that CM Recovery have some problem with zip file. If it's true, and there's not solution, what I can do? I must flash new recovery?
Thanks for help
Click to expand...
Click to collapse
Try flashing boot.img from any lollipop image rom
(Either @pabx or @Thomas Boot.img file is recommended)
Hope that works.
or install CWM via adb
Flash boot.img via flashtool
pawlinho said:
Flash boot.img via flashtool
Click to expand...
Click to collapse
Please tel me briefly.. I'm a beginner.. Where to download flashboot IMG??
And how to install via adb? Twrp recovery..
Thanks
ClockworkMod Recovery (6.0.5.1) Open Bump Edition for LG G Pad 8.3 v500. This custom recovery installation package is for v500 models only. Built from source on 2014-12-13 by Jenkins. This version of CWM 6.0.5.1 has been "bumped" so that loki tool is not required.
Installation: Flash zip file with any custom recovery and reboot into updated CWM recovery.
v500-CWM-6.0.5.1-20141213-recovery-bumped-signed.zip
MD5: 8c8593fc0fb8039949c0f06d48d97e4f
Note: An advantage to using the official CWM recovery with CM 11 is that the CWM recovery can be automatically updated with the CM Update tool, if enabled in the CM 11 developer options.
Manual Installation (first time installing custom recovery):
1) Gain root permission (ie; with Stumproot) and install SuperSU and Busybox.
2) Install Terminal Emulator or use ADB for opening up a shell (this example is using ADB).
Note: If using Terminal Emulator, make sure root access is given via SuperSU.
3) Download CWM installation zip file from the link above and manually extract it.
4) Copy recovery.img (contained in the CWM installation zip file from step #3) to /data/local/tmp on your LG G Pad 8.3 v500 tablet with either ADB or a root explorer application and install with "dd" command.
Code:
adb push recovery.img /data/local/tmp/
adb shell
su
cd /data/local/tmp
ls recovery.img
dd if=recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
exit
exit
adb reboot recovery
is this the touch version?
This is the latest official swipe version. It's not full touch.
Deltadroid said:
This is the latest official swipe version. It's not full touch.
Click to expand...
Click to collapse
are there any plans to port the touch version to the g pad?
Not at the moment. This recovery was taken from the official nightly builds. I did not personally build it. I have only "bumped" the image and packaged it.
only bumped roms or kernels works with bumped recoverys? what happens if i flash a normal rom?
auleu said:
only bumped roms or kernels works with bumped recoverys? what happens if i flash a normal rom?
Click to expand...
Click to collapse
Any rom or kernel can be installed with a bumped recovery. Although, some ROMs require that your aboot partition is from 4.2.2 so that loki will work so that the kernel can be installed (which has nothing to do with the recovery).
Deltadroid said:
Any rom or kernel can be installed with a bumped recovery. Although, some ROMs require that your aboot partition is from 4.2.2 so that loki will work so that the kernel can be installed (which has nothing to do with the recovery).
Click to expand...
Click to collapse
Installed this recovery following the instructions :
adb reboot recovery : my tablet didn't reboot to recovery but to system
then I boot into recovery using Titanium Backup (there's an option to boot into recovery in the menu)
I tried to install latest official CM12 nightly : error
tried with latest AOSP 5.1 too, same error
So I tried to toggle Loki in the CWM settings , same results.
Now I can't boot into system nor recovery : "Security Error"
Looks like I'm good to flash once again the stock rom...
Any tips to be able to install CM12 or AOSP 5.1 ?
Phenom2 said:
Installed this recovery following the instructions :
adb reboot recovery : my tablet didn't reboot to recovery but to system
then I boot into recovery using Titanium Backup (there's an option to boot into recovery in the menu)
I tried to install latest official CM12 nightly : error
tried with latest AOSP 5.1 too, same error
So I tried to toggle Loki in the CWM settings , same results.
Now I can't boot into system nor recovery : "Security Error"
Looks like I'm good to flash once again the stock rom...
Any tips to be able to install CM12 or AOSP 5.1 ?
Click to expand...
Click to collapse
When you typed "adb reboot recovery", make sure you unplug the usb cable or it will not reboot into recovery.. this occurs with all versions of CWM.
When you install a ROM, make sure that your aboot partition is loki exploitable (from 4.2.2) or it will not be able to install the kernel. Most ROMs still use the loki method to install the kernel, which still requires the older aboot.
Deltadroid said:
When you typed "adb reboot recovery", make sure you unplug the usb cable or it will not reboot into recovery.. this occurs with all versions of CWM.
When you install a ROM, make sure that your aboot partition is loki exploitable (from 4.2.2) or it will not be able to install the kernel. Most ROMs still use the loki method to install the kernel, which still requires the older aboot.
Click to expand...
Click to collapse
Ok, so I should flash the first stock rom before trying to install a recovery right ?
- Flash 1st stock rom
- Get root (I use towelroot)
- Install recovery with cmd
- Boot recovery and flash rom + gapps
Right ? (edit : OK, I managed to install AOSP 5.1 with theses instructions coming from stock V50010B)
I understood that there's 2 major exploit, loki and bumb.
4.4 = bumb only
4.2.2 = both ?
Isn't your rom (cm12) bumb enabled ? (edit : "Currently, all official CyanogenMod ROMs use loki tool to install the kernel on the LG G Pad 8.3 v500" )
The current official nightly still uses loki so it still requires the 4.2.2 aboot. There is another thread about switching boot loaders which will also downgrade aboot with flashable zip. If the rom you are installing is pre bumped, then an aboot from 4.4.2 will work, but i still recommend downgrading aboot to 4.2.2 version for better compatibility with older roms and official cm.
so i installed the recovery, after i push the power button in the factory reset menu to load the recovery, the lg logo screen is very dark just like when youre in download mode, is this normal? i'm on kitkat bootloader
auleu said:
so i installed the recovery, after i push the power button in the factory reset menu to load the recovery, the lg logo screen is very dark just like when youre in download mode, is this normal? i'm on kitkat bootloader
Click to expand...
Click to collapse
Yes, that is normal.
Deltadroid said:
Yes, that is normal.
Click to expand...
Click to collapse
and if i install a rom and at the end says something like not loki exploitable does this mean that the rom is not bumped?
auleu said:
and if i install a rom and at the end says something like not loki exploitable does this mean that the rom is not bumped?
Click to expand...
Click to collapse
Yes
Deltadroid said:
Yes
Click to expand...
Click to collapse
if i enable loki support in cwm can i install a non bumped rom ? or what does that setting do?
auleu said:
if i enable loki support in cwm can i install a non bumped rom ? or what does that setting do?
Click to expand...
Click to collapse
Enabling loki support in cwm is deprecated and wont do anything. The problem is that you need to downgrade your aboot so that the Rom you are installing can execute it's scripts properly. There is a thread here that provides flashable zip files to switch bootloaders. You will want to choose the bootloader package with the downgraded aboot if you want to install older ROMs that have not been updated to use bump yet.
http://forum.xda-developers.com/showthread.php?p=52910560
does cwm have a rom size limit? im trying to sideload the stock lollipop rom with over 1gb size and gives error. failed to write data 'protocol fault (no status)'
auleu said:
does cwm have a rom size limit? im trying to sideload the stock lollipop rom with over 1gb size and gives error. failed to write data 'protocol fault (no status)'
Click to expand...
Click to collapse
This recovery is probably better suited for lollipop
http://forum.xda-developers.com/showthread.php?p=61363260
Deltadroid said:
This recovery is probably better suited for lollipop
http://forum.xda-developers.com/showthread.php?p=61363260
Click to expand...
Click to collapse
i've installed that one, it worked but didnt tried sideloading it, instead i copied it to sdcard. also its strange that cwm dosent have mount sdcard option
Hi using the guide i've tried on both PC and terminal emulator and also flashing the zip in cmw but it still keeps booting to CMW 6.0.3.5
Any help?
thanks
Jamie
cramhead said:
Hi using the guide i've tried on both PC and terminal emulator and also flashing the zip in cmw but it still keeps booting to CMW 6.0.3.5
Any help?
thanks
Jamie
Click to expand...
Click to collapse
try flashtool > fastboot mode > flash recovery via select kernel to hot boot
edit:flash .img file
yeah i forgot to mentipon i also tried that.
fastboot flash recovery recovery.img
didnt work
oops my bad
the install recovery + option is gray on my flashtool. I cant see that option
mostafaz said:
try flashtool > fastboot mode > flash recovery via select kernel to hot boot
edit:flash .img file
Click to expand...
Click to collapse
cramhead said:
oops my bad
the install recovery + option is gray on my flashtool. I cant see that option
Click to expand...
Click to collapse
sorry for late responce
i did try some method and this one is good
try this hack and by flash via recovery and then flash your own recovery
latest recovery is here
installed both .............Nothing happened
I'll try an old TWRP
Which rom are you on?
try flashing TWRP 2.8.5 the official version and you should be able to boot to TWRP Recover.
http://forum.xda-developers.com/showpost.php?p=57718351&postcount=2
check the link, thats what Oliver has to say about the ROM, boot.img file
I tried flashing version TWRP 2.5 and that still did nothing. I'm using ANDROID 5.1. XPERIA Z(YUGA)
:crying:
cramhead said:
I tried flashing version TWRP 2.5 and that still did nothing. I'm using ANDROID 5.1. XPERIA Z(YUGA)
:crying:
Click to expand...
Click to collapse
Sorry only last question, who's ROM are you using and build date.
Hey, I believe it's the 5.1 version for this
build says full_c6603-userdebug 5.1 LMY47D eng.adrian.20150312.205659 test-keys
cramhead said:
Hey, I believe it's the 5.1 version for this
build says full_c6603-userdebug 5.1 LMY47D eng.adrian.20150312.205659 test-keys
Click to expand...
Click to collapse
Ok, so the ROM by pabx, This rom does not have in built arrangement for TWRP, you will have to compile it on your own.
You will find the steps here http://forum.xda-developers.com/xperia-z/general/turorial-add-twrp-to-boot-img-t2951658
and then flash TWRP to Fotakernel first and then flash boot.img
learn something new everyday
could I flash a philz recovery?
I can't find a .zip and can't do "fastboot recovery.img "the philz.img
thanks
I have not tried Philz, so i cannot give you an answer.
you may want to head over to this link http://forum.xda-developers.com/xperia-z/general/z-xzdualrecovery-qa-t2477769
Had the same problem.
TWRP Recovery wasn`t available after I flashed yuga.
Used "TWRP Manager" (only with root) which worked for me even when the app said that the installation failed.After rebooting I was able to enter TWRP again.
SO I installed This and I now have TWRP 2.8.
0! My rom won't boot any more, but who cares I can now install CM!..............I hope
have you tries the hack that oliver has on his thread http://forum.xda-developers.com/showpost.php?p=57718351&postcount=2
flash Olivers TWRP to FotaKernal and then from cm recovery flash the hack, reboot and enter recovery and check
I have not personally check but give it a try if you like.