Develop Bugs

[Q] After unroot can't root again on htc one x

I rooted and unlocked on my ics in HTC one X and no rom. But after HTC officially released Jelly Bean 4.1.1 , i unrooted again and updated in official Jelly Bean. now i wanted to use CM 10.1 rom and many days i searched a lot and failed to root again. please help me i got some problem.
#unlocked
# S on
# Hboot 1.36
#OS JB 4.1.1
#when i select recovery in Bootloader it show a error sign and restart
#failed to open master usb....
#i tried JB but it failed too
* i did a factory reset and now erase everything.
* if i make a call somebody can't hear my voice and some said very low voice.
please help me. Thanks in advanced

After you updated the phone you must unlock the bootloader (if you relocked it) and flash a new custom recovery.
Flash the new boot.img from the new rom, perform a full wipe in the recovery and install the new rom.zip !

Mr Hofs said:
After you updated the phone you must unlock the bootloader (if you relocked it) and flash a new custom recovery.
Flash the new boot.img from the new rom, perform a full wipe in the recovery and install the new rom.zip !
Click to expand...
Click to collapse
It's still shows unlocked and i wanna wipe or install from SD card but Recovery option not working.

Like i said, you must flash a custom recovery first. When you updated the phone its done with a stock recovery. A stock recovery is useless to us flashers.
Its all exactly the same as it was with ics.....

Mr Hofs said:
Like i said, you must flash a custom recovery first. When you updated the phone its done with a stock recovery. A stock recovery is useless to us flashers.
Its all exactly the same as it was with ics.....
Click to expand...
Click to collapse
r u saying to do follow the same way like i did for unlocked+root on my ICS ? i tried it but HTCdev not working like before.

Look.....you don't have to do the htcdev thing. You say your bootloader is unlocked. So flash a custom recovey and install a JB rom as usual

Mr Hofs said:
Look.....you don't have to do the htcdev thing. You say your bootloader is unlocked. So flash a custom recovey and install a JB rom as usual
Click to expand...
Click to collapse
okay on my way to try and i will get back to u. btw do u have any correct link of which i should follow ? Thanks a lot

Use this to guide you.
http://forum.xda-developers.com/showthread.php?t=1592355
But flash this recovery and not the one mentioned in the guide
http://db.tt/SPXdFfPw

Mr Hofs said:
Use this to guide you.
http://forum.xda-developers.com/showthread.php?t=1592355
But flash this recovery and not the one mentioned in the guide
http://db.tt/SPXdFfPw
Click to expand...
Click to collapse
C:\fastboot>fastboot flash recovery-clockwork-touch-5.8.4.0-endeavoru.img
unknown partition 'recovery-clockwork-touch-5.8.4.0-endeavoru.img'
error: cannot determine image filename for 'recovery-clockwork-touch-5.8.4.0-end
eavoru.img'
C:\fastboot>fastboot flash philz recovary 5.6.1.img
error: cannot load 'recovary'

Put my linked recovery into the fastboot folder....
Then rename the file to just "recovery.img
Fastboot flash recovery recovery.img
You seem to have messed up the command mate

himel_htc said:
C:\fastboot>fastboot flash recovery-clockwork-touch-5.8.4.0-endeavoru.img
unknown partition 'recovery-clockwork-touch-5.8.4.0-endeavoru.img'
error: cannot determine image filename for 'recovery-clockwork-touch-5.8.4.0-end
eavoru.img'
C:\fastboot>fastboot flash philz recovary 5.6.1.img
error: cannot load 'recovary'
Click to expand...
Click to collapse
i think u should rename it as : recovery.img

Husky34 said:
i think u should rename it as : recovery.img
Click to expand...
Click to collapse
Lol....beat you to it !

Mr Hofs said:
Put my linked recovery into the fastboot folder....
Then rename the file to just "recovery.img
Fastboot flash recovery recovery.img
You seem to have messed up the command mate
Click to expand...
Click to collapse
Yes u r right...thank u so much
cyMod RC2 loading......
#If i ever want to back to HTC official rom when the release the 4.2.2 what should i need to do ?

Well then you need to install the stock nandroid backup, flash the stock recovery and then update

Unfortunately, the process com.android.phone has stopped.....:crying:
after open first msg it and i can't do anything. what wrong i did ?

Sure you installed gapps too, and that it the right gapps ?
* flash boot.img
* make a full wipe in the recovery
* install CM10.1
* install gapps
* reboot

Mr Hofs said:
Sure you installed gapps too, and that it the right gapps ?
* flash boot.img
* make a full wipe in the recovery
* install CM10.1
* install gapps
* reboot
Click to expand...
Click to collapse
1.wipe everything then tried randomly all
2.cm-10.1.0-endeavoru
3.UPDATE-SuperSU-v1.00
4.gapps-jb-20130301-signed
#CWM-6032-advwipe-jb422-nontouch-recovery-endeavoru-v1.2
should i try anything else or change my recovery ?

changed recovery to TWR v2.5.0.0
flash boot.img
wipe factory reset
flashing CM 10.1 and gapps-jb-20130301-signed ...completed
rebooting system.....well again process com.android.phone stop

Why update su ? Link me to the thread please...
and try another rom for test purposes

Mr Hofs said:
Why update su ? Link me to the thread please...
and try another rom for test purposes
Click to expand...
Click to collapse
http://www.chainfire.eu/articles/129/SuperSU_v1_00_has_been_released_/
any good rom suggest please?

Any one rooted OFFICIAL CM12 & Issues after updating

Any one rooted after updating to CM12 (Official)
I have updated my so far i have noticed some lags & network issues
PLS share your problems
THX

