Can someone please help with this ?
I'm want to flash the stock recovery in order to receive the 4.2.2 OTA update (currently I have the stock 4.1.2 + root + TWRP + S-OFF)
Can someone guide me please, what stock recovery do I need to flash and where should I grab it from ?
I've found only this link http://forum.xda-developers.com/showthread.php?t=2158763
Not sure if is the right recovery but the download link from there is broken
Any idea if I need to be S-OFF or ON in order to receive the OTA ?
That's old thread. Run either a ruu or Mike's stock. Be sure u have stock recovery as well.
Sent from my HTC One
where can I have the stock recovery ? (I can't find it)
- Ok after a lot of digging around I've found a stockrecovery.img file , so I've flashed that like this: fastboot flash recovery stockrecovery.img
- the spooky part after doing this was that I was unable to enter into recovery anymore , the screen alway remained in Entering Recovery and that was it ... maybe someone explain why ?
- then I've locked the bootloader like this: fastboot oem lock
- then I've installed a RUU for Europe (also found out here after diggin around) which actually downgraded my firmware to an older version
- after downgrade I've received an OTA update to a newer firmware - did that
- then after I've received the 4.2.2 OTA update , finaly
- then I've performed a bootloader unlock
- then I've flashed a TWRP recovery image in order to root the device
Now here comes the issue, after flashing the TWRP recovery image, while entering into the TWRP recovery I'm not able to click on any menu , is like the touch screen does not take any input so I'm unable to install the SU binaries
Has anyone encountered this issue ?
How did you root your stock 4.2.2 device ?
Reflashed the CWM recovery (instead of TWRP) as somebody recommend it and it worked - now I have root, too.
dinoc said:
Reflashed the CWM recovery (instead of TWRP) as somebody recommend it and it worked - now I have root, too.
Click to expand...
Click to collapse
Hi there,
i have the exact same problem, the screen wont register touches. How do i reflash CMW? im a noob
You are going to flash it in the same manner you did with the TWRP.
You put your phone into fastboot then issue a command like :
fastboot flash recovery cwm_image_name
You should search for a cwm recovery image file.
And you need to have the bootloader unlocked
After update to 4.2.2 TWRP wont recocnize touch due to the driver update.
Here is a modified version of TWRP where touch work with 4.2.2 OTA
Download and rename it to howdoyouwant.img then
fastboot flash recovery howdoyouwant.img
fastboot erase cache
Related
Hello,
I have a Developer Edition (unlocked) with Stock 4.3 at the moment, is rooted and with TWRP 2.6.3.0 custom recovery, my phone is asking me to upgrade to 4.4. My questions are:
- What would be the results of the upgrade?
- It will flash over my custom recovery without problems?
I guess I will loose root and custom recovery but I can flash them again, my main concern is that the OTA will not flash correctly for being rooted and with custom recovery. Thanks a lot for those that know the answer and want to help me.
gustavorod said:
Hello,
I have a Developer Edition (unlocked) with Stock 4.3 at the moment, is rooted and with TWRP 2.6.3.0 custom recovery, my phone is asking me to upgrade to 4.4. My questions are:
- What would be the results of the upgrade?
- It will flash over my custom recovery without problems?
I guess I will loose root and custom recovery but I can flash them again, my main concern is that the OTA will not flash correctly for being rooted and with custom recovery. Thanks a lot for those that know the answer and want to help me.
Click to expand...
Click to collapse
i guess you cant flash official OTA through custom recovery..u need stock recovery to do this
gustavorod said:
Hello,
I have a Developer Edition (unlocked) with Stock 4.3 at the moment, is rooted and with TWRP 2.6.3.0 custom recovery, my phone is asking me to upgrade to 4.4. My questions are:
- What would be the results of the upgrade?
- It will flash over my custom recovery without problems?
I guess I will loose root and custom recovery but I can flash them again, my main concern is that the OTA will not flash correctly for being rooted and with custom recovery. Thanks a lot for those that know the answer and want to help me.
Click to expand...
Click to collapse
Actually, you won't be able to do an OTA update when you've a custom recovery (you shouldn't even get it in the first place, sometimes it comes through), if you try to apply the OTA, you'll boot back to the TWRP recovery.
So, you should either go full stock (recovery & ROM), then do an OTA. Or flash some 4.4 Custom ROM.
By itself the phone alerted me that the OTA download is available and wants to download and flash itself as it did when it upgraded from 4.2.2 to 4.3 so I am not planning to flash through TWRP...
gustavorod said:
By itself the phone alerted me that the OTA download is available and wants to download and flash itself as it did when it upgraded from 4.2.2 to 4.3 so I am not planning to flash through TWRP...
Click to expand...
Click to collapse
it will download OK, but when it reboots to start installing, you'll just see the TWRP screen and nothing is gonna happen; because the OTA expects stock recovery.
Thanks!!!!
I guess I better flash another 4.3 or 4.4 by myself, I just thought the OTA would be better first to upgrade to the latest firmware...
gustavorod said:
I guess I better flash another 4.3 or 4.4 by myself, I just thought the OTA would be better first to upgrade to the latest firmware...
Click to expand...
Click to collapse
you can do two things:
1- get s-off and flash any firmware you want
2- "download & install later" the OTA, once downloaded pull it to your PC, the OTA file will contain a "firmware.zip" which is signed and can be flashed in fastboot ruu mode (you have to issue the flash command twice!!!), which would upgrade your firmware (including hboot, kernal and recovery), but will leave your rom intact
----- because it flashes recovery, you need to reflash custom recovery
----- and, kernel (boot.img) you'll need to reflash the custom one (or dirty install the ROM), otherwise the ROM won't boot up
nkk71 said:
you can do two things:
1- get s-off and flash any firmware you want
2- "download & install later" the OTA, once downloaded pull it to your PC, the OTA file will contain a "firmware.zip" which is signed and can be flashed in fastboot ruu mode (you have to issue the flash command twice!!!), which would upgrade your firmware (including hboot, kernal and recovery), but will leave your rom intact
----- because it flashes recovery, you need to reflash custom recovery
----- and, kernel (boot.img) you'll need to reflash the custom one (or dirty install the ROM), otherwise the ROM won't boot up
Click to expand...
Click to collapse
I've looked around for a CWM compatible version of the Dev Edition + Root, but I'm not finding one. Is anyone aware of a CWM-packaged version that I can flash using CWM on a rooted device? Reverting to stock to pick up the OTA seems like a long way to go
I have been using "fastboot boot recovery.img" to load into TWRP after OTA updates to load SuperSU as I am only rooted using the stock ROM. However, after this recent update (2.16.651.4) that includes the WiFi Calling and Android 4.4.3, when I run the command it just causes the phone to reboot. It does not reboot into TWRP, which is my recovery.img file.
I found a Nexus thread talking about having to add a kernel command line for the Nexus after a certain version of hboot, so I am not sure if it is related.
Does anyone know how to fastboot boot now with the latest update? I would like to avoid replacing my stock recovery with TWRP and just continue to boot into it. Alternatively, is there any other way to install supersu?
Thank you,
Ben
ReproOne said:
I have been using "fastboot boot recovery.img" to load into TWRP after OTA updates to load SuperSU as I am only rooted using the stock ROM. However, after this recent update (2.16.651.4) that includes the WiFi Calling and Android 4.4.3, when I run the command it just causes the phone to reboot. It does not reboot into TWRP, which is my recovery.img file.
I found a Nexus thread talking about having to add a kernel command line for the Nexus after a certain version of hboot, so I am not sure if it is related.
Does anyone know how to fastboot boot now with the latest update? I would like to avoid replacing my stock recovery with TWRP and just continue to boot into it. Alternatively, is there any other way to install supersu?
Thank you,
Ben
Click to expand...
Click to collapse
As a quick work around flash twrp onto the device, once done with it then flash the factory recovery back, Also check to make sure your bootloader didn't relock after update.
stock recovery from the update.
nfinitefx45 said:
As a quick work around flash twrp onto the device, once done with it then flash the factory recovery back, Also check to make sure your bootloader didn't relock after update.
stock recovery from the update.
Click to expand...
Click to collapse
Thank you for the reply. I thought about taking that approach, but I was really hoping someone would have an answer on why the procedure wasn't working now. My bootloader is still unlocked.
I found this as an approach someone did on the Nexus 4 for a similar issue:
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
Thoughts?
nfinitefx45:
I did just now flash TWRP into recovery, loaded SuperSU, and then flashed your recovery.img back to the phone. So thank you very much for the recovery.img.
I'd still like to know if fastboot boot can still work, and also if there is a way in the future I can get my own recovery.img (possibly back it up before taking an OTA)?
ReproOne said:
nfinitefx45:
I did just now flash TWRP into recovery, loaded SuperSU, and then flashed your recovery.img back to the phone. So thank you very much for the recovery.img.
I'd still like to know if fastboot boot can still work, and also if there is a way in the future I can get my own recovery.img (possibly back it up before taking an OTA)?
Click to expand...
Click to collapse
not sure about the fastboot issue, but to backup your recovery any time just go to adb and type the following
adb shell
su
dd if=/dev/block/mmcblk0p43 of=/sdcard2/recovery.img
this will copy your recovery to the external sdcard
Thank you for those steps. I do not have an external SD card installed, so I modified it to store the recovery.img on sdcard instead.
Now I can always fastboot flash twrp and then back to stock recovery.
Thank you again!
nfinitefx45 said:
not sure about the fastboot issue, but to backup your recovery any time just go to adb and type the following
adb shell
su
dd if=/dev/block/mmcblk0p43 of=/sdcard2/recovery.img
this will copy your recovery to the external sdcard
Click to expand...
Click to collapse
You would need root to do this. Not being able to use "fastboot boot" you would just be backing up the flashed recovery. Possibly towel root temp root, but I would assume it has been patched in newest update.
So I am S-On with a non-HK M8
I was on stock rooted 4.4.2 and I flashed the stock recovery and took the OTA
Now I am on 4.4.3 and still have SuperSU installed (not rooted)
Everything is working fine, but when I try to boot to recovery i get the red triangle with the !
Any suggestions?
neudof said:
So I am S-On with a non-HK M8
I was on stock rooted 4.4.2 and I flashed the stock recovery and took the OTA
Now I am on 4.4.3 and still have SuperSU installed (not rooted)
Everything is working fine, but when I try to boot to recovery i get the red triangle with the !
Any suggestions?
Click to expand...
Click to collapse
That's the stock recovery. Did you ever flash a custom recovery back on after the OTA?
xPhantom said:
That's the stock recovery. Did you ever flash a custom recovery back on after the OTA?
Click to expand...
Click to collapse
I am s-on & unlocked but i was able to flash the stock recovery from sd card to take the ota.
Is it possible to flash twrp back in the same way?
neudof said:
I am s-on & unlocked but i was able to flash the stock recovery from sd card to take the ota.
Is it possible to flash twrp back in the same way?
Click to expand...
Click to collapse
Yes, after the OTA, just flash TWRP back through fastboot and then re-flash SuperSU to get root back.
nfinitefx45 said:
As a quick work around flash twrp onto the device, once done with it then flash the factory recovery back, Also check to make sure your bootloader didn't relock after update.
stock recovery from the update.
Click to expand...
Click to collapse
I just applied the update released today, and I tried to save the recovery.img file before flashing TWRP. However, it kept giving me permission denied. Do you have the recovery.img file from the update released today so I can use it for the next update?
fastboot not working
please any help on how to access fastboot on HTC one m8.
its showing black screen n fastboot mode...
wot can I do 2 annul d problem
rooting problem
hey i am using htc one m8, i unlocked the bootloader and the device reads as
device status modified
*unlocked*
s-on
after this i flashed twrp and cwm a couple of times but its not loading on the device but shows success in the command window, however after clicking on recovery the custom recovery does not show up, and it reboots back into the fastboot mode.
please help me
thank you
jinal shah said:
hey i am using htc one m8, i unlocked the bootloader and the device reads as
device status modified
*unlocked*
s-on
after this i flashed twrp and cwm a couple of times but its not loading on the device but shows success in the command window, however after clicking on recovery the custom recovery does not show up, and it reboots back into the fastboot mode.
please help me
thank you
Click to expand...
Click to collapse
What's the output in the terminal when you fastboot flash recovery?
rooting problem
It doesn't show any error as such.
In the command window it shows successful.
But when I click on recovery it reboots back to fast boot.
Like for a second it shows the screen which reads 'this build is only for developers'
But then instead of opening Twrp it reboots back to fast boot.
Hi all.
This is a moment that I'm disconnected hacks because I am in stock (6.0.401.11) and satisfied. I had OTA updates without problems until this kitkat version but today after receiving and downloading 2 times the OTA lollipop I can not install it because installation starts well and some moments later, the screen is stuck on the phone with red triangle and I have this in the recovery:
Verifying current system ...
"/ System / bin / reboot" has unexpected content
Installation aborted
Even when I do it manually, it's the same. Yet I have just manually switch successfully 6.0.401.12 that I missed somehow.
What's the trouble?
kamso said:
Hi all.
This is a moment that I'm disconnected hacks because I am in stock (6.0.401.11) and satisfied. I had OTA updates without problems until this kitkat version but today after receiving and downloading 2 times the OTA lollipop I can not install it because installation starts well and some moments later, the screen is stuck on the phone with red triangle and I have this in the recovery:
Verifying current system ...
"/ System / bin / reboot" has unexpected content
Installation aborted
Even when I do it manually, it's the same. Yet I have just manually switch successfully 6.0.401.12 that I missed somehow.
What's the trouble?
Click to expand...
Click to collapse
this says to me, in system/bin you have modified files, you must be 100% stock so flash TWRP recovery then use this: https://www.androidfilehost.com/?fid=95864024717072880 to retore full stock rom.
DO NOT try and root or anything, 100% pure stock required.
Full Reboot into android
boot back to recovery and flash this pre-load data here: https://www.androidfilehost.com/?fid=95864024717072879
Full reboot into android
You will need TWRP recovery for both of the above files, but you will also need to flash stock recovery afterwards to update which is here: https://www.androidfilehost.com/?fid=95864024717072472
fastboot flash recovery
fastboot erase cache
fastboot reboot-bootloader
full reboot into android, then update.
DO NOT try and root or anything, 100% pure stock required.
Seanie280672 said:
this says to me, in system/bin you have modified files, you must be 100% stock so flash TWRP recovery then use this: https://www.androidfilehost.com/?fid=95864024717072880 to retore full stock rom.
DO NOT try and root or anything, 100% pure stock required.
Full Reboot into android
boot back to recovery and flash this pre-load data here: https://www.androidfilehost.com/?fid=95864024717072879
Full reboot into android
You will need TWRP recovery for both of the above files, but you will also need to flash stock recovery afterwards to update which is here: https://www.androidfilehost.com/?fid=95864024717072472
fastboot flash recovery
fastboot erase cache
fastboot reboot-bootloader
full reboot into android, then update.
DO NOT try and root or anything, 100% pure stock required.
Click to expand...
Click to collapse
Ok, thank you. But what I don't understand is that there's a long time I'm no more root, I'm full stock (Rom, recovery...), only S-off and Unlocked. So Why for previous OTA updates I have not had this problem? Why I have to manually update successfully from 6.09.401.11 version to 6.09.401.12 one? Why it is only the upgrade to the Lollipop which has problem?
What is the preload data? I already have this: https://www.androidfilehost.com/?w=...0f40a2a319761577a4c3f1e723594b05669cb009e9d00
Can I flash it and the stock recovery only?
Your problem is the lack or corruption of the file /bin/reboot
2 solutions:
Flash a custom recovery and reflash the rom
Flash a custom recovery and replace the file
migascalp said:
Your problem is the lack or corruption of the file /bin/reboot
2 solutions:
Flash a custom recovery and reflash the rom
Flash a custom recovery and replace the file
Click to expand...
Click to collapse
Ok thanks. I'm downloading the Rom and I have to flash it through TWRP, flash stock recovery and try OTA update again.
kamso said:
Ok thanks. I'm downloading the Rom and I have to flash it through TWRP, flash stock recovery and try OTA update again.
Click to expand...
Click to collapse
preload data is HTC's little hidden way of stopping you getting OTA's if you unlock your bootloader, and yes it is required to update, without it, updates will fail.
Seanie280672 said:
preload data is HTC's little hidden way of stopping you getting OTA's if you unlock your bootloader, and yes it is required to update, without it, updates will fail.
Click to expand...
Click to collapse
Ah Ok I understand. These are applications that disappear when we unlock the bootloader. I had already installed them there's a long time. As I said my OTA updates passed without problem.
Problem flashing stock Rom in TWRP:
"- Zip signature verification failed
- Error flashing zip"
I don't understand anything, what's happen?
Problem solved and phone updated. Thank you!!!
Dear xda_users,xda_devs
Greetings .
I am using HTC one M7 UL . I have downloaded 3 gb of updates from OTA. as I was not using it from 2 years, it upgraded from 2.xxx -> 7.xx i.e Sense 6 and Android 5.0 , In between update process I flashed cwm (TWRP is not working ,idk why, fastboot boot recovery command is also not working),and figured out that when i try to install OTA it fails , some check sum or signature failure was there .
And when i flashed a stock recovery from my phone my phone was kind of soft reset , and it went to version 2.xxx . So I have to download all the updates again, which I did , now my question is how can I make a nandroid backup without flashing custom recovery , as if I flash a custom recovery after updating . 1. I download update , it wont install from OTA. 2. I used by backup which i created from cwm it will restore my phone to that date . but cwm will be also recovered , so My point of backup will be useless.
Conclusion :- I need to install updates from OTA , plus I need root as well ( Sadly fastboot boot recovery.img is not working ). I am having no issues with custom recoveries but I have to install OTA .And also why my phone get reset when I flashed my stock recovery , it didnt happened in cwm or TWRP or philz
In seek of help
Thanking You
rahulnegi1409
Hi guys, I have to flash a recovery stock to update via OTA. Should I use a recovery related to my serial number (as explained here) or can I use a generic recovery for EMUI 5.0? On my p9 Plus now I have EMUI 5.0.3
Briefly, I saved an EMUI 5.0 recovery on my PC, can I always use this or after every new update the recovery changes and I have to flash a new one looking at my build number?
Sorry for my noob question, thanx in advance
Guys, nobody can help me?
1st, if you have rooted your phone you must do a full update (download the full update package)
2nd for the recovery flash the image of your current version, and next time never flash moded recovery img on recovery partition, you must flash it in recovery2 partition (cmd : fastboot flash recovery2 recovery_image.img)
xzanium said:
1st, if you have rooted your phone you must do a full update (download the full update package)
2nd for the recovery flash the image of your current version, and next time never flash moded recovery img on recovery partition, you must flash it in recovery2 partition (cmd : fastboot flash recovery2 recovery_image.img)
Click to expand...
Click to collapse
Thanx for your answer, really interesting! So if I flash TWRP on recovery2 partition I will be able to update directly via OTA from the update menu on my phone without connect it to pc even if I'm rooted because I maintain my stock recovery on recovery partition?
And after update I have to re-root my phone or this method keep it safe?
yes, you can update directly.
and after the update you have to re-flash TWRP on recovery2 and re-root your phone, and mabye you need to re-unlock your phone first
xzanium said:
yes, you can update directly.
and after the update you have to re-flash TWRP on recovery2 and re-root your phone, and mabye you need to re-unlock your phone first
Click to expand...
Click to collapse
Ok I understand, thanx a lot! :good: