Database Develop

[Q] OTA Update with custom recovery?

Hello! I received the 1.29.1540.16 update today. I have the Team Win's recovery flashed on my Dev Edition. When I try to update, TWRP starts and no update happens.
How should the OTA updates be addressed with custom recoveries?

Same here... I have a rooted Dev Edition with CWM Touch recovery. Got prompted to update to 1.29.1540.16 (currently on 1.29.1540.3). Tried to install a couple of times, but, it just reboots without installing the update.

mrcobain said:
Hello! I received the 1.29.1540.16 update today. I have the Team Win's recovery flashed on my Dev Edition. When I try to update, TWRP starts and no update happens.
How should the OTA updates be addressed with custom recoveries?
Click to expand...
Click to collapse
Flash stock recovery first.

MediocreFred said:
Same here... I have a rooted Dev Edition with CWM Touch recovery. Got prompted to update to 1.29.1540.16 (currently on 1.29.1540.3). Tried to install a couple of times, but, it just reboots without installing the update.
Click to expand...
Click to collapse
i think you have to install stock recovery and maybe relock bootloader

skinsfanbdh said:
i think you have to install stock recovery and maybe relock bootloader
Click to expand...
Click to collapse
%$($*&%(@%... I was too hasty. Rebooted to recovery, wiped cache and tried to flash the downloaded OTA update zip (named OTA_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.16_R-1.29.1540.3_release_318620_signednimix5ealszkrygs.zip) which I found in the downloads folder.
It started the installation, and is now hung at the "Running bug-fix1 tool..." step.
Not sure how long I should wait before aborting it. Am concerned that aborting (forcing a reboot) will cause more damage.

MediocreFred said:
%$($*&%(@%... I was too hasty. Rebooted to recovery, wiped cache and tried to flash the downloaded OTA update zip (named OTA_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.16_R-1.29.1540.3_release_318620_signednimix5ealszkrygs.zip) which I found in the downloads folder.
It started the installation, and is now hung at the "Running bug-fix1 tool..." step.
Not sure how long I should wait before aborting it. Am concerned that aborting (forcing a reboot) will cause more damage.
Click to expand...
Click to collapse
abort and restore you backup

Aborted... rebooted... looks OK. Still on 1.29.1540.3. Still prompted to update. So, basically, status quo.
Looked around for stock recovery - the only ones I find are the 401 (instead of 1540) - which, if I understand, is from the international version and NOT the Dev Edition. Can anybody please help me get the stock recovery for the Dev Edition. (My first nandroid backup was *after* installing CWM and rooting.)

MediocreFred said:
Aborted... rebooted... looks OK. Still on 1.29.1540.3. Still prompted to update. So, basically, status quo.
Looked around for stock recovery - the only ones I find are the 401 (instead of 1540) - which, if I understand, is from the international version and NOT the Dev Edition. Can anybody please help me get the stock recovery for the Dev Edition. (My first nandroid backup was *after* installing CWM and rooting.)
Click to expand...
Click to collapse
you may be able to get it to install if your on a stock rom but im not sure about it

Yeah, I have stock ROM. Looks like I have to do what this person has done here.
Has to wait until I get home this evening.

MediocreFred said:
Yeah, I have stock ROM. Looks like I have to do what this person has done here.
Has to wait until I get home this evening.
Click to expand...
Click to collapse
or just flash the ruu for your phone

But, doesn't flashing the RUU wipe apps/data? I'd like to do this in the least destructive way possible. If I can get away with just flashing original recovery, installing the OTA update and flashing CWM back, I'll be happy.

yes it will. if you can get away with that then go for it

I have cwm installed on my htc one and I couldn't ruu my one back to a stock image. It would freeze up during the flash image process in the beginning.

No harm in trying the 401 or 707 recoveries ... if OTA doesnt work, just hard reboot and flash another
AND REMEMBER - NO NEED TO RELOCK FOR OTA UPDATES !

Ok got this to work and here's how, it goes without saying that this was my experience and the steps I used and I by no means accept any responsibility for any of these steps functioning on any other device...
I was using TWRP 2.5 and was rooted but otherwise was still on the stock rom that my developer edition shipped with.
I went here and downloaded the stock recovery for .16.
I opened the rar file which included other bat files to push the recovery but I didn't use that. I went to the fastboot folder and pulled the recovery.img file and dropped it in my M7 all in one tool kit folder under data and recoveries.
I then plugged in the phone and opened the toolkit and flashed my own recovery and followed the directions in the toolkit. After reboot the device came up and wanted to load the update which I let it do.
It went through and loaded and the scroll bar went all the way to the end and stuck. I waiting ten minutes and when it didn't restart I held the power button for about 15 seconds (until buttons stopped flashing) and the device screen went blank and I let go of the power button.
At this point it went through a couple screens where it appeared to be loading the update. Scroll bar went to the end and the device restarted and did that again. On the third restart it did a full boot and was good.
I then went back to the toolkit and flashed the TWRP recovery and then after reboot I went into recovery and flashed supersu to get root back.
Not sure if this helps anyone but wanted to share my experience...
MG

[Q] Error sideloading 4.4 on GPE HTC one

I'm getting the following error updating my htc one to 4.4 using the google provided zip file.
I'm able to adb sideload the zip file to the device in ClockworkMod Recovery v6.0.3.2 but I get the following error message on the device:
Code:
Warning: No file_contextsPackage expects build fingerprint of htc/m7_google/m7:4.3/JWR66Y.H1/239564:user/release-keys or htc/m7_google/m7:4.4/KRT16S.H5/280886:user/release-keys; this device has cingular_us/m7/m7:4.1.2/JZO54K/166754:12:user/release-keys
E: Error in /tmp/update.zip
(Status 7)
Installation aborted.
Any ideas how I can fix this? Honestly I never use any of the rooted features, so if there's just a way to wipe my device and go back to stock recovery and everything I'd even go for that.

The error is right there in your message:
expects build fingerprint of htc/m7_google/m7:4.3/JWR66Y.H1/239564:user/release-keys or htc/m7_google/m7:4.4/KRT16S.H5/280886:user/release-keys;
this device has cingular_us/m7/m7:4.1.2/JZO54K/166754:12:user/release-keys
So looks like your device is NOT GPE converted or perhaps running a GPE custom rom. In short you need:
- Unlock bootloader (you may have this already)
- Install custom recovery + root ( you may have this already )
- S-Off ( you will need to run the correct rumrunner/moonshine/revone S-Off)
- Then install the full GPE RUU from http://forum.xda-developers.com/showthread.php?t=2358781

SaHiLzZ said:
The error is right there in your message:
expects build fingerprint of htc/m7_google/m7:4.3/JWR66Y.H1/239564:user/release-keys or htc/m7_google/m7:4.4/KRT16S.H5/280886:user/release-keys;
this device has cingular_us/m7/m7:4.1.2/JZO54K/166754:12:user/release-keys
So looks like your device is NOT GPE converted or perhaps running a GPE custom rom. In short you need:
- Unlock bootloader (you may have this already)
- Install custom recovery + root ( you may have this already )
- S-Off ( you will need to run the correct rumrunner/moonshine/revone S-Off)
- Then install the full GPE RUU from http://forum.xda-developers.com/showthread.php?t=2358781
Click to expand...
Click to collapse
I'm really not sure how I got in this state I unlocked a long time ago using the htc all in one tool, and then I didn't end up really needing root. As it stands I've tried everything - i even did a factory reset and I went back to 4.2.2 and the OTA updates still don't work. They show up in the stock recovery with the sideways android and a red exclamation and the unhelpful message "Error".
I tried also doing the GPE RUU install you mentioned and I got the following error:
Code:
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
Really, at this point I'm willing to re-wipe my device and do anything, just to get back to a stock GPE that can accept OTA updates.

[Q] HTC One. stuck in recovery error flashing roms

okay so i went through a bit of problems, and now i can only access recovery/bootloader because the rom i originally flashed messed up for some reason
anyways, im in recovery i use : adb push rom.zip /sdcard/rom.zip
it works i get the rom
i got to install from sd card
and when i flash the rom i get the error unable to open zip file. i also tried sideload but to avail.
any suggestions?
using TWRP, S-off , unlocked.
trying to flash a 4.4 rom
EDIT:::
after pushing loads of times, i guess the rom pushed correctly, anyways i try to flash here's what i get:
set_metadata_recursive: some changes failed
E: error executing updater binary in zip

for 4.4 roms you need twrp 2.6.3.3

baadnewz said:
for 4.4 roms you need twrp 2.6.3.3
Click to expand...
Click to collapse
ah im using 2.6.3.0 at the moment, ill try getting 2.6.3.3 and seeing if it works
thanks in advance!
EDIT: IT WORKED! thanks so much

[Q] Soft-Brick Reverted to S-ON and Can't Flash ROMs

Hi guys, I've been working on my ATT m7 for a day or so now.
Story:
I was on CWM recovery and CyanogenMod 11 M7 without any issues for a long time, rooted, S-OFF, etc. Phone all of a sudden got a bunch of force closes and errors such as "com.google.gapps has encountered an error and needs to close" it would repeatedly appear. I tried killing apps, force closing apps, etc to no avail.
I restarted the phone and it froze on the HTC logo. Hard reset, same thing. Wouldn't go past HTC logo. No big deal, went into recovery, cleared cache, Dalvik, reboot, hangs on HTC logo. Kept trying this, same result. Decided to just factory wipe and try that. Used adb to pull my files off the phone, then factory wiped, still no luck, hangs on HTC logo. Tried reflashing previously working CyanogenMod zip, no luck.
Flashed TWRP recovery and tried all of the above again, still no luck. Strangely, TWRP says it looks like my phone is not rooted and asks to install su. I verified root through adb shell, but TWRP still reports no root. Also verified in TWRP going to console and "whoami" gives "root" so not sure what's going on there.
Tried an RUU that looked like it was working, but then randomly failed out ERR 155.
Then I just happened to notice my bootloader says I now have S-ON! Wtf?
Not really sure what to try at this point, you guys have any suggestions?
Edit:
Just tried flashing a stock ATT Sense OTA zip but TWRP gives errors:
Full SELinux support is present
E: Unable to mount '/cache'
E: Unable to mount '/cache'
MTP Enabled
Installing '/sdcard/TWRP/ATT_Sense6_OTAPkg.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
file_getprop: failed to stat "/system/build.prop": No such file or directory
E: Error executing updater binary in zip '/sdcard/TWRP/ATT_Sense6_OTAPkg.zip'
Error flashing zip '/sdcard/TWRP/ATT_Sense6_OTAPkg.zip'
Updating partition details
E: Unable to mount '/cache'
eguh.

wingman358 said:
Hi guys, I've been working on my ATT m7 for a day or so now.
Story:
I was on CWM recovery and CyanogenMod 11 M7 without any issues for a long time, rooted, S-OFF, etc. Phone all of a sudden got a bunch of force closes and errors such as "com.google.gapps has encountered an error and needs to close" it would repeatedly appear. I tried killing apps, force closing apps, etc to no avail.
I restarted the phone and it froze on the HTC logo. Hard reset, same thing. Wouldn't go past HTC logo. No big deal, went into recovery, cleared cache, Dalvik, reboot, hangs on HTC logo. Kept trying this, same result. Decided to just factory wipe and try that. Used adb to pull my files off the phone, then factory wiped, still no luck, hangs on HTC logo. Tried reflashing previously working CyanogenMod zip, no luck.
Flashed TWRP recovery and tried all of the above again, still no luck. Strangely, TWRP says it looks like my phone is not rooted and asks to install su. I verified root through adb shell, but TWRP still reports no root. Also verified in TWRP going to console and "whoami" gives "root" so not sure what's going on there.
Tried an RUU that looked like it was working, but then randomly failed out ERR 155.
Then I just happened to notice my bootloader says I now have S-ON! Wtf?
Not really sure what to try at this point, you guys have any suggestions?
Edit:
Just tried flashing a stock ATT Sense OTA zip but TWRP gives errors:
Full SELinux support is present
E: Unable to mount '/cache'
E: Unable to mount '/cache'
MTP Enabled
Installing '/sdcard/TWRP/ATT_Sense6_OTAPkg.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
file_getprop: failed to stat "/system/build.prop": No such file or directory
E: Error executing updater binary in zip '/sdcard/TWRP/ATT_Sense6_OTAPkg.zip'
Error flashing zip '/sdcard/TWRP/ATT_Sense6_OTAPkg.zip'
Updating partition details
E: Unable to mount '/cache'
eguh.
Click to expand...
Click to collapse
you can not flash OTA, these are patches, not complete rom and when flashed over the appropriate rom version, must be done using stock recovery, not twrp.
What version of twrp are you using? CM11 need block:by-name support in the recovery kernel.
For your s-on issue, you probably have used 'fastboot oem writesecureflag3' command by mistake

alray said:
you can not flash OTA, these are patches, not complete rom and when flashed over the appropriate rom version, must be done using stock recovery, not twrp.
What version of twrp are you using? CM11 need block:by-name support in the recovery kernel.
For your s-on issue, you probably have used 'fastboot oem writesecureflag3' command by mistake
Click to expand...
Click to collapse
Thanks for the info... do you recommend trying a stock rom or CM11? I'm on the latest TWRP, it's v2.8.0.2.
And regarding the command 'fastboot oem writesecureflag3' I've never seen it before, and certainly haven't issued it by hand. Whether the command was issued by some tool or file I've tried, I don't know.
EDIT:
I think the reason for the RUU failure may be due to the version, I believe it was trying to flash 1.xx over 3.xx. Does that sound right? Also, is it correct that I need stock recovery and locked bootloader for a RUU??

wingman358 said:
Thanks for the info... do you recommend trying a stock rom or CM11? I'm on the latest TWRP, it's v2.8.0.2.
And regarding the command 'fastboot oem writesecureflag3' I've never seen it before, and certainly haven't issued it by hand. Whether the command was issued by some tool or file I've tried, I don't know.
EDIT:
I think the reason for the RUU failure may be due to the version, I believe it was trying to flash 1.xx over 3.xx. Does that sound right? Also, is it correct that I need stock recovery and locked bootloader for a RUU??
Click to expand...
Click to collapse
Well somehow I was able to flash a stock ROM ([ROM][4.4.2] - AT&T 4.18.502.7 Stock Rooted from this thread). Then flashed PA_gapps over (with dalvik and cache wipe before and after flashes).
On boot, it cleared the HTC logo (finally!). Then it hit me with "Google search has stopped unexpectedly" and goes back to the HTC logo... wtf... then it popped up "Dialer has stopped unexpectedly"... then the home screen came up, and it rebooted itself.
After rebooting, I swiped to unlock the screen and it showed the dreaded white HTC logo... ugh, then it hits me in quick succession with "Hangouts has stopped" "Google Play Music has stopped" "Youtube has stopped" and so on. If I hit the screen off button then turn it on, it showed the lock screen. The lock screen seemed fine, the clock worked, and swiping to unlock worked, but when it unlocked instead of the home screen it showed the white HTC logo. Eventually it rebooted itself. After I think the third time rebooting itself, the android setup/configuration came up. "_____ has stopped" keeps popping up.
I was able to restore contacts and stuff by signing into my google account, but I am almost continually getting "_____has stopped" pop-ups, and if I let the phone sit for a few minutes it reboots itself maybe every 5 minutes or so. Also I don't think I have cell service (it just shows an X with no bars). It seems normal aside from those (not much home screen lag, apps open, wifi seems to work).
I did a permissions fix from recovery which completed without errors, but it didn't seem to help.

wingman358 said:
Well somehow I was able to flash a stock ROM ([ROM][4.4.2] - AT&T 4.18.502.7 Stock Rooted from this thread). Then flashed PA_gapps over (with dalvik and cache wipe before and after flashes).
Click to expand...
Click to collapse
Why flashing gapps over a stock sense rom?

alray said:
Why flashing gapps over a stock sense rom?
Click to expand...
Click to collapse
Great question... I've been in the habit of always flashing gapps after flashing rom, does gapps come with stock rom??

wingman358 said:
Great question... I've been in the habit of always flashing gapps after flashing rom, does gapps come with stock rom??
Click to expand...
Click to collapse
Yes, wipe everything and reflash the rom

alray said:
Yes, wipe everything and reflash the rom
Click to expand...
Click to collapse
That did it! Wiped, reflashed, and no more force closes, not one. Thanks a bunch alray!!!

Soft Bricked m7 on hboot 1.44. How to completely wipe + flash recovery + flash rom?

Hello everyone,
I recently ran into a bit of problem with my HTC One m7 (early model). Back when I first got it I performed an HTC Dev bootloader unlock and ever since I've been flashing different roms through TWRP. The other day I tried downgrading from Android 5 to 4.2 and something went wrong. The Aroma installer for AndroidRevolutionHD hung at 10% for about an hour, and I decided to restart. Upon restart, TWRP greeted me with messages such as
"E:/ cannot mount system" or "E:/ cannot mount cache".
After changing through various TWRP revisions (2.6.1 seemed to remove the system error), I still have not been able to install any ROMS successfuly. I tried different versions of ARHD and ViperROM but they all seem unable to install to some part of the filesystem, and the phone never boots.
Is there a way to gain S-OFF while in this dummy state?
Is there a way to flash over everything and get a clean recovery and rom working (through fastboot/terminal)?
All help is appreciated. Thanks a lot.

Rarestg said:
Hello everyone,
I recently ran into a bit of problem with my HTC One m7 (early model). Back when I first got it I performed an HTC Dev bootloader unlock and ever since I've been flashing different roms through TWRP. The other day I tried downgrading from Android 5 to 4.2 and something went wrong. The Aroma installer for AndroidRevolutionHD hung at 10% for about an hour, and I decided to restart. Upon restart, TWRP greeted me with messages such as
"E:/ cannot mount system" or "E:/ cannot mount cache".
After changing through various TWRP revisions (2.6.1 seemed to remove the system error), I still have not been able to install any ROMS successfuly. I tried different versions of ARHD and ViperROM but they all seem unable to install to some part of the filesystem, and the phone never boots.
Is there a way to gain S-OFF while in this dummy state?
Is there a way to flash over everything and get a clean recovery and rom working (through fastboot/terminal)?
All help is appreciated. Thanks a lot.
Click to expand...
Click to collapse
1- recovery is too old, you need at least 2.6.3.3 or higher, you could check 2.8.6.4 universal build
2- FAQ Sticky in particular page 3
3- as for S-OFF, if you are truly on such old firmware, then
---> hboot 1.44 dated pre June 2013, you can use this with revone
---> or rumrunner

nkk71 said:
1- recovery is too old, you need at least 2.6.3.3 or higher, you could check 2.8.6.4 universal build
2- FAQ Sticky in particular page 3
3- as for S-OFF, if you are truly on such old firmware, then
---> hboot 1.44 dated pre June 2013, you can use this with revone
---> or rumrunner
Click to expand...
Click to collapse
Thanks for the advice, but after updating to TWRP 2.8.6.4 it still displays " E: unable to mount '/system' ". Tried flashing the stock rom that you linked in that thread but its installer hangs again while "formatting partitions".
If I try to flash a stock recovery, how do I avoid updating hboot? Also is it possible to use revone or rumrunner without access to the Android system? Both guides seem to depend upon Android working on said system.

Rarestg said:
Thanks for the advice, but after updating to TWRP 2.8.6.4 it still displays " E: unable to mount '/system' ". Tried flashing the stock rom that you linked in that thread but its installer hangs again while "formatting partitions".
If I try to flash a stock recovery, how do I avoid updating hboot? Also is it possible to use revone or rumrunner without access to the Android system? Both guides seem to depend upon Android working on said system.
Click to expand...
Click to collapse
1- revert back to twrp 2.6.3.3 as mentioned in the faq
2- do the [real] formats in twrp 2633
3- then flash rom (take your pick, adb push, sideload or otg)
4- get s-off (provided the per-requisites are met)