vipimg said:
Any one rooted after updating to CM12 (Official)
I have updated my so far i have noticed some lags & network issues
PLS share your problems
THX
Click to expand...
Click to collapse
If you wanna root it....Just install a custom Recovery & flash SuperSu.zip

hrishi21007 said:
If you wanna root it....Just install a custom Recovery & flash SuperSu.zip
Click to expand...
Click to collapse
I am just asking if its the same procedure as CM11 ....?(Dont wat to brick it)

Yup its same!
But u need to install 64bit custom recovery!
There is 64bit twrp recovery thread in Yureka android development!.
I rooted my phoe successfully and works great ??

Mine's bricked.
rahulsingh616 said:
Yup its same!
But u need to install 64bit custom recovery!
There is 64bit twrp recovery thread in Yureka android development!.
I rooted my phoe successfully and works great ����
Click to expand...
Click to collapse
i also update to lollipop, unlocked the bootloader and flashed 64bit twrp but my phone is bricked. can u please help?
thanks in advance.

aakarshak said:
i also update to lollipop, unlocked the bootloader and flashed 64bit twrp but my phone is bricked. can u please help?
thanks in advance.
Click to expand...
Click to collapse
This is what I was trying to say i was not sure about it i didnt do it yet just waiting for a solid one

Mr aakarshak
May i ask if your phone now in boot loop ...? or something else

vipimg said:
Mr aakarshak
May i ask if your phone now in boot loop ...? or something else
Click to expand...
Click to collapse
I jst flashed the cwm recovery and its working fine

Yes i was about to tell u to flash CWM recovery

aakarshak said:
I jst flashed the cwm recovery and its working fine
Click to expand...
Click to collapse
which one... is it 64 bit or the old one ????
rahulsingh616 said:
Yup its same!
But u need to install 64bit custom recovery!
There is 64bit twrp recovery thread in Yureka android development!.
I rooted my phoe successfully and works great ����
Click to expand...
Click to collapse
i am also trying to flash the same thru fastboot but every time i am booting to recovery it shown cynogen's recovery.
update cm recovery is already unchecked in Dev option.?
any help

Rooted my phone, bricked it, and now went back to default Lollypop
-> I flashed the official CMD 12S, and flashed supersu alongwith, the first time when it was released, i.e. Thursday evening.
-> I was rooted to begin with, setup everything, everything worked.
-> Out of curiosity, rebooted to recovery to check the recovery, what it is. I was on clock work mod recovery, when I was on kit kat.
-> That's when my device would go to YU screen, and never go beyond that.
-> Luckily, I could still go into adb shell and fastboot. I flashed, the default boot and recovery from the original 12S zip, and logged into recovery again. Then used the update process in default recovery, to install 12S again.
-> So far so good. I can go to recovery as well.
-> What different I did this time, well did not root my device using supersu. So whoever have rooted your device using older supersu, would suggest to reboot to recovery, and if it breaks, you can still get your device back, by the process I mentioned, but that would confirm that old supersu could break recovery.

After flashing dont start ua phone
Go to recovery mode directly!

abeyhere said:
-> I flashed the official CMD 12S, and flashed supersu alongwith, the first time when it was released, i.e. Thursday evening.
-> I was rooted to begin with, setup everything, everything worked.
-> Out of curiosity, rebooted to recovery to check the recovery, what it is. I was on clock work mod recovery, when I was on kit kat.
-> That's when my device would go to YU screen, and never go beyond that.
-> Luckily, I could still go into adb shell and fastboot. I flashed, the default boot and recovery from the original 12S zip, and logged into recovery again. Then used the update process in default recovery, to install 12S again.
-> So far so good. I can go to recovery as well.
-> What different I did this time, well did not root my device using supersu. So whoever have rooted your device using older supersu, would suggest to reboot to recovery, and if it breaks, you can still get your device back, by the process I mentioned, but that would confirm that old supersu could break recovery.
Click to expand...
Click to collapse
What is the proper procedure to install the fast boot version as I am facing issues after installing the OTA and probably they can be resolved with the fastboot option. Kindly help.

I hv updated my yureka yesterday manually to cm12 and device is running very smoothly..bt I faced an issue while charging the phone..it was taking around 4hrs of time and phn heating a lot .. I was thinking to revert back to kitkat which was also working f9 for me without any heating issue bt I came to know it is not passible to go back.. I was bit tensed regarding heating issue bt suddenly I see my lumia 520 charger and I charged yureka with that charger and u won't believe charging speed is increased and phn was nt heating up at all.. I don't knw what is issue with charning in lollipop bt nw I am very relaxed ...

original 12S zip links
abeyhere said:
-> I flashed the official CMD 12S, and flashed supersu alongwith, the first time when it was released, i.e. Thursday evening.
-> I was rooted to begin with, setup everything, everything worked.
-> Out of curiosity, rebooted to recovery to check the recovery, what it is. I was on clock work mod recovery, when I was on kit kat.
-> That's when my device would go to YU screen, and never go beyond that.
-> Luckily, I could still go into adb shell and fastboot. I flashed, the default boot and recovery from the original 12S zip, and logged into recovery again. Then used the update process in default recovery, to install 12S again.
-> So far so good. I can go to recovery as well.
-> What different I did this time, well did not root my device using supersu. So whoever have rooted your device using older supersu, would suggest to reboot to recovery, and if it breaks, you can still get your device back, by the process I mentioned, but that would confirm that old supersu could break recovery.
Click to expand...
Click to collapse
Can u post links to original CM12S zip u mentioned above...?

vipimg said:
I am just asking if its the same procedure as CM11 ....?(Dont wat to brick it)
Click to expand...
Click to collapse
I bricked mine... So i dont recommend rooting after upgrading to cm 12

kailashnj said:
What is the proper procedure to install the fast boot version as I am facing issues after installing the OTA and probably they can be resolved with the fastboot option. Kindly help.
Click to expand...
Click to collapse
Kailas proper procedure, I won't know, as there may be a better way . However I'd tell you what worked for me.
-> I downloaded the zips (fastboot, and signed one, from http://forum.xda-developers.com/yureka/general/discussion-yu-yureka-cm-12s-lollipop-t3084461).
-> I moved the signed zip(cm-12.0-YNG1TAS0W0-tomato-signed-fastboot.zip) version to External SD card.
-> I extracted the fastboot zip file to folder in laptop, and flashed boot.img from it, using fastboot. Not sure if there would be any difference if I use the boot.img from usual signed zip file.
-> Then I rebooted to fastboot again, and flashed the recovery.img.
-> Thats when I booted to recovery, and updated the zip(I already moved earlier to sd in step 2) through default yureka recovery.
-> Once installation was completed, I cleared the catche again, as suggested by others.
Let me know if you need fastboot commands. The fastboot works using the verdor id as fastboot -i 0x1ebf. For ex.
fastboot -i 0x1ebf flash boot boot.img
And you can almost always login in fastboot, by
-> connecting USB to computer, and pressing power button, and volume down key together.
And on windows 8 the fastboot drivers are named as YunOS phone.
Zips link Signed http://click.xda-developers.com/api/click?format=go&jsonp=vglnk_14294725084389&key=f0a7f91912ae2b52e0700f73990eb321&libId=i8ov035t01000n4o000DL15p41qflr64vu&loc=http%3A%2F%2Fforum.xda-developers.com%2Fyureka%2Fgeneral%2Fdiscussion-yu-yureka-cm-12s-lollipop-t3084461&v=1&out=http%3A%2F%2Fbuilds.cyngn.com%2Fcyanogen-os%2Ftomato%2F12.0-YNG1TAS0W0-tomato%2F56deeca328%2Fcm-12.0-YNG1TAS0W0-tomato-signed.zip&title=DISCUSSION%3A%20YU%20Yureka%20CM%2012(S)%20Lollipop%20Upda%E2%80%A6%20%7C%20YU%20Yureka%20%7C%20XDA%20Forums&txt=http%3A%2F%2Fbuilds.cyngn.com%2Fcyanogen-os%2F...ato-signed.zip
Fastboot: http://click.xda-developers.com/api/click?format=go&jsonp=vglnk_142947255030510&key=f0a7f91912ae2b52e0700f73990eb321&libId=i8ov035t01000n4o000DL15p41qflr64vu&loc=http%3A%2F%2Fforum.xda-developers.com%2Fyureka%2Fgeneral%2Fdiscussion-yu-yureka-cm-12s-lollipop-t3084461&v=1&out=http%3A%2F%2Fbuilds.cyngn.com%2Fcyanogen-os%2Ftomato%2F12.0-YNG1TAS0W0-tomato%2F56deeca328%2Fcm-12.0-YNG1TAS0W0-tomato-signed-fastboot.zip&title=DISCUSSION%3A%20YU%20Yureka%20CM%2012(S)%20Lollipop%20Upda%E2%80%A6%20%7C%20YU%20Yureka%20%7C%20XDA%20Forums&txt=http%3A%2F%2Fbuilds.cyngn.com%2Fcyanogen-os%2F...d-fastboot.zip
Let me know if you have any questions. Cheers.

abeyhere said:
Kailas proper procedure, I won't know, as there may be a better way . However I'd tell you what worked for me.
-> I downloaded the zips (fastboot, and signed one, from http://forum.xda-developers.com/yureka/general/discussion-yu-yureka-cm-12s-lollipop-t3084461).
-> I moved the signed zip(cm-12.0-YNG1TAS0W0-tomato-signed-fastboot.zip) version to External SD card.
-> I extracted the fastboot zip file to folder in laptop, and flashed boot.img from it, using fastboot. Not sure if there would be any difference if I use the boot.img from usual signed zip file.
-> Then I rebooted to fastboot again, and flashed the recovery.img.
-> Thats when I booted to recovery, and updated the zip(I already moved earlier to sd in step 2) through default yureka recovery.
-> Once installation was completed, I cleared the catche again, as suggested by others.
Let me know if you need fastboot commands. The fastboot works using the verdor id as fastboot -i 0x1ebf. For ex.
fastboot -i 0x1ebf flash boot boot.img
And you can almost always login in fastboot, by
-> connecting USB to computer, and pressing power button, and volume down key together.
And on windows 8 the fastboot drivers are named as YunOS phone.
Zips link Signed http://click.xda-developers.com/api/click?format=go&jsonp=vglnk_14294725084389&key=f0a7f91912ae2b52e0700f73990eb321&libId=i8ov035t01000n4o000DL15p41qflr64vu&loc=http%3A%2F%2Fforum.xda-developers.com%2Fyureka%2Fgeneral%2Fdiscussion-yu-yureka-cm-12s-lollipop-t3084461&v=1&out=http%3A%2F%2Fbuilds.cyngn.com%2Fcyanogen-os%2Ftomato%2F12.0-YNG1TAS0W0-tomato%2F56deeca328%2Fcm-12.0-YNG1TAS0W0-tomato-signed.zip&title=DISCUSSION%3A%20YU%20Yureka%20CM%2012(S)%20Lollipop%20Upda%E2%80%A6%20%7C%20YU%20Yureka%20%7C%20XDA%20Forums&txt=http%3A%2F%2Fbuilds.cyngn.com%2Fcyanogen-os%2F...ato-signed.zip
Fastboot: http://click.xda-developers.com/api/click?format=go&jsonp=vglnk_142947255030510&key=f0a7f91912ae2b52e0700f73990eb321&libId=i8ov035t01000n4o000DL15p41qflr64vu&loc=http%3A%2F%2Fforum.xda-developers.com%2Fyureka%2Fgeneral%2Fdiscussion-yu-yureka-cm-12s-lollipop-t3084461&v=1&out=http%3A%2F%2Fbuilds.cyngn.com%2Fcyanogen-os%2Ftomato%2F12.0-YNG1TAS0W0-tomato%2F56deeca328%2Fcm-12.0-YNG1TAS0W0-tomato-signed-fastboot.zip&title=DISCUSSION%3A%20YU%20Yureka%20CM%2012(S)%20Lollipop%20Upda%E2%80%A6%20%7C%20YU%20Yureka%20%7C%20XDA%20Forums&txt=http%3A%2F%2Fbuilds.cyngn.com%2Fcyanogen-os%2F...d-fastboot.zip
Let me know if you have any questions. Cheers.
Click to expand...
Click to collapse
Are you sure this worked for you,cause basically you are just saying that you did the normal rooting procedure that we did when we had kitkat,just that you used a 64 bit recovery this time

Stock recovery for CM 12
abeyhere said:
-> I flashed the official CMD 12S, and flashed supersu alongwith, the first time when it was released, i.e. Thursday evening.
-> I was rooted to begin with, setup everything, everything worked.
-> Out of curiosity, rebooted to recovery to check the recovery, what it is. I was on clock work mod recovery, when I was on kit kat.
-> That's when my device would go to YU screen, and never go beyond that.
-> Luckily, I could still go into adb shell and fastboot. I flashed, the default boot and recovery from the original 12S zip, and logged into recovery again. Then used the update process in default recovery, to install 12S again.
-> So far so good. I can go to recovery as well.
-> What different I did this time, well did not root my device using supersu. So whoever have rooted your device using older supersu, would suggest to reboot to recovery, and if it breaks, you can still get your device back, by the process I mentioned, but that would confirm that old supersu could break recovery.
Click to expand...
Click to collapse
Can you tell you you flashed the cm12 recovery ???
i cannot find it inside the cm12 update zip file.

abeyhere said:
Kailas proper procedure, I won't know, as there may be a better way . However I'd tell you what worked for me.
-> I downloaded the zips (fastboot, and signed one, from http://forum.xda-developers.com/yureka/general/discussion-yu-yureka-cm-12s-lollipop-t3084461).
-> I moved the signed zip(cm-12.0-YNG1TAS0W0-tomato-signed-fastboot.zip) version to External SD card.
-> I extracted the fastboot zip file to folder in laptop, and flashed boot.img from it, using fastboot. Not sure if there would be any difference if I use the boot.img from usual signed zip file.
-> Then I rebooted to fastboot again, and flashed the recovery.img.
-> Thats when I booted to recovery, and updated the zip(I already moved earlier to sd in step 2) through default yureka recovery.
-> Once installation was completed, I cleared the catche again, as suggested by others.
Let me know if you need fastboot commands. The fastboot works using the verdor id as fastboot -i 0x1ebf. For ex.
fastboot -i 0x1ebf flash boot boot.img
And you can almost always login in fastboot, by
-> connecting USB to computer, and pressing power button, and volume down key together.
And on windows 8 the fastboot drivers are named as YunOS phone.
Zips link Signed http://click.xda-developers.com/api/click?format=go&jsonp=vglnk_14294725084389&key=f0a7f91912ae2b52e0700f73990eb321&libId=i8ov035t01000n4o000DL15p41qflr64vu&loc=http%3A%2F%2Fforum.xda-developers.com%2Fyureka%2Fgeneral%2Fdiscussion-yu-yureka-cm-12s-lollipop-t3084461&v=1&out=http%3A%2F%2Fbuilds.cyngn.com%2Fcyanogen-os%2Ftomato%2F12.0-YNG1TAS0W0-tomato%2F56deeca328%2Fcm-12.0-YNG1TAS0W0-tomato-signed.zip&title=DISCUSSION%3A%20YU%20Yureka%20CM%2012(S)%20Lollipop%20Upda%E2%80%A6%20%7C%20YU%20Yureka%20%7C%20XDA%20Forums&txt=http%3A%2F%2Fbuilds.cyngn.com%2Fcyanogen-os%2F...ato-signed.zip
Fastboot: http://click.xda-developers.com/api/click?format=go&jsonp=vglnk_142947255030510&key=f0a7f91912ae2b52e0700f73990eb321&libId=i8ov035t01000n4o000DL15p41qflr64vu&loc=http%3A%2F%2Fforum.xda-developers.com%2Fyureka%2Fgeneral%2Fdiscussion-yu-yureka-cm-12s-lollipop-t3084461&v=1&out=http%3A%2F%2Fbuilds.cyngn.com%2Fcyanogen-os%2Ftomato%2F12.0-YNG1TAS0W0-tomato%2F56deeca328%2Fcm-12.0-YNG1TAS0W0-tomato-signed-fastboot.zip&title=DISCUSSION%3A%20YU%20Yureka%20CM%2012(S)%20Lollipop%20Upda%E2%80%A6%20%7C%20YU%20Yureka%20%7C%20XDA%20Forums&txt=http%3A%2F%2Fbuilds.cyngn.com%2Fcyanogen-os%2F...d-fastboot.zip
Let me know if you have any questions. Cheers.
Click to expand...
Click to collapse
I did install the rom from the fastboot method still it did not work. I am fed up of the CM12 rom.

Zenfone 2- Need To Go Back To Stock Recovery For OTA

How to remove twrp and put stock recovery
Hi guys, can you please help me with this problem?
Yesterday i went for CM 12.1 but didn't like it at all, I installed it via twrp...
So now i flashed asus rom 2.20.40.59, but i want to put OTA and i can't do it with TWRP.How can i put stock recovery and remove twrp? I tried several methods, but none of them worked for me...
Thanks in advance!

I couldnt put stock recovery either.

Please take a look at this thread:
http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
the method of flashing stock recovery is the same as flashing the twrp.
Here's a link to the stock recovery collection from the same thread:
http://www.mediafire.com/folder/setyy42t2cymy#dy87k1a0f8m81

You can flash any recovery without PC by using [ROOT] Rashr - Flash Tool.
Search at play store.

thezibrail said:
Please take a look at this thread:
http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
the method of flashing stock recovery is the same as flashing the twrp.
Here's a link to the stock recovery collection from the same thread:
http://www.mediafire.com/folder/setyy42t2cymy#dy87k1a0f8m81
Click to expand...
Click to collapse
I try to flash stock recovery with adb (fastboot flash recovery recovery.img) but when I try to enter in recovery I got an Error screen.
I also noticed in the bootloader screen that the product_name is Z008, but I have Z00A with 4Gb ram..
Any solution?
edit: do you know if are there other link for recovery stock files?

Yco.giusti said:
I try to flash stock recovery with adb (fastboot flash recovery recovery.img) but when I try to enter in recovery I got an Error screen.
I also noticed in the bootloader screen that the product_name is Z008, but I have Z00A with 4Gb ram..
Any solution?
edit: do you know if are there other link for recovery stock files?
Click to expand...
Click to collapse
Thats so strange about ur phone model!!
I've got zenfone ze550ml, model is z008, 2 GB ram . for recovery I downloaded this one: http://www.mediafire.com/folder/setyy42t2cymy#ma3w61exgyy06
and perhaps u have already converted into stock recovery.
When u get an error screen while trying to go to recovery mode (probablu u saw a dead android bot with an error) press and hold power button, then (while holding power button) quickly press Vol up and release and then also release power button..
hope this helps. i had the same error screen

thezibrail said:
Thats so strange about ur phone model!!
I've got zenfone ze550ml, model is z008, 2 GB ram . for recovery I downloaded this one: http://www.mediafire.com/folder/setyy42t2cymy#ma3w61exgyy06
and perhaps u have already converted into stock recovery.
When u get an error screen while trying to go to recovery mode (probablu u saw a dead android bot with an error) press and hold power button, then (while holding power button) quickly press Vol up and release and then also release power button..
hope this helps. i had the same error screen
Click to expand...
Click to collapse
I tried to use your method but no result then I tried to flash stock rom with twrp and I don't know why, this time work(maybe because I wipe data and cache first, or maybe I was on cyanogen rom and not paranoid). Then i flash the stock recovery and apply ota. Now the model on bootloader is z00A again.
OT: Anyway every rom, with his bugs, is better than asus stock. Damn!

how to flash stock rom using twrp (ZE550ML/Z008)
i saw ur post and u mentioned that u again installed asus stock rom using twrp.
as far as i know, for installing stock rom, u must use the stock recovery.
it will be very helpful if u kindly post the stapes to flash stock recovery via twrp
i am now in cm12.1 but i could not roll back to stock rom inspite i flashed the original stock recovery
i am desparate to roll back in stock recovery and rom and get ota update for the upcoming periods
peace (Y)
---------- Post added at 05:09 AM ---------- Previous post was at 05:06 AM ----------
Yco.giusti said:
I tried to use your method but no result then I tried to flash stock rom with twrp and I don't know why, this time work(maybe because I wipe data and cache first, or maybe I was on cyanogen rom and not paranoid). Then i flash the stock recovery and apply ota. Now the model on bootloader is z00A again.
OT: Anyway every rom, with his bugs, is better than asus stock. Damn!
Click to expand...
Click to collapse
i am on also unofficiam cm12.1 nightly
i also want to get back to stock rom
will u plz tell me the stages u followed to port stock rom in ur device via twrp
i am using (ZE550 ML /Z008)

Yco.giusti said:
I tried to use your method but no result then I tried to flash stock rom with twrp and I don't know why, this time work(maybe because I wipe data and cache first, or maybe I was on cyanogen rom and not paranoid). Then i flash the stock recovery and apply ota. Now the model on bootloader is z00A again.
OT: Anyway every rom, with his bugs, is better than asus stock. Damn!
Click to expand...
Click to collapse
Asus stock would have been good without the bloat wares.

I tried to flash stock rom in my asus zenfone 2, but it said that, "the package is for Z008 but this is Z00A" but my phone is ZE550ML (Z008). I dun know why I can't get back to stock rom using twrp. I also tried to side load "update.zip" from ADB sideload using stock recovery but it also shows error. this time it says "This package is older than the Build"
Sent from my ASUS_Z008 using Tapatalk

update rom stock with twrp
Hello,
I have only install twrp recovery (no root) but now how do I update ota with TWRP ?
if not possible, Can i update the rom stock with twrp?
I try with "file.zip" from asus site but don't work.
I read some threads but I could not understand...
thanks for help me

Just "fastboot flash" recovery and splashscreen from YOUR model.

RealYoti said:
Just "fastboot flash" recovery and splashscreen from YOUR model.
Click to expand...
Click to collapse
thanks for answer...
where can i found the recovery?
I don't understand much, sorry...
can you write me a small and quick guide?
very grateful

All recoveries are here: http://www.mediafire.com/folder/setyy42t2cymy
From fastboot/bootloader mode:
Code:
fastboot flash recovery recovery.img
fastboot flash splashscreen splashscreen.img
Fastboot is a program in Android SDK tools.

Now I understand...thank you very much....
Can I use this command line:
adb sideload file.zip (file.zip is the file of firmware zip that I download of asus - for exemple: UL-Z00A-WW-2.18.40.12-user.zip.)
this command line has some effect on the bootloader or recovey?
sorry for my many questions...I'm learning...

bozzy_guzz said:
Can I use this command line:
adb sideload file.zip (file.zip is the file of firmware zip that I download of asus - for exemple: UL-Z00A-WW-2.18.40.12-user.zip.)
Click to expand...
Click to collapse
Yes, from/in recovery. And better use shortest command (e.g. "adb sideload d:\adb\update.zip") or you'll get an error.
bozzy_guzz said:
this command line has some effect on the bootloader or recovey?
sorry for my many questions...I'm learning...
Click to expand...
Click to collapse
Your bootloader will be untouched, recovery will be updated (if you flash newer zip) or untouched (for same version).

RealYoti said:
Yes, from/in recovery. And better use shortest command (e.g. "adb sideload d:\adb\update.zip") or you'll get an error.
Your bootloader will be untouched, recovery will be updated (if you flash newer zip) or untouched (for same version).
Click to expand...
Click to collapse
thanks for your time...
Last question...
I use the command line "adb sideload d:\adb\update.zip" and I have installed TWRP recovery
I think that twrp becomes a recovery stock...Is it correct?

bozzy_guzz said:
I use the command line "adb sideload d:\adb\update.zip" and I have installed TWRP recovery
Click to expand...
Click to collapse
"ADB sideload" work with stock recovery only, as I know. Just reinstall TWRP after.

RealYoti said:
"ADB sideload" work with stock recovery only, as I know. Just reinstall TWRP after.
Click to expand...
Click to collapse
done everything ok, thanks
I read that twrp support "adb sideload".
1.entry in twrp
2.select advanced
3.select adb sideload
4.lunch the command line:
- adb devices (for device is recognized)
if this is correct lunch the command line:
- adb sideload name_Zip_Rom.zip
I have not tried it yet...when I will install a new update will try it.

bozzy_guzz said:
done everything ok, thanks
I read that twrp support "adb sideload".
1.entry in twrp
2.select advanced
3.select adb sideload
4.lunch the command line:
- adb devices (for device is recognized)
if this is correct lunch the command line:
- adb sideload name_Zip_Rom.zip
I have not tried it yet...when I will install a new update will try it.
Click to expand...
Click to collapse
don't work it...

TWRP install on G4 H815 20A mm, doesn't stick (unlocked bootloader by LG official)

Hi,
I get TWRP running on phone , but when I boot into recovery , I always get the Standard Recovery, only option being a factory reset. Have opted for this factory reset and that is exactly what I get, no TWRP :crying:
Thanks

Also if you reboot to recovery through TWRP itself, it won't stick? If not: Is rooting an option for you? If yes: Try Flashify and flash it through this nifty little app .

MickyFoley said:
If not: Is rooting an option for you? If yes: Try Flashify and flash it through this nifty little app .
Click to expand...
Click to collapse
Thanks,
Yes rooting is where I want to go by means of TWRP and flashing these
Marshmallow custom kernel for root — Link | File: STOCK-20a-ROOTED.zip (16.5 MB)
Click to expand...
Click to collapse
I did have Twrp running on this phone but had to reinstall the full 6.00kdz to get out of a bootloop and since then TWRP won't sick.
thanks

More than one way to skin a cat. went HERE chainfire Systemless Root 2.61 using Running TWRP from PC
Update on getting TWRP to stick. ......... I had success using following
adb reboot bootloader
Click to expand...
Click to collapse
fastboot flash recovery twrp-2.8.7.0-h815.img
Click to expand...
Click to collapse
When done, execute “fastboot reboot”
Click to expand...
Click to collapse

This happened to me, too. Here is what i did:
Boot your device into fastboot mode via adb, straight up boot to recovery ("fastboot boot twrp-2.8.7.0-h815.img"), transfer the recovery image to your device, then flash it from within TWRP (there is an option for that within the normal install menu, its called "install image" or something like that). Hope this helps, it did for me.
Edit: Just realized you already found a solution. Never mind.

Ive the same problem. I unlocked the bootloader by the official procedure. Then i tried to flash twrp but it doesnt install truly. It always appear the stock recovery. I tried also clockrecovery but nothing. No recovery wants to get installed. Pls help me i want a custom rom on my g4

use twrp v2.8.7.0 on 20A mm....... adb reboot bootloader, fastboot boot twrp-2.8.7.0-h815.img, and to double check you have recovery,adb reboot recovery and then flash STOCK-20a-ROOTED

chester2011 said:
use twrp v2.8.7.0 on 20A mm....... adb reboot bootloader, fastboot boot twrp-2.8.7.0-h815.img, and to double check you have recovery,adb reboot recovery
Click to expand...
Click to collapse
Ok the one i tried is the newest. Ill gonna try the one u told me. But the line u wrote wont install twrp it will only boot it

setaf said:
Ok the one i tried is the newest. Ill gonna try the one u told me. But the line u wrote wont install twrp it will only boot it
Click to expand...
Click to collapse
sorry, fastboot flash recovery twrp-2.8.7.0-h815.img, instead of fastboot boot twrp-2.8.7.0-h815.img worked for me after hours and hours of boot loops and restoring

chester2011 said:
sorry, fastboot flash recovery twrp-2.8.7.0-h815.img, instead of fastboot boot twrp-2.8.7.0-h815.img worked for me after hours and hours of boot loops and restoring
Click to expand...
Click to collapse
Also u had problem with the 3.0 ? Ill update you later

setaf said:
Also u had problem with the 3.0 ? Ill update you later
Click to expand...
Click to collapse
yep.. but currently running with xposed and g4 tweaksbox (paid version) nicely

ok update:
finaly i got twrp 2.8.7.0 on my g4 (thanx chester) but i still cannot flash cyanogen.
when i try to do it by recovery i get the error message 7 then when i start the system im in damn bootloop
what i can do ?

flash twrp version 3.0.2.0

setaf said:
ok update:
finaly i got twrp 2.8.7.0 on my g4 (thanx chester) but i still cannot flash cyanogen.
when i try to do it by recovery i get the error message 7 then when i start the system im in damn bootloop
what i can do ?
Click to expand...
Click to collapse
you can upgrade twrp with the twrp manager from playstore (once youve got twrp and root of course)

TRWP Install help

I am trying to install TWRP on my swift.
I have installed android sdk and google drivers. Windows 10 adb and fastboot dont see the swift.
ABD shows no devices listed
Fastboot shows "8bce440" when "fastboot devices" is run
fastboot -i 0x2970 erase recovery sits at "waiting for any devices"
I have uninstalled sdk twice. Restarted laptop. Tried two different usb cables.
I am stumped. Any help guys.

You did the unlock bootloader bit in settings?

ReneX10 said:
You did the unlock bootloader bit in settings?
Click to expand...
Click to collapse
Hi cheers for replying.
Yeah I've unlocked bootloader in settings.
not sure what I'm not seeing.

GigahurtzUK said:
Hi cheers for replying.
Yeah I've unlocked bootloader in settings.
not sure what I'm not seeing.
Click to expand...
Click to collapse
Love to help more, but I've always used linux to fastboot.
Pretty sure with my swift the erase cmd didn't work for me, but the flash sudo fastboot -i 0x2970 flash recovery '/home/XXXX/Downloads/crackling-t0x1.img' did
Have you tested fastboot with any other devices? just as an experiment

ReneX10 said:
Love to help more, but I've always used linux to fastboot.
Pretty sure with my swift the erase cmd didn't work for me, but the flash sudo fastboot -i 0x2970 flash recovery '/home/XXXX/Downloads/crackling-t0x1.img' did
Have you tested fastboot with any other devices? just as an experiment
Click to expand...
Click to collapse
No other devices to test with.
I will have to try linux then. I just need a usb to make a linux live usb
Cheers

GigahurtzUK said:
I am trying to install TWRP on my swift.
I have installed android sdk and google drivers. Windows 10 adb and fastboot dont see the swift.
ABD shows no devices listed
Fastboot shows "8bce440" when "fastboot devices" is run
fastboot -i 0x2970 erase recovery sits at "waiting for any devices"
I have uninstalled sdk twice. Restarted laptop. Tried two different usb cables.
I am stumped. Any help guys.
Click to expand...
Click to collapse
If you see the device when command "fastboot devices" is used,
just enter "fastboot erase recovery" without the -i parameter.
This worked for me.

Is this the norm when changing recovery.img?
M_Kay said:
If you see the device when command "fastboot devices" is used,
just enter "fastboot erase recovery" without the -i parameter.
This worked for me.
Click to expand...
Click to collapse
i have cm-13.0-20160127-NIGHTLY-crackling-recovery.img installed, should i do the erase? i just flash it using TWRP 2.8.7.1, it is working when i install the cm13.0 but i couldn't install gapp - just hang. Is this the norm when changing the recovery? also can i revert back to the previous recovery img?

noob2016 said:
i have cm-13.0-20160127-NIGHTLY-crackling-recovery.img installed, should i do the erase? i just flash it using TWRP 2.8.7.1, it is working when i install the cm13.0 but i couldn't install gapp - just hang. Is this the norm when changing the recovery? also can i revert back to the previous recovery img?
Click to expand...
Click to collapse
I would replace the nightly recovery with the TWRP recovery img, because it has more options and you can backup your whole system.
So yes erase it and flash TWRP .8.7.1 recovery.
Are you stuck in a bootloop?
If you have intalled TWRP recovery boot into it and under option Wipe format the system and data folder (carefull your data will be lost!!!) . After that flash the nighthly rom again without gapps and check if you can boot.

Thanks for the fast reply and help
M_Kay said:
I would replace the nightly recovery with the TWRP recovery img, because it has more options and you can backup your whole system.
So yes erase it and flash TWRP .8.7.1 recovery.
Are you stuck in a bootloop?
If you have intalled TWRP recovery boot into it and under option Wipe format the system and data folder (carefull your data will be lost!!!) . After that flash the nighthly rom again without gapps and check if you can boot.
Click to expand...
Click to collapse
1st thanks for fast reply and help
im not in bootloop, thank goodness!
I'm currently in TWRP, when the recovery was in CM the gapp-arm64-aroma-5.1 it installed flawlessly following the cm12.1 flash but after the update 13.0 the gapp can't be installed even reverting back to 12.1 and using the same files. I did wipe all prior to change of rom also match it (i.e. cm13.0 to gapp 6.0).
Maybe this will solve it. I will try to erase recovery and re-install TWRP
i will report back after. Thanks

Works
Thanks it worked on pico gapp but not in aroma
followed the erase command and install TWRP again.
Many thanks

TWRP not working in Aroma Gapp need fix
In the previous post, i was able to install twrp but i found out on many trial and error that open gapp aroma/full doesn't work both on cm12.1 and cm13.0 using TWRP. Also cm13.0 recovery will not work with open gapp aroma/full.
What works: (haven't tried all version)
On TWRP - i was able to use arm64-pico-6.0 on cm13.0 20160130
On CM Recovery - arm64-aroma-5.1 on cm12.1 20160107
This is based on my experience with the HELP of the awesome people in the forum. I just want to let you know and maybe it will be useful to other noobs like me

noob2016 said:
In the previous post, i was able to install twrp but i found out on many trial and error that open gapp aroma/full doesn't work both on cm12.1 and cm13.0 using TWRP. Also cm13.0 recovery will not work with open gapp aroma/full.
What works: (haven't tried all version)
On TWRP - i was able to use arm64-pico-6.0 on cm13.0 20160130
On CM Recovery - arm64-aroma-5.1 on cm12.1 20160107
This is based on my experience with the HELP of the awesome people in the forum. I just want to let you know and maybe it will be useful to other noobs like me
Click to expand...
Click to collapse
This TWRP works wioth aroma gapps
https://s.basketbuild.com/devs/beroid/Wileyfox%20Swift%20-%20Crackling/TWRP

Thanks
robin0800 said:
This TWRP works wioth aroma gapps
https://s.basketbuild.com/devs/beroid/Wileyfox%20Swift%20-%20Crackling/TWRP
Click to expand...
Click to collapse
Thanks for the info and fast reply.
Will this work on Wileyfox Swift? i currently have TWRP 2.8.7.1 size 24.4mb but the link above is in 2.8.7.0 size 15.1mb

noob2016 said:
Thanks for the info and fast reply.
Will this work on Wileyfox Swift? i currently have TWRP 2.8.7.1 size 24.4mb but the link above is in 2.8.7.0 size 15.1mb
Click to expand...
Click to collapse
Works well on mine both for AROMA and cryogenmod nightly updates and to install c-apps for cm13 unoficial

I will try
robin0800 said:
Works well on mine both for AROMA and cryogenmod nightly updates and to install c-apps for cm13 unoficial
Click to expand...
Click to collapse
Thanks for the reply and also on my other post.
Since this is for swift, i will try to install but sadly i have given it back already. It was just here for the upgrade and when i got the chance to get hold of it again i will definitely try and report back.
Many thanks.

Following the various instructions for both TWRP and CM recoveries provide the same frustrating result: I'm getting a black screen when I reboot into recovery.
Everything seemed to go ok on the flashing using ADB but then when replacing the battery and vol-down +power to reboot into recovery I'm greeted with nothing.
Subsequent reboots into recovery from the OS reinstate the Cyanogen recovery.
What am I doing wrong?
Thanks

msiviter said:
Following the various instructions for both TWRP and CM recoveries provide the same frustrating result: I'm getting a black screen when I reboot into recovery.
Everything seemed to go ok on the flashing using ADB but then when replacing the battery and vol-down +power to reboot into recovery I'm greeted with nothing.
Subsequent reboots into recovery from the OS reinstate the Cyanogen recovery.
What am I doing wrong?
Thanks
Click to expand...
Click to collapse
The easy way
Install recovery in bootloader mode with fastboot flash recovery "the name of your recovery"
Hold volume down
issue this command fastboot reboot
when phone restarts you can release volume down the phone should now boot to your new recovery
Note TWP version 3.0.0 is out https://www.androidfilehost.com/?w=files&flid=48495

robin0800 said:
The easy way
Install recovery in bootloader mode with fastboot flash recovery "the name of your recovery"
Hold volume down
issue this command fastboot reboot
when phone restarts you can release volume down the phone should now boot to your new recovery
Note TWP version 3.0.0 is out https://www.androidfilehost.com/?w=files&flid=48495
Click to expand...
Click to collapse
I think it was a windows 10 problem, I gave it all another try this morning firstly using the WinDroid Universal Android Toolkit to Unlock Bootloader and flash TWRP . I then rebooted into recovery and hey presto TWRP. Flashing CM13 nightly and pico gapps was then childsplay.
Any ideas why google play didnt offer to auto restore all my apps? Thats a bit of a pain.
Otherwise very pleased, phone seems a bit more responsive using CM13 than CyanogenOS. I tried to format my SD to use as internal storage too but i couldnt see them separately afterwards to free up device storage so I reverted back.
Thanks for trying to help.

Yey!!!
robin0800 said:
Note TWP version 3.0.0 is out https://www.androidfilehost.com/?w=files&flid=48495
Click to expand...
Click to collapse
Confirmed!!! It works... i used TWRP 3.0. Works on both aroma and pico. Thanks so much!!!!

Got stuck in a TWRP loop after installation. Regardless which reboot option I choose, always TWRP 3.0.0 comes up. No idea what I did wrong but for me it is of more interest how to get rid of it. Accessible external SD contains cm14-zip and also Stock 6.0.1. Installed CM14 multiple times, but has no impact on what comes up after selecting reboot/reboot recovery/reboot fastboot - it is always TWRP. Tried it also via adb sideload from within TWRP, no change of behaviour. Same when I tried to install stock rom.
Bootloader issue? How to get it back? I have 2 further Swifts available so I can dump several necessary partitions from them, but I need to know which tools are required, since I usually deal with MTK-based androids. Backup of userdata and sdcards is available, so if a reset to stock is necessary, this is not a problem from that point of view - if I only would have the info, how to get back a working bootloader.
Even though I love this recovery, it is obviously annoying ... Any help appreciated. Tnx in advance!
Edit: Fixed. I removed the battery for several hours and without battery with plugged in USB cable (not the WF one, I have tons of them lying arround here) I was able to reboot to normal fastboot. From then on it was strraightforward:
checked OEM lock status via fastboot command on PC
flashed newest TWRP
rebooted to TWRP
installed Stock ROM to get all partitions reinitialized correctly
rebooted to OS - YEAH, the swift lives again
Rebooted to recovery
Installed CM14 and OpenGApps Nano (ARM, not ARM64, since it produces an error)
Reboot to OS - YEAH, here we are.